Add Flux v2/GOTK and migration announcement

Need to inform the community of changes to come.

What about something like this?
diff --git a/config.toml b/config.toml
index 650e122..166ec45 100644
--- a/config.toml
+++ b/config.toml
@@ -11,6 +11,10 @@ slack                = "https://cloud-native.slack.com/messages/flux"
 mailing_list         = "https://lists.cncf.io/g/cncf-flux-dev"
 font_awesome_version = "5.3.1"

+notification = """
+📣 **[Flux v1 is in maintenance mode](https://github.com/fluxcd/flux/issues/3320)!** We will soon start publishing guides which help you migrate Flux v2 and the GitOps Toolkit. **[Learn more](https://toolkit.fluxcd.io/)** and **[join the discussion!](https://github.com/fluxcd/toolkit/discussions)**
+"""
+
 summary = """
 Flux is a tool that automatically ensures that the state of your [Kubernetes](https://kubernetes.io) cluster matches the configuration you've supplied in Git. It uses an [operator](https://github.com/operator-framework/awesome-operators) in the cluster to trigger deployments *inside* Kubernetes, which means that you don't need a separate continuous delivery tool.
 """
diff --git a/layouts/_default/baseof.html b/layouts/_default/baseof.html
index d9edd2b..4c7918e 100644
--- a/layouts/_default/baseof.html
+++ b/layouts/_default/baseof.html
@@ -10,6 +10,7 @@

+      {{ partial "notification.html" . }}
       {{ partial "navbar.html" . }}

       {{ block "main" . }}
diff --git a/layouts/partials/notification.html b/layouts/partials/notification.html
new file mode 100644
index 0000000..bf57283
--- /dev/null
+++ b/layouts/partials/notification.html
@@ -0,0 +1,4 @@
+{{ $notification := site.Params.notification | markdownify }}
+

+  {{ $notification }}
+

--

This is nice! <3

Moving to #25

Thanks everyone! This looks great! 😻


Fix subscription default generation

Subscription resolver interface is different from that of Query and Mutation.
This PR fixes the default generation value

/release-snapshot

/release-snapshot


Icona mono chrome IT Wallet

Use the correct icon attached (view the prototype reference)

Hi @RosaliaGaleano could you provide me with a svg version of the wallet icon?
it would be much easier to integrate it to the discovery page, alternatively if you only have the png version available I would ask you for a white version and a blue version with no background.
Unfortunately I don't have the necessary permissions to download the item from figma.

@MurruAlessio hi! I attached the requested icon also in this thread:


Speedup of powers

Implementing the disjoing pressure as
function power_2(arg::Float64)
	return arg * arg
end

function power_3(arg::Float64)
	return arg * arg * arg
end

function power_9(arg::Float64)
	temp = power_3(arg)
	return power_3(temp)
end

function fast_disj_32(arg::Float64)
    return power_3(arg)-power_2(arg)
end

function fast_disj_93(arg::Float64)
    temp = power_3(arg)
    return power_3(temp)-temp
end

leads to a speedup of 4-5 times compared with
power_broad(arg,3)-power_broad(arg,2)

or
power_broad(arg,9)-power_broad(arg,3)

Thus I would implement them.
Questions to discuss are

howis it implemented as comfortable as possible for the user?
Does if n==9 && m==3 cost unnecesarry time or is the compiler clever enough to factor it out
Do we also want to implement things like $n=6,m=3$ as used by Uwe Thieles group

Actually power_9 is not needed, we only need prime numbers, every non-prime is a waste of time

Doing an ifelse is not a perfomance issue, the compiler while be clever enough to compile it out

Doing an ifelse is not a perfomance issue, the compiler while be clever enough to compile it out

Always a good feeling when something you guessed is actually true 😀.
Thanks for the work, I will implement it shortly.

I just ran one of my simulations, that due to the second field should have more overhead, and if I am not overseeing something it gave me an incredible speedup of factor 8

Should be according to your suggestions @aedolfi. Only have the two powers which are used in papers, thanks again for pointing out a way to increase performance 🚀


Import external calendars (ICS)

It would be great if we can import calendars from external locations. This way we could include feeds with local bank holidays, leaves or team meetings.

That would be great! Team Calendar doesn't (yet) support importing other ICS formatted calendars, however it does support contributed event sources.
To see external events in your Team Calendar, you can create a new event source as an extension, such as in this example: https://github.com/Microsoft/vsts-extension-samples/tree/master/calendar-public-events
Thank you!


SVG transcoder not multiplatform capable

I transcoded some icons with the SVG transcoder Gradle plugin but found that the generated Painters are not multiplatform capable. They contain the following import statements:
import androidx.compose.ui.geometry.*
import androidx.compose.ui.graphics.*
import androidx.compose.ui.graphics.drawscope.DrawScope
import androidx.compose.ui.graphics.drawscope.Fill
import androidx.compose.ui.graphics.drawscope.Stroke
import androidx.compose.ui.graphics.drawscope.clipRect
import androidx.compose.ui.graphics.drawscope.translate
import androidx.compose.ui.graphics.drawscope.withTransform
import androidx.compose.ui.graphics.painter.Painter
import java.lang.ref.WeakReference
import java.util.*
import kotlin.math.min

where these two
import java.lang.ref.WeakReference
import java.util.*

are the culprit. The Java dependencies are clearly not multiplatform but luckily they do not even seem to be needed.  It would be nice though if you could change the transcoder, so that they are not generated at all and the output could then be used directly without having to manually fiddle with the code.
Cheers
Michael

No part of Aurora is intended to be multiplatform capable. The only supported platform is desktop.
As for the specific references - they are used for transcoded <image> nodes. See documentation and a sample transcoded file

That would open the door to committing to something that I very much intentionally have no plans to commit to. Aurora is targeting only the desktop environment.


Sync with original fork

@mikesplain @steve450 please take a look at this upstream merge. It is small since Mike already did the real work recently

No corresponding change to Puppetfile to update brewcask version?

Our brewcask version was already at 0.0.7 in the Puppetfile

+1


add a mailto: link to contact

Hi.
How can I add an email  address to the contact menu, so it works as a mailto: link?

Hi there,
So you have this file, file name: /layouts/partials/header.html
Here, after line 17 you can do something like below

                {{ $url := .URL | relLangURL }}
                {{ range .Site.Menus.main }}

                    {{ .Name }}

                {{ end }} // this is line 17
                // you need to add this
                YOUR_EMAIL_ADDRESS

 // this is line 18
            {{ if gt (len .Site.Home.AllTranslations) 1 }}

Hello,
Sorry for the delay.
I added support for mailto: links inside the header menu here. You should now be able to add the link in the config, e.g.:
  [[languages.en.menu.main]]
    url =<EMAIL_ADDRESS>    name = "Mail me"
    weight = 4

Let me know if you have any questions,
Thank you!

Closed for no activity.
@coloquio let me know if the above doesn't fix your issue.
Thank you!

thanks it works now


Engsys/prepare for types node v16

with globalThis, old logic to get global object is no longer needed.
for some reason, TypeScript compiler couldn't resolve to use the proper setTimeout overload. Working around by casting callback to (args: any) => void or just returning Promise<void>

/azp run js - service-bus - tests

API change check
API changes are not detected in this pull request.


About aimbot

aimbot seems to aim at a target behind an obstacle, sometimes even a mountain

That's quite weird because the aimbot is doing a Physics.Linecast to detect if the target is "visible" (without something blocking the shot). That's why currently the aimbot is not firing when a target is behind bared wire fence.

https://github.com/sailro/EscapeFromTarkov-Trainer/assets/142997130/aeb9dd03-2855-46ba-8a54-c2d821f1fa6b

202308280949.mp4

Maybe it's because I used the  mod reshade-shaders and my graphics settings

这很奇怪，因为瞄准器正在检测目标是否“可见”（没有东西阻挡射击）。这就是为什么目前瞄准器在目标在带刺铁丝网后面时不会开火的原因。Physics.Linecast
您是否有更多信息，以便我们可以尝试重现？也许瞄准机器人能够用1px发现头部，而你无法用自己的眼睛看到它。

Like this
https://github.com/sailro/EscapeFromTarkov-Trainer/assets/142997130/502de3c1-2aa9-4fda-b027-367dab7cfea1

Ah good catch @leonardovac. I was thinking of the SilentAim, not the manual aimbot. But not sure we want to change that though. It can be quite useful to follow an enemy and then shoot as soon as he's visible.

Ah good catch @leonardovac. I was thinking of the SilentAim, not the manual aimbot. But not sure we want to change that though. It can be quite useful to follow an enemy and then shoot as soon as he's visible.

Hi team, this is actually a long standing issue that I designed a solution for a while back, which can be found in the issue linked here:
https://github.com/sailro/EscapeFromTarkov-Trainer/issues/75
We don’t currently have a consensus on that implementation though, and as Sebastian mentioned, being able to track an enemy through cover is particularly useful— which I hadn’t considered when designing that solution.
Maybe we can continue the discussion there and explore adding a subfeature toggle for the proposed visibility checking with the non-silent aiming mode?

Hi @Billybishop, I saw it after commenting on the issue, On my local repo I've added a toggle on the menu (which works only for normal Aimbot) already.
The only downside of the visibility check (with the current method): only the head bone works as intended.
Check below:


Link to Zotero group library not working

Hi Andrew, amazing that you made your materials publicly available, thanks!! I looked over the materials and noticed that the link to the shared Zotero group was not working for me. Could this be the link instead?

Nevermind! The link might just not be working yet for the fall semester, and the one I found on Zotero probably corresponds to the summer course


Atlassian Stride

I'm assuming the answer is the same as in https://github.com/howdyai/botkit/issues/1120 but I'm curious to see if people here are interested. Atlassian recently released Stride. If they see that peopel are interested here, they might put the effort in to make the integration work.

@plainspace that's about right. The Botkit core team is super interested in Stride as a platform. The best way to move it forward is either submit a request, or if you are a Stride customer submit a request to Atlassian!

thanks @peterswimm. just to clarify, do you mean submit a request here? i will reach out to Atlassian too!

@plainspace reach out to your stride representatives! We've added your vote here.

From what I understand reps from Atlassian and Botkit have talked and the issue is with the  business terms with regards to support for Stride so it is not a technical issue. What do you think the process might be to getting that resolved?

@plainspace I'm not exactly sure what business terms they're refering to, but it is true, there is nothing technical blocking someone from building an adapter for Stride.
We'd love to extend support to Stride, we just have to find someone who wants to dive in and build it!


Backport #22468 to 1.28

Failures:

https://github.com/grpc/grpc/issues/22351
https://github.com/grpc/grpc/issues/21934
https://github.com/grpc/grpc/issues/20677
Interop ALTS: Infra failure


Improve emoji SVG parsing by caching

This PR adds a cache for SVG parsing in the Text Server.
Basically, when we first encounter the document, we parse it as before, but we also note the offsets of other glyphs and store the remaining XML. The next time we see another glyph, we can simply parse that glyph node and insert it back into the stored XML.
Although it is still very slow in the case mentioned in #100278 (which is related to font rendering), the time difference is still significant (on my machine):
Before : 4 mins +
After: 35 secs
Fixes https://github.com/godotengine/godot/issues/100278

Seem like Windows build fail due to using designated tantalizers  😞
Fixed now.

And I add fb textserver part too.

@bruvzg , do you think these actually fixes #88809 and #100278 ? It still be very slow in #100278 case.

do you think these actually fixes https://github.com/godotengine/godot/issues/88809 and https://github.com/godotengine/godot/issues/100278 ? It still be very slow in https://github.com/godotengine/godot/issues/100278 case.

Not sure if a lot can be done for pre-rendering, pre-rendering option only exist because it is slow and primarily for MSDF, it should not be used for emojis in a first place.

Looks good! Could you squash the commits? See PR workflow for instructions.

Thanks! And congrats for your first merged Godot contribution :tada:


update target-observations to oracle-output

[ ] update file name for target-data/target-observations.csv to target-data/oracle-output.csv
[ ] within that file, update the observation column to oracle_value

Actually, we don't need to do this in this hub, because it contains time series data but not oracle output data.


Fix grammar and formatting in issues

Available for testing in fork: https://github.com/Technetium1/bitmagnet/issues/new/choose
This is a stopgap fix until migration to a proper YAML form.
Please squash merge since it's coming from my main branch :)

Thanks @Technetium1 , I'd also been meaning to update some of the wording on these and have done so on your PR.


Replace remaining Autograder references

This PR replaces the remaining references to "ag"/"Autograder" with "qf "/"QuickFeed".

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

406 of 1097 (37.01%)  changed or added relevant lines in 37 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 25.617%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

database/gormdb.go
30
31
96.77%

web/groups.go
16
17
94.12%

web/organizations.go
0
1
0.0%

web/rebuild.go
11
12
91.67%

database/gormdb_enrollment.go
22
24
91.67%

web/auth/provider.go
0
2
0.0%

web/repositories.go
4
6
66.67%

web/scm_helpers.go
11
13
84.62%

assignments/pull_requests.go
1
4
25.0%

database/gormdb_repository.go
5
8
62.5%

Files with Coverage Reduction
New Missed Lines
%

database/gormdb_submission.go
1
67.83%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2710

Relevant Lines:
10579

💛  - Coveralls

Codecov Report

Merging #672 (9584295) into master (2dfec96) will not change coverage.
The diff coverage is 44.83%.

@@           Coverage Diff           @@
##           master     #672   +/-   ##
=======================================
  Coverage   23.00%   23.00%
=======================================
  Files          65       65
  Lines       10181    10181
=======================================
  Hits         2342     2342
  Misses       7512     7512
  Partials      327      327

Flag
Coverage Δ

unittests
23.00% <44.83%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

qf/assignment.go
50.00% <ø> (ø)

qf/course.go
0.00% <ø> (ø)

qf/enrollment.go
53.42% <ø> (ø)

qf/group.go
28.00% <ø> (ø)

qf/pull_request.go
37.50% <ø> (ø)

qf/qf.pb.go
4.48% <ø> (ø)

qf/qf_grpc.pb.go
0.00% <0.00%> (ø)

qf/rebuild.go
0.00% <ø> (ø)

qf/repo.go
22.00% <ø> (ø)

qf/review.go
84.21% <ø> (ø)

... and 41 more

Continue to review full report at Codecov.

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

Only thing is the generated index.html that shouldn't be added, but should be listed in .gitignore.

Updated .gitignore, removed index.html.


Issues adding trunk and phone number to service provider with no accounts

Steps to recreate:

create a new service provider (SP) in the portal
create a new carrier for that service provider

Problem: after saving the carrier, the carrier list is empty.  It should show the carrier you just created
Now, if you did the steps this way, the problem does not occur:

create a new service provider in the portal
create a new account within that service provider
create a new carrier for that service provider

Then the problem does not happen.  In other words, if you immediately create an account after creating a service provider, you do not have the issue.  But it should not be required to do things in this order: you should be able to create an SP and then a Carrier for that SP without first creating an account

This issue comes from this one line.
https://github.com/jambonz/jambonz-webapp/blob/bb335d08387d20706ec0308f3cfd4cf098563ea1/src/components/pages/internal/CarriersList.js#L107
Simply removing it will fix this problem.
However, I am not sure why it is there at the first place. There should be a reason why it is there at the first place. So there is something about it that we can work toward it.

From this, I also discovered that this line is called twice when there is no accounts but once when there is an account.
https://github.com/jambonz/jambonz-webapp/blob/bb335d08387d20706ec0308f3cfd4cf098563ea1/src/components/pages/internal/CarriersList.js#L95
It is also safe to assume that some other methods on higher levels are also repeating. That seems like somewhere to fix also, maybe a bit minor.


[SNAP-859] Moved registration of InternalDistributedMember from Spark…

Changes proposed in this pull request
-Changes related to SNAP-859
-Removed registration of InternalDistributedManager from Spark Codebase
Patch testing
Prechecking was clean
Other PRs
Yes
Snappydata-293

@SachinJanani looks good.

Closing this PR as it is obsolete


Cancel rearm if parameter safety switch is otherwise turned back on

I've been making great use out of this component to automate some temperature / humidity control in my house and ran into a funny scenario. My automations will essentially turn off the safety switch, make their modifications, then rearm the switch manually. This mostly works just fine, but I was noticing spurious failures caused by the safety switch being enabled even though I just disabled it. I then checked the documentation to see that there was this rearm logic for 60 seconds... and my temperature and humidity sensors updated every 60 seconds....
So long story long, extra logging proved that since this rearm is unconditionally fired, the safety switch was (occasionally) being turned on again right between when I'd turn it off and edit a parameter or two. Quite the luck!
This change intends to fix that by keeping track of the rearm task and simply cancelling it if the switch has otherwise been rearmed.
(Note: This is the first pull request I've made in some time; apologies for any procedural errors.)

Thanks for the PR.  Looks like a good improvement.  I'll take a more detailed look later today.  I recall there being some unit tests for parameter safety - let's see if they need to be changed or added to to test this case?


update-automation: Create ~/bin if missing

Follow up to https://github.com/SUSE-Cloud/automation/pull/2715/


Native GCS support

What
part of https://github.com/roapi/roapi/issues/240
Before this PR, we allow use GCS via S3 API, but it requires setup of HMAC keys and it is not native.
https://cloud.google.com/storage/docs/authentication/hmackeys
This PR adds native GCS support using Google service account. GCP workload identity is NOT supported yet, depends on https://github.com/apache/arrow-rs/issues/3490.
Test
Integration test is added in CI.
(I also test locally with real GCS bucket)
Document
https://github.com/roapi/docs/pull/16
To Reviewer
This PR is based on https://github.com/roapi/roapi/pull/247, so need rebase if https://github.com/roapi/roapi/pull/247 is squash merge.

I was thinking to release 0.8.2 before this PR and after https://github.com/roapi/roapi/pull/247 is merged, but we merge too fast 😝 .
nvm, let's go directly to 0.9.0 after #250


Feature Request: Remove Unused Generated Hashes

From the README:

Like pip-compile, uv generates a platform-specific requirements.txt file (unlike, e.g., poetry and pdm, which generate platform-agnostic poetry.lock and pdm.lock files). As such, uv's requirements.txt files may not be portable across platforms and Python versions.

When --generate-hashes is supplied, since there is the above restriction on using requirements.txt anyways, is it possible to output only the hash(es) for that platform and Python version?
I know that uv behaves like pip-compile here. The main appeal of my suggestion is reducing the amount of volume being checked into the repository (see spoiler for how much was generated from one dependency). I imagine there would also be a slight uv pip compile, install and sync performance boost for not having to calculate and check against as many hashes.
Additionally, I think it would also improve reproducible slightly, though please correct me if any of my following logic is wrong. Say my application is working on Python 3.12 Windows given my compiled requirements on that developer platform and version combination. Perhaps the libraries I am using require extra dependencies when running on older Python versions (like typing_extensions to stub for new additions in typing) and a different OS. I then accidentally install my compiled requirements on and start my app in a Python 3.11 Linux environment where my service isn't going to work due to those needed extra dependencies missing.
Under the proposed behavior, I would find out about the host mismatch at build time, by my uv pip sync / install failing due to a hash for a different platform plus version not being listed. Under the current behavior, the install on the mismatched environment would still succeed and I would find out at runtime when one of my dependencies throws an error about say typing_extensions missing.

I think this is a very reasonable request but we need some new API for it. Something like: --generate-hashes=all vs. --generate-hashes=compatible.

@charliermarsh Yes, with one difference. It seems the other poster is requesting an opt-in flag for generate hashes to do this behavior. My thoughts are this behavior should become the only option. Pure python packages would be unaffected. And while that would be backwards incompatible for packages with binaries per platform, those relying on the current behavior are carrying a high risk anyways because they are (probably unintentionally) performing development / testing with a binary different from production. In a setting where --generate-hashes is being used, that discrepancy at best goes against efforts to obtain reproducible builds and at worst could be uncompliant with security standards. Though I understand if this comes across as being too purist.

Ah we commented at same time. Yes, the example API you gave would still be wonderful for my usecase and would enable smooth transition for existing users. In case you wanted to consider how an API could look for the more strict change I recommended above, I'd suggest a --generate-hashes={environment} where each invocation generates for only one OS and python version combination. If environment is host, it would resolve to host environment. Otherwise, environment should be {python-version}-{os} or whatever is standard.
Only one invocation needed for iterating locally, two invocations needed for iterating and deploying to different environment. If someone with the latter usecase used the proposed --generate-hashes=all, they would still be bringing in hashes for all these unnecessary environments used neither locally nor in production.

Actually, my suggestion of having to generate a lock file for the production environment specifically separately would require #3347. At that point, I believe my suggested --generate-hashes could become arg-less, and it could read the environment to generate hashes for in the same way the work spawning from that ticket reads the environment to cross-compile for.


Implement constant evaluation in patterns

The following tests fail due to the absent constant evaluation in patterns:

co19/LanguageFeatures/Patterns/constant_A03_t03
co19/LanguageFeatures/Patterns/constant_A03_t06
co19/LanguageFeatures/Patterns/map_A01_t01
co19/LanguageFeatures/Patterns/constant_A03_t07
co19/LanguageFeatures/Patterns/constant_A04_t01
co19/LanguageFeatures/Patterns/constant_A04_t02

Consider the following program as an example:
String test(List value) {
  if (value case const <int>[1, 2]) {
    return "[1, 2]";
  }
  return "other";
}

main() {
  print(test(const <int>[1, 2]));
}

When complied to Kernel currently, only one of const <int>[1, 2] is represented as a constant.
library /*isNonNullableByDefault*/;
import self as self;
import "dart:core" as core;

static method test(core::List<dynamic> value) → core::String {
  final core::List<dynamic> #t1 = value;
  if(#t1 =={core::List::==}{(core::Object) → core::bool} core::_GrowableList::_literal2<core::int>(1, 2)) {
    {
      return "[1, 2]";
    }
  }
  return "other";
}
static method main() → dynamic {
  core::print(self::test(#C3));
}
constants  {
  #C1 = 1
  #C2 = 2
  #C3 = <core::int*>[#C1, #C2]
}

It prevents the equality to work for constants as expecting, resulting in failing tests. When the program shown above is run, it prints other.

Related to #50629

This seems to have been fixed together with #50629


Edit: Set the default model to Claude Sonnet 3.5

Closes https://linear.app/sourcegraph/issue/CODY-2549/change-inline-edits-default-model-to-sonnet-3-5
Description
This PR:

Updates the inline-edit default model to Claude 3.5 Sonnet
Adds support for setting different defaults for edit/chat

Test plan

Clear local storage
Check the edit model default is 3.5 sonnet
Check the chat model default is 3 sonnet

Oops, somehow broke the chat input selector... looking into the fix

@umpox w decided to use 3.5 sonnet as the default model for chat, and updated that in https://github.com/sourcegraph/cody/pull/4822 which also set it to be the default model for Edit.
As @jamesmcnamara  is currently working on using server-side config as the default model list, I think we can close the issue and this PR since there will be some changes on the overall Model class and services.
Thank you so much for your quick work on this 🙇♀


almalinux: "/sbin/mount.vboxsf: mounting failed with the error: No such device" for vagrant-vbguest > 0.21

Installation fails on almalinux/8 with vagrant-vbguest versions 0.22 and later with the following error:
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000,_netdev vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

Downgrading to version 0.21 fixes the problem.
To reproduce:
vagrant plugin install vagrant-vbguest
vagrant init almalinux/8
vagrant up

Complete log:

admin@macmini2020e vagrant-test % vagrant --version
Vagrant 2.2.19
admin@macmini2020e vagrant-test % vagrant plugin install vagrant-vbguest
Installing the 'vagrant-vbguest' plugin. This can take a few minutes...
Fetching micromachine-3.0.0.gem
Fetching vagrant-vbguest-0.30.0.gem
Installed the plugin 'vagrant-vbguest (0.30.0)'!
admin@macmini2020e vagrant-test % vagrant init almalinux/8
A `Vagrantfile` has been placed in this directory.  Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
admin@macmini2020e vagrant-test % vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'almalinux/8'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'almalinux/8' version '8.6.20220513' is up to date...
==> default: Setting the name of the VM: vagrant-test_default_1653676739872_49106
==> default: Fixed port collision for 22 => 2222. Now on port 2208.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2208 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:2208
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
[default] GuestAdditions seems to be installed (6.1.28) correctly, but not running.
Redirecting to /bin/systemctl start vboxadd.service
Redirecting to /bin/systemctl start vboxadd-service.service
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules.  This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions:   /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Kernel headers not found for target kernel
4.18.0-372.9.1.el8.x86_64. Please install them and execute
  /sbin/rcvboxadd setup
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Restarting VM to apply changes...
==> default: Attempting graceful shutdown of VM...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default:
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
==> default: Mounting shared folders...
    default: /vagrant => /Users/admin/vagrant-test
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attempted was:

mount -t vboxsf -o uid=1000,gid=1000,_netdev vagrant /vagrant

The error output from the command was:

/sbin/mount.vboxsf: mounting failed with the error: No such device

admin@macmini2020e vagrant-test % client_loop: send disconnect: Broken pipe

This is on:

MacOS 10.15.7 (Catalina)
VirtualBox 6.1.16r140961
Vagrant 2.2.19

This line appears to be your problem (I'm also have a similar issue):
VirtualBox Guest Additions: Kernel headers not found for target kernel
A "chicken and egg" issue - the running kernel in the base box doesn't have the proper kernel header source installed for the Guest Additions to build properly, but the current kernel-headers packages match the current kernel, which isn't running in the box. If the kernel headers don't match then the Guest Additions build will fail. Hence vboxsf is not being inserted into the running kernel. I believe that's the problem you're facing.
Trying to specify the exact kernel-header package doesn't seem to work either as it seems older kernel-header packages are removed from the base/updates repos (at least for Rocky Linux - it may work for Alma)
One workaround to try is to vagrant ssh to the box, upgrade the running kernel, and install the proper kernel-devel and kernel-headers packages, along with the proper build packages (bzip2 elfutils-libelf-devel gcc kernel-devel kernel-headers make perl tar). You could also see if the kernel-headers for your running kernel are available in a repo somewhere.
You can also try to install those required pacakges with the installer_hooks config option:
vm.vbguest.installer_hooks[:before_install] = ["yum -y install bzip2 elfutils-libelf-devel gcc kernel-devel kernel-headers make perl tar", "sleep 2"]

That command won't work directly because I'm guessing kernel-headers will install the most recent kernel headers and not the one for your running kernel. That's the boat that I'm in.
Depending on your distro you may or may not be able to install the proper version of the kernel headers. this is the case I'm trying to find a solution to.
The following would be good for the vbguest plugin to perform as a kernel-headers mismatch seems to be a fairly regular case (at least with RH linux variants - centos, rocky, etc):

Check if allow_kernel_upgrade is true
IF TRUE

Upgrade kernel and install proper build dependency packages
Reboot
Upon restart try guest additions ISO mount and installation

ELSE

Warning the user that the installation may fail if allow_kernel_upgrade is false
Proceed with guest additions ISO mount and installation

Another check could be run uname -r (or equivalent Ruby code) and verify that the kernel headers installed match the running kernel. If there is a mismatch and allow_kernel_upgrade is true then perform the same steps as my TRUE pseudo-code block above.
I know no Ruby code, nor syntax. I will try to build a pull request to add this functionality, but would like to hear from the vagrant-vbguest maintainers to hear their thoughts on this use case. This case seems fairly common, but they probably have more wisdom than I  😁

Follow-up: for my situation, adding the following to my Vagrantfile worked to get guest additions running (if you don't mind upgrading the kernel in your vagrant box):
    # Get the kernel inside the box upgraded so VBox Guest Additions work
    app1.vbguest.installer_options = { allow_kernel_upgrade: true, auto_reboot: true }
    app1.vbguest.installer_hooks[:before_install] = ["dnf -y install bzip2 elfutils-libelf-devel gcc kernel kernel-devel kernel-headers make perl tar", "sleep 2"]

Change app1 to the name of your vm or if you have a standard Vagrant.configure("2") do |config| loop I think you would change app1 to config.vm (I'm a newb vagrant user so it may take some fiddling to get the proper option).
I still initially received the message about Kernel headers not found however after my vagrant box rebooted vboxsf was installed into the running kernel and sync_folders worked.
Good luck!

Thanks for the detailed analysis. What I don't understand, why does it seem to work with 0.21? Or at least, there is no error message with 0.21.
You mentioned Rocky. Is there a notable difference between Alma and Rocky?

Just was bitten by this again. We moved our services to a new host, and of course I forgot to downgrade the plugin. Current version is 0.31, and still same problem.
Apparently in the mean time:

support for Rocky has been added: #424
but not support for Alma: #430

Both distros claim to be binary-compatible, so I think they can be treated the same?
Anyway, I moved my box to Oraclelinux, and all is fine now.


Changing the text "clear" of the clearing button

Hi, I'm a bit bugged by the "Clear" content of the button element, I wish I could get a X instead, or an arbitrary nice character, or an svg.
What do I need to write with "new PagefindUI(" to correct that ?
I don't know javascript.
Thanks

@evanescente-ondine you can change the labels like this:
window.addEventListener('DOMContentLoaded', (event) => {
    new PagefindUI(
      {
        element: "#search",
        translations: {
          clear_search: "X",
        }
      });
  });

Other translatable strings are listed here: https://github.com/CloudCannon/pagefind/blob/main/pagefind_ui/translations/en.json
I don't think you can put an image there.

ok, I'm starting to understand the pattern now. Much thanks, what a great
app.


Document svelte:document

Should address #374. Or at least be a start.
I tried adding an example, but the REPL wasn't working as expected:
<svelte:document on:mouseenter='set({ entered: true })' />

The mouse is {entered ? 'in' : 'out'}

Maybe that's because how the REPL is built?

thank you!


Passing incompatible CPU's

It is passing several incompatible CPU's.  i.e. Intel Core i5-1035G7, Intel Core i7-4600U and Intel Core i5-7300U.  I am not sure what I would need to modify in the script to eliminate those CPU's from being counted as compatible.

The script is pulling the CPU list of Intel devices from here which does not appear to be open to changes from the public.
We might be able to add filters script side to accommodate for that limitation.
What brought you to the conclusion that these CPUs are not compatible with Windows 11? It would be nice to know since Microsoft seems to insist they'll work in their docs.

If you search the list those CPU’s are not on it.  There are no CPU’s before 8th gen anywhere on that list.
Sent from my iPhone

On Apr 19, 2022, at 15:16, Dakota Clark @.***> wrote:

The script is pulling the CPU list of Intel devices from here which does not appear to be open to changes from the public.
We might be able to add filters script side to accommodate for that limitation.
What brought you to the conclusion that these CPUs are not compatible with Windows 11? It would be nice to know since Microsoft seems to insist they'll work in their docs.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

Correction to last post the Intel Core i5-1035G7 is on the list but the other 2 are not.

It looks like AMD and Intel both had a processor with 4600U, with the AMD being compatible. I was only looking at the model, not the brand which seems to be the issue. I think I have a fix but don't have any of the processors listed available to test. Could I have you replace lines 8-20 in Win11Compatablilty.ps1 with the following and see if you still are getting a false compatible? If this fixes it for you, I will push the new version to the repo.
###Import approved Processor list
$final = Import-Csv "C:\temp\proc.csv" | ForEach-Object {
[PSCustomObject]@{
'Brand' = $.Brand -replace "???","(TM)" -replace "??","(R)"
'Model' = $.Model
}
}
###Get Procossor
$proc =  Get-CimInstance -class CIM_Processor | Select-Object Name
$ProcCompatible = $false
###Compare processor to approved list
foreach($cpu in $final){
if($proc3 -like "*" + $cpu.Brand + "*" + $cpu.Model + "*"){
    $ProcCompatible = $true
    break
}

}

The i7-4600U, 15-6300U and i5-7300U are still showing up in the compatible list.  Now the i5-8500T, i5-8350U, i5-8365U, W-2255, i5-1145G7 and i5-10310U are failing the check, but are all in the Microsoft Compatibility list.  I can manually ween them out when using the original script, just by putting in a Not Any filter  since there are only 3 CPU's.  But if you want me to test script changes for you I am game, scans do take some time as we have over 3000 devices.  I don't get why the 6300U or 7300U keep passing as they are not found in AMD, Intel or Qualcomm's lists.


feat: add line-number to templateSimpleExpression output

In this PR, I:

Changed the content of the not-simple-expression.vue just for testing.
Added (Line ${lineNumber}) to the final console log in the not-simple-expression.vue test.
Added the logic to obtain the lineNumber for each expression in matches array.

I couldn't get to test the feture as an end user, I tried both ways @rrd108 recommended in #54 but I didn't get anywhere. But using Debug: JavaScript Debug Terminal I could follow the lineNumber calculation and I checked with multiple cases and it seems to work.

I'll leave this as a Draft PR just because I couldn't verify it that way

HI @rrd108
I just realized that there is a function called getLineNumber that is being used in multiple parts of the codebase. So I'm trying to use that implementation in my PR but I'm a bit confused about the arguments the function receive. It receives source and pattern as strings.
From all places where its used it uses the descriptor.source that is basically a code fragment and the pattern is it the regex used to find the matches?

So I'm trying to use it like this but it's not working as expected, am I sending the wrong parameters?

I'll close this PR cause the issue was already solved in a1203bb


"Comparision" rule is not matching

Issue type

Bug Report: no
Feature Request: no
Question: yes
Not an issue: no

Prerequisites

Can you reproduce the issue?: yes
Did you search the repository issues?: yes
Did you check the forums?: yes
Did you perform a web search (google, yahoo, etc)?: yes

Source code: https://github.com/deostroll/feel/tree/traces
Grammar file: grammar/feel.pegjs
Executable file: dummy.js
Program output: https://gist.github.com/deostroll/027ea709b1506393974e2ab5358640ca
Description
Unable to figure out why the Comparison rule is not matching. I have enabled tracing for my parser. The built-parser (with default tracing) is available in the above source code repository. The output of the program is the trace + some console.log which comes towards the end - that is the parser messages itself. It is linked above.
Steps to Reproduce

Download repo, and, npm install (make sure of the correct branch)
Copy code from below to file dummy.js
Run node dummy.js

Example code:

const feelFactory = require('./index');

const {feel} = feelFactory();

const exp = "date(\"2012-12-25\") – date(\"2012-12-24\") = duration(\"P1D\")"
// const exp = "(1) - 2"
const spacedString = ' '.repeat(exp.length);
//
const parserOptions = {};
const payload = {

}
try{
    var ast = feel.parse(exp); //parser call
}
catch(excep) {
    console.log(excep.message);
    let errStatement = exp;
    console.log(exp);
    let pointer = [].slice.call(' '.repeat(exp.length));
    pointer[excep.location.start.offset] = '↑';
    pointer[excep.location.end.offset] = '↑';
    console.log(pointer.join(''))
    // pointer[excep.location.start.offset] = '|';
    // pointer[excep.location.end.offset] = '|';
    // // errStatement += pointer
    // console.log(pointer.join(''));
    return;
}

    ast.build(payload)
    .then(res => {
        console.log(res)
    })
    .catch(e => console.log(e));

Expected behavior:
Should have evaluated to true
Actual behavior:
Throws a parser exception.
Software

PEG.js: 0.10.0
Node.js: v10.15.1
NPM: 6.2.0
Browser: chrome
OS: windows
Editor: vs code

After fiddling with this for 30+ minutes I realised something was off with the input, not the grammar 🤣
$ node
> "–".charCodeAt(0)
8211
> "-".charCodeAt(0)
45

In other words, this:
const exp = "date(\"2012-12-25\") – date(\"2012-12-24\") = duration(\"P1D\")"

should be this:
const exp = "date(\"2012-12-25\") - date(\"2012-12-24\") = duration(\"P1D\")"

Thanks a ton!!!


Stackage

It would be nice to have taggy in Stackage. I know it's not hard to add to extra-deps but it would still be nice!
The same applies to taggy-lens. Should I open an issue there as well?

No need to open an issue there. I wouldn't mind having those on stackage. I'll take care of this when I get a chance to, in the upcoming days =)

Awesome, thanks!

PR submitted to Stackage: here
Closing the issue. Thanks!


Use static code analysis by Code Climate (free for open source projects)

I've seen this in multiple repositories: https://codeclimate.com/oss/
Would this or similar tools be interesting for this project? It'd be free
Example report for a project that uses Code Climate:
https://codeclimate.com/github/gitlabhq/gitlabhq

Thanks for the suggestion, but I'm going to pass.


Update ORC to 1.7.5

Description
This PR aims to upgrade ORC to version 1.7.5.
ORC 1.7.5 is the latest version of ORC with the following patches:

https://github.com/apache/orc/releases/tag/v1.7.5
https://orc.apache.org/news/2022/06/16/ORC-1.7.5/

This PR has:

[x] been self-reviewed.
[x] added or updated version, license, or notice information in licenses.yaml

For some reason, Travis CI didn't run on this patch. I'll cycle it to get it to run.

It looks identical. Is there another way to make CI happy?

Hmm, I'm not sure why it still won't run. This change seems low risk, though, so I'll merge it anyway. If it causes a problem for some reason we can revert.

Thank you so much, @gianm and @williamhyun ! :)


DRAFT Revert "GEODE-7556: remove membership dependencies on geode-core exeptions"

Reverts apache/geode#4502
These changes seem to have broken the types of exceptions that are thrown when a split brain is detected.

Not needed, @bschuchardt fixed the bug this change introduced.


NIFI-13714 Fix RecordTransform python processor partition handling

Summary
NIFI-13714
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Thanks for finding and addressing this issue @lordgamez. The change looks like the right approach based on the description in the Jira issue, requiring the translation from the Python dictionary to the Java Map.
There is an existing PythonProcessorIT class that exercises the SetRecordField Processor, so it would be helpful to add a new test method to verify the partition handling behavior. Did you consider updating that test class?

Thanks for pointing out the PythonProcessorIT test suite @exceptionfactory, I added a separate test for checking the partitioning in a46024b7a2293ff9c6f21703aafa7fc1d19e334c


[sync] OWL Axiom and MRCM reference set support

@nagyo This PR is going to be merged into your branch (and new PR) that contains all the recently added refset types, right?


Submission_GroupL01_Team21_2213054_2213858_2210147_2212113

MEMBER

Lam Hoang Tan - 2213054 - Leader
Vo Quoc Tu - 2213858
Truong Nguyen Hoang Anh - 2210147
Nguyen Tran Khoa My - 2212113

POLICY DESCRIPTION
Column Generation (policy_id = 1)
Column Generation is an optimization method used to solve large-scale cutting stock problems by iteratively generating new patterns to improve the solution. The algorithm starts by using a set of initial patterns and then solves a linear programming (LP) relaxation of the problem. In each iteration, it solves a pricing problem to generate new patterns that can potentially reduce waste and improve material utilization. By adding these new patterns to the model, the algorithm narrows down the feasible solutions, ultimately arriving at the optimal cutting pattern. Column Generation helps efficiently tackle problems with large numbers of patterns and constraints, making it particularly useful in industries like textiles and manufacturing.
Implement details: None
Genetic Algorithm (policy_id = 2)
The Genetic Algorithm (GA) is a population-based search technique that is applied to solve the cutting stock problem through evolutionary principles. It generates an initial population of candidate solutions, each represented as a chromosome (a set of cutting patterns). Over multiple generations, the algorithm selects the best individuals based on a fitness function that evaluates material utilization and waste reduction. The algorithm then applies crossover and mutation operations to create new candidate solutions. This process is repeated for several generations, improving the solution until a near-optimal cutting pattern is found. The Genetic Algorithm is particularly effective in solving complex and large-scale cutting stock problems where traditional optimization methods may be less efficient.
Implement details: population_size=300, penalty=2, mutation_rate=0.1, MAX_ITERATIONS = 150
RESULT
Here the result when we run the first 100-espisode in this policy with seed = 42:

Policy
Average Filled Ratio
Average Trim Loss
Average Execution Time

Random
0.08
0.4122
29.15 seconds

Greedy
0.0613
0.5325
25.74 seconds

Column
0.1950
0.5694
23.62 seconds

Genetic
0.1374
0.4642
399.07 seconds

v

My old repository have been deleted. How can i do now

I accidentally deleted old repository after closing PR and we couldn't reopen it. This is our new PR. Hope you accept it. We sincerely apologize for this mistake.

Close PR as it does not comply with the submission guidelines.


fix tvOS file 'React/Base/RCTTVRemoteHandler*' included in iOS

Motivation
fix bugs
Test Plan
please look at the code，u will know me.
Release Notes
fix tvOS file 'React/Base/RCTTVRemoteHandler*' included in subspec 'React/Core' iOS
[CATEGORY] [TYPE] [LOCATION] - MESSAGE
[IOS] [BUGFIX] [React.podspec] - fix tvOS file 'React/Base/RCTTVRemoteHandler*' included in subspec 'React/Core' iOS

cc @dlowder-salesforce
Douglas, should we move all AppleTV/TV-specific files to a dedicated folder?

@shergin sorry I didn't answer your earlier question.... moving tvOS-specific files to their own folder is a really good idea.  I'll create an issue to track that.


Enabling allow list approach

Change Description
This PR enables the use of the allow list approach for image redaction and provides a demo notebook.
Issue reference
This PR fixes issue #XX
Checklist

[X] I have reviewed the contribution guidelines
[ ] I have signed the CLA (if required)
[X] My code includes unit tests
[X] All unit tests and lint checks pass locally
[ ] My PR contains documentation updates / additions if required

Will merge from main after PR https://github.com/microsoft/presidio/pull/1113 is complete.

Thanks! looks great. Do you want to keep it in draft until the other PRs are merged and the notebook is updated?

Thank you! Now that PR #1113 is merged in, I'll update the notebook in this PR and publish the PR. Likely sometime today.


error: use of undeclared identifier 'kVK_RightCommand'

Robotgo version (or commit ref): v0.92.1
Go version: go1.15.4 darwin/amd64
Gcc version: Apple clang version 12.0.0 (clang-1<IP_ADDRESS>)
Operating system and bit: macOS Catalina 10.15.7
Resolution: 1440*900
Can you reproduce the bug at :

[x] Yes (provide example code)
[ ] No
[ ] Not relevant

Provide example code:

package main

import (
	"fmt"

	"github.com/go-vgo/robotgo"
)

func main() {
	fmt.Println(robotgo.GetPixelColor(100, 100))
}

module foo

go 1.15

require github.com/go-vgo/robotgo v0.92.1

Description
Hi, when I try to compile the program above I get the following error
Checking for required docker image techknowlogick/xgo:latest... found.
Cross compiling ....
Enabled Go module support
Building /source/go.mod...
Compiling for darwin-10.6/amd64...
# github.com/go-vgo/robotgo
In file included from /go/pkg/mod/github.com/go-vgo/robotgo@v0.92.1/robotgo.go:44:
In file included from ./key/goKey.h:14:
In file included from ./key/keypress_c.h:1:
In file included from ./key/keypress.h:6:
./key/keycode.h:62:12: error: use of undeclared identifier 'kVK_RightCommand'
        K_RMETA = kVK_RightCommand,

It looks like the key kVK_RightCommand does not exists. After a quick search I found this issue which suggests the following change.
I tried the suggested change in a fork, and I successfully compile the same go code above using the following go.mod
module foo

go 1.15

require github.com/go-vgo/robotgo v0.92.1

replace github.com/go-vgo/robotgo v0.92.1 => github.com/krostar/robotgo v0.92.2-0.20201112181729-dde19e3430d6

Checking for required docker image techknowlogick/xgo:latest... found.
Cross compiling ....
Enabled Go module support
Building /source/go.mod...
Compiling for darwin-10.6/amd64...
# github.com/go-vgo/robotgo
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(png.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngread.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngwrite.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngmem.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngget.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngset.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngtrans.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngrtran.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngerror.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngwio.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngrutil.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngwutil.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngwtran.o)) was built for newer OSX version (10.10) than being linked (10.6)
ld: warning: object file (/go/pkg/mod/github.com/krostar/robotgo@v0.92.2-0.20201112181729-dde19e3430d6/cdeps/mac/libpng.a(pngrio.o)) was built for newer OSX version (10.10) than being linked (10.6)
Cleaning up build environment...

./foo-darwin-10.6-amd64
16191f

Do you want to suggest the change I made in my fork in a pull request ?
I hope this issue help
krostar

But I can't reproduce it on my Macos.


Update footer link

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0002%

Covered Lines:
5374

Relevant Lines:
5423

💛  - Coveralls


Hash issue for cpu-z

#530 was closed and that hash is showing as the expected hash, but I'm getting a different hash when trying to install cpu-z
PS C:\Users\staked> scoop install cpu-z
Installing 'cpu-z' (1.80).
cpu-z_1.80-en.zip (2.5 MB) [==================================================================================] 100%
Checking hash of cpu-z_1.80-en.zip... Hash check failed for 'http://download.cpuid.com/cpu-z/cpu-z_1.80-en.zip'.
Expected:
3c2fdb6f79cb2f1a2dac9ace906956b4b9f6f0ff6bb0d5f98ab15f335c0b73ad
Actual:
f92fb1c1fa2c2d8dd581b77d28d8cb53538014eca1e426eb243a63a6fee6619e
PS C:\Users\staked>

Strange, they have already changed it 3 days ago. 😕
Fixed 👍


GDS Admin API: VASP Detail Endpoint

This endpoint provides a mechanism to retrieve the details for a VASP
that are required for the Admin UI - including some computed values and
extra information that are not standard in the pb.VASP record.
Fixes SC-571
TODO:

[x] create endpoint stub in client and server
[ ] define vasp detail record
[ ] implement admin api endpoint

Codecov Report

Merging #101 (18ae82c) into main (49da4e3) will increase coverage by 0.02%.
The diff coverage is 31.81%.

:exclamation: Current head 18ae82c differs from pull request most recent head 784b0ec. Consider uploading reports for the commit 784b0ec to get more accurate results

@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   27.59%   27.61%   +0.02%
==========================================
  Files          31       31
  Lines        3599     3621      +22
==========================================
+ Hits          993     1000       +7
- Misses       2441     2454      +13
- Partials      165      167       +2

Impacted Files
Coverage Δ

pkg/gds/admin.go
0.00% <0.00%> (ø)

pkg/gds/admin/v2/client.go
59.04% <63.63%> (+0.53%)
:arrow_up:

Continue to review full report at Codecov.

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


Disable libzstd support when building llvm (see #32)

Do you want to push a commit reverting the platform disabling so we can test this in CI?

CI run for arm on this branch

Looks good, thanks!


chore: dep bump everything

🛠 Changelog

deps: bump everything that isn't held back / major version.
fix: lock file keeps getting broken with any package change.
deleting and recreating fixes it, but installs latests deps.

🧪 Test plan

Automated: build / lint.
Manual / robot: clicking around (spot testing core functionality).

🎫 Tickets

TILA-####

Merged https://github.com/City-of-Helsinki/tilavarauspalvelu-ui/pull/1378 and https://github.com/City-of-Helsinki/tilavarauspalvelu-ui/pull/1433 into this.


A.36.IR40.etrs89.itrs.crs

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
Testability: refer to note in test case: 'will not be complete without a machine-readable "whitelist" register of the acceptable CRSes with their CRS identifiers and commonly used aliases'

Testing against an agreed list of terms will only test that the term has been used, not that the dataset can be supplied in that CRS.  There should really be a test request using one of the listed CRS.
A white-list of acceptable CRS may help in the testing, but it should be easily updated; as the TG only give recommendations for identifiers. Ideally we would want some sort of  resolver to check that any cited CRS is using ETRS89 for the horizontal component.

I propose to move this issue forward to the implementation phase of the ETS. Therefore I set the label to status:wontfix


exposing missing token claims parameters

Bug fix:

Added missing tenant_region_scope and tenant_region_sub_scope claims from Token Claims

Codecov Report

Merging #5789 (d063fcf) into dev (81d34b4) will increase coverage by 2.44%.
The diff coverage is 70.31%.

Flag
Coverage Δ

msal-angular
96.63% <100.00%> (+0.13%)
:arrow_up:

msal-browser
86.25% <65.76%> (-0.22%)
:arrow_down:

msal-common
?

msal-core
?

msal-node
?

msal-node-extensions
?

msal-react
94.68% <100.00%> (ø)

node-token-validation
?

Impacted Files
Coverage Δ

...ib/msal-browser/src/app/PublicClientApplication.ts
95.19% <ø> (-0.14%)
:arrow_down:

lib/msal-browser/src/error/BrowserAuthError.ts
95.95% <50.00%> (-0.95%)
:arrow_down:

...ser/src/telemetry/BrowserPerformanceMeasurement.ts
77.27% <52.63%> (-19.16%)
:arrow_down:

...-browser/src/telemetry/BrowserPerformanceClient.ts
68.85% <58.33%> (-16.87%)
:arrow_down:

.../src/interaction_client/NativeInteractionClient.ts
75.77% <64.44%> (+6.78%)
:arrow_up:

lib/msal-browser/src/app/ClientApplication.ts
92.51% <75.00%> (-0.06%)
:arrow_down:

lib/msal-angular/src/msal.interceptor.ts
100.00% <100.00%> (ø)

lib/msal-angular/src/packageMetadata.ts
100.00% <100.00%> (ø)

...er/src/broker/nativeBroker/NativeMessageHandler.ts
85.03% <100.00%> (-0.92%)
:arrow_down:

lib/msal-browser/src/internals.ts
100.00% <100.00%> (ø)

... and 2 more

... and 158 files with indirect coverage changes


chore(main): release veto 0.0.1

:robot: I have created a release beep boop
0.0.1 (2024-04-12)
Features

veto: add initial package (c2d360a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/uniform/releases/tag/veto-v0.0.1 :sunflower:


Error in Key Authentication

Code which was working fine till Friday is now throwing error of Key Authentication. Please advise if some maintenance is going ON.

There has been no communication from Breeze team although all users are facing the same issue since saturday

Dear Sushant,
Could you please check now?
If you still encounter any issues, kindly let us know.
[E29CF836]
Thanks & Regards,
Hiten Solanki,
Team Breeze API,
ICICI Securities

From: sushantbisht @.>
Sent: Sunday, December 15, 2024 10:43 AM
To: Idirect-Tech/Breeze-Python-SDK @.>
Cc: Subscribed @.***>
Subject: Re: [Idirect-Tech/Breeze-Python-SDK] Error in Key Authentication (Issue #172)
CAUTION: This email originated from outside the organization! Do not click links, open attachments or reply, unless you recognize the sender's email address! Use 'Report suspicious Email' button in the toolbar to report Phishing mails. Beware!
There has been no communication from Breeze team although all users are facing the same issue since saturday
—
Reply to this email directly, view it on GitHubhttps://github.com/Idirect-Tech/Breeze-Python-SDK/issues/172#issuecomment-2543452307, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3TQZ47SCW5QAVK43SEPQOL2FUFYTAVCNFSM6AAAAABTUFXKBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGQ2TEMZQG4.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
Print this mail only if absolutely necessary. Save Paper. Save Trees." "The information contained in this e-mail and any attachments to this message are intended for the exclusive use of the intended recipient and may contain proprietary, confidential or legally privileged information. If you are not the intended recipient, please note that you are not authorised to disseminate, distribute or copy this e-mail or any parts of it or act upon/rely on the contents of this e-mail in any manner. Please notify the sender immediately by e-mail and destroy all copies of this e-mail and any attachments. Please also note that ICICI Bank or its subsidiaries and associated companies, (collectively "ICICI Group"), are unable to exercise control or ensure the integrity of/over the contents of the information contained in e-mail transmissions and that any views expressed in this e-mail are not endorsed by/binding on the ICICI Group unless the sender does so expressly with due authority of ICICI Group. Before opening any attachments please check them for viruses and defects and please note that ICICI Group accepts no liability or responsibility for any damage caused by any virus that may be transmitted by this email. Any unauthorized use of this email or any attachment(s) may be treated as infringement of right(s) including right of privacy under the applicable laws of India including Information and Technology Act, 2000. Thank you for your cooperation. Regulatory Disclosures are available on https://www.icicisecurities.com (for institutional business) and www.icicidirect.com (for retail business).

It is working now...Thx

Working now...Thx
On Sun, Dec 15, 2024 at 6:02 PM Idirect-Tech @.***>
wrote:

Dear Sushant,
Could you please check now?
If you still encounter any issues, kindly let us know.
[E29CF836]
Thanks & Regards,
Hiten Solanki,
Team Breeze API,
ICICI Securities

From: sushantbisht @.>
Sent: Sunday, December 15, 2024 10:43 AM
To: Idirect-Tech/Breeze-Python-SDK @.>
Cc: Subscribed @.***>
Subject: Re: [Idirect-Tech/Breeze-Python-SDK] Error in Key Authentication
(Issue #172)
CAUTION: This email originated from outside the organization! Do not click
links, open attachments or reply, unless you recognize the sender's email
address! Use 'Report suspicious Email' button in the toolbar to report
Phishing mails. Beware!
There has been no communication from Breeze team although all users are
facing the same issue since saturday
—
Reply to this email directly, view it on GitHub<
https://github.com/Idirect-Tech/Breeze-Python-SDK/issues/172#issuecomment-2543452307>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/A3TQZ47SCW5QAVK43SEPQOL2FUFYTAVCNFSM6AAAAABTUFXKBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGQ2TEMZQG4>.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
Print this mail only if absolutely necessary. Save Paper. Save Trees."
"The information contained in this e-mail and any attachments to this
message are intended for the exclusive use of the intended recipient and
may contain proprietary, confidential or legally privileged information. If
you are not the intended recipient, please note that you are not authorised
to disseminate, distribute or copy this e-mail or any parts of it or act
upon/rely on the contents of this e-mail in any manner. Please notify the
sender immediately by e-mail and destroy all copies of this e-mail and any
attachments. Please also note that ICICI Bank or its subsidiaries and
associated companies, (collectively "ICICI Group"), are unable to exercise
control or ensure the integrity of/over the contents of the information
contained in e-mail transmissions and that any views expressed in this
e-mail are not endorsed by/binding on the ICICI Group unless the sender
does so expressly with due authority of ICICI Group. Before opening any
attachments please check them for viruses and defects and please note that
ICICI Group accepts no liability or responsibility for any damage caused by
any virus that may be transmitted by this email. Any unauthorized use of
this email or any attachment(s) may be treated as infringement of right(s)
including right of privacy under the applicable laws of India including
Information and Technology Act, 2000. Thank you for your cooperation.
Regulatory Disclosures are available on https://www.icicisecurities.com
(for institutional business) and www.icicidirect.com (for retail
business).
—
Reply to this email directly, view it on GitHub
https://github.com/Idirect-Tech/Breeze-Python-SDK/issues/172#issuecomment-2543855522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD4T2PVRMU5CBUXPVO6LTMD2FVZENAVCNFSM6AAAAABTUFXKBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTHA2TKNJSGI
.
You are receiving this because you commented.Message ID:
@.***>


A Saved Variable does not get Stored in a Variable upon Resetting.

Describe the bug
When resetting, the variable's value from saved data doesn't get stored in a variable, even though the game is saved.
To Reproduce
Steps to reproduce the behavior:

Insert a scene
Add a trigger and then add a variable with a value other than 0 (false) in it
Add another trigger with a text box that shows the variable using $
Add an event that'll attach the START button to a script
In said script, add the event, 'Game Data Save'
On the scene init add the event, 'Store Variable from Game Data In Variable', put the variable in both fields
Click on Run
In game, click on the first trigger, it'll set the variable to a value other than 0
Then click on the second trigger, it'll show you the value in the text box
Then press START, it'll save the game
Restart/Reset the game
Click on the second trigger, it'll now show you that the value is 0, even though the variable is saved in the game's data.

Expected behavior
A variable's value from a saved game slot should've been able to be stored in another variable without loading said game slot.
Platform (please complete the following information):

OS: Windows 10 Home V21H1 (OS Build 19043.2006)
App version 3.1.0

Additional context
I want to be able to store a variable's value from a saved data to another variable without having to load it first.

Test this in an external emulator, gbstudio clears saves between builds as save data is build specific (load save game will crash if it's not) and it may clear them between runs.
Make sure the standard load/save game events work first, and then try loading var from game data after a title screen, not sure if you need a "game data exists" check.
Also make sure you're using global variables as local variables may be confusing you (local are per trigger/actor/scene).

I see what I did wrong, I tested it on GB Studio's emulator, which gave me the bug. But, it works fine on an external emulator, thanks!


Define KPIs

The purpose of this issue is to define the first KPIs of every different analytics page for GY Analytics product.
Tasks

[x] Define which pages will be available at first version of GY Analytics.
[x] Define each KPI for each page.

In order for this issue to be closed, all tasks should be completed.

Initial pages

Fall of the Gods
GY Accounts
GYCODING's GitHub


Version history page not highlighting changes

Affected module
UI
Describe the bug
When the datatype of my column changed from string to float in the version history page it seems like I've two columns named timestamp

Got it thanks @Sachin-chaurasiya, also it will not be possible to have two columns of same name!

Happy to help @ulixius9, so, closing this.


ReferenceError: primordials is not defined

After installing the package, I tried running the command parker  spinner.css but I got a reference error. Here is the full message:
fs.js:35
} = primordials;
    ^

ReferenceError: primordials is not defined
    at fs.js:35:5
    at req_ (C:\Users\DELL\AppData\Roaming\nvm\v12.16.1\node_modules\parker\node_modules\natives\index.js:143:24)
    at Object.req [as require] (C:\Users\DELL\AppData\Roaming\nvm\v12.16.1\node_modules\parker\node_modules\natives\index.js:55
:10)
    at Object.<anonymous> (C:\Users\DELL\AppData\Roaming\nvm\v12.16.1\node_modules\parker\node_modules\graceful-fs\fs.js:1:37)
    at Module._compile (internal/modules/cjs/loader.js:1158:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
    at Module.load (internal/modules/cjs/loader.js:1002:32)
    at Function.Module._load (internal/modules/cjs/loader.js:901:14)
    at Module.require (internal/modules/cjs/loader.js:1044:19)
    at require (internal/modules/cjs/helpers.js:77:18)

I have:
node v12.16.1
npm 6.13.4

I'm also having this issue.

Me too has this issue. node.js v.14.17.6.
fs.js:45
} = primordials;
    ^

ReferenceError: primordials is not defined
    at fs.js:45:5
    at req_ (/usr/lib64/node_modules/parker/node_modules/natives/index.js:143:24)
    at Object.req [as require] (/usr/lib64/node_modules/parker/node_modules/natives/index.js:55:10)
    at Object.<anonymous> (/usr/lib64/node_modules/parker/node_modules/graceful-fs/fs.js:1:37)
    at Module._compile (internal/modules/cjs/loader.js:1072:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
    at Module.load (internal/modules/cjs/loader.js:937:32)
    at Function.Module._load (internal/modules/cjs/loader.js:778:12)
    at Module.require (internal/modules/cjs/loader.js:961:19)
    at require (internal/modules/cjs/helpers.js:92:18)

Now I see in /usr/lib64/node_modules/parker/node_modules/graceful-fs/package.json
"version": "3.0.12"
and remember the innocent-looking warning I got from node.js upon installation:
npm install -g parker
npm WARN deprecated<EMAIL_ADDRESS>This module relies on Node.js's internals and will break at some point. Do not use it, and update to<EMAIL_ADDRESS>...

But why didn't node.js do this itself? What is the purpose of offloading dependency tracking to some tool, only to have to track individual version dependencies manually afterwards? I don't get it...

Solution
Since the author did not yet accept the pull request of @dsiddy above, we have to take matters in our own hands... :unamused:
Step 1: Upgrade graceful-fs
npm install -g graceful-fs
+<EMAIL_ADDRESS>added 1 package in 0.349s

Step 2: Rename parker's own old graceful-fs version
mv /usr/lib64/node_modules/parker/node_modules/graceful-fs /usr/lib64/node_modules/parker/node_modules/graceful-fs-3.0.2-deprecated
Step 3: Be happy
:smiley:


Git Update for Template Projects

Summary / 概要
It's something i though about for a while, when using template projects, it probably being updated or maintained from time to time, but as projects are static folders, you can't "update" them.
My use case was to clone the project in my template folder and run a git pull from time to time.
My idea is to see how we could do some kind of updating from within vrc-cli / ALCOM.
Be able to be suggested to update the template project when creating a new project on this template.
I don't know how technically we should do that, if we should store it in a different way, but i felt that could be an interesting additional feature that VCC doesn't have.
Purpose / 目的
This would allow to keep the template projects up to date when someone is actively working on it, or simply to keep the inner dependency up to date.
Additional context / 補足
The use case i have is my NDMF template project where i update the dependencies on the go.
https://github.com/Spokeek/vrchat-ndmf-template-project

It's unlikey to change the template project (except for something like default unity version and corresponding package updates) and it's almost unnecessary I think so I think this feature bring small benefits with big costs.
Could you explain the benefits for updating the project based on the template?

That would be i believe for this reasons:
The project template isn't a feature that is used that much.
And having more convenience for day by day avatar creation is always a plus, so i felt that could have been a direction to go towards to.
From that perspective, i'm mostly thinking of people not being used to avatar or world creation, and if someone creates a template, people may want to have this template evolve, the same way that we have packages that evolve with time.
I may be thinking too much ahead and planning a usage that isn't relevant yet, but that's what i had in mind.
The same way, having a system integrated to the project manager (ALCOM) would avoid the need to manually ensure that your project is up to date as it would notify you when it needs to.
My third point was to maybe add some additional feature that could improve the workflow of people that isn't available in the vcc tool and adds additional value to vrc-get/ALCOM

You can add your template as a project to VCC/ALCOM and directly update it. Templates are nothing more than finished projects that get copied over, really.
Meaning, you can update a template the same way as you would update existing projects.
If there was going to be an implementation for template updates, you would just trigger an "update all" of that template project and that would be it pretty much.

You can add your template as a project to VCC/ALCOM and directly update it. Templates are nothing more than finished projects that get copied over, really.

This is true and that's what i do for updating my template, but i was more thinking on the user perspective side.
They (probably) don't want to have to update their template manually by opening them.

Fair.
If we talk about a user facing feature though, we would also need full template management inside the GUI.
Just automatically updating on creation is not necessarily a good idea, we don't know if they got specific versions of packages in the template for a reason. And adding that to the creation flow sounds like a UI/UX headache to me, but maybe you got a good idea to make that work, without overwhelming people with niche options.
Templates are, even in VCC, treated more as a power user feature at this time.
I do like the Idea of a template manager though, that would be neat to have.

That's mostly why i made this as a discussion start point. There is probably a lot of edge case on how to approach the thing, but wanted to see if that was worth exploring.

I'm also thinking about making the template feature more useful. (in #602 )
The intent of this(602) issue is to make it easier to create user-made templates. For more advanced users, the ability to specify version ranges with Semver is also envisioned.
It would be good to be able to edit the created templates later, so this is exactly the “template manager” we are thinking of (maybe?).
And finally, import/export via zip would make it very easy to share templates.

i'm closing this as that was more a discussion to have.
So i did, come discuss here for more on that topic
https://github.com/vrc-get/vrc-get/discussions/1512


Add yarn

Yarn helps new contributors to get started more easily as it locks down the dependencies (not for the lib, but for the development). Here a detailed article: https://yarnpkg.com/blog/2016/11/24/lockfiles-for-all

Current coverage is 100% (diff: 100%)

Merging #51 into master will not change coverage

@@           master   #51   diff @@
===================================
  Files          11    11
  Lines          30    30
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           30    30
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update f210866...babcade


MSC2403: Add "knock" feature

Rendered
Soru is also interested in providing implementations in both synapse and riot-web for this, however, as her workload is currently rather high so the development progress would likely be slowly.
Signed-off-by: Sorunome<EMAIL_ADDRESS>Synapse PR
Shepherd: @anoadragon453

Gives me Habbo vibes...

@turt2live

why not the invite power level?

(github doesn't allow to reply to that conversation)
because invite and knock are two different features so you can easily think of scenarios where you want different PLs for those features

Everyone: I've been assigned as Spec Core Team member to shepherd this MSC and help get it through.

I've created a sequence diagram of the flow, including the proposed CS stuff from @turt2live. Should hopefully help others wrap their head around things (it definitely helped me writing it).

I've updated the sequence diagram (new link) to note that the CS endpoints will only return after a knock succeeded or failed, and updated how the client was informed on knock progress.

btw: this needs a section saying where the API endpoints will live during development.

I think I've covered all of the things you've asked for @richvdh, and would love another look over :innocent:

Are there any concerns given rooms with this mode toggled on, will see lots of state events with keys relating to users not part of the room, which could lead to a performance impact on the servers taking part in that room?
While I'm not a state-res expert, I think that special attention is taken to membership events of type "ban" sent by room admins as they control who is allowed to send further events to the room, and so these bans of users who have never joined the room will need to accumulate forever.
The traditional method of managing a invite only room where you use a website or similar doesn't accumulate these failed joins, as they're effectively kept outside of the room of interest, so keeping the room state clear of temporary information.

Are there any concerns given rooms with this mode toggled on, will see lots of state events with keys relating to users not part of the room, which could lead to a performance impact on the servers taking part in that room?

Unfortunately even preventing users from rescinding their knocks won't eliminate this attack vector, and an attacker could create infinite users/servers.
I would say that this is the same problem a public room faces with joins, but @turt2live makes a good point in that:

it's worth mentioning that this attack is easier with knocks than it is with join/leave cycles, as joining often takes effort while knocking doesn't.

One interesting idea off the top of my head that could be explored is requiring a certain amount of time to pass before a server will accept another knock attempt. While yes, accurate time doesn't really exist in a federation, even rough time could be useful here.
It's not a be-all end-all solution, but I'm open to ideas on a better one!

This MSC has been sitting around the same generally agreed upon state for a good long while now. I think it's ready to go:
@mscbot fcp merge

I like the concept this MXC brings up, however I have two big issues that remain unaddressed in it's current form.
Firstly is state spam. This is currently only a concern for public rooms and rooms with invite being accessible to normal users. Adding knock provides a false sense of protection to a knock room, as there are already numerous scripts that can be used to spam-join a room by abusing homeservers without adequate registration requirements. This does nothing to protect against that, and citing this as a "known issue" doesn't fix the problem
Secondly is state pollution/state bloating. i.e: rooms having so many states that it begins to lock out clients that can't handle large amounts. knock doesn't address this either, external users can still manipulate room state.
Users who are not participating in a room should not be able to directly manipulate it, like knock currently allows them to.

On synapse lazy_loading_members don't give all membership state events at once, maybe that can be applied here? ("Don't load knock memberships older than a day, unless explicitly requested.")

On synapse lazy_loading_members don't give all membership state events at once, maybe that can be applied here? ("Don't load knock memberships older than a day, unless explicitly requested.")

It's also possible that knock requests then shouldn't be visible for users that cannot accept them

That's a client solution to a to be server problem. Ignoring the states client-side doesn't help homeservers with low complexity values, which could be locked out of rooms if they're knock-spammed enough

The first issue can be addressed (e.g. if a certain domain starts spamming the room with knock requests) with ACL lists

ACL banning entire servers is not a solution. Once you ACL one server, they'll just use another.

The other solution is to expire "knock" events, then, but that can be problematic due to people "refreshing" them.

The best solution would probably be to keep knocks behind a designated endpoint, similar to how other platforms do. That however isn't a very "matrixy" solution though.
Several matrix communities already use secondary or "vetting" rooms to alleviate spam in the "actual" room. Maybe knock requests could be directed into to another room, and clients would /peek into it to view knock information.

@kakolisgay @ShadowJonathan PLEASE use threads for comments on MSCs!


Update push_evaluations_to_hub.py

Fixes wrong naming in script that adds git tags to spaces.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Offer special programming blocks "debug" and "assert" to the end user

We have already two blocks which are hidden for the user "debug" and "assert". And soon "eval".

We should offer them for every supported system, e.g. in a new category in the advanced toolbox.
Currently they are only available with a special key combination.

Nice name for the category wanted!

"miscellaneous", "code analysis", "code quality"

won't fix


Add feature: override role name displayed to end user from config option

This patch adds a configuration option which will let end users arbitrarily override the role displayed to end users from the config option
overrideRoleNameDisplay
This allows to hide a moderator with a hitched role which is unsuitable to be displayed to end users. In our case, specifically a hidden moderator with a general user role. Not able to use fallbackRoleName, because the hidden moderator has a hitched role.
I have not coded in a very long time, and never in JS before, so rusty doesn't even begin to cover it. Thoughts/rejection/comments/patches appreciated :)
I've tested this patch on our server, and it appears to work okay, but have not tested all existing functions exhaustively

TODO:

Verify fallback works when override not in effect
Document option in configuration.md

Fallback still works whilst override not enabled, configuration option documented

This looks good, thank you for the PR!


no explanation for "FormAssembly.com" in Normal forms section

Hello
Actually, it is not a big deal, just some formatting. There is no description for FormAssembly in Normal Forms section.

I went to look for who had introduced that line, and turns out it was @agarrharr himself in a7c016273 😄
@Nikronic what would you suggest as a description for that link?

Awesome but expensive forms!
Actually, I am not a web developer, so I do not know what should be highlighted in the description.

From the text in the website, and after removing a ton of marketing speak, I came up with the following description using their words:

a web form creation and integration solution for enterprises, including integration with Salesforce.

How does this sound, @Nikronic / @agarrharr?
(Personally, I'm not sure they qualify as awesome, but that's a judgment I'll leave @agarrharr to make.)

@Nikronic why did you close this?

Because adding a simple description does not take two month. And after all, I opened this issue in 1 Novemeber for the first time and I closed issue a week ago because I thought this repository no longer maintenance. And exactly after I closed issue, the owner opened it again! WTF!
And now I am sure.


Dropdown error: Error: javascript:; is not an HTML Element

Hi everyone,
I have recently decided to migrate my project in materialize 1.0.0 (before it was in materialize v0.100.2).
I have read and apply the migration documentation from materialize official github repository : https://github.com/Dogfalo/materialize/blob/v1-dev/v1-changelog.md
In the user point of view it's seem to be ok, but I have an error in my web développement console: "Error: javascript:; is not an HTML Element"

My HTML code is :

            ICON

                    LABEL

And my javascript trigger is :
$(document).ready(function(){
            let dropdownTrigger = document.querySelectorAll('.dropdown-trigger');

            M.Dropdown.init(dropdownTrigger, {
                inDuration: 300,
                outDuration: 225,
                constrainWidth: false, // Does not change width of dropdown to that of the activator
                hover: true, // Activate on hover
                gutter: 0, // Spacing from edge
                belowOrigin: false, // Displays dropdown below the button
                alignment: 'left', // Displays dropdown with edge aligned to the left of button
                stopPropagation: false // Stops event propagation
            });
});

So, functionally it's ok, it's works, but I want understand why I have this error and fix it !
Thanks by advance for your help.
Best regards.

Please change your href in your a-tag to href='#' and try it out again
https://materializecss.com/dropdown.html

Please change your href in your a-tag to href='#' and try it out again
https://materializecss.com/dropdown.html

Hi Maqsyo,
Thanks for your response.
I have try this, but have the same error : Error: # is not an HTML Element.
I have also try to remove the href and I have again the same error : Error:  is not an HTML Element.
I don't understand the error !
If you have another idea, I'll take it :).

oh yeah.. i made a codepen and could figure it out really fast
https://codepen.io/anon/pen/zVVdxb?editors=1010
data-target="mytarget" has to be the id of your dropdown
so it should be data-target="ID"

You are using the init on the array and not the HTML element

Hi all,
Thanks for your responses, but I again the problem.
I think it's caused by "dropdown" because I have a similar error when I call : M.FormSelect.init(elems, options);  and my select doesn't work. The first option is displayed, but when a click on it, the dropdown options is not display :/.
Have you a similar issue ?

Hello,
I found my problem. I had a js/css conflict with an other lib called "Rapael.js".


Dev Server does not always show webpack config compilation errors

Describe the bug
React dev server not consistently showing webpack configuration errors.
cra's default webpack config doesn't cause any problems.
You can reproduce this problem by customizing your webpack config via tools like react-app-rewired.
This issue is 100% reproducible.
Did you try recovering your dependencies?
It happens in the latest version.
Which terms did you search for in User Guide?
This is a problem that does not show an error message, so I think it has nothing to do with the user guide.
The words I searched for are:

show only 'Starting the development server...' and not execute
pending compile when execute npm start

Environment
current version of create-react-app: 5.0.0
running from /Users/peter.lee/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app
System:
OS: macOS 12.0.1
CPU: (10) arm64 Apple M1 Pro
Binaries:
Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
Yarn: 1.22.17 - /opt/homebrew/bin/yarn
npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
Browsers:
Chrome: 98.0.4758.102
Edge: Not Found
Firefox: Not Found
Safari: 15.1
npmPackages:
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
react-scripts: ^5.0.0 => 5.0.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

Create a basic CRA project

$ npx create-react-app test-app

Customize webpack config to build multiple entries and html

install other packages

<EMAIL_ADDRESS><EMAIL_ADDRESS>

Create separate entry js and html files

Configure config-overrides.js (root path)

const path = require("path");
const { override } = require("customize-cra");
const HtmlWebpackPlugin = require("html-webpack-plugin");

const isEnvProduction = process.env.NODE_ENV === "production";

module.exports = {
  webpack: override(function (config) {
    config.entry = {
      main: path.resolve(__dirname, "src/index.js"),
      second: path.resolve(__dirname, "src/second.js"),
    };

    const htmlWebpackPlugin = config.plugins.find(
      (element) => element.constructor.name === "HtmlWebpackPlugin"
    );

    htmlWebpackPlugin.userOptions.chunks = ["main"];

    config.plugins.push(
      new HtmlWebpackPlugin({
        template: path.resolve(__dirname, "public/second.html"),
        filename: "second.html",
        chunks: ["second"],
        minify: isEnvProduction,
      })
    );

    return config;
  }),
};

Modify npm script in packages.json

  "scripts": {
    "start": "react-app-rewired start",
    "build": "react-app-rewired build",
    "test": "react-app-rewired test",
    "eject": "react-app-rewired eject"
  },

$ npm run start

Expected behavior
If it does not run normally, an error should be displayed on the console.
Actual behavior
No error occurs, only the following message is exposed and does not run normally

Reproducible demo
It can be easily reproduced with the reproduction steps described above.
additional clarification (Important)
Not running is normal. (I wrote the code wrong.)
However, the problem is that there is no hint (error message) as to why it was not executed.
I debugged react-scripts in the following way and found the cause of the project not running.
The cause is that the webpack config.output.filename property was not a value for configuration for multiple entries when in development mode.
Debugging was performed by additionally performing the following steps.

Set the failed hook of webpack compiler inside the createCompiler function of node_modules/react-dev-utils/WebpackDevServerUtils.js to expose an error message when compilation fails.

compiler.hooks.failed.tap('failed', async stats => {
    console.log(chalk.red('Failed to compile.\n'));
    console.log(stats)
});

$ npm run start
Check the error message

Modify output.filename of webpack config for multiple chunks (config-overrides.js)

const path = require("path");
const { override } = require("customize-cra");
const HtmlWebpackPlugin = require("html-webpack-plugin");

const isEnvProduction = process.env.NODE_ENV === "production";

module.exports = {
  webpack: override(function (config) {
    config.entry = {
      main: path.resolve(__dirname, "src/index.js"),
      second: path.resolve(__dirname, "src/second.js"),
    };

    const htmlWebpackPlugin = config.plugins.find(
      (element) => element.constructor.name === "HtmlWebpackPlugin"
    );

    htmlWebpackPlugin.userOptions.chunks = ["main"];

	// !!! Update !!!
    if (!isEnvProduction) {
      config.output.filename = "static/js/[name].bundle.js";
    }

    config.plugins.push(
      new HtmlWebpackPlugin({
        template: path.resolve(__dirname, "public/second.html"),
        filename: "second.html",
        chunks: ["second"],
        minify: isEnvProduction,
      })
    );

    return config;
  }),
};

$ npm run start
Check output in console

I've been suffering for months with the same problem. It was previously sorted by simply disabling linting for the dev environment, however, after upgrading to react-scripts 5.0.1 this was a problem again which disabling linting did not fix. With these suggestions, I was also to pinpoint the error to start fixing it.


Time Series Product Sales Analysis and Forecasting

Project Request
This project focuses on analyzing and forecasting the sales of a product over time using time series analysis techniques. The dataset used in this project contains monthly sales data of a product. The goal is to build a predictive model that can forecast future sales based on historical patterns.

Field
Description

About
Time Series Product Sales Analysis and Forecasting

Github
ayush-09

Email
<EMAIL_ADDRESS>

Label
Project Request

Define You

[x] GSSOC Participant
[x] Contributor

Time Series Product Sales Analysis and Forecasting

Description

This project focuses on analyzing and forecasting the sales of a product over time using time series analysis techniques. The dataset used in this project contains monthly sales data of a product. The goal is to build a predictive model that can forecast future sales based on historical patterns.
Scope
The scope of this project includes the following steps:
Data Cleaning: Clean the provided dataset by renaming columns, removing unnecessary rows, and converting the "Month" column to a datetime format.
Data Visualization: Visualize the cleaned data to understand the sales patterns and identify any seasonality or trends.
Testing for Stationarity: Test the stationarity of the sales data using the Augmented Dickey-Fuller (ADF) test. Apply differencing if the data is non-stationary to make it stationary.
Differencing: Perform differencing on the sales data to remove any trend or seasonality components and make the data stationary.
Autocorrelation and Partial Autocorrelation Analysis: Use autocorrelation and partial autocorrelation plots to determine the order of the AutoRegressive Integrated Moving Average (ARIMA) model.
Model Building: Build an ARIMA model based on the identified order. Train the model using the historical sales data.
Model Evaluation: Evaluate the ARIMA model using various statistical measures to assess its performance and goodness of fit.
Forecasting: Use the trained ARIMA model to make future sales predictions. Visualize the forecasted sales values alongside the actual sales data.
Timeline
One week after get assigned

@adithya-s-k Please assign this to me


Allow attachments for integration types, e.g. for storing an integrat…

…ion logo.

Can one of the admins verify this patch?


Allow use of password (as in a11) in console login

Starting in a11, telnet console is password protected.

This would be resolved by #4 :)


Binary Matrix

Need a clean truth table with any given number of variables.
When it is given x variables, it displays a matrix with x columns having alternating T(rue) or F(alse) entries.

This feature was already completed in another issue.

This branch can be deleted and closed.


QA| Warrents pdf related changes

1728298161357AdMueJZmJo.pdf
Uploading<PHONE_NUMBER>795rqGcxOHIdA.pdf…

Hi @Ajith-beehyv  Please do the dev testing and confirm

Hi @rajeshcherukumalli  can you please retest this Issue

Hi @Ajith-beehyv, please look on this, these changes we need to change __
1728378899170HfBueHlcQA.pdf

@kashish384

executor name is not available
depending no of sureties judge selected we print with one surety in the sum of rupees or two sureties
hearing date not getting from UI
in sample pdf signature and seal of court are there

https://docs.google.com/document/d/1WwJBOxotx6jwSaNT_iPgrQjiohLYdZoRDraZlZzwhgs/edit

@vaibhavct , please look on this.

Executor name _missing
1728551980017jzfMCYBBVP.pdf

still a issue.
1729679811741dtogWgffDi.pdf

We already have another ticket for related issue, so I'm closing this ticket.
reference:
#1981


New action request: docker/build-push-action

Action name
uses: docker/build-push-action
Reasons
No response
Intended usage
No response
I have checked the internal marketplace for similar actions and couldn't find one that works for us.

[X] I have checked the internal marketplace first

:robot: Found these results:

Check
Results
Links

CodeQL on the forked repo
:x:
CodeQL run

Security scan:

Check
Result

No Dependabot configuration found
⛔

No CodeQL Init found
⛔

No CodeQL Analyze found
⛔


Added format mistake

@zaru238, looks good. Your checker worked as expected. Please close this PR.


feat(client): add navigation

What is the scope of the feature?
client
Description
This proposes the addition of a navigation bar on the site. It would allow users to switch between pages.
Proposed solution
Since the navigation is present on the pages, use an Astro component.

This was implemented