Consider switching to main area widget

We like to keep the side panel widgets for things that are skinny...
Since this might wanna be a bit larger, if you are trying to see someone's notebook, it might be nice to have this also be able to be a main area widget with a launcher icon.
cc @isabela-pf

Thanks for mentioning me @saulshanabrook! I also think it would make more sense to have the video interface appear as a main area widget for a few reasons. Most of all, I think having the video in the right side bar as it is now makes it harder to find as that is a less familiar area than a main area widget. Having a normal tab also means it no longer has to rely on harder to read sideways text.
If the video chat was originally put in the sidebar to make sure it was easy to have it next to an open file, I would recommend having Jupyter open with the two tabs side by side (like the below image). I’m pretty sure this can be configured via workspaces.

There’s also a chance that this might address #2’s scaling issue since the implementation might have to change some by moving its location.

Thanks for chiming in / opening this issue, @saulshanabrook @isabela-pf!
The widget started out as a main area widget, and after testing with a few users I moved it to a sidebar. The use case we developed this for is to have a few students in groups working together. You might screen share, or see someone else's video - but often you'll just 'hide' and use audio only - so you have full screen real estate. I couldn't figure out how to implement 'hide / show' with a main area widget, so it's a sidebar. I kept trying to make the sidebar open to be much wider by default, but after a day trudging through the lumino code I gave up... Almost all the users will also come in via an nbgitpuller link so won't ever see the launcher UI.
Do you think we can either:

Make it a main area widget that can 'dock' to the sidebar
Make the sidebar open wider? I was trying to figure out how to achieve the same thing as the CSS 'min-width' property.

Thank you!

Could we add a way to do both? Where there is a button to pop out the sidebar to a main area widget maybe?

I think there are compelling use cases for sidebar, main area, and even second fat browser tab (e.g. you want to share your lab, and be able to see people without the glitch-in-the-matrix effect). I'll maybe have a crack at this...
Also, I had no idea jitsi was all XMPP under the hood. Makes sense! There's a lot we can do with that...


Issue with removeFromPasted option

Hello !
First, thank you for your great plugin :) very easy to use !!
However, I have an issue with the removeFromPasted option. When I write text into the text area, and I add space between two paragraphs, if I make backspace from a paragraph to the previous, the font size of the text change (the plugin add an inline style of 1.6em font-size)
The original text:

When I apply a backspace on the last paragraph to the second one:

Thank you for your help
Chrome 52 on Ubuntu 16.04

I thinks it is a Chrome Ubuntu bug :(

It also appears on Chrome Windows

We used our own CSS to use the plugin, we add a font-size: 16px; important! on all the children of  trumbowyg-box. It removed the wrapping span with the inline style of 1.6em font-size and it fixed the issue. May be it can help you to find the problem...

Thanks for your feedback!
The reason that I can't reproduce the bug is I have normalize.css on my dev page.
So I need to add something like that in the doc or in the core default CSS.
I think that could resolve the #203 too.
Thanks!

You're welcome

Need to add a section in documentation to tell to Trumbowyg users to define a font-size.


Removed pluralExtensions lookup from detectLanguageFromPath

As discussed at https://github.com/i18next/i18next-node/issues/175, I removed lines that forced pluralExtensions lookup when detectLanguageFromPath was called (since none of the others "detectLanguage" methods have this check in them). This allows use of custom language shortcodes, not just predefined ones).

will be merged - just will change that to have an option to toggle on/off this behaviour to keep up backwards compatibility.

will be in next version coming this week

sorry had to change this, as it was breaking the tests by allowing anything for detecting lng from route path even if a route does not provide locale.
changed it to lookUp if locale is valid in supportedLngs. So adding a lng that is not in plurals list to supportedLngs will pass that check.

:+1:


268 us in list column value editing

added in column editing on double click. Popups included for the save. Also included popup when user tries to edit primary key.

There seems to be a mismatch when editing cells
Clicking on "Walmart" cell, but it tries to edit the "Google" value, which is the last from the table

Fixed. Should be good to go.


chore(typespec): bump to tsp 0.61.2

Description
resolve https://github.com/Azure/autorest.csharp/issues/5111
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

Record an issue regarding the regression in operation id doc: https://github.com/Azure/autorest.csharp/issues/5117


Replace npm with yarn as a package manager

It would be good to replace npm with yarn in the app.
Benefits it'll bring:

Faster downloads
Keeps track of specific version in yarn.lock
Emojis when running commands (obviously this is the main reason 😄  )

I've been using yarn for a couple weeks now and haven't had any problems.
Transition was seamless for us.

it uses the same package.json
very similar cli commands

If anyone has had problems with it, honestly would be interested to hear.

@petrgazarov thanks for the issue. Looks like this has been brought up before and someone had problems https://github.com/FreeCodeCamp/FreeCodeCamp/issues/11208. Have you tested yarn with the FreeCodeCamp repository yet?

Works fine for me locally!
Steps I did:

recloned repo
yarn install
installed gulp and bower globally with yarn
setup database, as per instructions
yarn run only-once

Then ran all scripts in package.json, substituting npm with yarn
Everything worked as expected.
My env details for reference:
node -v
v6.0.0

yarn version v0.16.1

npm -v
3.10.8

Mac OS Yosemite
10.10.5

@petrgazarov Thanks but we will be sticking with npm for the foreseeable future. I don't see Yarn taking over just yet.


[SPARK-20421][core] Add a missing deprecation tag.

In the previous patch I deprecated StorageStatus, but not the
method in SparkContext that exposes that class publicly. So deprecate
the method too.

Test build #76364 has started for PR 17824 at commit 15d1977.

@vanzin are we going to remove these listeners in future, or just keep them as deprecated? Some projects like Zeppelin explicitly depends on these listeners not only for code simplicity, but also for spark1/spark2 compatibility (SparkListener's signature is changed in Spark2, directly depending on SparkListener requires code recompile, so cannot achieve one build to support both Spark1/Spark2).

Test build #76364 has finished for PR 17824 at commit 15d1977.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76364/
Test FAILed.

I'm planning to remove these listeners completely in 2.3. (StorageStatus, which is the theme of this particular PR, is not currently in my crosshair, but I my decide to clean that one up also.)
I'd suggest you look at alternative ways of getting the data you want (either the rest api or the SparkStatusTracker API).

Thanks @vanzin ! SparkStatusTracker depends on JobProgressListener which was already deprecated, will you remove this JobProgressListener and rewrite SparkStatusTrack?

Yes SparkStatusTrack will keep working the same way it does today.

Merging to master / 2.2.


Double compiling

I want that any element with title attribute behaves like an uibTooltip atribute (from UI Bootstrap module). So, I created a simple directive that automatically puts this atribute and removes that other one, like this:

angular.module( 'ui.bootstrap.tooltip' )
.directive( 'title', function( $compile ) {
return {
restrict: 'A',
link: function( scope, elem, attrs ) {
attrs.$set( 'uibTooltip', attrs.title );
$compile( elem.removeAttr( 'title' ) )( scope );
}
};
} );

It converts the attributes and then it compiles again.

The problem appears, for example, in this element (in Bootstrap design):

> ```html
<div ng-controller="ButtonController as vm">
  <button type="button" class="btn btn-default" title="Add" ng-click="vm.add()"><span class="glyphicon glyphicon-plus"></span></button>
</div>
> ```

With appropriate controller:

> ```javascript
angular.module( 'app' ) // Whatever name
  .controller( 'ButtonController', function() {
    var vm = this;
    vm.add = function() {
      console.log( 'Added!' );
    }
  } );

Since it recompiles, ngClick function executes twice on click.
Which is the way for change element's attributes before compilation?

Re-compiling an already compiled element is not supported (and can lead to all sorts of problems, including memory leaks). What you can do instead, is specify a high-priority, terminal directive, switch the attributes and then continue the compilation starting from your directive's priority.
See https://github.com/angular/angular.js/issues/15270#issuecomment-253900234 for more details on how you can do this.

It is not a solution. The troubles is only in ngClick, ngDblClick, ngMouseenter... event attributes.

It is not a solution. The troubles is only in ngClick, ngDblClick, ngMouseenter... event attributes.

Not sure what you mean 😕

Here you have an JSFiddle example. Update with your suggestion and share what you are exactly recommending, please.
The problem is 2 console logs on one click.

The priority on your directive override for ui.bootstrap.tooltip needs to be very high (e.g. 2000), and it needs to be a terminal directive. The reason you're getting a double compile issues is because you're running $compile again on the ENTIRE element after the framework has already compiled it for you. However, if you set priority to something very high, and set the directive to terminal, then it will ONLY compile the "decorator" directive which changes title to uib-tooltip. Then it will stop, due to the terminal flag. You can then manually compile the rest of the directives on the element via the $compile service. Just ensure you set the maxPriority argument to whatever high number you used on the directive override. That way the decorator directive will not be recompiled. This will compile all remaining elements on the directive, but NOT the decorator directive which has already been compiled by the angular framework.
For more info, see the usage section here: https://docs.angularjs.org/api/ng/service/$compile

Fixed your jsFiddle

Nice! It is running well! Take updated JSFiddle example.
Thanks!

The solution is fantastic, but there is a problem with ngRepeat directive when the affected element is a child of repeated parent. I forked the JSFiddle test: here.

@Miqueliu, I'd be glad to take a look at it, but this isn't really the place for debugging. Unless you think this is actually a bug in the framework (which I don't think it is, I think it's something about the transclusion) you should do a stack overflow.

Ok. I will. Thank you.

In Stack Overflow, it is said that the ngRepeat directives conflict against terminal property (of directives definition).


vscode-json-languageserver crashes on start: Cannot find module '../out/jsonServerMain'

VSCode Version: n/a
OS Version: macOS 10.15.6 (19G2021)

Steps to Reproduce:

npx vscode-json-languageserver (or run it locally, this is just the quickest repro)
See the following:Cannot find module '../out/jsonServerMain'
Require stack:
- /Users/cameronlittle/.npm/_npx/63688/lib/node_modules/vscode-json-languageserver/bin/vscode-json-languageserver

This doesn't happen on the previous release (npx<EMAIL_ADDRESS>

I pushed<EMAIL_ADDRESS>with the fix

Thanks! It's working now and this can be closed.


Eta decay like NNs

Hi all,
is eta decay in every iteration possible  for GBMs ? i mean we set eta = 1.0, and got a parameter such "eta_decay" = 0.9995 , in every iteration eta will be updated eta = eta*eta_decay,
Regards

Not directly. But here's is an example that effectively duplicates that functionality.
https://www.kaggle.com/ashhafez/springleaf-marketing-response/xgb-learning-rate-eta-decay

I added eta_decay in python, see https://github.com/dmlc/xgboost/pull/563

Closes via #563


aniwave.to unsupported

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a new site support request
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that none of provided URLs violate any copyrights or contain any DRM to the best of my knowledge
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and am willing to share it if required

Region
singapore
Example URLs
https://aniwave.to/watch/one-piece.ov8/ep-1
Provide a description that is worded well enough to be understood
can't download , will support?
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp https://aniwave.to/watch/one-piece.ov8/ep-1 -v
[debug] Command-line config: ['https://aniwave.to/watch/one-piece.ov8/ep-1', '-v']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [f10589e34] (pip)
[debug] Python 3.11.8 (CPython x86_64 64bit) - macOS-10.15.5-x86_64-i386-64bit (OpenSSL 3.0.13 30 Jan 2024)
[debug] exe versions: none
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.02.02, mutagen-1.47.0, requests-2.31.0, sqlite3-3.45.1, urllib3-2.2.0, websockets-12.0
[debug] Proxy map: {'http': 'http://<IP_ADDRESS>:7890', 'https': 'http://<IP_ADDRESS>:7890'}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1798 extractors
[generic] Extracting URL: https://aniwave.to/watch/one-piece.ov8/ep-1
[generic] ep-1: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] ep-1: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://aniwave.to/watch/one-piece.ov8/ep-1
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/yt_dlp/YoutubeDL.py", line 1587, in wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/yt_dlp/YoutubeDL.py", line 1722, in __extract_info
    ie_result = ie.extract(url)
                ^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/yt_dlp/extractor/common.py", line 718, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/yt_dlp/extractor/generic.py", line 2531, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://aniwave.to/watch/one-piece.ov8/ep-1

Piracy sites will not be supported, sorry.


CIS3.2 Default tags

Hi again. In my tests, i have found that the python cis_reports, is given me an OK in the CIS3.2, becuase it's find that there is a tag with value ${iam.principal} created. But does not check if this tag is applied always. I mean default tags.
Thanks.

Sorry I have checked using 2.5.7. With the latest 2.5.8 it's OK.

It's working with latest release 2.5.8


Improve error handling with s3 and hdfs protocols

 Issue by vga91
Friday Sep 17, 2021 at 13:38 GMT
Originally opened as https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/2212

Expected Behavior (Mandatory)
Should return apoc.util.MissingDepencencyException similarly to MongoDb and Couchbase procs.
Actual Behavior (Mandatory)
Return java.net.MalformedURLException: unknown protocol: s3 or unknown protocol: hdfs
How to Reproduce the Problem
Call any export/import/load procedure with a protocol s3 or hdfs. For example:
CALL apoc.load.csv('s3://MY_S3_URL')

Specifications (Mandatory)
Currently used versions
Versions

OS: Mac BigSur
Neo4j: 4.2.7
Neo4j-Apoc: <IP_ADDRESS>

The issue is no longer present with apoc 4.3+


indicate ngInject, encapsulate full controller name

Style Y251 indicate ngInject, encapsulate full controller name for VS Snippet

This is my first PR for a project this large. I had great incuragement from @MAustinMMDP. Please be kind. :)

Thankyou for this @EskoCruz - it was next on my TODO list.

thanks for the PR.
why are you suggesting renaming the placeholder with a name suffix? i'd like to understand

@johnpapa - Not sure why @EskoCruz chose the name suffix but I chose it for the other templates/snippets to demonstrate the need to camelcase, however, in regards to the controller, I would suggest the name part be a placeholder so it can be prefixed automagically to "Controller". I would also make sure the placeholders match the approved WebStorm live templates, e.g., dependency1 to dependency. Lastly, the directive should not be capitalized; I would use directiveName.

im cool with that.

@MAustinMMDP - Thank you I will keep going.
@johnpapa - I was trying to stay constant with the WebStorm templates #544
I am more than happy to go with whatever you wish to abide by with these templates.

I dont feel strongly either way about Name or no name. I do care that we have a reason that's all :) Feel free to make a pitch for either.

Any final changes to this? or do you want more folks to test it?

I would say Ready for testing for Visual Studio Javascript plugin. working on Typescript next.

closing as we never got full testing on it.
feel free to open a new PR if we get more testers.


implement an overrideable JSCS config in ember-suave

implement an overrideable JSCS config in ember-suave
https://github.com/ember-cli/ember-cli/issues/3948

:+1: - Will work on this soon.

I just submitted https://github.com/dockyard/ember-suave/pull/15 to resolve this.  Once @brzpegasus has had a chance to review, we will release.

Released in 0.1.7.


HDDS-8241. Transfer leader command doesn't work in secure cluster

https://issues.apache.org/jira/browse/HDDS-8241

@nandakumar131 , thank you for the review.


Mona and Ayaka alternate sprint talent missing

Alternate sprint talent (ex: Mona and Ayaka) missing on character detail page

Fixed #295


Use arguments file to avoid long classpath. #402

Fixes #402

@BugDiver Thank you for contributing to gauge-java. Your pull request has been labeled as a release candidate 🎉🎉.
Merging this PR will trigger a release.
Please bump up the version as part of this PR.
Instructions to bump the version can found at CONTRIBUTING.md
If the CONTRIBUTING.md file does not exist or does not include instructions about bumping up the version, please looks previous commits in git history to see what changes need to be done.

This won't be required as the version is already bumped up.


my hydra is bugged

Describe the bug
My hydra went offline and I can't solve it. I've tried uninstalling, closing, checking my internet but nothing worked.
Steps to Reproduce
I clicked on "surprise me" and then my hydra couldn't search, I thought it was my internet, so I went to check and it wasn't. I've tried closing the program, ending the task and reinstalling hydra but it didn't help at all. The catalog didn't show any games and only the selection screen remained. When I reinstalled it wouldn't let me log in, and I'm still trying to solve it.

Expected behavior
I was hoping to be able to search for other games (and log in again)
Additional information and data
info.txt
pythoninstance.txt
error.txt
Operating System
windows 10
Hydra Version
v3.0.5
Before opening this Issue

[X] I have searched the issues of this repository and believe that this is not a duplicate.
[X] I am aware that Hydra team does not offer any support or help regarding the downloaded games.
[X] I have read the Frequently Asked Questions (FAQ).

we performed an API optimization that required a downtime.


exec format error

Hi, I'm trying to deploy the docker-compose.yml, but I'm getting exec error.
My compose looks like this
version: "3.8"

services:
  sptnr:
    container_name: sptnr
    image: krestaino/sptnr:latest
    environment:
      - NAV_BASE_URL=https://xxx.xxx.xxx
      - NAV_USER=xxxxxxxx
      - NAV_PASS=xxxxxxxx
      - SPOTIFY_CLIENT_ID=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      - SPOTIFY_CLIENT_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    volumes:
      - /srv/dev-disk-by-uuid-5b67514d-485e-4306-873e-b1cbb54ccf99/Config/sptnr/logs:/usr/src/app/logs

networks:
  omv1:
    external: true

I have added omv1 network because I have not enough non-overlapping IPs.
The first time I ran it I got:
root@openmediavault:~# root@openmediavault:~# docker-compose run sptnr
WARN[0000] network default: network.external.name is deprecated. Please set network.name with external: true
[+] Running 9/9
 ✔ sptnr 8 layers [⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                               12.3s
   ✔ 24e221e92a36 Pull complete                                                                                1.1s
   ✔ 6b9513afbd99 Pull complete                                                                                0.6s
   ✔ 55ea35dd0432 Pull complete                                                                                0.9s
   ✔ e544e6fd47b5 Pull complete                                                                                1.0s
   ✔ 9f311383358c Pull complete                                                                                1.4s
   ✔ 471c37cf8014 Pull complete                                                                                3.4s
   ✔ 261624c2de83 Pull complete                                                                                3.0s
   ✔ 9b17a06ed32b Pull complete                                                                                2.3s
exec /usr/local/bin/python: exec format error

I fixed the syntax of omv1 network like above (some apps want it in a way, some others in another) and in this case all I get is:
root@openmediavault:~# docker-compose run sptnr
exec /usr/local/bin/python: exec format error

Also tried to add /music to my Navidrome address AND local IP instead of public domain with same result.
EDIT I'm on Open Media Vault 6 x86.

I just pushed a new version which has better error handling. Please try the new version 1.1.0 and update your issue here with any relevant error messages. You can either pull the changes and build/run locally, or simply use the latest public Docker image.

I have the same problem; it looks like there are only ARM64 builds pushed to Docker hub. Running on x86 won't work.
https://hub.docker.com/r/krestaino/sptnr/tags

I just pushed a new version which has better error handling. Please try the new version 1.1.0 (or higher) and update your issue here with any relevant error messages. You can either pull the changes and build/run locally, or simply use the latest public Docker image.

I tried the docker-compose again with same exec error, I assume the problem is what basdp said. Anyway I'm not familiar with building from CLI, I always deploy from Portainer, which ins this case seems not pertinent, as this is more a "command" rather than a service. Although would be nice if it was and fired periodically.

@basdp Thank you for pointing that out.
I was able to reproduce this error on my x86 desktop. I have pushed a new version 1.3.0 which now supports linux/amd64 and linux/arm64. I just tested the new build on my x86 desktop and it's working now. Please pull the latest image and let me know if it's working for you now.

I keep getting exec error. Is it possible that the previous image is not being replaced? How do I clear it without prune command? I have many stopped containers that I don't want to prune, nor start all together. From Portainer I can select the single image I want to remove, but how do I do that from CLI?

@janaxhell You should be able to simply run docker pull krestaino/sptnr:latest to grab the latest image.

Yes, it's working now. I thought that since krestaino/sptnr:latest  was in the compose, it would pull when I ran the .yml file.
It is showing a lot of albums and songs scrolling now. It will take a long time, I have 33K albums. I'm curious to see how it will look after it's finished.


Disable Telemetry at Installation not working

Describe the problem
Hi, During the installation of the Bravo BI tool (0.9.1 using msi), I deselected the Telemetry options.  However when I saw the "Diagnostics" option the Telemetry button was active.
Bravo version
0.9.1
Tabular model
Power BI Desktop, import mode
Power BI
Power BI Desktop version March 2022
Steps to reproduce the behavior
No response
Additional context
No response
Screenshots

Anything else ?
No response

The option available during installation sets the default value to be used when starting the application for the first time - when the application has never been installed before. If telemetry is disabled during installation but subsequently re-enabled via the diagnostic options, then this latter setting wins and will be applied.
All application settings are stored in this JSON file %LOCALAPPDATA%\Bravo\usersettings.json. You can try closing the application and deleting (or renaming) this file. The next time you start the application you should find telemetry disabled, as you chose during installation.

@albertospelta - "but subsequently re-enabled via the diagnostic options" - sorry are you suggesting that I changed the setting after the installation?  I am pretty sure I did not re-enable the

@daryl-lynch-bzy,  thanks for your feedback! This could be a problem with the installer but unfortunately I cannot reproduce in my environment. Could you please provide the current values of these two settings?

telemetryEnabled property in user settings file %LOCALAPPDATA%\Bravo\usersettings.json
applicationTelemetryEnabled key in registry HKEY_LOCAL_MACHINE\SOFTWARE\SQLBI\Bravo\applicationTelemetryEnabled

If you rename the %LOCALAPPDATA%\Bravo\usersettings.json file and start the application again, what is the value of the telemetryEnabled property in the newly created file?
Thank you!

@albertospelta - It looks like the Reg is missing False value after the Install, so when the User opens Bravo for the first time, the setting forced by the App install is ignored.

Thanks for reporting and for the detailed repro steps! I located the bug and the fix will be available with the next release.

Fixed in 0.9.3


Is sentiment feature supported with "en-IN" or "hi-IN" locale in Speech-to-Text batch transcription service?

I am getting  {"code":"InvalidPayload","message":"This locale does not support sentiment analysis."} when I try to add sentiment to config properties.
Please clarify.

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

ID: 4de08d1f-8114-7bef-7ef4-022f79c69742
Version Independent ID: 4c0ceab9-24ed-de01-db30-31acf1de0f48
Content: Language support - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/language-support.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @IEvangelist
Microsoft Alias: dapine

I am using a standard subscription (S0).

@mansi-aggarwal-2504 Thanks for the question. We are investigating the issue and will update you shortly.

@PanosPeriorellis could you pleae have a look at this?

#reassign: @PanosPeriorellis

We will soon start supporting more locales. For the time being these locales are not supported.

@mansi-aggarwal-2504 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Develop

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

202 of 251 (80.48%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 67.192%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

compass/exceptions.py
5
6
83.33%

compass/dao/csv.py
69
72
95.83%

compass/views/api/student.py
5
50
10.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
2343

Relevant Lines:
3487

💛  - Coveralls


Remove erroneuous quotes in order to support docker v1.13.0

First and foremost, you should know this project is awesome. Keep up the good work!
When running an executable image for testing, the plugin is unable to correctly fetch the exit code of because the following exception is thrown:
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':project:runTestImage'.
Caused by: java.lang.NumberFormatException: For input string: "'0'"
        at org.stackwork.gradle.docker.tasks.ExecutableImageRunner.runExecutableImage(ExecutableImageRunner.groovy:86)
        at org.stackwork.gradle.docker.tasks.ExecutableImageRunner.runTestImage(ExecutableImageRunner.groovy:14)
        at org.stackwork.gradle.docker.tasks.ExecutableImageRunner$runTestImage.call(Unknown Source)
        at org.stackwork.gradle.docker.tasks.RunTestImageTask$_closure1.doCall(RunTestImageTask.groovy:21)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:588)
        at org.gradle.api.internal.AbstractTask$ClosureTaskAction.execute(AbstractTask.java:569)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:95)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:76)
        ... 69 more

This can be easily reproduced by creating a simple build.gradle file with the following contents:
task test {
    doLast {
        OutputStream exitCodeOutput = new ByteArrayOutputStream()
        exec {
            setCommandLine(['docker', 'inspect', '-f=\'{{.State.ExitCode}}\'', "STOPPED_CONTAINER"])
            setStandardOutput exitCodeOutput
        }
        println "Exit code: ${exitCodeOutput.toString().trim()}"
        println "The following line will throw an exception: "
        exitCodeOutput.toString().trim() as int
    }
}

This is how I fixed it in the branch:
task test {
    doLast {
        OutputStream exitCodeOutput = new ByteArrayOutputStream()
        exec {
            setCommandLine(['docker', 'inspect', '-f', '{{.State.ExitCode}}', "STOPPED_CONTAINER"])
            setStandardOutput exitCodeOutput
        }
        println "Exit code: ${exitCodeOutput.toString().trim()}"
    }
}

I've confirmed this patch to be working on my build environment.
The cause of the problem is that docker treats single quotes differently in v1.13.0. Also, in some way gradle seems to add quotes to the actual CLI command being executed and I couldn't figure out why. I've tested 4 different versions of docker to confirm.

Test results here
$ uname -a
Darwin 15.6.0 Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64 x86_64 i386 MacBookPro11,1 Darwin
$ docker --version
Docker version 1.13.0, build 49bf474
$ docker inspect -f="'{{.State.ExitCode}}'" $STOPPED_CONTAINER
'0'

$ uname -a
Linux 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ docker --version
Docker version 1.13.0, build 49bf474
$ docker inspect -f="'.State.ExitCode'" search_ingester_1
'0'

$ uname -a
Linux 4.9.6-1-ARCH #1 SMP PREEMPT Thu Jan 26 09:22:26 CET 2017 x86_64 GNU/Linux
$ docker --version
Docker version 1.12.6, build 78d18021ec
$ docker inspect -f="'{{.State.ExitCode}}'" $STOPPED_CONTAINER
0

$ uname -a
Linux 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ docker --version
Docker version 1.12.5, build 7392c3b
$ docker inspect -f="'{{.State.ExitCode}}'" $STOPPED_CONTAINER
0

$ uname -a
Linux 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ docker --version
Docker version 1.11.2, build b9f10c9
$ docker inspect -f="'{{.State.ExitCode}}'" $STOPPED_CONTAINER
0

Hey @nevers. I completely missed this PR. I will take a look at it this weekend. Thanks!

Question: did you check whether the fixed version still works on 1.12.6 ?
It would be good not to forcing users to upgrade to 1.13

I can confirm the fix is working in docker version 1.11.2.

I merged into a branch (so the build on Travis has the ENVs to decrypt the properties file), but somehow the build is failing on Travis:
https://travis-ci.org/stackwork/stackwork/builds/209302602
I need to see what this issue is - probably unrelated.
If there will be future commits on this PR, maybe it can be setup with 'support-docker-v1.13.0' as tracking branch, instead of master

This took some time because there was some work to be done on other things (Docker for Mac support, and a newer Docker version also broke a test case). Your commit is now being released under version 1.9.0.
Thanks for getting me back to work :)

Note that I rebased your commit, but you're still the author (only I don't see you under https://github.com/stackwork/stackwork/graphs/contributors :( )


Port to better-files and remove fs-component

Coverage increased (+0.05%) to 97.17% when pulling 4a14df1582af78a31545bdfc913dd119d203eee5 on jaa127:master into 49a0839bc19247399c9c1990179f94bb234190bb on sn127:master.


Builder with CDATA doesn't work !

Hi guys,
I have a problem on the builder with CDATA. Here is just a simple example on ReadMe:
`var xml2js = require('xml2js');
var obj = {root: {$: {id: "my id"}, _: "my inner text"}};
var builder = new xml2js.Builder({ cdata: true });
var xml = builder.buildObject(obj);`
Xml generated:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <root id="my id">my inner text</root>
So it misses CDATA wrapping "my inner text"
I see the code of node-xml2js, because of this line: https://github.com/Leonidas-from-XIV/node-xml2js/blob/aefc64af9e9badbd0aade00814548f2ea33c9b4e/src/builder.coffee#L7
requiresCDATA = (entry) ->   return typeof entry is "string" && (entry.indexOf('&') >= 0 || entry.indexOf('>') >= 0 || entry.indexOf('<') >= 0)
I think we don't need that. Because it tested _ and option cdata of builder
Can you vote this to remove this condition. Thank you

Yes please! I have to generate xml for a foreign application and they will throw an error if certain fields aren't wrapped in CDATA.
So either remove the condition or have the cdata flag as a tristate option like true | false | 'force' where force overrides the condition, that way you stay backwards compatible.

I fixed that on this repository: https://github.com/brunovuftv2018/node-xml2js

Yes please! I have to generate xml for a foreign application and they will throw an error if certain fields aren't wrapped in CDATA.
So either remove the condition or have the cdata flag as a tristate option like true | false | 'force' where force overrides the condition, that way you stay backwards compatible.

yes, I met the same problem. Please remove this condition or perhaps add anothor option named forceCdata?


makefile image targets should be updated to use the quay.io registry

there are a bunch of old gcr.io based registry targets in the makefile, these should be replaced to use the current image location at quay.io/cluster-api-provider-kubemark.

/remove-lifecycle stale


this component can’t run in IE11 and safari5.1?

That may be. I’ll check and fix this asap, thanks!

Can confirm this as I am having the same issue right now.
It occurs because IE11 does not support shorthand functions like:
{
  mounted() {},
  watch() {},
}

So it needs to be transpiled for ES5 support.

Oh right, I forgot to add babel again after a rollup update. I’ll fix this asap when I’m back from my current roadtrip. Thanks for finding out!

i just released a hotfix version 1.2.4 with included babel build. i would see this issue as fixed. let me know if problems still occur. cheers 🍻

@headione This seems to be an issue again. If you see in the dist script there is a => use    https://github.com/KitchenStories/vue-gallery-slideshow/blob/caf6ad7739b953de2066c2b33e5de65d27d0b8a4/dist/js/vue-gallery-slideshow.js#L303 which is not es5 compatible.


add help button for how to pop out video in firefox

Possible quick fix for https://github.com/microsoft/pxt-arcade/issues/5490, since firefox doesn't support picture in picture api / have there own way to do it.

We'd have to write a quick markdown page at /firefox-picture-in-picture which I didn't do, but would likely largely be similar to https://support.mozilla.org/en-US/kb/about-picture-picture-firefox

LGTM, but should we wait until we have the docs to check in?

Could we do an anigif to quickly show how instead? Something that appears in a div when you click that button?

Primary object for the students is to watch the video and popping out is secondary action only if required.  This long text makes me think, students will try to click or play with the button instead of watching the video. Just keep the old "Pop out" and take them to the documentation page for firefox? It is also not worthwhile to spending engineering effort on this as Firefox is less than 1% of our use base.

I'm kind of worried that the pop-out markdown would cause more trouble than the video.  Even with the button, they're probably pretty likely to click that full-screen icon.
This is a tough one,


Contribution Guide

Please review the draft document and comment below.
Contribution Guide v2.pdf

Thanks Ryan.
Most of this matches my experience from other teams/projects I've been working with. A few points I'd like to raise:

In other projects, I have seen a separate category for issues containing bug reports. These typically do not really fit into the pattern of "As x I want y".
I agree the description (and sometimes the title) should be modified to reflect the latest state of discussion. However, at some point we must "finalize" the description, because we cannot develop against a moving target. (Double quotes around "finalize" because during development issues may arise that require changing the description again.)
I'm not sure about the labels. My first impression of the issues list in your repo is that there's too much of them, but perhaps I only need to check on filters etc.


tapgarden: add FundBatch and SealBatch requests

Closes #820
Update the minting state machines to move batch funding into a separate command that can execute before batch finalization. Add a new command to supply group anchor witnesses before batch finalization.
Remaining TODOs:

[x] derive seedling script keys in prepAssetSeedling
[x] DB migration to add seedling script key reference field
[x] Update DB queries to write & fetch seedling script key
[x] Update DB queries to write & fetch batch TX
[x] derive group internal key in prepAssetSeedling
[x] Update DB queries to write & fetch seedling group internal key
[ ] Extend tapdb/asset_minting tests to cover new query params
[ ] Add tests for tapdb/asset_minting/CommitBatchTx
[x] Resolve FinalizeParams handling wrt. fundBatch
[ ] Extend tapgarden/planter_test test to cover FundBatch and SealBatch
[x] Implement SealBatch
[x] Remove batch ticker from caretaker and tapgarden tests

Will be pulled out of draft and merged this sprint

Feature work is done IMO, follow-on work can happen in a separate PR as this one has already ballooned quite a bit.
Remaining tasks are just unit test coverage AFAICT, should add some usage in an itest as well.

One DB change is actually missing from this PR, related to group key handling. We need to also associate a [32]byte with a Seedling, which would later map to a GroupKey.TapscriptRoot. Without that, a user could not later provide a custom tapscript root for a group key, and if they generated witness using such a root they would not verify with the group virtual TXs made during sealBatch.

Updated to address some feedback and update tests to exercise query changes. Also fixed some issues with not accepting externally-set seedling script keys and group internal keys.
Hitting some issues with minting DB tests around using the seedling group tapscript root.
From discussion offline, I think the simplest behavior for FundBatch and SealBatch would be that they can be called exactly once before Finalize. Its straightforward to detect if a batch is funded or sealed, so it should also be straightforward to return an error here and require the batch to be resubmitted.

Added logic to reject FundBatch and FinalizeBatch calls when the pending batch is already funded.
Updated minting DB tests for the new seedling key handling, and for better coverage.
We had some behavior around group verifiers that assumed that the group tapscript root was always empty, which is fixed.
I also removed the old static DeriveGroupKey func, as it is no longer appropriate with all the new seedling options (and it wasn't being tested in the VM tests either).
Also added a test around making a batch with external seedling keys and actually using FundBatch.
Moving on to the follow-up PR but will some spots here like new queries around seedling groups still need tests added.

Rebased.

Needs another rebase to apply new linter rules, then a couple of fixes for the new rules.


MB-2345 TOO OrdersDetailForm - Storybook

Description

Given that I am the DEVELOPER/DESIGNER
When I navigate to Storybook
Then I am taken to a page where I can see the OrdersDetailForm component
And I can interact with the component fields

Connecting the component and creating the DocumentViewer page layout will be done in this story here: LINK
Reviewer Notes
Is there anything you would like reviewers to give additional scrutiny?

This PR introduces a few new inputs for Formik:

DatePickerInput
DropdownInput
DutyStationInput (Needs some major refactoring that will be done in here: LINK)

Setup
Add any steps or code to run in this section to help others prepare to run your code:
yarn install
make storybook

Navigate to Storybook: http://localhost:6006/?path=/story/too-tio-components-ordersdetailform--with-buttons
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Messages

:book:
:link: MB-2345

  Generated by :no_entry_sign: dangerJS against ffdf3fe663c133945b2874caede981a4b0980c36


conformance results for v1.7/hauwei.

THis is PR about conformance results for v1.7/hauwei.
1、The some PR need commit to https://github.com/cncf/k8s-conformance fewer days later.
2、README.md and PRODUCT.yaml need you preview, and make some suggestion.
3、 I will supply other files laters.

It need your preview.  I'll supply others file, such as e2e.log, junit_01.xml, and modify  version.txt later. Thanks @deepak-vij  @quinton-hoole

This is  conformance testing report,  and have one given failure.
I also follow this opening PR( https://github.com/cncf/k8s-conformance/pull/24 ) step, that 's ok, i will commit another PR about it. @deepak-vij @quinton-hoole @kevin-wangzefeng


Fail to install dependencies on Centos7.2

Detected that this is a Fedora-based distribution.
No compiler is specified. Default compiler is clang++.
We currently are unable to support clang++ installation on Fedora distributions.

Hi @huangll99. I have been unable to build the project with clang on Fedora, so we have to default to using gcc instead. If you build with the -g flag, that will tell the script to use gcc instead of clang. Let me know if you have any other questions.

Hi @huangll99. I have been unable to build the project with clang on Fedora, so we have to default to using gcc instead. If you build with the -g flag, that will tell the script to use gcc instead of clang. Let me know if you have any other questions.

thanks a lot


Fix argument in README

What's this PR do?
update README.md (remove extra argument)
Where should the reviewer start?
README.md
What are the relevant tickets?
#166

Thanks 👍


how to run tests

some quick docs on how to get a test environment set up would be nice. Assuming:
vagrant up
vagrant ssh
make test

... but I'm not sure

just wrote it up here.
https://github.com/progrium/dokku/pull/1064


update leaflet to 1.8.0 to fix demo in Safari

resolves #46
ref: https://github.com/Leaflet/Leaflet/issues/7255

Thanks!

no worries at all. your issue reminded me i had a few TODO:s of my own. 🙏

Hi! i update to leaflet 1.9 and i cant see my layers. Any solution?

i know 1.9 included some breaking changes. if you can share a simplified repro case that shows exactly what the issue is that'd make it more convenient to track down the problem.

This is my app. Works ok on all devices except ios
mapa.desarrolloi.org/
My repo
https://github.com/Nicocaputocai/LanusInteligenteMapa
I worked with GeoJSON files

by 'repro case', i mean sharing the bare minimum of code necessary to display the problem you're seeing.
this library doesn't do anything in the way of 'drawing', so if you aren't seeing GeoJSON files in iOS only. it'd be worth whittling things down to confirm that its not a problem with Leaflet itself.

Oh, sorry. I speak English a little.
Here i create the popups
function onEachFeature(feature, layer) {
// does this feature have a property named popupContent?
if (feature.properties && feature.geometry.type != "Polygon") {
return layer.bindPopup(

${feature.properties.name}
Dirección: ${feature.properties.address} ${feature.properties.height}
);
}else if (feature.properties && feature.geometry.type == "Polygon"){
return layer.bindPopup(

${feature.properties.name}
Dirección: ${feature.properties.address}
)
}
}
async function setMap(arr) {
var map = L.map("map", {
center: [-34.7033363, -58.3953235],
zoom: 13,
"tap": false
});
One example
var health = L.geoJSON(healthData, {
onEachFeature: onEachFeature,
pointToLayer: function (feature, latlng) {
if (feature.properties.dependence == "Municipal") {
return L.marker(latlng, { icon: healthIconMunicipal });
} else if (feature.properties.dependence == "Provincial") {
return L.marker(latlng, { icon: healthIconProvincial });
} else {
return L.marker(latlng, { icon: healthIconPrivate });
}
},
var overLayers = {
Clubes: club,
"Dependencias Municipales": MunicipalDependence,
"Educación Inicial": initialEducation,
"Escuelas Primarias": primaryEducation,
"Escuelas Secundarias": hightSchollEducation,
"Escuelas Técnicas": tecnicalHightSchollEducation,
Universidades: universityEducation,
"Otros establecimientos educativos": otherEducation,
"Parques y plazas": squareAndPark,
Salud: health,
"Seguridad y Justicia": security,
Transporte: transport,
};
L.control.layers(overLayers, baseMap).addTo(map);
    })

return arr;

none of the code you shared comes from arc.js so there's not much we can do about your problem here.
https://github.com/springmeyer/arc.js#api


No preferences tab in firefox

Hi,
Really cool idea! Hope I can make it working :)
On Firefox 115.11.0esr, the tool shows "can't read and change data on this site".
Clicking the cog gear takes me to the addons dialog, but I there's no preferences tab to enable it for my site.

oh, web tools :)


Node.js compatibility fix

Node.js runtime doesn't provide self referring to DOM window object.

@postspectacular Looking at the issues and PRs, it looks like you don't have much time maintaining this project. I would be more than happy to participate.


remove unneeded base_class assignment

think this assignment can be condensed since (base_class = rbac_base_class(klass)) isn't doing much
@miq-bot add_label cleanup
 139/365 = 0.3808

@miq-bot assign @kbrock

        else
          target_ids    = targets.collect(&:id)
          klass            = targets.first.class.base_class unless klass.respond_to?(:find)
        end

is from https://github.com/ManageIQ/manageiq/commit/b0eb62f6d57d3da81a753a81ddc2d048dc3a52b9
else
          target_ids = targets.collect(&:id)
          klass         = targets.first.class
          unless klass.respond_to?(:find)
            if klass.respond_to?(:base_class) && rbac_class(klass).nil? && rbac_class(klass.base_class)
              klass = klass.base_class
            end
          end
        end

is from https://github.com/ManageIQ/manageiq/commit/f32c23c4cf3464cc87fb8a08fe7d0fc0adb0e009
and then we moved that logic out into a separate method in
https://github.com/ManageIQ/manageiq/pull/14665/files#diff-d358bd713792676d3c2a55f77c9bb7fcac1c8cea70a8e43de01c8c0a3e64caf4L216
and then the find check got added to handle the MiqAeDomain weirdness

think this ensures that rbac base class is not nil. Think there was an automate use case that madhu had that did not return a value. Think there was only one class that failed.
think it was a child class that was legit but not the parent class.
sorry, answer foggy here

think this ensures that rbac base class is not nil. Think there was an automate use case that madhu had that did not return a value. Think there was only one class that failed.
think it was a child class that was legit but not the parent class.
sorry, answer foggy here

The only place base_class seems to be used in this method is on line 266 where it gets reset anyway

The only place base_class seems to be used in this method is on line 266 where it gets reset anyway

I just didn't understand the intent, but that makes more sense. I'm fine with this getting closed, mostly I just needed a commit for seventeen days ago.

I just didn't understand the intent, but that makes more sense. I'm fine with this getting closed, mostly I just needed a commit for seventeen days ago.

thank you @lpichler for your awesome git commit message f32c23c4
This is how I remember it and there may be an edge case that I don't know...
We are ignoring  acts as active record (i.e.: responds_to?(:base_class))
We are also ignoring the case where this class is not supported by rbac (i.e.: rbac_class(klass.base_class).nil?)
ok, we want to do the rbac class of the base class for everything
Well, of course there is a special case. While Domain is a subclass of Namespace, they are both supported. So for that one case, do rbac_class(klass). We probably want to keep using Domain so we can use the default_scope.
@lfu and I already have found that Domain should not really be a subclass of Namespace, but it is tricky to get rid of STI classes and add tables, so it is basically left alone.
Once we do separate out those classes out, I'm pretty sure we can change this to rbac_class(klass.base_class), well - given that it has base_class and it is supported by rbac_class.

thank you @lpichler for your awesome git commit message f32c23c4
This is how I remember it and there may be an edge case that I don't know...
We are ignoring  acts as active record (i.e.: responds_to?(:base_class))
We are also ignoring the case where this class is not supported by rbac (i.e.: rbac_class(klass.base_class).nil?)
ok, we want to do the rbac class of the base class for everything
Well, of course there is a special case. While Domain is a subclass of Namespace, they are both supported. So for that one case, do rbac_class(klass). We probably want to keep using Domain so we can use the default_scope.
@lfu and I already have found that Domain should not really be a subclass of Namespace, but it is tricky to get rid of STI classes and add tables, so it is basically left alone.
Once we do separate out those classes out, I'm pretty sure we can change this to rbac_class(klass.base_class), well - given that it has base_class and it is supported by rbac_class.


release 0.5.1

Ⅰ. Describe what this PR did
release 0.5.1
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #952 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #952   +/-   ##
==========================================
  Coverage      37.17%   37.17%
  Complexity      1027     1027
==========================================
  Files            225      225
  Lines           8906     8906
  Branches        1070     1070
==========================================
  Hits            3311     3311
  Misses          5209     5209
  Partials         386      386

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 966561b...bf832ea. Read the comment docs.


tests: net: socket: tls: Fix race on TCP socket close

One of the tests closed the underlying TCP connection right after establishing one. This caused a certain race between incoming TLS handshake data and entering FIN1 state (experienced on nrF52840), where the TLS handshake data could be received after the FIN1 state was entered, causing the server side to send RST packet. This disrupted the test flow, as graceful TCP connection teardown was expected.
Fix this, by adding a small delay for such case to avoid the race.
Fixes #66871

CC @katgiadla


Update Composer dependencies (2021-02-17-00-03)

Visual regression test passed!
View the visual regression test report


Move language selection buttons

Suggest moving the buttons for selecting interface languages to the top of the page and consolidate into one dropdown menu

I'm not sure about this. There's not much room up top, and in TracPro (assuming we want these dashboards to be consistent) there's even less room. Language selection will usually be a infrequently used function that users set from their first login page and leave.

Agreed. Time to close this one out.
On Thu, Feb 19, 2015 at 12:06 PM, Rowan Seymour<EMAIL_ADDRESS>wrote:

I'm not sure about this. There's not much room up top, and in TracPro
(assuming we want these dashboards to be consistent) there's even less
room. Language selection will usually be a infrequently used function that
users set from their first login page and leave.
—
Reply to this email directly or view it on GitHub
https://github.com/rapidpro/chatpro/issues/8#issuecomment-75009665.


Add Assertion to the SharedTimer Test

Is your feature request related to a problem? If so, please give a short summary of the problem and how the feature would resolve it

When I am walking through the unit test of the mssql-jdbc, I noticed that currently the SharedTimerTest does not contain any assertion statement to verify the behavior and state of the SharedTimer after execution of its getTimer() method in a multithreaded environment. The test ensures that references are added and removed, but does not assert the expected state of the SharedTimer (e.g., it is stopped and cleaned up properly after all references are removed). This could potentially mask issues with how SharedTimer manages its lifecycle and resources.
Current Implementation:
@Test
    void getTimer() throws InterruptedException, ExecutionException, TimeoutException {
        final int iterations = 500;

        ExecutorService executor = Executors.newFixedThreadPool(2);
        try {
            ArrayList<CompletableFuture<?>> futures = new ArrayList<>(iterations);
            for (int i = 0; i < iterations; i++) {
                futures.add(CompletableFuture.runAsync(() -> SharedTimer.getTimer().removeRef(), executor));
            }

            CompletableFuture.allOf(futures.toArray(new CompletableFuture[0])).get(2, TimeUnit.MINUTES);
        } finally {
            executor.shutdown();
        }
    }

Describe the preferred solution

I'd like to propose a minor improvement by adding a simple assertion at the end of the getTimer test method to verify that the SharedTimer has indeed been stopped and its resources have been cleaned up after all references to it have been removed. This could be accomplished by asserting that SharedTimer.isRunning() returns false, indicating that the internal ScheduledThreadPoolExecutor has been shut down and the SharedTimer instance has been cleaned up. Here is the suggested code snippet for this improvement:
    @Test
    void getTimer() throws InterruptedException, ExecutionException, TimeoutException {
        final int iterations = 500;
        ExecutorService executor = Executors.newFixedThreadPool(2);

        try {
            ArrayList<CompletableFuture<?>> futures = new ArrayList<>(iterations);
            for (int i = 0; i < iterations; i++) {
                futures.add(CompletableFuture.runAsync(() -> SharedTimer.getTimer().removeRef(), executor));
            }

            CompletableFuture.allOf(futures.toArray(new CompletableFuture[0])).get(2, TimeUnit.MINUTES);
        } finally {
            executor.shutdown();
            if (!executor.awaitTermination(800, TimeUnit.MILLISECONDS)) {
                executor.shutdownNow();
            }
        }

        assertFalse(SharedTimer.isRunning(), "SharedTimer should be stopped after all references are removed.");
    }

Describe alternatives you've considered

An alternative would be to incorporate more detailed logging within the SharedTimer class regarding its state transitions (e.g., when references are added or removed, and when it starts or stops). While this would provide more insight during test execution, it would not replace the need for explicit assertions to verify the correct behavior programmatically.
Additional context

Reference Documentations/Specifications

This suggestion does not directly relate to any specific JDBC Specifications.

Reference Implementation

If this suggestion is helpful, I am more than happy to submit a Pull Request to implement the refactoring.

hi @Codegass
this sounds reasonable yes please submit a PR it will go through the review process, thanks!

closing, please go ahead and submit a PR your convenience it will go through the review process

Sure! I will submit the PR ASAP. Thanks.

Reopening since there is now a PR to address this.


Add "common issues" doc to cover known workarounds

I'm happy to write a first draft of this if the maintainers would like it. But I don't want to put in the effort if it's not wanted.
I've run into two issues which really puzzled me in terms of what to do until I poked around in issues here. I'm sure there are others.
hybrid_property can't use the special magic of property in mypy, but #98 has a workaround seems to work. And #94 covers ways of getting UUID(as_uuid=True) to work.
It would be helpful (since these are not going to be fixed soon) if this library made these workarounds part of its docs. It could be done at the end of the readme or in a separate markdown doc linked in the repo.

#114 also has a workaround for Enum.


Missing suggestions for nested neighbor modules.

Environment data

Language Server version: 2022.9.40
OS and version: Windows 10 Version	10.0.19044 Build 19044 | Ubuntu 22.04 LTS
Python version (& distribution if applicable, e.g. Anaconda): 3.9 | 3.10

Repro Steps
Assume following project structure (open in Visual Studio Code).
Project must be correctly configured python package, installed into virtual environment.
source/
    project1/
        nest1/
            sub1/
                mod1.py
                __init__.py
            sub2/
                mod2.py
                __init__.py
        sub3/
            mod3.py
            __init__.py

All files are empty.
Now let's populate mod1.py with:
class SomeSymbol:
    pass

Then lets open mod2.py and start typing:
SomeSym

Do same thing for mod3.py
Expected behavior
class SomeSymbol should be suggested everywhere, both in mod2.py and mod3.py.
Actual behavior
class SomeSymbol is suggested in mod3.py but its not in mod2.py
Additional information
When suggestions work correctly for "flatter" projects, ie.
source/
    project1/
        sub1/
            mod1.py
            __init__.py
        sub2/
            mod2.py
            __init__.py
        sub3/
            mod3.py
            __init__.py

Suggestions are available everywhere.
I can not provide logs as issue was found in non public environment. I'll provide them later if necessary.

Project must be correctly configured python package, installed into virtual environment.

Are you saying that there's an editable install involved here? If so, can you provide more explicit instructions on how that should be configured in your sample?

Yes, but I'm not 100% sure. It is possible that some of environemnts, I have used, were based on editable builds while others were constantly reinstalling packaged build. I'm considering example similar to this package. I have recently moved to use poetry with simpler setup, but problem still occurs and I haven't fully set up any public project latter way. If you are willing to use async_py_octocat, you will have to follow this instructions. Otherwise it should be possible to reproduce this issue with minimal poetry project (easiest to acquire) with poetry init followed by poetry shell and poetry install or dev branch of this repository (last one is what i used).
I am willing to help more with reproduction but I have to know which method, out of listed, is prefrerred.

I am willing to help more with reproduction but I have to know which method, out of listed, is prefrerred.

Whichever you prefer is fine with me. If an editable install is involved, I'm wondering if you may be hitting the issues described here.

Closing since there's been no response in more than a month. We can reopen if you are able to provide more info.


Create a better DateTimeWidget.

Right now a datetime field is handled by a very simple text widget expecting the user to enter a JSON valid datetime.
We should provide a better UX by default, through a more advanced, convenient and usable widget.

WiP


Regressions: v5 RC breaks all touchables by react-native-gesture-handler in FlatList

@andreialecu I can tell you that I've upgraded and the first thing I realized is that that new release is breaking the swipe behavior in my view. I can only swipe tabs now when I place my finger on the tabs directly or when I swipe in the header area or on a view that does not use touchables by RNGH.
It does not play nicely with RectButton, BaseButton etc by react-native-gesture-handler anymore. It does work with RN-Touchables (which should not be used in FlatLists anyway, because they don't work nicely with FlatList, activating with scroll which they should not)
It does work with TouchableOpacity, TouchableWithoutFeedback etc (from react-native) though
v4 did not had any issues with RectButton
P:S: Can't select "issue" as "issue", only Feature Requests and Questions.

For now (with a broken heart), I swapped RectButton with TouchableWithoutFeedback.
I really did nothing but upgrading and got those weird TabNameContext issues. Could not reproduce that after upgrade to RC.4 for now - weird (maybe metro bundle cache or some node_modules weirdness again when working with monorepos)
Ok, whats left is RNGH :/

If you'd like to help out to figure out if there are any workarounds, or the reason for the RNGH issue it would be greatly appreciated.

Are you importing Flatlist from RN or from RNGH? Usually it's enough to use Flatlist by RNGH to get rid of touchable issues (it's also preferred when working with gestures).

Hm... dang. I'm also seeing my items disappear sometimes now, like when you use removeClippedSubviews. It happens very randomly, have to investigate further

I filed an issue at both repos

Just figured that containerStyle is also not working with the new RC. Had to make small adjustments

My PR has been merged, it was an issue with pager-view. A new version has been released.

Other regressions:

useTabsContext must be inside a Tabs.Container.
useTabNameContext muss be inside a TabNameContext

I am not even using this. Its coming from the FlatList Implementation.

I was facing the same issue. The error disappeared after I changed Tabs.ScrollView for Animated.ScrollView.


Develop with live-compilation, bundle for production

Is it possible to utilize System.js' transpiler feature to develop locally, then when ready, use aurelia-bundler to deploy? I can't figure out how to make that work, since in the config i specify to look in my src folder, but when it's bundled, it will be in a different folder, such as dist. Is this possible? if so, could someone show me an example config that supports this?

It is possible, but not smth you want - too slow. For example i even bundle all 3rd party resources in development and leave my app code unbundled until going to production.

@atsu85 Do you have an example of it working the way I'm describing?
Also, are you saying that you run bundle on your 3rd party resources, then do what I'm describing above for your source code? Because I could be down for that.

We would recommend other build setups such as webpack of cli.

@LordZardeck

Do you have an example of it working the way I'm describing?

NO! As I said:

It is possible, but not smth you want - too slow.

The development process with System.js transpiler (in browser) would be way-way-way too slow. For me even the default skeleton setup where in development mode You don't have anything bundled is too slow. So to waste less time on each refresh

i even bundle all 3rd party resources in development and leave my app code unbundled until going to production.

So to achieve that setup where only 3rd party assets are bundled (but not my app-specific code), i have budnles.js:
// based on https://github.com/aurelia/skeleton-navigation/blob/master/skeleton-typescript/build/bundles.js
module.exports = {
  "bundles": {
    "bundled-app": {
      "includes": [...],
      "options": {...}
    },
    "bundled-vendor": {
      "includes": [...],
      "options": {...}
    }
  }
};

and gulp tasks look smth like this:
// based on https://github.com/aurelia/skeleton-navigation/blob/master/skeleton-typescript/build/tasks/bundle.js
...
var config = { ...};
gulp.task('bundle', ['static',  'html', 'typescript'], function() {
  return bundler.bundle(config);
});

gulp.task('bundleVendor', ['unbundle', 'static',  'html', 'typescript'], function() {
  return bundler.bundle(getBundleConfig(config, "bundled-vendor")); // <-- WHAT SHOULD BE BUNDLED
});

gulp.task('unbundle', function() {
  return bundler.unbundle(config);
});

function getBundleConfig(config, bundle) {
	if(bundle) {
		for(someBundle in config.bundles) {
			if(bundle !== someBundle) {
				delete config.bundles[someBundle];
			}
		}
	}
	if(Object.keys(config.bundles).length < 1) {
		throw new Error("Didn't find bundle config by bundle name '" + bundle + "'");
	}
	return config
}

I hope it helps someone who wants to continue with jspm + SystemJS (as opposed to aurelia-cli that looks great as well or webpack that has its own pros and cons).

The reason I want to do it regardless of speed, is conscience. Being able to have a coworker just run it without having to install some build process would be a huge win for us


Added intersectsLine for Ellipse, Circle, added game.debug.geom(ellipse)

This PR:

changes the public-facing API

Describe the changes below:
added:

Added intersectsLine for Phaser.Circle, Phaser.Ellipse
Added Ellipse geom debug Phaser.Utils.Debug#geom

intersectsLine checks for intersection points for Circle vs Line , Ellipse vs Line. Returns true or false by default or optionally returns an array of intersection points. The formula is from:
http://www.ambrsoft.com/TrigoCalc/Circles2/Ellipse/EllipseLine.htm
It also uses Phaser.Line#pointOnSegment to return true only if one or two points lie on the line segment.
demo (includes game.debug.geom(ellipse)):
https://codepen.io/Samid737/pen/GvejyO
or:
https://samid737.github.io/phaser-ce/

Thanks. Saving this for 2.9.0.

I reset my own fork to the upstream master to make sure i'm up to date with 2.8.7 . Didn't think that the PR would be changed :(...... I was just about to make a new PR for interpolateColor in HSV...........

I still have it in https://github.com/photonstorm/phaser-ce/tree/pr/341.


Time To Complete Shows Hours if Needed

Depending on the install size of selected Updates and large applications installers like Autodesk or Adobe, FFU builds can take more than an hour. The display then rolls over the minutes and looks a little strange.

Add Hours, Minutes and Seconds to Total Time to Complete if total time has gone over 1 hour. Else only shows the minutes and seconds.

What's the size of the FFU when Adobe or Autodesk is installed? Just curious.

What's the size of the FFU when Adobe or Autodesk is installed? Just curious.

About to deploy a new Creative Cloud All Apps Sutie for a new Image. I will build it and let you know.
just for example though, a download of Autodesk with CAD and Inventor 2024 is sitting around 20Gigs just for the offline installer.  These apps are huge and Intune is not gonna work in these situations. The other option is everyone logs into their Cloud accounts and pulls down the Click to runs, but this a huge bandwith and time suck. 😞

So, I just did an Autodesk build and the FFU is now 19.6 Gigs. Thats with all the Apps Updated and Install Office to True.
Had I added the Update Latest CU it might be slightly bigger and would have taken more time, as this run was an hour and 10 mins.
I need to supply the -DiskSize 50GB now, as the last run had me down to 200mb to spare before sysprep.


Move all_tuples and friends into its own crate

FYI I'm merging the simple fix in #15933 now, but I do think we should move fully to this. It does make me think we should pull all_tuples out into its own crate though: I'm not a fan of bevy_math relying on bevy_utils.

Originally posted by @alice-i-cecile in https://github.com/bevyengine/bevy/issues/15936#issuecomment-2415352291

This should be part of the Bevy extended universe, over with atomiccow. The name of the crate should not have "Bevy" in it to encourage broader adoption.

To commence the bikeshedding, I propose polytuple as a name.

variadics_please gets my vote.

Oh in line with the not-BSN crate, i-cant-believe-its-not-variadics

I like variadics_please, but maybe we should also consider keeping the name all_tuples (assuming someone else hasn't taken it)? Especially considering it's a fairly known about macro in the community.

I think that putting variadics into the crate name in some form is helpful for searchability. I also think it's a natural home for any other variadic-related functionality that Bevy or other users might need.

Since bevy_utils/macros only contains all_tuples! and all_tuples_with_size!, it seems like the steps are pretty straightforward:

Reserve the name variadics_please on crates.io
Create the repository bevyengine/variadics_please
Copy bevy_utils/macros into the new repo, polish the documentation, etc.
Publish
Update bevy_utils to re-export variadics_please, or update the other crates to directly use variadics_please instead.

https://crates.io/crates/variadics_please


[Feature] : Music Selection Dropdown during the simulation

Here's a breakdown of the feature implementation
Introduced a dropdown element in the HTML code, offering options for different background music tracks.
Initially, the dropdown is hidden using inline CSS styling (style="display:none;"). It becomes visible dynamically through JavaScript when the submit button is clicked to start the simulation.
Users can select background music tracks from the dropdown without reloading the page, thus improving usability and convenience.
Sound effects were integrated into the simulation section, eliminating the need for them in the form. This streamlines the user interface and ensures consistency.
The addition of the music selection dropdown provides users with the flexibility to customize their simulation experience, enhancing overall appeal and engagement.
The implementation involved adding an HTML element with music options, dynamically showing the dropdown using JavaScript, and implementing functionality to change background music based on user selection.
Fixes #78
Demo video
https://github.com/sk66641/Random-Disco-Light-Simulator/assets/92214013/49ecb990-bb73-404f-8edb-b6a53d7148af
@sk66641  please review this pull request and merge this under gssoc labels

@aditya-bhaumik
can you add an option  "none" so that user after selecting any sound if he/she wants to deselect it, there should be an option
and make "div with id 'particles-js' " display as "none"?

@sk66641 i have added the changes you told to make but while merging the code to resolve the conflicts caused by the other pull request i by mistake made a error because of which the randomize button or the code added in the other pull request could you please help me
Right now i have added the none as you had asked in the dropdown but the randomize button got removed and trying to add it is causing more conflicts

@aditya-bhaumik
you can revert your changes and add 'none' option and create pr, i'll try to resolve the conflicts or you can also make changes once again on the current code base.

@sk66641 i have made all the changes you requested and resolved the conflicts i was having i have created another pull request please review and merge it
also please close this pull request thank you
the pull request is #111


Add markdown linter check at PR

This job only check updated files
Fix a few of the lint errors that we got
Solves #2

We will need to ignore a few markdown linting rules and I will update the PR with these.

Even though I have ignored the errors in .markdown-lint.yml github/super-linter don't seem to respect it. I have seen similar issues in the grafana-operator repo...
I do not get these issues locally using the cli tool manually nor when i used the container they provide:
docker run \
  -e RUN_LOCAL=true \
  -e ACTIONS_RUNNER_DEBUG=true \
  -e DISABLE_ERRORS=false \
  -e ERROR_ON_MISSING_EXEC_BIT=true \
  -e LINTER_RULES_PATH=. \
  -e MULTI_STATUS=false \
  -e VALIDATE_ALL_CODEBASE=false \
  -e VALIDATE_MARKDOWN=true \
  -v $(pwd):/tmp/lint \
  ghcr.io/github/super-linter:slim-v4

2021-09-14 14:25:03 [INFO]   File:[/github/workspace/docs/xks/developer-guide/cloud-resources.md]
2021-09-14 14:25:04 [DEBUG]   Found errors. Error code: 1, File type: MARKDOWN, Error on missing exec bit: false
2021-09-14 14:25:04 [ERROR]   Found errors in [markdownlint] linter!
2021-09-14 14:25:04 [ERROR]   Error code: 1.  Command output:
------
/github/workspace/docs/xks/developer-guide/cloud-resources.md:64:1 MD037/no-space-in-emphasis Spaces inside emphasis markers [Context: "** Golang **"]
/github/workspace/docs/xks/developer-guide/cloud-resources.md:70:1 MD010/no-hard-tabs Hard tabs [Column: 1]
/github/workspace/docs/xks/developer-guide/cloud-resources.md:73:1 MD010/no-hard-tabs Hard tabs [Column: 1]
/github/workspace/docs/xks/developer-guide/cloud-resources.md:98:1 MD037/no-space-in-emphasis Spaces inside emphasis markers [Context: "** C# **"]

As a wokaround i have added
<!-- markdownlint-disable -->
<!-- markdownlint-restore -->

It will have to do for now.
I might rewrite the CI solution and stop using the super-linter and just use a node agent and install the cli tool and run it locally.


Biabduction fails to detect NPE in presence of goto-s and if statements

I am playing with an Go frontend for Infer where goto-s are (arguably) a more acceptable way of altering control flow than in C/C++, and while testing biabduction (with C) I noticed that it does not detect a case which it probably (maybe?) should:
int foo() {
	int *p = 0;
	for (int i=0; i < 7; i++) {
		if (i == 1) {
			goto label;
		}
	}
	return 42;
label:
	return *p;
}

Please note that if to goto is unconditional, the NPE will get detected.
I was wondering if this is intentional or perhaps it is indeed due to some current limitation.

But I don't see any reason for this to be reported with low confidence though. We should try to understand what is happening here.


Add dovetech

Hi @notrab,
I would like to suggest adding Dovetech to the list.
Thanks

Looks great! Thanks


how to use ChoiceType?

Checklist

[X] The bug is reproducible against the latest release or master.
[X] There are no similar issues or pull requests to fix it yet.

Describe the bug
sqladmin.exceptions.NoConverterFound: Could not find field converter for column symbol (<class 'sqlalchemy_utils.types.choice.ChoiceType'>)
my code like this :
condition_choices = [(0, '='), (1, '/='), (2, '>'), (3, 'include'), ]
symbol = Column(ChoiceType(condition_choices, Integer()), default=0)
but  when i use sqladmin , i got this error "sqladmin.exceptions.NoConverterFound: Could not find field converter for column symbol (<class 'sqlalchemy_utils.types.choice.ChoiceType'>)"
Steps to reproduce the bug
sqladmin.exceptions.NoConverterFound: Could not find field converter for column symbol (<class 'sqlalchemy_utils.types.choice.ChoiceType'>)
my code like this :
condition_choices = [(0, '='), (1, '/='), (2, '>'), (3, 'include'), ]
symbol = Column(ChoiceType(condition_choices, Integer()), default=0)
but  when i use sqladmin , i got this error "sqladmin.exceptions.NoConverterFound: Could not find field converter for column symbol (<class 'sqlalchemy_utils.types.choice.ChoiceType'>)"
Expected behavior
No response
Actual behavior
No response
Debugging material
No response
Environment
windows/python3.8/sqladmin0.10.3
Additional context
No response

Hey, this is not supported yet.
Feel free to implement it here: https://github.com/aminalaee/sqladmin/blob/main/sqladmin/forms.py#L468
Otherwise I will get it when I have the capacity.

Thank you for your reply!


Change license element to support CURIEs, e.g., for SPDX

The license element of the schema is currently a URI. It would be nice to be able to specify licenses based on SPDX identifiers as well, since this has the benefit of being a controlled vocabulary, and pushing people towards using well-defined licenses

In principle no objection to that, but it should be noted that, with the current implementation in SSSOM-Py, the “as well” bit is not possible: either the slot expects a URI, or it accepts a CURIE, but it cannot accept both: SSSOM-Py enforces any slot typed as a EntityReference MUST be in CURIE form.
So if we change the type of license to be an EntityReference, SSSOM-Py will no longer accept the use of plain IRI, and will barf on a mapping set with
#license: https://creativecommons.org/licenses/by/4.0

(which is currently perfectly valid). This will have to be replaced by a pseudo-CURIE, as in
#curie_map:
#  CCORG: https://creativecommons.org/licenses/
#license: CCORG:by/4.0

I’m very reluctant to break existing mapping sets just for that, so I will oppose any such change until/unless SSSOM-Py is made to silently accept the use of IRIs for EntityReference-typed slots.

Has anyone ever tried to validate
#curie_map:
#  CC.ORG: "CC.ORG:"
#license: CC.ORG:by/4.0

Just out of curiosity for a hacky workaround for some cases. In general if we type something "uriorcurie" its is my understanding it should literally be possible to either or, even if tools don't support it yet.
All that said,
is this really that bad?
#curie_map:
#  SPDX: https://spdx.org/licenses/
#license: SPDX:AdaCore-doc

TBH SPDX may not be as strong a case for allowing curies explicitly, even if the RDF transformation of the above adds https://spdx.org/licenses/AdaCore-doc as the license..

Has anyone ever tried to validate
#curie_map:
#  CC.ORG: "CC.ORG:"
#license: CC.ORG:by/4.0

Err, yes, this works, but why would ever do that?

If you really want to store the license as a CURIE, you can do so the “normal” way, without having to make this weird “prefix” declaration:

#curie_map:
CCORG: https://creativecommons.org/licenses
#license: CCORG/by/4.0

This already works perfectly fine, both with SSSOM-Py and with SSSOM-Java. It’s just that, _officially_, this is not a CURIE, this is string that happens to look like a CURIE (which means, for example, that SSSOM-Java will _not_ expand it as it normally does for all other EntityReference-typed slots). The requested change here is to make this slot accept CURIEfied values officially, rather than as something that is silently accepted by implementations.

> In general if we type something "uriorcurie" its is my understanding it should literally be possible to either or

This is what SSSOM-Java does. This is also what SSSOM-Py _used_ to do, but now it only accepts CURIEs. Any attempt to validate a set containing a IRI where an EntityReference is expected results in:

WARNING:sssom.util:Slot 'license' has an incorrect value: https://creativecommons.org/licenses/by/4.0/

(here, after I changed the type of `license` from URI to EntityReference, as requested).

My understanding is that this change, the fact that SSSOM-Py enforces that all values of EntityReference-typed slots MUST be in CURIE form, was a deliberate decision. Was that not the case?

My understanding is that this change, the fact that SSSOM-Py enforces that all values of EntityReference-typed slots MUST be in CURIE form, was a deliberate decision (in fact this is because of that change that, when re-writing the specification, I baked in the requirement that all identifiers in a SSSOM/TSV file had to be in CURIE form only). Was that not the case?

I believe you are right!
And yes, hence my comment about SPDX. Not sure this case merrits drilling into the data model. @cthoyt whats your opinion, this is not good enough?
curie_map:
  SPDX: https://spdx.org/licenses/
license: SPDX:AdaCore-doc

Not sure this case merrits drilling into the data model.

The problem is not so much changing the data model per se (as I have said, I would have no objection to making that slot a EntityReference), it’s more that it is a breaking change, because existing sets that are currently using a plain IRI in their license field would suddenly fail to validate with SSSOM-Py after this change is introduced.
I am not opposed to changing the model, but now that we are post-1.0 any change must be carefully weighted, especially breaking changes. From what I see, that particular change is clearly not worth breaking existing sets.

Ahhhh oops sorry, I totally messed up here. I thought the problem was something else :D
Basically for this to be a non breaking change, we would literally have to implement a union data type curie or uri so that we can have both CURIE values and URI values in the field.
The real question was if @cthoyt's wish to do
curie_map:
  SPDX: https://spdx.org/licenses/
license: SPDX:AdaCore-doc

is a high enough marginal gain over the current solution
license: https://spdx.org/licenses/AdaCore-doc

to justify changing the tool.. the answer is of course that we should be faithful to the docs, and here the big question is what the linkml:UriOrCurie datatype truly is..
https://github.com/mapping-commons/sssom/blob/1177d54122754a1311c143ad426b0742dda4d6f8/src/sssom_schema/schema/sssom_schema.yaml#L72
Sorry for misleading the discussion I corrected my comment above


OAuth callback with boolean flag

Signed-off-by: Hristo Iliev<EMAIL_ADDRESS>

Coverage decreased (-0.6%) to 84.883% when pulling 669c16f99d2bc3e41682f9730c44d570e68b5939 on SAP:replay_on_token into 707680061e4c44bcfa0dd49ddf8c1baa51e2bbcf on cloudfoundry-incubator:master.


SQL Dev: Doubled blank lines before comments

Hi Philipp,
thanks for your great blog and sharing your code on SQL Developer formatting.
I have an issue with this configuration. All blank lines before comments will be doubled after formatting.
Example:
CREATE OR REPLACE PACKAGE test_formatting AS

   /* Tow line before this comment will result in four lines */
   FUNCTION foo (
      p_bar VARCHAR2
   ) RETURN NUMBER;

END test_formatting;

After format I got this result:
CREATE OR REPLACE PACKAGE test_formatting AS

   /* Tow line before this comment will result in four lines */
   FUNCTION foo (
      p_bar VARCHAR2
   ) RETURN NUMBER;

END test_formatting;

I tried this with SQL Developer 19.4 (64-bit, Java 1.8.0_221) on Windows 10.
Regards,
Markus

Thanks @markushohloch for reporting this issue. Could you please provide a little example? Thank you.

Ok, I can reproduce it.
select * from dual;

-- test comment
select * from dual;

First format result under macOS. I can repeat formatting it. Result stays the same.
select * from dual;

-- test comment
select * from dual;

First format result under Windows:
SELECT *
  FROM dual;

-- test comment
SELECT *
  FROM dual;

Second format result under Windows:
SELECT *
  FROM dual;

-- test comment
SELECT *
  FROM dual;

I guess the problem is the preference Line breaks -> After statements -> Preserve original.
Obviously Preserve original does not work on any platform. I tried to change it to Single break. This seams to work.
However, the behavior is still strange (this time on macOS where the number of lines is reduced by every formatter call until it's just one empty line. I consider this a bug of the formatter Java class and not of the Arbori program. So we have to inform the SQL Developer team to fix that.

I checked with default settings.  For  Line breaks -> After statements -> Double break. This works differently under Windows and macOS as well.
Adding "spaces" an empty lines changes the behavior as well. Really strange.
Using Single break or Double break seems to be the only feasible workaround for the time being.

Ok, thank you very much for your quick response. I can ask the SQL Developer Team if they can take a look at it.

Yes, please. Could you also post the link here? Thanks a lot.

You're welcome. https://twitter.com/MarkusHohloch/status/1250110284032806919

https://community.oracle.com/message/15597056#15597056


Allow users to unsubscribe from emails with one-click from the email itself

Without requiring login.

Perhaps could work with integration of Action Mailbox in Rails 6.


Launching chromium often hangs on ubuntu 20

Continuation from #2
I did some testing on our ubuntu 20 box and discovered that our playwright fork is able to consistently record with both FF and chromium but puppeteer consistently crashes when recording.
Both of the following run correctly (climatescape.js is a copy of our playwright-tests example)
PLAYWRIGHT_CHROMIUM=1 PLAYWRIGHT_HEADLESS=1 node ./climatescape.js
PLAYWRIGHT_HEADLESS=1 node ./climatescape.js

When I update that script to use puppeteer instead, it hangs when trying to open a new page.

Can you tell why it's crashing?  Is there a way to get the output that the browser writes to stderr (setting RECORD_REPLAY_VERBOSE should help if we can get that output)?

Doesn't look like it's making it far enough to log anything with that. Adding DEBUG="puppeteer:*" provides the following:
ubuntu@ip-172-16-162-168:~/ryan/test-pw$  PLAYWRIGHT_HEADLESS=1 RECORD_REPLAY_VERBOSE=1 DEBUG="puppeteer:*" node ./climatescape.js
2022-02-17T00:58:56.854Z > Explore climatescape.org
  puppeteer:launcher Calling /home/ubuntu/.replay/puppeteer/chrome-linux/chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=Translate --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --enable-blink-features=IdleDetection --headless --hide-scrollbars --mute-audio about:blank --remote-debugging-port=0 --user-data-dir=/tmp/puppeteer_dev_chrome_profile-xBwPIU +0ms
  puppeteer:protocol:SEND ► {"method":"Target.setDiscoverTargets","params":{"discover":true},"id":1} +0ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetCreated","params":{"targetInfo":{"targetId":"15011941375F4ED655F8D2B881F2A1B9","type":"page","title":"","url":"about:blank","attached":false,"canAccessOpener":false,"browserContextId":"A5E8A1A654E31DFA82B58A59F43B09D2"}}} +0ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetCreated","params":{"targetInfo":{"targetId":"8720d414-98e6-4585-bdf8-e4730e959316","type":"browser","title":"","url":"","attached":true,"canAccessOpener":false}}} +0ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetCreated","params":{"targetInfo":{"targetId":"e8eba59f-4f17-4855-9ce4-499db170505f","type":"browser","title":"","url":"","attached":false,"canAccessOpener":false}}} +1ms
  puppeteer:protocol:RECV ◀ {"id":1,"result":{}} +0ms
  puppeteer:protocol:SEND ► {"method":"Target.createTarget","params":{"url":"about:blank"},"id":2} +4ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetCreated","params":{"targetInfo":{"targetId":"79B393E814A86A9B8137D11A71EC6F5A","type":"page","title":"","url":"","attached":false,"canAccessOpener":false,"browserContextId":"A5E8A1A654E31DFA82B58A59F43B09D2"}}} +10ms
  puppeteer:protocol:RECV ◀ {"id":2,"result":{"targetId":"79B393E814A86A9B8137D11A71EC6F5A"}} +9ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetInfoChanged","params":{"targetInfo":{"targetId":"79B393E814A86A9B8137D11A71EC6F5A","type":"page","title":"about:blank","url":"about:blank","attached":false,"canAccessOpener":false,"browserContextId":"A5E8A1A654E31DFA82B58A59F43B09D2"}}} +677ms
  puppeteer:protocol:SEND ► {"method":"Target.attachToTarget","params":{"targetId":"79B393E814A86A9B8137D11A71EC6F5A","flatten":true},"id":3} +696ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetInfoChanged","params":{"targetInfo":{"targetId":"15011941375F4ED655F8D2B881F2A1B9","type":"page","title":"about:blank","url":"about:blank","attached":false,"canAccessOpener":false,"browserContextId":"A5E8A1A654E31DFA82B58A59F43B09D2"}}} +1ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetInfoChanged","params":{"targetInfo":{"targetId":"79B393E814A86A9B8137D11A71EC6F5A","type":"page","title":"about:blank","url":"about:blank","attached":true,"canAccessOpener":false,"browserContextId":"A5E8A1A654E31DFA82B58A59F43B09D2"}}} +11ms
  puppeteer:protocol:RECV ◀ {"method":"Target.attachedToTarget","params":{"sessionId":"F510F8610BCEE5376E97C7C272D4896C","targetInfo":{"targetId":"79B393E814A86A9B8137D11A71EC6F5A","type":"page","title":"about:blank","url":"about:blank","attached":true,"canAccessOpener":false,"browserContextId":"A5E8A1A654E31DFA82B58A59F43B09D2"},"waitingForDebugger":false}} +0ms
  puppeteer:protocol:RECV ◀ {"id":3,"result":{"sessionId":"F510F8610BCEE5376E97C7C272D4896C"}} +0ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Page.enable","id":4} +14ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Page.getFrameTree","id":5} +1ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Target.setAutoAttach","params":{"autoAttach":true,"waitForDebuggerOnStart":false,"flatten":true},"id":6} +1ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Performance.enable","id":7} +1ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Log.enable","id":8} +3ms
  puppeteer:protocol:RECV ◀ {"id":4,"result":{},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +156ms
  puppeteer:protocol:RECV ◀ {"id":5,"result":{"frameTree":{"frame":{"id":"79B393E814A86A9B8137D11A71EC6F5A","loaderId":"720F859130F2E496A92A19DCC9CBC4BA","url":"about:blank","domainAndRegistry":"","securityOrigin":"://","mimeType":"text/html","adFrameType":"none","secureContextType":"InsecureScheme","crossOriginIsolatedContextType":"NotIsolated","gatedAPIFeatures":["SharedArrayBuffers","SharedArrayBuffersTransferAllowed"]}}},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +0ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Page.setLifecycleEventsEnabled","params":{"enabled":true},"id":9} +149ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Runtime.enable","id":10} +1ms
  puppeteer:protocol:SEND ► {"sessionId":"F510F8610BCEE5376E97C7C272D4896C","method":"Network.enable","id":11} +0ms
  puppeteer:protocol:RECV ◀ {"id":6,"result":{},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +8ms
  puppeteer:protocol:RECV ◀ {"id":7,"result":{},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +8ms
  puppeteer:protocol:RECV ◀ {"id":8,"result":{},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +0ms
  puppeteer:protocol:RECV ◀ {"method":"Page.lifecycleEvent","params":{"frameId":"79B393E814A86A9B8137D11A71EC6F5A","loaderId":"720F859130F2E496A92A19DCC9CBC4BA","name":"commit","timestamp":8071954.886432},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +0ms
  puppeteer:protocol:RECV ◀ {"method":"Page.lifecycleEvent","params":{"frameId":"79B393E814A86A9B8137D11A71EC6F5A","loaderId":"720F859130F2E496A92A19DCC9CBC4BA","name":"DOMContentLoaded","timestamp":8071954.886862},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +1ms
  puppeteer:protocol:RECV ◀ {"method":"Page.lifecycleEvent","params":{"frameId":"79B393E814A86A9B8137D11A71EC6F5A","loaderId":"720F859130F2E496A92A19DCC9CBC4BA","name":"load","timestamp":8071954.8876},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +0ms
  puppeteer:protocol:RECV ◀ {"method":"Page.lifecycleEvent","params":{"frameId":"79B393E814A86A9B8137D11A71EC6F5A","loaderId":"720F859130F2E496A92A19DCC9CBC4BA","name":"networkAlmostIdle","timestamp":8071954.888491},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +7ms
  puppeteer:protocol:RECV ◀ {"method":"Page.lifecycleEvent","params":{"frameId":"79B393E814A86A9B8137D11A71EC6F5A","loaderId":"720F859130F2E496A92A19DCC9CBC4BA","name":"networkIdle","timestamp":8071954.888491},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +0ms
  puppeteer:protocol:RECV ◀ {"id":9,"result":{},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +0ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetCrashed","params":{"targetId":"15011941375F4ED655F8D2B881F2A1B9","status":"crashed","errorCode":134}} +242ms
  puppeteer:protocol:RECV ◀ {"method":"Inspector.targetCrashed","params":{},"sessionId":"F510F8610BCEE5376E97C7C272D4896C"} +40ms
  puppeteer:protocol:RECV ◀ {"method":"Target.targetCrashed","params":{"targetId":"79B393E814A86A9B8137D11A71EC6F5A","status":"crashed","errorCode":134}} +0ms

I compared the flags passed between playwright and puppeteer and this flag to disable these features seems to be the ticket:
--disable-features=ImprovedCookieControls,LazyFrameLoading,GlobalMediaControls,DestroyProfileOnBrowserClose,MediaRouter,AcceptCHFrame,AutoExpandDetailsElement

Seems to be running better after the last round of chromium patches.


LAB_04-Implement_Virtual_Networking.md

English:
Name
Current Translation:
Name
Suggested Translation:
名稱
Description:
It should be translated according to the context. Global check.

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Run the bugfix tool and waiting for result. ICMS QUERY

The issue has been fixed, so I close the PR.


Unbound keybindings should not show up in watermark

Also on Windows. @mousetraps also noted the alignment of "unbound" is a little off.

Added keybinding for Open Folder (only used on Windows and Linux) and fixed the layout for 'unbound' for November.

My point was rather: what good do we do to a new user by telling him, the very first time he opens Code, that some command doesn't have an associated key binding?

I agree and am tracking that as #16837.

Missed the link. 👍