versions: Expose channel-group

When listing versions or creating a cluster, we can now specify the
channel group to use, with a default of 'stable'. Interactive mode now
reads the channel group flag and displays the correct list when creating
the cluster.
https://asciinema.org/a/b4vW7EtlDp0vRBbljSbnnGwBa

@jeremyeder - we gate the channel groups directly in CS: https://gitlab.cee.redhat.com/service/uhc-clusters-service/-/blob/master/cmd/clusters-service/service/versions.go#L41-52

/retest

/test lint

/lgtm :+1:


Apply default value "application/json" to contentype and accept

Fix #2702, hard cord default value as "application/json". See details at: https://github.com/Azure/autorest.csharp/issues/2702#issuecomment-1249109692

@pshao25, could you solve the conflict from this PR? thanks


Explain how to write callbacks for custom types

Happy to change stuff if something is off.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


AllocateTensors fails in hello world example

@tensorflow/micro
System information

Host OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
TensorFlow installed from (source or binary): Source
Tensorflow version (commit SHA if source): 32165792a
Target platform (e.g. Arm Mbed OS, Arduino Nano 33 etc.): Host

Describe the problem
I try to run the hello world example as described on page 92 of the TinyML book but it fails.
Please provide the exact sequence of commands/steps when you ran into the problem
Building the binary
make -f tensorflow/lite/micro/tools/make/Makefile hello_world
Running the binary
tensorflow/lite/micro/tools/make/gen/linux_x86_64/bin/hello_world
I get back
Failed to allocate memory. Requested: 400, available 264, missing: 136
Failed to allocate memory for node_and_registrations.
AllocateTensors() failed
[1]    9967 segmentation fault (core dumped)  tensorflow/lite/micro/tools/make/gen/linux_x86_64/bin/hello_world

Hi Colin,
I had the same issue. I'm using Ubuntu 18.04 on aarch64.
I'm not sure if this solution fixes the "real" root of the problem but it helped.
In the file tensorflow/lite/micro/examples/hello_world/main_functions.cc:
You have to increase your reserved memory block.
original line 38:
constexpr int kTensorArenaSize = 2 * 1024;
new line 38:
constexpr int kTensorArenaSize = 3 * 1024;
I'm really not sure why this is a problem on a custom pc. I built this example with the command
make -f tensorflow/lite/micro/tools/make/Makefile TARGET=mbed TAGS="CMSIS-nn nucleo_f207zg" generate_hello_world_mbed_project
for my STM development board and it worked with the 2048 bytes.
As mentioned in the book defining a tensor arena could be trail and error.
Cheers
Philipp

@muskedunder It looks like you are using an older Version of Tensorflow . Many bugs have been fixed in the latest version. Could you please execute your code using Latest Version 2.4.1 or 2.5 and let us know if the issue still persists? Thanks!


feat: add possibility to reply with sendMessage

Hello,
This PR introduces an enhancement to the existing sendMessage function, allowing to optionally reply to a specific message.
This feature is implemented by extending the SendMessageInput interface to accommodate reply metadata, and by adding conditional logic to the sendMessage function to handle the construction of the request body for a reply message.
Exemple of use :
client.on(Events.Chatroom.Message, (messageInstance) => {
  const message = messageInstance.data
  if (message.content === "ping") {
    client.api.chat.sendMessage(message.chatroom_id, "Pong!", {
      originalMessageId: message.id,
      originalMessageContent: message.content,
      originalSenderId: message.sender.id,
      originalSenderUsername: message.sender.username
    })
  }
})

This update does not affect the existing functionality of the sendMessage function for sending standard messages. It is a backward-compatible enhancement that introduces an additional capability for users wishing to reply directly to messages.

LGTM, I've made a few stylistic changes to the function parameters if you wanted to check before I merge it in.

Moved parameter type to it's own interface and also simplified the object property names.


graph data should be saved in mongo not redis

HKube micro-service
To which micro-service the bug related to, Dashboard ,Monitor-Server etc.
Describe the bug
graph data should be saved in mongo not redis
if restarting the cluster the graph data is lost

fixed by
https://github.com/kube-HPC/DAG.hkube/pull/19
https://github.com/kube-HPC/monitor-server/pull/37
https://github.com/kube-HPC/hkube/pull/1198
https://github.com/kube-HPC/db.hkube/pull/10
Notes:

api-server should migrate graphs from redis to mongo
new graphs are written to redis
monitor-server reads graphs as part of the job

Affected functionality:

graph view in UI
get graph api (raw, parsed)
tensor boards
pipeline driver recovery

tested on
systemVersion: "v2.0.121",
fullSystemVersion: "v2.0.121-1617274600478",
versions: [


Permission denied: 'ghostdriver.log' in alarmdotcom

Home Assistant release (hass --version):
0.25.2
Python release (python3 --version):
Python 3.4.2
Component/platform:
platform alarmdotcom
Description of problem:
alarmdotcom tries to create ghostdriver.log somewhere, don't know where, but gets permission denied.
Expected:
Should be able to write ghostdriver.log, or don't create it in the first place.
Problem-relevant configuration.yaml entries and steps to reproduce:
alarm_control_panel:
  platform: alarmdotcom
  name: "LiveWatch Alarm"
  code: 1234
  username: myusername
  password: mypassword

Enter the above config
Start/restart hass
Look in the dev-info to see the error

Traceback (if applicable):
16-08-09 17:37:11 homeassistant.components.alarm_control_panel: Error while setting up platform alarmdotcom
Traceback (most recent call last):
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 98, in _setup_platform
    discovery_info)
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/alarmdotcom.py", line 36, in setup_platform
    password)])
  File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/alarmdotcom.py", line 47, in __init__
    self._alarm = Alarmdotcom(username, password, timeout=10)
  File "/home/hass/.homeassistant/deps/pyalarmdotcom/pyalarmdotcom.py", line 82, in __init__
    if not self._login():
  File "/home/hass/.homeassistant/deps/pyalarmdotcom/pyalarmdotcom.py", line 95, in _login
    self._driver = webdriver.PhantomJS()
  File "/home/hass/.homeassistant/deps/selenium/webdriver/phantomjs/webdriver.py", line 51, in __init__
    log_path=service_log_path)
  File "/home/hass/.homeassistant/deps/selenium/webdriver/phantomjs/service.py", line 50, in __init__
    service.Service.__init__(self, executable_path, port=port, log_file=open(log_path, 'w'))
PermissionError: [Errno 13] Permission denied: 'ghostdriver.log'

Additional info:
home-assistant installed on a Pi 2 using this script: https://home-assistant.io/getting-started/installation-raspberry-pi-all-in-one/

I wanted to mention that I have the same problem.  I initially used the all in one installer on a Pi 3.  I reinstalled it with the normal installation procedure but I still have the same problem.  Editing the path of ghostdriver.log in the referenced files doesn't work since the files are reinstalled on every restart.  Using chmod to change the permissions for the directory of the file doesn't help either since it is reinstalled.

I am also having this issue as well.  Tried everything @rebelnme tried as well with the same results
RP1
Python 3.4.2
HA 0.31.1

I finally got mine working and it works perfectly.
I followed the recommendation from here:
https://community.home-assistant.io/t/alarm-com-issue/262/19

@rebelnme I'm still getting the [Errno 13] Permission denied: 'ghostdriver.log' after installing phantomjs using the link in the comment you linked.
I'm on v.33 using hassbian on a RP2b.

This has worked for me now for over a month after following the directions I shown at the link above.  It provides status and can arm/disarm Alarm.com system.  The only difference is that in trying to resolve this issue; before I tried the above link, I had converted my raspberry pi to a standard install instead of the all-in-one installer.

Have you installed openzwave after getting it to work? I had it working after installing without the AiO, but once I installed openzwave it stopped working again. I believe it installs some dependencies that update or break pyalarmdotcom's dependencies.

Actually when I changed to the standard install vs the all in one, I switched to using a veraplus for all my device connections.  It works great for all z-wave devices including locks, thermostats, and garage door openers.  Maybe as you say, that is why my ghostdriver.log still works.  You could try reinstalling the phantomjs and see if it makes the openzwave stop working.  Sorry I can't help anymore than that.

See my comment here on a possible fix, I don't know how to implement or test it: https://github.com/Xorso/pyalarmdotcom/issues/4

Figured out that it's trying to put the log file in the root directory. You can kludge a fix as follows:
sudo touch /ghostdriver.log && sudo chmod 777 /ghostdriver.log


[import_goodreads] No documentation

I have no idea how to use that plugin.

> nikola help
...
nikola import_goodreads     import a Goodreads RSS
...

> nikola import_goodreads
ERROR: Nikola: Unknown command import_goodreads

I get:
> nikola import_goodreads
Purpose: import a Goodreads RSS
Usage:   nikola import_goodreads [options] rss_url

Options:
  -o ARG, --output-folder=ARG  Location to write imported content.

It looks like there's a problem with your nikola and/or plugin installation. Which python version and nikola version are you using?

Python 3.6.0 and Nikola v7.8.3.  the virtualenv was setup yesterday, the site files are older.

Hmm, here it works fine (Python 3.6.0, Nikola github master which is essentially v7.8.3, though without virtualenv). I created an empty site with nikola init -qd, entered the folder, imported the plugin and got the help text.
Can you try to reproduce this with an empty site? Like:
nikola init -qd test
cd test
nikola plugin -i import_goodreads
nikola import_goodreads

That works. But I found the problem: it doesn't work if the current directory is plugins. The site's root works.


Proxy Support for Outbound Selenium Traffic (control messages) in Nightwatch

For nightwatch consumers of magellan-saucelabs-executor, this PR adds support for SAUCE_OUTBOUND_PROXY, which is the same variable used by<EMAIL_ADDRESS>Also:

Updates to<EMAIL_ADDRESS>Fixes regressed tests
Adds tests for proxy configuration
Updates README

Note: Support for non-nightwatch frameworks is not covered by this PR because other frameworks only extract desiredCapabilities at this time.
/cc @archlichking

Codecov Report

Merging #12 into master will increase coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master      #12     +/-   ##
=========================================
+ Coverage   87.55%   87.65%   +0.1%
=========================================
  Files           9        9
  Lines         474      478      +4
  Branches       87       89      +2
=========================================
+ Hits          415      419      +4
  Misses         59       59

Impacted Files
Coverage Δ

lib/settings.js
100% <0%> (ø)
:arrow_up:

lib/configuration.js
100% <0%> (ø)
:arrow_up:

lib/profile.js
89.13% <0%> (+0.24%)
:arrow_up:

Continue to review full report at Codecov.

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

👍


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=448973604
https://github.com/Azure/azure-cli-extensions/commit/2edad2049dd11841b606f1ace7146015cffa1310

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

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


Feature/tcvp 1295 file storage leak fix

Description
This PR includes the following proposed change(s):

TCVP-1295 - re-submit of file storage leak fix
Minor fix to the email send, where the ticket id was being populated to the wrong attribute.
Unit tests for the RedisCachService

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
New Unit tests and manual verification
Does the change impact or break the Docker build?

[ ] Yes
[x] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes

This PR has a long history.  Just thinking that you might benefit from doing an interactive rebase of your PR onto main instead of doing a merge from main.  This may help with inadvertently losing code with any merge conflicts.


skip ed should be excluded from benchmarks

          skip ed should be excluded, cc @dmoka

Originally posted by @mrq1911 in https://github.com/galacticcouncil/hydration-node/pull/889#discussion_r1785262523

I think it is fine, as in every on_transfer we start with checking if the ED should be skipped.
https://github.com/galacticcouncil/hydration-node/blob/5d4121cbe3fd852b8e8341d2358c19cf118946bc/runtime/hydradx/src/assets.rs#L256-L260


Added a limit condition that interrupt insertion

As mentioned in https://github.com/nathanvda/cocoon/issues/194, I made a contribution that consider a limit condition in parameter as:
link_to_add_association 'Add Association', f, :associations, limit: 3

and interrupt the insertion the nested associations in that node and also trigger the event cocoon:limit-reached.

Hi, can I use this to limit insertions? how?

+1

+1

not merged?

+1

+1 Hope it make the add button disappear with a 'limit reached' message on it.

+1

I try to do this but nothing.

+1

This is old, but I am cleaning up. Sorry I never replied to this before.
Not merged because it is easy to implement using callbacks, and there are imho different approaches based on your UX. In my opinion implemented like in this PR encourages bad UX (show a link and only after click we start counting where imho we know beforehand clicking the link would not be allowed)
Example implementation: https://github.com/nathanvda/cocoon/wiki/How-to-limit-the-number-of-nested-fields


Dialog 'confirm' callback is called multiple times if dialog was previously canceled

I'm opening a custom dialog multiple times like this
  let dialog = phonon.dialog(dialogEl)
  dialog.on('confirm', confirmFn)
  dialog.on('cancel', cancelFn)

  dialog.open()

When the dialog is opened, canceled, then opened again and confirmed, the 'confirm' callback is called twice.
In fact, the 'confirm' callback is called as many times as the dialog was previously canceled + 1 :smile:

In addition to the fixes in the pull request, I also had to reorder my code like this:
  let dialog = phonon.dialog(dialogEl)
  dialog.open()
  dialog.on('confirm', confirmFn)
  dialog.on('cancel', cancelFn)

ie. call open() first, then install the callbacks. Otherwise backdrop clicks would not call the cancel callback.

Hi @michaelkoetter,
Thank you for reporting.
I can't reproduce this issue.. it is working on Chrome.
This is what I did in ES5:
function setDialog() {
	var dialog = phonon.dialog('#simple-dialog')
    dialog.on('confirm', function () {
		console.log('CONFIRM')
	})
    dialog.on('cancel', function () {
		console.log('CANCEL')
	})

    dialog.open()
}

setDialog()

// click on a button before the timeout
setTimeout(function () {
	setDialog()
}, 3000)

When I click on "confirm", then reopen the dialog and click on "confirm" again, the callback is called once.

Yes, clicking on "Confirm" removes the callback. Try clicking on cancel a couple of times, and then "Confirm".
It is also evident from the code, the "fireEvent" function contains this
this.off('tap', fireEvent);

which only removes the event handler from the button that was clicked. So if you clicked "cancel", the 'cancel' event handler is removed - the 'confirm' handler remains installed on the button.
Then, if the dialog is created again, a second 'confirm' handler is added, etc.
When 'confirm' is finally clicked, all those event handlers are called.

Hi @Qathom, don't want to nag you but it's been a while - did you have a chance to test my scenario, as described above? :smiley:

Hi @michaelkoetter,
I just understood the problem! I clicked on "confirm", then "cancel". Yes, the "cancel" handler is called twice.
I added the off function in order to remove listeners when the dialog is closed (reset the dialog).
Thank you for your help :)
I will add this fix in the next release asap!


Slow require() of v1

Using require("uuid/v1") under Electron, I've noticed anywhere from 2x to 4x increase in window load time. I've tracked this to the unwrapped call to rng() which in turn synchronously calls crypto.randomBytes(). From the NodeJS docs:
The crypto.randomBytes() method will block until there is sufficient entropy. This should normally never take longer than a few milliseconds. The only time when generating the random bytes may conceivably block for a longer period of time is right after boot, when the whole system is still low on entropy.
This is unfortunately the behvaviour I'm seeing. The loading of the entire window is being held up by the call to crypto.randomBytes. Changing my use of uuid/v1 to uuid/v4 fixes the problem.
If there is sufficient interest in modifying uuid/v1 to use the asynchronous version of crypto.randomBytes or otherwise wrap the synchronous version so it is not called on require time I would be happy to open a PR.

2x to 4x increase in window load time

What kind of time are we talking about here?  msecs?  secs?

Changing my use of uuid/v1 to uuid/v4 fixes the problem

v4 uses rng() as well

The only time when generating the random bytes may conceivably block for a longer period of time is right after boot, when the whole system is still low on entropy.

That's for node.js though, not the browser, right?  How does that affect window load time in your clients?  I would expect the entropy of a node.js server to have been established by the time it's ready to start handling requests.

interest in modifying uuid/v1

I think you mean rng.js, as that's where this issue should be addressed.
I'm open to fixing this, but adding/converting to an async api is a non-trivial change.  I'd like to make sure it's actually solving a real problem.  That your problem goes away when you switch to v4() has me suspicious... 😕
(I could be way off base on all of this, btw... I won't pretend to know with certainty what crypto.randomBytes() is doing under the hood.)

Thanks for the quick response @broofa. In terms of slowdown, we're talking the difference between 20ms and 300ms.
Electron is a framework for building desktop apps with web technologies. Each window is a separate process, including a separate instance of NodeJS. Therefore each window's requires are evaluated each time a window is loaded. The difference between v1 and v4 in my case is the unwrapped usage of crypto.randomBytes.
From the v1 source;
// Unique ID creation requires a high quality random # generator.  We feature
// detect to determine the best RNG source, normalizing to a function that
// returns 128-bits of randomness, since that's what's usually required
var rng = require('./lib/rng');
var bytesToUuid = require('./lib/bytesToUuid');

// **`v1()` - Generate time-based UUID**
//
// Inspired by https://github.com/LiosK/UUID.js
// and http://docs.python.org/library/uuid.html

// random #'s we need to init node and clockseq
var _seedBytes = rng();

Each time uuid/v1 is required (in my case on startup of each window, when entropy is low), cyrpto.randomBytes is invoked.
Compared to v4
var rng = require('./lib/rng');
var bytesToUuid = require('./lib/bytesToUuid');

function v4(options, buf, offset) {
  var i = buf && offset || 0;

  if (typeof(options) == 'string') {
    buf = options == 'binary' ? new Array(16) : null;
    options = null;
  }
  options = options || {};

  var rnds = options.random || (options.rng || rng)();

  // Per 4.4, set bits for version and `clock_seq_hi_and_reserved`
  rnds[6] = (rnds[6] & 0x0f) | 0x40;
  rnds[8] = (rnds[8] & 0x3f) | 0x80;

  // Copy bytes to buffer, if provided
  if (buf) {
    for (var ii = 0; ii < 16; ++ii) {
      buf[i + ii] = rnds[ii];
    }
  }

  return buf || bytesToUuid(rnds);
}

module.exports = v4;

Where the only thing happening at require time is the the further requiring of .lib/rng as well as ./lib/bytesToUuid and the creation and exporting of the v4 function. In v4, crypto.randomBytes is not invoked until the v4 method is.
This is where the performance difference is coming from. The difference in time in the process' lifecycle when crypto.randomBytes is being called. At startup (when entropy is low) in v1, versus at some point in the future, during runtime when entropy is (presumably) higher in v4.

We're seeing this behavior as well albeit with a much higher penalty (around 1 second for the initial call)

We're using webpack and typescript and import the v4 version using an import statement, this causes the v1 version to get loaded as well.

It seems like the initial call to crypto.randomBytes can be extraordinarily expensive when running under electron. I suspect this is something we can improve in electron and I'll open an issue there to discuss it.
For now we've worked around the issue by creating our own wrapper around uuid that sources entropy using window.crypto instead of the Node.JS crypto module and the initial load time is now trivial. I threw up my workaround in a gist if you're interested @chgibb.

Update: there's already an issue tracking this in electron, see https://github.com/electron/electron/issues/2073

Thanks @niik !!


Add additional duplicateFileMode options

Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[x] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
See https://github.com/liquibase/liquibase/issues/5856
Adds additional additional modes for duplicateFileMode including:

INFO - Logs when duplicate changelog files are found at the INFO level
DEBUG - Logs when duplicate changelog files are found at the FINE level
SILENT - Does not log when duplicate changelog files are detected

Things to be aware of

I opted to use the term DEBUG rather than FINE as I think it clearer in the context of the duplicateFileMode parameter that it refers to a log level.
Similarly I opted for the term SILENT instead of IGNORE (as suggested in the original issue) because it is less ambiguous.
The method handleDuplicateFileModeLogging was added to the ResourceAccessor interface with a default implementation, this isolates the logging modes from ERROR and SILENT modes. This allows users to implement some custom logging without impacting the get functionality of ResourceAccessor
Things to worry about
Nothing I am aware of, the default value for duplicateFileMode remains as ERROR

Additional Context
The context can be found in the original issue

Thank so much for submitting this PR! We will work on adding it to our next release.


Interested in collaboration?

Hey there. I've put quite some time into a tree-sitter parser for Nim as well.
https://github.com/aMOPel/tree-sitter-nim
Would you be interested in collaborating?

Damn, you made dial.nvim. Great plugin, using it with delight :)
I would be open to introducing you to my codebase in a call if you want. Or you wanna work into it yourself?

I have created a bunch of issues on the repo now. If you want to contribute you can state so in the respective issue and make a PR. Or if you want I can also make you a collaborator.

Thank you so much!
I am going to check the code and the Issue first.

Thank you too :)
I've added a section to the readme with stuff from my vimrc to ease development, especially the writing of tests. Maybe it's useful to you.
The offer for a call still stands if you have any questions.


Implement directory level for command

Added a currentDirectory with integral value in VersionedAddressbook. For currentDirectory 0 represents root, and non-zero integer represents the issue with that index. It can be accessed and modified through ModelManager. Besides, the selectCommand now change the current directory to the selected issue when it executes.


feat: showing the selected generator

Fixes Issue
My PR closes #378
👨💻 Changes proposed(What did you do ?)
✔ Check List (Check all the applicable boxes)

[] My code follows the code style of this project.
[] This PR does not contain plagiarized content.
[] The title and description of the PR is clear and explains the approach.

Note to reviewers

📷 Screenshots

Is this what you mean? About overlapping

@Dun-sin yes...

It may not be possible to resolve this issue with a single line of code. This issue may be more complex than you initially thought.

i wanna give it a try, trying

Hey @Dun-sin sorry for not being active here, i think i can't make it happen, looking forward for new issues and PRs. Thank you

Hey @Dun-sin sorry for not being active here, i think i can't make it happen, looking forward for new issues and PRs. Thank you

Alright, thanks to the trying🤞🏽


Adding "Endcard" option

Hi,
for an upcoming project I needed a way to add an endcard to certain videos.
Since it's basically "just the pause screen, but at the end of the video", I already did some tinkering around in the code and implemented it like this:
        player.displayOptions = {
[...]
                htmlOnCompleteBlock: {
                    html:                     null,
                    height:                   null,
                    width:                    null
                },
[...]
        }

If approved by the staff, I would like to make a pull request, however there is still one issue I would like to have resolved before the changes hit the production code:
If you are on the endscreen and seek right back into the video, the screen won't switch back to a regular pause screen.
So somehow there would need to be a check, whether after a seek event the player is still paused and which of the two overlays is currently displayed. If somebody could point me to the right position in the code, that would be awesome.
For reference, the changed files:

https://github.com/sevildevil1990/fluid-player/blob/master/fluidplayer.js
https://github.com/sevildevil1990/fluid-player/blob/master/fluidplayer.css

On a sidenote: There is also a weird quirk, that interferes with the endcard, that is in the base player right now:
If a Post-Roll is played, the video-player skips back to the first position in the video, thus never reaching the point of triggering the end screen.

Just what I'm looking to do :)  Great suggestion. Now if we could get some traction here...

@sevildevil1990 -  Can you please confirm if the issue still persist ? Or can I go ahead and close the ticket

@sevildevil1990 - Can you please confirm if the issue still persist ?

Since there is no confirmation from the reporter regarding the issue, we are closing the ticket


Potential new criterion: Developer Certificate of Origin (DCO) or better

One user risk is that an OSS project may not have the right to redistribute parts of its software, e.g., because one or more contributors isn't authorized to contribute that code.  A number of projects have a variety of ways to reduce this risk.
One of the more common methods is a Developer Certificate of Origin (DCO).  The Linux kernel developers created and use this, and support for it is built into git. We also use DCOs in the BadgeApp.
Using a DCO is plausibly a best practice, especially if it's generalized to something like:

The project SHOULD have a legal mechanism where all developers of non-trivial amounts of project software assert that they are legally authorized to make these contributions.  This may be implemented using a Developer Certificate of Origin (DCO), a Contributor License Agreement (CLA), a Copyright Assignment Agreement (CAA), or other legal mechanism.  Note that git directly supports a "signed-off" feature using "commit -s", but to be effective the project documentation has to explain what "signed-off" means.

Comments?  I'm thinking about adding this for the 2017 version of the criteria.

BTW, back in January I submitted a change to git's documentation so that the meaning of "signed-off-by" is much clearer.  It was accepted into git version 2.7.1, so that version and later has clearer documentation.  It's a trivial change, but it gives the signed-off-by tags an even stronger legal footing.  My change is here:
https://github.com/git/git/commit/b2c150d3aa82f6583b9aadfecc5f8fa1c74aca09
My change was based on the interaction here:
https://lwn.net/Articles/669976/
Some discussion of signed-off-by is here:
http://stackoverflow.com/questions/1962094/what-is-the-sign-off-feature-in-git-for

I'll bite, since this has been quiet for 6 months.  I think the preferred mechanism should be DCO, since it's lightweight and difficult to get wrong or lose track of.  If a project insists, a CLA can be used as an alternative, but this does cause problems.  I really think a CAA should not be recommended: they're the most legally complex system to implement, they tend to antagonise your base by taking ownership of their code from them and they have few advantages over DCO or CLA.
Using this, as a guide, I'd propose

The project SHOULD have a legal mechanism where all developers of non-trivial amounts of project software assert that they are legally authorized to make these contributions. This SHOULD be implemented using a Developer Certificate of Origin (DCO) but MAY be implemented as a Contributor License Agreement (CLA),  or other legal mechanism. Note that the DCO is the recommended mechanism because it's easy to implement, tracked in the source code and git directly supports a "signed-off" feature using "commit -s"; however, to be effective the project documentation has to explain what "signed-off" means.

Thanks so much for the feedback!
We're adding this to the draft "passing+1" set of criteria.  We're closing this for now; a new  issue can be opened after we've had a chance to clean it up.


Vue 3.0 release date

I cannot find any current information about the planned date of 3.0 version release. It would be very helpful to have some idea about the current approximate time of the release.
Regards

Sorry, but it's definitely not related to Vue documentation issues.

Which repo os apropriate?
śr., 19 cze 2019, 17:26 użytkownik Natalia Tepluhina <
<EMAIL_ADDRESS>napisał:

Sorry, but it's definitely not related to Vue documentation issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vuejs.org/issues/2204?email_source=notifications&email_token=AH3DZZWXY74YK5LEAZ6UVS3P3JFZPA5CNFSM4HZKFPU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYCHOFQ#issuecomment-503609110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH3DZZWOTFURB2Z63PKMUZ3P3JFZPANCNFSM4HZKFPUQ
.


Intellisense does not show text description.

From @objectref on June 6, 2017 21:47

VSCode Version: Code 1.12.2 (19222cdc84ce72202478ba1cec5cb557b71163de, 2017-05-10T13:13:11.413Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author
Version

csharpextensions
jchannon
1.3.0

csharp
ms-vscode
1.10.0

team
ms-vsts
1.118.2

vscode-icons
robertohuertasm
7.9.0

Steps to Reproduce:

Copied from original issue: Microsoft/vscode#28152

From @objectref on June 6, 2017 22:0
Hi. WriteLine is a method of Console (of .net core), not mine. Or I misunderstood your question?
Anthony
From: Ramya Rao<EMAIL_ADDRESS>Reply-To: Microsoft/vscode<EMAIL_ADDRESS>Date: Wednesday, 7 June 2017 at 00:57
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: objectref<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] Intellisense does not show text description. (#28152)
@objectrefhttps://github.com/objectref Can you share a screen shot of the place where WriteLine is defined? Does it have any comments/docs on it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/28152#issuecomment-306629255, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUHTS39s2XgicZWrK8KysF0yIWOPSsKqks5sBctIgaJpZM4Nx9Up.

@objectref Can you share a screen shot of the place where WriteLine is defined? Does it have any comments/docs on it?

Do a F12 or "Go to Definition" on the "WriteLine" method, that will take you to the file where it is defined.
Once there, see if there are any docs for the method.
Only if the method in question has any accompanying docs, the same appear in the suggestion list.

Also, hover on the WriteLine method, do you see any docs/description showing up?

From @objectref on June 6, 2017 22:18
I did that F12 and indeed there it does not seem any doc/description in the WriteLine method. But I remembered that this thing always showed me help description in intellisense (C#). And surely, I remembered it in JavaScript coding too! And now it does not seem to work even there (JS). See the attached picture.
From: Ramya Rao<EMAIL_ADDRESS>Reply-To: Microsoft/vscode<EMAIL_ADDRESS>Date: Wednesday, 7 June 2017 at 01:12
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: objectref<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] Intellisense does not show text description. (#28152)
Also, hover on the WriteLine method, do you see any docs/description showing up?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/28152#issuecomment-306632391, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUHTSy9_aNOAKhvm8QIyfXd4bjk10Hb8ks5sBc7IgaJpZM4Nx9Up.

if you don't see any docs/description on hover either, then there must be an issue with the C# extension.
Will move this issue over to the extension's repo. They can better investigate if the extension is sending the required info to VS Code

C# for VS Code does pass along documentation to the completion items it creates. However, in this case, it appears that the documentation is not available to it at all.
@objectref: Could you run dotnet --info in the your project folder and let me know what the output is?
@terrajobst, @richlander: Poking around a bit, it appears that the NETStandard.Library packages don't appear to contain XML documentation like, say, the ASP.NET packages do, which means that users don't get documentation on hover or completion in VS Code for core types and members. Is there are plan to start including documentation so that users get a good experience?
cc @Pilchie

dotnet –info command at project folde output:
.NET Command Line Tools (2.0.0-preview1-005977)
Product Information:
Version:            2.0.0-preview1-005977
Commit SHA-1 hash:  414cab8a0b
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.12
OS Platform: Darwin
RID:         osx.10.12-x64
Base Path:   /usr/local/share/dotnet/sdk/2.0.0-preview1-005977/
Microsoft .NET Core Shared Framework Host
Version  : 2.0.0-preview1-002111-00
Build    : 1ff021936263d492539399688f46fd3827169983
From: Dustin Campbell<EMAIL_ADDRESS>Reply-To: OmniSharp/omnisharp-vscode<EMAIL_ADDRESS>Date: Wednesday, 7 June 2017 at 16:19
To: OmniSharp/omnisharp-vscode<EMAIL_ADDRESS>Cc: objectref<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [OmniSharp/omnisharp-vscode] Intellisense does not show text description. (#1551)
C# for VS Code does pass along documentationhttps://github.com/OmniSharp/omnisharp-vscode/blob/master/src/features/completionItemProvider.ts#L60 to the completion items it creates. However, in this case, it appears that the documentation is not available to it at all.
@objectrefhttps://github.com/objectref: Could you run dotnet --info in the your project folder and let me know what the output is?
@terrajobsthttps://github.com/terrajobst, @richlanderhttps://github.com/richlander: Poking around a bit, it appears that the NETStandard.Library packages don't appear to contain XML documentation like, say, the ASP.NET packages do, which means that users don't get documentation on hover or completion in VS Code for core types and members. Is there are plan to start including documentation so that users get a good experience?
cc @Pilchiehttps://github.com/pilchie
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OmniSharp/omnisharp-vscode/issues/1551#issuecomment-306791988, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUHTS0UX7EBiIqlcU6LGMBiNlCqtYFQbks5sBqNcgaJpZM4NyDNh.

The last update to this issue was 8 months ago, were you able to find a fix @objectref ? @DustinCampbell do you know why the standard core SDK may be installing without XML documentation? F12 goes to definition from metadata, but this metadata has comments as seen in standard visual studio,  OmniSharp doesn't seem to use them though.

I can only get documentation work, when i clear out workspace storage, dotnet clean and build the projects against net462 or something similar. We cant have the spear head of .NET xplat development deliver a arguably worse dev experience for xplat projects than for full framework windows only projects.
Can we please get some communication here regarding XML documentation between this project and @terrajobst, if this has something to do with XML files missing in the NETStandard.Library package?
This is really annoying and i take documentation working over razor support any day.

This still seems to be an issue, even today, at least on ArchLinux.
I can get documentation to work(testing with System.Console.WriteLine()) by downloading the windows binaries, and copying the ~/packs/Microsoft.NETCore.App.Ref/3.1.0/ref/netcoreapp3.1/System.Console.xml to /usr/share/dotnet/packs/Microsoft.NETCore.App.Ref/3.1.0/ref/netcoreapp3.1/ in the case of a console application targeting netcoreapp3.1 as well as ~/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1/netstandard.xml to /usr/share/dotnet/packs/NETStandard.Library.Ref/2.1.0/ref/netstandard2.1/ in the case of a class library targeting netstandard2.1.
Surely fixing this would be a small change in a build script somewhere to output the XML documentation for Linux builds?

This works, provided that you follow these steps:

install the SDK via a script, see https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script. Thus the xml files with documentation are included in the SDK's ref folder.
Download the script
chmod +x dotnet-install.sh
./dotnet-install.sh --install-dir /home/yourusere/dotnet -channel Current -version latest
In your ~/.bashrc:
export PATH=$PATH:$HOME/dotnet
export DOTNET_ROOT=$HOME/dotnet
export PATH="$PATH:$HOME/.dotnet/tools"

start vscode from the command line

You may also need to run omnisharp: select project from the command palette.

I'm hitting this bug on Windows as well, but only if I'm building against netstandard2.0, not if I'm building against netcoreapp3.1.
I used the official x64 SDK installer from here:
https://dotnet.microsoft.com/download/dotnet-core/3.1
This is how the intellisense popup looks for me in VS Code:

This is what it looks like in Visual Studio 2019 (Community edition):

Output of dotnet --info:
.NET Core SDK (reflecting any global.json):
 Version:   3.1.403
 OS Name:     Windows
 OS Version:  10.0.19041
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.1.403\

Host (useful for support):
  Version: 3.1.9
  Commit:  774fc3d6a9

.NET Core SDKs installed:
  2.1.811 [C:\Program Files\dotnet\sdk]
  3.1.403 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Same problem here.
There is no documentation when using netstandard 2.0 in VS Code under Windows.
Did anyone manage to get intellisense to work with netstandard 2.0?
Thanks!

Update:
I figured out that the problem was based on Unity referencing its own netstandard.dll and doesn't provide the corresponding xml documentation file.
After copying the xml file from the official nuget package, everything worked as expected.

(For example, copy something like Program Files\dotnet\packs\NETStandard.Library.Ref\2.1.0\ref\netstandard2.1\netstandard.xml to somewhere like \[Unity editor application]\Data\NetStandard\ref\2.1.0\, the same folder containing netstandard.dll)

The same problem with .NET 7.0.203 and Visual Studio Code 1.77.3 on Windows

Cannot reproduce with current release.


fix algolia search

Signed-off-by: Samhita Alla<EMAIL_ADDRESS>dummy edit -- updated requirements.txt
Read then delete this section
- Make sure to use a concise title for the pull-request.
- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version
will be bumped. More details
TL;DR
Please replace this text with a description of what this PR accomplishes.
Type

[ ] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
Remove the 'fixes' keyword if there will be multiple PRs to fix the linked issue
fixes https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

Should we merge this?

Should we merge this?

Yes!


ROI not performed in v1.9.2

Hi all,
I am using a holybro pixhawk 4 with px4 version 1.9.2 (px4_fmu-v5_multicopter.px4). I wanted to try ROI by yawing the copter instead of a gimbal.
Describe the bug
I noticed that ROI is not performed between two waypoints. Hence, the copter's nose is not pointing towards ROI, but instead towards the next waypoint.
To Reproduce
Steps to reproduce the behavior (with Airsim simulation):

Uploaded mission in QGC (see attachment mission.txt)
Started mission
Took off
See if ROI works
Observations:
Waypoint 1 is reached.
Copter is oriented towards Waypoint 2
Copter flies towards Waypoint 2 (nose headed towards it)
Waypoint 2 is reached.
Mission ended -> RTL

Expected behavior
The ROI from the exact same mission is performed as intended with the firmware 1.8.2: The copter's nose is pointing towards ROI while flying to Waypoint 2. Hence Reproduce step 6 should be "oriented towards ROI"
Drone (please complete the following information):

I first noticed the behavior with my Hexacopter Y6
All further tests were done (with the exact reproduced problem) inside simulation (Airsim HIL)
Both cases: Firmware 1.9.2, px4_fmu-v5_multicopter.px4 not working, and px4_fmu-v5_default.px4 1.8.2 working

Log File
I will simulate the mission again, and hand in the log file asap

Thanks for reporting. @MaEtUgR @bresch


pylance is adding () when auto paran is enabled for decorator

type  @override or @overload
in
class A:
       @overload

if autoParan is on, pylance will insert () after decorator interfering typing.

Yeah that seems like a case we should skip adding the parens.

Briefly looked at this issue, @heejaechang are we suggesting to disable parentheses for all decorators? There're decorators with parameters that would need the parentheses to be there.

I think doing less is better than doing wrong. because doing wrong will require users to fix things up. especially if it is done without user explicit asking such as this case.
so in my opinion, the simplest way to fix will be just not adding () for all decorators. but that said, if we want to make it a bit smarter, then we can check whether the decorator is a regular decorator (one that doesn't have arguments), or decorator factory (one that has arguments) and only add () if we are sure the decorator is a decorator factory.
I didn't see the code to see whether there is already existing info on whether decorator is factory or not. but if not, we could use some heuristic to check.


Prepend queue ids

closes #1245 - does what it says on the tin.
I'd rather have a has_many :subjects, through: :set_member_subjects relation on SubjectQueue working but the has_many_through scope didn't work with the belongs_to_many link.


use RepeatedPtrFieldtipb::Expr instead of vector<tipb::Expr *>

What problem does this PR solve?
Issue Number: ref https://github.com/pingcap/tiflash/issues/6233
Problem Summary:
Use RepeatedPtrField<tipb::Expr> instead of vector<tipb::Expr *> to reduce useless copy and make code clear.
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[x] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge


2.0.0.Alpha1

@jamezp  I'll do a 2.0.0.Alpha1 pre-release according to RESTEasy 5.0.0.Alpha1 pre-release. I disabled the deploment tests because jboss-modules is no longer exist.

pr moved here: https://github.com/resteasy/resteasy-spring/pull/7


Fix some issues in Beyla component docs

PR Description
This PR fixs the following issues in Beyla docs page.

Link to Kubernetes section were broken
block table had improper formating

PR Checklist

[ ] CHANGELOG.md updated
[x] Documentation added
[ ] Tests updated
[ ] Config converters updated

I'll merge this one so the fix is in quickly :-)


Onboarding credentials showing loading spinner without credentials

Lately when going through the onboarding flow, sometimes the issuance of the started credentials shows the following page. When resetting the dashboard and starting over it is often resolved, but I've had occurrences where it will happen twice in a row.
Not sure what is going on here. No errors are logged in the browser console.

@janrtvld any idea what is happening here?

This is probably because the credential issue request is rejected or still pending (for some reason). I've made it so that you can't continue, but when the request is rejected there's no error handling in place. The user is issue the credentials again by pressing i didn't receive anything, but this should be handled differently.
What wallet are you using? I've had this issue with the Trinsic wallet sometimes, but never with Lissi.

Closing this as i've added error handling a few months back and this should be solved.


Popup content keeps rendering

Bug Report
Steps

Place a <Popup />
console.log the render of the Popup's content
Trigger the Popup
Watch console - infinite renders, while the Popup is triggered

Expected Result
Render component only when it's required and necessary
Actual Result
Infinite number of renders
Version
0.81.1
Testcase
https://codesandbox.io/s/8kxxwjm3ol
note - the forked codesandbox was originally 0.75.x which was working as expected. After I changed version to 0.81.1, the bug came up as described

Caused by https://github.com/Semantic-Org/Semantic-UI-React/pull/2775?

Very likely so<EMAIL_ADDRESS>still works, #2775 was released in 80.0.1


Birthday Cake

Yellow cake: https://smittenkitchen.com/2009/07/best-birthday-cake/
Raspberry filling: TODO
Chocolate ganache frosting: use the recipe I already have
Decoration: TODO - flowers, maybe with a raspberry in the middle of each one?

More recipes for reference
https://tidymom.net/chocolate-frosted-yellow-cake/
https://foodlikecake.wordpress.com/2014/03/19/yellow-cake-with-raspberry-filling/
https://www.bobsredmill.com/blog/recipes/yellow-cake-with-raspberry-and-chocolate-frosting/
https://hipfoodiemom.com/2012/12/14/vanilla-cake-with-raspberry-filling-and-chocolate-buttercream-frosting/

What I used:

yellow cake
raspberry filling
chocolate ganache frosting


TypeError: Cannot read property 'map' of null when parsing certain URLs

Platform: Mac OSX 10.13.6
Mercury Parser Version: 2.1.0
Node Version (if a Node bug): 11.13.0

Expected Behavior

Should be able to parse url
Current Behavior
Encounter error when attempting to parse certain URLs.
TypeError: Cannot read property 'map' of null

Steps to Reproduce

Call the parse method with the following URL (example) https://www.nationalreview.com/corner/indias-economy-to-surpass-britains/

Detailed Description
The error is hit here:
Trace: TypeError: Cannot read property 'map' of null
    at Object.<anonymous> (.../node_modules/@postlight/mercury-parser/dist/mercury.js:1267:43)

It occurs because the "urlSet" variable ends up being a string with length 1 which is only whitespace: a single space character. The urlSet.match function subsequently returns null and an error is hit when calling .map() on that null
Possible Solution
One solution that worked was adding an extra condition to the if statement on 1262
if (urlSet) {
// changed to:
if (urlSet && urlSet.trim()) {

But a more general purpose solution is to properly account for the possible null returned from the match function
if (urlSet) {
  // a comma should be considered part of the candidate URL unless preceded by a descriptor
  // descriptors can only contain positive numbers followed immediately by either 'w' or 'x'
  // space characters inside the URL should be encoded (%20 or +)
  var candidates = urlSet.match(/(?:\s*)(\S+(?:\s*[\d.]+[wx])?)(?:\s*,\s*)?/g);
  if (!candidates) return; // <----- Adding this line here
  var absoluteCandidates = candidates.map(function (candidate) {
    // a candidate URL cannot start or end with a comma
    // descriptors are separated from the URLs by unescaped whitespace
    var parts = candidate.trim().replace(/,$/, '').split(/\s+/);
    parts[0] = URL.resolve(rootUrl, parts[0]);
    return parts.join(' ');
  });

  var absoluteUrlSet = _toConsumableArray(new _Set(absoluteCandidates)).join(', ');

  setAttr(node, 'srcset', absoluteUrlSet);
}

Thanks for reporting and looking into this, #386 addresses this issue.


Creating a new branch for the homepage project.

Create and checkout to develop branch — git checkout -b develop.

Develop branch - created


chore: create folder structure for web_helper helper functions

generate_button.R, download_data.R, select_sets.R, select_weights.R.
Where do these files live?

web_dev folder


(#681) packageName needs to be lowerCase for v3-flatcontainer

According to https://docs.microsoft.com/en-us/nuget/api/package-base-address-resource#request-parameters-1
Also, added some logging to "see" the error in the first place.
fixes #681

@nils-a thanks for getting this fixed up!


Monitoring

Add the facility to monitor gateways

Send e-mail if there is an issue
Provide a dashboard of status

Implemented in the ttn-monitor repo


Accessing the bootloader after assembly

TL;DR
add hole to bottom plate
find proper button to fit on existing pads
In order to access the bootloader, should it need to be updated or changed after assembly, we need to add a hole to the bottom plate .dxf OR drill into the bottom plate while the paper adhesive is still on the plate.
We also need a button to solder onto the "sw2" pads on the bottom side of the board. I used the ones in the link but they don't actually fit. I had to do some ghetto bending of the pins.
https://www.amazon.com/dp/B07VSNN9S2

This may only be necessary during active development.
Can make hole big enough for standard pair of tweezers or change footprint / part to a standard 6mm^2 momentary push button

foot print has been changed on the layout. a standard 6mm^2 pushbutton should fit onto / into the pads


Resolve and redirect different urls for platform pages

Platform page is currently at https://creativecommons.org/platform/ .. new staging puts it at https://staging.creativecommons.org/about/platform/ .. Let's make sure both direct to the same place once launched.
Also for toolkit, it currently sits at https://creativecommons.org/platform/toolkit/ .. new staging puts it at https://staging.creativecommons.org/about/platform/integration-toolkit/ .. let's make sure both direct to same page

There are now redirects in place from the old locations to the new.


Extensions shows two striff-report buttons when switching between tabs in a GitHub PR

Unable to reproduce.


Add region handling of boundary points from arc

Currently only start and end point of arc are included in region, it is required to include at least some points on arc to correctly create regions.

Needs #64

Will be closed by #59


Finish beach reassembly

Photos by Vincent Lyon:

Essentially described in #50, so closing this one.


feat: add mongodb 1.15.2 release

update mongodb with release 1.15.2

:tada: This PR is included in version 1.115.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


no matches for kind "analytics" in version "config.istio.io/v1alpha2"

When I execute
kubectl apply -f samples/apigee/definitions

I got the following error.
customresourcedefinition. "apigees.config.istio.io" created
customresourcedefinition. "analytics.config.istio.io" created
authorization.config.istio.io "apigee" created
error: unable to recognize "samples/apigee/definitions.yaml": no matches for kind "analytics" in version "config.istio.io/v1alpha2"

Did I miss any step? Thanks.

Yes, sometimes Istio has a timing issue. Can you please rerun this command and it will work?


Can not sanitize simple git repos

Right now, because of how we check if something is a git repo, simply running git init on an empty folder and committing some files to it is not enough for repobee-sanitizer to recognize the folder as a valid git repo

What exactly is the problem? The check_repo_state function will pass just fine if you have only a single commit.

I made a repo with git init, but some files in it, and committed. Got an error saying that it was not a proper git repo. I dont know exactly what it said but im guessing it came from the gitpython library

I can't reproduce that. Could you give me a step-by-step of what you did?

This works now! I think i must have had a repo without any commits even though I thought i had at the time.


Ion-select is broken, not showing any text value

Short description of the problem:
ion-select is broken. The popup has no text.
What behavior are you expecting?
ion-select work as expected, showing text values for the options.
Steps to reproduce:

Create an ion-select with a few ion-option.
Set value for every option (value="f") and mark one as checked (checked="true")
Observe the wrong behavior

The pop up window shows the radio buttons but not the associated text with them

The issue occurs with the basic code example used in the docs. (Not the demo on the right, but the code used in a plunker. Maybe the demo uses an older ionic version?)
<ion-item>
  <ion-label>Gender</ion-label>
  <ion-select [(ngModel)]="gender">
    <ion-option value="f">Female</ion-option>
    <ion-option value="m" checked="true">Male</ion-option>
  </ion-select>
</ion-item>

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
This issue can be related to other recent issues with ion-select like #6970, #6898
Which Ionic Version?
Ionic 2.x
Plunker that shows an example of your issue
http://plnkr.co/edit/8p4z8T?p=preview
Run ionic info from terminal/cmd prompt:
Your system information:

Cordova CLI: 6.2.0
Gulp version:  CLI version 1.2.1
Gulp local:   Local version 3.9.1
Ionic CLI Version: 1.7.16
Ionic App Lib Version: 0.7.3
ios-deploy version: 1.8.6
ios-sim version: 5.0.8
OS: Mac OS X El Capitan
Node Version: v6.3.0
Xcode version: Xcode 7.3.1 Build version 7D1014

Hello! Thanks for opening an issue with us. I have tested with the latest nightly and their does not seem to be an issue anymore. If you would like to give ionic 2 nightly a try yourself you can run npm install ionic-angular@nightly and this will install the latest ionic 2 nightly package for you. Thanks for using Ionic!


iptables - unable to create rules on WSL2 (iptables "recent" module)

Windows Version
10.0.22631.3007
WSL Version
WSL version: <IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64
Distro Version
CentOS
Other Software
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3007
Rocky Linux 9.3
Repro Steps
WSL2 : Centos/Rocky Linux 9
iptables -A test0-in -p tcp --dport 1111 -m state --state NEW -m recent --set
Warning: Extension recent revision 0 not supported, missing kernel module?
iptables v1.8.8 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain
Expected Behavior
Rules has to set
Actual Behavior
Warning: Extension recent revision 0 not supported, missing kernel module?
iptables v1.8.8 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain
Diagnostic Logs
No response

@sreemtech current WSL Linux kernel has CONFIG_NETFILTER_XT_MATCH_RECENT not set, so -m recent fails.
See details at: https://github.com/microsoft/WSL2-Linux-Kernel/blob/ee5b8e3dcbc682f7b3f149d90544b007c50d74f6/arch/x86/configs/config-wsl#L1172


Specify URL Scheme ide://

I figured out that the URI Scheme was missing.
Specifying the URL Scheme does try launch starfix application(tested on macos Catalina 10.15.7).
The problem that still remains is that I am unable to launch the Starfix application on mac (after moving starfix to application folder).
One might wonder that if the application doesn't launch then how am I concluding that this ide:// scheme handler works ?? Well, on hitting open ide://somtxt on the Terminal I can see starfix application bouncing on my Dock at the bottom (The same behaviour which happens when I try  to open the starfix application directly)
Another thing I was wondering is that could we run the build.sh script beforehand while the installer is being generated(through gh-actions) . This is a low priority concern but I was just thinking about it so that the user gets the starfix.app directly which he can directly move to applications folder. (I am not sure if the output of build.sh is system dependant: if yes then this point is of no use)

Here's a quick preview of what happens. Note that here I am triggering starfix application from the browser which indicated that the ide:// protocol  handler is working fine. (I've installed the extension from the Mozilla Add on store just to confirm if evrything is working fine with the extension)
https://user-images.githubusercontent.com/31308705/128033518-d7bb95e1-84dc-4951-b682-37698a4a9257.mov

The problem that still remains is that I am unable to launch the Starfix application on mac (after moving starfix to application folder).

what are you moving to the application folder exactly ?

Another thing I was wondering is that could we run the build.sh script beforehand while the installer is being generated(through gh-actions) .

Thats the intention (that it runs during gh-actions)

The problem that still remains is that I am unable to launch the Starfix application on mac (after moving starfix to application folder).

what are you moving to the application folder exactly ?

I'm trying to move starfix.app ( the output generated after running build.sh)


validation custom directive

http://plnkr.co/edit/Sr7NZIcjf13p9EEZe3PL?p=preview
when user focus in custom directive(first element in sample) then blur without value, validation not show any error message.
but user focus in input tag(second element in sample) then unfocus without value,validation show error message .
why validation not show error message for my custom directive ?

Did you copy the CSS Styling from the examples I made? Also which browser and AngularJS function are you using?

I added css styling to plnker example but not correct .
I use of chrome 54 .
Please see plnkr link http://plnkr.co/edit/Sr7NZIcjf13p9EEZe3PL?p=preview
validation not work for custom directive .

Your custom element <my-input/> (let's call it the Parent) is creating a regular input (the Child) but you didn't pass the validation attributes to the Child input. You need to pass the validation attribute to the <input/>  that is inside the Directive.

You can take a look at this custom input template example which was created by another user. It is similar to your problem.

This is partially working, don't have more time to spend http://plnkr.co/edit/ZWgTxOm4WYNYyHQhG8H0

thank you


closes #1105 Make brands clickable on Product Page

Description

Made brands clickable on the product page.

Created Model class brand to hold the JSON result of API Call.

Created BrandActivity to show the list of products the brand contains in recyclerView.

Related issues and discussion
closes #1105
Screen-shots, if any
Loading Screen:

Products List:

Error Screen:

Nice .

Thanx @PrajwalM2212 :).

@Karljoones I've made the changes also added infinite recycler view and as @jaztriumph has suggested I've used Search.java model class instead of creating a new one to hold the response. Please review :).

small conflict to merge

Merged, thanks @Shubham2320 !


Make the firstChecksum positive by adding 10 if it's negative

Before this patch, it was possible to have a result "100003050-18" for the number 100003050.
This is fixed now.

Thanks! Can you add unit tests for this specific case too?

Sure I can but I'm not sure I understand correctly. Did you mean new unit tests for TurkishIdGen or new test cases in addition to the existing ones for TurkishIdNumber and TurkishIdAttribute? Asking because TurkishIdNumber.IsValid handles the case very well, the only problem was generator utility which has no tests right now. Please let me know then I'll do what needs to be done.

Oh sorry I thought this was a bug in the library. Didn't notice it was a problem with the generator. I don't think we need tests for that. Thanks!


express-ws does not work with razzle

How to set websocket for razzle? Below is my code.
// server.js
import express from "express";
// ...
import expressWebSocket from "express-ws";
const server = express();

expressWebSocket(server);
server
  .ws("/echo", function(ws, req) {
    ws.on("message", function(msg) {
      console.log(msg);
    });
    console.log("socket", req.testing);
  })
 // ...

// pages/Home.js

class Home extends React.Component {
  componentDidMount() {
    new WebSocket(`ws://${document.location.host}/echo`);
  }
}

My error shows up in the console of my browser:
WebSocket connection to 'ws://localhost:3000/echo' failed:
Error during WebSocket handshake: Unexpected response code: 200

This issue is still the case for me. bump.


Meta PR: Including all my changes

Added sprinting #10
Allow Forward/Backward movement while strafing
Fixed runtime script error (assign const) #4
Reorganized and renamed files to play nicer when imported from the asset library #5 #2
Reorganized the Scene file so that the FpsController parameters can be accessed by the including scene #8

Merge pull request button is not working.. very good request


1、批预测时预先为结果开辟空间。

2、修改批预测时结果变量名称。

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.PowersMrLi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

paddlex.h 头文件中 批处理结果 也应该有result 变为results 这个头文件没有提交。


s3proxy: skip tests on Darwin

Tests block (seemingly) forever on Darwin, but otherwise the package builds and runs fine.
I tried enabling the sandbox on a Darwin machine, but that fails because the tests can't run a service on <IP_ADDRESS>.
Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[X] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[X] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks @wegank - applied and squashed.

@ofborg build s3proxy s3proxy.passthru.tests


HSEARCH-4496 Upgrade to Elalsticsearch 8.0.1 (client and tested version)

https://hibernate.atlassian.net/browse/HSEARCH-4496

Elasticsearch 8.0.1 has a regression; I'll move the testing of Elasticsearch 8.0.1+ to a separate ticket (https://hibernate.atlassian.net/browse/HSEARCH-4497) and reopen a PR for the client upgrade only.


About forget password and signup support

We're not going to add signup and forget-password support to the app anytime soon, and the next section explains why
Why?
After careful evaluation, our team has decided to not include the feature in the app, since HotinGo is supposed to be an admin-level management system, and giving direct access to signup and take destructive actions inside the application is never going to be secure, and since the function is not going to be used more than 1-2 times in the entire application's lifecycle, why bother risking security for pure aesthetics. So, the feature would be only available through direct MySQL database updates.

That's the current state, and this closes the issue


Remove additional parenthesis

Accidently added an additional parenthesis when updating regex from PR feedback previously

Fine, merging into dev_0.2.6 and squashing afterwards before taking into main. Closing, thanks!


MC: designated reporter "someone else" label styling issue

The "someone else:" label has no padding applied above or below. See figma for correct padding.
Build:

This is a duplicate. closing


df-358: Allowing self-signed certs in unirest

This PR resolves #358. It creates a custom http client with a custom verifier to allow all certs. Super insecure but it was a request.
It also surfaces any error that is caused during the construction of the dot valve due to a problem creating the httpclient.

This was a tough one to test...i resurrected DrillTest (github.com/hashmapinc/DrillTest) and created a self-signed cert and added that to the configuration, then i went through the token refresh before and after. it failed before, it works now.


Implement pow

I implemented __pow__ method. It uses identity.
check #358 first
related to #36

LGTM


chore: bump version

bumping for next release to b4

I guess b2 and b3 weren't merged to main yet then - nvm this PR then!


look into maplibre as replacement for mapbox

https://github.com/maplibre/maplibre-gl-js

done in upcoming v2


Some types (int64) are not supported yet.

🐛 Bug
By mistake i tried to add an image (array) of type int64 and boom -- it crashes.
We might want to have some tests or examples for more exotic types.
For example, complex types would be cool but are outside the scope of this issue...
(but exciting!)
To Reproduce
Create an array of int64 dtype and try to view it in napari...
You get this:
WARNING: Traceback (most recent call last):
  File "/Users/royer/workspace/python/pitl/pitl/it/demo/demo_it_n2s_gbm_2D_rgb.py", line 76, in <module>
    demo(astronaut())
  File "/Users/royer/workspace/python/pitl/pitl/it/demo/demo_it_n2s_gbm_2D_rgb.py", line 31, in demo
    rescale_intensity(noisy, in_range='image', out_range=(0, 1)), name='noisy'
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/contextlib.py", line 119, in __exit__
    next(self.gen)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/napari/_qt/event_loop.py", line 31, in gui_qt
    app.exec_()
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/app/backends/_qt.py", line 501, in event
    out = super(QtBaseCanvasBackend, self).event(ev)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/app/backends/_qt.py", line 818, in paintGL
    self._vispy_canvas.events.draw(region=None)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/util/event.py", line 455, in __call__
    self._invoke_callback(cb, event)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/util/event.py", line 475, in _invoke_callback
    self, cb_event=(cb, event))
  << caught exception here: >>
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/util/event.py", line 471, in _invoke_callback
    cb(event)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/scene/canvas.py", line 217, in on_draw
    self._draw_scene()
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/scene/canvas.py", line 266, in _draw_scene
    self.draw_visual(self.scene)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/scene/canvas.py", line 304, in draw_visual
    node.draw()
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/scene/visuals.py", line 99, in draw
    self._visual_superclass.draw(self)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/visuals/visual.py", line 443, in draw
    self._vshare.index_buffer)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/visuals/shaders/program.py", line 101, in draw
    Program.draw(self, *args, **kwargs)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/gloo/program.py", line 533, in draw
    canvas.context.flush_commands()
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/gloo/context.py", line 176, in flush_commands
    self.glir.flush(self.shared.parser)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/gloo/glir.py", line 572, in flush
    self._shared.flush(parser)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/gloo/glir.py", line 494, in flush
    parser.parse(self._filter(self.clear(), parser))
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/gloo/glir.py", line 819, in parse
    self._parse(command)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/gloo/glir.py", line 787, in _parse
    ob.set_data(*args)
  File "/Users/royer/anaconda3/envs/pitl/lib/python3.7/site-packages/vispy/gloo/glir.py", line 1537, in set_data
    raise ValueError("Type %r not allowed for texture" % data.dtype)
ValueError: Type dtype('int64') not allowed for texture
ERROR: Invoking <bound method SceneCanvas.on_draw of <SceneCanvas (PySide2) at 0x128724438>> for DrawEvent
WARNING: Error drawing visual <Image at 0x133fde5f8>
ERROR: Invoking <bound method SceneCanvas.on_draw of <SceneCanvas (PySide2) at 0x128724438>> repeat 2

Environment

napari Version (e.g., 1.0): 0.1.3
OS (e.g., Linux): OSX
Python version: 3.7
Any other relevant information:

I can reproduce this bug - probably fixable by checking the type and casting the _data_view which is what we actually send over to vispy, that way the original data is unchanged.
@kne42 @jni do you have thoughts on how best to do this? Something like?
if X.dypte == np.int64:
   X = X.astype(int)

If modifying the original array is not something that we'll be doing, I would use the following instead:
if arr.dtype == np.int64:
    warn("Type dtype('int64') not allowed for texture")
    arr = arr.view(np.int)

This way we aren't creating a new copy every time :)

you'd also probably want to cover all of the other exotic data types:
from vispy.gloo.glir import GlirTexture
texture_dtypes = GlirTexture._types.keys()

...

dtype = np.dtype(arr.dtype)
msg = f'type {dtype} not allowed for texture; must be one of {set(texture_dtypes)}'
if dtype not in texture_dtypes:
    try:
        dtype = dict(i=np.int32, f=np.float32)[dtype.kind]
    except KeyError: # not an int or float
        raise TypeError(msg)
    warn(msg)
    arr = arr.view(dtype)

@kne42 doesn't np.int resolve to np.int64 on most platforms these days?

@jni correct, so it should explicitly be np.int32 in the first example


[hotfix] Fix that Maven 3.2.5 cannot build paimon-core

Purpose

Use Maven 3.2.5 to build paimon-core will throw error: cannot find org.apache.hadoop.hive.ql.exec.vector.
This PR fix it.
Tests

API and Format

Documentation

+1


Add macro to include style from external css file.

Currently we can write the style directly inside style! macro. We are validating some basic things like semicolons and valid css properties in this style macro. But full css support from IDE might be usefull for big projects. So we can give one more macro something like style_sheet!("path/to/the/file").

Now this feature has been added in version v0.2.0. So closing this issue.


Confusing use of identically named miden.toml in both miden-client and miden-node

When attempting to run both miden-node and miden-client for testing one is tempted to run the node and client in the same local directory on top of the same miden.toml file. Afterall, aside from the rpc protocol endpoint field, the miden-node version of miden.toml seems to carry the same information which appears in the miden-client version. this however is not the case. Even after introducing the rpc endpoint protocol field in the miden-node version, attempting to run miden-client database operations throws errors such as
store error: database-related non-query error: no such column: a.id in SELECT a.id, a.nonce, a.vault_root, a.storage_root, a.code_root, a.account_seed FROM accounts a WHERE a.nonce = (SELECT MAX(b.nonce) FROM accounts b WHERE b.id = a.id) at offset 7
Obviously, if miden-client and miden-node are run from separate directories everything works fine. This begs the question of whether it's absolutely necessary for the two miden.toml files to be named identically.

This is a good point. We should probably rename the client's toml file to miden-client.toml or something similar.


Conflict between 'email' and 'admin_email'

The install.php script uses the INSTALL_EMAIL environment variable in two places (for email and for admin_email):
'email'     => getenv("INSTALL_EMAIL"<EMAIL_ADDRESS>'admin_email' => getenv("INSTALL_EMAIL"<EMAIL_ADDRESS>This results in the following error:
Installing database. Please wait...
Database installation failed. Errors:
  Conflicts with system email above

Caused by this in upload/setup_hidden/inc/class.installer.php:
    //Staff's email can't be same as system emails.
    if($vars['admin_email'] && $vars['email'] && !strcasecmp($vars['admin_email'],$vars['email']))
        $this->errors['admin_email']=__('Conflicts with system email above');

The fix is to differentiate between the email address of osticket vs. the email address of the admin user.  Consider replacing INSTALL_FIRSTNAME, INSTALL_LASTNAME, etc with ADMIN_FIRSTNAME, ADMIN_LASTNAME, ADMIN_EMAIL, etc...

Thanks for reporting the issue. You're right, the environmental variable is incorrectly used twice for different purposes.
I've updated the image and renamed the administrator related variables to resolve. Let me know if you have any further issues.


Database lock when running two SoS on the same system

This is perhaps hard to reproduce, but I'm again on the cluster but 2 different compute nodes. One node runs one interactive SoS command and the other runs a task based command. The SoS project folders are different. However I got an error on database lock in one of my command.
WARNING: Failed to set step signature for step 68ec857ec4de65a4: database is locked

Not sure how to reproduce it reliably, but perhaps there are some first principle based diagnostics (eyeballing the code ...) that can give a hint of what is going on?

There is still a unprotected global signature database, used to track steps with output outside of the current project directory... perhaps this can be removed.

Is this ~/.sos/step_signatures.db the file in question? I still see it generated after I removed it and ran my workflow on current master. Looks like it is still being used? I tried to run two workflows from two folders, and still got for one of them:
[WARNING: Failed to clear workflow database: database is locked
WARNING: Failed to write workflow signature of type workflow and id 75df8719e260ce54: database is locked

In fact it now looks worse:
INFO: Step lm_less03 (index=108) is ignored with signature constructed
WARNING: Failed to set step signature for step a6b2e54eb4987efd: database is locked
WARNING: Failed to write workflow signature of type tracked_files and id a6b2e54eb4987efd: database is locked
INFO: Step lm_less03 (index=109) is ignored with signature constructed
WARNING: Failed to set step signature for step de08897f9353e0c8: database is locked
WARNING: Failed to write workflow signature of type tracked_files and id de08897f9353e0c8: database is locked
INFO: Step lm_less03 (index=110) is ignored with signature constructed
WARNING: Failed to set step signature for step e3ab9d75217c2d15: database is locked
WARNING: Failed to write workflow signature of type tracked_files and id e3ab9d75217c2d15: database is locked
INFO: Step lm_less03 (index=111) is ignored with signature constructed
WARNING: Failed to set step signature for step b44ddb5bfe4d2711: database is locked
WARNING: Failed to write workflow signature of type tracked_files and id b44ddb5bfe4d2711: database is locked
INFO: Step lm_less03 (index=112) is ignored with signature constructed
WARNING: Failed to set step signature for step 150328a38c102e83: database is locked
WARNING: Failed to write workflow signature of type tracked_files and id 150328a38c102e83: database is locked
INFO: Step lm_less03 (index=113) is ignored with signature constructed
WARNING: Failed to set step signature for step 61849aee778e6686: database is locked
WARNING: Failed to write workflow signature of type tracked_files and id 61849aee778e6686: database is locked
...

This file should be gone now


Got Cartpole working

Sorry one more comment, I didn't review the notebooks as it's just a terrible interface on github. If you want those reviewed just LMK


A possible memory leak issue in wasi-nn.c

A module instance is inserted into an internal wasi-nn hashmap when wasm runtime gets wasi-nn context, but is not removed when destroying wasi-nn context, which may cause memory leak and get a stale instance or context.
I found this issue during a test where a wasi-nn enabled host application tried to load and unload a wasi-nn wasm module repeatedly. This issue looks gone after removing the instance in wasi_nn_destroy.

please review the created PR: https://github.com/bytecodealliance/wasm-micro-runtime/pull/2613

You are right, thanks!


Artwork history

Artwork history sections.
#minor

Fails

:no_entry_sign:
No CHANGELOG added.

:no_entry_sign:
Missing Test Files:

src/lib/Scenes/Artwork/Components/__tests__/ArtworkHistory-tests.tsx

If these files are supposed to not exist, please update your PR body to include "#skip_new_tests".

  Generated by :no_entry_sign: dangerJS

@saolsen looks like you have some typescript errors and still need to remove the ArtworkHistoryState  interface, but other than that this looks good to go!

merge on green


Fix some linter warnings from mfma refactor

@AlexBrownAMD I think we should have a separate pipeline for static code lint, as it is hardware agnostic and shouldn't prevent pytest from running

@AlexBrownAMD I think we should have a separate pipeline for static code lint, as it is hardware agnostic and shouldn't prevent pytest from running.

I don't disagree, but this somewhat relates to #982 and automatic code reformatting. We need to choose YAPF or a similar solution, instead of imposing draconian Lint checks as part of QA. If lint failures can be removed by virtue of a reformatter, then this issue becomes moot.


Sc-5986 : implement Trisa organization profile component

Scope of changes
Sc-5986 : implement organizational detail component
Type of change

[ ] bug fix
[x] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria

Author checklist

[ ] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report

Merging #579 (f6fbba8) into main (a3b6e1d) will increase coverage by 0.31%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #579      +/-   ##
==========================================
+ Coverage   37.84%   38.16%   +0.31%
==========================================
  Files         413      153     -260
  Lines        4711     2416    -2295
  Branches     1163      614     -549
==========================================
- Hits         1783      922     -861
+ Misses       2749     1320    -1429
+ Partials      179      174       -5

Impacted Files
Coverage Δ

...r-ui/src/components/NetworkAnnouncements/index.tsx

...er-ui/src/components/OrganizationProfile/index.tsx

web/gds-user-ui/src/components/Sidebar/index.tsx

...s-user-ui/src/modules/dashboard/overview/index.tsx

...user-ui/src/components/Section/MembershipGuide.tsx

...er-ui/src/components/Sidebar/MobileNav.stories.tsx

...b/gds-user-ui/src/components/ContactForm/index.tsx

...ts/SwitchFormControl/SwitchFormControl.stories.tsx

...workAnnouncements/NetworkAnnouncements.stories.tsx

...b/gds-user-ui/src/components/UserDetails/index.tsx

... and 250 more

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 a3b6e1d...f6fbba8. Read the comment docs.


*: adjust region syncer code structure

What problem does this PR solve?
extract the region syncer to a package.
Check List
Tests

Unit test
Integration test

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

PTAL @disksing @rleungx


Add OverseasPassportsCalculator to regression test checksums

Description
This should've been added as part of #2367, so that changes to the calculator cause the regression tests to run.
I did this by running the following command:
$ rails r script/generate-checksums-for-smart-answer.rb overseas-passports \
  lib/smart_answer/calculators/overseas_passports_calculator.rb

External changes
None.

Well spotted, thanks for adding this @floehopper

Rebasing against master and force-pushing in preparation for merging.


Update tgl.po

Finished updating. Pls check for some mistakes. Thanks 😄

Sorry for taking this long


Feature dynamic fusion - fuses communication calls based on fusion policy

This PR implements communication fusion, where they level of fusion is implemented via a simple integer policy (2 = fuse every 2 comm calls into 1), with the idea of later plugging in various fusion policies.
It uses a single, global comm buffer to optimize for speed and minimal memory overhead.   In effect it is a cascading series of graph rewrites to optimize the communication overhead.
This PR is dependent upon the status of the clone node removal PR (pending), so for now this adds the impl but is not linked to run via SPMD api in this PR.

Regarding the general questions:
1 - Could we add unit tests to make sure that we check transformation behavior?
Yes, but I'd like to do it separately vs this PR as this PR is already dependent on another PR (the clone node PR).  That's in part why fusion is not hooked in for this PR (adds the code, but not live/linked to SPMD api yet.
Once the clone PR is finalized, then can do the unit tests.  Have opened this issue to track:
https://github.com/pytorch/tau/issues/655
2 - Could you explain what are the current limitations of the approach and what are the next steps?
Sure - current limits:
a - we expect the DTensor signature for comms as we reuse the existing wait_comm nodes for where fusion is implemented.  Thus need to add ability to generate our own wait_comm nodes if we want to have it handle any comm calls for fusion.
b - right now we assume that all calls use the same process group (and thus any call is eligible for fusion with any other call).  That is not correct for all cases and so we need to add inspection of PG and then only fuse same PG calls in the future.
(added tracking issue: https://github.com/pytorch/tau/issues/657)
c - similarly, we assume we need an FP32 buffer but we should inspect the dtype and then enable appropriate dtype buffer.
(added tracking issue: https://github.com/pytorch/tau/issues/656)

Next steps:
a - get clone situation finalized
b - add fusion policy based on requested comm size (currently impl as merging of number of calls to merge)
c - add unit tests
d - integrate reader function that can read the policies expressed by variable bucket size policy (where we will have erratically spaced fusions).  This seems to be the most performant per the simulation so need to get a real graph and add a reader to interpret that.
e - add reader and functions for for capuchin policy (dynamic activation checkpointing) where we will checkpoint only some tensors and swap others.  This is arguably the other 'big' improvement for perf in the immediate pipeline.
f - add shifting support where we move some comms into forward pass to improve net backwards pass time.

Regarding the general questions:
1 - Could we add unit tests to make sure that we check transformation behavior?
Yes, but I'd like to do it separately vs this PR as this PR is already dependent on another PR (the clone node PR). That's in part why fusion is not hooked in for this PR (adds the code, but not live/linked to SPMD api yet. Once the clone PR is finalized, then can do the unit tests. Have opened this issue to track: #655
2 - Could you explain what are the current limitations of the approach and what are the next steps? Sure - current limits: a - we expect the DTensor signature for comms as we reuse the existing wait_comm nodes for where fusion is implemented. Thus need to add ability to generate our own wait_comm nodes if we want to have it handle any comm calls for fusion. b - right now we assume that all calls use the same process group (and thus any call is eligible for fusion with any other call). That is not correct for all cases and so we need to add inspection of PG and then only fuse same PG calls in the future. (added tracking issue: #657) c - similarly, we assume we need an FP32 buffer but we should inspect the dtype and then enable appropriate dtype buffer. (added tracking issue: #656)

Thanks Less! Why do we need the clone node PR for adding unit tests? Can we add a unit test without the SPMD linking?

Regarding the general questions:
1 - Could we add unit tests to make sure that we check transformation behavior?
Yes, but I'd like to do it separately vs this PR as this PR is already dependent on another PR (the clone node PR). That's in part why fusion is not hooked in for this PR (adds the code, but not live/linked to SPMD api yet. Once the clone PR is finalized, then can do the unit tests. Have opened this issue to track: #655
2 - Could you explain what are the current limitations of the approach and what are the next steps? Sure - current limits: a - we expect the DTensor signature for comms as we reuse the existing wait_comm nodes for where fusion is implemented. Thus need to add ability to generate our own wait_comm nodes if we want to have it handle any comm calls for fusion. b - right now we assume that all calls use the same process group (and thus any call is eligible for fusion with any other call). That is not correct for all cases and so we need to add inspection of PG and then only fuse same PG calls in the future. (added tracking issue: #657) c - similarly, we assume we need an FP32 buffer but we should inspect the dtype and then enable appropriate dtype buffer. (added tracking issue: #656)

Thanks Less! Why do we need the clone node PR for adding unit tests? Can we add a unit test without the SPMD linking?

The main issue is that depending on how the clone node PR lands (i.e. it goes in or does not, and if it goes in, which PR as two ways to fix), the handling of the graph for fusion will need to adjusted, which then flows into also changing the unit tests.
So it is not "must do first" but rather a nice to do to avoid future make work to adjust for the clone situation.
Re: add unit test without the SPMD linking -
we could make a simple test using a prebuilt backwards graph and just supply that for unit testing.  That would remove the need to link SPMD, but the drawback is then we are not really testing that changes in SPMD don't break fusion, which would be the main point of the unit tests.
That's why I was thinking better to have SPMD linked in so unit testing is actually providing comprehensive tests, but we could start with a simple standalone for now.


KARAF-4809, SSH should not listen to all hosts

The default SSH server configuration will make Karaf listen to all
hosts. It is usually good practice to instead listen to localhost only
by default to avoid possible security risks (e.g. accidentally exposing
an unconfigured SSH server).

Can you please close this PR ?  Thanks.

Sure. It's closed.


[question] [1.20.2] code wise how do i make the agglomeration combine 2 agglomerations

i had a quick look through the source but I couldn't find where it would be defined that agglomerations couldn't be combined. btw sorry for asking a question about such an old version

it might be this but honestly im not that used to editing java code

The agglomeration itself doesn't really care about what's part of it as evidenced by the exploit that used to allow you to combine agglomerations. What I think you're looking for is the AgglomerateRecipe, more specifically the lines that check whether an item is a valid one to agglomerate.

ok thank you, i'll check it out and try to make it work when i get home

ik im a bit late but when i try to compile the mod it throws an error


Textbox "Account and projectId can't be specified together"

ISSUE TYPE

Bug Report

COMPONENT NAME

UI

CLOUDSTACK VERSION

4.11

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

When I view the "Networks" view after selecting a project in the web-UI a textbox with the message "Account and projectId can't be specified together" has to be confirmed.
STEPS TO REPRODUCE

Log in to the web-UI.
Select a project.
Select the "Network" view

EXPECTED RESULTS

No textbox. ;)

ACTUAL RESULTS

A textbox with the message "Account and projectId can't be specified together" has to be confirmed.

A screenshot of the textbox:

FYI - we had a similar fix for projects view - https://github.com/apache/cloudstack/pull/2464 /cc @DaanHoogland @PaulAngus

Checked, fixed in https://github.com/apache/cloudstack/pull/2464 @mdesaive you may test the fix using diff from the PR (https://github.com/apache/cloudstack/pull/2464/files)


add role session name to sts call

This is apparently required and will not default. Set a default to exchange id + UUID for easier log tracing.

This change is


fix typos

@rex4539 Thanks for the corrections! I'll double check with the team on how we will merge the PR.

Rebased and fixed conflict.

Withdrawn due to no interest.


Clean up ExtractMetadata

This merges into #27, review that first.
I went down the rabbit-hole and cleaned up ExtractMetadata.
PLEASE CHECK THIS VERY CAREFULLY!

The slug is replaced by unique_filestem. It's a much more sensible name.  We don't need to slugify anything any more.
Methods in ExtractMetadata are laid out more sensibly.

https://github.com/neuralaudio/hear-preprocess/pull/30


Alt+Up/Down in replace box in editor find widget triggers move lines actions

From @eamodio here
In replace box of editor find widget, alt+up/down should not trigger editor.action.moveLinesUpAction or editor.action.moveLinesDownAction commands

Same problem with the commit message input box.

Same problem in the extensions view as well.

@sbatten custom menu bar seems to fix this, any idea why?

@JacksonKearl I thought it might have to do with the ModifierKeyEmitter in MenubarPart.ts but commenting that out didn't change the behavior

This seems to be somehow related to menus: It affects actions which have menu bar items (move/copy lines up/down), doesn't affect lines which do not (Delete lines).
Strangely, globally changing the each id from 'editor.action.moveLinesUpAction' to ''editor.action.moveLinesUpAction2' (or similar) will fix the issue

No longer reproducible.


vectorized support assert num rows operator

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 36.08 seconds
load time: 487 seconds
storage size:<PHONE_NUMBER>3 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221208060022_clickbench_pr_59936.html


Update Scaled JTC to current version of ros2_controllers

Recent updates in the JTC conflicts with the current version of the scaled JTC. Update the derived update funciton of the scaled JTC

Addressed in https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver/pull/133


WL-3054: Mouse-over site URL in My Active Sites list

The problem is that when the hover-over text for a site in My Sites is being processed, which is the site url, the url is escaped which replaces the colons with %3As amongst other things. This change is to replace them back.

Is it possible todo this in a more generic way which we can feedback to Sakai?

yup
--
Nick Wilson
Senior Software Developer / Project Lead
Technology Enhanced Learning, Academic IT
IT Services, University of Oxford
13 Banbury Road, OX2 6NN
Tel: 01865 613716

From: Matthew Buckett<EMAIL_ADDRESS>Sent: 05 October 2016 10:35 AM
To: ox-it/sakai
Cc: Nick Wilson; Author
Subject: Re: [ox-it/sakai] WL-3054: Mouse-over site URL in My Active Sites list (#234)
Is it possible todo this in a more generic way which we can feedback to Sakai?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/ox-it/sakai/pull/234#issuecomment-251627983, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHHLkU32MroQrcB_81klQgv-12EHFrYMks5qw291gaJpZM4KN0o4.

Superceded by WL-4614