deploy: implement GHA with replacing Cloud Build

AsIs
Currently we are using Google Cloud build for deploying application, but it is deactivated on the platform side.
Since this application will run on GKE, we can simply use GitHub Actions and build the container image for serve from GitHub packages.
ToDo

[x] replace Cloud Build with GitHub Actions
[x] implement pipeline to push image to GitHub Packages

Confirmed that container image build by build packs has been uploaded to GHCR as GitHub Packages.
As fixed in 3908837, note that we could not include upper case in tag name with GHCR. Otherwise, the process will be exited error with following errors.
ERROR: failed to build: invalid image name 'ghcr.io/hwakabh/6ow3idGirl:latest': 'ghcr.io/hwakabh/6ow3idGirl:latest' is not a valid tag reference: could not parse reference: ghcr.io/hwakabh/6ow3idGirl:latest
Error: Process completed with exit code 1.

Confirmed that all workload has been deployed successfully with build image by GitHub Actions + Buildpacks, and we can see page rendered with temporary EXTERNAL-IP of Kubernetes service resource.
Note that we had manually updated serviceType with kubectl edit after manifests applied, since we need to manage external access with Kubernetes ingress resources instead of service whose type is LoadBalancer.
Also, the strange thing is we can not reach to express app within container with default port tcp/3000, so we have updated it with tcp/8080 and mapped it with tcp/80 for external access.
% kubectl -n 6ow3idgirl get all
NAME                           READY   STATUS    RESTARTS   AGE
pod/express-555d69797d-btk2d   1/1     Running   0          4m22s
pod/express-555d69797d-mhcn7   1/1     Running   0          4m6s
pod/express-555d69797d-rkmnj   1/1     Running   0          4m17s

NAME              TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)        AGE
service/express   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:32389/TCP   6h26m

NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/express   3/3     3            3           6h26m

NAME                                 DESIRED   CURRENT   READY   AGE
replicaset.apps/express-555d69797d   3         3         3       4m23s
replicaset.apps/express-5b579977b9   0         0         0       35m

% curl -D - -o /dev/null -s -X GET http://<IP_ADDRESS>
HTTP/1.1 200 OK
X-Powered-By: Express
Content-Type: text/html; charset=utf-8
Content-Length: 17396
ETag: W/"43f4-rnvat1TLASIZ3pj7i3KfZCFOXcA"
Date: Fri, 01 Mar 2024 13:22:09 GMT
Connection: keep-alive
Keep-Alive: timeout=5


Ported the SquareLinear interpolator to Strata #805

This interpolator needs to be added to StandardCurveInterpolators to make it available.


Question: License

Hi
What is the license type for snippets and the BLE libraries?
Thanks

https://github.com/nkolban/esp32-snippets/blob/master/LICENSE

Thanks
On Wed, Mar 6, 2019 at 1:21 PM chegewara<EMAIL_ADDRESS>wrote:

https://github.com/nkolban/esp32-snippets/blob/master/LICENSE
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nkolban/esp32-snippets/issues/828#issuecomment-470240517,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHyzP0RBapN-5Ui_7IxV8KCpJvht3b8tks5vUBVKgaJpZM4bhkJs
.


[FEATURE] Add a scroll-to-top button

Is this a unique feature?

[X] I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.
Scrolling down to the bottom of the website and then scrolling back to top can sometimes annoy users.
Proposed Solution
A scroll-to-top button will help in easier navigation and thus improve user experience.
Screenshots

Do you want to work on this issue?
Yes
If you want to work on this issue...
I would create a button that would come into view when the user starts scrolling down the website. On clicking the button the user will automatically be led to the top of that page.

@akash0708 I am not sure that you did check the closed issues as this has been raised on multiple occasions and closed, as this is not a feature we are looking for.  I am therefore closing this issue.


View Service

Introduce a ViewService which knows about Nitro's views.
This can be some sort of a flat list (or a tree, see #19) which then can be used in the view_list helper (here) and the router (here).
Performance-wise it might be a tad slower than the current implementation but a lot more readable. See here.
Ideally the list doesn't need to be recalculated on every request but can be cached. This might introduce new issues when creating/deleting/renaming views, but should be solvable.
Maybe this can be somehow integrated with express/hbs?

now we have a lil helper for views - bit more readable (470de26395b656842568746f734695e8d2bd1aca)
will close now.


NeuroPoly logo disappears in dark mode

Here's how it looks like:

Related to https://github.com/neuropoly/axondeepseg/issues/480
There must be a way to deal with that intelligently... having maybe two images: one for dark mode one for bright mode.

See below. I do not see the image in the repo so it is hosted OUTSIDE of this repo and is not a problem at IvadoMed OR ADS.
This is the source file: https://raw.githubusercontent.com/ivadomed/doc-figures/main/contributors/neuropoly_logo.png
The best effort/reward action is to add white background to the image. It will look best and fix the issue across all repos.
I have updated the fixed logo below and whoever has access to "https://github.com/ivadomed/doc-figures" should be able to open a PR there to address this. Recommended to instead of using transparent GIF/PNG, have white background for the logo where current transparency resides.
Could someone transfer this issue to "ivadomed/doc-figures" repo?


Feature request: Stop node from ANY directory

People using aeproject should be able to stop the running instances of it from ANY directory.
Steps to reproduce:

Create an aeproject
Spin up a node via aeproject node
Go back, and create another project
Try to use aeproject node --stop in second project's directory to stop the docker instances.

➜  waellet-contracts git:(master) ✗ aeproject node --stop
===== Node is not running! =====
➜  waellet-contracts git:(master) ✗ aeproject node

===== Port [3001] is already allocated! Process will be terminated! =====
Cannot start AE node, port is already allocated!
➜  waellet-contracts git:(master) ✗ docker ps -a
CONTAINER ID        IMAGE                            COMMAND                  CREATED             STATUS                      PORTS                                      NAMES
74020d07ad84        nginx:1.13.8                     "nginx -g 'daemon of…"   4 days ago          Up 4 days                   80/tcp, <IP_ADDRESS>:3001-3003->3001-3003/tcp   example_todo_proxy_1
534c92f08f92        aeternity/aesophia_http:v3.2.0   "/docker-entrypoint.…"   4 days ago          Up 4 days (healthy)         <IP_ADDRESS>:3080->3080/tcp                     example_todo_compiler_1
ad245be4fd18        aeternity/aeternity:v4.1.0       "/docker-entrypoint.…"   4 days ago          Up 4 days (healthy)         3013-3015/tcp, 3113/tcp                    example_todo_node1_1
3e7272c06878        aeternity/aeternity:v4.1.0       "/docker-entrypoint.…"   4 days ago          Up 4 days (healthy)         3013-3015/tcp, 3113/tcp                    example_todo_node3_1
cb488664ec9d        aeternity/aeternity:v4.1.0       "/docker-entrypoint.…"   4 days ago          Up 4 days (healthy)         3013-3015/tcp, 3113/tcp                    example_todo_node2_1
3246727c2e2b        aeternity/aesophia_http:v3.2.0   "/docker-entrypoint.…"   6 weeks ago         Exited (255) 3 weeks ago    <IP_ADDRESS>:3080->3080/tcp                     addressbook-aepp-aeternity_compiler_1
ce121ee85a39        aeternity/aeternity:v3.2.0       "/docker-entrypoint.…"   6 weeks ago         Exited (255) 3 weeks ago    3013-3015/tcp, 3113/tcp                    addressbook-aepp-aeternity_node1_1
1fc414c88fde        aeternity/aeternity:v3.2.0       "/docker-entrypoint.…"   6 weeks ago         Exited (255) 3 weeks ago    3013-3015/tcp, 3113/tcp                    addressbook-aepp-aeternity_node2_1
a2296f94d779        aeternity/aeternity:v3.2.0       "/docker-entrypoint.…"   6 weeks ago         Exited (255) 3 weeks ago    3013-3015/tcp, 3113/tcp                    addressbook-aepp-aeternity_node3_1
19396ef3e47e        nginx:1.13.8                     "nginx -g 'daemon of…"   6 weeks ago         Exited (255) 3 weeks ago    80/tcp, <IP_ADDRESS>:3001-3003->3001-3003/tcp   addressbook-aepp-aeternity_proxy_1
8840edef2149        cypress/browsers                 "node"                   4 months ago        Exited (255) 3 months ago                                              wizardly_clarke
➜  waellet-contracts git:(master) ✗

@mradkov hey this issue is already in development and it will be added in the next release probably. Thanks for the feedback. The reason why it is not currently working is because of some limitations of the docker-compose.
Stay tuned for the next updated version.
Martin

Hey @mradkov,
Your issue has been resolved in #273
This has been added in the latest release of aeproject @2.0.1
Hope you enjoy it.
Hristiyan

Thanks!


Set docs docstring_style

Hi, Thank you for this great library!
It seems that the docstrings are not rendered correctly in the docs. I think we should explicitly set the docstring_style because it defaults to "google" but outlines is using numpy.
Before:

After:

There seem to be other issues in the docstrings:

for example Properties should be Attributes
only openai and transformers models are present in the api reference

I'm happy to make followup PRs for those.
Please let me know if I missed something, I couldn't find related issues/PRs.

Thank you so much for this fix!


Menghan

Changed run and write_data in sandpile.py. Changed the branching_parameter func in data_utils.py about truncation rule. Added spike_density_plot in plotting_utils.py. Added some running parameters settings func in .ipynb.


Mode selector for startup

Now that we start an electron browser as part of PiClock, need to add a way to determine if the code is starting as a server / client / all in one.
Basically, under the current architecture, you could use a single instance to poll the weather, and then display it on multiple screens / browsers / etc.  This would allow multiple clocks from a single API call.

Mode selector implemented, but electron framework requires an X windows server, so server mode still requires an X session, even though there is no rendering occurring.  Not a show stopper, so calling this closed unless someone complains.


⚠ Punto de Fuga has degraded performance

In 748e173, Punto de Fuga (http://puntodefugapodcast.com) experienced degraded performance:

HTTP code: 200
Response time: 12917 ms

Resolved: Punto de Fuga performance has improved in 183365a.


Use CSS layers for implementing utility classes

Feature Description
Gitea has a helper.css file with a host of utility classes. However, they use important!. Instead, have we thought about using CSS layers? Here's a quick example of what I have in mind.
/* We would need to remove fomantic from webpack and add it to the CSS file */
/* Notice it is a named called framework */
@import url("../fomantic/build/semantic.css") layer(framework);

/* Custom utilities that don't need the use of important */
@layer utilities {
  .gt-mt-0 { margin-top: 0; }
  .gt-font-light { font-weight: var(--font-weight-light); }
  .gt-relative { position: relative; }
}

/* Here we order the layers in the order we want them to be in the final CSS file */
@layer framework, utilities;

CSS layers are well supported: https://caniuse.com/css-cascade-layers

It seems pretty new. I guess it would break some browsers like https://github.com/go-gitea/gitea/pulls?q=is%3Apr+palemoon+is%3Aclosed

@wxiaoguang according to the Gitea docs, we are covered. Gitea only supports the last 2 versions of Chrome, Firefox, Safari, and Edge. These versions have implemented CSS layers.

@wxiaoguang according to the Gitea docs, we are covered. Gitea only supports the last 2 versions of Chrome, Firefox, Safari, and Edge. These versions have implemented CSS layers.

Theoretically, I could agree. But personally I haven't found a reason to introduce CSS layers soon.

CSS layers could be more modern, while!important also works and doesn't bring real problems at the moment.
CSS layers could break some users, while !important just works.
There are far more other problems in Gitea's frontend than !important problem, while these more important problems could have higher priority.

@wxiaoguang according to the Gitea docs, we are covered. Gitea only supports the last 2 versions of Chrome, Firefox, Safari, and Edge. These versions have implemented CSS layers.

Theoretically, I could agree. But personally I haven't found a reason to introduce CSS layers soon.
* CSS layers could be more modern, while`!important` also works and doesn't bring real problems at the moment.

* CSS layers could break some users, while `!important` just works.

* There are far more other problems in Gitea's frontend than `!important` problem, while these more important problems could have higher priority.

What would you say is more important than !important at the moment that can be improved? We have had issues with !important taking precedence over styles and generally polluting the code-base.
Now that we support tailwind, shouldn't we start deprecating the helper.css functions, or am I misunderstanding?

What would you say is more important than !important at the moment that can be improved? We have had issues with !important taking precedence over styles and generally polluting the code-base.

Yup, that's one of the root problems. These !important rules are written intentionally to globally override other global styles (from Fomantic UI, or from Gitea's old bad design). If you would like to use CSS layer to replace, then it might need a "globally polluting" CSS layer to override other global styles (just like before?). I don't see much difference at the moment.
If you think CSS layer could really help about the global overriding/polluting, could you help to  propose a simple demo about how to implement it?

Now that we support tailwind, shouldn't we start deprecating the helper.css functions, or am I misunderstanding?

Yup, the deprecating has started, it also needs a lot of work, helping to migrate the styles is very appreciated. So IMO the first step is to clearly deprecate the helper.css , instead of introducing a new approach too soon.

What would you say is more important than !important at the moment that can be improved? We have had issues with !important taking precedence over styles and generally polluting the code-base.

Yup, that's one of the root problems. These !important rules are written intentionally to globally override other global styles (from Fomantic UI, or from Gitea's old bad design). If you would like to use CSS layer to replace, then it might need a "globally polluting" CSS layer to override other global styles (just like before?). I don't see much difference at the moment.
If you think CSS layer could really help about the global overriding/polluting, could you help to propose a simple demo about how to implement it?

Thanks, I understand the concern a bit more. We can take a look at a demo, but sounds like starting on the issue below makes more sense initially.

Now that we support tailwind, shouldn't we start deprecating the helper.css functions, or am I misunderstanding?

Yup, the deprecating has started, it also needs a lot of work, helping to migrate the styles is very appreciated. So IMO the first step is to clearly deprecate the helper.css , instead of introducing a new approach too soon.

Excellent. Totally agree. We can help with that effort.

We close issues that need feedback from the author if there were no new comments for a month. :tea:


Toolbar quick return

I scrolled to bottom too much and wanted to do a search. I had to scroll back to the top to find the search button.

I've toyed with this idea but think that you're likely in either feed browsing 'mode' or searching. It seems unlikely that you switch between these tasks. I also really like the simplicity of a static toolbar which emphasizes that content is literally the topmost entity.  For these reasons, i'm inclined not to add quick-return but I could be convinced otherwise.

I was browsing. I scrolled really much. And one of the designs were really similar to something I remember vaguely. I had to search and find it. I found it eventually. Quick return would help me in this scenario. But in overall use case of the app, I am not sure.


Implement Circular Binary Segmentation algorithm

We need to have a Circular Binary Segmentation algorithm implementation in Java. The algorithm is described here:
Olshen, A. B., Venkatraman, E. S., Lucito, R., and Wigler, M. (2004).
Circular binary segmentation for the analysis of array-based dna copy
number data. Biostatistics, 5:557–72.
and speed improvements described here:
Venkatraman, E. S. and Olshen, A. B. (2007). A faster circular binary
segmentation algorithm for the analysis of array cgh data. Bioinformatics,
23:657–63.
The R implementation is in the DNACopy package:
http://bioconductor.wustl.edu/bioc/vignettes/DNAcopy/inst/doc/DNAcopy.pdf
The requirement is to take data from the R package and implement the algorithm to produce results equivalent to those from R (there may be small differences due to random number generation).

@cwhelan and @LeeTL1220 please chip in regarding requirements.

the speed requirement is to be within 5x of the R code.

it's acceptable to call out to R as the first version of the algorithm. Use RScriptExecutor

Ported to hellbender-protected: https://github.com/broadinstitute/hellbender-protected/issues/10


Cant battle anymore

I used the walk anywhere but now I can't battle anymore i tried refreshing the website it still doesn't work any way to fix my issue?

i cant even battel bro

same

No, you can't,  just create a new account or so lay prodigy anymore.


hardening vitor

http://forums.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/t/vitor-safely-edit-the-tor-configuration-file/13213/20

Not hardening, more like echoing useful info.
Pointing out “it’s a symlink” would be good for usability. If you like implementing this. Small usability gain.
if test -L /path/to/filename ; then
   echo something
fi

From all of the file alternatives, I don’t think vitor should edit anything that is not a a -f regular file. What do you think?

Yes, edit regular file only.

In the end, it was hardening because it was not blocking non regular files, it was just failing on the editor if it was a directory and not copying to temporary location if it was not a regular file, so making an empty copy.


Add youtube

Add youtube search in main.py

I would like to work on this issue!!

I would like to work on this issue!!

@uniocto assigned. Make sure to update the fork since some changed are made recently.


file not downloading when stream initiated in app

The Issue
When attempting to stream a video, the download appears to hang before any data is received. A file is created in the download directory but it sits at 0 bytes.
Steps to reproduce

launch lbrynet-daemon (lbrynet-daemon-v0.10.3rc4)
launch lbry app (LBRY_0.10.0_amd64)
navigate from discover page to video content page
press play

Expected behaviour
video should begin downloading in daemon and playing after ~30s
Actual behaviour
Download begins but no data is received. The daemon reports the download is proceeding, sending a message every second "lbrynet.lbrynet_daemon.Downloader:78 Downloading stream data (### seconds)." The '###' counts up from 1 second until it hits 180, at which time the download times out and the daemon reports we already have the file. After some time (180 seconds?) the loading screen in the browser changes to contain the following message: "Started 1 - capital. - Pillsbury Boy.mp4, got 0/29 blobs, stream status: running"
After navigating away from the content page and back, "0% Complete" is displayed where the "Download" link normally sits, and I'm greeted with the "Started 1 - capital. - Pillsbury Boy.mp4, got 0/29 blobs, stream status: running" message within seconds of pressing play.
The file is indeed present in the download directory, but sized at 0 bytes.
System Configuration
{
"id": null,
"jsonrpc": "2.0",
"result": {
"build": "rc",
"ip": "<IP_ADDRESS>",
"lbrynet_version": "0.10.3rc4",
"lbryschema_version": "0.0.4",
"lbryum_version": "2.7.22",
"os_release": "4.4.0-78-generic",
"os_system": "Linux",
"platform": "Linux-4.4.0-78-generic-x86_64-with-Ubuntu-16.04-xenial",
"processor": "x86_64",
"python_version": "2.7.12"
}
}

LBRY Daemon version: v0.10.3rc4
LBRY App version: LBRY_0.10.0
LBRY Installation ID: unsure
Operating system: Ubuntu 16.04
(just noticed the 10.1rc1 release is available for the app, will attempt to reproduce on new release)

Anything Else
Unsure if related, this is the state of my daemon after the preceding events: http://imgur.com/dhVo2eN
Screenshots
See http://imgur.com/a/Hg5SV for illustrative screenshots. It's more than one or two but I wanted to capture the state of the client both during and after the problem first occurred.

getting similar behavior on LBRY_10.1rc1:
when starting the daemon the connection to the file in question (pillsburyboy) is initialized. However an error is thrown by EncryptedFileManager ~80ms before this happens. Could be unrelated, EFM appears to be working fine 24ms before the pillsburyboy DL is initialized.
http://imgur.com/HvYFKHA
Missing from that screenshot is a message ~140ms later:
2017-05-22 12:45:49,876 INFO     lbrynet.lbryfilemanager.EncryptedFileDownloader:32: lbry://pillsburyboy (2771b9) is unknown
And here's what happens when pressing play to start the stream in the browser:
http://imgur.com/qihHkcr
On the browser side of things everything is the same as reported above except now the message "Downloading stream... not long left now!" has replaced the loading screen message containing info about number of blobs downloaded.

Can you try again on the latest version?

What's the URI for the claim.. I'll try it here too

This is no longer happening in the 0.12 release.

Please close the issue.


Add onScheduled callback in job

i faced with a task where i need to handle when the job was added to the queue, is it possible to add some callback to notify particular a job?

Can you explain this a little better? I don't understand what you mean with queue. When the job runs, then you immediately receive the callback in the job.

right, but when we don't meet requirements (like connection, etc) - there are no callbacks in the job, right? just reschedule every time we don't meet requirements.

i meant callback similar to android async task:
onPreExecute, onBackground, onPostExecute.
But in this case it could be: onBeforeRun, onRun, onAfterRun, or something similar.

I'm sorry, but I don't intend to extend the API. You can achieve the same, if you set requirements enforced to false. Then you'll receive a callback and can manually check if the requirements are met. That has the same effect.
new JobRequest.Builder("Tag")
        .setExecutionWindow(3_000, 4_000)
        .setRequiredNetworkType(JobRequest.NetworkType.CONNECTED)
        .setRequirementsEnforced(false) // that's the default
        .build()
        .schedule();

// and in your job
Device.getNetworkType(getContext())

In this case my job will be executed every time even if requirements were not met. it's the same as just to run a job...

No, that's not true. The requirements enforced flag is mainly helpful for the AlarmManager API, which does not support any requirements and they were back-ported. However, the other APIs respect the requirements, even if they're not enforced.


Occupied_Heating_Discharge_Air_Flow_Setpoint

In point-setpoints-airflow I see "Occupied_Heating_Discharge_Air_Flow_Setpoint" but I am looking for "Heating_Discharge_Air_Flow_Minimum_Setpoint".  The context is around a electric heating coil which require a minimum amount of airflow to prevent a high temperature safety.  This number is usually calculated by the kW rating and delta-T I believe.  Did I miss it somewhere?

You are looking for a Parameter class, not a Setpoint class in that case -- Parameters, specifically Limits, can place policies around other values like Setpoints. In this case the class you are probably looking for is brick:Max_Occupied_Heating_Discharge_Air_Flow_Setpoint_Limit


Projects: Add ability to display social network buttons (e.g. Github)

Hi,
One useful addition could be to enable social buttons for projects themselves: in many cases, a project will have its own GitHub repository, or Twitter/Facebook/YouTube accounts, and it would be great to be able to add them to a project automatically. Something simply like:
[params.social]
icon = "github"
icon_pack = "fa"
link = "//github.com/gcushen"

in the TOML headers of a project, for instance. The buttons could then show directly under the project thumbnail in the home page, and just under the title in the project page.

I would also be happy to have this features. Right now I use some "ugly" tricks :
If external_link is filled then the link to your project will be this external_link but you can still access your project by using its Permanent Link (yourwebsite.io/project/yourproject) : a Go to the project website will appear (using the external_link).
An ugly trick is to change the project layout to force the local link to be used when .Content is filled, in themes/academic/layouts/partials/widgets/projects.html line 67 :
Change {{ if $project.Params.external_link }} by {{ if and (not (.Content)) ($project.Params.external_link) }}. This way, when Content is filled, the home page will link to the local page of the project.
I know this is not perfect as you have only one link and it's not social links. I might see and propose something.

Thanks for the PR, I think it could be a nice feature, especially for big projects which are more likely to have various social networking elements.
I'm not sure about the layout and location of the social links near the share links though. Open to feedback from everyone...

Another way this could be integrated is via custom buttons (like publications have) but using custom buttons which support icons.

I agree that it's too close to the other socials links. Do you suggest to use quite the same design that is used for publications ?

I think the features requested in this issue and #645 are quite similar. Both involve the ability to add buttons (with/without icons) that might link to the projects code, data, documentation (if it's some API), youtube channels etc. Maybe their functionality could be merged.


Fix links

Description
Changes proposed in this pull request (what was done and why):

Updated a broken link
Removed a link to a non-existing section from the ToC

Changes refer to particular issues, PRs or documents:

Testing the new custom link checker

Traceability

[ ] The PR is linked to a GitHub issue.
[ ] New features have a milestone set.
[ ] New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
[ ] The corresponding GitHub issue has a respective area and kind label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.
[ ] Adjusted the documentation if the change is user-facing.
[ ] The feature is unit-tested
[ ] The feature is e2e-tested

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


Are there any plans to support the naming method of anime like vcb?

like: [VCB-S&philosophy-raws][Seraph of the End：Vampire Reign][BDRIP][02][HEVC Main10P FLAC][1920X1080].mkv
Seraph of the End：Vampire Reign is title
VCB-S&philosophy-raws is group

It seems to work mostly fine, though will try and fix the issue with the title.
I hadn't seen torrents with that kind of format, do you have other similar examples? Would help making other future matches more accurate!

Also, for now, I'd suggest comparing strings not with equality but with in, so if there's an excess it still works for you.

I will provide some examples as soon as possible.
Friends.S09.720p.BluRay.DD5.1.x264-NTb\Friends.S09E23E24.720p.BluRay.DD5.1.x264-NTb.mkv
and it is  issue for this.
title show Friends S09

Thanks for the list! Am currently working through them, will prioritise title-breaking stuff and look at encoder/group issues later as they matter a bit less I think.
Though if you are using encoder/group info, I'd love to know how! I've never really looked at them in my own projects so usually work on them less, but knowing a reason why they matter would push me to get them working better. Encoder is often not even tested for at the moment.
Might take a bit to release as well as I've been having issues with my CI, if I fix most of these I'll just manually upload the latest version to PyPI. Thanks again!

dev branch now has fixes for all issues but 18 and 21.

Fixed all.

Fixes included in 2.4


Connection from SSRS to Azure Analysis Service

Hi Team,
We installed all latest client libraries and tried all connection string types to connect from ssrs data source to azure analysis services still it does not connect.
Are we missing somethin here?
Regards,
Vishal

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

ID: 7777fdb6-db9d-a6e6-724e-acabe0d5d9f8
Version Independent ID: 8457dd13-3401-c6a1-26e0-d3c7c720e7f3
Content: Connecting to Azure Analysis Services servers
Content Source: articles/analysis-services/analysis-services-connect.md
Service: azure-analysis-services
GitHub Login: @Minewiskan
Microsoft Alias: owend

@vishalaj1
Thanks for the feedback! We are currently investigating and will update you shortly.

Hi,
If this helps identify problem.
We have AD on Azure, we are able to connect using management studio.
When we use Microsoft Analysis Service connection type from data source for ssrs we cannot connect!
When we connect using oledb connection we can connect thru ssrs datasource but it is not accepting dax query parameters! We cannot develop using oledb connection!
Regards,
Vishal

We have following scenario:
On - Prem:
Server 1 - DB Server - SSRS ReportServer, ReportServerTempDB is placed here
Server 2 - SSRS Report Server - Report engine is installed here
Server 3 - SSAS Tabular Server - Installed here
Clients are able to access the reports pointing to Server 3. (We have added SPNs correct for on prem domain account)
Now, we have moved Server 3 to Azure Analysis Service
Server 1, Server 2 - are still same
Server 3- Azure Analysis Service
We have registered an App - Provided Read, Write access to Azure Analysis Service and created a key, Added app:abcd@asdf as Analyis Server Admin.
Using SQL Server Management Studio:
If we use Active Directory password - app:abcd@asdf and key as password we can connect.
But when we use the same credentials on Report Server Data Source it fails -
ERROR: Report server unique dump occured. Exception: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.ArgumentException: Authentication failed: User ID and Password are required when user interface is not available., Message: , Unhandled Exception: False

@vishalaj1 this feature is not officially available yet.  Here is the User Voice request to have this implemented, where you can see some workarounds and suggestions:
https://feedback.azure.com/forums/556165-azure-analysis-services/suggestions/17173610-built-in-ssrs-support-for-azure-as


docs: npm compatible documentation

Currently the documentation for both npm and deno is the same. Npm should have npm specific documentation for it's own module system.

Note: https://github.com/denoland/dnt#mapping-specifier-to-npm-package-subpath

Will this be able to affect JSDoc comments?


Sidebar > The sub-options are in incorrect place

Pre-condition
User logins successfully and is on the W2 homepage
Steps to reproduce the problem

Click on a specific option which has sub-option (Works & Projects/ Office/ Asset & Facility)
Click on arrow button at the bottom of the sidebar
Observe the sub-option that is displaying

Expected Result
The sub-option should be displayed besides the icon (see the 1st screenshot)
Actual Result

The sub-options are displayed in incorrect place
The distance from the sub-option to the icon is too far
(see the 2nd screenshot)

Screenshots
Expected:

Actual:

fix

Done


Document Observable.subscribe()

We missed the most basic thing: to document the subscribe method under Observable. It's currently missing. For context: https://twitter.com/Shahor/status/839512270061334530
PRs welcomed

Yeah, I had that in mind. I guess I will make it a priority. More involved description of an Observer (and partial observers as well) should probably be a companion.

The real question is if we want it te be dry and precise, or newcomer-friendly? What I wrote so far sounds more like an introduction to how subscriptions work and what is a lifecycle of Observable stream (next, complete, error). I am not sure if that is a good or should I just focus on what subscribe accepts etc.

The newcomer-friendly part is the Manual, where we explain those types of stuff. The JSDoc can be more technical (and/or type aware) description. The exception is operators, which need newcomer-friendly description because they aren't described in the Manual.
Essentially the Manual teaches the essential concepts and methods in RxJS, but the API ref explains operators and factories in details.

I was wondering if there is a reason that subscribe() is currently missing from the online documentation


1.10.8 release

Urgency

[ ] Blocker
[x] High
[ ] Medium

Requirements

See the contribution guidelines.
Build content locally and test for formatting/links.

Scheduled for release on Thursday afternoon Pacific, links need review for consistency but won't go live until the release.


Extractor uses Saver to Write to S3

Extractor needs to be saving to Disk and S3

This PR is ready for Review


Import projects via config file

Declaring what to import already from a config file / k8s Secret.
 But the "spin up pre-populated environment of Wharf" is a promising feature.
This should get an RFC!
Concerns:

There will be secrets in these configs.

This would involve the API having to speak with the providers. We have to be careful here not to introduce a circular dependency chain as the providers currently depend on the API. Or the providers read the config instead

Either we watch for updates in the configfile, allowing hot reloading, or we only import on boot. Config could have settings such as:
importOnStartup: true
importOnConfigChange: true

Maybe a new "Import from config" operation in the frontend via new API endpoint?
Trigger it with .wharf-ci.yml?
Pros of auto importing:

Can be deployed without further actions

Cons of auto importing:

More error prone. We have to deal with project collisions and previously deleted projects


Update documentation for .NET Core 2.0

Rendered page at:
https://github.com/jerboaa/s2i-dotnetcore-ex/tree/2.0-doc-update

@aslicerh Please take a look when you get a chance.

@jerboaa Looks good to me. Ship it.


Moving the tree navigator

We need some way to move the navigator around when it is blocking the view

It was decided to remove this functionality in the new editor. Instead the sidebar always stays at the right side, but user can hide it with a toggle button.


No jest "codeframes" in test output

Is this a bug report?
Yes
Did you try recovering your dependencies?
No. This happens on a fresh install of create-react-app. Yarn version 1.6.0
Which terms did you search for in User Guide?
"test" "jest"
Environment
Environment:
  OS:  macOS High Sierra 10.13.4
  Node:  10.0.0
  Yarn:  1.6.0
  npm:  6.0.0
  Watchman:  4.9.0
  Xcode:  Not Found
  Android Studio:  Not Found

Packages: (wanted => installed)
  react: ^16.3.2 => 16.3.2
  react-dom: ^16.3.2 => 16.3.2
  react-scripts: 1.1.4 => 1.1.4

Steps to Reproduce

create-react-app dir && cd dir
Change built-in test to fail.
Run tests with yarn test

Expected Behavior
A codeframe (https://facebook.github.io/jest/blog/2017/12/18/jest-22.html#codeframe-in-test-failures) would be displayed.
Actual Behavior
Codeframe missing from test output.
Reproducible Demo
Change built-in test to:
it('fails', () => {
  expect(false).toBe(true);
});

Run yarn test

That's in Jest 22, CRA is on an older version (updated in alphas, though)


Add override flags for Nix generic-builder

Currently, cabal2nix supports following CLI flags:

--no-check
--no-haddock
--no-hyperlink-source

Appropriate CLI flags for stack2nix should accept a list of parameters (packages); an empty list means override globally for all packages.

Update.
Stack packages set takes into account only library and executable dependencies and completely ignores test dependencies of its packages. Thus, to be sound, Stack packages-override should be built with no-check and no-haddock arguments.

Update
The current implementation of cabal2nix fromGenericPackageDescription marks packages broken if they have missing dependencies. Since Stackage is only a subset of Hackage (see the previous comment), test and benchmark dependencies may be missing. As an example, see lts-6-35 unordered-containers package that miss hashmap benchmark dependency.
Stackage packages that miss test or benchmark dependency should not be marked as broken.

resolved in e268fb7f6b78da11258d15cd9ea1c75e563906de


[DOCS] Add CONTRIBUTING.md file

Is your feature request related to a problem? Please describe.
Since people will be contributing to this repository, I think it would be helpful to have a CONTRIBUTING.md file as a guide for contributions in this repository.
Describe the solution you'd like
I would like to add a CONTIBUTING.md file to this repository.

@visheshrwl i can continue on this issue can you assign me the issue
of updating of contributing.md

@visheshrwl i have create the contribution.md file for this and submitted the pr for the same sir

I would like to contribute on contribution.md file for this. please assign me that issue.


No such property: GROUP for class

Error:FAILURE: Build failed with an exception.

Where:
Script 'https://raw.githubusercontent.com/chrisbanes/gradle-mvn-push/master/gradle-mvn-push.gradle' line: 48

What went wrong:
A problem occurred configuring project ':app'.

A problem occurred configuring project ':library'.
No such property: GROUP for class: org.gradle.api.publication.maven.internal.deployer.DefaultGroovyMavenDeployer

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

@1371030 why would you deploy library to Maven? :) Just comment out line apply from: 'https://raw.githubusercontent.com/chrisbanes/gradle-mvn-push/master/gradle-mvn-push.gradle' from build.gradle if you want to build library from source.

This should be fixed in the code itself. It's quite annoying that about half the repos out there require you to change something in the code to even compile... :(
Please, at least put these instructions on the main page of the repo.


Duplicate entry

It really seems like the entry
wm/concept/causal_factor/economic_and_commerce/economic activity/market/inflation

in wm_metadata.yml is duplicated.  In any case, it's tripping up the Eidos unit test.  Can someone verify and remove if that's the thing to do?

I can't assign anyone, so this is to bring it to @vanh17 's attention.  Thanks.  The change, if any, also needs to get back to Eidos.

Yes, @vanh17, can you please fix this?

Yes, I definitely can. I will check on this when I get off work today.
Best,
Henry
Get Outlook for Androidhttps://aka.ms/ghei36

From: Mihai Surdeanu<EMAIL_ADDRESS>Sent: Friday, June 7, 2019 1:31:26 PM
To: WorldModelers/Ontologies
Cc: Hoang Van; Mention
Subject: Re: [WorldModelers/Ontologies] Duplicate entry (#9)
Yes, @vanh17https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvanh17&data=02|01|vanh17%40hanover.edu|ebb7e69104784ebbd32008d6eb6df881|3b2321d0ffc34a04b6fa567b9bca8a22|0|0|636955254885674191&sdata=MegoY5RTu%2FkJWzCxWa%2FrX%2FCQREWYC8FfUE1phMLFGB0%3D&reserved=0, can you please fix this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWorldModelers%2FOntologies%2Fissues%2F9%3Femail_source%3Dnotifications%26email_token%3DACQD3IXKSPWBGQV36OLDN4LPZKLO5A5CNFSM4HVY4V52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXGPPYA%23issuecomment-499972064&data=02|01|vanh17%40hanover.edu|ebb7e69104784ebbd32008d6eb6df881|3b2321d0ffc34a04b6fa567b9bca8a22|0|0|636955254885674191&sdata=GhTmP%2Fei0UyseVGaXHm69CMJkLHFlSnqSBsrrnbkjNw%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACQD3IRBS7XJFC4HRKI3VH3PZKLO5ANCNFSM4HVY4V5Q&data=02|01|vanh17%40hanover.edu|ebb7e69104784ebbd32008d6eb6df881|3b2321d0ffc34a04b6fa567b9bca8a22|0|0|636955254885684188&sdata=KfBsO2%2Bo7YHj970N5lACJxzuVM3PsCaJUCFL2%2FG5KlE%3D&reserved=0.

I don't see that this has happened.  Are things OK, @vanh17?

Hi Keith,
Sorry for the deplay. I have removed all the possible duplicates  Please let me know if the code is still broken.
Best,
Henry
Get Outlook for Androidhttps://aka.ms/ghei36

From: Keith Alcock<EMAIL_ADDRESS>Sent: Sunday, June 9, 2019 12:01:01 PM
To: WorldModelers/Ontologies
Cc: Hoang Van; Mention
Subject: Re: [WorldModelers/Ontologies] Duplicate entry (#9)
I don't see that this has happened. Are things OK, @vanh17https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvanh17&data=02|01|vanh17%40hanover.edu|dab31f0bc8d543adf6b608d6ecf3aba8|3b2321d0ffc34a04b6fa567b9bca8a22|0|0|636956928644202490&sdata=4sAId31e%2FkA0kZ6v1vXphsFk0oAjRvEaLS0IhV3Xe3E%3D&reserved=0?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWorldModelers%2FOntologies%2Fissues%2F9%3Femail_source%3Dnotifications%26email_token%3DACQD3ITR2IW2JJKSNGM3OITPZUSL3A5CNFSM4HVY4V52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXINDEQ%23issuecomment-500224402&data=02|01|vanh17%40hanover.edu|dab31f0bc8d543adf6b608d6ecf3aba8|3b2321d0ffc34a04b6fa567b9bca8a22|0|0|636956928644212482&sdata=iQv9eRxzI9KklUVjazXq5RzakZWsbJ8qmx1%2FHjRTfwA%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACQD3ITZZM3COUHPSNO7LFTPZUSL3ANCNFSM4HVY4V5Q&data=02|01|vanh17%40hanover.edu|dab31f0bc8d543adf6b608d6ecf3aba8|3b2321d0ffc34a04b6fa567b9bca8a22|0|0|636956928644212482&sdata=O1Xd0EtLQcvNwabHstx0m0o%2FRvzGVtIIyd416t67ERE%3D&reserved=0.

It seems to be better.  I was assuming that the change needed to be done to this WorldModelers/Ontologies repo, to which I have limited access, rather than directly to clulab/eidos.  That's why the call for help.  I guess that the change needs to be back ported now.  Eidos is happy now.  Thanks.

in the future, we should make the changes here [WorldModelers/Ontologies]
first, as this is the "source"
On Sun, Jun 9, 2019 at 8:57 PM Keith Alcock<EMAIL_ADDRESS>wrote:

It seems to be better. I was assuming that the change needed to be done to
this WorldModelers/Ontologies repo, to which I have limited access, rather
than directly to clulab/eidos. That's why the call for help. I guess that
the change needs to be back ported now. Eidos is happy now. Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/WorldModelers/Ontologies/issues/9?email_source=notifications&email_token=ABJCPCN5ARQSYD5I5Y4GN6DPZXGKBA5CNFSM4HVY4V52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXI3UIQ#issuecomment-500283938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJCPCJERMCKCTCBU6ADVOLPZXGKBANCNFSM4HVY4V5Q
.

Fixed with #10


Retry file downloads if the file doesn't exist on disk

Related: https://github.com/matrix-org/synapse/issues/1555


An issue to be cross-referenced while not locked

Good: Even though this issue is completed, cross-referencing it (from #6) DID add a link/note here.


Github Files

Added ability to get item resource details for Github
Added ability to download an item resource for Github
Added ability to upload to an container for Github

¯_(ツ)_/¯


Don't recommend extension base on apps installed on user's computer

How do vscode know what App is on my computer?
Does microsoft collect these info?
If it does, can I disable this feature?

/needsMoreInfo

Story:
I have firefox installed on my computer.
And I found out that vscode recommend extension "Debugger for Firefox" for me.
Since I didn't open any file relate to firefox development.
I'm concern about my privacy about what app I've installed, even what's on my computer

Maybe check if you have an extensions.json file in the .vscode folder, extension recommendations can come from that file.
https://code.visualstudio.com/docs/editor/extension-gallery#_workspace-recommended-extensions

No, both {home}/.vscode and {workspace}/.vscode don't have extension.json.

And it says "because you have Mozilla Firefox installed"

Also if you hover over the extension that is recommended the tooltip will tell you why it was recommended

Maybe they do check your apps :/

In the settings it says that "some recommendations are fetched from a microsoft online service"... maybe if you have windows and install apps via the app store this information is queried by VSCode

Firefox is install by the installer downloaded from Mozilla.
I don't think Mozilla will provide microsoft such info

They do parse your folder
I found the code
extensionTipsService.ts
`
private async getValidExecutableBasedExtensionTips(executableTips:
IStringDictionary): Promise<IExecutableBasedExtensionTip[]> {
	const result: IExecutableBasedExtensionTip[] = [];
	const checkedExecutables: Map<string, boolean> = new Map<string, boolean>();
	for (const exeName of Object.keys(executableTips)) {
		const extensionTip = executableTips[exeName];
		if (!isNonEmptyArray(extensionTip?.recommendations)) {
			continue;
		}

		const exePaths: string[] = [];
		if (isWindows) {
			if (extensionTip.windowsPath) {
				exePaths.push(extensionTip.windowsPath.replace('%USERPROFILE%', processEnv['USERPROFILE']!)
					.replace('%ProgramFiles(x86)%', processEnv['ProgramFiles(x86)']!)
					.replace('%ProgramFiles%', processEnv['ProgramFiles']!)
					.replace('%APPDATA%', processEnv['APPDATA']!)
					.replace('%WINDIR%', processEnv['WINDIR']!));
			}
		} else {
			exePaths.push(join('/usr/local/bin', exeName));
			exePaths.push(join(this.environmentService.userHome.fsPath, exeName));
		}

		for (const exePath of exePaths) {
			let exists = checkedExecutables.get(exePath);
			if (exists === undefined) {
				exists = await this.fileService.exists(URI.file(exePath));
				checkedExecutables.set(exePath, exists);
			}
			if (exists) {
				extensionTip.recommendations.forEach(recommendation => result.push({
					extensionId: recommendation,
					friendlyName: extensionTip.friendlyName,
					exeFriendlyName: extensionTip.exeFriendlyName,
					windowsPath: extensionTip.windowsPath,
				}));
			}
		}
	}

	return result;
}

`

This seems to be more privacy-violating telemetry that isn't actually disabled when setting the global Enable Telemetry setting to false. It may be because they choose not to define it as "telemetry", similar to the experiments-related behavior that was addressed in another recent issue.
While I can appreciate an argument for having the setting to disable this to be separate from the global one, I think the ethical thing to do would be to still have it appear in the settings results when users search for telemetry settings. That would avoid any appearance of bad faith on the part of Microsoft, since I'm sure many users trying to disable telemetry don't expect vscode to continue to snoop around their computer's file system after disabling the only obvious settings.

We don't send anything back in telemetry here, it all happens on the desktop in an attempt to provide users with recommendations of useful extensions based on what they have installed.


Replace ScanTask's resultQueue with Future

Originally from https://issues.apache.org/jira/browse/ACCUMULO-3357

ScanTask has a single element ArrayBlockQueue it uses to pass results back from the worker thread / pass errors back / wait for worker thread to complete. This sounds like the perfect case for a Future.

Closing this for now. Doesn't seem like its worth changing at this time. This can be re-opened if it turns out to be more of a priority at somepoint.


Submit Starter Code

This pull request should address #6 , #20 .

modified submission.ts to scrape different HTML elements conditioned on submission status
modified helper.ts and interfaces.ts to accommodate new submission status
created a submit() method in old_index.ts to get the results of a submission. returns a Submission object.
created test cases in src/testcases for submit() method
created a main() method in old_index.ts to test if submit() is working correctly

Modifications to consider:

having a single Helper with one set of "session", "csrfToken" making HTTP requests has caused me to encounter "Rate Limit Exceeded" from Leetcode

solution: create User objects to make HTTP requests individually?

error handling for in submission.detail(). Sometimes the response could be missing fields that we are scraping for. I think it   would make sense to wrap the code with try...except blocks

Looks good. I've been testing it and I it seems to work well. One thing I think should be added is the total_correct and total_testcases attributes of submission. These could be passed to the front end so the player could know how many test cases each of his submissions passed.
To get this working with sockets, I think the best approach would be to integrate these functions into the Race class in src/socket/race.ts. A socket event listener could listen for a "submit" event that passes the code and language used. This listener could then call some function in Race that handles the submission and emits a socket event to the Race's socket room with details of the results.

I'll leave this open for now since I didn't have time to test it too thoroughly. I'll be able to look over it more tonight.

total_correct and total_testcases should already be attributes of submission.
I've changed the code from the last sprint. Getting a problem by difficulty is no longer a route. Now all of that logic should be in the static class src/lib/LeetcodeProblems.
I've added some code in race.ts to get a problem.

Should have just changed the setProblem() method to be non-static, will work the sockets later today.


cri-o 1.29 Tetragon not show namespace/pod information

What happened?
It seems that with CRI-O 1.29, Tetragon does not visualize information about namespaces and pods.
Check the logs of the test container:
kubectl exec -ti -n tetragon tetragon-r292s -c tetragon -- tetra -d getevents -o compact|grep passwd
time="2024-06-24T14:54:53Z" level=debug msg="Processing event" event="process_exec:{process:{exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzUyOTE2NjY1NDAxMzE6MzU1MzYzNw==\"  pid:{value:3553637}  uid:{}  cwd:\"/\"  binary:\"/bin/cat\"  arguments:\"/etc/passwd\"  flags:\"execve rootcwd clone\"  start_time:{seconds:1719240893  nanos:353654638}  auid:{value:4294967295}  parent_exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzQ4NTUwMjk4NTEwNzk6MzU1Mjc0OQ==\"  tid:{value:3553637}}  parent:{exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzQ4NTUwMjk4NTEwNzk6MzU1Mjc0OQ==\"  pid:{value:3552749}  uid:{}  cwd:\"/\"  binary:\"/bin/sh\"  flags:\"execve rootcwd clone\"  start_time:{seconds:1719240456  nanos:716961213}  auid:{value:4294967295}  parent_exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzQ4NTUwMjM4Nzk4MTM6MzU1Mjc0Nw==\"  tid:{value:3552749}}}  node_name:\"mynode.local\"  time:{seconds:1719240893  nanos:353650458}"

🚀 process mynode.local /bin/cat /etc/passwd
time="2024-06-24T14:54:53Z" level=debug msg="Processing event" event="process_exit:{process:{exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzUyOTE2NjY1NDAxMzE6MzU1MzYzNw==\"  pid:{value:3553637}  uid:{}  cwd:\"/\"  binary:\"/bin/cat\"  arguments:\"/etc/passwd\"  flags:\"execve rootcwd clone\"  start_time:{seconds:1719240893  nanos:353654638}  auid:{value:4294967295}  parent_exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzQ4NTUwMjk4NTEwNzk6MzU1Mjc0OQ==\"  tid:{value:3553637}}  parent:{exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzQ4NTUwMjk4NTEwNzk6MzU1Mjc0OQ==\"  pid:{value:3552749}  uid:{}  cwd:\"/\"  binary:\"/bin/sh\"  flags:\"execve rootcwd clone\"  start_time:{seconds:1719240456  nanos:716961213}  auid:{value:4294967295}  parent_exec_id:\"ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjI4NzQ4NTUwMjM4Nzk4MTM6MzU1Mjc0Nw==\"  tid:{value:3552749}}  time:{seconds:1719240893  nanos:354155578}}  node_name:\"mynode.local\"  time:{seconds:1719240893  nanos:354155575}"
💥 exit    mynode.local /bin/cat /etc/passwd 0"

Switching log to tracing mode I can see this messages:
tetragon time="2024-07-05T08:24:38Z" level=trace msg="process_exec: no container ID due to cgroup name not being a compatible ID, ignoring." cgroup.id=98592 cgroup.name=container process.binary=/bin/sh process.exec_id="ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjcyMjM0MTAxNzQ3OTIyOjIyNTA2NA=="

where exec_id is the same from:
{
    "process_exec": {
        "process": {
            "exec_id": "ZGtyLWNiLXV4aTQwMi5pdHRlc3QuY29ybmVyLmxvY2FsOjcyMjM0MTAxNzQ3OTIyOjIyNTA2NA==",
            "pid": 225064,
            "uid": 0,
            "cwd": "/",
            "binary": "/bin/sh",

I execute crictl insepct and crictl inspect <container_id>| grep cgroupsPath
and into cgroupsPath:
sudo find /sys/fs/cgroup//kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2263b521_f8ac_475e_82a0_95937cce8f0f.slice/ -type
d
/sys/fs/cgroup//kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2263b521_f8ac_475e_82a0_95937cce8f0f.slice/
/sys/fs/cgroup//kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2263b521_f8ac_475e_82a0_95937cce8f0f.slice/crio-13af5e5e8dd365f35cd40d268140600b80449b3c956c1ee257961ea51dfc1f74
/sys/fs/cgroup//kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2263b521_f8ac_475e_82a0_95937cce8f0f.slice/crio-4ff86f4fe0ebd2556606a6b049b94ae571e3486c4c265230dc8ce87f887ffd15.scope
/sys/fs/cgroup//kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2263b521_f8ac_475e_82a0_95937cce8f0f.slice/crio-4ff86f4fe0ebd2556606a6b049b94ae571e3486c4c265230dc8ce87f887ffd15.scope/container

Tetragon Version
1.1.2
Kernel Version
6.1.0-24
Kubernetes Version
1.29.2
Bugtool
No response
Relevant log output
No response
Anything else?
No response

It seems that this version of cri-o uses paths such as:

/sys/fs/cgroup//kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2263b521_f8ac_475e_82a0_95937cce8f0f.slice/crio-4ff86f4fe0ebd2556606a6b049b94ae571e3486c4c265230dc8ce87f887ffd15.scope/container

For the container cgroup that do not work well with tetragon.
I think the best solution is to connect to the container runtime (https://github.com/kubernetes/cri-api/blob/c75ef5b/pkg/apis/runtime/v1/api.proto), get the cgroups used, and use the cgroup id to do the mapping. I think we would want to have an option to enable this.
There was a short discussion about this in the Tetragon Community Meeting (July 8th): https://docs.google.com/document/d/1BFMJLdtisiCSLfMct0GHof_ioL-5QVNLEaeMSlk_7Eo/edit#heading=h.cd9xm2lbvnw4.

I'm reopening this to add instructions on how to use the features introduced from #2776


wip: new(docs): update Changelog for 0.34.0

Signed-off-by: Luca Guerra<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area tests

/area proposals

/area CI

What this PR does / why we need it:
Add v 0.34.0 release notes 📝
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LucaGuerra
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval by writing /assign @andreagit97 in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 2fd1f77170ec3cccc82aabf3cdce363b5cb0cf54

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, jasondellaluce, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


support spacy models

for NLP, it would be nice to add support for spacy models

Currently looking at the spaCy API docs, if using the nlp model itself, each model is from Thinc. The pipeline components are NOT Thinc models, but are using a predict method, much like the support of the other modeling frameworks in vetiver. I'm wondering if it is more useful for people to deploy the Thinc model itself, or the larger pipeline objects created with spaCy. There's also another option where we support Thinc models, which can wrap models like PyTorch or TensorFlow, and then support spaCy pipelines separately.


switch to kramdown since GH will drop support

please look here for a sanity check.  LGTM but want another set of eyes.

cc @mochajs/mocha this needs to be addressed before May Day

-- is being rendered as – in using kramdown, which is a good thing imo. But they could use surrounding spaces. Take a look at the 'Pending Tests' section.

Also, Here's is being rendered as Here’s using kramdown, which again is preferable, I believe.

@dasilvacontin fixed the --watch thing

The following block is being rendered quite differently (maybe because of your branch not being up to date with master) : screenshot 2016-04-10 12 21 29

This is due to a tabs/spaces disagreement; I'll fix


Clean the global state

Description
Currently a lot of global state is used (inputs, outputs etc). This makes it very hard to test the application and generally requires running scripts via subprocess which is hard to debug.
This removes the global state in preference for a PriorConfig object to carry around the options. This config object is still created from environment variables.
This also enables the GeoJSON test which was previously disabled because of dependency issues.
Checklist
Please confirm that this pull request has done the following:

[x] Tests added
[x] Documentation added (where applicable)

Notes
This also moves the input and output directories into the data/ directory

@crdanielbusch Ping


#0: Lower timeout of nightly to 40 mins

@TT-billteng @mtatsumiTT @arakhmati
Note we lowered pipelines to 40 mins


Can't resolve '@material-ui/core/Button'

Hello I try to integrate your TimeInput and I have got this error:
./node_modules/material-ui-time-picker/lib/TimeInput.js
Module not found: Can't resolve '@material-ui/core/Button' in '..\node_modules\material-ui-time-picker\lib'
import TimeInput from 'material-ui-time-picker'
render () {
const props = omit(this.props, [
'className',
'id',
])
return (

<TimeInput
{...props}
mode='12h'
onChange={(time) => this.handleChange(time)}
/>

)
}
React 16.4.1

This component is only compatible with @material-ui/core 1.0.0 or later. It's not compatible with earlier versions.


[BUG] Build failure on Mac OSX

Describe the bug
//publish:cel.publish doesn't build on Mac OS. Full error message is below.
I believe the problem is that parser/src/main/java/dev/cel/parser/CelParser.java conflicts with CELParser.java generated by the antlr build rule here:
https://github.com/google/cel-java/blob/cf3d719adf01afd7e0837d2a4e679ec8048f4172/parser/src/main/java/dev/cel/parser/BUILD.bazel#L106-L112
And the default filesystem of MacOS does not have case sensitive file paths. This (https://support.apple.com/lt-lt/guide/disk-utility/dsku19ed921c/mac) looks like the most official documentation of this behavior, and I believe you need to do a full disk reformat to fix so not easy to workaround.
To Reproduce
On OSX:
$ bazel build //publish:cel.publish
INFO: Analyzed target //publish:cel.publish (0 packages loaded, 0 targets configured).
INFO: From Action publish/cel-docs.jar:
javadoc -cp ....
javadoc: warning - You have specified to generate frames, by using the --frames option.
The default is currently to not generate frames and the support for
frames will be removed in a future release.
To suppress this warning, remove the --frames option and avoid the use of frames.
/var/folders/f9/sc20dw5134n9vxn6np883f5c0000gp/T/unpacked-sources790206605151880537/dev/cel/parser/CELParser.java:24: error: interface CelParser is public, should be declared in a file named CelParser.java
public interface CelParser {
       ^
1 error
1 warning

ERROR: /Users/mike.danese/code/cel-java/publish/BUILD.bazel:52:12: output 'publish/cel-docs.jar' was not created
ERROR: /Users/mike.danese/code/cel-java/publish/BUILD.bazel:52:12: output 'publish/cel-docs-element-list-dir/element-list' was not created
ERROR: /Users/mike.danese/code/cel-java/publish/BUILD.bazel:52:12: Action publish/cel-docs.jar failed: not all outputs were created or valid
Target //publish:cel.publish failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 2.182s, Critical Path: 2.03s
INFO: 2 processes: 1 internal, 1 darwin-sandbox.
ERROR: Build did NOT complete successfully

AFAIK, this is a Bazel limitation: https://github.com/bazelbuild/bazel/issues/7627. Java builds are especially susceptible because it caches all of the java classes in the same location.
If the ANTLR generated code is the only problem, I'd be OK with changing its class name to sidestep this (e.g: CELInternalParser.java). I don't have a good way of confirming this. Please feel free to open a PR, I'd be happy to take a look.

Here you go: https://github.com/google/cel-java/pull/194


fix build conflict, rename namespace.

Both modified code and omnisci header file have method named inline_int_null_value which will cause build issue.
and rename namespace facebook::velox::omnisci to facebook::velox::cider

will merge it today. cc @Intel-bigdata/bdf-cider-engine


Migrating to the VS2017 project structure is Tough Bananas

This is akin to plucking your pubes one at a time with a tweezer over a random Thread.Sleep(2000) interval using 2/3 processor cores(3 if you are me).
The MsBuild infrastructure needs a complete rethink(do over).

Xml namespaces are not a thing anymore in CsProj files

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

Becomes
<Project  Sdk="Microsoft.NET.Sdk">

TargetFramework becomes TargetFrameworks to support dotnet standard/core.

<PropertyGroup>
    <TargetFrameworks>net45;netstandard1.6</TargetFrameworks>
</PropertyGroup>

This changes how build targeting works.

Build targeting needs to be change for every CsProj.

 The one Castle.Windsor has and the one defined in Sdk.props. Pathing between the two is PITA.

Compile include is not a thing anymore.

<Compile Include="<folder>\<file>.cs" />

Sdk.props cannot find Microsoft.Common.props. This is perhaps the most frustrating thing. It is kicked out of Build.proj whilst running build.cmd from the root folder in admin mode. Faaark!

Nursing dead code in #205 does not make this any easier because grepping across *.csproj makes things harder, there is just too much noise that comes up.

I recommend keeping the bootstrapper build.cmd in the root folder, and then introducing something like FAKE for doing this, with a completely new .csproj structure supporting dotnet45 at first and then standard 1.6 later(obviously including first class NuGet support). This is one fakking huge PR. Also think moving to appveyor would be better than managing VM's running teamcity. Targetting new frameworks adds extra weight to the build/publish solution. If you want to look at examples please see how I have done it here: https://github.com/cryosharp/fluentwindsor.
Think it is time you guys start thinking about making me a member. I can get us to dotnet core faster and make things a lot lighter in terms of maintenance.

Gentleman, this gets more mental the deeper I go. I am not going to go away until this is done(as I said you will hate me ... #165).
@jonorossi - I just want to thank you for you involvement so far. Please don't be disparaged. I believe we can get this done. Please bear with me.
Doing incremental PR's is not an option. I personally think the flux at Microsoft has created a divergence in terms of how the MsBuild works and backwards compatibility has been forgone. This makes the previous weeks of my clean up m00t in terms of build stuff. Disappointing for me especially but I willing to take the hit. This has left me frustrated though.
The new learnings/frustrations I found tonight:

Baking binary dependencies into master has not done us any favours. NUnit being a case in point. Charlie Pool deprecated the ExpectedException attribute a while ago. Not using a package management for NUnit has hidden this breaking change. Removing this from the code was a pain in the arse but I have done it.

Breaking changes around logging abstractions from Core has caused issues in getting tests to compile for Windsor. I honestly don't believe logging should be abstracted for each logging dependency. That is why you use NuGet. It should be reduced to a lambda func based subscription from a static member which calls out to something that the client code of windsor does, not Windsor or Core itself. This will make logging cloud friendly. Did you know azure application insights was a thing? Log shipping becomes weird in this space. We should stop doing that.

 No matter which way you cut it. I think we should just do it. I am not keen on trying to find incremental ways anymore. I am also not keen on waiting for PR's to take 2/3 days to merge. There is clearly demand for a core version of this(myself included). I will honour the WcfIntegration responses(as in #165). I cant tolerate the maintenance of dead code for #203, https://github.com/castleproject/Attic/pull/2, #205. Please can we merge my PR's? I am running out of patience on this.

On the positive side, the polyfills from Core helped heaps to get things to compile. This is a good thing.

Please see the size of the change for the DNM-PR(DO NOT MERGE PR) just to get an idea. You are welcome to tell me off but I am the only guy doing stuff here ...

@fir3pho3nixx as per our code of conduct please "be careful in the words that we choose", excessive or unnecessary profanity is unwelcome and unprofessional. To be clear, the first paragraph of your issue description is what pushed me over the line to call you out on this but the constant profanity is unnecessary, I would appreciate if you could adhere to our code of conduct.

The MsBuild infrastructure needs a complete rethink(do over).

As I've mentioned several times in other issues we should ignore the existing MSBuild based build scripts and dump all that mess that hooks into the csproj project files when using the new .NET tooling as it supports multiple platforms itself.

Think it is time you guys start thinking about making me a member.

Not to sound rude but that isn't the way it works here, we have since 2003 followed the Apache Software Foundation process (Windsor started life in the Apache Avalon project). Under this process a candidate is nominated (http://www.castleproject.org/about/team/), the Project Management Committee votes, and the committer is invited. I'm not saying this process is needed anymore (the PMC would have to vote to remove it) but more than anything trust has to be built, for example I don't even know your name other than "Gav".

I personally think the flux at Microsoft has created a divergence in terms of how the MsBuild works and backwards compatibility has been forgone. This makes the previous weeks of my clean up m00t in terms of build stuff. Disappointing for me especially but I willing to take the hit. This has left me frustrated though.

I'm confused a little by your comments here, as I mentioned I had made it clear that I didn't see a future for those build scripts, most of your commits though were actually affecting the source code, the changes to those build scripts wasn't wasted, it allows us to easily see what features are left in them that are currently left to port to the new tools.

Baking binary dependencies into master has not done us any favours. NUnit being a case in point. Charlie Pool deprecated the ExpectedException attribute a while ago. Not using a package management for NUnit has hidden this breaking change. Removing this from the code was a pain in the arse but I have done it.

NuGet or no-NuGet wouldn't have made a difference here, we have just been using an old version of NUnit. Windsor committing binaries predates NuGet by many many years. I agree that we should be upgrading NUnit just as I did with the recent clean up in Castle Core.

Breaking changes around logging abstractions from Core has caused issues in getting tests to compile for Windsor. I honestly don't believe logging should be abstracted for each logging dependency. That is why you use NuGet. It should be reduced to a lambda func based subscription from a static member which calls out to something that the client code of windsor does, not Windsor or Core itself. This will make logging cloud friendly. Did you know azure application insights was a thing? Log shipping becomes weird in this space. We should stop doing that.

What breaking changes occurred with the logging abstractions in Castle Core 4.0? I don't recall we made any, we didn't note any in the release notes. This is a discussion for another issue, but again the logging integration used to be used by the many Castle projects and it predates the whole Azure platform.

The size of this PR is going to be **** ****ing huge(#215). No matter which way you cut it. I think we should just do it. I am not keen on trying to find incremental ways anymore. I am also not keen on waiting for PR's to take 2/3 days to merge. There is clearly demand for a core version of this(myself included). I will honour the WcfIntegration responses(as in #165). I cant tolerate the maintenance of dead code for #203, castleproject/Attic#2, #205. Please can we merge my PR's? I am running out of patience on this.

I'm not even sure how to respond to this, so I just won't as your aggression is really showing through. I don't and never have been paid to work on Castle, 2/3 days to merge a PR shouldn't be seen as unacceptable.

Ok @jonorossi

@fir3pho3nixx as per our code of conduct please "be careful in the words that we choose", excessive or unnecessary profanity is unwelcome and unprofessional. To be clear, the first paragraph of your issue description is what pushed me over the line to call you out on this but the constant profanity is unnecessary, I would appreciate if you could adhere to our code of conduct.

I have updated comments to remove bad words. I wont do that again. Let's remember I was trying to help. Start there and you will see the light.

Gav: The MsBuild infrastructure needs a complete rethink(do over).

Jonothan: As I've mentioned several times in other issues we should ignore the existing MSBuild based build scripts and dump all that mess that hooks into the csproj project files when using the new .NET tooling as it supports multiple platforms itself.

Where is your plan fella? You cannot expect willing contributor's to understand that. You need a plan where is it?

Gav: Think it is time you guys start thinking about making me a member.

Jonothan: Not to sound rude but that isn't the way it works here, we have since 2003 followed the Apache Software Foundation process (Windsor started life in the Apache Avalon project). Under this process a candidate is nominated (http://www.castleproject.org/about/team/), the Project Management Committee votes, and the committer is invited. I'm not saying this process is needed anymore (the PMC would have to vote to remove it) but more than anything trust has to be built, for example I don't even know your name other than "Gav".

Not to sound rude but think it is time we have a call? Seriously committee? Your project is dying. Is this how you roll in Oz? Common man! My email is listed on Github. Stop messing about. Your God complex needs to ratchet itself down a notch. You also have members willing to PAY for contributions. This was my attempt at getting admin access to your build server. Your doing my head in.

Gav: I personally think the flux at Microsoft has created a divergence in terms of how the MsBuild works and backwards compatibility has been forgone. This makes the previous weeks of my clean up m00t in terms of build stuff. Disappointing for me especially but I willing to take the hit. This has left me frustrated though.

Jonothan: I'm confused a little by your comments here, as I mentioned I had made it clear that I didn't see a future for those build scripts, most of your commits though were actually affecting the source code, the changes to those build scripts wasn't wasted, it allows us to easily see what features are left in them that are currently left to port to the new tools.

Understandable for most who speak english. Confusion for me is how we just let this go and move on to the next thing. In fact the whole community is confused. There is no migration, just let it go. There is no reference. Move on!

Gav: Baking binary dependencies into master has not done us any favours. NUnit being a case in point. Charlie Pool deprecated the ExpectedException attribute a while ago. Not using a package management for NUnit has hidden this breaking change. Removing this from the code was a pain in the arse but I have done it.

Jonothan: NuGet or no-NuGet wouldn't have made a difference here, we have just been using an old version of NUnit. Windsor committing binaries predates NuGet by many many years. I agree that we should be upgrading NUnit just as I did with the recent clean up in Castle Core.

Yes it would. Auto upgrades in your build process would have prevented you from releasing a new version. This means it would have been dealt with sooner. Common man, committing binaries is bad. Just admit it!

Gav: Breaking changes around logging abstractions from Core has caused issues in getting tests to compile for Windsor. I honestly don't believe logging should be abstracted for each logging dependency. That is why you use NuGet. It should be reduced to a lambda func based subscription from a static member which calls out to something that the client code of windsor does, not Windsor or Core itself. This will make logging cloud friendly. Did you know azure application insights was a thing? Log shipping becomes weird in this space. We should stop doing that.

Jonothan: What breaking changes occurred with the logging abstractions in Castle Core 4.0? I don't recall we made any, we didn't note any in the release notes. This is a discussion for another issue, but again the logging integration used to be used by the many Castle projects and it predates the whole Azure platform.

Whoa Nelly! Tried to see what happens when you upgrade to VS2017. I leave that one to you.

Gav: The size of this PR is going to be **** ****ing(<- sorry for this) huge(#215). No matter which way you cut it. I think we should just do it. I am not keen on trying to find incremental ways anymore. I am also not keen on waiting for PR's to take 2/3 days to merge. There is clearly demand for a core version of this(myself included). I will honour the WcfIntegration responses(as in #165). I cant tolerate the maintenance of dead code for #203, castleproject/Attic#2, #205. Please can we merge my PR's? I am running out of patience on this.

Jonothan: I'm not even sure how to respond to this, so I just won't as your aggression is really showing through. I don't and never have been paid to work on Castle, 2/3 days to merge a PR shouldn't be seen as unacceptable.

I am not being paid to work on this mate. Ask @hikalkan I never took his offer. This is pure passion fella.

@jonorossi seriously dude... grow a pair.

@fir3pho3nixx as per our code of conduct please "be careful in the words that we choose", excessive or unnecessary profanity is unwelcome and unprofessional. To be clear, the first paragraph of your issue description is what pushed me over the line to call you out on this but the constant profanity is unnecessary, I would appreciate if you could adhere to our code of conduct.

The MsBuild infrastructure needs a complete rethink(do over).

As I've mentioned several times in other issues we should ignore the existing MSBuild based build scripts and dump all that mess that hooks into the csproj project files when using the new .NET tooling as it supports multiple platforms itself.

Think it is time you guys start thinking about making me a member.

Not to sound rude but that isn't the way it works here, we have since 2003 followed the Apache Software Foundation process (Windsor started life in the Apache Avalon project). Under this process a candidate is nominated (http://www.castleproject.org/about/team/), the Project Management Committee votes, and the committer is invited. I'm not saying this process is needed anymore (the PMC would have to vote to remove it) but more than anything trust has to be built, for example I don't even know your name other than "Gav".

I personally think the flux at Microsoft has created a divergence in terms of how the MsBuild works and backwards compatibility has been forgone. This makes the previous weeks of my clean up m00t in terms of build stuff. Disappointing for me especially but I willing to take the hit. This has left me frustrated though.

I'm confused a little by your comments here, as I mentioned I had made it clear that I didn't see a future for those build scripts, most of your commits though were actually affecting the source code, the changes to those build scripts wasn't wasted, it allows us to easily see what features are left in them that are currently left to port to the new tools.

Baking binary dependencies into master has not done us any favours. NUnit being a case in point. Charlie Pool deprecated the ExpectedException attribute a while ago. Not using a package management for NUnit has hidden this breaking change. Removing this from the code was a pain in the arse but I have done it.

NuGet or no-NuGet wouldn't have made a difference here, we have just been using an old version of NUnit. Windsor committing binaries predates NuGet by many many years. I agree that we should be upgrading NUnit just as I did with the recent clean up in Castle Core.

Breaking changes around logging abstractions from Core has caused issues in getting tests to compile for Windsor. I honestly don't believe logging should be abstracted for each logging dependency. That is why you use NuGet. It should be reduced to a lambda func based subscription from a static member which calls out to something that the client code of windsor does, not Windsor or Core itself. This will make logging cloud friendly. Did you know azure application insights was a thing? Log shipping becomes weird in this space. We should stop doing that.

What breaking changes occurred with the logging abstractions in Castle Core 4.0? I don't recall we made any, we didn't note any in the release notes. This is a discussion for another issue, but again the logging integration used to be used by the many Castle projects and it predates the whole Azure platform.

The size of this PR is going to be **** ****ing huge(#215). No matter which way you cut it. I think we should just do it. I am not keen on trying to find incremental ways anymore. I am also not keen on waiting for PR's to take 2/3 days to merge. There is clearly demand for a core version of this(myself included). I will honour the WcfIntegration responses(as in #165). I cant tolerate the maintenance of dead code for #203, castleproject-deprecated/Attic#2, #205. Please can we merge my PR's? I am running out of patience on this.

I'm not even sure how to respond to this, so I just won't as your aggression is really showing through. I don't and never have been paid to work on Castle, 2/3 days to merge a PR shouldn't be seen as unacceptable.


added explanation of performance issues on osxfs from @dsheets post

Proposed changes
Added topic on "Performance issues, solutions, and roadmap".
Related issues
issue: https://github.com/docker/pinata/issues/5564
forum topic: https://forums.docker.com/t/file-access-in-mounted-volumes-extremely-slow-cpu-bound/
Please take a look
@samoht @dsheets @justincormack @thaJeztah
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

Great @dsheets , thanks.
On Tuesday, November 1, 2016, David Sheets<EMAIL_ADDRESS>wrote:

@dsheets commented on this pull request.
LGTM. I just have a few small comments. :-) Thanks!
In docker-for-mac/osxfs.md
https://github.com/docker/docker.github.io/pull/379#pullrequestreview-6601750
:

+### Performance issues, solutions, and roadmap
+
+With regard to reported performance issues (GitHub issue 77: File access in mounted
+volumes extremely slow), and a
+similar thread on Docker for Mac forums on topic: File access in mounted volumes
+extremely
+slow,
+this topic provides an explanation of the issues, what we are doing about it,
+how the community can help us, and what you can expect in the future.
+This explanation is a slightly re-worked version of an understanding
+performance
+post
+from David Sheets (@dsheets) on the Docker development
+team to the forum topic just
+mentioned. We wanted to surface it in the documentation for wider reach.
We wanted to surface it in the documentation for wider reach.
reads awkwardly but is probably fine. The text is in the present with the
reader.
In docker-for-mac/osxfs.md
https://github.com/docker/docker.github.io/pull/379#pullrequestreview-6601750
:

+so must be invalidated if OS X ever reports an event delivery failure.

+2. Running ember build in a shared file system results in ember creating many
+different temporary directories and performing lots of intermediate activity
+within them. An empty ember project is over 300MB. This usage pattern does not
+require coherence between Linux and OS X but, because we cannot distinguish this
+fact at run-time, we maintain coherence during its hundreds of thousands of file
+system accesses to manipulate temporary state. There is no "correct" solution in
+this case. Either ember needs to change, the volume mount needs to have
+coherence properties specified on it somehow, some heuristic needs to be
+introduced to detect this access pattern and compensate, or the behavior needs
+to be indicated via, e.g., extended attributes in the OS X file system.
+
+These two examples come from performance use cases contributed by users and they
+are incredibly helpful in prioritizing aspects of file system performance to
+improve. I am personally developing statistical file system trace analysis tools
s/I am personally/We are/
In docker-for-mac/osxfs.md
https://github.com/docker/docker.github.io/pull/379#pullrequestreview-6601750
:

+fact at run-time, we maintain coherence during its hundreds of thousands of file
+system accesses to manipulate temporary state. There is no "correct" solution in
+this case. Either ember needs to change, the volume mount needs to have
+coherence properties specified on it somehow, some heuristic needs to be
+introduced to detect this access pattern and compensate, or the behavior needs
+to be indicated via, e.g., extended attributes in the OS X file system.

+These two examples come from performance use cases contributed by users and they
+are incredibly helpful in prioritizing aspects of file system performance to
+improve. I am personally developing statistical file system trace analysis tools
+to characterize slow-performing workloads more easily in order to decide what to
+work on next.
+
+Under development, we have:
+
+1. A Linux kernel module to reduce data path latency by 2/7 copies and 2/5
s/kernel module/kernel patch/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker.github.io/pull/379#pullrequestreview-6601750,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALHuA3nhUAY3SK5PQlv8Ss_vaPZrgJeKks5q5y2CgaJpZM4Kj-Am
.

@dsheets @thaJeztah @MagnusS @dave-tucker @mstanleyjones @johndmulhausen Can someone give this a final review and approve my changes so I can merge? Thanks!

@dsheets :-) how about now? merge if you think it's good, thanks!


@conda/@pypi appears to remove CUDA instructions for GPU

Hello,
As the title mentions, I am trying to get a job run on AWS Batch that will run on a GPU. When I omit the @conda/@pypi decorator, I am able to see that a GPU is allocated. However, when I throw on an @conda/@pypi decorator, I am unable to get a GPU appear. Why is this? For reference, I am essentially using this Cloud Formation template.
Here is some simple code to demonstrate the issue. Again this occurs whether I use @pypi or @conda. I am using MetaFlow version 2.12.5. Note that if I omit the tensorflow library in the @conda decorator, I get a ModuleNotFoundError: No module named 'tensorflow', so the @conda/@pypi decorators seems to wipe the Tensorflow library from the compute instance.
from metaflow import FlowSpec, step, batch, conda, conda_base

@conda_base(python='3.12')
class test_gpu(FlowSpec):
    @batch(gpu=1, image="docker.io/tensorflow/tensorflow:latest-gpu", queue="job-queue-gpu-metaflow",)
    @conda(libraries={'tensorflow': '2.16.1'})
    @step
    def start(self):

        import tensorflow as tf
        print("tensorflow" + tf.__version__)

        import sys
        print("Python version")
        print(sys.version)

        print("Num GPUs Available: ", len(tf.config.list_physical_devices('GPU')))

        self.next(self.end)

    @step
    def end(self):

        print("All done. \n\n Congratulations!\n")
        return

if __name__ == '__main__':
    test_gpu()

For reference, this is the output:
2024-06-27 14:54:07.462 Creating local datastore in current directory (/Users/ed/Developer/metaflow-test-gpu/.metaflow)
2024-06-27 14:54:07.462 Bootstrapping virtual environment(s) ...
2024-06-27 15:17:46.520 Virtual environment(s) bootstrapped!
2024-06-27 15:17:47.734 Workflow starting (run-id 15):
2024-06-27 15:17:52.723 [15/start/56 (pid 5595)] Task is starting.
2024-06-27 15:17:54.545 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status SUBMITTED)...
2024-06-27 15:17:57.656 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:18:27.686 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:18:57.741 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:19:27.845 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNABLE)...
2024-06-27 15:19:28.346 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:19:58.409 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:20:28.590 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:20:58.855 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status STARTING)...
2024-06-27 15:21:27.582 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting (status RUNNING)...
2024-06-27 15:21:26.689 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Setting up task environment.
2024-06-27 15:21:34.717 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Downloading code package...
2024-06-27 15:21:35.552 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Code package downloaded.
2024-06-27 15:21:35.590 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task is starting.
2024-06-27 15:21:35.983 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Bootstrapping virtual environment...
2024-06-27 15:22:00.642 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Environment bootstrapped.
2024-06-27 15:22:02.275 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] 2024-06-27 22:22:02.275781: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
2024-06-27 15:22:02.275 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-06-27 15:22:04.153 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] tensorflow2.16.1
2024-06-27 15:22:04.154 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Python version
2024-06-27 15:22:04.154 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] 3.12.0 | packaged by conda-forge | (main, Oct  3 2023, 08:43:22) [GCC 12.3.0]
2024-06-27 15:22:04.154 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Num GPUs Available:  0
2024-06-27 15:22:31.518 [15/start/56 (pid 5595)] [226c27ff-1f24-431a-8afa-753aa1bbea82] Task finished with exit code 0.
2024-06-27 15:22:32.432 [15/start/56 (pid 5595)] Task finished successfully.
2024-06-27 15:22:33.633 [15/end/57 (pid 8378)] Task is starting.
2024-06-27 15:22:40.407 [15/end/57 (pid 8378)] All done.
2024-06-27 15:22:41.998 [15/end/57 (pid 8378)]
2024-06-27 15:22:41.998 [15/end/57 (pid 8378)] Congratulations!
2024-06-27 15:22:41.998 [15/end/57 (pid 8378)]
2024-06-27 15:22:42.793 [15/end/57 (pid 8378)] Task finished successfully.
2024-06-27 15:22:43.116 Done!

@EdIzaguirre - @conda and @pypi provide a clean virtual environment. The default tensorflow conda package is not GPU-compatible; have you tried the tensorflow-gpu package instead?

When I try using the tensorflow-gpu package instead of tensorflow in the @conda decorator, I get:
Micromamba ran into an error while setting up environment:
    command '/Users/ed/.metaflowconfig/micromamba/bin/micromamba create --yes --quiet --dry-run --no-extra-safety-checks --repodata-ttl=86400 --retry-clean-cache --prefix=/var/folders/y6/vkmmb9lj41q4_0dq4q_h0xyh0000gn/T/tmplv17ujp3/prefix --channel=conda-forge --channel=Microsoft --channel=defaults requests==>=2.21.0 boto3==>=1.14.0 tensorflow-gpu==2.6.0 rmg::glibc==2.19 python==3.12' returned error (1)
    nothing provides __glibc >=2.17 needed by tensorflow-base-2.6.0-cuda110py37hb8f09f9_2

. Notably, when I use the @pypi with the tensorflow library, I do see a GPU. However, one of my packages doesn't work with @pypi, so I would like to use the @conda decorator.

You may be able to try CONDA_OVERRIDE_GLIBC=2.17 as an env var. You can also try the bleeding edge decorators that allow you to combine conda and pypi (see here: https://docs.metaflow.org/scaling/dependencies/libraries#bleeding-edge-versions-of-the-decorators) and also handle the GLIBC notion a little bit differently. +1 to @savingoyal 's point about package name and the "clean slate". Package names usually match between pypi and conda but that is not always the case; conda still distinguishes the GPU version (it basically adds additional dependencies). Feel free to come on slack too for a more interactive conversation. There is a similar question that was asked there in the last two weeks iirc.

Hi Romain, it's Ed, the same guy from the Slack 😅. I wanted to formalize my question on the GitHub, sort of put all my comments/thoughts in one post.
I was able to get tensorflow-gpu conda library working when setting the Python version to 3.9. I still am having issues with my other library (keras-cv) but I suppose that deserves it's own post. Thanks!


ClientFactoryBeanPostProcessor implements PriorityOrdered.

#89

Pull Request Test Coverage Report for Build 339

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 72.276%

Totals

Change from base Build 336:
0.009%

Covered Lines:
2315

Relevant Lines:
3203

💛  - Coveralls


Doesn't use socket from current docker context

In Docker Desktop (for Linux), when trying to analyze local image, dive doesn't use current docker context endpoint (socket), but apparently always uses "default" endpoint (/var/run/docker.sock), which means it fails to access images built under Docker Desktop environment.
 Built an image. I'm able to analyze it:
$ dive 627547a71182
Image Source: docker://627547a71182
Fetching image... (this can take a while for large images)
Analyzing image...
Building cache...

When I start Docker Desktop (or switch docker context), this same image is still accessible by dive, even if it is not available for docker (under current context):
$ docker image inspect 627547a71182
[]
Error: No such image: 627547a71182

When listing images from current (Docker Desktop) context, listed-ones are not accessible to dive:
$ docker image ls
REPOSITORY                                                          TAG          IMAGE ID       CREATED         SIZE
something_phpfpm-pa                                                latest       36328f223adc   11 hours ago    114MB

$ dive 36328f223adc
Image Source: docker://36328f223adc
Fetching image... (this can take a while for large images)
Handler not available locally. Trying to pull '36328f223adc'...
Using default tag: latest
Error response from daemon: pull access denied for 36328f223adc, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
cannot fetch image
exit status 1

Output of docker context ls:
$ docker context ls
NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT                                    KUBERNETES ENDPOINT   ORCHESTRATOR
default             moby                Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                                              swarm
desktop-linux *     moby                                                          unix:///home/bostjan/.docker/desktop/docker.sock
ecs-prod            ecs

(asterix on desktop-linux line shows which context is current, so which will be used for all docker commands).
I tried also running dive using docker run and mounting correct endpoint (so the one from current context), but it still didn't worked...
More info on docker contexts in scope of Docker Desktop: Switch between Docker Desktop and Docker Engine

bump: please make the Docker REST API endpoint configurable on CLI, so that dive can also be directly used with other engines, such as podman that support the Docker REST API; these tend to run on their own socket API paths in order to allow side-by-side co-existance.

Hi.
I have just faced with this problem.
Use this environment variable to change default socket.
DOCKER_HOST=unix:///home/kamil/.docker/desktop/docker.sock
Of course home catalog may be different :)

On macos, if you have Advanced/User settings ("Choose how to configure the installation of Docker's CLI tools"), you'll need to do this to make local builds work:
export DOCKER_HOST=unix:///Users/yourusername/.docker/run/docker.sock

Unfortunately, setting the $DOCKER_HOST variable conflicts with docker context AFAIK.
Warning: DOCKER_HOST environment variable overrides the active context. To use a context, either set the global --context flag, or unset DOCKER_HOST environment variable.


How to set past dates as selected, when we set minimum date as current date(Date())

I kept Minimum date as current date (Say, 2019-11-21).
Now I need to set few of the dates(say, 2019-11-16, 2019-11-08, 2019-11-30) which includes past dates & future dates as selected(I mean with default blue colour background).
If it is future date it is working fine. I can able to set it as selected
Now, issue is if am trying to set past date, it is getting crash
Here is the code which I tried.
@IBOutlet weak var customCalender: FSCalendar!

//MARK: Getting date in YYYY-MM-DD format
for dateStr in selectedCustomDaysArr {
    customCalender.select(dateStr.getDateFromString(DateFormarts.yyyy_MM_dd, timeZoneId: "UTC"))
}

//MARK: Handling with Delegates
extension SelectDaysVC: FSCalendarDelegate, FSCalendarDataSource, FSCalendarDelegateAppearance{
    func minimumDate(for calendar: FSCalendar) -> Date {
        return Date()
    }
}

Minimum Date
Minimum date means the starting date of the calendar.
If in case we don't put any minimum date then the user selects all days i.e previous dates also.
If you need user not access the previous days at that time we put minimum date as a current date that means the starting date is the current day , due to that user cant access previous days.