Which parts of TeamsJS get defined on this list?

For instance, this list describes the "location" and "media" capability, and the "TaskInfo" interface. What meets the bar to be on this list?

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

ID: ff9690f5-fa8b-98bb-d3b4-ad4ed1030114
Version Independent ID: ff9690f5-fa8b-98bb-d3b4-ad4ed1030114
Content: Microsoft Teams developer documentation- Glossary - Teams
Content Source: msteams-platform/get-started/glossary.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: surbhigupta

Hi @surbhigupta12 , could you please help here responding to the above asked query?

All key and unique concepts from the TeamsJS library will be included in the glossary. We will refrain from including method names, namespace references, and interface names unless there is a notable demand for clarification from developers through various feedback channels.


Testing of CI checks

Pull Request Test Coverage Report for Build 218

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.19%

Totals

Change from base Build 215:
0.0%

Covered Lines:
1873

Relevant Lines:
2100

💛  - Coveralls

Test cases are passing more consistently now even with actual implementation. Tests on Appveyor now seems a little inconsistent, but tests are passing consistently on Travis.


Do not set VCAP_ID stickyness cookie if value already provided by backend.

…kend.
Thanks for contributing to gorouter. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:
Do not set VCAP_ID stickyness cookie if value already provided by backend.
GoRoute would set the VCAP_ID Cookie ignoring an already present Set-Cookie Header from the backend, which results in a dublicate Set-Cookie Header.
This is important to allow the backend to change the routing of a sticky session to a different instance.

An explanation of the use cases your change solves
Rerouting indication from the backend where overwritten by gorouter. gorouter schould not set the
VCAP_ID Cookie twice if it is already present in the backend response.

Instructions to functionally test the behavior change using operator interfaces (BOSH manifest, logs, curl, and metrics)

Expected result after the change

Current result before the change

Links to any other associated PRs

[X] I have viewed signed and have submitted the Contributor License Agreement

[X] I have made this pull request to the master branch

[ ] I have run all the unit tests using bin/test

[ ] I have run CF Acceptance Tests on bosh lite

@shalako and @shubhaat Any thoughts on this?

Hi @thomasbuengener,
I think you are aware that we use VCAP_ID to support sticky sessions or session affinity in the Gorouter as described here: https://docs.cloudfoundry.org/concepts/http-routing.html#sessions. We expect backend instances to set the JSESSIONID. If the app instance returns a JSESSIONID, the CF Routing tier generates a unique VCAP_ID based on the GUID. The CF routing tier uses the VCAP_ID cookie to forward client requests to the same app instance every time.
May we know a little more about your use case where an app instance sets the VCAP_ID? Why do you want  to allow the backend to change the routing of a sticky session to a different instance?
Thanks,
Shubha

Hi Shubha,
the requirement is to modify the route from the backend by setting the sticky-cookie.
Whenever a cookie is already set by the backend,
gorouter shall not overwrite this. I thinks this generally makes sense and is the way most common loadbalancers
handler this usecase, too.
Yours,
Thomas Büngener
Software Architekt inSign
Telefon: +49 (8161) 606-17
Mobil: +49 173 21 45 032
E-Mail: thomas.buengener<EMAIL_ADDRESS>[IS2-Logo-2010-RGB-standard-60x20]  Intelligent Solution Services AG
Am Bäckeranger 2 | 85417 Marzling | www.is2.dehttps://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
[website]https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer  [xing_is2ag] https://www.xing.com/companies/is2intelligentsolutionservicesag   [facebook_is2ag] https://www.facebook.com/is2ag/   [Linkedin] https://de.linkedin.com/company/is2-intelligent-solution-services-ag   [youtube] https://www.youtube.com/user/iS2AG
Besuchen Sie uns auf unserer neuen Website >>https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
IS2 Intelligent Solution Services AG, Hauptverwaltung: Am Bäckeranger 2, 85417 Marzling;
Vorsitzender des Aufsichtsrats: Rolf Koch, Vorstand: Stephan Hämmerl, Thomas Wolf;
Sitz der Gesellschaft: Marzling; Handelsregister: HRB 145168, Amtsgericht München
Von: Shubha Anjur Tupil<EMAIL_ADDRESS>Gesendet: Dienstag, 24. Juli 2018 20:34
An: cloudfoundry/gorouter<EMAIL_ADDRESS>Cc: Thomas Büngener<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [cloudfoundry/gorouter] Do not set VCAP_ID stickyness cookie if value already provided by backend. (#220)
Hi @thomasbuengenerhttps://github.com/thomasbuengener,
I think you are aware that we use VCAP_ID to support sticky sessions or session affinity in the Gorouter as described here: https://docs.cloudfoundry.org/concepts/http-routing.html#sessions. We expect backend instances to set the JSESSIONID. If the app instance returns a JSESSIONID, the CF Routing tier generates a unique VCAP_ID based on the GUID. The CF routing tier uses the VCAP_ID cookie to forward client requests to the same app instance every time.
May we know a little more about your use case where an app instance sets the VCAP_ID? Why do you want to allow the backend to change the routing of a sticky session to a different instance?
Thanks,
Shubha
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cloudfoundry/gorouter/pull/220#issuecomment-407508300, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACcb1V-O-D5iB5JbpQJ2G13S_eQiET1oks5uJ2imgaJpZM4VHoR5.

@thomasbuengener
Hello Thomas,
Could you please tell us why you want an application instance to modify the route?

Dear fellow routers,
this can sometimes be neccesary to optimize caching in scenarios where multiple clients
access and modify the same large data instance (blob) in an stateful application, where transporting the
data between nodes may be inapropriate or neccessary for legacy reasons.
Mit freundlichen Grüßen
Thomas Büngener
Software Architekt inSign
Telefon: +49 (8161) 606-17
Mobil: +49 173 21 45 032
E-Mail: thomas.buengener<EMAIL_ADDRESS>[IS2-Logo-2010-RGB-standard-60x20]  Intelligent Solution Services AG
Am Bäckeranger 2 | 85417 Marzling | www.is2.dehttps://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
[website]https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer  [xing_is2ag] https://www.xing.com/companies/is2intelligentsolutionservicesag   [facebook_is2ag] https://www.facebook.com/is2ag/   [Linkedin] https://de.linkedin.com/company/is2-intelligent-solution-services-ag   [youtube] https://www.youtube.com/user/iS2AG
Besuchen Sie uns auf unserer neuen Website >>https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
IS2 Intelligent Solution Services AG, Hauptverwaltung: Am Bäckeranger 2, 85417 Marzling;
Vorsitzender des Aufsichtsrats: Rolf Koch, Vorstand: Stephan Hämmerl, Thomas Wolf;
Sitz der Gesellschaft: Marzling; Handelsregister: HRB 145168, Amtsgericht München
Von: Shannon Coen<EMAIL_ADDRESS>Gesendet: Donnerstag, 9. August 2018 22:38
An: cloudfoundry/gorouter<EMAIL_ADDRESS>Cc: Thomas Büngener<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [cloudfoundry/gorouter] Do not set VCAP_ID stickyness cookie if value already provided by backend. (#220)
@thomasbuengenerhttps://github.com/thomasbuengener
Hello Thomas,
Could you please tell us why you want an application instance to modify the route?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cloudfoundry/gorouter/pull/220#issuecomment-411888951, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACcb1SNgSPeGSrYi-fQDjR3mbigaJvY2ks5uPJ2hgaJpZM4VHoR5.

For this to work, an app instance would have to be aware of the guids of other instances. How do you imagine doing this?
https://docs.cloudfoundry.org/concepts/http-routing.html#sessions
Consider also that these guids change, as containers are destroyed and recreated on new hosts.

Hi Shannon,
sure, this little adjustment in gorouter is only only the smallest part oft he puzzle.
The handling oft he guids is done by the application, but outside oft he scope oft he
propsed change to gorouter.
This implementations already working fine on several different platforms.
Mit freundlichen Grüßen
Thomas Büngener
Software Architekt inSign
Telefon: +49 (8161) 606-17
Mobil: +49 173 21 45 032
E-Mail: thomas.buengener<EMAIL_ADDRESS>[IS2-Logo-2010-RGB-standard-60x20]  Intelligent Solution Services AG
Am Bäckeranger 2 | 85417 Marzling | www.is2.dehttps://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
[website]https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer  [xing_is2ag] https://www.xing.com/companies/is2intelligentsolutionservicesag   [facebook_is2ag] https://www.facebook.com/is2ag/   [Linkedin] https://de.linkedin.com/company/is2-intelligent-solution-services-ag   [youtube] https://www.youtube.com/user/iS2AG
Besuchen Sie uns auf unserer neuen Website >>https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
IS2 Intelligent Solution Services AG, Hauptverwaltung: Am Bäckeranger 2, 85417 Marzling;
Vorsitzender des Aufsichtsrats: Rolf Koch, Vorstand: Stephan Hämmerl, Thomas Wolf;
Sitz der Gesellschaft: Marzling; Handelsregister: HRB 145168, Amtsgericht München
Von: Shannon Coen<EMAIL_ADDRESS>Gesendet: Mittwoch, 15. August 2018 23:00
An: cloudfoundry/gorouter<EMAIL_ADDRESS>Cc: Thomas Büngener<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [cloudfoundry/gorouter] Do not set VCAP_ID stickyness cookie if value already provided by backend. (#220)
For this to work, an app instance would have to be aware of the guids of other instances. How do you imagine doing this?
https://docs.cloudfoundry.org/concepts/http-routing.html#sessions
Consider also that these guids change, as containers are destroyed and recreated on new hosts.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cloudfoundry/gorouter/pull/220#issuecomment-413334777, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACcb1fZE09LtiA3IuS-s3fp7UZvpnwq9ks5uRIvEgaJpZM4VHoR5.

transporting the data between nodes may be inapropriate or neccessary for legacy reasons

Do you mean that multiple instances of this application are unable to share a data store? Only one instance has access to the blob? Doesn't this represent a single point of failure?

Hi,
all nodes have access tot he data, but switching and synchronizing access might be to slow (data would need to e transfered between nodes on every single access).
This is why multiple clients should be directed tot he same node that holds the cache oft he blob data.
In case of node failure a new node will automatically selected by the loadbalancer which then will reload the data from the store.
So, no SPOF here.
Mit freundlichen Grüßen
Thomas Büngener
Software Architekt inSign
Telefon: +49 (8161) 606-17
Mobil: +49 173 21 45 032
E-Mail: thomas.buengener<EMAIL_ADDRESS>[IS2-Logo-2010-RGB-standard-60x20]  Intelligent Solution Services AG
Am Bäckeranger 2 | 85417 Marzling | www.is2.dehttps://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
[website]https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer  [xing_is2ag] https://www.xing.com/companies/is2intelligentsolutionservicesag   [facebook_is2ag] https://www.facebook.com/is2ag/   [Linkedin] https://de.linkedin.com/company/is2-intelligent-solution-services-ag   [youtube] https://www.youtube.com/user/iS2AG
Besuchen Sie uns auf unserer neuen Website >>https://www.is2.de/?utm_source=footer&utm_medium=email&utm_campaign=email_footer
IS2 Intelligent Solution Services AG, Hauptverwaltung: Am Bäckeranger 2, 85417 Marzling;
Vorsitzender des Aufsichtsrats: Rolf Koch, Vorstand: Stephan Hämmerl, Thomas Wolf;
Sitz der Gesellschaft: Marzling; Handelsregister: HRB 145168, Amtsgericht München
Von: Shannon Coen<EMAIL_ADDRESS>Gesendet: Samstag, 18. August 2018 00:14
An: cloudfoundry/gorouter<EMAIL_ADDRESS>Cc: Thomas Büngener<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [cloudfoundry/gorouter] Do not set VCAP_ID stickyness cookie if value already provided by backend. (#220)
transporting the data between nodes may be inapropriate or neccessary for legacy reasons
Do you mean that multiple instances of this application are unable to share a data store? Only one instance has access to the blob? Doesn't this represent a single point of failure?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cloudfoundry/gorouter/pull/220#issuecomment-414001141, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACcb1b4IGwyh_qFe-wHqQdfr-A-e25wdks5uR0AVgaJpZM4VHoR5.

closing for now, please reopen when you have the tests 👍


Issues found when battletesting centralized bridge

No gas prices was being specified when sending Eth transactions.
No exception handling when sending Eth transactions.
Too much intenstive polling when waiting for Eth transactions receipt.

Adding a try when calling handle_requestUpdate makes the poller keep running even if the infura node is stopped


How to use bones without node?

Anyone knows how can i use bones as standalone js for my html pages? the functions like require() etc. does not work because i want to run it in a browser.

Hey @cnkt: the functionality of bones mainly lies in working with expressjs and server side code - if you just want write a client side app, use Backbone directly.


SLD: fix invalid state error message

which claimed this happens with a remote description, not a local one

Codecov Report

Merging #23 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #23   +/-   ##
=======================================
  Coverage   91.86%   91.86%
=======================================
  Files           1        1
  Lines         774      774
=======================================
  Hits          711      711
  Misses         63       63

Impacted Files
Coverage Δ

rtcpeerconnection.js
91.86% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Second screeshot has the same Policy name as the first one

In the second screenshot the Policy name is the same as in the first screenshot. I guess it should be different.
[Enter feedback here]

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

ID: 9561a367-20d8-62e9-57e5-694bab4c0878
Version Independent ID: a7c757e0-052b-fc42-70c5-030081baa573
Content: Configure authentication session management - Azure Active Directory
Content Source: articles/active-directory/conditional-access/howto-conditional-access-session-lifetime.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@BillGatesIII
Thanks for your feedback! I have assigned this issue to the author who will investigate and update as appropriate.

Name your policies however your organization has created standards. These are just screenshots for reference. #please-close


User Login and Logout

As a User of ATT&CK Workbench, I want to be able to log in to or log out of the application.

Prior to login, I should only have access to the home page.
Once logged in, I should see my identity icon in the header and have the option to logout.

I think unauthenticated users may also want to access the documentation pages:

An individual stumbling upon the application deployed within their organization without knowing what it is may want to refer to that documentation to determine if they want to register
Said documentation may also include registration instructions.

Given that the documentation pages on Workbench simply mirror the docs/ folder of this repository, there shouldn't be any security risk to providing access to those pages to unauthenticated users.


Test Time 16

Test Time 16

@MihaiDejeu thank you for reporting this. I'll assign someone to take care of it soon.

@amihaiemil this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2020-12-24T11:16:56.380678.
Estimation here is 33 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@amihaiemil Don't forget to close this ticket before the deadline (2020-12-24T11:16:56). You are past the first half of the allowed period.

@amihaiemil Looks like you've missed the task deadline (2020-12-24T11:16:56). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@PerteGeorge this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2021-01-03T11:21:06.974370.
Estimation here is 33 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@PerteGeorge Don't forget to close this ticket before the deadline (2021-01-03T11:21:06). You are past the first half of the allowed period.

@PerteGeorge thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


[IOTDB-723] add raft log delete mechanism

The main logic for deleting raft logs is as follows:
Each server periodically(3600 seconds) triggers the operation to check the deletion of the log. If the distance between the last deletion log index and  the current maximum commited index exceeds a certain threshold, it performs the deletion operation, otherwise do nothing.
please leave your opinions, thanks

How about the raft logs in Memory(CommittedLogManager)?Is it better to make them consistent after deleting old logs?

LGTM


E: Unable to locate package https://github.com/rebootuser/LinEnum/blob/master

The title speaks for itself. I can't get LinEnum because of that. :/

What are you trying to do?

just use wget command


Blocking call in coroutine

I was trying to implement HomeMatic IP into HomeAssistant too and ran into your repo. So happy to see this.
But I think there is a problem with your implementation:
I see you are calling turn_on() inside a coroutine async_turn_on. turn_on() is a blocking call to an http request which will block the entire event loop. This will lead to errors inside your hass instance.
https://github.com/mxworm/home-assistant-custom/blob/master/switch/homematicip.py#L62
Sander.

Hi Sander,
As I'm not a python nor homeaassistant expert I would highly appreciate your help.
Ciao

@mxworm
There can be two approaches to this:

Homeassistant allows threaded implementation of a component too (see for example the philips hue implementation where there is no @asyncio coroutines used.)
Another option is to try to create an asyncio version of the library created by coreGreenberet and use that for HASS.

I prefer the second option, but that needs either forking and maintaining an async copy of the library created by coreGreenberet or adding asyncio functionality to the existing library. I am in the process of checking which option is preferrable..

@mxworm
I have a more or less working version of the async homematic implementation working:
https://github.com/sander76/homematicip-rest-api/tree/async
I have been looking at your code and we can use it as a basis for further implementation. But you are using it as a custom component. Are you planning to submit it to hass as a plugin ? In the end I think that would be great...


Fix "Form too large" exception

When a SAML user belonging to multiple (~1k) groups tries to login,
a POST to v1/token containing all the group identities is done, so cattle
can create cattle identities for these groups and generates a token for the
user. This POST was causing "Form too large" exception and not letting such
users login
https://github.com/rancher/rancher/issues/8754
https://github.com/rancher/rancher/issues/14756

LGTM except for the checkstyle failure that is causing the build to fail

@cjellick fixed checkstyle error. The current drone TD seems unrelated

LGTM


Doesn't work reject for scaling in StatefulSet.

Hello. Thanks a  million for your operator.
But i can't realize reject for sts.
I use next modrule:
apiVersion: api.kubemod.io/v1beta1
kind: ModRule
metadata:
  name: reject-sts-scale-control-clients
  namespace: redis
spec:
  type: Reject
  rejectMessage: 'More than 3 pods are not allowed, but ordered are - {{ .Target.spec.replicas }}'

  admissionOperations:
    - CREATE
    - UPDATE

  match:

    - select: '$.kind'
      matchValues:
        - 'StatefulSet'

    - select: '$.spec.replicas > 3'

And it doesn't work ( instead of the Deployment  via replicaset).

Hi @vassilvk

Do you see anything odd in KubeMod's operator logs?
No, I don't.

Did you make sure to deploy the ModRule to the correct namespace?
Yes, i did.     "namespace: redis" confirms it.

Also, are you deploying the ModRule and the StatefulSet at the same time to the same namespace?
No, I've investigated only UPDATE func via changing scale.

If so, you might want to make sure the ModRule is deployed ahead of time. You can also deploy the ModRule as a cluster-wide rule (by deploying it to namespace kubemod-system) that targets your StatefulSet namespace by setting targetNamespaceRegex. Either way, the ModRule should be there before one attempts to create/update the StatefulSet.
Shure, I'll be do it.

Also I've faced problem with "Reject" rule:  operator log writes redundant data

But does not work when changes scale in sts , I guess it has to exec UPDATE admission.

Just so I understand, the rule does reject a StatefulSet CREATE operation when the StatefulSet includes more than 3 replicas, but does not reject UPDATE to a StatefulSet whose replicas are higher than 3? You said "I've investigated only UPDATE func via changing scale" - can you please elaborate? Did you use kubectl scale, kubectl apply, kubectl edit, or kubectl patch? Or is the change made by an in-cluster operator performing an update against the StatefulSet?
In addition, looking at the log messages, it seems like the operator does reject (or attempts to reject) UPDATE operations, however, the target resource is not StatefulSet - it is ReplicaSet.
Something seems off here. Unlike Deployments, StatefulSets do not use ReplicaSets to scale their pods - the StatefulSet controller performs pod scaling directly, so I'm wondering, what is this ReplicaSet about...

:( No one kind hadn't work

Also I faced problems w non-working probes,/metrics - may be necessary rebuild container using any extra options?

Not sure what you mean by this. Are you having trouble installing/running the kubemod operator?

Regarding:

:( No one variant hadn't worked.

Hopefully I'll have some time soon to take a closer look and try to reproduce.

Regarding:

:( No one variant hadn't worked.

Hopefully I'll have some time soon to take a closer look and try to reproduce.

That's great

Happy NY


ReferenceError: window is not defined

package.json
{
  "name": "",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "build": "webpack --mode=production",
    "dev": "webpack-dev-server --mode=development"
  },
  "repository": {
    "type": "git",
    "url": "https://gitee.com/yangjiedage/checheHomepage.git"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "css-loader": "^1.0.0",
    "file-loader": "^2.0.0",
    "glob": "^7.1.3",
    "glob-all": "^3.1.0",
    "html-loader": "^0.5.5",
    "html-webpack-plugin": "^3.2.0",
    "image-webpack-loader": "^4.3.1",
    "mini-css-extract-plugin": "^0.4.3",
    "purify-css": "^1.2.5",
    "purifycss-webpack": "^0.7.0",
    "style-loader": "^0.23.0",
    "uglifyjs-webpack-plugin": "^2.0.1",
    "url-loader": "^1.1.1",
    "webpack": "^4.20.2",
    "webpack-cli": "^3.1.1",
    "webpack-dev-server": "^3.1.9"
  },
  "dependencies": {
    "popper.js": "^1.14.4"
  },
  "description": ""
}

webpack.config.js
const path = require('path')
const devMode = process.env.NODE_ENV !== 'production'
const HtmWebpackPlugin = require('html-webpack-plugin')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const glob = require('glob-all')
const PurifyCssPlugin = require('purifycss-webpack')
const webpack = require('webpack')
const UglifyJsPlugin = require('uglifyjs-webpack-plugin')

module.exports = {
  entry: {
    app: './src/app.js'
  },

  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: devMode ? '[name].js' : '[name].[hash:5].js',
  },
  resolve: {
    alias: {
      jquery$: path.resolve(__dirname, 'js/jquery-2.0.2.js')
    }
  },

  optimization: {
    minimizer: [
      new UglifyJsPlugin({
        cache: true,
        parallel: true
      })
    ]
  },
  module: {
    rules: [
      {
        test: /\.css$/,
        use: [
          // devMode ? 'style-loader' : MiniCssExtractPlugin.loader,
          MiniCssExtractPlugin.loader,
         'css-loader'
        ]
      },

      {
        test: /\.(png|jpg|jpeg|gif)$/,
        use: [
          {
            loader: 'url-loader',
            options: {
              name: '[name]-[hash:5].[ext]',
              limit: 10000,
              outputPath: 'assets/imgs'
            }
          },
          {
            loader: 'image-webpack-loader',
            options: {
              mozjpeg: {
                progressive: true,
                quality: 65
              },
              // optipng.enabled: false will disable optipng
              optipng: {
                enabled: false,
              },
              pngquant: {
                quality: '65-90',
                speed: 4
              },
              gifsicle: {
                interlaced: false,
              },
              // the webp option will enable WEBP
              webp: {
                quality: 75
              }
            }
          }
        ]
      },

      {
        test: /\.(eot|woff2?|ttf|otf|svg)$/,
        use: [
          {
            loader: 'url-loader',
            options: {
              limit: 5000,
              name: '[name]-[hash:5].[ext]',
              outputPath: 'assets/fonts'
            }
          }
        ]
      },

      {
        test: /\.html$/,
        use: [
          {
            loader: 'html-loader',
            options: {
              attrs: ['img:src', 'script:src', 'link:href']
            }
          }
        ]
      }
    ]
  },
  plugins: [
    new PurifyCssPlugin({
      paths: glob.sync([
        path.join(__dirname, './template.html'),
        path.join(__dirname, './src/*.js')
      ])
    }),
    new webpack.ProvidePlugin({
      $: 'jquery',
      jQuery: 'jquery'
    }),
    new HtmWebpackPlugin({
      filename: 'index.html',
      template: 'template.html'
    }),
    new MiniCssExtractPlugin({
      filename: devMode ? '[name].css' : '[name].[hash:5].css',
      chunkFilename: devMode ? '[id].css' : '[id].[hash:5].css'
    })
  ]
}

getting errors
(node:96841) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
Hash: 8f60d876eb4cb9635979
Version: webpack 4.20.2
Time: 8994ms
Built at: 2018-09-28 14:04:48
                                       Asset      Size  Chunks                    Chunk Names
 assets/fonts/fontawesome-webfont-c8ddf.woff  88.3 KiB          [emitted]
                 assets/imgs/car-1-d9487.jpg  46.9 KiB          [emitted]
                 assets/imgs/car-3-37c7c.jpg    34 KiB          [emitted]
                 assets/imgs/car-4-8b8fd.jpg  34.9 KiB          [emitted]
                 assets/imgs/car-5-bde1b.jpg   446 KiB          [emitted]  [big]
                 assets/imgs/car-6-c4928.jpg  59.5 KiB          [emitted]
assets/fonts/fontawesome-webfont-e6cf7.woff2  70.2 KiB          [emitted]
  assets/fonts/fontawesome-webfont-25a32.eot  74.7 KiB          [emitted]
                 assets/imgs/car-2-6cff3.jpg   235 KiB          [emitted]
            assets/imgs/ajaxloader-e9623.gif  28.6 KiB          [emitted]
  assets/fonts/fontawesome-webfont-1dc35.ttf   149 KiB          [emitted]
  assets/fonts/fontawesome-webfont-d7c63.svg   382 KiB          [emitted]  [big]
                  assets/imgs/bg-5-53cec.jpg  30.7 KiB          [emitted]
                  assets/imgs/bg-4-ca2e9.jpg   202 KiB          [emitted]
                                     app.css  56.6 KiB       0  [emitted]         app
                                      app.js  84.2 KiB       0  [emitted]         app
                                  index.html  1.16 KiB          [emitted]
Entrypoint app = app.css app.js
[0] ./src/app.js 1.84 KiB {0} [built]
[1] ./js/jquery-2.0.2.js 237 KiB {0} [built]
[2] (webpack)/buildin/module.js 519 bytes {0} [built]
[3] ./css/styles.css 39 bytes {0} [built]
    + 4 hidden modules

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  assets/imgs/car-5-bde1b.jpg (446 KiB)
  assets/fonts/fontawesome-webfont-d7c63.svg (382 KiB)

WARNING in webpack performance recommendations:
You can limit the size of your bundles by using import() or require
ERROR in   Error: /Users/jason.yang/Desktop/cheche-homepage/template.html:8934
  })( window );
      ^
  ReferenceError: window is not defined

  - template.html:8934 Object.<anonymous>
    /Users/jason.yang/Desktop/cheche-homepage/template.html:8934:5

  - template.html:8935 Object.module.exports
    /Users/jason.yang/Desktop/cheche-homepage/template.html:8935:30

  - template.html:21 __webpack_require__
    /Users/jason.yang/Desktop/cheche-homepage/template.html:21:30

  - template.html:8953 Object.module.exports
    /Users/jason.yang/Desktop/cheche-homepage/template.html:8953:18173

  - template.html:21 __webpack_require__
    /Users/jason.yang/Desktop/cheche-homepage/template.html:21:30

  - template.html:85 core_strundefined
    /Users/jason.yang/Desktop/cheche-homepage/template.html:85:18

  - template.html:88
    /Users/jason.yang/Desktop/cheche-homepage/template.html:88:10

  - index.js:247 HtmlWebpackPlugin.evaluateCompilationResult
    [cheche-homepage]/[html-webpack-plugin]/index.js:247:28

  - index.js:161 Promise.resolve.then.then.then.compiledTemplate
    [cheche-homepage]/[html-webpack-plugin]/index.js:161:23

Any ideas?

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.

webpack runs in a Node environment, add a check to your code: https://github.com/webpack/webpack/issues/7112#issuecomment-383866094

I encourage you to ask your question on StackOverflow instead. We try to use the issue tracker for bug reports and feature requests, as well as some discussions, but this appears to be a very localized question.
I’m closing for these reasons.


Fixed dimension escaping and bug setting dynamic widget labels

When implementing improved widget value formatting in #562 I didn't handle the dynamic widget case causing some issues as described in #571 and partially fixed in #572. I've also included another fix for escaping dimension names that was overlooked previously and partially fixed in #574.

Ready to merge.

Good to fill in holes in the validation. Merging.


⚠ ClamAV has degraded performance

In f4f19a8, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 193 ms

Resolved: ClamAV performance has improved in 70c2198.


Update Pro Drivers to 2024.03.0

Use the latest version of the Professional Drivers

Is there a CentOS 7 release for this? I noticed those builds are failing for us.
There is. The filename changed. I popped on a commit: s/el7/el/.


End support for Ruby 1.9.3 and Rails 3

Ends support for the now unsupported Ruby 1.9.3 and the semi-supported
("severe" security fixes only) Rails 3.2.
This is in readiness for our support of Rails 5, and also to decrease the
support burden for increasingly uncommon configurations.

But even rails 4 supports 1.9.3 as minimum version :cry:

@isqad88 Internally, this project hasn't changed much over the years and given we're a pretty lightweight dependency, I suspect you could happily use the current released version 0.3.5 if you wanted to support that particular configuration.

@pxlpnk Any thoughts before I merge?

We are not trying to rely on 1.9.3 features. The code in general is more focused on rails than on ruby.
I am even pretty sure that lograge runs with all 1.9 rubies. However to slim down our dependencies we should move forward and leave 1.9.3 behind. :wave: :sob:


ES6 remap

Fix  https://github.com/sourcelair/xterm.js/issues/158
Slice code in ES6 module.
Compositionhelper, viewport & eventemitter are proper ES6 classes.
The Terminal classe is big, yet wcwidth and escapeSequence have been sliced too, this increase overall readability and testing scope. ( slicing can be done on other parts of Terminal class, if desired)
Tests are fine
Documentation generation is fine
new pm task

npm run build:dist to build standalone version ( exactly same signature as current version) in /dist folder

Strongly simplify demo/app.js (server side)
no need for external fetch, just use WS socket all along
Strongly simplify demo/index.html / demo/main.js
Strongly simplify addon design & loading
in package.json
node_modules/.bin is in npm run path, so no need to set it

@parisk  , it it possible for you to create a v2.0 branch ? I think my PR will be easier to merge in a dedicated branch (not in master), for now.

@parisk let's pause all commits on master until we merge one of the fix for #158, merging will be a nightmare if any commits go in. I'm working on the ts solution now.

I'v also fixed the 'document' isolation (spawing new Terminal in nodejs is no longer an issue), no "hacks" are needed anymore here

@Tyriar yep. Let's not merge anything until we sort out the build system.
Adding labels to all PRs.

FYI, per ES6 out-of the box compatiblity with Typescript, i've successfully tested this branch against Visual Studio Code.
Note that VSCode is an electron app and just "require('xterm')", hence, works with the RAW es6 files of this branch (not the /dist/ folder !!)

I just understood that @Tyriar works for MS and  :laughing:  !
I LOVE VISUAL STUDIO CODE :heart:

@parisk  Ok, last bug was epic.
I just created a sourcelair account, imported xterm.js project and got everything working (until this binding bug)
This was so meta, fixing xterm.js in a sourcelair / xterm.js (with a vm containers everywhere)

@131 :heart:

@131 You removed the additional side communication for resizing from the demo. Your replacement does a string vs. buffer (binary data) distinction instead. Will this work for all browser engines?
Also the ASCII limitation could be lifted with a real UTF-8 conversion (a pity TextEncoder is in such an early stage, would make it usable for arbitrary jsonified content in a reasonable runtime).

for the WS-only channel (as i dropped the REST process), binary distinction will work on all browsers yes.
A real UTF-8 conversion is "easily" atteignable using new Buffer(JSON.stringify(stuff), 'utf-8'), yet, i didn't want to increase the generated file with browserify/buffer polyfill.

Sweet, than this is the real solution for the problem. We had a discussion about it before here #171 and ended up with the additional communication approach.
Yeah no need for any bloatware in the demo, it gets the job done.

While I lean more towards TypeScript now that I took a deeper look at it and @Tyriar's PR, I would like to make one main comment here: could we leave demo refactoring out of this, in order to reduce to-be-reviewed code?
Also may I ask we did you decide to introduce the index.js files?

Would I help if I moved the addons directory into src in the meantime (#250)?

@parisk When they're named index.js they can be included in node using require('./addons/fit'') (vs require(./addons/fit/fit), this is probably the reason for the switch. It would look a bit funny in a script tag though <script src="addons/fit/index.js"></script>

Im targetting a sane loading API
for user usin umd modules (and browserify/ webpack) just
var Terminal = require('xterm')
// aplly addon using
require('xtem/addon/fit)(Terminal)
And for user using the /dist edition
< script src=xterm/xterm.js/>

Im targetting a sane loading API
for user usin umd modules (and browserify/ webpack) just
(see demo/main.js)
var Terminal = require('xterm')
// aplly addon using
require('xtem/addon/fit)(Terminal)

And for user using the /dist edition
(see dist/index.htmljs)
< script src=xterm/xterm.js/>
<script src=xterm/addon/fit.js->

Please wait for a minute. I think I am preparing a quite simpler PR.

Sorry i'vnt seen your message.
(now waiting)

ES6 conversion is complete, xterm.js is fully ES6 AND did not even loose commit/blame/history (no indentation change)

It seems that when I was referring to a minute, I meant 3 hours...
I started getting scary with the magnitude of these PRs, so I started a new smaller one (strictly less than 200 additions), in order to move things forward gradually, instead of all at a time.
Could you please take a look at #251?

Sorry about being late to reply here but my main issues with this PR were:

difficulty in reviewing (it included thousands of additions and removals)
introduction of additional logic than the one described in #158

Despite that I would like to thank you very much for your contribution as it motivated me to open #251!
Please feel free to open up an issue to change the demo protocol if you would like to take over this task 😊 .


Window resize results in black screen

Its a graphics driver dependant bug. So far it has only been reported on windows. Whenever you resize the window manually or by setting another MODE all uploaded bitmaps and the screencontent gets lost.

At least the bitmaps are no longer lost on resize. "Fixed" in v0.4.0.


Add filter-lang to query body to support changes in pgstac 4.5.

Ref https://github.com/stac-utils/stac-fastapi/issues/335

🤔 not sure what changed in pgstac but CI fails, it's not related to your PR so I'll merge 🙏


Pods are waiting for grace-period before exiting

Discovered when looking at #678, pods are waiting the full 90 seconds of grace-period before ending.

Found the problem and have a PR that addresses it. This has uncovered a variety of CI failures that I'm working through.


-l 0 takes 0 messages, not all messages from the group

I tried running "telegram-messages-dump --chat="----" -p +3----- -e csv -l 0" and it says me

Dumping 0 messages into "telegram_--aDeZaBA.log" file ...
Merging results into an output file.
INFO:Writing a new metadata file.
0 messages were successfully written in the resulting file. Done!

Hi,
This problem is supposed to be fixed in v0.3.5


refact: align the starlark interface

Description

the implementation of install.system_packages is apt-get, should we change to install.apt_packages? Also, we have config.apt_source, not config.system_source.
runtime.expose(envd_port, host_port), io.copy(src, dest), io.mount(src, dest), should we align the term?
config.pip_index(mode, url, extra_url), config.apt_source(mode, source), if mode is not supported yet, should move this parameter to the last one instead of the first one?

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

I totally agree.
Ref https://github.com/tensorchord/envd/issues/149
/cc @Xuanwo @VoVAllen

the implementation of install.system_packages is apt-get, should we change to install.apt_packages?

Agree.

2. runtime.expose(envd_port, host_port), io.copy(src, dest), io.mount(src, dest), should we align the term?

Agree.

3. config.pip_index(mode, url, extra_url), config.apt_source(mode, source), if mode is not supported yet, should move this parameter to the last one instead of the first one?

What does mode mean?

What does mode mean?

If mode=auto, envd will try to detect the location and choose the nearest mirror.
This hasn't been implemented yet.

Not sure whether we should support other package management or not. If yes, maybe keep install.system_packages and have different implementation below may be a good idea

The main concern is GPU support. So far as I know, only Ubuntu has good Nvidia support for deep learning.

This hasn't been implemented yet.

I prefer to remove it.

This hasn't been implemented yet.

I prefer to remove it.

SGTM.

io.mount -> runtime.mount


[Key Vault] Raise useful error when KeyReleasePolicy is incorrectly created

The KeyReleasePolicy model expects an encoded_policy parameter as bytes. If a string is passed instead, no error is raised -- but when the created policy is provided to a create_key request, the service returns an error suggesting that the policy was never provided (see https://github.com/Azure/azure-sdk-for-python/issues/29945):
azure.core.exceptions.HttpResponseError: (BadParameter) AKV.SKR.1004: Exportable keys must have release policy.

This doesn't make the cause of the failure obvious at all. Though input validation is generally avoided, we should raise an error when a string is provided to the KeyReleasePolicy constructor so that users have an easier way to identify the problem.

Not applicable to the Go SDK. Validation should happen on the server side.


Bluetooth: shell: A2DP: fix compiling issues

Bluetooth: fix compiling issue when either A2DP SRC or SNK are not en…
Some of the A2DP interfaces are not defined if the corresponding feature is not enabled, and therefore shall not be initialized. This patchs include the interfaces/variables by the configurations to go through the compiling stage.

@gzh-terry thanks for the pull request! You'll need to fix the Compliance Check issues related to your commit message before this can be merged. In particular you'll need to fix your git author information to follow the format "Firstname Lastname ".  You'll also need to shorten the commit message lines according to what you see in in the Compliance check logs.

@gzh-terry thanks for the pull request! You'll need to fix the Compliance Check issues related to your commit message before this can be merged. In particular you'll need to fix your git author information to follow the format "Firstname Lastname ".  You'll also need to shorten the commit message lines according to what you see in in the Compliance check logs.

@jhedbergThanks for your prompt reply. I fixed the name and commit message issue.

Hi @lylezhu2012 , are all progress done for this commit? I saw the checks are passed, is there any thing to do at this stage?
This is my first time adding codes here so I'm not very familier with the workflow.
Thanks in advance.
Best regards,
Zihao

Hi @lylezhu2012 , are all progress done for this commit? I saw the checks are passed, is there any thing to do at this stage? This is my first time adding codes here so I'm not very familier with the workflow. Thanks in advance.
Best regards, Zihao

I didn't find anything else that needed to be done.

Hi @lylezhu2012 , are all progress done for this commit? I saw the checks are passed, is there any thing to do at this stage? This is my first time adding codes here so I'm not very familier with the workflow. Thanks in advance.
Best regards, Zihao

I didn't find anything else that needed to be done.

Hi @lylezhu2012 ,
So I just wait someone to merge this commit?
How long does it generally takes?
Thanks,
Zihao

@lylezhu2012 To merge this we still need a proper bug report, as the release is still ongoing.
When you have opened that bug report, add a "Fixes #bug-report-number" to the main text of this PR.

@lylezhu2012 To merge this we still need a proper bug report, as the release is still ongoing. When you have opened that bug report, add a "Fixes #bug-report-number" to the main text of this PR.

Sure.

Sure. Whether "Fixes #bug-report-number" needs to be added into commit of this PR?

It's enough to add it to the PR description


Crashes when reading OTIO file with SerializableCollection

If Raven is given an OTIO file with a top-level object that isn't a Timeline, it crashes. The most common case of this is an OTIO file with a SerializableCollection containing multiple timelines.
At the very least, it should give the user a helpful error message instead of crashing.
Even better it could present each different type of OTIO object in a reasonable manner. For SerializableCollection, maybe tabs for each item. For other types like MediaReference, Clip, etc. it could just show the JSON and Inspector without the timeline view.

Here's an example of a case where it would be useful to view a SerializableCollection: https://github.com/AcademySoftwareFoundation/OpenTimelineIO/issues/1687


fix!: use prefixing conventions for enums

This changes all enums to introduce a _UNKNOWN = 0 variant to make it work well with the pb-json serializer.
Release-As: 0.29.0

This changes all enums to introduce a _UNKNOWN = 0 variant to make it work well with the pb-json serializer.
Release-As: 0.29.0


⚠ Bofrost.be has degraded performance

In b2bd97b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1383 ms

Resolved: Bofrost.be performance has improved in 3d0ee3b.


Cupcake website page creation - Help/FAQ page

User Story

As an IBM.com page creator

I need to: know where to find the answers for the most asked questions

so that I can: get help efficiently.

Additional information

The FAQ page on the Carbon Design website can be viewed here.
The FAQ page on the current v19a website can be viewed here.
We need to do adopter research to see what questions our adopters have for the Cupcake website. This task also might be for v1.1 instead of v1.0.

Task

Collaborate with Wonil for the content creation.

Acceptance criteria

[ ] Content and design published with markdowns.
[ ] Content and design reviewed with Wonil.
[ ] Content and design accepted by Wonil and Linda.

Note: What is the difference between Component and Pattern?


DECCOLM escape sequence doesn't work

Your Windows build number:

Microsoft Windows [Version 10.0.16299.371]

What you're doing and what's happening:

I'm trying to switch between 80 and 132 columns with the DECCOLM escape sequence (ESC [ ? 3 h), and although it clears the screen and resets the cursor position, it appears to have no effect on the actual width of the screen. This is my test case to enable 132 columns:
printf "\e[?3h"

After poking around in the code a bit, I noticed there is a test at the start of the AdaptDispatch::SetColumns method, which stops the call from have any effect if the member variable at offset 30h is false (which it is). If I manually set that value to true then the call works.
I thought this might mean the DECCOLM functionality was disabled by default (as it is in XTerm), but I couldn't see any option in the console properties that would enable it, and Windows doesn't seem to support the escape sequence that XTerm uses to enable it (ESC [ ? 40 h).
I should also mention that even when the SetColumn call is working, it doesn't actually function as I would it expect it to. Both XTerm and Gnome Terminal resize the actual window when the DECCOLM mode is toggled, but the Windows console just alters the buffer width, leaving the window size unchanged. Having those two widths out of sync introduces a whole host of other problems.

What's wrong / what should be happening instead:

When the DECCOLM mode is set, I'd expect the screen width to change to 132. When it is reset, I'd expect the screen width to change to 80.

You're right, that functionality is actually disabled right now. I can't remember what at the moment, but we had to disable the resizing, and I added a backlog task to make it into a real setting. Only thing really stopping me is the fact that the current settings UI makes it fairly hard to another property.
For m records, this is MSFT:10086990
Thanks for calling out that it only changes the buffer, not the viewport, that'll be important to fix when I get to that.

Instead of worrying about getting an option added to the settings, could we not just implement the escape sequence I mentioned above that XTerm uses (ESC [ ? 40 h)? I've had a look at the code for this and it looks like it's an easy fix. The _fIsSetColumnsEnabled flag is already there, so it just needs a new method to set it, and a call from the _PrivateModeParamsHelper method to trigger it. As far as I can tell, you've already fixed whatever the problem was with the viewport not being sized.
And once this escape sequence is supported, a bunch of the 132 column tests in Vttest will immediately start working (or at least working better), because Vttest enables this option on startup - it has to for XTerm to work.
So what do you think? Should I submit a PR for this, or do you have other plans for how you want to handle it?

Good news! This was released for the in-box console with insider build 18945!


cargo dist init in new js project gives strange prompts

repro:

add a dist-workspace toml to a js project
run cargo-dist init

ag_dubs@Ashleys-MBP-2 workers-sdk % vi dist-workspace.toml
ag_dubs@Ashleys-MBP-2 workers-sdk % cargo dist init
let's setup your cargo-dist config...

? looks like you deleted the cargo-dist-version key, add it back?
    this is the version of cargo-dist your releases should use
    (you're currently running 0.21.0) (y/n) › yes

Wow I must've glazed over this every time -- yeah there's no reason for us to ever prompt for this. We should just do it.


feat: improved error management

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[X] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Small Improved to error managment, for more security.
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes (if not applicable, please state why)

LGTM, just did a small change. Good work! 💚


Add feature to create a hash

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Working on feature.
https://github.com/ryansmith98/hash-generator/tree/feature-create-hash

Feature complete.


Not connecting to the server and getting stuck at connecting state only

Describe the bug
I am using it since last 2 years but today I am not able to use it and it got stuck at connecting state only. I am using latest version of win-acme
To Reproduce

Run with command line with administrator mode
Navigate to win-acme.exe and run it

Expected behavior
It should work without any issues
Log
Please add any available log output. You may copy it from the console window, get it from the Windows Event Viewer, or the log files on disk, which can typically be found in a sub folder of %programdata%\win-acme.

Platform:

OS: windows 2019
Version: 64 bit

It is working fine. The issue is from my side.


New Font Suggestion (Comic Sans)

Issue Type: Feature Request
Hi VSC team !
I recently had a dream of a world where I could code in Comic Sans MS, and talked about that vision on Twitter where your Twitter account agreed that it could be an interesting addition!
I am now following up on that tweet and officially submitting this Feature Request for Comic Sans to be one of the available fonts for VSC.
Hoping to you'll consider my request !
Cheers,
Jibril (@jibdraws)
VS Code version: Code 1.56.2 (054a9295330880ed74ceaedda236253b4f39a335, 2021-05-12T17:13:13.157Z)
OS version: Windows_NT x64 6.3.9600
Fetching remote diagnostics for 'SSH' failed.

@Djbrl The Comic Code font by Toshi Omagari might be interesting for you. An Open Source alternative is Comic Mono.

Awesome thank you!!
Le ven. 11 juin 2021 à 10:57 AM, Gérard Mathiuet @.***>
a écrit :

@Djbrl https://github.com/Djbrl The Comic Code
https://www.myfonts.com/fonts/tabular-type-foundry/comic-code font by Toshi
Omagari https://tosche.net/fonts/comic-code might be interesting for
you. An Open Source alternative is Comic Mono
https://dtinth.github.io/comic-mono-font/.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/125975#issuecomment-859403000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG56PFF7IGOHZY75E24NDZ3TSHFYZANCNFSM46PPITZA
.


Confidence scores for Body Tracking Joints

Most 2D Pose Estimation models output a confidence score (0-1.0) for each joint, in addition to their XY position. This allows applications built on top of the model to gracefully handle situations like occluded joints.
Could we see this added to the Tracking SDK?

Thanks for the feedback. The team has had intense debates on whether to expose a joint confidence. Assuming you had a joint confidence how would you make use of it in your application? How would it be reflected in the user experience?

My team is also very interested on have confidence score or something similar for each joint not only for joint position or if it is occluded or not but also from the rotation perspective. For us is very important to know if we can trust or not in rotation data to determinate if we need to add some corrections to rotations for example.

@qm13
We are trying to build setup a multi kinect system in a room with several things that can occlude parts of the bodies but when we use multiple cameras there are at least one or two that could see the body without occlusion. Our goal is to fuse the joint positions from the different kinects to get a fused skeleton. It would be very helpful to have a confidence per joint per Kinect for that which will affect the weighting for this joints position in the data fusion

@qm13 here is an use case: I'd like to overlay the user's joint with virtual object. Let's say I want to put a ball of fire in the user's hand on screen. Let's forget for a moment that hands are not tracked (yet). If the user moves his/her hand behind the body, the ball of fire should disappear. It would be easy to do that, if there were tracking states or confidence scores. Without this feature, one should guess whether the hand is visible or not.

@qm13 - This could also help provide a workaround for issues such as #738 where developers could filter out obvious inaccurate positions by some combination of the confidence score and velocity (ie, joint position 'moved' 1 meter within 1 frame. )

Pretty much every application of pose estimation would benefit from joint confidence scores. Even a simple skeletal visualization looks odd at the moment because of the inhuman poses the SDK estimates when joints are occluded, instead of just hiding them. Another example is form analysis of an athlete during an exercise. If a joint has low confidence, we'd prefer to ask the athlete to change positions (remove occlusions) rather than present nonsensical feedback to them.
Hope something can be put together soon, as we are having to explore alternative models that use the kinect depth data. On that note, hope it's not too rude to ask the community here whether they have found any good alternatives? For instances, has anyone tried this one: https://github.com/lmb-freiburg/rgbd-pose3d @billpottle @rfilkov @RoseFlunder
Thanks

@hmexx I haven't looked for alternatives that use depth data yet. The current system still uses the kinect v2 which has a confidence value. At the moment I am still working on replacing the kinects v2 with azure kinects and integrate them in our ROS environment. Therefore I did the some work on the azure kinect ROS package (i.e. added body tracking data publishing). However a colleague mentioned we could compare the results to open pose, which doens't use depth data, but has a 3D pose estimation for multi view (we use four kinects).

The team has debated internally for some time on whether to expose some form of joint confidence. We are pleased many in the community have asked for joint confidence and explained your use cases. Thank you.
We are proposing to provide a joint confidence indicator for each joint. The indicator has one of four values:
CONFIDENCE_HIGH - high confidence in joint pose
CONFIDENCE_MEDIUM - medium confidence in joint pose
CONFIDENCE_LOW - not observed (likely due to occlusion), predicted joint pose
UNSUPPORTED - joint out of range (too far from depth camera).
We are specifically NOT exposing a joint numerical weight (0 - 1). Weights are not consistent between model adjustments and training. We believe relying on a numerical weight will lead to backward compatibility problems.
We look forward to your feedback.
Regards
Azure KInect Body Tracking team

Thank you for the update. This will be very helpful in my application.

A 3/4 tier confidence score will probably be sufficient for a majority of
use cases, although I m sure there are some cases where a full range (0-1)
might yield some small benefits as well.
I’m happy with the proposal in any case and look forward to seeing it
implemented. Any ideas on how much work it is and how long it will take?
Thanks for listening.
On Tue, 24 Sep 2019 at 18:14, Stephan Mävers<EMAIL_ADDRESS>wrote:

Thank you for the update. This will be very helpful in my application.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/734?email_source=notifications&email_token=AA23NYWEKKT5WUCE7GKBFCDQLJDHLA5CNFSM4IUFZWSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7PDTKA#issuecomment-534657448,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA23NYXFAILVPWR5OTPAIS3QLJDHLANCNFSM4IUFZWSA
.

Sound great for us too.
Thank you @qm13 for the feedback.
It could be useful to explain the differences between High and Medium confidence (Low = not visible, it's clear).
Regards

Such an indicator would indeed perfectly fit my needs. Thanks for listening to our feedback!

Sounds great! It would be fairly easy to convert these levels to confidence score. As to me, only the lowest confidence level should have a consistent name, something like CONFIDENCE_NONE instead of UNSUPPORTED. But this is a cosmetic issue.
@qm13 Could you please explain (maybe with a simple example), what would be the difference between the high and medium joint confidence? The other two levels are pretty clear.

Thank you for the prompt feedback. What is the difference between HIGH and MEDIUM you ask? We have an implementation of the API that we are currently evaluating against the key performance indicators we use to measure algorithmic improvement. Once this analysis is complete the intent is to provide the developer community with a defined statistical cut off between MEDIUM and HIGH. Stay tuned.

@RoseFlunder @qm13 I am a researcher from the Microsoft skeleton tracking team. Internally, we developed the 3D skeleton fused system for multiple cameras using detection weights. Depending on my experiences, the confidence scores from 2D DNN output is not very dependable. So we come with another solution. The scores come out of  a combination of multiple factors, mostly influenced by 3D geometry.

Each joint has a intrinsic given score from 0~1. joints such as shoulder, hip are more stable than ears, eyes thus getting  a higher score.

The relative orientation of the skeleton to the camera. If the camera see more of the side view of the body, the score is low and vice versa.

The distance of the skeleton to the camera. closer--->higher score

We are in the process of polishing the code and will release it if approved.

@rbteyedeng
Thats sounds great and I want to follow the same approach, using distance + orientation to the camera as additional factors. So I am looking forward to your code.
But I the confidence indicator @qm13 mentioned will help a lot when some joints are just occluded for certain cameras and therefore the position is just kind of guessed.
In my scenario there will be multiple persons which can partly occlude each other for certain cameras.
Moreover there will be other things that can occlude joints like a bed or a wheelchair.
So I am planning to exclude joint positions (weighting factor 0) if the confidence value @qm13 proposed is UNSUPPORTED or CONFIDENCE_LOW.

Released in v0.9.4

@qm13 @RoseFlunder I have a question about the body tracking sdk. Can it be used in raspberry pi 4? I want to obtain the skeleton data in system of raspberry pi4 + ros + azure kinect. Looking forward to your reply.

@Michael-robo13 i am no member of the Microsoft team but as far as I know the Body Tracking SDK is dependant on a Deep Neural Network thats using CUDA. So you need a NVidia GPU which the Raspi does not have.


Tune STOMP.js WebSocket heartbeat intervals?

Hello there,
Just figured out that homebridge-flexom, which relies on flexom-lib, sends/receives frequent pings/pongs from the Hemis WS endpoint. Currently the interval for both c2s and s2s are set to 5s.
Also, the reconnect delay is set to 100ms, which I'm afraid could trigger a flood of connection attempts if the WS server goes down for a few seconds. Which could lead to the target WS server implementing restrictive rate-limits if there are too many homebridge-flexom clients flooding when it goes back online.
Ref: https://github.com/rsauget/flexom-lib/blob/master/src/hemis/ws.ts#L36
Is that necessary? Could all intervals be made larger?
Here's what I'd suggest, based on working w/ WS servers in different networking environments (eg. w/ restrictive NATs killing long-running TCP connections that do not heartbeat frequently-enough):
    reconnectDelay: 1000,
    heartbeatIncoming: 20000,
    heartbeatOutgoing: 20000,

This changes reconnectDelay from 100ms to 1s, heartbeatOutgoing  + heartbeatIncoming from 5s to 20s.

Thanks @valeriansaliou, I don't have your experience using websockets, so I'm gonna trust you on this one (I also went through some docs & articles and it seems sensible) 👍


Add pool creation preview

When creating a pool we should show some information about the poll status and what is the expected results;

Slippage: tokens to be used between:

Depositing: 0.8 ~ 1ETH : calculates on the front end
Depositing: 1800 ~ 2000DAI: calculates on the front end
where the second value is the value inputted by the user and the first one is the tolerance;
Estimated LP Tokens: 0.8 ~ 2 LP: this value could be returned by the contract

ping: @kallemoen

Designs can be found here: https://miro.com/app/board/uXjVOynDXW4=/
@luizstacio Waiting on feedback


Add linkable support for firefly://data URIs

We've been using/encouraging a pattern for NFT URIs that follows a URI scheme of firefly://data/<data-hash> to identify that the NFT metadata is contained in a private FireFly data item.
Assuming we do want to commit to this as a generally supported pattern, we could add link support in the UI (also assuming that token URIs continue to show up in more places), so that these links can be clicked to take you to the data item.

where you want this link to be added ?
I can work on this issue


Remove asCallback / nodeify methods from docs

asCallback and nodeify were removed in v2, but these references still remain in the documentation.

Coverage remained the same at 97.127% when pulling 288150ae1e7a224742f676b36b3f403b8ac8d766 on studiozeffa:ascallback-nodeify-docs into 218052ce7e24131653bc3787ebdae78420a9f963 on Vincit:master.

Thank you!


AST,Basic: update support for process execution on Windows

Implement process launching on Windows to support macros.  Prefer to use
the LLVM types wherever possible.  The pipes are converted into file
descriptors as the types are internal to the process.  This allows us to
have similar paths on both sides and avoid having to drag in Windows.h
for the definition of HANDLE.  This is the core missing functionality
for Windows to support macros.

CC: @DougGregor @rintaro @bnbarham

@swift-ci please test

@swift-ci please test

@swift-ci please test


.gitignore test.html

test.html is a handy file to have around for testing the polyfill manually but shouldn't be checked into the repository. This change saves having to worry about it when doing a git add -A.

Perhaps it would make sense to have a skeleton test.html file in the repository so (a) this .gitignore line makes sense in new checkouts and (b) people have a framework to start with that takes care of any boilerplate that might be involved.

Turns out that's not a capability of .gitignore files. Files checked into the repo are ignored in .gitignore (as in the instruction to ignore them is ignored).

lgtm


Can you hack YacineTv_V3.apk with api http://ver3.yacinelive.com?

How did u hack Yacine TV?

by reversing the yacine tv native lib to get the xor key.


Update when the skeleton skin is changed.

Posted for posterity.
Will update the issue when the fix is verified.
Verified.

Thanks!


issue found on: stapi/api_impl.go:311:1: combine parameters types

an issue has been detected in source code: restapi/api_impl.go:311:1: combine parameters types: func(username, cluster string, reason string, description string, configuration []byte)

Fixed in #496


Add early-escaping condition for cost-based-strategy

In our druid cluster consists of 70 servers with 200,000+ segments (will be 300,000+ to the end of this month), we've found newly added segments(we makes 2000+ segments a day with batch ingestion) are loaded to historical very slowly. If the purpose of BalancerStrategy is selecting a server with lowest cost, we can escape early when current calculating cost is exceeding previous cost. This is for that.
In a word,
    for (DataSegment s : segmentSet) {
      totalCost += computeJointSegmentsCost(segment, s);
    }

is changed to
    for (DataSegment s : segmentSet) {
      totalCost += computeJointSegmentsCost(segment, s);
      if (totalCost > currentCost) {
        break;
      }
    }

This halved required calculation, but it was not enough for our use case. Anyway it worked.

NICE!

but it was not enough for our use case
Perhaps the following issue https://github.com/druid-io/druid/issues/3202 applies to your use case as well?

@sascha-coenen It's basically a random strategy with some additions. But because druid does not support configuring strategies currently, I think that part should be changed first.

I'm generally in favor of this PR. I still have a few unaddressed comments. @navis can you confirm u guys have tested this code in a prod like env?

@fjy yep, we ran on production env and could see decrease of time but as described in comment, it was not enough for our use case. I'm good to close this.

@navis can you provide relative numbers or benchmarks for this so acceptance or just closing can be determined?

for example, a 10% improvement is pretty good because if we can get 10 "small" 10% reductions without sacrificing other capacities, that's like a 65% overall reduction in execution time.

@navis i think this PR is ultimately helpful. Do you have any numbers or benchmarks?

Going to remove milestone until author is available to work on this again.


Disabled footer for smaller devices

fixed absolute positioning of footer
made footer disappear for devices having height less than 680px as either it cant be seen properly or goes over the warning message

-.-

@fineanmol


[announce] Upgrade Twitter announcer to v2 of Twitter API

JReleaser relies on Twitter4J 4.0.7 to send tweets. This is done through Twitter's v1 of their API which as of late April 2023 seems to be no longer working with free access.
Twitter4J 4.1.2 is the latest release as of April 2023. It offers partial support for v2 as far as I can tell.
$ jarviz bytecode show --gav org.twitter4j:twitter4j-core:4.1.2
subject: twitter4j-core-4.1.2.jar
Unversioned classes. Bytecode version: 52 (Java 8) total: 201
Versioned classes 9. Bytecode version: 53 (Java 9) total: 1

$ jarviz module name --gav org.twitter4j:twitter4j-core:4.1.2
subject: twitter4j-core-4.1.2.jar
name: org.twitter4j
source: explicit
automatic: false
valid: true

$ jarviz module descriptor --gav org.twitter4j:twitter4j-core:4.1.2
subject: twitter4j-core-4.1.2.jar
name: org.twitter4j
version: 4.1.2
open: false
automatic: false
exports:
  twitter4j
  twitter4j.management
  twitter4j.v1
requires:
  java.base mandated
  java.logging
  java.management
  org.apache.logging.log4j static
  org.jetbrains.annotations static
  org.slf4j static

Unfortunately it brings an additional dependency: org.jetbrains:annotations
https://repo1.maven.org/maven2/org/twitter4j/twitter4j-core/4.1.2/twitter4j-core-4.1.2.pom
Moreover, there's a BC change added in 4.1.0 that needs to be addressed by jreleaser-twitter-java-sdk https://github.com/Twitter4J/Twitter4J/issues/392

🎉 This issue has been resolved in v1.6.0 (Release Notes)


Dashboard doesn't work in pulsar-standalone docker image

Describe the bug
If you run the pulsar-standalone docker image, which bundles the dashboard with pulsar, the dashboard collecter fails to run, with this error:
Traceback (most recent call last):
  File "./collector.py", line 58, in fetch_broker_stats
    _fetch_broker_stats(cluster, broker_url, timestamp)
  File "./collector.py", line 76, in _fetch_broker_stats
    topics_stats = get(broker_url, '/admin/v2/broker-stats/destinations')
  File "./collector.py", line 41, in get
    proxies=http_proxyes,
  File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 897, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

The issue is that the endpoint /admin/v2/broker-stats/destinations doesn't exist. In the V2 API, the endpoint was renamed to /admin/v2/broker-stats/topics. The fix is a simple replacement of "destinations" with "topics" in collector.py.
While investigating this, I noticed this change was made in PR #3657, which made its way into the Docker image in 2.4.0:
workspace ~/pulsar/docker $ docker run -it apachepulsar/pulsar-standalone:2.3.1 grep destinations /pulsar/django/collector.py
    topics_stats = get(broker_url, '/admin/broker-stats/destinations')
workspace ~/pulsar/docker $ docker run -it apachepulsar/pulsar-standalone:2.4.0 grep destinations /pulsar/django/collector.py
    topics_stats = get(broker_url, '/admin/v2/broker-stats/destinations')

I was wondering why the Pulsar dashboard works for anyone after this change was made. I was baffled for a while, until I realized the repo has 2 copies of collector.py, which, believe me, is confusing.
The main dashboard image is built from the files in dashboard/django. The collector.py in that directory was not modified by PR #3657. So, the main dashboard Docker image is fine.
However, for building the pulsar-standalone Docker image, the docker/pulsar-standalone/django directory is used. That file was modified (incorrectly) in #3657. There really should be a single source for the these Django files.
I think it would be possible to modify the pulsar-standalone Dockerfile to use the main dashboard/django files when building the pulsar-standalone Docker image. Then the changes made in the two copies of collector.py can be merged into a single file.
I will put together a PR with changes to this effect.
To Reproduce
You just need to run the pulsar-standalone Docker image. This is how I do it:
docker run \
	-p 6650:6650 -p 8081:8080 -p 80:80\
	-d --rm \
	--name pulsar-standalone  \
	--mount source=pulsardata,target=/pulsar/data \
        --mount source=pulsarconf,target=/pulsar/conf \
	apachepulsar/pulsar-standalone:2.4.1

Expected behavior
The dashboard should work in this Docker image, since that seems to be the point of it. It is essentially pulsar-all image plus the dashboard.

pr 5420 merged.


make default VERSION and IMAGE_TAG the same (#353)

This passes the same options for the default value of VERSION and IMAGE_TAG. This ensures that the version the image is tagged with is the same as the version that the nomos binary is built with. This disparity was leading to a test failure when the HEAD commit has a tag.
This change does not alter the release functionality, since the release flows pass in a value rather than relying on the default.

/lgtm
/approve

/lgtm


How to start the red lora icon?

How to start the red lora icon? I do not have this icon when I have installed it, but my classmate has this icon when he has installed it. Could you please help me

That icon is part of the Native Automatic1111 install, It was added several weeks ago.  If you don't have it, perhaps you need to git pull an update to your A1111 install.


Add e2e test of chatqna for genai example

Description
Add e2e test of chatqna for genai example.
Issues
n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)

Dependencies
n/a.
Tests
n/a.

The CI issue not related to k8s, will track separately.


flutter/flutter CI should automatically detect all dart packages under //dev and run their tests

Today, tests under //dev are run as part of the framework misc shard, specified by this code: https://github.com/flutter/flutter/blob/3f722c1442fa07e6afc2442853bc2a7813a3ba8c/dev/bots/test.dart#L982.
This requires hard coding the path to each dart package and then invoking flutter test or dart test on them. However, it is easy to overlook this (for example, currently tests under //dev/tools do not get run). Instead, test.dart should automatically detect every pubspec.yaml under //dev and run flutter test on it.

@christopherfujino I agree that this would be valuable. I'm not sure having an issue to track it is going to help though (anyone can do this, and there's no particular owner for this logic). If nobody is running to implement this, should we close this issue for now?

@christopherfujino I agree that this would be valuable. I'm not sure having an issue to track it is going to help though (anyone can do this, and there's no particular owner for this logic). If nobody is running to implement this, should we close this issue for now?

i won't object to closing this. could you clarify our policy for which bugs should be open and which closed? should those with no owner and no assignment be closed?

https://github.com/flutter/flutter/wiki/Issue-hygiene#closing-issues is the answer to the above question, such as it is


WebSocket Ready flag should only be set after Open event

Currently, the WebSocket Client Transport will mark itself as 'ready' once it has received a PeerMessage from the server, otherwise one second after construction.
However, if for some reason the WebSocket takes more than one second to fully establish, the Transport will be marked ready and will emit the 'ready' event prior to the WebSocket transport actually being ready to accept 'send' calls. This could be resolved by moving the 'auto-ready' setTimeout call into the 'onOpen' callback function.
We are periodically seeing 'Websocket not ready' messages emitted by this line:
https://github.com/automerge/automerge-repo/blob/main/packages/automerge-repo-network-websocket/src/BrowserWebSocketClientAdapter.ts#L141
Since Automerge Repo is fully responsible for sending messages, either there is an issue with the 'ready' handling, or the Transport is being marked 'ready' before the WebSocket is in the OPEN state. It should be noted that we were seeing this issue with the public/test Websocket server, which may be slower/more latent.

Thanks for the bug report, @justin0mcateer! I see the comment indicates that this choice was deliberate by @alexjg so before I change this let's see if he has any comment on why he set it up that way.

The reason for the setTimeout which marks the adpater as ready is because we don't do anything until all the network adapters have said they are ready. The idea of the "ready" callback was not to wait for peers who might never appear (because for example they are overloaded and will never respond), but just to avoid situations where an adapter will take a few miliseconds to set up (such as for the MessageChannel adapter) and consequently races with a Repo.find call on application startup. Frankly, this is a bit of a hack, a more principled approach probably means introducing some additional states in the NetworkSubsystem to track the state of an adapter (connecting, handshaking, ready etc.).
In this case however, we can probably continue hacking. The problem is that the setTimeout is in the connect handler, which means that if we take longer than a second to connect then we end up telling the network adapter we are ready for messages when we aren't. Probably the easiest way around this is to make the readiness timeout configurable - with the option to have no timeout whatsoever. It should be noted though that until we mark the adapter as ready the Repo will not do any networking at all, which means you'll force all requests for a document to wait on the adapter being ready.


Bump to 9.4.0-4 to address permission issues

New Node.js minor version bump
Use this issue template to report a minor version bump in Node.js.
New Node.js version number: 9.4.0-4
Tasks
Check out the branch for whatever version is being updated. E.g.
git checkout v9.x

All of the following tasks occur on this branch.

[x] Ensure a published node-rpm for this version exists.
[ ] Update versions.mk with the correct version number for NODE_VERSION and NPM_VERSION (not relevant).
[ ] Update releases.json and image-streams.centos7.json with new version information. (not relevant).

node-metadata -i <major-version> | jq '.' > releases.json
node-image-stream -f releases.json -i bucharestgold/centos7-s2i-nodejs > image-streams.centos7.json

[x] Ensure that make all passes successfully.
[x] Tag the new release: git tag -s -m 'Update to Node.js version 8.10.0' v8.10.0
[x] Publish the release to docker hub (you will need to have DOCKER_USER and DOCKER_PASS in your environment).

make tag publish

[x] Finally, push your changes to github: git push origin <branch> --follow-tags.

Fixes: https://github.com/bucharest-gold/centos7-s2i-nodejs/issues/38

Closed with tag node-9.4.0-6.


Change TX_SUB_ENABLED to DISABLE_TX_SUB

Preview is available here:http://developers-pr237.previews.kube001.services.stellar-ops.com


Audio live not working

When I'm doing a live of an app it doesn't stream the sound

I don't think that's going to be easy to support until Discord themselves support M1 -- in the official app, on macOS, to capture sound while screen capturing it's required to install a helper application. This application is based on the web version of discord, which also does not support audio capture.

Ok, thank you anyway, i'll close this


👷 add publishing workflow

Generated summary (powered by Graphite)

TL;DR
This pull request adds a new GitHub Actions workflow for publishing our Python package to PyPI automatically whenever a new release is created.
What changed
A new file .github/workflows/publish.yaml was added. This file defines a GitHub Actions workflow that triggers on the release event. The workflow includes steps to checkout the repository, setup Python, install Poetry, configure Poetry with PyPI API token, and finally build and publish the package to PyPI.
How to test
To test this change, you can create a new release on GitHub. Once the release is created, the workflow should trigger and you should see the package published on PyPI.
Why make this change
This change automates the process of publishing our Python package to PyPI. This ensures that the package is always up-to-date with the latest release and reduces the manual effort required to publish the package.

Current dependencies on/for this PR:

main

PR #68   👈

PR #69

This stack of pull requests is managed by Graphite.

Merge activity

Dec 31, 11:11 AM: @mingi3314 started a stack merge that includes this pull request via Graphite.


LaunchOnGridGetNMM does not calls CalculateNMM

After the whole code was moved into a module the call of CalculateNMM from LaunchOnGridGetNMM is simply skipped. This has to do something with Maple modules.

Missing export for CalculateNMM - was not seen in the Grid.


Matrix Inverse Error

Great work.
When I try this code, I met a same error for several senarios:
Process Process-1:
Traceback (most recent call last):
   File "/home/zzl/miniconda3/envs/nice-slam/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
      self.run()
   File "/home/zzl/miniconda3/envs/nice-slam/lib/python3.7/multiprocessing/process.py", line 99, in run
      self._target(*self._args, **self._kwargs)
   File "/home/zzl/workspace/nice-slam/src/NICE_SLAM.py", line 263, in tracking
      self.tracker.run()
   File "/home/zzl/workspace/nice-slam/src/Tracker.py", line 195, in run
     device).float().inverse()
torch._C._LinAlgError: cusolver error: CUSOLVER_STATUS_EXECUTION_FAILED, when calling `cusolverDnSgetrf( handle, m, n, dA, ldda, static_cast<float*>(dataPtr.get()), ipiv, info)`. This error may appear if the input matrix contains NaN.

So far, this happens for imap in Apartment and nice-slam in TUM_RGBD/freiburg1 (nice-slam in Apartment and imap in TUM_RGBD/freiburg1 are ok). I haven't try other scenarios yet.
This error usually happens in first five frames optimization and is reproducible. I haven't change any code yet, so I wonder why the matrix that can't be inversed emerges.

Hi Zizhang,
Thanks for your interest in our work!
I just tested the code on a brand new machine following the step-by-step description in README.md, and it does not have the error you said. Could you please give more information, for example, your environment? Also, it would be nice of you to print out the matrix it cannot inverse.
Best,
Zihan

Hi Zihan,
Thanks for reply. This error occurs for this line of code:
delta = pre_c2w@self.estimate_c2w_list[idx-2].to(device).float().inverse()

I try to print the matrix that can't be inversed, but I find it is a matrix that can be inversed, for example for imap* in CoFusion/room4, at Frame 2, the matrix to be inversed is:
tensor([[ 9.9996e-01,  6.4982e-03,  5.0393e-03,  3.8073e-03],
        [-6.5110e-03,  9.9997e-01,  2.5397e-03,  1.5920e-03],
        [-5.0227e-03, -2.5724e-03,  9.9999e-01,  3.3164e-04],
        [ 0.0000e+00,  0.0000e+00,  0.0000e+00,  1.0000e+00]])

I ran all the experiments that failed before on different GPU settings, and find that when using RTX3090 with CUDA 11.2 the computation is fine, but when on GTX1080 with CUDA 11.0 this error occurs. So far I think the CUDA version is the reason.

I see, maybe GTX1080 is a bit old and has some compatibility issues with CUDA 11.0 and some PyTorch functions. Glad to hear you are able to run it now on a new machine.

Hi
The matrix inverse computation also fails for RTX TITAN with CUDA 11.1, but if move the matrix to cpu will not cause any error. So I change the L195 to following and it seems to be an appropriate solution with no performance decreasing.
delta = pre_c2w@self.estimate_c2w_list[idx-2].float().inverse().to(device)


Add a command to add a folder to a workspace

There's a vscode.openFolder command but doesn't seem to be one that will add a folder to the workspace.
This would be really useful for a "new project" command I'm working on (if you invoke it from within a workspace I want to add it, not replace the workspace with just the new folder).

I don't know how to +1 this but I hope this gets noticed by the devs

@laaaaanceeee On my first comment above there's a little 👍 icon you can click to add your "vote".

@egamma I think that'll work fine, thanks! Though the API for delete seems a bit wonky - why delete by index/count and not Uri? Not only is it a bit weird it's more likely to suffer from race conditions if not synchronous whereas the URIs can't be interpreted wrongly?

The goal was to have a minimal API that supports adding/removing multiple folders in one call. For this reason we went an Array.splice style API.

it's more likely to suffer from race conditions if not synchronous

pls note the following comment:
* **Note:** it is not valid to call [updateWorkspaceFolders()](#updateWorkspaceFolders) multiple times
		 * without waiting for the [`onDidChangeWorkspaceFolders()`](#onDidChangeWorkspaceFolders) to fire.

Adding  @bpasero

The goal was to have a minimal API that supports adding/removing multiple folders in one call

I'm not sure I understand why an array of the Uris/WorkspaceFolders to remove wouldn't do this? (I'm not actually like to use this so it doesn't affect me, I'm just thinking that once you put this in it's gonna be hard to change)
updateWorkspaceFolders(
  start: number,
  workspaceFoldersToAdd?: { uri: Uri, name?: string }[],
  workspaceFoldersToRemove?: Uri[] | WorkspaceFolder[]
): boolean

pls note the following comment in the API documentation

I was thinking more about if the extension had gotten a list of workspaceFolders and did something async (eg. check if they contain a specific file or something) and then called this but the user had added/removed a folder in the meantime, the indexes could all be wrong. Indexes/lengths can't be wrong if you don't have them :-)
Again, I don't feel strongly about this, it just feels a bit so I thought I'd mention!

@DanTup I do not understand that argument about long running tasks and race conditions. You should always before you call into this method check the contents of the vscode.workspace.workspaceFolders array to ensure you are doing the right thing.
Is there a specific scenario that the current API does not allow you to do?

Nothing I can't do; just felt wonky. The user is likely to already have a WorkspaceFolder or Uri for what they'd like to remove, it seems weird to have them convert it to indexes when Code could do it with a nicer interface.
Personally I only need the add functionality so it's not something I feel strongly about; I just wanted to provide the feedback (and I totally appreciate you're way better placed to make decisions like this than me :-))


[FEATURE] Create response_model schema with header

Is your feature request related to a problem? Please describe.
It's currently possible to set the response model to a pydantic class which is very handy but as far as I can see it's not possible to set up the header properties inside the object. I know that I can set up the header in Response but that won't be included in opeanapi documentation.
What I get:

What I want:

Describe the solution you'd like
I think one should be able to create a pydantic object for responses which supports headers, content, etc.
from pydantic import BaseModel, Schema, UrlStr
from uuid import UUID

class CreatedHeader(BaseModel):
    """Header for created response."""
    Location: UrlStr = Schema(
        ...,
        description='Location of the newly created resource.'
    )

class CreatedContent(BaseModel):
    """Content for created response."""
    id: UUID = Schema(
        ...,
        description='Id for the newly created resource.',
        example='3fa85f64-5717-4562-b3fc-2c963f66afa6'
    )
    message: str = Schema(
        None,
        description=' A human readable message',
        example='Use Location in headers to access the new object.'
    )

# This should be used as the response_model
class Created(BaseModel):
    headers: CreatedHeader
    content: CreatedContent

Describe alternatives you've considered
For now I create a response model only for content. Header is missing from documentation but I add to description that see header for Location.
Additional context
This can be considered/ addressed as part of  #16. Generally speaking the response documentation/ validation similar to what is possible for parameters and query will be very helpful.

Thanks for the report. Yes, I plan on adding that as part of #16 (or based on it).

It's now possible to include responses in path operations, including everything available/valid in OpenAPI, like headers: https://fastapi.tiangolo.com/tutorial/additional-responses/
It's available in version 0.12.0. :tada: :rocket:

@tiangolo, beautiful! I will try it out and let you know the results. cheers.

@tiangolo quick feedback. Adding responses works as expected and I can also add the header like this:
@router.post( [...] ,
    responses={
        **additional_error_post_responses,
        201: {'headers': {'Location': ''}}
        }
)

but this doesn't have type checking for Location format. If I pass a pydantic object to 'headers' it gives an error. I tried both assigning a model to header which gives me an error on building the redoc page:
class Location(BaseModel):
    """Header for created response."""
    Location: UrlStr = Schema(
        ...,
        description='Location of the newly created resource.'
    )

@router.post( [...] ,
    responses={
        **additional_error_post_responses,
        201: {'headers': {'model': Location}}
        }
)

and writing the whole response model as a pydantic object which in this case it takes headers as part ot the Response content schema:
@router.post( [...] ,
    responses={
        **additional_error_post_responses,
        201: {'model': CreatedResponse}
        }
)

Hmm, I see. We can think of it as a feature request to support Pydantic models in headers, but it would be exclusively to generate the JSON Schema.
Have in mind that:

You still need to return a Response with the headers already included.
Those header's won't be validated by FastAPI, but you can pass them to your model to validate them in your code (in your path operation) and then convert them to a dict, before passing them to the Response.
Also, the Pydantic models are currently used to define response bodies, but they are not being used to include several parts of a response in a single model (headers and content).

Thank you for the explanation. Since the first solution already addresses this feature request and there are alternate ways for validating the header I close this issue. Thank you for addressing it quickly.

Great, thanks!


Erros

I Tried to use but there is erros showing on the console.

Can you send me your code sample? Also error.

On 16 Sep 2021, at 16:59, Bruno @.***> wrote:
I Tried to use but there is erros showing on the console.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/caglardurmus/react-native-insta-story/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPU4ARORQBE3R6YOTZPMK3UCHZ3BANCNFSM5EE2RRBQ.

Hi, I appreciate your response, first error the npm install  did not installed the src folder, I did manually but did't works because the system was telling about Invariant Violation: Tried to register two views with the same name RNCSafeAreaProvider.
Thank you so much

Hi, install v1.0.3 and pod install

On 16 Sep 2021, at 17:33, Bruno @.***> wrote:
Hi, I appreciate your response, first error the npm install did not installed the src folder, I did manually but did't works because the system was telling about Invariant Violation: Tried to register two views with the same name RNCSafeAreaProvider.
Thank you so much
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/caglardurmus/react-native-insta-story/issues/1#issuecomment-920957663, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPU4ASZ2K6HSLRIMB7AY2TUCH53ZANCNFSM5EE2RRBQ.

HI, i'm getting this error now

Hi again, remove old version and install last v1.0.5 then nix pod-install and build again.

On 16 Sep 2021, at 19:25, Bruno @.***> wrote:
https://user-images.githubusercontent.com/12675160/133649495-bb72eb51-edaf-4ef9-bd7a-bfc520fb8a24.png
HI, i'm getting this error now
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/caglardurmus/react-native-insta-story/issues/1#issuecomment-921049394, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPU4AUFE4PXI6C3SP2R4S3UCILABANCNFSM5EE2RRBQ.


[!] Unable to find a specification for SwiftyJSON (= 2.1.3)

Hi,
Using the --pre release version (0.36.0.beta.1) of cocoapods and a including this line in our Podfile
pod 'SwiftyJSON', '2.1.3' we are getting the following error when doing a pod install:
[!] Unable to find a specification for SwiftyJSON (= 2.1.3)
Anyone else getting this?

Hi,
Adding this line
source 'https://github.com/CocoaPods/Specs.git'
to my Podfile resolved the issue.


[Sort] List of records not refreshed when removing sort field

To reproduce:

Sort records by a field in the Sort "filter".
Remove the filter by pressing the "x".
You have to press the "Sort" button again to remove the sorting and update the view. For the other filters, pressing the "x" automatically refreshes the view.

)

At the moment this filter is different from the rest, having to click "sort" to confirm the action. @Amelie-V, do you think we can remove the filter directly and maybe add a "remove all" like in the rest?

El cambio mayor deseable es que no haya que clicar un button de validación (Sort) y que el reorden se haga en tiempo real.
Si se quiere esperar la revision global de los filtros que esta pendiente, de momento podemos efectivamente permitir cerrar el modal cuando se da a la cruz

The Sort filter has a different behaviour with X button. For filters, the X button clears all selected fields for that filter.  In sort component, the X button drops the sort field configuration, and it used for changing sort configuration before apply it (Like changing selected fields for a filter).
To apply change proposed by @Amelie-V I would like to use the X button in a same way like filters do: clear totally the sort configuration and then close modal. If we decide to close the modal every time we click the X button, changing configuration in a sort with multiple fields could be a bit annoying

Would it be possible/relevant to add this logic? @frascuchon @dcfidalgo @dvsrepo @leiyre

Add a  "remove all sort" when 2 or more sort actived . On click on it, close the modal directly.
When there is only one sort actived, click on the X button close the modal too.

Would it be possible/relevant to add this logic? @frascuchon @dcfidalgo @dvsrepo @leiyre

Add a  "remove all sort" when 2 or more sort actived . On click on it, close the modal directly.
When there is only one sort actived, click on the X button close the modal too.

I think the same button should resolve the same action for all cases (clear the Sort configuration) like filter component does. Could you provide a sketch design proposal @Amelie-V ?
Anyway, i think It should be better invest the effort to normalize the filter section


Paste style doesn't recompute text boundaries

See repro:
https://user-images.githubusercontent.com/197597/155434537-1a770b5b-f72c-4cfc-8252-4787f08faccc.mov

Thanks for the quick fix!


WIP on lidar-reposition-dev

!UNTESTED!
using SLAM gridmap to detect cones (2D)
use of LiDAR DBSCAN point clustering process

[ ] Refactor
[x] Feature
[ ] Bug Fix
[x] Optimisation

Description:
This script takes the SLAM gridmap that gets created, recognizes and clusters points using DBSCAN
the clustered points then get recognised as cones if they are within certain parameters
the gridmap get a new origin point with each update the map gets
Documentation:
https://www.notion.so/qut-motorsports/SLAM-Cone-Detection-9b6e0e06287b4d12b28a27e52a949ccd

(cone overlay onto SLAM toolbox gridmap)

Accidental merge request to master instead of staging. Merge request closed


Feature Request: Register a converter that can intercept private subtypes

Scenario:
The default PipeReader is Pipe+DefaultPipeReader. Pipe+DefaultPipeReader extends the abstract PipeReader, but it is private so cannot be registered as a known subtype.
In StreamJsonRpc, we have a PipeReaderConverter : MessagePackConverter. When serializing Pipe+DefaultPipeReader, the PipeReaderConverter is not chosen. I had to use the overload of JsonRpc::InvokeWithCancellationAsync that accepts an array of argument types and set the argument type to PipeReader so that the PipeReaderConverter is used.
It would be helpful if we could somehow register a converter that could intercept the private subtype Pipe+DefaultPipeReader. Otherwise, consumers must explicitly declare the correct type, or StreamJsonRpc needs to check all types being serialized to see if they extend the public abstract PipeReader.

Otherwise, consumers must explicitly declare the correct type

Don't they already? Or is this for the untyped JsonRpc.InvokeAsync(string, object[]) case?

The only thing I can think of at the moment is to offer a way to users to say "I want to convert this type and all derived types except derived types that are specifically otherwise registered."

The tests in StreamJsonRpc currently tend to use the object[] overload. In my PR I updated many of those tests to declare the types as well, so that pipe reader would get converted correctly. But this seems like either a take-back, or an additional restriction for the NB.MP formatter we'll need to document.