Azure Blob default content-type should be application/octet-stream

Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the Azurite was used?
3.2.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
dockerhub
What's the Node.js version?
10.15.3
What problem was encountered?
After uploading a blob, the content-type is returned as application/xml; charset=utf-8, however, the Azure Blob default in this case is application/octet-stream (https://docs.microsoft.com/en-us/rest/api/storageservices/get-blob-properties).
Steps to reproduce the issue?

Upload a blob with no x-ms-blob-content-type set
Call GetBlobProperties and examine the Content-Type

Have you found a mitigation/solution?
No. The only workaround is to always explicitly set x-ms-blob-content-type to application/octet-stream.

@timuralp
Thanks for reporting the issue!
We will consider to fix it in a future release.

@timuralp
We can't repro this issue on 3.3.0-preview.
We have tried to upload a small Block Blob(<4MB), a big Block blob(>500MB), and a page blob. all works well, and has default content type is application/octet-stream
And in code, you can see the default content type is also right: https://github.com/Azure/Azurite/blob/df5bf1dd57162f7722cc861124c9d7c6c9b71352/src/blob/handlers/BlockBlobHandler.ts#L37
In Rest API, there are 2 header can set Content-Type: x-ms-blob-content-type , Content-Type. Please check you have not set any of them. The created Blob only in default contenttype when you don't set any of the 2 hearders.

@blueww I tried to reproduce again and wasn't successful. I went through a few versions of Azurite and checked the commit history -- I'm not sure how I encountered this error. Thanks for checking it and apologies for the invalid report!


⚠ Bofrost.lu has degraded performance

In 0587423, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1638 ms

Resolved: Bofrost.lu performance has improved in 1f83e22 after 1 hour, 12 minutes.


TypeError: init() missing 1 required positional argument: 'loop'

$ PLAYWRIGHT_WS_URL=wss://playwrightserver.herokuapp.com/ws python ex.py
Traceback (most recent call last):
File "ex.py", line 4, in
with playwright_browser('chromium') as browser:
File "D:\Program Files\anaconda3\lib\contextlib.py", line 113, in enter
return next(self.gen)
File "D:\Download\audio-visual\saas\deploy\playwright-python-playWithWebSocket\with_playwright_browser.py", line 11, in playwright_browser
with sync_playwright_remote(ws_endpoint) as playwright:
File "D:\Download\audio-visual\saas\deploy\playwright-python-playWithWebSocket\playwright_remote_context_manager.py", line 41, in enter
self._connection = Connection(
TypeError: init() missing 1 required positional argument: 'loop'

It seems you are using older version of example code in https://github.com/YusukeIwaki/playwright-python-playWithWebSocket
It is already outdated and not compatible with recent playwright >= 1.15
You would have to upgrade the code by refering the README of this repository.


Handle malformed coding in ResourceHeader

Coverage: 93.694%. Remained the same when pulling 265d9a3082f77fdadda0c49f35b69af456b0335b on cody-handle-malformed-coding into 1bed93bf67a9d0e9f5eb2b4c7d601c5c6a17e005 on main.


Using meshes provided by example-robot-data

Following recent discussions, I propose to move forward in  the direction of using meshes provided by example-robot-data instead of native description packages.
I will propose a pull request handling robots for which I will have tested that this does not break anything when loading models.
I also propose to revert commit ed85b87 since @cmastalli uses the lighting provided by the models.

Sounds good for me.
Thanks for taking care @florent-lamiraux

Done.


[WIP] Fix NRT test failure due to increased overhead when running in coverage

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2612   +/-   ##
=======================================
  Coverage   86.31%   86.31%
=======================================
  Files         320      320
  Lines       66708    66708
  Branches     7537     7537
=======================================
  Hits        57578    57578
  Misses       7915     7915
  Partials     1215     1215


remove invalid ovs build option

Pull Request

[x] Make sure you have followed Kube-OVN Code Style.

What type of this PR
Examples of user facing changes:

DEB BUILD OPTIONS will be reset by make debian-deb, it can be removed.

Which issue(s) this PR fixes
Fixes #(issue-number)

dist/images/Dockerfile.base-dpdk should be updated.


Player stalls when seeking on LIVE edge

Have you read the FAQ and checked for duplicate open issues?
Yes
What link can we use to reproduce this?
https://shaka-player-demo.appspot.com/demo/#audiolang=it-IT;textlang=it-IT;uilang=it-IT;panel=CUSTOM CONTENT;build=uncompiled
Content URL sent at<EMAIL_ADDRESS>What version of Shaka Player are you using?
v3.1.0-uncompiled
What browser and OS are you using?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36
What did you do?

play content
wait for content starting to play
click on the negative offset to seek to live edge

What did you expect to happen?
Player buffering for some time and then start playing again.
What actually happened?

Player stalls and from Network I see that fetches "manifest.mpd" continuosly without fetching segments.

@llooz, I get "HTTP 403 access denied" when I try to play the content you sent us privately.  Can you please enable access or provide us with a means to authenticate for this content?
@defnull, you're close, but streaming.bufferingGoal is not how much we need to start playback.  It's how far ahead we attempt to get before we stop fetching new segments, and does not influence startup or buffering at the live edge.  If the distance to the live edge or VOD duration is less than bufferingGoal, it doesn't do anything.
The streaming.rebufferingGoal setting is what we need to start or resume playback.  In DASH, we also consider the manifest's minBufferTime attribute, which you can disable with manifest.dash.ignoreMinBufferTime.
You should also be aware that there are effectively two different live edge concepts: one for buffering (availability), and one for presentation to the user.  The DASH "availability window" means "what's on the server".  This is the "true" live edge, and we can buffer up until that point.  What we show the user as the live edge, though, is offset from this by the "presentation delay".  DASH has a suggestedPresentationDelay attribute to tell the player how far these two should be apart, and this is the maximum we can buffer ahead of what the user is seeing.  If it's too small, the player can never achieve "live" in the UI.  If it's too large, buffering is improved at the cost of increased delay of the live event from camera to screen.
You can use manifest.defaultPresentationDelay to set the presentation delay used when there isn't one specified in a DASH manifest, and you can use manifest.dash.ignoreSuggestedPresentationDelay to ignore the manifest's presentation delay so that only manifest.defaultPresentationDelay will be used.

Thanks for the detailed explanation. In my tests, the manifests states suggestedPresentationDelay="PT2S" and minBufferTime="PT4.0S". This is what ffmpeg outputs for a 2-second segment size. My shaka config sets streaming.bufferingGoal: 4 and leaves the other values to their defaults.
If I understand you correctly, then shaka should refuse to play until at least 4 seconds are buffered (as required by manifest.minBufferTime=4s, which overrules the smaller streaming.rebufferingGoal default of 2 seconds). Clicking on the PresentationTimeTracker component should jump to the presentation live edge, which is 2 seconds behind the availability live edge (honoring manifest.suggestedPresentationDelay=2s). This is too far, and we need 4 seconds buffered minimum.
If the PresentationTimeTracker display is relative to presentation live edge, the player should be able to start playing at -00:02, because 2 seconds behind presentation live edge means 4 seconds behind availability live edge which is enough to satisfy minBufferTime (given a fast internet connection and nearly instant segment downloads). But there is also minimumUpdatePeriod="PT2S" in the manifest, which means that both live-edges jump in 2-second steps. Is this the reason I see the player buffering until -00:03 or -00:04 is displayed, instead of -00:02?
(Sorry for hijacking this issue, I realize that I am asking questions better suited for a mailing list).
To get on-topic again: If the presentation live edge cannot be possibly satisfied because the suggested presentation delay is larger than the minimum buffer size, then perhaps PresentationTimeTracker should be made aware of that and instead work relatively to the satisfiable live edge instead of the suggested one? I'm not sure if this is @llooz problem, though. If not, it might be worth discussing in a new issue?

Clicking on the PresentationTimeTracker component should jump to the presentation live edge, which is 2 seconds behind the availability live edge (honoring manifest.suggestedPresentationDelay=2s). This is too far, and we need 4 seconds buffered minimum.

That appears to be true.  I thought that we would see "buffered to the live edge" as sufficient without meeting the rebufferingGoal / minBufferTime requirement, but that appears not to be the case.  shaka.media.BufferingObserver is completely disconnected from the knowledge that we've hit the live edge (shaka.media.StreamingEngine).  I may have been remembering the way things were in an older version, back when StreamingEngine was more complex (if you can believe that).

But there is also minimumUpdatePeriod="PT2S" in the manifest, which means that both live-edges increment in 2-second steps. Is this the reason I see the player buffering until -00:03 or -00:04 is displayed, instead of -00:02?

That sounds right.  If the manifest uses SegmentTemplate@duration (fixed duration segments), then the update period will not matter.  But if it uses SegmentTimeline (each segment described explicitly), then the update period matters.  Without an update, we don't have a description of the segment, and we can't fetch it.  (As the code stands today.  Maybe some predictive fetching would help, but that would be a feature request.)

perhaps PresentationTimeTracker should be made aware of that and instead work relatively to the satisfiable live edge instead of the suggested one?

That might make sense.  The API that drives this part of our provided UI, as well application-specific custom UIs, is player.seekRange().  This, in turn, is driven by shaka.media.PresentationTimeline.  So the adjustments to the live edge would need to be made in PresentationTimeline.  It may be as simple as using the max of presentationDelay and rebufferingGoal / minBufferTime, but as rebufferingGoal can be dynamically adjusted by the app during a playback session, this would have to be adjusted any time the player config changes.
Interested in sending a PR?

@llooz, sorry for the distracting side-conversation with @defnull.  If you can provide us access to your content (still getting HTTP 403), then we can test to see if @defnull's suggestions would solve your issue.
Alternately, you can try setting a higher presentation delay:
player.configure({
  manifest: {
    defaultPresentationDelay: ENTER_DELAY_HERE,
    dash: {
      ignoreSuggestedPresentationDelay: true,
    },
  },
});

Or you can set a lower rebuffering goal:
player.configure({
  manifest: {
    dash: {
      ignoreMinBufferTime: true,
    },
  },
  streaming: {
    rebufferingGoal: ENTER_REBUFFERING_GOAL_HERE,
  },
});

Or both.  @llooz, please let us know if these suggestions help, and please let us know when/how we can access the content.  Thanks!

@joeyparrish sorry for the delayed response, unfortunately the content has some geoblocking restriction and can be accessed only from Italy
I will try to check next week with the content provider if there is a way to get an url without restrictions for testing purposes

We can VPN through Italy if that is all that is required.  Thanks!

The problem is that when we can't find the segment, getIteratorForTime returns an iterator with an index of -1, which causes problems streaming.

@llooz The latest release has several changes related to this, it might be worth testing if it has been resolved.

@llooz, can you please retest with v3.0.12 or v3.1.1?  This may be resolved now.

@joeyparrish @avelad  I've tested again with the same live content on the demo app with v3.1.1.
When I click on the negative offset it buffers until the offset reaches -0:05 and then plays without stalling forever, so it seems that this issue has been resolved 🥳


Poor documentation on App Framework 3.0

Hi,
Global documentation is missing on this project : about App Framework 3.0 for example.
This url : http://app-framework-software.intel.com/ presents the basic idea, with short blocks of code, but should at least contain, in addition :

the why of the evolutions since v2.x: why use jQuery now ? and why not jQueryMobile ? or Zepto ? or other general choices...
a clear explanation about what files to include in the code, and what role they have.
a step by step tutorial example, with directories and files structure for each step (i have in mind the excellent AngularJs tutorial example, for example)
the same kind of documentation for each plugin.
and a whole block of precisions on the examples included in the Intel XDK, with information about which version it uses etc...

As is, I've been trying to use v3.0, but couldn't go any further because of mistakes on the website. So, it was a waste of time as it makes us unable to get started quickly/at all with App Framework v3.0.

Quickstart guide is at http://app-framework-software.intel.com/documentation.php
API is at http://app-framework-software.intel.com/api.php
UI Components are at http://app-framework-software.intel.com/components.php

Thanks for those links Ian, i knew these by the way.
But they're exactly illustrating what could be improved : take for example the UI Components page.
We arrive at v3.0 documentation section, as there's also a link to 2.2 on this page.
Allright.
But then, when i click on "Create snippet", all snipets are showing examples of AppFramework 2.1 with CDN links! So, on this simple page we have 3 versions of App Framework :

2.2 link at the top of the page
3.0 documentation, the current and last version of AF
and 2.1 snippets...
Well, not very clear to me, and surely, it could be clearer.

Another example :
in XDK, somme projects' templates (i did not verify on all) are showing a minified version of appframework. So, there are no comments. And that's impossible to tell which version is used, and what files/plugins it's getting.
Again, small details, but very troublesome when you want to start. That's my point.
Are you sure you want close this issue? Because for me, these links are not even the beginning of a solution...

I never find any document about menu Button,do your app have menu button???   link in uiinsetlist  is all broken. not any theme template also .  if I my app have three type menuButton,then I need create threen header and footer, do you think that is a good design?

@dargoan I think you are confusing the XDK and App Framework.  The XDK is a consumer (like any developer) of App Framework.
@lilili87222 - yes there is a menu button https://github.com/01org/appframework/blob/master/templates/drawer.html

Thanks @imaffett for your answer, but i'm not confusing between those two.
I speak about appframework. In the examples, i didn't find any coherence about documentation, version code, and appframeworks. Why bother to put minified code in examples ? Today, there are plenty of tools outhere that do minification of code.
But, maybe, things have changed since my last post, I didn't check if today it's different.

Button Documentation is not clearly documented. i mean, what kind of button enable to implement other than "menuButton".. try to create my own combination of icon, but it not well displayed.


GH-39251: [JS] Use resizable buffer in builder

Closes: #39251

@ursabot please benchmark lang=JavaScript


Pagination shows more buttons when switching from page 1 to 2 to 3 etc.

[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version

Steps to reproduce

Go to the docs: https://www.flowbite-react.com/docs/components/pagination
Pagination example shows "Previous [1] 2 3 4 Next"
Press "Next"
Pagination example now shows "Previous 1 [2] 3 4 5 Next"
Press "Next"
Pagination example now shows "Previous 1 2 [3] 4 5 6 Next"

Current behavior
On page 1 the pagination shows pages 1-4
On page 2 the pagination shows pages 1-5 (becomes longer)
On page 3 the pagination shows pages 1-6 (becomes even longer)
Expected behavior
The Pagination component should show constant number of pages.
Context
Tried it on the demo page (https://www.flowbite-react.com/docs/components/pagination) with Google Chrome and Microsoft Edge.
Tested in own project with:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

I'd like to fix this!
I'm thinking about showing always 6 elements (if they exist)

By looking at the figma and the html version of the component, the selected page should be in the middle and not the first one, so i'm changing it to 5 to have two pages per side.
In the figma is present a variant with a "..." button and the last page. I couldn't find it anywhere. @tulup-conner @rluders Wanted to know if I could maybe implement it

@DavideFrancescon About the centering, yes, you are correct, but... normally we only implement the version that is available at the flowbite.com documentation, not the Figma. But, maybe we could expand it... I see no reason for not unless there are some copyright concerns here. WDYT  @zoltanszogyenyi?

@rluders On the official documentation the example has the active page in the middle.
The problem now is that the code is not passing the tests, i'm checking what the problem is but is think is caused by the test being done for how the previous pagination worked (wrongly). So i might have to fix those too


Use wall-clock agnostic System.nanoTime

As pointed out in #95, System.currentTimeMillis is sensitive to changes
in wall-clock time, such as when the user or NTP changes the system time.
This makes currentTimeMillis inapropriate for most timeout applications.
System.nanoTime, on the other hand, is wall-clock time agnostic.

Awesome, great contribution! From what I can see it's backward compatible as well?

Yes, I tried to make it backward compatible.

Thanks a lot for the pull request.

NP. Thanks for the nice library :)
I'd love to get using this. Are you planning a release anytime soon?

I'd love to get using this. Are you planning a release anytime soon?

Yes ;)


No Response

I've got an X10 bridge I wrote, modified from edc1591/gohome, which has been working right along until iOS 11. After iOS11, homekit wouldn't see my bridge anymore. I ended up removing and re-adding it from homekit and things worked better but not great. Basically my bridge would become periodically unresponsive for no apparent reason.  So today, I updated to hc master in hopes things would be better since it seems to have new mdns code. What I'm experiencing now is that within about 30 seconds of starting, my bridge disappears and is I get "No Response". Seems to work fine for those 30 seconds and then no response. Since others seemed to be having problems with special characters, I tried changing mine from "X10 Bridge" to "X10.Bridge" to "X10-Bridge" but it didn't help. Also the "." seemed to get replaced with an "_" in that test. Here's what I see scanning for hap mdns entries:
solyaris> dns-sd -B _hap._tcp
Browsing for _hap._tcp
DATE: ---Thu 19 Oct 2017---
13:40:25.983  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
13:41:19.019  Add        2  13 local.               _hap._tcp.           X10_Bridge
13:41:45.775  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
13:46:10.267  Add        2  13 local.               _hap._tcp.           X10_Bridge
13:46:42.954  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
14:09:05.208  Add        2  13 local.               _hap._tcp.           X10_Bridge
14:09:33.415  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
14:13:50.605  Add        2  13 local.               _hap._tcp.           X10_Bridge
14:14:24.253  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
14:15:35.356  Add        2  13 local.               _hap._tcp.           X10_Bridge
14:17:14.464  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
14:22:26.395  Add        2  13 local.               _hap._tcp.           X10_Bridge
14:23:06.355  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
14:31:58.205  Add        2  13 local.               _hap._tcp.           X10_Bridge
14:32:29.270  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
14:33:53.671  Add        2  13 local.               _hap._tcp.           X10_Bridge
14:34:24.412  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
15:07:50.564  Add        2  13 local.               _hap._tcp.           X10_Bridge
15:08:19.210  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
15:13:26.244  Add        2  13 local.               _hap._tcp.           X10-Bridge
15:13:44.775  Rmv        0  13 local.               _hap._tcp.           X10-Bridge
I'm not clear on how this all ties together but any help appreciated.

Please enable debug logging in hc with log.Debug.Enable() (don't forget to import "github.com/brutella/hc/log") and attach your log.

The log doesn't seem particularly useful in that when (according to dns-sd run in a different window) the mdns Rmv occurs, nothing is logged. Maybe something in there is meaningful to you?
Here's the dns-sd output for the time this log was created:
solyaris> dns-sd -B _hap._tcp
Browsing for _hap._tcp
DATE: ---Thu 19 Oct 2017---
19:18:29.370  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
19:18:40.264  Add        2  13 local.               _hap._tcp.           X10_Bridge
19:19:16.955  Rmv        0  13 local.               _hap._tcp.           X10_Bridge
home.log

I still have not had any luck getting this to work. I incorporated the slight changes from the example code (setting up the onTerminiation func) but it still stops working after 30 seconds, as soon as it disappears from the dns-sd listing. For reference, my normal host is an EL6 linux box running go 1.7.6. When I try to run the same on my Mac with High Sierra and a MacPorts installed go 1.9.1, it blows up in the mdns code:
solyaris> ../../../../bin/X10-BottleRocket-Bridge
panic: reflect: call of reflect.Value.Int on zero Value
goroutine 1 [running]:
reflect.Value.Int(0x0, 0x0, 0x0, 0x13e9df7)
/opt/local/lib/go/src/reflect/value.go:908 +0x141
golang.org/x/net/ipv4.sysfd(0x15a7ac0, 0xc42000e048, 0xc42000e048, 0x15a7ac0, 0xc42000e048)
/Users/tjb/goWorkspace/src/golang.org/x/net/ipv4/helper_unix.go:46 +0x196
golang.org/x/net/ipv4.(*payloadHandler).sysfd(0xc4200824d0, 0x15a7ac0, 0xc42000e048, 0xc4200824b0)
/Users/tjb/goWorkspace/src/golang.org/x/net/ipv4/helper_unix.go:31 +0x5b
golang.org/x/net/ipv4.(*PacketConn).SetControlMessage(0xc4200824b0, 0x8, 0xc420082401, 0xc42000e048, 0x0)
/Users/tjb/goWorkspace/src/golang.org/x/net/ipv4/endpoint.go:55 +0x4c
github.com/brutella/hc/vendor/github.com/brutella/dnssd.newMDNSConn(0x10, 0x0, 0x0)
/Users/tjb/goWorkspace/src/github.com/brutella/hc/vendor/github.com/brutella/dnssd/mdns.go:105 +0x5f2
github.com/brutella/hc/vendor/github.com/brutella/dnssd.NewResponder(0x13ea972, 0x8, 0xc420014800, 0x10)
/Users/tjb/goWorkspace/src/github.com/brutella/hc/vendor/github.com/brutella/dnssd/responder.go:40 +0x26
github.com/brutella/hc/vendor/github.com/brutella/dnssd.init()
/Users/tjb/goWorkspace/src/github.com/brutella/hc/vendor/github.com/brutella/dnssd/responder.go:37 +0x198
github.com/brutella/hc.init()
:1 +0x7f
main.init()
:1 +0x49
solyaris>

Could someone with a working environment please post details. Base OS version, GO version, etc. High Sierra/GO 1.9.2 blows up in the mdns code like in the comment above.

@tjbx Same for me on High Sierra - after @brutella refactored mdns. I will try today with some ARM with armbian OS and let you know

Any updates?

Sorry nowadays I have no time for my hc project. Will try to reach it in this week.

@tjbx Make sure that the package in $GOPATH/src/golang.org/x/net is up-to-date to resolve your crash.

I thought 'go get' should have kept stuff up to date automatically but it appears it doesn't. On my High Sierra/go 1.9.2 test setup, removing src/golang.org/x/net and rerunning go get fixed the problem of the immediate crash. With that success in mind, on my EL6/go 1.7.6 normal setup, I blew away all of src to make sure everything was up to date and ran go get. That fixed all my problems - hap no longer disappears after 30 seconds when monitoring with "dns-sd -B _hap._tcp". In fact, everything seems much more responsive than ever before.

Great news. I think we can close the issue now.


very nice code!

I really like the code of this paper, using very few libraries, and the parameter modifications are all available at the beginning of the paper, which is very nice. I would like to use style transfer work for road segmentation. Thank you for the code in this paper.

Thanks for your comment. Hope it helps.


Variables - Getter block to match Scratch 2.0

This block should have a single text field, set to the name of the variable, but the right-click menu should behave like the dropdown on a fieldVariable.

Please don't make us have to keep using ([] of []) for getting variables by name!
https://scratch.mit.edu/discuss/topic/211154/

Though to really make it work well you could add a label "variable with name", or something.

I prefer the current system it makes it easier to delete, rename, and change the variable in the reporter

I also like the dynamicly get variable thing. PLEASE do not change it to 2.0-style

Maybe have both? The current system for those particular cases and 2.0's for convenience. It would also be good if you could switch between them in the right-click menu.

IMO an "of myself" block would fit best with 2.0, as it is now.

I feel like the option to switch between them would be messy and unnecessary. +1 for "myself" or "this sprite" option in the "_ of _" sensing block

I like the dropdown version because currently you can create semi-hacky dynamic variables with but without actually hacking the blocks because you can drop a reporter into the variable getter, and setter, if variables are designed like 2.0, you would have to hack the xml of the sensing of block because you cannot put reporters into sensing of.

Yeah, but it doesn't look good:

The only visible thing that tells you it's a dynamic variable getter is the red ring around the block. That's not very obvious, which is why I suggested (var name) of [myself].

@rachel-fenichel - As we discussed we should update the variable getter to match 2.0. As you described the menu items should appear in the right-click.

Typing in the variable name should still be an option. It can get
inconvenient when you have 500 variables in your project.
On Tue, Jan 17, 2017 at 6:53 AM, carljbowman<EMAIL_ADDRESS>wrote:

@rachel-fenichel https://github.com/rachel-fenichel - As we discussed
we should update the variable getter to match 2.0. As you described the
menu items should appear in the right-click.
[image: screen shot 2017-01-17 at 9 52 24 am]
https://cloud.githubusercontent.com/assets/3409578/22025170/ae34203e-dc9a-11e6-8ad3-1cfc6167e356.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LLK/scratch-blocks/issues/573#issuecomment-273189956,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARIzhpW8mxKD7Jwi4VM2xFVcmQRocCDIks5rTNXOgaJpZM4Jl79e
.

RIP fun times
On Tue, Feb 28, 2017 at 3:20 PM, Rachel Fenichel<EMAIL_ADDRESS>wrote:

Closed #573 https://github.com/LLK/scratch-blocks/issues/573 via #810
https://github.com/LLK/scratch-blocks/pull/810.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LLK/scratch-blocks/issues/573#event-980987030, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ARIzhlBUZIuDu0kjHVv5wYNAd6C8b2CLks5rhKvZgaJpZM4Jl79e
.


Fix exception where IEnumerable could be null

This PR fixes a scenario where GetCustomerProperties could return an IEnumerable that were null, causing a NullReferenceException. The solution suggested is to never return a null-Enumerable, but instead an empty ICollection.

@stefanolsen Thanks for making the fix.
I will create a new release once the other PR's are resolved.


General access page for users

Landing Page

Colors:
Green for logo - 89b36d
Green for text boxes - cce4bd
Logo Token color - e4b934
Fonts:
Header: Comic Sans
Description: Arial


DBZ-4900 Use exponential back-off for log availability check

https://issues.redhat.com/browse/DBZ-4900

@gunnarmorling I've added a commit using Duration so please take a look

LGTM now, merging. Thx for the quick update, @jpechane, and the original work, @Naros!

Logged https://issues.redhat.com/browse/DBZ-4902 as a follow-up. Probably a matter of minutes to do this change.


Sass Converter Error

I followed instructions
allan@allan-pc:~/test/Artists-Theme$ jekyll serve --watch --trace
Configuration file: /home/allan/test/Artists-Theme/_config.yml
Source: /home/allan/test/Artists-Theme
Destination: /home/allan/test/Artists-Theme/_site
Incremental build: disabled. Enable with --incremental
Generating...
Conversion error: Jekyll::Converters::Sass encountered an error while converting 'assets/css/all.sass':
Error: Invalid CSS after "$accent": expected 1 selector or at-rule, was ": #c99065;" on line 15:1 of all.sass >> $accent: #c99065; ^
Traceback (most recent call last):
28: from /home/allan/gems/bin/jekyll:23:in <main>' 	27: from /home/allan/gems/bin/jekyll:23:in load'
26: from /home/allan/gems/gems/jekyll-4.0.0/exe/jekyll:15:in <top (required)>' 	25: from /home/allan/gems/gems/mercenary-0.3.6/lib/mercenary.rb:19:in program'
24: from /home/allan/gems/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in go' 	23: from /home/allan/gems/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in execute'
22: from /home/allan/gems/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in each' 	21: from /home/allan/gems/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in block in execute'
20: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/commands/serve.rb:86:in block (2 levels) in init_with_program' 	19: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in process_with_graceful_fail'
18: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in each' 	17: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in block in process_with_graceful_fail'
16: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:36:in process' 	15: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:65:in build'
14: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/command.rb:28:in process_site' 	13: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/site.rb:76:in process'
12: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/site.rb:202:in render' 	11: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/site.rb:515:in render_pages'
10: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/site.rb:515:in each' 	 9: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/site.rb:516:in block in render_pages'
8: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/site.rb:523:in render_regenerated' 	 7: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/renderer.rb:63:in run'
6: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/renderer.rb:84:in render_document' 	 5: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/renderer.rb:100:in convert'
4: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/renderer.rb:100:in reduce' 	 3: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/renderer.rb:100:in each'
2: from /home/allan/gems/gems/jekyll-4.0.0/lib/jekyll/renderer.rb:102:in block in convert' 	 1: from /home/allan/gems/gems/jekyll-sass-converter-2.0.1/lib/jekyll/converters/scss.rb:179:in convert'
/home/allan/gems/gems/jekyll-sass-converter-2.0.1/lib/jekyll/converters/scss.rb:187:in `rescue in convert': Error: Invalid CSS after "$accent": expected 1 selector or at-rule, was ": #c99065;" (Jekyll::Converters::Scss::SyntaxError)
on line 15:1 of all.sass

$accent: #c99065;

I am completely new to SCSS
Can you offer any advice
Regards
Allan

The line that solves the sass issue (based on @frobnitzem's solution!) is changing line 13 in all.sass to
$projects: ( {% for project in site.data.settings.projects %} "{{ project.folder }}", {% endfor %} )
I am also new to sass, but it seems as though adding brackets (square or round) stops the converter stops throwing the issue.


Applying QueryID Fix to QPI and TSGs

PR Checklist
This PR included a change to fix the QueryID mismatch between azure_sys and log analytics workspace.
The link to direct testing shared with reviewers to test the QPI and TSGs.
If adding or updating templates:

[ ] post a screenshot of templates and/or gallery changes
[ ] ensure your template has a corresponding gallery entry in the gallery folder
[ ] If you are adding a new template, add your team and template/gallery file(s) to the CODEOWNERS file. CODEOWNERS entries should be teams, not individuals
[ ] ensure all steps have meaningful names
[ ] ensure all parameters and grid columns have display names set so they can be localized
[ ] ensure that parameters id values are unique or they will fail PR validation (parameter ids are used for localization)
[ ] ensure that steps names are unique or they will fail PR validation (step names are used for localization)
[ ] grep /subscription/ and ensure that your parameters don't have any hardcoded resourceIds or they will fail PR validation
[ ] remove fallbackResourceIds and fromTemplateId fields from your template workbook or they will fail PR validation

Following are the snapshot of features or areas where we pushed the changes.
Long running queries chart:

Wait Stats Chart

Top Queries by Calls chart

Top Queries by Data - Usage

Top Queries by IOPS


Add the option to hardcode read and write throughput

For on-demand capacity we used to default to 100 throughput both when reading and writing. It is useful to
let the user decide how much throughput to use, based on how much they are willing to spend and how fast
should the opertaions take place.

https://github.com/audienceproject/spark-dynamodb/issues/32


When "ctrl+enter" or "shift+enter" it run the wrong cell

Environment data
VS Code version: 1.60
Jupyter Extension version (available under the Extensions sidebar): v2021.8.1054968649
Python Extension version (available under the Extensions sidebar): v2021.7.1060902895
OS (Windows | Mac | Linux distro) and version: Windows 10: 21H1
Python and/or Anaconda version: 3.8.10/3.9.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Jupyter server running: Local | Remote | N/A: Local and remote
Expected behaviour
Run the selected cell when "ctrl+enter" or "shift+enter".
Actual behaviour
Sometimes, when "ctrl+enter" or "shift+enter" to run a cell, it run the wrong cell.
It seems to me that it is running the last cell ran.
Steps to reproduce:
Hard to reproduce as it is happening randomly. I would suspect it to happen after a high memory consumption (reaching to max) that will make it bug until we restart the apk/computer.
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

VSCode core handles the ctrl+enter and shift+enter shortcuts so transfering there.

Having the same issue, I've tried playing with the shortcuts, but I can't seem to fix it.  It really makes VSCode Notebooks unusable 😞
It seems like there's some discrepancy with where the editor cursor is, and where the notebook thinks the cursor is when executing.

Same issue, default keybinding ctrl+Enter runs the above(previously edited) cell instead of the current one. Resetting shortcut keybinding make the problem go away for a while but then happens again radomly.

I can't reproduce this. A gif would really help. @yuanchongtt had a screenshot of a notebook with the editor focus and cell focus out of sync.

Is that what people are seeing? Would really like to see a gif of how people get into that state

I have noticed similar behaviour. I don't know if it's actually the problem. But this happens when I create one cell using code button that appears on hovering over the cell and then create another cell using the code button at the top.
Steps to reproduce:

Create a new notebook.
Delete the first cell that appears.
Use +code button on the screen to create a cell (execute it with Ctrl + Enter).
Then use +code button (that appears on the top bar) to create another cell.

Now the cursor appears to stop on the first cell.
This is for a completely new notebook. But unable to reproduce this behaviour when the notebook already have some cells.
I don't know how to create a gif but I hope the steps I mentioned will be helpful.

I think the problem is that vscode is not focusing on the current cell, the result of that is ctrl+enter runs the other cell
made a gif

@roblourens I'm running into this pretty consistently, will ping when today when I run into this.

This issue has been killing me. makes the vscode notebooks almost unusable. I generally resort to manually clicking the play button on a given cell to get it to run. This generally does not fix the behavior or change focus, but sometimes it does. Seems very stochastic overall.

Added detail: Often this seems to be caused by a clear separation of focus, where the blue vertical bar focus indicator is not on the cell currently being edited, as in the gif above.
However, at other times, the blue cell focus indicator is correct and a different cell is still run, with no visual indication of which one it will be.

I am still not able to repro this. People who see this, cold you try downloading the Insiders' build and tell me whether it happens there? https://code.visualstudio.com/insiders

@roblourens i think https://github.com/microsoft/vscode/issues/133026 is a dup of this. Possible the contexts weren't working correctly. E.g. i run into issues where selecting a cell and hitting the DD to delete a cell wouldn't work, until and unless i closed and re-opened the notebook.
FYI - I haven't been able to replicate this, since monday.

I've switched to insiders and haven't had the problem again yet! I'll message back again if it happens again in the insiders version.

Moving to October - seems like this has still been observed once or twice in Insiders, but there's nothing that I can do here right now. Please continue to report it if you see it and let me know what actions you took.

I have been using a fresh install of the 1.61.0-insider build on Fedora for a week. Only extensions are Dracula theme, phtyon extension, and tabnine, also no settings sync. I haven't encountered this bug yet.

I've been plagued by this issue for some time now, on the Insiders build as well. I've managed to reproduce it consistently by and below are some screenshots of how I reproduce it.

Create a new cell and run it

Click the first cell to select it and then create a new cell below

Clicking the new cell places the cursor in it and allows for editing while the first cell remains selected

Shift+enter in the new cell incorrectly runs the first cell

Cell selection/run-context is now messy and shift-enter behavior unpredictable.

Hope this helps.

Thanks for the screenshots! I see you have an update pending in that Insiders build, can you check the date on it? (Help > About)
I've found two ways to get the editor and list focus out of sync. But neither is what we are seeing here.

Focus the cell 1 editor
Mouse down on the cell 1 statusbar and drag off it
Click on the cell 2 editor
Now both cell editors have the focus outline and cell 1 will never lose it until the editor is focused and blurred again

Focus the cell 1 editor
Click to add a breakpoint in cell 2
Now cell 2 has list focus but cell 1 still has editor focus

I don't think either of these are worth taking for this release. I still don't see how it's possible to insert a cell and end up with that cell not focused

Thanks for the screenshots! I see you have an update pending in that Insiders build, can you check the date on it? (Help > About)

Version: 1.61.0-insider
Date: 2021-09-16T08:31:28.161Z

I still don't see how it's possible to insert a cell and end up with that cell not focused

Are you referring to my situation? If so, is there anything else I can do or test to ease your debugging?

Have been using insiders for a while and not been having the problem but just had it again today... I'm surprised to see my info date says 9-26 since I thought I'd just updated.  I'll update again and report back if the problem continues
Version: 1.61.0-insider (Universal)
Commit: 214ac689ca9874a8a4be386f73d5cb60e15af25e
Date: 2021-09-28T05:14:06.244Z
Electron: 13.4.0
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 17.7.0

I am still having this problem running on 1.62.3, Windows. It has been plaguing me for a while. The problem is intermittent and hard to reproduce in my case too. I have noticed that when it happens the thick blue 'active cell' line indicator (on left of cell) remains fixed on a certain cell, despite the creation or clicking on new cells. This is the cell that also executes, so I imagine the two are related. The cell toolbar also remains fixed on this cell despite focussing/clicking on a new cell in my case.
I have attached a screenshot here to better explain my descriptions.

Having the same issue as well. It's not a big issue as I can close and reopen the notebook to temporarily fix it, but it is annoying as hell.

Same, this issue was fixed a bit—but then started happening again recently. 😢

It just happened to me again. I tried to execute a cell above or below a certain cell, but this cell kept executing instead. In fact I noticed that by clicking in the gutter I could move the blue active line and cell toolbar (that I mentioned above https://github.com/microsoft/vscode/issues/133038#issuecomment-976529373) but even though this UI was changed, the wrong cell kept executing. So my last comment maybe somewhat of a red herring!
Another thing I noticed is that I had clicked away to a different program and when I returned to VS Code the problem had sorted itself out and the correct cell would execute.

Same here. Is there any solution found for this issue, rather than closing and reopening the notebook?

@hamiddashti if this is the same problem I reported (https://github.com/microsoft/vscode/issues/136310) then a potential solution is to change focus from vscode to another application and then switch back. I noticed this as each time I encountered the issue I tried to switch to a screen recorder to record and the problem went away. It could well be a different issue though, or behave differently on different platforms (I'm using Linux)

No reports of this in awhile - closing


golang google cla checker is reporting ✅incorrectly

What did you do?
I opened golang/scratch#29 with commit 678ef4683d36dc2c5e1ee7d5fb6b5d73e6276b2c. That commit accidentally had it's author email set to<EMAIL_ADDRESS>which is not the email I use to contribute to Go.

What did you expect to see?
I expected to see the Google CLA checker to 🔴.
What did you see instead?
The Google CLA checker responded with ✅.

Note
I've updated golang/scratch#29 so that it has the email address I use to contribute to Go projects, but if you pull that commit or look at the commit on Gerrit, you can see the original email.

Your CLA on file has your GitHub username on it, and I assume that your @mcchouse.com email address is linked to your GitHub account, so the CLA bot connected the dots.


[RTE] Floating toolbar

When you use the rich text editor in the Internal content interface and you add several snippets one after the other, having to scroll up to the toolbar each time is quite frustrating.
Could we add a floating toolbar for example?

Floating toolbar is far too buggy. Froala does not work well with modals and scrolls.
The only option left is inline mode which lets you show the toolbar wherever you click thus removing the need from scrolling up or down.


[import/no-unused-modules] Report error on export specifier node

I noticed when an export declaration has multiple specifiers of which only a subset is unused the rule reports the error on the whole statement. In my code editor this draws a red squiggly under the whole statement. I can read which specifier is unused from the message of the reported error. Wouldn't it be nicer if the error was reported only on the specifier that is unused? That way I wouldn't necessarily need to even read and can let the red squiggly lead my monkey brain.
Consider the following export declaration
export { foo, bar } from './foo';

Assume foo is used, bar is unused. Usually the fix would be to remove bar. I'd expect the reported error to point to that node as it would make it slightly more intuitive to attack it directly.
I'd imagine this change isn't breaking as the same errors still get reported for the same reasons, just pointing to different nodes.
I couldn't think of a reason one would want the report on the parent declaration instead but if there is one please educate me.
I changed the test assertions that have to do with a declaration that has multiple specifiers to also assert a specific location for the reported errors. I changed the node the errors are reported on to make the tests pass again. I then reverted the test changes because CI disagreed even though they passed locally :shrug:.

I am very surprised that test changes wouldn't be required - can we remove the revert, so i can look into the failures?

can we remove the revert, so i can look into the failures?

The history of the failed test runs is still available.

The tests failed on endLine so I knew line had passed. I tried removing just the end assertions and that seems to work.
I still don't know why it didn't work but this is almost as good in terms of test strictness.


Search

Based on https://github.com/scientific-python/scientific-python-hugo-theme/releases/tag/v0.20 but this needs another change to fix the macOS keyboard shortcut

Working now! Try it in the deploy preview at https://deploy-preview-210--pybamm-developer-preview.netlify.app/

For testing: https://deploy-preview-210--pybamm-developer-preview.netlify.app/. It should work with macOS (Command + K) and Windows (Ctrl + K).

Thanks for the review! Yes, many of these points are likely coming from upstream, so, would it be okay if I can try to fix the fifth point for now, and split the rest of the items off into a separate issue?
It looks like we can upstream the fixes too, later, so I'd like to have a detailed look at them in some time (I don't really have experience with SASS/SCSS, so I'll have to learn some of the semantics).

Merging this for now, but I'll open a separate issue to handle these improvements. Thanks, @arjxn-py!

Thanks, no hurry on the improvements :)
+1 to open a tracking issue for now.

Thanks – I forgot to merge :P


--hot for whole project rather than just /src

Yet another enhancement! It would be cool if srvs could watch for changes in index.html, style.css, and all code files in the project, rather than just files in /src

Supporting other files is possible, but would be additional work that I don't currently have time for. If someone wants to contribute such an enhancement I'd be open.

I'm adding poor-man's  hot reloading for the docRoot folder by refreshing the page in the next release.


Citation - specific data sets

There will eventually be papers tied to specific datasets...but not yet. So I feel like every fd_xxx() function should end by calling a data_conditions() function, something like this:
data_conditions <- function(x, published = FALSE, contact_person, citation) {

    if(!published) {
        warning("These data are unpublished. Please contact ", contact_person, " to ask about using")
    }

    message("Data citation: ", citation)
    message("Contact person: ", contact_person)

   # add the above information to `x` as attributes...

    invisible(x)
}

working on trying this out, but having issues incorporating.
Error: 'data_conditions' is not an exported object from 'namespace:fortedata'

Tagging in @bpbond
I added section of code to utils.R
`# data conditions
data.frame() if necessary
not a user-facing function; document via roxygen?
data_conditions <- function(x, published = FALSE, contact_person, citation) {
if(!published) {
warning("These data are unpublished. Please contact ", contact_person, " to ask about using")
}
message("Data citation: ", citation)
message("Contact person: ", contact_person)
add the above information to x as attributes...
invisible(x)
}`
And as a test I revised fd_inventory() to this:
`fd_inventory <- function() {
Data Creation and Authorship Information
contact_person <- "Jeff Atkins"
citation <- "ESSD"
inv <- read_csv_file("forte_inventory.csv")
inv$date <- as.Date(inv$date, format = "%m/%d/%Y")
inv <- split_subplot_id(inv)
Currently there's a bad entry in the table. Nuke it. Temporary
inv$dbh_cm <- as.numeric(inv$dbh_cm)  # temporary, until we fix row 791
inv <- inv[c("subplot_id", "replicate", "plot", "subplot","date","tag", "species", "dbh_cm", "health_status", "canopy_status", "notes")]
weak_as_tibble(inv)
data conditions
data_conditions(x, published = FALSE, contact_person, citation)
}
`

reinstating data conditions


add in prometheus ports

https://github.com/blockstack/app.co/blob/551ec9f675ff3f416d817127fd7a756f67361e56/server.js#L116-L121

@kyranjamie would you be able to take this on?


The source code is being included twice in our packaged libraries (5.5 confirmed)

Frontend version
5.5, possibly earlier as well
Problem component
Frontend
Description
The source code is being included twice in our packaged libraries, which is causing a larger download size than necessary, longer compile times, more convulted builds, more difficult debugs, and tricky bugs when/if users use the wrong functions.

I'm unsure if this is true for version prior to 5.5, but I will prepare a fix and backport as necessary.

Fixed in master and UE5.5 branches: https://github.com/EpicGamesExt/PixelStreamingInfrastructure/commit/a7e4a3eec4f760783c7f19f4b93a3154ca335d08


Allow continuous variables to be visualized on map tool

Allow continuous variables to be selected as the "Main" variable on the map viz tool.
This ticket is dependent on:
Add gradient colormap for continuous variables (sequential, diverging): https://github.com/VEuPathDB/web-eda/issues/1041
Backend needs to know number of unique values of var in the dataset in order to determine if it’s a discrete continuous or continuous overlay: https://github.com/VEuPathDB/plot.data/issues/156
Legend update to handle binned continuous variables (discretization of the continuous colormap): https://github.com/VEuPathDB/EdaNewIssues/issues/218

Mostly implemented in https://github.com/VEuPathDB/web-eda/pull/1186 but keeping this open until the discrete/continuous thing is addressed.

I can't see how we can test low-cardinality numeric variables right now. SCORE Seasonal/Mozambique and UMSP don't have such variables.
Shall we close this ticket @d-callan and @asizemore ?  I am happy to.

looking good!


pdf.js in mobild not work

Hello, I found pdf.js on mobile not work, iframe DOM is empty,  the DOM not wokr too Is there a solution?

Closing as incomplete; please read CONTRIBUTING.md before opening an issue and make sure that you provide all of the information requested in ISSUE_TEMPLATE.md.


Can not tab to navigation arrow buttons

Can not access navigation arrow buttons using only keyboard. Which makes this component non-accessible.
Ref: https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html

If you're referring to the arrows to change the month, you can use (cmd+)+ctrl+right arrow/left arrow to navigate between those.  Likewise to change year you can use (cmd+)+ctrl+up/down.  I believe that satisfies accessibility requirements since it provides an alternative method to use those arrows.  I've actually been trying to locate the documentation for those things.
@chmln was there ever anything added to the docu for the keyboard shortcuts?  I never saw it mentioned in https://github.com/flatpickr/flatpickr/issues/623.

@mike-strauch keyboard stuff could definitely use documentation. As usual when time is a constraint, these things get pushed down the priority queue. But I'll get around to it someday :)

No problem; just wanted to make sure I hadn't overlooked it somewhere.

I would also really like to see those a11y features described in the W3 example page.
For example:

Proper keyboard navigation with tab and arrow-keys
Proper focus management:

focus to dialog on open
focus to last focused element (input or toggle-button) on dialog close
focus-trap: prevent tabbing away from the dialog

Etc..

Otherwise flatpickr is a really good and feature-rich datepicker. 👌  But since the EU regulations with the a11y are being pushed as mandatory requirements accessibility is no longer a nice to have feature but a must.

I would also support this feature/issue.
I'm using the calendar in our system to book the holidays, but tested from a blind guy that works with us it turned out almost totally unusable. Having it in a modal windows doesn't help, but anyway there's no way to navigate on it with a screen reader.

The calendar modals work if screen reader is in Focus mode / interactive mode.
Voice Over with mac OS - Works seamlessly no need to change modes.
NVDA/ JAWS on windows - Works on focus mode / interactive mode. (Default keys to enable the mode is insert key + spacebar key).


Storage servers space reclamation

Storage servers space reclamation tracking issue
Details
Storage servers enter into contract with the network to store data for some period of time.  Our current storage design uses an immutable data store interface using CAS.  When the data is contract state and the state mutates, the keys (hash of contents) change, and old data in the CAS KV store becomes unreachable.  We should have a mechanism to allow storage servers to reclaim this storage, e.g., via garbage collection.
Unless the storage server knows the structure of the data stored in the h(V) ->V storage, it does not know what blobs are unreachable from the current root hash.
Linked Issues

[ ] Co-design of Merklized storage data structure and CAS storage
[ ] Design of GC mechanism / APIs
[ ] Modify storage servers to enable reclamation

Done as part of #1759.


Initial commit to create stern-based debug container and kubernetes job

Introduction to Logger

The logger container and debugjob K8s job have been created to aid troubleshoot/debugging on the kubernetes cluster by capturing the pod logs
Logger uses a tool called "stern" to collect the pod logs.
It is also capable of executing kubectl commands to extract cluster state.

Additional items
Capabilities that need to be added (being worked currently) to the debug container to increase its effectiveness/utility include:

Collect node logs  (kubelet)
Capture kube-system logs (this can be obtained by passing --namespace arg to stern. However, this may need to be an optional param)

Sample outputs detailing logger's functionality are provided below :

Debug pod

karthik@MayaMaster:~/debug$ kubectl get pods
NAME                                                             READY     STATUS    RESTARTS   AGE
debugjob-gdxch                                                   1/1       Running   0          4m
maya-apiserver-55d949f8f5-9xnfg                                  1/1       Running   1          8d
maya-grafana-5bb5dc8c9-tlzwc                                     1/1       Running   0          1d
openebs-provisioner-7958c6d44f-mx9dw                             1/1       Running   1          8d
percona                                                          1/1       Running   0          22h
pvc-16b2fe4b-1d43-11e8-a068-000c298ff5fc-ctrl-7f5cbb8c97-g7bdv   1/1       Running   1          5d
pvc-16b2fe4b-1d43-11e8-a068-000c298ff5fc-rep-7876c6ffbb-8cr2n    1/1       Running   1          5d
pvc-16b2fe4b-1d43-11e8-a068-000c298ff5fc-rep-7876c6ffbb-hnnll    1/1       Running   1          5d
pvc-52e7c747-2093-11e8-8188-000c298ff5fc-ctrl-74774c464d-znx7k   2/2       Running   0          22h
pvc-52e7c747-2093-11e8-8188-000c298ff5fc-rep-758589859b-4h8h8    0/1       Pending   0          22h
pvc-52e7c747-2093-11e8-8188-000c298ff5fc-rep-758589859b-prxfr    1/1       Running   0          22h

debugjob description

karthik@MayaMaster:~/debug$ kubectl describe job
Name:           debugjob
Namespace:      default
Selector:       controller-uid=b720dbee-2152-11e8-8188-000c298ff5fc
Labels:         controller-uid=b720dbee-2152-11e8-8188-000c298ff5fc
                job-name=debugjob
Annotations:    kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"batch/v1","kind":"Job","metadata":{"annotations":{},"name":"debugjob","namespace":"default"},"spec":{"template":{"metadata":{"name":"deb...
Parallelism:    1
Completions:    1
Start Time:     Tue, 06 Mar 2018 20:56:17 +0530
Pods Statuses:  1 Running / 0 Succeeded / 0 Failed
Pod Template:
  Labels:  controller-uid=b720dbee-2152-11e8-8188-000c298ff5fc
           job-name=debugjob
  Containers:
   debugjob:
    Image:  logger
    Port:   <none>
    Command:
      /bin/bash
    Args:
      -c
      ./logger.sh -d 5 -r maya,openebs,pvc; exit 0
    Environment:  <none>
    Mounts:
      /mnt from logs (rw)
      /root/admin.conf from kubeconfig (rw)
  Volumes:
   kubeconfig:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      kubeconfig
    Optional:  false
   logs:
    Type:  HostPath (bare host directory volume)
    Path:  /mnt
Events:
  Type    Reason            Age   From            Message
  ----    ------            ----  ----            -------
  Normal  SuccessfulCreate  5m    job-controller  Created pod: debugjob-gdxch

Logs being captured when debugjob is in progress

karthik@MayaHost01:/mnt$ ls -ltr
total 112
drwxr-xr-x 3 root root  4096 Mar  5 11:51 openebs
-rw-r--r-- 1 root root  5541 Mar  6 20:56 kubectl_cluster_info.log
-rw-r--r-- 1 root root 11366 Mar  6 20:56 maya.log
-rw-r--r-- 1 root root 51712 Mar  6 20:56 openebs.log
-rw-r--r-- 1 root root 36145 Mar  6 20:56 pvc.log

Upon debugjob completion, logs are placed in a support bundle

karthik@MayaHost01:/mnt$ ls -ltr
total 116
drwxr-xr-x 3 root root   4096 Mar  5 11:51 openebs
-rw-r--r-- 1 root root 112640 Mar  6 21:01 Logstash_06_03_2018_03_31_PM.tar

@AmitKumarDas,  have made changes based on review comments.


LinkLiar always says I'm slipping

LinkLiar always shows me the slipping icon in the menu bar. Can anyone help? Using LinkLiar 2.1.1 on OSX 10.14.6

That means the MAC address of one or more interfaces cannot be changed by ifconfig.
Do you have an external hub attached to your computer? Something that has an ethernet port? Those usually can't be changed. I actually have the same problem and thought about implementing a function to ignore that icon warning for particular interfaces.

I usually see this message whenever I’m using my usb-c to Ethernet adapter on my Mac. @halo I also think that adding an option to ignore certain interfaces if they’re leaking would be useful!

Hi. Yes I have an external USB type A hub connected to my Mac but I had the same setup with my previous Mac and LL was working fine on that. So does they mean the MAC address of my actual computer is still being spoofed? If so, that’s all I really care about (unless the MAC address of my hub can be used to trace me?). Just a bit disconcerting as the Slipping icon is always visible.
Sent from my iPhone

On 5 Jun 2020, at 09:09, halo<EMAIL_ADDRESS>wrote:

That means the MAC address of one or more interfaces cannot be changed by ifconfig.
Do you have an external hub attached to your computer? Something that has an ethernet port? Those usually can't be changed. I actually have the same problem and thought about implementing a function to ignore that icon warning for particular interfaces.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@JamieJ1

So does they mean the MAC address of my actual computer is still being spoofed?

Let me phrase it this way. If you set the default in LinkLiar to "random", every interface that can be spoofed is being spoofed. If any one interface cannot be spoofed (or is not configured to be spoofed), then the slippery icon will show.

unless the MAC address of my hub can be used to trace me?

If you do not plug a cable into the hub, it cannot be used to trace you. The MAC address on cable interfaces is only known when you use a cable. The MAC address of WiFi interfaces is known as soon as you turn the WiFi on, because it will send out its MAC address eventually, to communicate with a hotspot.

but I had the same setup with my previous Mac and LL was working fine on that

Either you had another hub (one that could be spoofed, whereas the new one maybe cannot be spoofed), or you did not configure LinkLiar to spoof the new hub.
@ajkblue

adding an option to ignore certain interfaces if they’re leaking would be useful!

To me it would make sense to not show the slippery icon for interfaces that are set to "ignore". Would that suffice? I think so.

@halo yes, that was what I was thinking would make the most sense in this case. Maybe also a little explanatory pop-up when clicking ignore could be useful, but I believe it’s pretty self-explanatory.
As a side note, do any of you know of a usb to Ethernet adapter that does allow spoofing?

@halo

If you do not plug a cable into the hub, it cannot be used to trace you.

Bit confused. What good would a USB hub be if there were no cables connecting it to the computer and to devices?

To me it would make sense to not show the slippery icon for interfaces that are set to "ignore". Would that suffice? I think so.

It would be useful if possible to have a sub-list of all attached devices and be able to see each of them with the status by them so you can see exactly what is protected throughout your system. Then I wouldn't mind if the main slipping icon was always in the Home bar, because at least I could go and see which device was causing the slip and try and fix it.

What good would a USB hub be if there were no cables connecting it to the computer and to devices

To be clear: as long as you do not plug a network cable (that is, a CAT cable) into the hub, there will be no leaking. MAC addresses are only used in network communication (at the very least from one end of the cable to the other), but not for USB devices, such as a keyboard or a printer.

It would be useful if possible to have a sub-list of all attached devices

I think this might be a misunderstanding due to me not being clear. USB devices to not leak anything, so there is no use in showing those devices. LinkLiar is only concerned with Ethernet interfaces (Wi-Fi or Cable Ethernet).

As a side note, do any of you know of a usb to Ethernet adapter that does allow spoofing?

I have not found one yet. But fortunately the anonymity is pretty good if you bought one paying cash :)
Closing this issue because I don't think it's actionable.


Generate dist when publishing to npm

What's done
When frint is published to npm next time, it would generate and upload the dist files too, and that would make it available via CDN:
Example URL<EMAIL_ADDRESS>Usage example
<!-- dependencies -->
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/0.14.8/react.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/0.14.8/react-dom.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/rxjs/5.0.0-rc.5/Rx.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.2/lodash.min.js"></script>

<!-- frint -->
<script<EMAIL_ADDRESS>
<script>
  // frint is now available as `window.Frint`
</script>

Coverage remained the same at 100.0% when pulling 36d02318aa5e57644d6609009072b6c08d0adf6b on dist into 321eb672e8973a7c2aa152f4c3f1d79a222828ef on master.


[Jupyter] Paginated Filebrowser

Modifies the CustomFileBrowser used within the extension's Explore view to paginate its contents if too many items are returned. Currently this is set (globally, within the code) to 100 items. This should^[1] prevent the extension from crashing when trying to view a directly containing a large number of files.
Implementation
This was implemented using the ideas developed here. Unfortunately there doesn't appear to be a straightforward way for our extension to extend the FileBrowser class into a PaginatedFileBrowser, so the workaround was to place a Paging widget below the FileBrowser widget and have this Paging widget share some state with our implemented MountDrive.
This works well enough, but there is a downside. All of the contents of a directory are streamed from the jupyter-server backend to the frontend. This cannot be avoided unless we re-implement their ContentsManager with pagination support. The result is that, when loading a directory, the user must wait for all directory contents to be streamed to the frontend and therefore the directories containing more files take longer to load. However, since we are forced to load the contents into memory we cache the results to allow moving between pages to be instantaneous.
Other Fixes:

The createFileBrowser method was bugged. The code to remove the NewLauncher and NewFolder buttons act on the global browser object, and therefore the after a couple load all of the toolbar buttons are removed and the method starts to silently fail. None of the buttons (besides refresh which now with cached paginated won't do anything) are relevant for our explore view so I just removed the toolbar.
Also removed the FilenameSearch since it only works for the current page being displayed. However, I'm tempted to add this back in since without it the filebrowser looks a bit bare and technically when paginated is not activated (<100
files) the search bar works as intended.
The MountDrive had a bug where it wasn't sending the options to the backend.

Screen Recording
For some reason the screen recording has the cursor spinning wheel all glitched but on my screen it displayed fine.

[1] The jupyter-server backend still streams all of the contents to the frontend, so technically the user's browser could run out of memory trying to load and cache the directories contents.

Two questions, actually, that I thought of as soon as I ended the call :joy: :

How would you feel about switching the color of the pagination buttons from green to purple? (just to match e.g. the pipeline extension, and sort of the general theme?) Would it be hard? Would it be ugly?
Did you get a chance to test this on a larger repo (the kind that was crashing for Brody/RiskThinking?) I'm realizing that we should make sure to confirm for ourselves that this works.

Two questions, actually, that I thought of as soon as I ended the call 😂 :
1. How would you feel about switching the color of the pagination buttons from green to purple? (just to match e.g. the pipeline extension, and sort of the general theme?) Would it be hard? Would it be ugly?

2. Did you get a chance to test this on a larger repo (the kind that was crashing for Brody/RiskThinking?) I'm realizing that we should make sure to confirm for ourselves that this works.

Changing the color is easy. I was actually going to change the color but I didn't really have a strong opinion on what color to change it to. It's currently set to one of jupyter's predefined (--jp-icon-contrast-color1). What purple are you referring to?
Yeah tested against brody's cluster (both the image and video are using those datasets).

What purple are you referring to?
I had in mind the color of the "Run" button in the pipeline extension?

Yeah tested against brody's cluster (both the image and video are using those datasets).
:tada: :fire:


Lock 'hasha' to 5.0.0 to fix the issue

Fix #100.
Signed-off-by: Denis Golovin<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master     #101   +/-   ##
=======================================
  Coverage   71.98%   71.98%
=======================================
  Files          19       19
  Lines         971      971
  Branches      144      144
=======================================
  Hits          699      699
  Misses        272      272

Continue to review full report at Codecov.

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


Question about Voice Transcription

I am using Jitsi-meet and am a beginner.
I have checked your ìpàdé source and its features, and it seems that there are many better features than the existing Jitsi. I am particularly impressed with the Voice Transcription feature. I have several questions in this regard.

Did you develop the Voice Transcription feature yourself?
Or did you develop it using open source? If you developed it with open source, what is the name of that open source?

Can ìpàdé store voices in a database such as MySQL separately for each user?

Can I use it by duplicating your ìpàdé repository on my PC and configuring a virtual host within the web server of Nginx or Apache, just like the existing 'Jitsi Quick Installation method'?

and it seems that there are many better features than the existing Jitsi.

Thanks for the kind words, but I won't say they are better. They are extra features requested by users of Openfire Meetings. For more details, see my blog posting

Did you develop the Voice Transcription feature yourself?
Or did you develop it using open source? If you developed it with open source, what is the name of that open source?

The voice transcription is a web standard (webkitSpeechRecognition). See code here
It currently only works in Chrome browsers for now.

Can ìpàdé store voices in a database such as MySQL separately for each user?

The voice recording chunks are stored temporary from the browser in the IndexDB database of the browser and then assembled into a webm file. You can add additional code to upload the webm file from the client to an external MySQL DB on a web server.

Can I use it by duplicating your ìpàdé repository on my PC and configuring a virtual host within the web server of Nginx or Apache, just like the existing 'Jitsi Quick Installation method'?

As I mentioned before, this project ìpàdé is extracted from the Openfire Meetings project which uses Jitsi Meet and Jitsi Videobridge with Openfire XMPP server. It different from the standalone Jitsi solution that uses the Prosody XMPP server. The Jitsi Meet code in ìpàdé was modified to remove dependency on a web server so that it can be used as a static web site on GitHub Pages with any Openfire Meetings service (like pade.chat) or Jitsi Meet service like (meet.jit.si)


Release 1.1.12

Going to test in all browsers + portal

One thing that I had not thought of but am fine with: the bitmask demo doesn't use the random colors when there's no selection.  I'm fine with this, though, since it matches the behavior for the non-bitmask polygonal segmentations.

Besides the above, everything looks good to me.


Comma formatter for external js file

Apologies, I know you've been over this many times, but I can't seem to find an example like mine. I am using an external js file to call countTo which pulls the "to" value from the html (.count-number). I am trying to include the custom formatter to add the commas but I can't get it to work. Here is what I currently have:
function initCounters(){
$(".count-number").appear(function(){
var count = $(this);
count.countTo({
from: 0,
to: count.html(),
speed: 1300,
refreshInterval: 60,
formatter: function (value, options) {
value = value.toFixed(options.decimals);
value = value.replace(/\B(?=(\d{3})+(?!\d))/g, ',');
return value;
}
});
});
}
What am I doing wrong? Needless to say I am a total novice and appreciate any assistance!

Hi @originalorange , did you found the solution about this? Need it so hard


Doesn't work?

I may be doing something stupid, but this does not seem to be working, codespell does not detect any errors:
 6 Running codespell on '' with the following options...
 7 Check filenames? 'true'
 8 Checking filenames
 9 Check hidden? ''
10 Exclude file ''
11 Skipping 'spelling.txt,LICENSE.OpenSSL'
12 Builtin dictionaries ''
13 Ignore words file ''
14 Ignore words list ''
15 Resulting CLI options  --check-filenames --skip spelling.txt,LICENSE.OpenSSL
16 0
17 Codespell found no problems

See pull request https://github.com/adrienverge/openfortivpn/pull/921 and the .github/workflos/codespell.yml file
---
name: Codespell

on:
  push:

  pull_request:
    branches:
      - master

jobs:
  codespell:
    name: Codespell
    runs-on: ubuntu-latest

    steps:
      - name: Run Codespell
        uses: codespell-project/actions-codespell@master
        with:
          check_filenames: true
          skip: spelling.txt,LICENSE.OpenSSL

After a look at your own .github/workflows/codespell.yml, I added:
      - uses: actions/checkout@v2

just before:
      - uses: codespell-project/actions-codespell@master

Much better! Perhaps you could add an example to the documentation in README.md.


fix(collector): actually enable the deployment of PrometheusRule when using PodMonitor

When fixing this logic regressions were introduced that would prevent the PrometheusRule from rendering in some very unique monitoring scenarios.
I have checked this with as many permutations that I can manually.
If a user wants to render the PrometheusRule, they should be able to so long as they have enabled ServiceMonitor or PodMonitor, and in the case of the ServiceMonitor they have set Values.service.enabled == true.

i didn't realize at first, but i think i introduced a regression initially in https://github.com/open-telemetry/opentelemetry-helm-charts/pull/1415. i think testing should be expanded to validate that the output matches the input of values for these specific scenarios, but is somewhat obfuscated by the helper here which can obfuscate user input a little, but i understand why it exists.


Scale text and scale bars are likely incorrect

I'm thinking that our scales are likely incorrect since they are based on a map that's 1000x500 pixels. I wonder if there's a way to set the map size to be about what it would be if it was the width of an 8.5 size of paper. Then maybe we would need to add some sort of disclaimer to the report saying that the scales are based on a certain size of paper.

I would rather only display the map scale without the scale bar if there is even a possibility of it being incorrect. I would think we let UGS decide what to do?

If the scale bar is incorrect, then the scale text would be incorrect as well. They are both in the same situation.

I'm not so sure that is true. I thought the scale to which the map is set is fixed no matter what the size of the image. Am I not understanding that properly?

AOI overview map printed scale looks the same as subsequent maps (1:15k), but scale bar is different than those maps, and is identical to the earthquake ground shaking map, which is double the scale value:
AOI:

Collapsible Soil:

Earthquake Ground Shaking:


Sync native calls

https://github.com/aspnet/IISIntegration/issues/1006

For #1006

functional tests

I can add a test that tries to force the crash but it would be inherently racy and unreliable so I'm a bit sceptical about it.

As I mentioned offline, at worst you can verify that the behavior that normally would be racy doesn't fail. Ex send a request to the server that obtains server variables and verify it doesn't crash.

:up::date:


Add minimal logging, monitoring and alerting to checkmate

We can't really go live with a part of our infrastructure blind.
Tasks

[x] Integrate New Relic client in the most basic way - https://github.com/hypothesis/checkmate/pull/17
[x] Add dead mans handle monitoring to see if the service is dead
[x] Integrate with Papertrail
[x] Setup a Papertrail group for the service in the UI
[x] Integrate Sentry in the code (h-pyramid-sentry can probably do this for us)
[x] Configure the deployment to send stats to sentry (The two vars I can see are SENTRY_ENVIRONMENT and SENTRY_DSN)
[x] Get some basic alerts setup
[x] Integrate dependabot - Is this done? How would I tell. It's in the apps in github

Point to note: NewRelic has been configured, but as it stands alerts will only go through to Slack. When we know the go-live date we should update the NR config to push alerts to PagerDuty.

We think we've configured sentry now, but it's kind of hard to tell for a few reasons:

Nothing is / can use this yet
Unless this fails, I'm not sure how we tell that Sentry is working


Periodic Purge Deletion / Hard-deletion

@rsharath

would prefer to keep the top-level key more generic as I have some thoughts on other data tooling that may be needed.
2 & 3. For open source, let's leave more complex retention strategies to the implementer (i.e. turn off auto-purging and run your own strategy against the DB.)


Unintentional but unacceptable diagnostic language

Description
Not sure this bug really belongs on SPM. I just built swift-format and the build ended with:
remark: Incremental compilation has been disabled: it is not compatible with whoremark: Incremental compilation has been disabled: it is not compatible with whoremark: Incremental compilation has been disabled: it is not compatible with whoremark: Incremental compilation has been disabled: it is not compatible with whoremark: Incremental compilation has been disabled: it is not compatible with whoremark: Incremental compilation has been disabled: it is not compatible with whoremark: Incremental compilation has been disabled: it is not compatible with who[11/16] Co[25/25] Compiling SwiftFormatTestSupport DiagnosingTestCase.swift
Build complete! (103.43s)
Something needs to be inserting a newline in the output before all remarks.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
Build swift-format from the CLI with swift 5.7
Swift Package Manager version/commit hash
No response
Swift & OS version (output of swift --version && uname -a)
No response

Almost certainly the remark refers to "whole module optimization".  Seems to be two bugs:

the message cut off
it needs a newline, as you say
Taking a look.

Also seems unfortunate to be getting that same message so many times; either SwiftPM should dedupe or maybe that's something in the driver.  In any case the missing newline seems to be the first thing to address here, and that is almost certainly on the SwiftPM side.

So this looks like a combination of two things:

swift-driver emits both its JSON output and raw remarks to stderr (this seems unfortunate)
swift-package tries to interpret the JSON packets from the driver but when it can't it just emits the raw bytes, and ends up losing the newline (still looking into that one)

For example:
swiftc -parseable-output -whole-module-optimization -incremental -c foo.swift
remark: Incremental compilation has been disabled: it is not compatible with whole module optimization
1201
{
  "command_arguments" : [
    "-frontend",
    "-c",
    "foo.swift",
    "-target",
    "arm64-apple-macosx12.0",
    "-Xllvm",
    "-aarch64-use-tbi",
    "-enable-objc-interop",
    "-stack-check",
. . .

Filed https://github.com/apple/swift-driver/issues/1241 on the Swift Driver issue and will see what we do in SwiftPM about the current state of affairs.  Since the output is always line-based, we should be able to do better in the JSON parser than we are currently doing.

This is fairly reminiscent of the llbuild issue that we had on Windows - we would not buffer things correctly and interleave messages: https://github.com/apple/swift-package-manager/pull/4192

That's a good point — thanks for pointing this out.  In this case it seems that this is actually handled fairly well already by the JSON parser in SwiftPM, and an additional newline is all that's needed.  That doesn't explain the truncation but does at least properly emit the diagnostics.  I still think the driver should emit JSON for its own diagnostics, though, when -parseable-output is in effect.

I'm preparing a SwiftPM PR for the newline at least.

rdar://103608636

Fixed in https://github.com/apple/swift-package-manager/pull/5987

Also nominating for SwiftPM 5.8 as it's a safe fix.

This fix adds the requisite newlines.  I wonder if the original truncation had something to do with https://github.com/apple/swift-package-manager/issues/5960.


Bugfix/xref parser tests

Description
Two bugs have been discovered in xref_parser.t in the course of testing the new UniProtParser, which is more strict regarding its input than the old version.
Use case
For the new UniProtParser, xref_parser.t (now a part of the Ensembl Core test suite and is executed by Travis) as it is fails due to:

using a nonexistent species ID in UniProtKB records it uses, and
inserting malformed cross-reference lines into said records.

For the old parser the latter is of no consequence due to more loose parsing of UniProtKB input, whereas the former causes offending entries to be quietly skipped.
Benefits
Makes xref_parser.t compatible with the new UniProtParser, and hopefully somewhat increases test coverage of the old one.
Possible Drawbacks
None I can think of.
Testing
Have you added/modified unit tests to test the changes?
Yes
If so, do the tests pass/fail?
Yes
Have you run the entire test suite and no regression was detected?
N/A - the only thing that has changed is a single test file.

Coverage decreased (-0.005%) to 81.364% when pulling 67f1a263ea0ad76fef27e3ff289bc8b785e06860 on bugfix/xref_parser_tests into 32104e58f23ec4da918bd6e515cb8f4cd466b557 on feature/xref_sprint.


OAuth2 access token call /login/oauth/access_token always returns unsupported_grant_type

Gitea version (or commit ref): gitea-master-linux-amd64
Git version:NA
Operating system: Cent OS
Database (use [x]):

[ ] PostgreSQL
[ x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x ] Not relevant

Log gist:

Description
I have been trying accessing to obtain access token for Gitea , I have invoked "/login/oauth/access_token" as post API with
request body as below
{
"grant_type": "authorization_code",
"code": "",
"redirect_uri": "http://localhost:8080/js/qa/oauth2.jsp",
"client_id": "",
"client_secret",""
}
Possible options tried for grant_type is "authorization_code" & "refresh_token" with valid details for code , client_id & client_secret.
for all invocations i get
"
{
"error": "unsupported_grant_type",
"error_description": "Only refresh_token or authorization_code grant type is supported"
}
"
...
Screenshots

Please take https://gitea.com/lunny/testGiteaOauth2 as an example.


Stabilise and improve UART protocol

There are a few design flaws in the current UART upgrade protocol and the use thereof, as mentioned in #191

dpsctl.py does not do do retransmits
As there are no counters in the CMD_UPGRADE_DATAframes, a resent frame might result in device reported CRC error at the end of the upgrade process.

As this leads to changing the boot loader, the following should be added while at it:

There should be protocol support to change the baud rate.
Backwards compatibility should be kept (old/new dpsctlshould be able to upgrade new/old dpsboot for all permutations of 'old' and 'new').

I guess a new CMD_UPGRADE_DATA2 frame is needed with a counter and dpsctl could start with this one and fall back to CMD_UPGRADE_DATA. The silly thing is that the boot loader does not NAK frames with unknown commands meaning we will need to throw a handful of CMD_UPGRADE_DATA2 at the DPS before falling back the old protocol. Gah!
A boot loader upgrade method should be implemented too for the brave out there.

It is really a good idea to have some kind of handshake dialogue for the bootloader and to repeat a broken frame. I found (#191) that the device just breaks at some point in communication where the GUI is still running. But I am not quite sure if this is always the same behaviour. I will try to verify this tomorrow.

BTW has opendps ability to set device address in the serial protocol... I believe that original firmware allows to use multiple devices on single serial line (= they only TX when queried by specific address)

Any updates on this? I cannot upload firmware due to Error: device reported CRC error.


Add support for max runtime for workloads

What would you like to be added:
It would be useful if ClusterQueues had a way to enforce walltime limit.
This would enforce a walltime limit for any workload that is admitted into the ClusterQueue.
Why is this needed:
In HPC schedulers, it is common to have multiple layers where users can request a job with a set walltime limit.  It is also common for admins to set up walltime limits.
A Batch user can submit a workload and should also be able to request a walltime limit for their job.  This can be useful because it allows a user to have greater control over how long their job will run for.
An admin can design queues with various lengths for run time.  I've seen this in some HPC centers as a way to have dedicated queues for short lived jobs.
One question I have is where should the user requested walltime limit live?
Completion requirements:
This enhancement requires the following artifacts:

[x] Design doc
[x] API change
[x] Docs update

The artifacts should be linked in subsequent comments.

What do you need in addition to terminating the job once the deadline is hit?
Such field already exists in Job: https://kubernetes.io/docs/concepts/workloads/controllers/job/#job-termination-and-cleanup
Although we don't utilize that information in kueue.

Yea I saw that as I posted this.  In the Kueue design docs, it talks about having workloads as an abstraction for Jobs/CustomJobObjects.  That link is obviously specific to Jobs but I was wondering for other custom controllers.  But maybe we can call it solved for the JobController at the moment.  And other Job implementations would need their own deadline implemented.
And are you okay with the addition to CQ?  Even if most users puts a deadline on their job, it may be good to have default limits on Queues for those that do not.

/lifecycle rotten

@kannon92 please have a look at the preemption KEP https://github.com/kubernetes-sigs/kueue/tree/main/keps/83-workload-preemption #83
Please reopen if you would like to still have some form of max runtime even with preemption.

Also you could have a look at #477


Set toNative() to be not enumerable

This would fix #2344

Thanks! I'll merge after having successfull test run.

Looks like oracle dropped support for node 5,7 and will drop 9 also soon https://github.com/oracle/node-oracledb/issues/811 so I need to fix test setup to not install oracle stuff on non lts node versions..


I think you need to remove the opencc entry from ci.baseline.txt

Note https://github.com/microsoft/vcpkg/pull/39366#pullrequestreview-2126949720

Sorry guys, not really have energy to work on this now. Probably will try this again much later time.


⚠ Bofrost.es has degraded performance

In 45983b2, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1372 ms

Resolved: Bofrost.es performance has improved in eeb923b after 6 minutes.


Add target resource

Add target resource. Change code language to C#.

@jiashuoli : Thanks for your contribution! The author, @tamram, has been notified to review your proposed change.

@sayamk - Thanks for making this update.
If you can change C# to csharp as the language designation for the code examples, we can go ahead and merge the PR.

@lyra7 - We updated this article for the GA of Azure AD integration. Please see:
https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-msi
These changes should address your suggestion.
#please-close


Can't scroll (native) a container if i touch scroll on an input.

Can scroll (native) a container if i touch scroll on an input on ios

Greetings @do-web!
My sensors indicate that I require more information in order to assist you.

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this happen occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?

Additionally, providing a codepen that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting the forum, where many humans will be able to offer wisdom and advice.
Thank you for allowing me to assist you.

Ionitron
http://newculture.pl/option_dragon
24.03.2015, 19:26, "Ionitron" notifications@github.com:Greetings !
My sensors indicate that I require more information in order to assist you.
Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this happen occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?
Additionally, providing a  that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting , where many humans will be able to offer wisdom and advice.
Thank you for allowing me to assist you.
—Reply to this email directly or .

Greetings @do-web!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.

This is still happening and it hasn't been fixed yet.


[C++] Introduce portable compiler assumptions

Describe the enhancement requested
Compiler assumptions (standardized in C++23) [1] are supported in today's compilers via macros.
When used well they can hint the optimizer in ways that can improve performance, but more importantly, reduce binary-size in compute kernel loops that have to be specialized for many different types [2]
Like other features compiler features, this could become usable via a macro in macros.h.
[1] https://en.cppreference.com/w/cpp/language/attributes/assume
[2] While working on a refactoring of Take I was able to shave-off ~13Kbytes off compute/kernels/vector_selection_take_internal.cc.o on macOS.
Component(s)
C++

Issue resolved by pull request 41021
https://github.com/apache/arrow/pull/41021


Program terminated with errors!

When I executed the instruction
LXI SP,0001
It gave me an error:
Program terminated with errors!
This is most probably due to some unimplemented intruction in the simulator itself. Currently, the instructions RIM, RST, IN, DI are not supported. Please look at the JavaScript console to know more details.

I think a HLT at the end should fix it.


Shorter output of import()

Search Terms

Suggestion

I'm glad that TypeScript 2.9 finally support import() function call, however, I think it can be improved.
TypeScript currently emits this code for import('./lib'):
Promise.resolve().then(() => __importStar(require('./lib')))

which is longer and more verbose than this:
Promise.resolve(__importStar(require('./lib'))

I also created a test repo: https://github.com/KSXGitHub/typescript-async-import.git
Use Cases

Examples

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions
[ ] This isn't a runtime feature (e.g. new expression-level syntax)

These two versions don't behave identical. In the first version, if either __importStar or require throw an error, then you end up with a rejected promise. But in the second version the Error will affect the importing function directly.

Makes sense. Thanks for clarify.

@MartinJohns How about this?
new Promise(r => r(__importStar(require('./lib'))))

Slightly shorter.


PrimaryCommand icons in PageHeader get hidden when the header text is too long

Mostly encountered on mobile, when I have an especially long header, on page load the PrimaryCommand icons are shown properly, but if I run any command that toggles their visibility they gradually get all hidden into the ellipsis.
Repro steps: load a page with a long header, a back, forward and home buttons. The visibility of the back and forward buttons are bound to whether there is a previous or next item, respectively. When I press next, the backing value is recomputed, and regardless of its value all or some icons get hidden.
I believe this is new in 1.1.12 as another project I had running on an older version of Template10 didn't exhibit that behavior.

Could you post a screen cap of what you are talking about?

Thank you for your reply. The first screenshot (please ignore the non-English text) shows the Next arrow, and when I press it, the next content is loaded and a Previous and Next arrows should show, but they end up being pushed to inside the ellipsis.

I recommend you use Dynamic Overflow.  https://msdn.microsoft.com/en-us/library/windows/apps/windows.ui.xaml.controls.commandbar.isdynamicoverflowenabled

Thank you, that was exactly what I was looking for.


Deal with hints_directory during cleanup/destroy

This will deal with cleaning up hints_directory if it's being set
@aboudreault can you review please?

tyvm