Windows 2012 server were .net 4.8 won't repair. How do i fix that

I have a patched Windows 2012 machine. I'm getting a communications error - System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. This is happening when a web application I wrote tries to access a SQL Server at the hosting provider Arvixe. I don't get the error on windows 10 machines. Anyway.. doing a little digging most suggest that i need to run .net 4.8 on the 2012 machine. The issue i'm having is that .net 4.8 says it's installed. The .net repair tool says it's installed but not correctly. So i can't install it again and it's not working correctly. .net 4.8 is not one of the unisntall programs under the add remove programes like some of the other .net versions are. I've included what powershells Get-WindowsFeature net shows in case that is helpful.
Can anyone give some advice on hot to get 4.8 working on this machine. Thanks

Hey shannon32,
Thanks again for contacting Microsoft, we value your feedback.
You have described an issue with a product or service rather than our documentation. Please see our GitHub content feedback guidelines. As this is a non-documentation issue, we’ll now be closing this thread.
Thank you and have a most pleasant day.
#please-close


Binance.US: added exchange support

since Binance and Binance.US share the same API, they inherit from BinanceGroupCommon
this is similar to the refactoring in OKGroup #418
fixed bug in ExchangeGlobalCurrencyReplacements in BitBank
added trade stream (websockets) support for Binance DEX
unfortunately, Binance DEX doesn't share the same API as Binance and Binance.US
now that a new ExchangeBinanceDEXAPI class is created, others are free to contribute additional implementation details

Thanks so much for sharing this code. Any change we can make the Binance specific models internal?


Remove collaborator emails#428

Added collaborator's email inside the if loop.
If the author has logined, then show the collaborator's email.

Coverage remained the same at 83.996% when pulling 9e1d4fdd26f7db1a14b10d58534c430255e3e4d3 on Sahaj8:remove-collaborator-emails#428 into c3c4d787783ea04c171e5ceec8c2b2e472baa6d3 on CircuitVerse:master.

Great

Thanks for the contribution @Sahaj8 ! :tada:
You seemed to have made two commits for this change, could you squash them into one?


[requested functionality] Enable crosshair to auto-align to x-values of multiple line series.

I have a line series with a crosshair on a single XYFlexiblePlot, that uses time x-values. When I add another line series with a different set of x-values to the plot, the crosshair only auto-aligns to one set of x-values. So the crosshair shows up for all the points in the first line series, but not the points in the second line series. When I remove the first line series, the crosshair then correctly auto-aligns to the x-values in the second line series.
I want a single crosshair to show up for all x-values in either line series. Is there currently a way to do so? If not, would it be possible to add this functionality?
Two potential ways to achieve this functionality:

Allow user to pass in a custom "data" prop to the Crosshair component, that is used for auto-aligning the crosshair.
This prop, if passed in, would override the results of getAttributeFunctor(this.props, 'x');, which is currently used in react-vis/crosshair.js to get the x-values. In the case described above, I could pass in the combined set of points from both line series to allow the crosshair to auto-align to all points displayed by either line series.

Expand the getNull atrribute of the LineSeries component.
Currently, based on the boolean returned from the function passed to this attribute, the line series handles a null y-value by either displaying the point with a y-value of 0, or not displaying the line at all over that point (ie, displaying two line segements terminating at the points before and after the point with the null y-value). This attribute could be reworked to allow an additional case: if a y-value is null, do not display the point, but display a line segment from the previous point to the next point.

I think you could actually do this without modifying the codebase! The way I generally approach multiple line problem mouse over problems is by making voronois.  in this article I give a really extensive discussion of this exact topic (I know it is real pretentious to link to one's own medium articles, but what can you do ugh).
The TLDR is that you can place voronoi points in place where you want your user to interact with them, and position so that things are just as you desire.

I'm gonna close this but feel free to reopen if you like


Add display title customization

Changes included in this PR:

The ability to customize display title for entries (e.g. series or episode).
Episodes now store both the episode and the series id, because we need the series info to figure out the COO (country of origin).
When viewing metadata of a series, episode, movie or movie box-set (the last two types will be added in another PR), the id for AniDB and both ids for Shoko associated with the entry will be shown under "External IDs".

Besides the white-spaces, I think it's ready to merge now. Please review.

You don't need to separate the provider into two (Shoko Series and Shoko Episode).
One, it breaks the existing libraries if someone tries to update episode before updating series.
Two, it's already being stored, so access it directly. You can get series ID using info.SeriesProviderIds.GetValueOrDefault("Shoko") in the episode provider

and what is the use of this ExternalIds class? I'm just asking because I don't know.

I separated the series id and episode id because I use both for a single movie, and also because I plan on adding the file id for both episodes and movies to keep track of the resume-time and watch state (on a per file/item basis and not on a per episode, or on both a file and episode basis).
The IExternalId is used to display the IDs in the metadata view. It's more of a sugar addition for the curious and for development when quickly checking the the related API endpoints using those ids directly.
Below are examples of where they show up:
Episode view:

Series view:


Image and Buffer read

Hello please look at providing image and buffer data as part of cgltf_data.
Having said this, Is the image and buffer data part of cgltf_data when reading a GLB file.
Thank you!!!

cgltf_load_buffers can be used to load buffer data.
There's currently no way to load image data; OTOH it's not clear what exactly is the best way to do this - loading raw encoded image data in, say, PNG format as a set of bytes isn't useful, and adding a dependency on a third-party image loader is against the dependency policy of this library. So it'll have to be some sort of callback API, but the callback has to be able to load both from memory (in case image data is embedded) and from file.

Hello, please consider embedding third party image reading sources, like jsmn source embedded currently.
This is the only reason why I am stuck with using tinygltf, the compile time for that one file which uses tinygltf is more than the entire solution combined.

Hi @amadlover, you can easily use a third-party image loader in combination with cgltf, there is nothing preventing you from doing that yourself in the application.
For example, in Filament we use cgltf combined with stb_image.

@prideout thank you for pointing it out.


SAM_Molmo_Whisper requirements.txt out of sync with SAM2 requirements

Any chance requirements.txt could be updated?
Because SAM2 was updated after SAM_Molmo_Whisper there are some versioning problems with torch*.
When installing on a fresh machine, I'm getting version conflicts with torchaudio leading to errors like this:
Thanks.
Traceback (most recent call last):
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/gradio/queueing.py", line 622, in process_events
    response = await route_utils.call_process_api(
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/gradio/route_utils.py", line 323, in call_process_api
    output = await app.get_blocks().process_api(
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/gradio/blocks.py", line 2014, in process_api
    result = await self.call_function(
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/gradio/blocks.py", line 1567, in call_function
    prediction = await anyio.to_thread.run_sync(  # type: ignore
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/anyio/to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 2505, in run_sync_in_worker_thread
    return await future
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 1005, in run
    result = context.run(func, *args)
  File "/opt/conda/envs/SAM_Molmo_Whisper/lib/python3.10/site-packages/gradio/utils.py", line 846, in wrapper
    response = f(*args, **kwargs)
  File "/root/verb-workspace/SAM_Molmo_Whisper2/SAM_Molmo_Whisper/./app.py", line 92, in process_image
    transcribed_text, prompt = get_whisper_output(audio, transcriber)
  File "/root/verb-workspace/SAM_Molmo_Whisper2/SAM_Molmo_Whisper/utils/model_utils.py", line 76, in get_whisper_output
    sr, y = audio
TypeError: cannot unpack non-iterable NoneType object

I will check and update here.

@medatasci Can you please let me know what version of PyTorch you are using?
I just went through the SAM2 repo and saw that the minimum version has been updated from 2.4 to 2.5 now. I will see to the issues and push an update as soon as possible.

@medatasci An update.
I checked that the recent changes had requirement issues. I have updated all requirements to match SAM2. Please install everything in a new conda environment with Python >= 3.10. It should work.
I am closing the issue for now. Please re-open if you face issues.

Thanks for the really prompt bug fix, much appreciated.
Images are working well.
I had some trouble with videos and submitted a new issue.  Could it be caused an updated SAM2 API?
Marc
From: Sovit Ranjan Rath @.>
Sent: Saturday, December 14, 2024 8:46 PM
To: sovit-123/SAM_Molmo_Whisper @.>
Cc: Marc Edgar; Mention @.***>
Subject: Re: [sovit-123/SAM_Molmo_Whisper] SAM_Molmo_Whisper requirements.txt out of sync with SAM2 requirements (Issue #8)
Closed #8https://github.com/sovit-123/SAM_Molmo_Whisper/issues/8 as completed.

Reply to this email directly, view it on GitHubhttps://github.com/sovit-123/SAM_Molmo_Whisper/issues/8#event-15658909022, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWISOXJ75ZY7KSPN4HDIQCL2FTNPJAVCNFSM6AAAAABTT2KMVKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGY2TQOJQHEYDEMQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi. I have given an initial reply in the video processing issue that you created. Let's continue the conversation there.


[WIP] Set physical range to digital range for stim channels

Fixes #5159. This is a long shot, let's see if other things break.

I ran the EDF tests locally, and test_edf_stim_channel fails in line 267 (assert_array_equal(true_data[-1], edf_data[-1])). However, I'm not sure if the text file (true_data) actually contains the true data, because even in master the data of the regular channels are not identical in the two arrays (but the stim channels match).

Forget my comment about the data not being equal, I just saw that you have to multiply them by 1e-6.

In the test file from #5159, the stim channel gets scaled so that data[stim_channel_idx].min() is 41009.076118414174 and data[stim_channel_idx].max() is 41009.16551108155. Then the array is converted to an int array in lines 318-319, which is why all values are identical to 41009.
Does anyone have a suggestion what we could do in such a situation?
In addition, I have no idea what the bitwise and with 2**17 - 1 does...

I can scale the stim channel up if the difference between max and min is less than 1. This actually seems to work and doesn't require tinkering with the physical/digital min and max. All EDF-related tests pass on my local machine.

Determining data scaling based on the contents of the data is dangerous. For one example, your code here will break if the max and min of the data are the same (though this can be fixed with a conditional). For another, consider if one file has only trigger value 1, another has only a value of 100, and a third file has both 1 and 100. These will be messed up, right?
The information to scale properly is not located anywhere in the file itself?

The information is in the file header, but for whatever reason even the stim channel gets rescaled. This results in values that differ only in the fifth decimal place, so converting that to int yields identical values.

Regarding your points, if the minimum equals the maximum there are no events we can extract. Also, I'm only rescaling if the difference between max and min is less than 1, so your example would not be a problem. My thinking was that there must be something wrong if the stim channel values differ by less than 1.

Also, I'm only rescaling if the difference between max and min is less than 1, so your example would not be a problem.

I guess I'm really getting at "do we have a way to know that this will this always work for people"? Can a file reasonably have values at that point in the code with a peak-to-peak of 0.9999? Of 1.00001? If both of these are possible, do these depend on the actual triggers that were used during acquisition? If so, then this code will not work robustly.
However, if we are guaranteed that exclusively 1) values are encoded as float-like between 0 and 1 or 2) values are encoded as integers, then some variant of what you have (triaging based on peak-to-peak) will probably work. If we do not have this guarantee, then I don't think it will. Agreed?
And if the answers to these questions are "we don't know", then I think we're taking a risk implementing another EDF fix that might fix one thing and break another. Perhaps instead we shouldn't do any int casting, and instead warn if the data are not already int-like until we can figure out what the right thing is to do based on the EDF trigger format / specs.

Absolutely, this is definitely a bad hack almost guaranteed to break other files. The problem is that this is an ordinary data channel, so it is not standardized at all. As long as there is some way to derive events via differentiation (i.e. at time instants when values change), everything is possible. This is not the dedicated annotation channel labeled "EDF Annotations", which we already parse separately.
Converting to int seems like a bad idea in this case. Also, I am still clueless why it is then and-masked with 2**17 - 1. Biosig can parse this channel correctly as events. Maybe something you could help us out @holgern?

Do they not limit their events to be integer values? Then nothing magical should need to be done.
Or you mean they don't have this weird scaling issue, and do have integer values (or at least nicer floats)?

I don't know, I think they also have integer event codes. Biosig seems to treat this channel differently, maybe based on the channel label (it is called "Status").

Yes, I can confirm that BioSig treats channels labeled "Status" in a BDF file as event channels, which means that they don't show up as data channels at all. There is even a dedicated function bdf2biosig_events that converts a BDF Status channel to events (using one of various modes).
How do we want to proceed? It might be a good idea to mimic what BioSig does, i.e. treat "Status" channels differently (given that the stim_channel argument is set to 'auto' or to a specific channel label/index).

sounds fair to me

I'm now scaling only data channels after processing the stim channel. This seems like the right thing to do, and it does work with the test file by @ElBibulo. Here, we now get exactly the values he was expecting (1, 2, 3, and 4).
However, this means that event values might change for other files, such as in test_edf_stim_channel, which expects values 0 and 100, but the reader now produces 98304 and 32767. I'm not sure how to proceed.
Either we interpret a channel as a data channel - then we apply the necessary scaling. Or we interpret it as a stim channel, then the scaling should not matter because we're converting the channel to int anyway. But we can't extract events from a scaled data channel (in general), which like in this example file has values that differ in the fifth decimal place due to scaling (and we are converting stim channels to int).
I have no idea why this channel gets scaled like that, but that's what's in the header. EDF does not restrict scaling of stim channels to 1. In fact, EDF doesn't even define stim channels.
Ideas?

Should we scale EDF but don't scale BDF Status channel?

If you want to define a channel as a stim channel, you shouldn't expect to get any specific values

I'm surprised by this. Is this some peculiarity of EDF/BDF? With the systems I'm used to, you know exactly what trigger values are stamped during recording, and should expect that stim channels will accurately reflect them.
Maybe we should look at what values pyedflib or other libraries give for these files. It's possible they know something about the formats that we don't.

Biosig doesn't find any events in test_edf_stim_channel.edf. Instead, it interprets the last channels as a normal data channel, and the values are what we expect (0 and 100) because a data channel gets scaled according to the header settings.
In the case of test.bdf that started this discussion, Biosig recognizes the channel labeled "Status" as an event channel. The values of the events are coincidentally mapped to 1-4, which in this case is what we expected. But I think this is because events that are not recognized by Biosig are always mapped to numbers starting at 1.
We have a Biosemi amp, and sometimes there is an offset of some power of 2 value that I need to subtract before I get the expected values. And yes, this is a peculiarity of file formats that store events in a data channel. A much better option is a dedicated event channel, such as in GDF or EDF+, where events are really treated as events.

We have a Biosemi amp, and sometimes there is an offset of some power of 2 value that I need to subtract before I get the expected values.

FYI mask and mask_type='not_and' in find_events will do this sort of thing for you. Basically it means that there is some bit that is always "on" in your data. Bit-masking is a little bit safer than subtraction because it also works if the bit turns on and off (instead of always staying on).

And yes, this is a peculiarity of file formats that store events in a data channel. A much better option is a dedicated event channel, such as in GDF or EDF+, where events are really treated as events.

I'm not clear on what makes events stored in a "data channel" vs events stored in a dedicated "event channel". In Neuromag (and it sounds like Biosemi), the TTL pulses are encoded converted to integers and stored some channel (or multiple channels), but this channel (or these channels) are no different from other channels in terms of how data are stored, scaled, etc. They just receive a different type in the meas info, and are useful because they contain integers.
Thus if the file is written correctly (with correct scaling factors, etc. based on how the data are stored internally), nothing special needs to be done.

Biosig doesn't find any events in test_edf_stim_channel.edf. Instead, it interprets the last channels as a normal data channel, and the values are what we expect (0 and 100) because a data channel gets scaled according to the header settings.

This is what we try to do -- and seems like the correct thing to do -- in MNE as well, at least according to my interpretation above. In this sense, instead of "doesn't find any events" I would say "does not do anything special to the channels to deal with events", as the events are still there and encoded properly / in the standard way.
There are other formats that have events stored using discrete markers (e.g., Brainvision, maybe also GDF and EDF+?). In MNE we do some work to convert these to the integer-values-in-a-data-channel representation so that find_events will usually work. But I don't think that's what we're talking about here.
From what I can tell, the problem is that some files put in bad scaling values so that the channel that is supposed to encode integers related to TTL pulses during the experiment do not write the scale factors correctly, so we end up with non-integer values in the channel.
If this is true, and we know that the BDF "Status" channel always (or hopefully almost always) has this property that the scale factors don't make sense, then it seems like the right fix to treat the "Status" channel in a special way.

FYI mask and mask_type='not_and' in find_events will do this sort of thing for you. Basically it means that there is some bit that is always "on" in your data. Bit-masking is a little bit safer than subtraction because it also works if the bit turns on and off (instead of always staying on).

Yes, by subtraction I really meant I am applying some mask until I get the desired values.
I prefer to treat events and data channels as different entities. I don't really like the concept of trying to coerce discrete markers into a continuous stim channel. Why do we have to invent a new channel when all we need are the events? This can lead to inconsistencies as we have seen in the output of mne.find_events and edf.find_edf_events. But some systems, including Biosemi, only work with events in a regular data channel, so we can't get around this problem.
You are right that if the scaling values in the file header are correct, we should get the expected integer values that we recorded. And you are also correct that in this BDF file, the scaling values are apparently bad, which leads to float values. But there is nothing in the specs that tells us that the scalings are bad. This is what I was trying to do by setting the scaling to 1 if I get floats, but we agreed that this was a pretty unstable solution.
We already have the argument stim_channel for the user to specify which channel should be interpreted as a stim channel. If we set stim_channel=None, we do nothing special. If we set it to 'auto', we can take the last channel (or I can add code that chooses channel "Status" if it exists in BDF files). But then what do we do with this stim channel? Do we scale it as per the information in the header, which doesn't work if the scaling is wrong? Other toolboxes such as Biosig seem to derive event information from the stim channel in its unscaled form.

I prefer to treat events and data channels as different entities. I don't really like the concept of trying to coerce discrete markers into a continuous stim channel. Why do we have to invent a new channel when all we need are the events? This can lead to inconsistencies as we have seen in the output of mne.find_events and edf.find_edf_events. But some systems, including Biosemi, only work with events in a regular data channel, so we can't get around this problem.

I would agree if I were starting a package and file formats from scratch. But this is how we currently do things in MNE-Python, and how we write files (in the FIF format spec). We can have a bigger conversation about the refactoring necessary to move away from this elsewhere, but it's out of scope for fixing this issue. So for here it seems most productive to stick with the concept, flawed though it may be, that we should try to shoehorn each format into a FIFF/Biosemi/EDF-like encoding of events as integers in a channel.

But then what do we do with this stim channel? Do we scale it as per the information in the header, which doesn't work if the scaling is wrong? Other toolboxes such as Biosig seem to derive event information from the stim channel in its unscaled form.

How about we add an argument stim_scaling='auto' (default) | True | False. 'auto' means True (use header values just like for all other channels) for anything other than "Status" channel in a BDF file. False means "do not scale". It seems like this would make all of our test files "just work" and for unknown cases we will inevitably hit, we have given people the option to scale or not.

Agreed, we should focus on fixing this issue. I don't really have the time anyway to completely refactor how events are represented ATM.
I like your idea of introducing a new argument! This seems like a great solution! I'll push an update to this PR ASAP.

In the code where you implement it, could you put in a mention of gh-5160 in a comment? Future @cbrnr and @larsoner will probably appreciate it when looking at the spaghetti code we are making :)

Sure, will do :smile:!

five years later (https://github.com/mne-tools/mne-python/pull/832) I am still haunted by the EDF format 👻
to echo @larsoner, the TTL pulse into the data channel used to be (and still is) a convention for reporting out event markers in the data. I agree that annotations or integer values are the best but a lot of setups still rely on this method.
we should still have a suite of irregular edf files. we should make sure to check against them

@teonbrooks file formats are a nightmare! I'm sure someone will come back to me in five years regarding either this or some other "feature" I've added to our readers... 😵
@larsoner, are you OK with adding the new argument stim_scaling to BaseRaw._read_segment_file and the overridden method in RawEDF? If yes, I'll also add it to read_raw_edf and RawEDF.__init__, and the best position for the new argument would be right after stim_channel. Or do you want me to add it at the end right before the verbose argument?

I don't know, I feel a bit uncomfortable changing such a widely used class. We could also just implement this behavior (scale stim channels for EDF, don't scale for BDF) by default and fix it when the next file breaks.

@teonbrooks https://github.com/teonbrooks file formats are a nightmare!

well FIF is complicated but files are a lot more consistent and unambiguous
to read.

Looks good so far, ready to merge when all Travis jobs are happy!

So no need for a new parameter now?
Instead of triaging during this indexing operation, would it be cleaner for BDF stim channel to ensure that the scale factors are set properly to not scale the data?

So no need for a new parameter now?

This would involve changing a method in the base class (at least its signature), but I don't think this is a good idea since this seems to be a BDF-related peculiarity.

Instead of triaging during this indexing operation, would it be cleaner for BDF stim channel to ensure that the scale factors are set properly to not scale the data?

You mean setting cal and gains to 1 and offsets to 0 for the stim channel? I'm not sure if this is cleaner, the way it's done now ensures that the original scaling values from the file header are at least accessible.

This would involve changing a method in the base class (at least its signature

It shouldn't involve any change in BaseRaw if that's what you mean. Each reader can put arbitrary data in _raw_extras and use it whenever they need to.-

You mean setting cal and gains to 1 and offsets to 0 for the stim channel? I'm not sure if this is cleaner, the way it's done now ensures that the original scaling values from the file header are at least accessible.

The idea is that for BDF we can/should probably think of these values as being incorrect, as they scale things incorrectly. In that sense, it makes sense to correct the problem by changing the errant scale factors rather than introducing a conditional about what scale factors to apply during the reading phase. But it probably doesn't make too much difference.

It shouldn't involve any change in BaseRaw if that's what you mean. Each reader can put arbitrary data in _raw_extras and use it whenever they need to.

You're right, this would have been necessary only if we'd added a new argument to _read_segment_file - then I think we'd had to add that to the super method as well, right? Since a new argument is not necessary, this issue has been resolved for me.

The idea is that for BDF we can/should probably think of these values as being incorrect, as they scale things incorrectly. In that sense, it makes sense to correct the problem by changing the errant scale factors rather than introducing a conditional about what scale factors to apply during the reading phase. But it probably doesn't make too much difference.

Right, I can do it either way, the result will be identical. But I wouldn't correct the scale factors in the _raw_extras dict, because people might want to apply the (possibly errant) scale factors for whatever reasons. So in the if subtype == 'bdf' I would then set cal, offsets, and gains to 1 and 0, respectively, so this would merely be an internal implementation detail.

@larsoner @agramfort do you want me to change anything? Otherwise I think this could be merged (and I'd also backport it to 0.16).

is it bug fix ? or API change? it seems more an API change so I would not backport.
can we add a test for this?

This is a bug fix, I didn't change the API. I'll add a test, the best thing would be to add the problematic BDF file. I have to find/create a small file, because I guess we don't want to add another 15MB just for this test.

@cbrnr do you have time to make this tiny file?

I found a bug related to reading with preload=False, this is fixed (and I've added a test). I've also cropped the BDF file from @ElBibulo (it contains only 3 data and 1 stim channel, and is only 20 seconds long). @ElBibulo could you please give us permission to use your file (heavily cropped, see the Files changed tab)?
If @ElBibulo agrees and CIs are happy, this is ready to be merged.

can we avoid putting a new binary file in the repo and put the file in mne-testing if we have permission?

Yes, I can certainly do that.

@agramfort but note that the file is only 61kB. I know that we want to move all test files out of the main repo, but currently this means that I have to download the whole test data repo, which is almost 1GB. See also #4926.

or fair enough. 61kB is really small.
ok for you @larsoner
@cbrnr can you see why travis complains?

I put it in mne-testing-data, PR forthcoming to this branch to bump to 0.49

Let's just make sure we get permission to use this file. And let's discuss how to proceed in the future in #4926.

(for some reason I could not make a PR to your branch)

Let's just make sure we get permission to use this file. And let's discuss how to proceed in the future

Sure but in the meantime I don't want to add more files to mne-python. Until we make this decision I think they should live in mne-testing-data. It sounded like your opposition to doing this here was mostly that it involved downloading a lot of data on your machine, which you no longer have to deal with because I did it instead. (You can mirror the changes locally just by copying the file over to the right place.)

Thanks @larsoner. Yes, downloading the whole repo is really unwieldy. Thanks for solving this for this issue, but the problem remains in general. Now I can't run the test without the huge download.

it's not so huge... and it's a git repo with incremental updates. Also this
tells me that you don't have the testing data on your system to run the
tests locally?

Now I can't run the test without the huge download.

See my comment above as:

You can mirror the changes locally just by copying the file over to the right place.

In other words, move the file that you had in io/edf/tests/data to MNE-testing-data/BDF/.
For devs who needs latest updates often and doing the 1GB download with python -c "import mne; mne.datasets.testing.data_path(force_update=True, verbose=True) in the background is untenable, you can also incrementally update locally by downloading files from commits rather than updating everything. It is manual work but shouldn't take more than a minute or two.

@agramfort yes, basically because every time I tried downloading the repo from GitHub it was super slow. So yes, I don't run all tests locally 😺 (thanks Travis!).
@larsoner I see - manually moving a file to a different folder is tenable for running specific tests. Re your latest comment, the problem was getting a complete checkout once. Updating should be straightforward afterwards.
All in all, it is OK, but any improvement to make this process easier would be highly welcome.

OK, ready to merge. Ideally, we should get permission to use this data set, but it seems like @ElBibulo isn't responding anymore. In any case, the data is heavily cropped, and already in the other repo.

Sorry i missed your first request. Of course you can use the data :)

Great, thanks @ElBibulo!

@larsoner please feel free to merge, I'm all set.

Thanks @cbrnr


Dockerfile: Set path and target via ENV

Set $PATH and $CARGO_TARGET_DIR via the ENV instruction. This allows us
to drop the path from all subsequent RUN and CMD invocations which is
quite nice.
By setting a custom $CARGO_TARGET_DIR we avoid trouble with local IDEs
and such that would otherwise share the same directory as the container,
blocking and invalidating each other.
Jira:^H^H^H^H^H Hahaha, this isn't Gerrit.

No. This is not Gerrit.


possibility to change list view by icon

Hello, good afternoon, I'm new using filegator. I would like to know if there is a way to change the list view by icon.

Hi,
I'm not sure what do you mean here, to change what exactly?

view attachments or documents in icons like this

Ok, I see, you want to toggle between different layouts and you want to be able to preview file contents.
This is not supported but let's leave this here as a feature request.
Thanks

refs #98 #92


2.0.6 fails to dump any couchdb

{"version":"1.2.9","db_type":"http","start_time":"2017-06-12T19:21:25.665Z","db_info":{"db_name":"ceshhar-init","doc_count":9,"doc_del_count":1,"update_seq":12,"purge_seq":0,"compact_running":false,"disk_size":5509231,"data_size":5419807,"instance_start_time":"1497266954301576","disk_format_version":6,"committed_update_seq":12,"host":"http://localhost:5984/ceshhar-init/","auto_compaction":false,"adapter":"http"}}
db.type() is deprecated and will be removed in a future version of PouchDB
db.type() is deprecated and will be removed in a future version of PouchDB
unexpected error
{ [Error]
result:
{ ok: false,
start_time: Mon Jun 12 2017 22:21:25 GMT+0300 (EAT),
docs_read: 0,
docs_written: 0,
doc_write_failures: 0,
errors: [],
status: 'aborting',
end_time: Mon Jun 12 2017 22:21:25 GMT+0300 (EAT),
last_seq: 0 } }
undefined
Rolling back to 2.0.0 seems to work fine.

I can confirm downgrading to 2.0.0 solved similar issues for me.

Ran into the same issue. Downgrading to 2.0.5 worked for me.


Prevent provisioning of persistent volumes on nodes with an empty paths list

Hi,
I have a cluster with two nodes:

the first node is home to deployments using local-path-provisioner (aka first.example)
the second node (aka second.example) was recently added to try to add room for deployments that do not need a persistent volume.

local-path-provisioner has been configured to have an empty paths list for nodes others that the first node:
    {
            "nodePathMap":[
            {
                    "node":"DEFAULT_PATH_FOR_NON_LISTED_NODES",
                    "paths":[]
            },
            {
                    "node":"first.example",
                    "paths":["/opt/local-path-provisioner"]
            }
            ]
    }

However, it seems that local-path-provisioner is trying to create persistent volumes on the second node:
error syncing claim "e0b17b36-47e5-416f-a4c7-5eada4db8165": failed to provision volume with StorageClass "local-path": no local path available on node second.example

My guess is that local-path-provisioner is not responsible for that choice, and that it's just a "fail-safe".
If one node is listed but with paths set to [], the provisioner will refuse to provision on this node.

The node is selected by the scheduler for the volume:
/* vendor/sigs.k8s.io/sig-storage-lib-external-provisioner/controller/volume.go */

// ProvisionOptions contains all information required to provision a volume
type ProvisionOptions struct {
	 /* ... */
	// Node selected by the scheduler for the volume.
	SelectedNode *v1.Node
}

But the pod that interacts with the persistent volume claim is not yet scheduled on a node (status Pending), maybe Kubernetes misses a mechanism for solving such case.
With a nodeSelector on the pod, the persistent volume is correctly created.
If I am correct, this issue can be converted into a documentation issue and I'm willing to add a sentence for that case.

Kubernetes v1.18.9
rancher/local-path-provisioner:v0.0.17

Yes, local-path-provsioner adopts WaitForFirstConsumer volume binding mode to wait for the consumer pod arranged. This is the native behavior of dynamic provision.
We will enhance the README a bit to make sure the case clear for the users.

I suggest that you use the nodeSelector on the DaemonSet to install the provisioner only at the nodes that actually has local storage.

Hi, I'm running in the same issue.

I suggest that you use the nodeSelector on the DaemonSet to install the provisioner only at the nodes that actually has local storage.
Could you be a bit more precise? Which DeamonSet are you talking about?

I'm not sure I understand why putting a path: [] for the default nodes shouldn't work. Am I correct in assuming that if you created manually a pair of PV/PVC, the pod that uses it will run on a node which is able to satisfy this claim? If so why shouldn't this work? I'd like to avoid having to use the nodeSelector on my pod.


Add support for filling layout

TODO

[x] Make sure this works with Quarto
[x] Do a test run through more widgets
[x] Make sure specified height/width works sensibly
[ ] Finish updating examples to leverage fill
[ ] Remove the examples/fill/app.py?
[ ] Clean-up/simplify resize logic
[ ] Make sure we aren't mutating objects
[ ] Update example requirements
[ ] Make it possible to opt out of fill in the output_widget

Follow up

[ ] Make sure @render.plot fills
[ ] Send PR to py-shiny to make ui.output_ui() a fill carrier

My only concern for the record--should not hold up merging--is that this is assuming that the vast majority of widgets are going to want to fill. This might turn out to be true, but if not, then we'll have to be ready to respond.


执行npm run build  后 生成的index.html没有js与css 导致页面空白

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>Framework version: 最新
Browser: chrome<IP_ADDRESS>

What is expected?
正常访问
Steps to reproduce
arco init mydemo
npm install
npm run build

@2011shao hi 可以参考一下 这个issue https://github.com/arco-design/arco-design-pro-vue/issues/225

@2011shao done v2.6.0


Fix tor

Current coverage is 87.17% (diff: 83.87%)

Merging #133 into master will increase coverage by 0.01%

@@             master       #133   diff @@
==========================================
  Files            20         21     +1
  Lines          3029       3142   +113
  Methods           0          0
  Messages          0          0
  Branches        450        466    +16
==========================================
+ Hits           2640       2739    +99
- Misses          291        302    +11
- Partials         98        101     +3

Powered by Codecov. Last update bcac0c7...9465ebc


[Interchange] necessity of the utility library triggers is missing in Interchange docs

I was experiencing some issues with Interchange and Foundation 6.4.3.
On resize, the images set in the arrays didn't get replaced. I did include all the libraries as mentioned in the docs below the 'JavaScript Reference' section.
When I started debugging in the foundation.interchange.js file, I noticed that the event resizeme.zf.triggers was called. After including the foundation.util.triggers.js file, interchange worked as it should.
Please add foundation.util.triggers.js to the 'JavaScript Reference' section of the docs of Interchange to make sure it's up to date again.

Hi @rianne-o,
can you provide a codepen which reproudces this and shows us this behavior / issue?

Hi @rianne-o,
can you provide a codepen which reproduces this and shows us this behavior / issue?

Hi @rianne-o,
thanks for reporting this.
We'll add it to the docs.

Cant you just update foundation.interchange.js to import the triggers and initialise them directly, as is done in OffCanvas, Sticky, DropdownMenu, Reveal, Tooltip, Slider or Toggler?


One swipe can sometimes register as more than one back/forward button press

Sometimes a swipe generates more than one click of the back or forward button. I tried reducing the sensitivity to see if this helps but that just changes the threshold of detection. I still see multiple back forward movements.
Perhaps there should be an option to only generate one back/forward event per swipe?

Happens especially often on Wikipedia

When I browse wikipedia pages, this addon sometimes goes back two wikipedia pages

I know why the bug happens: its because lastswipe is not persisted when navigating, every content script on every page has its own variables.

So when I go back on a page and the browser navigates back one page, if my fingers are still on the trackpad swipping, it will go back again, since the difference between Date.now() and last swipe variable is greater than 1000. (The lastSwipe variable is holding the value 0 or some old value on that page).

The way I know that is that I tested pasting window.history.back();
window.history.back();
window.history.back();
in the devtools console and the browser only went back one page, so its not the event triggering on one page repeatedly, but on diffferent pages, driving to the conclusion in the previous comment.

I wrote a fix for this, will prepare a pull request.
¨

Happy to hear that! Have tried to message the lastSwipe to previous pages to fix the issue with multiple navigation events.

Thanks to @artisticfox8 for fixing the issue with multiple navigation events.
Updated and pushed the add-on to Mozilla


Fixes: not working with OBS v28>, potential security issues from old dependencies. Improves: build size, performance, error handling, ui

Works with OBS v28 and newer
Defaults to autostart with VS Code, with improved timings
Defaults port to default obs-websocket port 4455
Reduced size considerably
New indicator icon (bottom right) showing whether the active file is being hidden or not
Removed connected/disconnected messages in order to avoid clutter when connecting and disconnecting
"Cut" transition fallback to a "Cut"-alike transition whenever Cut is not found. Will usually default to the equivalent of "Cut" on OBS setups where the locale isn't English

Feel free to try it out (the zip only contains the .vsix packed extension, github won't let me upload the .vsix itself because of the extension)
obs-switcher-0.1.4.zip

Hello, this was one month ago, I'll be independently publishing this in few weeks if I don't get any feedback

Thanks for your PR, @quiquelhappy.
Your work looks great, but I suggest keeping the default auto-connect function the same, as it may cause errors when OBS isn't running. Most users will likely encounter this scenario, so it's best to keep it false by default. Power users can modify it in the VS Code settings.
I'd merge this and perform a release if you're OK with that.

I believe it is ok to push, specially given that there are plenty of users with lack of support rn, in the future I may revisit this to provide better transition fallback and just polish some things here and there. Have a nice weekend.


Waypoints 2 and 3 in Basic HTML5 and CSS pass after only adding the closing tags

Waypoints 2 and 3 ( http://www.freecodecamp.com/challenges/waypoint-inform-with-the-paragraph-element ) in Basic HTML5 and CSS pass after only adding the closing tags for h2 and p elements respectively, without requiring the actual text "CatPhotoApp" and "Hello Paragraph" to be written between the tags.
The tests bellow the next challenge button indicate correctly that these are missing, but the "Go to my next Challenge" button is active and allows progression to the next chalenge.
Have a nice day and good luck fixing this. :)

I cannot reproduce this behavior. Provide screen cap perhaps?
To owners: has this been fixed and the issue not closed?

This seems to be an issue for me in all of the Basic HTML5 and CSS waypoints so far.
The "Go to my next challenge" button activates too soon, before the last one or two conditions/tests for the lesson are fulfilled. As can be seen in the above screencaps from "Waypoint: Import a Google Font": I have not completed the font-family attribute, between the brackets, in the style section, for the h2 element, but the site allows me to move on, nevertheless.
I'm using a Firefox web browser on Linux: Fedora. Maybe it's something that only happens in Linux?

You seem to have included your link element within your style element. It should be outside to begin with.
Perhaps the interpreter/validator crashes because of this?

Hello Jeff,
I don't think the validator crashes because of some code I write. It
just seems to activate the "Go to the next challenge" button too soon,
when you still have one or two tests left to pass. For example in the
"Waypoint: Create a Set of Radio Buttons" it did not activate until
there was only one test left, as can be seen from the screenshots
attached. Here the code is as it should be, but the name attribute is
missing.
Under Linux there have been many times that I have encountered sites
that don't behave as they should, but I don't think this here is ok, as
it lets lazy students pass without learning correctly.
Thank you for your input and have a nice day,
Ariadna
On 05.08.2015 00:22, Jeff Noel wrote:

You seem to have included your |link| element within your |style|
element. It should be outside to begin with.
Perhaps the interpreter/validator crashes because of this?
—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/freecodecamp/issues/1503#issuecomment-127765708.

@ariadna-m Is this still an issue?


[semver:skip] Fix misspelling in README Contribution guidelines

I'm assuming this was cargo-culted / copy-pasted from somewhere else where it might be good to also fix this, but I'm not sure where that would be, so I'm updating it here where I encountered it. 😉

@abernix This orb was generated from https://github.com/CircleCI-Public/Orb-Project-Template. Thanks for the heads up!


[crypto] Update x25519-dalek fork to remove duplicate version

Found this dupe dependency looking at this weeks dep changes. I fixed this upstream in the x25519-dalek fork https://github.com/novifinancial/x25519-dalek/pull/7 and this updates our Cargo.lock to pick up that change.

LSR dependency change summary:
target packages:
  M x25519-dalek 1.1.0 (direct third-party, external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#4d6e37cee0a2ae0d3df522b3c6286fab6ce607b6')
    * source changed from external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#dc82145d8d25529d8aecab93d3ddf7062a74c719'
    * (unchanged features: fiat_u64_backend, std)
  R curve25519-dalek 3.0.0 (transitive third-party, external 'git+https://github.com/calibra/curve25519-dalek.git?branch=fiat3#2940429efd0e6482af1531cff079e6605cbc9cf2') (other versions: 3.0.0)
    * (old features: alloc, fiat-crypto, fiat_u64_backend, std)

LEC dependency change summary:
target packages:
  M x25519-dalek 1.1.0 (direct third-party, external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#4d6e37cee0a2ae0d3df522b3c6286fab6ce607b6')
    * source changed from external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#dc82145d8d25529d8aecab93d3ddf7062a74c719'
    * (unchanged features: fiat_u64_backend, std)
  R curve25519-dalek 3.0.0 (transitive third-party, external 'git+https://github.com/calibra/curve25519-dalek.git?branch=fiat3#2940429efd0e6482af1531cff079e6605cbc9cf2') (other versions: 3.0.0)
    * (old features: alloc, fiat-crypto, fiat_u64_backend, std)

release binaries dependency change summary:
target packages:
  M x25519-dalek 1.1.0 (direct third-party, external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#4d6e37cee0a2ae0d3df522b3c6286fab6ce607b6')
    * source changed from external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#dc82145d8d25529d8aecab93d3ddf7062a74c719'
    * (unchanged features: fiat_u64_backend, std)
  R curve25519-dalek 3.0.0 (transitive third-party, external 'git+https://github.com/calibra/curve25519-dalek.git?branch=fiat3#2940429efd0e6482af1531cff079e6605cbc9cf2') (other versions: 3.0.0)
    * (old features: alloc, fiat-crypto, fiat_u64_backend, std)

@davidiw @mimoo any chance you can look at this?

looks like it is still blocking, I think this needs both my and @davidiw approval?

/land

LSR dependency change summary:
target packages:
  M x25519-dalek 1.1.0 (direct third-party, external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#4d6e37cee0a2ae0d3df522b3c6286fab6ce607b6')
    * source changed from external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#dc82145d8d25529d8aecab93d3ddf7062a74c719'
    * (unchanged features: fiat_u64_backend, std)
  R curve25519-dalek 3.0.0 (transitive third-party, external 'git+https://github.com/calibra/curve25519-dalek.git?branch=fiat3#2940429efd0e6482af1531cff079e6605cbc9cf2') (other versions: 3.0.0)
    * (old features: alloc, fiat-crypto, fiat_u64_backend, std)

release binaries dependency change summary:
target packages:
  M x25519-dalek 1.1.0 (direct third-party, external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#4d6e37cee0a2ae0d3df522b3c6286fab6ce607b6')
    * source changed from external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#dc82145d8d25529d8aecab93d3ddf7062a74c719'
    * (unchanged features: fiat_u64_backend, std)
  R curve25519-dalek 3.0.0 (transitive third-party, external 'git+https://github.com/calibra/curve25519-dalek.git?branch=fiat3#2940429efd0e6482af1531cff079e6605cbc9cf2') (other versions: 3.0.0)
    * (old features: alloc, fiat-crypto, fiat_u64_backend, std)

LEC dependency change summary:
target packages:
  M x25519-dalek 1.1.0 (direct third-party, external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#4d6e37cee0a2ae0d3df522b3c6286fab6ce607b6')
    * source changed from external 'git+https://github.com/novifinancial/x25519-dalek.git?branch=fiat4#dc82145d8d25529d8aecab93d3ddf7062a74c719'
    * (unchanged features: fiat_u64_backend, std)
  R curve25519-dalek 3.0.0 (transitive third-party, external 'git+https://github.com/calibra/curve25519-dalek.git?branch=fiat3#2940429efd0e6482af1531cff079e6605cbc9cf2') (other versions: 3.0.0)
    * (old features: alloc, fiat-crypto, fiat_u64_backend, std)


Display the notional value of last 24h traded volume somewhere in console or governance page

Story
As a DeFi user who may or may not be trading via Console
I want to see the notional value of the 24h traded volume on each market
So that that I can compare to other DeFi protocols and see that Vega is clearly a success.

Btw. I think console would be best because in the governance page we don't break things down by a market... and also I think ppl will be looking in the console.
Acceptance Criteria

[ ] I can see the 24h notional value traded on a given market if it's displayed in the console
[ ] The value should be rounded depending on total to display a compact but useful number (Eg. 5M, rather than 5,000,000)
[ ] TBD (UX) show asset symbol? (edit as appropriate)
[ ] TBD (UX) display location? (edit as appropriate)

Tasks

[ ] UX (if needed)

[ ] Decide on location for display
[ ] Decide on whether to show asset symbol

[ ] Design (if needed)
[ ] Team and stakeholder review
[ ] Specs reviewed and created or adjusted
[ ] Implementation
[ ] Testing (unit and/or e2e)
[ ] Code review
[ ] QA review

Sketch
Additional details / background info

@davidsiska-vega We don't have a feasible way of calculating this accurately without tracking every single trade, we think this should probably be added as a field to a candle

@barnabee do you think this warrants a spot in the market header?

If this is actual 24h notional (size * price for every trade, summed for the past 24h) then yeah I think this should be in the header. Probably in the volume cell, something like

Volume (24h)
48.7151 (1.427m)

We can approx this a few ways

Current price x 24h vol
Price at some intervals over 24h x volume in those intervals (hourly sampling)
Infra fees on that market / infra fee factor

Option 2 seems fair for now


servo example on rpi 2 - no movement

hi,
first of all thank you for you extraordinary work!
can you give me some hint why my servo isn't moving. your example code compiles without errors, runs without errors. but servo stands still. when i try to move the servo with python code it works fine, so its no power or current issue or general I/O issue. it's a small sg90 servo. Do you have an idea where i can start to investigate?
Greetings

Hi @0Kraft,
there are problems with the management of PWM in ofxgpio.
you can try to use pin number 18 (GPIO18)
to see if the example works. be sure to run the example as a super user
to avoid problems with permits.
in the future I will fix this.
Ciao


Update munit, munit-scalacheck to 0.7.29

Updates

org.scalameta:munit
org.scalameta:munit-scalacheck

from 0.7.28 to 0.7.29.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #177 (57b08c8) into main (203374d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #177   +/-   ##
=======================================
  Coverage   89.49%   89.49%
=======================================
  Files          88       88
  Lines        2561     2561
  Branches       72       72
=======================================
  Hits         2292     2292
  Misses        269      269

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 203374d...57b08c8. Read the comment docs.


z_sendmany --- z_address to z_address

Command
votecoin-cli z_sendmany "zs1r57w2scma5q8sy8p63ql5nk6t69uw305fw2sdm20az2z3zx50uadus2kkccy767py9n6j5u78tx" '[{"address": "zs1h6mt6vvstnqsfh9mh8df32ua9acaa72px59724v2r6x57ermwazg6p3mzk66y6jyr6s3unpne36" ,"amount":<PHONE_NUMBER>5}]'
TX Confirmation
opid-57836a27-67b0-496c-ba63-f6a4b90ed6a9
Error shortly after
votecoind: wallet/wallet.cpp:1973: void CWallet::GetSaplingNoteWitnesses(std::vector, std::vector<boost::optional<libzcash::IncrementalWitness<32ul, libzcash::PedersenHash> > >&, uint256&): Assertion `*rt == witnesses[i]->root()' failed.

@EvilRedHorse I have the same issue on my project. Did you solve it? If yes, could you please help me? Thanks

Not a solution but I used:
votecoin-cli  z_exportwallet "zexport"
then
votecoin-cli z_importwallet "zexport"
to a new wallet.
I get the same error sending from the new wallet.
I get the same error on other computers.
Over 20+ GB of RAM was available during z_sendmany
still trying...

Solution:

increase the size of the Huge Pages pool

sudo sysctl -w vm.nr_hugepages=128


craco-cesium seems not to be maintained

Last update on craco-cesium has been 3 years ago.
Is that library maintained?
As per recommended setup in resium and in craco-cesium with typescript added many TS features fail, for example ! and:

Note that now CRA is not recommeded to be used to start React development: https://github.com/reactjs/react.dev/pull/5487#issuecomment-1409720741 .
I recommend using Vite. Minor maintenance such as version upgrades can be performed on craco-cesium, but no drastic functional development is planned.


ui: show guest networks for guest vlans list

Description
Fixes #7247
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan ui

@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/9554 (QA-JID-429)

@shwstppr
code lgtm
have you tested user-shared networks ?

@weizhouapache I'm not sure but is there some backend issue with VLANs for shared networks?
While VLAN is assigned to the network, it still shows as Free in the VLANs list

Also, we maybe returning DB IDs in the listguestvlans API

@weizhouapache I'm not sure but is there some backend issue with VLANs for shared networks? While VLAN is assigned to the network, it still shows as Free in the VLANs list

Also, we maybe returning DB IDs in the listguestvlans API

if create a shared network with specified vlan and skip vlan overlap check, the vlan will not be updated in table op_dc_vnet_alloc
to test user-shared network, you can

create a network offering for shared network with specifyvlan=false
create a shared network with the new network offering
you need to specify an isolated (or L2) network with associated network (the two networks will use the same vlan).

when done, the guest networks tab will list both networks, for example

the table op_dc_vnet_alloc does not have column uuid so only id is returned and displayed on UI.
considering the api is only available for root admin, it might be a minor issue

@weizhouapache works fine

@weizhouapache works fine

cool, thanks @shwstppr


Fixed HP raid parser when disks are in JBOD

The function parsing the RAID logical volumes in the HP module did not manage the case where disks were set in JBOD mode, thus having no RAID array set.
This patch fixes this by checking if arrays are defined on pdisks before parsing the logical disks.
Also added returncode read when executing the RAID related commands to raise a more precise error.

fyi:

netbox_agent.raid.hp.HPRaidControllerError: Failed to execute command 'ssacli ctrl slot=2 pd all show detail':
Error: The specified controller does not have any physical drives on it.


work on display

notes are drawn on top of each other
chord notes do not alternate side of stem if needed
tie draw is dumb; doesn't attempt to stay out of the way of notes
triplet drawn too close together
no support for 8va / 15ma
whole notes use too much space if alone on bar
colors are atrocious (read color palette from SVG?)

Triplet drawn too close together may be related to code that identifies the notes as tied, since they are 2/3rds the duration of normal notes. Don't know why they aren't drawn as tied, though, but I suspect that the shortened visual duration is because the first note of the tied notes is shorter. Still working on understanding this.

triplets draw correctly now

Beamed notes were accidentally disabled; they're working again. Added code to prevent beaming across measure bars.


TLS Support

Adding tls support. Maybe reference the approach of mitmproxy.

As previously discussed in Issue #5, it is possible to use '''iostream.start_tlsto change the src stream into theSSLIOStream```.
The following is a simple snippet that can do the job.
import ssl
try:
    ssl_context = ssl.create_default_context(ssl.Purpose.CLIENT_AUTH)
    ssl_context.load_cert_chain(certfile="/tmp/cert.crt", keyfile="/tmp/cert.key")
    stream = stream.start_tls(server_side=True,
                                                              ssl_options=ssl_context,
                                                              server_hostname=None)
except Exception as e:
    print e

And using the following command to generate the server certificate and private key.
openssl req -new -x509 -days 365 -nodes -out /tmp/cert.crt -keyout /tmp/cert.key

One more thing for above snippet, the ssl.create_default_context is only available in python 2.7.9 or above. So, if encounter any problem, please check the python verison first.

nice work~~

May encounter the following error when serving https://www.apple.com/iphone/
2016-05-19 09:35:02,484 - microproxy.layer.http1 - ERROR - [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca

And also the following error.
2016-05-19 09:36:58,270 - microproxy.layer.tls - ERROR - IOStream is not idle; cannot convert to SSL
Traceback (most recent call last):
  File "/home/mike820324/SourceCode/myProject/microProxy/microproxy/layer/tls.py", line 22, in process
    src_stream = yield self.context.src_stream.start_tls(server_side=True, ssl_options=src_ssl_context)
  File "/home/mike820324/ProgrammingEnv/python/microProxy/site-packages/tornado/iostream.py", line 1131, in start_tls
    raise ValueError("IOStream is not idle; cannot convert to SSL")
ValueError: IOStream is not idle; cannot convert to SSL

The IOStream is not idle problem may be a little bit difficult to solve than I expected.
The problem is caused by the fact that there are already some data in source stream read buffer.
In current tornado design, it is impossible for us to pause the IOStream.read_to_buffer , which is what we need in this case.
I may need to survey a while to resolve this issue.

It's weird to have this error unless we have some bugs in SocksProxy
According to document from tornado about the IOStream start_tls method:

This method cannot be used if there are outstanding reads or writes on the stream, or if there is any data in the IOStream’s buffer (data in the operating system’s socket buffer is allowed). This means it must generally be used immediately after reading or writing the last clear-text data. It can also be used immediately after connecting, before any reads or writes.

I had checked our code, and find the last thing we do over the source stream is read_bytes and write,
and we had yield the future to wait for the socket done the action.
I think we should not have any outstanding reads or write over the stream.
Is this error occur frequently?
Or on what situation we will encounter this problem?

Because Tornado provide basic ssl context base on server_side or not,
I think we could just doing like this:
server_ssl_options = dict(certfile=self.context.config["certfile"],
                          keyfile=self.context.config["keyfile"],)
src_stream = yield self.context.src_stream.start_tls(server_side=True,
                                                     ssl_options=server_ssl_options)
dest_stream = yield self.context.dest_stream.start_tls(server_side=False,
                                                       ssl_options=dict(cert_reqs=ssl.CERT_NONE))

for moe cleaning style
I had try and it works fine~

I think it's nothing to do with the socks proxy, it's just how tornado iostream works.
Tornado use epoll or kqueue to implement it's event based system. When a socket receive/write data, iostream will first read/write the data to the iostream._read/write_buffer.  As a result, when we reach the src_stream.start_tls part, it is highly possible that the browser already sent the client hello to our proxy, and then store inside iostream._read_buffer.
I think what the document trying to say is that, if there are data in  iostream._read_buffer or iostream._writer_buffer , the start_tls will failed.
The following is the code in torando iostream. https://github.com/tornadoweb/tornado/blob/master/tornado/iostream.py#L1126
 if (self._read_callback or self._read_future or
       self._write_callback or self._write_future or
       self._connect_callback or self._connect_future or
       self._pending_callbacks or self._closed or
       self._read_buffer or self._write_buffer):
    raise ValueError("IOStream is not idle; cannot convert to SSL")

By the way, as for the new style, I think it's great. Much more clear than the original one.

OK, you are right about the _read_buffer or _write_buffer that the IOStream will buffer the content.
I miss the keyword: must and immediately...

This means it must generally be used immediately after reading or writing the last clear-text data.

So the problem is: when we finish the socks handshake and tell the client that I could start read your request, the client will start transmit the request content and the source stream will start buffer from the socket. And error will be raised when tls handshaking is slower than the IOStream read buffer.
I just guess, am I right? yoyo~
But I should say, I hand't seen this error in my macbook.

You are absolutely right, I haven't see this in my macbook too. I believe it's some implementation difference between kqueue and epoll.
I think I should start merge this PR and add another issue for this. I may need to add some new code, but this PR may killing me if I have to rebase it. XDDD
Do you have any other stuff need to add for this PR??

Let's just merge it!


Supplement: When reading the local offline json file, the data is not filtered according to the max_image_size passed in.

Thanks for the PR, merged to the main branch


Request: show basic file properties in the explorer window (size, date modified)

Very simply I would like to have the option of showing some core data about each file within the explorer window aside from it's file name.  ie file size, date last modified.     It really surprises me this isn't present and would surely be quick to add.

@isidorn  I didn't think that customising what returns in the default explorer window is possible (hence my request)   Is there documentation to clarify that ?

Yes it is not possible to add in the explorer. But the extension could add a new view in the Explorer Viewlet, and the new view could show the file properties. There is probably already an extension for this. I would first checkout the marketplace.


Add -fstandalone-debug for Clang Debug builds

Scope & Purpose
Add -fstandalone-debug for our Clang Debug builds, so we get debug symbols for the STL etc.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required
[ ] Backports required for: (Please specify versions and link PRs)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket number:
[ ] Design document:

Testing & Verification
(Please pick either of the following options)

[x] This change is a trivial rework / code cleanup without any test coverage.
[ ] The behavior in this PR was manually tested
[ ] This change is already covered by existing tests, such as (please describe tests).
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Link to Jenkins PR run:
Documentation

All new features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the CHANGELOG so that
support, end users, and other developers have a concise overview.

[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

External contributors / CLA Note
Please note that for legal reasons we require you to sign the Contributor Agreement
before we can accept your pull requests.

LGTM, but changelog entry is missing.

Do we need one? This does not affect our "normal" builds, just custom ones of developers.

It'd of course be no problem to write one, I just don't think it's necessary, and wouldn't be of interest for users to read. @mchacki WDYT?

ok, i do not think a CHANGELOG entry is relevant here.
This is meant to be user-facing, and there is nothing that this PR changes for our users (we build with gcc on Linux, and Apple has the Flag set anyways)
If at all there should be README_Maintainers entry for this kind of PRs, if the Developers need to take some kind of action, which I do not see in this pr at all.
So I think this PR is all good if it helps us internally and no further file entry is required.


Add example for screenshotting long pages (over 16,000px)

Figured it'd be useful to have an example for the screenshot issues around.
Chromium issue: https://crbug.com/770769
This is a workaround that creates a few screenshots. It doesn't stitch them together though folks have had success using sharp for that.
(Apologies for using a private API ;)
Fixes #929, #926, #933, #359

Thank you @paulirish - I haven't had a chance to test this yet but wanted to quickly share this Google Chrome plugin that I'm been testing in past week (maybe 20+ times) that splits up long screenshots quite well:
https://mrcoles.com/full-page-screen-capture-chrome-extension/
https://github.com/mrcoles/full-page-screen-capture-chrome-extension
Maybe of some use as the code is Open Source too.

@paulirish i think we should fix this in puppeteer / chromium. Its very surprising that full-page screenshot does not take a full page screenshot.

Just an FYI...I tried this approach, as well as iterating over a grid of captures, on a project I am currently working on without much success. It was not so foreign to me as I have had to do the same thing with Phantom in order to keep memory consumption down on AWS Lambda.
In my use case I was taking screenshots of pages around 4000x4000. Each page contained between 6-15 full size original jpg images from digital cameras arranged on a page with a large png with transparent cutouts laid on top of the whole thing. I observed that the more images there were combined with the visual complexity of the overlay png, played a part in successful capture, or where the capture would fail silently with unrasterized blocks.
 Even when taking the stripes down to 10px and the grid down to 50px boxes, it was still problematic. Granted, my case is more extreme, but I just wanted to point out that the above approach still has limits when you get into things that are a bit more than capturing mobile web pages.
That said, puppeteer project looks super promising and was a delight to work with in comparison to alternatives, so needless to say I was very sad to have to abandon it (for the time being). Hoping to see this issue in Chromium resolved so I can pick it back up again in the future. Very exciting work.

Closing this since we not gonna land it.

Regarding @aslushnikov's comment: is there a bug we can track in Chromium?


Cannot activate extension with 1.39.2

Environment data

VS Code version: 1.39.2 - 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Extension version:  2019.10.41019
OS and version: rhel7 Linux x64 3.10.0-1062.1.2.el7.x86_64

Expected behaviour
After updating to 1.39.2, python plugin no longer starts.
Actual behaviour
Opening a python file prints Extension activation failed, run the 'Developer: Toggle Developer Tools' command for more information.
Toggling the develop tools shows an error
[Extension Host] Here is the error stack:  TypeError: Expected a string, got undefined
	at e.exports.e (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:1:339796)
	at g (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:399622)
	at m.update (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:395663)
	at m.initialize (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:399537)
	at new m (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:390681)
	at Function.getInstance (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:390888)
	at d.getSettings (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:388423)
	at new b (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:538539)
	at Object.t.resolveInstance (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:24:27409)
	at /home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:24:26617
	at Object.t.resolve (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:24:26884)
	at /home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:24:17956
	at e._get (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:24:17722)
	at e.get (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:24:16433)
	at o.get (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:75:1334728)
	at /home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:9:346991
	at /home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:9:347811
	at t.activate (/home/e/.vscode/extensions/ms-python.python-2019.10.41019/out/client/extension.js:9:350013)
	at Function._callActivateOptional (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:667:613)
	at Function._callActivate (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:667:264)
	at Promise.all.then.n (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:666:404)

Running Python: Enable Source Source Map Support for Extention Debugging fails with the error command 'python.enableSourceMapSupport' not found.  I've tried manually renaming ms-python.python*/out/client/extension.js.map.disabled file  to .map but it's renamed back to .disabled by vscode and I can't get a better trace.

@eaubin, thanks for letting us know about this.  We will look into the problem and get back to you as soon as we can.

I think I have the same problem, but different error messages.
Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18865
/C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243 [Extension Host] Error Python Extension: 2019-10-28 13:51:44: [TypeError: Cannot convert object to primitive value	at Array.toString (native)	at Object.getOwnPropertyNames.forEach.t (c:\Users\deral\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:1:64504)	at Array.forEach (<anonymous>)	at Object.l [as sendTelemetryEvent] (c:\Users\deral\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:1:64426)	at Object.sendSettingsTelemetry (c:\Users\deral\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:75:630578)	at Timeout.s.timer.setTimeout [as _onTimeout] (c:\Users\deral\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:1:133304)	at ontimeout (timers.js:425:11)	at tryOnTimeout (timers.js:289:5)	at listOnTimeout (timers.js:252:5)	at Timer.processTimers (timers.js:212:10)]
t.log @ /C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243
/C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243 [Extension Host] Error Python Extension: 2019-10-28 13:51:45: Detection of Python Interpreter for Command python and args  failed as file  does not exist
t.log @ /C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243
/C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243 [Extension Host] Error Python Extension: 2019-10-28 13:51:45: Detection of Python Interpreter for Command python3 and args  failed as file  does not exist
t.log @ /C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243
/C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243 [Extension Host] Info Python Extension: 2019-10-28 13:51:45: Failed to get conda environment list from conda { [Error: spawn C:\Users\deral\Anaconda3 ENOENT	at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)	at onErrorNT (internal/child_process.js:407:16)	at process._tickCallback (internal/process/next_tick.js:63:19)]  errno: 'ENOENT',  code: 'ENOENT',  syscall: 'spawn C:\\Users\\deral\\Anaconda3',  path: 'C:\\Users\\deral\\Anaconda3',  spawnargs: [ 'env', 'list' ] }
/C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243 [Extension Host] Error Python Extension: 2019-10-28 13:51:45: Failed to parse interpreter information for 'C:\Users\deral\AppData\Local\Microsoft\WindowsApps\python.exe' with JSON Python was not found but can be installed from the Microsoft Store: https://go.microsoft.com/fwlink?linkID=2082640 [SyntaxError: Unexpected token P in JSON at position 0	at JSON.parse (<anonymous>)	at t.WindowsStorePythonProcess.getInterpreterInformation (c:\Users\deral\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:9:39937)]
t.log @ /C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243
/C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243 [Extension Host] Error Python Extension: 2019-10-28 13:51:45: Failed to parse interpreter information for 'C:\Users\deral\AppData\Local\Microsoft\WindowsApps\python3.exe' with JSON Python was not found but can be installed from the Microsoft Store: https://go.microsoft.com/fwlink?linkID=2082640 [SyntaxError: Unexpected token P in JSON at position 0	at JSON.parse (<anonymous>)	at t.WindowsStorePythonProcess.getInterpreterInformation (c:\Users\deral\.vscode\extensions\ms-python.python-2019.10.44104\out\client\extension.js:9:39937)]
t.log @ /C:/Users/deral/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:243

Please notice that a different error is logged even when I install Python from the Store which, as far as I know, is not needed if I have Anaconda configured correctly.
Also: The same extension seems fine when I work on WSL Ubuntu 18.04

I somehow had an extra line in my settings.json "python.formatting": "black",. Removing this gets rid of the problem.
@alessandrostranieri your stack trace seems different to me, I'd guess you'd want to open a different issue.


Releases: add 0.19.1

[x] Update dates (rename the _posts file and edit the YAML date field in the _releases file)
[x] Optional: add magnet link to the _releases file

Note: tests expect to fail until the binaries have been uploaded to /bin/.  After that's done, restart Travis and it should pass.

Thank you! Added a commit that fills in the release date and magnet link, this can be merged when it passes Travis.

Thanks, I whitelisted the torrent hash 8b6ad1da5bbb24656234efc2370abc14781a6f83 on my tracker.

@Sjors thanks!


CDC for Streaming data in mysql

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
I Want to synchronise data from one mysql table to another mysql table with cdc using apache seatunnel 2.3.1 version.
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

env {
execution.parallelism = 1
job.mode = "BATCH"
checkpoint.interval = 10000
}
set the value of execution.parallelism as 1


Pilot discovery readiness probe not working

Describe the bug
the readiness probe for Pilot didn't work right on pod start:
Warning  Unhealthy         7s                 kubelet, tess-node-f4mb4.stratus.lvs.ebay.com  Readiness probe failed: Get http://<IP_ADDRESS>:8080/ready: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

and I tried getting into the pilot discovery container and curling localhost but it didn't work either:
root@istio-pilot-785c8cb887-8xfqm:/# curl -iv localhost:8080/ready
*   Trying <IP_ADDRESS>...
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> GET /ready HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.47.0
> Accept: */*
>

the port 8080 is open and the server is simply time out.
However, in this case Pilot is functioning which means all the gateway pods are able to get the correct envoy configs if I disable this readiness probe.
Expected behavior
readiness probe should work. Per https://github.com/istio/istio/issues/12308 mentions, at least curl localhost:8080/ready shouldn't time out with this ipv4 cluster.
Steps to reproduce the bug
clean install istio 1.1

any more log from pilot?

@hzxuzhonghu I'm not sure if it's related but I missed some ClusterRoles for my Galley(didn't notice it was from 1.0.x) and it kept errorring. Once it got fixed, the Pilot discovery readiness probe works well.
I will close this issue. Thanks!


Provide error: The API of DataCite or Crossref says there is a problem with accessing the record

Enhancement
Provide error: The import service for DOIs cannot be reached (Crossref or DataCite)

API errors => The API returns 4xx or 5xx errors. The former: a record could not be found, or can't be accessed; the latter: the API returns some kind of general system error.

For context, see epic #1091
Success criteria
Whenever something is broken within the Crossref or DataCite service, I see an error toaster. See implementation suggestions.
Implementation suggestion
Publications

To be adapted:

The route to other import options (now just a link)
The error code

            DOI import
            404

        <button class="close" type="button" data-dismiss="toast" aria-label="Close">

        </button>

The publication could not be imported.

The DOI was recognised, but Crossref could not access the record.

Try again later, or use a different import option.

Datasets

To be adapted:

The route to other import options (now just a link)
The error code

            DOI import
            404

        <button class="close" type="button" data-dismiss="toast" aria-label="Close">

        </button>

The dataset could not be imported.

The DOI was recognised, but DataCite could not access the record.

Try again later or manually add your dataset.

To be revisited


The new Pixi.js (dev branch) is  with ES6 , Is there still a ES5 version in the furture?

If not , How to let the ES6  version could run in old JS Engine ?

The built files are ES5, we transpile using babel.
Only the source before the build is ES6.


Setting ?queryparam when on root triggers refresh

The problem occurs when trying to set a query param when on the root page on non-default locale only. Setting the query param should trigger a global component to render, instead, the page refreshes and render the component. For some reason, it requested a script that is wrong (see image).

It's trying to access the it.js script where it is the locale in the url.
Im setting the Href of the Link component to '?queryparam=true'

I cannot reproduce that bug. Could you make a minimal reproduction?


Include third-party files

Hi,
I need to include jQuery and more third-party scripts, but I'm having a hard time with it. I do not understand webpack and I cannot include it in the index.html file, for it never finds it. I've put those files in src/static/scripts/.
Thank you.

Use yarn or npm to bring in your third party dependencies

See @mteichtahl's answer (thanks!).


omxplayer overlapping with other shared lib providers

I am seeing this error regularly
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libswresample.so.3: omxplayer, libswresample (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: omxplayer, libavutil (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavdevice.so.58.3.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: omxplayer, libavutil (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavcodec.so.58.18.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavcodec.so.58: omxplayer, libavcodec (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavformat.so.58: omxplayer, libavformat (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libswscale.so.5: omxplayer, libswscale (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: omxplayer, libavutil (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libswresample.so.3.1.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavcodec.so.58: omxplayer, libavcodec (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavformat.so.58.12.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavformat.so.58: omxplayer, libavformat (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavdevice.so.58.3.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: omxplayer, libavutil (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavfilter.so.7.16.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libswresample.so.3: omxplayer, libswresample (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavcodec.so.58.18.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: omxplayer, libavutil (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libswscale.so.5.1.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: omxplayer, libavutil (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavformat.so.58.12.100)
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: omxplayer, libavutil (used by files: /mnt/b/yoe/build/tmp/work/cortexa7t2hf-neon-vfpv4-yoe-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin)

It seems omxplayer is bundling stuff, so we need to be careful and fix the providers to address this error.

I am also facing a similar issue:
ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavformat.so.58: libavformat, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: libavutil, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavcodec.so.58.18.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: libavutil, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libswresample.so.3.1.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: libavutil, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavformat.so.58.12.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavcodec.so.58: libavcodec, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavformat.so.58.12.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavcodec.so.58: libavcodec, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: libavutil, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libswscale.so.5.1.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libswresample.so.3: libswresample, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavcodec.so.58.18.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: libavutil, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavformat.so.58: libavformat, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavdevice.so.58.3.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libswscale.so.5: libswscale, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: libavutil, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavdevice.so.58.3.100) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libswresample.so.3: libswresample, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/bin/omxplayer.bin) ERROR: omxplayer-git-r5 do_package: omxplayer: Multiple shlib providers for libavutil.so.56: libavutil, omxplayer (used by files: /home/adwait/yocto/rpi/build/tmp/work/raspberrypi0_wifi-poky-linux-gnueabi/omxplayer/git-r5/packages-split/omxplayer/usr/lib/omxplayer/libavfilter.so.7.16.100)
It is preventing the build from completing.
Any known workaround?

I made a change to meta-rpi/recipes-multimedia/omxplayer/omxplayer_git.bbappend (copied from https://<IP_ADDRESS>/c/yocto/meta-boot2qt/+/280226) that seems to resolve this issue.
PRIVATE_LIBS += "\
    libavcodec.so.58 \
    libavformat.so.58 \
    libavutil.so.56 \
    libswresample.so.3 \
    libswscale.so.5 \
"

Hope this helps.

perhaps turn this into a patch ?

@leon-anavi @trowhite are you guys up for a patch if this is still an issue in master? I know it's an old issue hence asking.

@agherzan I built today with hardknott and had to apply this, so IMHO still worth applying.

@deets thanks for confirming. Could you check it on master as well?

@agherzan I just tried but got not too surprisingly caught in the whole syntax-change issue, so it's at least not easy - I'd have to update a few of my own recipes of which this is part of. Would expect the behaviour to change?

@deets Any chance you are still up for pushing a patch for this?

I'll try to find time in september, I'm on vacation now for a while. But I got some more exposure to the newer yocto releases, so I feel more confident about working against master. I made myself a reminder so I can get back to you.


Synax highlighiting bug for shell (.sh)

Type: Bug
Code example which illustrates the issue:
#!/bin/sh

# The following line is valid shell code but everything after it is colored as a quote
test="$( case a in b) printf '%s ' "c"; esac )"

echo "for example, this line is colored as a quote"

Expected behavior: following lines should not be colored as quotes.
VS Code version: Code 1.70.3 (a21a160d630530476218b85db95b0fd2a8cd1230, 2022-08-31T08:03:55.990Z)
[ Edit: The issue remains with VS Code 1.85.1. ]
OS version: Windows_NT x64 6.1.7601
Modes:
Remote OS version: Linux x64 6.2.0-32-generic
Extensions (3)

Extension
Author (truncated)
Version

remote-ssh
ms-
0.84.0

remote-ssh-edit
ms-
0.84.0

shellcheck
tim
0.35.0

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.85.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

The issue remains with VS Code 1.85.1.

should move report to https://github.com/jeff-hykin/better-shell-syntax

should move report to https://github.com/jeff-hykin/better-shell-syntax

I should report it there?

VSCode uses that extension as the default builtin shell highlighting

I reported the issue in better-shell-syntax:
https://github.com/jeff-hykin/better-shell-syntax/issues/72

Thanks for moving the issue @blunderful-scripts!


Catching up with commons 0.5.0

This PR upgrades the dcos-commons dependency to 0.5.0.

@mesosphere-ci retest this please.


problem for the matemathical examples #2

@Johnabarreto commented 15 hours ago — with docs.microsoft.com
In the mathematical examples no working fine, show this information: \begin{align} & \begin{bmatrix} 1 \ 0 \end{bmatrix} ^ {\otimes 1} = \begin{bmatrix} 1
In English working fine!

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

ID: 434e640f-ea90-3c49-9510-1fda8cbee7a1
Version Independent ID: 9c5af71d-7980-d644-b2bc-9b54bda5e551
Content: Vectors and matrices - Microsoft Quantum
Content Source: articles/concepts/vectors-and-matrices.md
Product: quantum
GitHub Login: @QuantumWriter
Microsoft Alias<EMAIL_ADDRESS>

this problem is occuring at every webpage wherever there is the mathematical expressions!!
how to fix it  ??

Hi @sutteri thank you for reaching out. We just noticed the problem as well. The rendering stopped working as we noticed yesterday. We are trying to find the root cause.

thanks for your response ..yes the rendering has stopped... i was trying to
learn quantum computing and this happened last night !!
On Thu, 4 Jun 2020 at 18:02, Kitty Yeung<EMAIL_ADDRESS>wrote:

Hi @sutteri https://github.com/sutteri thank you for reaching out. We
just noticed the problem as well. The rendering stopped working as we
noticed yesterday. We are trying to find the root cause.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/quantum-docs-pr/issues/669#issuecomment-638818328,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP2UOCDVYIYSVRYTG3L3YJTRU6H6NANCNFSM4KMYC2ZQ
.


🚀

smpn ava => Futuristic test runner � on Windows.
Fixable?

👎

Works as expected on Linux. Oh well.