#6416 was closed.

I see my previous feedback request was closed with following statement :
"Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content."
Please note, I am FTE with Microsoft and this is not an issue with my tenant, the article has incorrect information which needs to be updated.

@Sagamare Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@Sagamare Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @Sagamare, thank you for your feedback and help us to improve docs.microsoft.com.
These two articles contain different topis but related:

One of them is related to the complimentary dial-out period. It ended on November 30, 2019, and included 900 minutes per user per month.
The other is related to the "Dial-Out/Call Me At" minutes benefit. It began on December 1, 2019, and includes 60 minutes per user per month.

Hi @Sagamare, thank you for your feedback and help us to improve docs.microsoft.com.
These two articles contain different topis but related:

One of them is related to the complimentary dial-out period. It ended on November 30, 2019, and included 900 minutes per user per month.
The other is related to the "Dial-Out/Call Me At" minutes benefit. It began on December 1, 2019, and includes 60 minutes per user per month.

@scanum I think we can close this issue. Thank you!

If you have a Microsoft alias, you can link your accounts in GitHub so that a blue "Microsoft submitter" label appears to any PR's or issue you submit. Guidance on it here: https://docs.opensource.microsoft.com/tools/github/index.html
Here is the site you can use to see the mappings between GitHub and Microsoft aliases: https://repos.opensource.microsoft.com/people?q=Sagamare

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Tweak Signal Documentation

Add missing operator and leading description
Avoid calling "Signal" an object or class.
Add more details to connect and disconnect. There are ported from https://github.com/godotengine/godot/pull/67880.
Other tweaks all around.

I feel like the docs are missing two infos along the lines of "you usually don't really want to instantiate this type by hand using the constructors, the engine does that for you with the signal keyword in GDScript or [Signal] annotation in C#" and "you'll mainly be using this type when working with the object.signal_name.connect(...) syntax".
I know the former is mentioned in the linked tutorial, but just reading these class docs doesn't make the internal nature of this type clear enough IMO.
(Disclaimer: not sure if that's how signals still work in today's C# integration!)

I have to admit I have gotten lazy after the major Object documentation overhaul, and I don't have the time to test every function thoroughly once more. My biggest doubt about Signals right now is that there is both Object.add_user_signal() and the Signal constructor, and at this moment in time, I cannot check if they essentially do the same thing. Regarding empty Signal & Callables, I don't see why one would want to manually create them if not as placeholders. So that may need to be noted.
You're right in needing to mention that GDScript does a lot of the work for you. Signals can be defined for the entire custom class with the keyword, and so can Callables with the func keyword. Both Signal and Callable  (https://github.com/godotengine/godot/pull/68262)'s documentation need to be carefully looked at.

Force-pushed again because the Mac build craves to fail whenever it feels like it.

Thanks!

I noticed we're getting new warnings because a codeblock tag from this PR should actually be codeblocks, plural. 🙃

https://github.com/godotengine/godot/pull/69107


Skeleton code for offline portion of model

This should include at least classes and method stubs. Some code can probably be reused from our solo assignments.

If "skeletal" means attributes and methods from the UML, we are nearly done.  These have yet to be skeletoned fully:

DataSource
Cache
ServerInterface (probably not necessary at this point, really)
ResultCallback

How's this looking guys? It's due today.

I just finished that shell I was writing.  I'll get on this tomorrow.


无法克隆?

C:\Users\Administrator>git clone git@github.com:xwartz/PupaFM.git
Cloning into 'PupaFM'...
The authenticity of host 'github.com (<IP_ADDRESS>)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of know
n hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
C:\Users\Administrator>git clone git@github.com:xwartz/PupaFM.git
Cloning into 'PupaFM'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

应该是你 git SSH 配置有问题

那git其它的东西都是正常的啊,咋个唯独你家的就不行了,好奇怪的.有点郁闷

不知道哦，没做什么限制


Is it possible to build/export it as legacy

I really like your template,  but I just think it would be better if it could be built/exported as legacy build, I tried running npx sapper build --legacy and npx sapper export --legacy but it doesn't work, and I think that you should update some versions in package.json most importantly svelte and sapper and also some other libraries/dependencies.
Thank you in advance
Mihael

@Charca @tommywalkie and once again thank you for your dedication

Hey @PH4NTOMiki, thanks for bringing this up. I've fixed it in #17, so if you pull the latest from the master branch, it should be working fine now. Try using: npm run build -- --legacy.


Draft Wireframe of New Home Page

Driven by personas work
Has CTAs to quickly get folks where they need to go
Potential areas to address in tight copy: "what is TBD from a developer perspective", "what is Web5", "why does all this matter", "How to get started making Web5 applications", "what/why of tbDEX"

@dayhaysoos notes: let's start by putting graphics into a repo as proposals for folks to comment on and evolve. Not finding great open editable tooling to do this in a collaborative fashion aside from sharing images.

If closed, do we have link to where those wireframes live? Last I caught I think they were an in-progress work for what's now called "Getting Started", the home page of the docs section? Something we were gonna do a Phase 2 release of at the F2F? @bobbilee19 makes sense to reopen as "In Progress" until that's done, or do you have something else which satisfies this?


With sticky monitor conf, restarting workspacer moves windows around

In my config, I have the following:
  var monitors = context.MonitorContainer.GetAllMonitors();
  var sticky   = new StickyWorkspaceContainer(context, StickyWorkspaceIndexMode.Local);
  context.WorkspaceContainer = sticky;
  for (int i = 0; i < monitors.Length; i++) {
    int j1 = i+1;
    sticky.CreateWorkspaces(monitors[i], j1 + ":1", j1 + ":2", j1 + ":3", j1 + ":4", j1 + ":5", j1 + ":6", j1 + ":7", j1 + ":8", j1 + ":9");
  }

Each time I restart Workspacer, some windows move around in workspaces. For instance, I may have two windows on the second tag of the second monitor (2:2). When restarting, the two windows may move on the 7th tag. The movement seems arbitrary. However, what is consistent is that the focused tag will always move to the first tag. So if you're focusing a window on third tag (2:3), then after restart, the window is going to be on tag 2:1.
Why is that? Is that a bug or something with my config? In any case, I think that Workspacer should prevent this whatever the config of the user...

If I change the above snippet to:
  var monitors = context.MonitorContainer.GetAllMonitors();
  if (monitors.Length == 1) {
    context.WorkspaceContainer.CreateWorkspaces("1", "2", "3", "4", "5", "6", "7", "8", "9");
  } else {
    var sticky = new StickyWorkspaceContainer(context, StickyWorkspaceIndexMode.Local);
    context.WorkspaceContainer = sticky;
    for (int i = 0; i < monitors.Length; i++) {
      int j1 = i+1;
      sticky.CreateWorkspaces(monitors[i], j1 + ":1", j1 + ":2", j1 + ":3", j1 + ":4", j1 + ":5", j1 + ":6", j1 + ":7", j1 + ":8", j1 + ":9");
    }
  }

I don't get the issue on a single monitor setting.

I believe PR #183 fixed the issue. If you could quickly test it as well we can close this one.

Thanks! I can now use multiple monitors with Workspacer!!!


node-md5 doesn't work with browserify

<EMAIL_ADDRESS>// => TypeError: object is not a function

It took me a while to find this module since I kept running into md5.
The existing md5 module seems like some random test/stub. Maybe @coolaj86 you could unpublish it, and @pvorb you could publish over it. Then you can decide whether you want to continue using MD5 or md5 as the main entry point (i.e. where one depends on the other). Alternatively you could just deprecate one with details pointing to the correct module in the readme.

There are very practical reasons to not use md5.
In addition, it has been deprecated and is not being included in newer
crypto libraries.
I would strongly recommend using sha1 or sha256 instead.
I probably reserved it and never did anything with it because it already
exists in node.
That said, I've added pvorb https://github.com/pvorb as an owner of md5
on npm.
AJ ONeal
(317) 426-6525
On Wed, Jul 15, 2015 at 12:36 PM, Matt DesLauriers<EMAIL_ADDRESS>
wrote:

It took me a while to find this module since I kept running into md5
https://www.npmjs.com/package/md5.
The existing md5 module seems like some random test/stub. Maybe @coolaj86
https://github.com/coolaj86 you could unpublish it, and @pvorb
https://github.com/pvorb you could publish over it. Then you can decide
whether you want to continue using MD5 or md5 as the main entry point
(i.e. where one depends on the other). Alternatively you could just
deprecate one with details pointing to the correct module in the readme.
—
Reply to this email directly or view it on GitHub
https://github.com/pvorb/node-md5/issues/5#issuecomment-121707402.

@coolaj86

I would strongly recommend using sha1 or sha256 instead.

Yep, that's right. But there still are some use cases where you want to use MD5 (most likely for compatibility reasons, e.g. Gravatar).

That said, I've added pvorb https://github.com/pvorb as an owner of md5 on npm.

So what should we do now? In my opinion, a sane plan would be to entirely drop one of the packages on npm and replace it by MD5. If you agree with me, I'll try to figure out if that's even possible.

I think the best course of action would be to artificially bump your
version to 2.0.0 on lowercase md5, deprecate the uppercase MD5 with a
version 1.1.0, and keep both modules up for backwards compat.
AJ ONeal
(317) 426-6525
On Wed, Jul 15, 2015 at 1:04 PM, Paul Vorbach<EMAIL_ADDRESS>wrote:

@coolaj86 https://github.com/coolaj86
I would strongly recommend using sha1 or sha256 instead.
Yep, that's right. But there still are some use cases where you want to
use MD5 (most likely for compatibility reasons, e.g. Gravatar).
That said, I've added pvorb https://github.com/pvorb as an owner of md5
on npm.
So what should we do now? In my opinion, a sane plan would be to entirely
drop one of the packages on npm and replace it by MD5. If you agree with
me, I'll try to figure out if that's even possible.
—
Reply to this email directly or view it on GitHub
https://github.com/pvorb/node-md5/issues/5#issuecomment-121714951.

@pvorb

If you agree with me, I'll try to figure out if that's even possible.

:+1: Yup, this way you only need to maintain one npm module. The other one can remain deprecated with large and clear text directing users to the correct module.
@coolaj86

I would strongly recommend using sha1 or sha256 instead.

Sure, it can be added as a note, but it is still useful to have a MD5 function on npm. :smile: Example use-case.

@coolaj86 That sounds good.
Replacing md5 completely with MD5 would have the benefit of being able to still use var md5 = require('MD5'); as well as var md5 = require('md5');. So the code of MD5's dependents wouldn't need to change. On the other hand, there still are packages depending on old versions of md5 and MD5. Those should also be supported.

@coolaj86 https://github.com/coolaj86 That sounds good.
Replacing md5 completely with MD5 would have the benefit of being able to
still use var md5 = require('MD5'); as well as var md5 = require('md5');.
So the code of MD5's dependents wouldn't need to change. On the other hand,
there still are packages depending on old versions of md5 and MD5. Those
should also be supported.

Yeah, so just bumping the major version as a "warning, this might be a
breaking change for you" and adding a deprecation notice (there's an npm
commandline option for that) should be suitable.
It's probably possible to add a little shim that would make it backwards
compatible in most cases too. But if you bump it to 2.0.0, I'd say don't
worry about a shim -  just let my old version break and die.

The key being "add", not "replace" nor "delete".

MD5 1.2.2 -> 1.3.0 with "deprecated, use lowercase<EMAIL_ADDRESS>from now on"
md5 1.0.0 -> 2.0.0 (with or without shim)

The deed is done.
$ npm view md5

{ name: 'md5',
  description: 'js function for hashing messages with MD5',
  'dist-tags': { latest: '2.0.0' },
  versions: [ '1.0.0', '1.0.1', '2.0.0' ],
  maintainers: [ 'coolaj86<EMAIL_ADDRESS>'pvorb<EMAIL_ADDRESS>],
  time:
   { modified: '2015-07-15T21:33:44.776Z',
     created: '2011-08-27T21:25:23.732Z',
     '1.0.0': '2012-05-13T00:00:30.935Z',
     '1.0.1': '2012-05-13T00:00:11.449Z',
     '2.0.0': '2015-07-15T21:33:44.776Z' },
  author: 'Paul Vorbach<EMAIL_ADDRESS>(http://paul.vorba.ch)',
  repository: { type: 'git', url: 'git://github.com/pvorb/node-md5.git' },
  users: { haeck: true, samhou1988: true },
  homepage: 'https://github.com/pvorb/node-md5#readme',
  readmeFilename: 'README.md',
  contributors: 'salba',
  bugs: { url: 'https://github.com/pvorb/node-md5/issues' },
  license: 'BSD-3-Clause',
  tags: [ 'md5', 'hash', 'encryption', 'message digest' ],
  version: '2.0.0',
  main: 'md5.js',
  scripts: { test: 'mocha' },
  dependencies: { charenc: '~ 0.0.1', crypt: '~ 0.0.1', 'is-buffer': '~ 1.0.2' }
,
  devDependencies: { mocha: '~ 1.4.2' },
  optionalDependencies: {},
  gitHead: 'c018e8932d0fbb2a200a540a055da487f4f9c150',
  dist:
   { shasum: '75e392e0ebd5a9b88dc7cb7a93875137b87c8a33',
     tarball: 'http://registry.npmjs.org/md5/-/md5-2.0.0.tgz' },
  directories: {} }

$ npm view MD5

{ name: 'MD5',
  description: 'native js function for hashing messages with MD5 (deprecated, use lowercase<EMAIL_ADDRESS>from now on)',
  'dist-tags': { stable: '1.0.0', latest: '1.3.0' },
  versions:
   [ '0.0.0',
     '1.0.0',
     '1.0.1',
     '1.0.2',
     '1.0.3',
     '1.1.0',
     '1.2.0',
     '1.2.1',
     '1.2.2',
     '1.3.0' ],
  maintainers: 'pvorb<EMAIL_ADDRESS>  time:
   { modified: '2015-07-15T21:39:04.054Z',
     created: '2011-11-25T02:59:35.402Z',
     '0.0.0': '2011-11-25T02:59:38.617Z',
     '1.0.0': '2012-06-18T09:36:25.690Z',
     '1.0.1': '2012-09-11T08:16:17.207Z',
     '1.0.2': '2012-11-25T12:00:29.943Z',
     '1.0.3': '2012-11-25T12:47:30.470Z',
     '1.1.0': '2013-07-11T19:09:28.438Z',
     '1.2.0': '2013-11-21T18:13:15.045Z',
     '1.2.1': '2014-04-05T09:10:01.649Z',
     '1.2.2': '2015-05-19T18:50:09.803Z',
     '1.3.0': '2015-07-15T21:37:45.247Z' },
  author: 'Paul Vorbach<EMAIL_ADDRESS>(http://vorb.de)',
  repository: { type: 'git', url: 'git://github.com/pvorb/node-md5.git' },
  homepage: 'https://github.com/pvorb/node-md5#readme',
  contributors: 'salba',
  bugs: { url: 'https://github.com/pvorb/node-md5/issues' },
  readmeFilename: 'README.md',
  users:
   { 'shen-weizhong': true,
     tmypawa: true,
     yourhoneysky: true,
     csbun: true,
     ernie55ernie: true,
     andriecool: true,
     ronnykj: true },
  license: 'BSD-3-Clause',
  tags: [ 'md5', 'hash', 'encryption', 'native', 'message digest' ],
  version: '1.3.0',
  main: 'md5.js',
  scripts: { test: 'mocha' },
  engines: { node: '*' },
  dependencies: { charenc: '>= 0.0.1', crypt: '>= 0.0.1' },
  devDependencies: { mocha: '~ 1.4.2' },
  optionalDependencies: {},
  gitHead: '01663ccb3b365cd347e959878c2d9deb009d1a86',
  dist:
   { shasum: '3cc266f0e89abb6b43a50f39a459df5bfde0b240',
     tarball: 'http://registry.npmjs.org/MD5/-/MD5-1.3.0.tgz' },
  deprecated: 'deprecated, use lowercase<EMAIL_ADDRESS>from now on',
  directories: {} }


How to specify paths correctly?

I am interested in evaluating performance on the OntoNotes dataset using the provided trained BERT-base model (I am not training from scratch). In order to evaluate performance, I need to first run ./setup_training.sh <ontonotes/path/ontonotes-release-5.0> $data_dir. However, I am unsure how to specify <ontonotes/path/ontonotes-release-5.0> and data_dir. What is the difference between the two? I have set data_dir to be '.' and the <ontonotes/path/ontonotes-release-5.0> path to be the full path to where I have stored onotonotes-release-5.0, but I am not sure if this is correct (I also tried making data_dir the path to the directory where ontonotes-release-5.0 is stored and <ontonotes/path/ontonotes-release-5.0> to be 'ontonotes-release-5.0', but that didn't help)? Could someone provide an example of how to correctly specify these paths?
I tried running GPU=0 python evaluate.py 'bert_base' and find that it evaluates on 0 examples. I assume that is because there is an issue with the data paths. Would appreciate any help in getting evaluate to work!

Update: I saw that minimize_partition() in minimize.py currently writes 0 documents, which makes sense that we are evaluating on 0 examples. Not sure if this is a data path-related issue as I discussed above, or something else altogether.

I am interested in evaluating performance on the OntoNotes dataset using the provided trained BERT-base model (I am not training from scratch). In order to evaluate performance, I need to first run ./setup_training.sh <ontonotes/path/ontonotes-release-5.0> $data_dir. However, I am unsure how to specify <ontonotes/path/ontonotes-release-5.0> and data_dir. What is the difference between the two? I have set data_dir to be '.' and the <ontonotes/path/ontonotes-release-5.0> path to be the full path to where I have stored onotonotes-release-5.0, but I am not sure if this is correct (I also tried making data_dir the path to the directory where ontonotes-release-5.0 is stored and <ontonotes/path/ontonotes-release-5.0> to be 'ontonotes-release-5.0', but that didn't help)? Could someone provide an example of how to correctly specify these paths?
I tried running GPU=0 python evaluate.py 'bert_base' and find that it evaluates on 0 examples. I assume that is because there is an issue with the data paths. Would appreciate any help in getting evaluate to work!
Update: I saw that minimize_partition() in minimize.py currently writes 0 documents, which makes sense that we are evaluating on 0 examples. Not sure if this is a data path-related issue as I discussed above, or something else altogether.

Hi there, can I ask how did you manage to produce the temp files?


IGNITE-12666 Provide cluster performance profiling tool

Cluster profiling based on performance logging to profiling files.
The Ignite log some additional internal statistics to profiling files (IgniteProfiling interface). The format is like WAL logging (FileProfiling).
One disk-writer thread and off-heap memory buffer will be used to minimize affect on performance. Maximum file size and buffer size can be configured on start. See IgniteProfilingMBean
The tool to build the report placed in ignite-extensions. See https://github.com/apache/ignite-extensions/pull/16
The report contains statistics:

cache operations: get|getAll|put|putAll|remove|removeAll|getAndPut|getAndRemove|lock|invoke|invokeAll
transaction commit, rollback; histogram of transaction durations
SQL, SCAN queries, top of slowest queries
Tasks and jobs. Top of slowest tasks.

Hello! Thanks for the PR.
Let's make the following changes:

core module should contain all implementations and interfaces that required to:
a. Collect profiling data.
b. Iterate through profiling data from disk
html report generation should be in ignite-extension as a separate module.
please, create the ticket to provide ability to profile only specific operations. Something like profiling.enable(TRANSACTION, CACHE_OPERATIONS)

It seems to me that work "profiling" not clear enough.
"Profiling" is a process that can be done with the data that will be collected with the patch.
But, "profiling" is not a single use-case for the data.
I can imagine something like automatic parameters tuning, affinity function tweaks, etc. based on the data about performance.
I propose to use "Performance statistics" or similar words to describe the new feature and "performance report" to name report based on collected data.
WDYT?

Do we have test for a SCAN query?

Do we have test for a SCAN query?

Yes. See PerformanceStatisticsQueryTest#testScanQuery()

Let's add tests to check tracking of INSERT and UPDATE queries.

We need to add tests that execute operations from client node or thin clients across the cluster of at least 2 nodes.
And check we can observe operations results on all nodes.


Api analyzer breaks due to NSDecimalNumber

The following errors started occurring on 9/30 build
2016-10-01T04:15:50.7362850Z ##[error] d:\Build\Agent5_work\32\s\include\Foundation/NSDecimalNumberBehaviors.h(26,4): expected a type
2016-10-01T04:15:50.7362850Z ##[error] d:\Build\Agent5_work\32\s\include\Foundation/NSDecimalNumberBehaviors.h(31,47): expected a type
2016-10-01T04:15:50.7362850Z ##[error] d:\Build\Agent5_work\32\s\include\Foundation\NSDecimalNumberHandler.h(26,55): expected a type
2016-10-01T04:15:50.7362850Z ##[error] d:\Build\Agent5_work\32\s\include\Foundation\NSDecimalNumberHandler.h(33,39): expected a type
2016-10-01T04:15:50.7362850Z ##[error] d:\Build\Agent5_work\32\s\include\Foundation\NSDecimalNumberBehaviors.h(26,4): expected a type
2016-10-01T04:15:50.7519045Z ##[error] d:\Build\Agent5_work\32\s\include\Foundation\NSDecimalNumberBehaviors.h(31,47): expected a type

closing as per #1082


chore: adapt GitHub Actions for this fork

Replace Docker Hub by GitHub Packages
Replace main by main-fork
Add manual dispatch

close #7


[feature]: Do not keep MC data for blinded hops.

Due to the ephermal nature of the blinded route and its hop pubkeys it does not make sense to persist this data. Therefore we should only keep this data in memory during the payment process and remove it afterwards.
See also https://github.com/lightningnetwork/lnd/pull/9316

A very nice design approach was mentioned by @ellemouton:
We should use the new namespace feature of the mission-control system to save the blinded path mission control data there separately. When looking for a path we would have to merge those different namespaces together (which is the difficult part of this change) so we have the whole data available for pathfinding. Then during startup because Route-Blinding data is ephemeral we wipe this blinded route namespace.


Add new file in libogg readme

In #33192 a new file was added named crctable.h, but I forgot to include this in the README, so this is a quick PR to document that. Sorry for the hassle!

Thanks!


feat: Add path to OneToOneAssociationField error message

1. Why is this change necessary?
See https://github.com/shopware/shopware/pull/3722 but for OneToOne associations

2. What does this change do, exactly?

3. Describe each step to reproduce the issue or behaviour.
-
4. Please link to the relevant issues (if any).
-
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[x] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

thanks for your contribution @aragon999 👍🎉💙


Move nomad examples to plugin extend

Closed in favor of #448

Closed in favor of #448

@RubelMozumder I thought there were some good ideas here, maybe we can come back to these when #448 is done.


Killer Knive bugfix suggestion

the killer knive only checks for the target entity's look vector this line, you should check against the body rotation vector instead.
also you should really move that to the item class instead of using the event since it's your own item.

Thanks for the suggestion. I'll try it.
Moving this to item class will be done in updates, even if this doesn't change something.


Editing multiple cells is slow

System information:

Operating system (distribution) and version: Windows 10
DBeaver version: 5.3.5
Java version: bundled
Additional extensions: n/a

Describe the problem you're observing:
Editing multiple cells at once is way slower than copy-pasting to multiple cells. Ideally the former is not more difficult than the latter, hence the bug.
Steps to reproduce, if exist:

Select many cells, say 80
Press enter
Write a value
Press enter again to confirm the value.
All selected cells get the new value, but only after a few seconds where DBeaver is entirely frozen

Workaround:

Select the first cell
Press enter
Write a value
Press enter again to confirm the value.
The single cell gets the new value immediately
Copy the content
Select the other 79 cells
Paste
All selected cells get the new value immediately, without waiting like above.

Thanks for the bug report


Support GRPCRoute and HTTPRoute on the same Gateway listener

Description:

Do we need to support GRPCRoute and HTTPRoute attached the same Gateway Listener ?

If we do we need to refactor the xDS HCM Logic that changes the codec type as well as includes web socket options based on whether the listener is linked to HTTP2 or not
[optional Relevant Links:]

Any extra documentation required to understand the issue.

Do we need to support GRPCRoute and HTTPRoute attached the same Gateway Listener ?

There are a few real-world cases of this. For example, etcd will expose port 2379 for both gRPC and HTTP API.

thanks for pointing that out @muyuan0, can you also link this to the etcd docs as well

great thanks for sharing these links @muyuan0, we can prioritize this issue once this becomes more relevant for users

Do you mean itself detect protocol to upgrade ?

Yes. Envoy will do auto detection if the codeType is AUTO, see
https://github.com/envoyproxy/envoy/blob/6c702f45fadf4abd2f24605e3d9e81c748b13f85/source/common/http/conn_manager_utility.cc#L56-L76


RancherUI,Can't add USER to Env and form validate err

Rancher versions:
rancher/server:1.6.14
rancher/agent:1.2.9
Infrastructure Stack versions:
healthcheck:0.3.3
ipsec:0.13.7
network-services:0.9.5
scheduler:0.8.3
kubernetes (if applicable):
Docker version: (docker version,docker info preferred)
beside the point
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
beside the point
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
beside the point
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
beside the point
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
ERR01
Steps to Reproduce:
ALL Name input ! if i fill with chinese,RancherUI will report me error,when I del it and fill english,it still report me error!
Results:
report me error
ERR02
Steps to Reproduce:

enable access control
add user test
into Manage Environments
click button Add Environment
in Access Control area
fill test and click +
report Identity not found: test
Results:
report Identity not found: test
ALL user unless root can't login
but when the new user is admin role,all will be ok,please tell me if all user need set to admin role?

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


[BUG]: (MDA Reference App/Tag Picker Page) Custom styles container does not auto grow

Describe the bug
Related to #97, however once that is fixed, the height of Example2ContentContainer needs to add Picker1.AutoHeight
To Reproduce
Steps to reproduce the behavior:

Open the Tag Picker custom page (once #97 is fixed)
Add colored tags in the 'custom styles' picker until the height increases
Notice that the container does not grow to accommodate the new height

This has been fixed and will be available in the next release.


add list datatypes

add followings data type and associated tests

IntegerListType
DoubleListType
StringListType
DateTimeListType

I've changed the test to subtests. And probe some odd cases.
One interesting case is that, in the case of array of string that member contain "," I decide to throw error here because the result list will become unusable

update re: @smulube suggestion to use CSV package to parse string array instead


Iframe insert page , download lose efficacy

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Chrome 97.0.4692.71(正式版本）
Operating system and its version: Mac OS 10.14.6
PDF.js version:2.12.313
Is a browser extension: no

Steps to reproduce the problem:

I used pdfjs in my react project，the way is: <iframe src='generic-legacy/web/viewer.html?file=xx'></frame>,everything is ok, then,I deployed the project to the server, i get a page url (just name it a.page);
in my another react project，i wanna insert a.page in this way: <iframe src='a.page'></frame>, then, i can normally preview pdf   as i expected, it can print、zoom in/out....., but, download lose efficacy，then i debug in ‘download-manager.js’ , seems to a.click()  don't trigger,i don't know whether it caused by inserting too much iframe?

What is the expected behavior? (add screenshot)
download be efficacy;
What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

I used pdfjs in my react project

Unfortunately we know nothing about React, or other frameworks, here and consequently we cannot provide support for that.
Furthermore, please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.

my fault，i‘ve set sandbox attribute for iframe, so, download doesn't work.


Downgrade message severity and provide sample name as context

Close #171

this solves it for the case that it is intended,  but is it possible that we do want at least a single warning for cases where it really is missing and that's unintended?

How would a Sample infer intent?

Opened https://github.com/epigen/looper/issues/173 for subsequent discussion


Curator leader election breaks in the overlord when zookeeper has issues

When zookeeper has a blip, the overlord can get into a condition we call "split brain" where leadership election is all screwed up. This causes the state of submitted requests to be non deterministic, sometimes "succeeding" or sometimes registering that it succeeding but not actually returning a success.
We have found two indicators for such a scenario. One is the following error in the logs of the overlord:
org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /DRUID_PATH/indexer/leaderLatchPath/_c_3c32cd34-4370-4e26-922d-a9b24afa4a91-lock-0000102217
        at com.google.common.base.Throwables.propagate(Throwables.java:160)
        at io.druid.indexing.overlord.TaskMaster.getLeader(TaskMaster.java:251)
        at io.druid.indexing.overlord.http.OverlordRedirectInfo.getRedirectURL(OverlordRedirectInfo.java:52)
        at io.druid.server.http.RedirectFilter.doFilter(RedirectFilter.java:73)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
        at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:83)
        at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:364)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
        at org.eclipse.jetty.server.Server.handle(Server.java:497)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248)
        at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:620)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:540)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /DRUID_PATH/indexer/leaderLatchPath/_c_3c32cd34-4370-4e26-922d-a9b24afa4a91-lock-0000102217
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
        at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper.java:1212)
        at org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:304)
        at org.apache.curator.framework.imps.GetDataBuilderImpl$4.call(GetDataBuilderImpl.java:293)
        at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:108)
        at org.apache.curator.framework.imps.GetDataBuilderImpl.pathInForeground(GetDataBuilderImpl.java:290)
        at org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:281)
        at org.apache.curator.framework.imps.GetDataBuilderImpl.forPath(GetDataBuilderImpl.java:42)
        at org.apache.curator.framework.recipes.leader.LeaderSelector.participantForPath(LeaderSelector.java:375)
        at org.apache.curator.framework.recipes.leader.LeaderSelector.getLeader(LeaderSelector.java:346)
        at org.apache.curator.framework.recipes.leader.LeaderSelector.getLeader(LeaderSelector.java:339)
        at io.druid.indexing.overlord.TaskMaster.getLeader(TaskMaster.java:243)
        ... 22 more

( This looks like https://issues.apache.org/jira/browse/CURATOR-358 )
And the other is increased CPU on both active overlords.
The solution is to restart the overlords and let them clean up their state.
In rare scenarios, a middle manager can fail to submit its stuff to the overlord after a peon completes, and will never complete because it can get in a state where the peon already gave up its task lock, but never properly finished its segment insertion at the middle manager level, so the middle manager will retry indefinitely. The fix here is to restart the middle manager, but this looses any outstanding stuff not yet submitted to the overlord.

This is the motivation for https://github.com/druid-io/druid/issues/3835 better monitoring of what the overlord thinks its internal state is.

Reopening this issue, since the Curator upgrade was reverted in #4103.

Tagging as 0.10.1 to remind us to look to see if there has been a Curator fix for https://issues.apache.org/jira/browse/CURATOR-394 when we start working on the 0.10.1 release.

Might be related: https://github.com/druid-io/druid/pull/3768

https://issues.apache.org/jira/browse/CURATOR-394 is not fixed yet although there is a patch out.

fyi, we saw this issue with druid-25.x I am not sure the new curator fixes it.  I am going to dig deeper to try and figure out what is going on and try to post some relevant logs.


MTV 467: Additional changes for MTV 2.4 documentation

MTV 2.4
Resolves https://issues.redhat.com/browse/MTV-467 by making any changes in the list that were not covered in other PRs.
Previews:

http://file.emea.redhat.com/rhoch/MTV_467/html-single/#source-vm-prerequisites_mtv "Source virtual machines  prerequisites"
http://file.emea.redhat.com/rhoch/MTV_467/html-single/#mtv-resources-and-services_mtv "MTV custom resources and services"

@ahadas @qiyuann Please review this PR.

@ahadas @qiyuann Please review this PR.


Support non-constructor JSX factory functions

TypeScript Version:  3.3.3  to 3.8.3

Search Terms:
jsx factory function constructor component ElementClass
Expected behavior:
I'm trying to pass a factory function instead of a class component as a JSX element constructor function. It should be possible according to the Handbook, as described here. See the example under the Type checking -> class component section (I can't deep-link with hash/anchor because the server isn't properly configured :( ). I should get no errors with the code provided below.
Actual behavior:
I get the following error:
JSX element type '{ render: () => { custom: string; }; }' is not a constructor function for JSX elements.
  Property 'custom' is missing in type '{ render: () => { custom: string; }; }' but required in type 'Element'.(2605)

From what I can tell, this used to work, but the behavior broke somewhere between v3.1.6 and v3.3.3 (as tried in the Playground). I'm guessing there was some change that altered detection between React function components and class components and that change introduced this bug. I'm not even sure if React runtime even allows factory functions, but my use case is a custom library and I'm not using React at all. This error is the same regardless of using React or not.
Also, with the exact example from the Handbook, because the JSX.Element is not specified explicitly, there is no error, even when there should be one. See Playground Link for Handbook example

Related Issues:
https://github.com/microsoft/TypeScript/issues/5740
https://github.com/microsoft/TypeScript/issues/5478
Code
declare namespace JSX {
  interface Element {
    custom: string;
  }
  interface ElementClass {
    render: () => Element;
  }
}

class MyComponent {
  render() {
    return {
      custom: "2"
    };
  }
}
function MyFactoryFunction() {
  return { render: () => { return { custom: "2" }; } }
}
function MyFunctionComponent() {
  return { custom: "2" }
}

<MyComponent />; // ok
<MyFactoryFunction />; // ok
<MyFunctionComponent />; // ok

class NotAValidComponent {}
function NotAValidFactoryFunction() {
  return {};
}

<NotAValidComponent />; // error
<NotAValidFactoryFunction />; // error

Output
"use strict";
class MyComponent {
    render() {
        return {
            custom: "2"
        };
    }
}
function MyFactoryFunction() {
    return { render: () => { return { custom: "2" }; } };
}
function MyFunctionComponent() {
    return { custom: "2" };
}
<MyComponent />; // ok
<MyFactoryFunction />; // ok
<MyFunctionComponent />; // ok
class NotAValidComponent {
}
function NotAValidFactoryFunction() {
    return {};
}
<NotAValidComponent />; // error
<NotAValidFactoryFunction />; // error

Compiler Options
{
  "compilerOptions": {
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "useDefineForClassFields": false,
    "alwaysStrict": true,
    "allowUnreachableCode": false,
    "allowUnusedLabels": false,
    "downlevelIteration": false,
    "noEmitHelpers": false,
    "noLib": false,
    "noStrictGenericChecks": false,
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "esModuleInterop": true,
    "preserveConstEnums": false,
    "removeComments": false,
    "skipLibCheck": false,
    "checkJs": false,
    "allowJs": false,
    "declaration": true,
    "experimentalDecorators": false,
    "emitDecoratorMetadata": false,
    "target": "ES2017",
    "module": "ESNext"
  }
}

Playground Link: Provided

@RyanCavanaugh , I see that you marked this as a Suggestion. I believe this is a bug, because the feature is documented in the official handbook, as described above, and it used to work in previous versions.
I know it's still an obscure case, but if this functionality was dropped on purpose (please confirm?), then my issue should be closed and I can open a PR to remove the misleading documentation from the handbook repo.
P.S. Sorry for tagging you, I know the repo is assaulted with new issues every day and there is limited time for triage.

5.1 should provide a workaround, here's a playground using the nightly build. JSX.ElementType was added in #51328.
The class components section in the handbook definitly needs updating though because it does state that JSX factory functions work using JSX.ElementClass. Potentially JSX.ElementClass can and should be deprecated now that JSX.ElementType exists.


2048 game added for hacktoberfest 2022

2048 game added under hacktoberfest 2022, please have a look at it and merge it

still files missing, please check committed files before creating pr

no rush, I would suggest you to first learn basic git commands

That's what I am doing right now, Thanks


[New game]:  Asteroids 3D

🎮 Game Request
Implementing a 3D software renderer for rendering asteroids.
Point down the features
The game features a player-controlled spaceship that can move and shoot bullets. The goal of the game is to destroy the asteroids by shooting them with bullets. The asteroids move around the screen and can collide with the player's spaceship. The game also includes explosions and visual effects.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @sabhisharma-ise !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @sabhisharma-ise ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Allow turning off vibration

Is your feature request related to a problem? Please describe.
When making this app available to my partner, she didn't like the vibration caused by executing actions.
Describe the solution you'd like
Add an ability to disable vibrations, either in the app's IQ store configuration or in the dashboard definition
Describe alternatives you've considered
Turn off the vibration globally in the watch, this is not desireable to my partner
Additional context
~~

Include: Fix a dereferencing null bug in HomeAssistantService.mc
Amend this:
var entity_id = data.get("entity_id");
if (entity_id == null) {
    entity_id = "";
}

To this:
var entity_id = "";
if (data != null) {
    entity_id = data.get("entity_id");
    if (entity_id == null) {
        entity_id = "";
    }
}

Wow, thanks for the quick followup! :partying_face:


When you press F5 frequently and quickly to refresh the page, the application will crash

The information when the application crashes is shown in this picture

Based on my testing, there doesn't seem to be an issue.
https://mudblazor-s.dotnet6.cn/pages/products

After my continuous testing, the bug caused by this FluxorComponent component crashed the program, but what is the purpose of this component. I deleted it from the program, but I didn't find that it affected the program

Yes, I found it too, so I removed Fluxor in this project

I have fixed it, see fluxor branch

Thank you for your efforts！


Please add star counters and comments!

like how scratch does it you know

I remember that a while ago, me, Omay and Leo discussed this, the conclusion was: It's not a good idea, because we have many beginners in the gallery, a game with few reactions could demotivate

@Patcybermind Because you're asking for two different features, can you break this into two issues? One requesting star counters and one for comments? And clearly describe the feature you're requesting so anyone reading can understand without knowing what scratch does?

ok i will

and ok lucas


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/386 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 1ba498d:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

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

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-02-04-19-58-02 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-02-04-19-58-02

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Error: Quickstart: Run a Spark job on Azure Databricks Workspace using the Azure portal

when you follow the steps listed in this section. You get the error as attached "error.jpg" once you try to run the cell to read the data into dataframe.  I tried on US West 2 initially. I got the error.  I google for answer and most reply talk about time settings. I did try to restart the spark cluster but it is same error. I checked and the dataset seem to reside in US East. Hence, i delete everything and rebuild using US East region, hopefully no time sync delay. However, same error appear.

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

ID: 355fba0e-958e-f572-18c2-892c91d20b13
Version Independent ID: 7fe76247-c969-2068-2c3c-bf327fbbe39e
Content: Quickstart - Run a Spark job on Azure Databricks Workspace using Azure portal
Content Source: databricks/scenarios/quickstart-create-databricks-workspace-portal.md
Service: azure-databricks
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

@gohsoonheng  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

support-request

Can also confirm I am also having this issue - is there any update on this being fixed?

#please-close

#please-close


Cannot update since v1.33.1

Hey, I use docker-compose and since 1.33.1 I can't update anymore.
Executing docker-compose pull and docker-compose up -d --force-recreate  doesn't update my version number in the web panel anymore.
This has always worked beforehand. Is the docked image not updated?
I use the default docker-compose.yml.
Really like the project thanks for your great work :).

We had an error in the last version where we had the wrong version number. It should be fixed in the latest v1.36.0

I just tried to pull new images and still shows me at 1.33.1.  What am I missing?  Thanks

I just tried to pull new images and still shows me at 1.33.1. What am I missing? Thanks
Can confirm. Same issue here

@cirrusflyer are you using this image in your docker-compose.yml ?
ghcr.io/mikecao/umami:postgresql-latest

Yes, but my install wasn't mission critical, so I just started completely over and working now.

Got the same issue, but found the solution :
My docker-compose file was referring to
ghcr.io/mikecao/umami
but now, docker images are hosted on umami-software org, instead of mikecao account.
Just replace base docker image path with this line, and it should be ok :
ghcr.io/umami-software/umami

Solution:
Replace ghcr.io/mikecao/umami:postgresql-latest with ghcr.io/umami-software/umami:postgresql-latest
in your docker-compose.yml.


Using time instead of chrono

Hey @edg-l,
I wanted to ask if you are interested in having time as an alternative to chrono?
I already made some changes in my fork (https://github.com/Atrox/sitewriter/commit/c10a05e36633d047f09abd093af8efb718914295) but I would assume you wouldn't want to merge this, as it currently replaces chrono completely. Would you be open to have time as a feature flag?

I would be open if you make a pr, otherwise i can do it when i find some free time.
Sorry for the late response 😅


Make row limit configurable

I'd like to bump it from 100 to 1000 for another project.

Hard-coded here at the moment: https://github.com/simonw/django-sql-dashboard/blob/504af12638a1d193c45919ad97f99f8e17c07400/django_sql_dashboard/views.py#L147-L156


bug: pod-gateway crashing randomly

Crashes cause outage of any containers using pod-gateway, requiring (afaik) a restart of the pod before it can recognize the "new" pod-gateway that relaunched.

kubectl describe and log show no faults.  Pod restart hasn't happened for 4+ hours, and no change was made, other than all containers (4 total 🤔) not being able to access the restarted, "new" container.
downloads-gateway-pod-gateway-85dd5cbb76-gmwf6           3/3     Running   4 (4h35m ago)   10h

trying e012ca06a36bdde2632cb2d1e67c6a7b6a2f5674 because maybe this is a resource constraint issue somewhere?  radarr and sonarr don't need to use the VPN either way.

https://github.com/qdm12/gluetun/issues/641
My hunch is that the container is restarting due to wireguard failures upstream.  I'm attempting to change the VPN to somewhere geographically closer.  This won't fix the bug above, but may reduce occurrences of the symptoms.

downloads-gateway-pod-gateway-5b5989fbc8-ft586           2/2     Running   0               27h

looking like the hunch was correct.  No pod restarts after changing VPN locations, along with no VPN rebuilds in the logs.


How to disable "Power BI Desktop infrastructure update" preview feature

[Enter feedback here]
Is there any command-line options during installation for disabling "Power BI Desktop infrastructure update" preview feature?

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

ID: e2102c86-5037-0609-9dd3-a1487732df3f
Version Independent ID: 73cfef71-a511-5ba2-b7b1-fa02a58a9e15
Content: Get Power BI Desktop - Power BI
Content Source: powerbi-docs/fundamentals/desktop-get-the-desktop.md
Service: powerbi
Sub-service: pbi-fundamentals
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for posting – note that we can only answer feedback related to the documentation, and can’t provide direct support or respond feature requests / how-tos.
Your best venue for getting an answer to your question is from the community (https://community.powerbi.com) or from support at https://support.powerbi.com. You can also provide feedback using the Give Product Feedback button at the bottom of the article page.


Mention the existence of the Xcode7 branch in the README

As suggested in #337. Let's not merge this until that work has been rebased and put onto the Xcode7 branch.

Awesome, thanks for the writeup, @pivotal-brian-croom!


Karma ranking

An update for the karma module that can show karma ranking would be cool.

 Karma ranking


Error using goTo

TypeError: Cannot read property 'canenter' of undefined
at Scope.a.goTo (assets/plugins/angular-wizard/angular-wizard.min.js:7)
When I click on the Tabs, it shows error.

@narangrishab  Can you create a fiddle?

'use strict';
/* Controllers */
angular.module('app', ['mgo-angular-wizard'])
.controller('FormWizardCtrl', ['$scope', 'WizardHandler', function($scope,WizardHandler) {
     $scope.finished = function() {
        alert("Wizard finished :)");
    }

    $scope.logStep = function() {
        console.log("Step continued");
    }

    $scope.goBack = function() {
        WizardHandler.wizard().goTo(0);
    }

    $scope.getCurrentStep = function(){
        return WizardHandler.wizard().currentStepNumber();
    }
    $scope.goToStep = function(step){
        WizardHandler.wizard().goTo(step);
    }

}]);

That's my Angular JS code for form wizard. Would this work? or do you want a fiddle in specific?

@narangrishab Can you make a fiddle so I can play around with it? I think I see the issue but I would know for sure if I could click around.

this.goTo = function(step) {
                var enabledSteps = $scope.getEnabledSteps();
                var stepTo;
                //checking that step is a Number
                if (_.isNumber(step)) {
                    stepTo = enabledSteps[step]; ...

According to this code goTo uses only enabled steps. This was issue in my case.

I think this happens when using title instead of wz-title. Someone needs to update the documentation. It still says title in places.

@createthis @Adverse191 @narangrishab This issue has been fixed with the latest release.


HR: COSE Payload is missing expiry date

@TKlauenberg
@daniel-eder
@kristinaleko
FYI and kind attention.
HR/2DCode/raw/1.json
and
HR/2DCode/raw/3.json
COSE Payload is missing mandatory expiry date: Key 4.

@kristinaleko any update on this?

@SchulzeStTSI @bhavin-qryptal  the test files have been updated yesterday , it should be resolved now.

@kristinaleko thanks you - the automated check for HR passes, so I'll close this issue.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1839

Questions ?
Please refer to the Backport tool documentation


Documentation for @PropValidator

It would be nice to mention in documentation that validator method should return boolean, i.e.
@PropValidator(propertyName = "size")
boolean sizeValidator(String value) {
    return "large".equals(value) || "small".equals(value);
}

Also declare propertyName as default, so it would be possible to use
@PropValidator("size")

Indeed, and the annotation processor should probably fail if it does't return a boolean. I add this as improvements.
If you have time and want to try we also welcome external contributions ;).

@adrienbaron Not sure I can contribute currently with the code, but I have such plans for 2018.

Ok I'll see to do this then 😉


Integrate AgentKeepAlive fix into botframework-connector

High volume azure hosted bots can start getting timeouts due to an SNAT issue.  We have a blog post for how to fix this but I think we could build the fix into the connector such that's it easier to turn on and configure.  I'm not sure it should be on by default but I'm all for making it easy to enable.

The challenge here is to get both proxy support and keep-alive working together. It seems that now you can have just one or the other.

Guys, any news on this? I'm doing a benchmark with the partner and we are seeing 1/2 of the performance from a Node.js bot compared to a .NET Core one. If somebody can point me where this call is made I could try to implement the change to check if this is the cause of the performance difference I'm seeing and submit a PR.

Hey @damadei
Thank you for your willingness to help out with this issue. I'd like to work with you it, and I've emailed you offline.

It seems that the reason BotBuilder-dotnet does not have these issues is due to the caching of ConnectorClients https://github.com/Microsoft/botbuilder-dotnet/blob/master/libraries/Microsoft.Bot.Builder/BotFrameworkAdapter.cs#L59 as well as using a static HttpClient https://github.com/Microsoft/botbuilder-dotnet/blob/master/libraries/Microsoft.Bot.Builder/BotFrameworkAdapter.cs#L886  These two patterns, or something similar, should also be implemented in BotBuilder-js.

@EricDahlvang https://github.com/Azure/ms-rest-js/issues/308 and https://github.com/axios/axios/pull/1831

Now that we are off autorest, we can modify the code that could address this.  moving out of 4.5

This is still blocked; the last release of the 1.x line of @azure/ms-rest-js does not contain a way to inject a custom Agent with keepAlive configured to true (AxiosHttpClient.sendRequest()).

Actually, previous comment only applies for using the built-in Node.js HttpClient (AxiosHttpClient in 1.x of ms-rest-js).
If https://github.com/microsoft/botbuilder-js/issues/2013 is addressed and ServiceClientOptions is surfaced to developers, they would be able to provide their own HttpClient which could use their own HTTP request library with Agent support.

With https://github.com/microsoft/botbuilder-js/issues/2013 merged, it is now possible to provide a custom @ms-rest-js.HttpClient as a parameter to BotFrameworkAdapter:
const adapter = new BotFrameworkAdapter({
    appId: process.env.MicrosoftAppId,
    appPassword: process.env.MicrosoftAppPassword,
    clientOptions: { httpClient: new CustomAxiosHttpClient() }
});

However, this is still very inconvenient and cumbersome to implement.  The AxiosHttpClient provided by the 1.x version of ms-rest-js contains some custom error handling, abort logic, stream support, etc. Much of this is not needed by the sdk, but in order to use agent keepAlive our recommendation for R9 will be to copy this file into the bot and modify axios.create() to include:
httpAgent: new http.Agent({ keepAlive: true }),
httpsAgent: new https.Agent({ keepAlive: true }),

We could make this easier.
Lastly, we need to consider options for providing keepAlive agents to QnAMaker, LUIS, and storage providers.

Hi Team,
i am facing one issue of connection reset an need the same requirement so that i can take a reference to implement the code base directly in my solution.please do Let me know if any input you can provide.

Hi @Bradrajkumar
Currently, the sdk provides and httpClient parameter in BotFrameworkAdapter's ConnectorClientOptions:
const adapter = new BotFrameworkAdapter({
    appId: process.env.MicrosoftAppId,
    appPassword: process.env.MicrosoftAppPassword,
    clientOptions: { httpClient: new CustomAxiosHttpClient() }
});

Here is a CustomAxiosHttpClient implementation:
customAxiosHttpClient_js.txt
Unfortunately, the sdk does not currently expose an agent parameter for QnAMaker or Luis implementations which are using node-fetch

🚀 https://github.com/Azure/ms-rest-js/pull/404 🚀


Synapse trustedServiceBypassEnabled setting not deploying through Bicep.

Bicep version
0.12.40
Describe the bug
Deploy Synapse Workspace through Bicep with trustedServiceBypassEnabled set to true. After deployment otherwise successfully finishes, the setting is "false", which is the opposite of what is declared in the template. Expected "Allow Azure services and resources to access this workspace" to be enabled.
To Reproduce
Deploy Synapse Workspace resource through a Bicep template file using resource group scope in either Complete or Incremental mode.
resource synapseWorkspace 'Microsoft.Synapse/workspaces@2021-06-01' = {
  name: synapseWorkspaceName
  location: azureLocation
  identity: {
    type: 'SystemAssigned'
  }
  properties: {
    azureADOnlyAuthentication: true
    cspWorkspaceAdminProperties: {
      initialWorkspaceAdminObjectId: '<ObjectID>'
    }
    defaultDataLakeStorage: {
      accountUrl: <SymbolicNameForDataLakeStorage>.properties.primaryEndpoints.dfs
      createManagedPrivateEndpoint: false
      filesystem: 'synapse'
    }
    publicNetworkAccess: 'Enabled'
    sqlAdministratorLogin: '<AdminName>'
    sqlAdministratorLoginPassword: '<LoginPass>'
    trustedServiceBypassEnabled: true
  }
}

Additional context
Also tried the trustedServiceByPassConfiguration resource type as described in documentation:
https://learn.microsoft.com/en-us/azure/templates/microsoft.synapse/workspaces/trustedservicebypassconfiguration?pivots=deployment-language-bicep
However that resulted in a NullRequest: Request was deserialized as null error.

If a property is being ignored, that is not a bicep specific issue. It's possible you need to use a different property and the property you are setting is being ignored silently (which is not great!)
@tlaur - can you open a support ticket to have this routed to the synapse resource provider team?

I see, so there is a possibility the documentation is not up to date on the correct property to use? Is opening the support ticket through the Azure portal the correct channel?

Yes opening the support ticket should result in docs get updating if that ends up being part of the issue.

Unfortunately it is not possible to submit a technical support ticket on Azure without a paid plan, which is something we do not have at the moment. I'm therefore at a bit of an impasse. Best I can do is a tweet or Stack Overflow.

Got it - I will share this internally with the synapse team and see if they can help.

Hi happy new year!
@alex-frankel I'm facing same issue, do you have any updates to share?

I got no response to what I shared internally. @sdib - are you able to open a support case?

The resource type should be 'Microsoft.Synapse/workspaces/trustedServiceByPassConfiguration@2021-06-01-preview'.
Ref: https://learn.microsoft.com/en-us/azure/templates/microsoft.synapse/workspaces/trustedservicebypassconfiguration?pivots=deployment-language-bicep

@coolswatish thanks for this but unfortunately it doesn't work.
Deployment fails with following error:
{
    "status": "Failed",
    "error": {
        "code": "NullRequest",
        "message": "Request was deserialized as null. "
    }
}

I tried with nested and non-nested resource declaration (using Bicep) result is same for both.
do you have it working on your side?

Hi @sdib,
I was able to reproduce the same failure as you have after configuring the trustedservicebypassconfiguration resource.
I found that the below firewall rule is equivalent and it works. Just add this in your template next to the Synapse workspace deployment.
resource windowsAzureIpsRule 'Microsoft.Synapse/workspaces/firewallRules@2021-06-01' = {
  name: 'AllowAllWindowsAzureIps'
  parent: synapseWorkspace
  properties: {
    startIpAddress: '<IP_ADDRESS>'
    endIpAddress: '<IP_ADDRESS>'
  }
}

Please note that it is important to keep the name AllowAllWindowsAzureIps otherwise the deployment will fail.


Make the compatibility matrix sections link to the build report.

Fixes #1561

Moved link to full build report from (1) to (2)
Made both of the matrix sections (platform and Swift version) links to the same report.

It looks like there are huge changes to the snapshots, but I double checked and the only visual changes apart from the moving of the link. It just makes a huge difference because the whole page shifts upwards.

I'm getting a bit of a weird wrapping behaviour:

I've run make build-front-end. It's resize-independent, i.e. it stays like this at any window width.
It's because I'm zooming out one step to get smaller fonts.
Also, should we maybe just call the link "All Builds"? Given the placement, that's really enough, isn't it?

I'm getting a bit of a weird wrapping behaviour
It's because I'm zooming out one step to get smaller fonts.

Yea it was only on smaller zooms and only in Safari. All the bugs are Safari-only these days 😢 I played with it and found a workaround, but then changed the copy instead which had the same effect.

Also, should we maybe just call the link "All Builds"? Given the placement, that's really enough, isn't it?

All Builds felt a little too short, but I changed it to "Full Build Results" which is slightly smaller and also fixes the Safari layout issue.


chore: Remove extra else

I know this is related to #245, but I decided to revert it. See https://github.com/vuejs/vue-next/pull/257
Please note that in general, I do not encourage style-related PRs. I understand the desire to contribute, but please also realize that style related changes are often subjective in terms of whether it improves the quality of the code - yet they still create the extra workload for the maintainers.

Thanks @yyx990803 for such detailed explanation. I understand your concern and will try to create some useful PRs :)


Let students see only lessons released

Each lesson has a date to be released. Now, students should see only the ones which already have been released.

Done.


GlobalStyles docs & performance

https://blazorstyled.io/globalStyles
@Styled.GlobalStyles["ColorHotPink"] no longer available in v3.
Should be replaced with @Styled.GetGlobalStyle("ColorHotPink")
Edit: Also it's extremely slow (somewhere between 5x to 10x slower) compared to previous version and does not work very reliably (sometimes it's like styles weren't even loaded).

I haven't been able to update the docs site due to: https://github.com/chanan/BlazorStyled/issues/102


How do you optimally perform a data collection for TTS?

Are there good tools for this?
How are the data requirements different for other kinds of TTS systems out there?

https://github.com/MycroftAI/mimic-recording-studio


[Bug] Line error  mismatch

After updating from the latest 12 to the latest 13 (13.1.2) I noticed that failures doesn't correctly print any of the trace.
Given a failure, this is the report in version 13
 FAIL  tests.js
 ✖ [ok], title, 123321 !== '123321'

const tap = require('tap')
const { required } = require('./payloads')

  --- expected
  +++ actual
  -"123321"
  +"123"

  at:
    line: 1
    column: 2309
    file: advertises/tests/patch.js
    type: Test
    function: tap.test
  stack: |
    Test.tap.test (advertises/tests/patch.js:1:2309)

this is the report in version 12
tests.js ............................................ 11/12
  ok
  not ok [ok], title, 123321 !== '123321'
    --- wanted
    +++ found
    -123321
    +123
    at:
      line: 10
      column: 9
      file: advertises/tests/patch.js
      type: Test
      function: tap.test
    stack: |
      Test.tap.test (advertises/tests/patch.js:10:9)
    source: >
      tap.strictSame(payload.user, '123321', `[ok], title, ${payload.title} !==
      '123321'`)

This is likely a failure in the sourcemap handling in NYC v14 vs v13.  Do you have a reproduction case?

const tap = require('tap')

tap.test('VALIDATE ok', async tap => {
  tap.equal([1, 2], [1], 'this will fail')
  tap.end()
})

tap.test('VALIDATE ok', async tap => {
  tap.equal([1, 2], [1], 'this will fail too')
  tap.end()
})

tap.test('VALIDATE ok', async tap => {
  tap.strictSame([1, 2], [1], 'this will fail too, too')
  tap.end()
})

the output it is a bit different than expected, same issue though:
FAIL  -----------/test.js
✖ this will fail

 -----/test.js
> 1 | const tap = require('tap')
 2 |
 3 | tap.test('VALIDATE ok', async tap => {
 4 |   tap.equal([1, 2], [1], 'this will fail')

 found:
   - 1
   - 2
 wanted: []
 compare: ===
 stack: |
   Test.tap.test (-------/test.js:1:1735)

 FAIL  -----------/test.js
 ✖ this will fail too

  ---------/test.js
> 1 | const tap = require('tap')
  2 |
  3 | tap.test('VALIDATE ok', async tap => {
  4 |   tap.equal([1, 2], [1], 'this will fail')

  found:
    - 1
    - 2
  wanted: []
  compare: ===
  stack: |
    Test.tap.test (----------/test.js:1:1909)

As you can see the output display the same line number but the column number it is different

This is a different issue.  In the example provided, the test itself is being run as coverage-instrumented code, munged by NYC, which is almost never a good idea.
Compare this:
$ tap -Rterse line-numbers.js
 FAIL  line-numbers.js
 ✖ this will fail

  line-numbers.js
> 1 | const tap = require('tap')
  2 |
  3 | tap.test('check the line number', async tap => {
  4 |   tap.equal([1, 2], [1], 'this will fail')

  --- wanted
  +++ found
   - 1
  +- 2

  stack: |
    Test.<anonymous> (line-numbers.js:1:1070)
    Object.<anonymous> (line-numbers.js:1:981)

 FAIL  line-numbers.js 1 failed of 1 720ms
 ✖ this will fail

Suites:   1 failed, 1 of 1 completed
Asserts:  1 failed, of 1
-----------------|----------|----------|----------|----------|-------------------|
File             |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
-----------------|----------|----------|----------|----------|-------------------|
All files        |      100 |      100 |      100 |      100 |                   |
 line-numbers.js |      100 |      100 |      100 |      100 |                   |
-----------------|----------|----------|----------|----------|-------------------|

with this, where line-numbers.js is excluded from NYC:
$ tap -Rterse line-numbers.js --nyc-arg=-x=line-numbers.js
 FAIL  line-numbers.js
 ✖ this will fail

  line-numbers.js
  2 |
  3 | tap.test('check the line number', async tap => {
> 4 |   tap.equal([1, 2], [1], 'this will fail')
    | ------^
  5 |   tap.end()
  6 | })

  --- wanted
  +++ found
   - 1
  +- 2

  stack: |
    Test.<anonymous> (line-numbers.js:4:7)
    Object.<anonymous> (line-numbers.js:3:5)

 FAIL  line-numbers.js 1 failed of 1 626ms
 ✖ this will fail

Suites:   1 failed, 1 of 1 completed
Asserts:  1 failed, of 1
----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |        0 |        0 |        0 |        0 |                   |
----------|----------|----------|----------|----------|-------------------|

NYC defaults to excluding any files in node_modules, test/*, __test__/*, *.test.*, and (iirc?) *.spec.*.
In your initial example, it looked like the file would've been excluded by NYC by default.
Do you have an NYC config file, or an nyc section in your package.json file?  Are these test files showing up on the coverage report?  If they're not, then something else is going on.
You can also try running with --no-esm to see if that changes the equation at all.

@milkandsour did you figure this out?


No need to add configuration manually

Hi. I did this months ago, but I forget to make a PR. This just adds the configuration to to the plugin so that it does not have to be added manually. Cheers.

Ok thanks! :pray:


Redeploy Azure resource to fix "The service is unavailable"

I tried to show my friend our beautiful project this evening, but Azure App Service is not cooperating. I think something is either wrong with Azure or wrong with the resource. I'll try to deploy again tomorrow.

It seems to work if I upgrade to the non-free tier, but I don't want to do that. I did a quick hack on Azure and it's working now...


Support for headless/server builds

Firstly, thank you for making and sharing this awesome plugin. I expect to be using it a lot!
Secondly, would you consider adding support for Godot headless and server builds?
This is especially useful for the running the plugin in headless CI/CD environments such as GitHub actions.
It should be as easy as adding "Server" alongside "X11" and "OSX" as headless/server builds are currently only supported on Linux and macOS.
I tested this change using a basic plugin.gd file with server/headless builds locally on my Linux laptop and on GitHub actions using this Godot headless Docker image (results here) , and everything seems to be working fine.

Thanks, glad that it helps!
My bad, I thought "X11" includes all Linux machine.
Will merge this PR when I get to my desktop.
Thanks for the contribution!


Getting AggGrid's state

Hey @PablocFonseca, thank you for such an amazing job on integrating AggGrid in Streamlit, I highly appreciate the efforts and happy to contribute if there are any known issues that need help from python side of things.
One task I am having hard time to wrap my head around is getting AggGrid state after a user interacts with it.
I.e., I have a multi-select to keep grouping consistent between page reloads or new data push.
# let user pick cols from dataframe she want to group by
if st.sidebar.checkbox("Enable default grouping"):
    default_group_col = st.sidebar.selectbox("Default group by: ", cols, 1)

# if any of columns are selected, apply it to aggrid and persist on page reload,
# as default_group_col state is persisted under the hood by streamlit
try:
    gb.configure_column(default_group_col, rowGroup=True)
except:
    pass

Now say a user groups by an additional column using AggGrid groupby feature, collapses some of the resulting groups and keeps the others expanded. I would assume AggGrid itself stores this state somewhere in client side JS. Is there a potential way to get stat state back to python in order to save it somewhere in a dict and persist between page reloads when AggGrid component is being redrawn or populated with new data?
Thanks!

I have a similar question. Is there a way to get the modified data back in python

check the example folder (e.g. two_grids.py)
to get modified data, you would use something like:
grid_return = AgGrid(df, key='grid1', editable=True) df = grid_return['data'] st.write(df)

The feature to save grid's current state is not implemented yet.
I just saw this post: https://blog.ag-grid.com/persisting-ag-grid-state-with-react-redux/#managing-state-in-ag-grid
So, it can be done. Unfortunately, I'm lacking the time to dig into this..

Hi. Was this feature implemented. Would you suggest what to edit in J's code to make this work?


⚠ Bofrost.be has degraded performance

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

HTTP code: 200
Response time: 1802 ms

Resolved: Bofrost.be performance has improved in f1195c1 after 36 minutes.


Mxnet Initializer equivalent

Hi there
I am working on an old mxnet code. (https://mxnet.incubator.apache.org/tutorials/nlp/cnn.html)
Here initialization is being done in the following manner:
Initializer(name, arg_dict[name]).... Now this has been deprecated. How can i re-write this in the new version ?
The reason for me to ask this question is that i can't find the version before which this was deprecated. hence , i cant find the documentation

The documentation indeed needs lots of improvement.
Did you try to type help(function_name) to check the documentation for the previous version and compare with the current version?


Naming inconsistency in output files / documentation

Hi @lazear,
First and foremost, thanks for the great work!
Continuing the conversation from compomics/psm_utils#31: It seems that internally, the _q suffix is indeed used as is also documented for the result.sage.tsv output:
https://github.com/lazear/sage/blob/5f95d454f9b126cf93b2ec96443f4aaa8a88f588/crates/sage-cli/src/output.rs#L62C21-L64
However, the header names use the _fdr suffix:
https://github.com/lazear/sage/blob/f55a9e525cf353de94e194428a3a5615d0cbab8c/crates/sage-cli/src/output.rs#L113C18-L115
Personally, I think the _q suffix makes more sense, but for backwards compatibility (which might not be so much of an issue yet), you could opt to keep the _fdr suffix.

I agree, the _q suffix makes more sense (and is correct). I think I initially changed it to fdr to clarify for any users that don't know what q-values are. I will leave this issue open for a week or so in case someone wants to voice opposition to using spectrum_q, etc instead of spectrum_fdr.

+1 for _q, I forget where I first came across this but when I see q in this context I immediately think: "adjusted FDR"


OwnTracks waypoints crash HA if you have Share Off

Home Assistant release (hass --version):
0.17
Python release (python3 --version):
Component/platform:
Owntracks
Description of problem:
Owntracks (at least on Android) crashed if it receives a waypoint enter/exit event without a description.
Looks like this is what the owntracks app sends if sharing is turned off
Expected:
I don't think HA can do much with an unnamed enter/edit event (Owntracks will already send a location update anyway) - but it should just output an error - and not crash
Traceback (if applicable):
01 20:08:16 homeassistant.core: BusHandler:Exception doing job Traceback (most recent call last): File "/home/pi/homeassistant/local/lib/python3.4/site-packages/homeassistant/core.py", line 794, in job_handler func(arg) File "/home/pi/homeassistant/local/lib/python3.4/site-packages/homeassistant/components/mqtt/__init__.py", line 90, in mqtt_topic_subscriber event.data[ATTR_QOS]) File "/home/pi/homeassistant/local/lib/python3.4/site-packages/homeassistant/components/device_tracker/owntracks.py", line 84, in owntracks_event_update location = data['desc'].lstrip("-") KeyError: 'desc'

Additional info:
Reported by @Nutti85 on gitter
I'll fix this.

This has been fixed in 0.17.


mypy compatibility: missing py.typed

Issue Type
Feature Request
Source
binary
Tensorflow Version
tf 2.8, tf 2.10
Custom Code
No
OS Platform and Distribution
Linux Ubuntu 20.04, macOS Ventura arm
Mobile device
No response
Python version
3.7, 3.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
mypy is one of the great tools that many people use to run type checking via type annotations. Unfortunatelly, tensorflow does not play very nicely with it. As specified in the examples, many tensorflow-based objects are seen as Any by mypy. This can lead to various unexpected (and confusing) behaviour in the code that depends on tensorflow.
Extra change required
IIUC this is an invalid type annotation according to mypy:
https://github.com/tensorflow/tensorflow/blob/bff338f421322c2ccd1d7e2c5e24ff6c1b0c133c/tensorflow/python/ops/ragged/dynamic_ragged_shape.py#L206
Changing to
           static_inner_shape: Any = None):

should solve the problem (of course a more specific type annotation would be better).
Proposed solution
I suspect that this is because a single file is missing to make tensorflow type annotations recognised by mypy: py.typed. Adding that file resolves the issue, and stops mypy from treating tensorflow entities as Any.
Please kindly let me know if I missed anything.
Standalone code to reproduce the issue
Basic example
import tensorflow as tf

reveal_type(tf.Tensor)

Without py.typed:
error: Skipping analyzing "tensorflow": module is installed, but missing library stubs or py.typed marker  [import]
note: Revealed type is "Any"

With py.typed:
Revealed type is "def (op: Any, value_index: Any, dtype: Any) -> tensorflow.python.framework.ops.Tensor"

More complicated example
(comments explain what is seen without py.typed)
import tensorflow as tf

class A(tf.Module):
    pass

class B(A):
    def foo(self) -> str:
        return "foo"

class C(B):
    def __init__(self, value: int) -> None:
        super().__init__()
        self.value = value

class D1(C):
    pass

class D2(C):
    def __init__(self, value: int) -> None:
        super().__init__(value)

    def do_something(self) -> int:
        return self.value

class D3(C):
    def do_something(self) -> int:
        return self.value

reveal_type(A())  # Reveals 'A' <- OK
reveal_type(B())  # Reveals 'B' <- OK
reveal_type(B().foo)  # Reveals 'str' <- OK
reveal_type(C(1))  # Reveals 'C' <- OK
reveal_type(D1(1))  # Reveals 'C' <- ??? 'D1' expected
reveal_type(D2(1))  # Reveals 'D2' <- OK but why?
reveal_type(D2(1).do_something)  # Reveals 'int` <- OK
reveal_type(D3(1))  # Reveals 'C' <- ??? 'D3' expected
reveal_type(D3(1).do_something)   # Reveals 'Any' <- ??? 'int' expected

With py.typed everything is as expected:
tf_mypy.py:36: note: Revealed type is "tf_mypy.A"
tf_mypy.py:37: note: Revealed type is "tf_mypy.B"
tf_mypy.py:38: note: Revealed type is "def () -> builtins.str"
tf_mypy.py:39: note: Revealed type is "tf_mypy.C"
tf_mypy.py:40: note: Revealed type is "tf_mypy.D1"
tf_mypy.py:41: note: Revealed type is "tf_mypy.D2"
tf_mypy.py:42: note: Revealed type is "def () -> builtins.int"
tf_mypy.py:43: note: Revealed type is "tf_mypy.D3"
tf_mypy.py:44: note: Revealed type is "def () -> builtins.int"

@sushreebarsa
I was able to reproduce the issue on Colab using TF v2.11. Please find the gist here and attachment for reference.
Thank you!

Could we please have an update for this?

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


group lesson buttons.

To have a cleaner UI and to encourage users to attempt challenges before asking for help, we need to group the help buttons in lessons.
There should only be three buttons in each lesson: "run the tests", "reset all code", "get help", and their wrapper element should get a button-group class to space the buttons out and improve lighthouse scores.
"get hint", "ask for help", "watch a video" buttons should be grouped under the "get help" button and displayed as a dropdown similar to the certification section on settings, or it could be a "dropup" to account for lessons that have a couple of tests or for mobile views.

No assignment needed. please proceed with submitting your solution in a pr.

I'll take this one.

@stefanosu go ahead

@thecodingaviator Let's not remove the help wanted label until we get at least one PR submitted.


Favorite

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?

If you'd like to see this feature implemented, add a 👍 reaction to this post.

That's too low information Closed as spam


PR: Update outline explorer when the syntax highlighter detects a change

Description of Changes

[x] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)
[ ] Included a screenshot (if affecting the UI)

Updates automatically  the cell name when the syntax highlighter sees a change
This is building on top of #9219 and #9082
Issue(s) Resolved

Fixes #
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
impact27

Hello @impact27! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/outlineexplorer/widgets.py:

Line 449:72: W291 trailing whitespace

In the file spyder/widgets/fileswitcher.py:

Line 591:1: W293 blank line contains whitespace

Hi @impact27 thanks again!
This depends on the other PRs right?

yes on #9219 and #9082

I added that in https://github.com/spyder-ide/spyder/pull/9219 as both needed similar code


IOS device Error while connect to server

It success run on android but when I run on ios, it error  " Error while connect to server" .
any solution ?

Hi @monyoudom , let me look into the issue. Thanks.


Validation tests

validation.js tests

Success: https://dev.azure.com/azure-sdk/public/_build/results?buildId=214095&view=results

File an issue about implementing client valiedation.

https://github.com/Azure/autorest.csharp/issues/357


NTR intracellular G-protein coupled receptor activity

Hello,
I came across some G proteins that are not on the plasma membrane, but rather in the nucleus (or even on the Golgi). See reviews: PMID:24568158 and  PMID:16902576.
However the term 'GO:0004930 G-protein coupled receptor activity' has a parent 'cell surface-receptor activity', so I cannot use it. I am not sure how to deal with this; but it would be nice if the general 'G protein.coupled receptor activity' remained under 'cell surface-receptor activity', since that's the general case.
Thanks, Pascale
Reported by: pgaudet
Original Ticket: geneontology/ontology-requests/11721

Function term no-longer has link to cell-surface receptor activity
Pathway term now includes gloss: The pathway can start from the plasma membrane, Golgi or nuclear membrane (PMID:24568158 and PMID:16902576).


feat(tabs): paginate tab header when exceeds width

Shuffled the logic so that the majority of scrolling stuff is evaluated on content check and checks are only made conditionally (e.g. tab list changed, selected index changed, etc)
Really appreciate the reviews, the amount of layout reflows has dropped significantly.

Removed the internal comment.
I'd like to add a reference drawing into the folder to help people understand better about how the element container widths/offsets work. Here's the WIP: https://docs.google.com/drawings/d/1fhtiM-NabWhKP8pVsz8hCAQkzWz1QXrUG0LH-xQdpqI/edit?usp=sharing

Property {'_disableScrollBefore', '_disableScrollAfter', '_handleKeydown'} is private and only accessible within class 'MdTabHeader'

Okay, should be good to merge!


Add minimum node information to project

Library Affected:
workbox-sw, workbox-webpack-plugin, etc.
Issue  Description:
when running the webpack.config I am getting the following error:
 ... node_modules\workbox-webpack-plugin\build\index.js:32
class WorkboxBuildWebpackPlugin {
^^^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:404:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous>
    at Module._compile (module.js:397:26)
    at Object.Module._extensions..js (module.js:404:10)
Process terminated with code 1.

When I manually add 'use strict' to

node_modules\workbox-webpack-plugin\build\index.js

it gets resolved and throws an error from another file.
webpack.config.js https://github.com/dhananshan/PWA.NetCore/blob/master/PWA.NetCore/webpack.config.js
Node: 8.0.0
npm: 5.0.0

OK, It's because visual studio has its own node which uses an older version. I synced with global node now its working, but yet the issue exist with node < 6v.

@addyosmani @jeffposnick should we be adding in a minimum version of node to our package.json? Would that have helped with this?

We have
"engines": {
  "node": ">=4.0.0"
}

in the package.json for workbox-webpack-plugin.
We have
"engines": {
  "node": ">=6.0.0"
},

in our top-level package.json for the monorepo. In general, we've been assuming node 6+ throughout the code, and have been liberal with using ES2015 features.
At the same time, create-react-app still supports node 4, and the longer-term goal is to start using workbox-webpack-plugin there. So perhaps we should add Babel transpilation with the node 4 preset into the workbox-webpack-plugin build process?

Related: https://github.com/GoogleChrome/workbox/issues/603

i guess it shouldn't be a big change adding it into the babel process

Should we make it a blanket node-4 support for CLI, build and webpack-plugin?

Everything has node 4.0.0 in the node modules so I think we are ok to close this issue now


Azure policy Deploy SQL database vulnerability assessment is now deprecated

What happened? Provide a clear and concise description of the bug, including deployment details.
The Azure policy Deploy SQL database vulnerability assessment which is in the Deploy SQL database built-in security configuration policy set is now tagged as deprecated.
Can the policy set be updated with the latest policy to replace that?
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
What was the expected outcome?
No response
Relevant log output
No response
Check previous GitHub issues

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

Code of Conduct

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

Hi @amp-pds! Please note that the initiative in question has been updated, and there is a new version available (and deployed by ALZ as of the latest release) - the new initiative is https://www.azadvertizer.net/azpolicyinitiativesadvertizer/Deploy-Sql-Security_20240529.html (the old initiative has been deprecated).


Add support of ESMFold on HPU

What does this PR do?

Add support of ESMFold on HPU
This PR modified some implementations on modeling_esmfold.py and modeling_utils.py to fit in HPU. These changes are either to optimize the performance on HPU, or make sure the model can run on HPU correctly.
A example demo was also created under example/esm folder to show how to do protein folding prediction with ESMFold on HPU. The content of this demo is same as the one from this link,  https://colab.research.google.com/github/huggingface/notebooks/blob/main/examples/protein_folding.ipynb, except adding several lines of code to run it on HPU with optimum-habana. The output of the demo is a pdb file. It contains the predicted 3D positions of the protein's atoms. The values of these positions have been verified with the values that got from GPU.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@regisss, I have changed the folder name accordingly and verified the application works as we expected :)
Thanks again for your quick response.

@bzhu-habana Have you tried mixed precision with ESMFold?

@regisss Yes. We tried mixed precision on HPU too. We saw some (minor) numeric difference compared to fp32. That's expected behavior. But because we didn't find a criterion to define if that numeric difference is acceptable or not, also one of our customer cares about the accuracy of protein folding very much, they prefer to use fp32 only. So we decided to not add mixed precision support.

@bzhu-habana Hi Bob, since SynapseAI v1.11 has been released, I was wondering if there is anything to do with those two workarounds:

https://github.com/huggingface/optimum-habana/blob/d3f6c069dcca41efc51d6105ca3aab545c80991c/optimum/habana/transformers/models/esm/modeling_esmfold.py#L252
https://github.com/huggingface/optimum-habana/blob/d3f6c069dcca41efc51d6105ca3aab545c80991c/optimum/habana/transformers/models/esm/modeling_esmfold.py#L311
?

Hi @regisss , I will try to verify if we can remove these two WAs on the 1.11.0 once I get the chance.


Fix multiline comment spacing on TOML configs

This PR fixes multiline comments on TOML not having the one space padding on their other lines

This is something that should probably be done in the annotation processor in QuiltConfig itself. I would also like to point at that you can use multiple @Comment annotations for multiline comments.

With multi-line strings in Java 17 it doesn't make sense to require splitting into multiple annotations

With multi-line strings in Java 17 it doesn't make sense to require splitting into multiple annotations

Agreed, the functionality in this PR makes sense. I just thought it was worth mentioning that there is an existing solution for multiline comments.

Yeah, I made this PR so that @Comment played nicer with Java's multiline strings; I did strumble on the possibility of using multiple @Comment while making this PR, but yeah, I prefer the triple double-quotes

https://github.com/QuiltMC/quilt-config/pull/3 succeeds this pull request.


On Linux, it's not possible to monitor task changes in subdirectories, but it is possible on Windows.

Running into this same issue myself. On Windows, the directory is monitored using ReadDirectoryChangesW, which reports changes for the contents of the directory and all subdirectories. On Linux however, it uses inotify, which reports changes in the directory but not subdirectories. https://man7.org/linux/man-pages/man7/inotify.7.html.
Simplest fix here is at least to document it in the README so that users don't expect the same behavior across platforms.


Page Carousel - Remove Blue Indicator When Only One Page

Bug Description
When there is only one page there shouldn't be a blue indicator on the page thumbnails in the carousel
Expected Behaviour
The blue line shouldn't be there.
See figma for examples
Steps to Reproduce

View a single page story

Screenshots

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

@samitron7 Should the blue line still show on hover?


feat: add a simple redux counter app

@SethDavenport I removed the old flux ngcourse-next based application and put a simple redux counter application instead.
Next step would be to port the react-redux-seed application in here

I'm fine to :shipit: the other tweaks/etc can come in as other PRs - but this gives it a good start.


Announcements

Description
Added announcements table to database schema, and seed file
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[x] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[x] Heroku database shows new table

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

 Add table for announcments to database schema and seed table


Implement _ pattern (#148)

Closes #148.
Closes #151.

Alright, time to get this merged! Thank you once again for taking your time to contribute.  Many thanks for doing some proper testing on records, it makes me a lot more confident it'll be a feature you can rely on.


replace node-sass by dart-sass in sandpack

Discussed in https://github.com/codesandbox/sandpack/discussions/613

Originally posted by Chris-Kin October  8, 2022
There's node-sass(which is deprecated) in yarn.lock, and it's required by<EMAIL_ADDRESS>In<EMAIL_ADDRESS>node-sass has been removed. Maybe we should update package-build-stats to 7.3.11 or higher version?

Hey @Chris-Kin, it looks doable. Would you like to give it a try and update it?
Thanks

Hey @Chris-Kin, it looks doable. Would you like to give it a try and update it?
Thanks

I'll take a try~

من المتوجب تحديث احصائات الحزمه وبنائها الى 7.3.13


Jar files contain different code than source files

The ZabbixAgent.java  source code it says:
    public void setServerAddress(String serverAddress) {
	this.serverAddress = serverAddress;
}

In the ZabbixAgent.class contains the code:
public void setServerAddress(InetAddress serverAddress) {
	this.serverAddress = serverAddress;

This makes the ExampleActiveAgent causing an error.

What's in the repository is a newer version than what's in Maven Central. Either build from source and use that version, or use the version in Maven Central?


removed an extraneous whitespace

Spotted while reading the printed book, which I'm really enjoying -- thanks!

Thanks!


[skip ci] fix images

Also replaced new MethodHook() with new PinePatchFn(callFrame -> {})

<3

Wrong button

tfw fix settings.gradle

tfw fix settings.gradle

Haha, always forgetting to change back settings.gradle


Supported OSes for the first release are not clear

In D2.1 we state that:

The toolkit should aim at running on all the major system platforms (Windows, Linux and macOS) and embedded systems.

However, currently, we ran tests only for Linux. Are we going to only support Linux or do we plan on supporting other OSes as well? Should we target only Linux in the first release? The majority of robotics systems are developed using linux (when an OS is used), so this can be used as an argument to support this decision. However, I am afraid that if we completely exclude the other platforms, it would be difficult to support them later and major code restructuring might be needed (e.g., if some libraries are not available on Windows). Another solution would be to support Windows indirectly, e.g., using the WSL.

OSes that are going to be supported for each release has been specified, so I am closing this issue.