custom-marker-anchor-&-draggable

Add anchor to custom marker to fix position issue with InfoWindow and the marker itself when the image is similar to google marker.
Add draggable action and event to custom marker.
Refferer to issue https://github.com/allenhwkim/angularjs-google-maps/issues/557
Refferer to issue https://github.com/allenhwkim/angularjs-google-maps/issues/531

Thanks for this fix.
I also want to have

a testapp page e.g. testapp/custom-marker-with-info-window.html

I also prefer keep one parameter only for the initialization for CustomMarker if possible. For example

map: map instance is always available by getMap method. Like a Marker, a CustomMarker should b e able to be instantiated without a map.

anchor: this should be this.position it self. A Marker does not have anchor, so this should not have either.

From this line, I see we are passing map and anchor to instantiate a custom marker.
https://github.com/danielechizen/angularjs-google-maps/blob/patch-1/directives/custom-marker.js#L194le.
Personally, I think we should not pass any but options if possible

Ok! I did know that map instance is available through getMap, i will change that.
About anchor, a Marker can have an anchor. Its the landing point of the icon, as u can see here:
https://developers.google.com/maps/documentation/javascript/examples/icon-complex

so how to set a custom offset for windows and/or anchors?
because in my case i would prefer a +10 pixel to center infowin arrow on  row
https://github.com/allenhwkim/angularjs-google-maps/blob/master/directives/custom-marker.js#L76


Add ranking to projects

When projects are requested with beta_approved or launch_approved they
will be sorted by default by their assigned ranking.
Closes #1161

LGTM - are you going to set some defaults?

Not in code. I was going to go through and at least order the launched panoptes projects above the rest of them.

Ah the failures seem to be due to rails' awesome idea to convert params to strings in controller tests :+1:

This looks good to go.


Your code is great. It's like the emperor's new clothes.

So what's the point of your writing this line？

The code and models are released, enjoy! Sorry for unexpectedly delayed release due to company's review process.


vcoco json file and visualizationprogram

hello，i wonder if you could upload the vcoco json file and visualization program file. I'd apprecicate it if you could.

About the annotation files of verb-coco can be seen in #16 and #7. The visualization scripts are not formatted now, and could you provide me an E-mail address where I sent the code?

About the annotation files of verb-coco can be seen in #16 and #7. The visualization scripts are not formatted now, and could you provide me an E-mail address where I sent the code?

<EMAIL_ADDRESS>      Thank you very much.

About the annotation files of verb-coco can be seen in #16 and #7. The visualization scripts are not formatted now, and could you provide me an E-mail address where I sent the code?

Hi, I also want the scripts<EMAIL_ADDRESS>Thanks a lot!

All above are responded through E-mail.

Hey @YueLiao, Can you please provide me also your video demo script ?

Dear Liao @YueLiao
I also need the above scrips (e.g., visualization scripts, video demo script)
My E-mail address is<EMAIL_ADDRESS>Thanx a lot lot lot.

Dear Liao @YueLiao
Could you please share me with the visualization scripts for vcoco through the email<EMAIL_ADDRESS>Thanks a lot.

Dear Liao @YueLiao
I also need the above scrips (e.g., visualization scripts, video demo script)
My E-mail address is<EMAIL_ADDRESS>Thanx a lot lot lot.

Dear Liao @YueLiao
I also need the above scrips (e.g., visualization scripts, video demo script)
My E-mail address is<EMAIL_ADDRESS>Thx a lot.

Dear Liao @YueLiao
I also need the above scrips (e.g., visualization scripts, video demo script)
My E-mail address is<EMAIL_ADDRESS>Thanx a lot lot lot.

Dear Liao @YueLiao I also need the above scrips (e.g., visualization scripts, video demo script) My E-mail address is<EMAIL_ADDRESS>Thx a lot.

In this issue


[Feature] Ability to store vector index to pinecone or local storage

Now all vector index only temporary. Can we make an options to save it to our local storage or another vector index like pinecone ?

Was thinking of making an extension to add in chromadb local storage for the vector store, any thoughts? @quangnhut123


Invalid number of arguments to _on_open and _on_message callbacks

When trying to implement a simple script following the given example the following errors are shown:
error from callback <bound method Connection._on_open of <Connection(PysherEventLoop, started daemon<PHONE_NUMBER>98208)>>: _on_open() takes 1 positional argument but 2 were given
error from callback <bound method Connection._on_message of <Connection(PysherEventLoop, started daemon<PHONE_NUMBER>98208)>>: _on_message() takes 2 positional arguments but 3 were given
Connection: Connection closed

When checking out the documentation for websocket-client, the implementation given in its example does not seem to match the implementation in connection.py.
Pysher version: 1.0.1 (installed with pip)
websocket-client version: 0.52.0
Python version: 3.7.0
OS: Mac OS X (Mojave)

It looks like this has regressed. 1.0.1 works, but 1.0.4 gives errors:
2018-12-01 18:11:37 ERROR (PysherEventLoop) [websocket] error from callback <bound method Connection._on_open of <Connection(PysherEventLoop, started daemon<PHONE_NUMBER>62432)>>: _on_open() takes 1 positional argument but 2 were given
2018-12-01 18:11:37 ERROR (PysherEventLoop) [websocket] error from callback <bound method Connection._on_message of <Connection(PysherEventLoop, started daemon<PHONE_NUMBER>62432)>>: _on_message() takes 2 positional arguments but 3 were given

Is your websocket - client up to date,
@craigjmidwinter?
I'm migrating to another websocket library, but progress is achingly slow, due to very little available time on my end.


Add initial version of iscsictl.py helper.

iscsictl.py is a helper for QA to setup iSCSI targets and initiators.

Do not make mkfs
Make the initiator autologin when reboot
Better autoclean of temporal keys
Helper for configurations updates
Test with multiple initiators

r? @aspers @toabctl @jsuchome

Rebased

It would be nice if it wouldn't support only loop devices

initiator should be just able to discover target by IP, and not use predefined names

use also hostname, not just IP to identify hosts

Allows loop devices and block devices
Initiator can discover targets by the IP and the IQN ID (optional)
Address can be IPs and hostnames

Tested in different setups (local mkcloud, remote HA mkcloud and real hardware)
Can we merge this version? If the script needs improvement, we can do it later.

I agree that further improvements might be added later.

r? @aspiers @toabctl

Add some documentation

+1

merged


Incorrect title value in Action.OpenUrl.Sentiment.json

Platform

Shared model

Version of SDK
1.2
Issue
Text in sample appears to have a typo: "Action.Pawsitive", and the meaning isn't clear.

I opened this issue with my personal account for demo purposes


POC demonstrating how to use guest attributes to improve notebook VM startup output.

Note intended as-is for commit. Intended as POC.
A good implementation would probably include getting attributes through the GCP API (through a wrapper in the
terra-cloud-resource-lib).
Would anticipate having command-line flags for people to choose whether they want to fire and forget or wait for completion.

Example output: SUCCESS
$ terra resource create gcp-notebook --name=test1
Successfully added controlled GCP Notebook instance.
Name:         test1
Description:
Type:         AI_NOTEBOOK
Stewardship:  CONTROLLED
Cloning:      COPY_RESOURCE
Access scope: PRIVATE_ACCESS
Managed by:   USER
Private user<EMAIL_ADDRESS>Properties:   class Properties {
    []
}
GCP project id:                terra-hidden-7350
Instance id:   test1
Location: us-central1-a
Instance name: projects/terra-hidden-7350/locations/us-central1-a/instances/test1
State:         PROVISIONING
Metadata:
   warmup-libraries: matplotlib.pyplot
   proxy-mode: service_account
   terra-workspace-id: test-dev-workspace
   shutdown-script: /opt/deeplearning/bin/shutdown_script.sh
   post-startup-script: https://raw.githubusercontent.com/DataBiosphere/terra-workspace-manager/main/service/src/main/java/bio/terra/workspace/service/resource/controlled/cloud/gcp/ainotebook/post-startup.sh
   notebooks-api-version: v1
   terra-cli-server: verily-devel
   disable-swap-binaries: true
   enable-guest-attributes: TRUE
   serial-port-logging-enable: true
   notebooks-api: PROD
Proxy URL:     (undefined)
Create time:   2023-03-27T17:41:52.825217851Z
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.

STARTED..........
COMPLETE

Example output: FAILURE
$ terra resource create gcp-notebook --name=test2 --post-startup-script gs://test-bucket-terra-dev/post-startup.sh
Successfully added controlled GCP Notebook instance.
Name:         test2
Description:
Type:         AI_NOTEBOOK
Stewardship:  CONTROLLED
Cloning:      COPY_RESOURCE
Access scope: PRIVATE_ACCESS
Managed by:   USER
Private user<EMAIL_ADDRESS>Properties:   class Properties {
    []
}
GCP project id:                terra-hidden-7350
Instance id:   test2
Location: us-central1-a
Instance name: projects/terra-hidden-7350/locations/us-central1-a/instances/test2
State:         PROVISIONING
Metadata:
   terra-workspace-id: test-dev-workspace
   post-startup-script: gs://test-bucket-terra-dev/post-startup.sh
   warmup-libraries: matplotlib.pyplot
   notebooks-api-version: v1
   proxy-mode: service_account
   shutdown-script: /opt/deeplearning/bin/shutdown_script.sh
   disable-swap-binaries: true
   notebooks-api: PROD
   enable-guest-attributes: TRUE
   serial-port-logging-enable: true
   terra-cli-server: verily-devel
Proxy URL:     (undefined)
Create time:   2023-03-27T19:57:05.818802611Z
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.
ERROR getting notebook startup status: 1
The post-startup script has not started.

STARTED......
ERROR
Error on line 1, command "exit". See /home/jupyter/.terra/post-startup-output.txt for more information.


raftstore: update size after leader transfer

What have you changed? (mandatory)
Assume that a region is on storeA, storeB and storeC, and leader is on storeA with a calculated approximate size based on current stats. Then leader is transferred to storeB and approximate size of region is changed a lot. Once leader is transferred back to storeA and there is no write, namely, split-checker is not invoked. At this point, pd will get a stale approximate size of the region from storeA.
To be noted, it may cause performance issue when transferring leaders dramatically
What are the type of the changes? (mandatory)

Bug fix (non-breaking change which fixes an issue)

How has this PR been tested? (mandatory)
unit-test
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No
Does this PR affect tidb-ansible update? (mandatory)
No

Closing since there is no activity for some time.
@Connor1996 please open a new PR if you get back to this code


[[FIX]] Dont crash when testing x == keyword if eqnull is on

If eqnull was on jshint previously crashed if the right hand side of an
assignment was not an expression.
Fixes #2587

Squashed and merged to master at commit 6afd373e9b3f9e22076122bc7d7e7a16f7b368dd. Thank you, Luke!


    fix: mention that Node.js 13/15 support is dropped (fixes #9113)

New updates on head repo.
https://github.com/vitejs/vite/commit/2826303bd253e20df2746f84f6a7c06cb5cf3d6b

こちら対応します🦕


After restarting IIS(OIDC Server), I receive an error as State not valid

Issue and Steps to Reproduce
After restarting IIS, I receive an error as follows when users first log in. After redirect login and try again it works.
Versions
7.19.0
Screenshots

After refresh in same page:

Expected
It should work for first login.
Actual
It is getting error after reset IIS session.

1- Our OIDC IIS Server
2- I don't have any network history only have this link and these console messages:
/auth-callback?code=RkdVAiHe-dC0CoDQkQCIvP747mXZPlhFnxuC1IxiBj8&state=5bNZgSMAwLxFAvqR&iss=XXXXX

We realized that it was related to service worker and had to turn off this mode. :/

Thank you @ozanmanav for the feedback. It is a strange bug. I cannot reproduce it.

I found the problem I think and fixed it here : https://github.com/AxaFrance/oidc-client/commit/44d15be1c4d8f5069f15ddc5351e546fc5eb7730
It took me time but it already fix the HTTP 401 on the userinfo endpoint on the first connection.

This still seems to be the case, we get an error on the first login when we reset iis on the server side. @guillaume-chervet  :/


Define WAGTAILADMIN_BASE_URL setting

(This PR is against the upgrade/wagtail branch, not the main branch.)
As of Wagtail 3.0, we need to define a Django setting named WAGTAILADMIN_BASE_URL to tell Wagtail the base URL of the running website (example: https://www.consumerfinance.gov).
Without defining this, Django reports this warning when it runs:

?: (wagtailadmin.W003) The WAGTAILADMIN_BASE_URL setting is not defined HINT: This should be the base URL used to access the Wagtail admin site. Without this, URLs in notification emails will not display correctly.

This commit sets a default of "http://localhost:8000" for this value, or uses the environment variable WAGTAILADMIN_BASE_URL if it is defined.
Ideally we would be able to put "http://localhost:8000" in our settings.local and rely on
os.environ["WAGTAILADMIN_BASE_URL"] in our settings.production. Due to uncertainty around use of cf.gov production settings in Docker-based environments, though, we can't guarantee that environment variable will be set.
Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code follows the standards laid out in the CFPB development guidelines

@willbarton I've added a second commit here to fix some unit tests that surprisingly started failing with this change. We had some custom logic to create a simulated request for cases where we want to send password reset emails without having a request available; but the request is no longer needed for password reset emails because the Wagtail email template uses this new WAGTAILADMIN_BASE_URL setting.


Fix call_handler of the IdleTime class to send the IdleTime instance as parameter.

Fix call_handler of the IdleTime class to send the IdleTime instance as parameter.
This is supposed to be passed as convenience for plugins and user scripts!

Fixed in dev.


Display company names in the home page preview tabs dynamically

At present, the company names that are displayed in the home page in the Wishlist, In Process, Applied and Offers cards are hardcoded. The names in the card need to be updated as the company names get updated by the user in the dynamic tables.

Implemented and resolved in #6.


Duckduckgo wait_for_results selector doesn't work in case of no results

Hello
It seems like the selector you are currently using to scrape the Duckduckgo Result Page is not properly working in the case that the search doesn't produce any results:
[i] duckduckgo scrapes keyword ... on page 1
Problem with scraping ... in search engine duckduckgo: TimeoutError: waiting for selector ".result__body" failed: timeout 10000ms exceeded

I think the issue here is the selector you are using:
async wait_for_results() {
        await this.page.waitForSelector('.result__body', { timeout: this.STANDARD_TIMEOUT });
    }

If the search produces no results, the Duckduckgo Results Page doesn't have a div with the class .result__body.
As a fix I suggest using one of the following selectors instead (I have not tested it though, but they are present in both cases):
#links
.serp__results

have you got a solution for this?


Obsolete FixtureType property of AutoDataAttribute

The FixtureType property was introduced at times when we had constructor taking the fixture Type. Now that constructor is totally deprecated, so the FixtureType property should be deprecated as well - as it's purpose is very unclear.

Done


Show full help when the user leaves off all arguments

When running a command-line tool, if the user doesn't specify any inputs at all it's a good bet that they aren't familiar with the command. If there are required arguments/options/flags, we should show the error message with the full help screen instead of just the abbreviated usage.
For example, if you run the example repeat command with no inputs, you get this:
$ swift run repeat
Error: Missing expected argument '<phrase>'
Usage: repeat [--count <count>] [--include-counter] <phrase>

Instead, it would be great to show this:
$ swift run repeat
Error: Missing expected argument '<phrase>'

USAGE: repeat [--count <count>] [--include-counter] <phrase>

ARGUMENTS:
  <phrase>                The phrase to repeat.

OPTIONS:
  --count <count>         The number of times to repeat 'phrase'.
  --include-counter       Include a counter with each repetition.
  -h, --help              Show help information.

Looks like #135  addresses this issue.

I like this suggestion @natecook1000


Error: No matching state found in storage - at OidcClient.readSigninResponseState

Hi@all
When I refresh the page, I get logged out.
Reproduce:

Click login button
Login via keycloak/openid
Redirect back (address is: https://helpme.test/de/admin/organizations?state=311b124c928e4cd3a5b282fd16dd4475&session_state=2793988e-f78f-4d42-8164-61ab7697af9e&code=4bdf7c6d-7d29-4d8c-95a9-0913b62591a7.2793988e-f78f-4d42-8164-61ab7697af9e.e1f6f519-030c-4204-beab-f4dfe064baa7)
Refresh page (Command+R)
Now i am logout and have follow error

Error:
Error: No matching state found in storage
    at OidcClient.readSigninResponseState (oidc-client-ts.js:1443:1)
    at async UserManager.signinCallback (oidc-client-ts.js:2312:21)
    at async react-oidc-context.js:154:1

oidc-client-ts.js:1443:1:
  async readSigninResponseState(url, removeState = false) {
    const logger2 = this._logger.create("readSigninResponseState");
    const response = new SigninResponse(UrlUtils.readParams(url, this.settings.response_mode));
    if (!response.state) {
      logger2.throw(new Error("No state in response"));
      throw null;
    }
    const storedStateString = await this.settings.stateStore[removeState ? "remove" : "get"](response.state);
    if (!storedStateString) {
=>>>>>>>>>>>>>>>>>>>>>>>      logger2.throw(new Error("No matching state found in storage"));
      throw null;
    }
    const state = SigninState.fromStorageString(storedStateString);

Does anyone have any idea what went wrong?

The Authorization Code Grant with PKCE needs a temporary local state to function.
When creating the sign-in request the oidc-client-ts is storing that state here https://github.com/authts/oidc-client-ts/blob/809da48c91b44df27454d8c0a6a5c04f4e748339/src/OidcClient.ts#L135
When the callback is coming back it needs to match the incoming request against the original request, thus searching for the previous stored state...
In your case somehow this does not work. Best way is to add logging in oidc-client-ts. The state is stored by default in localSession...


Remove Credential

As a holder I want to remove credentials from my wallet so that I can keep my wallet organized and clear of unnecessary credentials
Wireframes:
https://xd.adobe.com/view/5edd5ca1-8978-4b3f-bf87-9ef21548b877-0b8e/
GIVEN the holder is in a credential detail screen
WHEN the holder selects "Remove from wallet"
THEN the holder is taken to an intermediary screen with more details of credential removal
AND a "Remove credential from wallet" button is available.
GIVEN the holder is in the intermediary screen with more details of credential removal
WHEN the holder selects "Remove credential from wallet"
THEN the holder is taken to the Credential List screen
AND a success temporary toast notifications appears

It will need changes to the react hooks library which might slow the release

When Wallet/AFJ provides a list of credentials eligibly to fulfill a presentation request it is currently including deleted credentials.

@cvarjao I've already added draft PR in react-hooks (https://github.com/hyperledger/aries-framework-javascript-ext/pull/113) but it needs to be released in core first so the react-hooks dependency can be updated.

This is manually tested but needs Test Automation for regression testing.


Add unit tests for the centering function

This PR adds unit tests for the centering function as to solve the issue discussed in issue #34 .
It adds following functions,

abel.tools.get_quadrants :  a helper function to get the 4 quadrants of the image, as defined by @stggh implementation of Hassen&Law. The code is a bit different, but the result should be the same.
abel.benchmark.is_symmetric: checks that an image is symmetric, with respect to its center (both for odd and even images). The symmetry center is defined in the discussion of the issue #34.
abel.tests.test_benchmark.test_symmetry_function: some constancy tests for is_symmetric
abel.tests.test_tools.test_centering_function_shape: check that center_image preserves shape (for odd and even images)
abel.tests.test_tools.test_centering_function: check that center_image centers the image correctly for both odd and even images.

With the current code base, 4 tests for the centering function do not pass (both in test_centering_function_shape and in test_centering_function), as can be seen in the Travis CI logs. This PR should be merged before PR #37, and those 4 failing tests should then be fixed by PR #37.

abel.tools.get_quadrants is a neat idea and your code is clever to include the an additional 1/2 pixel for odd size images. The extra 1/2 pixel will require a correction to the speed profile. (*)
Feature request:  add option   ,reorientate=True)
to deliver the quadrants with the correct orientation for use with iabel_hansenlaw_transform()
if reorientate:
    Q0 = np.fliplr(Q0)
    Q2 = np.flipud(Q2)
    Q3 = np.fliplr(np.flipud(Q3))

Also, is the following too obscure?
m_c = m%2 + m//2
n_c = n%2 + n//2

(*) The Hansen Law algorithm does not require a uniform sampling grid (last sentence on page 513 of article). I have not thought about the consequences. It is a matter of keeping track of the (0,Rmax) grid, or (0,vmax) speed grid, associated with the pixel image.

[Off topic - ignore if I should google the answer]
Git - how do I merge @rth's tools.py with into my own fork without causing chaos in the final push merge of my fork into the master?  i.e. tools should be merged from @rth's fork, and only the hansenlaw stuff from my own.

@stggh I updated the code with your suggestions.
As far as I understand, to merge this into you fork you have two options:

To use it right now, I think you can just merge this branch into yours. I believe you can do a PR from my fork to your on github.

If you wait a bit until this is merged into PyAbel master, a better solution, I think, would be to rebase your fork on the PyAbel master as to keep a clean git history without too many  merges. In our case, that would be as explained in this post,
Add the remote, call it "upstream":
git remote add upstream git@github.com:PyAbel/PyAbel.git
Fetch all the branches of that remote into remote-tracking branches,
such as upstream/master:
git fetch upstream
Make sure that you're on your master branch:
git checkout master
Rewrite your master branch so that any commits of yours that
aren't already in upstream/master are replayed on top of that
other branch:
git rebase upstream/master

more information about this can be found at this link. I think for us it would be necessary to rebase anyway at some point before merging to master, as there is more and more parallel branches that sometimes change the same files.

I think that we can go ahead and merge this. In American English, reorientate should be reorient, but we can leave reorientate in honor of @stggh's Australian nationality. :) I doubt that anybody will be confused.


Release 1.18.0

The tracking issue for release Jaeger 1.18.0
Release commit history: https://github.com/jaegertracing/jaeger/compare/v1.17.1...master
This release should include jaeger-ui 1.9.0 - the release has to be done.
@jaegertracing/helm-charts-maintainers please list any outstanding issues that should be included in jaeger or jaeger-ui for this release.

If there won't be any concerns I would like to get the release out before Wednesday 13.5.

I think you meant to cc jaeger maintainers not the charts maintainers @pavolloffay ?

yes  cc @jaegertracing/jaeger-maintainers

I think we should include #2242, because without it PR #2090 results in confusing behavior.


Some suggestions

An idea for a new flower:

rain flower: generates mana while it is raining

It would also be nice to see a new mana pool that is 2x the size of a normal mana pool.

The flower is a cool idea. I don't think I am going to create a bigger mana pool but Botanical Machinery has a mana battery that can store 10 times as much as a mana pool.


Pin myst-nb

I'm starting to see our docs build failing, and I think the reason is the new myst-nb release.
HoloViews:

Panel:

I ran with the upper pin on Holoviews docs and got it to pass.
https://github.com/holoviz/holoviews/actions/runs/6954932260

Will merge but we should get a myst-nb 1.0 compatible release out asap.


DOI, change logs, and zenodo for github repo

I've seen zenodo used as in here
https://zenodo.org/records/6099888
the doi icon at the top of https://github.com/compSPI/simSPI?tab=readme-ov-file
See the changelog: https://github.com/compSPI/simSPI/commits/v0.0.2
This project has a DOI through open science foundation, but that is more for the dataset / project.
https://osf.io/8h6fz/
There will be a seperate DOI(s) for a paper(s), which can be attached to the OSF project as a citation(s).
How does zenodo work with PyPI integration?
@DavidHerreros , what do you suggest?

I've seen zenodo used as in here
https://zenodo.org/records/6099888 the doi icon at the top of https://github.com/compSPI/simSPI?tab=readme-ov-file

Here do you mean adding a badge with the Zenodo DOI?

See the changelog: https://github.com/compSPI/simSPI/commits/v0.0.2
This project has a DOI through open science foundation, but that is more for the dataset / project. https://osf.io/8h6fz/
There will be a seperate DOI(s) for a paper(s), which can be attached to the OSF project as a citation(s).
How does zenodo work with PyPI integration?

The GitHub actions in charge of pushing everything to pypi on merging into main will also copy the README contents into the pypi package webpage. If they DOI is added to the README, it should be automatically reflected on pypi when it is released, is this what you mean?

@DavidHerreros , what do you suggest?

I think it makes sense having a DOI for this repo specifically, although I am not very familiar on how Zenodo works when the repo is updated. The ChangeLog in the Zenodo example is a nice idea as well. There could be a CHANGES.txt in the repo that can be updated everytime a release is done to reflect the new functionalities. Other option is to rely on the PRs descriptions and titles to generate an automatic ChangeLog on a new release, although I would only gow for this one if the PRs are informative enough.

Let's look into automatic changelog from the PR titles. And where to show this info (PyPI, Zenodo, etc).

@DavidHerreros publishing to PyPI is not a big priority. The change logs and doi are more interesting


window(s)IsAnyHovered ?

Hello,
there is a difference between docu and source between windowIsAnyHovered and windowsIsAnyHovered.
I think it should be windowIsAnyHovered (without 's') for both.
Franc

Thanks for the issue, I believe it should be fixed now.


Use space for scope separator

Hi Neil
I've been using the library, but found in the documentation that the scope separator needs to be a space rather than the default comma.
regards
Steve

Thanks for your pull request. You can specify the scope separator in the $options array, see the repo's readme.

Hi Neil
We did try that but found it didn't work.  It seems better to just set it in the function rather than have the user have to remember to set it when they call anyway.  That seems to be how other clients have been setup.
Cheers
Steve

Oh ok, can you send me a link to an example? For some reason, I thought the recommended way of doing this was to pass it in to the options.

There's a few doing it this way in the list here.  https://github.com/thephpleague/oauth2-client/blob/master/docs/providers/thirdparty.md
For example Amazon
https://github.com/michaelKaefer/oauth2-amazon/blob/master/src/Provider/Amazon.php

Thanks for the pull request, and your comms whilst I was reviewing


libcontainer/runc v1.0.0-rc91 introduces breaking changes

/kind bug
Using this issue to track a problem introduced by runc v1.0.0-rc91 in various areas.
c/common v0.15.2 now depends on rc91, which causes the issue.
Root cause:
https://github.com/opencontainers/runc/blob/819fcc687efb6e99d980a257f1dc8d92d02ba5bd/libcontainer/configs/device.go#L37
Device permissions are now a custom type
This commit
goochjj@2b64224
identifies the lines that need to change to support it.
Short term - fix + reversion c/common with rc90 dependency, and use this to discuss game plans going forward.

Further discussion from #6882

@rhatdan I see you doing vendoring things in Buildah - do you have another plan in mind?

Yes we need to get this fixed in Buildah and then vendor the whole thing into podman.  Problem is Buildah CI system is in a sad shape right now.

OK want to weigh in on the plan then? :)

Change c/common to require runc rc90 instead of rc91 - which fixes libpod builds and allows pids-limit to proceed forward
Leave c/common requiring rc91, and force-replace with rc90 on libpod - which fixes libpod builds and allows pids-limit to proceed forward, but allows projects that don't issue a replace line to fix their runc-caused build issues... Perhaps introduce a second PR to undo the sticky version and fix the build
Assume that runc-rc91 is the new hotness
a) buildah needs to depend on c/common 0.15.2, or at least runc rc91 explicitly
b) buildah src needs 2 lines patched as indicated in my referenced commit
c) libpod needs 2 lines patched as indicated in my referenced commit
d) pids-limit change is now dependent on runc-rc91 compat.

Prob with 1 is at sometime in the future we're going to need to undo that too...

I think option 2 is probably the best.
#6897

@goochjj Where are we on this issue now?

All the vendoring was done so this is resolved AFAIK.


Different Versions of Node.js Required?

I suspect these two references should be consistent and both say Node.js version 8 or better?
Or, maybe better, leave out the Node.js version on this page, so that info does not need to be maintained?

After the test run has been created, ensure that the following software is installed on the computer that will submit the tests:
Node.js 6.3
App Center CLI
Instructions for installing the App Center CLI maybe be found in the README.md on GitHub.

But in the linked reference (https://github.com/Microsoft/AppCenter-CLI#installation)

Prerequisites
App Center CLI requires Node.js version 8 or better.

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

ID: adb0ff0a-1fb7-9362-34e4-50879d07f0f2
Version Independent ID: 469a4e00-53a3-b903-eb0d-1d307b4b4166
Content: Preparing Xamarin.UITests for Upload - Visual Studio App Center
Content Source: docs/test-cloud/preparing-for-upload/uitest.md
Service: vs-appcenter
GitHub Login: @glennwester
Microsoft Alias: glwest

@glennwester we just updated the one and haven't fixed the other one yet.

Assigning @amchew

Thanks @GlennWilson for notifying on the discrepancy - I've made a PR to fix this here.

Fix applied, closing issue


[Feature request]  create-react-lib for react component library projects

Say you want to publish a react component to npm, would be nice to have a scaffold that would get rid of most of the boilerplate, yet allow you to take advantage of create-react-app features.

Yes! I just started a discussion about this: https://github.com/facebookincubator/create-react-app/issues/1492

There's also been a few earlier discussions too.
Closing as a duplicate.


Problem with import order differs between Android Studio and KtLint

Formatting imports in Android Studio with SessionsViewModel causes this problem.
I believe it is probably a KtLint or Spotless configuration issue.

Could I take this issue? I think we can fix the issue by setting a EditorConfig property.
https://pinterest.github.io/ktlint/rules/configuration-ktlint/#import-layouts

This is a very annoying issue. If you fix this we are happy 🙏


Expand Not Working in Solution Explorer

Description
I click on a folder in the solution explorer but the files never show
To Reproduce
Steps to reproduce the behavior:

Load .Net Core solution in VS Code and wait for solution to render
Click folder under solution and wait for it to expand

Expected behavior
I expect the caret on the left of the folder to point down,
I expect the "loading indicators" or spinner to display while the file list loads
I expect the spinners to stop and the files to appear
The loading indicators do not load and the files do not appear for certain projects
Screenshot Enclosed
It shows the MIG.Preferences.Infrastructure project with the downward caret icon which I clicked on but the files (shown above in file explorer) never show up
Environment

OS: Windows 10 Pro
Extension Version: 0.7.4
vscode version: 1.74.0

Additional Info
This does not happen for other developers with same versions as far as I can tell.  It happens for me in different solutions though - some .net core 3.0 and some in .Net 6.0

I've added a PR that might fix this: https://github.com/fernandoescolar/vscode-solution-explorer/pull/240


Feature Request: Add ability to set to-do due date from template variable

It would be cool if there was a template_due_date variable that allowed setting of the note's due date from the template

Actually, I'm not aware of due_date in notes. Are you talking about the alarm feature for todos?

yes, the alarm feature


[ISSUE #292] Add support of transactional message feature

Please do not create a Pull Request without creating an issue first.
What is the purpose of the change
In order to implement  eventual consistency in distributed system, we define a new type of message named transactional message, it can be thought of as a two-phase commit message implementation to ensure eventual consistency in distributed system. Transactional message ensures that the execution of local transaction and the sending of message can be performed atomically.
Brief changelog
In our implementation, we made full use of the mechanism of rocketMQ itself to avoid external dependencies, and we defined a pair of message: named half message and commit/rollback message.  Half message means prepared message, which are not visible to consumers，and it will be sent before local transaction is executed. After the local transaction ends，producer will send a commit or rollback message to broker based on local transaction execution result
Verifying this change
This is a trivial change.
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Redo it ? @duhengforever I will close the PR and hope to see a squashed PR.


Update package version

@label-u/components 2.1.0 (2023-08-02)
Bug Fixes

components: add shortcut tooltip for 1-9 (2e6a76c)
components: annotation attribute tab visibility (c020c26)
components: fix redo \ undo \ switch shortcuts (4f0ff92)
components: fix redo \ undo \ switch shortcuts (ba05d15)
components: fix redo undo history stack (da1b311)
components: fix styles (ac1ded9)
components: hide annotation result tab if there is no graphic tool (a272a8c)
components: support redo undo shortcut for mac (e348684)
components: update attribute tabs style (24b9a26)

Features

components: add 1-9 shortcuts to set attribute (5014ee0)
components: support shortcut for rotation (bd79435)
components: update hotkeys tooltip (619c7fb)

Dependencies

@label-u/annotation: upgraded to 2.1.0
@label-u/utils: upgraded to 1.0.2

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


Global planner doesn't allow to fly below 2 meters

Describe the bug
Whenever I set a clicked goal altitude below 2 meters, the global planner won't fly there and says "goal position is occupied"
To Reproduce
Steps to reproduce the behavior:

Drone is in Offboard mode

Setting goal altitude to 1.8m and min_altitude to 0m in Dynamic Reconfigure, see screenshot

Click goal in Rviz

See error and log file below
[ INFO] [1589013752.459053907, 34.960000000]: OctoMap memory usage: 0.046 MB
[ INFO] [1589013752.459185862, 34.960000000]: Planning a path from (5,-11,3) to (5,-11,3)
[ INFO] [1589013752.459213565, 34.960000000]: curr_pos_: 5.51,-10.69,3.57	 s: 5.50,-10.50,3.50
Search              iter_time overest   num_iter  path_cost
NodeWithoutSmooth   inf       2         0         0         (cost: 0.00, dist: 0.00, risk: 0.00, smooth: 0.00)
SpeedNode           inf       1.25      0         0         (cost: 0.00, dist: 0.00, risk: 0.00, smooth: 0.00)
SpeedNode           -nan      1.06      0         0         (cost: 0.00, dist: 0.00, risk: 0.00, smooth: 0.00)
Total time: 0.77 ms
[ INFO] [1589013753.137902542, 35.580000000]: Setting goal: Frame:local_origin, Position(0.530, -18.315, 0.000), Orientation(0.000, 0.000, -0.447, 0.895) = Angle: -0.927
[ INFO] [1589013753.217684820, 35.656000000]: ========== Set goal : (0,-19,1) ==========
[ INFO] [1589013753.543816882, 35.964000000]: OctoMap memory usage: 0.046 MB
[ INFO] [1589013753.543924621, 35.964000000]: Goal position is occupied
[ INFO] [1589013753.543989295, 35.964000000]: Failed to find a path
Total time: 0.43 ms
[ INFO] [1589013754.571964586, 36.960000000]:   STOP
[ INFO] [1589013754.572157098, 36.960000000]: OctoMap memory usage: 0.046 MB
[ INFO] [1589013754.572251670, 36.960000000]: Planning a path from (5,-11,3) to (5,-11,3)
[ INFO] [1589013754.572324511, 36.960000000]: curr_pos_: 5.53,-10.64,3.57	 s: 5.50,-10.50,3.50
Search              iter_time overest   num_iter  path_cost
NodeWithoutSmooth   inf       2         0         0         (cost: 0.00, dist: 0.00, risk: 0.00, smooth: 0.00)
SpeedNode           inf       1.25      0         0         (cost: 0.00, dist: 0.00, risk: 0.00, smooth: 0.00)
SpeedNode           inf       1.06      0         0         (cost: 0.00, dist: 0.00, risk: 0.00, smooth: 0.00)
Total time: 1.02 ms

Log Files and Screenshots
Always provide a link to the flight log file:
https://logs.px4.io/plot_app?log=86bfb4f7-a721-456d-87d9-12341c47af7a
Additional context
Is this the expected behaviour?
If yes, why is the local planner able to fly below 2m but the global is not?
If no, any ideas what could be the problem?
I also wonder, why the "min_altitude" setting does not have any effect on the planner.
If I set it to 5m, I still can fly below, e.g. to 3m. And setting it to 0m won't make it possible to fly below 2 m.

@Sebboo97 Yes, this is the expected behavior, the map is trying to avoid taking the ground as part of the obstacle map.

@Jaeyoung-Lim Thank you for your answer!
I have now changed max_cell_risk to >1,1 in the code and with that I'm able to fly below 2m without any problems.
Is there a reason why max_cell_risk is limited to 1 by default in the rqt_reconfigure tool?
In other words, may it cause a problem to leave it at 1,1?


Too much memory used with 32 processes/node

Create celeste_1.sl containing:
#!/bin/bash -l

#SBATCH --partition=debug
#SBATCH --nodes=1
#SBATCH --job-name=celeste
#SBATCH --time=00:30:00

export OMP_NUM_THREADS=1
export JULIA_NUM_THREADS=1
module load julia
export I_MPI_PMI_LIBRARY=/opt/slurm/default/lib/libpmi.so
export I_MPI_PIN_DOMAIN=auto
srun -n 32 julia /global/homes/k/kpamnany/.julia/v0.4/Celeste/bin/celeste.jl infer-box 200 200.5 38.1 38.16 $SCRATCH

Use your Celeste directory, of course. Run this with sbatch celeste_1.sl and the slurm-xxxxxxx.log file will contain the output (where xxxxxxx is the job ID). The job is killed due to running out of memory.

Shouldn't we use
module load julia/0.5.0-dev-2918
?
On Tue, Apr 5, 2016 at 5:02 PM, kpamnany<EMAIL_ADDRESS>wrote:

Create celeste_1.sl containing:
#!/bin/bash -l
#SBATCH --partition=debug
#SBATCH --nodes=1
#SBATCH --job-name=celeste
#SBATCH --time=00:30:00
export OMP_NUM_THREADS=1
export JULIA_NUM_THREADS=1
module load julia
export I_MPI_PMI_LIBRARY=/opt/slurm/default/lib/libpmi.so
export I_MPI_PIN_DOMAIN=auto
srun -n 32 julia /global/homes/k/kpamnany/.julia/v0.4/Celeste/bin/celeste.jl infer-box 200 200.5 38.1 38.16 $SCRATCH
Use your Celeste directory, of course. Run this with sbatch celeste_1.sl
and the slurm-xxxxxxx.log file will contain the output (where xxxxxxx is
the job ID). The job is killed due to running out of memory.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jeff-regier/Celeste.jl/issues/215

Or rather, I'm a little confused -- why are you using julia4?  Sorry if I'm
behind the curve.
On Tue, Apr 5, 2016 at 5:16 PM, Ryan Giordano<EMAIL_ADDRESS>wrote:

Shouldn't we use
module load julia/0.5.0-dev-2918
?
On Tue, Apr 5, 2016 at 5:02 PM, kpamnany<EMAIL_ADDRESS>wrote:

Create celeste_1.sl containing:
#!/bin/bash -l
#SBATCH --partition=debug
#SBATCH --nodes=1
#SBATCH --job-name=celeste
#SBATCH --time=00:30:00
export OMP_NUM_THREADS=1
export JULIA_NUM_THREADS=1
module load julia
export I_MPI_PMI_LIBRARY=/opt/slurm/default/lib/libpmi.so
export I_MPI_PIN_DOMAIN=auto
srun -n 32 julia /global/homes/k/kpamnany/.julia/v0.4/Celeste/bin/celeste.jl infer-box 200 200.5 38.1 38.16 $SCRATCH
Use your Celeste directory, of course. Run this with sbatch celeste_1.sl
and the slurm-xxxxxxx.log file will contain the output (where xxxxxxx is
the job ID). The job is killed due to running out of memory.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jeff-regier/Celeste.jl/issues/215

Also, Rollin, what was the correct way to load libcfitsio.so on Cori?  I'm
getting this error:
ERROR: LoadError: error compiling main: error compiling stage_box_nersc:
error compiling query_overlapping_fieldids: error compiling
query_overlapping_fields: error compiling call: error compiling
fits_open_file: could not load library
"/global/u2/j/jregier/.julia/v0.4/FITSIO/deps/usr/lib/libcfitsio.so"
...which is probably an artifact of my having copied it over from Jeff's
directory.  (There are no obvious simlinks that I can see, so julia might
have cached the path somewhere?)
On Tue, Apr 5, 2016 at 5:17 PM, Ryan Giordano<EMAIL_ADDRESS>wrote:

Or rather, I'm a little confused -- why are you using julia4?  Sorry if
I'm behind the curve.
On Tue, Apr 5, 2016 at 5:16 PM, Ryan Giordano<EMAIL_ADDRESS>wrote:

Shouldn't we use
module load julia/0.5.0-dev-2918
?
On Tue, Apr 5, 2016 at 5:02 PM, kpamnany<EMAIL_ADDRESS>wrote:

Create celeste_1.sl containing:
#!/bin/bash -l
#SBATCH --partition=debug
#SBATCH --nodes=1
#SBATCH --job-name=celeste
#SBATCH --time=00:30:00
export OMP_NUM_THREADS=1
export JULIA_NUM_THREADS=1
module load julia
export I_MPI_PMI_LIBRARY=/opt/slurm/default/lib/libpmi.so
export I_MPI_PIN_DOMAIN=auto
srun -n 32 julia /global/homes/k/kpamnany/.julia/v0.4/Celeste/bin/celeste.jl infer-box 200 200.5 38.1 38.16 $SCRATCH
Use your Celeste directory, of course. Run this with sbatch celeste_1.sl
and the slurm-xxxxxxx.log file will contain the output (where xxxxxxx
is the job ID). The job is killed due to running out of memory.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jeff-regier/Celeste.jl/issues/215

We switched back to Julia 0.4 because we can't use threads, I thought. It's
faster and more stable than 0.5
On Tue, Apr 5, 2016, 5:28 PM Ryan<EMAIL_ADDRESS>wrote:

Also, Rollin, what was the correct way to load libcfitsio.so on Cori? I'm
getting this error:
ERROR: LoadError: error compiling main: error compiling stage_box_nersc:
error compiling query_overlapping_fieldids: error compiling
query_overlapping_fields: error compiling call: error compiling
fits_open_file: could not load library
"/global/u2/j/jregier/.julia/v0.4/FITSIO/deps/usr/lib/libcfitsio.so"
...which is probably an artifact of my having copied it over from Jeff's
directory. (There are no obvious simlinks that I can see, so julia might
have cached the path somewhere?)
On Tue, Apr 5, 2016 at 5:17 PM, Ryan Giordano<EMAIL_ADDRESS>wrote:

Or rather, I'm a little confused -- why are you using julia4? Sorry if
I'm behind the curve.
On Tue, Apr 5, 2016 at 5:16 PM, Ryan Giordano<EMAIL_ADDRESS>wrote:

Shouldn't we use
module load julia/0.5.0-dev-2918
?
On Tue, Apr 5, 2016 at 5:02 PM, kpamnany<EMAIL_ADDRESS>wrote:

Create celeste_1.sl containing:
#!/bin/bash -l
#SBATCH --partition=debug
#SBATCH --nodes=1
#SBATCH --job-name=celeste
#SBATCH --time=00:30:00
export OMP_NUM_THREADS=1
export JULIA_NUM_THREADS=1
module load julia
export I_MPI_PMI_LIBRARY=/opt/slurm/default/lib/libpmi.so
export I_MPI_PIN_DOMAIN=auto
srun -n 32 julia
/global/homes/k/kpamnany/.julia/v0.4/Celeste/bin/celeste.jl infer-box 200
200.5 38.1 38.16 $SCRATCH
Use your Celeste directory, of course. Run this with sbatch
celeste_1.sl
and the slurm-xxxxxxx.log file will contain the output (where xxxxxxx
is the job ID). The job is killed due to running out of memory.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jeff-regier/Celeste.jl/issues/215

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jeff-regier/Celeste.jl/issues/215#issuecomment-206046813

Right. Hence just the module load julia, to get Julia 0.4 by default.

@rgiordan, sorry I've been offline a bit.  I guess Julia must have the path cached somewhere when you copied things from Jeff.  I don't have problems with FITSIO building when I install Celeste though so you should be able to get it that way.

Yep, Pkg.add("FITSIO") is working again.

Still running out of memory at higher node counts. At 16 nodes:
<snip>
[82] processing source 753: objid =<PHONE_NUMBER>297286725
slurmstepd: Step 1758132.0 exceeded memory limit (130506800 > 127926272), being killed
slurmstepd: Step 1758132.0 exceeded memory limit (130510336 > 127926272), being killed
slurmstepd: *** STEP 1758132.0 ON nid00161 CANCELLED AT 2016-04-06T02:03:45 ***
slurmstepd: Exceeded job memory limit
<snip>

This is weak scaling 0.5x0.5 per node, so 16 nodes was trying to run inference on a 8.0x0.5 patch of sky.

The built-in whos function may be useful for figuring out what's using all the memory. I didn't know about this function before. Whereas the --track-allocation flag records how much memory each line is allocation, the whos function reports which data structures are pointing to memory that hasn't been freed at the the time when it is called.

Apparently the whos command doesn't report memory allocated by ccall, and most memory gets allocated within libraries by ccall. We may get further suggestions from this question I posted on stack overflow.

I've instrumented divide_and_infer() in src/api.jl to output GC stats at different points -- before and after calling infer(). This has, unfortunately, not provided any helpful data.  The next call is to infer(), after which:
[19] post-infer()  49.926849 seconds (44.18 M allocations: 4.902 GB, 6.28% gc time)
[19] post-infer()  15.640568 seconds (15.59 M allocations: 2.975 GB, 15.73% gc time)
[19] post-infer()  12.401329 seconds (11.71 M allocations: 2.671 GB, 14.92% gc time)
[19] post-infer()  15.127516 seconds (19.55 M allocations: 2.477 GB, 8.40% gc time)
[19] post-infer()   7.619690 seconds (6.57 M allocations: 1.344 GB, 13.24% gc time)
[19] post-infer()  14.732585 seconds (14.27 M allocations: 2.036 GB, 9.88% gc time)
[19] post-infer()   7.890878 seconds (6.84 M allocations: 1.365 GB, 12.81% gc time)
[19] post-infer()  12.889648 seconds (11.72 M allocations: 1.798 GB, 10.37% gc time)
[19] post-infer()  20.485179 seconds (26.43 M allocations: 3.841 GB, 12.63% gc time)
[19] post-infer()  60.575250 seconds (87.63 M allocations: 8.735 GB, 8.49% gc time)
[19] post-infer()  28.389027 seconds (26.97 M allocations: 3.870 GB, 10.02% gc time)
[19] post-infer()  27.118950 seconds (39.23 M allocations: 4.879 GB, 12.66% gc time)
[19] post-infer()  14.435009 seconds (11.90 M allocations: 1.832 GB, 9.12% gc time)
[19] post-infer()  18.493309 seconds (15.88 M allocations: 2.196 GB, 8.90% gc time)
[19] post-infer()  39.584765 seconds (37.87 M allocations: 4.820 GB, 9.42% gc time)
[19] post-infer()  51.040483 seconds (76.76 M allocations: 7.913 GB, 12.23% gc time)
[19] post-infer()  26.205530 seconds (28.83 M allocations: 4.041 GB, 12.39% gc time)
[19] post-infer()  44.100024 seconds (48.03 M allocations: 7.090 GB, 14.22% gc time)

Unfortunately, you cannot tell the state of the heap (or Julia's memory pools) from this data. So, that's the next thing I'm trying to trace.

Looks like mp.tile_sources uses a lot of memory, based on the output of top. If we get rid of the concept of tiles as part of #219, that should bring memory usage way down.

This is awesome! Hopefully this took away the leak also. Will test on Cori.

It's should be fairly straightforward now to get an additional 90%
reduction in memory use, since all the images are getting copied to each
process, but only a few tiles are needed by each worker process at a time.
Maybe this is good enough for now though, if multithreading will be working
soon?
On Tue, Apr 26, 2016, 9:18 AM kpamnany<EMAIL_ADDRESS>wrote:

This is awesome! Hopefully this took away the leak also. Will test on Cori.
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/jeff-regier/Celeste.jl/issues/215#issuecomment-214799272


Fix OOM virtiofs container limit

Signed-off-by: Romà Llorens<EMAIL_ADDRESS>What this PR does / why we need it:
We found that with intensive disk usage, virtiofs container OOMs at the current limit (40M)
Bumping this limit to 80M solved our issue (Max usage observed is 71M)
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Issue discussed on Slack Channel with @xpivarc
Release note:
Bump virtiofs container limit

/lgtm

/retest-required


Fix wrong tag_column indentation

The tags_width was being subtracted in any case, which resulted in flushright alignment per default. When a negative tag_column value was given, the tags_width was subtracted twice, resulting in a broken alignment.

tag_column is not meant to be negative. Flushright alignment is how Emacs aligns it. Initial implementation was wrong, but I fixed it some time ago. Agenda is also aligned that way (kind of).

If it's not meant to be negative, then 1) the DOCS.md is wrong and 2) there is no real reason for this subtraction, or is there? Actually, I think there should be no math.abs either in this case, just a default value.

My emacs says this:
org-tags-column is a variable defined in ‘org.el’.
Its value is -77

Documentation:
The column to which tags should be indented in a headline.
If this number is positive, it specifies the column.  If it is negative,
it means that the tags should be flushright to that column.  For example,
-80 works well for a normal 80 character screen.
When 0, place tags directly after headline text, with only one space in
between.

You are completely right, I misunderstood it. I thought it always behaves as flushright.
I think what we need to do here is to change the default for org_tags_column to -80 instead of 80, and to apply your fix. Test with :ARCHIVE: tag shouldn't need to be changed since it should pass with your fix and the default value change.

@kristijanhusak I applied the changes you suggested. Indeed, the change in the unit test was not necessary :+1:


Color Polygons

Add colors to polygons option

When SHOW button is clicked for polygon color table, the color table window pops up below the visible range in the MT workspace. We solved this by zooming out and scrolling down to find it.


allowIndentation docs are outdated

What happened?
The docs on the website mention allowIndentation setting but it looks this setting is not functional: indentation is allowed regardless.
Should we adjust the docs?
To reproduce
Use allowIndentation: true or allowIndentation: false, nothing changes.
Version
0.3.4
Additional context
Looks like it was disabled in this PR: https://github.com/markdoc/markdoc/pull/105
And here is the comment by @rpaul-stripe that explains the decision: https://github.com/markdoc/markdoc/issues/82#issuecomment-1165784291

Yes, indent-based code blocks are now disabled by default. The allowIndentation option is still relevant, however, because it tells the tokenizer to allow other block types to be parsed when indented.
For example, consider the following Markdoc source:
This is a test

    - This is another test

When the allowIndentation option is not enabled, the list is not recognized as such because it is indented more than three spaces, resulting in this output:

This is a test

- This is another test

. With the option enabled, the list tag parses as expected.
The reason we still don't turn this on by default is because content written with this sort of indentation will not parse as expected in a CommonMark-compliant parser.
I can update the docs to clarify this and address that indent code blocks are now off by default regardless of the setting. Thanks for raising this. 👍

Indented code blocks are a significant use case, though, especially with regards to portable content. Indented blocks are the only one supported by more "old-school" parsers including the original Gruber one, especially when dealing with content nested inside lists. For example, in Python-Markdown, even with the "extra" settings for code fences,  you can't use code fences in lists, but you can use indented code blocks. Content that's written for these parsers can also be handled by CommonMark parsers, but disabling indented code breaks that.
I say this as someone who has been writing such content for 9 years, and finds a lot of the content incompatible with Markdoc because of the use of indented code blocks inside lists.

@mDuo13 if you really need to parse content written with indented code blocks in Markdoc, you can still subclass Markdoc's Tokenizer class and set up an instance of MarkdownIt with whatever features (and specific plugins) you want.


config option to change the extension

In previous versions the filename remained the same across backups/reduces/resizes.
In commit f9eed2f1f5b6f89bb6ff8fc849951f0804c13379 the code was changed to change to the file type's extension, breaking my app (when I updated). I don't expect the filenames to change (even if they are wrong).
Made it optional with a config option changeExtension, that defaults to false (the original behavior). I know it's back and forth on 'breaking changes' but hopefully there are more people who haven't yet updated than there are people who have (or had to revert to the old code after finding it breaks their app).

Will change to Boolean(), waiting for the tests to finish because I think there's another failing test and I can't run it on my machine for some reason.
How will it bother ImageMagick? He gets the raw data (see https://github.com/ysugimoto/aws-lambda-image/blob/9924bc179fbc3567d97f86eef8ae94915dd51034/lib/ImageResizer.js#L34) he doesn't know what filename you'll save it to. All that really matters with image types is the mime type set in S3 metadata, which this project does properly. Nobody looks at the filename, only the content type received from the HTTP web server (which S3 chooses according to the metadata).

Yes, ImageMagick doesn't have to know. ImageData.js detects MIMEType from raw data using image-type package. If we do reduce after resize, Is there the resized image's raw data like JPEG format, but raw data is PNG? I concern about this.
If this is clearly, let's merge it.

It should be fine, the type of the data (chosen by ImageMagick and determined by image-type) is completely unrelated to the output filename chosen, which can be anything and doesn't affect the data.
A browser downloading the image from S3 and showing it in an <img> tag would not care about the filename (URL) either, it only looks at the Content-Type header of the response which is sent by S3 according to the mime data set on the file, S3 doesn't care about the filename either.
The only problem is if someone takes the S3 file and determines the file type according to the extension (which is a bad way to determine), in this case the package's user can use the changeExtension option.
Can you check why travis is stuck? I think there might be one failing test I need to fix before this is merged.

Changing you app to make it expect change of the extension would seem to be more reasonable approach for me :)

@kdybicz that would mean the lambda needs to update the DB (Mongo in my case). I actually have all images uploaded as "image.jpg" (to different directories) and I prefer it not to change ever :smile:

@ysugimoto I've been wrapping my brain around these failures and I have no clue 😢
I can barely run the test suite, I have to disable eslint and then I get a lot of Error: write EPIPE. Would also be nice to be able to run a single test. Any ideas?

@odedniv I saw Travis's log, some assertions are failed. And eslint error reports in your environments? An error of write EPIPE might be a process I/O error in node.js, and I'm not sure why, or when that error is occurs 😢
Anyway, you can run a single test to install ava globally, I think:
$ npm install ava -g
$ ava test/e2e-jpeg.js

If we passed the tests, let's merge this

This is the output I get from running the tests:
oded@plex ~/devel/aws-lambda-image $ ava test/e2e-jpeg.js
Reducing to: in-place
Reducing to: some
Backing up to: in-place
Resizing to: in-place
Resizing to: in-place
Resizing to: in-place
Resizing to: in-place
Resizing to: in-place
Reducing to: in-place
Reducing to: in-place
Reducing to: in-place
Reducing to: in-place
Reducing to: in-place

  1 passed
  3 exceptions

  Uncaught Exception
  Error: write EPIPE

  Uncaught Exception
  Error: write EPIPE

  ✖ Test results were not received from test/e2e-jpeg.js

It doesn't make sense on many levels... for example the file contains more than 4 tests

Hmmmmm...
I just run test as same as you, success it.
So, I'm using node v6.9.1 on macOS. Please let me know about your environment?
In addition, please reinstall ImageMagick if you can.

Didn't work... Well if it succeeds for you I guess it can be merged :)


Fix bad doc guidance around auth

To refresh an app token, you simply make the same call to the AAD endpoint again. The "refresh" flow you recommend there is not usable in this context because you have to auth code.
Source: I am the EM of the Identity SDK for .NET

Learn Build status updates of commit 189acd9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

uwp/monetize/create-and-manage-submissions-using-windows-store-services.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#sign-off


How to match / in globPatterns

Welcome! Please use this template for reporting bugs or requesting features. For questions about using Workbox, the best place to ask is Stack Overflow, tagged with [workbox]: https://stackoverflow.com/questions/ask?tags=workbox
Library Affected:
workbox-webpack-plugin
Browser & Platform:
Chrome
Issue or Feature Request Description:
How to match / in globPatterns whatever i tried I always get an error that / is not cached offline.  Also, the / is rendered by server side and it's not the actual file. (Laravel backend)
When reporting bugs, please include relevant JavaScript Console logs and links to public URLs at which the issue could be reproduced.
new workboxPlugin({
                    globDirectory: DIST,
                    globPatterns: [
                        '**/*.{html,js,css,jpg,png,gif,svg,wotf,wotff,xml,json}',
                        '**/'
                    ],
                    swDest: path.join(DIST, 'sw.js'),
                    clientsClaim: true,
                    skipWaiting: true,
                })

The templatedUrls config option can be used to properly version dynamic/server rendered/templated URLs like what you describe: https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-build#.Configuration
What you need to do is specify a mapping of server-rendered URLs to the list of local files available during your build process that they depend on. And then if any one of those files changes, the entire URL will be invalidated and refreshed when the service worker updates.
(The one wrinkle here is that if you server uses a mix of local files and remote resources, like a database lookup, to determine how to respond to a URL like /, you won't be able to safely precache that URL. You can only depend on files that are present at build time.)
new workboxPlugin({
  globDirectory: DIST,
  globPatterns: [
    '**/*.{html,js,css,jpg,png,gif,svg,wotf,wotff,xml,json}',
  ],
  swDest: path.join(DIST, 'sw.js'),
  clientsClaim: true,
  skipWaiting: true,
  templatedUrls: {
    '/': [
      'path/to/index.template',
      'path/to/inlined/styles/*.css'
      // etc., for any other local files that go into determining the server-output for '/'
    ],
  },
})

@jeffposnick thank you for this answer. And how do you deal with authorized VS non-authorizsed? I have it somehow working but not sure how to deal with with LOGOUT it still server the user / which has been cached?
.webpackConfig(
    {
      plugins: [
        new WORKBOX({
          globDirectory: DIST,
          globPatterns: [
            '**/*.{js,css,jpg,png,gif,svg,wotf,wotff,xml,json}'
          ],
          swDest: DIST + '/sw.js',
          clientsClaim: true,
          //navigateFallback: '/login',
          cacheId: 'operationsApp',
          skipWaiting: true,
            templatedUrls: {
                '/': [
                    '../resources/views/layouts/app.blade.php',
                    '../resources/views/layouts/login.blade.php',
                    '../resources/views/auth/login.blade.php',
                    '../resources/views/layouts/partials/meta.blade.php',
                ]
            }
        })
      ]
    }
  )

There are a few options for clearing storage at https://stackoverflow.com/a/47417193/385997


doc: Update the required-permissions.md

Add the description of permissions for the account scanner stack.

@Arroxane-TM
Thanks for your suggestion. I only have one question for you, please refer to https://github.com/trendmicro/cloudone-filestorage-deployment-templates/pull/126#discussion_r1411213059.


Add details tags for the All Monoid signatures [docs]

This adds a sample taste for using details tags for alternative explanations the documentation.
This tag is not currently supported by IE or edge browsers.

Coverage remained the same at 100.0% when pulling 931425585c727c3680d8dd3c28920c73c330c796 on rstegg:rsteg-docs into ac363e963373af6bb2b1707cc53637124d829293 on evilsoft:master.

Closing for now, will still do these tho.


Fix logic for MSSQL Server AzureAD administrator

Issue-id
PR Checklist

[ ] I have added example(s) inside the [./examples/] folder
[ ] I have added the example(s) to the integration test list for normal (~30 minutes) or long runner >30 minutes
[x] I have checked the coding conventions as per the wiki
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?

Description

The current implementation is creating dynamic configuration based on a optional attribute (doc).
This PR allow assigning AzureAD administrator to a SQL Server without enforcing usage of "Active Directory Only" users.
Does this introduce a breaking change

[ ] YES
[x] NO

Testing

thanks for your contribution to Cloud Adoption Framework @a-ferri!


Interference with automatic list continuation

Thanx for your great plug in. I noticed an issue: when the plug in is disabled, if i am in a list and press enter, a new bullet point appears (or check-box or numbered-list item, depending the list type) and remember the identation. When the plug in is enabled and i am in a list, pressing enter would just create a new line and not add a bullet point and also forget the identation.

Hello @bthollet ,
Thank you for your feedback and for using my plugin. I appreciate your contribution to improving the quality of this plugin.
After conducting a thorough investigation, I can confirm the existence of the bug you mentioned. I have taken action to address this issue, and it has been successfully fixed in PR#6. The fix has been incorporated into the latest plugin release, version 0.0.5. To resolve this problem, all you need to do is update your plugin to the most recent version.
Your keen observation is invaluable in helping us maintain and enhance my plugin's functionality. We greatly appreciate your diligence in reporting this issue.
If you encounter any further problems or have additional questions while using the plugin, please don't hesitate to reach out to me at any time. I'm here to assist you and ensure a seamless experience.
Once again, thank you for your contribution and for your continued support.
Best regards,
Hobee Liu


feat: whitelist .config dirname

This PR closes #6.
This pull request includes a small change to the src/main.rs file. The change introduces a whitelist for hidden files, allowing certain hidden files to be visible.

src/main.rs: Added a WHITELIST constant to allow .config files to be visible in the is_hidden function.

Good enough for now, I might revisit the hidden file question later.


Add responsive components

Details
Add a HOC that transforms responsive props

Not moving forward for the following reasons:

Components should render the same way cross-platform
Only Layout should be responsive


Branch management for 2.0

We are regularly receiving incompatible changes with the 1.x versions.
In order to be able to anyway incorporate those changes, we should dedicate a specific branch the future potentially incompatible version (2.0).
As it seems that mostly everyone uses master as is as 1.x compatible version, we are stuck with master being used for the v1. wdyt ?

Please keep master fully backwards compatible with no exceptions. It's far too relied upon that I want to compromise the trust of the community. I am conflicted on how to proceed for the future, safely.

Indeed, that was what I was talking about. As the master branch is used in most project as the next version branch, we could also to avoid any fogginess freeze the master branch and use a dedicated v1 branch and create when wanted a v2 branch.

I think that's the way to go David.
By the way, thanks for all your stewardship here

Agreed on wanting to keep things as stable as possible. We will want to make sure Go modules works correctly in the propsoed scenario.
A question this brings up in my mind is at what point do people expect v2.0 to be the default and master being v1.0 starts to become a problem? I've not personally run in to other repos that do this, so logrus would be totally undoing assumptions I've been able to make about packages in the Go ecosystem. Are we okay with that? Is it healthy? I'm not sure I have an answer.
Do we have a bar for ever making master v2.0? If we never plan on doing that, does a 2.0 even make sense since they will most-likely end up on v1.0 and the newer features won't be exercised as much?

I noticed this thread after open a PR to add go module support (https://github.com/sirupsen/logrus/pull/817). I believe that the current thinking for go modules and v2 versions is to create a directory v2 inside the repository (rather than a branch). However given how much flux there is with go modules, I may be out of date with this statement.

@dgodd from what I understand from this page https://github.com/golang/go/wiki/Modules we don't need to move code in a subdirectory when using go module. This is only need to import such path when NOT using go modules.

I suggest creating a new branch. Until Go Modules stabilize  I hesitate to adopt it within the master branch.

@aarongreenlee module definition has already been added to the mastre branch. It should not have any  impact in the build process of package stored in $GOPATH/src, but can already be used by anyone else.
I think its important for a package as much used as logrus to quickly provide its modules definition in order to help other including package to also adopt/experiment with modules.

@sirupsen, if you agree with the naming, I'm going to create release-v1 and release-v2 branches. I think only you has the rights to then perform the following options:

define release-v1 as the default target branch for pull request
potentially forbid merge request on master branch
if you could also lock 1-0-stable as it seems to have never have been used


correcting a few typos

Noticed a few typos.

ugh, merge conflicts.
thanks so much! wish i saw this earlier.

✨🍰✨


Project: Hotolink Management System

Project name
Contoso Hotolink
Description
A smart desk management system powered with AI, which helps the users to manage the reservation and generates the report. Here user can interact with App using Teams and manage the reservation and PVA helps in making smart decisions.
Project Repository URL
https://github.com/Mr-Clrscr/MSFT_HTT23_HOTOLINK
Project video
https://youtu.be/flSBDRyus0M
Team members
vinaydeep ayinapurapu(vayina10@5wrdjv.onmicrosoft.com), RadhaKrishna Tharavarthi<EMAIL_ADDRESS>

Hi @vayinapurapu, thank you for your project submission. I only see a readme file in your repository. Would you be able to provide your source code in the repository as well. It's mandatory for the project submission. Please let me know.

Hi Walder, we have used the Power Virtual Agent which is Power Platform service and where we are expecting to be accessed from the BOT icon on home page. If you are still persisting the issues, you can try below link as well where we have published to PVA workspace.
https://web.powerva.microsoft.com/environments/Default-c494bf0b-4107-4675-bf1a-f5ecd654a7d3/bots/crcea_zoyaTheHelpAssist/canvas?__version__=2

Thank you for the additional information. This hackathon is focusing on apps for Microsoft Teams built using pro-code approach and using Power Platform and its features like PVA is outside of the scope of the hackathon. In the judging process, we'll focus on the pro-code portion of your app.


Add option support to async helpers

I've been trying to fix #62 as we need that functionality in Ghost. I can fix it by doing an override of registerAsyncHelper locally, but I also found this way to update the existing code to support both the existing version which assumes there is only context, and support helpers which also provide options.
Not sure if my approach is ideal though, so thought I'd raise it as a PR here and get some feedback. If the approach is good then I'll add some tests.

will look at this in about 8 later today

That's a simple, effective solution. Why didn't I think of that? Please add tests and I'll integrate.

Hey @mgutz thanks for checking this out so quickly. After spending quite a lot of time digging through the deeper levels of hbs.js and async.js trying to fix the issue, I didn't quite believe it when it dawned on me I could do it this way!
I've updated my PR to include tests which demonstrate using a basic option and also the much more advanced block async helper usecase and it all seems to work smoothly :)

@mgutz just FYI - if you want any code changes for style or anything, or want new or different tests, just say - more than happy to fixup :+1:

:dancers:


Remove Package.resolved post dependency resolution

Removes the Package.resolved file that was auto-deleted by Xcode after resolving the dependency graph in SwiftRefactorExtension project.

@swift-ci Please test


Auth via connect button?

I am not sure if this is feasible, but is there any way to let users use the connect button to auth (basically prooving to our backend server that the user does own the private key to that radix account)? Kind of like "login with google" but "login with radix wallet".
Ideally I need a service where users can signup / login via wallet app instead of creating a new account (with email  or login with google / facebook or similar).
A use case might be: I have a centralized service that lets you track radix wallet's and sends emails whenever a new transaction on one of the watched addresses is submitted. Ideally users do not need to signup with email but can signup by connecting their radix wallet only. Additionally I want to give a discount for all users that did their first transaction before 2024.
edit: I think this can be done using ROLA. (https://docs.radixdlt.com/docs/rola-radix-off-ledger-auth)

Yes, ROLA is the answer. If in doubt, please reach out to us and other developers through discord


Minecraft Logo doesn't show up

Latest log link
hi, installed fabrication on 1.20.1 recently and the logo doesnt show up anymore. in the woina section it says the logo is "not ported", though the files listed in the description of it (config/fabrication/block_logo.png and config/fabrication/block_logo.ini) are there.

Not ported does mean just that. yes the files are still there. but it should be turned off because it doesn't work.
There's a 30 moneyz bounty for it,  if someone feels like fixing it though.


integrations: Add webhook payloads for Stripe

Automated message from Dropbox CLA bot
@Bickio, it looks like you've already signed the Dropbox CLA. Thanks!

Hi @Bickio!
Thanks for working on this, it looks great!
 Thanks!

Ok sorry about that. It should be on commit now.

Oops. Fixed the lint error.

@timabbott This is ready to merge, I believe.  @Bickio did a great job to get so much test data (15 files!), but as he mentioned in his notes to zulip-gci, there were even more messages that he couldn't retrieve without credit card info.   My guess is that we'll want to write the initial integration to use what we have now, put that out in the world, and then iterate from there.

Cool, yeah, this looks great, thanks @Bickio!  @Bickio are you planning to continue with writing the stripe webhook integration?  What we've been doing is leaving these PRs open for the author to continue with adding the integration itself in the same PR.

Yeah. I may as well!
It appears, though, that the stripe coding task is not available. Maybe someone has already taken it? Or do you only release it once the first part has been done?
A note about the credit card info; all of the messages were available, but only with blank messages (no real data like balances, amounts, customer info etc.) Also, there was no ability to test slacks integration, as that required a full stripe account as well.
Cheers,
Bickio

Alan Zhu is doing the implementation, so if it could be merged that would be great.
Cheers

OK, merged, thanks @Bickio!


Connect helper

I was wondering if there's any reason for the absence of a connect helper.
Let's say i have stateful component and I want to call an effect that fetches an API on componentDidMount. How can i achieve it without hooks?
because right now i was trying to use Hooks but i get useAlveron is not a function because on import it's an object and not a function, so i suppose my react version doesn't support hooks.
"react": "16.6.3",

Why did you close that one? Found that hooks require >16.8.0?
I was just about to answer this week :/

ii wrote a sort of helper to do something like that, but if you want to keep it open i can reopen it. I got no answer so i thought you were no interested in it.


:hammer_and_wrench: Allow for get_content of LSP to be configurable.

Did you check the docs and existing issues?

[X] I am using latest nougat.nvim
[X] I have read all the nougat.nvim docs
[X] I have searched the existing issues of nougat.nvim

Problem
get_content of LSP config is currently hardcoded to a set function
Solution
Allow for a configurable opts to be passed to allow overriding the default implementation
Alternatives
An alternative would be created the Item then merging it with another table that has my custom function
local item = nut.lsp({
  config = {},
  prefix = "  ",
  hl = { fg = color.green },
  sep_right = sep.right_chevron_solid(true),
  on_click = function()
    vim.cmd("LspInfo")
  end,
})

stl:add_item(Utils.merge(item, { content = custom_content_fn }))

Additional Context
No response

What are you trying to config?
Did you try the config.content? Example taken from https://github.com/MunifTanjim/nougat.nvim/pull/53:
local lsp_servers = nut.lsp.servers.create({
  ctx = {
    content = {
      lua_ls = "LuaLS",
    },
    hl = {
      lua_ls = { fg = "cyan" },
    },
  },
  priority = 1,
  hl = { bg = "gray", fg = "white" },
  sep_left = sep.left_lower_triangle_solid(true),
  config = {
    content = function(client, item)
      return {
        content = item.ctx.content[client.name] or client.name,
        hl = item.ctx.hl[client.name],
      }
    end,
    sep = " ",
  },
  suffix = " ",
})

A more detailed example: https://github.com/MunifTanjim/nougat.nvim/issues/49#issuecomment-1825004239


Check asm of PartialEq on ppc64le

PPC64LE has a vcmpeq instruction that returns a vector of bools (like on x86 and arm), but also sets the CR[6] to true if all elements of the vector of bools are true, which allows implementing == using a single instruction since the vector reduction is not necessary.
The current implementation of PartialEq for the portable vector types does an a.eq(b).all() which might be hard for llvm to lower correctly to vcmpeq because llvm.vector.reduce.and is pretty new. It might be worth it to check if this is generated correctly, and if not, figure out what to do. We need to add a codegen/ module for partial_eq and call into that on ppc instead of doing the generic a.eq(b).all() dance.

I'm not sure I follow exactly what the relationship between PartialEq and a.eq(b).all() is

PartialEq is currently implemented as a.eq(b).all(). That's it.

it seems to me that what is needed is an ability to do the equivalent of

Yep, this needs using a different PartialEq implementation on ppc architectures. I checked and LLVM does not properly lower a.eq(b).all() (see: https://bugs.llvm.org/show_bug.cgi?id=36702#c6).
The problem remains: until that LLVM bug is solved, there is no way for a.eq(b).all() to lower to vcmpeq.

We know that our handling of vector reductions is generally lacking as it all naively lowers each of the operations that the reductions break down into. We're working on improving this handling in the back end in general.
In the meantime, there's always the option of using the intrinsics that we use for vec_all_eq and vec_any_eq.

In the meantime, there's always the option of using the intrinsics that we use for vec_all_eq and vec_any_eq.

This is the workaround proposed in this issue.

We need to add a codegen/ module for partial_eq and call into that on ppc instead of doing the generic a.eq(b).all() dance.

Basically, on ppc, instead of just calling a.eq(b).all() like we are currently doing, we would just implement PartialEq::{eq,neq} using vec_all_eq and vec_any_eq for the vector types that support it.
stdsimd does not implement vec_{all,any}_eq yet, but once it does, implementing this workaround shouldn't be too hard.

We're working on improving this handling in the back end in general.

That's good to hear! Note that we will probably implement the workaround for 128 bit wide vectors initially only, so that smaller and wider vectors might still be using a.eq(b).all() afterwards.

Tracked in https://github.com/gnzlbg/packed_simd/issues/9 , we are currently not testing the machine code of any portable operations but this would be a good start.


Unable to deploy to production due to rails 5.0.1 conflict with bundler 2

Rails 5.0.1, which the base app is made in, requires (bundler (< 2.0, >= 1.3.0)). However, the current bundler version is 2.0.1 which is not within this requirement.
I tried uninstalling bundler with gem uninstall bundler and then installed the last version that should work with gem install bundler --version 1.17.3. That worked and I was able to bundle install successfully.
However when I deploy to production in heroku it crashes half-way through installing the gems with this message in the terminal output:
Downloading rails-5.0.1 revealed dependencies not in the API or the lockfile
remote:        (bundler (< 2.0, >= 1.3.0)).
remote:        Either installing with --full-index or running bundle update rails should
remote:        fix the problem.
I reasoned that the problem was with the gemfile.lock, but altering it to bundler ( = 1.17.3) doesn't solve this problem.
I tried to use all my technical sophistication (over a number of hours this evening) but I can't work out how to resolve this so I can deploy to heroku. The only other thing I can think of is upgrading rails.. but when I searched for this the page I checked said that rails version needs to be decided when you create the app.

Also, running bundle update rails as the terminal output suggests has no effect, simply yielding the output: Bundler attempted to update rails but its version stayed the same

I’ve recently updated the app’s Gemfile.lock to use Bundler 2.


add Dnsmasq exporter into exporters list

Signed-off-by: Matt Pursley<EMAIL_ADDRESS>

@brian-brazil , this PR just adds dnsmasq_exporter into exporters.md...
exporters.md -> Miscellaneous -> Dnsmasq exporter](https://github.com/google/dnsmasq_exporter)
In case you haven't come across it before, "Dnsmasq is a lightweight, easy to configure DNS forwarder, designed to provide DNS (and optionally DHCP and TFTP) services to a small-scale network."...
-- https://en.wikipedia.org/wiki/Dnsmasq
It's small, easy and included in a bunch of Linux distros.  So, it probably gets enough use to worth having the exporter mentioned here too...

Thanks!
All of these metrics sound like Counters rather than Gauges.


Variation in coordinate values

I am rendering a point cloud from  LAS file.
During debugging of render.js's ParticleSystemBatcher.prototype.push method, I found that points added to particle system have coordinate values always positive. And Z component for most of the points is in range of 8-10 units.
Rendered scene is as:

Red axis is X, green axis is Y and blue axis is Z.
As can be seen, coordinate values along all three are both positive and negative. And along Z, coordinate values are very small(image 2), while I found it to be in range of 8-10 during debugging.
What causes this variation?

I also notice weird Z values, they seem to be rounded as my points appear in layers when they really should be distributed across the Z axis. Any reason for this behavior?


Event sourcing candidate

Hi we are looking at good ways of doing event sourcing in Elixir and we have been looking at:
https://github.com/slashdotdash/eventstore
It has some problems with clustering setup and it might be too specialized where we can't just easily add new event handlers as we would get with using a general solution solutions for the log like with Kafka.
I'm just wondering if Antidote would be a good candidate to do most of the hard work in doing event sourcing in your option?
Also is it crazy to use Antidote at this stage, it seems to be build on pretty solid foundations and we are not expecting it to be bug free, but should we wait to explore it?

Hi, my knowledge of event sourcing is also not going to be the best since I'm new to it.
Here is an image
But what is drawing us to that concept is:

Immutability (Having a clear record of what was asked when)
Separation of asking for something to to be done (command) and it being executed by a event handler to be possible being replied to a subscriber.
We have a command that is evaluated by a command handler that might be turned into an event that an event handler is going to react to. So these things are going to be stored in a log (for example Kafka) for persistence. So you have both what was requested and what was the consequence.
Replaying things if something goes wrong.

We aren't going to have large scalability problems yet and we are moving from isolation (deis) to a cluster setup so we can use Erlang a bit better. We are currently having problems with the version in a stream because they require having a singleton handling it and if you make other database connections you get a warning about the version number.
Here is probably better explanations about Event Sourcing.
http://cqrs.nu/Faq
Why we like Antidote:

It's managing very easy to reason about structures.
It has subscriptions.
It does distributed computing.
It's on the BEAM.
It's using proven technology underneath (riak).
I was going to mention that you can access it outside of the BEAM but most databases and other solutions have that also :)

We would need a durable log, where ordering of events is stable.
We would want to read events from the log in an ordered fashion from any point in the log (from the beginning will be a common use-case) to the end, and then continue writing and reading from the end

Sorry for the delay, but I checked with some teammates regarding your requirements.

It is certainly possible to subscribe to events in Antidote; we use ZeroMQ as one components.
We are building on riak-core, but we do not use riak as backend.
All items in the log are stored in a sequence; the backend is in the current version an append-only log.
All updates on one data shard are ordered sequentially, and this order is the same for all replicas of this shard. Across shards we use vector clocks to relate the order of updates.

Antidote strength is actually with concurrent modifications of data types; but you can certainly also use it for immutable data.
We currently do not have an API for getting data directly from the log; instead we serve locally available versions of a data item. So for your use case, we would need to adapt the interface to serve also the log(s) for the different shards, right?

Let me add just one thing to what Annette has already replied.
Regarding subscribing events in Antidote, we have already done it for a
project where clients would subscribe for the updates in a set of objects.
The API for doing this is experimental, but it should be possible to use it.
Nuno
On Thu, Apr 6, 2017 at 4:08 PM, Annette Bieniusa<EMAIL_ADDRESS>wrote:

Sorry for the delay, but I checked with some teammates regarding your
requirements.

It is certainly possible to subscribe to events in Antidote; we use
ZeroMQ as one components.
We are building on riak-core, but we do not use riak as backend.
All items in the log are stored in a sequence; the backend is in the
current version an append-only log.
All updates on one data shard are ordered sequentially, and this order
is the same for all replicas of this shard. Across shards we use vector
clocks to relate the order of updates.

Antidote strength is actually with concurrent modifications of data types;
but you can certainly also use it for immutable data.
We currently do not have an API for getting data directly from the log;
instead we serve locally available versions of a data item. So for your use
case, we would need to adapt the interface to serve also the log(s) for the
different shards, right?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SyncFree/antidote/issues/290#issuecomment-292100521,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJZR8vro0V12rqMh8tNJZUQkcHE4K5DDks5rtJ2QgaJpZM4MzLk3
.

can you point me to where i should be looking?
examples?


Enable compilation of server-side gRPC files

By default, we're only building client-side gRPC files:
https://github.com/cosmos/cosmos-rust/blob/388b18b73e513e9ac7896cf8d245c68ea4c57bf4/proto-build/src/main.rs#L212-L213
Towards providing support for both client-side and server-side implementations, shall we consider adding a cmd-line argument to enable compilation of server-side files?
This feature is needed in a mock chain implementation by @CharlyCst, comment below:

I was about to open an issue for a feature request, but it seems that it would be more appropriate to post it here:
I'm building a mock node for testing purpose and I rely on ibc-proto for proto definitions, however proto-compiler only builds client-related definitions (see this line). For now I simply forked the crate but I would very much appreciate having all the definitions in a single place.
I'm not very familiar with ibc-proto and the needs of the cosmos ecosystem in general, but if someone is willing to provide some guidance I can help on moving thins forward.
Originally posted by @CharlyCst in https://github.com/informalsystems/ibc-rs/issues/425#issuecomment-735920505

I think this should be pretty straightforward. I'll give it a try later today.

closing as stale, we no longer need this right now


AppStore profile - error

Hello
first of all thanks for making our lives a lot easier with your tools.All of them.
Quick question. I tried to run the command below to get an App-Store provisioning profile but it failed.
sigh -a com.company.appname

The error is below:
i also get a screenshot saying: an unspecified error occured.Please refresh and try again
INFO [2015-02-17 10:56:52.35]: Login successful
INFO [2015-02-17 10:56:52.36]: Fetching all available provisioning profiles...
INFO [2015-02-17 10:56:53.31]: Checking if profile is available. (5 profiles found)
INFO [2015-02-17 10:56:53.31]: Could not find existing profile. Trying to create a new one.
INFO [2015-02-17 10:56:53.31]: Creating new profile for app 'com.company.appname' for type 'AppStore'.
/Library/Ruby/Gems/2.0.0/gems/poltergeist-1.5.1/lib/capybara/poltergeist/node.rb:23:in `rescue in command': Firing a click at co-ordinates [737, 641] failed. Poltergeist detected another element with CSS selector 'html body.developer-portal div.ui-widget-overlay' at this position. It may be overlapping the element you are trying to interact with. If you don't care about overlapping elements, try using node.trigger('click'). (Capybara::Poltergeist::MouseEventFailed)
	from /Library/Ruby/Gems/2.0.0/gems/poltergeist-1.5.1/lib/capybara/poltergeist/node.rb:17:in `command'
	from /Library/Ruby/Gems/2.0.0/gems/poltergeist-1.5.1/lib/capybara/poltergeist/node.rb:108:in `click'
	from /Library/Ruby/Gems/2.0.0/gems/capybara-2.4.4/lib/capybara/node/element.rb:133:in `block in click'
	from /Library/Ruby/Gems/2.0.0/gems/capybara-2.4.4/lib/capybara/node/base.rb:84:in `synchronize'
	from /Library/Ruby/Gems/2.0.0/gems/capybara-2.4.4/lib/capybara/node/element.rb:133:in `click'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.3.2/lib/sigh/developer_center.rb:465:in `click_next'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.3.2/lib/sigh/developer_center.rb:273:in `create_profile'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.3.2/lib/sigh/developer_center.rb:227:in `maintain_app_certificate'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.3.2/lib/sigh/developer_center.rb:168:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.3.2/bin/sigh:52:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.0/lib/commander/command.rb:179:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.0/lib/commander/command.rb:179:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.0/lib/commander/command.rb:154:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.0/lib/commander/runner.rb:421:in `run_active_command'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.0/lib/commander/runner.rb:81:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.0/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.3.2/bin/sigh:83:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.3.2/bin/sigh:103:in `<top (required)>'
	from /usr/bin/sigh:23:in `load'
	from /usr/bin/sigh:23:in `<main>'

Thanks for the kind words.
Mh, that's difficult to debug. Could you also attach the screenshot sigh generated for you?

thanks for your time
here is the screenshot

Okay, can you create the provisioning profile yourself on the Apple Dev Portal?

i tried it at first and got this screen. then i tried it again and i successfully created it manually

i tried it again and now it works fine. guess it was a provisioning portal issue. thanks for your support :+1:


update images to newest prefect-saturn and dask-saturn

This PR proposes updating the customer-facing Saturn images to use the newest versions of dask-saturn and prefect-saturn.
They technically already would have gotten these new versions at build time, since the environments use floors like dask-saturn>=0.2.2, but the changes in this PR protect against the case where some environment solve leads to silently getting older versions of those client libraries.

newest dask-saturn is 0.2.3: https://pypi.org/project/dask-saturn/
newest prefect-saturn is 0.5.0`: https://pypi.org/project/prefect-saturn/

Just opening this as a draft, since prefect-saturn won't be published until https://github.com/saturncloud/prefect-saturn/pull/40 is merged and a new prefect-saturn release is cut.

prefect-saturn 0.5.0 is now available on PyPI, so this is ready for review.

FYI - aside from saturn-r, none of the images are getting built for the 04.19 release. They will however be built in the next release, so this is still the correct branch for this to merge.

FYI - aside from saturn-r, none of the images are getting built for the 04.19 release. They will however be built in the next release, so this is still the correct branch for this to merge.

Makes sense, thanks for adding that note.

I won't merge until @jsignell approves as well


RFC: re-export stdlib macros from submodules

Summary
This RFC proposed we start re-exporting macros currently exposed in core::* from submodules. We define a mapping of which macros to re-export from which submodules, though in some cases it makes most sense to keep the macros exported from core.
This RFC does not yet propose we deprecate or migrate any code, that is left up to future RFCs.

Rendered

Nit: I don't think assert and family belong under core::panic, despite causing panics; I think they'd be more appropriate under a module assert or test or similar.
Also, even for some of the unstable macros, we may want to provide them in the prelude if we're not providing them in the crate root. assert_matches, for instance, like assert_eq, is most useful if it doesn't require importing.

Nit: I don't think assert and family belong under core::panic, despite causing panics; I think they'd be more appropriate under a module assert or test or similar.

Yeah, that's fair. The first draft of this I shared on the libs Zulip had them under core::assert, but I changed it based on feedback. Both test and assert would be acceptable to me if that's what libs prefers.
Though I do have a preference for core::panic. I view panic! as a way to unconditionally trigger a panic. And assert! as a way to conditionally trigger a panic. Having them both co-located in the same module feels similar to me to anyhow's macros are structured, and I think would provide a useful overview of the various ways in which panics can be triggered.

ping @rust-lang/libs-api: I don't believe there should be anything major preventing this from being accepted? Whether to export assert! as std::assert:assert! or std::panic::assert! feels like a relatively minor detail. Can I ask you to discuss this RFC during a future sync meeting? Thanks!

vs macros that live in the crate root (e.g. format)

This presumably refers to the use of #[macro_use] on injected extern crate std; which it has been proposed to remove: https://github.com/rust-lang/rust/issues/53977

In the long term, we thought it might be good to 'hide' the original exports from the crate root. We'll keep them there for backwards compatibility (because someone can do std::println!() today),

Is it something that can and should be dealt with using editions?
This applies more to the prelude than macros explicitly used via std:: prefix. Is the cost of deprecation worse than the potential confusion of having an unexpected name in scope? (I didn't know module_path!() was a macro until just now, and posted this last week when I found Rust was not resolving the column! macro I thought it was.)