Doc issues + Rectangular or lasso selection is not available out of the box, right?

First, in the docs for "Adding Interactivity", the links here

The picking engine is exposed through the DeckGL.pickObject and DeckGL.pickObjects methods.

should probably go to

http://deck.gl/#/documentation/deckgl-api-reference/deck?section=methods

instead of

http://deck.gl/#/documentation/deckgl-api-reference/react/deckgl

because the picking methods are covered in the docs for Deck, but not in the docs for the DeckGL component.

Second, in the Deck docs there is some confusion:

pickMultipleObjects
Performs deep picking. Finds all close pickable and visible object at the given screen coordinate, even if those objects are occluded by other objects.
deck.pickObject({x, y, radius, layerIds, depth})

Should the example there be about pickMultipleObjects rather than pickObject?

Finally, in early 2017 it looks like there was an idea of supporting rectangle or lasso selection. I don't think lasso was ever implemented, and for rectangular region selection, an earlier questioner was pointed to the pickObjects docs #1683.
I wanted to confirm that there's no built-in notion of selecting a set of objects. I've started doing something like this...
export default class SelectablePolygonLayer extends PolygonLayer {
  renderLayers() {
    var {id, getFillColor, data, isSelected, ...rest} = this.props;
    const selectedOverlayProps = {
      id: `selected-${id}`,
      getFillColor: [64,64,64],
      data: data.filter(isSelected),
      ...rest
    };

    const overlay = new PolygonLayer(selectedOverlayProps)
    return [...super.renderLayers(), overlay];
  }
}

and then, using my particular data structures...
          isSelected: cellEntry => this.state.selectedCellIds[cellEntry[0]],
          onClick: info => {
            const cellId = info.object[0];
            if (this.state.selectedCellIds[cellId]) {
              this.setState((state) => {
                delete state.selectedCellIds[cellId];
                return {selectedCellIds: state.selectedCellIds}
              })
            } else {
              this.setState((state) => {
                state.selectedCellIds[cellId] = true;
                return {selectedCellIds: state.selectedCellIds}
              })
            }
          }

... which lets me select individual objects, but maybe there's a better way? Thanks!

Correct, deck.gl does not have the notion of "selection". Rectangular selection can be implemented with deck.pickObjects, and lasso (picking by arbitrary bounds) is going to be tricky.

I've started doing something like this...

I believe "lasso" type selections are indeed implemented in some of our internal deck.gl (or rather nebula.gl) applications the way I believe you are proposing, by creating a non-pickable "mask" layer with a polygon that covers the screen and has a lasso-shaped hole.
Then any non-hidden objects can be picked with Deck.pickObjects.
However, I don't think the technique required any custom/subclassed layers, the standard polygon layer did the trick.
@georgios-uber am I getting this right? Does nebula.gl itself contains any code or example of this technique?

Oh, thanks: That sounds like an interesting approach. For now I'll try to get the rectangular selection first, and then look at the lasso: If I get something tidy, I'll post an example here.
(For me, making a composite layer seemed like an easy way to distinguish the behavior and style for the selected and unselected objects, but I could see putting if-thens in the properties, too.)
Feel free to close?

I've started doing something like this...

I believe "lasso" type selections are indeed implemented in some of our internal deck.gl (or rather nebula.gl) applications the way I believe you are proposing, by creating a non-pickable "mask" layer with a polygon that covers the screen and has a lasso-shaped hole.
Then any non-hidden objects can be picked with Deck.pickObjects.
However, I don't think the technique required any custom/subclassed layers, the standard polygon layer did the trick.
@georgios-uber am I getting this right? Does nebula.gl itself contains any code or example of this technique?

Yes, nebula uses standard deck methods to implement selection.

@georgios-uber : Thanks! I'll look deeper into that. I filed some small PRs on the docs, but I think I'm still confused by the relationship between Deck and DeckGL. At the end, the DeckGL docs say:

All Deck methods are available on the DeckGL component.

I may be interpreting it wrong, but it doesn't seem to work that way for me:
    ...
    this.deck = <DeckGL {...props}/>;
    console.log('pickObjects?', this.deck.pickObjects);
    console.log('other properties:', this.deck);

produces:
pickObjects? undefined
other properties:
    {$$typeof: Symbol(react.element), type: ƒ, key: null, ref: null, props: {…}, …}
    $$typeof: Symbol(react.element)
    key: null
    props: {controller: {…}, getCursor: ƒ, onDrag: ƒ, onDragStart: ƒ, onDragEnd: ƒ, …}
    ref: null
    type: ƒ DeckGL(props)
    _owner: FiberNode {tag: 1, key: null, elementType: ƒ, type: ƒ, stateNode: Spatial, …}
    _store: {validated: false}
    ...

The pickObjects method is not available there.
I've also tried something like nebula, here, but for me the context is undefined, and even if it weren't, the layerManager docs make it sound like an internal I should not need to touch.

Your JSX stanza (this.deck = <DeckGL {...props}/>;) is only going to return a tiny ReactElement descriptor, which holds the props and is later used during the React diffing process to create/update the actual React component instance.
You need to get a ref to the actual DeckGL React component, that ref will have the functions you seek.
https://github.com/uber/deck.gl/blob/master/modules/react/src/deckgl.js#L79
Google "React refs" to see how this is done, i.e. <DeckGL ref={....

That solves that problem. Thank you! I'll close this.
There are still issues, but it's on my side: My data has coordinates from 0-50000, and if I try too large of a region I have an error in drawAndSamplePickingBuffer:
var pickedColors = new Uint8Array(width * height * 4);
Uncaught RangeError: Invalid typed array length:<PHONE_NUMBER>

Figuring out exactly what that limit is:
> new Uint8Array(Math.pow(2,31))
  Uncaught RangeError: Invalid typed array length:<PHONE_NUMBER>
> new Uint8Array(Math.pow(2,31)-1).byteLength
<PHONE_NUMBER>
> new Uint16Array(Math.pow(2,31)-1).byteLength
  Uncaught RangeError: Array buffer allocation failed
> new Uint16Array(Math.pow(2,30)).byteLength // Might squeeze out a little more memory by using a different type? Not sure what's going on here.
<PHONE_NUMBER>

So, for me, I think I'll keep my coordinates as they are, and implement my own region selection, but may revisit this in the future. Thank you again!


2.x Deprecate Timber\PostClassMap filter and rename it to timber/post/classmap

Ticket: #2073
This pull request handles the following todo in #2073.

[x] Deprecate Timber\PostClassMap filter and rename it to timber/post/classmap. Currently, it’s called timber/post/post_class in the 2.x branch.

The filter timber/post/post_class was added in the 2.x way earlier, so it’s safe to remove it.
Considerations
I guess were not exactly deprecating the Timber\PostClassMap filter, because it will not work the way it did before. We can also consider using Helper::doing_it_wrong() instead. On the other hand, when upgrading to 2.0, you will want to remove all notices that will appear, including the notices about deprecated hooks. So maybe it doesn’t really matter.
What do you think?
Testing
~Not yet.~ Now added.

@gchtr I don't think it's necessary to go too deep on the deprecation protections here (beyond what you've done already). The way classes are handled with Factories means so many changes that I don't think a single "missing" doing_it_wrong() is really going to be of much value.
Would you like me to develop tests here or do you already have that covered?

@gchtr I don't think it's necessary to go too deep on the deprecation protections here (beyond what you've done already). The way classes are handled with Factories means so many changes that I don't think a single "missing" doing_it_wrong() is really going to be of much value.

👍

Would you like me to develop tests here or do you already have that covered?

@jarednova Currently, you could only add tests for the deprecation of the filter, but not how the post class map actually works, because Coby is still working on that. But I’d be glad if you could add the tests for the deprecation.

The Class Map filters are all tested at the Factory layer. We don't have any doing_it_wrong() reporting right now because I wanted to circle back to it once we had a good architecture. That has been discussed here as well. I thought I remembered some follow-up discussion to that but I can't find it right now; in any case I don't think we arrived at a conclusion.
My main concern in this area is what happens when someone returns a class name from a timber/*/classmap filter that doesn't implement CoreInterface. PHP will throw a Fatal Error when the Factory's ::build() method tries to return it. So my questions is whether we call doing_it_wrong() and let it fail directly afterward, or if we throw our own exception immediately explaining exactly what happened.

@acobster if I'm following you here correctly, I think the place to go is with ...

we throw our own exception immediately explaining exactly what happened.

Since it's a fatal error, an exception would feel most appropriate. In the docs for WordPress's _doing_it_wrong() it uses the phrase "called incorrectly" which feels like a softer warning.

@gchtr for some reason this is triggering a ton of ...
[ Timber ] Class T either does not exist or implement \Timber\Post

warnings in PHPUnit. I'm trying to rope through and figure out where that's originating, but can't seem to track it down. Is this worth time? or does the forthcoming work from @acobster (perhaps) render that irrelevant?

The Class Map filters are all tested at the Factory layer. We don't have any doing_it_wrong() reporting right now because I wanted to circle back to it once we had a good architecture. That has been discussed here as well. I thought I remembered some follow-up discussion to that but I can't find it right now; in any case I don't think we arrived at a conclusion.

Discussion is a bit scattered. I guess we discussed this in https://github.com/timber/timber/pull/2073#issuecomment-583776292 and then further in https://github.com/timber/timber/pull/2196, which led to this issue for the future: https://github.com/timber/timber/issues/2210.

I'm trying to rope through and figure out where that's originating, but can't seem to track it down. Is this worth time? or does the forthcoming work from @acobster (perhaps) render that irrelevant?

I would really wait for the rest of the post factories to be implemented first, and then come back to see how we do error handling. I only wanted to work alongside Coby. There are a few other pull requests that also need to wait for other functionality. I’m going to add wip labels for these to make it more clear.

FYI I updated the base branch here just to compare with the bleeding-edge Post API. We can still move forward with this (or not) however we choose.
@gchtr I think the TODOs for this PR boil down to:

[ ] PostGetter will no longer be used at all, so the Timber\PostClassMap filter will have no effect at all. So if I'm understanding the way it worked in 1.x, there's nothing for us to really hook into and no way for us to even discern that a user is doing_it_wrong() by adding such a filter! So I think we should just make a note that this is a breaking change.
[ ] It adds a docblock for the new timber/post/classmap filter.
[ ] It (potentially) adds a check and a corresponding Exception when the result of the classmap filter is something other than a CoreInterface instance. We could write up a new issue for that, but at this point I'd favor just doing it here.

cc @jarednova

I had to merge in the current version of the 2.x-posts-api branch.

PostGetter will no longer be used at all, so the Timber\PostClassMap filter will have no effect at all. So if I'm understanding the way it worked in 1.x, there's nothing for us to really hook into and no way for us to even discern that a user is doing_it_wrong() by adding such a filter! So I think we should just make a note that this is a breaking change.

Could we add a call to the deprecated filter right before we use the timber/post/classmap filter and check whether a filter was applied?
/**
 * Filters the class(es) used for different post types.
 *
 * @deprecated 2.0.0, use `timber/post/classmap`
 */
if ( 'deprecated' !== apply_filters( 'Timber\PostClassMap', 'deprecated' ) ) {
	\Timber\Helper::deprecated(
		'The `Timber\PostClassMap` filter',
		'the `timber/post/classmap` filter',
		'2.0.0'
	);
}

// ...
$classmap = …

It adds a docblock for the new timber/post/classmap filter.

Should be okay now.

It (potentially) adds a check and a corresponding Exception when the result of the classmap filter is something other than a CoreInterface instance. We could write up a new issue for that, but at this point I'd favor just doing it here.

I’d be glad if you could add that!

@acobster @jarednova I could still use some feedback on my recent comment, so we can finalize this 😊.
By merging in the current 2.x branch, we lost the PostGetter class, so apparently there’s no Timber\PostClassMap filter to deprecate. Still, I’d find it helpful if we could add a notice (not in the sense of a deprecation) in case this filter is still used.

@gchtr I see - just some extra guardrails around the new hooks, warning of the old usage. Makes sense! I will add that in along with the Exceptions, probably some time next week.

@jarednova This is now good for another review.
I added my proposal from https://github.com/timber/timber/pull/2293#issuecomment-704484660 and added a test to make sure it works as expected. And I added the remaining todo as a separate issue in #2487 so that it doesn’t get lost.

This looks good! (and feels like how it should have now always been). Thanks for pulling in some of those lingering notes and capturing #2487 for the future


Introduce Literal as an own type

Final contribution to making kinds of RDF terms own types.
Previous PRs: #49 , #48 , #47
Closes: #34
Input from: #35 and previous PRs

This PR refactors sophia::term::Term's Literal variant into an own, public type and aligns its interface to the APIs of the previous PRs for other kinds of terms.
Due to its scale and decisions to discuss this is marked work-in-progress.
ToDo:

[x] Create type Literal.
[x] Refactor _literal_kind.rs into literal.rs.
[x] Integrate Literal into Term.
[x] Refactor conversion primitive types <-> literal.
[ ] Final alignment of Variable, BlankNode, Iri and Literal to provide a uniform API for terms.

[x] Remove unsafe from all *_unchecked() methods and introduce debug_assert!().
[x] Similar implementations of From, TryFrom, PartialEq and other convenience traits.
[ ] ...

As always, the todo-list is my personal roadmap and is open to discussion.

If any changes are requested I'm happy to follow or discuss.

One moment please I'm just doing some last minor changes myself

Now I'm done :wink:


Tensorboard logger: let x-axis be epochs instead of step for training logs

What is your question?
Hello PyTorchLightning Community.
We upgraded from version 0.8 to the current version 1.0.8 and then got the error that training_epoch_end cannot return any results.
We used that before to aggregate our metrics and then return the averaged logs.
We removed the method and instead are using the self.log_dict now in training_step and it works.
However, on the x-axis there is now a step number which is corresponding to batch update steps and not the epoch number.
What's the recommended way to have it be the epoch number?
Code
What we had before:
def training_epoch_end(self, outputs):
    avg_loss = torch.stack([x['loss'] for x in outputs]).mean()
    tensorboard_logs = {'0_train/loss': avg_loss}
    for name in self.metrics:
        tensorboard_logs['0_train/{}'.format(name)] = torch.stack([x['metr'][name] for x in outputs]).mean()
    tensorboard_logs['step'] = self.current_epoch  # This was used to log by epoch instead of by step

    return {'loss': avg_loss, 'log': tensorboard_logs}

What have you tried?
We removed the training_epoch_end method and instead in our training_step do:
self.log_dict(metrics_dict, on_step=False, on_epoch=True)
For validation it still works, so we have the validation_epoch_end method and tensorboard logs per epoch and also shows the epoch numbers on the x-axis.
Any help how to have the same behavior in the current version again would be much appreciated.

I have the same question, I was returning a dict of metrics in validation_epoch_end before and the model checkpoint will read into it and monitor one of the metric.
And also I log these metrics to tensorboard using epoch instead of step.
Now there is a warning saying validation_epoch_end shouldn't return anything, and I have to use self.log which has the same problem as above which is I'm not able to specify the x-axis to be epoch rather than step.

I have the same question, I was returning a dict of metrics in validation_epoch_end before and the model checkpoint will read into it and monitor one of the metric.
And also I log these metrics to tensorboard using epoch instead of step.
Now there is a warning saying validation_epoch_end shouldn't return anything, and I have to use self.log which has the same problem as above which is I'm not able to specify the x-axis to be epoch rather than step.

Has anybody found a workaround to this problem?


DOC: fix cuts/dangles result order in polygonize_full docs

Closes https://github.com/shapely/shapely/issues/1691

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
2394

Relevant Lines:
2748

💛  - Coveralls


Add docker 1.11 and latest installation options to engine opts

Version - master 6/17
Verified fixed


FollowRedirectsBackend does not alter method on redirect to GET, as most user agents do

https://tools.ietf.org/html/rfc2616#page-62 says that this behavior is unspecified, but most user agents (and all browsers) follow the logic of a method being changed to GET upon receiving a 302. This means that the client won't behave as expected for many servers.
Given that this is implementation-dependent, but most implementations choose to change the method to GET, I argue sttp should do the same.

Closed! I see the option is here. Nevermind.


feat: Reimplement imports and expose wildcards as a named node

Make the import name much more restrictive, this helps avoid conflicts between dotted names and "." before "*" in imports.
Don't allow aliases with wildcard import, choose one or the other.
Write more test cases.

I used this docs as a reference: https://www.groovy-lang.org/structure.html
Related:

https://github.com/nvim-treesitter/nvim-treesitter/pull/6979

ping @murtaza64

Thanks, I'm on holiday so might not be able to merge straight away but will take a look soon!

PR looks good. Do you need to update the highlights upstream for groovy too? If so, I'd appreciate if you could update the highlights here too!


🎨 Adding tag AWS Runner-Manager

Removed the link on https://github.com/scality/devinfra/issues/83 as it's a different topic/PR

Removed the link on scality/devinfra#83 as it's a different topic/PR

Done!


Suggest to enlarge default resource name char length limit to 63

The default resource name length when running helm create is limited to 24 chars,
suggest to enlarge it to 63 chars as kubernetes 1.4 should have already supported this by this PR.

Since this is a minor change, I have submitted a PR (https://github.com/kubernetes/helm/pull/1830) for this,  please help to check if this is suitable for merge.

Thanks. I am marking this as closed with #1830 , which I just merged.
Thank you for the PR.

@technosophos My pleasure, thanks for this great project. :)


Consistently handle forward and reverse sides of 1:N relations

Changes Unknown when pulling 2735461eb532a68a50d660574a667055cbe081b8 on CyberiaResurrection:BiDirectionalBugFix into ** on Algo-Web:master**.


Use DB backend in test client

closes #1603
Also fixed two issues, revealed by this migration:

wrong assumptions about API safety in changes trie storage implementation;
fixed simultaneous import of block B + finalization of its ancestors (i.e. #1602).

This PR also introduced test_client::new_light to be used in integration tests. The test_client::LightFetcher is currently a stub, because I'm not sure yet about its implementation (it will be fixed as a part of #1669).

Can we not then drop client/in_mem.rs?

But the kvdb in memory implementation is also just in memory? In my opinion this just requires additional code that is only used in tests and we don't test the real code that interacts with the db interface.
We should maybe improve the implementation of the kvdb in memory to support stuff like comparing etc.

But the kvdb in memory implementation is also just in memory?

Comparing kvdb = comparing db-level representation (columns, ...) even if we improve it. Also it could be affected by some irrelevant factors (insertion order - idk?). To compare two client backends we need to compare the set of headers + the set of chain (best + last finalized + ...) + ... => we'll need several HashMaps + insertion ops anyway (which is in_mem::*).

In my opinion this just requires additional code that is only used in tests and we don't test the real code that interacts with the db interface.

Exactly. We have a lot of code that is only used in tests (helpers/stubs/mock objects/...). Consider in_mem::* as another one helper. Like we do not tend to use wasm executor in every test, though there are some tests that are testing it.

That said, I'm ready to give up if you'll find more supporters on your side :) But would prefer to separate "Use DB backend in test-client" and "Get rid of in-memory backend" tasks.

I don't want you to give up^^
It is just that kvdb-memorydb uses a hashmap internally: https://github.com/paritytech/parity-common/blob/9abaf267d1319ed65e2fdd90ee55432dc4540f78/kvdb-memorydb/src/lib.rs#L29
In #1609 we have the situation that we need to implement a completely different interface for in_mem. Thus, the real interface will not be tested by unit tests. So, we maybe do not catch bugs in tests.

I'd say that it is probably better to rebase #1609 on this PR && add unimplemented!() in in_mem::Blockchain::children() until some specific implementation is actually required for some low-level tests. I could see that right now all new tests there are using test_client::new() => DB backend will be used.

Okay, sounds like a plan :)


v0.1 build is not published to npm

src are published to npm instead of build ;)
after install, you have to
cd node_modules/rollup-plugin-web-template/ && npm i && npm run build && cd  ../../

OK, sorry, "dist/rollup-plugin-web-template.js" is included to NPM now.


Packaging with Nix - Error: test_output_functions_BLS381 (Failed)

I'm trying to package this library with Nix. But I'm getting the following error:
       > 97% tests passed, 1 tests failed out of 39
       >
       > Total Test time (real) =   1.35 sec
       >
       > The following tests FAILED:
       >         33 - test_output_functions_BLS381 (Failed)
       > Errors while running CTest
       > make: *** [Makefile:114: test] Error 8

and, with ctest:
33/39 Test #33: test_output_functions_BLS381 .....***Failed  Required regular expression not found. Regex=[SUCCESS
]  0.00 sec

When I try to build the library directly on my system (arch linux x86_64) everything seems to work just fine.
I'm using the cmake flags that are needed to build Decentralized Trust Authority.
Does anyone knows the reason why this is happening?

@pallatinus  do you have a branch to share and debug?


Make course grade column header clickable to sort asc/desc

From @steveswinsburg on July 11, 2015 22:53
Make course grade column header clickable to sort asc/desc
Copied from original issue: steveswinsburg/gradebookNG#141

Hey @kyleblythe just checking if we have a requirement for this? I don't have much in the original ticket so can't remember if this is something I came up with myself or something we discussed.

Discussed 29/1/2016
Make this a clickable heading, consistent with the other assignments. Clicking will toggle the sort by asc/desc.
Implementation notes
Need to add a comparator, an entry to GradebookUiSettings to store it (noting that each thing that is clicked clears the sorting of the other fields), pass this setting in to the matrix builder, then add a block for sorting using the comparator.

I've got this assigned to me as it is straightforward and was going to give to @amiedavis if possible.

Note that this is trickier now that we have the GbCourseGradeLabel which does all of the logic. That logic is being moved to the service for generating a display string

Hi @steveswinsburg
Interesting...a few things:

When sorting ascending/descending by course grade, there's no up/down arrow that displays to the far right of the column header letting you know that it's sorted/which way it's sorted:

Also, as you can see in the screenshot above, the "Course Grade" text seems to have some padding on top that the other column headers do not have.

As of right now, once you start sorting by the "Course Grade" column, you cannot then start sorting by another column. I can click on other column headers and the page will refresh. Then, even though there's a sorting up/down arrow on that item's column header, the table itself is still sorted by the course grade:

Lastly, it looks like, even when you're sorting ascending, the actual percentages for the students are still being sorted descending. So, even though F's will display at the top, the percentages themselves still descend:

Also, as you can see in the screenshot above, the "Course Grade" text seems to have some padding on top that the other column headers do not have.

This one is due to some CSS that can now be removed! Namely #gradebookGrades .gb-course-grade > div {   padding: 6px 0; }

Discussed on the call, currently this sorts by the course grade display string which is built using the settings. Could just sort by points only but then course grade overrides would not be considered.

I'll have a go at introducing a course grade sort string that will allow sorting by grade letter (including the overridden value) then the point value.  Kinda like this maybe: . For example:
0000003700000100 == A- (100)
0000004000000120 == A+ (120)
0000003700000090 == A- (90) (B overridden as A-)

Ok cool. The GbCourseGradeFormatter figures out the display string, it could also determine the sort string at the same time. So if you returned a String[] and picked out the values for both display and sort and stored the sort in the GbCourseGrade. Then just flip the comparator over to use the sort string :thought_balloon: :ok_hand:

Hi @payten in your example above, I think A+ would need to be 42. But I think you may we using a different scheme for this anyway. We'll need to be able to account for anything from A+ down to F-. I think we'll also want to account for Pass / Not Pass: http://www.screencast.com/t/fedQWy7QgY0

Yep, good catch @jeffpasch.  I think we'll need to base our letter ordering off the grade scheme completely -- especially as instructors can create completely custom/random grading schemes if they desire.
The pull request above aims to use this grading scheme to order the letter grade (taking into account the overridden grade letter value) and then secondarily orders by points.

Ok this is in, lets see if it does what we need 👍

Hi @payten and @steveswinsburg ,
Looks like the secondary ordering by points isn't getting reflected. :-/ It appears to still order primarily by the letter grade, then using the student name as the secondary sort:

It is, however, now allowing you to switch from course grade column sorting to item-based sorting, so we're good there.

Thanks @kyleblythe.  It looks like I was sorting on the pointsEarned, which doesn't always match up with the calculatedScore (which takes into account weightings and extra credit scores).
I've changed the sorting algorithm to first sort on the index of the letter grade within the grading scheme and then by the calculated score.   PR pending.

Confirmed! Working great!

Will create a separate issue for sorting within the "Students" column.


CAS Errors out on https://rcos.io

I have made a ticket with DOTCIO to get this fixed: https://itssc.rpi.edu/hc/en-us/requests/71589

Should be fixed as of 09/30/2021


JWT authorization only?

Hello,
I'm currently testing this Gem for accessing the Smooch API, mainly the post_messages feature, but I'm realizing only the JWT authorization works.
At the beginning, I was configuring only the Basic Authentication (as described in the Readme):
SmoochApi.configure do |config|
      config.username = 'API_KEY_ID'
      config.password = 'API_KEY_SECRET'
end

But all my requests failed: SmoochApi::ApiError: Unauthorized
After some debugging, I found that: the request (made by build_request in SmoochApi::ApiClient) had the header Authorization set to nil (which now is making sense for the Unauthorized error). So I looked deeper and this Authorization header is set by the method update_params_for_auth! which is taking as argument a list of "authorization methods" I guess. And in the method post_message_with_http_info, you can see line 336 this code: auth_names = ['basicAuth', 'jwt'] => which means: to use/try both authentication methods.
But, in update_params_for_auth!, the authentication method is skipped if not found in the configuration, but this default configuration sets both here - which means, the next unless auth_setting in update_params_for_auth! is not enough, because only the last value of auth_names will be used: jwt
It can be fixed by checking if the value of the authentication method is not nil - like by replacing next unless auth_setting by `next if auth_setting.nil? || auth_setting[:value].nil?.
Let me know if I'm missing something, and/or if you want me to do a PR for that.
Thank you very much

Thanks for the report, and the detailed investigation! This should be fixed in the latest version 5.24.1


enhance FloatHistogram CopyToSchema method

Fix #11270
The basic idea behind the current implementation of the CopyToSchema method is

first convert the FloatHistogram.PositiveSpans/NegativeSpans into targetSchema  by floatBucketIterator
then got each bucket in targetSchema by Next()
then add back to the target FloatHistogram object

Basically we can summarize the process is OriginalSpan[] -> TargetBucket[] -> TargetSpan[]
So I think we could enhance this process into OriginalSpan[] -> TargetSpan, by directly processing the Spans
So I wrote a simple implementation in this idea, with Function name CopyToSchemaNew and wrote a benchmark test for CopyToSchema and CopyToSchemaNew
The test result shows that the enhanced one is 50% faster than orignal one on my laptop
BenchmarkCopyToSchema-8      	 1176043	      1023 ns/op
BenchmarkCopyToSchemaNew-8   	 2502216	       498.0 ns/op

All comments are resolved
@beorn7

@beorn7 All comments are fixed.


Prevent exporting server components with client components

Description
Sometimes (but not always), we will see this when attempting to build a Hydrogen app:
[vite-plugin-react-server-components] Cannot import ./ShopifyProvider.server from "/home/runner/work/hydrogen/hydrogen/packages/hydrogen/src/foundation/ShopifyProvider/index.ts". By react-server convention, .server.js files can only be imported from other .server.js files. That way nobody accidentally sends these to the client by indirectly importing it.
error during build:

I'm not sure why we don't always see it. Perhaps has to do with how the source is built. Regardless, this PR ensures we are more careful about exporting a server component explicitly rather than from a shared component. This also prevents server-only logic from leaking into the client via useShop() etc.

I think I can get this error most every time when doing yarn test-e2e --clearCache && yarn test-e2e? Or at least, it's currently hitting me every time.
(You get a more detailed error log of why it fails if you take out the --logLevel silent command)


MW not detected as a coremod

First, it did this...
[00:33:46] [main/DEBUG] [FML/]: Examining for coremod candidacy movingworld-MC1.8-V1.8.1.jar
[00:33:46] [main/INFO] [FML/]: Loading tweaker org.spongepowered.asm.launch.MixinTweaker from movingworld-MC1.8-V1.8.1.jar
...but didn't say "Adding movingworld to list of coremods". Then it gives the error:
[00:33:56] [Client thread/ERROR] [FML/]: The mod ArchimedesShipsPlus (Archimedes' Ships Plus) requires mods [MovingWorld] to be available
Using Forge 1.8-<IP_ADDRESS>3, Minecraft 1.8, and a number of other mods which loaded and worked fine when not using AS+ and MW.

This has been addressed a multitude of times, try without other mods, try and single out the problem causer, make sure you're using their latest build, update to the latest forge, etc. Also, read the CONTRIBUTING file (the one that it tells you to read before submitting an issue) BEFORE you submit an issue.
If you're not sure what to do look at other closed issues and you should be able to find a similar situation and how they resolved the issue.


Jesse: Watch khidmatgaar.com

Jesse requests the watch of the watch_keyword khidmatgaar\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

khidmatgaar\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


Transfer ownership to JSFoundation

Since all of the projects in ESLint organization are under JSFoundation, we should transfer ownership of this project over as well. @kborchers could you provide the steps necessary to do that?

So it looks as if this project was created within the ESLint org after the JSF took ownership of the project, is that correct? If so, technically the JSF already owns this repo and the copyright info in the license is incorrect and just needs to be updated and you're done.
If it was created elsewhere and transferred in, it should not have been transferred in without an explicit assignment. I'll have to talk to legal about the best way to proceed in this scenario but just let me know the sequence of events and we'll go from there.

I created the repo as not-an-aardvark/eslint on January 11th. A bit later, I made an issue to suggest transferring the repo to the eslint organization. On February 16th, the ESLint TSC decided to accept that proposal, so I transferred the repo to the eslint organization right after that.

Hmm, OK. My guess is legal will say that a case could be made that the vote to transfer in will act as a transfer to the JSF but I will double-check and let you know.

Sounds good, thanks! Sorry about the inconvenience -- I hadn't realized that there was an official process for transferring the repo.

No worries. We're still working in documenting things like this so we're all learning as we go. 😉

@not-an-aardvark @kborchers Did we resolve this?

I'm not sure -- I haven't heard anything about this aside from the contents of this issue.

Sorry, this definitely fell off my radar. I have pinged legal on it and will respond ASAP. My apologies again for the delay.

Legal has confirmed that since all 3 contributors on the project have signed the CLA, this is ready to close with 1 exception. Please change the copyright line in the LICENSE.md to just Copyright contributors and then you are good to go.

@kborchers "Copyright contributors", not "Copyright JS Foundation and other contributors, https://js.foundation"?

@platinumazure Correct. In this case, since the copyright was never assigned to the JSF, just licensed via the CLA, we can not claim copyright ownership. In general, we would prefer to do a full assignment with paperwork and everything but decided for this one instance, it was not necessary and wouldn't burden the 3 contributors with the paperwork. Happy to do it if you would prefer consistency, but not necessary.
All of that said, you should always ping the TAC or me before transferring in a repo going forward.

@kborchers Would it cause problems if it said something like "Copyright ESLint team and contributors"? It reads a little more naturally, but if it could raise legal questions about "wait, did the 3 contributors actually transfer copyright to the ESLint team", then we can just leave it at "Copyright contributors".

We should definitely follow legal's advice here and either do a full IP assignment and use the usual copyright line with JS Foundation in it or just use "Copyright contributors" to avoid any issues.

@kborchers Seems like our TSC should probably evaluate which path they want to take here. We'll ping you if we decide we want to do a full IP assignment. In the meanwhile, would you please read the summary below and advise if I misrepresented anything? Thanks!
TSC Summary
Kris Borchers from JSF has given us two paths forward to fully resolve the IP/ownership issues around this repository:

Declare "Copyright contributors" in the copyright file and do nothing further (JSF will not assert copyright and does not need to)
Do a full IP assignment of this repository to JSF, which requires all committers so far (3 at last count) to fill out paperwork of some sort. Then declare "Copyright JS Foundation and other contributors", same as ESLint itself.

TSC Question
Which path do we want to take in order to finish (legally) transferring ownership of this repository!

@platinumazure LGTM

In today's TSC meeting, we decided to just use "Copyright contributors".


Fix dependency on newer versions of python-dxf

Since python-dxf 10.0.0 internal method _get_dcd is not available any more. Add proper fix to support this version and newer ones.

Fixed at d6189ac8ceeadbae9ace5e984c18f023f601dd8e


Fix PoisonError and deadlocks in tests.

When running tests in parallel, deadlocks may happen if a thread panics inside a critical section and doesn't reach release.
Additionally, a panic causes the global mutex to be poisoned so we need to clear the poison.

Discussed in today's WG meeting:

There's consensus that the wanted behavior if f panics should be "leave the CS unlocked", not "leave locked/poisoned".
We should check the code changes in with don't result in increased code size in programs with panic=abort (when compiled with optimizations).
The behavior should be documented in with's docs.

Added docs and #[inline(always)] to the drop function.


Confirm propagation independently of the broascating mean

In previous versions the propagation was confirmed only when the transactions were broadcast to the peer-to-peer network. However, it is important to verify the propagation also when it is sent directly to the trusted node using the RPC interface or when the transaction is sent to the backend.

The problems seems to be:

we cannot distinguish node as exposed as onion services
we receive duplicated messages
we send inv messages with MSG_TX  but we receive them as MSG_WTX


Tcpdump test fails?

I've got the following error during tests of tcpdump today. My question would be in the sense of this behaviour of start/exit/Received data process is happening as expected? Should I see the on / the data fetched from the target pods?
Snoopy Operator data pod:
snoopy-operator# kubectl exec -ti -n snoopy-operator snoopy-data-747ff95898-8k86r -- /bin/bash
bash-5.1# ls
bin     dev     etc     home    lib     lib64   media   mnt     opt     pcap    proc    root    run     sbin    server  srv     sys     tmp     usr     var

Some of cnf-pods logs:
snoopy-job-cnf-example-pod-7b464f54d6-9cl5w-tt42j podtracer I0224 12:37:53.291663       1 request.go:665] Waited for 1.037839544s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/snapshot.storage.k8s.io/v1?timeout=32s
snoopy-job-cnf-example-pod-7b464f54d6-q662c-dc5tg podtracer �ò�tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
snoopy-data-747ff95898-8k86r snoopy-data 2022/02/24 12:37:55 start new server
snoopy-data-747ff95898-8k86r snoopy-data 2022/02/24 12:37:55 exit
snoopy-job-cnf-example-pod-7b464f54d6-q662c-dc5tg podtracer 2022/02/24 12:37:55 Received: Received data for pod cnf-example-pod-7b464f54d6-q662c
snoopy-job-cnf-example-pod-7b464f54d6-q662c-dc5tg podtracer 2022/02/24 12:37:55 finished with pod data
snoopy-job-cnf-example-pod-7b464f54d6-q662c-dc5tg podtracer 2022/02/24 12:37:55 context canceled
snoopy-job-cnf-example-pod-7b464f54d6-9cl5w-tt42j podtracer �ò�tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
snoopy-data-747ff95898-8k86r snoopy-data 2022/02/24 12:37:55 start new server
snoopy-data-747ff95898-8k86r snoopy-data 2022/02/24 12:37:55 exit
snoopy-job-cnf-example-pod-7b464f54d6-9cl5w-tt42j podtracer 2022/02/24 12:37:55 Received: Received data for pod cnf-example-pod-7b464f54d6-9cl5w

Node which is running the cnf-example-pod:
/snoopy-operator# kubectl get pods -n cnf-telco -o wide
NAME                               READY   STATUS    RESTARTS   AGE     IP             NODE                                         NOMINATED NODE   READINESS GATES
cnf-example-pod-7b464f54d6-9cl5w   1/1     Running   0          4m30s   <IP_ADDRESS>   ip-10-0-141-229.us-west-2.compute.internal   <none>           <none>
cnf-example-pod-7b464f54d6-q662c   1/1     Running   0          4m34s   <IP_ADDRESS>   ip-10-0-141-229.us-west-2.compute.internal   <none>           <none>

Nodes which is running the snoopy-operator and its jobs:
snoopy-operator# kubectl get pods -n snoopy-operator -o wide
NAME                                                READY   STATUS      RESTARTS   AGE     IP             NODE                                         NOMINATED NODE   READINESS GATES
snoopy-data-747ff95898-8k86r                        1/1     Running     0          32m     <IP_ADDRESS>    ip-10-0-189-217.us-west-2.compute.internal   <none>           <none>
snoopy-job-cnf-example-pod-7b464f54d6-9cl5w-tt42j   0/1     Completed   0          3m52s   <IP_ADDRESS>   ip-10-0-141-229.us-west-2.compute.internal   <none>           <none>
snoopy-job-cnf-example-pod-7b464f54d6-q662c-dc5tg   0/1     Completed   0          3m52s   <IP_ADDRESS>   ip-10-0-141-229.us-west-2.compute.internal   <none>           <none>
snoopy-operator-d7cfcb599-7p75n                     1/1     Running     0          32m     <IP_ADDRESS>    ip-10-0-189-217.us-west-2.compute.internal   <none>           <none>

I guess this issue can be closed, once we've already posted a deployment sample using the hostname instead of ip.

@acmenezes , could you please close this issue?


way to automate advanced brewer

Describe your idea
As of right now on the minecraft 1.19.2 supported version of the mod
you can automate making duplication of potions part of the way
you can place the items in and have the potion made even take out the finished
potions but then the empty bottle can not be extracted from any side
I thought maybe this was intended to stop automation as to why you have the rest automatable then prevent the extraction of the empty bottle

If you're using a mod with pipes in your pack, you should be able to extract this bottle from the top side.


Scala 3 support

Would be great to have Scala 3 support for this library, though I'm not sure what would be required to do this, as there are no macros presently I guess this might be fairly straightforward?

Should be. The generic module has a shapeless-2 dependency which could be replaced (source-incompatibly) with shapeless-3 for Scala 3. I'm not sure where doobie is wrt Scala 3 ... @tpolecat?

Should be. The generic module has a shapeless-2 dependency which could be replaced (source-incompatibly) with shapeless-3 for Scala 3. I'm not sure where doobie is wrt Scala 3 ... @tpolecat?

doobie and skunk are both up to date and available for Scala 3, so this is probably doable

doobie and skunk are both up to date and available for Scala 3, so this is probably doable


1.9.4 1.0.5 not showing rf per tick for deep ressonance crystals

it just shows 0 rf/t

I cannot reproduce this. What version of Deep Resonance? Also can you give a screenshot?

deep ressonance  1.9.4 1.14beta32

Fixed next release of Deep Resonance (actually a bug in DR and not in TOP)


NameError: name 'java_common' is not defined

We're encountering the following error with skydoc 0.2.0 on Bazel 0.21 on rules that use java_common:
NameError: name 'java_common' is not defined

The rule has the following attrs entry
        "_jdk": attr.label(
            providers = [java_common.JavaRuntimeInfo],
            default = Label("@bazel_tools//tools/jdk:current_java_runtime"),
        ),

and refers to java_common in its implementation
    java_runtime = ctx.attr._jdk[java_common.JavaRuntimeInfo]

The rule itself works fine, however including it as a srcs entry to skylark_doc raises the NameError above.

This should be fixed (and we have an e2e test verifying java_common.JavaRuntimeInfo in particular)


Text says the command is for site collections, but the first sample is a subsite misidentified as a site collection

The text says this is for a top-level site (i.e. site collection).
Example 1 says:

This example creates a new Microsoft 365 Group named "site1group" and connects site collection https://contoso.sharepoint.com/sites/site1...

https://contoso.sharepoint.com/sites/site1 is a subsite.
https://contoso.sharepoint.com/sites is the site collection.
Something needs correcting here. Perhaps we expanded the capabilities?

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

ID: 9f97f530-5982-64b0-8cf5-02a9f361b75b
Version Independent ID: f10aeefa-17b4-1929-8e89-b8a2b67ee5fa
Content: Set-SPOSiteOffice365Group (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Set-SPOSiteOffice365Group.md
Service: sharepoint-powershell
GitHub Login: @trent-green
Microsoft Alias: trgreen

Hello @fselkirk How are you?
https://contoso.sharepoint.com/sites/site1 is actually a site collection and /sites/ is the managed path.
for example

A subsite would be: https://contoso.sharepoint.com/sites/Site1/Subsite1/
for example:

I have no idea where my brain was. You are completely right.
Frances Selkirk
Support Escalation Engineer | SharePoint Online and SharePoint Client Technical Support
fselkirk<EMAIL_ADDRESS>| +1<PHONE_NUMBER> | Available Monday – Thursday: 11:00 – 18:00, ET (GMT -5 :00)
Manager: Floyd Mathias  floydm<EMAIL_ADDRESS>| +1<PHONE_NUMBER>
Backup: Brian Yau  brian.yau<EMAIL_ADDRESS>|  +1<PHONE_NUMBER>
From: Andres Mariano Gorzelany<EMAIL_ADDRESS>Sent: Monday, August 31, 2020 09:50 AM
To: MicrosoftDocs/office-docs-powershell<EMAIL_ADDRESS>Cc: Frances Selkirk<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/office-docs-powershell] Text says the command is for site collections, but the first sample is a subsite misidentified as a site collection (#6416)
Hello @fselkirkhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffselkirk&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945680370&sdata=oWlBmokMcjOvc54D9OSCO3AOLk39i%2FUDGmj%2Fz3skAnc%3D&reserved=0 How are you?
https://contoso.sharepoint.com/sites/site1https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2Fsite1&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945690368&sdata=PxB7H6MvrWfq95fkRXUhxuMqiKLtw9fYhtviNALm17A%3D&reserved=0 is actually a site collection and /sites/ is the managed pathhttps://nam06.safelinks.protection.outlook.com/?url=https:%2F%2Fdocs.microsoft.com%2Fen-us%2Fopenspecs%2Fsharepoint_protocols%2Fms-wssts%2F4c7a8d5a-4bcf-45a1-a414-2c9878e4a897%23:~:text%3D2.1.%26text%3DA%2520managed%2520path%2520specifies%2520a%2Cpaths%2520and%2520wildcard%2520managed%2520paths.&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945690368&sdata=2r1UvDdU1rlaQHnUZI68VBy6bhkNSPj0UlTQBilkSXU%3D&reserved=0.
for example
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F36666927%2F91726249-50a6d300-eb76-11ea-81fd-9423a6caa27c.png&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945700359&sdata=OCx0ljsuN0Me2BlFOCq08JWfueqHJrgzwQc%2BghFTGiU%3D&reserved=0
A subsite would be: https://contoso.sharepoint.com/sites/Site1/Subsite1/https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcontoso.sharepoint.com%2Fsites%2FSite1%2FSubsite1%2F&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945700359&sdata=eDGv%2BB%2Fag774URgh7XMu1WW8HFfYN4MebLr%2Bo%2FyanZc%3D&reserved=0
for example:
[image]https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F36666927%2F91727144-9f08a180-eb77-11ea-8629-9294b9568ae8.png&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945710355&sdata=s0wTGZldE8cw9b464BeDMJ9gZrSiUTpvwrgP0rpq67Y%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F6416%23issuecomment-683790770&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945720354&sdata=p%2B9xcQkYAGrWwN6D%2FWzftbr%2FeIXOrPPCL%2F5UybNIquc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJFSDWP2LE3E2YMUPSM4FL3SDOTADANCNFSM4QNGYBJQ&data=02|01|fselkirk%40microsoft.com|9b1998831e9d453bcce908d84db4bd0f|72f988bf86f141af91ab2d7cd011db47|1|0|637344785945720354&sdata=l%2FNeoTjjJmTeuvI1vvOLeTsgNJQRSf1Hwv0dXqyOuw8%3D&reserved=0.

I have no idea where my brain was. You are completely right. Frances Selkirk Support Escalation Engineer | SharePoint Online and SharePoint Client Technical Support

No worries at all 👍 Thanks for getting back!

@get-itips Thank you very much for the contribution and sharing this explanation. @fselkirk Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also


Add world_state and first version of history_tutor

Adds a world_state json object which is passed between client and server and a ui element that's specific to each mode.
In the history_tutor example, a second prompt updates the world-state based on the chat history to indicate if the user has answered the questions correctly which prompts the conversation prompt to move onto other questions.
The history_tutor component currently displays the full worldstate but as a next step will display a count of questions that still need to be answered.

updated based on comments, ptal.


update lora-phy to v2 and remove external-lora-phy from modulation

The async-device implementation with lora-phy is updated to 2.1.1.
lora-phy now depends on the local repo crate lora-modulation v0.1.2, therefore we can remove feature from lora-modulation.
Also, a little bit of clippy is cleaned up.

DNM yet. Found some things to fix

All is resolved, I believe.


--filesystem=xdg-run/pipewire-0 reduces security

https://github.com/bilelmoussaoui/ashpd/blob/e082795083a86c78df5196c15759e34d742fcd8d/src/desktop/camera.rs#L121-L122
The portal doesn't return a node ID, but you can use the file descriptor returned by the portal to iterate the camera node IDs, making exposing xdg-run/pipewire-0 unneccesary. The portal sets up security restrictions on the socket before returning the socket to the application, but always ensures that the application can iterate and access camera devices.
--filesystem=xdg-run/pipewire-0 is insecure as it allows the application to effectively bypass the permission prompt.

My pipewire knowledge is limited, feel free to contribute a patch to make the pipewire_node_id uses the fd returned by the portal directly. I didn't manage to do so

This would require an API incompatible change as the application needs to pass the file descriptor to the function.

That's not a problem as the V2 is not API stable yet. It's still an alpha so such change in the api is not problematic

https://github.com/bilelmoussaoui/ashpd/blob/e082795083a86c78df5196c15759e34d742fcd8d/src/desktop/camera.rs#L113-L115

https://github.com/bilelmoussaoui/ashpd/blob/e082795083a86c78df5196c15759e34d742fcd8d/src/desktop/camera.rs#L113-L115
Not passing a node id won't confuse GStreamer as GStreamer can automatically iterate through nodes itself. However if the underlying node is disconnected, pipewire-media-session may incorrectly reconnect the client to a node that the client don't have access to.

https://github.com/bilelmoussaoui/ashpd/blob/e082795083a86c78df5196c15759e34d742fcd8d/src/desktop/camera.rs#L113-L115
Not passing a node id won't confuse GStreamer as GStreamer can automatically iterate through nodes itself. However if the underlying node is disconnected, pipewire-media-session may incorrectly reconnect the client to a node that the client don't have access to.

It does though, if you start a camera stream and then started a screen cast session, the screen cast stream is rendered in your end app instead of the camera one.
You can try it with the ashpd-demo by yourself and see. Note you will need to comment the code that checks for a node ID for the camera stream

Hmm... I was able to reproduce it on pipewire-media-session but not on my patched copy of Wireplumber. This is probably because if you don't give GStreamer a node ID, it will rely on the media session controller to auto-connect it, which connects to the wrong one.
I will test it against an unpatch Wireplumber later.


[FEATURE] avx512 aggregation for compress_store and algo

https://github.com/jfalcou/eve/pull/1232


pylyzer: 0.0.58 -> 0.0.59

Description of changes

pylyzer: 0.0.58 -> 0.0.59
pylyzer: move to pkgs/by-name

Changelog: https://github.com/mtshiba/pylyzer/releases/tag/v0.0.59

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.


Update bindblenderprogressivetilecallback.cpp

Updated immediate mode openGL, to modern openGL, using openGL shading language 3.30 core.

wouldn't glGetIntegerv(GL_CURRENT_PROGRAM, m_shader_program_id) fix this?

Work picked up by @mororo250 and PR superseded by #2549.


ACCUMULO-4867: Java Collections Improvements in DefaultLoadBalancer

Is this waiting on something for merge?

I was going to merge it after I do a quick build test to ensure no formatting fixes are required and that it doesn't introduce any new build warnings. I haven't had time, but I can do so now.

Hi @belugabehr, thanks for contributing. This is your second PR merged. If you're interested in contributing regularly, please consider subscribing to the developer mailing list and introducing yourself, and possibly describing which areas of the Accumulo project you're most interested in helping out with, so we can welcome you to our community and get to know you better.


Incomplete README

It's not completely clear what is this library for and how one can use it

Added installation guide.
Marking as resolved.

I can't agree with decision of this issue to be resolved.
There is still missing project motivation and description whatsoever

I really don't hasve time for this.
PR maybe?


Implement XML support

I would really like to be able to add this icon via xml layouts.

Ideally it'd be nice to be able to set the attributes via XML directly -
but the imageview subclass should be enough for my needs.
Christopher L. Mailloux
Software Engineering Student,
Florida Gulf Coast University
On Wed, Jun 27, 2018 at 2:23 AM, Alexey Derbyshev<EMAIL_ADDRESS>wrote:

@maillouxc https://github.com/maillouxc there's PlayIconView class,
which is ImageView subclass, I can add xml attrs today, so you can use it
in your xml layouts, does it work for you?
Or you need to actually specify all the settings somewhere in the
/res/drawable? In this case it's a very limited thing
https://stackoverflow.com/questions/9019044/create-a-custom-drawable-and-use-it-in-xml,
working only within your application-package and it starts from 24 API level
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alxrm/youtube-play-icon/issues/2#issuecomment-400556712,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL5cApVXFad4IWeklYaTrXVpuRrm7i8Dks5uAyT_gaJpZM4U45YF
.


Inter Tight is missing

Inter Tight font is missing.
https://fonts.google.com/specimen/Inter+Tight

Hi @JSBmanD, thanks for your patience here - happy to report that the font is now available with https://github.com/material-foundation/google-fonts-flutter/pull/278.


fix: Disable possibility of vault creation with chain name or an url

Target branch not 'develop' @pstachel


fix(docker/falco): trust latest GPG key

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area build
/area CI
What this PR does / why we need it:
This PR fixes the Dockerfile we use for building the falcosecurity/falco image by trusting the latest GPG organization key used to sign packages available at https://falco.org/repo/falcosecurity-packages.asc.
This is supposed to fix the current CI issues we have due to the GPG key currently being rotated.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
fix(docker/falco): trust latest GPG key

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docker/OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.34.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docker/OWNERS [FedeDP,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 37a7f5f9e3984546e5a2368604cd6ea651aacf44

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

docker/OWNERS [FedeDP,jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Follow standby redirects

In Marathon 1.7.x, Marathon will be sending 301 redirect responses when requesting /v2/events from a non-leader. Marathon-lb needs to be updated to follow these redirects.

@timcharper I can send a PR for this. Can you link me to a relevant Marathon PR or commit? I tried looking but I couldn't find any!

@timcharper NVM, found it.
Original Marathon JIRA card → https://jira.mesosphere.com/projects/MARATHON/issues/MARATHON-7178
Feature branch → https://github.com/mesosphere/marathon/compare/inc/events-redirect

@timcharper Also, FYI, the code in your branch returns a 302, not a 301.

In Marathon 1.7.x, Marathon will be sending 301

@paambaati Thanks for the clarification!


Decompiler does not work.

I set it up in VSCode "omnisharp.enableDecompilationSupport" Is true.
I created a new Web API project for. Net core on the MacOS platform, and then I started to try whether decompiling works.
In the end, I still can't see the source code part. The method returned is empty or only "throw null".

This is currently a limitation in ILSpy and not a bug in OmniSharp. The ref and implementation assemblies are not resolved automatically, in this case the decompilation happens against Microsoft.AspNetCore.App.Ref instead of the implementation assembly.
You can observe the same behavior in Visual Studio as well. When it is fixed there, we will inherit the fix.

@filipw can you add a reference to the ILSpy bug you mention here? I tried to search they repo for it but didn't find anything. Just for reference and other people that looking for that feature and may wish to follow.

See https://github.com/dotnet/roslyn/issues/24349 for more background.
The limitation is that at design time we operate on reference assemblies instead of implementation assemblies.

Sorry to dredge up an old issue but the issue was resolved ~8 months ago in https://github.com/dotnet/roslyn/pull/62406 and opening the project in Visual Studio the feature seems to work quite well. Is it likely we'll ever see a fix in omnisharp or is it too much work to implement?
Thank you for all of your hard work!


SVG loses quality in latest version

This is the first time I've ever submitted a GitHub issue, please let me know if I am out of line in any way making this post lol. Anyways, I am lazy and have been using 1.8.22 up until today and an SVG I had in a drawing became incredibly blurry at the same zoom I had it at in 1.8.22 when it looked perfect. For now I've just reverted back to 1.8.22 and the issue is resolved. I honestly would not even know where to begin looking to solve this issue for the latest release, but I thought maybe you'd like it brought up. Maybe I'm doing something wrong, but I haven't changed anything other than updating plugins and I didn't have to turn off any others besides Excalidraw to fix the issue. Great plugin, thanks for your hard work!

@Gazebeaux you are probably referring to some third party plugin which uses Excalidraw ?

@zsviczian I presume obsidian?

Oh my lord, can't believe I forgot to mention that. I think I even remember that there's a separate github page for the Obsidian plugin and I should have posted this there.

Yep, there's https://github.com/zsviczian/obsidian-excalidraw-plugin/issues, unless it turns out it's really a problem in the excalidraw library itself!

closing this as its related to Obsidian, feel free to reopen if this happens in Excalidraw as well


Issue with latest use-package?

Here's a couple declarations that used to work but no longer do, each with corresponding backtrace:
(use-package no-littering
  :demand t
  :config
  (savehist-mode 1)
  (add-to-list 'savehist-additional-variables 'kill-ring)
  (save-place-mode 1)
  (setq auto-save-file-name-transforms
        `((".*" ,(no-littering-expand-var-file-name "auto-save/") t))))

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("^.*/\\(.+\\)\\.git$" nil)
  straight-vc-git-local-repo-name((:package "t" :type git))
  apply(straight-vc-git-local-repo-name (:package "t" :type git))
  straight-vc(local-repo-name git (:package "t" :type git))
  straight-vc-local-repo-name((:package "t" :type git))
  straight--convert-recipe((t) nil)
  straight-use-package((t) #f(compiled-function (package available) #<bytecode 0xfbc6e5>))
  straight-use-package-ensure-function(no-littering (t) (:demand t))
  eval-buffer(#<buffer  *load*> nil "/home/diego/.emacs.d/init.el" nil t)  ; Reading at buffer position 4592
  load-with-code-conversion("/home/diego/.emacs.d/init.el" "/home/diego/.emacs.d/init.el" t t)
  load("/home/diego/.emacs.d/init" t t)
  #f(compiled-function () #<bytecode 0x260ad7>)()
  command-line()
  normal-top-level()

(use-package exec-path-from-shell
  :defer 5
  :config
  (setq exec-path-from-shell-check-startup-files nil)
  (exec-path-from-shell-initialize))

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("^.*/\\(.+\\)\\.git$" nil)
  straight-vc-git-local-repo-name((:package "t" :type git))
  apply(straight-vc-git-local-repo-name (:package "t" :type git))
  straight-vc(local-repo-name git (:package "t" :type git))
  straight-vc-local-repo-name((:package "t" :type git))
  straight--convert-recipe((t) nil)
  straight-use-package((t) #f(compiled-function (package available) #<bytecode 0x13a8235>))
  straight-use-package-ensure-function(exec-path-from-shell (t) nil)
  eval-buffer(#<buffer  *load*> nil "/home/diego/.emacs.d/init.el" nil t)  ; Reading at buffer position 5042
  load-with-code-conversion("/home/diego/.emacs.d/init.el" "/home/diego/.emacs.d/init.el" t t)
  load("/home/diego/.emacs.d/init" t t)
  #f(compiled-function () #<bytecode 0x260ad7>)()
  command-line()
  normal-top-level()

This particular issue seems to start here: https://github.com/jwiegley/use-package/commit/a0154a9259d41a6f11aaed1d40df082a45ba9d43, but the latest commit that actually works smoothly is https://github.com/jwiegley/use-package/commit/4f483b6f5171819779cbc8836feeacacfef5ed55

See https://github.com/jwiegley/use-package/pull/552.

Discussion has since moved to https://github.com/jwiegley/use-package/pull/584.

@dieggsy I tested the two examples you gave, and they work with the latest version of use-package and
(setq straight-use-package-by-default t)

Couple things:

This variable name seems unintuitive, maybe straight-use-package-install-by-default?
 I (cautiously) think everything is running smoothly now. Thanks!

@dieggsy

This variable name seems unintuitive, maybe straight-use-package-install-by-default?

The reason I have shied away from mentioning install anywhere is that installation may not be required, and really what is usually happening is that the package is getting added to the load-path and its autoloads are being evaluated. If other people agree though, then I'll change the variable name.


Show image dimensions

It would be nice to see image dimensions when I open image in VSCode. Atom shows that information in status bar.

In the native browser hower I am now showing the image dimensions. Thats a good start for this feature 👍

Verification: we show image dimensions and file size (latter for all binary files) in the right corner of the status bar.

Thank you guys


There should be a recommended work flow for getting and installing the Depth Engine.

We need to add some documentation for this.

Our recent packing additions going a long way, but we should still document how to get the depth engine when building privately.


Support for passing through a jump server or bastion node

I'd like use this code to connect to a server node01 through a bastion node or a jump server (login).  Currently, I can use cygwin and ssh config files to get through login to node01, but I'm trying to find a way if your code supports a similar outcome. Ultimately, I'd like to use a YubiKey to access node01 while jumping through login.
Command to access node01 through login: ssh -F config-ssh node01
Response: Yubikey for 'healykys':
config-ssh:
Host *
User healykys
#Public
Host login
Hostname 12.345.67.890
IdentityFile ./login
Host node01
Hostname 21.543.76.908
IdentityFile  ./node
ProxyCommand ssh -F config-ssh login -W %h:%p
Formatted image of config-ssh below:

*One caveat is that I'm trying to use a Yubikey as well on node01. This relates back to a different response you had with regards to an interactive password.

Hi @healykys. I'm unfamiliar with Yubikey, but generally the way I use jump hosts is to SSH forward port 22 of the protected server via a plain SSH connection to the jumpbox.
ssh jumpbox.somedomain.com -L 2201:dangerbox.local.com

Now dangerbox's SSH server is exposed on localhost:2201, and you can start up win-sshfs pointing to it.
Regarding keyboard interactive auth, you might still run into issues there. If it doesn't accept a public key or non-interactive auth, and the keyboard-interactive auth prompt doesn't match the hardcoded "Password:" thing here, it's probably not going to work without tweaking.

@masaeedu  awesome. I'll dig farther into the command you sent. That should hopefully get me farther into what I need.
Yubikey is just a 2-form authentication method (https://en.wikipedia.org/wiki/YubiKey). It's more related to the password and interactive keyboard side of the house here. I suspect I'll need to tweak it a little bit to get the yubikey to work.

Going to close this assuming you were able to get whatever you needed working using SSH forwarding; please comment if there's anything that needs to be added to support the usecase.


stop working

i tried to install tensorflow in raspberry pi 3, but when build parameter" sudo bazel build --config ...." the process stop working while process on 4233/8000s.
what should i do?
thank you

@nafitriaulia
There are a few things I have to ask you a question.
Please answer all questions.
Otherwise I can not solve it.

Do you have a reason not to use ".whl"?
The version you are trying to build is "Tensorflow v1.11.0"? Or is it "Tensorflow v1.12.0"?
You need to extend the SWAP area to 2 GB, did you do it?

$ sudo nano /etc/dphys-swapfile
CONF_SWAPSIZE=2048

$ sudo /etc/init.d/dphys-swapfile restart swapon -s

What did you specify for the parameters in the "./configure" script?
Can you post the full error message because there are too few information you provided?

@PINTO0309
i followed every single instruction in this post

I use .whl exactly like this site. i use tensorflow-1.11.0-cp35-cp35m-linux_armv7l.whl https://github.com/PINTO0309/Tensorflow-bin/raw/master/tensorflow-1.11.0-cp35-cp35m-linux_armv7l_jemalloc.whl

it is tensorflow-1.11.0

but i have 22gb available sd card. i use 32gb sd card

Please specify the location of python. [Default is /usr/bin/python]:

Found possible Python library paths:
/usr/local/lib/python2.7/dist-packages
/usr/local/lib
/home/pi/tensorflow/tensorflow/contrib/lite/tools/make/gen/rpi_armv7l/lib
/usr/lib/python2.7/dist-packages
/opt/movidius/caffe/python
Please input the desired Python library path to use.  Default is [/usr/local/lib/python2.7/dist-packages]
Do you wish to build TensorFlow with XLA JIT support? [y/N]: n
No XLA JIT support will be enabled for TensorFlow.
Do you wish to build TensorFlow with OpenCL SYCL support? [y/N]: n
No OpenCL SYCL support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: n
No CUDA support will be enabled for TensorFlow.
Do you wish to download a fresh release of clang? (Experimental) [y/N]: n
Clang will not be downloaded.
Do you wish to build TensorFlow with MPI support? [y/N]: n
No MPI support will be enabled for TensorFlow.
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -march=native]:
Would you like to interactively configure ./WORKSPACE for Android builds? [y/N]: n

there's no error message because my raspberry pi 3 stop working anything. it looks like "lag" but can not do anything, even moving the pointer mouse. so i should unplug the power cable and plug in again to restart the raspberry pi

@nafitriaulia

I use .whl exactly like this site. i use tensorflow-1.11.0-cp35-cp35m-linux_armv7l.whl

After executing the following command, installation of "Tensorflow v1.11.0" and "TensorflowLite v1.11.0 " has already been completed.
You do not need to build Tensorflow.
$ sudo apt-get install python-pip python3-pip python3-scipy libhdf5-dev
$ sudo apt-get install -y openmpi-bin libopenmpi-dev
$ sudo pip3 uninstall tensorflow
$ wget -O tensorflow-1.11.0-cp35-cp35m-linux_armv7l.whl https://github.com/PINTO0309/Tensorflow-bin/raw/master/tensorflow-1.11.0-cp35-cp35m-linux_armv7l_jemalloc.whl
$ sudo pip3 install tensorflow-1.11.0-cp35-cp35m-linux_armv7l.whl

but i have 22gb available sd card. i use 32gb sd card

The extension of the SWAP area must be set to eliminate RAM shortage.
It is necessary to allocate the SWAP area separately from the whole size of the SD card.
About 3 GB of RAM is the minimum required to compile Tensorflow, but RaspberryPi's RAM has only 1 GB.
It is a move to evacuate the portion which can not fit in RAM to SDCard.

there's no error message because my raspberry pi 3 stop working anything. it looks like "lag" but can not do anything, even moving the pointer mouse. so i should unplug the power cable and plug in again to restart the raspberry pi

When SSH is used, it hangs up frequently in the middle of processing.
It is recommended to connect the RaspberryPi directly to the HDMI display.
When I was using SSH, I was repeating the same phenomenon as you.
SSH hangs up at high load.

@PINTO0309
thank you for your response.
oh i think i should build parameter also after do this step "sudo pip3 install tensorflow-1.11.0-cp35-cp35m-linux_armv7l.whl"
btw do you know solution on my issue? why did i still fail when execute tensorflow lite?
error message is
Traceback (most recent call last):
File "tflitevideo.py", line 26, in
interpreter = tf.contrib.lite.Interpreter(model_path='quantized_model_cityscapesv3_2.tflite')
File "/usr/local/lib/python3.5/dist-packages/tensorflow/contrib/lite/python/interpreter.py", line 53, in init
model_path))
ValueError: Op builtin_code out or range: 97. Are you using old TFLite binary with newer model?Registration failed.

@nafitriaulia

Are you using old TFLite binary with newer model?

Probably this error message represents the opposite meaning.
Please try to regenerate the .tflite file from the .pb file using toco of v1.11.0.

@PINTO0309
Ok i will try. thank you for your advice
can i ask another thing?
I used tensorflow for object segmentation with video input. But raspberry stop running the program around 2 until 4 minutes. What do you think about it?  is it raspberry's fault or tensorflow's fault?
My program successfully running on my PC untill the end of video.
Thank you

@nafitriaulia
I do not know the program you wrote at all, so I can not answer.
Rather than discuss here, posting a question with StackOverflow can clarify the solution.

Since two weeks have passed since the last reply, I will close the issue.


Add new contributors resource type

Introduces a new YAML resource type specs.openrewrite.org/v1beta/contributors which contains information regarding recipe contributors. These resources get loaded through the ClasspathScanningLoader and are used to augment the RecipeDescriptors which get created for declarative and imperative recipes.

@sambsnyd Some notes regarding the implementation:

At the moment the ClasspathScanningLoader must be used to get recipe contributor information. The YamlResourceLoader also implements the ResourceLoader interface, but since it only processes a single resource at the time and we will typically have a separate resource for the contributors data (containing nothing else), I don't see that it makes sense to implement this for YamlResourceLoader. I.e. YamlResourceLoader#listRecipeDescriptors() will always return recipe descriptors without contributor data.
When Recipe#getDescriptor() is used, the returned descriptor currently also doesn't contain any contributor data.
The ClasspathScanningLoader implementation was changed to first scan YAML files, so that the contributor data (loaded from YAML) is available when processing the Recipe classes.
The resource type is now specs.openrewrite.org/v1beta/contributors. But please let me know if we should switch to authors as you documented it in openrewrite/rewrite-build-gradle-plugin#5.

Thanks for this, Knut. I have added this functionality in this commit.


yaml.constructor.ConstructorError: could not determine a constructor for the tag

I am trying to run the demo and run into the following issue on my Ubuntu 16.04 machine.
Called with args:
Namespace(background_name='data/cache/backgrounds.pkl', cad_name='data/LOV/models.txt', cfg_file='experiments/cfgs/lov_color_2d.yml', gpu_id=0, imdb_name='lov_keyframe', kfusion=False, model='data/demo_models/vgg16_fcn_color_single_frame_2d_pose_add_lov_iter_160000.ckpt', network_name='vgg16_convs', pose_name='data/LOV/poses.txt', pretrained_model=None, rig_name='data/LOV/camera.json', wait=True)
Traceback (most recent call last):
File "./tools/demo.py", line 77, in
cfg_from_file(args.cfg_file)
File "/home/nivedithak/Downloads/PoseCNN-master/tools/../lib/fcn/config.py", line 303, in cfg_from_file
yaml_cfg = edict(yaml.load(f))
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/init.py", line 74, in load
return loader.get_single_data()
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/constructor.py", line 39, in get_single_data
return self.construct_document(node)
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/constructor.py", line 48, in construct_document
for dummy in generator:
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/constructor.py", line 398, in construct_yaml_map
value = self.construct_mapping(node)
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/constructor.py", line 208, in construct_mapping
return BaseConstructor.construct_mapping(self, node, deep=deep)
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/constructor.py", line 133, in construct_mapping
value = self.construct_object(value_node, deep=deep)
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/constructor.py", line 88, in construct_object
data = constructor(self, node)
File "/home/nivedithak/Downloads/PoseCNN-master/PYTHON_27/local/lib/python2.7/site-packages/yaml/constructor.py", line 414, in construct_undefined
node.start_mark)
yaml.constructor.ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/tuple'
in "experiments/cfgs/lov_color_2d.yml", line 12, column 16
I don't see any unusual characters in that line and it is using the python specific tag !!python/tuple.

Which version of YAML are you using ? I downgraded PyYAML from 4.1 to 3.12 typing
pip install PyYAML==3.12
and it worked well.

That totally did it! I had version 4.1 too.


Gemfile refactorings

In preparation for adding Oculus crawler logic to versioneye

Simplify Gemfile
Use Version.rb for version definition
Remove Gemfile.lock

These are all just suggestions, I understand if you don't want any of those changes.
Maybe we can also schedule a call so I can clarify why I suggest these changes and can get some more insight into the Versioneye system to integrate Oculus.

Hey @stefan-kolb. Many Thanks for your pull request. Do you know the jeweler project? We are using it to manage this Gem project. If I create a new patch release I use this script for example: https://github.com/versioneye/versioneye-core/blob/master/scripts/patch.sh. So all the entries in the gemspec are auto generated.
I thought about skipping the Gemfile.lock and at first it was OK for me. But now I would like to keep it because I monitor the Gemfile.lock with VersionEye and if there are some security vulnerabilities in the transitive dependencies I would like to know about it.
What is the value of moving the depdencies from the Gemfile to the gemspec? At least for right now I would like to keep them in the Gemfile because I can monitor the Gemfile with VersionEye. Right now we don't have support to monitor gemspec files. That will come in future.

Hi @reiz,
I know the jeweler project. I get the idea why you use it, but in my opinion it adds unecessary overhead and it is easy to just use the build in Gem functionality of bundler or just gem build . In your case the gemspec is overly big including all files and need to be regenerated all the time. In my case you don't need to update anything except the version number for a new release (which is typically done inside this version.rb which is not used at the moment). This is maybe the only drawback as you can do this automatically at the moment. However, jeweler is not the real issue here, we could keep this the way it is.
A bigger problem is the Gemfile.lock and the overly strict dependencies. For a rationale on why I moved the dependencies to the gemspec and removed the Lockfile, see http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/.
Problems here are the strict dependencies that may force conflicts in other application setups and the Lockfile which makes it for example impossible to run this Gem on Windows.
Actually, the project is no real Gem at the moment. The question is if you want to make it a Gem or not.
Again, we can set up a call so I can describe the things I had in mind more easily. Just drop me a mail stefan.kolb(at)uni-bamberg.de.

For parsing gemspecs you could just use https://github.com/gemnasium/gemnasium-parser from your competitor :wink: ?!

Hi @stefan-kolb, I just finished reading the article. Now it makes sense to me :)

@stefan-kolb Integrating the gemnasium parser would be another thread. You wanna work on it?

@reiz Maybe at a later time. First priority for me would be to integrate the crawling logic for runtime languages as I want to use it inside https://paasfinder.org and deprecate my old crawler.

Hey @stefan-kolb. All right. That's OK for me.
Since I merged the pull request I can't start the ruby console anymore.
rake console --trace
W, [2016-07-11T17:35:17.213465 #80648]  WARN -- : Creating scope :parents. Overwriting existing method Project.parents.
initialize Settings
load config/settings.json
rake aborted!
Don't know how to build task 'console' (see --tasks)
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/task_manager.rb:71:in `[]'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:151:in `invoke_task'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:108:in `block (2 levels) in top_level'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:108:in `each'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:108:in `block in top_level'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:117:in `run_with_threads'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:102:in `top_level'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:80:in `block in run'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:178:in `standard_exception_handling'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/lib/rake/application.rb:77:in `run'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/gems/rake-11.2.2/exe/rake:27:in `<top (required)>'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/bin/rake:23:in `load'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/bin/rake:23:in `<main>'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/bin/ruby_executable_hooks:15:in `eval'
/Users/reiz/.rvm/gems/ruby-2.3.0@veye-core/bin/ruby_executable_hooks:15:in `<main>'

Any thoughts on this?
I have another branch where I can do hot fixes right now. In the long run I want to make this project to a real Gem project that's why I will go through this changes.

Probably the console task came from jeweler, so it is gone right now. Maybe we have to add one manually if you need it: https://simonecarletti.com/blog/2009/09/rake-console/

@stefan-kolb The tests on CircleCI are all green after the merge. But somehow the console task disappeared from rake. Maybe it was part of jeweler?

@stefan-kolb Yep, that worked. Thanks for your help.


Initial commit with documentation

Replacing all occurrences of Hoodie  with Hudi . Process employed to perform this change :

Goto find in the project and perform a search on Hoodie  and replace with Hudi .
Edit couple of other places (in titles of the pages that ended with the Hoodie keyword) and perform the same replacement manually.

Hudi /Hoodie presently names all it's packages, metadata and other dataset content with hoodie. This requires a larger effort and involves migration of datasets (if done) which will have to be discussed. Hence, all such references have been left unchanged as Hoodie.

Goto find in the project and perform a search on Hoodie and replace with Hudi .
Can you please list out the specific Hoodie references have been touched/untouched? @n3nash

@n3nash any thoughts on my comments above?

I missed that you have a space at the end. That should mostly work..
Once we get one more review, we can merge?


add dark mode with toggle and system preference

I wanted to be able to apply dark mode. this automatically applies dark mode based on the user's system preference, and adds a toggle to switch between light and dark on the settings tab.
this is still in progress, but I'd appreciate any early feedback. what I plan to do still:

[ ] fix CssBaseline import in OnnxWeb.tsx to match other imports
[ ] move logic for checking the user's system preference and the current theme out of OnnxWeb.tsx and into utils.ts
[ ] add a label to light/dark mode toggle
[ ] improve logic for light/dark mode toggle based on system preference

what I'd like to do at some point, but may do as a separate PR:

[ ] add custom theming/colors

Nice, this looks pretty good.
I see two minor issues, one of which you've already noted:

mode: state.theme as PaletteMode doesn't check to make sure that state.theme is really valid, and mui will throw an error and not load the app if that is not a valid theme name
if the user has not picked a theme yet, the toggle will not reflect their system settings and will always start with the light theme: if (state.theme === 'light') ...

For the import, I think you can import directly from the mui package, import { CssBaseline } from '@mui/material';.

Hi, you will probably need to rebase this in the aftermath of https://github.com/ssube/onnx-web/pull/208 (i18n)


RDART-964: Add PrivacyInfo.xcprivacy for iOS and macOS

Adds privacy manifests to our iOS and macOS plugins.
While we only need to update the plugins listed here for now (ie RealmSwift), the wording of the page:

The following are commonly used SDKs in apps on the App Store

suggests that the list of things for which this is required is just an arbitrary cutoff rather than a conceptual distinction, so it seems safest to just assume the list will grow over time and do this for the realm flutter package as well. To be honest I don't trust that Apple got the list right.
Note that we are following the standard Flutter / Cocoapods implementation which has the following caveat:

The large caveat is that we do not currently know if this actually works. This is the method of inclusion that seems to be the consensus among people using Cocoapods, as bundling it directly as a resource causes problems for clients who do not use use_frameworks. (In theory it seems like a manifest would not actually be required in that case since there is no framework, but it has the potential to actually stomp top-level resources.) Hopefully the automated analysis that Apple will eventually roll out will tolerate the file being bundled in a resource bundle in the framework rather than a top-level manifest file. If not, however, it's not clear how Cocoapods can be supported, so we can adopt this common approach for now under the assumption that eventually tooling will adapt to the reality of the ecosystem, and revisit the exact bundling later if necessary.

Source: https://github.com/flutter/packages/commit/c5349bc9a5be1cbef9c13571d9d6d2b506240b20
The flutter repo is tracking the approach here.
As to why the we (and the flutter team) add _privacy to the resource bundle id see
https://github.com/flutter/packages/pull/5846#issuecomment-1881788602
The actual privacy manifest files are lifted from the realm-swift repo.
I'll quote the commit message, as to. why it looks as it does:

Since we don't include the analytics code in builds for the app store, the only
thing we need to declare is that we call fstat() on files in the app container,
which core uses internally to check the size of Realm files. This is assuming
that if the app logs into Atlas that's something that the app itself has to
declare rather than us, as we don't automatically talk to the server on our own
behalf.

The CocoaPods bundling might not actually work. This is the approach that most
of the SDKs on the mandatory privacy manifest list are taking, but since Apple
isn't actually checking the manifests yet no one knows if they'll accept this
fairly weird way of bundling the xcprivacy file. The less weird way breaks
building pods as non-framework static libraries.

Fixes: #1551
Fixes: #1629
Fixes: #1630

Looks good, should we symlink those manifests or duplicating them is fine?

I would prefer not, for now.


fix spelling avg_excution_price

Found this when writing my own auth-tests.
Fixes

Minor spelling potentially causing crash.

Tests

Don't believe it makes sense to test this since you'd need to make an actual order.

A test would be preferable (mock the endpoint), but for this kind of fix (thanks!), I'll accept it without a test.


Master.controller is missing in Demo

In both http://veui5infra.dhcp.wdf.sap.corp:8080/demokit/#/sample/sap.ui.core.sample.RoutingMasterDetail/code/routingApp%252Fview%252FMaster.view.xml and https://sapui5.hana.ondemand.com/explored.html#/sample/sap.ui.core.sample.RoutingMasterDetail/code/routingApp%252Fview%252FMaster.view.xml , there is a Master.view.xml which controller is "sap.ui.core.sample.RoutingMasterDetail.routingApp.controller.Master", but this file is missing.

You're right, download configuration for that sample is missing the Master.controller.js. You can however directly view it here until the issue has been fixed: https://github.com/SAP/openui5/blob/master/src/sap.ui.core/test/sap/ui/core/demokit/sample/RoutingMasterDetail/routingApp/controller/Master.controller.js

Also missing: mock data file routingApp/controller/data.json.


CUDA mGRID roadmap

Starting next release, CUDA backend will have special execution mode: some ops can be combined, and multiple ops applied to the same data. Something between SIMD and MIMD technically. Not a pure SIMD, not a pure MIMD.
Roadmap:

PairwiseTransform followed by Scalar. That's the most important combination, average 20% of all  op pairs, it'll be included in 0.6.0
Scalar followed by Reduce. That's not too popular combination, but as prototype might be interesting for 0.6.0
Scalar/Transform, Transform/Pairwise, Transform/Broadcast, Transform/Reduce, etc. These combinations will be included only as EXPERIMENTAL in 0.6.0 and will require manual libnd4j compilation, due to extended compile time for these ops. In future they will probably be included in main codebase.

MIMD with DP:
New execution model will make possible in-order and out-of-order execution with DynamicParallelism. Obviously, this part of code will be available only for cc3.5+ and won't be available for AWS. However, DP won't be available in 0.6.0 probably, and will be announced in subsequent release.

We're also going to move away from CUDA synchronization as mush as possible.

I'm going to rebuild op invocation mechanics for CUDA.
Initial prototype will be made for mGRID meta ops, and later it will be propagated to other ops.
Basic idea is simple as usually: let's remove op selection outside of kernels themself. 1 kernel == 1 op.
I suspect that it'll be just faster. 500-1000 nanos per call.

Looks like due to MSVC preprocessor limitations, time to introduce m4 for kernels/invokers construction

As part of mGRID -> GRID improvement, we're also going to address GC pauses: initial version of automated local scope clearance should be introduced. So this should bring us flat 2 improvements:

Less GPU memory pressure via enforced caching, since cache workflow will become more "atomic", with respect to scopes.
Our reliance on JVM GC will be greatly reduced, due to known-in-advance scopes for temporary allocations.

https://github.com/deeplearning4j/nd4j/pull/1731


Updating plan baseline for drill4449.q

Hey Robert, I've run tests to confirm that this change runs successfully. Please take a look.

Khurram, if you can take a look - it would be great.

@Agirish  Changes look good. LGTM.


Switch from deprecated TIME_MINUTES to UnitOfTime.MINUTES

I've noticed the following warning in HASS:
2024-01-15 22:14:02.684 WARNING (MainThread) [homeassistant.const] TIME_MINUTES was used from nhc2, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTime.MINUTES instead, please create a bug report at https://github.com/joleys/niko-home-control-II/issues                                                                                2024-01-15 22:14:02.696 WARNING (MainThread) [homeassistant.const] TIME_MINUTES was used from nhc2, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTime.MINUTES instead, please create a bug report at https://github.com/joleys/niko-home-control-II/issues                                                                                2024-01-15 22:14:02.705 WARNING (MainThread) [homeassistant.const] TIME_MINUTES was used from nhc2, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTime.MINUTES instead, please create a bug report at https://github.com/joleys/niko-home-control-II/issues

Changes made to switch from the "in the near future" deprecated TIME_MINUTES to UnitOfTime.MINUTES.
In order to help out on this nice component, I hope this PR brings a nice contribution.

@xirixiz Thx! I am working on bringing the Integration up to date with v1.3 of the documentation in https://github.com/joleys/niko-home-control-II/pull/110
Which also includes this fix: https://github.com/joleys/niko-home-control-II/pull/110/commits/87b74343d421bc6cc3f5375e05eabd8929557dd4

I also maintain a component myself. If you ever need help, just send me a message.
Always willing to do some contribution as I know it can be challanging sometimes in maintaining these things together with a personal life 😄

... ah, I can check it here to help out  I see: https://github.com/joleys/niko-home-control-II/pull/110
Great!


T74721 : Imported glTF Files Are Having Double Vertices

https://developer.blender.org/T74721
@emackey @donmccurdy Can you please confirm this is the correct behavior, because of UVMap we need to duplicate the vertex?

Done


Only works for direct references, Not transitive?

I've tried to incorporate this in a couple projects where we use Moq (thankfully 4.18 and lower right now) and it doesn't seem to trigger even if Moq is updated to the offending version(s).
The only time i got it to trigger and fail the build was when i delibrately added a direct reference to Devlooped.SponsorLink to a project.

I tried it locally against 4.20.0, I saw the SponsorLink dependency (and its subsquent nag) but the analyzer didn't trigger. I tried debugging it, and indeed the reference is not in ctx.Compliation.ReferencedAssemblyNames. I'm not sure if that's expected or not, though.


How to get row highlighting on hoverable tables

Looking at the example of a hoverable table on here: http://materializecss.com/table.html
When I use the class="hoverable" on my table, I only get the drop-shadow around the border of the whole table, and not the grey highlighting on each of the individual rows as the mouse hovers over them.
Is this a bug, or am I supposed to do something else to get the row highlighting?

Actually .. I've narrowed the problem down a little further. The rows do not highlight when I populate the table with javascript, but if I already have the data hard-coded in html, then I get the highlighting.
If this is not a bug, then please let me know how I can work around this issue.

I don't like the drop shadow around the table so I used simple row highlighting
tr:hover { background: #f5f5f5; }

This actually is a bug. The hoverable class is used twice.
Once for the card hover effect which generates the shadow around the table in this case
and second for row highlighting in tables. If you apply this class now, it will apply both effects on tables which is not intended i guess.

This is actually already fixed: 7866e719b60b7f95645b8eed9b26e8331c54d006
Hoverable table rows will be available using the "highlight" class on the the table after the next update.
I guess you could close this issue as there are so many of them and they can't keep up anyways :wink:

I'm still concerned with the fact that I don't get the row highlighting on rows I add with javascript. For example, I have a table that I have roughly set up in html, and then I populate that table with more data that I get from a $.get request. But I'll raise that in a separate issue if it's not fixed by the update :)

@brandonSc  Did you ever put in an issue for the rows not being highlighted when added with javascript?
Thanks,
Mike