feat: programmatically select active items

Add active property which describes currently selected items.
Remove initData property since everything works on top of active.

if possibly merged in, a thing that is left is to update README.md (remove info about initData and add active)

@Namek ok, looks really good to me!
2 things:

please add Readme update
fix tslint issues :)

@valorkin done, that should be it.
To make it more angular-way we should enable two-way databinding by merging active input with selected output into @Input() selected + @Output() selectedChange.
In case you didn't know what I'm talking about, these two snippets are equal:
<input type="text" class="form-control" required
  [ngModel]="model.name"
  (ngModelChange)="model.name = $event" >

<input type="text" class="form-control" required
  [(ngModel)]="model.name">

(source: https://angular.io/docs/ts/latest/guide/forms.html)
But I think if selected would be changed to selectedChange then we should also rename other outputs. I didn't PR'ed this because I'm not sure if you like it.

Any timeline when this will be merged and released to NPM?

Usually Monday - Tuesday is release days
On Fri, Jun 3, 2016, 12:51 Achim Hasenmueller<EMAIL_ADDRESS>wrote:

Any timeline when this will be merged and released to NPM?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/valor-software/ng2-select/pull/223#issuecomment-223538329,
or mute the thread
https://github.com/notifications/unsubscribe/ABDk440mecFLLWz-NmI2s0x7cMgiFO5Eks5qH_kPgaJpZM4Iqo0T
.

Am I wrong? I don't see the changes published to NPM.
Thanks

Again, any timeline on when this will be merged in?

Any update one when it will be published to npm?

I'm releasing a product and really need this now.

Hey guys, thanks a lot for this awesome directive! I could not make [active] property works. I have tried with everything Array, any[], cast element as SelectItem but nothing, there is no way for me to set the directive with initial data. It seems to be that this issue is related to that. We are using this in PRD so the sooner you could fix this or merge the fix, will be more than appreciated. Thanks in advance.


Consume latest version of remote-ui to support error handling

Background
This PR consumes latest version of remote-ui to support error handling.
Ref https://github.com/Shopify/checkout-web/issues/5252
Solution
Consume latest version of remote-ui
🎩
See https://github.com/Shopify/web/pull/45842
Checklist

[x] I have :tophat:'d these changes

Ready for another look

@henrytao-me I'm reading the TS docs and I think the root of the problem is that remote-ui/react should include @types/react-reconciler as a dependency (similar to how @types/react is included) since it's a library that bundles its declaration files.
From the example in the docs: https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#including-declarations-in-your-npm-package

Here, our package depends on the browserify and typescript packages. browserify does not bundle its declaration files with its npm packages, so we needed to depend on @types/browserify for its declarations. typescript, on the other hand, packages its declaration files, so there was no need for any additional dependencies.

Our package exposes declarations from each of those, so any user of our browserify-typescript-extension package needs to have these dependencies as well. For that reason, we used "dependencies" and not "devDependencies", because otherwise our consumers would have needed to manually install those packages. If we had just written a command line application and not expected our package to be used as a library, we might have used devDependencies.

I think we should update remote-ui/react to set @types/react-reconciler as a dependency instead of manually adding it for our react packages


cli gem

Hey!  I negotiated a transfer of the cli gem in November with James Charles Russell, the owner of the old gem. I promised him I would keep support for his old interface in my new lib. I'v been very busy through the Christmas season and was just now getting ready to release it when, lo, I up and find out that you've pushed a gem to it.
I would like it back, please!
Now, I'm not unreasonable and I took a look at your library with the thought that perhaps it being a significantly awesome CLI library then I would consider letting it go. But, in all honestly, your cli lib is much the same library as about a half dozen or so other libraries that are out there. I'm not degrading your work, please don't misunderstand. Implementation looks well done from what I've seen. But it's simply the fact that your CLI library is essentially the same library as many others. Some that are fairly popular are:

Trollop (http://trollop.rubyforge.org)
Slop (https://github.com/injekt/slop)
micro-optparse (http://florianpilz.github.com/micro-optparse/)

There's also Thor, albeit a little different interface, is nonetheless similar and extremely popular due to it's use by Rails.
And personally. the one I think is the very best b/c of it's utter simplicity is CLAP (http://druwerd.wordpress.com/2010/10/20/clap-command-line-arguments-parsing/).
So given all these choices (and then some) I can't help but wonder why you weren't happy enough with any of those? Or at least try contributing to one of those projects if it were close to what you'd like sans a feature or two?
Well, I figure none of that is going to convince you. After all, we programmers generally like to scratch our own itch. So I tell you what I am going to do. Instead of trying to beg the gem away from you, you just hang on to it for safe keeping. I'll release my work under another name, and then I will demonstrate it to you. Given that you keep an unbiased mind, I have no doubt you will be sufficiently impressed enough to up and re-release the cli gem as a metagem just to install mine ;-) Okay, I might be going a little overboard there. But I do think you will be impressed.
Regardless of my work, I think you will ultimately decide to jump ship b/c command line parsers are one of those notorious monsters that we all think ti would cool to create but in the end aren't worth the trouble, so we think, 'ey', might as well use 'optparse'.

Hi,
Sorry about that.
When I was looking for name for it I have used gem search and I have found out that there was cli_base but no cli gem. So it was an obvious choice for me!
To be honest I have only noticed that there were some older versions of this gem already there when I have checked rubygems.org site after I have already pushed my gem.
I was assuming that once you take a name it is locked forever. I was surprised that 'cli' gem name was not taken.
As for reinventing the wheel again... I have done my research before creating my gem.
I was working on a program that had many executable prats (UNIX style) and I needed argument parsing (not only switches like -x) and STDIN handling that I could quickly use and get help generated for free.
Before that I was using 'main' gem but it was too complicated, I liked Slop and Trollop API but they were lacking argument and STDIN support.
I needed something quickly and it took me 1 day to implement the API and features I needed - it would probably take me more to get into somebody else code.
Than it took me 2 more weeks to make it properly documented and robust  so I could release it as a gem so after all it was quite a lot of work to get it there but now it is complete.
Command line parsing is a very common problem that should have been solved long time ago and we should have all the features we would ever need but in fact that is not the case with ruby.
There is no gem that would make someone else to invest time in getting more features in and therefore we end up with so many different approaches.
I think this diversity is a good aspect of open source and some clean winner will show up after enough time had passed.
When your are ready with your gem let me know.
If it fits better for the name I may let it go for you.
Anyway, can you tell me what is your gem about?
Regards,
Jakub
Wiadomość napisana przez 7rans w dniu 30 Jan 2012, o godz. 07:43:

Hey!  I negotiated a transfer of the cli gem in November with James Charles Russell, the owner of the old gem. I promised him I would keep support for his old interface in my new lib. I'v been very busy through the Christmas season and was just now getting ready to release it when, lo, I up and find out that you've pushed a gem to it.
I would like it back, please!
Now, I'm not unreasonable and I took a look at your library with the thought that perhaps it being a significantly awesome CLI library then I would consider letting it go. But, in all honestly, your cli lib is much the same library as about a half dozen or so other libraries that are out there. I'm not degrading your work, please don't misunderstand. Implementation looks well done from what I've seen. But it's simply the fact that your CLI library is essentially the same library as many others. Some that are fairly popular are:

Trollop (http://trollop.rubyforge.org)
Slop (https://github.com/injekt/slop)
micro-optparse (http://florianpilz.github.com/micro-optparse/)

There's also Thor, albeit a little different interface, is nonetheless similar and extremely popular due to it's use by Rails.
And personally. the one I think is the very best b/c of it's utter simplicity is CLAP (http://druwerd.wordpress.com/2010/10/20/clap-command-line-arguments-parsing/).
So given all these choices (and then some) I can't help but wonder why you weren't happy enough with any of those? Or at least try contributing to one of those projects if it were close to what you'd like sans a feature or two?
Well, I figure none of that is going to convince you. After all, we programmers generally like to scratch our own itch. So I tell you what I am going to do. Instead of trying to beg the gem away from you, you just hang on to it for safe keeping. I'll release my work under another name, and then I will demonstrate it to you. Given that you keep an unbiased mind, I have no doubt you will be sufficiently impressed enough to up and re-release the cli gem as a metagem just to install mine ;-) Okay, I might be going a little overboard there. But I do think you will be impressed.
Regardless of my work, I think you will ultimately decide to jump ship b/c command line parsers are one of those notorious monsters that we all think ti would cool to create but in the end aren't worth the trouble, so we think, 'ey', might as well use 'optparse'.

Reply to this email directly or view it on GitHub:
https://github.com/jpastuszek/cli/issues/1

Jakub Pastuszek
<EMAIL_ADDRESS>tel: +353 86 380 51 55
skype: kazuya_smoku

Sorry about the late reply. It's quite alright. It is my fault after all. I should have put up a dummy gem until my code was ready.
So I have gone with the name executable instead. The gem is not quite ready for "production" use yet --sometime soon I hope to sit down and polish it off, but you can see what it's all about here.
Maybe when I've finally finished I will contact you again and we can compare approaches and discuss.


change for sampling features form

change for sampling features form

@miguelcleon, congrats on this big release!
https://github.com/ODM2/ODM2-Admin/releases/tag/v0.5000-beta
Wohoo!


Is there any relevant api documentation?

Is there any relevant api documentation?

You can refer the document of telegram


SSL Certificates Expired

I installed the GPG key and repo file from the main page here:
https://unitedrpms.github.io/#repository
When attempting to search/install I get
unitedrpms 34 - x86_64                                                                                0.0  B/s |   0  B     00:00
Errors during downloading metadata for repository 'unitedrpms':
  - Curl error (60): SSL peer certificate or SSH remote key was not OK for https://sourceforge.net/projects/unitedrpms/files/34/x86_64/repodata/repomd.xml [SSL certificate problem: certificate has expired]
Error: Failed to download metadata for repo 'unitedrpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Same thing happens for the osdn link
unitedrpms 34 - x86_64                                                                                20 kB/s |  20 kB     00:00
Errors during downloading metadata for repository 'unitedrpms':
  - Status code: 404 for https://osdn.net/projects/unitedrpms/storage/34/x86_64/repodata/repomd.xml (IP: <IP_ADDRESS>)
  - Curl error (60): SSL peer certificate or SSH remote key was not OK for https://sourceforge.net/projects/unitedrpms/files/34/x86_64/repodata/repomd.xml [SSL certificate problem: certificate has expired]
Error: Failed to download metadata for repo 'unitedrpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

Setting sslverify=0 in unitedrpms.repo gets around the issue but obviusly not in a good way.

https://osdn.net/projects/unitedrpms/storage/34/x86_64/repodata/repomd.xml and https://sourceforge.net/projects/unitedrpms/files/34/x86_64/repodata/repomd.xml have valid certificates now , I guess , but nothing we can do unless report upstream

I think this is what is causing the issue: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
 echo | openssl s_client -showcerts -servername sourceforget.net -connect sourceforget.net:443
CONNECTED(00000003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify error:num=10:certificate has expired
notAfter=Sep 30 14:01:15 2021 GMT
verify return:1
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
notAfter=Sep 30 14:01:15 2021 GMT
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify error:num=10:certificate has expired
notAfter=Sep 29 19:21:40 2021 GMT
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
notAfter=Sep 29 19:21:40 2021 GMT
verify return:1
depth=0 CN = sourceforget.net
notAfter=Nov 28 06:50:25 2021 GMT
verify return:1

This is probably going to hit lots of people but I would have thought sourceforge would fix this since its has been 2 weeks.

echo | openssl s_client -showcerts -servername sourceforget.net -connect sourceforget.net:443
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = sourceforget.net
verify return:1

[makerpm@fedora ~]$ echo | openssl s_client -showcerts -servername sourceforget.net -connect sourceforget.net:443
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = sourceforget.net
verify return:1
---
Certificate chain
 0 s:CN = sourceforget.net
   i:C = US, O = Let's Encrypt, CN = R3
-----BEGIN CERTIFICATE-----
fooo xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-----END CERTIFICATE-----
Server certificate
subject=CN = sourceforget.net

issuer=C = US, O = Let's Encrypt, CN = R3

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 4542 bytes and written 436 bytes
Verification: OK
---
New, TLSv1.2, Cipher is fooooxxxxxxx
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : fooxxxxxxxxxxx


Design/implement forecast interval predictions

Linked to evaluation framework #64

This is a can of worms...
Why: this is a different "kind" of prediction, essentially a third option next to deterministic and probabilistic supervised prediction or forecast.
Prediction intervals can hence appear in any case when the predicted object has a continuous/numeric type.
To my knowledge there is no package that has a clean interface for prediction forecasts, but what comes closes is ...
https://github.com/alan-turing-institute/skpro
... which is currently looking for a maintainer or v2 re-design.
As a hack, one could make PI boundaries part of a dict return object, similar to mean/var in sklearn, but it wouldn't account for:

the possibility of producing PI boundaries at different levels of prediction confidence (e.g., 75%, 90%)
deriving these from fully probabilistic predictions
evaluation via losses specific for PI

As a slightly less hacky option, one could attach traits to each method about which kinds of predictions it can make: PI mean/var; PI, quantile-based, fully probabilistic, etc.
The return object of predict would be a dictionary with pre-defined fields, and there would be input fields to specify the quantiles one want for PI.
Anything "nicer" (e.g., along the lines of MLJ's ontology of det/prob/etc) would require an interface redesign and/or further work on skpro, in my opinion.

@frthjf 's opinion might also be helpful, if he's still following github discussions...

Maybe we should just adopt a quick, hacky statsmodel/pmdarima-style solution where one can optionally compute confidence intervals for a user given alpha value (related to #104). The fully probabilistic interface requires much more work.

A bit late to the party so please if ignore if no longer applicable as already closed. I might lack context of the wider project here, but from what I understand it seems indeed like a type of problem that the skpro API tried to address. I'd like to think of the problem as 'speculative API' problem where the issue is that we try to define an intermediate return object without knowing how it is going to be used. In skpro, the object was a distribution and the issue is that the user might be interested in something as complex as the pdf() but might just as well only care about the mean. The return type somehow has to represent mean, pdf() and any other conceivable property of interest but ideally only the ones that are actually used to avoid a lot of wasted computation. Here, we have a similar problem where the general return object are intervals ranging from simple boundery values to something like get_interval(confidence=0.9).
In skpro, the solution paradigm to this issue was lazy execution; the computation of mean, pdf() etc. is described but only executed when accessed and actually used. This has the problem that one still needs to define how all the potential properties of interest would be computed for each an every model, so the computional burden of full eager execution is transformed into an implementational burden that is not very user friendly.
The other option is something like a predictive API where you say, well, we assume most people are only interested in alpha value intervals, so let's hack that in and if it turns out people actually care about other things then we have to go back and implement something else (I think that's the way to go as a quick fix)
Now, I believe there is a better way to solve this because we shouldn't be forced to speculate about what is actually needed if we could look at the entire computation ahead of the execution of each steps and truncate intermediate objects that are not needed for the end result (a bit like in Tensorflow's compute graph). Unfortunately, as @fkiraly recognized, this is a true can of worms and would require a huge amount of work. In any case, maybe this perspective helps with the further development.


Use full service name for Azure NetApp Files

Geert van Teylingen (ANF PM) here. Can you rename 'NetApp' to the actual full service name 'Azure NetApp Files' in this sentence:
Data services use a combination of high-performance storage on Ultra or Premium solid-state disks (SSDs), file storage on Azure NetApp Files or Azure Files, and standard blob, archive, and backup storage that can be locally redundant or geo-redundant.

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

ID: d151997c-4629-0167-3bb8-f14e35c119dc
Version Independent ID: 2a7f8f92-e594-c6c1-07ce-a02d4d47af24
Content: Refactor IBM z/OS Coupling Facility - Azure Reference Architectures
Content Source: docs/reference-architectures/zos/refactor-zos-coupling-facility.yml
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @EdPrice-MSFT
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 512661

I've put in a PR to update the doc. It will go live once the doc author has approved it.


Simple modifications on Readme.md

Simple modifications in manual installation
and usage section to make it a bit more readable.

The program has been published to pypi, now the installation is managed with pip.

The program has been published to pypi, now the installation is managed with pip.


chore(requirements): update pytz to 2017.2

See https://launchpad.net/pytz/+announcement/14547

Codecov Report

Merging #1280 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1280   +/-   ##
=======================================
  Coverage   86.63%   86.63%
=======================================
  Files          45       45
  Lines        3929     3929
  Branches      681      681
=======================================
  Hits         3404     3404
  Misses        356      356
  Partials      169      169

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 0ef67fa...88846bf. Read the comment docs.


Add STI to download

Added

Add type column to Download #2494
Add corresponding types of Download (bibtex, coldp, dwc_archive, etc.)

Changed

Extract metamorphosize from is_data and add to its own concern
Update Download factories to reference type

Codecov Report

Merging #2498 (14d179a) into development (9d7b6ef) will decrease coverage by 21.66%.
The diff coverage is 100.00%.

@@               Coverage Diff                @@
##           development    #2498       +/-   ##
================================================
- Coverage        87.65%   65.98%   -21.67%
================================================
  Files             1812     1334      -478
  Lines            62704    36410    -26294
================================================
- Hits             54961    24024    -30937
- Misses            7743    12386     +4643

Impacted Files
Coverage Δ

app/helpers/downloads_helper.rb
72.72% <100.00%> (ø)

app/models/concerns/shared/is_data.rb
44.94% <100.00%> (-33.47%)
:arrow_down:

...p/models/concerns/shared/is_data/metamorphosize.rb
100.00% <100.00%> (ø)

app/models/download.rb
97.50% <100.00%> (+0.62%)
:arrow_up:

app/models/download/basic_nomenclature.rb
100.00% <100.00%> (ø)

app/models/download/bibtex.rb
100.00% <100.00%> (ø)

app/models/download/coldp.rb
100.00% <100.00%> (ø)

app/models/download/dwc_archive.rb
100.00% <100.00%> (ø)

app/models/download/sql_project_dump.rb
100.00% <100.00%> (ø)

app/models/download/text.rb
100.00% <100.00%> (ø)

... and 1005 more

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 9d7b6ef...14d179a. Read the comment docs.

@mjy cannot see anything wrong. Do we skip next minor release or merge now?

Merge after minor.


Black screen in next videos played

First video has double the sound so pausing it is the only way to listen to the video.
Sound is coming from the background of the video without the foreground playing video, there is no control to stop the background audio from playing.
After the audio of the video has completed the next video begins playing if autoplay is on but the box where the video is normally displayed suddenly goes black and even the controls for the video disappear.
This is of course on Youtube.com

I'm getting black screen on "YouTube Shorts"

Did ya'll skip the post titled...?
❗Temp Fix To Current v5.4/v5.5 problem❗ - Downgrade to v5.3 [Text and video instructions]
Joelmatic knows about the problems.
Downgrading to 5.3 works for now until a new stable version is released.


Export to html doesn't work

Hello,
this projects looks really nice and is useful to us. However, we're able to see the widget only when the notebook is opened inside VSCode/jupyter server. When we attempt to convert the notebook to html via jupyter nbconvert --to html, we get something like this:

Basically, instead of the widget, there's some "SpectrogramPlayer(...)" truncated string. I believe this is the textual representation of the Python class providing the widget. It would be nice we we were able to export the notebook to html.
Nevertheless, thanks for the widget!

oh, and versions:
IPython          : 8.16.1
ipykernel        : 6.25.2
ipywidgets       : 8.0.2
jupyter_client   : 8.4.0
jupyter_core     : 5.4.0
jupyter_server   : 2.9.1
jupyterlab       : 4.0.7
nbclient         : 0.8.0
nbconvert        : 7.9.2
nbformat         : 5.9.2
notebook         : 7.0.6
qtconsole        : not installed
traitlets        : 5.11.2

speechwidgets                 1.0.1

Hey!
Hey!
Thanks for the feedback.
This toy project is not really under active development and should probably be in an archived state. However, I played around with it and managed to get the HTML export working.
In Jupyter, ensure that Settings > Save Widget State Automatically is checked. See the image below for reference:

Then, when exporting to HTML, I used the following command:
jupyter nbconvert --to html --EmbedWidgetsPreprocessor.embed_widgets=True test.ipynb

The widget then rendered properly when I opened the HTML file in Chrome:

Please let me know if you are able to get it to work or if you find any other issues.

@srdecny Did you manage to get it working?

Hi I tried to od the export but I am getting the following error (After I install jupyter_nbextensions)
python3.10/site-packages/jupyter_nbextensions_configurator/__init__.py", line 18, in <module>
    from notebook.base.handlers import APIHandler, IPythonHandler
ModuleNotFoundError: No module named 'notebook.base'

Hey @janvainer
I've attempted to replicate the issue you're experiencing without success. Here's the detailed process I followed to mimic your environment:

Based on the package versions listed by @srdecny , I created a requirements.txt file in a new directory:

IPython==8.16.1
ipykernel==6.25.2
ipywidgets==8.0.2
jupyter_client==8.4.0
jupyter_core==5.4.0
jupyter_server==2.9.1
jupyterlab==4.0.7
nbclient==0.8.0
nbconvert==7.9.2
nbformat==5.9.2
notebook==7.0.6
traitlets==5.11.2
speechwidgets==1.0.1

I created and activated a new virtual environment, then installed the required packages:

python -m venv env

source ./env/bin/activate

pip install -r requirements.txt

I initiated a Jupyter server using the command:

jupyter notebook

I created a new notebook named test.ipynb.

In the first cell, I inserted the code snippet provided by @srdecny:

from speechwidgets import SpectrogramPlayer
word_intervals = [['0.54', '0.84', 'this'],
        ['0.84', '1.1', 'little'],
        ['1.1', '1.4', 'work']]
s = SpectrogramPlayer(
    wav_file_path="/Users/nicolvisser/Datasets/LibriSpeech/dev-clean/652/130726/652-130726-0000.flac",
    win_length=400,
    hop_length=160,
    f_min=50,
    n_mels=80,
    power=1.0
)
#s.annotate(data=word_intervals, title="Word Intervals")
import IPython.display as ipd
ipd.display(s)

After running the cell, which took some time to import initially, I proceeded with the following steps.

I ensured that the Settings > Save Widget State Automatically was checked.

I manually saved the notebook via File > Save Notebook.

I terminated the Jupyter server by pressing Ctrl+C in the terminal.

I converted the notebook to an HTML file with embedded widgets using the command:

jupyter nbconvert --to html --EmbedWidgetsPreprocessor.embed_widgets=True test.ipynb

Upon opening the generated test.html file in Google Chrome, the result appeared as follows:

Unfortunately, I was unable to reproduce the error following these steps.
The error you get indicates that Python is unable to find the module named 'notebook.base', which should be a part of the Jupyter notebook package.
It might be worth checking your Jupyter notebook installation.
I really hope you can get this working. I'm curious to see what you are working on and am eager to assist. If you could provide any additional details or specific circumstances under which the error occurs, it would be very helpful.

test.html.zip
See if you can download and open this file. This is the exported HTML


cancelInteractiveMovement() seems broken

Cells should return to original positions, but some are missing or inconsistent with model. This seems to be on Apple's end; can you confirm?
To reproduce: call cancelInteractiveMovement() on gesture .Ended instead of endInteractiveMovement(). Wrapping in performBatchUpdates w/ reload in completion almost fixes, but not quite always.

I've seen similar things with cancelInteractiveMovement() too on iOS 9.2. My workaround at the moment is to call collectionView.reloadItemsAtIndexPaths(collectionView.indexPathsForVisibleItems()) immediately afterwards which sometimes causes a slightly ugly re-shuffle, but at least the resulting cells reflect the model accurately. Be interested to hear if a better solution is known.


mongo_db_plugin needs to respect transaction status in irreversible blocks

In _process_irreversible_block(), the plugin does not look up the transaction status in each transaction receipt. As a result, there's no indication if a transaction fails at BP signing.
Example: block 8972110, the first two transactions have status hard_fail, but previously they were delivered and processed by _process_applied_transaction(), so they look like totally valid transfers (except that global action sequence is the same number for both).
So, _process_irreversible_block() should update existing documents and mark the status or delete failed documents.
See also:  https://github.com/cc32d9/eos_zmq_plugin/commit/d9ad18d9dbcf9678f1155f14c4dedc99a1c71d32

You should not have this problem if you run with read-mode = read-only

I don't think it would help. At the moment I'm synchronizing a node with my ZMQ plugin. It does the verification on trace->producer_block_id.valid() like in Mongo plugin, and this machine has one p2p peer to a nearby node, and I never pushed transactions to it.
At the moment it's still re-syncing , and it's at 2018-09-19 13:14:23, and it delivered 1224 transactions which were then marked as failed in subsequent irreversible blocks.
The same thing happens if I re-play the blockchain from a local blocks archive.
the node is not configured with read-only mode. I can add it now and see if the number of such transactions increases.

ah, sorry, I just read the full description of read-only mode. If it only delivers irreversible blocks, then it definitely solves the issue. Probably the mongodb plugin should check if this option is enabled?

read-only does NOT only deliver irreversible blocks. It delivers signed blocks (before they become irreversible).
If you run any mode except read-only then you speculative execute (and deliver to plugin) p2p transactions. Even if you don't send any transactions directly to the node.
If you check trace->producer_block_id.valid() then you should not process any speculative transaction traces. You are seeing this with the trace->producer_block_id.valid() ?

yes, I'm seeing this with
    void on_applied_transaction( const transaction_trace_ptr& trace )
    {
      // see a long comment in mongo_db_plugin.cpp for applied_transaction()
      if( !trace->producer_block_id.valid() ) {
        return;
      }

also I see it in replay-blockchain mode

What is the value of your producer_block_id for those in block_num 8972110?

eosio@eosnode:~$ cleos get block 8972110 | head -30
{
  "timestamp": "2018-08-01T23:42:52.000",
  "producer": "eoscanadacom",
  "confirmed": 0,
  "previous": "0088e74dea0a4e4e8883ad54bcc0e44908d24ec465c17ef79e7109e25d78a70d",
  "transaction_mroot": "13a1b4957c7d8d09d4df285a585882f54bf79265e2c55449c402424ac2595dfe",
  "action_mroot": "90acc8ba680042dcb29fab82e6e286b1af7d9df26f1ea4331d03cedbb57cf442",
  "schedule_version": 255,
  "new_producers": null,
  "header_extensions": [],
  "producer_signature": "SIG_K1_K8zSiHw6fjZBJ7WaZK71CC4QQAWViqLnwxfLaxEFNoBy6hfE34QvZEA6cN7FowfQDFFPKxEZhsAV2n4nCnSCPkKWrtCNWt",
  "transactions": [{
      "status": "hard_fail",
      "cpu_usage_us": 0,
      "net_usage_words": 0,
      "trx": "4e5d4fcef0f7a5cc00350b107e4a9387541a0e0335179dac06870ac274302152"
    },{
      "status": "hard_fail",
      "cpu_usage_us": 0,
      "net_usage_words": 0,
      "trx": "f2720351ddee5e9734368643b14d8e81faf99e3dcf5f9df8e08dd7e303cbdfd5"
    },{
      "status": "executed",
      "cpu_usage_us": 534,
      "net_usage_words": 13,
      "trx": {
        "id": "18f7f2de67e8e0f099a06ca30ff0e2e9e0b288d9209e3ba5f1438fb7b5b2d147",
        "signatures": [
          "SIG_K1_Ki6iWfHD19ZmrFkLfyJATrPchGEP8EAJiUiyGjh1B8zaDCrGyVvu2Q8iCCRv16yEUNEcKXvvQNwNi7kdJB6QQ2y52hjWJK"
        ],

in "previous" I see the block ID from your pastebin. And as you see, the transactions are marked as failed, and your mongodb has them as happening. This is exactly what I described

The pastebin I show has them all as:
"trx_status" : "hard_fail"

yes, but it still has "global_sequence" : 144602772, and that violates a unique index, because this global sequence belong to a different transaction that was executed successfully.

global_sequence should not be a unique index. You can get duplicates for hard_fail as we see here. [producer_block_id, trx_id, receipt.global_sequence] would be unique assuming producer_block_id is valid if you really want an index which includes global_requence.


[seal] update to <4.0.0>

Fix #27914
Update seal to the latest version 4.0.0
All feature are tested successfully in the following triplet:

x64-windows
x64-windows-static

Thank you!


[#ISSUE 7909] Fix send retry message permission check

Which Issue(s) This PR Fixes

Fixes #7909
Brief Description

Require the SUB permission of retry topic,not the producer group.
How Did You Test This Change?

UT

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 42.88%. Comparing base (72bd03c) to head (d535981).
Report is 1 commits behind head on develop.

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #7917      +/-   ##
=============================================
- Coverage      42.89%   42.88%   -0.02%
  Complexity      9909     9909
=============================================
  Files           1190     1190
  Lines          86042    86038       -4
  Branches       11081    11081
=============================================
- Hits           36912    36901      -11
- Misses         44559    44565       +6
- Partials        4571     4572       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@dingshuangxi888 Please help review this pr.


Soft multitenancy, tenant aware storage

Requirement - what kind of business use case are you trying to solve?
I want to deploy a single Jaeger instance (collector, query) and be able to store and query data for multiple tenants. I want tenant data to be separated e.g. I don't want tenant A to access data from tenant B.
Proposal - what do you suggest to solve the problem or improve the existing situation?
The tenant information can be propagated down to the storage layer and storage can decide how to store it. For instance, in ES the storage would add tenant name into index name. This feature requires changes in multiple areas - storage, API, metrics, internal components. The storage implementation could decide whether multi-tenancy is supported or not.
Storage API change
There are probably 3 ways to implement this at the storage API

Add a parameter to identify a tenant
Propagate tenant in context.Context

There might be as well a third solution - propagate tenant in data, but I would exclude it because for instance GetServices (and other APIs) does not have any data parameter.
type Writer interface {
	WriteSpan(ctx context.Context, span *model.Span) error
}

type Reader interface {
	GetTrace(ctx context.Context, traceID model.TraceID) (*model.Trace, error)
	GetServices(ctx context.Context) ([]string, error)
        ...

API change
For similar reasons as in the storage API here, I would propose to propagate tenant in headers and then put it in the context.
message PostSpansRequest {
    Batch batch = 1 [
        (gogoproto.nullable) = false
    ];
}

message PostSpansResponse {
}

service CollectorService {
    rpc PostSpans(PostSpansRequest) returns (PostSpansResponse) {
        option (google.api.http) = {
            post: "/api/v2/spans"
            body: "*"
        };
    }
}

message GetServicesRequest {}

message GetServicesResponse {
  repeated string services = 1;
}

Internal metrics
Some internal metrics should include tenantID label
Any open questions to address
References
Multi-tenancy blog post: https://medium.com/jaegertracing/jaeger-and-multitenancy-99dfa1d49dc0

+1
Does it make sense to propose an API for admin functions such as listing the tenants known to storage, or configuring a list of acceptable tenants for WriteSpan?  Or are those ideas outside of the APIs and part of script tools and internal config?

Jaeger v2 will inherit the multi-tenancy capabilities of OpenTelemetry Collector, as defined here:
https://github.com/open-telemetry/opentelemetry-collector/issues/1260
For Jaeger v2, it means that we would have a configuration like this:
processors:
  routing:
    from_attribute: X-Tenant
    default_exporters: elasticsearch
    table:
    - value: acme
      exporters: [elasticsearch/acme]
exporters:
  elasticsearch:
    endpoint: localhost:9122
  elasticsearch/acme:
    endpoint: localhost:9123

This is mostly handled by the routing processor: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/routingprocessor
Would that work for your scenario?

My preference for storage APIs would be to capture tenancy explicitly as an argument, not pass it implicitly via Context.

It makes sense. I was also thinking about RBAC here and it would be maybe great to support a list of tenants? The storage could support join view across multiple tenants.

About the Jaeger V2, this is something we have been talking about a long time ago. Pity that Jaeger v2 codebase was removed in the past.
It could partially solve our use-case. In this case, the collector requires reconfiguration and restart if a new tenant is added/removed. A preferred solution is to do not require deployment changes when adding a new tenant.

Pity that Jaeger v2 codebase was removed in the past.

We decided to remove it, as it was causing tech debt that nobody was taking care of. More specifically, OpenTelemetry Collector was breaking the API compatibility at every new release, so bumping the versions at go.mod wasn't sufficient. From what I remember, the plan is still to have v2 based on OpenTelemetry Collector, we are just waiting for v1 to happen.

Thanks, @pavolloffay for starting this1 🤗
I am digesting your @jpkrohling response https://github.com/jaegertracing/jaeger/issues/3427#issuecomment-985632588, but I don't get how this is multi-tenant. It only helps with routing to hard tenant elastic backends, right?
Ideally, we have hundreds / thousands of tenants using a single Jaeger + Storage cluster. In both Cortex, Thanos, Loki and Tempo this can be solved by attaching tag/label/externalLabel/attribute to the data or group of data from single tenant. So then you can limit access, RBAC, limit resources based on requests against certain data. Ideally, cross-tenant reads are supported too. Would there be a way to just add another tag to each trace? and then expand API to treat is a special parameter when calling (could be header as well, no need for the parameter for the first iteration).

Pavol linked a blog post published some time ago on the topic of multitenancy and the different options. Typically, we've been hearing people wanting to have different storages for different tenants, which resulted in the routing processor.
Storing tenancy information as part of the span is certainly possible, but it leads to questions like:

How do you ensure the tenant ID is only set at trusted components?
What to do with traces composed of spans coming from multiple tenants? Should those spans be simply from the trace, or should people still be able to view the timing information, just not its metadata?

The routing processor would be part of a Jaeger v2 instance, so, you'd still only have one Jaeger cluster. You can also still have one storage cluster, with each tenant being an index at the storage layer.

Good points Juraci, thanks 👍🏽

How do you ensure the tenant ID is only set at trusted components?

By overriding it always on trusted proxy/collector?

What to do with traces composed of spans coming from multiple tenants? Should those spans be simply from the trace, or should people still be able to view the timing information, just not its metadata?

Good question. I think this should be simply not allowed in single iteration, i.e those never connect

The routing processor would be part of a Jaeger v2 instance, so, you'd still only have one Jaeger cluster. You can also still have one storage cluster, with each tenant being an index at the storage layer.

great!

By overriding it always on trusted proxy/collector?

It's doable, especially if we use an attribute name that is unique enough to us, like __jaeger_tenant. But in general, just overriding data is a problem waiting to happen. After all, we'd be overriding a value that was explicitly set by someone at an earlier stage.

The OTELcol proposal is missing one key use case and that is the read/query path. @jpkrohling could you please extend your proposal and include it? It might be very similar to multiple exporters but in this case using multiple extensions, here I am not sure if there can be multiple extensions of the same type.

The OTELcol proposal

What is this proposal exactly? Do you mean Jaeger v2 rebuilt on OTELcol? IMO it doesn't solve the multi-tenancy issue.

yes I mean Jaeger V2. It looks more like a workaround and pushes the heavy lifting on the user to wire/configure everything together.
From your perspective Yuri, what are the missing pieces?

I think the storage and UI need to be tenant-aware, OTELcol does not help with that.

Can we also use the service name for storage isolation in injester and query UI for adaptation

Because as a multi tenant solution in the cloud era, we need to consider being as insensitive to tenants as possible, so we may provide a general collector. In this case, I suggest that different storage resources can be adapted according to the service name. Storage resources here refer to storage clusters with the same service and different storage drivers

Maybe the point we need to change is that injester and query UI can complete this relatively complex thing

A trace usually spans many services, service name is not a tenant-like differentiator.

If this is the case, as the Infrastructure Department of a company, I provide a Jaeger cluster. If I do not distinguish according to services, it is bound to let my tenants know which cluster he uses, and I hope I can flexibly schedule the storage cluster at the back end. Because we may face hundreds of thousands of services
@yurishkuro

We may encounter the scenario of opening up and isolating certain services. It is not that the user or business needs to decide which tenant to use from input to end
@yurishkuro

Closing, let's continue discussion in #3881


stdlib.Symbols is not recognize: "undefined: stdlib.Symbols"

The following program sample.go triggers a panic:
package main

import (
	"github.com/containous/yaegi/interp"
	"github.com/containous/yaegi/stdlib"
)

func main() {
	i := interp.New(interp.Options{})

	i.Use(stdlib.Symbols)

	_, err := i.Eval(`import "fmt"`)
	if err != nil {
		panic(err)
	}

	_, err = i.Eval(`fmt.Println("Hello Yaegi")`)
	if err != nil {
		panic(err)
	}
}

Expected result:
$ go run ./sample.go
Hello Yaegi

Got:
$ yaegi ./sample.go
.\main.go:11:8: undefined: stdlib.Symbols

It worked for me in the past, I am not sure what happened.

Hello,
In the latest version the support of go1.13 has been dropped
I think that you are using go1.13, so I recommend to update your go version.

I upgraded to go1.15 and now it's ok, thanks


Failed at setup_env.py gitstatus_query_p9k_

Hi!
I'm using:

Ubuntu 24.04
clang version 18.1.8
python 3.9.19 with pyenv (2.4.1)
cmake 3.28.3

When I execute the command after downloading the model from HG:
python setup_env.py -md models/Llama3-8B-1.58-100B-tokens -q i2_s

I got this message:
INFO:root:Compiling the code using CMake.
INFO:root:Loading model from directory models/Llama3-8B-1.58-100B-tokens.
INFO:root:Converting HF model to GGUF format...
[1]    904944 terminated  python setup_env.py -md models/Llama3-8B-1.58-100B-tokens -q i2_s
gitstatus_query_p9k_:print:68: write error: broken pipe

After debugging the setup_env.py file, I found the problem raises when executing this line:
python utils/convert-hf-to-gguf-bitnet.py models/Llama3-8B-1.58-100B-tokens --outtype f32

I get a similar error during setup

It is probably because the memory exhuasted. Can you provide the device information. You can also try to run the 700M model to check whether it works.

I am also facing issues while running this command :  python setup_env.py -md models/Llama3-8B-1.58-100B-tokens -q i2_s
the issue I am facing is :
INFO:root:Compiling the code using CMake.
ERROR:root:Error occurred while running command: Command '['cmake', '-B', 'build', '-DBITNET_X86_TL2=ON', '-T', 'ClangCL']' returned non-zero exit status 1., check details in logs\generate_build_files.log

I am also facing issues while running this command : python setup_env.py -md models/Llama3-8B-1.58-100B-tokens -q i2_s
the issue I am facing is : INFO:root:Compiling the code using CMake. ERROR:root:Error occurred while running command: Command '['cmake', '-B', 'build', '-DBITNET_X86_TL2=ON', '-T', 'ClangCL']' returned non-zero exit status 1., check details in logs\generate_build_files.log

The solution I found is to use a model other than Llama3-8B-1.58-100B-tokens. You can see the solution I discovered at  https://github.com/microsoft/BitNet/issues/77#issuecomment-2436022313https://github.com/microsoft/BitNet/issues/77#issuecomment-2436022313.


Wallet runs, but user interface does not open on Linux

System Specs: AMD 3600 CPU on Manjaro (and Ubuntu VM).
The wallet works as expected on the same computer using Windows 10. On linux, the wallet process is running, but the interface is not popping up. Could it be an electron issue?

@conjohnerton is this a case of Daedalus window showing but being blank (completely white or black) or you are not seeing the window at all?

The Daedalus wallet just isn't showing a window at all! 😓
On Sat, Feb 6, 2021, 4:36 PM Nikola Glumac<EMAIL_ADDRESS>wrote:

@conjohnerton https://github.com/conjohnerton is this a case of
Daedalus window showing but being blank (completely white or black) or you
are not seeing the window at all?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/2346#issuecomment-774547514,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEMH5XA2BJWHFVHRJBG4TGTS5WY5HANCNFSM4XGTZRJA
.

Well, we are running Daedalus in Ubuntu VMs all the time. This must be related to your setup or your VM/Ubuntu config...


DCS Branch Management

Pseudo-code:
On Read
if user branch exists then attempt retrieval of USFM from the user branch;
otherwise use the master branch
On Save
if user branch exists then post/put edited USFM to the user branch;
otherwise create the branch first, then do the post/put.

[ ] If user branch exists with book, then read it; else from master branch
[ ] If user branch does not exist, create it (only checked on save)
[ ] If user branch file exists, update it on save; else create it


feat(client): Add news translation

Signed-off-by: nhcarrigan<EMAIL_ADDRESS>Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Lays the groundwork for allowing translations of the trending article links. With this foundation, it would now be possible to showcase the trending English articles for the English page, the trending Spanish articles for the Spanish page, etc.

I still need to build/expand the tests for this addition - I'm stepping out for an appointment but will work on those when I return. 🙂


[BUG] Custom Attributes on Metrics sent from Open Telemetry not appearing in App Insights

Library name and version
Azure.Monitor.OpenTelemetry.Exporter 1.0.0-beta.10
Describe the bug
Adding custom attributes to Metrics doesn't actually route the Attributes to Application Insights with the metrics
See github project here: https://github.com/joebeernink/DemoOpenTelemetry
                .WithMetrics(builder => builder
                    .AddAspNetCoreInstrumentation()
                    .AddHttpClientInstrumentation()
                    .AddConsoleExporter()
                    .AddAzureMonitorMetricExporter(o =>
                    {
                        o.ConnectionString = appInsightsConnection;
                    })
                    .ConfigureResource(resource =>
                    {
                        resource.AddService(DiagnosticsConfig.ServiceName);
                        resource.AddAttributes(customerInstanceConfig.Values);
                    }))

where the customerInstanceConfig is:
       public class CustomerInstanceConfigurationOptions
    {
        public string EnvironmentShortName { get; set; } = string.Empty;

        public string RegionShortName { get; set; } = string.Empty;

        public string StampName { get; set; } = string.Empty;

        public string CustomerId { get; set; } = string.Empty;

        public string CustomerInstanceName { get; set; } = string.Empty;

        public string Name { get; set; } = string.Empty;

        public string DnsSubDomain { get; set; } = string.Empty;

        public IEnumerable<KeyValuePair<string, object>> Values
        {
            get
            {
                var kvps = new List<KeyValuePair<string, object>> {
                            new("EnvironmentShortName", EnvironmentShortName),
                            new("RegionShortName", RegionShortName),
                            new("StampName", StampName),
                            new("CustomerId", CustomerId.ToString()),
                            new("CustomerInstanceName", CustomerInstanceName),
                            new("Name", Name),
                            new("DnsSubDomain", DnsSubDomain)
                        };
                return kvps;
            }

 And the values loaded from the appsettings.json are:

       "CustomerInstanceConfiguration": {
    "EnvironmentShortName": "dev",
    "RegionShortName": "wus2",
    "StampName": "01",
    "CustomerId": "joeb",
    "CustomerInstanceName": "001",
    "Name": "dev-wus2-01-joeb-001",
    "DnsSubDomain": "joeb001"
  }

In the values received by AI, cannot filter or group by these attributes:

Expected behavior
The attributes should show up in Application insights as part of the OpenTelemetry.Instrumentation.AspNetCore metrics and OpenTelemetry.Instrumentation.Http metrics
Actual behavior
Attributes are missing.
Reproduction Steps
See github repo: https://github.com/joebeernink/DemoOpenTelemetry
Environment
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\7.0.201\
Host:
Version:      7.0.3
Architecture: x64
Commit:       0a2bda10e8
.NET SDKs installed:
6.0.408 [C:\Program Files\dotnet\sdk]
7.0.201 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.14 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.14 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.14 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.16 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86   [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download

@joebeernink This issue is a duplicate and the same ask is being tracked in https://github.com/Azure/azure-sdk-for-net/issues/35487 . Follow the PR https://github.com/Azure/azure-sdk-for-net/pull/36027 and https://github.com/Azure/azure-sdk-for-net/pull/36063

The work items seem to be closed, but the functionality still doesn’t work for metrics as of the 1.5.0-beta release of the OpenTelemetry SDK. So is there another version coming with the fix included?
Thanks
From: navba-MSFT @.>
Sent: Wednesday, July 19, 2023 9:47 PM
To: Azure/azure-sdk-for-net @.>
Cc: Joe Beernink @.>; Mention @.>
Subject: Re: [Azure/azure-sdk-for-net] [BUG] Custom Attributes on Metrics sent from Open Telemetry not appearing in App Insights (Issue #35844)
@joebeernink https://github.com/joebeernink  This issue is a duplicate and the same ask is being tracked in #35487 https://github.com/Azure/azure-sdk-for-net/issues/35487  . Follow the PR #36027 https://github.com/Azure/azure-sdk-for-net/pull/36027  and #36063 https://github.com/Azure/azure-sdk-for-net/pull/36063
—
Reply to this email directly, view it on GitHub https://github.com/Azure/azure-sdk-for-net/issues/35844#issuecomment-1643167347 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5UXDKQ4U42MF5Z22IC3XLXRCZ4LANCNFSM6AAAAAAXM3GN7M .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AA5UXDPXVINNUDYCE3HSDCDXRCZ4LA5CNFSM6AAAAAAXM3GN7OWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTB6C7HG.gif Message ID: @.*** @.***> >


using $pull from $bind causes type error

using $pull with $bind causes the following type error
Type instantiation is excessively deep and possibly infinite. ts(2589)

Thanks for the report. Could you paste some reproduction codes?

I found that TypeScript >= 3.5 cause this error. I'll try to resolve this error.


Feature view repositories

Closes #15
Currently, the user home page is /u/{username}/repos. This takes you to the list of repositories of the user {username}. The page also features client-side searching and filtering.
Which repository will be shown depends on its visibility, whether it belongs to an organization, and the user making the request (or guest, if you're signed out). Check repo_service::user_has_read_access_to_repo() for implementation details.
Clicking on the name of any repository opens the main page of that repository, under the URL /r/{repo_canonical_name}. Page design is based on DockerHub's repository page design: there's a tabbed pane with "overview" and "tags". For now, both are placeholders as those can be a separate feature.

NOTE: I would appreciate if the code review actually had the code being... reviewed. Focus on the backend: the frontend is barebones. If you care about the web app, provide feedback on what I should change on the UI/UX side. This isn't a complicated feature but we're establishing conventions and app architecture as we go, so code review is a good place to figure out how things work. I try my best to keep the commits isolated both between layers (frontend vs backend) and between features (user vs repo vs org). All in the name of readability.

Maybe you could add placeholders for some extra features. For example:

Show the total number of repository downloads.
Add badges for three types of repositories, such as Docker Official Image, Verified Publisher, and Sponsored OSS.
Display the timestamp for when the repository was last updated.

Added. There's a new dependency in the web app, so be sure to npm i before running the app.

Add options to sort and filter tags.

I didnn't do this because I'm still not sure what a tag is, and I don't want to guess the model. Besides, tags themselves are a pretty "big" feature on their own, so I'll leave it for later.


[anza migration]: update repo path

Problem
Docs mention the wrong repo.
Summary of Changes
Update the repo path

@yihau , can you let me know how we handle agave-specific PRs?

we only have a special prefix. I just edited it!

we only have a special prefix. I just edited it!

Awesome, thank you!


rustup.exe hangs on windows and can't be killed

Another more severe issue is that rustup.exe process seem to be hanging and it cannot be killed from the Windows Task Manager. Due to this issue, I cannot remove the .cargo and .multirust directories and I have to_force_ reboote the PC to recover (using the power button).

Source.

@retep998 suggested it could be interaction with antivirus.

Not sure if this is of any help, but this is what I get when trying to kill it with taskkill:
$ tasklist.exe | grep -a rustup
rustup.exe                    1356 Console                    1      6▒480 K
rustup.exe                   11096 Console                    1      7▒072 K

C:\windows\system32>taskkill.exe /pid 1356 /f
ERROR: The process with PID 1356 could not be terminated.
Reason: There is no running instance of the task.

Regarding the antivirus, I cannot find a way to stop it as I am using a work PC and I don't have access to change the antivirus settings.
cc @retep998

I have a similar problem on a Win 7 64-bit virtual machine. No anti-virus.
I'm trying to build files from the host using virtualbox's shared folder feature.

I was hit by this issue. But I found that manual coping the proxy binary will make it works.
@echo off
setlocal
set dir=%~dp0
set files=cargo rustc rustdoc rust-gdb rust-lldb rls
for %%f in (%files%) do (
    del /q %dir%.\%%f.exe
    copy /y /b %dir%rustup.exe %dir%.\%%f.exe
)
endlocal

Run this .cmd file evertime after rustup updated.

It's been almost 6 years without any more reports or details. Should this be presumed fixed?

It's been almost 6 years without any more reports or details. Should this be presumed fixed?

Sounds good. I am going to close this issue now.


chore(NumberTheory/RamificationInertia): change the variables in inertiaDeg_algebra_tower to explicit variables

Change the variables in Ideal.inertiaDeg_algebra_tower to explicit variables, since no variables can be inferred.

maintainer merge

Thanks!
bors merge


Provide Licence so that devs are 100% sure the code is free to use

Just as the title implies, it is very important to add License to the repository

That's an oversight. Thank you for pointing it out. It will be an Apache 2.0 license like the other SDK's. This is easy enough to do but I will have to touch each file.


typescript-final: fix compile error in Typescript strict mode

typescript-final example: fix the following compile error in Typescript strict mode
Failed to compile.

./pages/posts/[id].tsx:42:40
Type error: Object is possibly 'undefined'.

  40 |
  41 | export const getStaticProps: GetStaticProps = async ({ params }) => {
> 42 |     const postData = await getPostData(params.id as string)
     |                                        ^
  43 |     return {
  44 |         props: {
  45 |             postData
info  - Creating an optimized production build .npm ERR! code ELIFECYCLE

Replaced by https://github.com/vercel/next-learn/pull/100


Definition of time period for log analytics query is both irrelevant and confusing

The "Time Period" description on this page is flawed.
First, the parameter name does not match the portal UI, which calls this parameter "Period (in minutes") making it unclear if, indeed, the doc is describing the evaluation period. Doc should consistently match the UI. Full stop.
Worse, this text is both useless and inaccurate:
"Time Period. Specifies the time range for the query. The query returns only records that were created within this range of the current time. Time period restricts the data fetched for log query to prevent abuse and circumvents any time command (like ago) used in log query."
First, "abuse" is probably not the first thing that someone reading the doc is trying to accomplish. This is the developer talking about a feature he or she implemented.
Second, "circumvents any time command (like ago)..." Say what? A perfectly acceptable query can include "[table] | where TimeGenerated > ago(5min)" to which the UI appends "| count".
Plus, elsewhere this page suffers from grammatical errors one couldn't get by a high-school teacher, for example subject-verb disagreement.
Like much of the Azure doc, this page is hot mess.

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

ID: ab89353c-6acc-9944-40e0-d8ab067e7d41
Version Independent ID: b8c18210-d14f-4b7c-aee9-545cafd20582
Content: Log alerts in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/platform/alerts-unified-log.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @yanivlavi
Microsoft Alias: yalavi

@yobyot Thanks for the feedback. We are investigating the issue and will update you shortly.

Assigning content owner @yanivlavi for visibility, review and document enhancement consideration as appropriate.

We are planning a big UX change that will remove the need to understand the period parameter.
This should resolve this issue as well.
We will be reworking the documentation for log search alerts for this as well to improve overall language and structure.

This should be resolved. We reworked all of the docs to fix the above issues.
@KrishnaG-MSFT

#please-close


[FEATURE] User and Role Collection - Add Attribute Option to resource

When assigning role collections we currently do not support the variant of --to-attribute and the --attribute-value which comes into play when the user makes the assignment and has a custom IdP in place.
The action is supported by the BTP CLI (see https://help.sap.com/docs/btp/btp-cli-command-reference/btp-assign-security-role-collection) and the scenario is a valid scenario at customers. For details see https://help.sap.com/docs/btp/sap-business-technology-platform/map-role-collections-to-user-attributes
We need to close this gap and support this as a third variant when assigning role collections to users.

Enhancements available in branch issue-31

[ ] Enhancement of code for resources (types, schema, CREATE and DELETE)
[ ] Enhancement of code in facade
[ ] Add tests for resources
[ ] add test for facade
[ ] generate documentation


[Snapshots] Cannot snapshot two previews in different files with same package

We've had a client present an edge case that causes snapshots to fail when two different preview functions live in separate files with the same package/name:
// Snapshot1.kt
package com.example

@Preview
@Composable
fun MyPreview() {...}

// Snapshot2.kt
package com.example

@Preview
@Composable
fun MyPreview() {...}

We use the FQN of the composable function as the primary key (with preview details), meaning in both cases the key is com.example.MyPreview. Depending on which is invoked first, the second will result in a crash as a snapshot with that key has already been saved.

The best workaround for this currently is one of three options:

Ensure the fully qualified name (package.method name) is unique for each preview function. This would mean moving one function to a different package.
Renaming one function, resulting in unique FQNs for both methods.
Modifying the @Preview annotation to have different parameters, as Emerge keys off a combination of FQN and preview parameters.

We're looking into use the file as an additional key in the future to solve this, but there's currently no ETA on that change.

We've added a better error state in Emerge's snapshotting UI to handle this case as an immediate fix. We'll plan to take the file name into account in the snapshot's key in an upcoming update.