Deal with ambiguity in TargetResolver where a mass-only molecule had very small differences in iRT library and document…

… (mass serialized as "344.300548579909" vs "344.300548580")

In the TargetResolver constuctor, there's one code path that does this:
                _targetsByName = targets.Select(t => t.ToSerializableString())
                    .Distinct()
                    .Select(Target.FromSerializableString).ToLookup(GetTargetDisplayName);

This part of it:
Select(t => t.ToSerializableString())
                    .Distinct()
                    .Select(Target.FromSerializableString)

round-trips the target to a string, and I think it is important for removing duplicates.
The other code path does not do that:
_targetsByName = accessions.ToLookup(a => a.Item1, a => a.Item2);
I'm thinking a better fix might be to change:
foreach (var target in targets)
to:
foreach (var target in targets.Select(t=>t.ToSerializableString()).Distinct().Select(Target.FromSerializableString))
on line 68 in TargetResolver.cs

I'll have a look, thanks!

@nickshulman OK, a slightly different take on your idea, normalizes everything at the start of the ctor.


Consistent Makefile between Medik8s Operators - Updating Targets

For better collaboration I am aligning our Makefiles, and this is the first PR.
It would be easier (or not) to see changes, commit after commit.

Add PHONY to each target and update it's description (use make help)
Use kubectl or oc and 'test-no-verify` target (for passing CI test when there are uncommitted changes).

/hold
Waiting with the other PRs, till we finish the next releases. It is not urgent.

/hold cancel
A new try to make consistent Makefile, the PR's description has been changed

/retest

Since the changes require reordering the file and for better reviewing the changes I am splitting this PR.
Next PRs will include Operator-sdk upgrade changes,Bundle CSV fixes, Reordering Makefile by categories and Updating Go, K8s.

/lgtm


Reduce callback allocations

Additional allocations were found in the callbacks in this build: https://buildkite.com/clima/climaatmos-ci/builds/10766#0188f5d4-9d79-4469-a5ed-e39286c5f014 when running at a higher sample rate.

I also added save_to_disc_func, and it looks like the majority is coming from type instabilities in ClimaCore's write!. Maybe we can fix this with a function barrier.

It looks like that will mostly fix the issue (it's still the top allocator, though). Builds:

https://buildkite.com/clima/climaatmos-ci/builds/10791#0188f96b-cf72-4cfb-8f7e-e2813efd8ed9
https://buildkite.com/clima/climaatmos-ci/builds/10794#0188f9a8-3e51-437b-89e6-7b4e5124249b


example(slack-qa-bot): Add slack QA bot example

Description
This PR fixes #
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

I'm also preparing a blog post to explain step by step how to deploy and how it works!


Allow arbitrary arguments to be passed into casper.

Allow custom arguments to be passed into casper, and on to PhantomJS.
(Sorry for duplicate pull request, messed up my branches a little and I couldn't edit the old request)

Thanks


Update  Nathanmac namespace

This needs to specify that it's a class namespace

::class only works (and is only required) outside string quoting.  Both cases this PR is attempting to change are already quoted, so this change would actually break the code.

Also, PHP 5.4 doesn't support ::class at all either way...


Update jquery-mockjax to 2.1.1

I think the title speaks for itself!

thanks a mucho :+1:  @YoranBrondsema

:+1:


Added 5 new GPTs in Education and philosophy

Added GPTs in Education and philosophy categories.

thanks for your contribution @Shivak11


Make os freeze on ubuntu like Chromium

I solve the problem of Chromium with the help of the answer blow.
https://askubuntu.com/questions/765974/chrome-freeze-very-frequently-with-ubuntu-16-04
I guess it is the same problem on vscode. Can anyone check this?

If this seems to be Electron related

I have no clue.

Can you follow this wiki and post the results back here to understand more about why performance is so bad for you: https://github.com/Microsoft/vscode/wiki/Performance-Issues
Thanks!

It seems not a performance issue. I'm going to  try  'code --disable-gpu'  first to see if the problem still exists.

OK


"From image" example results in stack overflow

Hello, I've tried testing this library using the "From image" example code from the readme, but the program seems to overflow its stack when calling ThemeBuilder::with_source.
I've tried using an image smaller than the 1080p one that the example uses, but it still crashes.
use material_colors::{
    image::{FilterType, ImageReader},
    theme::ThemeBuilder,
};

#[tokio::main]
async fn main() -> Result<(), reqwest::Error> {
    let image = reqwest::get("https://picsum.photos/200/300")
        .await?
        .bytes()
        .await?
        .to_vec();

    let mut data = ImageReader::read(image).expect("failed to read image");

    // Lancsoz3 takes a little longer, but provides the best pixels for color extraction.
    // However, if you don't like the results, you can always try other FilterType values.
    data.resize(128, 128, FilterType::Nearest);

    let theme = ThemeBuilder::with_source(ImageReader::extract_color(&data)).build();

    // Do whatever you want...

    Ok(())
}

I tried to reproduce your issue, but the code above works for me without errors.

Getting similar issue. From debugging it seems
let wu_result = QuantizerWu::default().quantize(pixels, max_colors, None);
is causing the issue

fixed in e90c351

have a same problem
use material_colors::{
    image::{FilterType, ImageReader},
    theme::ThemeBuilder,
};

#[tokio::main]
async fn main() -> Result<(), reqwest::Error> {
    let image = reqwest::get("https://picsum.photos/200/300")
        .await?
        .bytes()
        .await?
        .to_vec();

    let mut data = ImageReader::read(image).expect("failed to read image");

    data.resize(128, 128, FilterType::Nearest);
    let theme = ThemeBuilder::with_source(ImageReader::extract_color(&data)).build();

    Ok(())
}


README

As a bootcamp student,
I want the prework notes to be structured on a webpage,
So taht I can easily find and read the information.
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information
Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it


Fix broken from(Config) method in PB client config builder

Add tests for same.
Add convenience method to ClusterConfig for using 1 config across
many hosts.

+1 to merge


Add tests

[x] Add tests for builders
[x] Add tests for loading all modules
[x] Add tests for models inference
[x] Add tests for preprocessors inference
[x] Add tests for metrics inference
[x] Add tests for embeddings inference
[x] Add tests for creating dataloaders from datasets
[x] Add tests for one batch training with each trainer

This task was done in #121


Make: [docker-corpus-add] Error 137

[carstenh@archmoter8 bapc_meowkov]$ cat \#reddit-buildapc/bapc.log | sudo make docker-corpus-add
docker start meowkov_corpus
meowkov_corpus
docker start meowkov_irc
meowkov_irc
docker run -v /home/carstenh/git/bapc_meowkov/meowkov.conf:/meowkov/meowkov.conf:ro --link meowkov_corpus:redis -i --rm meowkov -import=true -purge=false
2015/08/15 13:06:09 IMPORT: loading piped data into corpus at localhost:6379
Makefile:43: recipe for target 'docker-corpus-add' failed
make: *** [docker-corpus-add] Error 137

Hey, second time loading stuff into the corpus. This time about 143MB of IRC logs from one channel. After some minutes importing it spit out this error code but I'm not sure what could have caused that.
Is there a way to debug this?

Nice! My test corpus was 10 smaller :-)) I reproduced the error with 150MB one and what I think is happening is that there are more goroutines than Redis was able to serve.
I added a buffered channel in https://github.com/lidel/meowkov/commit/7aa45d08a76af5467df33f7d00376d38d644a87b which limits the number of goroutines during corpus import and the issue seems to be fixed on my box.
Please run make docker-rebuild and let me know  if it fixed it for you too. :rocket:

2015/08/15 17:33:18 IMPORT: loading piped data into corpus at localhost:6379
2015/08/15 17:36:36 IMPORT finished, processed 2340625 lines

Yay! Issue got fixed, lovely.


Add EPUB support

Should add support for creating EPUB books using mmdutil. Will need the zipc code to do it...

Since codedoc can already do this and uses MMD to read markdown source files, not going to repeat it here.


Add cf services bridge

add bridge that measures cf services usage
rename the old cf bridge to applications
discard outdated documentation

Coverage decreased (-4.5%) to 86.234% when pulling 6421f4a3d8739b04e20ede036c15e8c8b880c5f7 on SAP:master_service_bridge into 9212a7805454499f50d1ae8dc8f197790df0322c on cloudfoundry-incubator:master.

Coverage increased (+0.03%) to 90.781% when pulling c2acc25ba889132cd74ffd2e69d19b49ebecdc8e on SAP:master_service_bridge into 9212a7805454499f50d1ae8dc8f197790df0322c on cloudfoundry-incubator:master.

Coverage increased (+0.08%) to 90.881% when pulling ed38b869830c12256e865a5e9929394fb64210b6 on SAP:master_service_bridge into 5418b479dd9b8a7895bccea6273e5424e7e0628a on cloudfoundry-incubator:master.

Coverage increased (+0.08%) to 90.881% when pulling ed38b869830c12256e865a5e9929394fb64210b6 on SAP:master_service_bridge into 5418b479dd9b8a7895bccea6273e5424e7e0628a on cloudfoundry-incubator:master.

Coverage increased (+0.08%) to 90.881% when pulling ed38b869830c12256e865a5e9929394fb64210b6 on SAP:master_service_bridge into 5418b479dd9b8a7895bccea6273e5424e7e0628a on cloudfoundry-incubator:master.

Coverage increased (+0.1%) to 90.935% when pulling ad6ee421216a89899729357bb33878f953f01946 on SAP:master_service_bridge into 5418b479dd9b8a7895bccea6273e5424e7e0628a on cloudfoundry-incubator:master.

Coverage increased (+0.1%) to 90.935% when pulling ad6ee421216a89899729357bb33878f953f01946 on SAP:master_service_bridge into 5418b479dd9b8a7895bccea6273e5424e7e0628a on cloudfoundry-incubator:master.


Fix space character in raise action.

The 'raise' action has an extra space character, causing incorrect suggestions in the editor and parameter mismatches in the actionTaken function. I have removed the extra space character from the raise action definition. This update ensures accurate code suggestions and correct function parameter handling, improving the overall functionality and reliability of the library.

Thanks for the fix!


Use smarter masks derived from the anatomy

Add subject-level "gray matter" masks from the freesurfer segmentation, and use an average of these at the group stage.

Closed with #106


Domino test case duplicate stones

Should the tests require all the values to be unique ? My understanding is that all pieces in a domino set are unique (Double 6's or Double 9's)
Duplicate (1,2)
https://github.com/exercism/xrust/blob/master/exercises/dominoes/tests/dominoes.rs#L149
Duplicate (2,4)
https://github.com/exercism/xrust/blob/master/exercises/dominoes/tests/dominoes.rs#L135
(1,2) == (2,1)?
https://github.com/exercism/xrust/blob/master/exercises/dominoes/tests/dominoes.rs#L121

wouldn't it be OK if we were using two domino sets though? see no reason why the dominoes would have to be unique

I am just trying to understand the rules of this "game". I have not really played this kind of loop "chain" dominos. I'd like to add more test cases to a Swift version I am working on.  My first impression is that all stones in a chain should be unique because most games with dominos are played using one one set of unique dominos. Otherwise we can have test cases like (1,1), (1,1), (1,1), (1,1), (1,1),  that would be valid but don't really make sense. Plus I'd like to expand my version to check to see if a stone can be inserted into a valid chain or if a stone can be removed and still have a valid chain etc.

Well, let's explain why those tests cases are there in the first place, they stop some incorrect solutions from falsely declaring a chain is possible when it isn't.
Consider the [(1, 2), (2, 1), (3, 4), (4, 3)] test case. Some solutions will falsely declare that a chain can be made of [(1, 2), (2, 1)] when this is incorrect because it hasn't used all the dominoes. Sure, it could be changed to [(1, 2), (2, 3), (1, 3), (4, 5), (5, 6), (4, 6)], but that seems unnecessary.
Similarly, [(1, 2), (2, 3), (3, 1), (2, 4), (2, 4)] is there to stop some solutions from falsely declaring that (1, 2), (2, 3), (3, 1) is a valid chain when it's clearly invalid because it hasn't used all the dominoes. Sure, it could be changed into [(1, 2), (2, 3), (3, 1), (2, 4), (4, 5), (5, 2)] but it also seems unnecessary.
Why did I say in both cases that something seems unnecessary? Becuase it over-complicates the test cases to expose simple problems. I think it should be a principle to find the simplest test case that exposes a problem.
I have no opinions about [(1, 2), (5, 3), (3, 1), (1, 2), (2, 4), (1, 6), (2, 3), (3, 4), (5, 6)] though. That was here long before my time.

Plus I'd like to expand my version to check to see if a stone can be inserted into a valid chain or if a stone can be removed and still have a valid chain etc.

You may find that those checks devolve into "is that domino of the form (x, x)?"
If the checks can affect multiple dominoes, then the checks become "are the dominoes themselves a valid chain?"

I see, is more about making it a little more challenging.


Update part1-ex2-job-retry.md

@osg-cat I don't think we mention max_retries in the lecture. @xamberl can say more as she went through the whole exercise and suggested this change.

@osg-cat Showmic is right, I removed reference to max_retries because the lecture materials did not mention it, making it confusing.


Returning exception to callback method receiving invalid json

As there are no/limited error handling mechanisms available for the end user now, returning exception to the callback method on getting an invalid json back from Google service.

manupsunny Please check out this one too which I did without first seeing your change:
https://github.com/jsoma/tabletop/pull/131
My version returns a status code such as 400 and 404 as soon as the xhr request fails.
I think our versions can be easily combined, since it may still be possible for the xhr request to succeed while the user still experiencing the same error later on. I will look into this later.
Also I think it would be nice to have standard messages for each HTTP status code based on what's usually the problem -- for example, an unpublished spreadsheet should result in a 403 error, while 404 is obviously an invalid URL, and 400 is some kind of less specific problem with the xhr request sent to the server (like header corruption I believe.

And further in regard to HTTP error codes, I think I would actually prefer to customize these myself, but perhaps we could return a detailed error object, like this:
{    code: 403,    message: "403 Forbidden – Your request to view the public version of the spreadsheet was rejected by Google's servers. Please ensure that you have made your spreadsheet public." }
Then the user would just deal with the first err parameter just like we both had in mind:
mySheet.fetch(err, res) {   if (err) handleError(err)   // do stuff with result here if no error) }


Document best practices for ensure_index

Right now I'm putting "ensure_index" statements right in my models, but this seems likely to cause problems (or at least a lot of no-ops).  How are people using ensure_index?  Do they call it from a rake task post-deploy?  Put it in an initializer and hope everyone remembers to set ":background => true" or suffer blocking deploy hell?
It seems like a pretty important topic for it to be utterly absent from the docs.

Indexing should not be tied to your application's boot process. I do them in a rake task and run it separately whenever it is needed.
On Tuesday, November 1, 2011 at 9:06 PM, Kyle VanderBeek wrote:

Right now I'm putting "ensure_index" statements right in my models, but this seems likely to cause problems (or at least a lot of no-ops). How are people using ensure_index? Do they call it from a rake task post-deploy? Put it in an initializer and hope everyone remembers to set ":background => true" or suffer blocking deploy hell?
It seems like a pretty important topic for it to be utterly absent from the docs.
--
Reply to this email directly or view it on GitHub:
https://github.com/jnunemaker/mongomapper/issues/337

Excellent, that's what I thought.  I'll just put in this ticket, in case it gets searched for, that I am now writing a db:mongo:index rake task to do the work.  It looks something like this:
namespace :db do
  namespace :mongo do

    desc "Create mongo_mapper indexes"
    task :index => :environment do
      Pants.ensure_index :color

      Outfit.ensure_index :nickname, :unique => true
      Outfit.ensure_index [[:created_at, Mongo::DESCENDING]], :background => true
    end

    desc "Remove old MongoDB indexes"
    task :deindex => :environment do
      # If you find out an index is un-needed, you should add an appropriate Model.collection.drop_index here.
      # MongoMapper doesn't yet have an inverse of ensure_index, so you have to do it via the index name and Mongo driver.
    end
  end
end

No: I do not own enough clothes to warrant MongoDB-backed tracking.  It's just an example.

@jnunemaker @bkeepers @kylev i've actually been looking at ensure_index lately too. One thing that I came across is that mongo mapper is actually NOT doing ensure_index per se the ensure_index method for a collection provided by the mongo ruby driver. The mongomapper method is using create_index under the hood. As far as mongo and the ruby driver are concerned, ensure_index and create_index are different, so for the MM method to be called ensure_index and actually just use create_index is misleading imho. @jnunemaker is there another reason why MM's ensure_index map's to the ruby driver's create_index ?
I'd be happy to send a pull-request to make sure that MM's ensure_index actually uses the ruby driver's ensure_index method under the hood. I was also thinking of mapping, these ruby driver methods to the MM indexes plugin: drop_index, drop_indexes, create_index, and index_information. I know that one can easily just drop to the ruby driver to call those methods, but it would be nice to have them in the indexes plugin. What do you guys think?

@hamin sounds reasonable. I don't know that I would map the other methods, simply because I think it's really unlikely that they'll be used, but I'm not opposed.
One idea I've been throwing around lately is a way to define syntaxes in a non-ruby syntax. I'd love to have a file like db/indexes.yml (yaml is not a great format for this, I tried) that a built-in rake task can look for and call to load the indexes. I'm thinking non-ruby so the rake task doesn't have to load all the models and everything. But if Ruby makes the most sense, then that's fine to.  But basically, it'd be like db/seeds.rb.
thoughts?

so the reason i though the other methods would be good to have is coz i was thinking of something similiar to what you were saying, something like db/seeds.rb for indexes. I thought that if the other methods were mapped too it would make it convenient to provide rake tasks to reindex and drop_index .  Just feel like we need to be consistent with the driver
@bkeepers @jnunemaker thoughts?

@hamin that sounds good to me.

@bkeepers Do you have a methodology for previewing the textile contents?  I started on additions to the docs, but have no idea if they'll render correctly.  Do you have a little textile web server or a Rakefile to generate them?

@kylev check out http://mongomapper.com/documentation/contributing.html I think that has the answer to your question.

I made the changes we talked about, along with adding a rake task.  I'm assuming it just forwards those named methods to the Ruby driver ?

@bkeepers feel like we should definitely update the docs for indexes to reveal that change

@hamin Sorry, I was working on some other stuff and just did it. Forwardable is like delegation in ActiveSupport.
I'll take your docs request as a volunteering to do it. :)

@bkeepers you bastard :)

@hamin hey man, I don't use the docs, so I don't care about them.

@bkeepers i was just jesting...no i'd be more than happy to contribute to the docs again...i always end up learning something new when i do :)

I could go either way. Feel free to submit a patch to make it work like you describe.

Thanks for the inspiration... I documented my own progression through the forest of Indexing... Pretty sure there is lots more bushwhacking left, but I did arrive at a little clearing.
http://technicaldebt.com/?p=1089


Verify Proofs against Spec

We have a proof that the preimage of the leaf node is the given bytes and that cannot be faked. However, as we allow flexibility in defining how key, value is transformed to the lead preimage, there is space for maliability. Or claiming a different subset of that preimage is actually the key and value.
To compact that we define a ProofSpec which is a list of requirements that all proofs from a given backend will meet. So, an Iavl Proof must match one spec, while a merk-js proof matches another spec.
These specs are also serialize able protobuf objects, not special code paths, to allow them to be registered and stored as configuration. And New chains to be added without adding client side code.
Please add the spec struct and logic to check it

Update: mostly closed by #9
Lacking spec enforcement code for js client

Fully closed via #13


Reserve a number of registers for constant values when compiling brillig programs

As of the latest sync PR https://github.com/noir-lang/noir/pull/5790, the sha256 program consists of 1034 opcodes when compiled to brillig. If I extract all of the CONST opcodes we end up with the list below.
  CONST R8 = 2
  CONST R10 = 2⁶
  CONST R9 = 1
  CONST R10 = 0
  CONST R11 = 2⁶
  CONST R12 = 2
  CONST R14 = 8
  CONST R13 = 1
  CONST R15 =<PHONE_NUMBER>
  CONST R16 =<PHONE_NUMBER>
  CONST R17 =<PHONE_NUMBER>
  CONST R18 =<PHONE_NUMBER>
  CONST R19 =<PHONE_NUMBER>
  CONST R20 =<PHONE_NUMBER>
  CONST R21 = 528734635
  CONST R22 =<PHONE_NUMBER>
  CONST R23 = 1
  CONST R23 = 0
  CONST R24 = 0
  CONST R12 = 0
  CONST R10 = 2⁷
  CONST R3 = 2⁶
  CONST R2052 = 2⁶
  CONST R6 = 1
  CONST R12 = 1
  CONST R13 = 57
  CONST R12 = 2⁶
  CONST R12 = 57
  CONST R10 = 2⁶
  CONST R8 = 2
  CONST R3 = 2⁴
  CONST R6 = 1
  CONST R3 = 0
  CONST R15 = 2⁴
  CONST R6 = 2⁴
  CONST R16 = 8
  CONST R6 = 1
  CONST R16 = 2⁴
  CONST R17 = 8
  CONST R6 = 0
  CONST R12 = 0
  CONST R10 = 2⁶
  CONST R3 = 2
  CONST R7 = 2
  CONST R12 = 2⁵
  CONST R3 = 1
  CONST R12 = 0
  CONST R13 = 2⁵
  CONST R14 = 2
  CONST R16 = 2⁴
  CONST R15 = 1
  CONST R16 = 0
  CONST R17 = 2⁴
  CONST R7 = 2⁴
  CONST R16 = 8
  CONST R3 = 1
  CONST R16 = 2⁴
  CONST R17 = 8
  CONST R3 = 0
  CONST R9 = 8
  CONST R9 = 1
  CONST R9 = 1
  CONST R10 = 0
  CONST R10 = 2⁵
  CONST R4 = 1
  CONST R11 = 2⁵
  CONST R11 = 2⁵
  CONST R9 = 1
  CONST R3 = 7
  CONST R14 = 8
  CONST R13 = 4
  CONST R9 = 4
  CONST R15 = 1
  CONST R7 = 0
  CONST R7 = 4
  CONST R9 = 1
  CONST R16 = 4
  CONST R18 = 0
  CONST R17 = 31
  CONST R19 = 1
  CONST R22 = 2⁵
  CONST R2052 = 2⁵
  CONST R21 = 1
  CONST R20 = 1
  CONST R3 = 1
  CONST R3 = 0
  CONST R14 = 0
  CONST R14 = 4
  CONST R15 = 15
  CONST R18 = 2⁴
  CONST R2052 = 2⁴
  CONST R17 = 1
  CONST R7 = 1
  CONST R15 = 2⁸
  CONST R16 = 1
  CONST R18 = 4
  CONST R20 = 0
  CONST R20 = 2⁶
  CONST R19 = 2⁶
  CONST R9 = 56
  CONST R9 = 2⁶
  CONST R10 = 0
  CONST R9 = 8
  CONST R9 = 8
  CONST R6 = 63
  CONST R15 = 8
  CONST R17 = 1
  CONST R18 = 8
  CONST R19 = 1
  CONST R21 = 8
  CONST R22 = 0
  CONST R24 = 2⁶
  CONST R2052 = 2⁶
  CONST R23 = 1
  CONST R20 = 1
  CONST R9 = 0
  CONST R15 = 2⁶
  CONST R2052 = 2⁶
  CONST R3 = 1
  CONST R8 = 1
  CONST R10 = 1
  CONST R3 = 1
  CONST R3 = 0
  CONST R15 = 0
  CONST R15 = 4
  CONST R16 = 15
  CONST R19 = 2⁴
  CONST R2052 = 2⁴
  CONST R18 = 1
  CONST R6 = 1
  CONST R16 = 2⁸
  CONST R17 = 1
  CONST R19 = 4
  CONST R21 = 0
  CONST R21 = 2⁶
  CONST R20 = 2⁶
  CONST R9 = 63
  CONST R9 = 0
  CONST R15 = 2⁶
  CONST R2052 = 2⁶
  CONST R3 = 1
  CONST R8 = 1
  CONST R10 = 1
  CONST R10 = 0
  CONST R16 = 1
  CONST R15 = 1
  CONST R16 = 1
  CONST R18 = 2⁶
  CONST R2052 = 2⁶
  CONST R16 = 1
  CONST R17 = 1
  CONST R9 = 2⁶
  CONST R12 = 2
  CONST R8 = 2⁴
  CONST R9 = 1
  CONST R8 = 0
  CONST R17 = 2⁴
  CONST R9 = 2⁴
  CONST R18 = 8
  CONST R15 = 1
  CONST R18 = 2⁴
  CONST R19 = 8
  CONST R15 = 0
  CONST R12 = 1
  CONST R8 = 1
  CONST R8 = 0
  CONST R17 = 0
  CONST R17 = 4
  CONST R18 = 15
  CONST R21 = 2⁴
  CONST R2052 = 2⁴
  CONST R20 = 1
  CONST R9 = 1
  CONST R18 = 2⁸
  CONST R19 = 1
  CONST R21 = 4
  CONST R23 = 0
  CONST R23 = 2⁶
  CONST R22 = 2⁶

This is 179 CONST opcodes (~17% of the overall program!), there's clearly a lot of duplication here (although some of these constants may differ by bit size so duplication is likely lower than it appears here).
We should keep track of commonly used constants within a program and reserve a set of registers for which these can be stored across the lifetime of the program. This will prevent us from having to make many identical copies of these constants unnecessarily.

cc @vezenovm @sirasistant


GitHub Action for AnyLint

Problem Statement
It's not as easy as it could be to setup AnyLint at the moment for GitHub Actions. Also, the results don't show up in GitHub changes as comments directly. Could also just be integrated with https://github.com/marketplace/actions/lint-action.
Suggested Solution
There should be a ready GitHub action similar to this action for SwiftLint for quick usage.

With #39 and once AnyLint is added to Homebrew core, there's probably no need for this as installing is as simple as brew install anylint and running just anylint. The dropping of the swift-sh dependency helps a lot.


Fix typo in INDEX_TYPE deprecation note

span_CONFIG_INDEX_TYPE was changed to span_CONFIG_SIZE_TYPE in 0c95c299 but due to a typo, this was not described correctly in the README.md

Thanks @mjacobse


Incorrect handling of object expressions combined with other arguments

Input:
clsx(a, b, { [foo]: bar }, c);

Output:
clsx(a, b, c, bar && foo)

Problem
In the generated call, when bar is true, the expression results in clsx(a, b, c, foo) it should be clsx(a,b,foo,c).
The order of classes th in the class attribute matters: https://codepen.io/dfernandez-asapp/pen/mdJBQOX

The order of classes th in the class attribute matters: codepen.io/dfernandez-asapp/pen/mdJBQOX

I cannot reproduce this. The color is the same for
Test
 and
Test
. Which browser/OS are you using?

@eps1lon thanks for looking into the issue, your clarification helped in my confusion.
I'm going to close this, since is a non-issue.


Error when loading settings menu from Config-UI-X

Describe the bug
Whenever I try to access the settings menu from the config-ui-x plugins page the gear just spends.
Expected behavior
It should load the settings menu for me to configure, right?
Logs
[Homebridge UI] [homebridge-camera-ui] file:///usr/lib/node_modules/homebridge-camera-ui/homebridge-ui/server.js:28
const cameraUI = config?.platforms?.find((plugin) => plugin?.platform === 'CameraUI');
^
SyntaxError: Unexpected token '.'
at Loader.moduleStrategy (internal/modules/esm/translators.js:140:18)
at async link (internal/modules/esm/module_job.js:42:21)
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Node.js Version: v16.13.2
Homebridge Version: 1.4.0 Config-UI-X: v4.42.0
Camera UI Version:  v5.0.14
Operating System: Bullseye
Browser: Chrome

should be fixed in the current beta, can you give it a try pls
v5.0.15-beta.1

v5.0.15 online

works, thanks!


use associated iterator types for InspectEnumerable

Changes the return types of the InspectEnumerable traits' methods to an associated iterator type, removing the forced boxing.
Closes #12231.

bot rebase

bot merge

bot merge

bot merge


Support setting Content-Encoding in the s3Upload step

Please check if the PR fulfills these requirements

[x] The commit message describes your change
[ ] Tests for the changes have been added if possible (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Changes are mentioned in the changelog (for bug fixes / features)

What kind of change does this PR introduce?
Feature: Allow Content-Encoding header can be specified in the s3Upload step.

What is the current behavior? (You can also link to an open issue here)
We can't set the Content-Encoding header with the s3Upload step.

What is the new behavior (if this is a feature change)?
We can set the Content-Encoding header if we want.

Does this PR introduce a breaking change? (What changes might users need to make in their setup due to this PR?)
No.

Other information:
N/A

@hoegertn do you mind taking a look at this pull request?

Looks great. Can you please add the feature to the changelog and the readme documentation?

Looks great. Can you please add the feature to the changelog and the readme documentation?
@hoegertn, I'm not sure about the changelog part. Can you take a look again?
Thanks.

@thaiphv I tried this and it doesn't seem to work. It's not enough just to set the encoding. The stream actually has to be encoded. So if I set the content encoding to gzip, S3 serves corrupt files. Don't we need to add an encoding step?

Yes. That's my use case. I gzip'd the files before calling the s3Upload step. Think of the step as an interface to the AWS API.

I see. Are you uploading files with the gzip extension, or normal files that are gzip'd? I ask because I'm not sure if the transfer manager would get the content type and content size right of the original file. Or does it matter?
Could you share how you gzip'd your files?
For the record, the core S3 plugin supports gzipping the content on the fly. Perhaps that could be considered for this plugin as well.

I think S3 doesn't really care what's the content type of the objects. If you want to make sure S3 keeps and serves the right content type, you can specify it using the contentType argument with the s3Upload step. In my case, I don't change the files' extension but only gzip'd them so basically I just use gzip and mv as below:
$ gzip jquery.js && mv jquery.js.gz jquery.js

I'm aware that the s3-plugin does support gzip'ing the files and setting the content encoding to application/gzip but it's the only encoding that it supports. With the contentEncoding argument, we can specify any encoding and I don't think it's possible to support any encoding that we can specify.


Discovery doesn't work on Android

While implementing this library as a way of transfering data between my desktop and android application (written using Kotlin Multiplatform).
The desktop application finds itself and the android application. The android application on the otherhand is only able to find itself and not the desktop application. NOTE: when using an actual android device instead of emulator, the desktop CANT find it...
I don't know exactly how the discovery process works. From what I can tell it uses Broadcasting, but that doesn't explain as to why the desktop application can find the Android application but it doesn't work the other way around...
I'm using all permissions in the AndroidManifest of this stackoverflow article. I also have tried using a MulticastLock which doesn't seem to affect anything
Extra information that might be helpful:

The ip of the android device is in the subnet: 192.168.1.x (or 10.2.2.x when using emulator), but both don't work
The ip of the desktop is in the subnet: 192.168.0.x
The port I'm using: 34340 (but the issue persists with other ports)

My Discovery Builder:
private val discover = Discovery.Builder(CoroutineScope(Dispatchers.IO))
        .setPort(34340)
        .setPing(1000L)
        .setDiscoveryTimeout(60000L)
        .setDiscoveryTimeoutListener {
            println("Discovery timeout")
            scope.cancel() //cancels another scope that is running (has nothing to do with the package directly)
        }
        .setDiscoverableTimeout(60000L)
        .setDiscoverableTimeoutListener {
            println("Discoverable timeout")
        }
        .build()

I don't know if this is an issue with the package directly, or the documentation or just Android in general...
I should state that the main goal is to sync my applications across devices on the same network

Can you please provide information how you start discovery on both ends.
Additionally I don't recommend using emulators, especially not mixed with real devices.
And FYI you can't broadcast to different subnets because Routers don't usually forward packets to different subnets.

To get broadcast over multiple subnets to work, we would need a Multicasting service.
I've never done that and absolutely no time to look into this, however if you're familiar with it, you can open a corresponding pull request.

fyi, I rewrote this library using ktor, and tried to expand things to ios. project can be found here: https://github.com/fluxxion82/k2k. desktop and android apps seem to work ok for the most part. ios is close to working but having some issues.


all inbox email suddenly disappeared on multiple devices

Expected behaviour
Tell us what should happen
Emails should remain on device until deleted
Actual behaviour
Tell us what happens instead
Emails suddenly disappear
Steps to reproduce

Environment
K-9 Mail version: 5.008
Android version: 5.1
Account type (IMAP, POP3, WebDAV/Exchange): POP 3

Please use the mailing list for support requests.


infinite with xcode 9 GM

Hello,
I tried my project with the new xcode 9 GM today, the BartyCrouch script never stops.
So I tried launching command :
bartycrouch interfaces -p [My Project Path] -v
The script is working for some files and then stops for one.
I tried launching with the source file and found that the problem comes from the file : Commander.swift , the line let outdata = outpipe.fileHandleForReading.readDataToEndOfFile() never stops.
I reproduced the same issue with a second project.
My XCode version is : 9.0 (9A235).

Hello bricecesarin ! I've exactly the same issue with my project with the last Xcode version.

I am also seeing this.
The bartycrouch interfaces command hangs indefinitely, but if I run /usr/bin/ibtool --export-strings-file directly, the strings are still exported, though with a bunch of warnings: 2017-09-13 13:37:43.724 ibtoold[3253:4694192] WARNING: Unhandled destination metrics: (null)
xcode-select points to the GM right now (though I have the old Xcode still installed)
ibtool --version:
<key>bundle-version</key>
<string>13196</string>
<key>short-bundle-version</key>
<string>9.0</string>

The nib it hangs on does have autolayout errors and if I delete the views causing the errors, bartycrouch runs fine. (Right now, I can't figure out a way to resolve the errors, IB is being weird).
I'm trying to create a nib from scratch that exhibits the same problem. I'll share here if I'm successful...

If I had to make a guess, it seems like this new version of ibtool isn't given an end-of-file indicator to standardOutput when there are errors (in this case, warnings).
It looks like commenting out let outdata = outpipe.fileHandleForReading.readDataToEndOfFile()  (so just ignoring the standard output) and the rest of the command runs fine, the string files get made.
Not that this is an actual solution or anything, just experimenting.

when I launch ibtool command from command line :
/usr/bin/ibtool --export-strings-file [myTmpStrings] [MyXib]
the warnings :
WARNING: Unhandled destination metrics: (null)
are appearing for all xib (event those which works).
It seems like the output are not different from the working xibs and the no-working xib.

The only output difference is :
/usr/bin/ibtool --export-strings-file [myTmpStrings] [MyWorkingXib] : less than 250 warnings
and
/usr/bin/ibtool --export-strings-file [myTmpStrings] [MyNoWorkingXib] : more than 250 warnings
Same thing with my 2 projects

I got a fix.
Simply reading stderr before stdout solves it.
Pull request incoming after a few more tests.

Fixed via #71.


Question about the format of panda video dataset

Hi @xiaoqian-shen ,
I followed the link you shared  to downlaod the raw video data. However, I am not able to download the videos you used from panda:

The link just contains .csv with the these attributes (videoID,url,timestamp,caption,matching_score):

Although I tried to download the original panda_2m dataset from the here, I am still not able to reach the required format you used in your training. Your format for the dataset is as follows:

Can you please upload the 27,092 .npy files you used in the training for panda dataset? Or at least please let me know how to reach from the training format from the original videos?
Your help is highly appreciated.
Best Regards,
Abdelrahman.

Hi, we download panda dataset from ShareGPT4Video using this script with panda.csv and save as .npy.
Or you can also find the raw videos they provided in here.

Thanks for your reply, I will close this issue since the problem is solved.


Sometimes backgrounds fail

Sometimes, when offline and the backgrounds fail fetch, the backgrounds are not found in (or served from) cache.
Investigate.
To repeat:

load app normally (online)
exercise all pages
go offline
reload app
exercise all pages
reload app
background fetches now somtimes fail

When they fail there is an uncaught fetch exception.

Ugh. This looks like a pixel math error issue.
Just observed a failure due to offline request height being off by one pixel from the cached request.

Fixed rounding via coverage option for sizeReporter in abacfec8cd1a908f12e28aa2c285de7790d20c9c


Unable to define custom error messages

Report a bug
🔎 Search Terms
custom error
🧩 Context

ArkType version: 10.0.16.alpha
TypeScript version (4.8, 4.9, or 5.0): 4.9
Other context you think may be relevant (Node version, OS, etc.):

🧑💻 Repro
import { type, scope } from "arktype"

const emailValidations = scope({
    hasADomain: type(["string", "=>", (s) => s.includes("@")], {
        mustBe: "a valid email with a domain"
    }),
    domainIsValid: type(["string", "=>", (s) => s.endsWith(".com")], {
        mustBe: "a valid domain"
    }),
    all: "hasADomain&domainIsValid"
}).compile()

export const emailValidator = emailValidations.all

export const { data, problems } = emailValidator(
    "should give a list of defined errors"
)

console.log(problems?.summary ?? data)

console shows
'should give a list of defined errors' must be...
• valid
• valid

But I expect it to show
'should give a list of defined errors' must be...
• a valid email with a domain
• a valid domain

https://stackblitz.com/edit/arktype-bug-2d9kpj?devToolsHeight=33&file=demo.ts

Integrating external concerns like custom error messages with a type system is a really tricky problem, and the solution I came up with for alpha really missed the mark. I'd recommend adding the problems directly like this:
import { type, scope } from 'arktype';

const emailValidations = scope({
  hasADomain: type([
    'string',
    '=>',
    (s, problems) =>
      s.includes('@') || !problems.mustBe('a valid email with a domain'),
  ]),
  domainIsValid: type([
    'string',
    '=>',
    (s, problems) => s.endsWith('.com') || !problems.mustBe('a valid domain'),
  ]),
  all: 'hasADomain&domainIsValid',
}).compile();

export const email = emailValidations.all;

export const { data, problems } = email('should give a list of defined errors');

console.log(problems?.summary ?? data);

(on StackBlitz)
Aptly, I was actually working on metadata intersections on beta when you logged this issue. I'll update the title and use this issue to track that work getting merged and that when it does, your original definition will work as expected ⛵


Metrics?

I'd love to start collecting metrics; is this in development at all?

Hi @spacekitteh, I haven't started it in earnest yet, although it's definitely something I want the library to offer. I'd be happy to provide guidance / code review if it's the sort of thing somebody starts working on though.

Sorry, I didn't see this reply!
How would one go about doing this?


Added custom datatype, changed the datatype name and moved the exampl…

…e yml file to here.

This comes in as a text date. How does it work when the user's browser is set to use different date formats?
Can we convert it to a DADateTime?


Automated summaries + releases via GitHub Actions?

Given the real-time urgency of this, it might be good to have automated summaries + releases via GitHub Actions. I'm not sure what summaries would be most useful for folks using the data, but please feel free to ping me if you want any help with any specific ideas that may come up.
Regarding automated releases, the following GitHub Actions from one of my repos might be a helpful template:
https://github.com/niemasd/curriculum-vitae/blob/master/.github/workflows/compile.yml

Hello,
Thanks for your input! Hearing from users like yourself helps us decide on features and prioritization.
I would like to proceed by separating the feature you would like from the way we provide it.
The what:
Any data sets you would find useful, ask for, and I will raise it with the team.
For our latest data set, and historical data sets, we link to our S3 bucket from our README. We can add more data sets to that bucket and provide open access.
If you are asking us to generate LaTex files specifically, I am not as sure. I would need to talk with my team.
The how:
Whether it's automating data ingestion or making LaTex files, Github is the wrong tool for the job. As an engineer I need to consider many factors (e.g. collecting metrics for Ops). I tried Github Actions, and they work fine for some work, but not this.
In short, I am not an epidemiologist or scientist, I only support those communities, and I am responsible and accountable for maintaining and updating our systems.
Let me know what you think, and thanks again!

Great connecting with you over email.
Going to close this based on our conversation, but feel free to reopen this or open new issues whenever you like!


Django 2.0 and tags__name__in=[""] error

In Django 2.0, filtering using tags__name__in doesen't work.
When try to use this function for example:
published= Post.published.all() and then
published.filter(tags__name__in=['music'])
I have this:
Traceback (most recent call last):
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/core/handlers/exception.py", line 35, in inner
response = get_response(request)
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/core/handlers/base.py", line 128, in _get_response
response = self.process_exception_by_middleware(e, request)
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/core/handlers/base.py", line 126, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/home/prorok/Django/mysite/blog/views.py", line 95, in post_detail
similar_posts = Post.published.filter(tags__in=post_tags_ids).exclude(id=post.id)
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/query.py", line 836, in filter
return self._filter_or_exclude(False, *args, **kwargs)
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/query.py", line 854, in _filter_or_exclude
clone.query.add_q(Q(*args, **kwargs))
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/sql/query.py", line 1252, in add_q
clause, _ = self._add_q(q_object, self.used_aliases)
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/sql/query.py", line 1276, in _add_q
split_subq=split_subq,
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/sql/query.py", line 1152, in build_filter
lookups, parts, reffed_expression = self.solve_lookup_type(arg)
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/sql/query.py", line 1015, in solve_lookup_type
_, field, _, lookup_parts = self.names_to_path(lookup_splitted, self.get_meta())
File "/home/prorok/Django/Django/lib/python3.6/site-packages/django/db/models/sql/query.py", line 1390, in names_to_path
pathinfos = field.get_path_info(filtered_relation)
TypeError: get_path_info() takes 1 positional argument but 2 were given
I used #509.

I was unable to reproduce. Could you provide more details about your minimal example or write a failing test for the taggit test suite?

Sorry for my bad english language.I attach a short description of the problem in .pdf
file. I'am new in Django and Python so now I can't write a good tests. It will change in future.
Django 2.pdf

Request Method:
GET

http://localhost:8000/stores/api/v1/itm/tgs/

2.0

TypeError

get_path_info() takes 1 positional argument but 2 were given

C:\Users\user\Documents\projects\v3\lib\site-packages\django\db\models\sql\query.py in names_to_path, line 1390
C:\Users\user\Documents\projects\v3\Scripts\python.exe 3.6.1
['C:\\Users\\user\\Dropbox\\projects\\global_api',
'C:\\Users\\user\\Documents\\projects\\v3\\Scripts\\python36.zip',
 'C:\\Users\\user\\Documents\\projects\\v3\\DLLs',
 'C:\\Users\\user\\Documents\\projects\\v3\\lib',
  'C:\\Users\\user\\Documents\\projects\\v3\\Scripts',
  'C:\\Python36\\Lib',
'C:\\Python36\\DLLs',
'C:\\Users\\user\\Documents\\projects\\v3',
 'C:\\Users\\user\\Documents\\projects\\v3\\lib\\site-packages']

models.py
class Item(ActiveAbstract, ContentTypeAbstract, UUIdAbstract):
    name = models.CharField(max_length=255)
    descr = models.TextField(null=True, blank=True)
    thumbnail = models.IntegerField(default=0)
    images = GenericRelation(Image)
    tags = TaggableManager(blank=True)
    def as_dict(self):
        return {
            'uuid': self.uuid,
            'name': self.name,
            'descr': self.descr,
            'thumbnail': self.thumbnail,
            'images': get_dicts(self.images),
            'tags': [(obj.name, obj.slug) for obj in self.tags.all()]
        }

api_views.py
def get_tags(request):
  items = Item.objects.filter(tags__name__in=['android','iphone')
  ctx = [obj.as_dict() for obj in items]
  return HttpResponse(json.dumps(ctx),content_type='application/json')

Mon, 18 Dec 2017 01:02:18 +0300
<EMAIL_ADDRESS><EMAIL_ADDRESS>it works fine with<EMAIL_ADDRESS>after update to<EMAIL_ADDRESS>something happen

same error here with django 2.0

Can you confirm you've included the changes from #509? The error suggests to me that is is missing.

oh you're right , i used pip install django-taggit today, but my version doesn't have the changes from #509

Thanks for testing.


Default maintainHistory marker option to false

This is a change I've been meaning to make for a while. I made find-and-replace and spell-check explicitly opt out of marker snapshotting, but in other situations where there are lots of markers (e.g. the linter w/ lots of errors, a big file w/ lots of folds) the marker snapshotting causes noticeable lag.
Before
In a 2000-line file w/ 150 folds, MarkerStore::createSnapshot takes a long time before and after each change. This character insertion took 15 ms.

After
Now that part of the flame graph is gone, because folds aren't snapshotted. Folds shouldn't be snapshotted, because they are destroyed if touched by a change anyway. The same character insertion took 4 ms.

I'm going to build this branch and use it for a while to make sure it doesn't cause problems.


upgrade some dev-dependencies

Summary & motivation
Upgrade flow, jest and prettier.
No code changes necessary.
Testing & documentation
Tests, type checks, and lint still pass.

LGTM


[feat] Support RFC3339 compliant time zone formatting when logging time fields

This PR adds a new time formatting directive for log record timestamps, namely the GNU date extension %:z. This directive will print the time zone difference in fully RFC3339 compliant way, i.e., +/-HH:MM instead or +/-HHMM, which %z prints.
This PR also replaces how Job's completion time is stored and retrieved, also inside the Slurm backend. We use time.time() to retrieve the time in seconds from the Epoch instead of datetime.now(), because datetime does not store time zone information. Also all backends are now required to provide the completion time in seconds from the Epoch, so Slurm backend was modified accordingly.
Fixes #1061.
@brandongc FYI

Codecov Report

Merging #1150 into master will increase coverage by 0.01%.
The diff coverage is 93.44%.

@@            Coverage Diff             @@
##           master    #1150      +/-   ##
==========================================
+ Coverage   91.96%   91.98%   +0.01%
==========================================
  Files          81       81
  Lines       11653    11696      +43
==========================================
+ Hits        10717    10758      +41
- Misses        936      938       +2

Impacted Files
Coverage Δ

reframe/core/schedulers/slurm.py
54.54% <0%> (ø)
:arrow_up:

unittests/test_logging.py
97.51% <100%> (+0.26%)
:arrow_up:

reframe/core/schedulers/__init__.py
95.95% <100%> (ø)
:arrow_up:

reframe/core/logging.py
84.19% <92%> (+0.35%)
:arrow_up:

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 af6f7ea...1e6be58. Read the comment docs.


FileNotFoundError: Couldn't find a module script at opencompass-main/accuracy/accuracy.py. Module 'accuracy' doesn't exist on the Hugging Face Hub either.

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] The bug has not been fixed in the latest version.

Type
I'm evaluating with the officially supported tasks/models/datasets.
Environment
为啥会报这个错呢
FileNotFoundError: Couldn't find a module script at opencompass-mainaccuracy/accuracy.py. Module 'accuracy' doesn't exist on the Hugging Face Hub either.
Reproduces the problem - code/configuration sample
1
Reproduces the problem - command or script
1
Reproduces the problem - error message
1
Other information
No response

在logs/eval/下面，不知道为啥会报这个错，这个文件需要从哪里下载码

这个是metric，huggingface 应该可以自动下载的，参考https://huggingface.co/spaces/evaluate-metric/accuracy  ，可以在命令行试试能不能跑链接给的案例

Feel free to re-open if needed.


Add Lizard functionality to hydropandas

Functions added to extract metadata and timeseries from a Lizard-API

Nice! I've been looking forward to this development!
FYI, you'll want to point the Pull Request to the dev branch. You can modify that by pressing the edit button to the right of the PR title and selecting base: dev.

Hi Anouk, I made some changes to the lizard function mostly to make it more uniform with the rest of Hydropandas and some to speed up the code. Some things to note:

I changed the format of the extent from [xmin, ymin, xmax, ymax] to [xmin, xmax, ymin, ymax] in order to match the existing extent format
I merged read_lizard_from_extent and read_lizard_from_list into one function read_lizard
I've added some tests. I did not add tests yet to combine the 'diver' and 'handmetingen' because I don't know which tube has both. Do you have the code of a tube that has both? Than we can test this.
I really liked the part where you use the ThreadPoolExecutor to do some parallel processing, I might use this for other modules of hydropandas as well.


./build

What reproduces the bug?

bpftrace --info
 Using cache
---> 1a3247018652
Step 12/12 : ENTRYPOINT ["bash", "/build.sh"]
---> Using cache
---> e5cdbdd29fab
Successfully built e5cdbdd29fab
Successfully tagged bpftrace-builder-focal:latest
/mnt/test/bpftrace
CMake Error at /usr/local/share/cmake-3.20/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Please install the libbpf development package (missing: LIBBPF_LIBRARIES
LIBBPF_INCLUDE_DIRS)
Call Stack (most recent call first):
/usr/local/share/cmake-3.20/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
cmake/FindLibBpf.cmake:31 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:103 (find_package)
-- Configuring incomplete, errors occurred!
See also "/mnt/test/bpftrace/build-release-focal/CMakeFiles/CMakeOutput.log".
See also "/mnt/test/bpftrace/build-release-focal/CMakeFiles/CMakeError.log".
-->
Already installed libbpf package

Can you try with this patch applied?
diff --git a/build.sh b/build.sh
index 4da38426..643c90c2 100755
--- a/build.sh
+++ b/build.sh
@@ -3,5 +3,6 @@ set -e
 export BASE=focal
 export LLVM_VERSION=12
 export RUN_TESTS=1
+export BUILD_LIBBPF=ON
 ./build-docker-image.sh
 ./build-release.sh "$@"

I have the same problem. Unfortunately the patch doesn't solve it.

你可以试试这个补丁吗？
diff --git a/build.sh b/build.sh
index 4da38426..643c90c2 100755
--- a/build.sh
+++ b/build.sh
@@ -3,5 +3,6 @@ set -e
 export BASE=focal
 export LLVM_VERSION=12
 export RUN_TESTS=1
+export BUILD_LIBBPF=ON
 ./build-docker-image.sh
 ./build-release.sh "$@"

Thank you. Maybe it has something to do with my operating system. My operating system is Euler

我也有同样的问题。不幸的是，补丁并没有解决它。

Maybe it has something to do with my operating system. My operating system is Euler

The problem is that you're missing the libbpf package. If Euler is not packaging it, you have to install from source (which is exactly what the above patch does).
@miwojcik could you try installing libbpf manually from https://github.com/libbpf/libbpf?

diff --git a/build-release.sh b/build-release.sh
index 2029c588..cd5c93d2 100755
--- a/build-release.sh
+++ b/build-release.sh
@@ -1,3 +1,3 @@
 #!/bin/bash
 set -eu
-docker run --network host --rm -it -u $(id -u):$(id -g) -v $(pwd):$(pwd) -e STATIC_LINKING=OFF -e STATIC_LIBC=OFF -e ALLOW_UNSAFE_PROBE=OFF -e VENDOR_GTEST=ON -e RUN_TESTS=${RUN_TESTS} bpftrace-builder-${BASE} "$(pwd)/build-release-${BASE}" Release "$@"
+docker run --network host --rm -it -u $(id -u):$(id -g) -v $(pwd):$(pwd) -e STATIC_LINKING=OFF -e STATIC_LIBC=OFF -e ALLOW_UNSAFE_PROBE=OFF -e VENDOR_GTEST=ON -e RUN_TESTS=${RUN_TESTS} -e BUILD_LIBBPF=ON bpftrace-builder-${BASE} "$(pwd)/build-release-${BASE}" Release "$@"

Can you try with this patch applied?

It looks to be a move in good direction, because libbpf build is now started in docker/build.sh script, but it fails to create /src directory:
~/bpftrace/docker ~/bpftrace
Sending build context to Docker daemon  20.48kB
Step 1/12 : FROM ubuntu:focal
 ---> a0ce5a295b63
Step 2/12 : ARG LLVM_VERSION
 ---> Using cache
 ---> 0731057d2519
Step 3/12 : ENV LLVM_VERSION=$LLVM_VERSION
 ---> Using cache
 ---> 9ddca20efe06
Step 4/12 : RUN apt-get update && apt-get install -y curl gnupg &&    llvmRepository="\ndeb http://apt.llvm.org/focal/ llvm-toolchain-focal main\ndeb-src http://apt.llvm.org/focal/ llvm-toolchain-focal main\ndeb http://apt.llvm.org/focal/ llvm-toolchain-focal-${LLVM_VERSION} main\ndeb-src http://apt.llvm.org/focal/ llvm-toolchain-focal-${LLVM_VERSION} main\n" &&    echo $llvmRepository >> /etc/apt/sources.list &&     curl -L https://apt.llvm.org/llvm-snapshot.gpg.key | apt-key add - &&     apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 4052245BD4284CDD
 ---> Using cache
 ---> 4044a97eecf4
Step 5/12 : RUN curl -L --output /tmp/cmake.tar.gz   https://github.com/Kitware/CMake/releases/download/v3.20.0/cmake-3.20.0-linux-x86_64.tar.gz   && tar -xf /tmp/cmake.tar.gz -C /usr/local/ --strip-components=1
 ---> Using cache
 ---> 4e8560612572
Step 6/12 : ARG DEBIAN_FRONTEND=noninteractive
 ---> Using cache
 ---> 6c7350c9dd72
Step 7/12 : RUN apt-get update && apt-get install -y       make       pkg-config       asciidoctor       bison       binutils-dev       flex       g++       git       libelf-dev       zlib1g-dev       libbpfcc-dev       libcereal-dev       libdw-dev       libpcap-dev       clang-${LLVM_VERSION}       libclang-${LLVM_VERSION}-dev       libclang-common-${LLVM_VERSION}-dev       libclang1-${LLVM_VERSION}       llvm-${LLVM_VERSION}       llvm-${LLVM_VERSION}-dev       llvm-${LLVM_VERSION}-runtime       libllvm${LLVM_VERSION}       systemtap-sdt-dev       python3       xxd       libssl-dev
 ---> Using cache
 ---> ed3eca524c1e
Step 8/12 : RUN if [ "$LLVM_VERSION" -ge 13 ] ; then apt-get install -y libmlir-${LLVM_VERSION}-dev ; fi
 ---> Using cache
 ---> 9ffe24847da0
Step 9/12 : RUN ln -s /usr/bin/python3 /usr/bin/python
 ---> Using cache
 ---> faa4f5b98812
Step 10/12 : COPY build.sh /build.sh
 ---> Using cache
 ---> ca238d6252db
Step 11/12 : RUN chmod 755 /build.sh
 ---> Using cache
 ---> 5c337eb7d60e
Step 12/12 : ENTRYPOINT ["bash", "/build.sh"]
 ---> Using cache
 ---> 90b5c333d265
Successfully built 90b5c333d265
Successfully tagged bpftrace-builder-focal:latest
~/bpftrace
mkdir: cannot create directory '/src': Permission denied

Hi, we have changed the way we're using BCC/libbpf. By default, both are vendored (built from source) in their last version. If you want to use system BCC and libbpf, you need to pass USE_SYSTEM_BPF_BCC=1 to the build.sh script (or to the docker run command).
That said, build-release.sh should now work out of box. Could you give it a try?

Classic build.sh now works fine for me @viktormalik. Great job!

Thanks for confirmation @miwojcik!


ARROW-761: [C++/Python] Add GetTensorSize method, Python bindings

This computes the memory footprint of a serialized arrow::Tensor so that an appropriate memory region can be allocated.

cc @pcmoritz

LGTM

rebased


Rename "tw credentials create" to "tw credentials add"

See https://github.com/seqeralabs/tower-cli/issues/112

duplicated https://github.com/seqeralabs/tower-cli/issues/107


match may not be exhaustive

Hi,
I am not sure whether it is a bug, but for sure it's quite a surprising behavior.
There is an option in the configuration called Configuration.default.withDefaults which allows for the derivation of non-case classes based on the fields they specify.
When combined with the following scalac options:-Xlint:strict-unsealed-patmat and -Wconf:cat=other-match-analysis:error it causes compilation to fail with "match may not be exhaustive" error.
This alone isn't yet that bad, but the error will propagate downstream through the chain of defined derivations and macros making it quite hard to debug for the end-users. I myself got it when I was trying to derive some tapir's type-classes that rely on circe codecs.
Here is a failed build on CI which illustrates that problem: https://github.com/softwaremill/livestub/runs/2586343239
Update: When trying to prepare a minimal example to reproduce I discovered that such a class needs also to specify an unapply method.
The minimal example to reproduce:
import io.circe.generic.extras.Configuration
import io.circe.generic.semiauto._

trait JsonSupport {
  implicit val config: Configuration = Configuration.default.withDefaults

  implicit val headerEncoder = deriveEncoder[Header]
}

class Header(val name: String, val value: String) {}

object Header {
  def unapply(h: Header): Option[(String, String)] = Some((h.name, h.value))

}

Thanks for the report! circe-generic-extras is maintained in a separate repo, though, so it'd probably be best to open this issue there.

Ok, I will move it there, thanks!


Brijesh STO FAQ

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[x] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.CX Engineering seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://671ad30a92b34b7ef0c1e1ad--harness-developer.netlify.app

This pull request has been automatically closed due to 30 days of inactivity. If you believe this was done in error, please feel free to reopen the PR or reach out to the BT team for further assistance. Thank you for your contributions!


Copy existing or generate new Fusion profile on prelaunch

Brief description
Fusion preferences will be copied to the predefined ~/.openpype/hosts/fusion/prefs folder (or any other folder set in system settings) on launch.
Description
The idea is to create a copy of existing Fusion profile, adding an OpenPype menu to the Fusion instance.
By default the copy setting is turned off, so no file copying is performed. Instead the clean Fusion profile is created by Fusion in the predefined folder. The default locaion is set to ~/.openpype/hosts/fusion/prefs, to better comply with the other os platforms. After creating the default profile, some modifications are applied:

forced Python3
forced English interface
setup Openpype specific path maps.

If the copy_prefs checkbox is toggled, a copy of existing Fusion profile folder will be placed in the mentioned location. Then they are altered the same way as described above. The operation is run only once, on the first launch, unless the force_sync [Resync profile on each launch] is toggled.
English interface is forced because the FUSION16_PROFILE_DIR environment variable is not read otherwise (seems to be a Fusion bug).
Note
I accidentally deleted my previous PR, that has already had some conversation and reviews, because I'm a dummy. Sorry!
You can find it here: https://github.com/ynput/OpenPype/pull/4456

I guess this new PR is intended to replace this one? https://github.com/ynput/OpenPype/pull/4456

I guess this new PR is intended to replace this one? #4456

exactly, the previous one deleted by mistake

exactly, the previous one deleted by mistake

Tried to match the reviewers, labels and milestone from the original PR just now. But can't seem to add back in @EmberLightVFX as reviewer. Other than that it seemed ok to set them for me.

exactly, the previous one deleted by mistake

Tried to match the reviewers, labels and milestone from the original PR just now. But can't seem to add back in @EmberLightVFX as reviewer. Other than that it seemed ok to set them for me.

I guess only @movalex can add @EmberLightVFX as reviewer.

exactly, the previous one deleted by mistake

Tried to match the reviewers, labels and milestone from the original PR just now. But can't seem to add back in @EmberLightVFX as reviewer. Other than that it seemed ok to set them for me.

I guess only @movalex can add @EmberLightVFX as reviewer.

I don't see such an option anywhere, should I look closer or do I need some special access rights for that?

I think you can only add as reviewer registered contributors of the project and those who have replied to the PR. So I think @EmberLightVFX can be added as a reviewer only when he's commented on this PR. I want to emphasize that I think that is the case.

Will take a look at this when I get some minutes over!

I think you can only add as reviewer registered contributors of the project and those who have replied to the PR. So I think @EmberLightVFX can be added as a reviewer only when he's commented on this PR. I want to emphasize that I think that is the case.

It is not the case. Only registered external contributors can be added as reviewers. And after the past few weeks i'd say tha @EmberLightVFX certainly earned that status. I'll sort it out.

Since we're now copying the prefs anyway, should the master prefs maybe be 'generated' along with the copied prefs and maybe get generated e.g. per project from e.g. OpenPype Settings instead. Looking at what is being altered in this PR I have a feeling it might be worth being able to just customize the master prefs directly from OpenPype settings?
We would basically deploy from settings into the copied preferences folder.
Thoughts?

Yes please! That would be an awesome feature!!

exactly, the previous one deleted by mistake

Tried to match the reviewers, labels and milestone from the original PR just now. But can't seem to add back in @EmberLightVFX as reviewer. Other than that it seemed ok to set them for me.

I guess only @movalex can add @EmberLightVFX as reviewer.

I don't see such an option anywhere, should I look closer or do I need some special access rights for that?

Since we're now copying the prefs anyway, should the master prefs maybe be 'generated' along with the copied prefs and maybe get generated e.g. per project from e.g. OpenPype Settings instead. Looking at what is being altered in this PR I have a feeling it might be worth being able to just customize the master prefs directly from OpenPype settings?
We would basically deploy from settings into the copied preferences folder.
Thoughts?

Yes please! That would be an awesome feature!!

I'm not sure if that's already done by someone, but I recently did some rework on the lua-to-python project called slpp, and now it converts the master prefs file to Python and vice versa. There's a test file to try. I just wonder if we can incorporate this code here as is, or it should be rewritten. It would be awesome to be able to specify the preferences on prelaunch hook project-wise.

I'm not sure if that's already done by someone, but I recently did some rework (deleted a couple of symbols actually) on the lua-to-python project called slpp. Now it converts the master prefs file to Python and vice versa. There's a test file to try. I just wonder if we can incorporate this code here as is, or it should be rewritten. It would be awesome to be able to specify the preferences on prelaunch hook project-wise.

I was thinking we don't need slpp at all for this. We can just have a plain text field in the settings where you could put whatever content you want in the master prefs file. No need to encode/decode we can just write whatever is there into the master prefs file one to one. It'd mean that you could just copy whatever you in the .prefs file now directly into settings. No need for the Python lib dependency for that.
By the way, maybe a bit offtopic I had tried slpp in the past, I think five years ago and it basically failed at everything I threw at it. I had hoped to just throw e.g. Fusion .comp files at it directly but no luck at the time. Is that working better nowadays?

By the way, maybe a bit offtopic I had tried slpp in the past, I think five years ago and it basically failed at everything I threw at it. I had hoped to just throw e.g. Fusion .comp files at it directly but no luck at the time. Is that working better nowadays?

I didn't try it with the comp file, but with the prefs file it did pretty well. I literally changed a single line for that. I wish I did a proper commit...

No need for the Python lib dependency for that.

Well, pasting the whole master.prefs file in the text field would be much easier, however a bit more error prone. Miss a single curly brace, and the changes would not be applied with no notice.

Well, pasting the whole master.prefs file in the text field would be much easier, however a bit more error prone. Miss a single curly brace, and the changes would not be applied with no notice.

I'd say the idea is that a studio or admin eould have "their" master prefs already, or use the one from OpenPype or know how to manage them (or would need to look up how it works in Fusion anyway). Adding a layer on top would mean more logic to maintain, more logic to document and potentially even teach. I for example wouldn't want to even spend time rewriting my master prefs, and if I do I just secretly copy what I need from customizing my Fusion preferences through the UI and then taking those values into master prefs. Otherwise the admin would still first need to figure out the name of the key, the nesting, etc and then write that in Python logic and then test whether that actually encodes into something that works.
I think the entry point to failure is the same size if not even bigger due to the extra dependencies.

@BigRoy
This comment in pre_fusion_setup.py is not clear to me:

Fusion 18+ requires FUSION_PYTHON3_HOME to also be on PATH

It used to be more descriptive before:
Fusion 18+ does not look in FUSION16_PYTHON36_HOME anymore
but instead uses FUSION_PYTHON3_HOME and requires the Python to
be available on PATH to work. So let's enforce that for now.

So does Fusion18+ require BOTH variables to be set, or FUSION_PYTHON3_HOME  in the Path would be enough?

So does Fusion18+ require BOTH variables to be set, or FUSION_PYTHON3_HOME  in the Path would be enough?

Yes those two would be enough. This is what I meant. I couldn't get FUSION_PYTHON3_HOME to work of the path wasn't also added to PATH.

According to our previous Discord conversation on how to manage the Fusion settings, so correct Fusion profile number would he used. I would simply restrict using other than default version convention in the applications/fusion/variants key. Of course, users still may change those default parameters, but I cannot imagine a single reason why they would want to. The version number is shown next to the app name in Applications attribute, and chaging the key in System settings, ditching the version number completely, would just would not make sense. Also this would require to change the corresponding project settings in project_anatomy/attributes/applications.  In a highly improbable situation, that the application key would not consist a valid Fusion version in any part of it, user will see this warning. What do you think?


localized strings cannot be used before the language is loaded

Caching happens too early for exported variables. This impacts localization of "Advanced" and "Extensions" in the editor.

Was just about to mention that moving it to the local context would break the monaco toolbox, but looks like you figured that out.

Need to check if v0 has this problem.


Rename entry_schema and key_schema to entry_type and key_type

The word "schema" is confusing here, as we are referring to a data type.
Changing it to _type also aligns with my general preference that keynames include the name of entity type of what they refer to.

I don't believe "type" is the correct type of entity here. Let's assume we have a list of lists. In that case the "entry_schema" is "list". But since "entry_schema" is required for lists, we also need to specify the entry schema for the list type specified in the original entity schema. This means that we may need full parameter definition syntax here, in which case we should consider renaming entry_schema to entry_definition, not entry_type.


Markdown formatting - Fixed table widths so they will properly render

Markdown formatting - Fixed table widths so they will properly render

@MattVevang : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks @MattVevang.


Removes verbose details from error logging in Problems

As described in #2357, the logging for the Problems DB (particularly the Drutiny scan) is far too verbose. Essentially we were sending along the entire request into the logs (which can be json objects with hundreds of fields or nested objects).
This PR simply removes the metadata that delivers the entire webhook through to the logs.
Checklist

[*] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for changelog and subsystem label(s) applied

Closing issues
closes #2357

Problems logging is being reworked


Add trigger

added a daemon around the runner
added a schedule to run each night at 00:00
added a cli to do an ad hoc run
Documentation

I will create the circleCI config and a top level package.json to ease install an testing


Enterprise Membership & Improved Consumed License Reports

Summary
A new enterprise membership CSV report enables enterprise administrators to better analyse their membership and take action based on that information. Alongside this, we have also improved the enterprise consumed licenses report to provide more information to administrators.
Intended Outcome
With these enhanced reports, customers should be able to more easily answer license consumption and enterprise access questions.
How will it work?
The Consumed Licenses report is available both in GHEC UI on the enterprise account's settings > enterprise licensing page as a download button for User licenses as well as via API.

The enterprise membership report, it is downloadable via the enterprise account's People page as a download button.

🚢 This has shipped: https://github.blog/changelog/2022-11-29-new-and-improved-enterprise-reports-now-generally-available


Uncaught (in promise) Error: incorrect header check

I am a noob developer simply trying to use youtubei to get search results. After struggling for days fighting CORS issues, I was able to disable chrome security and finally get some kind of reply other than a cors error. I am unsure if the error below is still due to a CORS as in the Network tab of Chrome Inspect I am able to see the search results but not print them in the console.
Furthermore, I am using Browserify to bundle the code.
Expected behavior
Produce an array of search results. The code works fine in the npm runkit. Was hoping to be pushed in the right direction as searching google has not returned much useful information as to Uncaught (in promise) Error: incorrect header check.
Screenshots

Duplicate of https://github.com/SuspiciousLookingOwl/youtubei/issues/10#issuecomment-812250052
This code is intended to be used on Node environment (server) only


Do you support Multichain ?

Hello ..
Multichain is a form of bitcoin and is a platform to build the private blockchain Apps.
In Multichain, we can create assets, and we need a wallet to integrate into the project, so we can manage to transfer the assets between users.
Does the NBitcoin wallet support Multichain?
Thanks

it does not.


Test workflow is failing with Jest snapshot errors

Test workflow is failing with Jest snapshot errors saying they are not up-to-date - but the updated snapshots have been checked in and the tests pass locally after a clean build.
Github CI run
$ jest --coverage --ci
...
Snapshot Summary
 › 11 snapshots failed from 4 test suites. Inspect your code changes or run `yarn test -u` to update them.

Test Suites: 4 failed, 3 passed, 7 total
Tests:       11 failed, 27 passed, 38 total
Snapshots:   11 failed, 7 passed, 18 total
Time:        5.62 s

Local run of the same branch with no other changes
$ jest --coverage --ci
...
Test Suites: 7 passed, 7 total
Tests:       38 passed, 38 total
Snapshots:   18 passed, 18 total
Time:        5.852 s

checked out the branch to a diff clean location in my machine and tried out the CI commands - no issues 😕
tried running the build locally in ubuntu container - runs fine without any issues
switching to mac-os from ubuntu for the workflow doesn't fix the issue :(
Resolved this issue by switching to CircleCi. Tests all pass now.

Reporting here because I like Github actions and would like to continue using it.

Not sure it's an issue with setup-node (since it just installs node) but I'll keep it open to investigate.  Might also be a VM / hosted pool machine issue?  I did see this before on one of our repos ...

I'm having a similar issue with typescript, same node version, npm, and typescript on my local machine than the ci machine, when i run the ci, i'm seeing errors that on my local machine doesn't appear.

+1

+1

Found a workaround. My jest was failing because I was using a arrow funcion on my vue template.
The arrow function was translated wrongly by babel istanbul plugin. Replacing it with a component method worked :sweat_smile:
Refs:

https://github.com/istanbuljs/babel-plugin-istanbul/issues/63

Out local node version is version 15.2. All our tests passes.
Github tests version 10.x, 12.x and 14.x. None of Github tests passes.
We then changed Github to only test version 15.x. Now all tests passes.

Same problem here. Works locally but somehow fails when running the jobs. It looks like GitHub adds some extra spaces or lines somehow?

Same problem here. Works locally but somehow fails when running the jobs. It looks like GitHub adds some extra spaces or lines somehow?

I got it to work by matching the runs-on environment and version to my local, as well as matching the node-version to my local.  So for me, this worked:
`name: Node Continuous Integration
on:
push:
branches: [master]
jobs:
run_tests:
runs-on: macos-latest
steps:
- uses: actions/checkout@v2
- uses<EMAIL_ADDRESS>with:
node-version: 14.x
- run: npm ci
- run: npm test
- run: npm run build`

@misterrodger You may be aware of this, but running Github Actions with a macOS runner costs 10x that of using the Linux runner. It's awesome you found a fix for your issue, but worth calling out the cost difference - you'll eat up your Github minutes much, much faster.
https://docs.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions

FWIW I was also debugging this for my CI build. My npm test just ran this:
{
  "scripts": {
    "test": "tsc && jest -u && git diff && git status && git reset --hard && jest"
  }
}

What was interesting was the git status:
2021-09-15T04:46:36.8432929Z Changes not staged for commit:
2021-09-15T04:46:36.8433672Z   (use "git add/rm <file>..." to update what will be committed)
2021-09-15T04:46:36.8434485Z   (use "git restore <file>..." to discard changes in working directory)
2021-09-15T04:46:36.8435533Z 	deleted:    src/components/__snapshots__/header.spec.tsx.snap
2021-09-15T04:46:36.8436063Z
2021-09-15T04:46:36.8436527Z Untracked files:
2021-09-15T04:46:36.8437176Z   (use "git add <file>..." to include in what will be committed)
2021-09-15T04:46:36.8437965Z 	src/components/__snapshots__/Header.spec.tsx.snap
2021-09-15T04:46:36.8438450Z

So I'm guessing this issue is a bug in jest related to casing -- as you can see, the version of Jest I created the snapshot with downcast the file name, even though the tested file was capitalized.
It's very similar to https://github.com/facebook/jest/issues/9865 and https://github.com/facebook/jest/issues/8900 but I think it's its own issue.
The good news (for me at least), was that fixing the casing discrepancy fixed the issue, and the latest version of Jest generated files with the correct casing (could have been updating, could have been me switching from Intel to ARM for dev -- who knows). So if you come to this issue via search, I'd check out these possible solutions.

In case someone has renamed the filenames that may not been updated Linux takes things case sensitive by mac os doesn't
Either remove snapshots and run all test cases or manually change snapshot file name

I am having a similar issue (failed test run link). If I should open a new issue instead of adding on here, please let me know.
It appears the issue might be caused by the colored formatting on the error messages?
I posted a StackOverflow question, if I get an answer that helps fix my problem I'll report back.

Hello guys,
Due to the fact that everything seems to be working now, I will close this issue. If you still experience any issues, feel free to leave a comment here or to create a new issue.

I try to compare images using toMatchSnapshot(). It is working fine locally but on CI (Github action) it fails
Below are errors encountered while running the test script:
Error: A snapshot doesn't exist at /home/runner/work/_Swag_Lab_Dummy_Module/_Swag_Lab_Dummy_Module/tests/Test_Scrip.spec.js-snapshots/loginImage-Pixel5-linux.png.
at ../Support/PageMethod/loginPageMethod.js:44
For reference screenshot attached

I also have a snapshot test failure in our github workflow that I don't experience locally.  I'm running the same versions of Node locally and in the workflow env.  It doesn't appear to be a case sensitivity issue either.  I want to diff the saved snapshot file with the snapshot produced during the test.  Is that possible?  The snap output in the github interface is "incomplete".  It prints about 100 of what should be about 500 total lines so i can't really diff them that way.
Thoughts?


Do you train in chunks? If yes, are there specific steps?

I don't know if I understand the 'chunks' in your description correctly. We used one model to represent the scene instead of using submodules, so we did not train in chunks.
And there is another 'chunks' in this repo, which saves the data into several chunks when setting '--dataset_type=filesystem', because the data is too large to load in memory.


Add syntax details for attributes in CDEvents

Expand the definition of mandatory attributes by adding syntax
details and examples.
Introduce the "version" as a mandatory attribute.
Add the subject as an optional attribute as discussed in the WG.
Signed-off-by: Andrea Frittoli<EMAIL_ADDRESS>

Thank you @m-linner-ericsson for the thorough review!
I think I either addressed or replied to all your comments.
I expanded on the source based on the discussion in the working group and the feedback I got from the CloudEvents folks on slack. I think for now we don't need source to be an object- I'd rather have the source being as simple as possible, at least until we hit a use case where we need more.

@afrittoli To ease the job of the reviewer it would be nice to have the complete history so you can see what has changed. A humble request would be that, if you want to force push could you force push the branch with all the commits?

@afrittoli To ease the job of the reviewer it would be nice to have the complete history so you can see what has changed. A humble request would be that, if you want to force push could you force push the branch with all the commits?

Yes, sure - I can do that.
My usual workflow is to force-push because that keeps the git history clean. Unfortunately GitHub, unlike Gerrit, doesn't have a concept of patchsets, only commits, which means that to keep a readable git history one then has to squash the commits into one before merging the PR. Assuming that in most cases we will only have one commit per PR that works relatively well.


PDF: Support "Acknowledgements" section

Follow-on from https://github.com/metanorma/metanorma-ieee/issues/107

So the Acknowledgements preface section follows the Keywords preface section.

(On the same page)

Done (example text rendering):


Theme doesn't work on new WhatsApp update

Screenshot: https://i.imgur.com/4hNVLgl.png

Same here

Can confirm

Yup, getting the same issue as above right now. Did they change some parent class? Cause it looks similar to what it was before.

They changed all the class names with yesterdays update.

Awesome. Literally 95% of things is broken and it'll take a while to fix. I'm so not looking forward to it. :disappointed:

@vednoc Please don't give up, I was about to publish my new addon version that have a whole section to customize your dark mode:

Just this morning i realized from testers that it's broken now.
I will try to help, but please don't give up.

(...) I will try to help, but please don't give up.

I won't give up, it's just disappointing to see everything gone in one update. It was an expected doomsday scenario, so to speak. Everything will be back to normal but things won't be as polished.
Also debating whether to refactor to stylus-lang preprocessor like in my other themes which unfortunately makes it more difficult for you guys that use the theme outside of Stylus but that makes it easier for (anyone) to contribute or for me to add/change/remove things in the future.

This is why i don't like auto-generated class names and css modules. At any point in time all the classes can randomly change their name and mess with userstyles.

I don't like them either! It was a very sad day back when WA decided to use them. I had to rewrite everything from scratch -- that was the moment when I decided to put this theme into a separate repository.

For next time, why don't you just save every component with a variable name that refers to it, and then simply when WhatsApp update the class names later it will just be simple "Find & Replace" commands to replace the old class names wit the new ones?
I just did this with the extension i'm coding as in most of its features it also depends on the class names, so I converted the dynamic class names to static variables such as senderChatBubble = '.whatEver-Class ... sideBar = '#side ...
Can we do this with your CSS?

This is how WhatsApp saving them anyway, as the extension have access to the page scripts, I guess I can always predict the new class names, I will investigate further and reply back.
Thanks.

The markup changes or they rearrange things around. It doesn't seem it'd be that simple to find a good solution. One thing that would help a lot would be to use IDs more since they don't seem to change, as well as attributes in the markup, but they're not available on each and every element (i.e. the modal: <div class="..." data-animate-status-v3-modal-background="true">).
One thing that is true is that the code needs to be structured in a better way -- something that'd be so much easier with stylus-lang.

I will search for someone who have an old copy of the WA web version to provide a temporary fix until you find out some solution. I hope that stylus-lang can export a compiled css file at the end, so that I can use it in the addon, does it?

I'll actually patch this up tonight and start refactoring when I have more time. Good thing they didn't change markup (as far as I can tell) otherwise it'd be a very sad day. :grimacing:

I hope that stylus-lang can export a compiled css file at the end, so that I can use it in the addon, does it?

Yes, though that might take a little bit to set up. You could always steal the compiled CSS from the browser so it shouldn't be that big of a deal. :smile:

Hotfix is out. Tomorrow I'll be able to spend more time fixing things. Thank you all for waiting patiently. :blush:

Thank you so much! looking forward to see the new version covering all the issues.

The v1.4.1 is out; gotta re-do starred messages because the colors are a bit off. Feel free to spam me things that are broken so I can prioritize them over polishing minor things. :sweat_smile:

@vednoc Kinda off-topic, but thank you very much for this dark theme and the fast fix. Spectacular work!

I was going through the css and finding all the selectors that have been changed. If you go by color it's a much quicker experience. Thanks @vednoc for addressing this so quickly and putting out the hotfix. I know it can be tedious and easy to give up on.

Mostly done, v1.4.3 is out.
I think the 'unknown sender' for people that aren't your contacts is still broken and I have no way to check it out. If someone could do it and give me a snippet of that part, I'd be very thankful!
Also, take a moment to vote for what I should do in #32. I'm looking for some feedback. :smiley:


Installation instructions?

This looks really cool, but how would someone go about installing it? I've been looking for a tiling WM for OSX and I'm currently using your Hammerspoon init.lua script, but something like this project seems to be the better solution.
It'd be cool if we could talk on IRC or something like that to get some more documentation around this.
I'm also looking for a bar solution, like https://github.com/stayradiated/bar but I'm having some issues with that as well.
Anyways, if you could put some installation instructions in the readme, I think it'd be awesome.

uh, it doesn't create an app bundle.
All you have to do is to execute the build script included to compile it, then launch it from a terminal.
The build script is just running the g++ command.
so cd into the source directory, ./build.sh to compile and launch with ./kwm

Thanks man! Love the image too. What are you using for the bar at the top? Can it be customized?

The bar is created using "nerdTool", it hasnt been maintained for quite a while i believe, but the latest version works just fine on el capitan

nerdTool huh? Bar looks good! I've been trying to build a bar with Hammerspoon and it's getting tricky.
Mind sharing your nerdTool bar config?

It's kinda tricky as each entry is a separate script, i could upload them as a .zip i guess.
What i did tho, is just create a picture in photoshop that i added to nerdTool (add image).
Now you just add whatever script you want, and set the X,Y coordinates to be somewhere on the bar.

cmd+alt+ctrl k creates the segfault ... wish i could try this out, that spaces.plist issue is pretty annoying though.

uh if we can talk on IRC or some other IM we can probably figure out why it's happening, if you'd like

yeah, perfect, I'm yuppie on freenode and rizon :sushi:

Dude! Excellent work on this! Just cloned it and started running! Working great so far. Jump on IRC again sometime.

Cheers, still a long way to go for a release tho.
Please do open issues if you discover something that appears to misbehave as it's quite hard finding them by myself.


Problem unlinking when checking out individual files

Local Repro
C:\gvfs_repos>gvfs clone https://gvfs.visualstudio.com/ci/_git/ForTests ft
Clone parameters:
Repo URL:     https://gvfs.visualstudio.com/ci/_git/ForTests
Branch:       Default
Cache Server: Default
Local Cache: C:.gvfsCache
Destination:  C:\gvfs_repos\ft
Authenticating...Succeeded
Querying remote for config...Succeeded
Using cache server: None (https://gvfs.visualstudio.com/ci/_git/ForTests)
Cloning...Succeeded
Fetching commits and trees from origin (no cache server)...Succeeded
Validating repo...Succeeded
Mounting...Succeeded
Registering for automount...Succeeded
C:\gvfs_repos>cd ft\src
C:\gvfs_repos\ft\src>git status
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
C:\gvfs_repos\ft\src>git checkout origin/FunctionalTests/20180214 -- Readme.md
error: unable to unlink old 'Readme.md': No such file or directory
C:\gvfs_repos\ft\src>type Readme.md >..\test.txt
C:\gvfs_repos\ft\src>git checkout origin/FunctionalTests/20180214 -- Readme.md
error: pathspec 'Readme.md' did not match any file(s) known to git
C:\gvfs_repos\ft\src>git checkout --ignore-skip-worktree-bits origin/FunctionalTests/20180214 -- Readme.md

@kewillford was able to workaround this by reading the file to bring it on disk and then using --ignore-skip-worktree-bits on the checkout as shown in the repro above. @jrbriggs as FYI

This command seems to still be doing the correct thing even though the error: message was shown since the file gets updated in the index and status is the same as when the command is ran on a non-VFS for Git repo, so this issue is really that an error is being shown to the user with the git command when it doesn't get shown in a non-VFS for Git repo.
VFS for Git
C:\gvfs_repos\ft\src>git checkout origin/FunctionalTests/20180214 -- Readme.md
error: unable to unlink old 'Readme.md': No such file or directory

C:\gvfs_repos\ft\src>git status
On branch master
Your branch is up to date with 'origin/master'.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        modified:   Readme.md

Not VFS
C:\git_tests>git clone https://gvfs.visualstudio.com/ci/_git/ForTests ft
Cloning into 'ft'...
remote: Azure Repos
remote: Found 3264 objects to send. (30 ms)
Receiving objects: 100% (3264/3264), 1.43 MiB | 5.86 MiB/s, done.
Resolving deltas: 100% (1601/1601), done.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        modified:   Readme.md


add graph network view to bacalhau dashboard

ETA: 2023Q1
just need to add the js in the viz directory to the js build that Kai made

I think this is done now, the dashboard includes a visual. Reopen if I'm wrong.


feat!: implement support for OCIO NamedTransforms

ColorProcCacheKey: Update definition, signature, and usage to support caching NamedTransform processor handles.
(Note: ABI-breaking)

ColorConfig: add NamedTransform convenience functions: getNumNamedTransforms, getNamedTransformNameByIndex, getNamedTransformNames, getNamedTransformAliases

ColorConfig: add createNamedTransform function returning new ColorProcessorHandle

Add ImageBufAlgo::ocionamedtransform functions

oiiotool: add --ocionamedtransform operator

python: add NamedTransform convenience function bindings

python: add ImageBufAlgo.ocionamedtransform(...) bindings

Update oiiotool and python documentation with examples

Description
OCIO-2 config authors may define a set of stand-alone "source-agnostic" NamedTransforms. Unlike the colorconvert, ociodisplay, and ociolook IBAs, which explicitly convert from a color space to something else, the ocionamedtransform IBA behaves more like the ociofiletransform IBA, where the transform itself can be applied either in the forwards or inverse direction, and does not take into consideration the input encoding or image state.
Quoting from the OCIO NamedTransform documentation:

Sometimes it is helpful to include one or more transforms in a config that are essentially stand-alone transforms that do not have a fixed relationship to a reference space or a process space. An example would be a “utility curve” transform where the intent is to simply apply a LUT1D without any conversion to a reference space. In these cases, a named_transforms section may be added to the config with one or more named transforms. [...] This feature may be used to emulate older methods of color management that ignored the RGB primaries and simply applied one-dimensional transformations.

Notably, the built-in OCIO-2 Studio config (ocio://studio-config-latest) contains NamedTransforms "sRGB - Curve" and "Rec709 - Curve", which we could implement as drop-in replacements for the existing linear_to_sRGB, sRGB_to_linear, linear_to_Rec709, and Rec709_to_linear functions in color.h (unless those functions are deprecated...).
There are several other applications for NamedTransforms as well. They can be extremely useful as workflow-oriented transforms implemented at various points in facility pipelines (e.g., for applying shot-specific conversions, grades, gamut-compression, etc.); they can be used to provide diagnostic transforms for visualizing "exposure zones", clipped areas, NaNs, etc; for visually "tagging" problematic clips; for applying parts of ACES Metadata Files parsed by OCIO's forthcoming AMF parser; for conversion to non-RGB color models... all sorts of things.
Tests
Tests are forthcoming. I've tested everything locally, but have not yet implemented proper tests in the testsuite.
Checklist:

[x] I have read the contribution guidelines.
[x] I have updated the documentation, if applicable.
[ ] I have ensured that the change is tested somewhere in the testsuite
(adding new test cases if necessary).
[x] If I added or modified a C++ API call, I have also amended the
corresponding Python bindings (and if altering ImageBufAlgo functions, also
exposed the new functionality as oiiotool options).
[x] My code follows the prevailing code style of this project. If I haven't
already run clang-format before submitting, I definitely will look at the CI
test that runs clang-format and fix anything that it highlights as being
nonconforming.

This is looking great, very complete, thanks!
You said in the PR comments that this is ABI-breaking, but actually I think it is not, since it only adds new non-virtual functions. I don't think it breaks backwards-compatibility with linkage. (And it seems to pass our CI test that does specifically check for ABI breaks.)
Shall I wait for you to add some kind of test? Or would you rather do that in a follow-up PR? I don't want us to forget about that, but given how thorough you were on this, I don't have any doubt that you'll follow up with the tests, and obviously these additions are new and can't break anything that previously worked.

You said in the PR comments that this is ABI-breaking, but actually I think it is not, since it only adds new non-virtual functions. I don't think it breaks backwards-compatibility with linkage. (And it seems to pass our CI test that does specifically check for ABI breaks.)

Ah, that makes sense... I was concerned that changing the signature for the ColorProcCacheKey constructor would break stuff (I'm not super C++ savvy, so I'm very out of my element here). I figured I'd err on the side of caution.

Shall I wait for you to add some kind of test? Or would you rather do that in a follow-up PR?

Whichever you'd prefer. I'm probably going to prioritize getting python wheels stuff together for next week, so it might be a short while before I get the tests in. (I figured, if this were ABI-breaking, it might make sense to get yr eyes on it sooner rather than later). I don't think it'll take me very much time.
On the other hand, I also noticed there were other OCIO features that needed tests; and there's an itty-bitty other PR I'd like to make adding a couple of ociofiletransform enhancements (context key/value support; "cccid" value support); and since testing context-variable stuff for ociofiletransforms requires a bit more setup, I can see dedicating an entire PR just to generating a testbed (ocio config + transforms) and thoroughly testing ColorProcessorHandle-generating IBAs, etc.
How about this -- let me see if I can bang out some NamedTransform-specific tests before the weekend; and if not, I'll circle back to this in a near-future PR, one way or another.

Sounds good.

Since the weekend came and went, I'm going to merge what you have so far (it's all new functions, so it can't break previously-working functionality). I trust you to come back shortly and add tests.


Home page lazy load images, add loading icon at bottom

When switch category, also use lazy loading. E.g. https://lab.openpitrix.io/apps/category/ctg-uncategorized, first request only fetch 10 images, when scroll down, load more..