Runner receivec SIGINT spontaniously

I'm currently running 2 runners on 2 odroid xu4 boards, version 0.0.5.
One of the runners works fine so far.
The other one, for some reason receives SIGINT from somewhere. After starting, it may pick up the job, work for couple of minutes and then gets SIGINT:
github@xu4r1:~$ github-act-runner log xu4r1
running as user 'github'
Jul 20 13:43:51 xu4r1 systemd[7135]: Started github-act-runner '/xu4r1'.
Jul 20 13:43:53 xu4r1 runner[7304]: Listening for Jobs
Jul 20 13:43:58 xu4r1 runner[7304]: Running Job 'linux - igagis/raspbian:buster'
Jul 20 13:43:58 xu4r1 runner[7304]: Failed to upload timeline with Status 404
Jul 20 13:44:16 xu4r1 systemd[7135]: Stopping github-act-runner '/xu4r1'...
Jul 20 13:44:16 xu4r1 runner[7304]: CTRL+C received, stopping accepting new jobs
Jul 20 13:44:16 xu4r1 runner[7304]: Canceled stopping
Jul 20 13:44:20 xu4r1 runner[7304]: Finished Job 'linux - igagis/raspbian:buster' with result: Canceled
Jul 20 13:44:20 xu4r1 systemd[7135]: github-act-runner.xu4r1.service: Succeeded.
Jul 20 13:44:20 xu4r1 systemd[7135]: Stopped github-act-runner '/xu4r1'.

I will do more observations.

For some reason, service is not restarted, though it has Restart=always...

This SIGINT comes from systemd:
Jul 20 13:44:16 xu4r1 systemd[7135]: Stopping github-act-runner '/xu4r1'...

It looks like the service was stopped by a script, then exited with code 0.

strange, because I did not stop it via script... I'll try to reboot the board, just in case

Maybe disable your update restarter: filesystem watching might sometimes see phantom changes.

it doesn't look like it is due to that, because it restarts the service and I tested that. In my case, the service is just stopped. I observe some strange behavior, after reboot the service is not started automatically. Maybe user systemd services are not started at boot... trying to figure out what's happening.
Also, on one board after reboot the script log command gives insufficient permissions. Restarting systemd-journald fixes that, but after reboot the error is back again. On the other board that does not happen...

Maybe user systemd services are not started at boot

It seems they are not started at boot by default, but with some changes to the script and service template it should work:
https://unix.stackexchange.com/questions/251211/why-doesnt-my-systemd-user-unit-start-at-boot
Summary:

We need default.target, the one used (WantedBy=multi-user.target) only works for systemwide start on boot.
Then we need to allow these user services to start on boot instead of waiting for the login loginctl enable-linger <username>
disable and enable the service.

My server keeps running since weeks, so I didn't observed this.

yes, I've just figured that out. Made a PR.
Though the insufficient permissions problem on one of my boards still remains... I'll investigate it further. But this issue can be closed with the PR.

@ChristopherHX
Could you make a new release, so that I could upgrade my runners?

done, will finish soon

Hm, let's wait for another N minutes :).
I think if it doesn't assign a runner in ~10 minutes it makes sense to just restart the workflow...


Is the cartridge path intended?

In the below image we see the overlay cartridge in the path after the SFRA cartridge.  Am I just getting the naming convention mixed up?  normally the intended pathing is "override cartridge:SFRA cartridge: Base cartridge".  Is this intended?

Hi @G4M3RZTWITCH ,
Yes, this is intended.
The "int_adyen_overlay" cartridge is mutual code for SFRA and SiteGenesis controllers.
That's why we have to put "int_adyen_SFRA" first and then the "int_adyen_overlay" cartridge.
Kind regards,
Bas Maassen
Adyen

👍


A few typos to fix

In the paragraph beginning "In the Semi-Annual servicing channel, feature updates are...", the word "modal" should read "model," the phrase "you choose" should read "you chose" and the phrase "it goes into" should read "it went into."

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

ID: c6957383-3bd9-eef9-6410-9c42f8a0b172
Version Independent ID: a2090374-0fd1-8d67-66de-30c4cf2835f7
Content: Overview of Windows as a service (Windows 10)
Content Source: windows/deployment/update/waas-overview.md
Product: w10
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

@officedocsbot assign @mypil

@dgcuff @illfated @tusharchandwani - From our understanding the issue has been resolved. If you feel it hasn't been resolved please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


Instead of muting can we move the dead to a different channel?

This is a good idea! Would make spectating more fun.

+1

the issue is that people will hear the sound of someone getting moved, and would know when someone dies. plus if someone has discord overlay on they will know who died.

the issue is that people will hear the sound of someone getting moved, and would know when someone dies. plus if someone has discord overlay on they will know who died.

We already have a method to stagger the dead player emojis until the discussion phase. We would wait to move players until the discussion phase

I was thinking about this today and I think a system with a channel for dead voice chat would be awesome. But that dead voice channel would miss out on any discussion from the alive players. I think an ideal setup would look like this:
Once, at the beginning of every task phase, all dead players are moved to a separate dead voice chat channel and unmuted, so they can rage/discuss with other dead people. Everyone remaining in alive voice chat is force muted.
Once, at the beginning of every discussion phase, all dead players are muted and moved back to alive voice chat. Alive players are force unmuted.
This allows dead players to hear the discussion and remain clued in to how crewmates are feeling/voting. Dead can no longer voice chat with other dead during discussion (but they can type via the ingame chat!)
This setup allows dead players to chat casually and not get bored once they complete their tasks. It would certainly be more fun to be screaming at clueless crewmates together!

Hey thanks; the latest 2.0.2 pre-release actually already has this behavior. It mutes+deafens alive players during the round (so they can't hear dead players), but the dead players can speak openly. Then at discussion, alive players are unmuted/undeafened, but dead players are muted. This should address the suggestions posted above; I don't think we'll look at moving functionality for the near future (it would blow past the Discord API rate limits even moreso than the current implementations).


Include Halo2 backend in install instructions

At the moment the docs for newcomers are misleading, if they follow the Installation page and then navigate to the Hello World page, the SNARK generation for the minimal VM fails as the Halo2 backend is not built by default in the CLI module.
I've proposed that the feature flag is enabled for the Halo2 backend in the Installation page to prevent others from having this issue.
A note could alternatively be added to the Hello World page, but I'm thinking in terms of which place will ensure people aren't going to hit snags when they first try out powdr.
The simplest solution would just be to enable the Halo2 backend by default, but no doubt you've disabled it for a reason.

Can you please rebase your branch on top of origin/main? We had a bug fix that's needed for CI.

Hi @conor10 a small correction: please rebase instead of merging our main into yours, otherwise we get this merge commit as part of the commits. Ideally there will be only one commit in this PR, the original one.


Introduce PrimeReact

Closes #21
All trees
https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector/assets/13104167/d9f5e447-df76-4710-94c0-82fc7054f523
Only Primereact Tree is enabled

Changes
The following changes have been done:
Structural

extension.ts files moved to entry-points
views renamed to plugin/peripheral
PeripheralTreeProvider extracted to own file and renamed to PeripheralTreeDataProvider
PeripheralDataTracker introduced with the goal to track/maintain the nodes instead of PeripheralTreeDataProvider directly.

Components
Reusable components were introduced:

Tooltip Component with FloatingUI as the tooltip of PrimeReact was not sufficient.
Tree Component with a common API to render Tree and TreeTable.

Unfortunately, the performance of the TreeTable is not as good as the Tree - it lags sometimes. The data comes at the same time for both Tree and TreeTable.

Based on the work of @jreineckearm
IMPORTANT
As visible on the debug console in the video, it is not possible to send edit operations. I'm not sure if that was an error on my side or already existing with the code base (I also tested it with the main branch).
All operations are called as before, but the debugger fails to write those data.
TODO

[x] Enable only one webview
[x] Fix license headers

As visible on the debug console in the video, it is not possible to send edit operations. I'm not sure if that was an error on my side or already existing with the code base (I also tested it with the main branch).

@haydar-metin , going to have a look at this. I assume this happens for any peripheral? If not, then it could be an unlucky selection of the peripheral for testing. Target accesses can for example fail if peripherals are not powered up/clocked. Will let you know after some testing.

Unfortunately, the performance of the TreeTable is not as good as the Tree - it lags sometimes

Let me check how bad it is. The treetable would be the preferred view. But if it becomes unusable we may need to work with the tree. Once we made a decision, we should turn off the other before a release.

Very nice PR as it easily allows to test all 3 solutions.

TreeTable approach seems definitely more readable and personally I prefer it. I'm worried however that it is indeed to slow. I've tested it on latest version of primereact but no changes to performance. I think that it will be okay only if a ProgressRing is added indicating that something is happening
The performance of the PrimeReact Tree solution is very good. I'm worried however that it will be less flexible with layout. It is okay if we want to have only 2 columns. It will not if we ever want to have more than that

@arekzaluski I added a progress bar and investigated the issue further. The problem stems from PrimeReact, as it doesn't support virtual scrolling for trees or tree tables. This results in an overloaded DOM, which significantly slows down the webview. The progress bar also gets stuck because the rendering process blocks the entire UI, making the application feel even more sluggish. To address this issue properly, we need virtual scrolling. Since PrimeReact doesn't support virtual scrolling for trees or tree tables, we should consider other frameworks, such as Ant Design (AntD) or anything similar. With the changes in this PR, we would only need to update the UI without any further modifications in the extension part, where the most changes were done in this PR.

I think that is is a sensible approach. PrimeReact table approach looks definitely the best visually but I agree that performance is not there.  https://ant.design/components/table looks very promising and I haven't used it before. It may be worth indeed doing a quick check how well it behaves.

@arekzaluski Thanks for the review! I disabled all the other trees and now only the Primereact Tree is visible. We should look into the other frameworks as a follow up.

@arekzaluski Thanks for the feedback and the fix for the codicons! You can see the changes in https://github.com/eclipse-cdt-cloud/vscode-peripheral-inspector/pull/24/commits/76c6967a3a5702f7e6a062033a842308ca89e66e

@planger I believe that it should be ready to be merged.


Record a number of frames then export it to a single PLY file

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Platform
PC

SDK Version
<IP_ADDRESS>

Language
C++

Segment
Robot

Issue Description
Hi,
In order to generate a complete mesh without gaps ( (because RealSense only takes the last frame to make the mesh), I was wondering if it was possible that in a first time I record let's say 5 frames containing a point cloud in a continuous way and then record the content of these five in the same PLY file? I have already tried with similar algorithms like KinFu or Open3D but without success.
I saw that it's possible to use the affine transform method to superimpose and align several point clouds, but I don't know if it is suitable for what I want to do or not?
Thank you.

Hi @Amayess  If your project is able to make use of an application outside of the RealSense SDK then you could investigate the possibility of saving 5 individual ply files in the SDK and then merging them together in the open-source RealSense-compatible C++ tool CloudCompare.  This tool is available for Windows, Linux and Mac.
CloudCompare
https://cloudcompare.org/
https://github.com/cloudcompare/cloudcompare
Cloudcompare point cloud merging
http://www.cloudcompare.org/doc/wiki/index.php?title=Merge
http://www.cloudcompare.org/forum/viewtopic.php?t=2543

Hi @MartyG-RealSense,
Thank you for your suggestion but actually I am looking for a way to do it without using an application outside of the RealSenseSDK.
I was thinking about doing a loop to generate let's say 5 frames then save them in a single PLY file using the affine transform method to superimpose each PLY.
Is this possible ?
My goal is to generate a complete mesh with no gaps.
Thank you.

I researched your request carefully but was unable to find an example of code that could perform the described method with a single camera within the RealSense SDK only.
The SDK does have an official C++ example program called rs-pointcloud-stitching for stitching pointclouds from two cameras into a single image.  This program makes use of the affine transform instruction rs2_transform_point_to_point
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/pointcloud/pointcloud-stitching

Hi @MartyG-RealSense thank you for your reactivity !
Okay understood, what about the fact generate a specfic number of frames using a loop ?
Logically, it's possible,  no ?

If you use a for int instruction then the script will be forced to loop a command for a specified number of frames before the script is permitted to move onwards past the 'for' instruction and carry out the rest of the script.  For example, a for-int loop to capture 30 frames exactly:
rs2::frameset frames;
for(int i = 0; i < 30; i++)
{
//Wait for all configured streams to produce a frame
frames = pipe.wait_for_frames();
}

In this example, the program should only be permitted to capture 30 frames before the pipe.wait_for_frames() instruction can no longer be initialized.
So conceivably you could change '30' to '5' to capture 5 frames only and place between { and } some code to generate a point cloud frame.  The instruction would loop for 5 frames before the loop ends.
You could then place pointcloud stitching code after the closing } bracket so that it only stitches the frames once 5 of them have been generated and the loop ends, permitting the script to move onwards to the next line outside of the for-int closing bracket.
However, if auto-exposure is enabled then the first several frames after the pipeline starts may be bad because auto-exposure requires time to settle down.  In the SDK's rs-save-to-disk C++ example, it deals with this by using a first for-int loop to wait for 30 frames, and then has a second for-int loop to do processing work on the 31st frame onwards now that auto-exposure has settled.
https://github.com/IntelRealSense/librealsense/blob/master/examples/save-to-disk/rs-save-to-disk.cpp#L29-L34


Tidy up some minor lints

See individual commits for better descriptions.

Does clippy warn about the match? :sweat_smile:
I prefer always matching on io::ErrorKind because it's somewhat likely we'll find out we want a special handling for some other kind. Could you drop the first commit please (or add an allow annotation to silence clippy).

Does clippy warn about the match? 😅

Only when configured to pedantic mode. So not really.

Ok, looks good then, thanks!


Error when making new CPC_v2 model

🐛 Bug
Missing Attribute "encoder" error when creating new CPC_v2 model.
Same code is shown in docs here: https://lightning-bolts.readthedocs.io/en/latest/self_supervised_models.html#research
To Reproduce
Steps to reproduce the behavior:
Run:
from pl_bolts.models.self_supervised import CPC_v2
from pl_bolts.losses.self_supervised_learning import FeatureMapContrastiveTask

amdim_task = FeatureMapContrastiveTask(comparisons='01, 11, 02', bidirectional=True)
model = CPC_v2(contrastive_task=amdim_task)

Error:
Traceback (most recent call last):
  File "/home/shatz/miniconda3/envs/fix_lightning/lib/python3.9/site-packages/pytorch_lightning/utilities/parsing.py", line 250, in __getattr__
    return self[key]
KeyError: 'encoder'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/shatz/Documents/lightning-bolts/mytest.py", line 6, in <module>
    model = CPC_v2(contrastive_task=amdim_task)
  File "/home/shatz/Documents/lightning-bolts/pl_bolts/models/self_supervised/cpc/cpc_module.py", line 72, in __init__
    c, h = self.__compute_final_nb_c(patch_size)
  File "/home/shatz/Documents/lightning-bolts/pl_bolts/models/self_supervised/cpc/cpc_module.py", line 103, in __compute_final_nb_c
    if self.hparams.encoder != 'cpc_encoder':
  File "/home/shatz/miniconda3/envs/fix_lightning/lib/python3.9/site-packages/pytorch_lightning/utilities/parsing.py", line 252, in __getattr__
    raise AttributeError(f'Missing attribute "{key}"') from exp
AttributeError: Missing attribute "encoder"

Expected behavior
No errors.
Environment

Ubuntu
Anaconda
Python version: 3.9.5
CUDA/cuDNN version: V10.1.243
GPU models and configuration: RTX2070

Additional context
The code is from the docs: https://lightning-bolts.readthedocs.io/en/latest/self_supervised_models.html#research

Fixed in Pull Request #680

Also its my first time contributing to a big project. Please let me know if I should do anything different.


metrics to monitor iNat's performance as an identification provider

We'd like to make some changes to help identifiers identify more and better, and thereby iNat a better place to get identifications and to make sure we are creating taxonomically verified data. Here are some metrics I think we should be monitoring:

time to ID: time between observation created_at and first identification created by someone other than the observer
time to community ID
number of unique identifiers
% identified

Here's some really gnarly SQL that will get at some of these:
DROP TABLE IF EXISTS identifications_for_others;
CREATE TABLE identifications_for_others AS
SELECT identifications.*
FROM identifications JOIN observations ON identifications.observation_id = observations.id
WHERE identifications.user_id != observations.user_id;

DROP TABLE IF EXISTS community_identifications;
CREATE TABLE community_identifications AS
SELECT identifications.*
FROM identifications JOIN observations ON identifications.observation_id = observations.id
WHERE
  identifications.user_id != observations.user_id AND
  identifications.taxon_id = observations.community_taxon_id;

DROP TABLE IF EXISTS obs_id_stats;
CREATE TABLE obs_id_stats AS
SELECT
  o.id,
  o.created_at,
  count(i.id) AS identifications_count,
  o.community_taxon_id,
  MIN(t.rank_level) AS community_taxon_rank_level,
  MIN(i.id) AS first_identification_id,
  (EXTRACT(EPOCH FROM MIN(i.created_at)) - EXTRACT(EPOCH FROM o.created_at)) AS ttid,
  (EXTRACT(EPOCH FROM MIN(ci.created_at)) - EXTRACT(EPOCH FROM o.created_at)) AS ttcid
FROM observations o
  LEFT OUTER JOIN identifications_for_others i ON i.observation_id = o.id
  LEFT OUTER JOIN community_identifications ci ON ci.observation_id = o.id
  LEFT OUTER JOIN taxa t ON t.id = o.community_taxon_id
WHERE
  o.observation_photos_count > 0
GROUP BY o.id;

SELECT
  round(AVG(ttid/60/60)::numeric, 2) AS avg_ttid, -- show as hours
  round(MEDIAN(ttid/60/60)::numeric, 2) AS med_ttid,
  round(MIN(ttid/60/60)::numeric, 2) AS min_ttid,
  round(MAX(ttid/60/60)::numeric, 2) AS max_ttid,
  round(AVG(ttcid/60/60)::numeric, 2) AS avg_ttcid,
  round(MEDIAN(ttcid/60/60)::numeric, 2) AS med_ttcid,
  round(MIN(ttcid/60/60)::numeric, 2) AS min_ttcid,
  round(MAX(ttcid/60/60)::numeric, 2) AS max_ttcid,
  round((count(first_identification_id) / count(*)::float * 100)::numeric, 2) AS percent_id,
  round((count(community_taxon_id) / count(*)::float * 100)::numeric, 2) AS percent_cid,
  round((count(CASE WHEN community_taxon_rank_level <= 20 THEN 1 ELSE NULL END) / count(*)::float * 100)::numeric, 2) AS percent_cid_to_genus,
  count(first_identification_id) AS total_id,
  count(community_taxon_id) AS total_cid,
  count(CASE WHEN community_taxon_rank_level <= 20 THEN 1 ELSE NULL END) AS total_cid_to_genus,
  count(*) AS total_observations
FROM obs_id_stats
WHERE
  obs_id_stats.created_at BETWEEN '2014-02-01' AND '2014-03-01'

which will yield
avg_ttid             | 407.44
med_ttid             | 2.74
min_ttid             | 0.01
max_ttid             | 10420.01
avg_ttcid            | 444.00
med_ttcid            | 2.77
min_ttcid            | 0.01
max_ttcid            | 10420.01
percent_id           | 71.91
percent_cid          | 70.68
percent_cid_to_genus | 64.66
total_id             | 18970
total_cid            | 18647
total_cid_to_genus   | 17059
total_observations   | 26381

That implementation has some caveats, mainly that the ttcid (time to community ID) is actually time until an identification added by someone else that matches the community ID, so not necessarily the time until there was enough confirmation to actually set the community ID, but maybe an ok proxy. percent_cid_to_genus is percent observationd ID'd to genus or lower.
Anyway, I propose that we add these as a new SiteStatistic type, where each day is a running average from the last 7 days like we're already recording. It will make the average TTID and percent identified look artificially low since it will miss observations that don't get ID'd for more than a week, but maybe it will still be informative.
@pleary, does this seem like a decent approach? We could also do something like store ttid and ttcid in the observations table, which might remove the need for some of these temp tables and/or sub-queries, and give us a more accurate ttcid.

Most of these have been implemented, just need to let them accumulate for a few days before they're visible at http://www.inaturalist.org/admin/stats

Right now it's admin only, would you consider letting others (or at least
curators, or at least me) see it, once it's accumulated data? Maybe that
was the plan anyway.
On Fri, Jun 26, 2015 at 6:24 PM, Ken-ichi<EMAIL_ADDRESS>wrote:

Most of these have been implemented, just need to let them accumulate for
a few days before they're visible at
http://www.inaturalist.org/admin/stats
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/612#issuecomment-115908168
.

--
Charlie Hohn
Montpelier, Vermont
coyot.es/slowwatermovement

Maybe eventually. Right now we're trying to come up with stats that are useful to us internally. Not really even sure if they're interesting yet.

Fair enough. Some would probably be interesting to me, but i am a weird
nerd :)  I'll wait and see what you all come up with.
On Fri, Jun 26, 2015 at 9:15 PM, Ken-ichi<EMAIL_ADDRESS>wrote:

Maybe eventually. Right now we're trying to come up with stats that are
useful to us internally. Not really even sure if they're interesting yet.
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/612#issuecomment-115931298
.

--
Charlie Hohn
Montpelier, Vermont
coyot.es/slowwatermovement


Add 'archived' query param to GetSpaces endpoint

Hey! In ClickUp Spaces can be archived, so I added an "archived" query param to GetSpaces endpoint.
https://clickup.com/api/clickupreference/operation/GetSpaces/

Hey, @w-haibara! Can you please merge it?

Sorry for the late reply. I'll merge it now.


Python3 and Pytorch 0.4

Do you have any plan to release code in python3 and pytorch0.4?

maybe not :) @ycxioooong
zh is lazy

Yes, of course. We will keep updating our project. Thanks for your concern!

Thank Yu Xiong again for his concern and his contribution to our work.

Python 2 is set to permanently expire in about a year. After this time it will receive no fixes or updates. It is therefore critical that the software in this repo be updated to support Python 3.


setVisibility not working

RecyclerView is empty and scrollbar still shows. I tried setVisibility(View.GONE) but does not work.

Neither setVisibility(View.GONE) nor  setVisibility(View.INVISIBLE) works on the DragScrollBar.

Unable to reproduce. Please provide some code if possible.


update: support running multiple event sources in parallel

What type of PR is this?
/kind design
/kind feature
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
See https://github.com/falcosecurity/falco/issues/2074. This is the last piece of "glue code" that uses all the preliminary work to support multiple parallel event processing loops coming from different sources.
From the UX known so far for Falco, this is a big no-op. However, this now supports loading multiple plugin with event sourcing capability and running all of them in parallel along with the traditional syscall event source. Each event source runs in its dedicated thread and does not influence the others. For example, this re-enables having both the k8s_audit and the syscall event sources on the same Falco instance.
By default, Falco enables the syscall event source and all the event sources implemented by the loaded plugin. The set of event sources enabled for event processing can be influenced with the --enable-source and --disable-source CLI options.
Which issue(s) this PR fixes:
Special notes for your reviewer:
There is a user-facing change that needed to be introduced in the stats writer (-s and --stats-interval CLI options). Considering that multiple event source can now run in parallel, the old stats formatting didn't make sense anymore. As such, the periodic sample is now partitioned by event source. Here's an example of the expected output:
{
  "sample": 71,
  "k8s_audit": {
    "cur": {
      "events": 1
    },
    "delta": {
      "events": 1
    }
  },
  "syscall": {
    "cur": {
      "drop_pct": 0,
      "drops": 0,
      "events": 9525,
      "preemptions": 0
    },
    "delta": {
      "drop_pct": 0,
      "drops": 0,
      "events": 137,
      "preemptions": 0
    }
  }
}

Does this PR introduce a user-facing change?:
update: support running multiple event sources in parallel
update(userspace/falco)!: adapt stats writer for multiple parallel event sources

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
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 [jasondellaluce]

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

/milestone 0.33.0

Local build is failing with
In file included from /home/federico/Work/falco/userspace/engine/filter_evttype_resolver.cpp:17:
/home/federico/Work/falco/userspace/engine/filter_evttype_resolver.h: In static member function ‘static void falco_event_types::check_range(uint16_t)’:
/home/federico/Work/falco/userspace/engine/filter_evttype_resolver.h:36:36: error: ‘range_error’ is not a member of ‘std’
36 |                         throw std::range_error("invalid event type");

Do i miss anything?
This is a clean build!

Local build is failing with
In file included from /home/federico/Work/falco/userspace/engine/filter_evttype_resolver.cpp:17:
/home/federico/Work/falco/userspace/engine/filter_evttype_resolver.h: In static member function ‘static void falco_event_types::check_range(uint16_t)’:
/home/federico/Work/falco/userspace/engine/filter_evttype_resolver.h:36:36: error: ‘range_error’ is not a member of ‘std’
36 |                         throw std::range_error("invalid event type");

Do i miss anything? This is a clean build!

Huh, I think this happens after rebasing on top of https://github.com/falcosecurity/falco/pull/2151. Does this happen on master too?

Does this happen on master too?

Confirm! Thanks! Weird that the issue is not spotted by the CI though.

Fixed by https://github.com/falcosecurity/falco/pull/2197

Fixed by https://github.com/falcosecurity/falco/pull/2197

Tests are back being all-green!

LGTM label has been added.  Git tree hash: 4ecde754214d0334b75968c12d0a49938fb37653

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce
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 [FedeDP,jasondellaluce]

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: FedeDP, jasondellaluce, leogr
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 [FedeDP,jasondellaluce,leogr]

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


Feature enhancement/process checklist/additional checklist

Description
New process checklist (PC)
Motivation and Context
Implement feature enhance request https://github.com/IMDA-BTG/aiverify/issues/187
Type of Change

How to Test

Install new plugins for aiverify.stock.process-checklist and aiverify.stock.reports.
Verify that the updated aiverify templates include new widgets for the new process checklist (see sample updated PDF).
Create new project and import from AI Verify Summary Report for Classification Model.
Fill in the process checklist and test arguments and generate new report.
Verify that the generated report include the new widgets (see sample updated PDF).
Repeat step 3-5 for AI Verify Summary Report for Regression Model

Checklist
Please check all the boxes that apply to this pull request using "x":

[x]  I have tested the changes locally and verified that they work as expected.
[ ]  I have added or updated the necessary documentation (README, API docs, etc.).
[ ]  I have added appropriate unit tests or functional tests for the changes made.
[ ]  I have followed the project's coding conventions and style guidelines.
[x]  I have rebased my branch onto the latest commit of the main branch.
[ ]  I have squashed or reorganized my commits into logical units.
[ ]  I have added any necessary dependencies or packages to the project's build configuration.
[ ]  I have performed a self-review of my own code.
[ ]  I have read, understood and agree to the Developer Certificate of Origin below, which this project utilises.

Screenshots (if applicable)
[If the changes involve visual modifications, include screenshots or GIFs that demonstrate the changes.]
Additional Notes
[Add any additional information or context that might be relevant to reviewers.]

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
   have the right to submit it under the open source license
   indicated in the file; or

(b) The contribution is based upon previous work that, to the best
   of my knowledge, is covered under an appropriate open source
   license and I have the right under that license to submit that
   work with modifications, whether created in whole or in part
   by me, under the same open source license (unless I am
   permitted to submit under a different license), as indicated
   in the file; or

(c) The contribution was provided directly to me by some other
   person who certified (a), (b) or (c) and I have not modified
   it.

(d) I understand and agree that this project and the contribution
   are public and that a record of the contribution (including all
   personal information I submit with it, including my sign-off) is
   maintained indefinitely and may be redistributed consistent with
   this project or the open source license(s) involved.

All 68 Unit Test Passed. Unit Test fails as Unit Test has not reached threshold level:

Pre-Merge Checks Failed Due To Vulnerability in Dependencies. @imda-peckyoke to handle vulnerability Post-Merged.

Screenshots of Changes:
Textual updates to existing process check 4.1.1:

Organisational Considerations In Report:

Version Number Update for all affected plugins:


OCM-7160 | feat: add example usage block

OCM-7160
Change type

[ ] New feature
[ ] Bug fix
[ ] Build
[ ] CI
[x] Documentation
[ ] Performance
[ ] Refactor
[ ] Style
[ ] Unit tests
[ ] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/test rosa-sts-advanced-critical-high-presubmit


Support CONNECT over HTTP/2

We could use caddy to test this, I guess.

Can we leave the proxy socket hack to http-tunnel and return the simple socket here? This package is already getting a bit large.

It might be better to just throw an exception for CONNECT requests on HTTP/2 connections for now and implement this later?

@kelunik I'm fine with throwing for now if you want to tag 4.0. Since the implementation got changed around this will have to be re-examined and I don't have the time to do that right now. We can always release a 4.1 with this supported.


MAINT: code refactoring to make it compatible with pandas 0.23.4

Added freq argument to plot.plot_cumulative_returns and plot.plot_cumulative_returns_by_quantile, which allow to avoid settings the index frequency inside perf.to_weights and perf.factor_returns (which in turn causes pandas  0.23.4 to crash, see #319 )
Also this closes #319

This also closes #319

wasn't there a commit to add newer pandas to travis?

wasn't there a commit to add newer pandas to travis?

Yes, but I removed it because there are changes in pandas 0.23.4 that conflict with pandas 0.18.1 and some tests fail. Those tests are not that meaningful, e.g. some nans are returned as 0s in new pandas and some indices need to be Categorical. Anyway I didn't want to chase what changed internally in pandas, so when we get rid of pandas 0.18.1 we can update the tests for new pandas versions.

Thanks @luca-s!


'null' tags returned for correctly tagged file... ?

Hi,
I'm trying to create a small app, using webpack, with an audio file located in my project folder. Here is my code:
import fs from 'fs'
import id3 from 'id3js'

tagReader: () => {
  id3('./../data/test.ogg', function(err, tags) {
    console.log('tags: ', tags)
  })
}

I checked the file which is correctly tagged (it is an .ogg), but for some reason I can't understand, all properties remains 'null'... Someone having the same issue, and/or able to give me some help? Thnak you in advance!

@soykje Does this work properly for MP3 Files or is this problem only occuring OGG Files?

Hi,
Thx for your answer. Yes it occurs only with ogg, not with mp3 files. Is this a know limitation, or is there any way to fix that?

@soykje Weird! However, I am going to fork it, and create an updated ID3 Metadata Parser for JavaScript within a few days. Most of the solutions on the web are totally outdated and don't use many of the today's best web practices. I was even unable to use this on Web now, also this and others have their fair share of bloatware, which hurts browsers a lot.

Ooow great, I'll be watching for it then!


fresh clone, gulp build serve error

I just cloned and ran npm install, then tried to gulp build serve and got this:
/Users/nathanbackup/.node/lib/node_modules/gulp/bin/gulp.js:129
    gulpInst.start.apply(gulpInst, toRun);
                  ^

TypeError: Cannot read property 'apply' of undefined
    at /Users/nathanbackup/.node/lib/node_modules/gulp/bin/gulp.js:129:19
    at doNTCallback0 (node.js:419:9)
    at process._tickCallback (node.js:348:13)
    at Function.Module.runMain (module.js:469:11)
    at startup (node.js:136:18)
    at node.js:963:3

NRWMacBook:angular2-seed-1 nathanbackup$ node --version
v4.2.2
NRWMacBook:angular2-seed-1 nathanbackup$ npm --version
2.14.7
NRWMacBook:angular2-seed-1 nathanbackup$ gulp --version
[16:32:49] CLI version 3.9.0
[16:32:49] Local version 4.0.0-alpha.2

Using the locally installed version explicitly worked, nvm:
./node_modules/gulp/bin/gulp.js build serve

I'm glad you managed to find the answer. This project requires Gulp 4 to be installed globally (or you can run the local version as you did).
I'll add it to README.md under Requirements.


eos_designs support for non-tenant networks

Issue Type

[X] Template enhancement
[ ] Role enhancement
[ ] Documentation enhancement (avd.sh)

Is your feature request related to a problem? Please describe.
Not always will users of EVPN employ it for its tenancy/vrf functionality but instead for the desire to manage flood lists dynamically using the EVPN control plane.  In the current Network Services model, network services can only be defined in the realm of tenants.  We should be able to leverage all the same templates for tenants.  Right now, that is not possible.
Describe the solution you'd like
Adjust tenant templates to allow for networks to be defined outside of the tenancy model.
Describe alternatives you've considered
Set no tenant networks with the current model and develop an abstraction of my own by using custom
Additional context
VXLAN: Updating the model to allow for these templates to be used either for tenancy or not would not break the current model.  To be clear VNIs and everything VXLAN should still be definable in this non-tenancy model.
Non VXLAN: Furthermore, there is no way to define non-vxlan networks across various leaf groups.  This function is a nice to have and can be address by doing something like https://gitlab.com/ryanmerolle/avd-demo/-/blob/ryan-v2/group_vars/CAMPUS_LEAFS.yml and https://gitlab.com/ryanmerolle/avd-demo/-/blob/ryan-v2/group_vars/CAMPUS_L3LEAFS.yml

For Non VXLAN we will implement this with a knob per svi/l2vlan. Also requested in #1022.
For using the default VRF for network services, I think we should still use EVPN control-plane for advertising L3 information. We will have to detect the vrf name and ensure a route-map is associated to the vrf. This is required in EOS to advertise subnets via EVPN in default VRF. This will be a great addition, and we can use it in other use cases as well.
Alternatively we could append the services to the redistribute connected route-map.
For both cases we could also optionally inject host-routes (attached-hosts).


Is WinAPPDriver dead or still maintained? Any Chance to use it with .NET 8 instead of .NET 5 (EoL)

The latest provided release from 2021 still works, but only if .NET 5 is installed.
But .NET 5 is is "End of Support" since May 2022.
Is there sourcecode available anywhere, to compile the WinAppDriver with .NET 8?
Seems this Repo https://github.com/microsoft/WinAppDriver only hosts the releases and some tools but not the WinAppDriver itself.

When you observe this comment being deleted by Microsoft you have your answer
DEAD


Make set & get types use generic state

Hopefully this fixes #32 and still allows type inference in JS files.
@jfbrazeau @drcmda  @Magellol @dm385

I'm not knowledgable about TS to review this, you're the pro 🙂 but if it solves the issue, let's merge.


open chrome-devtools:// url results in blank page

open("chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=<IP_ADDRESS>:9229/7ba02a53-c8ec-4b45-9096-d1c7dc55f7ba", "chrome")

+1 same issue

Finally I use https://chrome.google.com/webstore/detail/nim-node-inspector-manage/gnhhdgbaldcilmgcpfddgdbkhjohddkj?hl=en to trigger node inspector automatically

Not sure if it's the same issue.  Ubuntu 16.04 thunderbird can open URLs with firefox as default just fine.  When I try to make google chrome my default browser it breaks.  When I click on a URL with thunderbird I get a new blank tab in google chrome.


Spelling correction

current version (wrong ): /usr/share/java/jna-platrom-3.2.7.jar
correct version: /usr/share/java/jna-platform-3.2.7.jar

Hi @lukasreichart, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

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

TTYL, AZPRBOT;


Add API for list of callers and called functions

Need to add APIs to the function object to get the list of callers, and the list of functions called. This would assist in the construction of a function dependency graph. Also, it will allow us to automatically queue analysis in the priority queue for all functions that the function being viewed calls, which will significantly improve looking through a binary while it is still being analyzed (as calls to imports will be immediately resolved and displayed using the correct name).

This is implemented as .callees and .callers on functions in the Python API and has core APIs on the BinaryView.


fix: Update tooltip position and rotation in Discussion Notes panel

Proposed Changes

Fixes #8937
Corrected the conditional class name for tooltip rotation.
Ensured consistent tooltip positioning based on the show state.

@ohcnetwork/care-fe-code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[ ] Ensure that UI text is kept in I18n files.
[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.
[ ] Request for Peer Reviews
[ ] Completion of QA

LGTM

@coderabbitai full review

@khavinshankar your review required


[Fix bug 1227479] Hide multiple curators profile details

@akatsoulas r?

On 320x480 and 360x640 mobile views email is not rendered correctly when we have less than 3 curators.

@johngian PR updated

@johngian Thanks for the tip. PR updated.

PR updated. I tested it locally and it works as expected.

PR updated. I amended the commit to add @akatsoulas nice idea for adding a tooltip when we don't show curator's details.

@comzeradd I can't see the tooltip locally. Is the PR up-to-date?

@johngian for consistency I enabled jquery-ui tooltip site-wide. Keep in mind that the tooltip is displayed only when curator details are omitted.

I did a cross-check across the site and some tooltips show redundant information and don't look really good. eg.

In group list
Each group tab shows the name and hover a similar UI element shows the name once again
In base
Sign in button has a sign-in text and on hover it show "sign-in" once again

I don't think that it looks good. Let's restrict this only when we need it. For now this is only group curators in group view page and only if there are no curator details.

I did a cross-check across the site and I don't really like the way some tooltips get rendered. Eg.

In group list
Each group tab shows the name and hover a similar UI element shows the name once again
In base
Sign in button has a sign-in text and on hover it show "sign-in" once again

I know that the same think happens with the default title on hover but jquery-ui tooltip seems a bit too much for some cases.
I don't have any strong feelings on that. @akatsoulas @nikos any ideas on what is better?

The point of a tooltip it to provide additional information. So I would suggest we remove the title element from these two cases you mention. It doesn't offer anything.
Long term, we could also use boostrap's tooltip, since we already use bootstrap, and completely remove jquery-ui if it's not used anywhere else.

OK, for me our aim should be to not degrade the current UI just for a minor change. If we want to keep this tooltip please review the rest of the occurrences and omit the title. Else let's restrict to the scope of the current PR and open a bug to tackle the rest of the tooltips in the future.

I believe that we should aim for code maintainability, thus I am in favor of just adding the tooltip exactly and only where we need it. Removing just the title in a couple of cases is not a good idea in the long run. By revisiting this in a few months, nobody is going to remember why this was done in the first place. Moreover, it's not helpful either for contributors or anybody else that is working/going to work on the code-base.

I amended the commit to use the tooltip just for the multiple curators fix for the moment. I'll open a bug to review tooltips and jquery-ui in general for the whole website.

@comzeradd
Tested locally and it works fine. Also code looks OK.
Please rename groups.js to group_view.js following our current static file paradigm. Let's make sure that all references are also updated.
r+wc


Updated requirements.txt and README.md

Description
This pull request updates the requirements.txt and README.md files to the latest versions of the Python packages.
Changes

Updated the requirements.txt file to the latest versions of the Python packages.
Updated the README.md file to reflect the changes to the requirements.txt file.

Review
Please review the changes and let me know if you have any questions.

Since MetaGPT has adopted a new installation method, this PR will be temporarily closed. It can be reopened at any time if there are updates in the future.


Added "Edit this page" link to docs

With this PR readers can suggest changes to the docs with an easy to use WYSIWYG markdown editor.
This is how the editor looks like for this repo.
https://github.com/remorses/docusaurus-example/assets/31321188/43c8bc68-3668-4a25-bf1c-a70eceab7bcb

This is really cool! Would we need to add any applications to the repository with permissions of some sort?

I love it, but it seems to be taking a looong time to load for me.

Does it take a long time after clicking the "open pr" button? or just loading the website?

I got it to load after a refresh.
This is a really cool feature, and I appreciate you PR'ing this into the library. However, I don't want to add this feature yet. We will likely give the docs a makeover and we don't want to confuse contributors with the multiple auth steps and routing to a web editor.
I'll be sure to surface this PR whenever we revisit the docs stuff!

Ok, thank your for giving me some feedback!


Can anyone help with the events not firing when using this plugin with appgyver?

So far, I've been using bflood's way of adding the plugin to my appgyver project however I've been stuck for weeks on trying to get events to fire. MAP_READY does not work. Neither do any of the other events.
This is code I'm using:
document.addEventListener("deviceready", function() {
// Define a div tag with id="map_canvas"
var mapDiv = document.getElementById("map_canvas");
// Initialize the map plugin
var map = plugin.google.maps.Map.getMap(mapDiv);
// You have to wait the MAP_READY event.
map.addEventListener(plugin.google.maps.event.MAP_READY, onMapReady);
}, false);
function onMapReady () {
alert("yay I finally work");
}
});
This is the way I get the plugin to work. The map loads but no events get fired.
[
{"source":"https://github.com/wf9a5m75/googlemaps-ios-sdk-for-phonegap"},
{"source":"https://github.com/bFlood/phonegap-googlemaps-plugin#appgyver_bf","variables":{"API_KEY_FOR_IOS":"..."}},
{"source":"https://github.com/wf9a5m75/phonegap-http-request#app_gyver"}
]

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/24662326-can-anyone-help-with-the-events-not-firing-when-using-this-plugin-with-appgyver?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github).

Please have a look here:
https://github.com/wf9a5m75/phonegap-googlemaps-plugin/issues/443
and maybe you could ask for help @bFlood
He's the only one with appgyver knowledge


Update astropy-helpers to v1.3

This is an automated update of the astropy-helpers submodule to v1.3. This includes both the update of the astropy-helpers sub-module, and the ah_bootstrap.py file, if needed.
This is intended to be helpful, but if you would prefer to manage these updates yourself, or if you notice any issues with this automated update, please let @astrofrog know!

Coverage remained the same at 73.182% when pulling 6da9bbf7406fd73412e3070f5845ab39649c2433 on bsipocz:update-helpers-v1.3 into fed05775d77645e672ca32a11866b733be5e4ed0 on radio-astro-tools:master.


Proposal: Design for a more secure interaction

Right now the dependancies is on pod name to validate pod. Pods can mistakenly or maliciously use wrong names, more over people will use partially trusted code (i.e. layers of containers images, libraries and so forth). These things may load wrong names.
Proposal:

Use ambassador pattern, each pod contributing to this needs to run a simple container that talks to the vault on behalf of the pod.
The ambassador communicates with vault using client cert.
The ambassador is the one that looks up pod name.
The ambassador exposes a simple rest api locally to the pod. this is a proxy api to the actual vault.

Additional future features can be added to the ambassador, offloading common functions such as token validation, token renewal etc.

@khenidak Even if the pod uses the wrong, we still look up the pod in the API from a intermediate controller (vault-controller) running in the cluster, which looks up the Pod info from the Kubernetes API server, and only issues a one time use token to the Pod based on the annotations defined by the administrator. The Pod can only ask for this process to take place. We then call the Pod based on the Pod IP address return by Kubernetes. This is written up in the how this works section.
So the vault-controller seems to play the ambassador here. The Pod uses an init-container to kick the ambassador, which does steps 2- 3, and calls the init container back on an API using the IP address obtained from Kubernetes, not the Pod.
The

Also loading the wrong name would cause the vault-controller to look up either a Pod that does not actually exist, which means no  token will be generated, and if the Pod does exist it will validate the annotations of the Pod as returned by Kubernetes, and does not trust the Pod that initiated the original request. We are trusting the Kubernetes API and the administrators desired state. The token is then send to the IP address based on the information in the Kubernetes API, not the info submitted by the Pod. If this is a different Pod than the calling Pod, the original Pod still does not get a token.

@khenidak Did you see what we are actually doing here? We are using an "helper" container called vault-init that pulls the Pod name from the Kubernetes downward API, and initiates the flow outlined above and in the How it works doc.

Hi.
I can see more security flaw in the interaction model:
Vault policy name is specified client side. So user that creates pod can specify another policy and get secrets that are probably allowed only to other pods, which the user originally does not have access. This includes policy of the vault-contoller itself.
Proposal: remove policy annotation and generate policy name based on only data known to kubernetes.
Third-party resources come in mind as a solution, because their usage can be easily limited by user-based policies. Partcular users can be prohibited to use TPR, while limiting annotations is harder.


[AST] Special handling for existentials with superclass and marker pr…

…otocols
Even if protocol is not self-conforming it should be okay to produce a conformance based on superclass
if protocol bounds of the existential are all marker protocols.
Superclass concrete conformance is wrapped into an inherited conformance in such cases to
reference the existential.

@swift-ci please test

@swift-ci please test macOS platform

@swift-ci please test

@swift-ci please test


ityfuzzup fails if ~/.ityfuzz/bin folder doesn't exist

ityfuzzup fails if ~/.ityfuzz/bin folder doesn't exist in Mac OS,
curl -L https://raw.githubusercontent.com/fuzzland/ityfuzz/master/ityfuzzup/ityfuzzup | bash

gives this error:
could not chdir to '/Users/xxxx/.ityfuzz/bin'

I created the folder manually then it worked.

Fixed doc.
Use
curl -L https://raw.githubusercontent.com/fuzzland/ityfuzz/master/ityfuzzup/install | bash

instead


Monkeypatch ternServer.normalizeFilename so it doesn't break Mac/Linu…

…x absolute paths
Fixes two issues:

All Extensions/JavaScript Code Hinting tests fail on Linux/Mac (reported by @ficristo in https://github.com/adobe/brackets/pull/11569#issuecomment-242835715)
On Linux (probably also Mac), Code Hints are not shown immediately, but only after invoking them using Ctrl+Space (reported by @zaggino on Slack)

I could only test this on Linux.
The corresponding Tern "culprit" commit is ternjs/tern@24044a4781089b399f9bd4b98679c209ae8d86d0

On OSX Extensions \ Javascript Code Hints - JSQuickEdit now pass 🎆
Thank you @MarcelGerber
Do you think we should file an issue upstream?

By the way, how do you discovered this?
And should we replace ecma5 in ecmascript in HintUtils.js?

ping @marijnh any advice on this?

Diabling normalizing of filenames will definitely break several aspects of Tern. I couldn't find out, from this issue, why you'd want to do that.

git bisect is my friend. I used my original branch (which contains several Tern updates) to bisect there, then after I found the culprit there, I bisected Tern itself.
Yes, I think we should change the two leftover ecma5 references to ecmascript, so these literals and keywords are considered builtin (and as such, not as highly ranked). Could you raise a PR for that?
I'll file an issue over at Tern, even though I'm not sure this is an issue that many face. I also have a simple fix in mind.

Oh, didn't think you, @marijnh, would actually look at this issue, heh.
So let me explain a bit (I have to admit though that I don't know too much about Tern and how Brackets interacts with it):
We don't specify a projectDir, so Tern assumes /, which also cannot be changed to "" as this will be reverted in Tern.
As such, the paths Tern requests are at least to some extent absolute paths like /home/project/file1.js. Our file system layer resolves this just fine and delivers the file contents to Tern, which also has no problems handling it. But with normalizeFilename applied to the path, our file system layer is handed a path like home/project/file1.js (without the leading slash), which cannot be resolved (it's considered a relative path).
Notice also that everything worked fine until ternjs/tern@24044a4, which was part of our recent Tern (and Acorn) update.
What issues can such a change cause? I could think of requesting the same file two times (once with the absolute and once with the relative path), but that shouldn't cause too much trouble.
The fix I would suggest on your side is that projectDir: "" should be allowed, but let's see what you have to say.

@MarcelGerber just a quick look, isn't it possible to fix function getFile(name, next) { method instead of normalizeFilename ?

Well, the thing is, the leading slash is an indicator whether the path is absolute or relative, so we cannot decide that with the slash removed.

I think Tern will only pass normalized file names to getFile, so if you get a relative one, you should be able to assume that it's relative to your project dir, not the cwd.

Yes, but the issue is that when an absolute path is normalized, the trailing slash is stripped so it looks like a relative one.

I understand, but I think you can make your getFile interpretation handle that (as @zaggino also suggested)

@zaggino Could you try adapting the handleTernGetFile method? I wouldn't know how we can differentiate these two types of paths.

Ok, I'm gonna look at this tomorrow and report back.

I wouldn't know how we can differentiate these two types of paths.

(That's what I was talking about here )

@MarcelGerber I though about something like this https://github.com/adobe/brackets/compare/zaggino/tern
@marijnh I'd be useful if getFile method could receive also the parent information which is the file from which the name is referenced (like here: https://github.com/ternjs/tern/blob/master/lib/tern.js#L308-L315). srv.options.getFile(name, parent, function(err, text) { would be enough although it'd break the api in the current version. If I had the parent info, it would be easier to pinpoint which file is tern actually requesting.

Just noticed my branch made 1 test failing on windows and it worked for like only half of the linux tests. This normalizeFilename feature is quite a pain indeed.

It's configured as no-op here: https://github.com/ternjs/tern/blob/459b6705bada72027fbb922f4097b4dcf0ab305d/lib/tern.js#L24
Why our
ternServer.normalizeFilename = function (name) { return name; };

makes any difference?

https://github.com/ternjs/tern/blob/0bf87473bc8c21f8d37e2ff6157edf9df8bde521/lib/tern.js#L222-L226 is the one we care about. The one you found is only the one that feeds this one :)
Sadly, we cannot really do much with options.normalizeFilename, except for maybe a hack like prepending bracketsHack to every path and then dropping it later on, which is not much better than what we have now.
@zaggino Your solution probably fails in cases like /home/project/home/project/file1.js, where the project dir is /home/project. This is one edge case we definitely have to think about.
In this case, if we would get a request for home/project/file1.js (as I said above, we get both absolute and relative requests), we cannot tell which one it is.

Ok, understood, your solution has my LGTM then. :+1:

Would love to hear from @ficristo and @marijnh, too.
Now that @zaggino has apparently faced similar problems to those I described before, I feel confident that this is an issue that cannot be solved "nicely", at least on our side. Maybe now there's a possibility for a Tern fix?

If @marijnh could provide an API for us to use would be great.
But I don't have any opinions on the issue itself.

I stated before that normalization is necessary for Tern to function reliably. If you break it like this, you'll get situations where the same file is referred to by different names (for example when found through a relative import), and the module system will get confused.
I recommended to handle this in getFile, and explained that you don't need additional info, since you know that you get a normalized filename, and that this is relative to the project root.

I'm afraid that for tern resolving to work properly as intended, we'd have to not use file system root as tern server root but actual require root (not project root, explanation follows).
That brings us to a problem where project root might not be an actual requirejs root (if I open a subdirectory of a project). I can even have multiple requirejs roots in my opened folder structure (every default extension has its own require root https://github.com/adobe/brackets/blob/master/src/utils/ExtensionLoader.js#L172-L173 but usually you open just the brackets project). The only way I would know how to solve this problem is if in the getFile method I'd know, which file is the parent. Then I would be able to traverse the file tree to locate the nearest requirejs root and server file relative from there.

...continuing my previous babble ...I don't think this is easily solvable (resolving requirejs stuff). If you have a file with a non-relative imports like require('xxx') you will never know 100% from where you should load it. It depends on many things like which html page loaded the file, how the requirejs was configured with basepath, how are the paths set up, etc. So I believe we should do what we do now and that's to disable the file normalization like Marcel did in the PR.

Going for it now. Hope that's ok, but it seems to be fine with @zaggino and @ficristo

:+1:

Yeah, for now I trust our test suite.
Maybe open a new issue to investigate if we can "re-enable" the normalize function?


Refactor project to serverless AWS project

Currently all the code is written in GO and is meant to be hosted online (via docker containers/in AWS somehow).
I've had a change of mind and want this all to be in AWS. Initially I thought I would keep it mostly how it is and refactor to use DynamoDB but I'd rather a full refactor to also include serverless lambda functions.
While AWS does support go lambda functions, the AWS JS sdk is more widely used and has better community support.
The new architecture will be similar to the following:

GitHub repo: https://github.com/aws-samples/lambda-refarch-webapp
The frontend portion (which hasn't even been started) will largely remain the same but use  Amazon Cognito for auth. Here's an okta example of something similiar: https://developer.okta.com/blog/2020/04/22/build-secure-aws-lambda-nodejs-react
My intention is to use terraform to create/deploy all resources. Here's a good example of a very similar app: https://learn.hashicorp.com/tutorials/terraform/lambda-api-gateway?in=terraform/aws

This also seems like a good resource: https://aws.amazon.com/getting-started/hands-on/build-serverless-web-app-lambda-apigateway-s3-dynamodb-cognito/

Right now, I'm leaning on not using Amazon Cognito directly and instead I plan on using AWS Amplfy auth (https://aws.amazon.com/amplify/authentication/) which will provide us with the ability to login users without having to leave the website.


Adds async option for find method - #19

I've just implemented the proposal of @basco-johnkevin because I have the same need :)
Please let me know if it's fine for you.

Ok I fixed this option if not specified from the schema.
I wonder if it would be better to also add the id of a doc as a parameter from the options in order to do :
db.find('authors', {id: 1, async:true}) and not db.find('authors', {startkey:1, endkey:1, async:true})
thoughts ?

I don't think the does sideload if async option is force to false test is quite right. It seems to rely on the async === undefined checked described above, but the reason that res.books is undefined is not that docIds was unspecified – rather it's because the relationship was defined to be async in the schema. So the test would fail if you passed in e.g. 19 as the id, even though it should return the same result.
I think this PR needs a bit of work to ensure that the correct behavior occurs for the four possible cases (async true/false for schema/query), but it's going in the right direction. Thanks!

Hmmm not sure if I understand well your last comment ... I tried to modify the does sideload if async option is force to false test with  return db.rel.find('author', {startkey:19, async: false}); and it seems to work well, is that what you mean ?
By default async equals false so indeed I defined it to true in the schema. Then if I don't find with the forced async option to false, I get res.books undefined as expected.
I updated the check with typeof.

Sorry, what I meant to say is that I was unsure we had enough tests, and that I didn't really understand what the if (relationOptions && relationOptions.async && typeof idOrIds === 'undefined') line was doing exactly. (TBH I haven't looked at this code in a long time and I didn't write the async stuff.)
It kinda looks like the if condition is just checking for exactly the condition in the test and doesn't have anything to do with async vs non-async but I admit I should probably spend more time actually trying to understand this code.

The !idOrIds test is also not quite right because it will fail if the id is 0 no?

I'm starting to understand the general idea behind the code, but I think if we had a bit more tests for all edge cases (default is true/false, override is true/false, override is not specified, idOrIds is specified or not, idOrIds is 0) then probably it would be clearer why I think the if checks are not quite right here. Let me know if you think I'm being off-base, but I'm just trying to make sure I give this PR a good thorough review. :)

Ok ! I'll back on this next week, sorry I had some stuffs to finish before ;)

Just bumped into this problem, which slows things down quite significantly in some queries where you don't need all that data to be pulled in (easy to bypass by going back down to allDocs, but not very pretty). Has there been any progress on this? Happy to help move it forward if this PR is stalled and a contributor is needed!


feat(job): complete the job arguments per the new spec.

added workers config
added default image
added ttl_seconds_after_finished

closes https://github.com/leptonai/lepton/issues/6047
closes https://github.com/leptonai/lepton/issues/6048
Related to (but not closing) https://github.com/leptonai/lepton/issues/6001

done - ptal


Feature/update next event

@athackst this is so cool!!! Am I OK to pull a few of your changes into this repo? It looks like you've improved it a bunch :D

Thanks!
I was going to open an issue to see if you all would want a PR.  I forgot that PRs default to base repos and accidentally opened this before I was ready (whoops!) :facepalm:
My group also makes use of Meetingplace, so I used your excellent start to generalize it enough for our needs.
In particular:

I added a group info task that returns the description of the Meetingplace group.  I mostly did this just to be able to test that I'd integrated with Slack right without having to have an event within a certain time frame.
I added the ability to define channel and group with each task so that I could hook different channels up to different groups.  We're a collection of chapters and each chapter has its own Meetingplace group.  This is optional and otherwise uses the environment configuration for a single group->channel combo if not set.
I added deploy to Heroku button so other groups could spin up their own dynos.
I added some developer things -- dev container for VSCode, tasks, workflow to CD to Heroku, Dependabot

I wasn't sure what kind of changes you'd be interested in consuming

Do you want to completely subsume this and have this repo be a general Meetingplace bot?
Do you want to reference my general fork as a gem you can build custom virtual-coffee needs against?  I could either publish this as a gem or you could install from the git repo
Do you want to just merge what I have now and split it off from there?
Do you want just a subset of my changes?

Then I can open the relevant PR :smile:

Do you want just a subset of my changes?

I think for now I'd just like the changes you made to the .github files :) I'll cherry pick your commits into a new PR if you'd like? :)
My current plans for this repo is to keep the virtual coffee bot kind of specific to virtual coffee (I'm planning to make it do a bit more then meetingplace). Though I totally support what you're doing & I'm happy to help out if you'd like :)

Sure! SGTM
Feel free to take whatever you find useful. Let me know if you have any questions. 😄


Manage Apalache server

To provide a user-friendly API, we would like to have a way for quint to manage the apalache server so users don't have to think about this.
For the immediate term, we can just inform CLI users about how to run the server when a connection cannot be made. But as soon as we expose model checking functionality via the VSCode plugin, we should give the LSP server a way to start and spot the Apalache server.
For the future, perhaps we'll want some sort of interactive console similar to sbt, which can be used to manage various parts of the specification lifecycle.

Inspiration to gather options:

bazel runs a long-lived server process, with an idle timeout
bloop+metals
jupyter notebooks
proof assistants


add web annotation JSON-LD validation

JSON schema for JSON-LD web annotations validations should be carried out to a) validate the hypermerge storage (?) and b) for all REST endpoints.

ajv: https://github.com/epoberezkin/ajv

this grows or falls with schema enforcement methods of hypermerge/automerge; if any client can add any data with all other hypercore/hypermerge peers accepting the data, the data model can be compromised easily. however, this is even more related to consensus principles among peers of the swarm than to JSON validation.
nevertheless, the server should validate PUT/POST bodies before appending them to the annotation log.

in a recent discussion, @pvh addressed the issue of validation, local-first (ownership), and consensus. in a local-first system, proper ownership goes before consensus; inspired by physical ownership, as i understood it, a replica of a hypermerge document is first and foremost a copy and the subsequent collaboration/replication/merging is just a feature.
this should support the above concept of treating annotation collections more defensively and not opting for some sort of consensus on a notebook data structure. the gateway server, however, takes an important role when connecting notebooks to thin clients on the web:

it can guarantee that incoming data from web clients (create/update) is compliant with the WADM (JSON schema validation) and reject any invalid data.
it can validate entire notebooks and ensure WADM compliance to web clients. for example, the WAP endpoints would return just valid annotations (if there are any) and inform web clients about invalid data via extra HTTP headers such as x-invalid-entries: abc123,def456. fragmenting representations of data is not necessarily a good approach, but web clients would need to filter invalid annotations either way.
it even could offer straightforward repair mechanisms ("remove all invalid annotations"), but maybe that should be handled by actual local-first apps instead of thin clients on the web for the sake of security/privacy.

Thanks so much for listening to me natter on about this stuff, @falafeljan, so forgive me for clarifying my thoughts.
My view is that local-first software should, as much as possible, not be degraded by the loss of non-local infrastructure. That means embracing the cloud for responsibilities where it is required but avoiding it otherwise.
In this case, in my view, the decision of how to decode confusing or malformed data is something a client can make independently. If I want to collaborate with another client running a new or forked version of the code, why should a server interpose itself into that relationship? A client might choose to be more or less restrictive in what it accepts from a peer, just as it determines what to write.


A python script that scraps the home page of BBC and outputs the headlines as a result.

Description
A python script that scraps the home page of BBC and outputs the headlines as a result.
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

Category:

[x] Scrappers
[x] Fun
[ ]News

Contributor:  shubhexists
Description:  A python script that scraps the home page of BBC and outputs the headlines as a result.

PLease Mention the Issue No, If not create an Issue


Add, please, start drawing event.

Hello! @rsimon, add, please a way to listen start drawing event for all drawing tools. Thank you!

It's a good idea (and probably not a lot of work). I added it to the list of upcoming additions.

The event is called startSelection and will be part of the next release (v2.4.1).


[Feature Proposal] Given a Raw Search Query, Relevance Engineers/Business Owners Can Compare Two Search Configurations

Summary
Choosing different ranking algorithms can have drastically different effects on the users' search experience. Additionally, any operations on the query after the user submits and before results retrieval or after results are retrieved and before they are displayed can impact the user. This proposal is to build a simple UI in OpenSearch Dashboards to allow a user to visually and manually compare results of two different ranking algorithms for a given search query.

@macohen thanks for opening up the issue. Could you share more details on the proposal and how it would benefit the community?

Also is this something you are willing to take up and work on it?

@macohen thanks for opening up the issue. Could you share more details on the proposal and how it would benefit the community?
Yes. I could have left this in draft a little longer, but will add the detail. The idea overall is to build more into the distribution for measuring relevance ranking in search applications so search application owners can more easily understand how different search configurations produce different results and choose one that works well for their use case. More to come and thanks for the comment, @saratvemulapalli

Also is this something you are willing to take up and work on it?

Absolutely!

Assigned it to you.

Closing this as https://github.com/opensearch-project/dashboards-search-relevance/issues/2 supersedes it.


Add "MULTI_IP_SUBNET" guestOsFeatures option.

"MULTI_IP_SUBNET" is a valid guestOsFeatures option in the Compute Alpha API.
Description
Adding a new option to a list of values accepted by the API.
Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[ ] Documentation
[x] Tests
[ ] ICLA (required for bigger changes)

Thanks @illfelder!  LGTM.  @erjohnso OK to merge.


UUID links not rendering correctly in item descriptions

In GitLab by @Asacolips on Oct 4, 2022, 17:21
Summary
UUID links (such as those created by dragging and dropping documents) in item description fields are rendering as plain text.
Steps to Reproduce

Create an item
Create a second item
Edit the description of the second item
Drop the first item into the description

Screenshots

Labels (do-not-change)
/cc @Asacolips

In GitLab by @Asacolips on Oct 9, 2022, 19:22
Resolved in 4604c6f and will be included in release 0.6.1


Caching of images with pre-signed URL's

We use AWS for storing images and other assets. All our resource URL's are always signed and they look something like this:
https://our-aws-api.com/1e694fa00dac5bae71fe865f25117756a915118f.jpg?AWSAccessKeyId=MHSUQFKDUWROKGJSUI&Expires=1463062749&Signature=h2asdrt%2KDJSIAMtIasdzH6KgJDKSjw%3D

This does not work well with the caching mechanism of ImageDownloader, which identifies a resource by its absolute URL. See ImageDownloader.swift, line 527:
static func identifierForURLRequest(URLRequest: URLRequestConvertible) -> String {
        return URLRequest.URLRequest.URLString
    }

Where the implementation of URLString returns the value of the request URL's absoluteString.
Would it be an idea to provide a hook to provide a custom identifier for a given resource when scheduling the download? In our case, the image names (without signature parameters) would be sufficient, but I am not aware if this would work in all cases. Or is there already a mechanism in AlamofireImage that handles signed URL's that I am not aware of?
Update
After reading up on NSURLCache, which works out of the box/under the hood when using Foundation's URL*-classes, it's clear that the problem is not the in-memory Alamofire cache, but the NSURLCache. It cashes the NSURLRequest, probably using the absolute URL as well, and it looks like there's no way to change this.

You nailed i @kaspermunck...I don't think there's really anything we can do for that type of URL in AFI. Everything stored on-disk is using the NSURLCache which is what you're getting bit by.
If you really need more intelligent caching, you could build your own ImageCache that can persist images on-disk. However, I'd caution you to make sure this is absolutely necessary before doing so, b/c implementing an on-disk image cache is not trivial.
I'm going to go ahead and close this issue out @kaspermunck since I don't think there's an actionable item on our part. Please feel free to keep commenting on this ticket if you have additional questions or more info.
Cheers. 🍻

That's what I thought. Spinning up our own on-disk cache is definitely not something we wanted. Instead, when requesting a private image resource from Amazon, we hit a static URL on our own server, which then forwards the request to Amazon's signed URL. It works very well for us, but comes with a few caveats:

We must hit our own server before forwarding, which obviously increases the traffic. However, since it's merely an HTTP forwarding, it hasn't revealed any performance issues yet.
It does require a bit of client-side logic, where we have to hook into NSURLSession's dataTask:willCacheResponse... and the Manager's taskWillPerformHTTPRedirection methods and do a bit of work to remember the original (pre-forwarding) request, because the request will chance during the HTTP-forwarding.

Thanks for your time looking at the issue though.

Is there a way to implement cache key filter so we can use AlamofireImage directly with Amazon's signed URL?
SDWebImage had a similar issue that was resolved with something like
func registerSDWebImage() {
		SDWebImageManager.sharedManager().cacheKeyFilter = { url in
			let components = NSURLComponents()
			components.scheme = url.scheme
			components.host = url.host
			components.path = url.path!
			return components.URL!.absoluteString
		}
	}


data preprocessing

Hello author, I’m sorry to bother you again. In the paper, I didn’t see more detailed data preprocessing information. In the process of data preprocessing, is the slice data 256 bytes, 784 bytes, or 900 words? festival. Looking forward to your reply

Hello author, I’m sorry to bother you again. In the paper, I didn’t see more detailed data preprocessing information. In the process of data preprocessing, is the slice data 256 bytes, 784 bytes, or 900 words? festival. Looking forward to your reply

Hello, the datagram is sliced into lengths in this article and is controlled within 512, here is not referring to bytes, but the size of the slicing sequence.

Hello author, I’m sorry to bother you again. In the paper, I didn’t see more detailed data preprocessing information. In the process of data preprocessing, is the slice data 256 bytes, 784 bytes, or 900 words? festival. Looking forward to your reply

Hello, the datagram is sliced into lengths in this article and is controlled within 512, here is not referring to bytes, but the size of the slicing sequence.

According to the data set (packet) you gave, I found that there are 64 tokens in each category. How is this related to the 512 tokens you mentioned? Looking forward to your reply, sorry to bother you again

Hello author, I’m sorry to bother you again. In the paper, I didn’t see more detailed data preprocessing information. In the process of data preprocessing, is the slice data 256 bytes, 784 bytes, or 900 words? festival. Looking forward to your reply

Hello, the datagram is sliced into lengths in this article and is controlled within 512, here is not referring to bytes, but the size of the slicing sequence.

 According to the data set (packet) you gave, I found that there are 64 tokens in each category. How is this related to the 512 tokens you mentioned? Looking forward to your reply, sorry to bother you again

The 512 mentioned in the paper refers to the length of the final embedded representation used for pre-training, while in the pre-processing, the packet level and flow level are sufficient by controlling the actual length plus the special token to not exceed 512.


bug

hello, I installed the script, no issues. However when I use only one spike strip I get another three in my inventory, please help:

Fixed (hopefully)


get_environment_type() still exists in SS4

Sorry @zanderwar I'll merge this manually. :) Had to shift to 4.0 branch, otherwise it won't get into the tagged changelog.


[Bug] Part of the chart for stars was covered

Version
1.7.3
Current Behavior
Part of the chart for stars was covered.
https://github.com/Tencent/APIJSON

Expected Behavior
Move the chart lower that make it show completely.
Environment
- OS: MacOS Monterey 12.6
- Browser: Chrome 107.0.5304.110（正式版本） (x86_64)

Any additional comments?
None.

Hi @TommyLemon, thanks for your feedback! But I cannot repeat the problem you met🤔  :

When I open page in window mode and scroll the page sightly, this problem arises.

I have also tried this way but cannot reproduce the phenomenon 😆

@tyn1998 u need to scroll up the web page, if u don't, it will just show completely.

Close for now, anyway, thanks for your feedback!


Find in Files (Patterns of excluded directory)

Environment
. A project exists.
. Two directories exist in the project. Let's call them directory1 and directory2.
. Both directories have a json file which 'name' is written in.
Step

Select project.
Find in files.
Input 'name' in the key word.
Input 'json' in the 'Searched file' in the Optional fields'
Input 'directory2' in the 'Excluded directories' in the 'Optional fields'.
Click find.

Result
Not found.

It is in normal operation. Can't reproduce.

For more information,
the problem was temporarily occurred because of a server problem.


Determine where to slot K2 into kubernetes tooling docs

We need to get k2 (or k2cli probably) onto this page somewhere:  https://kubernetes.io/docs/getting-started-guides/
Figure this out after Node Management is (mostly) complete and see where joyent is.

joyent is dead.  don't consider it.


Add Promise return type for proxy function

Compiling this project in TypeScript 4.1.2 gave the following error:
error TS2314: Generic type 'Promise<T>' requires 1 type argument(s).
declare function proxy(proxyParams: ProxyParams): Promise

This commit tries to fix this error without being explicit with the return type.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Released in RC 6

Released in RC 6


Add onKeyDown support to grid.

Merging this, thanks.  I am going to simplify the comment a bit post-merge -- think its a bit too much detail on this issue, when all we really need is a pointer.


Downloaded files nowhere to be found

Hi!
Thx for making this application!
The application ends successfully on my laptop, but I can't find the downloaded files. According to the readme, they should be in the ~/.config/antfs-cli/ directory, but this directory does not exist. There are also no logs in the antfs-cli directory.
Am I doing something wrong, or is there something I'm missing? When I try to download the files again, they seem to be marked as 'already downloaded', as the application quits immediately.
Thx!

You night have another path set for $XDG_CONFIG_HOME. It looks for this env var first and then in ~/.config. Could this be it?

Ok, found it! I was looking at ./config on my root, not on the HOME directory:)
thx!

Glad you found 'em!


refine travis-ci scripts

Coverage decreased (-0.03%) to 90.094% when pulling 72340dc3341eaafdd18fc65d65bbc7238f0cae58 on XenoAmess:patch-1 into a9dd82f83e751022d1a7f8e6fde246d9082aeca5 on apache:master.

EmptyPropertiesTest fails on jdk13.
But....why?
the last commit 5 days ago can pass the build but this cannot?
I don't think I touched somethings that can affect the test result...
Anyway, it seems not related to this pr.


Update cancel-workflow-action

Codecov Report

Merging #814 (cfc76a0) into master (bfb47d8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #814   +/-   ##
=======================================
  Coverage   78.05%   78.05%
=======================================
  Files         102      102
  Lines       10041    10041
=======================================
  Hits         7837     7837
  Misses       2204     2204

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Messed up Merges

I messed up PR Merges due to multiple Contributors working simultaneously.
I tried to resolve a few conflicts but messed up the rest.

Looks like you could use a contributing guide for this repository for contributors which would have a detailed explanation about how to contribute here. If you could assign me this issue, I could draft it up for you so that the same problem doesn't happen again.

Looks like you could use a contributing guide for this repository for contributors which would have a detailed explanation about how to contribute here. If you could assign me this issue, I could draft it up for you so that the same problem doesn't happen again.

That would be great...
Thank You 😃


Signround code repo

The official implementation of "Optimize Weight Rounding via Signed Gradient Descent for the Quantization of LLMs" has been changed to https://github.com/intel/auto-round,  could you kindly have a change?

Thanks for the notification! We have updated the link for the implementation.


patch: support multiple select for EntityPicker

Hey, I just made a Pull Request!
https://github.com/backstage/backstage/issues/16334

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation: will do once changes are discussed.
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Let us know if this is ready for review by marking it as such! 🙏

Thanks @Rugvip , we can close this PR. We agreed to take another approach as discussed in https://github.com/backstage/backstage/issues/16334 .. but I have been finding it difficult to find time to implement that. Maybe someone can help there. Thanks.


chore add section in readme for local dev setup

Small PR to add a section to explain how to get a local development setup going to work on the code base.

Codecov Report
Base: 31.62% // Head: 31.62% // No change to project coverage :thumbsup:

Coverage data is based on head (0307712) compared to base (903e374).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #637   +/-   ##
=======================================
  Coverage   31.62%   31.62%
=======================================
  Files          97       97
  Lines       11630    11630
=======================================
  Hits         3678     3678
  Misses       7621     7621
  Partials      331      331

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update requirements

Coverage remained the same at 60.935% when pulling d01e9f21f9c1da1edc59c9af75041e6701aca390 on castrapel:up-reqs-12182018 into 388699be7c9b152f894ef7527ae1b5c8290eadc2 on Netflix:master.


The requested PHP extension xmlrpc is missing from your system.

I can not install your package. I got a message:
The requested PHP extension xmlrpc is missing from your system.
Please help me!! Thank you very much.

You need enable PHP xmlrpc extension to use this library.
For example, in Ubuntu, run these command to enable the extension.: sudo apt-get install php5-xmlrpc and sudo php5enmod xmlrpc

Thank you very much :D. But how can I upload a featured image?

First, use uploadFile method to upload your image to Wordpress. Get its ID from the returning array.
Next, set the $content['post_thumbnail'] to that ID and using newPost or editPost to attach the uploaded image as the post feature image.


Fix #337: Implement span creation in graph editor

Pull request type

Feature

What is the current behavior?

Issue Number: #337
What is the new behavior?

Implements span creation in graph editor:

Add syntax to ANTLR grammar
Implement handling
Add unit and integration tests

Fix #337

Does this introduce a breaking change?

No
Other information

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added or the PR is neither a bug fix nor a feature
[x] Docs have been reviewed and added / updated if needed or the PR is neither a bug fix nor a feature
[x] The Unreleased section in CHANGELOG.md has been amended to reflect the changes in this PR if needed
[x] Build (mvn verify) was run locally and any changes were pushed
[x] The pull request is against the correct branch (master for bug fixes, develop for new functionality)
[x] Dependencies and citation templates have been updated where necessary or there are no new dependencies

Checklist for maintainers
Releases

Do NOT push the green merge button on GitHub.
Follow the latest version of the developer/maintainer docs for making releases.
Check that license and citation information for dependencies are complete (each dependency has a folder in /THIRD-PARTY/).

Hello @bbunzeck, I've realized that my SonarCloud setup was still pointing to this repository, which means that I wasn't able to run all tests. This has been fixed in https://github.com/hexatomic/hexatomic/pull/338/commits/4f41b33f92aacdd540ec154b7bacf4ba4601178e. You can check the test results once the workflows have run there.

@bbunzeck As you can see, the tests now ran successfully: https://github.com/stephandruskat/hexatomic/actions/runs/1281800411.
If you decide to merge, I suggest you set the values for -Dsonar.projectKey= and -Dsonar.organization= back to the original values, so that the checks can also run in your repository after merge: -Dsonar.projectKey=hexatomic_hexatomic -Dsonar.organization=hexatomic.

@bbunzeck As you can see, the tests now ran successfully: https://github.com/stephandruskat/hexatomic/actions/runs/1281800411.
If you decide to merge, I suggest you set the values for -Dsonar.projectKey= and -Dsonar.organization= back to the original values, so that the checks can also run in your repository after merge: -Dsonar.projectKey=hexatomic_hexatomic -Dsonar.organization=hexatomic.

Thank you for your changes, now I am able to move the pull request forward.


Querying sequence with big number returns 0

If you have a SEQ with current value for example 30000 is ok, but if 30000000 you will get 0 in nextId.
Code with commit date older than 27 july 2018 works fine.
rows, _ := connection.QueryContext(ctx, "SELECT SEQ.NEXTVAL FROM DUAL")

var nextId int64

for rows.Next() {

	rows.Scan(&nextId)
}

Working on test cases for this now, so far not seen any issues. Can you please try this in SQL Plus and post the results?
Also, please post your full create statement for your sequence.

Unfortunately i cannot reproduce this in SQL*Plus because i never use it. I can only say it did not work in latest release i downloaded a week ago. So chose last working commit for me and downloaded as zip: go-oci8-e93f3e58bcb5be7ef81ff74133fab25be6153c2d.zip

CREATE SEQUENCE  "AGENCY_TEST"."S_TELEX_1"  MINVALUE 38999999 MAXVALUE<PHONE_NUMBER>999999999999999999 INCREMENT BY 1 START WITH 39000045 NOCACHE  NOORDER  NOCYCLE
here is my test sequence

Added sequence tests:
https://github.com/mattn/go-oci8/pull/286
They all passed. Far as I can tell driver is fine.
The problem you are having could be located elsewhere. If you still think it is a driver issue going to need more, like SQL Plus testing and full test case/code/SQL.

Close this?

I think yes


Obstacle stop planner causes slow creep and crash

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
Creating a simple scene in scenario_v2 of ego trailing a fake agent via ACC where the fake agent eventually stops, it causes ego to stop pass the stop point and to slowly creep forward onto the stopped agent.
Expected behavior
After the other agent stops, ego should stop and not creep forward.
Actual behavior
Ego stops past the obstacle stop line and it subsequently starts to creep forward.
Steps to reproduce

Create an agent that goes forward at constant speed and then stops.
Have ego in the same lane trailing the vehicle with ACC.
Make agent stop.

Versions

OS: Ubuntu 22.04
ROS2

Possible causes
Condition if (node_param_.enable_slow_down && latest_slow_down_section_) inside ObstacleStopPlannerNode::insertVelocity is the culprit. The logic makes it so the condition is always satisfied.
Additional context
No response

@xmfcx I finally tracked the problem down. The issue happens in the searchPredictedObjects function, particularly this line:  https://github.com/autowarefoundation/autoware.universe/blob/main/planning/obstacle_stop_planner/src/node.cpp#L904C1-L910C10
The issue is twofold:

The intersection polygon previously computed is not really a polygon. A quick debug_ptr_->pushPolygon shows that the intersection is actually a segment of the edge of the collision predicted object. I'm fairly sure the boost intersection geometry operations within the the searchPredictedObjects is not quite correct.

The collision_point computed as a result of the bg::intersection call is a point on the edge of the one_step_move_vehicle_polygon which will (with a bit of noise) cause the previously provided code snippet with the condition bg::within(collision_point, one_step_move_vehicle_polygon) to fail, which in turn causes the planner_data.found_collision_points to be false.

@MrRubyRed
Thanks for creating the issue.
Could you create a PR that solves the problem or could you share a scenario where the issue can be reproduced.

https://github.com/autowarefoundation/autoware.universe/pull/5545

Hi @MrRubyRed, I created a draft PR that may solve this problem. I wrote the idea behind this PR here. Can you try this PR for your case?

@MrRubyRed I will be closing the issue since it is stale. Please open up again if the issue is still there.


evaluation

The model was successfully trained by tape-train, and finally, a folder was created under the results folder. In this folder, I could not find anything about the evaluation of the results, such as accuracy, etc.What should I do to get the evaluation?

You can use the tape-eval function - however the eval is a little buggy at the moment unfortunately. It's on my list of things to do. I should get around to it sometime in the next week. I will update the README with instructions when I have everything sorted.

Please do! If you could do it faster than next week that would be greatly appreciated. I currently can't run evaluation for the UniRep model. I get the following error:
Evaluation:   0%|                                                                                | 0/1 [00:04<?, ?it/s]
Traceback (most recent call last):
  File "C:\Python37\Scripts\tape-eval-script.py", line 11, in <module>
    load_entry_point('tape-proteins==0.3', 'console_scripts', 'tape-eval')()
  File "c:\python37\lib\site-packages\tape\main.py", line 213, in run_eval
    return training.run_eval(**eval_args)
  File "c:\python37\lib\site-packages\tape\training.py", line 593, in run_eval
    save_outputs = run_eval_epoch(valid_loader, runner, is_master)
  File "c:\python37\lib\site-packages\tape\training.py", line 382, in run_eval_epoch
    save_outputs.append(_get_outputs_to_save(batch, outputs))
  File "c:\python37\lib\site-packages\tape\training.py", line 354, in _get_outputs_to_save
    outputs = outputs.cpu().numpy()
AttributeError: 'tuple' object has no attribute 'cpu'

So one other note - if you're just trying to evaluate the results of pretraining, tape-eval isn't really a great option. At best I could have it tell you language modeling accuracy / perplexity, but empirically this does not seem to have a strong correlation with performance on downstream tasks.
If you want to evaluate performance of a language model, your best bet is to use tape-train/tape-train-distributed along with the --from_pretrained flag to train a downstream task based on the pretrained model (this will run validation passes as well). tape-eval is only needed to run the test set of a task.
Regardless, I'll aim to have tape-eval fixed and a section in the README about evaluating models by the end of the week.

Thanks for the info :). When running tape-train, I only see validation losses though, no accuracies or other metrics, to compare against the metric given in the readme for the different tasks and models.

Ah yeah I'll fix that - API got updated a lot in the week before release and metrics were taken out for initial simplicity. Should be easy to add them back in.

Both issues should be fixed by #25, which adds metrics to the training loop and fixes the tape-eval command. I have also added sections to the README on evaluating a language model, training a downstream model, and evaluating a downstream model. Let me know if there is anything missing.
The one missing metric for tape-eval is Precision @ L/5 for contact prediction (this will be reported during train/eval but it is missing during test). I will fix this in the future, but wanted to get this out ASAP since all other tasks should be good to go.

Ran tape.eval and got this error. This makes me feel strange.

Closing because no response.