dockerfile rasa_core

Is there dockerfile of python3.6?
If I change python:2.7-slim to python:3.6-slim, it will report the following error:
pip._vendor.urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Read timed out.
How to solve it?

Thanks for raising this issue, @tmbo will get back to you about it soon.

Can you please post the whole stacktrace?

the content of Dockerfile3:
FROM python:3.6-slim
SHELL ["/bin/bash", "-c"]
RUN apt-get update -qq &&
apt-get install -y --no-install-recommends
build-essential
wget
openssh-client
graphviz-dev
pkg-config
git-core
openssl
libssl-dev
libffi6
libffi-dev
libpng-dev
curl &&
apt-get clean &&
rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* &&
mkdir /app
WORKDIR /app
Copy as early as possible so we can cache ...
ADD requirements.txt .
RUN pip3 install --upgrade pip
RUN pip3 install -r requirements.txt --no-cache-dir
ADD . .
RUN pip3 install -e . --no-cache-dir
VOLUME ["/app/dialogue", "/app/nlu", "/app/out"]
EXPOSE 5005
ENTRYPOINT ["./entrypoint.sh"]
CMD ["start", "-d", "./dialogue", "-u", "./nlu"]
sudo docker build -t rasa_core -f Dockerfile3 .
Sending build context to Docker daemon 158.7 MB
Step 1/13 : FROM python:3.6-slim
---> 425bf6046789
Step 2/13 : SHELL /bin/bash -c
---> Using cache
---> 400efc4e1f5e
Step 3/13 : RUN apt-get update -qq &&   apt-get install -y --no-install-recommends   build-essential   wget   openssh-client   graphviz-dev   pkg-config   git-core   openssl   libssl-dev   libffi6   libffi-dev   libpng-dev   curl &&   apt-get clean &&   rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* &&   mkdir /app
---> Using cache
---> 7953b4df447c
Step 4/13 : WORKDIR /app
---> Using cache
---> 71cdc19dc719
Step 5/13 : ADD requirements.txt .
---> Using cache
---> 711c34315017
Step 6/13 : RUN pip3 install --upgrade pip
---> Running in 489fc6def665
Requirement already up-to-date: pip in /usr/local/lib/python3.6/site-packages (18.0)
---> 5698eae37e50
Removing intermediate container 489fc6def665
Step 7/13 : RUN pip3 install -r requirements.txt --no-cache-dir
---> Running in 66a7fff89bbb
Collecting jsonpickle==0.9.6 (from -r requirements.txt (line 2))
Downloading https://files.pythonhosted.org/packages/32/d5/2f47f03d3f64c31b0d7070b488274631d7567c36e81a9f744e6638bb0f0d/jsonpickle-0.9.6.tar.gz (67kB)
Collecting six==1.11.0 (from -r requirements.txt (line 3))
Downloading https://files.pythonhosted.org/packages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Collecting redis==2.10.6 (from -r requirements.txt (line 4))
Downloading https://files.pythonhosted.org/packages/3b/f6/7a76333cf0b9251ecf49efff635015171843d9b977e4ffcf59f9c4428052/redis-2.10.6-py2.py3-none-any.whl (64kB)
Collecting fakeredis==0.10.3 (from -r requirements.txt (line 5))
Downloading https://files.pythonhosted.org/packages/64/bd/2756ddf350c4bb308e3255f9dcd6610f8b01344947bf74d5d166dc66b0a2/fakeredis-0.10.3-py2.py3-none-any.whl
Collecting future==0.16.0 (from -r requirements.txt (line 6))
Downloading https://files.pythonhosted.org/packages/00/2b/8d082ddfed935f3608cc61140df6dcbf0edea1bc3ab52fb6c29ae3e81e85/future-0.16.0.tar.gz (824kB)
Collecting numpy==1.14.5 (from -r requirements.txt (line 7))
Downloading https://files.pythonhosted.org/packages/68/1e/116ad560de97694e2d0c1843a7a0075cc9f49e922454d32f49a80eb6f1f2/numpy-1.14.5-cp36-cp36m-manylinux1_x86_64.whl (12.2MB)
Collecting typing==3.6.4 (from -r requirements.txt (line 8))
Downloading https://files.pythonhosted.org/packages/05/2b/2b05bf1d5a9dd450447c9a5df3e118a465e5d3cb12b73b7220a5064a403f/typing-3.6.4-py3-none-any.whl
Collecting ruamel.yaml==0.15.37 (from -r requirements.txt (line 9))
Downloading https://files.pythonhosted.org/packages/98/cc/ba3b6ccd0a4f6c51d128742fc5f0f43ae570d67174342578591c50f30013/ruamel.yaml-0.15.37-cp36-cp36m-manylinux1_x86_64.whl (641kB)
Collecting requests==2.18.4 (from -r requirements.txt (line 10))
Downloading https://files.pythonhosted.org/packages/49/df/50aa1999ab9bde74656c2919d9c0c085fd2b3775fd3eca826012bef76d8c/requests-2.18.4-py2.py3-none-any.whl (88kB)
Collecting graphviz==0.8.3 (from -r requirements.txt (line 11))
Downloading https://files.pythonhosted.org/packages/84/44/21a7fdd50841aaaef224b943f7d10df87e476e181bb926ccf859bcb53d48/graphviz-0.8.3-py2.py3-none-any.whl
Collecting keras==2.1.6 (from -r requirements.txt (line 12))
Downloading https://files.pythonhosted.org/packages/54/e8/eaff7a09349ae9bd40d3ebaf028b49f5e2392c771f294910f75bb608b241/Keras-2.1.6-py2.py3-none-any.whl (339kB)
Collecting tensorflow==1.8.0 (from -r requirements.txt (line 13))
Downloading https://files.pythonhosted.org/packages/22/c6/d08f7c549330c2acc1b18b5c1f0f8d9d2af92f54d56861f331f372731671/tensorflow-1.8.0-cp36-cp36m-manylinux1_x86_64.whl (49.1MB)
Exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/response.py", line 331, in _error_catcher
yield
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/response.py", line 413, in read
data = self._fp.read(amt)
File "/usr/local/lib/python3.6/http/client.py", line 449, in read
n = self.readinto(b)
File "/usr/local/lib/python3.6/http/client.py", line 493, in readinto
n = self.fp.readinto(b)
File "/usr/local/lib/python3.6/socket.py", line 586, in readinto
return self._sock.recv_into(b)
File "/usr/local/lib/python3.6/ssl.py", line 1009, in recv_into
return self.read(nbytes, buffer)
File "/usr/local/lib/python3.6/ssl.py", line 871, in read
return self._sslobj.read(len, buffer)
File "/usr/local/lib/python3.6/ssl.py", line 631, in read
v = self._sslobj.read(len, buffer)
socket.timeout: The read operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 141, in main
status = self.run(options, args)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/commands/install.py", line 299, in run
resolver.resolve(requirement_set)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/resolve.py", line 102, in resolve
self._resolve_one(requirement_set, req)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/resolve.py", line 256, in _resolve_one
abstract_dist = self._get_abstract_dist_for(req_to_install)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/resolve.py", line 209, in _get_abstract_dist_for
self.require_hashes
File "/usr/local/lib/python3.6/site-packages/pip/_internal/operations/prepare.py", line 283, in prepare_linked_requirement
progress_bar=self.progress_bar
File "/usr/local/lib/python3.6/site-packages/pip/_internal/download.py", line 836, in unpack_url
progress_bar=progress_bar
File "/usr/local/lib/python3.6/site-packages/pip/_internal/download.py", line 673, in unpack_http_url
progress_bar)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/download.py", line 897, in _download_http_url
_download_url(resp, link, content_file, hashes, progress_bar)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/download.py", line 617, in _download_url
hashes.check_against_chunks(downloaded_chunks)
File "/usr/local/lib/python3.6/site-packages/pip/_internal/utils/hashes.py", line 48, in check_against_chunks
for chunk in chunks:
File "/usr/local/lib/python3.6/site-packages/pip/_internal/download.py", line 585, in written_chunks
for chunk in chunks:
File "/usr/local/lib/python3.6/site-packages/pip/_internal/utils/ui.py", line 159, in iter
for x in it:
File "/usr/local/lib/python3.6/site-packages/pip/_internal/download.py", line 574, in resp_read
decode_content=False):
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/response.py", line 465, in stream
data = self.read(amt=amt, decode_content=decode_content)
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/response.py", line 430, in read
raise IncompleteRead(self._fp_bytes_read, self.length_remaining)
File "/usr/local/lib/python3.6/contextlib.py", line 99, in exit
self.gen.throw(type, value, traceback)
File "/usr/local/lib/python3.6/site-packages/pip/_vendor/urllib3/response.py", line 336, in _error_catcher
raise ReadTimeoutError(self._pool, None, 'Read timed out.')
pip._vendor.urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Read timed out.
The command '/bin/bash -c pip3 install -r requirements.txt --no-cache-dir' returned a non-zero code: 2

Just looks like the dependency couldn't be fetched from pypi - did you retry?

I tried it many times, but the same result

It's the internet problem


Implement crossdock tests for tracing propagation

@abhinav @breerly ready for review

@yurishkuro you are a beast 👍

lgtm sir :shipit:


Automated cherry pick of #8652: networks: make filter by bgp types available

Cherry pick of #8652 on release/3.5.
#8652: networks: make filter by bgp types available

/lgtm
/approve


Invalid json

Issue Summary
When using @sendgrid/client and calling /v3/marketing/contacts, I was hit with a 400 error and a message of Invalid json
Steps to Reproduce

Set up a nodejs application
Add the code snippet (as below) to a route of your choice. Mine is subscribe in this case.
Deploy and run the nodejs application and pass the following data

{
  "email"<EMAIL_ADDRESS>}

Code Snippet
app.post("/subscribe", function (req, res) {
  // Add your code here
  // res.json({success: 'post call succeed!', url: req.url, body: req.body})
  // don't need to json.parse req.body
  const { email } = req.body;
  const request = {
    method: "PUT",
    url: "/v3/marketing/contacts",
    data: {
      list_ids: [process.env.SENDGRID_LISTID],
      contacts: [
        {
          email: email,
        },
      ],
    },
  };

  sgClient
    .request(request)
    .then(([response, body]) => {
      console.log(`statusCode: ${response.statusCode}`);
      console.log(body);
      res.json({ statusCode: response.statusCode, body: body });
    })
    .catch(([response, body]) => {
      console.log(error);
      res.statusCode = response.statusCode;
      res.json({ statusCode: response.statusCode, body: body });
    });
});

Exception/Log
{
  "statusCode": 400,
  "error": {
    "field_id": "",
    "message": "invalid json"
  }
}

Technical details:

sendgrid-nodejs version: 6.0.0
node version: 10.23.0

The Fix
As discovered in packages/client/src/classes/client.js, it is expecting a property body instead of data for the FormData you are passing to sendgrid.
createRequest(data) {
    let options = {
    url: data.uri || data.url,
    baseUrl: data.baseUrl,
    method: data.method,
    data: data.body,
    params: data.qs,
    headers: data.headers,
};

If you go back to the code snippet above, just swap data to body and it should fix this issue for you.

I've no idea how to submit a PR to add this to the document but leaving this here for future reference lol

I am having the same issue even when using body


How to log in to the admin account？You will be prompted with an incorrect email address

What about just register a new account?

What about just register a new account?

But I need an administrator account, how can a normal account become an administrator's permission?

请问解决了吗这个问题我也是相同的问题，注册用户登录不能创建节点，不知道是不是需要管理员登陆

when you register a user the default role is admin. You can check that with this api get call in browser http://localhost:8081/api/v1/users?format=json/

and the default admin and pass are not working because the email is not configured properly see in line 17, 17. change the email from admin@cello =><EMAIL_ADDRESS>and run all the make commands then the creds<EMAIL_ADDRESS>pass should work but as there is not default organisation you will see a blank page like below

so I feel the line admin@cello is intestinal

Run into api_engine CONTAINER:
export<EMAIL_ADDRESS>python manage.py create_user
--username ${ADMIN_USERNAME:-admin}
--password ${ADMIN_PASSWORD:-pass}
--email ${ADMIN_EMAIL:-admin@cello}
--is_superuser
--role admin


KOGITO-8518: Add the ability to send json content as payload to the HttpRecpient and new API

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Your code is properly formatted according to this configuration
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

for pull request checks
Please add comment: Jenkins retest this

for a specific pull request check
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] tests

for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch

for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main

for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts

for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

for native checks
Run native checks
Please add comment: Jenkins run native

for a specific native check
Run native checks
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] native

for mandrel checks
Run native checks against Mandrel image
Please add comment: Jenkins run mandrel

for a specific mandrel check
Run native checks against Mandrel image
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] mandrel

for mandrel lts checks
Run native checks against Mandrel image and quarkus lts branch
Please add comment: Jenkins run mandrel-lts

for a specific mandrel lts check
Run native checks against Mandrel image and quarkus lts branch
Please add comment: Jenkins (re)run [kogito-runtimes|kogito-apps|kogito-examples] mandrel-lts

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

tests goes in  https://github.com/kiegroup/kogito-apps/pull/1609

For the record...
Unrelated tests fails because we need to rebase with main, but if we rebase with main, all the build will get blocked because of the  Gradle deamon issue....
We need to wait for this PR https://github.com/kiegroup/kogito-runtimes/pull/2769/files to be merged in to main, and then rebase.


Clarifies 1 code reviewer, 1 approver

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind documentation
[skip ci]
What does does this PR do / why we need it:
Updates the development.adoc documentation with regards to having 1 code
reviewer and 1 approver.
Which issue(s) this PR fixes:
N/A
How to test changes / Special notes to the reviewer:
N/A
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

Thanks for the catch @mik-dass


error due to pe_direction not being detected

Hi folks,
I have run qsiprep through the Flywheel gear qsiprep-fw v0.3.18_0.10.0, and my jobs are failing with a TraitError related to the pe_direction variable (please see below). The input DTI data has PhaseEncodingAxis set to "j", according to the Flywheel GUI. I am unsure if the error reflects a qsiprep code issue or a problem with the DTI metadata, but your feedback would be appreciated. I am happy to supply more info as helpful.
Thanks,
Jeff
Process Process-2:
Traceback (most recent call last):
File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
self.run()
File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 99, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/miniconda/lib/python3.7/site-packages/qsiprep/cli/run.py", line 884, in build_qsiprep_workflow
force_syn=opts.force_syn
File "/usr/local/miniconda/lib/python3.7/site-packages/qsiprep/workflows/base.py", line 261, in init_qsiprep_wf
force_syn=force_syn)
File "/usr/local/miniconda/lib/python3.7/site-packages/qsiprep/workflows/base.py", line 692, in init_single_subject_wf
source_file=source_file
File "/usr/local/miniconda/lib/python3.7/site-packages/qsiprep/workflows/dwi/base.py", line 431, in init_dwi_preproc_wf
output_spaces=output_spaces),
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 611, in init
from_file=from_file, resource_monitor=resource_monitor, **inputs
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 183, in init
self.inputs = self.input_spec(**inputs)
File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/specs.py", line 66, in init
super(BaseTraitedSpec, self).init(**kwargs)
File "/usr/local/miniconda/lib/python3.7/site-packages/traits/trait_handlers.py", line 172, in error
value )
traits.trait_errors.TraitError: The 'pe_direction' trait of a DiffusionSummaryInputSpec instance must be None or 'i' or 'i-' or 'j' or 'j-', but a value of '' <class 'str'> was specified.

Unfortunately the PhaseEncodingDirection field is necessary to determine what the distortions are. If you're not using fieldmaps you can put any of the allowed values in there. If you are using fieldmaps, you'll need to figure out which (the fieldmap or the dwi) has a positive or negative blip and fill out the field either manually or through the flywheel sdk.

Hi Matt,
Thanks for responding. I was looking for a way to specify pe_direction but
saw that it was not a config option. Should it be specified as a field in
the recon_spec file? And is there a good place to look for example
recon_specs?
Jeff
On Sun, Feb 21, 2021 at 1:54 PM Matt Cieslak<EMAIL_ADDRESS>wrote:

Unfortunately the PhaseEncodingDirection field is necessary to determine
what the distortions are. If you're not using fieldmaps you can put any of
the allowed values in there. If you are using fieldmaps, you'll need to
figure out which (the fieldmap or the dwi) has a positive or negative blip
and fill out the field either manually or through the flywheel sdk.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PennBBL/qsiprep/issues/227#issuecomment-782906742,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJ5MET6EEYYLSIBEDCYW6TTAFJH3ANCNFSM4X3NNGOA
.

The PhaseEncodingDirection is specified in the metadata of the DWI files. Since you're on Flywheel you can edit this info on the scan's container through the SDK or website

Thanks, Matt, I'll do that. These are Philips DTI data, and apparently it's
a known problem that Philips does not record the polarity of the phase
encoding:
https://github.com/rordenlab/dcm2niix/issues/279
Jeff
On Mon, Feb 22, 2021 at 10:24 PM Matt Cieslak<EMAIL_ADDRESS>wrote:

The PhaseEncodingDirection is specified in the metadata of the DWI files.
Since you're on Flywheel you can edit this info on the scan's container
through the SDK or website
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PennBBL/qsiprep/issues/227#issuecomment-783849397,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJ5METO2MP7SZZMPAPJ6ITTAMNVXANCNFSM4X3NNGOA
.


Subscribe to Google Fit Activity

I noticed that I must have Google Fit on my device to record activity.
I wanted to have the module record activity even if the device does not have Google Fit installed, so I added a subscribe function that writes user activity to the Google Fit Store.
It should be initialized when loading the app via Fitness.subscribe(), it returns a promise to show the status of the subscription (true for success and false for failure).

@ibraude it seems nice to me, can you also update the docs with the new methods? so we can test and merge this.
Thanks

@scerelli Will do.


Annotation only example

I don't know how are the min / max values calculate if there are only annotations and no series.
I think the min / max default values on the axes should take into account the position of all the annotations for which positions are defined as number (and therefore values on the axes).
We should first close this issue: https://github.com/zakodium/react-plot/issues/204
We could add first in the storybook an example with only 4 circles in position 1,1 - 2,2 - 1,2 and 2,1 to test.

Because positions are stored differently in circle, line, rectangle, polyline, etc it may be useful to get for each annotation a 'getBoundingRectangle' method.

That's not going to be easy for text and groups. I fear this is a very difficult issue to solve.

Do you have a real use case where it makes sense to not have a series and where you don't know the min/max ?

I was actually thinking about the PCA example https://github.com/zakodium/react-plot/issues/208.

I was actually thinking about the PCA example #208.

it's possible to calculate min,max in this exmple

I think that if we want to implement this feature we could only use the x like (x, x1, y1, array of the x for polyline, etc) and y like coordinates so we don't care about radius of circle, text size, etc.  We would need to add some padding if we are drawing circles and we would like they are not cut on a side.
So text and groups would only be considered as a point and only if the position is specified as numbers (relative to axes)

i think we can use circle radius ....etc for diffrent annotations
and about the group we can take his children
but text i think the only solution is consider it as a point (as u mentioned)

Currently we will not implemented it because annotations are not tracked in the state.


Code cleanup

Inference of return type
Change the order of .success, .failure events of single trait

I think that omitting the Observable Element type will not affect the performance issue (ex. compile time), since the return type of the function is already defined.
I would appreciate any further comments on my comments. :)

@freak4pc I accepted the review content and rebased. I thought it would be nice to use abbreviations in Swift whenever possible, but when I saw the comments, I found that readability could be a problem.
Single.create may be a performance issue, but it does not seem to have a significant impact, and it seems to be good for readability.
I would like to contribute to RxKingfisher open source by adopting PR.

Thank you for accept my PR :)
If I get a chance, I will contribute again😄


Usable record of benchmark run outcomes

in-meeting discussion: should be the whole set of data needed to generate the report.

Meeting discussion: add pip list, make it work with anonymous mode, fix id issue Daniel found


Remove Simulatable

Simulation implements the abstract interface Simulatable, but the latter is only used for Simulation and in an internal detail of the newton package (the way it handles springs). We should simplify newton by removing Simulatable.

cc @chinmaygarde for sanity check

Yeah, its an internal implementation detail. The only other place it is used are the spring solutions (which themselves are internal to newton).

Blocked on https://github.com/flutter/flutter/issues/2441


Move docker image to Alpine Linux

Now that docker users must build the image themselves (see #399), it is a good time to look into optimizing the image.  Building off of Alpine Linux instead of Ubuntu yielded significant improvements in both build time, and image size
Build time:
Alpine - 2:30
Ubuntu - 7:30
Image Size:
Alpine - 280 MB
Ubuntu - 735.7 MB
This change would see no change in the build process on the users side, other than a different mount point for the config.
If you would like to test this build, follow the same process as describe in the wiki, except use config:/usr/src/MusicBot/config as the argument to the -v option when running the image.

+1

👍

I'm going to commit this to review but I suppose I should figure out how this works for myself at some point.

Sounds good, until then I can (hopefully) help you with any questions about the changes


Bump dependencies

Namely enigma and cfr

Should wait for j16 enigma imo

Indeed, this build doesn't introduce too many new stuff; and enum improvements aren't really needed since now cfr is decompiling enums as regular classes somehow


Parts Unlimited-ASP.NET-CI pipeline failed

Hi all,
I've created Parts Unlimited-ASP.NET-CI pipeline following lab instruction, however after running I see the following errors:
Error: The process 'D:\a_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.195.0\Modules\DTAExecutionHost.exe' failed with exit code 1
##[warning]Vstest failed with error. Check logs for failures. There might be failed tests.
##[error]Error: The process 'D:\a_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.195.0\Modules\DTAExecutionHost.exe' failed with exit code 1
##[error]Vstest failed with error. Check logs for failures. There might be failed tests.
Thanks in advance,
Raquel

Same problem here.
Seems a problem with Castle.Core.dll version.
Error Message:
Test method PartsUnlimited.UnitTests.Controllers.OrdersControllerTests.Order_DetailWithOrderDetails threw exception:
System.TypeInitializationException: The type initializer for 'Moq.Mock`1' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Moq.Proxy.CastleProxyFactory' threw an exception. ---> System.IO.FileLoadException: Could not load file or assembly 'Castle.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
packages.config points to 4.0.0, not to <IP_ADDRESS>

app.config and PartsUnlimited.UnitTests.csproj refer also to 4.0, but publicKeyToken matches the one in error for 3.0
app.config:

PartsUnlimited.UnitTests.csproj

Thanks.

Build works from commit 816d9487 up to 5f9404c8 in master branch, all using vs2017-win2016 agent (windows-2019 fails).
From that point, build fails.

Facing the same issue. @juanandmsft.. unable to find a solution..

Three options here.
Quickest one is run the pipeline specifying what commit to use for build.

Second option is overwriting latest code with one in commit 5f9404c8.
And third option will be fixing code in master branch based on commit 5f9404c8.
Hope it helps.


[AUS] upgrade policy fast path

speed up overwrites for cluster upgrades to reach a certain version level.
based on design doc https://gitlab.cee.redhat.com/service/app-interface/-/merge_requests/100465
part of SDE-3696

/retest


Update PlacesDetailPanel with more flexible styling

In this PR

Edits the CSS of the core-data/PlacesDetailPanel component to remove the absolute positioning and fixed width;
Adds user stories showing use of the component inside a semantic-ui-react Sidebar component and Modal component

Notes
Unsure about the best way to structure this change; as is, it's sort of a breaking change in that existing uses of the panel as a sidebar specifically will need to be updated to actually wrap the component in a sidebar other custom styled component to recover the same behavior. Alternatively we could force backward compatibility by passing some sort of optional modal flag as a prop and only apply the updated CSS if that flag is applied, but that seems significantly less elegant. Open to thoughts!

Added some Tailwind examples to the Storybook page. @dleadbetter

Closing and reopening to try to get GitHub to update the file diffs.


[UNDERTOW-2109] The large file is in unexpected location on JDK17

UNDERTOW-2109 create large file in expected location

thanks @rmartinc  and @kstekovi , this PR will soon be merged


refactor: improve logic to calculate bitcoin fee

Try out this version of the Hiro Wallet - download extension builds.

WIP
This PR improves the fee estimation. Previously, we used coinselect to handle utxo selection and fees. This library is outdated and doesn't consider the varying output script sizes of different address types.
To fix this, and yield more accurate fee suggestions, a transaction size estimator is used. I copied this, and converted to TypeScript from a fork of this project https://jlopp.github.io/bitcoin-transaction-size-calculator/. This is done by using a naive "biggest first" model for selecting UTXOs, and using better size esimations to derive a fee.
I've moved to using the mempool.space API which seems to give the most realistic fee rates.

Looks good @kyranjamie, I like both of the changes you are making here. It is much more clear how the coin selection is happening and feels much more in our control to debug if needed. Also, like the fee api change. I am getting stuff when I click on Preview with the current build...

I am getting stuff when I click on Preview with the current build...

Think this was my error in the amount field not realizing what I entered. Just wasn't giving me an insufficient balance warning. Haha.


MidiEvent.Time isn't representing the "Absolute Time"

https://stackoverflow.com/questions/23070510/how-to-get-exact-time-of-a-midi-event
I don't know much to MIDI files but I can confirm that Time in MidiEvent.Time is not the correct time.

The time that is stored in the MIDI file is measured in an abstract time unit known as the "tick" and unless there is a bug MidiEvent.Time should be giving you the exact tick in which the event occurs.
Isn't that what you're getting?
If you're talking about "clock" time, that data is not stored in the MIDI file, it needs to be calculated after loading the entire file, based on the TicksPerQuarterNote value, a combination of all Tempo MetaEvents up to the event, and the absolute tick of the event.
Same thing with note length, there is no such thing in a MIDI file. You need to look ahead and find the closest Note Off event on the same channel and with the same note as the Note On event, and subtract the two absolute times to know the duration in ticks.
This project is just a simple parser which reads the MIDI data as close as possible to the original representation, so it doesn't do any extra calculations.
I've considered adding these extra calculations as extensions when I have some time but at the time they're outside the scope of the parser.

foreach (var track in midiFile.Tracks)
        {

            int[] NoteOnWait = new int[256]; //time = [Note]
            foreach (var midiEvent in track.MidiEvents)
            {
                if (midiEvent.MidiEventType == MidiEventType.NoteOn)
                {
                    var time = midiEvent.Time;
                    var channel = midiEvent.Channel;
                    var note = midiEvent.Note;
                    var velocity = midiEvent.Velocity;
                    NoteOnWait[note] = time;
                }

                if (midiEvent.MidiEventType == MidiEventType.NoteOff)
                {
                    var time = midiEvent.Time;
                    var channel = midiEvent.Channel;
                    var note = midiEvent.Note;
                    var velocity = midiEvent.Velocity;
                    var length = time - NoteOnWait[note];

                    // And Some Code here:
                    // Visualize objects:
                    // Object coordinate = (note, NoteOnWait[note]); (x,y)
                    // Size = (x, length)
                }
            }

And here is the results:    (Green is my visualizer)
It seems notes time which inside same beat were very close to each other, while notes time with different beat is opposite.

Thank you for the sample file, I was able to locate the issue, I'll try to update the repository tomorrow after I fix and run some tests.

Actually it was just one line of code... I pushed the fix now, hopefully it works.

Yes, it's fixed. Thank you!


missing the projection logic

https://github.com/vladikk/learning-ddd/blob/ebba3acb2112f346b264944ec2e9340097d69a8c/listings/07-02.cs#L1
only apply methods.
no projection logic which mentioned in the book.

sorry.
I misunderstand your intention.
I can project.


Adding dynesty support (especially to retrievals)

Hi Tomas, I just wanted to open this issue to keep track of our discussion about dynesty support. This isn't very urgent at all, but it would go a long way to help me be more productive with the retrievals I plan to do in the near future (for reasons I describe below).
I hope to start with adding dynesty support for the retrievals and then we can likely take the lessons learned there and add support for the forward modeling (I think that is less important since the nuances of nested sampling aren't really a potential limiting factor in doing the grid interpolation/model comparison).
Some hand wavy reasons for implementing dynesty:

options to do both static nested sampling (effectively reproduces MultiNest) and dynamic nested sampling (effectively reproduces UltraNest).
options to do importance nested sampling
the two above give more flexibility in allowing the user to choose how they'd like to estimate their posterior and to what fidelity
actively developed (so easier to bugfix and maintain as python versions change)
better documented
better multiprocessing support: will enable multiprocessing on a single machine without using mpi, and will enable using mpi across multiple nodes. for instance, at my facility there is only 48 cores per node, and so with mpi + multinest I can only use that many cores. but with schwimmbad and dynesty, i could allocate cores across multiple nodes that follows a single master process on one node (I think?).

The issue with a clean port, e.g. adding a run_dynesty function that is effectively the same as run_multinest except it passes the loglike and prior functions to the dynesty interface right now is that within species.fit.retrieval.run_multinest the loglike_func and prior_func are local objects, functions defined inside run_multinest and not class attributes or global objects. In this way, when attempting to set a pool with dynesty.pool.Pool(npool, loglike_func, prior_func) as pool:, you get an error like
AttributeError: Can't pickle local object 'AtmosphericRetrieval.run_dynesty.<locals>.loglike_func'
and when trying to initialize dynesty on one core dsampler = dynesty.NestedSampler(loglike_func, prior_func,len(self.parameters)), you get an error like
TypeError: AtmosphericRetrieval.run_dynesty.<locals>.prior_func() missing 2 required positional arguments: 'n_dim' and 'n_param'
I've tried to hack something together to show these errors on a dummy branch of my fork, dynesty_branch_2.
I've pseudo-coded / parallel implemented a bigger overhaul in a separate file species.fit.dretrieval.py on a branch of my fork dynesty-retrieval which is my first attempt to solve this by making loglike_func and prior_func attributes of the AtmosphericRetrieval class so that they can be interpreted by dynesty. This of course involves making the variables defined within run_multinest that loglike and prior rely on into class attributes as well, which became something of a mess - I don't intend that code to be the actual strategy of implementation, more like its a sketch book 😅 .
If there's a different way to do this that I've overlooked, however, that doesn't involve such a big change to the structure of the AtmosphericRetrieval class, I'd prefer that. Hence why I've done most of this in pseudo code and in a separate file to start tinkering with. I was able to run a full retrieval on some test data using multiprocessing locally using dynesty by calling AtmosphericRetrieval with dretrieval.py, but I haven't been able to get a mpi implementation to work.
I'm also trying to think through if there is any memory saving way to set up the retrieval across multiple cores, that doesn't involve having to load the opacity tables for each core..., that has been an issue on my cluster. That is definitely out of the scope of this issue but may be possible in the future with the schwimmbad/dynesty architecture this issue could help set up? I am thinking of the main/worker structure (like the mpi-demo.py in schwimmbad) that loads the AtmosphericRetrieval and RadTrans object once, but is able to distribute the calc_flux to workers in the pool. There is probably a reason I am not thinking of that this is not feasible.

Thanks a lot William! Great that you are trying to implement this!
In FitModel, there was a similar issue from what I remember when adding run_ultranest. I had to make the embedded function for the likelihood an actual method of the class. Within run_multinest and run_ultranest, I then added a local function for the likelihood that calls the class method. This should indeed be possible here as well (I think), although I am not sure how straightforward. I can have a look so the code structure can be used for your implementation.
Would really help indeed if the opacity memory could be shared between cores, but I am not sufficiently experienced with multiprocessing to understand what is the best way to do that... Maybe Paul and Evert have put some thought into that?

I have restructured the AtmosphericRetrieval class in the last commit on the main branch (see b2adbcbd623f3951cdcd06bfe0653492af661134).
In run_retrieval you can run the Dynesty sampler, which can use either prior_transform() and lnlike_func(), or lnprior_dynesty() and lnlike_dynesty(). The latter in case anything Dynesty-specific needs to be implemented with the prior/lnlike otherwise these can be removed.
Would this help with your Dynesty implementation?
I am not sure if lnlike_func/lnlike_dynesty can be pickled or if it needs to be moved outside of the class. In that last scenario it would be a bit more work to implement because the attributes should be converted into parameters. But hopefully it works like this 🤞.

Wow! Awesome stuff. I will pull soon and try out later this week ^_^ thanks for entertaining this implementation Tomas!

Hi Tomas - I've implemented an initial run_dynesty on my fork's branch add_run_dynesty that is based on the backtracks implementation. That branch is up to date with commit 3d150aa.
I've tested the various permutations* of the multiprocessing locally to confirm that they at least begin sampling and save the intermediate products. I have a few lines at the end that take the dynesty output results object and saves a retrieval_post_equal_weights.dat file that is equivalent to the output from pymultinest.

== (dynamic bool, n_pool None/int, mpi_pool bool, resume bool)

I'm going to try to test this on my cluster next, I couldn't do more than a few processes with mpi or a multiprocess Pool on my local machine due to memory constraints.
Let me know what you think, and if you'd like me to open a PR for that branch.

Awesome! Good to hear that it is working already!
Would be great if you could create a PR for that 👍

Thanks again for implementing the Dynesty support in AtmosphericRetrieval! Since I had been making some updates in FitModel, I have adapted run_dynesty in there, which was quite straightforward (see 1f02b5a).

Looks great! I had a commit I forgot to push to do something similar, though I hadn't yet documented it. I'll test on my end with some more AF Lep b fits. I think we can close the issue now :).


[MB-5926,MB-5948, MB-5951, MB-6016] Parse/test DTOD response and integrate into GHC planner

Description
This PR expands on the work started in #5508 to connect to the DTOD SOAP API.  At a high level, this PR adds the following:

parses the response from DTOD
adds unit tests that use a mocked DTOD API
integrates DTOD into the GHC planner skeleton from #5501

Reviewer Notes
I ran into several circular dependency problems that I had to work around.
One prevented me from keeping this in the services package (since something else in services already refers back to the route package).  To deal with that one, I moved the DTOD work into the route package itself (we had a similar problem with the RM integration).  This should be OK since the planner is really a service for the entire app.  I think it even makes some of the initialization more straightforward too.
The other prevented me from generating a mock for SoapCaller in the mocks directory because a different mock referred back to the route package already.  To work around this, I created a ghcmocks directory/package instead and placed SoapCaller in it.
If there's another straightforward way to handle either of these, please let me know.  I didn't want to get into a huge refactoring effort in this PR since we may have to refactor unrelated code to fix this without moving DTOD-related code.
Also, I noticed there were some old mocks that were in the pkg/services/mocks directory as I cleaned up one of mine in this PR after the refactor.  I am deleting those as well in this PR.
Setup
The GHC planner is not hooked up anywhere yet.  That is coming in a future story.
You can make server_test and see that the mocked SOAP API works.
To see a real call go through, you could temporarily edit serve.go and add in the following lines after the GHC planner is instantiated:
distance, err := ghcRoutePlanner.Zip5TransitDistance("05030", "05091")
logger.Debug("DTOD distance", zap.Int("distance", distance))

When you rebuild (rm bin\milmove && make server_build) and then run your server (make server_run), you should see a couple of debug-level statements related to distance in the log output.  Change the zips as desired to get different results.
Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-5926, MB-5948, MB-5951, MB-6016

  Generated by :no_entry_sign: dangerJS against d23100e3de7cbf043a74fcfb2d54060059d40f86

After going through the set up steps and re-running my server I get back a distance of 0 for the distance between these zips "05030" and "05091"

Oh, I wonder if you don't have the env.local variables related to DTOD yet.  I just added a note about this to the setup instructions.  See if that fixes the problem.


Validate README.md supported targets with CI

We should investigate if it would be possible to validate that the supported target table is correct
https://github.com/cross-rs/cross#supported-targets

I've created a very rudimentary attempt at this in target_info (only partially working on Android, and works for a few tested musl targets) to auto-generate a table similar to the one in README to compare and validate the information. This might also simplify the validation of the versions in #591.
The use of the script is quite simple (and a wrapper with many targets would be provided to extract info for all targets):
$ export TARGET=aarch64-unknown-linux-musl
$ docker run -e TARGET ghcr.io/cross-rs/"$TARGET":main bash -c "`cat extract_target_info.sh`"
| `aarch64-unknown-linux-musl`         | 1.2.0  | 9.2.0   | ✓   | 5.1.0 |

How this works is it queries the version information from GCC (or Clang), detects if Qemu is present and if so, gets the Qemu version. and determines if the command provided by CXX_$target exists, and if so, says there is C++ support. For libc, it's a bit more complicated, but most libc libraries are executable (especially musl), or have version info attached to them (glibc). For glibc, we might have a library like libc-2.31.so, or glibc 2.31. For musl, we can just execute the libc (using qemu if required) and extract  the version info.
This is then formatted to the desired output.

Awesome!
Something I just realised, we should/could label the images with the different version

That might be easier. I can get the libc versions for everything except FreeBSD pretty easily, and FreeBSD isn't hard, but the libc reported in the README is the base release (which is quite different than the symbol libc version).
For example, for the current base release of 12.3, we would get FBSD_1.5 based on Symbol Versioning.
So for this and Android, I'm not sure what the correct output should be. For FreeBSD, is the correct libc version 12.3 or 1.5? And for Android, I'm currently reporting the LLVM version, but should I report the NDK version?


licensing - total dependency graph 0 on pull-request workflow

Describe the bug
When the policy-is-code Action is run on a pull-request (scanning the non-default branch), License checking does not work because the dependency graph includes 0 dependencies.
When the action is run on the default branch, License checking works.
To Reproduce
Workflow
jobs:
  compliance:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
      - name: Advance Security Policy as Code
        uses<EMAIL_ADDRESS>        with:
          policy-path: .github/policies/custom.yaml
          token: ${{ secrets.GITHUB_TOKEN }}
          argvs: "--disable-dependabot --disable-secret-scanning --disable-code-scanning --display"

Policy:
name: custom

# Dependency Licensing Alerts
licensing:
  conditions:
    ids:
      - GPL-*
      - LGPL-*
      - AGPL-*

  warnings:
    # Warning is the dependency isn't known
    ids:
      - Other
      - NA

Open a PR and check the output of the action.
Expected behavior
Dependency Graph should be calculated with >0 dependencies.
Screenshots
action on PR (see https://github.com/it-at-m/appswitcher-vue/actions/runs/5711495958/job/15473216682)

action on main branch (see https://github.com/it-at-m/appswitcher-vue/actions/runs/5711336691/job/15472815170)

Additional context
I noticed Dependencies from Pull Request in the action log - does this mean the scan on a PR detects "changed dependencies" and therefore just scans these dependencies?

@GeekMasher thanks for looking into this issue!

can you please confirm you have enabled GitHub Advanced Security on this repository (api used)?

I did not find a specific setting for "GitHub Advanced Security" in repo settings, I suspect "Dependency graph" is needed? This is enabled.

Maybe this is a problem on pull request workflows because the GITHUB_TOKEN maybe has no sufficient rights? However some error handling or logging would be nice, as you mentioned ;)

I have created this discussion for now to help with this https://github.com/advanced-security/policy-as-code/discussions/56

@GeekMasher I added the permission (see https://github.com/it-at-m/appswitcher-vue/pull/74/files ) - the Action then reported 1 "Total dependencies in graph" -> this was advanced-security/policy-as-code, which was also updated in this PR (2.4.0 -> 2.4.1)
So still looks to me as only "changed" dependencies are analyzed? This would be fine IMHO.

https://github.com/it-at-m/appswitcher-vue/actions/runs/5718094968/job/15493206133

@eidottermihi You are correct, the policy-as-code looks at the diff in the PR versus all the dependencies in a PR.
https://github.com/GeekMasher/ghastoolkit/blob/main/src/ghastoolkit/octokit/dependencygraph.py#L120-L121
Glad to see it's working now, this will show warnings next time when the feature / permissions are missing.


DO NOT MERGE: Show preserved triple slash references in diagnostics for top200 analysis

Counterpart of #57569

@typescript-bot test top200

@typescript-bot test top400
@typescript-bot user test this

The fuels-ts one emits a directive into the published package which doesn't actually exist. https://unpkg.com/browse/<EMAIL_ADDRESS>

The jupyterlab one doesn't seem intentional, in that the package only dev deps on jest and there's a comment that says it's there for another reason. (I think normally such a reference would be elided if it were actually used elsewhere?)
In any case, these results are very good.


Add authentication and authorization

Issue
Link your PR to an issue
Fixes #___
Description
Add authentication and authorization. This PR adds auth support but stubs out the actual auth implementation. Supports JWT bearer tokens and form based auth, along with a few administrative functions to add users and change passwords. It also includes examples on the user api's demonstrating how to authorize endpoints based on scopes but it does not add that functionality to all of the endpoints in the api.
Testing

call auth/login with the default credentials
verify you can call /user/me
create a new user as an admin with the voter or some other scope
login as the new user and try to create a user, expect that it fails (since you aren't an admin)

@SteveMaier-IRT I completed the updates to the linting to get this pull request to pass.


Add option to open image in different orientation

Currently, manual_correction.py opens the input image and label in the original image orientation. For example, if the image is AIL, it will be opened in AIL orientation in FSLeyes. This might not be ideal, for instance, for rootlets corrections, as it is "easier" to correct the rootlets on an image with RPI orientation.
Idea: add a new input arg to the script, e.g., -orientation allowing to open the input image and label in an orientation specified by the user. The script could fetch the original orientation (e.g., using sct_image -i ${1} -header | grep -E qform_[xyz] | awk '{printf "%s", substr($2, 1, 1)}'), reorient the image to the intended orientation (sct_image), open FSLeyes, and then reorient back to the original orientation.

Implemented in #100


⚠ Samsung has degraded performance

In 841cc04, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2385 ms

Resolved: Samsung performance has improved in 1afc6d2.


eye disease detection

Description
The goal of this project is to create a model that accurately identifies and categorizes eye diseases from medical images. This project aims to achieve objectives such as disease identification, accuracy, early detection, efficiency, real-world applicability, generalization, ethical compliance, interpretability, continual learning, and validation.
Fixes #359
Type of change

[x] Added a new machine learning frameworks, libraries or software.
[ ] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

@sanjay-kv can you plz accept PR


A program to reproduce the error.
https://play.golang.org/p/mHJcF72uF9J
What did you see instead?
It gives error as below :-

# command-line-arguments
./3.go:11:23: internal compiler error: 'main': schedule does not include all values in block b19

Please file a bug report including a short program that triggers the error.
https://golang.org/issue/new

It looks like go 1.12 hits the same internal compiler error as go 1.13, but with go version devel +3eab754cd0 Thu Feb 13 19:49:45 2020 +0000 darwin/amd64, the program compiles and runs successfully.

Thank you for the report @amarjeetanandsingh and welcome to the Go project! Thank you @mark-rushakoff for the initial investigation.
Indeed, as @mark-rushakoff confirmed, the problem starts with Go1.12 and from my investigation, it seems to have been caused by https://github.com/golang/go/commit/f062f48c1f8862ff0ef7baccf563497339129743 aka CL 165858 (/cc @randall77 @dr2chase) in the short circuiting logic. It then seems to have been fixed by @josharian's https://github.com/golang/go/commit/52ae04fdfc66664b327a4cb4057e339f132de8f9 aka CL 178197 for Go1.14 aka Go tip so it is already fixed. @amarjeetanandsingh, in the meantime please use Go1.14beta1
https://golang.org/dl/#unstable
go get golang.org/dl/go1.14rc1

Perhaps we might need some backports?

I don't know for sure, but it seems likely to me that CL 178197 might have fixed this particular incident, but that there may yet be similar cases lurking. We should look to see whether there's an independent fix, not least because we shouldn't backport CL 178197.
I'm out of time for the moment, but here's a partially minimized reproduction:
package main

func main() {
	var n, a, b int64
	for i := int64(2); i < 10; i++ {
		for j := i; j < 10; j++ {
			if ((n % (i * j)) == 0) && (j > 1 && (n/(i*j)) == 1) {
				a, b = i, 0
				a = n / (i * j)
			}
		}
	}

	if a != b && a != n {
		println("YES")
	}
}

From my first look, it appears that the problem is with CSEing a Select0. When CSE moves a tuple generator to a new block it is supposed to move all selectors along with it. It did so, but somehow there was still a phi value using the old selector as an arg. The old selector thus doesn't get deadcoded, causing scheduling to fail.
That's as far as I've gotten, and as far as I'm likely to get in the very near term.
cc @cherrymui @randall77


Update fog version pin, formatting cleanup

Fog v2 is nearing release, and the current fog version pin
for this gem would cause an unexpected upgrade.  Also removed
the version pin on chef that was < 12 and other small formatting
changes.

+1 looks good to me


Wrong switch type for Generic example in README (CON-1323)

Describe the bug
Wrong switch type for Generic example in README.
The documentation indicates that by default latching switch is enabled:
https://github.com/espressif/esp-matter/blob/22fad1243ba0121845c8eff648eb57f0a99a13f5/examples/generic_switch/README.md?plain=1#L80
But in the project file it's the other way around:
https://github.com/espressif/esp-matter/blob/22fad1243ba0121845c8eff648eb57f0a99a13f5/examples/generic_switch/main/Kconfig.projbuild#L5
Environment

ESP-Matter Commit Id: 22fad1243ba0121845c8eff648eb57f0a99a13f5

ESP-IDF Commit Id: ea679d2dc6

SoC (eg: ESP32 or ESP32-C3): ESP32-C6

Device Logs (Please attach the log file):

Host Machine OS:

Host Machine Python version:

Commissioner app and versions if present:

Home hub app and versions if present:

Commissioner's logs if present:

@lboue , thanks for reporting the issue. We have added the fix.

Thansk. I think it would also be useful to add a few lines explaining how to change the type with the idf.py menuconfig command.
This would avoid wasting time searching through the code as I had to do.


404 at /docker-for-mac/engine/security/trust.md

I found a broken link : https://docs.docker.com/docker-for-mac/engine/security/trust.md
I arrived on this page through: https://docs.docker.com/docker-for-mac/release-notes/

Thanks for sharing this issue. The issue appears to be no longer applicable. If you still encounter the issue, please let us know.

This is still an issue. See screenshot.
On Tue, Apr 26, 2022 at 5:58 PM Craig Osterhout @.***>
wrote:

Thanks for sharing this issue. The issue appears to be no longer
applicable. If you still encounter the issue, please let us know.
—
Reply to this email directly, view it on GitHub
https://github.com/docker/docker.github.io/issues/13014#issuecomment-1110290613,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATJJT57P5DVJEPJINMT5VLVHBRH3ANCNFSM46VHCGFA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Do not go gentle into that good night,
Rage, rage against the dying of the light.

Dylan Thomas

Looks like the screenshot didn't make it to github  (probably doesn't work when using e-mail to reply)
The https://docs.docker.com/docker-for-mac/engine/security/trust/ URL is incorrect (so if that shows a 404, that's expected; correct URL is https://docs.docker.com/engine/security/trust/)
Can you provide details which link on https://docs.docker.com/docker-for-mac/release-notes/ brought you to that  URL?

Looking at the release page, and when I originally opened this ticket, I'd say it's fallen off and probably is no longer an issue after all. The last entry is from August, 2021 and this ticket was back in June 2021.

Looking at the release page, and when I originally opened this ticket, I'd say it's fallen off and probably is no longer an issue after all. The last entry is from August, 2021 and this ticket was back in June 2021.

Thanks for checking!


license

hello @smeucci thanks for writing this code and the paper - really usefull.
under which license is this distributed? Is this MIT licensed. I would like to incorporate it at https://github.com/DIGI-VUB/image.textlinedetector.
many thanks!

Hi @jwijffels, i have added a MIT license to the repository.

Thanks!


Call kdotool rapidly will make journalctl generating huge amount of garbage data.

Since KWin decided to use journalctl to record script output, if we want to record mouse locaion rapidly (e.g., using /dev/uinput to simulate a absolute mouse move), the log file blows up to hundered MBs.
I wonder if there is some alternative approaches that is feasable. For example, running a backend with root permissions that could obtain kwin's mouse location with libc::process_vm_readv.
I performed some attempt, and got this
Feel free to copy the code into your project:)

I'll change it to only generate log when --debug is specified. Hopefully that helps.


toArray using maps if exists

Looking to find a way to find this feature on Mappable trait.
Usage is for override toArray and get the columns as they where defined on $maps array.
public function toArray()
{
    $values = $this->attributesToArray();
    if (isset($this->maps)) {
        $flip = [];
        $flip = array_flip($this->maps);
        foreach ($values as $key => $value) {
            if (isset($flip[$key])) {
                $values[$flip[$key]] = $value;
                unset($values[$key]);
            }
        }
    }
    return array_merge($values, $this->relationsToArray());
}

I build this part code to address this return a I was expecting of return.
This feature aready exists and I don't know how to use?
Thanks! This Mappable it's awesome!

Is there anything I should address?

He seemed to have the same issue as I do.
After filling a model I cant get the Attributes as a bulk when a map was set.


Hand model looks very bad

I made a demo according to the official website https://jorge-jgnz94.gitbook.io/hptk/setup, but the hands in the scene are always incomplete.

Render queue is wrong on standard Skin_Master and Skin_Slave materials. Skin_Master should be 3000 (Transparent) and Skin_Slave should be 2000 (Geometry) so they don't overlap. I'll commit a fix for this issue

9ca954e076e61806a5f3e6f13f85e5876feb855b


[SPARK-46812][PYTHON][TESTS][FOLLOWUP] Skip pandas-required tests if pandas is not available

What changes were proposed in this pull request?
This is a follow-up of the followings to skip pandas-related tests if pandas is not available.

#44852
#45232

Why are the changes needed?
pandas is an optional dependency. We had better skip it without causing failures.
To recover the PyPy 3.8 CI,

https://github.com/apache/spark/actions/runs/8541011879/job/23421483071

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually test.
$ python/run-tests --modules=pyspark-resource --parallelism=1 --python-executables=python3.10
Running PySpark tests. Output is in /Users/dongjoon/APACHE/spark-merge/python/unit-tests.log
Will test against the following Python executables: ['python3.10']
Will test the following Python modules: ['pyspark-resource']
python3.10 python_implementation is CPython
python3.10 version is: Python 3.10.13
Starting test(python3.10): pyspark.resource.profile (temp output: /Users/dongjoon/APACHE/spark-merge/python/target/021bc7bb-242f-4cb4-8584-11ed6e711f78/python3.10__pyspark.resource.profile__jn89f1hh.log)
Finished test(python3.10): pyspark.resource.profile (1s)
Starting test(python3.10): pyspark.resource.tests.test_connect_resources (temp output: /Users/dongjoon/APACHE/spark-merge/python/target/244d6c6f-8799-4a2a-b7a7-20d7c50d643d/python3.10__pyspark.resource.tests.test_connect_resources__5ta1tf6e.log)
Finished test(python3.10): pyspark.resource.tests.test_connect_resources (0s) ... 1 tests were skipped
Starting test(python3.10): pyspark.resource.tests.test_resources (temp output: /Users/dongjoon/APACHE/spark-merge/python/target/671e7afa-e764-443f-bc40-7e940d7342ea/python3.10__pyspark.resource.tests.test_resources__lhbp6y5f.log)
Finished test(python3.10): pyspark.resource.tests.test_resources (2s) ... 1 tests were skipped
Tests passed in 4 seconds

Skipped tests in pyspark.resource.tests.test_connect_resources with python3.10:
      test_profile_before_sc_for_connect (pyspark.resource.tests.test_connect_resources.ResourceProfileTests) ... skip (0.005s)

Skipped tests in pyspark.resource.tests.test_resources with python3.10:
      test_profile_before_sc_for_sql (pyspark.resource.tests.test_resources.ResourceProfileTests) ... skip (0.001s)

Was this patch authored or co-authored using generative AI tooling?
No.

Thank you, @HyukjinKwon .

Merged to master.


Biweekly Contest 115 - Ranks are slightly off

Biweekly Contest 115 ranks are slightly off
All users at below link have ranks between 3326 to 3350
https://leetcode.com/contest/biweekly-contest-115/ranking/134/
However, take any user, and check at below link, it shows ranks to have between 4130 to 4157
https://lccn.lbao.site/predicted/biweekly-contest-115
please look into this when possible @baoliay2008

Hi, leetcode.com didn't sync with leetcode.cn, and if, when counting users from the CN region, it should be correct.


Find out design for Pirate mode

It would be nice to have using AutoOffload.Pirate take over mul!, *, etc. to check sizes and then fallback to the original method if it doesn't satisfy the heuristics for accelerator speedups. However, making that not fall into an infinite loop seems a little tricky.

I would argue that using a context-based approach (a la Cassette) is an overall better and safer experience for the user and packages which want this functionality. It is easier to disable if you know offload will be problematic, and with the help of a REPL mode or hook into IJulia, should be easy enough to enable for an entire session.


Smoke Tests

[ ] Produce a tool (Codename SMOKE) which launches a testnet on a schedule.
[ ] Produce a tool (Codename MONSTER) that can be used to run the integration test suite against a live network

@yourbuddyconner - can you add the exit criteria to the description?


For a multi-arch image is there a way to specify which architecture to dive?

Have a multi arch image and trying to debug some image differences per arch.  Running dive on amd64 but want to check out an arm64 image filesystem

I just found workaround for my image I wanted to check.
I cannot dive but actually I cannot also docker pull:
$ dive ghcr.io/mkyc/docker-multitool:v0.0.2-base
... boring ...
no matching manifest for linux/arm64/v8 in the manifest list entries
cannot fetch image
exit status 1
$ docker pull ghcr.io/mkyc/docker-multitool:v0.0.2-base
v0.0.2-base: Pulling from mkyc/docker-multitool
... boring ...
no matching manifest for linux/arm64/v8 in the manifest list entries

but if I docker pull with platform I need, then I can dive:
$ docker pull ghcr.io/mkyc/docker-multitool:v0.0.2-base --platform amd64
v0.0.2-base: Pulling from mkyc/docker-multitool
8a49fdb3b6a5: Pull complete
... boring ...
$ dive ghcr.io/mkyc/docker-multitool:v0.0.2-base
Image Source: docker://ghcr.io/mkyc/docker-multitool:v0.0.2-base
Fetching image... (this can take a while for large images)
Analyzing image...
Building cache...


Links to examples are broken

Need to add the XML ID to converted examples, similarly to the way it was done for images in issue #10.

Fixed by commit d9c459f


fix(cli-service): compatible with webpackServe.static option

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:
Fixes #7145

AppVeyor build failed


feat: remove the restriction that luogu can only query the first two …

remove the restriction and optimize for latest submission time on luogu platform.

missing error handle, should set upper limit based on page size and total

It turns out there are no error handling measures at past, and in fact, non-existent pages will not appear when the number of pages is greater than the actual value.

I understand your implementation now, it might be better to explicitly exit when the oldest record is encountered


Search in all folders

Please modify the search function to allow it to search inside all the folders.
This would make a fantastic addition to the premium version

see #73


Better error when submitting order with out of stock product

Issue: https://github.com/RailsEventStore/ecommerce/issues/375
Before when a product was added to an order and subsequently went out of stock before submission, the system incorrectly showed a success message  "Your order is being submitted" while leaving the order in draft status. Now it shows "Order can not be submitted! Product not available in requested quantity!".

There are a lot of changes. I will try to explain all of them in the comments below.
The implementation for the Result object was taken from this presentation: https://www.icloud.com/keynote/0x2bfAdGek3Eg-I_2kIomD-6g#Controller_refactoring (it lacks notes but you can check slides 7 and 17 for "before" and "after")

There are many changes in this pull request which I would like to debate separately, but as a whole I think it's ready to be merged.

Let's change the Result pattern to exceptions - we already use exceptions here a lot and we could save one pattern
Let's separate the service objects even if they are identical
No need for inheritance in service objects
process publishing events - let's have it for now, we will see how it feels in the code in the longer run, might be refactored later


Fix typo

Hi @federicobond, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Hi @federicobond, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


Update documentation and setup.py for alpha release

Signed-off-by: David Plowman<EMAIL_ADDRESS>

@davidplowman Thanks, just a couple of questions:
Should numpy not be installed from apt, as it takes quite a while to compile I thought.  I guess the reason for not doing that though is due to - https://github.com/raspberrypi/picamera2/issues/116 ?
I assume we're not supporting the OS prior to bullseye then, which uses python 3.7?
Cheers

@davidplowman Thanks, just a couple of questions:
Should numpy not be installed from apt, as it takes quite a while to compile I thought. I guess the reason for not doing that though is due to - #116 ?

Yes exactly. It's been commented on in the forums as well. Maybe once we do another full Bullseye update we might be able to get rid of it.

I assume we're not supporting the OS prior to bullseye then, which uses python 3.7?

Yes, also correct. We don't update libcamera packages on Buster any more so basically everyone needs to be on Bullseye.
Thanks!

Cheers

Makes sense, will merge now then :)


soroban-cli: value overhaul update - strval json/xdr parsing/serialization

What ?
soroban-cli: strval json/xdr parsing/serialization
Epic
https://github.com/stellar/soroban-tools/issues/471

Looking into the changes made to XDR, updating will result in simpler code. However, I estimate that the refactor would take several days, since ScVal is used in 9 files.  The biggest change being JSON --> ScVal and ScVal --> JSON

This is done.  The types are that useful for contract devs but are available now.

This is done. The types are that useful for contract devs but are available now.

great


[6.0] Allow captures in lookahead and atomic groups

Explanation: This resolves an issue where matching a pattern that includes a capture group inside a positive lookahead or an atomic group results in a runtime error.
Scope: All the changes are internal implementation within the _StringProcessing module.
Issue: rdar://126009544
Original PR: #723
Risk: Low. There's no API or ABI impact of this change.
Testing: This change adds tests that verify that the previously failing patterns are working correctly, and continues to pass the existing compilation and pattern-matching tests.
Reviewer: @stephentyrone

Cherry pick to swift/release/6.0 of #723.

@swift-ci Please test


[Event Change Request] Report 499 Delete Invoiced Purch. Orders - event OnAfterSetPurchLineFilters

Describe the request
We would like IncludeSender added to the following event.
Original:
[IntegrationEvent(false, false)]
local procedure OnAfterSetPurchLineFilters(var PurchaseLine: Record "Purchase Line")
begin
end;

Change:
[IntegrationEvent(true, false)]  // <-- IncludeSender true
local procedure OnAfterSetPurchLineFilters(var PurchaseLine: Record "Purchase Line")
begin
end;

Additional context
to get variables from our reportextension the publisher has to be set to IncludeSender true
Internal work item: AB#523675

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 18286.


fix restconfig debug & boolean handling

The example restconfig is misleading because it has the JSON string
"True" instead of the boolean value true (without quotes).  When
someone tries setting it to "False" it won't work because that's a
valid JSON string that python evaluates to true in places that say
"if config['debug'] ..."
Also fix a typo where the debug value is initialized from the
'insecure' keyword argument.

I was wondering that it was complaining about insecure connections when I had explicitly allowed it ;-)


Feature Management Deny List

Description
This adds the feature of disabling the Targeting Filter for a specific set of users or groups. This is currently only supported via local configuration, the full value of the feature flag using the targeting filter will need to be I the local file in order for it to be loaded..
All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[X] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
spring-cloud-azure-feature-management


Tensorflow looks for wrong libcupti.so version

OS: Ubuntu 16.04
*TensorFlow installed from: source
TensorFlow version: 1.1.0-rc2
Bazel version (if compiling from source): 0.4.5
CUDA/cuDNN version: 8.0/6.0
GPU Model and Memory: NVIDIA GTX 1060, 6 GB RAM
Exact command to reproduce:

MNIST examples works fine, bute MNIST example with summaries crashes with:
(tensorflow) stefano@stefano-linux:~/Dokumente/Programming/Python/TensorflowCoreTutorial$ /home/stefano/tensorflow/bin/python3 /home/stefano/Dokumente/Programming/Python/TensorflowCoreTutorial/src/mnist_with_summaries.py
Extracting /home/stefano/Dokumente/Programming/Python/MNIST/train-images-idx3-ubyte.gz
Extracting /home/stefano/Dokumente/Programming/Python/MNIST/train-labels-idx1-ubyte.gz
Extracting /home/stefano/Dokumente/Programming/Python/MNIST/t10k-images-idx3-ubyte.gz
Extracting /home/stefano/Dokumente/Programming/Python/MNIST/t10k-labels-idx1-ubyte.gz
2017-04-20 19:16:15.388639: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:901] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2017-04-20 19:16:15.389019: I tensorflow/core/common_runtime/gpu/gpu_device.cc:887] Found device 0 with properties:
name: GeForce GTX 1060 6GB
major: 6 minor: 1 memoryClockRate (GHz) 1.7085
pciBusID 0000:22:00.0
Total memory: 5.93GiB
Free memory: 4.97GiB
2017-04-20 19:16:15.389036: I tensorflow/core/common_runtime/gpu/gpu_device.cc:908] DMA: 0
2017-04-20 19:16:15.389042: I tensorflow/core/common_runtime/gpu/gpu_device.cc:918] 0:   Y
2017-04-20 19:16:15.389055: I tensorflow/core/common_runtime/gpu/gpu_device.cc:977] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX 1060 6GB, pci bus id: 0000:22:00.0)
Accuracy at step 0: 0.0981
Accuracy at step 10: 0.7258
Accuracy at step 20: 0.8151
Accuracy at step 30: 0.8572
Accuracy at step 40: 0.879
Accuracy at step 50: 0.8949
Accuracy at step 60: 0.9052
Accuracy at step 70: 0.9058
Accuracy at step 80: 0.915
Accuracy at step 90: 0.9137
2017-04-20 19:16:20.708545: I tensorflow/stream_executor/dso_loader.cc:129] Couldn't open CUDA library libcupti.so.8.0. LD_LIBRARY_PATH: /usr/local/lib:/usr/local/cuda/lib64:/usr/lib/x86_64-linux-gnu:/usr/lib/nvidia-375
2017-04-20 19:16:20.708600: F tensorflow/core/platform/default/gpu/cupti_wrapper.cc:59] Non-OK-status: ::tensorflow::Env::Default()->GetSymbolFromLibrary( GetDsoHandle(), kName, &f) status: Not found: /usr/local/lib/python3.5/dist-packages/tensorfl
ow/python/_pywrap_tensorflow_internal.so: undefined symbol: cuptiActivityRegisterCallbackscould not find cuptiActivityRegisterCallbacksin libcupti DSO

source code:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/tutorials/mnist/mnist_with_summaries.py
Problem is, that tensorflow looks for libcupti.so.8.0, but only libcupti.so.7.5 is installed:
stefano@stefano-linux:~$ ls /usr/lib/x86_64-linux-gnu | grep libcupti*
libcupti.so
libcupti.so.7.5
libcupti.so.7.5.18

I installed libcupti like described in the Install section on the Tensorflow website:
sudo apt-get install libcupti-dev

libcupti-dev 8.0 is not available for Ubuntu 16.04.

It looks for DSO_CUDA_VERSION which is the one you built it for.

Yes, I build it for CUDA 8.0. CUDA 8.0 is available for Ubuntu 16.04, but libcupti-dev is only available in version 7.5 for Ubuntu 16.04.
Do I have to install libcupti-dev 8.0 somehow?

@yifeif @jart we set the DSO_CUDA_VERSION from the CUDA lib, but apparently the profiler tools can have a different version. (the DSO_CUDA_VERSION is used to load both cuda lib and cupti). Since ubuntu 16.04 is the primary version for us, it should work out of the box. Should we configure to split the versions?

For everyone who has the same issue:
First download the libcupti8.0 debian package and install it:
http://packages.ubuntu.com/yakkety/amd64/libcupti8.0/download
Afterwards download libcupti-dev8.0 debian package in order to install it:
https://ubuntu.pkgs.org/16.10/ubuntu-multiverse-amd64/libcupti-dev_8.0.44-0ubuntu1_amd64.deb.html
This should solve this issue. Of course it would be still better if everything would work out of the box.

Would anyone happen to know where someone not running a Debian derivative can get the source for libcupti?

Looks like @StefanoD was able to find the resolution to this issue.
For posterity, You have to have the same version of CUDA and libcupti on your system. Latest version of libcupti or cuda may not be on debian repositories yet, so you may need to download these from nvidia, or more recent ubuntu distribution's repositories.

libcupti is available in Ubuntu 16.04 xenial only for CUDA 7.5, not CUDA 8. We can use deb packages from Ubuntu zesty repo:
wget http://cz.archive.ubuntu.com/ubuntu/pool/multiverse/n/nvidia-cuda-toolkit/libcupti8.0_8.0.44-3_amd64.deb
wget http://cz.archive.ubuntu.com/ubuntu/pool/multiverse/n/nvidia-cuda-toolkit/libcupti-dev_8.0.44-3_amd64.deb
sudo dpkg -i libcupti8.0_8.0.44-3_amd64.deb libcupti-dev_8.0.44-3_amd64.deb

It can be tested eg. by the scripts in https://medium.com/towards-data-science/howto-profile-tensorflow-1a49fb18073d.
[...]
2017-08-22 16:17:42.714397: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1045] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GeForce GTX 980 Ti, pci bus id: 0000:01:00.0)
2017-08-22 16:17:42.740833: I tensorflow/stream_executor/dso_loader.cc:139] successfully opened CUDA library libcupti.so.8.0 locally

Just adding another error string so this will turn up in search for people in the future:
2017-12-20 18:18:50.156691: F ./tensorflow/stream_executor/lib/statusor.h:212] Non-OK-status: status_ status: Failed precondition: could not dlopen DSO: libcupti.so.8.0; dlerror: libcupti.so.8.0: cannot open shared object file: No such file or directory


MongoDB Database for SpotifyAPI data

The implementation of jsontools and functions to add spotify api data should be edited and tweaked for mongodb database.
Installation and making a mongodb database

The insertion of track, album and artist is done successfully. --> next step is to change the Spotify API functionalities to store real data into it!

This Issue will be closed, but another issue will be created following up on this step --> Issue

Closed


Difference version repo and npm

Hi,
I have a problem when i install cordova plugin by npm not load the lastest changes, in this merge https://github.com/arnesson/cordova-plugin-firebase/commit/e132d7c55e615f0ff68757e0463741cfbd1e8246
Then I view the plugin package version and it's the same version. Why is it?

use 0.1.19


Delete an Images from MultipleImage Input Type return 500 internal server error

Laravel Version: 5.4.10
Voyager Version: 0.11.7
PHP Version: 7.0.14
Database Driver & Version: MYSQL 5.7.17
Description:
When I try to delete one of my multiple images input type. It does not do anything and just response with 500 internal server error.
Tried to look at the network call and it return 500 with
{data: {status: 500, message: "Trying to get property of non-object"}}

help @sikhub

Me too. Need help!

Labels: bug

It's been fixed on the latest version.
@fletch3555 maybe can close this alrdy.
thank you


Added note as per JAVA-3530

Thanks for the feedback, Jeff. I've tried to integrate the changes. What do you think?

Looks good.  But we've just merged the 4.x branch into master, so this will no longer rebase cleanly (the async docs are gone, and reactive streams docs have been added).  Up to you whether you want to rebase this on master or have us take care of it.

I have created a pull request to merge these changes into master.
https://github.com/jstewart-mongo/mongo-java-driver/pull/82

https://github.com/jstewart-mongo/mongo-java-driver/pull/82 has been merged, so closing this one.


Update vsphere tutorial to reflect non-free requirement

The guide updated in this commit does not work for the free version of ESXi due to the fact that any write operation fails with the error message "Current license or ESXi version prohibits execution of the requested operation."  See http://www.doublecloud.org/2011/01/free-esxi-and-apicli-support/ for discussion on the limitations of vSphere's API.

I signed it!

Thanks @nullstyle!


nms_cpu.py wrong

xx2 = np.maximum(x2[i], x2[order[1:]])
yy2 = np.maximum(y2[i], y2[order[1:]])
should be
xx2 = np.minimum(x2[i], x2[order[1:]])
yy2 = np.minimum(y2[i], y2[order[1:]])

I also have this doubts.Is there anything  special here?why is there no problem with the final result ?

@WHCer
Hello，can changing the code improve the result?Is there something different after the change?

While seems the code is not used...... Thus, no effect to result.

@WHCer thank you


pull request #764 Ignore submodules dirty in prompt info caused bug

Hi all!,
Git versions before 1.7.2 don't support the '--ignore-submodules'  syntax
ref: http://article.gmane.org/gmane.linux.kernel/1007412
It results in an error message.
As a result, no star appears next to the branch name if there are uncommitted changes
The latest pre-packaged version currently available for centos 6.2 is 1.7.1
A check should be added so that the old syntax is used for git versions before 1.7.2
I'm still new to git, but I'll make a pull request for this as soon as I learn how it's done. I'd be very thankful if someone beats me to it!
-Aleksey
P.S.: Thanks for making this great piece of software!!!

I have already sumited a pull req for this. #872.

Hi Scialex,
I wish I had seen that before. Maybe you could still use some of what I wrote?
my git_compare_version() routine is similar to your get_is_legacy_git() routine, but doesn't use external function calls and will check against any version, not just 1.7.2.
I also accomplish what you do in parse_legacy_git_dirty() and parse_recent_git_dirty() in only three extra lines in parse_git_dirty()
It didn't occur to me to unset some of these functions after they will no longer be used or save the value into a variable. Yours is no doubt faster at this point because of that. (Very willing to make those changes!)
I'm still very new to zsh, git, and github so any and all criticisms are welcome!
-Aleksey


Basic audio system

Description
Things I think I did correctly:

Functionality for all the bullet points from https://github.com/jeffcampbellmakesgames/UnityStarterTemplate/issues/7
Included a serializable dictionary library (I found the one in SuperUnityBuild but it didn't seem to work on a scriptable object)
Scriptable Object for audio settings / references to audioclips

Things I think I did incorrectly or could use work:

I included LeanTween (I used it for crossfading, and also just think it's a good inclusion to the package. I couldn't find a way to include it in the manifest though)
Currently all the audio playing is done with strings, in an ideal world it'd be done with enums or some other type-safe structure but I don't know how to do that (might need editor scripts?)
(as discussed previously) the audiomanager is currently tied directly to the settings UI so we need to encapsulate it and then tie it back through code.
I've done some testing but there's probably still a few bugs
I included test audio files, not sure if we should keep those in or not

Type of change

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

How Has This Been Tested?
Basic smoke tests of the core functionality
Checklist:
Check all as applicable or performed.

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes\

I haven't had a chance to pull and test in the editor, but overall great start 👍 After those other changes are made I'll be happy to pull, test, and otherwise pull this into the audio system branch to tweak further and help make some of those mentioned changes (helping abstract from the settings UI for example).
I'd look at the CONTRIBUTING.MD file at the root of the repo or other code in the repo for some hints about suggested code styling and system design for future PRs, really appreciate your support!

Rather than keep a centralized lookup of every sound on the AudioManager and using a string or enum to pick which one, could you change the API so that in PlaySound or PlayMusic it accepts an AudioClip parameter? This would make it so that the AudioManager doesn't need to know about every AudioClip ahead of time and other systems/FX can request their own audio to play.

Thanks for all the feedback! The only I point I want to push back on is this. In my experience, having audioclip references on everything is frustrating, especially when I need to change them later. The purpose of using some sort of "track list" was to have all that information in a central location (and you could even have multiple different versions and swap them out if you're trying out different styles). However, I also see how it would be convenient to pass in an AudioClip directly. How would you feel if I instead overloaded the functions in AudioManager so they could work either way?

I did some local testing using this branch and found that this fulfilled the feature requirements for what I was recommending in #7. I'd like to make some substantial refactors to help show some best practices for development and ease of use. Would you mind removing all of the test audio clips added in the final commit? After that I'll merge this in and make my changes on-top of this work as I'd like to recognize your contribution.

Oh right I forgot to mention about the audio clips. I found those audio files under the CC 1.0 license here https://freemusicarchive.org/music/Komiku/Helice_Awesome_Dance_Adventure_ and the artist who made it is very pro-open source stuff! https://twitter.com/RrrrroseAzerty I figured it'd be cool to include in the project for folks to use if they want. If you feel that it goes against the general aesthetic of the project or there are size considerations or some other thing I'm not thinking of I can take them out but they are in there because I thought it might be a nice add to the project. (also the "Pops" folder is just some basic sound effects I always use for prototyping, I recorded them myself and am happy to donate them if they are useful!)

I did some local testing using this branch and found that this fulfilled the feature requirements for what I was recommending in #7. I'd like to make some substantial refactors to help show some best practices for development and ease of use. Would you mind removing all of the test audio clips added in the final commit? After that I'll merge this in and make my changes on-top of this work as I'd like to recognize your contribution.

Oh right I forgot to mention about the audio clips. I found those audio files under the CC 1.0 license here https://freemusicarchive.org/music/Komiku/Helice_Awesome_Dance_Adventure_ and the artist who made it is very pro-open source stuff! https://twitter.com/RrrrroseAzerty I figured it'd be cool to include in the project for folks to use if they want. If you feel that it goes against the general aesthetic of the project or there are size considerations or some other thing I'm not thinking of I can take them out but they are in there because I thought it might be a nice add to the project. (also the "Pops" folder is just some basic sound effects I always use for prototyping, I recorded them myself and am happy to donate them if they are useful!)

I appreciate the thought! I'm mostly concerned about size considerations as this goes against the LFS count on my account and I'd rather only include minimal art and audio assets (especially as some of this content is preferential to taste). Once exception to that rule was including the KenneyNL UIPack, but I figured since that's pretty banal and it helps to show the UI a bit better than plain Unity textures.


Listview Item Templates Horizontal orientation

Hi,
Thanks a lot, this library is awesome!
I'm working on a project and can't seem to get the orientation of the contents listview items to horizontal. They always stack on top of each other. I tried using either a grid with columns, or a StackLayout with horizontal orientation, but nothing seems to work. Also the background of the viewcell seems to be black for some reason.
Here is an example
<ListView.ItemTemplate>
  <DataTemplate>
    <ViewCell>
      <StackLayout Orientation="Horizontal">
        <Label Text="{Binding .}"
               Style="{DynamicResource ListItemTextStyle}" />
        <Label Text="{Binding .}"
               Style="{DynamicResource ListItemDetailTextStyle}"/>
      </StackLayout>
    </ViewCell>
  </DataTemplate>
</ListView.ItemTemplate>

Both labels are rendered stacked on top of each other

Yeah, I know! What's up with that?! Sorry for the bug, need to look into it.

Any solution to this?
May be a workaround?

After a little digging and debugging the code, I found that events BatchCommitted and SizeChanged are not called for elements inside list view item. Not sure they are supposed to be called by Xamarin, it needs investigating. If not then may be the manual propagation of those events to ListView item children is required.

Hey @vignatov did you find a workaround to the issue?


[bug_5806] Applied jinja2

Applied jinja2
https://bugzilla.stxnext.pl/show_bug.cgi?id=5806

You have an unused import here:
https://github.com/stxnext-kindergarten/presence-analyzer-pgrundas/blob/master/src/presence_analyzer/tests.py#L10
You are not using views.

Also add new lines in the end of files.

Looks ok for me :+1:


Support multiple categories

Note that the LAST category will be used by fonts.google.com [for now]. This is meant to unblock data collection for multiple categories.

@RosaWagner I think this is what you want :D

Indeed, so I close your draft PR #4141 that doesn't give the correct example. For full clarity we should have, for example, in metadata.pb:
category: "SANS_SERIF" -> second category above, not yet supported
category: "MONOSPACE" -> first category under, currently in use

Updated my PR. @m4rc1e is this good to merge?

When I run add-font on an existing family, I get the following traceback:
Traceback (most recent call last):
  File "/Users/marcfoley/Type/tools/bin/gftools-add-font.py", line 271, in <module>
    app.run(main)
  File "/Users/marcfoley/Type/tools/venv/lib/python3.9/site-packages/absl/app.py", line 312, in run
    _run_main(main, args)
  File "/Users/marcfoley/Type/tools/venv/lib/python3.9/site-packages/absl/app.py", line 258, in _run_main
    sys.exit(main(argv))
  File "/Users/marcfoley/Type/tools/bin/gftools-add-font.py", line 257, in main
    metadata = _MakeMetadata(fontdir, is_new)
  File "/Users/marcfoley/Type/tools/bin/gftools-add-font.py", line 134, in _MakeMetadata
    metadata.category = old_metadata.category
  File "/Users/marcfoley/Type/tools/venv/lib/python3.9/site-packages/google/protobuf/internal/python_message.py", line 664, in setter
    raise AttributeError('Assignment not allowed to repeated field '
AttributeError: Assignment not allowed to repeated field "category" in protocol message object.

metadata.category = old_metadata.category is the issue here. I've added a commit which simply appends the old categories instead. I've tested this solution on both new and old families and it works ok.

Would it be supported by packager then? Like we just add a category in the yaml

Good point. I'll take a look.

For the packager, we need to decide how we're going to input the category. We have two options that I can think of.

Require the yaml file to use a list for the category e.g

category:
  - DISPLAY
  - SERIF
...

Or still keep it as a string but use a comma as a delimiter e.g:

```YAML
category: DISPLAY, SERIF

Option 2 may be easier but option 1 seems more legit.

Since we use comma for designers, should be the same for categories to avoid confusing users; the output will be different but this not the concern of users.

I'm looking at the strityaml docs to figure out how to do this, as comma separated string is basically the wrong data type, we want a list, to match the nature of the repeated entry of fonts_public.proto. So, good news, there's a CommaSeparated type.
A thing I'd personally would prefer would be to have an ordered set, i.e. a list with only unique entries, and there's also a type: UniqueSeq
The CommaSeparated would be specified something like: CommaSeparated(Enum(CATEGORIES)) in the YAML written as a comma separated string.
And the UniqueSeq would be something like: UniqueSeq(Enum(CATEGORIES)) in the YAML written as a list.
I wonder if: UniqueSeq(CommaSeparated(Enum(CATEGORIES))) would work as well.
I'm going to try the above and report back which options work....
What works:

CommaSeparated(Enum(CATEGORIES)) input as string
Seq(Enum(CATEGORIES)) input as list
UniqueSeq(Enum(CATEGORIES)) input as list

What Fails:

UniqueSeq(CommaSeparated(Enum(CATEGORIES))) input as string. This does not combine that way.

Welcome back everyone. I've decided to use the UniqueSeq approach. I've chosen not to parse a string ourselves since a UniqueSeq gives us auto validation. However, this now means we'll need to declare the category in the following manner:
category:
- DISPLAY
- SANS_SERIF

I've updated the template.yml so it;s clear that users now need to do this:
# Choose multiple of: DISPLAY, SERIF, SANS_SERIF, HANDWRITING, MONOSPACE. Currently, the last item will be used
# by Google Fonts
category:
  # - SANS_SERIF
  # - SERIF
  # - DISPLAY
  # - MONOSPACE
  # - HANDWRITING

@graphicore could you take a quick look?

@m4rc1e Sorry for the late reply, I'm just since yesterday back on keyboard. I submitted the review, I hope its not too confusing with the corrections I made on my own suggestions.

@graphicore Thank you for the thorough review. It wasn't hard at all to follow! I've implemented your feedback so ptal.


LineCharts throw IllegalArgumentException in Compose Previews

How to reproduce
Check Example app previews for ample evidence.
Android Studio Koala | 2024.1.1 Patch 1
Build #AI-241.18034.62.2411.12071903, built on July 10, 2024
Runtime version: 17.0.11+0-17.0.11b1207.24-11852314 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.6.1
GC: G1 Young Generation, G1 Old Generation
Memory: 8192M
Cores: 10
Metal Rendering is ON
Registry:
idea.ignore.disabled.plugins=true
Non-Bundled Plugins:
wu.seal.tool.jsontokotlin (3.7.4)
com.github.copilot (<IP_ADDRESS>56)
com.suusan2go.kotlin-fill-class (1.0.23)
com.getyourguide.paparazzi (1.2.2024.1)
Observed behavior

Expected behavior
Not throwing an exception
Vico version(s)
2.0.0-alpha.28
Android version(s)
n/a
Additional information
No response

Hi @mahoganykilo. This appears to be a bug in the Compose preview renderer. The Canvas initially has an incorrect size (0 by 0), while DrawContext.size reports the expected size. We will add a check for this and prevent the crash from happening, but since it's not actually a bug on our end, I'm closing this issue.

Hi @mahoganykilo. We've added a check that works around this renderer problem. It's available in Vico 2.0.0 Beta 1.


add dense/sparse biencoder models and refactor modeling module

Just to say thanks for sharing your very efficient framework and that I was able to test SPLADE with this PR implementation.
I only had to add a pyserini encoder (for eval) / change the Hard Negative code to use pyserini output (can add a PR later if you think it suits the project). Other than that the process was pretty smooth and results were pretty good.

Hi @cadurosar
Thank you very much for testing the SPLADE implementation.
And we look forward to your PR.