Removing VMSS  VMs from AD Domain during deletion

I am currently using the "JsonADDomainExtension" extension to add VMSS VMs to an Active Directory domain upon creation/update of each VM so that we can apply policies and use AD authentication to access the VMs. However, I cannot find any method to remove these VMs from the domain as apart of their deletion from the VMSS.
Is there any method to automatically delete the computer objects from AD once a scale set VM has been deleted? Currently, it seems to be a manual process which could lead to future problems if not maintained as the scaling for this VMSS will change fairly frequently.
Thanks

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

ID: b94c5948-acb1-e3aa-7148-6aa2278bcdef
Version Independent ID: 9ada224f-5a76-bcde-2dc0-928a29c4323f
Content: Azure virtual machine scale sets FAQs - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-faq.md
Service: virtual-machine-scale-sets
GitHub Login: @mayanknayar
Microsoft Alias: manayar

@pl-araw Hope the above provided information was helpful.
We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen the issue to continue the discussion.


[Bug]: Database not generated

Contact Details
<EMAIL_ADDRESS>What happened?
I have created one database and it is functioning correctly.
However, I've tried creating additional databases and they do not generate database table. The configuration button appears in the correct spot and the markdown looks correct. But, when I open either of the new databases I create causes an error.
This error does not occur on the initial database I created.
What platform were you using?
Desktop
Version of the plugin
3.3.2
Relevant log output
Uncaught (in promise) TypeError: X.error is not a function
    at y2.eval (plugin:dbfolder:120:60233)
    at Generator.throw (<anonymous>)
    at s (plugin:dbfolder:1:799)
eval @ plugin:dbfolder:120
s @ plugin:dbfolder:1

Are you using the latest version of the plugin in your Obsidian vault?

[X] I have verified that I am on the latest version

Are you check if there is a similar issue?

[X] I have verified that there are not similar issues

It is a problem that we have been dragging on for a while.  It has to do with developer options.  Disable the logs in case the problem could be solved (dbfolder general options, last section).  For some reason it does not correctly find the error, info and warn options on some devices.  I'll keep investigating since I can't reproduce the bug

I disabled the logs and the problem is resolved.
Thank you!


build: update all tools

Closes #37

Can you please post the segemehl error and some lines of the original output of bedops and that you get with a recent version?
Did you try to look at the changelogs of the tools to try to understand why you get these differences? Are there perhaps any changes in the CLI params (new/changed) that could explain these differences? Perhaps small changes in the commands would avoid the problems.
But if you don't find anything, it's okay to keep segemehl and bedops at their current versions. Or better would be to identify an acceptable range of versions that give us the output we expect. For example segemehl might need to be at least 0.2 but smaller than 0.3.

I looked at the different manifest layers to try spot any change but it seems I did not have to be looking there. I search how to see the changelogs and it seems it is done with the docker history command but again, could not find anything (at least understandable for me).
Bedops
The bedops actual version output (mirna_filtered.bed)  is:
19	38	122	MI0003140	.	+	.	miRNA_primary_transcript	.	ID=MI0003140;Alias=MI0003140;Name=hsa-mir-512-1
19	51	74	MIMAT0002822	.	+	.	miRNA	.	ID=MIMAT0002822;Alias=MIMAT0002822;Name=hsa-miR-512-5p;Derives_from=MI0003140
19	88	110	MIMAT0002823	.	+	.	miRNA	.	ID=MIMAT0002823;Alias=MIMAT0002823;Name=hsa-miR-512-3p;Derives_from=MI0003140

The bedops updated version is:
19	38	122	.	.	+	.	miRNA_primary_transcript	.	ID=MI0003140;Alias=MI0003140;Name=hsa-mir-512-1
19	51	74	.	.	+	.	miRNA	.	ID=MIMAT0002822;Alias=MIMAT0002822;Name=hsa-miR-512-5p;Derives_from=MI0003140
19	88	110	.	.	+	.	miRNA	.	ID=MIMAT0002823;Alias=MIMAT0002823;Name=hsa-miR-512-3p;Derives_from=MI0003140

Segemehl
The error that raises is found in the rule remove_inferiors:
[ERROR] Edit distance ('NM tag') missing! at ../scripts/sam_remove_duplicates_inferior_alignments_multimappers.1_6.pl line 185, <IN> line 5.

And in fact, some others besides the one in line 5 are missing the "NM tag" when using the newest version of segemehl on the map rule (there's no problem of updating segemehl in the prepare rule but for consistency if one is not updated the other shouldn't either)

The point for checking the changelogs was to identify what changed between versions and how we could update the actual commands to give us the desired outcomes. For example, there may, in never versions, be command line options that give us the NM tag, but that now need to be specifically provided. Similarly, there may be an option to modify the bedops output such that the result is consistent with what we got with previous options.

I've check the bedops changelog; apparently the newest version puts by default the gene ID on column 4. With the argument --attribute-key you can select what you want in the fourth column. I tried to explicitly request the gene ID, I tried with the transcript_id too and both times I got the fourth column with nothing but ..
Regarding segemehl, the changes made for the new version tell nothing about the NM tag. Not even in the docu they give any command to modify the tags nor anything similar.

Maybe you should file a bug report against bedops then, as this sounds very much like a bug (unless you did something wrong, in which case they may want to improve their docs). In both cases this is on their end, and until its resolved or clarified, please keep the old version.
As for segemehl: Did you try to call it with the --help option or read its documentation to see if you find any evidence of a CLI param that may include the NM tag in the output?

It seems that segemehl should still output the NM tag: https://www.bioinf.uni-leipzig.de/Software/segemehl/
If it doesn't, it is, again, either a bug, or the segemehl command or the follow up command running into a problem may need to be modified.

Maybe you should file a bug report against bedops then, as this sounds very much like a bug (unless you did something wrong, in which case they may want to improve their docs). In both cases this is on their end, and until its resolved or clarified, please keep the old version.
As for segemehl: Did you try to call it with the --help option or read its documentation to see if you find any evidence of a CLI param that may include the NM tag in the output?

On their changelog they state to have fixed this exact bug (at least for gtf2bed). Anyways, I'll keep the actual version.

It seems that segemehl should still output the NM tag: https://www.bioinf.uni-leipzig.de/Software/segemehl/
If it doesn't, it is, again, either a bug, or the segemehl command or the follow up command running into a problem may need to be modified.

I found the problem with the output of the segemehl file. It turns out that now segemehl also returns the unmapped reads. They provide the parameter -u to drop the unmapped sequences there but the final file still contain these "empty alignments". The solution, I believe, is to create a new rule that processes the output file and removes the unaligned sequences. Should it be done in this same PR?

Yes, I agree with the extended CIGAR being potentially useful. And I also think it should go in another PR, keeping v0.2 in this one.
As for bedops: even more reason to open an issue or add on to the existing one. But yes, keep the version for now.

Yes, I agree with the extended CIGAR being potentially useful. And I also think it should go in another PR, keeping v0.2 in this one.
As for bedops: even more reason to open an issue or add on to the existing one. But yes, keep the version for now.

Please resolve the conflicts so that I can merge this PR.

With the merge with the dev branch the expected output must be changed as now miRNA annotations are not filtered (I resolved the conflict the other way around).

As for bedops: even more reason to open an issue or add on to an existing one. But yes, keep the version for now. Please link to the issue discussing the bug here (if there is one), so that we can find it back later on.

Here's the link to the issue. I already comment on it


 U: .

 U: .

 U: .

 U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 36s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 29s
master passed

+0 :ok:
refguide
3m 51s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  8s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+0 :ok:
refguide
3m 51s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Other Tests _

+1 :green_heart:
asflicense
0m 25s
The patch does not generate ASF License warnings.

25m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2913

Optional Tests
dupname asflicense refguide

uname
Linux e8a432a6afd5 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / de51a40b53

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
66 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
6m 36s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
4m 29s
master passed

+0 :ok:
refguide
3m 51s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  8s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+0 :ok:
refguide
3m 51s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Other Tests _

+1 :green_heart:
asflicense
0m 25s
The patch does not generate ASF License warnings.

25m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2913

Optional Tests
dupname asflicense refguide

uname
Linux e8a432a6afd5 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / de51a40b53

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
66 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2913/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Allow to hide custom fields in text formatter

Hello,
I'm using logrus with the evalphobia/logrus_sentry middleware to both log errors to the console and send them to Sentry.
The middleware allows to specify certain fields that have a special meaning on Sentry, such as the full HTTP request object. However, passing those fields to the logrus.WithFields() function causes them to also display on the terminal, that is not what one may want: if you put it the entire web request, it actually becomes hard to read.
So, I'm passing the fields just to have them passed on to Sentry, but I don't want them to display on the terminal.
I thought about a HideCustomFields boolean option in the TextFormatter, that solves this use case without breaking any interface.
Thanks

@informationtr is there any chance this will be reconsidered? We're still keeping a separate fork for this. Thank you!


KeyError: 'decontXcounts'

Upon running the preprocess.py, I am getting the following error-
python scripts/preprocess.py --ts_path input.h5ad --out_path input
Loaded data.
Subsetted to CCLE genes.
Traceback (most recent call last):
File "/home/namratab/namratab/TransferLearning/Comparison/exceiver/scripts/preprocess.py", line 150, in
sys.exit(main(args))
File "/home/namratab/namratab/TransferLearning/Comparison/exceiver/scripts/preprocess.py", line 53, in main
tsdata = ad.AnnData(tsdata.layers[args.count_var], obs=tsdata.obs, var=tsdata.var, uns=tsdata.uns)
File "/home/namratab/.local/lib/python3.9/site-packages/anndata/_core/aligned_mapping.py", line 113, in getitem
_subset(self.parent_mapping[key], self.subset_idx),
File "/home/namratab/.local/lib/python3.9/site-packages/anndata/_core/aligned_mapping.py", line 148, in getitem
return self._data[key]
KeyError: 'decontXcounts'
How to resolve this?

Hi @namratabhattacharya -- you need to use the --count_var command line argument to specify the layer of your AnnData object to use. For instance, we worked a lot with the Tabula Sapiens dataset, so we default to using the decontXcounts layer. If you know the analogous layer in your AnnData object you should add --count_var [layer name] when running the script. If you don't need to select a specific layer you can just comment out that line in preprocess.py.

I have run the model successfully. However, I cannot retrieve the Leiden clusters. What steps are needed for that after the model is trained?

I want to find the sample embeddings mentioned in Fig 1c in the pre-print. Is it possible to fetch the embeddings without making changes in the code?

Yeah, we currently don't have a simple function or anything that will let you get the sample embeddings for given inputs in a single line. That is a good idea and something we should add though! For now you'll need to partially go through the forward method as I described before.

@namratabhattacharya
you can add this function to the model and use it to get your sample embeddings:
def get_latent(self, dataloader):         device = 'cpu'         latents = []         self.eval()         with torch.no_grad():             for batch in dataloader:                 gene_ids, gene_vals, _, _, key_padding_mask = [x.to(device) for x in batch]                 input_query = self.query_emb.repeat(len(gene_ids), 1, 1)                 latent, _ = self.encoder_attn_step(gene_ids, gene_vals, input_query, key_padding_mask)                 latent = self.process_self_attn(latent)                 latents.append(latent.detach())         all_latents = torch.cat(latents, dim=0)         return all_latents.cpu().numpy()


Set finding is_Mitigated on finding update

fix #3026
This template is for your information. Please clear everything when submitting your pull request.
Note: DefectDojo is now on Python3.6 and Django 2.2.x.
When submitting a pull request, please make sure you have completed the following checklist:

[x] Give a meaningful name to your PR, as it may end up being used in the release notes.
[x] Your code is flake8 compliant.
[x] Your code is python 3.6 compliant (specific python >3.6 syntax is currently not accepted).
[ ] If this is a new feature and not a bug fix, you've included the proper documentation in the ReadTheDocs documentation folder. https://github.com/DefectDojo/Documentation/tree/master/docs or provide feature documentation in the PR.
[ ] Model changes must include the necessary migrations in the dojo/db_migrations folder.
[ ] Add applicable tests to the unit tests.
[x] Add the proper label to categorize your PR.

For some reasons, I think I may be missing something obvious. Definitely works for my use-case through the UI, have to look elsewhere too. @valentijnscholten ?

Bulk edit and API come to mind

Bulk edit and API come to mind

They seem work well when testing.

When searching for .active = False I see lots of results and I think 40% of them do not set is_Mitigated.

I think this one already fixes a couple issues known so far. I'd be in favor of merging, and see if we experience any more side effects of it not getting set?

I don't remember all the details from the status discssion some months ago. But if "not active" always means "is_Mitigated", then we wouldn't need 2 booleans? I think we decided back then we need 2 booleans because "not active" is not always the same as "is_Mitigated", and vice versa. If that is the case, I think we should have them seperate everywhere and always let the user decide the value for both independently.
The good thing about this PR is that it only adds 'is_Mitigated = False' in those places where we were already settings mitigated = False. So PR is good IMHO.

I'd like to ask a potentially silly question. Why is the 'M' capitalized?

Not related to PR on previous quesiton, approving.

I'd like to ask a potentially silly question. Why is the 'M' capitalized?

Aha! yup... I didn't git blame, because I don't want to know.

The good thing about this PR is that it only adds 'is_Mitigated = False' in those places where we were already settings mitigated = False. So PR is good IMHO.

mitigated is actually a timestamp. Otherwise yes, no risk.

I think we could do a migration that renames the field (in a future PR).


Scalar mult from python

Call the scalar_mult method from python.
This was mostly a way for me to get a better sense of how python and unity are communicating through zmq. I also cleaned up the logs and fixed the unity warnings.

Woot woot!


[SSR] A solution for CSS-file-based styling and importing non-js files from webpack

A solution for CSS-file-based styling and importing non-js files from webpack in server side rendering. I have made a package that allows us to import non-js files directly in server side code, without prebundling, and works just like babel-register. I just want to share it to improve other devs experience with SSR:
https://github.com/namnm/webpack-register
I also would like to create a PR and include a link in the section that warns users not to use webpack loaders to support for other non-js files.
Hope this can help somewhere.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

We can easily require non-js files from webpack bundle, like sass .scss, image .png .jpg, ... in our server rendering code.
Current Behavior

Right now, we are not recommended to use CSS-file-based styling and importing non-js from webpack in SSR, due to a bunch of practical issues...
Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

next

node

OS

browser

etc

I'm sure curious to see a working example 😄

@timneutkens I have been looking around in next.js source code, and found out that the webpack config, which next uses, is not exposed out.
But I need that config to do a compiling session first, so it's not possible here.
I wonder if we can expose the webpack config to out API or there's a way to get it before next does compiling?

https://github.com/zeit/next.js#customizing-webpack-config it is exposed :)

@timneutkens Thank you, I come up with a way that we can get the webpack config asynchronously. However I dont think this helps much, since the config is only exposed when next starts bundling, but we need to hook the extensions really soon before any of modules has been loaded.
Do we have another way to get the webpack config synchronously before any modules has been loaded?

@timneutkens Another thing, is that when we do production serving, next doesnt do any webpack stuff, and it doesnt require the next.config.js file too. So in this case, the asynchronous function to get the webpack config which I mentioned above, doesnt work too.
I think we need to export a file webpack.config.js in our next API

"Right now, we are not recommended to use CSS-file-based styling and importing non-js from webpack in SSR, due to a bunch of practical issues..."
It would be helpful if you could list down a couple of these "practical issues"


Unify Grasshopper and Rhino Installers

Unify Grasshopper and Rhino installers into a single "product".
This change is to prevent any user from installing different versions of Rhino/Gh, which will lead to errors in either side.
The cause of this was that Rhino will always load the Rhino Connector dll files first, and then GH will use whatever Rhino loaded already. Meaning that, if Rhino had a version with breaking changes in core, GH will fail to load.
This is the main cause for the famous "No default kit found" error that has been haunting us forever.
Implementation
Rhino will automatically add any Rhino Plugin path to the "Grasshopper Developer Settings" paths, allowing Grasshopper to discover any .gha files located within the plugin folder itself.
For this to work, we'd just need to add ConnectorGrasshopper as a direct dependency of ConnectorRhino6/7, so that the .gha get's copied over, as well as any other dependencies such as GHAsyncComponent.
Any other shared dependencies (Core...) will be taken care of directly by the Rhino connector project build, ending in both plugins (Rhino and Grasshopper) having all their necessary dependency dll files in one place.
How does this fix it?
Since the dll files are now the same files in the same location, we no longer need to care about Rhino loading an incorrect one.
It will also no longer be possible to have different versions of Rhino and Grasshopper, as they'll be packaged in the same Installer.

🤷🏻 Issue was never automatically closed! Closing now!


Getting internal server error. Cannot use artifactory

Trying to access to dev.azure.com, getting:

Also, since yesterday we cannot sometimes install libraries from artifactory to databricks. Error is: artifact not found.

@estatic Are you using the Artifactory extension? (https://marketplace.visualstudio.com/items?itemName=JFrog.jfrog-artifactory-vsts-extension&ssr=false#overview)
If so, https://github.com/jfrog/artifactory-vsts-extension may be the right place for this issue.
This repository is for the built-in tasks for Azure DevOps, we don't do anything directly with Artifactory


Member Not Found: ReceiveSharingIntent.getMediaStream

Hello, I am working on adding this in (thank you for developing) to my flutter app and building on iOS. I followed the instructions in your setup guide, but now I'm seeing an error when building using either the flutter command or in Xcode:
Error: Member not found: 'ReceiveSharingIntent.getMediaStream'.
I went through and double-checked my steps and I'm not seeing anything obvious that I missed. I'd appreciate any help I can get, thanks!
Note: This dart code works on Android and the sharing works just fine, so it seems to be an iOS specific issue.

Looks like I had code from an outdated version of the library. Changing to ReceiveSharingIntent.instance.getMediaStream and updating my other references seemed to fix it.


[MRTCore] ResourceNotFoundEventArgs.SetResolvedCandidate will clobber if multiple handlers registered

The function call operator for C++/WinRT's winrt::event will invoke all registered event handlers (the order is not defined and so is not guaranteed, although I assume that it is FIFO). Because ResourceNotFoundArgs does not have a Handled property (or a means to determine if SetResolvedCandidate() had been previously invoked), there is no way for a handler for the ResourceNotFound event to know if another registered handler ran first and was able to provide a ResourceCandidate; the result is that handlers which run later will clobber handlers that run earlier.
The proposal is that a boolean Handled property be added to ResourceNotFoundEventArgs.

Added ResourceMap::TryGetValue. WinUI will use that to handle when resource is not found. The chance that app itself has multiple conflicting ResourceNotFound handlers is slim. We will keep the current behavior.

Added ResourceMap::TryGetValue. WinUI will use that to handle when resource is not found. The chance that app itself has multiple conflicting ResourceNotFound handlers is slim. We will keep the current behavior.


argmax failes the test

The argmax test passes with cargo test but fails with cargo test --release on my laptop, making it an interesting case for me. You can see the screenshot for the line number. To recap, argmax(None, false) admits distinct results under debug or release mode.

Thanks for reporting this, this seems very odd indeed and a bit scary.
The handling of None has been added in the last few days as well as this test. Looking at the output of your screenshot, it's as if it was not using None.
I ran the test on a couple computer locally today without hitting this issue. Could you try re-running the tests after a cargo clean? (I weakly suspect that incremental compilation is not working properly when the generated c++ files change)

Yes, cargo clean effectively eliminates the error. So the crate does not regard the version of C++ API?

Yes, this was actually something that has been overlooked in the compilation process (rust gets the rust dependencies for you but doesn't help on the c++ dependencies), I just pushed some changes that should help with this by triggering a recompilation when needed.

Thanks! Let's close this issue.


Latest version refuses to create windows? (any windows at all, not just new ones)

I'm running the latest brew/cask version of MacVim (I think? v8.0-134) on Mac OS 10.11 El Capitan. Pretty sure it's not my vimrc (I've tried removing my entire .vim directory, and still no luck), and I don't think I upgraded between the last time it worked and the first time it didn't, but all of a sudden, invoking MacVim from Finder (or double-clicking on text files, which are configured to open in MacVim by default) launches the application, but no window.
MacVim appears in the dock, is the active program in the CMD-tab app switcher, and has all its regular menus, but just won't open any windows. The only way I can get GUI vim to open a window is by calling mvim from the command line. Even then, CMD-n doesn't create a new window, either. I just get the one that opened on application startup.
I've tried brew cask uninstall macvim && brew cask install macvim. I've even tried sudo find / -iname "*macvim*" and then deleting all the leftover settings and temp files before reinstalling again, but still no dice.
This even occurs with the pre-built .dmg release.

As mysteriously as it began, this problem has disappeared.
(FWIW, I had reformatted my laptop in the interim and got everything set up on it again; MacVim was working just fine on a fresh install then, even with my old dotfiles, which I keep synced between machines.)


[Vertica] Can't execute a query if semicolon is on a new line

System information:

Operating system (distribution) and version Win10
DBeaver version 22.0.3

Steps to reproduce, if exist:

Open SQL Editor
Input a query with a semicolon on the next line
Try to execute a query

Expected: Query is executed
Actual: Query is ignored

Seeing this issue too for queries against Snowflake, but not when using Postgres.
I think this started in 22.0.1 or 22.0.2 - can try older version to verify if needed.

Verified


[Bug]: No code action found for create variable inside a annotation

Description
@test:Config {enable: enable2<CURSOR>} // No code action found for create variable for `enable2`
function testFromCsvWithTypeForRecordAndRecordAsExpextedType() {
    // logic
}

Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

The code action is based on the diagnostic variable assignment is required (BCE2526), and in the source you have provided, this diagnostic is not produced.


Tech stack visualization

Now that we have the full post text, we can generate tech stack visualizations similar to how github does breakdowns for languages used in a project

Add word maps


[Bug] Initial unknown scan progressible not visible anymore

For the games that are not known to the Studio, a progress bar should pop up showing the table scan progress.
This one seems to be gone.

Fixed with 3.7


Apply read_write_timeout to Unix socket connections.

I noticed my Predis connections timing out on long running Unix socket connections even with read_write_timeout set to 0. It looks like it only gets set when using TCP connections.
I copied the code from the tcpStreamInitializer() method right above it which is not necessarily nice but gets the job done. Please bear with me if I missed something since this is my first contribution on GitHub ever. :)

Thanks @srhnsn this will do for now for v1.0, I will most likely change how the underlying resource is initialized in v1.1 to reuse most of the code which is shared anyway when using PHP streams.


[BUGFIX] Fix linspace

Description
Fix #19825
Previously both mx.np.linspace  and numpy.linspace round towards infinity for negative int values. numpy.lincpace recently fixed this to round towards -infinity in: https://github.com/numpy/numpy/pull/16841. This PR makes the same change to mx.np.linspace and make it compatible with numpy.linspcae.
Checklist
Essentials

[ ] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-bot run ci [unix-cpu]


OIDC Provider with Import Cluster.

Is your feature request related to a problem? Please describe.
OIDC Provider with Import Cluster.
Describe the solution you'd like
OIDC Provider with Import Cluster.
Describe alternatives you've considered
OIDC Provider with Import Cluster so additional step is not required
Additional context
Add any other context or screenshots about the feature request here.

@shapirov103 Will you be able to help with this ?

@elamaran11 the OIDC provider of the imported cluster is supported now. What is not support is OIDC provider creation in case the original cluster does not have OIDC. We should review this issue through the lens of IRSAv2 and see if can simplify this process. v2 should eliminate the need for OIDC and trust relationship between roles in IAM and specific clusters. Let's review and yes, I may be able to help with it.


Upstream IPC: Web container => Jasonette

This PR allows a web container to reach outside of its own sandbox and call its parent Jasonette native app's JASON actions, simply by calling:
JASON.call(/****JASON ACTION****/)

from its javascript. You just need to pass the same action JSON as an argument. Here's an example:
{
  "type": "html",
  "text": ""
}

Another example:
{
  "type": "html",
  "text": ""
}

This is part 1 of the full IPC architecture as it addresses only the webcontainer ==> Jasonette direction communication.
The part 2, which is the opposite direction (Jasonette ==> web container), is much more complicated and involves introduction of multiple APIs since it needs ways to describe how to:

Identify each web container component with a unique identifier
Keep track of all the web containers that can be messaged
Dispatch a Javascript function call to only the intended web container

Part 1 is already useful for many cases and it looks like Part 2 will take some time to figure out, which is why it's broken down into two parts. The part 2 will be a separate PR.

@gliechtenstein would it be worth adding the above notes to the documentation issue for this ?

@mak done:) https://github.com/Jasonette/documentation/issues/66#issuecomment-321828003


[Feature][Zeta] Improve local mode startup request ports

Purpose of this pull request
close #4607

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

@hailin0 please help review, thanks.

Can you add test case for this change? Like use e2e create two local mode job in one container at same time.

./bin/seatunnel.sh --config ./config/v2.batch.config.template -e local

i run this command with zeta engine, it shows successful


Login page link to switch to AP provider is hidden behind log in button

Setup

Rancher version:
Rancher UI Extensions: post 2.7.5
Browser type & version:

Describe the bug

Link to switch log in page to the AP log components is hidden behind the button to log in as local user

To Reproduce

Setup auth provider (github is easiests
log out
switch to local user view

Result

see screenshots

Expected Result

switch screenshots around

Screenshots
Before

After

Additional context

See https://github.com/rancher/dashboard/pull/9261#issuecomment-1620365251

Automation failed, moving to test

Pass verified fixed in rancher v2.7-head commit ID 027246f

navigated to hamburger > users & authentication
clicked on auth provider
enabled github oAuth
logged out
naviagated to rancher URL in incognito window
confirmed login options as expected


How to register model chooser without touching the original models.py code ?

In documentation, you mentioned: "To enable the chooser for your model, you must register the model. For simple cases, decorate your model with @register_model_chooser".
How would you register the model in other cases ?
For example, I have a Django project to which I additionally added Wagtail. So I still have many pure Django apps. And I don't want to touch their source code so registering them with decorator is not an option for me.
Is there another way to register models ? Could I import this models into Wagtail app and make registration there ?

I haven't tested this but you should be able to call register_model_chooser as a function, so something like this should work
from wagtailmodelchooser import register_model_chooser
from other.package.models import Thing

register_model_chooser(Thing)

as long as you put this somewhere that's called on startup like wagtail_hooks.py or models.py I believe this should work. If it doesn't then we should look into making it work, let me know!


Increase max guest execution to 2^24 steps

Notes
The guest previously had a soft cap of 2^20 execution steps and 2^20 words of memory. This change increases both limits to 2^24 steps, which is the hard cap for the current circuit.
Per conversations with @jbruestle, increasing the cap will slow down proving by about 5% for all programs.
Changes

Increase kMaxCyclesPo2 from 20 to 24
Increase kMemBits from 20 to 24
Increase kDataSize from 160 to 162
Modify memory layout in memory.h and risc0.ld
Replace hardcoded 20 with kMemBits in mem_check.cpp

Unfortunately this also causes creation of MethodIds to become 16x slower. To address this, I've pushed #167 which provides a way to specify the expected max code size. Because of the build perf impact, I've set the default to remain at 12 (which is what it would be prior to this PR, e.g. kMaxCyclesPo2 = 20). Currently #167 only supports specifying the limit on targets using bazel. It should be easy to add support for rust targets using cargo.
@preston-evans98 Would this be sufficient for your use case?

Note that before this can land, the following memory locations need to be updated in rust code as well:

risc0/zkvm/sdk/rust/guest/src/lib.rs#L37
risc0/zkvm/sdk/rust/guest/src/gpio.rs#L15

Unfortunately this also causes creation of MethodIds to become 16x slower. To address this, I've pushed #167 which provides a way to specify the expected max code size. Because of the build perf impact, I've set the default to remain at 12 (which is what it would be prior to this PR, e.g. kMaxCyclesPo2 = 20). Currently #167 only supports specifying the limit on targets using bazel. It should be easy to add support for rust targets using cargo.
@preston-evans98 Would this be sufficient for your use case?

Yes, this is fine for our use case - please feel free to close this PR.


Add typescript support

It would be great if you could add type definitions as this would greatly improve the developer experience.

This issue was closed in #11


Timeline

An advertisement remains online for a certain period of time. This online time is configurable per category by the user with admin rights. For example, the online time for real estate category is 6 weeks.
During the online period of time, the advertisement can be changed or deactivated by the add owner.
Precondition: User profile should be implemented

Precondition not fulfilled yet.


Modification on Model to work on (x,y) scalars not y obly

Hello,
I'm using your model in a prediction problem for creating more training samples, and the results are really promising. In my problem the labels are co-ordinates, so I have two scalers (x, y) as label not only (y). Could you give me a hint on the route to modify model to achieve this? and Thanks!

I'm currently also handling with two scalar values (x, y). I made the CCDM model working, but not sure if the process is right. When calculating the vicinal parameters, I just used the average of labels (x and y) but I feel like conditional projection with two labels isn't that easy. Is there any other way you could suggest?


Configurable UA.stop() on page unload

I'd like to ask to make UA.stop() on 'unload' event to be configurable.
I think, most of users need the current behavior but I need UA.stop() not to be called to be able to recover call after page refresh.
If you are ok with making it configurable, I can implement it myself and create pull request for you.
To be more clear, I'm about the following piece of code in UA.js
  if (typeof environment.addEventListener === 'function') {
    // Google Chrome Packaged Apps don't allow 'unload' listeners:
    // unload is not available in packaged apps
    if (!(global.chrome && global.chrome.app && global.chrome.app.runtime)) {
      this.environListener = this.stop.bind(this);
      environment.addEventListener('unload', this.environListener);
    }
  }

I'd like to have it like the following:
  if (this.configuration.autostop && typeof environment.addEventListener === 'function') {
    // Google Chrome Packaged Apps don't allow 'unload' listeners:
    // unload is not available in packaged apps
    if (!(global.chrome && global.chrome.app && global.chrome.app.runtime)) {
      this.environListener = this.stop.bind(this);
      environment.addEventListener('unload', this.environListener);
    }
  }

Default value of 'autostop' could be true.

We would definitely take a pull request for this. I would like to maintain backwards compatibility, so the default would be to autostop. Thanks!

Please look at this change.

Solved now, thanks a lot!


WRQ-25355: A video player sample playing google video ads

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
https://github.com/enactjs/enact/issues/3245
Following this issue, I made a Sandstone VideoPlayer sample playing Google Video Ads.
Resolution
According to google adsense help, IMA SDK is needed to play google ads in a custom video player.
(Guidelines: https://support.google.com/adsense/answer/6391192?hl=en&ref_topic=1706004&sjid=6550346971434809951-AP)
So I integrated IMA SDK in a sample app, following the tutorial.
(Tutorial: https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side)
And I adjusted some details to make it work with sandstone video player.

adContainer node is placed in front of the VideoPlayer component to toggle the media controller by clicking the video layer.
playPauseButton is disabled before initializing IMA and during playing the ad.

Additional Considerations
Links
WRQ-25355
Comments
Enact-DCO-1.0-Signed-off-by: Jiye Kim<EMAIL_ADDRESS>

Added guide comments to App.js.
For errors on devtools when run the application,

imasdk.googleapis.com/js/core/bridge3.658.1_en.html#goog_271167832:1 The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol.

This error only appears on a http (untrustworthy) page, not a https page. As the log says, ads should be requested on a https page.

Blocked script execution in 'about:blank' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.

I couldn't find this error log.

LGTM but I switch to Draft PR because it doesn't fit the purpose of the Enact sample.


Approaching 1.0: SASS & Markup

I am officially putting on my calendar to start in the next couple weeks on building out FlipClock into a proper SASS structure. I wanted to outline my plans and thoughts here and get some preliminary feedback before I got too deep. I know some previous discussion has taken place on the subject, but I think a consolidated thread for discussion of the topic would make sense.
SASS Structure
I would like the structure of the files allow for easy inclusion of different clock face themes. Additionally, the variables should be set in their own file as well. Any mixins used from external libraries like Bourbon should be included in their own file so anyone compiling CSS for the project or making changes will be able to do so standalone.

flipclock.scss

core

_variables.scss
_mixins.scss
_base.scss

themes

_default.scss

I have considered adding in an animations.scss file, but for the time being, those can exist as mixins in the mixins.scss. In addition to the default face flipping, I have some ideas on how to make a glowing clock face and one that fades in. If it gets crazy, I may include those separately in another file. But for now, I feel like the above outline makes sense for the project.
flipclock.scss
This file will include all project SASS files for compiling.
_variables.scss
This file will include all variables for the project. These variables will all be declared as !default values, so they can be overridden in default.scss files if needed. All variables in this file will be the defaults to give base.scss it's bare-bones structure.
_mixins.scss
This file will include all mixins for the project. Anything used from external libraries should be added here. The project should compile without any external library dependencies.
_base.scss
The base structure for the project is here. If browser normalizing is needed, it is done here. This is the scaffolding for clock face themes to be built on.
_default.scss
Themes will extend the base.scss styles. I'd like to put together maybe 2-3 themes initially. This would allow people the option to switch out themes easily with the refactored SASS and also provide examples of what is possible with the themes if someone else wants to create their own.
Project Markup
I am fairly certain that the project will need some updates on markup for a couple reasons. I will build an initial, static example of what I feel this markup should be with the base.scss components to illustrate this point.
The main reasons I see the need for this:

True responsive clock
Dynamic centering labels above clock face sections

Right now both of the above are a bit tricky and require a lot of browser specific stuff going on to accomplish. With a couple minor updates to the markup, this could be fixed. I'll put something together and throw it on Codepen to illustrate this when I'm ready to move forward.

Feedback
I'd love some feedback on this if anyone else has any. And we can make this thread the go-to for discussion on the topic for the next week or two before I start. Once I begin, I can post updates and ongoing discussion of the work can take place here as well.
Thanks for taking the time to read my long post.

I just made a new "dev-1.0.0" branch for us to work and get this new version going. I am thinking about a series of changes on my end and refactoring the API's to be more coherent and easier to use/extend. Likely going to be some breaking API's changes, but will be for the better.
Looking forward to seeing what you do so I can make further improvements.

Thanks, Justin:
I'll actually dive into this a bit probably sometime this evening and
start getting things set up. I think I might actually make a static
test.html for doing the styling on just to make things easier. And this
way if I have to make any markup changes in 1.0, you'll have a guide for
that.
Regards,
Brian
-- BRIAN ESPINOSA
UI/UX
Designer, Font-End Developer
1105 Carey Dr. | Unit 201 |
Concord, CA 94520
direct:<PHONE_NUMBER>
office:<PHONE_NUMBER>
Justin Kimbrell wrote:
I just made a new "dev-1.0.0" branch for us to work and get this
new version going. I am thinking about a series of changes on my end and
refactoring the API's to be more coherent and easier to use/extend.
Likely going to be some breaking API's changes, but will be for the
better.
Looking forward to seeing what you do so I can make further
improvements.
—Reply
to this email directly or view
it on GitHub.

I just pushed a massive series of updates to the dev branch. This is a great start to the new v1. The individual components are each more simple. I really focussed on proper abstractions and reusable/extendible components.
I also added the ability to have alphabetical clocks, so numbers aren't even a requirement anymore. This will definitely pave the way for the edit you make and then making all the responsive stuff work properly.

This is exciting. I'll
pull these in tonight. I have meetings in San Francisco today all day. I
am going to add the scaffolding for the styles and get some elements
added either tonight or if not, over the weekend.
I've got a couple different clock face ideas that I'll be testing with
the markup before I finalize if anything need to be changed. One face is
a rolling number instead of a flipping number. I think I'll still be
able to do that with the existing markup.
I'll let you know when I have something to look at!
Regards,
Brian
-- BRIAN ESPINOSA
UI/UX
Designer, Font-End Developer
1105 Carey Dr. | Unit 201 |
Concord, CA 94520
direct:<PHONE_NUMBER>
office:<PHONE_NUMBER>
Justin Kimbrell wrote:
I just pushed a massive series of updates to the dev branch. This
is a great start to the new v1. The individual components are each more
simple. I really focussed on proper abstractions and reusable/extendible
components.
I also added the ability to have alphabetical clocks, so numbers
aren't even a requirement anymore. This will definitely pave the way for
the edit you make and then making all the responsive stuff work
properly.
—Reply
to this email directly or view
it on GitHub.

As I am laying out the files for this, rather than having people include and compile their themes based on the scss files, I think I am going to keep the reset/base styles as one style sheet and then have each theme be its own style sheet. So you'll include the flipclock.css and then a default.css (theme) directly after. What are the thoughts on this? I could also set it up to where the theme imports the reset and base styles as well and then there is only a single include. The pros to this would be a single file call and it would also allow you to override any scss variables inside the reset and base scss... which would allow for others to make more complex themes if they wanted.

Hmm.... I wish there were some more people that specialize in that sort of thing left to comment. As previously states, I don't use sass personally, so it's hard for me to comment beyond my experience with other libraries in relation to the design patterns they use. I think it's more common to see the former approach with a base file and theme file.  A very popular date picker library does the same thing, http://amsul.ca/pickadate.js/. But I also see your point of leveraging the real power of the scss variables and having a truly extendible themes API. As a programmer and engineer, I tend to always opt for decoupling components when necessary so if I had to vote either way with my limited knowledge of sass, I would have to opt to go with a base file and theme file.
Thinking of strict OOP design, is it possible to have a base theme file which the default theme would extend? I am not sure how scss works on a technical level, but this seems like it should be possible. So in theory on the front-end the user would only include "default.css", which extends "flipclock.css" base styles. Again, not even sure if this solves the problem but just a thought.

There are definitely pros and cons to each. Personally I am leaning a bit more towards a base CSS file and then a theme CSS file to include afterwards. This will make implementation easier for less experienced users I think. And anyone who wants to do more, they could always take the separate SCSS files and compile/minify them as they see fit with minimal effort. In my own projects I'll definitely be compiling one minified file. But I am leaning towards separate files for an open source project like this for ease of implementation. Sounds like we both feel the same way on this.

Sounds good to me.

Getting eager to see what you are cooking up over there! :)
I am ready to implement your new markup changes whenever. I literally abstracted every component of FlipClock. The new dev branch is really shaping up and pretty much finished with my changes until you have the new responsive stuff finished (no rush btw).

I keep getting pulled away on other projects, unfortunately... but I think I should have a huge chunk of time in the next few days to get something pushed to the dev repo to check out. I keep refactoring as I push things around and separate the logical items for framework versus actual theme.
Go ahead and send me access to that repo. My username on there is the same as here.
Is the CMS you are using Craft?

No worries, I know how it goes. I am actually using Statamic for this site. I have considered switching it to Craft CMS (which I love) but I am not sure we need a dashboard/publishing UI, admin logins, or a database. Right now it's built as a file driven CMS, so only PHP is needed (no db required).

Ok so I mistaken. Bitbucket is not where I am hosting the repo for the docs. It's actually on Beanstalk for automatic deployments. What email should I send the Beanstalk invite to?

What ever happened to this enhancement? It would be REALLY helpful right now.

I'm also wondering what happened to this? I've just used the clock in quite a fun project however I had to do some hackery due to inflexible nature of the current theme.

+1 for an update

+1 Is there any more information about this?

+1 any update on making flipclock inherently responsive?

+1 Would be very useful

Hi All:
An update on this... I have actually completed a style and markup overhaul for Flipclock in our dev branch. You'll be able to very easily scale Flipclock now. This was a 1:1 conversion of display so I have not created any other other clock face themes yet, but I will be getting to that in the next couple weeks. The nice thing is visually most of the work has now been done. The markup now needs to get sliced up and put into the dynamic modules in the plugin.
@objectivehtml is also working on some updates to the API so there's some more work to be done there as well. I'll drop in here when there's something more to see. Currently all that would be visible to you in the develop branch is new styles working (with better framerate performance) and a responsive example.
Thanks for being patient while we both juggle work and open source stuff.

Nice work dude. I am moving to Colorado at the end of this week. I will take a look at these updates first chance I get.

So was this feature added in the end? If so how can we use it?

@AdiRishi Yes, we are still in the process of implementing these updates. There will be 3-4 clock face themes to pick from, including the original style. And they'll all be responsive. The original clock face is already done. The next faces are being worked on now. This is a pretty massive update to the project visually and with the API... @objectivehtml and I have both been very busy with our day jobs as well so this has not been going as fast as we would have liked but there's been lots of movement in the last month. Hang in there.

Any updates on this?

@inspireme247 I have not had a chance to make any more progress on this. Day jobs have been pretty demanding.
To anyone else wondering about the progress of 1.0, we will definitely be posting updates to this thread so you're best off subscribing to it rather than asking for updates.
Thanks for your interest in the plugin!

@brianespinosa Have you thought about just releasing it as is and making the new faces 1.1?

@etcook the markup and API are changing which is not complete yet. When we have all of those pieces working if we still do not have the new faces done we will still release at least a beta when it is working and let the faces catch up. So basically we would be doing that if it happens that I get behind on my part.
You can take a look at the progress in the 1.0 branch if you're curious.

Despite this being long overdue, just wanted to update this thread. Hoping to get in more with FlipClock in the coming weeks and push forward to the 1.0 updates, where I hope we can start to have a much more active and up to date repo/project.
I've been working quietly in my free time trying to get the bugs worked. FlipClock 1.0 will definitely have full support for Browserify, Webpack, RequireJS and all the latest JS techniques. I've been working on all this stuff on other projects with my paid work, and it's 100% obvious FlipClock is dated and needs these updates.
Appreciate the support and everyone using this library. Definitely going to get it up to speed and more actively supported in the coming weeks.

Any updates on this? FlipClock is a beautiful widget but I'm finding it difficult to resize any part of it without causing graphical glitches.

Manually resize it with media queries, I've done it which can be seen at
deafab.co.uk
On 30 March 2017 at 22:33, Andrew Hamilton<EMAIL_ADDRESS>wrote:

Any updates on this? FlipClock is a beautiful widget but I'm finding it
difficult to resize any part of it without causing graphical glitches.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/objectivehtml/FlipClock/issues/161#issuecomment-290551359,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIE_ynLGEEn1cWC5sl3Xz43Uh7rRCfiUks5rrB-VgaJpZM4DF0WW
.

😞 Been fiddling with the .css for hours and cannot get it to be responsive. Looking forward to the upcoming release...

Following through with this again. The new js-es6 branch has all this code integrated, and completely rewritten the JS with ES6 syntax, webpack support, and much more. Going to be re-releasing the docs, as the syntax and API's have changed.

Will close this issue once v1.0 has been officially released.


Is this name decided on purpose?(doge

Of course, this is just a joke so there is no need to answer it.


Request for feature: Use variables

Allow declaration of variables (with their type, and their default value) via the meta
On a widget, allow changing the value of the variables

... and what do you think about global variables ? Which can be understood of two different ways :

Every widget has the same global variables (ex : background-color, background-opacity) I can set individualy on each widget
and/or I can set a variable globally for all the widgets
To be discussed further... :)

Are you referring to "only" css variables? If that's the case, wouldn't a best approach be to include a default "default.css" file that each .css files inherits from? Then if you want to set specific rules for specific widgets, all you have to do is overwrite the css-rule in the widget itself.


support install multi vsixs via cli in one command

In a offline env of Windows.
I need to install a lots of offline-visxs.
could we install vsixs via one command:
 code --install-extension .\snippets-plus-1.2.0.vsix .\vscode-gerrit-helper-0.0.9.vsix
thanks
 code --install-extension .\snippets-plus-1.2.0.vsix .\vscode-gerrit-helper-0.0.9.vsix
Installing extensions...
(node:22012) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `Code --trace-deprecation ...` to show where the warning was created)
Extension 'snippets-plus-1.2.0.vsix' was successfully installed.

You have to repeat --install-extension for each vsix. say: code --install-extension .\snippets-plus-1.2.0.vsix  --install-extension .\vscode-gerrit-helper-0.0.9.vsix


Create Kani Github Action

It might make things easier for customers if they can simply make use of a github action to run Kani on their code. Ideally this would be as simple as (for example) how we publish our ghpages:
- name: Run proofs
  uses: model-checking/kani-github-action@v1

Just heard about a project that would be interested in using an action like this.
By default, it should run cargo kani. But we should also provide the option to call a set of proofs, or exclude some proofs from executing (this is desirable if some proofs are failing, since we don't have the "expect-fail" annotation yet).
Another thing to take into account is that some proofs may need to enable flags. Do we want an annotation for extra flags?

Yeah, I think the idea is for annotations to do that work. I'm not sure if they could be arbitrary flags (easily, that is, it'd take some work to restructure how we do things...)

+1 for this feature. We had potential customers at my mid-internship talk who would be interested in using it in CI. Implementing it would go a long ways in terms of easing adoption.

There are some docker files that already exist for testing the Kani install procedure on different OSes that might serve as a starting point. For instance here is the ubuntu-latest one: https://github.com/model-checking/kani/blob/main/scripts/ci/Dockerfile.bundle-test-ubuntu-22-04

More details in #1587, but I think it would be better experience
customer-side if the actions uses a pre-built docker image that is
stored on GHCR/ECR. That's how it's done for codeguru etc.
I'll PR the action.yml and test by hosting the image on my fork with
GHCR, but I would like a discussion WRT to the permanent solution.

Released action


[iOS] Program Catalog

As a user I want to see all programs on the platform so that I can select the program.

Implemented through webview in the Discover tab. Closing ticket.


Hello, is there any plan to support reading in CSV file format

ATT

See https://github.com/MarkPflug/Sylvan, where the Sylvan.Data.Csv project lives. The fastest CSV parser for .NET.


VarQte MVP

Summary
This PR introduces Variational Quantum Time Evolution algorithms, imaginary and real, to the algorithms module. It uses variational principles: real McLachlan's, imaginary McLachlan's and real Time Dependent. It is part of the bigger framework for Quantum Time Evolution and implements the relevant interface.
The work is based on the PoC by @Zoufalc which has been significantly redesigned. The correctness has been cross-checked with the PoC.
Relevant papers:
https://github.com/Qiskit/qiskit-terra/pull/7349#issuecomment-985339705
It closes the following epic: https://github.com/Qiskit/qiskit-terra/issues/6838 and the following associated issues:
Closes: https://github.com/Qiskit/qiskit-terra/issues/6912,
Closes: https://github.com/Qiskit/qiskit-terra/issues/6913,
Closes: https://github.com/Qiskit/qiskit-terra/issues/6914,
Closes: https://github.com/Qiskit/qiskit-terra/issues/6915,
Closes: https://github.com/Qiskit/qiskit-terra/issues/6916,
Closes: https://github.com/Qiskit/qiskit-terra/issues/6931,
Closes: https://github.com/Qiskit/qiskit-terra/issues/7268,
Closes: https://github.com/Qiskit/qiskit-terra/issues/7070,
Closes: https://github.com/Qiskit/qiskit-terra/issues/7143,
... .
Details and comments
Things that will be addressed in separate PRs:

Calculating error bounds.
Implementation of the gradient() method in varqrte.py and varqite.py
Saving intermediate results to log files. https://github.com/Qiskit/qiskit-terra/issues/6935
Option for an error-based ODE function.

TODO:

[ ] Add unit tests with aux ops.
[ ] Add unit tests for errors raised in case of invalid bases and methods combinations.
[x] Fix 2 failing unit tests due to change of possible inputs in the gradient framework.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

309 of 326 (94.79%)  changed or added relevant lines in 21 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 83.815%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/algorithms/evolvers/variational/solvers/ode/abstract_ode_function_generator.py
18
19
94.74%

qiskit/algorithms/evolvers/variational/var_qite.py
24
25
96.0%

qiskit/algorithms/evolvers/variational/var_qrte.py
24
25
96.0%

qiskit/algorithms/evolvers/variational/variational_principles/real/implementations/real_mc_lachlan_variational_principle.py
27
28
96.43%

qiskit/algorithms/evolvers/variational/var_qte.py
57
59
96.61%

qiskit/algorithms/evolvers/variational/variational_principles/variational_principle.py
14
16
87.5%

qiskit/algorithms/evolvers/variational/calculators/metric_tensor_calculator.py
14
18
77.78%

qiskit/algorithms/evolvers/variational/calculators/evolution_grad_calculator.py
20
25
80.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
53473

Relevant Lines:
63799

💛  - Coveralls


Fix compilation warnings with GCC on Linux

GCC doesn't understand how to use printf with the standard
integer types. To get them to work, you have to use some
macros, which this patch uses instead.
Signed-off-by: Rian Quinn<EMAIL_ADDRESS>

Personally don't agree with moving doxygen data from the headers to the sources but the inttypes change is fine.

Will move the API docs to the .h, and update the Governance Model in a separate (soon) pull request


Can I select it accurately?

2019-04-30 16:06:11.355  INFO 9256 --- [           main] ShardingSphere-SQL                       : Actual SQL: gds-member ::: select * from member_1 join member_info_2 on member_1.id=member_info_2.member_id where member_1.id=? ::: [1123130828618035201]
2019-04-30 16:06:11.355  INFO 9256 --- [           main] ShardingSphere-SQL                       : Actual SQL: gds-member ::: select * from member_1 join member_info_0 on member_1.id=member_info_0.member_id where member_1.id=? ::: [1123130828618035201]
2019-04-30 16:06:11.355  INFO 9256 --- [           main] ShardingSphere-SQL                       : Actual SQL: gds-member ::: select * from member_1 join member_info_1 on member_1.id=member_info_1.member_id where member_1.id=? ::: [1123130828618035201]
tables: member   and  member_info
member_if   insert by member.id  so,they are the same node.just like
when the id is<PHONE_NUMBER>618035201,the data should be in member_1 and member_info_1
but the sql select 3 times;
can i have a way to configure the problem;

Hi @weikangqq, you can try to use binding-tables,
configure like
// spring boot properties
spring.shardingsphere.sharding.binding-tables= member, member_info

other configurations can see 4.1.2. Configuration manual


kernel/sched: Fix edge case in MetaIRQ preemption of cooperative threads

When a MetaIRQ preempts a cooperative thread, that thread would be
added back to the generic run queue.  When the MetaIRQ is done, the
highest priority thread will be selected to run, which may obviously
be a cooperative thread of a higher priority than the one that was
preempted.
But that's wrong, because the original thread was promised that it
would NOT be preempted until it reached a scheduling point on its own
(that's the whole point of a cooperative thread, of course).
We need to track the thread that got preempted (one per CPU) and
return to it instead of whatever else the scheduler might have found.
Fixes #20255
Signed-off-by: Andy Ross<EMAIL_ADDRESS>

@wopu-ot already has a test written as part of #20662 actually.  For sure that needs to be split out and added.

Could a preempted cooperative thread migrate to a different CPU? If that is the case, the metairq_preempted field would not be reset and next_up would see stale information.

Could a preempted cooperative thread migrate to a different CPU?

It cannot.  The preempted thread never gets requeued, so it will never be seen by the scheduler logic until it gets picked up on metairq exit.

Realized this morning there was a missed edge case: if a thread gets suspended while a metairq is running and the metairq returns to a different thread, the existing metairq_preempted field would be left non-NULL and that thread, if enabled later, would get incorrectly run on exit from a future metairq even though it hadn't been preempted.
Fixed, and cleaned up the nullification of that field so that it always happens on metairq exit (or if the existing preempted thread is detected to be non-runnable) regardless of what thread might have been stored.

Maybe I am missing something, but the updated commit looks just like to original commit to me?

Oops, must have missed a git add.  Should be fixed.  For review, this is the diff from the original:
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -182,6 +182,8 @@ static ALWAYS_INLINE struct k_thread *next_up(void)
        if (mirqp != NULL && (th == NULL || !is_metairq(th))) {
                if (!z_is_thread_prevented_from_running(mirqp)) {
                        th = mirqp;
+               } else {
+                       _current_cpu->metairq_preempted = NULL;
                }
        }
 #endif
@@ -319,7 +321,7 @@ static void update_metairq_preempt(struct k_thread *th)
        if (is_metairq(th) && !is_metairq(_current) && !is_preempt(_current)) {
                /* Record new preemption */
                _current_cpu->metairq_preempted = _current;
-       } else if (th == _current_cpu->metairq_preempted) {
+       } else if (!is_metairq(th)) {
                /* Returning from existing preemption */
                _current_cpu->metairq_preempted = NULL;
        }


Improve handling of anomalous SUBSCRIPTION_CREATED RealmAuditLog entries when upgrading to 8.x.

See https://chat.zulip.org/#narrow/stream/31-production-help/topic/Failed.20upgrade.20to.20zulip.208.2E0/near/1712411 for context.

Closing as we suspect this only affects one installation; we at least don't see a mechanism through which this state would have been created.


Sync fails to build IDE files because the set constructor for depsets is deprecated.

Using CLion 2017.1.3 with the Bazel plugin 2<IP_ADDRESS>.1, and Bazel 0.6.0-homebrew.
I import the sample clion-bazel project, click Sync, and I see it fails because "The set constructor for depsets is deprecated and will be removed. Please use the depset constructor instead. You can temporarily enable the deprecated set constructor by passing the flag --incompatible_disallow_set_constructor=false."
Syncing project...
Updating VCS...
Running Bazel info...
Command: /usr/local/bin/bazel info --tool_tag=ijwb:CLion --curses=no --color=no --noexperimental_ui --noprogress_in_terminal_title --

Command: git diff --name-status --no-renames 05ea74a8f7be2ee3e1271f0019f30ee1a705f629

Extracting Bazel installation...
..........................................................................
____Loading package: @bazel_tools//tools/jdk
____Loading package: @local_config_xcode//
____Loading package: @local_jdk//
____Loading package: @local_config_cc//
Computing VCS working set...
Your working set is empty
Sync targets from project view:
  //...:all

Building IDE info files...
Command: /usr/local/bin/bazel build --tool_tag=ijwb:CLion --keep_going --experimental_build_event_binary_file=/var/folders/yd/nc6_vq355v352hm7_q86gfmw0000gn/T/intellij-bep-991831ee-addb-40da-9115-a821077d3e35 --noexperimental_build_event_binary_file_path_conversion --curses=no --color=no --noexperimental_ui --noprogress_in_terminal_title --aspects=@intellij_aspect//:intellij_info.bzl%intellij_info_aspect --override_repository=intellij_aspect=/Users/ab/Library/Application Support/CLion2017.1/clwb/aspect --output_groups=intellij-info-cpp,intellij-info-generic -- //...:all

____Loading package:
____Loading complete.  Analyzing...
____Loading package: @bazel_tools//platforms
____Loading package: @intellij_aspect//
____Loading package: @bazel_tools//tools/launcher
____Loading package: @bazel_tools//third_party/java/jdk/langtools
____Loading package: @bazel_tools//src
____Loading package: @bazel_tools//src/tools/launcher/util
ERROR: /private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/local_config_cc/BUILD:33:1: in @intellij_aspect//:intellij_info.bzl%intellij_info_aspect aspect on cc_toolchain rule @local_config_cc//:cc-compiler-darwin:
Traceback (most recent call last):
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/local_config_cc/BUILD", line 33
		@intellij_aspect//:intellij_info.bzl%intellij_info_aspect(...)
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/intellij_aspect/intellij_info.bzl", line 18, in _aspect_impl
		intellij_info_aspect_impl(target, ctx, semantics)
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/intellij_aspect/intellij_info_impl.bzl", line 628, in intellij_info_aspect_impl
		list(set(export_deps))
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/intellij_aspect/intellij_info_impl.bzl", line 628, in list
		set(export_deps)
The `set` constructor for depsets is deprecated and will be removed. Please use the `depset` constructor instead. You can temporarily enable the deprecated `set` constructor by passing the flag --incompatible_disallow_set_constructor=false.
____Found 1 target...
____Building...
____[0 / 1] BazelWorkspaceStatusAction stable-status.txt
Target //:hello up-to-date (nothing to build)
ERROR: command succeeded, but not all targets were analyzed.
____Elapsed time: 32.431s, Critical Path: 0.02s
____Waiting for build event protocol upload: 0s
Total rules: 0, new/changed: 0, removed: 3
Reading IDE info result...
Loaded 0 aspect files, total size 0kB
Building IDE resolve files...
Command: /usr/local/bin/bazel build --tool_tag=ijwb:CLion --keep_going --experimental_build_event_binary_file=/var/folders/yd/nc6_vq355v352hm7_q86gfmw0000gn/T/intellij-bep-217d4d35-2777-45c7-bbba-a09dd52cbe4a --noexperimental_build_event_binary_file_path_conversion --curses=no --color=no --noexperimental_ui --noprogress_in_terminal_title --aspects=@intellij_aspect//:intellij_info.bzl%intellij_info_aspect --override_repository=intellij_aspect=/Users/ab/Library/Application Support/CLion2017.1/clwb/aspect --output_groups=intellij-resolve-cpp -- //...:all

____Loading package: @local_config_xcode//
____Loading complete.  Analyzing...
ERROR: /private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/local_config_cc/BUILD:33:1: in @intellij_aspect//:intellij_info.bzl%intellij_info_aspect aspect on cc_toolchain rule @local_config_cc//:cc-compiler-darwin:
Traceback (most recent call last):
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/local_config_cc/BUILD", line 33
		@intellij_aspect//:intellij_info.bzl%intellij_info_aspect(...)
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/intellij_aspect/intellij_info.bzl", line 18, in _aspect_impl
		intellij_info_aspect_impl(target, ctx, semantics)
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/intellij_aspect/intellij_info_impl.bzl", line 628, in intellij_info_aspect_impl
		list(set(export_deps))
	File "/private/var/tmp/_bazel_ab/fc7ea4530f9bdd4f1119eb797c96880e/external/intellij_aspect/intellij_info_impl.bzl", line 628, in list
		set(export_deps)
The `set` constructor for depsets is deprecated and will be removed. Please use the `depset` constructor instead. You can temporarily enable the deprecated `set` constructor by passing the flag --incompatible_disallow_set_constructor=false.
____Found 1 target...
____Building...
Target //:hello up-to-date (nothing to build)
ERROR: command succeeded, but not all targets were analyzed.
____Elapsed time: 25.473s, Critical Path: 0.00s
Prefetching genfiles...
Prefetching files...
Computing directory structure...
Committing project structure...
Workspace has 0 libraries
Workspace has 2 modules
Sync was successful, but there were BUILD file errors. The project may not be fully updated or resolve until fixed. If the errors are from your working set, please uncheck 'Blaze > Sync > Expand Sync to Working Set' and try again.
Updating in-memory state...

[...]

Where can I pass the --incompatible_disallow_set_constructor=false to workaround the bug?

This is fixed in the latest plugin release, though you'll need to update to CLion 2017.2 to pick it up (version compatibility listed here: https://plugins.jetbrains.com/plugin/9554-bazel)


Interactivesubtitle

This is the widgetTranscript we working on.
The srt2Json class has been added into n2.widgetTranscript
{ "widgetType": "transcriptWidget" ,"containerClass": "n2_content_text" ,"name": "trans1" ,"docId": "51a64a7d008484edb3b372899002a99e" ,"videoAttName": "input.mp4" ,"srtAttName" : "test.srt" ,"sourceModelId": "time" ,"timeTable":[ { "videoStart": 0 ,"videoEnd": 31 ,"timeStart": "2018-07-10" ,"timeEnd": "2018-07-28" } ] }

In n2.mediaDisplay.js, line 97, the default behaviour is changed for all atlases. Although the code seems to work fine for your example, it affects the expected behaviour of other instances not using this feature. Probably need to find a way to configure which display function gets called: _displayVideoMediaElementInplace or _displayVideoMediaElement


Switch default state store to SQLite for local experience

Describe the proposal
Running dapr init sets up a default state store "statestore" that is based on Redis. Redis has some issues when used as actor state store, so we should start by migrating the default state store used in the local experience to SQLite.
Release Note
RELEASE NOTE: UPDATE Switch default state store to SQLite for local experience

This requires a config file change.

Is there any update on this?

As discussed in an endgame sync, moving this to next milestone for now.

Yes please also update documentation how to do it withy VS2022 + docker-compose + .NET


Batch commiting

I see you updated the docs to suggest not using Promise.map on a messageSet in the Group Consumer handler (1a63120), but the commitOffset method signature still allows for an array of commits.
/**
 * Commit (save) processed offsets to Kafka
 *
 * @param  {Object|Array} commits [{topic, partition, offset, metadata}]
 * @return {Promise}
 */
GroupConsumer.prototype.commitOffset = function (commits) {
    var self = this;
    return self.client.offsetCommitRequestV2(self.options.groupId, self.memberId, self.generationId,
        self._prepareOffsetRequest('commit', commits));
};

Is it not safe, or otherwise undesirable, to batch commit the entire messageSet in the handler function for the same reason you suggest not doing concurrent commits of individual messages?

I don't think so. Even if I change this method to accept a single commit only it won't make an application code more safe in any way. The reason this method allows an array of commits is that the Kafka protocol allows it. no-kafka is a middleware, it shouldn't make protocol design decisions.

Ok thanks for the input!


Support for Mocks + other features?

Hello, do you plan to include support for Mocks? What do you think is still needed or has to be improved?

Personally, I haven't used Mocks. That's why Tau doesn't have it yet. Feel free to experiment with them and maybe open a PR and we can decide later.

Ok, so as soon as I have a bit of time I can try something and once I am happy with it, I will submint a PR.

Sure. Feel free to submit a PR when ready

I think, for such small test framework you need small mocking framework, like this: https://github.com/ztbrown/Simulacrum
Pair of Tau and Simulacrum looks promisingly. Despite both may have many issues, at least it's easy to fix both.

If you base your design of the code base around mocks, then you have lost already.
Mocking is a quick hack and incurs long-time costs on your code base.
Every code base must be inspectable more or less effortlessly and if you cant do that, then you already broke weak coupling preventing or adding heavy costs on refactorings: You cant specify the state of things via tests as invariants, because it is specified via state of other stuff (the mock).
Refactoring with explicit function signatures of tests is simple, as you can use regexes. You cant do this with mocking techniques.

I agree. I wasn't too sure if we needed to have Mocks in the first place and whether it was worth the headache. Probably not, but I'm open to ideas (and contributors too haha)


SSHKit::Runner::ExecuteError: Exception while executing: npm exit status: 254

Hi,
I have been getting intermittent npm install errors during my capistrano deploy process. I'm getting back npm error code 254, which is a bit cryptic as I can't find much info about it online. This is the capistrano failure error when deploying with --trace:
DEBUG [e9c1e739] Command: cd /apps/appName/releases/20161005212751 && /usr/bin/env npm install --production --silent --no-progress
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as<EMAIL_ADDRESS>npm exit status: 254
npm stdout: Nothing written
npm stderr: Nothing written
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/runners/parallel.rb:15:in `rescue in block (2 levels) in execute'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/runners/parallel.rb:11:in `block (2 levels) in execute'
SSHKit::Command::Failed: npm exit status: 254
npm stdout: Nothing written
npm stderr: Nothing written
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/command.rb:100:in `exit_status='
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/netssh.rb:127:in `execute_command'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:137:in `block in create_command_and_execute'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:137:in `tap'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:137:in `create_command_and_execute'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:69:in `execute'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/capistrano-npm-1.0.2/lib/capistrano/tasks/npm.rake:18:in `block (5 levels) in <top (required)>'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:88:in `with'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/capistrano-npm-1.0.2/lib/capistrano/tasks/npm.rake:17:in `block (4 levels) in <top (required)>'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:80:in `within'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/capistrano-npm-1.0.2/lib/capistrano/tasks/npm.rake:16:in `block (3 levels) in <top (required)>'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:29:in `instance_exec'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/backends/abstract.rb:29:in `run'
/Users/jcursi/.rvm/gems/ruby-2.2.2/gems/sshkit-1.9.0/lib/sshkit/runners/parallel.rb:12:in `block (2 levels) in execute'
Tasks: TOP => deploy:updated => npm:install
The deploy has failed with an error: Exception while executing as<EMAIL_ADDRESS>npm exit status: 254
npm stdout: Nothing written
npm stderr: Nothing written

Any ideas on why this is occurring? Thanks!

Started to get a similar issue out of the blue:
`cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as<EMAIL_ADDRESS>npm exit status: 1
npm stdout: Nothing written
npm stderr: Nothing written
SSHKit::Command::Failed: npm exit status: 1
npm stdout: Nothing written
npm stderr: Nothing written
Tasks: TOP => deploy:updated => npm:install
(See full trace by running task with --trace)
The deploy has failed with an error: Exception while executing as<EMAIL_ADDRESS>npm exit status: 1
npm stdout: Nothing written
npm stderr: Nothing written
`
Any ideas what it could be?

Add the lline below in deploy.rb and you will be able to see detailed log:
set :npm_flags, '--production'    # default

exit status: 254- >  happens when you have an out-of-resources condition....like low processing power or ram...for processes you are currently running...


Update to JupyterLite 0.4.0 final packages

Also bump @jupyterlab/galata to match the JupyterLab 4.2 version used by JupyterLite 0.4.0.

Merging as a mechanical update, and to make the changes available for https://github.com/jupyterlite/xeus/pull/104


Dedupe conflict errors with diff resource versions

Since objects are indexed by ID in the inventory, we don't need to index conflict errors by GVKNN. So this change modifies the conflict handler to index by ID instead. This should have no real effect.

/retest

new.go:480: 2024-06-11 18:26:30.354638367 +0000 UTC ERROR: waiting for ConfigSync Deployments to become available: WatchObject(Deployment config-management-system/reconciler-manager): predicates not satisfied: expected  config-management-system/reconciler-manager to have status "Current", but got "InProgress": context deadline exceeded
W0611 18:26:30.354767   24447 reflector.go:458] k8s.io/client-go/tools/watch/informerwatcher.go:146: watch of *v1.Pod ended with: an error on the server ("unable to decode an event from the watch stream: context canceled") has prevented the request from succeeding

This seems like a flake. I didn't change the reconciler-manager at all in this PR.
I suspect the apiserver just stopped the watch prematurely and the test watch client doesn't have a retry.


Example: Two-layered Cache

Continued from this thread: https://github.com/informalsystems/quint/discussions/1548#discussion-7450016

This is a design of an imagined Two-layered Cache with the following behaviors:

2 layer, N keys, 1 server/cache process, 1 client process
read from Layer 1, if not exists then Layer 2
if key is found in Layer 2, write back to Layer 1
expire time passed = key not exist

Correctness:

strong consistency: any read returns the latest written value
validity: any read returns a non-expired value

Model checking output:
Launching Apalache server
[ok] No violation found (187959ms).
You may increase --max-steps.
Use --verbosity to produce more (or less) output.
Shutting down Apalache server

hi @bugarela I simplified my spec a bit, inspired by the simplicity of https://github.com/mt40/azure-cosmos-tla/blob/master/general-model/cosmos_client.tla
Here are what's changed:

Remove key-value pairs and use a monotonic increasing num instead. This means I'm only considering only 1 key. Since keys are independent anyway, if 1 key works, then it's trivial to see that N keys would also work.
Removed server_process, client read/write directly from the cache layers
Remove expired_time logic. I think that's too detail and too long for an example/learning purpose.
Adding multiple client processes

The result is 100 LOCs stripped.


fix: use of deprecated DeltaTable::peek_next_commit

Maybe we could run CI with
cargo clippy ... -- -D warnings

to catch this early?

Good idea! Feel free to update this :).
Right now I am looking into how we can more deeply integrate with delta-kernel-rs, and APIs like these make this somewhat hard.
So interested in your use case for using this API at all :).
For context, over simplified, there are two kinds of users - the ones who only want the right data and do not care about the log at all, and the ones who care almost exclusively about the log...
In this case, would the CDF APIs also work for you?


not only documents as source?

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Mention any other details that might be useful
Right now in the default version, it only supports the uploaded documents. Is it possible to get information from the normal ChatGPT database, which are not included in my uploaded documents? So that it can provide answers, ChatGPT could also give me?
If so, how does the citations work in this scenario?

Thanks! We'll be in touch soon.

Hi @PhilippTP,
There is no ChatGPT database that I'm aware of. However, if more generally, you mean having the ability to tap into other data sources, you should be able to do that by querying that other data source, and adding the results for relevant documents to your prompt.
https://github.com/Azure-Samples/azure-search-openai-demo-csharp/blob/64a4bcd0d7fa4c64565727cd74577b466a378e6d/app/backend/Services/ReadRetrieveReadChatService.cs#L80
You might need to tweak your prompts as well to account for these other data sources.
Citations should work in a similar way as they do today, except now you'd be referencing the other data sources, not just the single Azure Search index shown in this application.
Note though that the more context and data sources you add to your prompt as context, the less tokens you have for your conversation. You might want to collate the various data sources and do further summarization before submitting them as context to maximize the information in your context while also not using a lot of tokens.


Persistent identifier for this project?

Hi @jwindhager, thank you for making this tool!  Substantially easier to use than past alternatives (e.g. histocat).
I'd like to cite this tool in a manuscript; any thoughts about a persistent DOI for this plugin (Zenodo or something else)?
Cheers

Hi @wflynny, thanks so much for your kind feedback and for giving credit! For now, you can cite the following preprint, as part of which napari-imc was published: https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>8357v1. Let me know if this is sufficient, or whether you require a versioned & archived way of citing napari-imc (e.g. using Zenodo, as you suggested). Cheers

Perfect, that'll work just fine!  Cheers.


disambiguation: improve logging & retry

don't run disambiguation for deleted records instead of handling it with NoResultFound exception

@MJedr Can there be tests for this or is it simpler to test in QA?

@nooraangelva added some tests


You cannot listen to SIGQUIT

It would probably make sense that a dart program could listen to sigquit.

SIGQUIT is used to toggle observatory in the Dart VM which is why you can't listen for it.

Ah - that makes sense. Thanks!


Issue #30 - fixed login and signup form elements

#30 Added a container-body class that adds margins to form elements.

Hey @stanikeva The changes you made are great, but can you make a total change of the UI, since all the place holders are so long and not so good looking. Can you make it more professional and premium login page. Make it short and subtle. You can refer the below attached UI :

If required, we'll merge the current PR and you can make the changes on a new PR as shown in the above Screen Shot.

Hey @stanikeva The changes you made are great, but can you make a total change of the UI, since all the place holders are so long and not so good looking. Can you make it more professional and premium login page. Make it short and subtle. You can refer the below attached UI :

Hey @stanikeva Do let us know about this.


Add an async message send API

The current interface only allows for sending messages synchronously in
response to some event. In the past, it was possible to get an
mpsc::Sender<WsMessage> to deliver messages asynchronously. This commit
restores that functionality with a slighly more ergonomic API.
The RtmClient has a new method
pub fn channel(&self) -> Option<Sender>

which returns a slack::Sender if the RtmClient has been logged in
(creating the slack::Sender requires the RtmClient's mpsc::Sender to
initialize itself).
Sender has a high and low level send API. The high level API
pub fn send_message_chid(&self, channel_id: &str, text: &str)

will automatically increment the message id, build the JSON payload, and
send it to the event loop for delivery. The low level API is two parts
pub fn get_msg_uid(&self) -> isize

for getting the next message id, and
pub fn send(&self, raw: &str)

for sending a pre-built JSON payload.
Resolves #50.

This looks good to me, thanks!

I will try to get out a release soon, I'm finishing a final project right now over at: https://github.com/fenichelar/CS4731Capstone
Once that's done (tonight/tomorrow) I'll update the changelog and push a release.

Awesome; thank you!

Version0.15.0 is now live on crates.io.

Thanks for the update 😁


Enable Wake-On-LAN in netplan config

I had a computer here that hadn’t WoL enabled by default. Usually enabling in the BIOS was enough for me but this time I had to enable it in the netplan config.
It might be a good idea to simply enable that by default for all ethernet devices.

Added in dev branch


Create/Publish iOS ipa file

Hey team! Please add your planning poker estimate with ZenHub @jleach @amanji


Fix #2386, Split up and simplify control flow in CFE_TBL_Register()

Checklist

[x] I reviewed the Contributing Guide.
[x] I signed and emailed the appropriate Contributor License Agreement to<EMAIL_ADDRESS>and copied<EMAIL_ADDRESS>
Describe the contribution

Fixes #2386

First chunk of issues listed in https://github.com/nasa/cFE/issues/1504
This PR addresses the high cyclomatic complexity of CFE_TBL_Register

Main change here was to pull out the logical blocks of work into helper functions.
Additional Changes
Name Size Validation:
Simplified the size checks to just a single check and report (old, new). Can revert this change if the extra verbosity is desired.
Previously, if any of the name size checks failed (and CFE_TBL_ERR_INVALID_SIZE Status was set), the code would then still run on to verify the specific table options flags (and re-assign another error code on top of CFE_TBL_ERR_INVALID_SIZE if this failed). Have updated this logic to only enter the TblOptionsFlags checks if the size checks pass successfully. No need to continue execution if error status already set.
Main Registration Block Control Flow:
Previously the code would search for an access descriptor even if already in error status here. This is unnecessary if already in error status so have changed this conditional to just check for == CFE_SUCCESS (link).
In 3 locations inside the this same main table registration block there were status guards of the form if (Status & CFE_SEVERITY_BITMASK) != CFE_SEVERITY_ERROR).
I have reduced the nesting in this section, and simplified these checks to just check for == CFE_SUCCESS. The only non-negative 'warning' status possible there was CFE_TBL_WARN_DUPLICATE, which was already being filtered out anyway. Also, these warning (i.e. non-success, non-error) status/return codes are intended to be deprecated anyway.
Minor Simplification:
Simplified this true/false assignment to this.
Note there are a few open issues already for specific issues inside CFE_TBL_Register:

https://github.com/nasa/cFE/issues/1837
https://github.com/nasa/cFE/issues/1506
https://github.com/nasa/cFE/issues/2280 (this one is fixed by this PR as well)

Testing performed
GitHub CI actions all passing successfully (incl. Build + Run, Unit/Functional Tests etc.). Local testing also conducted to confirm all variables and syslog strings printing as expected etc.
Expected behavior changes
Minor control-flow changes noted above. In general this PR will:

make unit testing much simpler/easier
ease future maintenance
reduce technical debt
ease use of cFE by developers

System(s) tested on
Debian GNU/Linux 11 (bullseye)
Current main branch of cFS bundle.
Contributor Info
Avi Weiss @thnkslprpt

Thanks @thnkslprpt !! Good work here, I like this .... sorry things sit so long.  Reviewing this now and hopefully we can merge it, as the existing TBL code is really hard to work with.

Thanks @thnkslprpt !! Good work here, I like this .... sorry things sit so long. Reviewing this now and hopefully we can merge it, as the existing TBL code is really hard to work with.

@jphickey
No problem at all Joe. We all do what we can with the time we have available.
I'll be interested to hear your feedback on this. FYI - I rebased it to main just now.
Cheers

I like this a whole lot better than what was in there.  It's far more readable and easy to understand what's going on.  The cyclic complexity measurement of CFE_TBL_Register() went from 52 to 20 after merging this change (still could be even better, but this is a huge improvement).
I've confirmed that everything seems to work as far as functional tests go - the only concern is that there are some missing lines in the coverage.  I may be able to address that.

I've confirmed that everything seems to work as far as functional tests go - the only concern is that there are some missing lines in the coverage. I may be able to address that.

Thanks for adding those coverage tests in.