armv7hf build errors

Hey
I'm trying to build my Golang app for armv7hf (GOARM=7, GO_ARCH=arm) but I got this errors.
Have you seen a way or idea to fix the problem, i thinks its releated to 32bit because armv7hf is 32Bit?
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/codec_context_flag.go:28:51: constant<PHONE_NUMBER> overflows CodecContextFlag
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/channel_layout.go:96:77: cannot use cUlong(len(b)) (value of type _Ctype_ulong) as _Ctype_uint value in variable declaration
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/dictionary.go:65:43: cannot use size (variable of type *_Ctype_ulong) as *_Ctype_uint value in variable declaration
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/dictionary.go:71:52: cannot use size (variable of type _Ctype_ulong) as _Ctype_uint value in variable declaration
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/frame.go:106:54: cannot use &linesize[0] (value of type *_Ctype_long) as *_Ctype_int value in variable declaration
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/frame.go:178:94: cannot use cUlong(size) (value of type _Ctype_ulong) as _Ctype_uint value in variable declaration
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/frame_side_data.go:25:11: cannot use d.c.size (variable of type _Ctype_uint) as _Ctype_ulong value in assignment
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/packet.go:91:75: cannot use size (variable of type *_Ctype_ulong) as *_Ctype_uint value in variable declaration
/go/pkg/mod/github.com/asticode/go-astiav@v0.13.1/stream.go:61:75: cannot use size (variable of type *_Ctype_ulong) as *_Ctype_uint value in variable declaration

when building for aarch64 i have no errors.
FFmpeg version n5.1.2
Golang versions tested : 1.22, 1.20.14
Thanks

For channel layout for example we could do something like this
channel_layout.go:96:77
// Directly use C.size_t for the size parameter to ensure compatibility.
C.av_channel_layout_describe(l.c, (*C.char)(unsafe.Pointer(&b[0])), C.size_t(len(b)))

For channel layout for example we could do something like this

Great idea! 💪
FYI I've pushed in master a commit that uses C.size_t and C.ptrdiff_t wherever it's better for compatibility purposes.
I've also pushed a dockerfile to test on armv7hf and (even though it took me the whole day yesterday to build the image 😵) I'll take a look to the last remaining error (the constant overflow) 👍
You should rebase your extradata PR to get this change as you'll need to use bytesFromC 👍

Thank you immensely for the prompt update and your incredible efforts! 💪 The enhancements for increased compatibility are fantastic and a major step forward. It’s also exciting to hear that we have the capability to conduct tests on armv7hf.
As soon as you've addressed the overflow issue, I'd be delighted to run tests on an actual armv7hf device. 😉
I've completed the rebase and reviewed the changes as advised.

FYI I've fixed all compilation errors in the armv7hf Dockerfile I've added and I've pushed all fixes on master.
However tests related to opening a file with a FormatContext are failing (it doesn't manage to find the proper codec parameters 🤔) and I can't figure out why.
Could you run tests on you armv7hf device and let me know whether everything works as expected?

Cool. I will Test it and let u know.. thanks

However tests related to opening a file with a FormatContext are failing (it doesn't manage to find the proper codec parameters 🤔) and I can't figure out why.

After further investigating it seems to be related to the way ffmpeg has been built more than issues in the code. For instance libpng is not present in the arm image I'm using (and maybe not present in arm by default) and needs to be built manually/enabled properly when building ffmpeg.

OK thanks for Info, i do custom builds with disable everthing. An enable what i need. Looks like that person build ffmpeg just remove it maybe, for size or other issues.


Set default ruby warning level to -W1

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

See https://github.com/Homebrew/brew/issues/10593
Increase the default warning level to -W1. I've played with this a little locally, and I don't see any issues so far. My understanding is that -W1 means that the only warnings that will be shown are those thrown using the #warn method. We don't use this method anywhere in Homebrew (it would likely be a bug if we did since it was being silenced), so the only potential warnings that could be shown are from other gems (e.g. rubocop or rspec). I've looked through the main commands that I think might have new warnings (including style, man, prof, bump, tests) and I don't detect any new warnings (the parser/current warning on brew tests is still present but is not new).
Homebrew developers can still set HOMEBREW_RUBY_WARNINGS to show more or less warnings if desired.

Review period will end on 2021-02-12 at 21:30:38 UTC.

Looks like the tests did catch one warning.

Maybe making code use a stage block (so a chdir block inside a chdir block) will work?

Maybe making code use a stage block (so a chdir block inside a chdir block) will work?

Sorry, not sure where you're talking about. Both cases of chdir involved here are called via stage methods

Basically this code is problematic:
Dir.chdir "a" do
  Dir.chdir "b"
end

This should not be (AFAIK):
Dir.chdir "a" do
  Dir.chdir "b" do
  end
end

So if we can adapt stage to support blocks then we can use a similar system there.

Ah, I see. You're right in that using the nested blocks doesn't throw the warning (which makes sense given what the warning's protecting against, I think). Let me see what I can do.

So if we can adapt stage to support blocks then we can use a similar system there.

This makes sense to me 👍🏻

That seemed to do the trick!

So, making this change brought the parser warnings back...
I've opened https://github.com/jeremyevans/ruby-warning/pull/11 to add some additional functionality to the Warning.ignore method that will (hopefully) make ignoring warnings easier.

Review period ended.

I've added a Warnings module that allows for the use of a block method to temporarily ignore warnings.
For example, to ignore the parser warnings, I use:
require "warnings"

Warnings.ignore :parser_syntax do
  require "rubocop"
end

This also works in the utils/rubocop.rb and test/spec_helper.rb using require_relative "../warnings".
One thing to note: in style.rb, we could replace the system rubocop calls with RuboCop::CLI.new.run to catch some extra things that would only be caught while running within Homebrew (e.g. the warning we discussed elsewhere). I decided not to do that, though, as I think there's value in having the brew rubocop command run the utils/rubocop.rb script, and I think it's better for style rules to be enforced consistently which might not be the case if we do this.


Unable to get server-side rendering to work after upgrading to 0.13.2

Hi,
I'm having trouble figuring out how to get server-side rendering to work after upgrading to React 0.13 and react-router 0.13.2
I first tried something like this:
Router.run(Routes, "/path", function(Handler, matched) {
  res.send("<!doctype html>"+React.renderToString(Handler()));
});

But that gives me the error TypeError: Cannot read property '__reactAutoBindMap' of undefined
Poking around I saw this bug, which hints that I might need to be using createFactory for server-side rendering. But when I try this:
Router.run(Routes, "/path", function(Handler, matched) {
  var fact = React.createFactory(Handler);
  res.send("<!doctype html>"+React.renderToString(fact()));
});

I get the following error: TypeError: Cannot read property 'mountComponent' of undefined
The app I'm trying to render is not a very complex react-router app. The Routes look like this:
<Route name="app" path="/path" handler={App}>
    <DefaultRoute name="dashboard" handler={Dashboard} />
    <Route name="otherPage" handler={OtherPage} />
    <NotFoundRoute name="notFound" handler={NotFound} />
  </Route>

And the App.jsx looks something like this:
var App = React.createClass({

  render: function() {
    return (

        ...

<Link to="dashboard">Dashboard</Link>

<Link to="otherPage">Other Page</Link>

        ...
        <RouteHandler />
        ...

    );
  }

});

Any tips or ideas as to what's going wrong?

Your createFactory snippet should work like that, but I would prefer using React.renderToString(React.createElement(Handler));. I suspect the error you're getting is caused by something else.
Are you using createFactory at other places perhaps? Apparently mixing it with JSX can cause that error, e.g.:
var Component = React.createFactory(require('./component'));

render(){
   return <Component />; // bad
}

To clear things up, those are equivalent:
var Component = React.createClass(..); // or as ES6 class

// 1) JSX
React.renderToString(<Component />);

// 2) createElement (this is also the output of JSX after processing)
React.renderToString(React.createElement(Component));

// 3) createFactory
var fact = React.createFactory(Component);
React.renderToString(fact());

Thanks for clearing things up so quickly! I was able to get React.renderToString(React.createElement(Handler)) working after all. As you suspected, I overlooked using createFactory when building my routes.

Exactly the mistake i made.  I wrapped my jsx component with React.createFactory call as shown below.
var App = React.createFactory(require('./components/app.jsx'));
This is wrong -
right way is
var App = require('./components/app.jsx');


FFV1: remove sar_den test must be 0 if sar_num is 0

Spec is currently not clear and FFmpeg creates such stream
(0/1 if unknown, e.g. with ./ffmpeg -f lavfi -i testsrc -vframes 1 -c:v ffv1 -level 3 -vf setsar=0/2 a.mkv)
FFV1-SLICE-sar_den test description needs to be updated.
Reported by user and detected by me at the same period.

Detected by user in Archivemtica 1.7 too -- is there a way to mitigate this error prior to the next release?

No, it is hardcoded.
Note that in any case such file is a corner case and may be considered as problematic, as the DAR is unknown in that case, the file should be "fixed" even if it is valid technically speaking.
Note: latest snapshot contains the fix, it could be used in Archivematica. Public release next week.

BTW, you need to clear the database, " --force" for each file with CLI (or drop the database), "Database" then "Delete all results from database" in GUI.

Thank you!


Updating how cross-application correlations are tracked

Instead of using a hash of the instrumentation key we now use the appId, matching the .NET sdk.
We also use different headers to match the .NET sdk.

@nizarq Could you please take a look at this and make sure I didn't miss anything important?

This PR is based on the changes made to the .NET sdk. Regarding your points:

I queue up a single request for the appId when a Config is created, and retry only on non-4XX errors every Config.correlationIdRetryInterval (default 30 seconds). Until the request completes successfully, the correlationId will remain undefined, and not block execution at all.
I allow for different endpoints as much as the previous version did: https://github.com/Microsoft/ApplicationInsights-node.js/pull/231/files#diff-7b48e6fce63062fb2711022cca6afa31L28 seemed to hardcode the URL, and I use the same (configurable) base URL to fetch the appId.
I'm not sure what you mean here. Do you mean allowing users to disable cross component correlation?

Thanks Jimmy!

From my understanding of your code any time Config object is created you are initiating  a new network request without checking if request to resolve the same ikey has already completed or is in progress. We should not be doing this unnecessarily.
Configurable base is not enough because users may be using one host name to send data (e.g. Vortex case) and another endpoint to resolve profile. We should expose this as separate configurable option, not derived from base.
To prevent uninitialized x-component dependencies (because of delay in resolution) that ultimately appear as extra nodes on app map, we should provide a way for a user to plug in a simple lookup table of ikey to appid mappings. For the entries provided in this lookup, calling profile endpoint will be unnecessary.

Since you made this change based on my original change. In the last couple of days I've sent these couple of updates to the original change. Please look at them and incorporate them as well. They address some of last remaining issues that Alex is pointing to.
https://github.com/Microsoft/ApplicationInsights-dotnet-server/pull/505
https://github.com/Microsoft/ApplicationInsights-dotnet-server/pull/526

@AlexBulankou

SDK should provide extensibility to specify instant resolution mechanism for customers who either wish to have no extra calls to profile endpoint or wish to always have them resolved, which wouldn't be the case because of requirement (1)

With 400s handled correctly, and ensuring a single call is made per ikey. I think above is a good to have at best. I would rather have customers ask us for this before we give it to them. For almost everyone out there in the wild, they will go against the public breeze endpoint and if breeze is up things work well. If not, we handle that gracefully.

I've updated it to only query once per ikey (per endpoint URL), and to default to a blank correlation id rather than lacking one, but it isn't clear to me exactly how that was supposed to work. @nizarq should we be sending the blank cid-v1: correlation ID on all requests (until we get the actual ID), or should we be checking for blank correlation IDs on inbound requests?
@AlexBulankou if you aren't content with having a single changable base endpoint, how do you want users to specify different endpoints for general telemetry and querying the appId?

@MSLaguana for the different base endpoint for the appid lookup, .NET uses the configuration option "ProfileQueryEndpoint". We can place this in our config object

@OsvaldoRosado How do you propose exposing it? As a parameter when constructing a Client / Config? As a parameter set immediately after constructing one, and we introduce a delay between constructing the Config and firing off the HTTP request? I know that the .NET sdk waits until the appId is needed before firing off a request, but I'd prefer to be more proactive to reduce the number of non-correlated requests if possible.

@MSLaguana  I'm not a big fan of changing the constructors for this, especially since a constructor parameter doesn't exist for the telemetry endpoint, which is far more frequently changed (this endpoint is essentially only necessary to change for internal use). It would also need to be on the Config, Client, and the appInsights.setup method. Introducing a delay seems like a hack but might be the best option if you don't want to resolve until telemetry is generated. You can at least be proactive for changes to it with a custom setter on the property.

If we allow people to change the base URL after we have already started a request, what is the expected behavior? Cancel any pending requests and start again with the new URL? Use the new URL on the next retry after getting an error (including a 4XX error)?
I was thinking more like
appInsights.setup("key").start();
appInsights.getClient().config.profileQueryEndpoint = "http://myCustomEndpoint.com"

and as long as that configuration was done synchronously with the creation of the client then it would be picked up in the request for the appId. We could also allow for environment variables, which might be easier.

Note that you want .client instead of getClient in the above example, otherwise you now have two telemetry clients 😄 But yes, setting the property directly like that is what I have in mind.
I would expect telemetry generated after the URL has changed to no longer use the previously looked up appid. A new appid can be looked up immediately on set through a custom setter. Any pending requests (for the specific client at hand since you can have multiple) can be discarded

@OsvaldoRosado See what you think of my changes to support profileQueryEndpoint. I don't currently support changing its value at an arbitrary time, but if that's a scenario that we want to support then I could.
@KamilSzostak Done.

@MSLaguana I don't think we can get around having to support changing the value at arbitrary times. Anything that determines its configuration asynchronously will need to be able to do this (or refactor their telemetry logic to not import AppInsights until after configuration, since we automatically create a client on import)

@OsvaldoRosado How's this look then?

@nizarq @AlexBulankou What is the expected behavior if the network is out? e.g. we fail to resolve the endpoint? Should we retry in that scenario, or should we give up immediately?

It looks like the node.js SDK was missing the x-ms-request-id header on outbound requests. @nizarq can you also check to see that I've got the semantics of this right in https://github.com/Microsoft/ApplicationInsights-node.js/pull/231/commits/e1d91303a1254e1435db2764688578f3a3ae9a73 ?

@nizarq @MSLaguana my proposed requirement (3) is closely related this PR: https://github.com/Microsoft/ApplicationInsights-dotnet-server/pull/526 So far I'm not sure I understand how this addresses the problem of  initial couple of calls aggregated incorrectly in case they are not resolved, hence my last comment.

I've addressed @OsvaldoRosado's comments, and rebased to clean up the commit history. If you're happy with it, please complete this PR.


Mixed results

Getting mixed results from server
since client is non blocking if you call method1 say "method1" twice you get the fastest response as result for first call
#call1
router.call("method1",msg) # first call taks 1sec
#call2
router.call("method1",msg) # second call taks  less (0.5sec)
the part waiting for results with async will queue  (call1,call2) but response from wrokers will be (call2, call1)
the server will return result2 for call1 and result1 for call2
to reproduce set one method that takes dynamic time to finish call it multiple times the results will be ordered by time of execution not order of calling. no suitable for concurrent tasks (maybe your tests included only sequencial calls of different methods)
in client
async def route(command,__retry=0,**args):
    router = await _get_router()
    msg= {"command":command,**args}
    result = await router.call("process",msg)
    if result:
        if "error" in result:
            raise EnsureBaseError(result['error'])
        elif "result" in result:
            return result['result']
    else :
        # None response, call failed
        if __retry<3:
            logging.info(f"Retry {__retry}")
            return await route(command=command,__retry=__retry+1,**args)
    return result

server
app = ZeroServer(port=5559,encoder=encode ,decoder=decode)
app.register_rpc(process)
app.run(workers)

Interesting. This should not happen. The mapping is done by the router itself. Can you provide the exact script where you are facing this? @kimboox44

I could reproduce the issue and solved here https://github.com/Ananto30/zero/pull/29


Typos in Chapter on GANs [version 2022-04-01]

(Findings due to Aalto Seminar students)
Comments are formatted via LaTeX. The page numbers follow the printed version.

p852, snd paragraph: the generative modelcitations. $\to$ The citations does not give an actual citation
p852, l26: "specified using by deep networks"
p854, l45: Should probably say "if the ratio is 1 everywhere in the support of $q_{\theta}$"
p854, l46: "Since we cannot evaluate..." has a repetition of  "we cannot evaluate"
p859, l42: "Section Section"
p800, l37: "where $\zeta_\phi$ regularized" is missing an "is"
p861 l32: Less of an error and more a minor inconsistency. Reproducing Kernel Hilbert Space is here fully written out, while p859,l35 only gives the abbreviation. Switching the two might be better.
p861, l36: ... vs $\ldots$
p863 l14 \sout{follow}
p864 l46 $\text{argmin min}{\bm{\phi}}L_D(\bm{\phi},\bm{\theta}) \to \text{argmin}{\bm{\phi}} L_D(\bm{\phi},\bm{\theta})$
p865, l34: "Section Section"
p872, l37: subindices error: $G_\phi(E_\xi(x)) = x$ instead of $G_\xi(E_\phi(x)) = x$
p875 l36, "An similar" $\to$ "A similar"

very helpful, thanks!


Bump to version 4.3.0 for release via CD

Next package version for deployment via CD.

@yevdyko I had to resolve conflicts, that's all that changed, FYI. Merging now 🚢🤞🏻!


NTR - primary active transporter activity

Suggested term label:
primary active transporter activity

Definition (free text)
Catalysis of the movement of substances (such as solutes or lipids) from one side of a membrane or membrane leaflet to the other, powered by a primary energy source such as ATP hydrolysis, redox energy or photon energy. [GOC]
(I've modified/generalized the definitions of the existing parent terms of the two children specified below)

Parent term(s)
transporter activity (GO:0005215)
catalytic activity (GO:0003824)

Synonym(s) (please specify, EXACT, BROAD, NARROW or RELATED)
translocase activity [EXACT]

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?
primary active transmembrane transporter activity (GO:0015399)
ATPase-coupled intramembrane lipid transporter activity (GO:0140326)

Cross-references
EC:7.-.-.-

Any other information

'primary active transmembrane transporter activity' (GO:0015399) currently has EC:7.-.-.- xref, but the name & definition of this GO term excludes "ATPase-coupled intramembrane lipid transporter activity" (GO:0140326), which has xref of EC:<IP_ADDRESS>.
So EC:7.-.-.- should be removed from GO:0015399, and added to the proposed term above that groups both the catalytic transmembrane and the catalytic intramembrane transporters.

GO:0015399 and GO:0140326 do not currently have parentage in the 'catalytic activity' branch of the GO. This can be rectified by making them children of the NTR, which itself is proposed to a be a child of 'catalytic activity'.

@kaxelsen Please say if the above make sense to you?

GO:0015399 has part 'some 'catalytic activity'
GO:0140326 'has part' some 'ATP hydrolysis activity'
we cannot use is_a, see https://github.com/geneontology/go-ontology/projects/32

We should document this somewhere, we keep on getting confused about this

What does NTR stand for?

New term request

Thanks for explaining the 'has part' thing (again!) Pascale. I think my problem is that the tools I use for viewing the GO (FlyBase, QuickGO, the go-basic.obo file) don't show that relation, and queries using those tools don't retrieve things via 'has part'....
But I think the NTR (new term request) here still stands to correct the EC:7 xref issue and thus align with the EC translocase class?

Thanks @kaxelsen. Following your comment, the alternative solution here would be to (i) not make the new grouping term, (ii) leave the EC:7 xref on GO:0015399, and (iii) make GO:0140326 a child of GO:0015399.

Sorry @sjm41 I just noticed -
GO:0140326 | ATPase-coupled intramembrane lipid transporter activity is not a transmembrane transport, so we cannot add the relation you propose.

Sorry @sjm41 I just noticed -

@pgaudet

GO:0140326 | ATPase-coupled intramembrane lipid transporter activity is not a transmembrane transport, so we cannot add the relation you propose.

Note that this transport is intramembrane since the lipid is inserted into the membrane so for P-type ATPases (flippases) this is a special case of transmembrane transport.


re-added support us page files and images

re-cloned repo and added each file one-by-one, shouldn't be any conflicts hopefully now

@kevinashworth I'm trying to add back and I suppose modify files that were part of my SupportUs Page that I built. @bruceplai had reverted back to pre-Support Us page this week bc something in my git history had done something to the package-lock file. I'm adding back exactly the files and code that makes this page render. I had to modify the typical way of using box / container in the index file  as the way the cards render in desktop vs. mobile isn't as simple as nesting, so they get shown and then hidden depending on screen size. If something needs to change with how I designed the page, please let me know. Also, I had to add the page to App.js so that it could route in the application

So you're adding back the files. And you're making some edits to use them at the same time. Makes sense.
And I'm creating an issue to fix the full-width appearance.


Remove nesting from json output

This includes at least dupver config
Not sure about removing it from dupver log because there might be a case where I want to load everything at once.

closing this as I'm not doing json output anymore


fetchHeaders looks for non semantic types

content-type should be replaced with Content-Type

turns out Content-Type does not work.


Saying date already has treatment logged

Trying to log my cat's treatment medication tonight but it's saying that I've already logged a treatment for today.

This is really tricky. I tried to fix a previous error by having the site better account for timezones, which it wasn't doing a good job on before.  It looks like because the old dates were not timezone aware, and the new one is, it's creating a slight error in reporting
If you click the "Allow multiple entries per day" option, this will allow you to enter the injection for today.

I believe I have fixed this specific issue.  Because I added timezones aware features to dates being logged starting oct 25th, anything logged before that is going to display incorrect time stamps on the log.  I am working on something to fix this in the next few days.
Sorry about the inconvenience!

@lizzyd1991 I believe all errors on the site are fixed.  The site now asks you to define your specific timezone, and all times are recorded and displayed relative to what you enter.  Please let me know if you find any additional errors, but I believe your concerns have been resolved.


bluez: 5.54 -> 5.55

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bluez/versions.
meta.description for bluez is: "Bluetooth support for Linux"
meta.homepage for bluez is: "http://www.bluez.org/"
meta.changelog for bluez is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.55 with grep in /nix/store/0lm8w7bwc42kfk2b8c7af5n62k73ylcf-bluez-5.55

directory tree listing: https://gist.github.com/b2fa8c528e6429004c9963f4e1524b41

du listing: https://gist.github.com/f1ae6b4026e33783fd0ae537941dbdac

Rebuild report (if merged into master) (click to expand)

2369 total rebuild path(s)

829 package rebuild(s)

829 x86_64-linux rebuild(s)
758 i686-linux rebuild(s)
43 x86_64-darwin rebuild(s)
739 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
adapta-gtk-theme
adoptopenjdk-icedtea-web
almanah
anydesk
apostrophe
aravis
arc-theme
areca
arx-libertatis
asciidoc-full
asciidoc-full-with-plugins
astroid
audio-recorder
azureus
balsa
baresip
bibata-cursors
bibata-cursors-translucent
bibata-extra-cursors
birdfont
bitwig-studio
bitwig-studio2
bitwig-studio3
bluejeans-gui
blueman
bluez
bluez-alsa
bluez5
bolt
bomber
bomi
bookworm
bovo
brasero
brasero-original
brltty
bt-fw-converter
btrbk
byzanz
cadence
calligra
calls
capitaine-cursors
cawbird
ccache
ccacheStdenv
ccacheWrapper
chrome-gnome-shell
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0lm8w7bwc42kfk2b8c7af5n62k73ylcf-bluez-5.55 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bluez https://github.com/r-ryantm/nixpkgs/archive/ef13bb70892224b58e3e235f20eec337b9c359e1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0lm8w7bwc42kfk2b8c7af5n62k73ylcf-bluez-5.55
ls -la /nix/store/0lm8w7bwc42kfk2b8c7af5n62k73ylcf-bluez-5.55/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings

https://nvd.nist.gov/vuln/detail/CVE-2020-27153

Link me: #102782


Pressable onHover, onMouseDown, onMouseUp callback

Hello mix team. Is there any way how to detect onHover, onMouseDown, onMouseUp from Pressable? I need to highlight specific a range of cells in a grid, starting from the one over which user has pressed mouse down and end on another where mouse up.

Hello! You can make use of the MouseRegion widget for the onHover callback:
MouseRegion(
  onHover: (event) {},
  child: Pressable(...),
),

For the onMouseUp and onMouseDown, you can make use of GestureDetector:
GestureDetector(
  onTapUp: (d) {},
  onTapDown: (d) {},
  child: MouseRegion(...),
),

I don't like the idea of adding more callbacks to Pressable. @leoafarias what do you think of adding gesture attributes, like:
final mix = Mix(
  onPressed(() {
    print('pressed');
  }),
  onEnterHover(() {
    print('entered hover');
  }),
);

Not a fan of adding too much behavioral and business logic into mix... let's close the flow on the style and visual piece and get some feedback

We use MouseRegion, thanks all for suggestions ;)


SAM-2586 Add Side Panel to Track Question Progress

Adds a side panel in tests, which are a single question per page, which shows test takers their progress in the test. Shows test takers what question they are on, all the other questions, which questions are answered, which questions are unanswered, and which questions are marked for review. Also allows test takers to navigate using the panel.

The styling of the panel looks a bit odd, also those look like clickable radio buttons. Maybe need some UX input?  Cool feature though.

Minor code changes suggestions provided

Whoops, pressed the wrong button!

@bjones86, I've addressed all your issues. Moving all the javascript to it's own namespace unfortunately broke the panel. In the meantime, I will close this PR and after I have fixed it I will reopen it.

Fixed what I broke.

I botched this, I should have reopened before force pushing the fixes. I can't reopen this, so I am making a new PR.  See #763


pytorchWithCuda does not install with CUDA

Describe the bug
When installing pytorch with cuda using python.withPackages (p: with p; [ pytorchWithCuda ])
I actually can't use pytorch with cuda
>> import torch
>> torch.cuda.is_available()
False

To Reproduce
Steps to reproduce the behavior:

nix-env -iA nixos.python37Packages.pytorchWithCuda
python -c "import torch; print(torch.cuda.is_available())"

Expected behavior
The python snippet should return True.
Additional context
nvidia-smi works fine.
On compilation i can see:
--   CMAKE_PREFIX_PATH     : /nix/store/cqdzxmf7dh4gz8n835p0xbx4zsfwgsxq-openblas-0.3.5:/nix/store/rml2wzx4yg7ibxk319dmqx7nsxd2bs4n-cudatoolkit-<IP_ADDRESS>-unsplit:/nix/store/dp1sivgbbskracywdblq52s1009q5ndv-cudatoolkit-<IP_ADDRESS>-lib:/nix/store/vg3w0kwigdn6r98narjrbwx9nk1hhhab-cudatoolkit-9.2-cudnn-7.2.1:/nix/store/ss2iqbj33xjmrng0a9ikqd4dji5c94bc-cudatoolkit-<IP_ADDRESS>:/nix/store/fl41dyb29hwgwg415l93yr94rppmb8lz-numactl-2.0.12:/nix/store/ws7zbv7xhdasdnhki1gqgp3l3cw2xd3j-python3.7-bootstrapped-pip-19.0.3:/nix/store/x9qhdlclpkq7sh57fwzva7npkb84y3g5-python3.7-cffi-1.12.1-dev:/nix/store/7qcr7gs35mlmpqd9f35w5fy8nwx5w0g5-libffi-3.2.1-dev:/nix/store/a0rz4s781sw9gfi2hvncw577ahh74x3r-libffi-3.2.1:/nix/store/9da2hplbdp9jrwn7331hf63w71cmrmc7-python3.7-pycparser-2.19:/nix/store/96p42644i76jqgdkxjgyl3f0c8n8k16j-python3-3.7.4:/nix/store/dvzig77cx97rdxn5i2pdmyblm8f6pf7d-python3.7-setuptools-40.8.0:/nix/store/dvzig77cx97rdxn5i2pdmyblm8f6pf7d-python3.7-setuptools-40.8.0:/nix/store/kn3nnz5fjy460jga9m1p20q6bpxpkwm6-python3.7-cffi-1.12.1:/nix/store/yp1699bckyw2chqr24lcs24lainrpiay-python3.7-numpy-1.16.1:/nix/store/azhay53hn57r174aqb0sbh8cky2k4frb-python3.7-PyYAML-3.13:/nix/store/rk0jndiqcpvp5vq8r05mpnas08mc78wl-libyaml-0.2.1;/nix/store/96p42644i76jqgdkxjgyl3f0c8n8k16j-python3-3.7.4/lib/python3.7/site-packages

...

-- Found gcc >=5 and CUDA <= 7.5, adding workaround C++ flags
-- Could not find CUDA with FP16 support, compiling without torch.CudaHalfTensor

...

disabling CUDA because NOT USE_CUDA is set
-- CuDNN not found. Compiling without CuDNN support

Metadata
$ nix run nixpkgs.nix-info -c nix-info -m                                                                                [19:50:55]
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.69, NixOS, 19.03.173426.541d9cce8af (Koi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - channels(arsleust): `"home-manager"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
  - python37Packages.pytorchWithCuda
# a list of nixos modules affected by the problem
module:

I tried to build using the definition on master, no change (CUDA not available during the test, no GPU capabilities when using pytorch) even though it was supposedly fixed in #60002.

#65041 should fix this

@GuillaumeDesforges https://github.com/NixOS/nixpkgs/pull/65041 was merged recently, can you please confirm this fixed your issue?

Thanks for the update! I removed NixOS from my computer recently, but I can do it next week.

Fixed by #65041, thx @prusnak !

I am facing the same issue. When I install Pytorch with CUDA, torch.cuda.is_available() returns False.

@ashkan-leo Please file a new issue


Can I disable the Dissenter new tab in the new version?

As much as most people in Dissenter use DuckDuckGo as their preferred search engine. I am one of the few who doesn't like it would prefer the default new tab experience and the google search engine.
Can we please give us an option to use the default tab rather than the dissenter tab?
I can't use the extension right now because of it.

Let me disable this. This absolutely should not be bundled in with the extension.

Let me disable this. This absolutely should not be bundled in with the extension.

I agree. I know that most users using Dissenter hate google but you have to let the non-haters have to choice not to use the new tab as well.

Hey. It isn't "haters vs non haters".  Okay.

Furthermore, just because I want to use Gab's service, does not mean I want them to inject stories into my new tab page. If I wanted to see "popular stories" and "recommended tabs" (which I assume Gab has a financial incentive to show me), I'd go visit www.dissenter.com myself. Tying this into an extension focused on freedom is a big no-no.

As much as most people in Dissenter use DuckDuckGo as their preferred search engine. I am one of >the few who doesn't like it would prefer the default new tab experience and the google search engine.

While I have nothing against DuckDuckGo, I prefer startpage.com and it hijacked that too. This concerns me. I also prefer Brave's new tab page, which I cannot use if I have dissenter enabled.

I'm using another tool to manage my tab page.  Any way to disable this ?

I'm using another tool to manage my tab page. Dissenter screwed me up. this should be optional.
Anyway, the fix is: edit manifest.json and remove the section which concerns newtab.html
IOW, delete ,"chrome_url_overrides":{"newtab":"newtab/newtab.html"} from the end of the manifest.json file in the root download.

Make sure to leave the last bracket though. When your editing is done the last couple of characters should look like this ,"keyword":"dissent"}}

Anyone know how to disable it on firefox?
i have my own riced up minimal homepage and do not want this JS flat design ridden mess.
In any case i will have to uninstall dissenter until it is removed or separated to another add-on

This has been fixed in 0.1.7

This has been fixed in 0.1.7

When and how

https://dissenter.com/dist/extensions/v0.1.7/dissenter_chrome.zip

Five hours ago: https://github.com/gab-ai-inc/gab-dissenter-extension/releases/tag/r10

Disabled new tab experience

@Lyeco, @danielb2, @pickx, @TehSViN24, @MasterOfTheTiger, @gary9872  in the latest release, r11, the Dissenter new tab experience has been made optional. It is off by default and can be toggled on from within the extension's options/preferences page.


let_xxx algorithms always specify set_error_t(exception_ptr) in the completion signatures

The let_xxx algorithms always specify set_error_t(exception_ptr) in the completion signatures, even if no exceptions can be thrown.
e.g. if I provide a sender, such that execution::connect(my_sender,r) is noexcept, and the arguments supplied to set_value by my sender are nothrow-move-constructible (e.g. int), and my sender never completes with set_error, then let_value(my_sender,[](auto ...) noexcept{ return another_noexcept_sender{}; }) should never complete with set_error either, since none of the constituent parts throw.
Thus, we need another potentially-throwing determination here, that detects if any of:

invoking execution::connect(s,r) can throw
storing args'... in op_state can throw (i.e. any of the types in Args are not nothrow_move_constructible) for any of the possible sets of Args for the completion of the source sender s.
invoking connect(f(args'...),out_r) can throw

and only includes the set_error_t(exception_ptr) in the completion signature if things are potentially throwing.

This might be impossible to implement under the current spec since we only get the environment type but not the receiver type in get_completion_signatures, which means that we cannot decide whether the connection would fail.

In order to implement this, then you connect the original sender with a proxy receiver. The proxy receiver then forwards to the final receiver. This way the type of the proxy receiver is known when determining whether or not the internal connect throws. I have implemented this.

In order to implement this, then you connect the original sender with a proxy receiver. The proxy receiver then forwards to the final receiver. This way the type of the proxy receiver is known when determining whether or not the internal connect throws. I have implemented this.

That is really a neat way that I haven't thought of to tackle the problem. Thanks for the inspiration!

@anthonywilliams Your proxy receiver suggestion requires something like virtual dispatch if I understand correctly. You want to test the noexcept-ness of connect before the actual receiver type is known. The indirect function call will lead to worse runtime perf.
Do I have that right? In your opinion, this trade-off is worth it?

Yes, it requires virtual dispatch, and yes it's a trade-off. If the cost isn't too high, I think it is worth it for the static properties that result. Being able to guarantee that there are no exceptions thrown is quite a nice property, and make it play better with freestanding environments.
However, I have not profiled it, or done this with real code and data, so I cannot tell you how the trade-off fares in practice.

It occurs to me that an implementation already has the freedom to provide an implementation that uses virtual dispatch to eliminate the possibility of a exception_ptr completion. I added implementor freedom to drop the set_error_t(exception_ptr) completion from any sender adaptor if the implementation is known statically to never call set_error with an exception_ptr ([exec.adapt.general]/p7).
This implementor freedom is good enough for me. @anthonywilliams ?


When should the NapariApplication be instantiated and its actions registered?

🧰 Task
When is app created?
When we initialize a napari.Viewer, we must also instantiate the NapariApplication object (which is our app-model app). The application is created when the get_app class method is first called.
Currently, this first call happens during execution of the intialize_plugins function, which is called first thing on Viewer.__init__ and registers npe2 plugin actions.
Is it strange that the NapariApplication, which is so critical to the Viewer and its function, is created in this little function rather than explicitly before we register manifest actions etc.? It seemed to @lucyleeow and I that it was a little hidden and potentially could lead to issues? So wanted to open for discussion.
When are actions registered?*
* I say actions here for brevity but these steps also include registering providers and processors.

Internal non-qt actions: as soon as we build the app, on NapariApplication.__init__. This seems normal to me.
Internal qt actions: on QtMainWindow.__init__. Also seems normal to me I guess - not sure if there's meaning to moving it up or down in the function.
Non-qt plugin actions: on initialize_plugins as above (which is up first on Viewer.__init__). This means it happens after internal non-qt actions and before internal/plugin qt actions. I think this is also ok.
Qt plugin actions: immediately after non-qt plugin actions, if qt is available. This means it's before qt actions, providers and processors are registered with the viewer, even though some plugin actions (if executed) may request the Viewer provider. @lucyleeow and I thought maybe this was kinda weird, and we should potentially consider splitting this out so that qt plugin actions are only registered after init_qactions?

Just a final note: in practice none of this seems to have caused any issues, and it may never. Everything is registered and available by the time the Viewer is returned. We just wanted to explicitly consider whether this is the right order of operations and whether there might be any potentially unintended consequences of the current setup down the line.

Thinking about this, where else do we get the app via get_app (which instantiates NapariApplication if one does not already exsit)? It would be good to decouple init of the app to plugins. I recall we were interested in being able to use napari standalone, without any plugins (napari-lite?).

Is it strange that the NapariApplication, which is so critical to the Viewer and its function, is created in this little function rather than explicitly before we register manifest actions etc.?

From my reading of the get_app classmethod, I think this is fine — it's written to work "just in time" so that it either returns the napari application if it exists, or it creates it otherwise. This is written this way specifically so that we don't have to plan when it gets instantiated, it just gets instantiated on demand the first time it's needed. If that happens to be in initialize_plugins, so be it! And:

It would be good to decouple init of the app to plugins. I recall we were interested in being able to use napari standalone, without any plugins (napari-lite?).

If at some point we want to implement a plugin-less app, we just need to call get_app where it is needed, and that might happen before plugin init, and that's fine, at that point the plugin init get_app will just get the already-created application.

immediately after non-qt plugin actions, if qt is available. This means it's before qt actions, providers and processors are registered with the viewer, even though some plugin actions (if executed) may request the Viewer provider. @lucyleeow and I thought maybe this was kinda weird, and we should potentially consider splitting this out so that qt plugin actions are only registered after init_qactions?

this is definitely a bit weird, but I don't know enough about the architecture to comment intelligently about whether it's worth rejiggering it.

whether it's worth rejiggering it.

Rejigging it would be trivial, we'd just move the safe_register_qt_actions function call out of where it currently is and below init_qactions. The downside to it, I guess, would be that plugin stuff gets registered now in two different spots, rather than in the one nice place. I don't see that as a super big downside, because at least this way there's a more explicit split between plugin actions that are qt dependent and ones that aren't. But I don't have very strong feelings - @lucyleeow?


Add Compatibility for Pydantic v2

Summary

makes prefect-fivetran compatible with Pydantic v2 Installed.

Relevant Issue(s)

#16
#15
Checklist

[x] Summarized PR's changes in CHANGELOG.md

@fivetran-aleksandrboldyrev @fivetran-nenad-stanojev
Are these tests outdated?

@fivetran-aleksandrboldyrev @fivetran-nenad-stanojev
Are these tests outdated?

Looks like - yes

closing as another PR addresses this


Auto Create/Fill In Structure fails on large structures

I'm reverse-engineering some code with incredibly large data structures, and my workload is much higher than it needs to be because the Auto Fill In Structure command arbitrarily stops working after offset 0x1000:
https://github.com/NationalSecurityAgency/ghidra/blob/a8cdc43bd4c885f5714f6267e6a4b29f05572bf9/Ghidra/Features/Decompiler/src/main/java/ghidra/app/plugin/core/decompile/actions/FillOutStructureCmd.java#L566
It's entirely reasonable to avoid improperly making huge structures, especially since they can slow Ghidra to a crawl, but can we change this value to be either (a) configurable in the UI or (b) reactive to the current size of the structure? I feel like
*(undefined8*)(this + 0xFF0) = 0;
*(undefined8*)(this + 0xFF8) = 0;
*(undefined8*)(this + 0x1000) = 0;
*(undefined8*)(this + 0x1008) = 0;

shouldn't stop creating fields in the middle just because an arbitrary limit got reached. Maybe something like max(0x1000, current_size * 2) would make more sense? Or at the very least, if using the "Fill In Structure" variant of the command, set that maximum to no less than the size of the existing structure.

Honestly the 4k default size limit seems reasonable enough, having a single allocated structure exceed a single memory page is a bad code smell. But sometimes we have to reverse-engineer stinky code, of course 😅
Nonetheless, I wouldn't want to ditch the size limit entirely, just because Ghidra has such trouble with large, unpopulated structures. I feel like it'd be simple enough to use Auto Recover to create the first 4k of the structure, see this[0x26] in the decomp output, manually increase the structure size, and then use Auto Fill In to snag the rest of the fields. So if that 0x1000 can just clamp itself to the existing structure size as a minimum, that'd be golden 🙂

@ryanmkurtz I've left some comments on the commit; you don't have to take them, of course, but I think they'll probably improve the code and the feature if so.

I'll defer this to @dragonmacher

@ryanmkurtz I've left some comments on the commit; you don't have to take them, of course, but I think they'll probably improve the code and the feature if so.

Thanks for your input.   I responded to your comments.


feat: add gaussian noise to image

Closes #381
Summary of Changes
Images can now be modified with "gaussian noise".

Need to add the new method to the image tutorial also.
Or do we generally create new issues for that? @lars-reimann

Need to add the new method to the image tutorial also.
Or do we generally create new issues for that? @lars-reimann

No, that should be added as part of this PR.

It's now added to the "Image Processing" tutorial.

Tests fail locally for me (top_level_collect).

Run poetry install.

Run poetry install.
Ofc, thank.s

Thanks, I've added that edge case too.

:tada: This PR is included in version 0.15.0 :tada:
The release is available on:

v0.15.0
GitHub release

Your semantic-release bot :package::rocket:


CIBA Sample App

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


3D grid project onto objects

this grid on an object would be a nice idea. there are 2 known methods:

gpu line rendering with bpy, this is performant but tricky to implement
shader material on all objects.. this is going to be laggy but very easy to setup. and only works in render mode.

this material shader was shown to me by Minimum Working Example in the blender discord.


reading eeglab set files

I was wondering if you have any tools for reading eeglab .set files (along with .fdt) and converting to mne-python representation?
It would have seemed easy to do if not for the fact that sometimes (always?) scipy.io.loadmat fails in reading eeglab .set files (eeglab .set files are just .mat files). See my issue on scipy repo here.

Not at the moment, but I think this would be a useful addition definitely.

I would be happy to dig into this, but I would have to use something else than scipy.io.loadmat to open the .set files. I'll try using h5py or h5io...

I tried the sample data from EEGLAB and it seems to be loading fine using scipy. Let us know what solution you find for your file.

Did you try the file I link to in the issue here?

I managed to open datasets from a different study with loadmat. I'll investigate this in the next couple of days.

I just tried and both files work fine for me.

... but I'm on python2.7

This would be cool to have. Would you also do EEGLAB ICA files? :)
As a workaround, I've previously used the BVA export function of EEGLAB.

What do you mean by EEGLAB ICA files?
eeglab keeps everything packed in the EEG structure (the .set file; the eeg signal is usually kept as float32 in a separate .fdt file). ICA weights are kept in EEG.icaweights and EEG.icasphere. I was planning to extract these too.

Yes, I meant writing out the EEGLAB ICA structure to mne/fif ICA objects.

I'm on it. I'll make a PR soon. @jona-sassenhagen you can lend a helping hand if you want ;) I'm not super-familiar with EEGLAB.

Just BTW - I still can't import that file (or any other file for that study) I linked at the scipy issue through read_epochs_eeglab :cry: (on python 3 at least)

A practical workaround might be downsampling in EEGLAB.

The samling rate was rather low for that file (250) but I could try downsampling. The funny thing is that MAT.jl (Julia lib for reading/writing mat files) handles the file without problems.

can you share the file?

Right, I forgot that the previous dropbox link doesn't work anymore.
Here is a working link - just one .set and corresponding.fdt.

io.loadmat('faces_e_22.set') works fine with me with
In [4]: scipy.version
Out[4]: '0.17.0'

I can confirm that the issue can be reproduced in python 3.5

@mmagnuski it seems more like a scipy issue to me than an mne-python one. You can get it working by switching to python 2.7

Thanks for checking!
Yes, I have scipy issue opened for this but it was inactive for quite long. I've already switched to Julia + PyCall for this project, but I will try things out in python 2.7 conda env.

pb solved:
https://github.com/scipy/scipy/issues/5516#issuecomment-225413189
use:
io.loadmat('faces_e_22.set', uint16_codec='latin1')
we should expose the uint16_codec parameter in the eeglab reader.
@mmagnuski can you give it a try?

Thanks, works very well!

cool
can you do the PR to expose the codec param in eeglab reader?

Sure, I can do that tomorrow.

Hi, I am working in python MNE with a .set file from EEGlab(matlab). I have imported the data using:
x=mne.io.read_raw_eeglab('Subject1.set')
but am trying to follow some tutorials and always run into the following error:
"IOError: [Errno 2] No such file or directory: u'Subject1.fdt'"
One line which gives this error is ln[8] of the following tutorial:
https://plot.ly/ipython-notebooks/mne-tutorial/
The error arises basically any time the word "time" appears
Help?! Thank you!! :)

Hi @KirstensGitHub could you share your Subject1.set file? Usually, the EEGLAB reader tries to find the .fdt file if that's pointed to in the .set file. Is your data also in the .set file? The reason you get your error later is probably because preload=False.

I see!
location: KirstensGitHub/Mich_collab/Subject1.set
I had seen somewhere after loading that the fdt file did exist, but the computer seemed to not find/recognize it.
I just tried x=mne.io.read_raw_eeglab('Subject1.set', preload=True) but got the same error..

what is the location of the '.fdt' file? It is typically in the data field of your mat file structure. Can you share both files (*.set and *.fdt) on dropbox or privately by email so we can diagnose further?

Ah, I feel so embarrassed. I just had the .fdt file saved in the wrong place... blush
All working now!
Thanks so much for your quick replies! I'm relatively new to GitHub and have never seen an "issues" page/discussion like this before- very cool!

another file-type-related question: is there a way to use mne.read_evokeds on the .fdt and .set files?

@KirstensGitHub this is not possible as of now. I suppose we could theoretically support it. But I don't know what the other developers have to say. I'm sure @agramfort has an opinion on this. @KirstensGitHub isn't it possible for you to save the epochs and then average it in MNE?

Is the EEGLAB format intended to store evoked data? I think it's intended for epochs and continuous.
EEGLAB is really not about evoked stuff, but about single trial stuff.

This is indeed what I thought ...

On my Windows 10 system, the mne.io.read_raw_eeglab reader always tried to append ".mat" to the .set file name with the error No such file or directory: 'xxxx.set.mat'. I tried reading the same EEG data in edf format , and mne.io.read_raw_edf() worked just fine.  Not sure why .mat is automatically appended to the .set file name...

what version of scipy are you using?

scipy version: 0.18.1
platform : win-64
conda version : 4.2.15
conda is private : False
conda-env version : 4.2.15
conda-build version : 2.0.2
python version : 2.7.13.final.0
requests version : 2.12.4

can you paste the error and also what exactly you are passing as input_fname?

The error @KirstensGitHub had (didn't notice that discussion before) reminds me of another problem when reading set files - eeglab, when reading set + fdt files checks the filename in EEG.data but also the name of the set file (mne python only checks EEG.data). In some cases these names are not exactly the same (ie EEG.data.replace('.fdt', '.set') != set_filename) so might be good not to rely (at least not only) on EEG.data field.

I just realize I need to do "import scipy" first. Now mne.io.read_raw_eeglab () can read raw EEG .set files just fine. But I could not get the mne.read_epochs_eeglab () to read in the epoched datasets in EEGLAB to work. The reader always showed AttributeError.
epochs = mne.read_epochs_eeglab(fname)

File "C:\Users\Yang\Anaconda3\lib\site-packages\mne\io\eeglab\eeglab.py", line 241, in read_epochs_eeglab
uint16_codec=uint16_codec)
File "", line 2, in init
File "C:\Users\Yang\Anaconda3\lib\site-packages\mne\utils.py", line 708, in verbose
return function(*args, **kwargs)
File "C:\Users\Yang\Anaconda3\lib\site-packages\mne\io\eeglab\eeglab.py", line 484, in init
event_type = '/'.join(ep.eventtype.tolist())
AttributeError: 'int' object has no attribute 'tolist'

please share the epochs EEGLAB dataset

Here are the epoched files from EEGLAB. I tested  several other epoched files from different EEG experiments using different versions of EEGLAB. They all showed the same error. Thanks.
http://zhanglab.wikidot.com/local--files/method/KH1_TONE1K_IGN1_epoch.fdt
http://zhanglab.wikidot.com/local--files/method/KH1_TONE1K_IGN1_epoch.set

Hi,
I am working on a .fdt file. While ı am trying to read it with python scipy-loadmat, I am taking this error:
ValueError: Unknown mat file type, version 147, 65
what should I do in this situation, thanks for your helps!

Can you please provide the full traceback? Also for questions, the right place to ask is the mailing list. You should post on github only if you are reasonably sure you have a bug

Fdt is not matlab file. It’s a companion file to a .set file that is actually a .mat file


fix: inappropriate type annotation

Before:

After:

I'm facing the same issue, a quick merge would be awesome!
Thanks for your work!


Reorganize source files and header files

We should move header files to an include/ directory.
ipam_client might need to be removed or separated.
pam_interactive.cpp should probably be main.cpp.

Also need to look into separating pam_handshake_auth_check executable. This is being used by the server-side plugin, but it may behoove us to make its own CMakeLists file for clarity and separation of concerns.

If any further reorganization is needed post-#21, please open a new issue.


SwaggerUI fails when running on IIS/dev-server : Service Unavailable …

SwaggerUI fails when running on IIS/dev-server : Service Unavailable  /swagger/v2/swagger.json.
However, opening path_to_app/swagger/v2/swagger.json in browsers produces the json-file.
Changing the SwaggerEndpoint to "v2/swagger.json" makes the UI appear, but the urls then used by the "execute"-buttons at the endpoints seems make the requestes at host/controller_route, that is miss the virtual directory. Adding a OpenApiServer seems to fix this.

Naming extended from:  https://swagger.io/docs/specification/api-host-and-base-path/
Https://data.ssb.no/folder1_on_iis/subfolder2_on_iis/route_prefix_in_app/controller_route...
__    host         / ______         ISS Path    ______/ _   route_prefix  _/_ controller_route __


[Claiming app] Proposal titles not parsing correctly

Bug description
The number of Snapshot proposals are not parsing correctly from tutish.eth.

The proposals are received correctly, however:

It is likely related to the regex parsing of the proposal number.
Steps to reproduce
Open in !IS_PRODUCTION environment and observe [SEP#6] not displaying the proposal number.
Expected result
safe-global/web-core#6 number is displayed correctly.
Obtained result
The number is not shown.

Is it a web-core issue or a claiming app issue?

Good point, it's related to the claiming app widgets. I've adjusted and transferred the issue accordingly.

I looked into this and the test proposals were created incorrectly. They should be [SEP #n] but are missing the space, [SEP#n].
As they are from our test space and the team is aware of the "correct" format, I will close this.


Missing entry for error SameKeyMaterialNotFoundOnRemoteServer

I think it should be nice to have an entry added for the SameKeyMaterialNotFoundOnRemoteServer error in this article. Let me know if you find it appropriate and I can add it myself<EMAIL_ADDRESS>Details about the error can be found here https://techcommunity.microsoft.com/t5/azure-database-support-blog/error-samekeymaterialnotfoundonremoteserver-while-coping-azure/ba-p/3630398

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

ID: 83b6d066-9a0d-ebdb-7432-fb4ae7a82794
Version Independent ID: 645e4ba4-7898-c2ec-bbb4-c39aecb7e21f
Content: Common errors with customer-managed keys in Azure Key Vault - SQL Server
Content Source: docs/relational-databases/security/encryption/troubleshoot-tde.md
Service: sql
Sub-service: security
GitHub Login: @rwestMSFT
Microsoft Alias: randolphwest

Nacho, if you want to create a PR for this, feel free.

@nachoalonsoportillo We haven't heard from you for a long time. Feel free to add a PR. In the meantime, I'm closing this.


Fix typo

could you please fix it in the template.md file too.

Fixed on template.md too @sokra

Thanks


Vagrant: Add default host fwd port

If the user doesn’t define DLV_RPORT variable during vagrant up, the command failed with the following message:
There are errors in the configuration of this machine. Please fix
    the following errors and try again:

    vm:
    * Forwarded port definitions require a "host" and "guest" value
    * Ports to forward must be 1 to 65535

This PR prevents this failure by setting up default ports if the user doesn't specify anyone.

@nam-jaehyun should I open an issue first?
If not, please review.

DLV_RPORT is defined in the Makefile, and we're using "make vagrant-{up|ssh|destory}".

you can raise an issue and finalize this PR.

Codecov Report

Merging #323 (fad2eab) into master (efe9b2f) will decrease coverage by 0.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #323      +/-   ##
==========================================
- Coverage   37.79%   37.43%   -0.36%
==========================================
  Files          21       21
  Lines        8943     8943
==========================================
- Hits         3380     3348      -32
- Misses       5216     5248      +32
  Partials      347      347

Impacted Files
Coverage Δ

KubeArmor/core/dockerHandler.go
52.14% <0.00%> (-12.46%)
:arrow_down:

KubeArmor/monitor/systemMonitor.go
32.50% <0.00%> (-0.39%)
:arrow_down:

KubeArmor/core/kubeUpdate.go
49.72% <0.00%> (-0.19%)
:arrow_down:

KubeArmor/feeder/policyMatcher.go
36.50% <0.00%> (+0.52%)
:arrow_up:

Continue to review full report at Codecov.

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


Relax Features that need to be Disabled prior to Upgrade check for pre-installed apps

Currently this check will flag on every app that is enabled, which includes the pre-installed apps.
Pre-installed apps typically cannot be disabled, only removed. We have received confirmation that upgrading with pre-installed apps enabled should not pose an issue to the upgrade.
As such, this check needs to be relaxed for such apps including:

Cisco_NIBASE (ACI version 4.2+)
Nexus Insights Cloud Connector (ACI Version 5.2+)
Cisco_ApicVision
Base Package apps:

Search
APIC Postman
Contract Viewer
VisuDash

The default apps ('IntersightDC', 'NIALite', 'NIBASE', 'ApicVision') are already covered.
The Base Package apps are no longer pre-installed, which makes this issue irrelevant for most of the recent versions.


Forward read_exact() as well as read().

If we don't do this we end up using the generic read_exact method
which is not necessarily optimal. This is especially when
using a specialized Read implementation to go fast.
See https://github.com/TyOverby/bincode/issues/206

Looks good, thanks!
I'm also really interested in your specialized Read implementation.  Is this the one that eschews bounds checking?

@TyOverby It's at https://github.com/servo/webrender/pull/1834.

I just realized that this pull request alone will improve deserialization performance because we'll now be using the read_exact() implementation on &mut [u8] which is simpler than the default read() implementation.


feat(chat):609 confirmation message if imports chat prompt is exist

Description:
Confirmation message if imports chat prompt is exist
Issues:

Issue #609

UI changes
<Please, provide Screenshots or Figma links>
Checklist:

[ ] the pull request name complies with Conventional Commits
[ ] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[ ] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[ ] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "feat(chat):609 confirmation message if imports chat prompt is exist". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - fix
 - hotfix
 - feat
 - feature
 - chore

/deploy-review

/deploy-review

/deploy-review

/deploy-review

/deploy-review

/deploy-review


 not working on tab's root page

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
 not working on tab's root page in iOS 10.2.
Ionic info:
Cordova CLI: 6.4.0
Ionic Framework Version: 2.1.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.3
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: OS X El Capitan
Node Version: v6.9.1
Xcode version: Xcode 8.2.1 Build version 8C1002

Hello! While we appreciate you opening an issue with us i am going to close this issue and ask that you open a new one that has the issue template filled out please. Thanks for using Ionic!


Add condition for merge straight

When the modifier is straight on a merge instruction, instructions should say "merge onto This Highway" instead of "merge straight onto This Highway" because "merge straight" doesn't make any sense.

[x] Add the case
[x] Add changelog entry
[ ] Review

I might hold off on this release for now... I want @mcwhittemore's eyes on the default part of this addition.
To clarify following questions from @bsudekum, this is adding special handling for a merge maneuver with a straight modifier.

fyi @lyzidiamond I incorporated @mcwhittemore's comment :)
@mcwhittemore can I get another 👁 ?


Support AltGr (ISO_Level3_Shift) as a modifier key

On US Keyboards the left Alt and right Alt key are the same. However, on European based keyboards the right Alt key is known as AltGr (ISO_Level3_Shift) and is a different modifier than left Alt. Currently it is not possible to use AltGr for a oneshot or mods_on_hold action. This PR changes that.

After some further testing I noticed that this PR breaks action such as mods_on_hold and oneshot in some cases. For example, in a terminal oneshot(I) works without problems but in Firefox nothing happens.
Also mappings such as mods_on_hold(C, esc) do not work anymore either.
So for now, please don't merge this.

Problem solved.

Thanks. I was peripherally aware of altgr but not really sure how it works. From your commit I conclude that it emits the same keycode as a US keyboard (rightalt) but is interpreted by the display server differently based on the key layout. Is this correct? Also, is there a reason you have chosen 'I' as the modifier? G would seem like a more natural choice to me, unless there is already precedent for the former that I am not aware of.

I've merged this and corrected some small mistakes. I've also renamed 'I' to 'G' in the in the meantime.

I was peripherally aware of altgr but not really sure how it works. From your commit I conclude that it emits the same keycode as the corresponding key on a US keyboard (rightalt) but is interpreted by the display server as an alphabetic modifier based on the key layout. Is this correct?

Yes, it shares the same key code but behaves as a alphabetic modifier for writing other or additional characters. These characters are dependent on the keyboard layout.

Also, is there a reason you have chosen 'I' as the modifier? G would seem like a more natural choice to me, unless there is already precedent for the former.

I choose 'I' because of it being called "ISO_Level3_Shift" by the xmodmap tool which was not a smart idea. I agree that 'G' is a much better choice.
Thanks for incorporating my changes into master!

Thanks for the contribution :). In the future please create an issue first. This was a good candidate for inclusion but I may reject certain patches.


Update README

Change-type: patch
Update README to make it explicit that this module is not meant only for enqueueing/dequeueing action requests.
Based on this discussion.

@Ereski Something else that might be worth discussing is the first item in the list of requirements. What exactly does it mean for a queue to be fast? Also, we rely heavily on graphile-worker. Does it allow us to completely meet this requirement?

@edufschmidt I've seen the code and it's as fast as postgres allows basically. And the heavy lifting is done by graphile-worker, yep.
There might be a couple of small optimizations that can be made but for a persistent queue backed by postgres it is what it is. You should take a look at graphile-worker it's not that complicated. Only thing it is missing (or was) is prioritization, which would be super interesting for JF so it can prioritize interactive actions (e.g. logging in) over stuff like sync.

oh it's a draft. @edufschmidt im making it ready for review but keep in mind that drafts can't be approved. And since PRs require one approving review, it's ok to make them normal PRs from the get go. Drafts are for stuff that you don't want merged nor approved.


website - broken link to main release file

Description of typo, bug or error
On your home page (https://obophenotype.github.io/cell-ontology/), under the Accessing CL header, this link:

The main release file can also be found here.

generated a 404 error (1/5/2004 5 pm Pacific time)

Thanks Karen.  @anitacaron - I think link just needs to change to release prod link.


How to blacklist mob of mods?

Hello, I was wondering if you could explain to me how I can fix my crashes.
I have mods active like outvoted, and zombified and some other ones with more mob varients, but they crash my game and I have 0 coding skills.
I changed this in the config but it does not work Example: I tried this: ,outvoted.wildfire
Then I changed it to ,outvoted:wildfire, but it changed the text in the file to this.. I tried some other things but I can not figure out how to exclude mobs.
// Exluded Entity List Bsp: minecraft.villager
"excluded_entity": [
"outvoted",
":wildfire",
"outvoted",
":glutton",
"outvoted",
":barnacle",
"outvoted",
":meerkat",
"outvoted",
":ostrich",
"zombified",
":arctic_zombie",
"zombified",
":beserker_zombie",
"zombified",
":crystal_zombie",
"zombified",
":infernal_zombie",
"zombified",
":miner_zombie",
"zombified",
":sludge_zombie"
],

yes it is only one dot between the modid and mobid so like you first tried "outvoted.wildfire"
what is important here, the modid and mobid has to be correct
For example, in the fabric.mod.json you can find the correct modid like here: https://github.com/How-Bout-No/Outvoted/blob/arch-1.17/fabric/src/main/resources/fabric.mod.json#L3
and here the mobid: https://github.com/How-Bout-No/Outvoted/blob/06c257f2cfef8355a3166ac6164a753b760173ca/common/src/main/java/io/github/how_bout_no/outvoted/init/ModEntityTypes.java#L16
So basically your first intention was correct


correct staking on windows

lol non siete neanche in grado di clonare i vostri stessi progetti... sistemate così posso dumpare anche questa moneta per xch... use google translate for that.
lo staking su windows non funziona.. Wallet_id error if try to stake it
THX

same

staking does not work in Windows. Wallet_id error,

Copy staking address and paste it to address or contact under SEND, enter amount to be stake and then send

Copy staking address and paste it to address or contact under SEND, enter amount to be stake and then send

how to withdraw the staked amounts?

what is the contract adress of ssd coin, where we must put in in the nft recovery tab in gui.

Please update your program to the latest version


getResultSet should return null after executeUpdate

Fixes #3523.
According to the doc of  interface Statement, Statement.getResultSet should return null when the result is an update count.

    /**
     *  Retrieves the current result as a ResultSet object.
     *  This method should be called only once per result.
     *
     * @return the current result as a ResultSet object or
     * null if the result is an update count or there are no more results
     * @exception SQLException if a database access error occurs or
     * this method is called on a closed Statement
     * @see #execute
     */
    ResultSet getResultSet() throws SQLException;

@SteNicholas I approve it, anything else for you?

@SteNicholas I approve it, anything else for you?

I have some comments which need author optimize.

@SteNicholas I approve it, anything else for you?

I have some comments which need author optimize.

resolved

@gfreezy Please update import order.

@SteNicholas Done. But if there is an import order to ensure, we should add an import order lint.

@terrymanu LGTM, please merge.

@gfreezy Check this CI failure result.

@SteNicholas It seems the problem of CI. How can i rerun it.

@gfreezy Please close this pull request, and reopen this pr.

/run ci

please use '/run ci' to restart ci, it is tested ok.

/run ci

Hi, the exception is caused by NPE, maybe we should debug the exception, not just run ci without any changes

@gfreezy Please modify the return value according above comment.

@gfreezy @SteNicholas hi, Please use English to discuss code review suggestions.

@terrymanu @SteNicholas https://github.com/apache/incubator-shardingsphere/pull/3547/commits/ce3be4be7e04f921f2b92ec590510b616a27640e
This change can bypass the null check. But i think it's really not a good idea to write like that. It is hard to get what will be returned.


Disable walking/running while performing expressions

Right now, the avatar skids if we try to perform expressions(Q) while walking/running. We should either disable walk/run while performing expressions or add proper animations for it. Same is the case with flying.
https://user-images.githubusercontent.com/35926530/180797925-fb1502fe-9b4b-452b-b782-746a78f41020.mp4
https://user-images.githubusercontent.com/35926530/180797946-4a24213c-041c-498d-a1b6-3be836a62028.mp4

fixed


Method onValidationError is called twice

Package
filament/filament
Package Version
v3.0-stable
Laravel Version
v10.10
Livewire Version
No response
PHP Version
PHP 8.2.15
Problem description
The method onValidationError is called twice from custom pages that use InteractsWithForms. My temporary fix is to not use it.
Expected behavior
It should be called only once.
Steps to reproduce

Create a custom page
Add use InteractsWithForms
Create a form and a submit method with validate
Do not follow the rules and submit
onValidationError will be called twice

Reproduction repository
https://github.com/sglkc/filament-issue
Relevant log output
No response

You do not need HasForms or InteractsWithForms when using a Filament page, we have those on the base Page class, and adding them again can cause issues like this


[ENG-3970] When normal pickle fails, try dill

If dill is not installed, suggest that the user pip install it.
Fix https://github.com/reflex-dev/reflex/issues/4147

Since we are adding dill to pyproject, is there any way that dill wouldn't be installed?

Since we are adding dill to pyproject, is there any way that dill wouldn't be installed?

it's a dev dependency, so it only gets installed when you do poetry install. if you just pip install reflex, then it won't be included


bureaucracy options set validate: 'image', failing non-image attachments

Finally got this bug!
This needs to be set to upload.validate || 'image', to properly set validator as in README: https://github.com/bevacqua/woofmark#optionsattachments.
https://github.com/bevacqua/woofmark/blob/master/src/prompts/prompt.js#L116
I also found that after solving that, I got options.mergeHtmlAndAttachment is not a function on this line:
https://github.com/bevacqua/woofmark/blob/2d932112d44c7f72ccc9e23daf6749b9cc8bcdde/src/html/linkOrImageOrAttachment.js#L51
That's because that should be specified here:
https://github.com/bevacqua/woofmark/blob/2d932112d44c7f72ccc9e23daf6749b9cc8bcdde/src/bindCommands.js#L74
But that doesn't seem to appear anywhere else in the codebase. I think it could be from a previous version of the API, but it seems to be pretty simple:
options.mergeHtmlAndAttachment(chunks.before + chunks.selection + chunks.after, link);

And it expects:
      chunks.before = parts.before;
      chunks.selection = parts.selection;
      chunks.after = parts.after;

I'm going to try just adding a default that wraps it in an <a> tag.
Happy to submit a PR shortly.

There may be a more up-to-date way to do this, perhaps modeling on what happens in https://github.com/bevacqua/woofmark/blob/2d932112d44c7f72ccc9e23daf6749b9cc8bcdde/src/markdown/linkOrImageOrAttachment.js -- but it's a bit obscure to me, so I'll stick with a minimal change for now.

Fix submitted in #46!


DASH compatibility

Current Behavior
Is the DASH/mpd file support disabled or broken?
Even in the demo version the DASH example isnt working. I tried multiple browsers but nothing changed.
Self hosted i cant seem to get a video stream up and running.
Expected Behavior
The video player should provide a video.
Steps to Reproduce

Look at own demo link. (https://cookpete.com/react-player/)
Or try following example:
<ReactPlayer url="https://dash.akamaized.net/envivio/EnvivioDash3/manifest.mpd"      playing="true" controls="true"/>

Environment

URL attempting to play: https://dash.akamaized.net/envivio/EnvivioDash3/manifest.mpd
Browser: Google Chrome
OS: Ubuntu 22

It looks like https://dash.akamaized.net/envivio/EnvivioDash3/manifest.mpd just isn’t available any more. The files from https://reference.dashif.org/dash.js/nightly/samples/ work so I’ll switch to one of those. Good spot.


Increase grpc connection timeout

fix TestReachability flake
I have seen it many times, here is one
https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio/26058/integ-security-k8s-tests_istio/17637
2020-08-03T06:24:20.683349Z	info	tf	  [ 0]                        vm-v1-67bb7d5cf5-6j994         Running (Ready)
2020-08-03T06:24:20.683758Z	info	tf	  [ 0]                          a-v1-d476f5469-sk9q8         Running (Ready)
    TestReachability: context.go:111: initialize instances: 1 error occurred:
        	* initialize TestReachability/[*kube.instance-2]: grpc client: context deadline exceeded

2020-08-03T06:24:21.054546Z	info	tf	=== DONE (failed):  Test: 'security[TestReachability] (21.119566006s)' ===
2020-08-03T06:24:21.054571Z	error	tf	=== Dumping Namespace reachability-22-85702 State...
--- FAIL: TestReachability (23.13s)

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
bbf5efa62be6f8038d4a74bbbcc40636856d1230
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
bbf5efa62be6f8038d4a74bbbcc40636856d1230
link
/test release-notes_istio

unit-tests_istio
bbf5efa62be6f8038d4a74bbbcc40636856d1230
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
bbf5efa62be6f8038d4a74bbbcc40636856d1230
link
/test release-notes_istio

unit-tests_istio
bbf5efa62be6f8038d4a74bbbcc40636856d1230
link
/test unit-tests_istio

integ-multicluster-k8s-tests_istio
bbf5efa62be6f8038d4a74bbbcc40636856d1230
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

Can you create an issue and assign to me for this?


Pinger makes undesired request to /

There's a tricky edge case here when remove_endpoint() is invoked on the pool while a soon-to-error-out pinger request is in-flight. Removing an endpoint from the pool close()s the PoolEndpoint and nulls out the ping_path. However, in that time, a pinger could have been started. If the pingers request were to error out it'll cause a subsequent ping() within the pinger to the root ("/") endpoint of your HTTP server. Most of the time this likely goes unnoticed in production environments.
It took a bit of weasling to reproduce in a test case, but if you take the check that I added out of the make_request() function, the assertion will fail.

Great catch, that's subtle! Fixed in<EMAIL_ADDRESS>


Saving tensorflow logs to a log file in python

Click to expand!
Issue Type
Support
Source
binary
Tensorflow Version
tf 2.2
Custom Code
No
OS Platform and Distribution
Windows 10
Mobile device
No response
Python version
3.7
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
While running a script that uses tf, it prints some logs such as info and warning that comes from inside the tensorflow library. Instead of printing this on console how can a user save it into a seperate log file and another log file for other modules. That is saving logs of tensorflow alone into one file and the python logging as per user preference.

Standalone code to reproduce the issue
import logging

# get TF logger
log = logging.getLogger('tensorflow')
log.setLevel(logging.DEBUG)

# create formatter and add it to the handlers
formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')

# create file handler which logs even debug messages
fh = logging.FileHandler('tensorflow.log')
fh.setLevel(logging.DEBUG)
fh.setFormatter(formatter)
log.addHandler(fh)

Relevant log output
No response

Hi @wanderer799 !
You can save the command line outputs directly to a log file through below command beside above code snippet.
python3 training.py > output.log
Feel free to explore other options from   tf.compat.v1.logging   ( like saving logs in each n epochs etc) too.
Reference.

Thank you!

Thanks for this info.
The Problem is I am making a module/package from scratch so it will have its own logging. What I need is that there should be two log file one with tensorflow.log and package.log . So I have to set this up inside the main python file on how the logs of tensorflow should be collected and saved.

@wanderer799 !
You can just use a logging function either from python/tf.compat.v1.logging in the package/module to call it by default when some functions are used in the main file save it into package.log . You can use the same logging function in main.py file to save it into tf.log . Attached a sample code below to explain above context.

# package.py
class package_1()
   def __init___():
      # take some params and initialize
   def log_data():
     logging.basicConfig(filename = 'package.log',   # confi
                    level = logging.WARNING,
                    format = '%(asctime)s:%(levelname)s:%(name)s:%(message)s')
    #error logs.
    #error warnings.

  def process_1():
      #some logic
      log_data() # call the logging function to log warning , errors  etc.

process_1()

#main.py

import tensorflow as tf

def log_data():
     logging.basicConfig(filename = 'package.log',   # confi
                    level = logging.WARNING,
                    format = '%(asctime)s:%(levelname)s:%(name)s:%(message)s')
    #error logs.
    #error warnings.

ob_test = package_1()
package_1.process_1() # while using functions of package_1 it logged the data for respective package
log_data()

Attached relevant thread for reference.
Thank you!

Thanks for this, it helped me though the issue with tensorflow, where its logs and all get displayed in my console is still there, its not able to save it into a file.
Say for eg: when I import tensorflow

this log warnings pop up, I just want it to be saved to a file.
As of now I am using sys.stderr to collect the messages coming into the console and redirecting it into a file.
A better solution would be appreciated, Correct me if I am misunderstanding the above solution.

Hi @gadagashwini !
Could you look at this issue.
Thank you!

Hi @wanderer799, You can use tf.get_logger() to get log details by setting log level.
tf.get_logger().setLevel('WARN')
_level_names = {
    FATAL: 'FATAL',
    ERROR: 'ERROR',
    WARN: 'WARN',
    INFO: 'INFO',
    DEBUG: 'DEBUG',
}

Thank you!

Can I use tf.get_logger() to store the logs from tensorflow into a seperate
log file rather than making it display on the console?
On Fri, Sep 9, 2022, 3:09 PM gadagashwini @.***> wrote:

Hi @wanderer799 https://github.com/wanderer799, You can use
tf.get_logger() to get log details by setting log level.
tf.get_logger().setLevel('WARN')
_level_names = {
FATAL: 'FATAL',
ERROR: 'ERROR',
WARN: 'WARN',
INFO: 'INFO',
DEBUG: 'DEBUG',
}
Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/57553#issuecomment-1241745453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOBE26YZJ6S3VY24IUHKM2DV5MAWDANCNFSM6AAAAAAQBJIHVQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @wanderer799, tf.get_logger() used to get the logger instance. Thank you!

I tried like this
import tensorflow as tf

tf_logs = tf.get_logger()
fh = logging.FileHandler("tf.log")
tf_logs.addHandler(fh)

Though the file is getting created its empty and all the warnings are shown in the console itself.

@thomasjv799 Just trying to understand why do you need to log all the warning including import warning? Can you please explain the use case. Thanks!!

I am trying to build a python package that mainly uses tensorflow models for predictions. In order to see the progress tqdm is used so that we can see the progress bar in the console. So when I run .py file, all the tensorflow warnings and such comes into the console mainly CUDA warnings and all. For the package part I am using a logging module and its gets saved to a file. I wanna at the same also record the tensorflow warnings and errors like the same way into a file for future reference.
In this way I will will two log files, one log file from my package and the other log file will contain only tensorflow logs.
Right now I am suppressing the tensorflow messages by raising the log levels as below:
import os
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'

However what I want is a console where there is no tensorflow warnings or such and gets saved to a seperate log file.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Rethink the linking of FB_Object:s

At the moment FB_Objects are able to be bound together via its FB_init "constructor". This property has been taken directly from TcOpen. For their (TcOpenGroup) use-case, objects are instantiated within a context, which has "global" shared resources for all the child objects to access. For instance, a TcoLogger within a context is available for all child objects to use. Here are a few points to mull over:

What are the real benefits of this practice (for our use case)?
Does this increases unnecessary and accidental couplings between objects?
Should this be the default behaviour for FB_Object? If not, should there be another object like FB_LinkedObject? Hence the final implementation would include FB_Object (resembling current FB_OrphanObject) and FB_LinkedObjects (resembling current FB_Object)

Does @Colho have any thoughts on this?

If we are keeping FB_Object as a generic object, that can and will be used as part of data structures, the FB_Object should only contain the basic functionality of a generic object. Functionality for linking objects together should be the responsibility of the higher level data structure, or then another object inherited from FB_Object, as you suggested.
On my opinion inheriting FB_LinkedObject from FB_Object as a separate class is the way to go here, and that can be used if needed. Having the possibility to link generic objects by themselves only enables the user to link something that should not be linked. For example using a list, which consists of FB_Objects, which are then again linked to another FB_Object, totally unrelated to the list. This would result in quite funky data structures.


feat: remove node 8 support

As Node 8 as already reached EOL, it would be better to support newer versions of Node (from 10) where it's possible to use the fs promises API and also helps not supporting outdated Node versions.

Thanks for contributing, but I do not see a reason why we should drop support for node 8 when it does not limit library functionality.
I will merge it when there will be more breaking changes...


A few questions about the details

Hi, congratulations on the great work! The results are really impressive.
I have a few questions regarding the implementation details, and wish you could help:

In Section 4.2, how do you calculate $\tilde n$ from $(n, o)$? Is it by concatenating since you directly downsample $\tilde n$ to 4-channel latent code? I also wonder the reason behind this step, since normal + visibility mask seems unrelated to the latent code.
For DMTet's network $\Psi(v_i)$, do you use any positional encoding on the input vertices? Or do you only use 3-channel xyz so the MLP is just 3-32-4?
In each iteration you use a large batch size of 24 cameras, could this be different from only using a  single camera per iteration?
Do you use any direction-augmented prompt like appending front/side/back/top view?

Finally, is there an expected date for code releasing?
Thanks in advance!

Hi, @ashawkey! We are incredibly grateful for your stable-dreamfusion project. Part of our code is implemented based on your work. I will answer your questions in the following.

Yes, it is. During the experiment, we observe that directly inputting rendered images to stable diffusion resulted in the network producing results that match the text description in visual effects, and it tends to fall into local optima and have very rough geometry, leading to fraudulent outputs. Therefore, we need features that could respond to geometric information, such as normals and masks. We choose to use normals and masks as latent code because the range of normalized normal values is exactly (-1,1), which is the data range required for latent space diffusion, and masks can reflect the contour information of objects. It is worth noting that in the early stage of optimization, we can quickly transform the ellipse into a rough target shape by concatenating the mask and normal and sending the downsampling results to the stable diffusion (without using an encoder at this time). In the later stage of optimization, using only high-resolution normals can increase geometric details, and an encoder is required for this phase.
We use hash-grid positional encoding for both the geometry and appearance modeling.
The larger the batch size used, the faster the results can converge. With large batches, the geometry updates can be monitored from a global perspective as much as possible during each iteration.
For objects with obvious directionality, we use the appending prompt like front/side/back view. We avoid using the "top view" prompt, as it can hinder the convergence of results. Conversely, for objects without clear directionality, we discard the direction-augmented prompt altogether.
Due to other things, we are currently unable to provide an accurate timeline for publishing the code. However, we will make every effort to organize and release the code as soon as possible.

I hope the answers provided above can be helpful to you. Thank you for your attention to our work!

Thanks for the detailed explanation! It solves my questions clearly.
Looking forward to the code releasing!

Well, I wonder whether you tested representing the DMTet sdf value and vertex deformation with a tensor instead of an MLP mentioned in the paper. if so, can it produce plausible result in geometry learning?

Well, I wonder whether you tested representing the DMTet sdf value and vertex deformation with a tensor instead of an MLP mentioned in the paper. if so, can it produce plausible result in geometry learning?

Sorry for the late reply! We once optimized the SDF value and vertex deformation without using MLP prediction and found that the mesh quickly diverged.

Truly polite indeed :)
Recently I tried the hash grid MLP but achieved poor results...If possible I would like to ask for some advices.
The first problem is the stability of the mesh optimization process. If I increase the weight of sds loss, the mesh will be empty after a few iteration. Have you encountered such circumtance?
The second is the quality of the result. With low sds loss weight the optimization can go on, but the resulting mesh is always quite noisy regardless of different regularization I tried. Would you like to share some important detail of the geometry optimization process?
Great thanks!

Truly polite indeed :) Recently I tried the hash grid MLP but achieved poor results...If possible I would like to ask for some advices. The first problem is the stability of the mesh optimization process. If I increase the weight of sds loss, the mesh will be empty after a few iteration. Have you encountered such circumtance? The second is the quality of the result. With low sds loss weight the optimization can go on, but the resulting mesh is always quite noisy regardless of different regularization I tried. Would you like to share some important detail of the geometry optimization process? Great thanks!

You can try this preliminary reproduction of our work. 😉

Thanks for the notification!


Enable YAML casing validation

[x] Enable YAML casing validation

AC at:
https://app.zenhub.com/workspaces/the-outlaws-6193fe815d79fc0011e741b1/issues/gh/energinet-datahub/the-outlaws/966

Codecov Report

Merging #1609 (427a1b0) into main (c3c84f6) will increase coverage by 13.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #1609       +/-   ##
===========================================
+ Coverage   18.55%   31.59%   +13.03%
===========================================
  Files          64       79       +15
  Lines        1520     1836      +316
  Branches      144        0      -144
===========================================
+ Hits          282      580      +298
- Misses       1229     1241       +12
- Partials        9       15        +6

see 19 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add support for 少数派 metrics

Currently, there is follower counts support in Substats.  It would be nice if it support metrics such as read counts, word count, etc.

You can easily fetch said metrics from SSPAI's own API without authentication if you want:
GET https://sspai.com/api/v1/user/slug/info/get?slug={user_id}

Substats' main purpose is to fetch the number of fans / followers and provide a easy-enough interface to add them up (hence the feature introduced in Multiple sources with a single query string). Although there are some exceptions (like the Reddit Karma and Jike highlights...), I don't think I'll be adding these specific metrics from SSPAI to the Substats' API. Thanks for understanding.

Another reason why I specifically included Jike's metric and not SSPAI's metrics is that SSPAI's API is simple enough to use directly with Shields.io but Jike's stats require a bit of hacking and definitely requires a third-party proxy service.