Update to NestJS 9

The interface INestApplication changed the name 'listenAsync' method to 'listen'.

Some PR exists but nobody can merge it for the moment

https://github.com/mxarc/nestjs-redoc/pull/63
https://github.com/mxarc/nestjs-redoc/pull/65

Someone created an alternative repo<EMAIL_ADDRESS>

Any update on this? Many issues are fixed but still not merged and released

Any update?

Following

waiting...

Following...

Following

I was getting fed up of this breaking my releases so I created a fork and updated everything to the most up to date versions,  I will keep this updated, you can find it here:
Github: https://github.com/juicyllama-community/nestjs-redoc
NPM: https://www.npmjs.com/package/@juicyllama/nestjs-redoc
Tests are not working in the original repo, but its tested and it is working.

Hi @oneVcard
Yes, we are, however, this has been absorbed into our main framework monorepo here: https://github.com/juicyllama/framework/tree/main/common/nestjs-redoc
The NPM link is still valid, I will update the original post.
I do want to improve the nestjs-redoc package some more, hopefully in the upcoming weeks I will find some time to make some improvements to it.

Great :D, thank you very much for keeping the package going :)
I would have a feature that could improve the nestjs redoc:
We have, like mentioned before, some big DTOs and it would be cool if there would be a limit that can be configured on how deep the dto is displayed
for example

mainDTO:

secondDTO:

thirdDTO:

fourthDTO:

for example here we would only like the depth that will be shown in the schema to be 2 so only mainDto and secondDto.
Do you think this feature could be implemented by you?

Hi @oneVcard
Any chance you can open a discuss here: https://github.com/juicyllama/framework/discussions
We can then scope it out together and create an issue once we have all the information.
Any screenshots of your docs now and how you would like them to look would be great.

Hi @oneVcard
Any chance you can open a discuss here: https://github.com/juicyllama/framework/discussions
We can then scope it out together and create an issue once we have all the information.
Any screenshots of your docs now and how you would like them to look would be great.

I will do that later that day and provide a example repository for you also with my personal account as i cannot share any code here with this company account

Hi, I just created a library for NestJS 10 supporting ExpressJS and Fastify without the need to import a big framework: nestjs-redox


tiff/decoder: use wrapping add for horizontal prediction

Closes #544
Is there a cleaner way to do the generic wrapping?

Thank you for contributing.
Unfortunately the does not exist a generic way. Generic numeric traits have been removed from Rust a while ago.


jenkins_job creation fails with 400 "Bad Request" error on jenkins-cli.jar download

I'm using Chef 12.3 with the jenkins cookbook from the supermarket and a jenkins_job block has failed consistently when a wget or curl command to the same URL are consistently successful from the same machine. Here is the error and the /var/chef/cache/chef-stacktrace.out below. I've Googled quite a bit with no hints. Any ideas?
  * remote_file[/var/chef/cache/jenkins-cli.jar] action create[2015-08-06T15:35:18-04:00] WARN: remote_file[/var/chef/cache/jenkins-cli.jar] cannot be downloaded from http://localhost:8080/jnlpJars/jenkins-cli.jar: 400 "Bad Request"                                                                           [11/1805]

      ================================================================================
      Error executing action `create` on resource 'remote_file[/var/chef/cache/jenkins-cli.jar]'
      ================================================================================

      Net::HTTPServerException
      ------------------------
      400 "Bad Request"

      Cookbook Trace:
      ---------------
      /var/chef/cache/cookbooks/jenkins/libraries/_helper.rb:394:in `ensure_cli_present!'
      /var/chef/cache/cookbooks/jenkins/libraries/_helper.rb:62:in `executor'
      /var/chef/cache/cookbooks/jenkins/libraries/job.rb:211:in `current_job'
      /var/chef/cache/cookbooks/jenkins/libraries/job.rb:87:in `load_current_resource'

      Compiled Resource:
      ------------------
      # Declared in

      remote_file("/var/chef/cache/jenkins-cli.jar") do
        provider Chef::Provider::RemoteFile
        action "create"
        retries 0
        retry_delay 2
        default_guard_interpreter :default
        path "/var/chef/cache/jenkins-cli.jar"
        atomic_update true
        source ["http://localhost:8080/jnlpJars/jenkins-cli.jar"]
        use_etag true
        use_last_modified true
        mode "0755"
      end

    ================================================================================
    Error executing action `create` on resource 'jenkins_job[dvs_shipments_api]'
    ================================================================================

    Net::HTTPServerException
    ------------------------
    remote_file[/var/chef/cache/jenkins-cli.jar] (dynamically defined) had an error: Net::HTTPServerException: 400 "Bad Request"

    Cookbook Trace:
    ---------------
    /var/chef/cache/cookbooks/jenkins/libraries/_helper.rb:394:in `ensure_cli_present!'
    /var/chef/cache/cookbooks/jenkins/libraries/_helper.rb:62:in `executor'
    /var/chef/cache/cookbooks/jenkins/libraries/job.rb:211:in `current_job'
    /var/chef/cache/cookbooks/jenkins/libraries/job.rb:87:in `load_current_resource'

    Resource Declaration:
    ---------------------
    # In /var/chef/cache/cookbooks/fit-jenkins/recipes/jobs.rb

     25:   jenkins_job "#{app}_api" do
     26:     config api_xml
     27:   end
     28:

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/fit-jenkins/recipes/jobs.rb:25:in `block in from_file'

    jenkins_job("dvs_shipments_api") do
      action :create
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      declared_type :jenkins_job
      cookbook_name "fit-jenkins"
      recipe_name "jobs"
      config "/var/chef/cache/dvs_shipments_api_config.xml"
    end

And /var/chef/cache/chef-stacktrace.out
Generated at 2015-08-06 15:35:22 -0400
Net::HTTPServerException: jenkins_job[dvs_shipments_api] (fit-jenkins::jobs line 25) had an error: Net::HTTPServerException: remote_file[/var/chef/cache/jenkins-cli.jar] (dynamically defined) had an error: Net::HTTPServerException: 400 "Bad Request"
/opt/chef/embedded/lib/ruby/2.1.0/net/http/response.rb:119:in `error!'
/opt/chef/embedded/apps/chef/lib/chef/http.rb:179:in `streaming_request'
/opt/chef/embedded/apps/chef/lib/chef/provider/remote_file/http.rb:60:in `fetch'
/opt/chef/embedded/apps/chef/lib/chef/provider/remote_file/content.rb:64:in `grab_file_from_uri'
/opt/chef/embedded/apps/chef/lib/chef/provider/remote_file/content.rb:49:in `try_multiple_sources'
/opt/chef/embedded/apps/chef/lib/chef/provider/remote_file/content.rb:38:in `file_for_provider'
/opt/chef/embedded/apps/chef/lib/chef/file_content_management/content_base.rb:40:in `tempfile'
/opt/chef/embedded/apps/chef/lib/chef/provider/file.rb:459:in `tempfile'
/opt/chef/embedded/apps/chef/lib/chef/provider/file.rb:337:in `do_generate_content'
/opt/chef/embedded/apps/chef/lib/chef/provider/file.rb:148:in `action_create'
/opt/chef/embedded/apps/chef/lib/chef/provider.rb:130:in `run_action'
/opt/chef/embedded/apps/chef/lib/chef/resource.rb:562:in `run_action'
/var/chef/cache/cookbooks/jenkins/libraries/_helper.rb:394:in `ensure_cli_present!'
/var/chef/cache/cookbooks/jenkins/libraries/_helper.rb:62:in `executor'
/var/chef/cache/cookbooks/jenkins/libraries/job.rb:211:in `current_job'
/var/chef/cache/cookbooks/jenkins/libraries/job.rb:87:in `load_current_resource'
/opt/chef/embedded/apps/chef/lib/chef/provider.rb:113:in `run_action'
/opt/chef/embedded/apps/chef/lib/chef/resource.rb:562:in `run_action'
/opt/chef/embedded/apps/chef/lib/chef/runner.rb:49:in `run_action'
/opt/chef/embedded/apps/chef/lib/chef/runner.rb:81:in `block (2 levels) in converge'
/opt/chef/embedded/apps/chef/lib/chef/runner.rb:81:in `each'
/opt/chef/embedded/apps/chef/lib/chef/runner.rb:81:in `block in converge'
/opt/chef/embedded/apps/chef/lib/chef/resource_collection/resource_list.rb:83:in `block in execute_each_resource'
/opt/chef/embedded/apps/chef/lib/chef/resource_collection/stepable_iterator.rb:116:in `call'
/opt/chef/embedded/apps/chef/lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block'
/opt/chef/embedded/apps/chef/lib/chef/resource_collection/stepable_iterator.rb:85:in `step'
/opt/chef/embedded/apps/chef/lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate'
/opt/chef/embedded/apps/chef/lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index'
/opt/chef/embedded/apps/chef/lib/chef/resource_collection/resource_list.rb:81:in `execute_each_resource'
/opt/chef/embedded/apps/chef/lib/chef/runner.rb:80:in `converge'
/opt/chef/embedded/apps/chef/lib/chef/client.rb:339:in `block in converge'
/opt/chef/embedded/apps/chef/lib/chef/client.rb:334:in `catch'
/opt/chef/embedded/apps/chef/lib/chef/client.rb:334:in `converge'
/opt/chef/embedded/apps/chef/lib/chef/client.rb:353:in `converge_and_save'
/opt/chef/embedded/apps/chef/lib/chef/client.rb:457:in `run'
/opt/chef/embedded/apps/chef/lib/chef/application.rb:271:in `block in fork_chef_client'
/opt/chef/embedded/apps/chef/lib/chef/application.rb:259:in `fork'
/opt/chef/embedded/apps/chef/lib/chef/application.rb:259:in `fork_chef_client'
/opt/chef/embedded/apps/chef/lib/chef/application.rb:225:in `block in run_chef_client'
/opt/chef/embedded/apps/chef/lib/chef/local_mode.rb:39:in `with_server_connectivity'
/opt/chef/embedded/apps/chef/lib/chef/application.rb:213:in `run_chef_client'
/opt/chef/embedded/apps/chef/lib/chef/application/client.rb:402:in `block in interval_run_chef_client'
/opt/chef/embedded/apps/chef/lib/chef/application/client.rb:392:in `loop'
/opt/chef/embedded/apps/chef/lib/chef/application/client.rb:392:in `interval_run_chef_client'
/opt/chef/embedded/apps/chef/lib/chef/application/client.rb:382:in `run_application'
/opt/chef/embedded/apps/chef/lib/chef/application.rb:60:in `run'
/opt/chef/embedded/apps/chef/bin/chef-client:26:in `<top (required)>'
/usr/bin/chef-client:51:in `load'
/usr/bin/chef-client:51:in `<main>'

@schisamo Any ideas?

Update: The Chef run still fails with the error I originally posted in this issue. However, the jobs are eventually created successfully. I haven't figured out why yet (perhaps subsequent Chef runs). Still, when I run chef-client on the Jenkins server, the Chef run fails with the same error. If anyone can shed light on this, it's much appreciated. Let me know if I can provide any more information.

This is still an issue for me. While I can make changes to my Jenkins jobs and expect that they will appear the next day, I can't make a change to me jobs recipe and apply those changes immediately because manual Chef runs fail with this error. Any info or help would be much appreciated. Thanks.

I had a similar problem (though my error was a 403 Forbidden) when using an http_proxy: setting in my .kitchen.yml. When I removed that, the problem went away.

This seems to be have been a point in time issue with specific versions of Jenkins. Please open a new issue if this behaviour has resurfaced.


application sharing

when i put app in background i am also able to share my mobile screen and other applications as well ; what can i do so that i can only share agora  application view . not the whole mobile

Why would you want sth like that? May i know your business requirements?

With Screen sharing demo I am able to share the screen of the application which is good for us. But when the user put an application in the background. Using home button screen sharing is still continuing so other users also able to see everything on sharing device Which should not happen as per our end requirements. Could you please guide me to get rid of it.

With Screen sharing demo I am able to share the screen of the application which is good for us. But when the user put an application in the background. Using home button screen sharing is still continuing so other users also able to see everything on sharing device Which should not happen as per our end requirements. Could you please guide me to get rid of it.

per my understanding, you may acheive your requirement by stop the screen sharing in your onStop() method in your application


medianFilter

If you support filters now, medianFilter no compiling, maybe after installing arduino 1.8.19. Thank you

I'm sorry, there is no problem. My arduino IDE was using a different median filter library


[Bug]: AWS AMI has too small root partition size

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When launching an instance with the appsmith latest AMI the disk run out of space after few minutes. The default size is 8GB for root.
I expect the AMI default root partition to have a default size which at least allow me to run the application.
After testing, it seems that 10GB should be plenty enough. Some people might want to increase it if they are not using external databases.
This does not count the fact that old versions of the application docker image might not be removed from the docker image store. (I can see that latest AMI holds 3 docker image versions) - but I disabled auto-update, as its by default turn on and not suitable for production usage.
Steps To Reproduce

launch an instance with the AWS AMI
logging and run df to check disk usage

Environment
Production
Version
Self-Hosted

Thanks, @gokuatkai for reporting this
We are looking to fix the default AMI settings so that you don’t run into the disk space issue. In the meantime, here’s a video on how to circumvent it by defining a larger disk during startup time itself: https://www.loom.com/share/ea41d08798304295a571b64d818a39a9.
The change is that you need to use the EC2 console instead of the “website” option to launch the AMI. This gives you more control over the settings.

thanks, I use terraform to deploy our AWS stacks. So this was not a problem for me to change the size. I was just expecting it to be adequate. The version is as well misleading, it says 1.3.5 on the AMI while in fact it is the latest docker image: v1.6.2 at this day.

Hey @gokuatkai, yes the AMI version is separate from the Appsmith / Docker image version. The AMI will just get the latest Docker image to run, irrespective of what the AMI version is. The AMI version is only incremented when we push fixes to the AMI itself, for things like security updates for the software in the image, or bug fixes in the setup flow etc.

EmreKspToken


document validation

How to validate object using dangoDB ?

Hi, elycheikhsmail. Could you please further describe your question so that I can properly address it?

I not yet try dango but in the readme I see schama describing object, I think we can make :
const result = mymodel.validation(someobject)

and result give missing key in given object and all errors

The validator option is a property that can be defined in the Schema Options object, it is not a method that can be called on the model. It is defined as either null by default or by user input. It must be a function that returns a boolean when the value of a given insertion/update query is passed into it. It is essentially a user-defined way of ensuring that a given value satisfies some criteria. For example, if the schema requires a number, the validator function could return true if the number is > 5. On any insertion/update queries thereafter the validator function would only 'pass' if the new entry had a value > 5. I hope this answers your question!


Speed powerup

This looks good
As a "user", I have released am having a hard time knowing what each powerup icon represents until I refer back to the instruction. Will it be okay to show the name of each powerup when the cursor has hovered on the powerups?

Yes to hovering over a powerup shows it's name - but ok to defer that until after today since today we need to get a version out for the larger demo day tonight/tomorrow/Wed. Normally I only show it to a one or two people but it's being opened up to the whole committee for Tues/Wed (I need to put out an email to them tonight after I load up whatever we have at that point). Longwinded way of saying yes hovering is nice, but not nice enough to delay a release tonight.


[Lambda] Create dummy segment when trace header is incomplete

When using Lambda, if there is no trace header or an invalid one we would like to send a NoOp segment instead of a Facade segment so that customers can call X-Ray SDK APIs and utilize X-Ray SDK without any output. This will not send data to X-Ray nor inject X-Ray trace headers downstream.
Description of changes:

When initializing the context, create a dummy segment if the trace header is incomplete
Appropriately identify when the created segment is a dummy and handle it accordingly ( or isinstance(current_entity, DummySegment))
Update comments and tests accordingly

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Do we have a unit test cover the trace header "Root=x;Lineage=y" case in Lambda enviroment?


Tests fail unless --skip-lint flag is set

#1452 adds the requirement for documentation whenever AccountInfo is used, which breaks a large number of tests unless you run them with --skip-lint set
Does it make sense to upgrade these tests to pass without --skip-lint by adding the required documentation (i.e. /// CHECK: ...)?

These tests aren't supposed to be secure programs but are testing specific behaviors. So for many of these, no, this doesn't make sense because they are in fact insecure.

Yeah, I can see the point that these aren't expected to be secure programs, nor the best practices, but on the other side I'd argue that tests shouldn't be excluded from linting because the cost is low and it always feels a bit unhygienic to have tests that require a special flag to run.
Having said that, I appreciate the reasoning and quick clarification. Thanks!


Support to apply suggestion automatically

ESLint does not provide an API for applying suggestion

from: https://github.com/eslint/rfcs/tree/main/designs/2019-suggestions

Unlike fixes, suggestion will not expose a new API function on CLIEngine to output selected suggestion to a file. Instead, integration would be expected to apply suggestion in memory and let the user save the file on their own.

Therefore, you will need to create your own mechanism for applying suggestions to achieve this functionality

Related works

vscode-eslint

https://github.com/microsoft/vscode-eslint/blob/3aef00d9320a00890beec9f3f8160d5f82a47626/server/src/eslintServer.ts#L456

Complete.


Rebuild Dropdown for better functionality and multiple styles

Should do a full rebuild of this since most is legacy pre-brutalism code. Styles should include native host app exactly (with PHXS having anomalous style), current style renamed as flat, better reactivity and implementation

Prototype <Select> component is done and far more flexible/better. Will write up docs on this tonight

Rebuild complete as Select component


Feature Discussion: Support nonfinite numeric values via feature flag

Currently this crate follows strict JSON protocol and does not allow nonfinite numeric values. However, when interacting with other services such as the Python standard library or Snowflake it would be nice to opt-in support for NaN, Infinity, and -Infinity numeric values with a feature flag. This is very important data when serializing from machine learning or scientific computing applications.
I'm able to implement it, but before I'd like to confirm if this is a feature that would get accepted into the crate.

I would prefer not to build this into serde_json but it would be reasonable for somebody else to maintain a different library for this.


Add vagrant

Add a basic vagrant box with separate Kernel and front controller. Use Ansible for provisioning.

Done in #4


Time to cut a new release?

Hi, I would love to see a new release with the changes done to support FosRestBundle in it :)

Will work on a new release after https://github.com/FriendsOfSymfony/FOSCommentBundle/pull/559 :)

https://github.com/FriendsOfSymfony/FOSCommentBundle/releases/tag/v2.0.9

Hi, - thanks. Is it possible to make the releasenotes a bit more informative?


Fix RUNTIME_IDENTIFIER for accountingservice

Changes
Fix #1798 - the issue is that the .NET Docker images are Debian based, however, the runtime identifier (RID) passed on the build step is targeting musl based distros, e.g.: Alpine. Fixing the RID avoids the error mentioned on #1798.

@pjanotti Thank you for the PR!
It made me understand better the issue.
In cartservice we build as musl because we run in Alpine: mcr.microsoft.com/dotnet/runtime-deps:8.0-alpine3.20.
For some reason, the AccountingService, when I switched to alpine it crashed. So I kept your change and also added the ARG TARGETARCH to the publish step.
@MMartyn would you be able to test this PR out?

@MMartyn would you be able to test this PR out?
Tried it out and it works great. Thanks for the explanation on what was wrong.

Thank you @pjanotti for fixing it, and thx @MMartyn for reporting and helping with the troubleshooting!


[Transforms] logicalNotOperatorInvalidOperations asserts in services layer

Expected: No assert
Actual:
  1) conformance tests compiler tests for tests/cases/conformance/expressions/unaryOperators/logicalNotOperator/logicalNotOperatorInvalidOperations.ts "before all" hook:
     Error: Debug Failure. False expression:
      at Object.assert (built/local/typescriptServices.js:1957:23)

#8208 fixes this.


[Enhancement] Support multiversion function hll _merge_registers

Why I'm doing:
Support multiversion function for hll _merge_registers().  Also check #43560 .
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[x] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

Thanks for your contribution

Similar as #43560, We should check whether it is on x86 platform before using multiversion function.

#43560 has been merged. Could use MVF_xxx to refactor this PR.


Update readme

Updated the readme to document all the new parameters the module accepts (the puppetforge documentation is out of date).

Thank you :)


Quick check if is inview?

Hey folks,
I need to figure out elsewhere in the code if my element is inview or not.
Is there some way to ask the inview variable if the element is currently in view?
something like:
var inview = new Waypoint.Inview({ ...
if (inview.isInview) { }
A workaround would be to change a var-state inside the enter and exited events, but that's pretty inconvenient for me. Just asking the object would be a huge benefit for me. Any ideas how to implement this?
Thanks!
Louis

:+1: for this feature. Our use case is tracking when an item comes into view, and adding a delay to double check that the user spent at least n milliseconds with the item still in view.

@katerlouis @shellscape
Set a data flag (or class if you wish) on the element in the handler.
onEnter: function () {
  this.element.setAttribute('data-inview', true)
},
onExit: function () {
  this.element.removeAttribute('data-inview')
}

/* ... */

thatElement.getAttribute('data-inview')

Outstanding. Thanks for adding that @imakewebthings :+1:

@imakewebthings finally just getting around to adding this to our code... I don't see the use or reference of enter or exit anywhere in the distributed code for the latest release. Please advise?

https://github.com/imakewebthings/waypoints/blob/master/lib/shortcuts/inview.js
http://imakewebthings.com/waypoints/shortcuts/inview/
On May 11, 2016, 7:42 AM -0700, Andrew<EMAIL_ADDRESS>wrote:

@imakewebthings(https://github.com/imakewebthings)finally just getting around to adding this to our code... I don't see the use or reference ofenterorexitanywhere in the distributed code for the latest release. Please advise?
—
You are receiving this because you were mentioned.
Reply to this email directly orview it on GitHub(https://github.com/imakewebthings/waypoints/issues/468#issuecomment-218480840)

@imakewebthings total brain fart over there, thanks much.


Add dependent events to async call

Add dependant event support for async kernel submission. To simplify these changes Kernel Launcher was updated to remove array allocation duplicates.

[x] Have you provided a meaningful PR description?
[x] Have you added a test, reproducer or referred to an issue with a reproducer?
[x] Have you tested your changes locally for CPU and GPU devices?
[x] Have you made sure that new changes do not introduce compiler warnings?
[ ] If this PR is a work in progress, are you filing the PR as a draft?

2714471093a4a976a5e66da03d824774812f2515 is not needed. I have handled the needed changes to support Numba 0.50 in #1250


Update add_my_project_to_inch_ci.yml

Hi there, sorry for keeping you waiting (I caught a nasty cold and wasn't really up to the task until now).
Your project is very interesting, because the parser I intended to use (JSDoc) does not catch your functions as function definitions. I suspect this is because you define them via describe-property (which, of course, is fine).
May I ask what you currently use to generate docs from the source?

@rrrene I don't generate docs from the source, tho I wish I could. I'm hoping to remove the dep on describe-property soon and move to ES6 classes, but I'd like support for ES7 property initializers to land in babel first.


open new file in an already open window

I'm using atom 1.0.0 in Ubuntu.
When i run atom nonExistantFile, a new window is opened for it.
As atom is slow on start-up, that's very inconvenient. Is there an option to open in an already open window?

That's weird - I can't reproduce this on Atom 1.0.2 on OS X 10.10.3. Can you try updating to the latest version (1.0.2)?

it happens only when the file in question doesn't exist and for commit messages if you set atom as the core.editor.
I'll update and try again

I updated (i don't think it has anything to do with the version).
Anyway, here is what happens:

If you open a new file in a directory that has an instance of atom open, it will open the file in the same window.
If you open a file new file in a directory that has no instance of atom open, it will open the file in a new window. (happens also for git commit message)
I think that it would be great to add it as an option atom --already-open fileName: and the file will be opened in the last active instance of atom.
This way we could fix it for the commit message too.

Ah, thanks! I can reproduce this now.

I can't believe this is the default behavior, much less the enforced behavior.
This is just a text editor!  Open my files in the text editor window, not 1 window per file!
My terrible workaround for now: add "/" as a project folder.

I am wondering how many years we will need till we will solve this bug. This one is very well defined and easy to reproduce, clearly against documentation.

  All you have to do is typo a filename, and my computer is basically unusable for a few seconds while Atom bootstraps the new window.  Yes I need a new computer.. but Atom needs a more efficient and quick bootstrap.. so a solution for this very old and easy-to-reproduce issue makes a great compromise :)

@mnquintana can this please be reopened?


[Metadata] Let entries expire in the metadata caches

Motivation

There's essentially a memory leak in the Metadata caches since the entries never expire in the current solution.
refreshAfterWrite will never expire entries. After the given time, the next request to the entry will
trigger a refresh in the background. The current entry will be used until the entry has been refreshed.

documentation for Caffeine's refresh feature: https://github.com/ben-manes/caffeine/wiki/Refresh

Modifications

expire after CACHE_REFRESH_TIME_MILLIS * 2

I think it's better not to increase metadata load, how about

refresh after CACHE_REFRESH_TIME_MILLIS
expire after CACHE_REFRESH_TIME_MILLIS * 2

@Jason918 thanks, I changed it in this way. PTAL


Cannot install VLS in VSCode

Specs:
Windows 7 SP1 64bit
VSCode 1.70.3
V Extension 0.1.14
V 0.3.4 bbd1027
When I try to install VLS through V VSCode Extension I get Error (101): Language server is not installed nor found.; code: 101 error.
Output from extension:
Spawning v ls --json --check...
[v ls] new data: {"error":{"message":"Language server is not installed nor found.; code: 101","code":"101","details":"- If you are using this for the first time, please run\n  `v ls --install` first to download and install VLS.\n- If you are using a custom version of VLS, check if\n  the specified path exists and is a valid executable.\n- If you have an existing installation of VLS, be sure\n  to remove \"vls.config.json\" and \"bin\" located inside\n  \"%USERPROFILE%\\.vls\" and re-install.\n\n  If none of the options listed have solved your issue,\n  please report it at https://github.com/vlang/v/issues"}}
Spawning v ls --json --install...
[v ls] new data: {"message":"Finding prebuilt executables from GitHub release.."}
[v ls] new data: Error 0x80090302 returned by InitializeSecurityContext (2)
Error performing handshake
{"error":{"message":"response does not start with HTTP/, line: ``","code":"0","details":""}}
Spawning v ls --json --check...
[v ls] new data: {"error":{"message":"Language server is not installed nor found.; code: 101","code":"101","details":"- If you are using this for the first time, please run\n  `v ls --install` first to download and install VLS.\n- If you are using a custom version of VLS, check if\n  the specified path exists and is a valid executable.\n- If you have an existing installation of VLS, be sure\n  to remove \"vls.config.json\" and \"bin\" located inside\n  \"%USERPROFILE%\\.vls\" and re-install.\n\n  If none of the options listed have solved your issue,\n  please report it at https://github.com/vlang/v/issues"}}

Running v ls --install manually fails with following error:
> Finding prebuilt executables from GitHub release..
Error 0x80090302 returned by InitializeSecurityContext (2)
Error performing handshake
v ls error: response does not start with HTTP/, line: `` (0)

C:/Users/User/AppData/Local/Temp/v_0/vls.2714178047656411777.tmp.c:9794: at print_backtrace: Backtrace
C:/Users/User/AppData/Local/Temp/v_0/vls.2714178047656411777.tmp.c:22300: by main__VlsUpdater_cli_error
C:/Users/User/AppData/Local/Temp/v_0/vls.2714178047656411777.tmp.c:22407: by main__main
C:/Users/User/AppData/Local/Temp/v_0/vls.2714178047656411777.tmp.c:22902: by wmain
004cb9d8 : by ???
004cbb3b : by ???
7770556d : by ???

Already resolved by using binary build from source.


Connection to API failed 404 when MOD_REWRITE  enabled

I am new to Respond and setting up local environment on my laptop. I have api running using MOD_REWRITE for other project on localhost. When I am hitting http://localhost/respond/app/public/install/
i get Connection to API failed and on clicking of api url, I get 404 error.
Also do I really need SSL for setting up sample demo website on my localhost?

You can find information on how to get Lumen/Laravel to run locally here:
https://laravel.com/docs/4.2/quick#local-development-environment
Respond requires the application to run at the root of the URL (locally this would be http://localhost).
I am going to close this issue as it is not related to a deficiency in the project.

I added instructions on how to install Respond locally.  Hopefully this will help you.
https://respondcms.com/documentation/installation-local


Examples of lookup_send and block_lookup

Hi Thomas,
Do you have any examples of using the lookup_send function and an example block_lookup function? I've been trying to work out how to send a large amount of data from SRAM but not having any luck.
Thanks,
Gary

I can get it to send a single 128 bytes but I can't work out how to send multiple packets for larger files. Any guidance appreciated.

Hi Gary
here is a block_lookup function from one of my projects:
inline word page_num_to_address(byte p) {
  return ((word) p & PAGE_ID_MASK) << PAGE_BITS;
}

void lookup_block(void *blk_id, size_t idSize, byte *data, size_t dataSize) {
  word page_addr = page_num_to_address(*((byte *) blk_id));
  for(byte i = 0; i < PAGE_SIZE; ++i) {
    data[i] = read_byte(page_addr + i);
  }
}

Baisically what this is doing is mapping a given block id to the memory addresses of a EEPROM chip and filling the memory pointed to by the data pointer with the data stored in the EEPROM.
For sending lookup_send will only take the id you pass to it and use the block_lookup function to send just that data in a xmodem transaction, if you want to send more things within the same xmodem transaction you should use the send_bulk_data function https://github.com/gilman88/xmodem-lib/blob/1.0.2/README.txt#L177-L202 this is used by all the sending functions internally so you can just take a look at the lookup_send and send functions to see an example of using this.
Hope this helps :)


'importwallet' is too keen to rescan

I just used 'importwallet' on a wallet I had already imported.
It found a whole lot of:
Skipping import of xEcwR41VwnQww32hVQstbg2W2UxhTEfjVf (key already present)
Skipping import of xRgYUcLrdjLHsWXPT5SQVsYt2x81DKunAR (key already present)
Skipping import of xJ8ei13ENVx8xZoAvTiX61jnAt7DMmEHJ9 (key already present)

but didn't actually import anything new.
It still went on to:
Searching last 332965 blocks (from block 0) for dug Clams...

which takes a long time and is unnecessary since nothing was imported.

Fixed in #149.


Crop/trim jams utility function

For scaper I need to crop/trim some audio files and their corresponding JAMS annotations. I started implementing a crop_jams method in scaper, but after chatting with @bmcfee it transpired that this might be something useful to have as part of the core jams library, and regardless there are some methodological questions best run through this crowd.
Question 1: is this something we want to implement as part of the core jams lib?
(this is the second time I need to crop jams annotations for a project, so at least based on my own experience this would be something very useful to have).
Question 2: regardless of where this is implemented, I can see (at least) two different approaches to implementation:

Edit the annotation "in place" by directly manipulating the annotation.data DataFrame.
Create a new annotation, copy over all metadata, and selectively adjust/add events based on the desired crop range.

The former has the advantage of not having to worry about replicating the annotation perfectly since the data frame (and .duration object variable) is manipulated directly. The latter has the advantage of (potentially) being independent of the internal storage mechanism, though it requires care in ensuring all annotation information is copied over. Also if we wanted it to be completely decoupled from the dataframe we might want/need to implement some form of get function or iterator to be able to access (and maybe even remove?) the annotation observations via an API.
This is a little time-critical for me, so thoughts/discussion are most welcome. Worst case scenario I'll implement this in scaper first and port it into jams at a later point if we decide that's the way we want to go.

I've also run aground of slicing jams annotations in this way in a few places, so it wouldn't be terrible to consolidate efforts in one place.
Here are my thoughts:

We should, wherever possible, strive to keep data immutable.  If we're going to be modifying annotations like this, it should return a new annotation, not modify in-place.  This argues for taking option 2.
In general, I think we should support both trimming to a time slice, and padding on the front or back.
I think this would be best implemented by object methods that return new instances with all fields appropriately modified.  So you could say sub_jam = jam.slice(start, end) or jam_pad = jam.pad(start_pad, end_pad) and get coherent data out without modifying jam.

I know this is time-critical for @justinsalamon, but it's a rather large undertaking that I don't want to hold up the (already absurdly delayed) next release.  Can we slot this for 0.3?  If @justinsalamon wants to implement in a PR, that's fine too.

We should, wherever possible, strive to keep data immutable. If we're going to be modifying annotations like this, it should return a new annotation, not modify in-place. This argues for taking option 2.

Sure

I think this would be best implemented by object methods that return new instances with all fields appropriately modified. So you could say sub_jam = jam.slice(start, end) or jam_pad = jam.pad(start_pad, end_pad) and get coherent data out without modifying jam.

Makes sense. For my own selfish reasons I'll start working on slice first though.

I know this is time-critical for @justinsalamon, but it's a rather large undertaking that I don't want to hold up the (already absurdly delayed) next release. Can we slot this for 0.3? If @justinsalamon wants to implement in a PR, that's fine too.

For my immediate work that would be ok (since I can just work against the PR branch), but releasing scaper would depend on this functionality and I'm concerned that waiting for 0.3 might stall it a little too much?
I'm planning on bashing this out today/next few days, how about we see how far I get by the end of this weekend to determine whether we can squeeze it into the upcoming release?

Sure.  We could also make a minor point release for this feature before 0.3.

Sure. We could also make a minor point release for this feature before 0.3.

👍 guess I better get started then... :)

Question: if we implement this method at the JAMS object level, it provides an easy way to trim all annotations contained in the jam with one call. On the flip side, since different annotations can span different time ranges, this means that we it doesn't really make sense to check/enforce that the specified trim start/end times are within the duration of every annotation (as they are likely to be within the range of some annotation and outside the range of others) - which means that basically this might actually end up "padding" some of the annotations, unless we only apply the trimming to those annotations for which the start/end times are valid and raise warnings for the others, but I'm not sure I like this option because it can (will) create a mess.
The alternative would be to implement trim as a method of Annotation, allowing the user to selectively trim only specific annotations. Then we could strictly require that the specified start/end times be within the annotation's duration, and could also implement another method at the JAMS object level that will iterate over all annotations and try to trim them (but will raise an error if any are outside the specified trim range).
Thoughts?

On the flip side, since different annotations can span different time ranges, this means that it doesn't really make sense to check/enforce that the specified trim start/end times are within the duration of every annotation

Not sure I follow you there.
Here's how I see it:

Implement Annotation.trim(start, end).  The logic is, I think, as follows:

my_end = ann.start + ann.duration
ann.start = min(0, ann.start - start)
ann.duration = min(end, my_end) - ann.start
And then trim all jamsframe events accordingly.
You might want to parameterize this by duration instead of end.  It might also be simpler to just handle the pad logic in here as well, in case end > ann.duration - ann.start.

Implement trim in all the other jams objects, particularly FileMetadata.

The top-level trim just recurses down the object hierarchy trimming things as needed to populate the new object.

Not sure I follow you there.

Let me try again: do we want to impose any conditions on being able to tim an annotation? For example, you can only trim an annotation if the specified start/end times are within the annotation's current start/end times? So for example, if an annotation starts at 5 and ends at 15, you can't for example call ann.trim(3, 8) because the new start time is outside the original range of the annotation.
Alternatively, we can just not impose any limitations, which means that trim can also be used to pad annotations (e.g. ann.trim(0, 20) would pad the annotation given above as an example).

ann.start = min(0, ann.start - start)

I'm not sure I follow the logic here, wouldn't it just be, for Annotation.trim(start, end):
ann.time = min(0, start)
ann.duration = end - start

The third option (perhaps what you were getting at?) would be to return the intersection of the original annotation range and the desired trim, so that calling trim(3,8) on an annotation that spans [5,15] would return an annotation spanning [5,8]. I'm not sure that's a good option though?

In case it makes things clearer, here's what Annotation.trim() might look like if we don't impose any conditions on trimming (i.e. trimming can also be padding):
    def trim(self, start_time, end_time):
        '''
        Trim the annotation and return as new Annotation object. Trimming will
        result in the new annotation only containing observations that occur
        between `start_time` and `end_time`. Observations that start before
        `start_time` but end after it will be trimmed such that they start at
        `start_time`, and similarly observations that start before `end_time`
        but end after it will be trimmed to end at `end_time`. The new
        duration of the annotation will be `end_time - start_time`. Note that
        depending on the values of `start_time` and `end_time` this function
        can also pad the annotation. This function also copies over all the
        annotation metadata from the original annotation, and adds a list of
        tuples to the annotation's sandbox keyed by `trim`, which documents
        the trim parameters: each trim operation adds a tuple to this list
        containing two elements: the `start_time` and `end_time`.

        Parameters
        ----------
        start_time : float
            The new start time for the annotation
        end_time
            The new end time for the annotation

        Returns
        -------
        ann_trimmed : jams.Annotation
            The trimmed annotation, return as a new jams.Annotation object.
        '''
        # Create new annotation with same namespace/metadata
        ann_trimmed = Annotation(
            self.namespace,
            data=None,
            annotation_metadata=self.annotation_metadata,
            sandbox=self.sandbox,
            time=start_time,
            duration=end_time - start_time)

        # Selectively add observations based on their start time / duration
        for idx, obs in self.data.iterrows():

            obs_start = obs['time'].total_seconds()
            obs_end = obs_start + obs['duration'].total_seconds()

            if obs_start < end_time and obs_end > start_time:
                new_start = max(obs_start, start_time)
                new_end = min(obs_end, end_time)
                new_duration = new_end - new_start
                ann_trimmed.append(time=new_start,
                                   duration=new_duration,
                                   value=obs['value'],
                                   confidence=obs['confidence'])

            if 'trim' not in ann_trimmed.sandbox.keys():
                ann_trimmed.sandbox.update(trim=[(start_time, end_time)])
            else:
                ann_trimmed.sandbox.trim.append((start_time, end_time))

        return ann_trimmed

p.s.

Implement trim in all the other jams objects, particularly FileMetadata.

Do we want this? You could reasonably want to trim an annotation without trimming the corresponding audio file, in which case the file metadata would remain unchanged. I would delegate this to the user, i.e. if they are also trimming the audio file, then they should make sure to update the file metadata. That's basically what will happen inside scaper.

Do we want this? You could reasonably want to trim an annotation without trimming the corresponding audio file, in which case the file metadata would remain unchanged.

If that's what you want to do, then it should be done by calling trim on the annotation of interest and adding it back to the existing jams.
At the top level, trimming a jams should trim the entire object (including metadata) so that everything stays consistent.

At the top level, trimming a jams should trim the entire object (including metadata) so that everything stays consistent.

Was there ever any assumption that all annotations in a jams file have consistent time/duration? Isn't it the case that the file_metadata should always correspond to the audio file, but the annotations can span any time range? Under this scenario I think you'd only want to change the file_metadata if you actually manipulated the audio file - but I don't see why manipulating the annotations (specifically trimming/padding) should change the file metadata. E.g., you have a 3 min audio file and an annotation that spans the first 2 min, then for whatever reason you trim it to span just the first 1 min - the audio file is still 3 min. That's why I'd delegate modifying the file_metadata to the code that modifies the audio file (e.g. MUDA or Scaper).
But anyway, before we figure that one out the most pertinent decision to make is whether we want to impose limitations on trimming (so that it's only really trimming) or not (in which case it's trimming/padding).
Right now i've implemented trimming at the annotation level without limitations (so it's trimming/padding) as per the snippet I pasted in this comment.

Was there ever any assumption that all annotations in a jams file have consistent time/duration?

Yes; at least, time within a single jams object should be consistent across all annotations.
It's okay for different annotations to span different subsets of the track: that's why we have Annotation.time,duration as well as within the observations.

Isn't it the case that the file_metadata should always correspond to the audio file, but the annotations can span any time range?

This is syntactically allowed, but should not happen.

Under this scenario I think you'd only want to change the file_metadata if you actually manipulated the audio file - but I don't see why manipulating the annotations (specifically trimming/padding) should change the file metadata. E.g., you have a 3 min audio file and an annotation that spans the first 2 min, then for whatever reason you trim it to span just the first 1 min - the audio file is still 3 min.

If you do this, then you should trim the annotation, not the jams object.
However, if you actually are trimming/padding a jams object to match an audio file (say, after doing some alignment / deskewing or what have you), then it's totally sensible to want to change the entire object at once.

That's why I'd delegate modifying the file_metadata to the code that modifies the audio file (e.g. MUDA or Scaper).

I think it's a useful enough operation to live inside jams.

But anyway, before we figure that one out the most pertinent decision to make is whether we want to impose limitations on trimming (so that it's only really trimming) or not (in which case it's trimming/padding).

I only mentioned padding in the previous post because it would simplify the logic a bit if you allow end to grow as well as shrink.
In general, padding is a separate problem, and should probably be a separate function.

I only mentioned padding in the previous post because it would simplify the logic a bit if you allow end to grow as well as shrink.
In general, padding is a separate problem, and should probably be a separate function.

So I already have this implemented (in a way that supports both trimming/padding) here.
This could be changed to only support trimming (by adding checks to ensure start_time and end_time are within the time range spanned by the annotation): let me know if that's how you want to go about it.
By "consistent time" I didn't mean a consistent time-grid, rather a consistent start time (which in jams-land is just called "time" everywhere) and duration, to which, as you noted in your second reply, the answer is no (i.e. different annotations can span different time ranges).

However, if you actually are trimming/padding a jams object to match an audio file (say, after doing some alignment / deskewing or what have you), then it's totally sensible to want to change the entire object at once.

ok, I'll go with this then.

After discussing further with @bmcfee , we've agreed on the following functionality:

Annotation.trim() (and hence JAMS.trim()) can only be used for trimming, not padding
calling ann.trim(start_time, end_time) will return the intersection of the annotation's original time range (defined by ann.time and ann.duration) and the range defined by start_time and end_time. Note that this can return an empty annotation if the ranges don't intersect at all (perhaps raise a warning in this case?)
ann.trim() will have an option strict argument, which when set to True requires the specified start_time and end_time to be contained within the range defined by ann.time and ann.duration (i.e. the trim range must be a sub-range of the annotation's current time range).
JAMS.trim() will result in calling Annotation.trim() on all annotations contained in the jam's annotation array. It will also update the jam.file_metadata.duration field.

In addition, I'm documenting every trim operation in the annotation sandbox (as ann.sandbox.trim which stores a list of tuples, each tuple containing the start_time and end_time of the trim operation) whenever ann.trim() is called. If jams.trim() is called, the same documentation will occur in jams.sandbox.trim, as well as in the sandbox of each annotation stored inside the jam.

I just realized something - the current behavior will trim the annotations, but will not modify their start time of the observations. This is useful for when you just want to trim an annotation but not the corresponding audio file. However, if you also trim the audio file, then you'd like the event times to also be adjusted accordingly.
@bmcfee How about we leave the default behavior as this (i.e. observation times are not changed), but add an optional parameter adjust_times=False which, if True, will also adjust the time of each observation?

How about we leave the default behavior as this (i.e. observation times are not changed), but add an optional parameter adjust_times=False which, if True, will also adjust the time of each observation?

Implemented by 66c1c25, 9f3c4d0, 3dec6c9.

Documenting latest modifications to API (as of 95cdda4):

trim() has been refactored into trim() and slice()

Here's the low-down for trimming:

Input parameters are start_time, end_time, and strict=False
Annotation.trim() will change the start time/duration of an annotation:
new start time is given by max(Annotation.time, start_time)
new duration is computed using new start time and new end time, where new end time is given by min(Annotation.time + Annotation.duration, end_time)
Annotation.trim() will remove all observations that lie outside of the trim range defined by the new start time and duration:
If strict=False (default), observations at the boundaries will be adjusted. I.e., if an observation starts before the new start time but ends after it, only the part that lies at/after the new start time is kept. The equivalent happens if the observation starts before but ends after the new end time.
If strict=True, observations at the boundaries are also discarded.
With the exception of annotations at the boundaries, Annotation.trim() does not modify the start time of the observations.
Each call to Annotation.trim() is documented in Annotation.sandbox.trim
JAMS.trim() calls AnnotationArray.trim() which calls Annotation.trim() on every annotation in the jams object.
JAMS.trim() is documented in JAMS.sandbox.trim
JAMS.trim() does not affect JAMS.file_metadata.duration

Here's the low-down for slicing:

Slicing (at the Annotation, AnnotationArray and JAMS level) behaves exactly the same as trimming, except:
After trimming, the start time of the annotation is recomputed and is given by max(0, trimmed_annotation.time - start_time), and the start times of all observations it contains are re-computed with respect to this new reference time. To give a concrete example, say an annotation spans time 10-15s. If we call ann.slice(12, 14), the new annotation will have a start time of 0 and duration 2. If instead we call ann.slice(5, 15), the sliced annotation will have a start time of 5 and duration 5.
JAMS.slice() calls AnnotationArray.slice() which calls Annotation.slice() on every annotation in the jams object.
JAMS.slice() does affect JAMS.file_metadata.duration, which becomes end_time - start_time

In a nutshell, trimming is useful when one wishes to modify the time range spanned by an annotation, but keep the corresponding audio file unchanged (and hence all the start times remain unchanged). Slicing is useful when the corresponding audio file will also be trimmed (cropped in time), in which case the start time of the annotation and all observations it contains to need to be adjusted.
Why doesn't slice() always set the start time of the annotation to 0?
This could lead to undesirable behavior if you tried to slice an annotation by defining a time range that starts before the start time of the annotation (i.e. start_time < Annotation.time). To give a concrete example, say you have an audio file from 0-15s, and an annotation that spans 10-15s. If you called jam.slice(5, 15), the sliced jam file would have a duration of 10s corresponding to "original" time 5-15s. The annotation would have a duration of 5s which corresponds to "original" time 10-15s, but since its start time was reset to 0, it would be as if the annotation describes time 0-5s in the new jam, while it actually describes time 5-10s. That is, it should have a start time of 5s. That's why the new start time of the annotation is given by max(0, trimmed_annotation.time - start_time).


test-branch/execute-job/comment-from-wrong-user-on-pr/d088e2b4-5926-44df-99f0-a1d8d0bfdd42

PR for testing 8097fa0b389c864817d8b069ff0ea1acfabf9c4c

/canonical/self-hosted-runners/run-workflows 8097fa0b389c864817d8b069ff0ea1acfabf9c4c


Can't Move Bar Items Using Image Insets

Whatever I change the insets, the image doesn't get any offset.
Is it only me having this problem?

What should I do if I have for example 2 rotation & 1 bounce (in order - rotation-bounce-rotat). I want to offset the middle one above and offset the rotation ones below a little. Is there a way or workaround for that?

I also tried using this (in AppDelegate) but doesn't change it.
            let midBtn = ramTBC.tabBar.items![1]
            midBtn.imageInsets = UIEdgeInsetsMake(5,0,-5,0)

Is there a workaround for that issue?

I found the way for vertical movements (y-offSet), but still looking for an answer for x-Offset..
Digging in the library, I realised that inside createCustomIcons method in RAMAnimatedTabBarController, createConstraints(icon, container: container, size: itemImage.size, yOffset: -5) helps yOffset. And I can wrap it in an if condition (index number indicates the tab number so you can give a different yOffset for different tab icons)
However, I still couldn't manage to move icons to left & right; how can I achieve the xOffset kind of approach for icons?


[Feature Request] Shift click to open effect AE dialogue

Shift click to open the active effect dialogue for the item (ideally  with initial focus set to the duration tab)
Extempore effects enables this for Pathfinder 2e effects and it is exceptionally useful for when durations need to be re applied after effects are accidentally removed, or if something impacts the duration of an effect initially.

You can open it by double clicking the icon. v2.0.1 fixes an issue where the ability to drag the panel around was interfering with this behavior


Add toggle on/off by keyboard shortcut

Could you please add toggle on/off functionality? Best would be to have a keyboard shortcut for that.
Currently it's only possible to enable/disable the extension and that requires a Visual Studio restart.

:+1: this feature. If not include a binding, at least provide the ability to create a binding.

provide the ability to create a binding.
:+1: on this.

I'll have a look after work today

I've stubbed in some of the code on my fork. I just need Guids and CommandIds, I believe, so it's as of yet not complete enough for a PR.
https://github.com/jeroldhaas/Visual-Studio-Power-Mode

+1

Any update on this?

I'm stalled at the moment. If someone wants to pick up where I've left off, they're welcome to it. 😄

#40 should fix this


Not all users receive the messages from Company Communicator.

Microsoft.Bot.Schema.ErrorResponseException: Operation returned an invalid status code 'NotFound' at Microsoft.Bot.Connector.Conversations.ReplyToActivityWithHttpMessagesAsync(String conversationId, String activityId, Activity activity, Dictionary2 customHeaders, CancellationToken cancellationToken) at Microsoft.Bot.Connector.ConversationsExtensions.ReplyToActivityAsync(IConversations operations, String conversationId, String activityId, Activity activity, CancellationToken cancellationToken) at Microsoft.Bot.Builder.BotFrameworkAdapter.SendActivitiesAsync(ITurnContext turnContext, Activity[] activities, CancellationToken cancellationToken) at Microsoft.Bot.Builder.TurnContext.[]c__DisplayClass31_0.[[SendActivitiesAsync]g__SendActivitiesThroughAdapter|1]d.MoveNext()--- End of stack trace from previous location where exception was thrown --- at Microsoft.Bot.Builder.TurnContext.SendActivityAsync(IActivity activity, CancellationToken cancellationToken) at Microsoft.Teams.Apps.CompanyCommunicator.Common.Services.Teams.MessageService.[]c__DisplayClass3_1.[[SendMessageAsync]b__1]d.MoveNext() in C:\home\site\repository\Source\CompanyCommunicator.Common\Services\Teams\Messages\MessageService.cs:line 94--- End of stack trace from previous location where exception was thrown --- at Polly.Retry.AsyncRetryEngine.ImplementationAsync[TResult](Func3 action, Context context, CancellationToken cancellationToken, ExceptionPredicates shouldRetryExceptionPredicates, ResultPredicates1 shouldRetryResultPredicates, Func5 onRetryAsync, Int32 permittedRetryCount, IEnumerable1 sleepDurationsEnumerable, Func4 sleepDurationProvider, Boolean continueOnCapturedContext) at Polly.AsyncPolicy.ExecuteAsync[TResult](Func`3 action, Context context, CancellationToken cancellationToken, Boolean continueOnCapturedContext) at Microsoft.Teams.Apps.CompanyCommunicator.Common.Services.Teams.MessageService.[]c__DisplayClass3_0.[[SendMessageAsync]b__0]d.MoveNext() in C:\home\site\repository\Source\CompanyCommunicator.Common\Services\Teams\Messages\MessageService.cs:line 94

What is the version of the app? 5.2.0
What the count of members in the team? 3121 users
Please share Success and failure count, supporting screenshot would be helpful -

Is this a first message? no

Hi @karloscri ,
Please try uninstalling the author, user app and re-upload it . Then try sending the message. Please keep us posted.

I had a similar problem, where the error occurred due to a manual lock made by the user.
I don't know if this can help.

Thanks will check that too.

From: WaldekBarros @.>
Sent: Friday, June 30, 2023 6:12:27 PM
To: OfficeDev/microsoft-teams-apps-company-communicator @.>
Cc: Jon Garrett @.>; Comment @.>
Subject: Re: [OfficeDev/microsoft-teams-apps-company-communicator] Not all users receive the messages from Company Communicator. (Issue #1080)
I had a similar problem, where the error occurred due to a manual lock made by the user.
I don't know if this can help.
[image]https://user-images.githubusercontent.com/129632590/250153622-3c21316d-d09f-4fcd-9774-67a7bbc36b5f.png
—
Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1080#issuecomment-1614942677, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXY763W5F66PG46FTZV2RJLXN4CHXANCNFSM6AAAAAAZVOZVVM.
You are receiving this because you commented.Message ID: @.***>
Please consider the environment before printing this email
Please see Osborne Clarke's updated Privacy Policy http://www.osborneclarke.com/website-privacy/ and our updated terms of business which reflect the changes required by the General Data Protection Regulation http://www.osborneclarke.com/general-terms-conditions/
Osborne Clarke LLP is a limited liability partnership registered in England and Wales with registered number OC397443 whose registered office is at One London Wall, London EC2Y 5EB. It is authorised and regulated in the UK by the Solicitors Regulation Authority (SRA) and is registered as a recognised body with SRA number 619990. More information about Osborne Clarke LLP can be found on our website http://www.osborneclarke.com.
The term ‘partner’ refers to a member of Osborne Clarke LLP. A list of members of Osborne Clarke LLP and their professional qualifications is available for inspection at the registered office. Any advice given by any individual member, employee, or consultant is the responsibility of Osborne Clarke LLP and not the individual.
Osborne Clarke LLP is part of an international legal practice.
…………………………………………
This email is confidential and may also be privileged. It is intended for the use of the addressee only except where the email states it can be disclosed: if you receive this email in error, please accept our apology and delete it.
Email communications may be monitored by us, as permitted by applicable law and regulations. We believe, but do not warrant, that this email and any attachments are virus free, but please be careful.

Please do not block the app.

Hi @karloscri , Please try uninstalling the author, user app and re-upload it . Then try sending the message. Please keep us posted.

As per the other thread:
So we believe this has been cause by the user deleting the message from Teams. The bot cannot then send a message to the user they way around it is to:
Logged on, cleared cache from roaming
C:\Users<User.Name>\AppData\Roaming\Microsoft\Teams\Cache\Cache_Data
Sometimes thats enough, if not is a reinstall of Teams. If anyone else could confirm their end user deleted the chat too and it fixed it?

I installed the latest version and I still have the same error 5.4.1

As per the other thread:
So we believe this has been cause by the user deleting the message from Teams. The bot cannot then send a message to the user they way around it is to:
Logged on, cleared cache from roaming
C:\Users<User.Name>\AppData\Roaming\Microsoft\Teams\Cache\Cache_Data
Sometimes thats enough, if not is a reinstall of Teams. If anyone else could confirm their end user deleted the chat too and it fixed it?

Just out of interest, if the user's deleted the conversation, surely a quick fix would be to delete the storage account table entry for the user instead?

I have this same problem again, How can I reopen the case?


Refresh Admin UI docs

this PR refreshes the Admin UI docs to match the latest version and brings the formatting and style up-to-date with current standards

@mechanomi wondering what your thoughts are on my screenshot comments?

@infoverload yup, I agree. just need to run through and generate them again

I have addressed the comments with a fixup
unfortunately, using the 4.3.1 release, I am unable to produce a new screenshot for the monitoring overview screen because of https://github.com/crate/crate/pull/10759
the fix for this is in the nightly release, but I am running into a second issue with that: the bin/crate script itself errors because of a Java issue. I am discussing this internally to see if I can figure out how to resolve the issue. otherwise, I will have to wait until 4.3.2 is released

still blocked on crate 4.3.2 release

@infoverload heya! I pushed the fixes you requested. can you take a look please? thx!!


version <IP_ADDRESS> of MembershipReboot.EF breaks  DisposableIdentityManagerService

Version 8 of the EF breaks the DisposableIdentityManagerService(IIdentityManagerService, IDisposable) constructor because the DefaultMembershipReboot no longer supports the IDisposable interface.

brockallen, I am not finding beta3. Please send me URL. DisposableIdentityManagerService still gives errors. Thanks for all your help.

It was removed in beta3 in favor of the new DI system.


Create docker.Container obj with Name. Integration test is using fake_do...

...cker_client
to create and start a fake container. When StartContainer, it pass a name as docker
ID for testing purpose, but leave Name uninitialized. This PR fixes such issue.
Fixed #4472.

cc/ @xiang90

LGTM.
Do you want to get this reviewed from someone specifically or is it good to merge?

I think this is ready to merge. Thanks!

@dchen1107 Ah. I think this is the root cause. Thanks.


Tags seem to all point to the same commit.

I kind of wanted to check out a specific version. And I think this also breaks jitpack distribution.

You can still reference commits by ID, through JitPack.


Vertical pfe-tabs need design updates

https://sketch.cloud/s/3WK1w/a/LEVm95

spacing updates
move highlight to left side
add hover state

closing, duplicate of  https://github.com/patternfly/patternfly-elements/issues/672


GPU utilization of these two Epoch is very low

I run https://www.tensorflow.org/alpha/tutorials/text/transformer in Calab with GPU.
The result is a strange phenomenon. The first two Epoch are very slow. I tried to run on my local machine and the result was the same. According to observations, the GPU utilization of these two Epoch is very low, almost zero. What happened to these two Epoch?
Epoch 1 Batch 0 Loss 4.4497 Accuracy 0.0000
Epoch 1 Batch 500 Loss 3.6058 Accuracy 0.0401
Epoch 1 Loss 3.3683 Accuracy 0.0538
Time taken for 1 epoch: 1175.7783224582672 secs

Epoch 2 Batch 0 Loss 2.8402 Accuracy 0.0966
Epoch 2 Batch 500 Loss 2.4239 Accuracy 0.1189
Epoch 2 Loss 2.3728 Accuracy 0.1240
Time taken for 1 epoch: 1116.1639959812164 secs

Epoch 3 Batch 0 Loss 2.4180 Accuracy 0.1410
Epoch 3 Batch 500 Loss 2.1358 Accuracy 0.1484
Epoch 3 Loss 2.1007 Accuracy 0.1518
Time taken for 1 epoch:<PHONE_NUMBER>7341614 secs

Epoch 4 Batch 0 Loss 2.2033 Accuracy 0.1632
Epoch 4 Batch 500 Loss 1.8985 Accuracy 0.1763
Epoch 4 Loss 1.8629 Accuracy 0.1806
Time taken for 1 epoch:<PHONE_NUMBER>1847534 secs

Epoch 5 Batch 0 Loss 1.9665 Accuracy 0.1941
Epoch 5 Batch 500 Loss 1.6708 Accuracy 0.2037
Saving checkpoint for epoch 5 at ./checkpoints/train/ckpt-1
Epoch 5 Loss 1.6434 Accuracy 0.2066
Time taken for 1 epoch:<PHONE_NUMBER>3805237 secs

Epoch 6 Batch 0 Loss 1.7504 Accuracy 0.2196
Epoch 6 Batch 500 Loss 1.4882 Accuracy 0.2233
Epoch 6 Loss 1.4662 Accuracy 0.2257
Time taken for 1 epoch:<PHONE_NUMBER>0370483 secs

Epoch 7 Batch 0 Loss 1.5731 Accuracy 0.2368
Epoch 7 Batch 500 Loss 1.3058 Accuracy 0.2438
Epoch 7 Loss 1.2844 Accuracy 0.2462
Time taken for 1 epoch:<PHONE_NUMBER>2595825 secs

Epoch 8 Batch 0 Loss 1.3853 Accuracy 0.2504
Epoch 8 Batch 500 Loss 1.1468 Accuracy 0.2625
Epoch 8 Loss 1.1327 Accuracy 0.2643
Time taken for 1 epoch:<PHONE_NUMBER>1892395 secs

Epoch 9 Batch 0 Loss 1.2550 Accuracy 0.2759
Epoch 9 Batch 500 Loss 1.0325 Accuracy 0.2769
Epoch 9 Loss 1.0226 Accuracy 0.2780
Time taken for 1 epoch: 99.68828344345093 secs

Epoch 10 Batch 0 Loss 1.1568 Accuracy 0.2833
Epoch 10 Batch 500 Loss 0.9410 Accuracy 0.2888
Saving checkpoint for epoch 10 at ./checkpoints/train/ckpt-2
Epoch 10 Loss 0.9350 Accuracy 0.2891
Time taken for 1 epoch:<PHONE_NUMBER>9683838 secs

Notice that such information appears when running locally, I don't know if it is related.
> 2019-05-05 09:14:47.113549: W tensorflow/core/common_runtime/executor.cc:2237] [/device:CPU:0] Executor start aborting: Invalid argument: You must feed a value for placeholder tensor 'Placeholder/_0' with dtype string and shape [10]
> 	 [[{{node Placeholder/_0}}]]
> 2019-05-05 09:14:47.114102: W tensorflow/core/common_runtime/executor.cc:2237] [/device:CPU:0] Executor start aborting: Invalid argument: You must feed a value for placeholder tensor 'Placeholder/_0' with dtype string and shape [10]
> 	 [[{{node Placeholder/_0}}]]

@soloice Can you please take a look at this issue? Thanks!

Probably the same as this one.

I tried the code on my local environment (GTX 1080 Ti + CUDA 10.0.0 + TF 1.13.1) and it runs normally (the very first epoch is slightly longer 154s vs. ~110s of subsequent epoches):
2019-05-17 14:21:46.428676: W ./tensorflow/core/framework/model.h:202] Encountered a stop event that was not preceded by a start event.
2019-05-17 14:21:56.422792: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:103] Filling up shuffle buffer (this may take a while): 11737 of 20000
2019-05-17 14:22:02.903131: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:150] Shuffle buffer filled.
Epoch 1 Batch 0 Loss 4.4382 Accuracy 0.0000
Epoch 1 Batch 500 Loss 3.4579 Accuracy 0.0389
Epoch 1 Loss 3.2365 Accuracy 0.0530
Time taken for 1 epoch:<PHONE_NUMBER>8368835 secs

2019-05-17 14:24:21.745880: W ./tensorflow/core/framework/model.h:202] Encountered a stop event that was not preceded by a start event.
2019-05-17 14:24:31.740729: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:103] Filling up shuffle buffer (this may take a while): 12293 of 20000
2019-05-17 14:24:38.427798: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:150] Shuffle buffer filled.
Epoch 2 Batch 0 Loss 2.6457 Accuracy 0.1018
Epoch 2 Batch 500 Loss 2.3402 Accuracy 0.1217
Epoch 2 Loss 2.2758 Accuracy 0.1303
Time taken for 1 epoch:<PHONE_NUMBER>5299072 secs

2019-05-17 14:26:16.247264: W ./tensorflow/core/framework/model.h:202] Encountered a stop event that was not preceded by a start event.
2019-05-17 14:26:26.241918: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:103] Filling up shuffle buffer (this may take a while): 13094 of 20000
2019-05-17 14:26:31.618235: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:150] Shuffle buffer filled.
Epoch 3 Batch 0 Loss 2.1175 Accuracy 0.1672
Epoch 3 Batch 500 Loss 1.9352 Accuracy 0.1706
Epoch 3 Loss 1.9053 Accuracy 0.1748
Time taken for 1 epoch:<PHONE_NUMBER>8468018 secs

2019-05-17 14:28:08.755016: W ./tensorflow/core/framework/model.h:202] Encountered a stop event that was not preceded by a start event.
2019-05-17 14:28:18.749417: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:103] Filling up shuffle buffer (this may take a while): 13690 of 20000
2019-05-17 14:28:23.495135: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:150] Shuffle buffer filled.
Epoch 4 Batch 0 Loss 1.8739 Accuracy 0.1959
Epoch 4 Batch 500 Loss 1.7347 Accuracy 0.1924
Epoch 4 Loss 1.7185 Accuracy 0.1950
Time taken for 1 epoch:<PHONE_NUMBER>9520264 secs

2019-05-17 14:29:57.784247: W ./tensorflow/core/framework/model.h:202] Encountered a stop event that was not preceded by a start event.
2019-05-17 14:30:07.778153: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:103] Filling up shuffle buffer (this may take a while): 12566 of 20000
2019-05-17 14:30:13.554589: I tensorflow/core/kernels/data/shuffle_dataset_op.cc:150] Shuffle buffer filled.
Epoch 5 Batch 0 Loss 1.7317 Accuracy 0.2044
Epoch 5 Batch 500 Loss 1.6061 Accuracy 0.2057
Saving checkpoint for epoch 5 at ./checkpoints/train/ckpt-1
Epoch 5 Loss 1.5919 Accuracy 0.2081
Time taken for 1 epoch:<PHONE_NUMBER>2338562 secs

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

I am seeing the same issue regularly, not every run though. My input data are images of the same size. This happens with all kinds of network sizes. It happens on both my machines.


Melos error when using drift postgres

Is there a reason the example uses this specific fork of the postgres package?
https://github.com/simolus3/drift/blob/e1b5da3160232403cbe95340218e8e6c762a07cd/extras/drift_postgres/pubspec.yaml#L26
So if you using melos to build a package and you follow the instructions in the readme you get the following error when running flutter upgrade and melos bs:
Because every version of drift_postgres from git depends on postgres from hosted and test_package depends on postgres from git, drift_postgres from git is forbidden.
So, because test_package depends on drift_postgres from git, version solving failed.

i managed to get rid of the error by unpinning the postgres and letting it use the package from pub.dev

I didn't know pub/melos also apply dependency_overrides from external dependencies - the override was just meant as something useful when working on drift_postgres itself.
Since a usable version of the v3 preview APIs have since been published to pub.dev, I've just removed the dependency override from the readme.


Adding endfloat.sty auxiliary files

endfloat.sty produces these two auxiliary files.
From Section 3.2 of its documentation:

Loading it will have LATEX produce two extra files with .ttt and .fff extensions (for tables and figures, respectively).

Thanks!


Webview related errors with SSH FS Addon. Blank tabs.

OS/Web Information

Web Browser: Firefox
Local OS: Homeassistant OS
Remote OS:
Remote Architecture:
code-server --version:

Steps to Reproduce

Install SSH FS Addon from marketplace
Open SSH FS configuration and add new connection
Blank tab appears

Expected
A tab with SSH FS settings should appear

Actual
Just a blank tab appears, and some webview related errors in Firefox console.

Logs
Not able to provide logs right now. See all information about this in link below.
https://github.com/SchoofsKelvin/vscode-sshfs/issues/279

Screenshot

Notes
All information can be found here:
https://github.com/SchoofsKelvin/vscode-sshfs/issues/279
I'm not sure if it's OK to open a bug report and just refer to another topic. But this is all I can do right now. Just trying to help out to get this bug sorted out. At least to start somewhere.

This issue can be reproduced in VS Code: Yes/No

I'm not sure if it's OK to open a bug report and just refer to another topic. But this is all I can do right now. Just trying to help out to get this bug sorted out. At least to start somewhere.

Really appreciate that ♥
So I'm using code-server 3.12.0 on macOS + Brave and this is what happens when I try to reproduce this.
Reproducing

Download extension from VSX marketplace
Install in code-server
Add new configuration

It works as expected. I think we're going to have to wait until you get more information so we can have you look at the browser logs.
If you're getting a blank tab, it's probably the resources failing to load, which is common when you're not using HTTPS.

I can try get the logs from where I am right now (not home).
So the easiest way to get browser logs?

Tell me and I'll try to bring that up for you.
I'm not a programmer/coder so maybe someone can help me out with this

No worries at all! I made a video to show you. Let me know if that helps.
Video
https://user-images.githubusercontent.com/3806031/135330178-8ee7a795-fefa-40da-b66d-24f47a792d83.mov

Thank you very much for that beautiful instruction.
Got the logs from when I press "Add new configuration"
I'm on remote access via Nabu Casa right now as you can see in the logs. It doesn't matter if I'm doing this locally, the tab is blank anyway.
08:10:45.532 Feature Policy: Skipping unsupported feature name “clipboard-read”. webviewElement.ts:84:10
08:10:45.532 Feature Policy: Skipping unsupported feature name “clipboard-write”. webviewElement.ts:84:10
08:10:45.536 Feature Policy: Skipping unsupported feature name “clipboard-read”. webviewElement.ts:117:16
08:10:45.536 Feature Policy: Skipping unsupported feature name “clipboard-write”. webviewElement.ts:117:16
08:10:45.537 Feature Policy: Skipping unsupported feature name “clipboard-read”. webviewElement.ts:130:10
08:10:45.537 Feature Policy: Skipping unsupported feature name “clipboard-write”. webviewElement.ts:130:10
08:10:45.600 GEThttps://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/index.html?id=ad398544-4049-4be9-9088-25cdd9aa35f7&swVersion=2&extensionId=Kelvin.vscode-sshfs&vscode-resource-base-authority=vscode-resource.vscode-webview.net
[HTTP/1.1 200 OK 240ms]

08:10:45.610 GEThttps://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/vscode-remote-resource?path=/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/resources/icon.svg&tkn=
[HTTP/1.1 200 OK 245ms]

08:10:46.016 GEThttps://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/host.js
[HTTP/1.1 200 OK 90ms]

08:10:46.167 GEThttps://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/main.js
[HTTP/1.1 200 OK 119ms]

08:10:46.449 Feature Policy: Skipping unsupported feature name “clipboard-read”. main.js:677:12
08:10:46.449 Feature Policy: Skipping unsupported feature name “clipboard-write”. main.js:677:12
08:10:46.449 Feature Policy: Skipping unsupported feature name “clipboard-read”. main.js:682:36
08:10:46.449 Feature Policy: Skipping unsupported feature name “clipboard-write”. main.js:682:36
08:10:46.449 Feature Policy: Skipping unsupported feature name “clipboard-read”. main.js:685:17
08:10:46.449 Feature Policy: Skipping unsupported feature name “clipboard-write”. main.js:685:17
08:10:46.474 GEThttps://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/fake.html?id=ad398544-4049-4be9-9088-25cdd9aa35f7
[HTTP/1.1 200 OK 85ms]

08:10:46.722 GEThttps://vscode-remote+xxxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/runtime-main.bundle.js
CSP

08:10:46.722 Content Security Policy: The page’s settings blocked the loading of a resource at https://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/service-worker.js?id=ad398544-4049-4be9-9088-25cdd9aa35f7&swVersion=2&extensionId=Kelvin.vscode-sshfs&vscode-resource-base-authority=vscode-resource.vscode-webview.net (“script-src”).
08:10:46.722 Loading failed for the <script> with source “https://vscode-remote+xxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/runtime-main.bundle.js”. index.html:116:1
08:10:46.739 Content Security Policy: The page’s settings blocked the loading of a resource at https://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/service-worker.js?id=ad398544-4049-4be9-9088-25cdd9aa35f7&swVersion=2&extensionId=Kelvin.vscode-sshfs&vscode-resource-base-authority=vscode-resource.vscode-webview.net (“script-src”).
08:10:46.740 GEThttps://vscode-remote+xxxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/269.bundle.js
CSP

08:10:46.740 Loading failed for the <script> with source “https://vscode-remote+xxxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/269.bundle.js”. index.html:116:1
08:10:46.740 Content Security Policy: The page’s settings blocked the loading of a resource at https://xxxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/service-worker.js?id=ad398544-4049-4be9-9088-25cdd9aa35f7&swVersion=2&extensionId=Kelvin.vscode-sshfs&vscode-resource-base-authority=vscode-resource.vscode-webview.net (“script-src”).
08:10:46.741 GEThttps://vscode-remote+xxxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/main.bundle.js
CSP

08:10:46.741 Loading failed for the <script> with source “https://vscode-remote+xxxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/main.bundle.js”. index.html:116:1

08:10:46.722 Content Security Policy: The page’s settings blocked the loading of a resource at https://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/service-worker.js?id=ad398544-4049-4be9-9088-25cdd9aa35f7&swVersion=2&extensionId=Kelvin.vscode-sshfs&vscode-resource-base-authority=vscode-resource.vscode-webview.net (“script-src”).
08:10:46.722 Loading failed for the <script> with source “https://vscode-remote+xxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/runtime-main.bundle.js”. index.html:116:1
08:10:46.739 Content Security Policy: The page’s settings blocked the loading of a resource at https://xxxx.ui.nabu.casa/api/hassio_ingress/WtaX-gg53dk1GeSkD5WUAKEQDCtkRyj-evGkjQTShZg/webview/service-worker.js?id=ad398544-4049-4be9-9088-25cdd9aa35f7&swVersion=2&extensionId=Kelvin.vscode-sshfs&vscode-resource-base-authority=vscode-resource.vscode-webview.net (“script-src”).
08:10:46.740 GEThttps://vscode-remote+xxxxx.ui.nabu.casa.vscode-resource.vscode-webview.net/data/vscode/extensions/kelvin.vscode-sshfs-1.22.0/webview/build/static/js/269.bundle.js
CSP

Ah-ha! Yup, it's been blocked. This could be a couple things:

are you using code-server 3.12.0? We fixed a bug related to this in that release.
are you running code-server over HTTPS? if not, that could be related.
do you have an ad-blocker or privacy settings? (like Brave) that could be related

Ad-block extensions in Firefox was inactivated during testing.
I don't think it's running over HTTPS.
The URL I'm using right now remotely to my HA instance is:
https://xxxx.ui.nabu.casa/hassio/addon/a0d7b954_vscode/info.
But when I'm using it locally the URL is:
http://192.168.x.x/hassio/addon/a0d7b954_vscode/info.
It seems like the VSCode addon using code-server 3.11.1.

But when I'm using it locally the URL is:
http://192.168.x.x/hassio/addon/a0d7b954_vscode/info.

This might be the source of the issue then. Can you try using HTTPS? We have some docs here or you can try running code-server --link.

Ad-block extensions in Firefox was inactivated during testing.
I don't think it's running over HTTPS.
The URL I'm using right now remotely to my HA instance is:
https://xxxx.ui.nabu.casa/hassio/addon/a0d7b954_vscode/info.
But when I'm using it locally the URL is:
http://192.168.x.x/hassio/addon/a0d7b954_vscode/info.
It seems like the VSCode addon using code-server 3.11.1.

@jsjoeio sorry, I accidentally messed up and closed this. Reopened again.
I'm not sure how to get the whole Home Assistant instance under HTTPS. It's strange because this blank tab and "react server" error has never showed up before and suddenly HTTPS it's a must. 🤓 I think I have missed some breaking change or something lately.
I tried  code-server --link and went through those steps and ended up with VSCode on this address:
https://a0d7b954_vscode-xxx.cdr.co/.
Then I installed SSH FS addon and tried again. Exactly the same behavior with blank tab when I tried to create new configuration.
The logs from Firefox are a bit different now:
10:27:31.533 Feature Policy: Skipping unsupported feature name “clipboard-read”. webviewElement.ts:84:10
10:27:31.533 Feature Policy: Skipping unsupported feature name “clipboard-write”. webviewElement.ts:84:10
10:27:31.538 Feature Policy: Skipping unsupported feature name “clipboard-read”. webviewElement.ts:117:16
10:27:31.538 Feature Policy: Skipping unsupported feature name “clipboard-write”. webviewElement.ts:117:16
10:27:31.539 Feature Policy: Skipping unsupported feature name “clipboard-read”. webviewElement.ts:130:10
10:27:31.539 Feature Policy: Skipping unsupported feature name “clipboard-write”. webviewElement.ts:130:10
10:27:31.595 GEThttps://a0d7b954_vscode-xxx.cdr.co/vscode-remote-resource?path=/root/.local/share/code-server/extensions/kelvin.vscode-sshfs-1.22.0/resources/icon.svg&tkn=
10:27:31.708 GEThttps://a0d7b954_vscode-xxx.cdr.co/webview/index.html?id=95ac0ffd-d310-48b3-bc0f-ec687c066be6&swVersion=2&extensionId=Kelvin.vscode-sshfs&vscode-resource-base-authority=vscode-resource.vscode-webview.net
[HTTP/2 200 OK 1344ms]

10:27:33.061 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. a0d7b954_vscode-xxx.cdr.co
10:27:33.130 GEThttps://a0d7b954_vscode-xxx.cdr.co/webview/host.js
[HTTP/2 304 Not Modified 1338ms]

10:27:34.546 GEThttps://a0d7b954_vscode-xxx.cdr.co/webview/main.js
[HTTP/2 304 Not Modified 2602ms]

10:27:50.007 Error in parsing value for ‘height’.  Declaration dropped. a0d7b954_vscode-xxx.cdr.co
10:27:50.084 GEThttps://a0d7b954_vscode-xxx.cdr.co/static/c680aae973d83583e4a73dc0c422f44021f0140e/usr/local/lib/code-server/lib/vscode/node_modules/xterm/lib/xterm.js
[HTTP/2 200 OK 2679ms]

10:27:52.890 GEThttps://a0d7b954_vscode-xxx.cdr.co/static/c680aae973d83583e4a73dc0c422f44021f0140e/usr/local/lib/code-server/lib/vscode/node_modules/xterm-addon-search/lib/xterm-addon-search.js
[HTTP/2 200 OK 2602ms]

10:27:52.890 GEThttps://a0d7b954_vscode-xxx.cdr.co/static/c680aae973d83583e4a73dc0c422f44021f0140e/usr/local/lib/code-server/lib/vscode/node_modules/xterm-addon-unicode11/lib/xterm-addon-unicode11.js
[HTTP/2 200 OK 2604ms]

10:27:52.891 GEThttps://a0d7b954_vscode-xxx.cdr.co/static/c680aae973d83583e4a73dc0c422f44021f0140e/usr/local/lib/code-server/lib/vscode/node_modules/xterm-addon-webgl/lib/xterm-addon-webgl.js
[HTTP/2 200 OK 2609ms]

I think I have missed some breaking change or something lately.

Nope, not a breaking change on our side (you would have known due to major version bump). But hey, maybe browsers made CSPs and/or service worker policies more strict? I'm not sure 🤷♂
Hmm... those logs are different but I'm not sure if it helps.
Let's call in an expert - @code-asher any ideas how to help them?

I don't know what "CSPs" are.
But I tried same procedure again, locally on Microsoft Edge and got following errors in Edge console:
Uncaught (in promise) Error: Service Workers are not enabled in browser. Webviews will not work.
    at main.js:211
    at new Promise (<anonymous>)
    at main.js:209
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'addEventListener')
    at createWebviewManager (main.js:291)
    at host.js:111

I don't know what "CSPs" are.

My bad! Content Security Policies.

Uncaught (in promise) Error: Service Workers are not enabled in browser. Webviews will not work.

Yeah same problem :( You're going to have to get HTTPS working in your environment to get this working. Sadly, we can't do much on code-server's end :(

I understand. But what I don't understand is why this blank tab never appeared before, without HTTPS.
This is so strange.
Anyway, I appreciate your help 🙏🏻

It does seem odd that you are getting a blank page on HTTP but we only
test on secure contexts like HTTPS so it is possible something changed.
Definitely try with HTTPS and see if that resolves the issue!

But I'm not sure how to do that.
VSCode running as a Home Assistant addon.
I connect to HA either locally (192.168.x.x:8123) or via Nabu Casa cloud/remote service. With Nabu Casa i get a HTTPS url. But maybe that's not enough. Either way, it gives blank tab.

Actually I should have read your logs more carefully since they indicate
you are already using HTTPS.
Your browser seems to be missing some features.  Are you using an old
version of Firefox?

Latest Firefox. Same problem with Microsoft Edge. Also same through Home Assistant app

There are some other instances where service workers will be disabled,
namely ESR releases before Firefox 78 and in private browsing mode.
I am not sure what else could cause them to be disabled...maybe
certificate issues?

Looked into it and explained some stuff on the other issue. Looks like it might be a Firefox bug. It's probably up to Firefox to fix it, or have VS Code change their webview code to account for this bug (if there's even a way to bypass it).

@flaektrem guessing you saw @SchoofsKelvin's debugging in the other issue. Since this is a Firefox issue (most likely), do you mind if we close this?

I saw that, it's ok. 🙂

I found 3.10 - the latest version that all has the same problem,
If you use <IP_ADDRESS> to access code-server page all the webview ok which like tabnine, platformio,eg
If you use real-ip like 192.168.x.x to access code-server page, all the webview is blanked screen

I think service workers work on localhost/<IP_ADDRESS> because they're allowlisted but anything else without https will not work

ause they're allowlisted

maybe,but code-server --link alway errors......

maybe,but code-server --link alway errors......

Yeah, unfortunately, we can't recommend that right now. I would advise you to check the docs here. You might have luck with using Caddy.


Pasted items with smart-quotes are being duplicated

Pasted text containing a smart quote appears twice.
Steps to reproduce
Paste the following into the console input:  example”  <- Right Double Quotation Mark
Expected results
Text appears once, as example"  <- Regular Quotation Mark (replaced in onDidPaste)
Actual results
example"example"
Text appears twice for some reason. Maybe something to do with the auto-completer?
Versions
Engine Version: 0.21.0
Web UI Version: 0.26.1
Java Version: 11.0.16
Barrage Version: 0.5.0

Note typing a smart quote directly doesn't trigger any weirdness.

Note: happens in both groovy and python consoles


Can't deploy Azure policy alzDefaultPolicyAssignments.bicep in latest commit c375e41 module with powershell

What happened? Provide a clear and concise description of the bug, including deployment details.
When trying to deploy step 8 ,via PowerShell, it gets stuck and never loads the template file. This works on a much older version. "version": "0.17.2". (I was upgrading to latest )
# For Azure global regions

$inputObject = @{
  DeploymentName        = -join ('alz-alzPolicyAssignmentDefaultsDeployment-{0}' -f (Get-Date -Format 'yyyyMMddTHHMMssffffZ'))[0..63]
  Location              = 'eastus'
  ManagementGroupId     = 'alz'
  TemplateFile          = "infra-as-code/bicep/modules/policy/assignments/alzDefaults/alzDefaultPolicyAssignments.bicep"
  TemplateParameterFile = 'infra-as-code/bicep/modules/policy/assignments/alzDefaults/parameters/alzDefaultPolicyAssignments.parameters.all.json'
}

New-AzManagementGroupDeployment @inputObject

Stuck, gave it a good 30min.

Please provide the correlation id associated with your error or bug.
No error never loads template file. Its like it is stuck.
What was the expected outcome?
It to deploy azure policy defaults
Relevant log output
NA
Check previous GitHub issues

[x] I have searched the issues for this item and found no duplicate

Code of Conduct

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

So if anyone else gets this issue I figured it out. It's too long a path for powershell to load the policies.
I was running from C:\users\myusername\Repos\blah\blah\blah
Move the whole alz-bicep repo to C:\


More Ansi color support for Windows

This was really hard to figure out because, while it seems that "keybase id" never had the proper ansi color treatment, Windows 10 has a console than can handle them. Chris Coyne and I just switched to Windows 10 at the same time, so this was invisible until I tried it on 7, then was able to repro on 10 by explicitly switching to legacy terminal mode:

After:

@maxtaco @patrickxb

:+1:


⚠ Bofrost.fr has degraded performance

In 694f717, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1615 ms

Resolved: Bofrost.fr performance has improved in 5e15c5f after 12 minutes.


Add Google Test to docker images (Run unit tests on CircleCI)

This is a rebase of PR #144.
PR #144 got merged to a non-master branch (PR #142). Following that, PR #129 got merged to master, which created some merge conflicts with the contents of PR #144. This is a rebase which resolves the merge conflicts, and sets master as the base branch.

Curiously CircleCI didn't run on these changes. Considering this includes CircleCI updates, that needs to happen.
Perhaps it was because I forced pushed the rebase, or had the old PR still open. I'm wondering if another push will unstick things.


Working demo with babel6 + karma

I've bumping my head to make proper babel6 code coverage using isparta + karma.
Right now this is the error I get from it:
Post-processing using source maps Nothing mapped from file:
My karma config:
coverageReporter: {
      instrumenters: {
        isparta : require('isparta')
      },
      instrumenter: {
        '*.js': 'isparta'
      }
    },
babelPreprocessor: {
      options: {
        sourceMap: 'inline'
      }
    },

Same here, without karma. I just get No coverage information was collected, exit without writing coverage information with no other information or error output.

As in right now, I can generate a pseudo babel6 coverage:

As you can see, the generated coverage is not properly formatted. I will try to fork the project and update istanbul peerdep.

This is my example of generating es6 coverage report with karma + karma-browserify + isparta(v4).
https://github.com/kt3k/karma-browserify-isparta-example
https://codecov.io/github/kt3k/karma-browserify-isparta-example?branch=master

@kt3k That's a pretty clever ideia. I've managed to make it work as well!

Currently istanbul's official babel-plugin-istanbul can instrument es6 code. I think that is now the most reliable way to create coverage report of es6 scripts.


Add unit tests for distributed search.

Add unit tests for distributed search in a multi-node, multi-split environment.

This is a duplicate of https://github.com/quickwit-inc/quickwit/issues/295.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_4dde93f8-1e9f-453e-adc5-e001f2c204cc/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_4dde93f8-1e9f-453e-adc5-e001f2c204cc.git

Docs Build status updates of commit a7ef4cb:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-ServiceAccountCannotAccessRepository] Your repository https://github.com/VSC-Service-Account/docs-archive-test-source has enabled Docs Build service account. It seems that at least one of the accounts, e2ebd4, does not have Read permission to the repo. Please ask your repo admin to grant correct permission to service accounts (refer to this document: https://review.docs.microsoft.com/en-us/engineering/projects/ops/engdocs/how-to-grant-service-account-permission-in-your-repository?branch=master#ops-e2e-ppe) and then retry the build. Don't know who to contact? Refer https://repos.opensource.microsoft.com/VSC-Service-Account/repos/docs-archive-test-source/permissions/ to get admin list of the repo if the repo is in one of the organizations Microsoft owns.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Adding errors

Trying to figure out why it didn't pass CI in #1

The issue was that the ast name is always but we need to print finally. It was caught by the pp(pp(x)) == pp(x) check which doesn't run by default locally.


DatabasesHADR table isn't updated when DBs removed from AG

The databases still appear to be in the availability group and it appears that the DatabasesHADR collection hasn't ran.

Fixed in 2.46.1 🎉


add USDT contract as example

material https://chat.openai.com/share/1563f588-b62b-45bb-a290-16957ae66a95

Added
Usdt Token Contract Eth


batch_sizes > 1024 are not respected by dataset.to_batches(...)

This could be user error, but in reading https://lancedb.github.io/lance/api/python/lance.html#lance.dataset.LanceDataset.to_batches, it doesn't look like there's any enforced limit. Behavior I'm seeing on lance 0.9.2 below:
for batch in dataset.to_batches(columns=["foo"], batch_size=100):
    print(len(batch)) # prints 100

for batch in dataset.to_batches(columns=["foo"], batch_size=1000):
    print(len(batch)) # prints 1000

for batch in dataset.to_batches(columns=["foo"], batch_size=10000):
    print(len(batch)) # prints 1024

This is technically in alignment with pyarrow's dataset: https://arrow.apache.org/docs/python/generated/pyarrow.dataset.Dataset.html#pyarrow.dataset.Dataset.to_batches

batch_sizeint, default 131_072
The maximum row count for scanned record batches. If scanned record batches are overflowing memory then this method can be called to reduce their size.

The batch_size parameter is "the max size of batches returned" and only slices batches if the underlying batch in the file is very large.  Lance defaults to batches of size 1024.
It looks like we have it documented as The number of rows to fetch per batch. which is misleading.  So we should at least update our docs.

gotcha - thanks for the speedy reply! Opened a PR to update the docs.


changed regex for included dashes and spaces, added filtering dashes out

Coverage decreased (-2.2%) to 74.836% when pulling abe1526f6683440d07c7d698a24b673f588a317a on UML-422-Accepting-OTP-and-LPAref-in-different-formats into 6fd9869eb69c2d8b770b9e079d11ac6e805dd1bd on master.