Authorization required for viewing SQL Queries is not provided

The authorization required to access this data is not provided in the documentation. Links provided as Next Steps never lead to this information.  Customers want to know what level of access is required to view this information and are interested in knowing how to secure this data so users can only see the queries they have submitted.
[Enter feedback here]

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

ID: 24fb9511-f478-d2be-40b3-1a839da0d7c8
Version Independent ID: 0036a800-a58b-c1c3-1c4c-7e22c0aff845
Content: How to monitor SQL requests in Synapse Studio - Azure Synapse Analytics
Content Source: articles/synapse-analytics/monitoring/how-to-monitor-sql-requests.md
Service: synapse-analytics
Sub-service: monitoring
GitHub Login: @matt1883
Microsoft Alias: mahi

Thanks for the feedback! We will review and get back to you shortly.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


BS: Add revocation handler

Add revocation handler both for direct and SCMP revocations.

Since the BS only sends via onehop or to the local AS we never have to deal with SCMP revocations. Either we issued them or there shouldn't be a revocation.


Free Food and Shuttle Notification Preferences Turning Off

Issue Description
When logging out and logging back into the app, notifications for Shuttles and Free Food are turned off in the User Profile.

Steps to Reproduce / Code Snippets
Check Notification Preferences in User Profile and log out. Log into the app and check Notification Preferences again.
Expected Results
Expected results would be for the app to save Notifications Preferences for each user. In my case, all of the notifications should've been kept on.

Additional Information

Platform(s) (iOS, Android, or both?): iOS

@sssaiya narrowed down the issue to the login portion of the code. The preferences are being reset upon login and seem to be consistent with dynamoDB when logging out.

Completed in:
bea184fcbeeaa28f56a776ed59854c8c4e7ec4ae
Sending to @g9singh and @c3bryant for review.

Verified & merged into branch 6.5

Verified on branch 6.5 - thanks @sssaiya & @g9singh, closing


Release/2.0.0

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Create release 2.0.0 and merge to main branch.

Reference Server Preview is available here:https://anchor-ref-pr898.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr898.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr898.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr898.previews.kube001.services.stellar-ops.com/


Hide ZcoinTransaction, ZcoinTxIn and ZcoinTxOut from outside

Need to remove ZcoinTransaction.Parse too.

After investigated it is blocked by #55.

We need to wait until NBitcoin release a new version (current version is 4.2.15).


Can you give us guide how to run your downloaded convmae.pth model to finetune?

Please refer to the following guidance for ConvMAE fine-tuning.
https://github.com/Alpha-VL/ConvMAE/blob/main/FINETUNE.md

Thanks.


Check for update results in an error

The "Check for update" function in KeePass returns an error for this plugin. In the Update check dialog it lists current version ok, but for available version is says "Update check failed. Version information file cannot be downloaded".

I need more info about your environment. What operational system? Which
keepass version?
On Nov 7, 2017 13:20, "David Williams"<EMAIL_ADDRESS>wrote:

The "Check for update" function in KeePass returns an error for this
plugin. In the Update check dialog it lists current version ok, but for
available version is says "Update check failed. Version information file
cannot be downloaded".
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/navossoc/KeePass-Yet-Another-Favicon-Downloader/issues/7,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACV--nAdA298fwOwC6HawwfkMro8Y2zOks5s0HU7gaJpZM4QU89A
.

I am using KeePass 2.37 on Linux.
I checked the source and it appears there is an 'update file' available, at
https://raw.githubusercontent.com/navossoc/KeePass-Yet-Another-Favicon-Downloader/master/VERSION
But the format of the file's contents appears incorrect.
It currently has what appears to be a signature at the beginning:
:Dj10LnyzaLuyCKTtwYHLh7KAd4C274gztflnPR4UDphmCIZ3cTHcHDX3R9+lJEjuACFmhG5fOSCysKy5DRXbQJrk7hjnKb3Rkj/uUTA+UR7XlcYinsl8tGnr6efO9UIODFsVjmjR0l4/K5Mj3yACva/13++skLA34hG3l8rPNo2Pz5CtQ6Ge413HqC6Dstl1JnHsQhimTmFXfWOOsxVLvqtZGA/xCrbUmKz0Ven0zFuimTrBGEXa1x5dtcxy+IA1TPpZsQkRemV5L8tpCo/k9DqDZ7LLdWR1RQm+BD4HysMbp9SqI5W9Fp7tqywY5IlPGTWhEwOtErb5wNIyBMH0ojkOb3R11Fg+MMgeQlVV8hUQcmGWZZn1Mz9ldOStknDsb8XYFtQcXqustlCzvpead5kaXDW562g65SvKinnFme2pHbzuW92P+vcgRRUublXHt5iG/UB/hsOfXkVcery6JX9MnbF9avWz5RlnJdrNUVNkAj7B5p4dPcb8x+fVqMrcj+a09v+lYTseMjNcWSz+UrSMI5z3tWX4nsZktKwtHqxEEm/Pl4w6CUuU8fXXohWjw9pSg7BMvS8dfbVtzK+h6R/GP3UDgM2d05FsuT+BCAh8Nchi6vhUrKqXQcjSpYLVUBiucPAaX4bI1/5p6HQBPPe2aECGCi2jp3Eg7KLvTa0=
Yet Another Favicon Downloader:<IP_ADDRESS>
:
From other examples I have seen, it would suffice to have simply
:
Yet Another Favicon Downloader:<IP_ADDRESS>
:
Is the 'signature data' intentional? Required?

I'm not at the computer right now, but this version file is signed. It's a
new feature available since 2.34.
https://keepass.info/news/n160611_2.34.html
It ensures you are not being tricked to update to a "fake version" from a
malicious part.
There is a mention here too, search for "signing":
https://keepass.info/help/v2_dev/plg_index.html
I may have missed something or it is a bug on keepass for Linux.
Windows is reporting the signature as ok.
On Nov 7, 2017 13:25, "David Williams"<EMAIL_ADDRESS>wrote:

I am using KeePass 2.37 on Linux.
I checked the source and it appears there is an 'update file' available, at
https://raw.githubusercontent.com/navossoc/KeePass-Yet-
Another-Favicon-Downloader/master/VERSION
But the format of the file's contents appears incorrect.
It currently has what appears to be a signature at the beginning:
:Dj10LnyzaLuyCKTtwYHLh7KAd4C274gztflnPR4UDphmCIZ3cTHcHDX3R9+
lJEjuACFmhG5fOSCysKy5DRXbQJrk7hjnKb3Rkj/uUTA+
UR7XlcYinsl8tGnr6efO9UIODFsVjmjR0l4/K5Mj3yACva/13++
skLA34hG3l8rPNo2Pz5CtQ6Ge413HqC6Dstl1JnHsQhimTmFXfWOOsxVLvqtZGA/
xCrbUmKz0Ven0zFuimTrBGEXa1x5dtcxy+IA1TPpZsQkRemV5L8tpCo/k9DqDZ7LLdWR1RQm+
BD4HysMbp9SqI5W9Fp7tqywY5IlPGTWhEwOtErb5wNIyBMH0ojkOb3R11Fg+
MMgeQlVV8hUQcmGWZZn1Mz9ldOStknDsb8XYFtQcXqustlCzvpead5kaXDW5
62g65SvKinnFme2pHbzuW92P+vcgRRUublXHt5iG/UB/hsOfXkVcery6JX9MnbF9avWz5RlnJd
rNUVNkAj7B5p4dPcb8x+fVqMrcj+a09v+lYTseMjNcWSz+UrSMI5z3tWX4nsZktKwtHqxEEm/
Pl4w6CUuU8fXXohWjw9pSg7BMvS8dfbVtzK+h6R/GP3UDgM2d05FsuT+
BCAh8Nchi6vhUrKqXQcjSpYLVUBiucPAaX4bI1/5p6HQBPPe2aECGCi2jp3Eg7KLvTa0=
Yet Another Favicon Downloader:<IP_ADDRESS>
:
From other examples I have seen, it would suffice to have simply
:
Yet Another Favicon Downloader:<IP_ADDRESS>
:
Is the 'signature data' intentional? Required?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/navossoc/KeePass-Yet-Another-Favicon-Downloader/issues/7#issuecomment-342517044,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACV--vjBf-cDZW9r19KPzWEi8CNaftdaks5s0HZqgaJpZM4QU89A
.

@daddavidw
I'll make some tests on linux later.
Which mono version are you using? Just to make the tests consistent.
So answering your question:
Is the 'signature data' intentional? Required?
It is intentional, but it is not required. It's just an additional security measure.

FWIW I have confirmed it works on windows for me too.
I have tried on two versions of Linux, Ubuntu 16.04 and 17.10 (both fail the 'update check').
I have also tried on my Mac machine, and it fails there in the same way.
My version of mono on the 16.04 machine is 4.2.1 (and on 17.10 it is 4.6.2).
In detail (for 16.04):
$ mono --version
Mono JIT compiler version 4.2.1 (Debian <IP_ADDRESS>+dfsg2-7ubuntu4)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS:           __thread
SIGSEGV:       altstack
Notifications: epoll
Architecture:  amd64
Disabled:      none
Misc:          softdebug
LLVM:          supported, not enabled.
GC:            sgen

@daddavidw I took a closer look at the issue.
Seems the problem is the URL used to check the version info, KeePass doesn't seems to like github too much 😆
If I use this link:
https://github.com/navossoc/KeePass-Yet-Another-Favicon-Downloader/raw/master/VERSION
Instead of:
https://raw.githubusercontent.com/navossoc/KeePass-Yet-Another-Favicon-Downloader/master/VERSION
Even if the link is a redirect, it works fine.
Weird...
Anyhow, it is scheduled to be fixed on the next release ;)
Thanks for your help.

@daddavidw I've released version <IP_ADDRESS>, see if it solves your problem.
Here it seems ok.

Yes, it works.
I installed new plugin on both Linux (my 16.04 system) and my Mac machine and after new one was installed then "check for updates" reports "Up to date" at 1.1.1 level (instead of displaying error).
I did not re-check Windows :)

I did check on Windows 10 and Debian 9.
Good to know it is working 💃


feat: automatically set defaults for txParams if not specified

Summary
This PR makes sure that the SDK will now automatically set sensible defaults for gasPrice and gasLimit transaction parameters in case they are not specified by the user.
// earlier, you would have always have to specify `txParams`. If you didn't, the transaction would fail.
await contract.functions.test_function().txParams({ gasPrice: 1, gasLimit: 10_000 }).call();

// now, you don't need to specify these values if you don't want to. This code works perfectly fine:
await contract.functions.test_function().call();

Closes #1696

Thinking of adding a test and some docs so marking this is a draft momentarily


Add authorization check to get process

Is there a related GitHub Issue?
#554
What is this change about?
This PR adds an authorization check to the GET /v3/processes/:guid endpoint.
Does this PR introduce a breaking change?
No
Acceptance Steps
See #554
Tag your pair, your PM, and/or team
@Birdrock

It seems that PR https://github.com/cloudfoundry/cf-k8s-controllers/pull/637 is conflicting a lot with this one. I am afraid that there would be lots of merge conflicts :(

Hey @davewalter
I have rebased the pr on top of main for you. It is unfair to make you do that on a cross-team collaboration story.
Hopefully next time we pick a cross-team story for you we would be careful not to heavily modify the code the story is all about so that we do not step on each others' toes.
I think that most of my comments have been already addressed with PR #637 , with the exception of the discussion on dot importing non-ginkgo packages.

Thanks @kieron-dev! I see that @gcapizzi has already re-opened the github issue. We'll take another crack at it in a separate PR.


Expanding a node on dropped

Hi guys,
I've been trying everything I can think of but can't get a node to expand on drop. My node have: data-collapsed="true" so they'll be collapsed by default.
In beforeDrag I've managed to do: sourceNodeScope.collapsed = false;
and the node actually expands. But in the dropped event I try to do:
event.source.nodeScope.collapsed = false;
and nothing happens. Any ideas? I also tried expand()

Did you try "beforeDrop" event instead of "dropped" ? As per documentation, dropped is only called when the position of dropped node changes !

Closed due to inactivity.


Isn't this project updated now?

Isn't this project updated now?

I have a simple project here https://github.com/createyourpersonalaccount/openldap-mediawiki if you are interested. It doesn't have all the configurations of osixia but it is up-to-date.

The project is dead, the company behind it seized to exist ( https://www.osixia.net/ )

Very relevant discussion over at #670 - it has been confirmed by the project owners, that the image is no longer maintained (the company still exists though).
You will find possible projects to migrate in the discussion, and also how to migrate.


Update to Argo 4

I pushed https://github.com/thoughtbot/ios-template/pull/16/commits/ae137f170b8d9313ecaba1077a6763798dba0497 to try and fix the CI failure.


Nan when up is aligned with target

I'm not sure what's the right way to fix this or even whether a fix is necessary. Just wanted to log it here:
// glMatrix version 3.3.0

// Note that both `up` and `direction` are the same
let q = mat4.getRotation([], mat4.targetTo([], [0, 0, -1], [0, 0, 0], [0, 0, 1]))

// Now all quaternion components are not numbers
assert(Number.isNaN(q[0]))
assert(Number.isNaN(q[1]))
assert(Number.isNaN(q[2]))
assert(Number.isNaN(q[3]))

I have the same issue. Seems like it doesn't work when target is at 0, 0, 0. Why is that?
const matrix = glMatrix.mat4.targetTo(glMatrix.mat4.create(),
    [0, 5, 0], [0, 0, 0], [0, 1, 0])
let rot = glMatrix.mat4.getRotation(glMatrix.quat.create(), matrix)
console.log(rot) // Float32Array(4) [NaN, NaN, NaN, NaN]

This results in a quat with "NaN, NaN, NaN, NaN"


css-variables

Would be great if this module could extract css-variables, so it can be used together with https://github.com/postcss/postcss-custom-properties (I know there's already https://github.com/postcss/postcss-brand-colors and that's what we're using but we'd like to focus on custom properties going forward).
I might have some bandwidth to contribute this. Interested?

Of course! Let's do it!
On Thursday, May 14, 2015, David Björklund<EMAIL_ADDRESS>wrote:

Would be great if this module could extract css-variables, so it can be
used together with https://github.com/postcss/postcss-custom-properties
(I know there's already https://github.com/postcss/postcss-brand-colors
and that's what we're using but we'd like to focus on custom properties
going forward).
I might have some bandwidth to contribute this. Interested?
—
Reply to this email directly or view it on GitHub
https://github.com/reimertz/brand-colors/issues/11.

Perfect, expect a PR in a day or so!
—
Sent from my iPhone
On Sat, May 16, 2015 at 12:52 AM, Pierre Reimertz
<EMAIL_ADDRESS>wrote:

Of course! Let's do it!
On Thursday, May 14, 2015, David Björklund<EMAIL_ADDRESS>wrote:

Would be great if this module could extract css-variables, so it can be
used together with https://github.com/postcss/postcss-custom-properties
(I know there's already https://github.com/postcss/postcss-brand-colors
and that's what we're using but we'd like to focus on custom properties
going forward).
I might have some bandwidth to contribute this. Interested?
—
Reply to this email directly or view it on GitHub
https://github.com/reimertz/brand-colors/issues/11.

Reply to this email directly or view it on GitHub:
https://github.com/reimertz/brand-colors/issues/11#issuecomment-102542770

@kesla How are you doin? Im closing this since it's really an issue on my side you know. :)

Oh, thanks yeah let's close this! I'll see when I get bandwidth for this.


seminar-minutes-2020-4

add seminar-minutes-2020-4

It would be great if we can also share the zoom recorded meeting video!

Thank you very much for adding the meeting video recording for our meeting notes!
I'd prefer to use the cloud recording next time because it seems that we can show both the slides and the video on the screen at the same time from the cloud recording.
Is there anyone who knows how to make this record format with the local recording? I believe we should use the "double mode(slides & video of the speaker)" as the default in the future.


On large data, len() gets much slower or fails entirely after dask 1.2.0/distributed 1.27.0

Bug report:

I don't have a great minimal example yet.  The symptom is that, in my dask setup in a JupyterHub+Jupyterlab+Kubernetes deployment, the dask dashboard loses connection with its workers.  This did not happen with dask 1.2.0  and distributed 1.27.0.  It appears to happen at dask 1.2.1 and distributed 1.27.1 and all later versions (including 2.0).  Although dask-kubernetes has evolved since then, it didn't change when the connection loss started appearing (it was at 0.7.0 then).  This is particularly strange since it looks like the changes in dask and distributed were purely cleaning up quote mark types and spacing.

This can be demonstrated if you use the notebook:
https://github.com/lsst-sqre/notebook-demo/blob/master/experiments/DASK-notebooks/gaia_all_sky.ipynb ; however, this example uses the PyPi repo "jupyterlabutils" in order to proxy the worker and status dashboards through jupyter-server-proxy.  If you're not running under Kubernetes (and I don't think k8s is implicated here), you can probably use the standard client and cluster classes.  Anyway, to replicate, use gcsfs and the GCS bucket gcs://jupyterlabdemo-gaia-dr2/gaia_source.parquet.  There's a persist() step, and then after that a cell where we use the %%time magic to time calculating the dataframe length.  That len(df) call will hang within the first five times you invoke it if it's going to (just keep re-executing the cell).  The symptom is that the len() doesn't return, and the dask progress graph and memory consumption (which are the two I usually have open) just stop updating.

I'll try to get a more minimal example, but I am pretty sure this is only going to show up on large datasets.

The slowness is real.  The hanging seems to be related to the %%time magic?  This is very weird.

Does the dashboard reveal what workers are busy doing on the profile tab?
Or are you suspecting that the cluster is doing nothing? I have tried, and even from my laptop, I can create the dataframe from the GCS data, and load the first partition's worth.

I just managed to trigger it without a %%time.  It happened, in this case, on the fourth run of the len(df) cell in fairly rapid succession.
The dashboard makes it look like everything completed, but the cell never returns.

Do you have the Variable Inspector extension? That was previously implicated in performance issues:
https://github.com/lckr/jupyterlab-variableInspector/issues/59#issuecomment-433009643
...though that was supposed to have been fixed. Anyway, since it sounds pretty strange it might be worthwhile trying without any other extensions active.

Probably not related, but just in case:
https://github.com/ipython/ipython/pull/11812

Indeed, it hadn't occurred to me, but @dhirschfeld has a point, it would be well worthwhile trying the code in a console with no jupyter stuff in the way at all.
As usual, it would be a good idea to check the scheduler and worker logs for any output.

Just dropping a note here that I have been doing a little more looking into this.  I have not been able to trigger the behavior directly from a python interpreter running in a terminal.  I'll post back when I have more info.

Now we're pursuing a hypothesis that it's actually related to the proxying we're doing to be able to get the dashboards to the end-user (via jupyter-server-proxy).

Still not a lot closer, but I have found, if you interrupt the hanging len() call, you get:
---------------------------------------------------------------------------
KeyboardInterrupt                         Traceback (most recent call last)
<ipython-input-18-9e112543b788> in <module>
----> 1 len(df)

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/site-packages/dask/dataframe/core.py in __len__(self)
    510     def __len__(self):
    511         return self.reduction(
--> 512             len, np.sum, token="len", meta=int, split_every=False
    513         ).compute()
    514

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/site-packages/dask/base.py in compute(self, **kwargs)
    173         dask.base.compute
    174         """
--> 175         (result,) = compute(self, traverse=False, **kwargs)
    176         return result
    177

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/site-packages/dask/base.py in compute(*args, **kwargs)
    444     keys = [x.__dask_keys__() for x in collections]
    445     postcomputes = [x.__dask_postcompute__() for x in collections]
--> 446     results = schedule(dsk, keys, **kwargs)
    447     return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])
    448

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/site-packages/distributed/client.py in get(self, dsk, keys, restrictions, loose_restrictions, resources, sync, asynchronous, direct, retries, priority, fifo_timeout, actors, **kwargs)
   2525                     should_rejoin = False
   2526             try:
-> 2527                 results = self.gather(packed, asynchronous=asynchronous, direct=direct)
   2528             finally:
   2529                 for f in futures.values():

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/site-packages/distributed/client.py in gather(self, futures, errors, direct, asynchronous)
   1821                 direct=direct,
   1822                 local_worker=local_worker,
-> 1823                 asynchronous=asynchronous,
   1824             )
   1825

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/site-packages/distributed/client.py in sync(self, func, asynchronous, callback_timeout, *args, **kwargs)
    761         else:
    762             return sync(
--> 763                 self.loop, func, *args, callback_timeout=callback_timeout, **kwargs
    764             )
    765

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/site-packages/distributed/utils.py in sync(loop, func, callback_timeout, *args, **kwargs)
    328     else:
    329         while not e.is_set():
--> 330             e.wait(10)
    331     if error[0]:
    332         six.reraise(*error[0])

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/threading.py in wait(self, timeout)
    550             signaled = self._flag
    551             if not signaled:
--> 552                 signaled = self._cond.wait(timeout)
    553             return signaled
    554

/opt/lsst/software/stack/python/miniconda3-4.5.12/envs/lsst-scipipe-1172c30/lib/python3.7/threading.py in wait(self, timeout)
    298             else:
    299                 if timeout > 0:
--> 300                     gotit = waiter.acquire(True, timeout)
    301                 else:
    302                     gotit = waiter.acquire(False)

KeyboardInterrupt:

So I think what's happening is that we get stuck in that wait loop forever called from sync() because it's defaulting callback_timeout to None ?

I suspect this is a subtle bug in either jupyter-server-proxy or in maproxy, or in my use of those classes.
It doesn't seem to exist when I'm not using my wrapper classes.
I've worked around it by adding a timeout with exponential backoff up to a maximum to sync(): see https://github.com/lsst-sqre/jupyterlabutils/blob/2d3757695fe3d731192c176d52c92ce9afab3640/jupyterlabutils/notebook/lsstdaskclient.py#L33
Probably close this?  I have an efficacious-if-gross workaround.

I'm going to close this particular one, but there is still an underlying issue.  See dask/distributed #2880 (https://github.com/dask/distributed/issues/2880)


Fix Aggregated Discovery

What this PR does / why we need it:
See https://github.com/kubevirt/kubevirt/issues/10262
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/cc @0xFelix

Update it here too?
staging/src/kubevirt.io/client-go/go.mod

I am a little bit unsure, since normally we bump all of k8s in one go. @xpivarc what do you think?

@0xFelix @rmohr PTAL
Since it is only a minor update I thought to get away with only client-go. No additional changes seem to be in other dependencies. Nevertheless, I updated all k8s dependencies.


Cv2.RotatedRectangle(r1, r2, Point2f[] intersection) throws exception

Cv2.RotatedRectangle(r1, r2, Point2f[] calls wrong NativeMethod function, resulting in an exception. (reported as issue #411)

Thanks!!


Ethereum

Hello @shahednasser , Can I work on this issue.

Sure I'll assign you @AJIT-KUMAR-PANDIT


Update zlib URL in r0.10 branch

This change fixes the broken zlib URL in yet another branch. Fixes #6950.

Jenkins, test this please.

Jenkins sanity tests are failing with java certificate issues.
That in turn aborts everything else.
Not sure how we can make this pass without making more changes into the branch.


Android sourceSets task does not show output in Gradle 6.8+

Expected Behavior
I can run the Android Gradle task sourceSets on an Android module and see output.
Current Behavior
No output is shown from the task.
Context
The task works in Gradle 6.7.1 but not Gradle 6.8 or higher (and I've just checked a very recent 7.0 nightly as well). I suspect the cause is https://github.com/gradle/gradle/commit/4dac91ab87ea33ee8689d2a62b691b119198e7c7 since SourceSetsTask extends AbstractReportTask which had its @TaskAction removed by that commit.
I originally raised this issue against Android's issue tracker but was told to raise against the Gradle project instead.
Steps to Reproduce
Open any Android project and run the sourceSets task in an Android module with Gradle 6.7.1 (works, prints output as expected) then switch to Gradle 6.8 and try again (does not show output).
Your Environment
Gradle 6.8.2, AGP 4.1.2 on Windows

@bamboo Could you check this? I reproduced it.

This will be fixed in Gradle 7.0 and most likely backported to Gradle > 6.8.3
Follow #16621 for this.

Thanks for the follow up, @ljacomet!


[QUESTION] Hardcoding in torch frontend build script prevents local building

I follow build docs in torch frontend README.md, while I encounter some build issue causing by hardcoding
For instances in /path/to/byteir/frontends/torch-frontend/scripts/envsetup.sh:15

and in /path/to/byteir/frontends/torch-frontend/scripts/build.sh

Can someone help address the hardcoding issues in the build script so that I can build and test ByteIR locally?

Hi, firstly, you do not need to install mhlo-tools, you can comment out this line.
Secondly, if you use frontends/torch-frontend/scripts/build.sh, you do not need the prebuilt llvm.
Use clang-11 because torch-2.4.1 requires gcc>8, you can change it to any cxx compiler which could work.
There are many limits when we try building, hardcoding is a naive way to provide a successful compilation.

In debian or ubuntu system, you can use apt install clang-11 to install clang.

yes I mean I am just a little confused why not just use clang instead of clang-11, clang may be softlink to clang-11 or some further clang version. Or is this project dependent on a specific version of Clang?

In industrial, most products are tested under setups only highly related to their production and/or development environment.
It doesn't mean the products only work in those setups, or specifically dependent on some functionality.
It simply means the products tested in those setups.
Think about this way.
It is extremely hard to test all versions, considering there are some combinations across many versions of OS, compilers, dependencies, drivers, and hardware.
That is why we need opensource community.
Feel free to test ByteIR in different environments.
If you hit related issues or/and happen to have a solution, also feel free to send us a PR.
I will close the issue, since your major questions got answered.
Feel free to open a question, if you have any further one.


Products not listed as required

Currently, the table Statement fields lists productsas not required. However, they should be according to the introduction.

I believe this is addressed by this part of the field's description:

this field is optional as it can cascade down from the encapsulating document, see Inheritance.

The idea is that if there's already a higher-ranking specification of the product(s), it's not necessary to redefine the product(s) for every statement in the document.
So while it's mandatory that the statement is associated with a specific set of products, it's not mandatory that the association be achieved via the statement's products field.
cc: @puerco

This was confusing to me as well, maybe partially due to a mix of possible inheritance scenarios?
It seems like there's two types of inheritance:

Timestamp inheritance from the VEX document struct
Timestamp or product id inheritance from the encapsulating document (in-toto, CSAF, etc)

Am I tracking this correctly? Maybe some clarification around this in the spec would be beneficial, I initially was thinking you could throw a products section into the document struct since the only inheritance examples are "pure VEX" (no encapsulation).

As Dan mentioned, the reason why products is technically optional is because the field can be inherited. Specifically, this is meant to inherit an attestations's subject. This is further explained in the attesting documentation. Perhaps the spec should explicitly mention this, I'll try to add some language to that effect in the next minor revision.

This, of course does, not imply that the VEX statement can be completed without products, it just means that the JSON struct can be considered valid by a simple validator if it does not have the products field.


Support new BOTD#2 protocol to recognise supported content type

Ref: https://dev.tdex.network/docs/specs/transport-protocol
ideally clients should call the Transport service and use the one more suited for the environment. The ENUM number states the priority
ie.
if in browser use first (if available)

JSON
GRPCWEB
GRPCWEBTEXT

if in node environment

GRPC
JSON

Ping @Janaka-Steph
Having Swagger definitions we can use it to auto-generate HTTP JSON clients https://github.com/tdex-network/tdex-daemon/tree/master/api-spec/openapi/swagger/tdex/v1


make maxRetries func param & try direct submission if delegator sign …

Description

get maxRetries in SubmitDelegatedFallbackDirect as func argument
try direct tx submission if signing from delegator fails

Fixes https://github.com/Bisonai/orakl/issues/1906
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] 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

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Deployment

[ ] Should publish npm package
[ ] Should publish Docker image

lgtm!, before merging and deploying this, let's send some klay from delegator to reporter wallet so that it can work in case of delegator failure


Support Unicode in lexer

@egavrin, I've updated the PR.

Good to me.

Some style issues, but the patch is close to ready.

@zherczeg, the PR was updated, please, check.

Even better ^_^

+1 lgtm

make push

Merged as 146ac15b5ffab8a08b45276cab9ab109ec6bd254


Discard stale watch events

If compilation takes a lot of time, all recompile events should be discarded other than process them in order. Or to say, only the latest recompile request should be processed. Reported by aleph on discord.

Shouldn't it instead finish the existing compilation before starting a new one? Otherwise it'll just never compile anything if you type quickly.

Shouldn't it instead finish the existing compilation before starting a new one?

exactly


Only create user journal when accepted/remove journals for unknown user

Otherwise there are phantom journals or could be payouts for users who don't exist

Can you please descirbe this issue. I cannot get it.


chore: fix documentation

fixes #222

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 27.407%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
111

Relevant Lines:
405

💛  - Coveralls


ReferenceError on the Graph tab

The graph tab in OSS is broken, tested it in staging and locally.
https://gitops.euw1.wego-gke.weave.works/kustomization/graph?clusterName=Default&name=flux-system&namespace=flux-system
Full trace (with sourceMap on):
act-dom.production.min.js:216 ReferenceError: $22b18e23564de7e8$exports is not defined
    at yQ (ReconciliationGraph.tsx:102:16)
    at bo (react-dom.production.min.js:157:137)
    at ol (react-dom.production.min.js:267:460)
    at jl (react-dom.production.min.js:250:347)
    at zl (react-dom.production.min.js:250:278)
    at Ql (react-dom.production.min.js:250:138)
    at kl (react-dom.production.min.js:243:163)
    at react-dom.production.min.js:123:115
    at v (scheduler.production.min.js:18:343)
    at ri (react-dom.production.min.js:122:325)
F

Results of research:

It looks like the error is related to the following PR, in which some parcel packages were upgraded:
https://github.com/weaveworks/weave-gitops/pull/3651/files

I had a similar error in this PR:
https://github.com/weaveworks/weave-gitops/pull/3640
and fixed it by adding an alias to package.json to help parcel resolve imports (please see the PR description for more details).
Something similar might work here, but I cannot think of a quick fix right now.

It is possible the error occurs because of d3 not initialized properly. If I add a debug message console.log(d3) right before the place where d3 is used first time, the graph is displayed (so, maybe a delay is needed to initialize it)

Probably something undefined here: https://github.com/weaveworks/weave-gitops-enterprise/tree/main/ui-cra/src/components/GitOpsSets
The error makes me think there is a module not being loaded

And the error points to the line on which d3 is first used in the graph:

I don't see this in the stack trace. What is the indication of this?

The trace with the line number is in the PR description:
Full trace (with sourceMap on):
act-dom.production.min.js:216 ReferenceError: $22b18e23564de7e8$exports is not defined
    **at yQ (ReconciliationGraph.tsx:102:16)**
    at bo (react-dom.production.min.js:157:137)
    at ol (react-dom.production.min.js:267:460)
    at jl (react-dom.production.min.js:250:347)
    at zl (react-dom.production.min.js:250:278)
    at Ql (react-dom.production.min.js:250:138)
    at kl (react-dom.production.min.js:243:163)
    at react-dom.production.min.js:123:115
    at v (scheduler.production.min.js:18:343)
    at ri (react-dom.production.min.js:122:325)
F

at yQ (ReconciliationGraph.tsx:102:16)

At least this is what I see in the trace when turning sourceMap on.


[Document] Highlight Cloudflare Workers Environment Differences

What is the feature you are proposing?
I attempted to modify the HonoRequest headers directly via c.req.raw.headers, but encountered an error: TypeError: Can't modify immutable headers. This functionality works as expected on Bun. After reviewing the Cloudflare Workers documentation, I discovered that the Request object is entirely immutable in this environment, including its headers.
To help developers understand such differences, I propose adding a note to the documentation that highlights the immutability of the Request object in Cloudflare Workers and encourages awareness of environment-specific behaviors in Cloudflare Workers versus other environments.
Reference
Request | Cloudflare Workers docs

You may also want to construct a Request yourself when you need to modify a request object, because the incoming request parameter that you receive from the fetch() handler is immutable.

Code Examples
This code will fail in Cloudflare Workers due to the immutability of the Request headers. (Adapted from #2847)
app.use(async (c, next) => {
  c.req.raw.headers.set('x-username', '6km')
  await next()
})

app.get('/', (c) => {
  return c.json(c.req.header())
})

This code works in Cloudflare Workers by creating a new Request instance with modified headers.
app.use(async (c, next) => {
  const newHeader = new Headers(c.req.raw.headers);
  newHeader.append("test", "test");

  c.req.raw = new Request(c.req.raw, {
    headers: newHeader,
  });
  await next();
});

Hi @catnaut
I think this is not only a matter of Cloudflare Workers. The same behavior has occurred on Deno. There are different implementations, but perhaps the specification is that the header should be immutable.
By the way, we are working on discussion the Proxy Helper for the proxy use case to avoid the user writing code for copying headers: https://github.com/honojs/hono/pull/3589

We already added the caution for it on our website: https://hono.dev/examples/proxy#proxy

Hi @catnaut
I think this is not only a matter of Cloudflare Workers. The same behavior has occurred on Deno. There are different implementations, but perhaps the specification is that the header should be immutable.
By the way, we are working on discussion the Proxy Helper for the proxy use case to avoid the user writing code for copying headers: #3589

awesome work on this! 👍


[Doc Improvement][Update Teams-Toolkit-CLI manifest parameters][3634069]

Fix --manifest-file to match --teams-manifest-file for 2.x versions of the CLI

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
87
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
87
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
87
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

msteams-platform/toolkit/TeamsFx-preview-and-customize-app-manifest.md
87
16
link
:white_check_mark:

msteams-platform/toolkit/create-new-project.md
87
15
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
88
86
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/toolkit/Teams-Toolkit-CLI.md
90
78
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


ssl problem, cont...

It appears that disabling ssl did not solve the issue completely (with reference to  upgrade fails #788 ).
It runs with no problem for a while and then exists with this error message below.
However, when I run manually:
/usr/local/share/bcbio/anaconda/bin/pip install -r https://raw.github.com/chapmanb/bcbio-nextgen/master/requirements.txt
Then tt works fine. I guess the installer is set to specifically use "/usr/local/share/bcbio/anaconda/ssl/cert.pem".  Not sure how to resolve this, how to update this specific certificate or use another certificate.
Kind regards,
Pär
Exception:
Traceback (most recent call last):
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/basecommand.py", line 232, in main
status = self.run(options, args)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/commands/install.py", line 321, in run
finder=finder, options=options, session=session):
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/req/req_file.py", line 31, in parse_requirements
session=session,
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/download.py", line 396, in get_file_content
resp = session.get(url)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/_vendor/requests/sessions.py", line 473, in get
return self.request('GET', url, **kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/download.py", line 365, in request
return super(PipSession, self).request(method, url, *args, **kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/_vendor/requests/sessions.py", line 461, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/_vendor/requests/sessions.py", line 573, in send
r = adapter.send(request, **kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/_vendor/cachecontrol/adapter.py", line 43, in send
resp = super(CacheControlAdapter, self).send(request, **kw)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/pip/_vendor/requests/adapters.py", line 431, in send
raise SSLError(e, request=request)
SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
Traceback (most recent call last):
File "/usr/local/bin/bcbio_nextgen.py", line 199, in
install.upgrade_bcbio(kwargs["args"])
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 53, in upgrade_bcbio
subprocess.check_call(sudo_cmd + [pip_bin, "install", "-r", REMOTES["requirements"]])
File "/usr/local/share/bcbio/anaconda/lib/python2.7/subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/local/share/bcbio/anaconda/bin/pip', 'install', '-r', 'https://raw.github.com/chapmanb/bcbio-nextgen/master/requirements.txt']' returned non-zero exit status 2

Pär;
Sorry about the issues, I'm not sure what is going on here. We added in the pointer to the locally installed certificates (instead of system certificates) to avoid this problem in #764 so I'm confused as to why it's now causing the issue. What type of system are you running on? Is there anything else about the SSL library setup between the systems where it works and doesn't work that might give us clues? Sorry, this is a bit out of my areas of expertise so just searching for potential starting points. Thanks for the help.

Tried different things, no success. Doing a complete reinstall now and hope that this will solve it.

The setup is identical between the machines, running ubuntu 14.04. However, the one that works is on a university network (no corporate firewall / filtering) and the other one is at the university hospital (with firewall/filtering but no proxy). I don't know how this might impact? I'll see if I can use the hospital's root certificate instead. (Just have to figure out how.)

I obviously don't know what I'm doing but it seems to work now. Just using the company root certificate did not work. However, when I linked /etc/ssl/certs/ca-certificates.crt with /usr/local/share/bcbio/anaconda/ssl/cert.pem the errors disappeared. With the caveat that the install is not yet finished.

Pär;
Apologies, I wish I understood more to help with this. If you find any generalizable solutions for your setup that would help, I'd be happy to roll them into bcbio.

No ... still fails! By redirecting the cert.pem link to "/etc/ssl/certs/ca-certificates.crt" the installation process  goes almost to completion.
But eventually it fails with the error enclosed below. Is there a way to disable the need to validate certificates?  I read that you can use "requests.get('https://www.reporo.com/', verify=False)", but I'm not sure how to modify the install script. I read also that one way is to create a new SSLContext. (I am aware of the security risks.)
I'm getting desperate.
INFO: List of genomes to get (from the config file at '{'install_liftover': False, 'genome_indexes': ['bwa'], 'genomes': [{'rnaseq': True, 'dbsnp': True, 'name': 'Human (GRCh37)', 'dbkey': 'GRCh37'}], 'install_uniref': False}'): Human (GRCh37)
Traceback (most recent call last):
File "/usr/local/share/bcbio/anaconda/bin/bcbio_nextgen.py", line 199, in
install.upgrade_bcbio(kwargs["args"])
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 89, in upgrade_bcbio
upgrade_bcbio_data(args, REMOTES)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 239, in upgrade_bcbio_data
remotes["genome_resources"])
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 256, in _upgrade_genome_resources
r = requests.get(remote_url)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/requests/api.py", line 65, in get
return request('get', url, **kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/requests/api.py", line 49, in request
response = session.request(method=method, url=url, **kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/requests/sessions.py", line 461, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/requests/sessions.py", line 573, in send
r = adapter.send(request, **kwargs)
File "/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/requests/adapters.py", line 431, in send
raise SSLError(e, request=request)
requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)

Sorry I wish I knew what to suggest. I guess your firewall is somehow modifying SSL requests causing these to fail, but I don't know why. If you want to hack around these issues, you could directly modify:
/usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py

so the two requests.get calls there don't use validation, and then re-run the data download. I wish I had a more long term solution but hope this helps.

It worked. To summarize, the following steps were required for the installation process:

Start installation using bcbio_nextgen_install.py
When it fails:
Relink: usr/local/share/bcbio/anaconda/ssl/cert.pem to /etc/ssl/certs/ca-certificates.crt
Add verify=False to the two requests.get() in /usr/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py

I have contacted our network people at the hospital to see if something is wrong here, or if they have suggestions for changes in the bcbio-nextgen install script.
//Pär

Pär;
Glad that worked, and thank you for following up. I pushed use of verify=False by default to those two requests calls. They're only pulling configuration and requirements files from GitHub so I'll prioritize it actually installing. I wish I knew a fix for the certificate issue but thanks for documenting the workaround. Thanks again for all the patience getting this running.


feat: add egg icon

Zoom
100%

Credit goes to https://github.com/feathericons/feather/pull/83

@mittalyashu hmm I'm not sure about the gloss line. I think without look a bit better with the others.

@ericfennis here's a comparison between egg with/without gloss line.

@mittalyashu  Isn't it a bit too pointy? Real life egg for reference:

I prefer the egg without gloss, but that is my preference. What do you think?

@Andreto that's true, just by creating and outline shape it will only look like an oval shape without giving a clear visual representation of an egg.
@ericfennis Sure, we can remove the gloss. But the image @Andreto shared does have a gloss 😂

@mittalyashu I realize that your more exaggerated shape does look a lot better in true size.

@ericfennis Could the gloss perhaps work better if it was a bit smaller and actually followed the shape of the edge?

After comparing all four, I like the 4th one.

@Andreto Yeah it is more about the gloss, we don't use it on other icons for example camera or smartphone. So that why I don't feel something for the gloss.
@mittalyashu I agree with you, 4th looks better!

@Andreto Since you've the source code of that 4th icon. You can override the changes to this PR or create a new one or can you share the source code?

@mittalyashu I was unable to push a commit to this pr. Could you perhaps turn on “Allow edits from maintainers.” ?

I was unable to push a commit to this pr. Could you perhaps turn on “Allow edits from maintainers.” ?

@Andreto It's already enabled.

I was unable to push a commit to this pr. Could you perhaps turn on “Allow edits from maintainers.” ?

@Andreto It's already enabled.


skip csrf verification if an api key is set and present

Check the Authorization header to make sure an API key is present and matches what is in the config table (assuming what is a valid string)

Hi @alex-phillips, thank you a lot for your PR. :+1:
On your installation, assuming you did composer --install (without the --no-dev) can you try vendor/bin/phpunit in your root (well where you would do php artisan ....
It seems to break on some tests ( https://github.com/LycheeOrg/Lychee-Laravel/blob/master/tests/Feature/HtmlTest.php ).

@ildyria thanks for the feedback!  I get the following output when I run phpunit:
PHPUnit 7.5.6 by Sebastian Bergmann and contributors.

..S                                                                 3 / 3 (100%)

Time: 343 ms, Memory: 20.00 MB

OK, but incomplete, skipped, or risky tests!
Tests: 3, Assertions: 26, Skipped: 1.

It seems to break on some tests ( https://github.com/LycheeOrg/Lychee-Laravel/blob/master/tests/Feature/HtmlTest.php ).

Really interesting that it only fails with the dev tools... Looks like a 500 error when it's expecting something else? A blank, maybe?

I fixed the error 500. :)


Fix path separator for urls on windows

This is done in https://github.com/bitovi/steal-tools/commit/9475fe1354c10ec53620baeb57308416c6c80495


Revise config files for consistency

-Config files now match the draft release.
-ELCI_2 was missing a parameter description.
-Removed 2 extraneous files
I will confirm on this pull request that all model runs import succesfully to openLCA as written.

I successfully imported and ran each of these models in openLCA


Warnings when importing a freshly created GKE cluster with default parameters

What happened?
Pulumi outputs warnings when importing a freshly created GKE cluster from Google Cloud console.
Steps to reproduce
pulumi import gcp:container/cluster:Cluster carsync-prod us-central1-a/carsync-prod

Expected Behavior
No warnings
Actual Behavior
Diagnostics:
  gcp:container:Cluster (carsync-prod):
    warning: One or more imported inputs failed to validate. This is almost certainly a bug in the `gcp` provider. The import will still proceed, but you will need to edit the generated code after copying it into your program.
    warning: gcp:container/cluster:Cluster resource 'carsync-prod' has a problem: Conflicting configuration arguments: "cluster_ipv4_cidr": conflicts with ip_allocation_policy. Examine values at 'Cluster.ClusterIpv4Cidr'.
    warning: gcp:container/cluster:Cluster resource 'carsync-prod' has a problem: Conflicting configuration arguments: "ip_allocation_policy": conflicts with cluster_ipv4_cidr. Examine values at 'Cluster.IpAllocationPolicy'.
    warning: gcp:container/cluster:Cluster resource 'carsync-prod' has a problem: Conflicting configuration arguments: "monitoring_service": conflicts with cluster_telemetry. Examine values at 'Cluster.MonitoringService'.
    warning: gcp:container/cluster:Cluster resource 'carsync-prod' has a problem: Conflicting configuration arguments: "logging_service": conflicts with cluster_telemetry. Examine values at 'Cluster.LoggingService'.

Versions used
CLI
Version      3.35.3
Go Version   go1.18.3
Go Compiler  gc

Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@Frassle I'd love your thoughts on this...

Even though these were just warnings, and the import was successful, I had to remove a bunch of conflicting fields for  pulumi up to work (it was giving an error). I still have no idea how the cluster was actually configured on Google Cloud. Did it use this or did it use that? Pulumi said it couldn't use both, but that was precisely what it imported.

@stack72 This will be based on whatever the Read method returned from the provider. The engine data flow is a very simple call Read, run the result of that through Check warn about any check failures but then save the state and code as returned.
I'd try making a gke cluster and then seeing what provider Read returns for it.

Can confirm, I also get these conflicts when importing a cluster.
pulumi import gcp:container/cluster:Cluster my-cluster com-my-dev-760a2504/us-central1/com-my-us-gke-dev
Then execute pulumi up with my code:
    error: gcp:container/cluster:Cluster resource 'my-cluster' has a problem: Conflicting configuration arguments: "logging_service": conflicts with cluster_telemetry. Examine values at 'Cluster.LoggingService'.
    error: gcp:container/cluster:Cluster resource 'my-cluster' has a problem: Conflicting configuration arguments: "ip_allocation_policy": conflicts with cluster_ipv4_cidr. Examine values at 'Cluster.IpAllocationPolicy'.
    error: gcp:container/cluster:Cluster resource 'my-cluster' has a problem: Conflicting configuration arguments: "monitoring_service": conflicts with cluster_telemetry. Examine values at 'Cluster.MonitoringService'.
    error: gcp:container/cluster:Cluster resource 'my-cluster' has a problem: Conflicting configuration arguments: "cluster_ipv4_cidr": conflicts with ip_allocation_policy. Examine values at 'Cluster.ClusterIpv4Cidr'.

The only way to resolve these errors is changes to the imported YAML to address the conflict.
For instance ipAllocationPolicy has conflicting entries so I remove the cidr blocks from them.
    clusterIpv4CidrBlock: <IP_ADDRESS>/18
    clusterSecondaryRangeName: gke-com-my-us-gke-dev-pods-5c803d01
    servicesIpv4CidrBlock: <IP_ADDRESS>/19
    servicesSecondaryRangeName: gke-com-my-us-gke-dev-services-5c803d01

Then I have to remove
  monitoringService: monitoring.googleapis.com/kubernetes
  loggingService: logging.googleapis.com/kubernetes

This fixes the conflicts. But it causes state drift against the remote API.
As indicated below:
     Type                      Name               Plan     Info
     pulumi:pulumi:Stack       k8s-us-dev
     └─ gcp:container:Cluster  my-cluster           [diff: +enableKubernetesAlpha,enableL4IlbSubsetting,enableLegacyAbac,enableShieldedNodes-clusterIpv4Cidr,loggingService,monitoringService,project~__defaults,ipAllocationPol

This issue needs ownership.

I used @jondkelley's fixes and do not experience state drift with remote API; however, it still seems odd that I'd have to manually edit an import from the actual state of the GCP Cluster. How can the current state be in conflict with itself...?

Given this cluster:
import * as gcp from "@pulumi/gcp";

const cluster = new gcp.container.Cluster("primary", {
    name: "my-gke-cluster",
    location: "us-central1",
    removeDefaultNodePool: true,
    initialNodeCount: 1,
});

export const clusterId = cluster.id;

I can now do an import without warnings:
Importing (dev2)

View in Browser (Ctrl+O): https://app.pulumi.com/anton-pulumi-corp/pulumi-gcp-844/dev2/updates/2

     Type                      Name                 Status
     pulumi:pulumi:Stack       pulumi-gcp-844-dev2
 =   └─ gcp:container:Cluster  c2                   imported (0.95s)

Outputs:
    clusterId: "projects/pulumi-development/locations/us-central1/clusters/my-gke-cluster"

Resources:
    = 1 imported
    2 unchanged

Duration: 2s

Please copy the following code into your Pulumi application. Not doing so
will cause Pulumi to report that an update will happen on the next update command.

Please note that the imported resources are marked as protected. To destroy them
you will need to remove the `protect` option and run `pulumi update` *before*
the destroy will take effect.

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";

const c2 = new gcp.container.Cluster("c2", {
    addonsConfig: {
        gcePersistentDiskCsiDriverConfig: {
            enabled: true,
        },
        networkPolicyConfig: {
            disabled: true,
        },
    },
    clusterIpv4Cidr: "<IP_ADDRESS>/14",
    clusterTelemetry: {
        type: "ENABLED",
    },
    databaseEncryption: {
        state: "DECRYPTED",
    },
    defaultMaxPodsPerNode: 110,
    defaultSnatStatus: {
        disabled: false,
    },
    initialNodeCount: 1,
    location: "us-central1",
    loggingConfig: {
        enableComponents: [
            "SYSTEM_COMPONENTS",
            "WORKLOADS",
        ],
    },
    masterAuth: {
        clientCertificateConfig: {
            issueClientCertificate: false,
        },
    },
    monitoringConfig: {
        advancedDatapathObservabilityConfigs: [{
            enableMetrics: false,
            enableRelay: false,
        }],
        enableComponents: ["SYSTEM_COMPONENTS"],
        managedPrometheus: {
            enabled: true,
        },
    },
    name: "my-gke-cluster",
    network: "projects/pulumi-development/global/networks/default",
    networkPolicy: {
        enabled: false,
        provider: "PROVIDER_UNSPECIFIED",
    },
    networkingMode: "VPC_NATIVE",
    nodeLocations: [
        "us-central1-b",
        "us-central1-c",
        "us-central1-a",
    ],
    nodePoolDefaults: {
        nodeConfigDefaults: {
            loggingVariant: "DEFAULT",
        },
    },
    nodeVersion: "1.29.4-gke.1043002",
    notificationConfig: {
        pubsub: {
            enabled: false,
        },
    },
    podSecurityPolicyConfig: {
        enabled: false,
    },
    privateClusterConfig: {
        masterGlobalAccessConfig: {
            enabled: false,
        },
    },
    project: "pulumi-development",
    protectConfig: {
        workloadConfig: {
            auditMode: "BASIC",
        },
        workloadVulnerabilityMode: "WORKLOAD_VULNERABILITY_MODE_UNSPECIFIED",
    },
    releaseChannel: {
        channel: "REGULAR",
    },
    securityPostureConfig: {
        mode: "BASIC",
        vulnerabilityMode: "VULNERABILITY_MODE_UNSPECIFIED",
    },
    serviceExternalIpsConfig: {
        enabled: false,
    },
    subnetwork: "projects/pulumi-development/regions/us-central1/subnetworks/def}, {
    protect: true,
});

This is accomplished by dropping out conflicting properties in pulumi-terraform-bridge during import. The dropout is not very intelligent but attempts to resolve conflicts.
Versions:
CLI
Version      3.117.0
Go Version   go1.22.3
Go Compiler  gc

Plugins
KIND      NAME    VERSION
resource  gcp     7.26.0
language  nodejs  unknown

Host
OS       darwin
Version  14.5
Arch     arm64

This project is written in nodejs: executable='/Users/anton/bin/node' version='v18.18.2'

Current Stack: anton-pulumi-corp/pulumi-gcp-844/dev2

TYPE                           URN
pulumi:pulumi:Stack            urn:pulumi:dev2::pulumi-gcp-844::pulumi:pulumi:Stack::pulumi-gcp-844-dev2
pulumi:providers:gcp           urn:pulumi:dev2::pulumi-gcp-844::pulumi:providers:gcp::default_7_26_0
gcp:container/cluster:Cluster  urn:pulumi:dev2::pulumi-gcp-844::gcp:container/cluster:Cluster::primary
gcp:container/cluster:Cluster  urn:pulumi:dev2::pulumi-gcp-844::gcp:container/cluster:Cluster::c2

Found no pending operations associated with dev2

Backend
Name           pulumi.com
URL            https://app.pulumi.com/anton-pulumi-corp
User           anton-pulumi-corp
Organizations  anton-pulumi-corp, moolumi, pulumi
Token type     personal

Dependencies:
NAME            VERSION
@pulumi/pulumi  3.120.0
@types/node     18.19.34
typescript      5.4.5
@pulumi/gcp     7.26.0

Pulumi locates its logs in /var/folders/gd/3ncjb1lj5ljgk8xl5ssn_gvc0000gn/T/com.apple.shortcuts.mac-helper// by default

I will close this as fixed but please feel free to open another issue if something is not working as expected.


add spidernode resource

What would you like to be added?
new resource spidernode
Why is this needed?
spidernode crd is a new resource type that addresses the following issues:

It provides a local IP list cache, so when requesting or releasing an IP, the address is not directly allocated from the ippool.
It solves the preparation work required before the IP is assigned to a node. This is especially relevant in public cloud scenarios with elastic network interfaces (ENIs), where the IP needs to be bound to the node before it can be used. Additionally, the IP can be classified as primary or secondary, with the primary IP assigned to the host and the secondary IP assigned to containers.

There are some differences between spidernode and spiderippool:

The addresses in ippool do not have a primary or secondary classification.
When multiple nodes are using the same ippool, it is not possible to specify a certain set of IPs to be allocated only to specific nodes. This situation often occurs in scenarios where multiple nodes correspond to multiple ippools.

For more information about ENIs, you can refer to the following link: https://github.com/AliyunContainerService/terway/blob/main/docs/design.md#eni多ip
How to implement it (if possible)?
controller add new actions:

Allocate addresses from ippool to node.spec resources based on pre-allocation policies.
Perform preparatory operations in the ENI scenario, primarily setting node.status, including setting addresses on the host and addresses that can be allocated to containers.
Mark address availability status and perform reclamation.

daemon add new actions:

Request and allocate addresses based on their sources, which can be from ippool, node, or ENI.
For addresses coming from the ENI source, additional actions are taken to mark the addresses as used.
Adjust priority strategies when addresses are sourced from node and ENI.

Additional context
related:  https://github.com/spidernet-io/spiderpool/issues/2465
I've read and agree with the following

[X] I've checked all open and closed issues and my request is not there.
[X] I've checked all open and closed pull requests and my request is not there.

@weizhoublue  WDYT ?

After the conversation, the Node ENI allocation should be handled by the Iaas controller. Spiderpool is a CNI plugin, it serves for the container IP allocation. We don't allocate IP for the Node secondary NIC.


Datepicker result in IE11

Hello,
the Datepicker result seems to be not correct in IE11 with type datetime and formats with Hours, Minutes and Seconds.

It's probably a more generic bug in Angular (or Intl):
https://github.com/angular/angular/issues/9524
https://github.com/angular/angular/issues/10147
For the time being, including ie.intl.shim.js (drop it to assets and include in your polyfills.ts) from this bugfix helped me:
https://github.com/Deutsche-Boerse-Risk/DAVe-UI/issues/7


Docker image does not seem to preload any lanugages.

docker run -p 8800:8800 -t beakernotebook/beaker
Works fine but I get infinite initilizing languages for everything except html and latex. Is there a flag or process to load language backend?

no, they should work.  what version of beaker is in your container (look in the help->about)?

i just checked and didn't have any problems.  can you give more specific steps to reproduce?

build time: 2015-10-06 20:50 UTC
version: 1.4.1-0-ge8427bf

I'm running this through docker-machine on an aws remote host which has been giving me problems on other images. Is there a specific port configuration that you recommend?

it just needs 8800 open.  if you get anything at all then it should work.

This is weird. My session expired and i reconnected and R and JS work. Nothing else yet.

What browser are you using?

Safari

Its giving me logs that indicate IPython noteboodk is good

althought it is giving me a 404 on an api request:
IPython-stderr>[W 18:14:20.613 NotebookApp] 404 GET /api/kernels83552e56-2407-4658-a3aa-5104d30328cc?_=1444846335144 (<IP_ADDRESS>) 1.70ms referer=https://<IP_ADDRESS>:8800/beaker/

Seems to be working on chrome however.

Oh okay so i think this is at least partially an issue on my end.
I was not running as daemon but was treating it as such.

Cool, glad you got it figured it out.

We should test more on Safari. it sounds like that may have confused the UI a bit.


Fix snapshot persistence

Closes #490

For contributor use:

[x] Targeted PR against master branch
[x] Linked to GitHub issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[ ] Updated relevant documentation
[x] Re-reviewed Files changed in the GitHub PR explorer
[x] Added appropriate labels

Sorry @chasefleming just saw the issue, actually documentation needs update, implementation is correct.
We have for some time possibility of snapshots without persistence, unfortunately when I made the storage reorg PR, I forgot the documentation update probably.

No worries @bluesign was fun to dig into the code. Do you want me to remove the change but keep some of the tests so that there are more tests? I can update the documentation as well in this to be correct. Let me know.

@bluesign I fixed the documentation and updated the tests to reflect what you said

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0273f8f) 54.71% compared to head (60ff731) 54.85%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #491      +/-   ##
==========================================
+ Coverage   54.71%   54.85%   +0.13%
==========================================
  Files          28       28
  Lines        3648     3648
==========================================
+ Hits         1996     2001       +5
+ Misses       1492     1485       -7
- Partials      160      162       +2

Flag
Coverage Δ

unittests
54.85% <ø> (+0.13%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


NNPA Performance regression in several models after llvm uplift

In the following models, roberta-base-11 t5-decoder-with-lm-head-12 resnet18-v2-7 resnet34-v2-7 resnet50-v2-7 resnet101-v2-7 resnet152-v2-7, there's a notable performance regression on NNPA between commit dce84b5 (good) and 96a2558 (regression).  See picture below for specific runtimes in ms.

All models compiled with --O3 --EmitLib --mtriple=s390x-ibm-loz --mcpu=z16 --maccel=NNPA  --onnx-op-stats TXT
runtimes in ms and are an average of 10 inferences after a single warmup inference
used the dataset inputs from the onnx model zoo for each model
Other models may be impacted these are just the ones I confirmed are affected by this commit specifically

I believe this is fixed by merged #2652

Confirmed. Runtime for the models above is back to previous norms:
Results from testing commit 826f9af7
roberta-base-11.onnx averaging 7.23199 ms
t5-decoder-with-lm-head-12.onnx averaging 10.2682 ms
resnet18-v2-7.onnx averaging 13.3078 ms
resnet34-v2-7.onnx averaging 16.9058 ms
resnet50-v2-7.onnx averaging 30.2422 ms
resnet101-v2-7.onnx averaging 44.4475 ms
resnet152-v2-7.onnx averaging 59.0743 ms


bug: bluesky social link doesn't work with just "username"

Expected Behavior
The documentation at https://github.com/theNewDynamic/gohugo-theme-ananke/wiki/Social-media-network-setup#available-networks implies that bluesky should just work. My hugo.toml had the following config
[params.ananke.social.bluesky]
  username = "simmervigor"

For this link to work, it would need to create a link with the url https://bsky.app/profile/simmervigor.bsky.social
Current Behavior
It created a link with the url https://bsky.app/profile/simmervigor, which fails to load in bluesky because its unknown
Possible Solution
I think this is similar to the mastodon situation described in https://github.com/theNewDynamic/gohugo-theme-ananke/wiki/Social-media-network-setup#mastodon. There can be various bluesky instances (PDS) and its going to be hard to guess. I resolved my problem by using a config with an explicit profilelink field. Perhaps all that is needed is to update the documentation to highlight this is an issue
[params.ananke.social.bluesky]
  username = "simmervigor"
  profilelink  = "https://bsky.app/profile/simmervigor.bsky.social"

Steps to Reproduce
This is no longer reproducible on my website since I resolved the issue. However, its fairly easy to repro

Add a [params.ananke.social.bluesky] config with only the username field

The bigger picture (we need context)
hugo v0.135.0-f30603c47f5205e30ef83c70419f57d7eb7175ab+extended linux/amd64 BuildDate=2024-09-27T13:17:08Z VendorInfo=gohugoio
ananke git submodule @ 892eaf2f18a8af63e4c586230332be86d772a26a

Currently, in my understanding of Bluesky, your username is actually simmervigor.bsky.social. I think there is a misunderstanding or "mis-naming" of username as in "what we use to login". it should probably be something along the lines of profilename. But I agree... as Bluesky is something that will grow like Mastodon instances, it's probably best to just circumvent the issue with the recommendation to use a profilelink setup.

Oh good point.
I'll let you resolve this as you see fit, just wanted to flag it before I forgot.

I added a note to the documentation. I will go through this whole config topic again when I check the share link setups... I had the feeling that there is more possible than just adding the link.


when using loadRemotemodule inside component it loads some different js and failes

we use loadRemotemodule inside component and on some scenario we call the remote entry with url but it fails with undefined js it try to bring.
it goes completely to different url than it was configured.
the url is configured hardcoded so it cant be undefined.

loadRemoteModule({
        remoteEntry: 'remoteUrl/remoteEntry.js',
        remoteName: 'financialPlanning',
        exposedModule: './RemoteAppModule',
      }).then(federated => {
        federatedComponent.createComponent(
          federated['financialPlanningMfeModule'].exports.find((e: any) => {
            return e.ɵcmp?.exportAs[0] === 'comp';
          }),
          { injector: ɵcreateInjector('module', this.injector) },
        );
      });

Can you please send me a reproduction?


primary carrier disposition is not used

Description of the issue
We have the primary energy carrier disposition (Definition: Primary energy carrier disposition is an energy carrier disposition of material entities that are extracted directly from natural resources or that are natural energy flows.), but it is not used for classes like hard coal or natural gas and thus these classes are not inferred as subclasses of primary energy carrier.
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

I identified the following classes where I am very sure that should get the axiom 'has disposition' some 'primary energy carrier disposition':

natural gas
crude oil
coal
peat`

The classes need discussion:

air
water
nuclear fuel

As from yesterdays discussion in the OEKG meeting there was already an agreement on the first group I'll implement these immediately. The second group we can discuss later.

In PR #1033 came the idea to give biomass the primary energy carrier disposition. This is a bit complicated, as biomass currently neither has an axiom has energy carrier disposition nor an axiom has fuel role. At least the latter one has we distinguish between biomass and biofuel. Only the later one has a fuel role. If we give now biomass the axiom primary energy carrier disposition, then basically say, that there might exist some biomass which is an energy carrier, but cannot be combusted. Do we want this?


Update release versions for all build files.

Codecov Report

Merging #1619 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1619      +/-   ##
============================================
- Coverage     83.51%   83.48%   -0.03%
  Complexity     1813     1813
============================================
  Files           261      261
  Lines          8339     8339
  Branches        803      803
============================================
- Hits           6964     6962       -2
- Misses         1121     1123       +2
  Partials        254      254

Impacted Files
Coverage Δ
Complexity Δ

...e/ocagent/OcAgentTraceServiceConfigRpcHandler.java
75.86% <0%> (-3.45%)
12% <0%> (ø)

Continue to review full report at Codecov.

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


elfwriter: Add test to check the preservation of links

This PR adds a minimal test to check the correctness of links in the elfwriter. It also fixes an existing test by adding .dynsym and .dynstr sections for the checks. Output of go test -v:
=== RUN   TestWriter_HasLinks
=== RUN   TestWriter_HasLinks/only_keep_file_header
=== RUN   TestWriter_HasLinks/only_keep_program_header
=== RUN   TestWriter_HasLinks/keep_all_sections_and_segments
--- PASS: TestWriter_HasLinks (0.00s)
    --- PASS: TestWriter_HasLinks/only_keep_file_header (0.00s)
    --- PASS: TestWriter_HasLinks/only_keep_program_header (0.00s)
    --- PASS: TestWriter_HasLinks/keep_all_sections_and_segments (0.00s)

cc @kakkoyun

Ok, now these are the correct ones. The bug is not in the elfwriter. It'll still be nice to add this though. So that we're not only checking the preservation of links on the filtering side but also on the writer's side as well. :)


Move to 2020.4; minor changes to get single layer tests working

There may be a lot of conflicts

Replaced by #30


20240206_allsky_v0.10.5_all_dec_srcdep_base

New Prod config
Self check-list:

[x] I have checked the lstchain config, in particular for:

[ ] az_tel instead of sin_az_tel if data to be analyzed have been produced with lstchain <= v0.9.7
[ ] "increase_nsb" and "increase_psf" are provided in "image_modifier" (if used)

[x] I have checked the environment in the lstmcpipe config and it is the one used to analyse DL>1 data
[x] I have provided the command (in README), or script (in additionnal .py file) used to produce the lstmcpipe config

Prod_ID
20240206_allsky_v0.10.5_all_dec_srcdep_base
Short description of the config
Base production for all declinations lines with lstchain v0.10.5 + source-dependent analysis

hi @SeiyaNozaki
will you regenerate this one using  lstmcpipe v0.10.4 and the new config?

Thank you! I created a new PR #455 using the new config


Supervisor HTTP API link broken

At the bottom of this page: https://www.balena.io/docs/learn/deploy/release-strategy/update-locking/

that link appears to resolve to https://www.balena.io/docs/learn/deploy/release-strategy/update-locking/API.md, though it's somehow invalid: https://github.com/balena-io/docs/blame/master/pages/learn/deploy/release-strategy/update-locking.md#L83

this file is actually generated from https://github.com/balena-io/balena-supervisor/blame/master/docs/update-locking.md#L83, so i am not sure how to properly templatize this variable between the supervisor docs and this repo

The file is also renamed in fetch-external.sh https://github.com/balena-io/docs/blob/master/tools/fetch-external.sh#L23. I think the only reasonable way to manage this is through a redirect.


Create a "Ongoing Projects" page in a blog style

Create a blog style webpage that our nav bar links to in order to solve the below issues.
Mandatory Requirements:

[ ] Individual "posts" that could contain a specific project and activities being worked on for that specific project
[ ] Post contains gallery (similar to the one on index.html) to show off progress photos
[ ] Any other fun items you believe might make a "Ongoing Projects" page shine!

Optional Requirements:

[ ] Maybe a way to easily hide past posts when projects are completed/archived?

Feel free to ask any questions.

@sarthakahuja07,
I have assigned this issue to you, if you have any questions feel free to ask them here.
Thanks and happy hacking!

@sarthakahuja07 See below

Something like this, where we can place information on the latest project the club is working on, but also have other projects that are being worked on/have been completed below the newest.
Basically a place to show off what we are working on.
Let me know if that answers your questions.


Publicity plan - what is the program committee's role with publicity?

Comments from Force2016 -

"Need to have a well defined publicity plan at the beginning of the conference planning and a point person to move this forward. Lack of an all-member listserv made it hard to communicate."

"The use of a assigned blogger really helped capture the planning and excitement up until the conference and we got a lot of positive feedback."

What is our role? What do we need to do in helping with publicity or how do we support those efforts of others?

We need to coordinate key dates and let us know when you would like us to send out announcements and such.


Godoc typo fix: OptionHTTPClient -> OptionFileUploadConcurrency

@evanfuller I don't have the ability to merge (not sure if there is some automation waiting to swoop in).

@evanfuller I don't have the ability to merge (not sure if there is some automation waiting to swoop in).

sorry about that, thanks for the fix!


When "All Layers" is used, polygon layers are being allowed

Seems like when "all layers" is used, we should have a check for only point feature layers. Currently, all feature layers are allowed.

the builder is allowing me to configure a form for all layers in a map, which ends up creating the conditions where i can select a form for a polygon feature layer.  if i do this, then fill out the form, select location, and submit. i get this error: "Sorry your entry cannot be submitted. Please try again."

More info:  In the builder it will also allow me to explicitly select a single polygon feature layer. So the check for point features layers should restrict the list of editable layers in step 2 of the builder to points. Otherwise i can create an app with one layer that will never allow end users to successfully submit an entry.

@iwittenmyer I think we decided to just do a feature layer detection because checking if the layer is editable requires another network request or creating the layer to do. @CTDisasterManagement can you confirm?
If we have the webmap created in the bulder, we could probably just use this method to see if the layer is editable.
https://developers.arcgis.com/javascript/jsapi/featurelayer-amd.html#iseditable

@CTDisasterManagement I'm seeing this issue:
 TypeError: undefined is not a function {stack: (...), message: "undefined is not a function"} "TypeError: undefined is not a function
    at null.<anonymous> (http://localhost/git/geoform-template-js/js/main.js:1613:52)
    at g.hitch (http://js.arcgis.com/3.13/init.js:177:296)
    at c (http://js.arcgis.com/3.13/init.js:76:221)
    at d (http://js.arcgis.com/3.13/init.js:76:10)
    at b.Deferred.resolve.callback (http://js.arcgis.com/3.13/init.js:77:350)
    at ia (http://js.arcgis.com/3.13/init.js:503:92)
    at Pa (http://js.arcgis.com/3.13/init.js:505:60)
    at oa (http://js.arcgis.com/3.13/init.js:504:397)
    at http://js.arcgis.com/3.13/init.js:513:482
    at c (http://js.arcgis.com/3.13/init.js:76:221)"

I don't think the layer is loaded yet so the function isn't available.
We may need a function like this to wait for it to be loaded first.
_featureLayerLoaded: function (layer) {
        var def = new Deferred();
        if (layer.loaded) {
          // nothing to do
          def.resolve();
        } else if (layer.loadError) {
          def.reject(new Error(this._dijitName + " Layer failed to load."));
        } else {
          var loadedEvent, errorEvent;
          // once layer is loaded
          loadedEvent = on.once(layer, "load", lang.hitch(this, function () {
            errorEvent.remove();
            def.resolve();
          }));
          // error occurred loading layer
          errorEvent = on.once(layer, "error", lang.hitch(this, function () {
            loadedEvent.remove();
            def.reject(new Error(this._dijitName + " Layer could not be loaded."));
          }));
        }
        return def.promise;
      },

Also, getting the layer twice isn't good. We should get the layer once and cache it as a variable. Calling getLayer() twice isn't very optimal.

@CTDisasterManagement I'm still seeing JS errors with this.
Here is my appid: be338760de9249f8b15df22a8e4ee586
Can you investigate?

Sure, we will look into this.

Hi @driskull ,
The error that we see in the appid you gave is due to a "length" property that is present as an enumerable property in the fields object of config.
Here is the snapshot:

Whereas the expected 'fields' object doesn't have any such property as we can see below:

We have handled this issue in the code, although we might have to investigate on, how this "length" property got pushed in the fields object of config of this webmap.
Please share your insights on the same, if any!
Thanks!!

@CTDisasterManagement Not sure how that happened. very odd.

@CTDisasterManagement This app was created before we moved to multiple layers so I'm assuming that it got messed up when it was converted. Since it was an array before becoming an object.
During the conversion, we should make sure we're not saving the object with a length property or something.
I'm guessing that's what happened.
Can you look into the code and

Hi @driskull ,
The other two snapshots of objects that are working fine are also from apps created before multiple layer functionality was built.
So chances are rare of this being the reason as the configs of these apps have also gone through the same updates.
We are looking into this and will let you know if we find anything relevant!
Thanks!

Ok thanks


feat(zkstack_cli): l2 contract verification

Added command for verifying L2 contracts deployed with zkstack_cli.
Tested with local env and on testnet.

Can you elaborate on what is this complication? If anything, this change:

decreases the amount of code
removes useless abstraction on script results
makes script usage more uniform (single entry point -> single output, generalization to arbitrary set of contracts instead of a bunch of chosen ones)


Understand and fix errors connecting to the Elastic deployment

Specifically:

ERROR u.a.w.p.a.f.e.GeneralExceptionMapper - Sending HTTP 500 from GeneralExceptionMapper. URI: /catalogue/v2/works?query=botany.
ERROR u.a.w.p.a.e.ElasticErrorHandler$ - Sending HTTP 500 from ElasticErrorHandler$ (Unknown error; ElasticError(504,504,None,None,None,List(),None))

Closing this as there I think there is a need to understand how to monitor Elastic better, and this is definitely not the most efficient way.


bindings_test flaky

This test:
https://github.com/epinio/epinio/blob/main/acceptance/bindings_test.go#L34
Sometimes it's not run at all:
https://github.com/epinio/epinio/runs/2885340957?check_suite_focus=true
some times it's green:
https://github.com/epinio/epinio/runs/2885077732?check_suite_focus=true#step:12:955
and some times it fails:
https://github.com/epinio/epinio/pull/526/checks?check_run_id=2885573423#step:12:1136
 [4]
[4]         ✔  Epinio Applications:
[4]         |      NAME      | STATUS |                     ROUTES                     |     SERVICES      |
[4]         |----------------|--------|------------------------------------------------|-------------------|
[4]         | apps-216083207 | 1/2    | apps-216083<IP_ADDRESS>.3.omg.howdoi.website | service-216084817 |
[4]
[4]     to match regular expression
[4]         <string>: apps-216083207.*\|.*1\/1.*\|.*service-216084817

Should the app have 2 instances?

I suspect that the not run at all is a mis-look.
Going to the linked logs and searching them for binding_test shows that it was run, and it was green.

Attempted to replicate locally, running the tests focused on bindings_test.go.
Four attempts. Twelve runs per attempt.
Each attempt used less timeout for the Eventually than the previous.

1min (unchanged compared to repo)
30s
10s
1s
0s

While the test flaked two times in attempts 1-4 none were due to Eventually timing out, it was always something in the setup or teardown.
In attempt 5 it flaked twice with the issue reported.
I strongly suspect that the issue seen in CI was a load spike on the action runner (VM (host)) slowing cluster operations extremely enough to run into the timeout. It should be a rare thing.
Best bet for a "fix" right now is to blindly increase the timeout to 5min to overcome even the slowest operation of the cluster used by the action runner.


Escaping the user's SQL in the explore view

When executing SQL from SQL Lab, we use a lower level API to the
database which doesn't require escaping the SQL. When going through
the explore view, the stack chain leading to the same method may need
escaping depending on how the DBAPI driver is written, and that is the
case for Presto (and perhaps other drivers).

Coverage decreased (-0.04%) to 69.345% when pulling 68deeb51d2e440e465e23d0cc94f31eb3ed133c6 on mistercrunch:fix_escape into aa95e03eb9305c81118876f05f351709daf4cb98 on apache:master.

Coverage decreased (-0.04%) to 69.345% when pulling 635b42d972e1a16812a9b40b8409418be3e0f52b on mistercrunch:fix_escape into aa95e03eb9305c81118876f05f351709daf4cb98 on apache:master.

Coverage decreased (-0.04%) to 69.345% when pulling 635b42d972e1a16812a9b40b8409418be3e0f52b on mistercrunch:fix_escape into aa95e03eb9305c81118876f05f351709daf4cb98 on apache:master.

Coverage decreased (-0.04%) to 69.345% when pulling 635b42d972e1a16812a9b40b8409418be3e0f52b on mistercrunch:fix_escape into aa95e03eb9305c81118876f05f351709daf4cb98 on apache:master.


Match SCG SQL Cluster Environment

Hey @LeoLiuGitbox - I think you might want to merge this into another branch you have - you probably dont want the ola master branch to have your local paths in it.


Monomorphization of Simplifier, leg #1

Fixes #3325 partially
Scope:
The 1st leg of the Simplifier monomorphization.
Modules affected:

Kore.Reachability.Prove
Kore.Rewrite.RewriteStep
Kore.Rewrite.Step
Kore.Simplify.Application

Estimate:

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

report-breakerzircon--leg-1_master.pdf
The performance test was run against two branches:
master: 0cc2eb046101cba0080b63e04a5b5a0f1374a99f
breakerzirconia/monomorphize-simplifier-leg-1: 08aac3df14fb6ae61567b889de642df6a44c833e
Result: (100% / 89.46% - 1) * 100% = 11.78% performance improvement.

Woo! Nice results! 🎉
I wonder why those two tests are slower on this branch. As a follow-up, please profile them with this change, and let us know if anything stands out. The two tests are:

bug approve succes
bug vat mului pas

Woo! Nice results! 🎉
I wonder why those two tests are slower on this branch. As a follow-up, please profile them with this change, and let us know if anything stands out. The two tests are:
* bug approve succes

* bug vat mului pas

Thank you, will do!
Also, my apologies, I messed up the percentages a little bit. Since the original number was 100%, and the resulting is 89.46%, there is 100% - 89.46% = 10.54% performance improvement.


Rendered docs

This PR adds the rendered documentation to the gh-pages branch, as discussed in #1.

Now that the repo is public, I turned on the pages setting and something seems to be a bit off in how the pages are being rendered. https://informsjoc.github.io/2023.0055/. Can you take a look?

@tkralphs thansk for checking! I think a simple .nojekyll file is missing from the root of the branch. By default Github pages assumes Jekyll builds, and then does not deploy anything form directories starting with an underscore (like our _static/ assets). The fix is, I think, to add an empty .nojekyll file to the gh-pages branch. The redeploy should happen automatically after committing.


Fix SVG height

Added bottom padding to SVG height. @Hermanya Please review

Thank you, this is now available in v4.0.0.


Provide restarts for parsing errors?

Should investigate being a Good CL Citizen and providing meaningful restarts where they Make Sense ™ © ® .
My main concern is how they might impact performance. Performance isn't the main concern of this library, but I don't want users to pay for features they don't use, and in my experience, restarts are primarily useful during repl development and not 'delivered code'
But that said, a good set of restarts is quite helpful during development.

Maybe you could look at how Eclector does it, here's what I found in < 5 minutes:

The doc
Bunch of conditions
Some recovery code??


Embrace semantic versioning

The latest update brought many breaking changes, including having to change the js module file. I would recommend embracing a "semantic" versioning kind of release scheme, where breaking changes require a major version increment.
https://semver.org/

It already does? This was a major version update to 4.0.0 and there was a huge breaking changes warning banner at the top of the release notes.

Got confused with another hacs repo which also brought breaking changes, apologies!


update requirements neccessary to run tests

the tests did not run until we installed pyblake2

Weird! What system/python version are you using?
The code tries to use the builtin hashlib before reverting to use pyblake2.
https://github.com/ethereum/beacon_chain/blob/b4179ec24e3530e17083c8ad22ae448cee51bd14/beacon_chain/utils/blake.py#L1-L4

we're running Python 3.5.2
and Ubuntu 16.04
until we installed pyblake2 the tests did not run.
Thanks for the quick response.

According to pyblack2: Python 3.6 and later have native support for BLAKE2 in hashlib derived from this implementation, with compatible API. This module should only be used if you want BLAKE2 in older Python versions, such as 2.7 or 3.5 and earlier.
Hmm, now the evm module in Py-EVM supports both 3.5 and 3.6, I think it's fine to add it, maybe add a comment like for Python version older than Python 3.6. Leave it until we provide different env setting in Py-EVM?

Yeah, I just saw that too. We can support 3.5 and 3.6 for now. I'll add the comment in the readme