Java CoreDump on Execution

Hi,
I tried to install the controller software on my firewall. Unfortunately, I receive a segfault on startup. For a more detailed error message, I startet the unify controller software directly from console. Error message is shown below:
# /usr/local/bin/java -jar /usr/local/UniFi/lib/ace.jar start
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000003c9ab02b0c0, pid=17994, tid=0x000000000001878e
#
# JRE version: OpenJDK Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11)
# Java VM: OpenJDK 64-Bit Server VM (25.131-b11 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# J 378 C1 java.net.URLClassLoader$1.run()Ljava/lang/Object; (5 bytes) @ 0x000003c9ab02b0c0 [0x000003c9ab02b080+0x40]
#
# Core dump written. Default location: /usr/local/etc/rc.d/java.core
#
# An error report file with more information is saved as:
# /usr/local/etc/rc.d/hs_err_pid17994.log
AHE@0x000003c9aa65b030: 0xb0000000 i2c: 0x000003c9aae88ae0 c2i: 0x000003c9aae88b43 c2iUV: 0x000003c9aae88b04
Compiled method (c1)    3449  378       3       java.net.URLClassLoader$1::run (5 bytes)
 total in heap  [0x000003c9ab02af10,0x000003c9ab02b2b8] = 936
 relocation     [0x000003c9ab02b038,0x000003c9ab02b070] = 56
 main code      [0x000003c9ab02b080,0x000003c9ab02b1a0] = 288
 stub code      [0x000003c9ab02b1a0,0x000003c9ab02b248] = 168
 metadata       [0x000003c9ab02b248,0x000003c9ab02b258] = 16
 scopes data    [0x000003c9ab02b258,0x000003c9ab02b270] = 24
 scopes pcs     [0x000003c9ab02b270,0x000003c9ab02b2b0] = 64
 dependencies   [0x000003c9ab02b2b0,0x000003c9ab02b2b8] = 8
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Abort (core dumped)

Any suggestions?
Thanks,
Xatru

What version pfsense?

Stale issue closing.


Any more examples?

Hello,
I recently came across this project and was wondering if you had any more examples that might use some of the other finctions?
fs.GlobFS
fs.ReadDirFS  as well as to how you fs.WriteDirFS
fs.StatFS
fs.SubFS
I am also particularly interested in reading/writing directories and putting files within those directories as wells as getting statfs on the filesystem total, fora directory, and file so that I can learn how it is done.
Thanks

Hey @lonnietc - you can find some examples of those in the tests - hopefully this is what you're after: https://github.com/liamg/memoryfs/blob/master/fs_test.go


Fix project manager display at small window sizes (3.x)

3.x version of https://github.com/godotengine/godot/pull/61211.

Don't use minimum size for project order/filter controls. This also allows the filter field to become longer at large window sizes.
Hide the loading label instead of changing its opacity. This causes a reflow during loading, but this is preferable to having the UI overflow.
Hide the About button on Android as it will spawn a dialog that's too large to be closed on most screens.
Hide the language dropdown on Android as it doesn't work correctly.

This allows the project manager to be displayed correctly at much lower window sizes than previously.
This partially addresses https://github.com/godotengine/godot/issues/60728. Further changes need to be made to the editor itself to reduce cases of UI elements overlapping (including preventing access to the About dialog within the editor).

#61215 is not trivial to cherry-pick due to some changes in the UI code for the project manager. Since it's related to this PR, maybe you can include it here as a first cherry-pick commit and then your further changes, so the whole can be tested together?

#61215 is not trivial to cherry-pick due to some changes in the UI code for the project manager. Since it's related to this PR, maybe you can include it here as a first cherry-pick commit and then your further changes, so the whole can be tested together?

Done.
@aaronfranke I noticed that the number of asset library columns is not set when switching tabs for the first time. This means that if you resize your window to a very small size then switch to the Asset Library tab, you will still see 2 columns instead of 1.

Thanks!


fix: Replace Collections method to native

This method checks node is in voiceClient and deletes it with Collection native method.
This PR also fixes error HTTPException: 404.

VC === this doesn't work sometimes. Current VoiceClient and VoiceClient inside Collection are sometimes different.
If stop() have to check it's same, Can I use id property to check it's same?


Fix: Handles incorrectly sanitized camelCase SVG attributes

Attempts to fix issue #483.

Closing as prettier added unwanted formatting.


gitea: add sqlite_unlock_notify build tag

Motivation for this change
Fix #109004
When building Gitea with sqlite support the sqlite_unlock_notify tag must also be added otherwise there will be frequent error reports of database is locked.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This should be applied to 20.09 as well.

This should be applied to 20.09 as well.

Already on it.

Already on it.

Ported to stable as ac88b3011d48388dd86454086e3b059fd659e8af.

Ported to stable as ac88b3011d48388dd86454086e3b059fd659e8af.


Plugin overwrites entrypoints

Kaniko image has entrypoint /kaniko/executor, see https://github.com/GoogleContainerTools/kaniko/blob/main/deploy/Dockerfile#L100
but:
- label: builder
    plugins:
      - kubernetes:
          podSpec:
            containers:
              - image: gcr.io/kaniko-project/executor:debug
                args:
                  - "--context=/workspace/[...removed...]"
                  - "--dockerfile=Dockerfile"
                  - "--destination=my-image"

gets me:
trap 'kill -- $$' INT TERM QUIT; --context=/workspace/[...removed...] --dockerfile=Dockerfile --destination=my-image
/bin/sh: --context=/workspace/[...removed...]: not found

this works:
- label: builder
    plugins:
      - kubernetes:
          podSpec:
            containers:
              - image: gcr.io/kaniko-project/executor:debug
                command: [/kaniko/executor]
                args:
                  - "--context=/workspace/[...removed...]"
                  - "--dockerfile=Dockerfile"
                  - "--destination=my-image"

Again, this should at the very least be documented.

Hi @c2h5oh,
The README says:

...

modifying the user-specified containers to:

overwrite the entrypoint to the agent binary
run with the working directory set to the workspace
The entrypoint rewriting and ordering logic is heavily inspired by the approach used in Tekton.

The entrypoint needs to be the Buildkite Agent, so that there is an agent to runs the command for the job.
The examples in the README also show kubernetes > podSpec > containers > command being used to provide the command for the agent to run.


policy/v1beta1 PodDisruptionBudget resources not reported

We used kubepug to scan our cluster before upgrading from K8S v1.24.6 to v1.25.6.
It didn't catch our policy/v1beta1/PodDisruptionBudget usages. Apparently because K8S already migrated these objects internally? (Is this behavior documented somehwere?)
#92 and the fix #96 seems to be about the same issue, but it apparently didn't take for our case.
I re-verified using kubectl apply on a v1.24.6 cluster, a v1beta1 PDB is then returned as v1, but maybe it also just looks that way because the client uses the v1 API to fetch them?
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration:
       {"apiVersion":"policy/v1beta1","kind":"PodDisruptionBudget","metadata":{"annotations":{},"name":"irrelevant-rabbitmq-temp","namespace":"irrelevant"},"spec":{"minAvailable":1,"selector":{"matchLabels":{"app.kub │
│ ernetes.io/instance":"irrelevant","app.kubernetes.io/name":"rabbitmq"}}}}
...

Of course, when using Helm, the annotation showing v1beta1 wouldn't be there.
GitVersion:    v1.4.0
GitCommit:     4de32d695b27c52c16d4a801b613b78e45e28ca9
GitTreeState:  clean
BuildDate:     2022-08-21T18:25:40
GoVersion:     go1.18.5

Hi @alshain, that's right.
What happens is that Kubernetes defines a preferred API version per release, and from v1.24.6 to v1.25.6 the preferred version for PDB may have changed from v1beta1 to v1.
I need to double check if this means that the etcd storage also got updated when you migrated, or if it still points to the old v1beta1 but re-touches to v1.
We don't have a way to define how the object is persisted on the database, to see if it was migrated during the upgrade or not. Anyway, I'm double checking here if I can get some field/indicative of how the object was persisted

@alshain I have confirmed with some folks here once you migrate your k8s version, the APIs are also updated. The idea of raising an alert on deprecation in Kubepug is if you are planning to do a jump migration (from v1.19 to v1.24 for instance) you may not have the API converted :)
I'm closing this, but feel free to re-open or reach me on Kubernetes Slack, thanks for using the project!


ft: enable aws backend object copy w/ versioning

PR has been updated. Reviewers, please be cautious.

@ironman-machine try

Hello @electrachong
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/16110' with the following env. args:
{
    "SCALITY_INTEGRATION_BRANCH": "ultron/master",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "master",
    "SCALITY_S3_BRANCH": "ft/aws-backend-versioning-copy"
}

end to end passed


Metadata Editor and Widget Bug Fixes

Various Bug Fixes as a followup to #591

Fixed required validation in MetadataEditor. Update to strict
equality check cause the undefined case to no longer be caught
by the null check
Text updates to RuntimesWidget to clarify rutime type and api url
Fixed support for RuntimeWidget when no runtimes are configured
Focus on Name field when opening a Metadata Editor tab
Update pipeline submission success dialog to use display_name

Fixes #798
Fixes #802
Fixes #806
Fixes #814
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

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

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

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

@ajbozart just noticed a regression. The tool tip used to be correct.

Pushed an update that addressed the following issues @ptitzler raised:

Focus on Name field when opening a Metadata Editor (including switching between tabs)
Fixed race condition causing Create new undefined tooltip
Fixed #814

Tried locally and it worked as expected for all of the issues mentioned. LGTM


Made a minor docs syntax fix.

These two things weren't showing up properly on the docs.

Thanks! No need to wait for the CI, this is documentation only.


The stream api suddenly disconnected and no exception was caught

After the program has been running on the server for a period of time, suddenly no data can be monitored!

The following error occurred 80 minutes before the program was disconnected:

The following error occurred 80 minutes before the program was disconnected:

Have this error been resolved?

Get the same error with u. Cant get any log


[Typo] Fix (in Django/Conf/global_settings.py)

situations -> possible scenarios

This is incorrect grammar. The sentence reads fine to me as is.


gchromVAR installation

Dear Caleb,Thank you very much for the help. I add the line for colname and it worked! so I am in the step of importbedscore. It said there is no function of importbedscore so I tried to install the package again and it gave me this error. Any other way to install it? Thank you !

devtools::install_github("caleblareau/gchromVAR")
Downloading GitHub repo caleblareau/gchromVAR@master
Skipping 1 packages not available: chromVARmotifs
Installing 3 packages: chromVARmotifs, motifmatchr, RSQLite
Installing packages into ‘C:/Users/rsong/Documents/R/win-library/3.5’
(as ‘lib’ is unspecified)
Error: Failed to install 'gchromVAR' from GitHub:
(converted from warning) package ‘chromVARmotifs’ is not available (for R version 3.5.1)

I tried different computer and it installed gchromVAR nicely! Thank you.

Hi @Renfang2019,
Out of curiosity, did you switch to OSX or Linux?
Jacob

Yes, I used the Windows yesterday and I tried on apple today.
Dr. Renfang Song Taylor
Assistant Professor
Department of Biology
College of Science and Mathematics
SOUTHWEST BAPTIST UNIVERSITY
1600 University Ave. | Bolivar MO 65613
Room: Wheeler Science Center 114D
OFFICE<PHONE_NUMBER>
rtaylor<EMAIL_ADDRESS>Follow us: Facebookhttps://www.facebook.com/SBUniv | Twitterhttp://www.twitter.com/SBUniv | Instagram[cid:0379be4a-e2eb-4685-943c-ba439fe5223c]http://www.instagram.com/sbuniv
Proverbs 2:10-11.For wisdom will enter your heart, and knowledge will be pleasant to your soul. and understanding will guard you.  箴言2：10-11智 慧 必 入 你 心 ． 你 的 靈 要 以 知 識 為 美 . 謀 略 必 護 衛 你 ． 聰 明 必 保 守 你

From: Jacob Ulirsch<EMAIL_ADDRESS>Sent: Thursday, July 25, 2019 6:32 AM
To: caleblareau/gchromVAR<EMAIL_ADDRESS>Cc: Renfang Taylor<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [caleblareau/gchromVAR] gchromVAR installation (#6)
Hi @Renfang2019https://github.com/Renfang2019,
Out of curiosity, did you switch to OSX or Linux?
Jacob
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/caleblareau/gchromVAR/issues/6?email_source=notifications&email_token=AMMOBOTZKO36R4OXEXDHPGTQBHWUBA5CNFSM4IGSUS42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD22MFCA#issuecomment-515162760, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMMOBOTKH3WTIS4YAU5WOVDQBHWUBANCNFSM4IGSUS4Q.


Fix issue with STM32duino Core and I2C address setting

Hi all,
here you can find the fix to make the library working also with STM32duino Core and also to fix the I2C address management. Best Regards,
Carlo

Now that there is a separate library for stm32duino, I am closing this issue.

Now that there is a separate library for stm32duino, I am closing this issue.

Hi @simondlevy
I think you should consider this even if we provide on our side an other library. Moreover, it provides some fixes I guess which would be useful.


Make parameters changeable in python layer w/o having to re-call Configure

See https://github.com/edwenger/emodlib/commit/fcf79c21886292ea35b0b59fb8ab2928ee95b518 for explicit handling of set_params + update_params (with C++ static parameters re-configured as needed).
However, one could imagine wanting to make this one level more transparent -- for example, rather than IntrahostComponent.set_params(dict(key=value)) something just like IntrahostComponent.params['key'] = value.


[#1165] improvement(tez): Unregister shuffle data after completing the execution of a DAG.

What changes were proposed in this pull request?
Generally, one application will execute multiple DAGs, and there is no correlation between the DAGs. Therefore, after completing the execution of a DAG, you can unregister the relevant shuffle data. Otherwise, when there are many DAGs, an application will occupy a large amount of resources for a long period of time.
Why are the changes needed?
Fix: https://github.com/apache/incubator-uniffle/issues/1165
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing test cases.

@zhengchenyu  Could you help me review this pr?

Codecov Report

Merging #1166 (c670049) into master (680b4ea) will increase coverage by 1.74%.
Report is 4 commits behind head on master.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1166      +/-   ##
============================================
+ Coverage     53.63%   55.37%   +1.74%
+ Complexity     2576     2256     -320
============================================
  Files           391      336      -55
  Lines         22359    15603    -6756
  Branches       1875     1404     -471
============================================
- Hits          11992     8640    -3352
+ Misses         9660     6506    -3154
+ Partials        707      457     -250

see 58 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@jerqi @zhengchenyu hi, could you review for my PR? thanks!


Added Python 3.7 to Travis

Coverage decreased (-1.5%) to 78.956% when pulling 40f149119e4752c9692da50e855885b1fc49eddf on expobrain:travis_py37 into 98486a43adb257b46af952e4d0e18ced5b25808d on Toblerity:maint-1.6.

Coverage decreased (-1.5%) to 78.956% when pulling 40f149119e4752c9692da50e855885b1fc49eddf on expobrain:travis_py37 into 98486a43adb257b46af952e4d0e18ced5b25808d on Toblerity:maint-1.6.

@expobrain Adding Python 3.7 to Travis is a good idea. However the .travis.yaml has changed quite a bit since the copy in maint-1.6. Can you open another PR with the change against master?
https://github.com/Toblerity/Shapely/blob/master/.travis.yml

@snorfalorpagus sure! Give some time to check out master and update the configuration


Rename "schema" + "data" tests

For v0.20.0, we want to make tests more powerful and (crucially) much more consistent. Today, there are real functional differences between "schema" tests and "data" tests. Instead, tests should just be tests. They'll still have two points of entry, but this should reflect only the dbt developer's choices to trade off clarity and reusability.
As such, we're thinking about renaming:

schema test → generic test

alternatives: "macro test," "reusable test"

data test → ~bespoke test~ singular test

alternatives: "file test," "one-off test"

This renaming has real implications for:

Internal objects (e.g. ParsedDataTestNode, ParsedSchemTestNode). This shouldn't have any implications for end users.
File names, e.g. builtin generic tests are defined in global_project/macros/schema_tests/. This is cosmetic only.
Resource FQNs + output of dbt ls. (Today, the unique_id is test.my_project.unique_model_a_fun, but the fqn is my_project.schema_test.unique_model_a_fun.)
Selection criteria: this represents a functional change, so I'll say more below

Selection criteria

dbt test --data, dbt test -m test_type:data
dbt test --schema, dbt test -m test_type:schema

Should instead become:

dbt test -m test_type:singular
dbt test -m test_type:generic

Notes:

We should make this backward compatible by continuing to supporting schema + data as aliases for the names we ultimately decide
We should nix the CLI flag form entirely, in favor of the test_type method. I'm open to whether we should continue supporting the --schema and --data flags for backwards compatibility.

Describe alternatives you've considered

Leaving the old names in place

I agree with this point tests should just be tests. But I am concerned that the rename (schema -> generic, data -> bespoke) could add confusion to existing users without adding value. What do you think?

I really appreciate you raising the concern @boxysean! For what it's worth, I'm not in love with the terms generic or bespoke either.
Part of the dbt v1.0 project is acknowledging that, given current growth trajectory in weekly active projects, the majority of post-v1.0 dbt users have still never used dbt. If we think there's something, anything, that could be improved for the sake of making it more intuitive and less confusing, the sooner the better.
My perspective here is that "data test" and "schema test" are themselves quite confusing names today—they're just the confusing names that we're used to. (All tests on are data; "schema" is an overloaded term, and schema tests don't need to be defined in files named schema.yml.)
I'm not after a 1:1 rename, exactly. Within the codebase, I'd like to see us redefine these to all just be test, wherever  possible, and then in our documentation we can differentiate between tests defined via one-off queries vs. tests defined via reusable/generic/parametrized queries, as different implementation mechanisms of the same functionality.
There are a few places where we need to pick specific words, however, for the sake of existing functional parity. The biggest one that comes to mind is the selection criteria:
$ dbt test -m test_type:data
$ dbt test -m test_type:schema

We're trying to make this distinction less explicit, but it still exists, so I'd like to find some words that would sit comfortably in the codebase, in the selection syntax docs, and in the hearts & minds of our community members.

Can I propose that

in the hearts & minds of our community members

is actually a two-parter as follows?

a pair of words that are effective opposites to aid discoverability (if you know what a generic test does, you can infer the behaviour of a bespoke test, as opposed to schema vs data)
each word should work individually in conversation (eg one-off/single purpose is better than bespoke - on its own, does bespoke imply that's the only type of test I can make for myself?)

I'm assuming the code and selection constraints boil down to short and unique is good, one word is better.
FWIW, I'm ok with generic as a name, but don't care for bespoke. Some alternative options: targeted/focused/single-use/single-purpose
Templated vs fixed?
Templated vs non-templated? A bit 🤢, but maybe just crazy enough to work. Particularly inelegant around node selection unless it changed to --exclude:test_type:templated

I agree that the current terms can be confusing to users. If you think about it, is a unique test not testing data? New users might understand terns like built-in or reusable vs custom.  I think that is the main difference for a newcomer.  You can use these simple words in your schema, pass in some parameters and leave the SQL to us wether that comes from dbt, dbt-utils, dbt-expectations, etc. OR if you want, you can create some custom test over here but it is likely that is not reusable.  When you advance you can take that custom test and make it reusable via a macro.

Okay this just hit me, and perhaps it's too late for additional input, but...
Splitting the two types of tests on a different axis: what if they were called YAML (file) tests and SQL (file) tests?

Ok, I think it's high time to make a final call here:

I'm quite happy with generic as a name for reusable macro-like tests
I'm significantly less happy with bespoke. We don't shy away from strange words when they're the right ones (hello ephemeral), but this one doesn't feel right. I'm now thinking that one_off or single_use (thanks @joellabes!) is much closer to the mark.

I'm open to one last round of persuading, if anyone wants to get a final word in. Then it's going west, going east, gone till 2.0 at least :)

I agree with @jtcohen6 , generic test is fine. Less of a fan of bespoke, and harder to explain to new users.
I'm not a fan of one_off or single_use either, to me they sound like you'd run these tests only once.
How about the antonym of generic: specific tests?
A generic test is re-usable across multiple models.
A specific tests is written to test one specific use case.

Good point about potential confusion around running only once.
I think specific is a solid option. It does make think of https://en.wikipedia.org/wiki/Sensitivity_and_specificity
@MartinGuindon What do you think of singular? Better/worse?

Singular is better than one off or single use, but not sure I like it more than specifc. But still a good option I think.

I'd take single purpose (instead of single use) over specific, but I'd take any of these over bespoke

"Generic test" 👍.
I am strongly against bespoke test. My favorite of the recent options is "singular".
I'll throw in different options of a slightly different dimension: "SQL statement test", "statement test", "unparameterized test", "custom test" (throwback to @noel's earlier comment).

Ooh I don't mind unparameterized. At that point I'd make a play for renaming generic tests to parameterized ones though.
Also there are like 4 different ways to spell parametrised by the time you sneak the extra E in and get the Ss and Zs in the mix 😥

I think one big difference is having a macro for generic test and NOT having a macro in a bespoke test.
So...  Generic Macro Test and  Custom SQL test

Thank you all! Sounds like we can really agree about "not bespoke" 😅
@noel : It's a fair distinction, and it's definitely how I think deep-down about the difference between the two: one of these is macro-like, one of these is just my SQL in a file. I struggle with names like custom, sql_test, or sql_file_test because it's desirable for users to write their own custom generic tests, as (parametrized) SQL, in .sql files!
@boxysean Parametrized is a really good word to use when communicating the underlying implementation. I've been using this word to explain how a generic test works:

I don't love unparametrized for the test-formerly-known-as-data, though, for the same reason I wouldn't like non_generic: I'd rather find a positive word that stands in sharper contrast.
@joellabes That's a really good point about how specific might make it even harder to talk about another test-related thing that I find myself struggling to find good words for, "a specific instance of a generic test," i.e.
models:
  - name: my_model
    columns:
      - name: id
        tests:
          - unique  # <---- this one
       - name: another_col
         tests:
           - unique # <---- not this one

So I'm leaning toward singular because:

It's an odd-enough word that it's unlikely to collide with other words we need to use in everyday conversation
Its meaning is intuitive for a person who's relatively new to dbt
By its other meaning, a singular test is also a really excellent one: standout, one-of-a-kind, suis generis
As its antonym, generic tests ought to be plural, which they sort of are!

@jtcohen6 when you say "it's desirable for users to write their own custom generic tests, as (parametrized) SQL" at this point they become a Generic Macro test, no? It's like a custom generic macro test or a custom sql only test.
Maybe custom is not the "right" word. Could be something like personalized or tailored

tailored reusable test (in macros dir)
tailored specific test (in tests dir)

@jtcohen6 I'd be happy with singular + generic.

Agreed that singular + generic is good. :-) I agree singular won't collide with other words and is reasonably related.

Lock it in 👍 🔒


Edpm networker node

This PR adds make file targets to create and deploy EDPM networker node(s) in very similar way to how edpm compute nodes are created.
Depends-On: https://github.com/openstack-k8s-operators/dataplane-operator/pull/590

I think we should extract common code into some edpm_node root, and edpm_compute /edpm_networker would call edpm_node passing the parameter compute/networker

I totally agree that we should reorganize it and extract some common code to reuse. But it's not just edpm-compute and now edpm-networker which are duplicating stuff like that. Please see e.g. scripts/gen-edpm-baremetal-kustomize.sh or devsetup/scripts/gen-edpm-compute-node-bgp.sh which are already there.
Would it be ok for You if we would go with this patch as it is now and I will propose new PR to clean this stuff up and reorganize code in the way that we will reuse as much as possible?

/lgtm

recheck

/lgtm

recheck

I just tested this once again locally and after deploying 2 edpm compute nodes and 2 edpm networker nodes I have all of that working fine:
sh-5.1$ openstack network agent list +--------------------------------------+------------------------------+--------------------+-------------------+-------+-------+----------------------------+ | ID                                   | Agent Type                   | Host               | Availability Zone | Alive | State | Binary                     | +--------------------------------------+------------------------------+--------------------+-------------------+-------+-------+----------------------------+ | 423849d5-7161-41f8-9bd4-1f9c1f2aa7c0 | OVN Controller Gateway agent | crc-mmwz7-master-0 |                   | :-)   | UP    | ovn-controller             | | 9689a789-6932-4933-a62a-5e23fa92c440 | OVN Controller Gateway agent | edpm-networker-0   |                   | :-)   | UP    | ovn-controller             | | addcaef5-e3c6-48bb-ba03-e691cb5ce8bc | OVN Controller Gateway agent | edpm-networker-1   |                   | :-)   | UP    | ovn-controller             | | 6d08c23d-06dc-4570-9dc4-46299af86037 | OVN Controller agent         | edpm-compute-0     |                   | :-)   | UP    | ovn-controller             | | 2d6d5c4d-de81-4da3-b085-9012f2f5ccef | OVN Controller agent         | edpm-compute-1     |                   | :-)   | UP    | ovn-controller             | | 3d8561a3-235b-5e11-b358-d52161ccd621 | OVN Metadata agent           | edpm-compute-0     |                   | :-)   | UP    | neutron-ovn-metadata-agent | | 7cdab5fe-33a3-54a3-834c-e4a60aafff99 | OVN Metadata agent           | edpm-compute-1     |                   | :-)   | UP    | neutron-ovn-metadata-agent | +--------------------------------------+------------------------------+--------------------+-------------------+-------+-------+----------------------------+

recheck


fix CVE-2021-43565

Ref: https://github.com/stolostron/backlog/issues/18885
Signed-off-by: haoqing0110<EMAIL_ADDRESS>

/assign @elgnay

/approve
/lgtm


Doesn't work with harmony proxies

This is more of a call for help rather than an issue. I have a testing library that I use that uses harmony proxies. It looks like this needs to be enabled, but I haven't figured out how to run the coverage with harmony proxies enabled. Any ideas?

Babel doesn't and can't support proxies due to the limitations of ES5. You'll likely have to wait until istanbul itself can cover proxies, which might be a long while.

Just for reference: https://babeljs.io/docs/learn-es2015/#proxies

Yeah, I know that Babel doesn't support it. Thought maybe there might be some way to run coverage with node --harmony-proxies. If not, ah well.

I actually don't see why istanbul itself wouldn't work with proxies since there is not special syntax involved. Have you actually tried running coverage with node and harmony proxies?

I've tried, but I fear that I don't have the syntax correct.


TCK Challenge: Server Async Tests

The WildFly team would once again like to challenge the tests in JaxRsServerAsyncTest. These tests and the functionality they exercise, while perhaps useful, are not required by the MP Telemetry 2.0 specification.
The only mention of "concurrency" in the spec is to note the removal of Jakarta EE Concurrency dependency, and the only mention of "async" is vague references to "sync and async" in describing some otel properties.
The purpose of a TCK is to verify an implementation's  faithfulness to a specification, and since this specification is silent -- in any meaningful way -- the TCK should be as well.

@donbourne I thought it was clear: these tests are verifying something that is not required by the specification. Regardless of how the concurrency is provided (JDK vs EE), concurrency is not required by the spec. It's just not discussed anywhere in the spec at all. That being so, this test, in a suite to verify compliance with a specification is out of place and inappropriate and should be removed.
It is currently not marked as optional as best as I can tell from the spec.

We will discuss this challenge on the MP Telemetry call 7th October. Please attend if you can.

I had an external appt this morning (and was out last week), so I was unable to attend today's meeting.

I don't mind having the test as mandatory. I was able to provide an executor (not Jakarta Concurrency) and successfully execute the test.

The question, though, is are the tests appropriate according to the spec. My assertion is that they are not. Optional's an acceptable work around, I guess, but that dodges the question a bit.

The question, though, is are the tests appropriate according to the spec. My assertion is that they are not. Optional's an acceptable work around, I guess, but that dodges the question a bit.

It is not optional. The async part in Jakarta Restful Web Services is not optional either. Since MP Telemetry supports the usage of Jakart Restful Web Services, the async part is supported of course. There is no need to list every part of Jakarta Restful Web Services. We discussed this at length in the recent weekly calls. Please see the minutes for more info.


Ability content

Using Legacy and Refactoring sections might be good outline  in general, thoughts? #30

Good point, thanks Bess. I changed that copy in the update PR.


No way to access value of a mime::ParamValue

mime::ParamValue has a private tuple struct constructor and no accessor methods, so there's no way to actually get the value out of them.

To give a bit of a more actionable comment, is the plan to implementing some kind of accessors for it, or can we just make the constructor public so that it's possible to pattern match on them?

@kyrias could you say more? ParamValue implements Display which is a way to access the value contained in the inner Cow<'static, str> through a unified interface. But did you have something else in mind?

Hm, didn't really think about Display since its generally for output and you don't really have any specific guarantee that it'll be just the raw string value that it contains.  But I guess passing format!("{}", foo) should be fine in this case, yeah.


Add BPMN Diagram (Zeebe) button for the Empty Tab

What should we do?
Add BPMN Diagram (Zeebe) button for the Empty Tab.
Why should we do it?
We want to support the Zeebe tab in all places.

Closed via https://github.com/camunda/camunda-modeler/commit/4e5fd1056ecf1ebdfd0bda2c1486b1336cca80e1


[BUG] KeyError: 'description'

Type of Connector
Custom Connector
Name of Connector
MyPractice API v1
Describe the bug
I'm trying to push the host name into the connection properties (would really like to add HTTP/HTTPS, gateway yes/no and baseURL as well, but have to start somewhere).
I've been following the steps at https://philcole.org/post/environment-specific-custom-connector-endpoints/ as best I can, but when I attempt the paconn update, I get the following error:
Connector selected: MyPractice API v1 - Craig Humphrey
'description'
Traceback (most recent call last):
  File "C:\Python311\Lib\site-packages\knack\cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\knack\invocation.py", line 188, in execute
    cmd_result = parsed_args.func(params)
                 ^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\knack\commands.py", line 131, in __call__
    return self.handler(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\knack\commands.py", line 238, in _command_handler
    result = op(client, **command_args) if client else op(**command_args)
                                                       ^^^^^^^^^^^^^^^^^^
  File "C:\Python311\Lib\site-packages\paconn\commands\update.py", line 48, in update
    connector_id = upsert(
                   ^^^^^^^
  File "C:\Python311\Lib\site-packages\paconn\operations\upsert.py", line 127, in upsert
    properties[_DESCRIPTION] = openapi_definition[_INFO][_DESCRIPTION]
                               ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: 'description'

Is this a security bug?
No, this is not a security bug
What is the severity of this bug?
Severity 1 - Connector is broken or there's a very serious issue
To Reproduce
I added the following connectionParameters to my apiProperties.json file:
"endpointUrl": {
"type": "string",
"uiDefinition": {
"constraints": {
"required": "true"
},
"description": "API host name (Exampled: mypracticeapi.company.com)",
"displayName": "API host name",
"tooltip": "API host name (Exampled: mypracticeapi.company.com)"
}
}
The rest is the same as in the tutorial (policy template).
Expected behavior
I was hoping it would just work :)
Environment summary
Install Method:
pip
CLI version (paconn --version)
paconn --version
0.0.20
Python (Windows) 3.11.3 (tags/v3.11.3:f3909b8, Apr  4 2023, 23:49:59) [MSC v.1934 64 bit (AMD64)]
OS version
Windows 11, 22H2 (22621.2134)
Shell Type
PowerShell v7
Additional context
This is my first Custom Connector and I need to parametrise the host so that I can have a generic Custom Connector name, so that it doesn't fail when I try to import my PowerApp/Automate solution into a client's tenant.
Thanks!

nudge


Update Vendored version of Nomad to 0.7.1.

The major release 0.7 of Nomad introduced ALCs amongst a raft
of other features. Therefore Levant requires updating to allow
users who are running the latest version of Nomad and using ACLs
to be able to use Levant.
The README.md has also been updated to provide a quick section on
what environment variables to be used by Levant and the Nomad
client to configure certain parameters.
Closes #75

Tagging @leeuwenrjj who raised the initial request.

Tested with tokens and works for me.


VTT writer and reader do not treat WebVTT cue ruby

Hello.
I am trying to convert between IMSC 1.1 and WebVTT including ruby.
For example, when I input the file ruby001.ttml from imsc-tests, it does not output the vtt file including ruby.
The same goes for inputting a vtt file including ruby.
Is there any plan for ttconv to support this?
Thanks

As I recall the feature was deferred until ruby annotations were reliably supported by WebVTT players (@andreastai might recall differentely).
What is the level of support for ruby annotations in WebVTT players today?

Ok. It looks like we should plan on adding this feature.
Do you have a catalog of files available for testing?

Unfortunately I do not have the files.
However, in my opinion, it is already in imsc-tests and ttconv/src/test in the necessary files.
In my opinion, there is no ruby functionality possible only in WebVTT.
I think the only CSS that can be specified for ruby in WebVTT is ruby-position. In other words, I think only ruby in imsc-tests is applicable. (rubyAlign is not.) However, as far as I confirmed, Chrome (and Edge), Firefox and Safari cannot render ruby-position.
Another feature related to ruby is writing-mode. This can be tested, for example, with bidi_vertical_lr.vtt and bidi_vertical_rl-oneline.vtt. Unfortunately, only Safari can render vertical-mode, Chrome and Firefox cannot.
I hope I can show you the information you need. Thanks.


Add Akka-Http-based VCR client

Akka-http offers several styles of HTTP clients API.
However, IIUC, akka-http does not offer HTTP-client interface unlike others.
Instead, in roughly speaking, akka-http offers a very simple function HttpRequest => Future[HttpResponse].
Request-level Client-Side API is one of HTTP Client API in Akka-http, and is recommended for most usage.
In that API, firstly, users call Http() to generate an instance of HttpExt.
To send HTTP request in Future-variant, users invoke HttpExt's method def singleRequest(request: HttpRequest): Future[HttpResponse].
I think def send(request: HttpRequest): Future[HttpResponse] in VcrHttp class could replace that.
HttpExt class is not just a HTTP client but could be a HTTP server.
HttpExt class is marked as @DoNotInherit, so I think we can not offer HttpExt that extends VcrClient capability.
I assume a realistic scenario is something like this:
import akka.http.scaladsl.Http
import akka.http.scaladsl.model._

// Subject to be tested, which consumes HTTP as client
class FooService(sendRequest: HttpRequest => Future[HttpResponse]) {
  def fetchSomething(): Future[Foo] =
     sendRequest(HttpRequest(...)).map(...)
}

object App {
  def main(args: Array[String]): Unit = {
    implicit val system = ActorSystem(Behaviors.empty, "SingleRequest")
    implicit val executionContext = system.executionContext

    val http = Http()
    // Inject "HTTP client" here
    val fooService = new FooService(http.sendRequest(_))

    fooService.fetchSomething
      .onComplete {
        case Success(res) => println(res)
        case Failure(_)   => sys.error("something wrong")
      }
  }
}

// test code
class FooServiceTest extends FunSuite {
  test("foo") {
     val vcrHttp = VcrHttp.create(...)
    // Inject VCR "HTTP client" here
    val foo = new FooService(vcrHttp.send(_))

    foo.fetchSomething().map { res =>
      assert(...)
    }
  }
}

Yeah, when I was looking around yesterday I saw that HttpExt class too, but it didn't seem like I could do much with it.
I was thinking maybe there's a way to inject at the actor level. Like have an actor in between that does the VCR matching logic. And if it doesn't match, then forward to ref ! SendRequest(...) as usual. But I don't see how that's possible either. Well, I don't know enough about Akka to rule it out for sure, but I imagine it would be hacky or difficult to do.
Anyway, I would be fine with going with the current design. It might require the user to restructure their code to inject sendRequest: HttpRequest => Future[HttpResponse] in the constructor (if they're not already doing that), but at least VcrClient doesn't show up in main scope.
Maybe in the future we can try to find some solution that works with all styles of using akka-http (if it's possible in the first place). But that doesn't have to be in this PR.


Use thiserror and refactor errors

Makes error variants a bit more sane and structured.
Also takes advantage of thiserror, since that's what we settled on in wgpu land.
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:

New code (HAL only):

Finished dev [unoptimized + debuginfo] target(s) in 17.65s

Old code (HAL only):

Finished dev [unoptimized + debuginfo] target(s) in 7.73s

New timing -  cargo-timing-20201202T054953Z.html.zip
Old timing -  cargo-timing-20201202T055308Z.html.zip
It's clear that gfx itself doesn't take more time to build. In fact, even less.
But in total the time now has to include the thiserror dependencies, including syn, quote, and proc-macro.
So it's a question of whether we expect the clients to already depend on thiserror (in which case it's free), or not.
The benefit is clear - our code becomes more manageable (+338 −865).

I believe the most important (current and future) consumers of gfx-hal are:

wgpu - already uses thiserror
amethyst - uses thiserror transitively through cpal, also depends on a lot of other crates that drag syn and friends in
webrender - also not a concern for it

So I think we should bite the bullet and go for it.

bors r+


Computational requirements for Training

Hey,
Can I train this on Google colab?
How long will it take in general?
Can you share some more info on where i can run this code?

Hi,
For your reference, we conducted experiments on an Nvidia TITAN RTX 24G GPU, and it takes about 20 hours on ImageNet-10 (13000 images, 10 classes).
The package dependency is given in readme.md. You may follow the instructions to run this code in the required environment.

Thanks!

I wanted to try the same network with a bigger batch doing something like the following:
    # initialize model
    res = resnet.get_resnet(args.resnet)
    model = network.Network(res, args.feature_dim, class_num)
    device = 'cuda'

    if torch.cuda.device_count() > 1:
        model = torch.nn.DataParallel(model)

    model = model.to(device)

I see that you use only one GPU and use a batch size of 256 for 1000 epochs.
Do you think doing something like above would be a better option in case I have 2 gpus for a bigger batch and to run lesser epochs.?

We didn't try DataParallel for our model. However, since our model is based on the standard SimCLR method, maybe you could refer to the SimCLR code with multi-GPU training for more details.


feature request: CoqToEndOfBuffer

in particular it should do the thing without moving the cursor

With be5c0b181b6c2cb2150c575afcf11ca9a097c0ae :$CoqToLine should do this. I didn't define a default mapping for it though.


Would like a little more info on how crazy this cow is !

Hi,
Your project sounded awesome to me, but there are some details I don't understand. If i understood right, you need to launch your remarkable differently than with the usual UI ? Or can you just switch to the keyboard typing mode by plugging a keyboard ?
My main point is trying to understand to what extent installing your code on a rM device will change the original writing experience with a pencil ?
Thanks a lot for this crazy project !
Darius

Hi Darius! Thanks for your note.

you need to launch your remarkable differently than with the usual UI?

Nope, you start the reMarkable up just normally.

Or can you just switch to the keyboard typing mode by plugging a keyboard?

Yes, exactly. I used it this morning, actually with a cheap USB wireless keyboard. Just plugged in the USB and started typing. That was the plan, and so far it seems to be working. :]

My main point is trying to understand to what extent installing your code on a rM device will change the original writing experience with a pencil?

No change at all. This morning I typed characters and also wrote notes next to them.
One small quirk to know: the "backspace" feature uses the reM Undo tool, so if you type and hit backspace it's fine, but if you pencil and then immediately backspace, it'll undo some of your pencil art.

Thanks a lot for this crazy project !

 I hope you enjoy it. So far I'm finding it nice to use.

Ok ! Good to hear !
But so what kind of keyboard do you plug in ? I tried with my computer keyboard, doesn't work, but I guess this is because rM tablet cannot power on the keyboard... What does the usb wireless keyboard u r using looks like ?
I'm pretty excited about making the cow getting crazy :p

Hm, one thing: it requires a USB OTG ("on the go") adapter to convert the keyboard's USB to the MicroUSB of the reM. I've successfully used both this ($5.59) and this ($4.99 for 5 of them).
If that connector's correct, then one keyboard I've used successfully is this ($11.69), and I've also used an older 2.4GHz USB wireless keyboard by plugging the 2.4GHz receiver into the OTG adapter.

So I've followed the install instruction. I've plugged in a USB bluetooth receiver via the OTG USB and try the associated keyboard to type down stuff ! But nothing happened :(
I'm using the wireless microsoft keyboard 2000 (working on my computer which is windows 10) and I know it is connected as I can control the page swipping with the keyboard left and right arrows. But clicking on a letter does not affect the current notebook. May it be the keyboard which isn't simple enough ? Or the fact it was working with windows and not Mac or Linux ? (Unix system ?)
Would you have any guess ?

Hi there,
Thank you for so much detailed info! As far as I know, you're the first person to try this besides me, and there's a lot we can do to try to debug this.
First of all, the left/right arrow keys were a great find. The reM built-in software supports those, so that's the perfect way to test that the keyboard is connected and supported.
As a next step, I've just pushed a new branch (complete with binary) specifically to solve this, called 1-device-testing. That version just does a ton of diagnostic printing.
Here's how to try it:

ssh into your device, and type systemctl stop crazy-cow to stop the service.
Download the debug version crazy-cow-debug and copy it to your device.
In your ssh window, type ./crazy-cow-debug and you should immediately output like this:

]] at line 586 in main
  ]] at line 579 in initialize
  ]] at line 581 in initialize

If no keyboard is plugged in, you should see this every few seconds:
    .. at line 550  (no keyboard)
    ]] at line 503 in find_devices
      .. at line 509 in find_devices
      .. at line 509 in find_devices
      .. at line 509 in find_devices
      .. at line 509 in find_devices
      .. at line 509 in find_devices
      .. at line 512 in find_devices
       .. found wacom dev platform-21a4000.i2c-event-mouse
      .. at line 516 in find_devices
  Connected to pen input device /dev/input/by-path/platform-21a4000.i2c-event-mouse.
      .. at line 509 in find_devices
    .. at line 554  (still no keyboard)

When a keyboard is plugged in, you should see something like this, just once:
  ]] at line 547 in do_main_loop
    .. at line 550  (no keyboard)
    ]] at line 503 in find_devices
      .. at line 509 in find_devices
      .. at line 509 in find_devices
      .. at line 509 in find_devices
      .. at line 509 in find_devices
      .. at line 526 in find_devices
       .. found keyboard dev platform-ci_hdrc.0-usb-0:1:1.0-event-kbd
  Connected to keyboard device /dev/input/by-path/platform-ci_hdrc.0-usb-0:1:1.0-event-kbd.

After that, with a notebook open and a pen selected, if you press the letter "A" on your keyboard you should see this output:
  ]] at line 547 in do_main_loop
  ]] at line 547 in do_main_loop
  ]] at line 547 in do_main_loop
  ]] at line 547 in do_main_loop
    ]] at line 413 in handle_event
      .. got key event type:1 code:30 val:1
    ]] at line 486 in handle_event
      .. character to type:a
  ]] at line 547 in do_main_loop
  ]] at line 547 in do_main_loop
  ]] at line 547 in do_main_loop
    ]] at line 413 in handle_event
      .. got key event type:1 code:30 val:0
  ]] at line 547 in do_main_loop
  ]] at line 547 in do_main_loop

...and should see a lower-case "a" appear right next to the pen tool:

If this fails...
All of those printed lines correspond to lines in main.cpp like this one, so at least we can see what's failing. It might also be worthwhile to try ls /dev/input/by-path/ in your ssh window, to see what's there and if plugging in the keyboard changes.
To start the non-debug version, you can just systemctl start crazy-cow in your ssh window again.
Please let me know what happens, and thank you for testing!

Ok so here it what happened :
I've copied and launched crazy-cow-debug (note that I had to chmod +x crazy-cow-debug before being authorized to run it)
And the predicted message kept appearing regularly until I plug the usb bluetooth receiver of the keyboard in my rM tablet.
Then I got the confirmation that a keyboard was connected :
  ]] at line 547 in do_main_loop     .. at line 550  (no keyboard)     ]] at line 503 in find_devices       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 512 in find_devices        .. found wacom dev platform-21a4000.i2c-event-mouse       .. at line 509 in find_devices       .. at line 509 in find_devices     .. at line 554  (still no keyboard)   ]] at line 547 in do_main_loop     .. at line 550  (no keyboard)     ]] at line 503 in find_devices       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 526 in find_devices        .. found keyboard dev platform-ci_hdrc.0-usb-0:1:1.2-event-kbd   Connected to keyboard device /dev/input/by-path/platform-ci_hdrc.0-usb-0:1:1.2-event-kbd.       .. at line 509 in find_devices       .. at line 512 in find_devices        .. found wacom dev platform-ci_hdrc.0-usb-0:1:1.1-event-mouse       .. at line 509 in find_devices       .. at line 526 in find_devices        **.. found keyboard dev platform-ci_hdrc.0-usb-0:1:1.0-event-kbd**       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 509 in find_devices       .. at line 512 in find_devices        .. found wacom dev platform-21a4000.i2c-event-mouse       .. at line 509 in find_devices       .. at line 509 in find_devices   ]] at line 547 in do_main_loop   ]] at line 547 in do_main_loop   ]] at line 547 in do_main_loop   ]] at line 547 in do_main_loop
But after that, opening a new notebook and typing 'a' or whatever other key did not cause any additional message to pop up in the terminal, nor any letter on the notebook.
Still, the basic input as you said were working : keyboard arrows, and the escape and home keys that would act like the rM1 central button.
 :(

That's good info... clearly the keyboard device is being opened with no problem, so it may be the case that something else is intercepting the key events so crazy-cow doesn't get them.
Here's something to try:
ls -l /dev/input/by-path/
...should show you the device aliases. In my case, I can see that my keyboard is being mapped to event3...
lrwxrwxrwx    1 root     root             9 Sep 18 13:49 platform-21a4000.i2c-event-mouse -> ../event0
lrwxrwxrwx    1 root     root             9 Sep 18 13:49 platform-21a4000.i2c-mouse -> ../mouse0
lrwxrwxrwx    1 root     root             9 Sep 18 13:49 platform-21a8000.i2c-event -> ../event1
lrwxrwxrwx    1 root     root             9 Sep 18 17:10 platform-ci_hdrc.0-usb-0:1:1.0-event-kbd -> ../event3
lrwxrwxrwx    1 root     root             9 Sep 18 17:10 platform-ci_hdrc.0-usb-0:1:1.1-event -> ../event4
lrwxrwxrwx    1 root     root             9 Sep 18 13:49 platform-gpio-keys-event -> ../event2

...so then we can use lsof to see who else has it open, like this:
lsof | grep /dev/input/event3 (replacing event3 with whatever your keyboard is mapped to)
...in my case, I see this:
systemd-l 174                 root   16u      CHR      13,67      0t0      14004 /dev/input/event3
xochitl   209                 root   23r      CHR      13,67      0t0      14004 /dev/input/event3
QEvdevTou 209 220             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
LoadingTh 209 226             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
QQmlThrea 209 227             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
Qt\x20bea 209 228             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
QDBusConn 209 229             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
QThread   209 232             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
QQuickPix 209 239             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
QNetworkA 209 263             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
DocumentW 209 269             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
QThread   209 270             root   23r      CHR      13,67      0t0      14004 /dev/input/event3
crazy-cow 323                 root    4r      CHR      13,67      0t0      14004 /dev/input/event3

This shows every process which found and opened the attached keyboard. In that list, I see xochitl (that's the reM built-in UI app) and I see crazy-cow, and then a bunch of others I don't know much about, but which don't seem to be causing any trouble.
If your list has items in it I'm missing, what are those?

Ok nice !
May be we'll find out the problem !
When I ls -l /dev/input/by-path/ here is what I got :
lrwxrwxrwx    1 root     root             9 Sep 18 12:13 platform-21a4000.i2c-event-mouse -> ../event0 lrwxrwxrwx    1 root     root             9 Sep 18 12:13 platform-21a4000.i2c-mouse -> ../mouse0 lrwxrwxrwx    1 root     root             9 Sep 18 12:13 platform-21a8000.i2c-event -> ../event1 lrwxrwxrwx    1 root     root             9 Sep 19 13:13 platform-ci_hdrc.0-usb-0:1:1.0-event-kbd -> ../event3 lrwxrwxrwx    1 root     root             9 Sep 19 13:13 platform-ci_hdrc.0-usb-0:1:1.1-event-mouse -> ../event4 lrwxrwxrwx    1 root     root             9 Sep 19 13:13 platform-ci_hdrc.0-usb-0:1:1.1-mouse -> ../mouse1 lrwxrwxrwx    1 root     root             9 Sep 19 13:13 platform-ci_hdrc.0-usb-0:1:1.2-event-kbd -> ../event5 lrwxrwxrwx    1 root     root             9 Sep 18 12:13 platform-gpio-keys-event -> ../event2
So you see my bluetooth receiver is connected to a keyboard and a mouse (which I don't switch on) But more intersetingly i think, there are two input for the keyboard. So in my case, event 3 and event 5. And crazy-cow seems to be connected to event 5 only :
When I lsof | grep /dev/input/event3 I got
systemd-l 191                 root   16u      CHR      13,67      0t0      23083 /dev/input/event3 xochitl   666                 root   23r      CHR      13,67      0t0      23083 /dev/input/event3 QEvdevTou 666 670             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 LoadingTh 666 676             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 QQmlThrea 666 677             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 Qt\x20bea 666 678             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 QDBusConn 666 679             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 QThread   666 680             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 QNetworkA 666 683             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 QQuickPix 666 685             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 DocumentW 666 778             root   23r      CHR      13,67      0t0      23083 /dev/input/event3 QThread   666 779             root   23r      CHR      13,67      0t0      23083 /dev/input/event3
And when I lsof | grep /dev/input/event5 I got
systemd-l 191                 root   17u      CHR      13,69      0t0      23092 /dev/input/event5 xochitl   666                 root   24r      CHR      13,69      0t0      23092 /dev/input/event5 QEvdevTou 666 670             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 LoadingTh 666 676             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 QQmlThrea 666 677             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 Qt\x20bea 666 678             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 QDBusConn 666 679             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 QThread   666 680             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 QNetworkA 666 683             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 QQuickPix 666 685             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 DocumentW 666 778             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 QThread   666 779             root   24r      CHR      13,69      0t0      23092 /dev/input/event5 crazy-cow 828                 root    5r      CHR      13,69      0t0      23092 /dev/input/event5
And here we see crazy-cow in the end of the list.
May be event 5 is not the good one and I should find a way to redirect crazy-cow toward event 3 (or at least have it work with both event ?)
Thanks for helping me out with that ! I feel like I'm begining to understand a bit more what your code is doing ^^'

Aha, clearly you're right. Somehow your setup is supplying two keyboards, and only one works.

The immediate workaround I suggest is to, if possible, simplify your hardware setup so that only a single keyboard is added.
I'll also explore the code change to support multiple keyboards. While it seems simple (and would be on a laptop), I want to be very (very) careful to avoid extra battery drain. Especially with eInk devices, that's what prevents a simple "polling devices" model. I'm sure there's a good way to do this, just need to try it and test it well.

With your current setup, is there an easy way to simplify it down to a single keyboard device?

Update: I've been able to connect two keyboards and exactly reproduce this issue. Looking into a clean fix...

Cool, thanks !
About the workaround, because the debug version was giving interesting info, I tried again with a non-bluetooth USB keyboard (so basically the keyboard of my PC) And in fact, the rM do detect it (and I guess is able to power it) and I this keyboard appears to be a single keyboard for the rM tablet. So once I launched crazy-cow, I become able to type letter down, as expected !
I think that might be usefuul for other users to have a fix for the two keyboards issue to allow more keyboards to work, and so more people to be able to use your code. But at least, with this detailed issue, they will have a chance to now why their keyboard doesn't work.
Now I have a lot of other feature requests hehe ! But I bet it will be cleaner if I write new issues !

To finish off this item, I've done a test implementation for multi-keyboard support. You can try the binary now, in the 1-multiple-keyboards branch of this project. It's not very well tested yet, but seems to do the trick.

Hi machinelevel,

Hm, one thing: it requires a USB OTG ("on the go") adapter to convert the keyboard's USB to the MicroUSB of the reM.

I tried SAUX USB C to USB 3.1 OTG without success.
Regards
Oliver


[bug] fn $FUNC($$$ARGS) { $$$ } does not match the function item of Rust

⏯ Playground Link
Playground link with relevant code
💻 Code
Code:
#[turbo_tasks::function]
async fn read(name: String) -> Result<Vc<Option<String>>> {

}

Pattern:
id: update-function-parameters
language: rust
rule:
  pattern: 'fn $FUNC($$$ARGS) { $$$ }'

or pattern = fn $FUNC($$$ARGS) { $$$ } in the playground
🙁 Actual behavior
It didn't match any function.
🙂 Expected behavior
It should match all functions

Thanks for the report!
There are two things in the repro:

fn $FUNC($$$ARGS) { $$$ } does not have a return type. So it does not match the fn read(name: String) -> Result<Vc<Option<String>>> because the latter has a return type. This is expected.

I recommend using any to combine these two cases.
id: update-function-parameters
language: rust
rule:
  any:
  - pattern: 'fn $FUNC($$$ARGS) { $$$ }'
  - pattern: 'fn $FUNC($$$ARGS) -> $RET { $$$ }'

However, the above YAML still does not match async function.  This is unexpected. Because async is not an AST node, the pattern query does not specify the keyword.  Both async and non-async should be matched.

I will investigate the latter case. Meanwhile this is the work around
id: update-function-parameters
language: rust
rule:
  kind: function_item
  has:
    kind: parameters
    pattern: $PARAMS

https://ast-grep.github.io/playground.html#eyJtb2RlIjoiQ29uZmlnIiwibGFuZyI6InJ1c3QiLCJxdWVyeSI6ImZuICRGVU5DKCQkJEFSR1MpIC0+ICRSRVQgeyAgJCQkIH0iLCJyZXdyaXRlIjoiIiwiY29uZmlnIjoiaWQ6IHVwZGF0ZS1mdW5jdGlvbi1wYXJhbWV0ZXJzXG5sYW5ndWFnZTogcnVzdFxucnVsZTpcbiAga2luZDogZnVuY3Rpb25faXRlbVxuICBoYXM6XG4gICAga2luZDogcGFyYW1ldGVyc1xuICAgIHBhdHRlcm46ICRQQVJBTVNcbiAgIiwic291cmNlIjoiI1t0dXJib190YXNrczo6ZnVuY3Rpb25dXG5hc3luYyBmbiByZWFkKG5hbWU6IFN0cmluZykgLT4gUmVzdWx0PFZjPE9wdGlvbjxTdHJpbmc+Pj4ge1xuICAgIFxufVxuIn0=


How to deploy in Linux server

Hello sir I'm new in laravel development. I'm created simple project with your laravel-vue-spa template.
This project works wery well in local machine. But server side problem. Please guide me.

Hi, this project already assumes that you are familiar with Laravel and Vue so you deploy it as any other Laravel app.
You should check the Laravel docs and forums for more info about deployment.


Change the react-native link command repositories.

In RN 0.59, the repositories of react-native link command moved to
react-native-community repository.[1]
The react-native-background-geolocation used the old repository,
so react-native link command failed.
This patch will change these repository.
[1] https://facebook.github.io/react-native/blog/#cli-improvements

Nice. Will merge this. Thank you!

Shouldn't this patch also add @react-native-community/cli to package.json?

@wmertens Actually good question. @mantaroh can you please confirm?

@mauron85 @wmertens

Shouldn't this patch also add @react-native-community/cli to package.json?

Oh... This is my mistake.
We need to add react-native-community, so I will push the fixed patch.
BTW, I have some question about the package.json.
At the moment, We use the minimum version of react-native is 0.49.0. Is this correctly?

At the moment, We use the minimum version of react-native is 0.49.0. Is this correctly?

I believe so.


Tweaks for 0.2.1

Put id and class on holder, fix self.config.
Remove debugging console logs.
Increment version to 0.2.1.

If you are actively accepting PRs, I can also hand over a form field for an editorjs widget (independent of a model).

@dfrankow Your PR will need to be changed. I just pushed my edits. Thanks


builder-jammy-tiny fails to build spring-boot: permission denied

I have a functioning spring-boot 3.3.3 service I'm trying to compile in native mode inside a podman container with the command:
mvnw clean package -Pnative spring-boot:build-image -Ddocker.publishRegistry.username=%username% -Ddocker.publishRegistry.password=%password% -Ddocker.publishRegistry.url=https://workharbour
The buildpack is pull and the compilation seems to be working. Sadly, the buildpack fails with a permission denied at the end:
[INFO]     [creator]        22.2s (9.3% of total time) in 1321 GCs | Peak RSS: 6.36GB | CPU load: 9.61
[INFO]     [creator]     --------------------------------------------------------------------------------
[INFO]     [creator]     Produced artifacts:
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/it.eng.silcloud.anagrafiche.AnagraficheApplication (executable)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libawt.so (jdk_library)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libawt_headless.so (jdk_library)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libawt_xawt.so (jdk_library)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libfontmanager.so (jdk_library)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libfreetype.so (jdk_library)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libjava.so (jdk_library_shim)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libjavajpeg.so (jdk_library)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/libjvm.so (jdk_library_shim)
[INFO]     [creator]      /layers/paketo-buildpacks_native-image/native-image/liblcms.so (jdk_library)
[INFO]     [creator]     ================================================================================
[INFO]     [creator]     Finished generating 'it.pem.bimbam.anagrafiche.AnagraficheApplication' in 3m 57s.
[INFO]     [creator]       Removing bytecode
[INFO]     [creator]     unable to invoke layer creator
[INFO]     [creator]     unable to remove /workspace/BOOT-INF
[INFO]     [creator]     unlinkat /workspace/BOOT-INF: permission denied
[INFO]     [creator]     ERROR: failed to build: exit status 1
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  05:58 min

Expected Behavior
The image should be compiled and pushed
Current Behavior
The buildpack fails with: unlinkat /workspace/BOOT-INF: permission denied
Possible Solution

Steps to Reproduce
Using Spring-boot 3.3.3 and paketobuildpacks/builder-jammy-tiny:latest
Motivations

I tried again after updating to podman 5.2.5 and the problem is the same. It looks like a permission error upon cleaning ?

You might check and see if podman exposes any properties or settings that you can use to control file permissions. Normally, at least with Docker, the file permissions will be inherited from your local file system. Thus if you pack build -p foo/ the /workspace will have all the files with the same permissions as foo/ locally.
It sounds like that's not the case here, which also sounds like something specific to Podman. I don't use that myself, so I really can't say why it's behaving that way, but there's not much we can do on the buildpack side. If the permissions on those files do not allow us to delete them, then we can't delete them and the build can't continue.

thank you for your kind answer. I guess this ticket can be closed then

Feel free to update us when you get this sorted out. It's possible other people may hit this as well, podman is popular.

yes, definitely. I cross posted it on stackoverflow here  and over docker it looks working


app user / admin port can have different passwords

if you want a different admin user password within the app, you can use
the APP_ADMIN_PASSWORD user. The /_mxbuild/ m2ee api will have the
ADMIN_PASSWORD value. This is not exposed to customers and thus not
documented, but we'll use it in the Mendix Cloud

CI failed because of schnapps-service-broker issue, not related, merging since it looks good to merge to me!


Fix or remove EVMLA

From the ZKSync docs:

EVM legacy assembly is very challenging to translate to LLVM IR, since it obfuscates the control flow of the program and uses a lot of dynamic jumps. Most of the jumps can be translated to static ones by using a static analysis of EVM assembly, but some of jumps are impossible to resolve statically. For example, internal function pointers can be written to memory or storage, and then loaded and called. Recursion is another case we have skipped for now, as there is another stack frame allocated on every iteration, preventing the static analyzer from resolving the jumps.
Both issues are being worked on in our fork of the Solidity compiler, where we are changing the codegen to remove the dynamic jumps and add the necessary metadata.

Their solc fork is in the works for a long time now (months if not years) and this is still the status quo. Also ZKSync is an ETH L2 and since they got away with this so far.
I'd like to set a clear path forward.

It is not entirely clear what the use case is for this? YUL is available and considered stable enough for years.
If we ultimately need it we can either

Declare it as experimental and accept the current status quo
Properly fix it on our own
Possibly work around this by just resolving those jumps dynamically at runtime?
Direct people to the matter-labs solc fork, assuming it is still general enough
Upstream the ML fixes? Why do they not upstream this?

Apparently uniswap v3 is so old that it is still built against Solidity 0.7.

It is not clear if we have to support it. Uniswapv4 exists and supports Solidity 0.8.


Confluence Loader: Fix CQL loading

fix #12082

@ccurme could you review the PR, please?

@baskaryan, @efriis, @eyurtsev could you review the PR, please?

@efriis, @eyurtsev, @ccurme could you review the MR with the fix? Without it, it's completely impossible to load confluence by CQL


Allow orbital space classes to be modifiable

At the moment most of the classes in Chemist, including the ones in the orbital space sublibrary, are immutable. This was done purely for convenience. The user should be allowed to change the state of non-const instances without having to make a copy with the new state (the current workaround).

The design has changed since this issue was opened.


fix(pydantic): Decouple Pydantic integration

Decouple the Pydantic integration from the core logic.
In previous versions, Pydantic integration was baked into the core schema generation, causing issues when trying to run Litestar without it. A recent PR (#2487) surfaced some of these issues, causing an ImportError when Pydantic was not installed.
This PR is an attempt to remove all direct references to Pydantic from Litestar's core, although due to other constraints, some of these should be seen as temporary workarounds.

One major issue preventing a clean solution here is the merging of the ParseType util into FieldDefinition that happened in #1912. This causes FieldDefinition to require information specific to Pydantic, which is not available to it, since this information is contained within the plugin, FieldDefinition however is an ubiquitous utility, used in places where an application context and therefore installed plugins aren't available (nor should they be).
A permanent solution to this would require unmerging these utilities again, creating a separation of concerns between field definitions and metadata and type information.

The coverage reports are not on new code but on already existing code, it's just that I touched these files. Did something change there recently? @peterschutt I think you made some changes to how we report coverage, but I don't think they should affect this?
I would prefer to not address these coverage issues in this PR though, since they don't really fit this scope, so I'd like to ignore them and still go ahead with the merge. That fine with everyone @litestar-org/maintainers?

I think you made some changes to how we report coverage

The main change was https://github.com/litestar-org/litestar/pull/2528 where we adopted the covdefaults plugin. The plugin enables branch coverage, and it might just be that there hasn't been a PR merged into main that has had the branch coverage reported for this file, so it is reporting it here.
We have min 80% coverage configured here: https://sonarcloud.io/organizations/litestar-api/quality_gates/show/9 but I think that is referring to line coverage. Condition coverage is 100% by default so we could look at adding a rule to lessen that constraint, which would probably make this transition period easier.


Changing KDE -> XFCE bricks installation

Basic info
To make sure that we are on the same page:

Kernel: (run uname -a)

Linux nixos 3.18.26 #1-NixOS SMP Thu Jan 1 00:00:01 UTC 1970 x86_64 GNU/Linux

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)

15.09.1113.23395c4 (Dingo)

Nix version: (run nix-env --version)

nix-env (Nix) 1.10

Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)

"15.09.1113.23395c4"
Describe your issue here
Attempted to install XFCE as the default desktop environment according to the instructions given here: https://nixos.org/wiki/Xfce.
Expected result
XFCE would be properly installed and launched on next login.
Actual result
Machine spontaneously restarts and deletes the demo user.
Steps to reproduce
Download and install the 64-bit VirtualBox appliance. Launch. Add services.xserver.desktopManager.xfce.enable = true; to /etc/nixos/configuration.nix. Run sudo nixos-rebuild switch.
Then everything breaks. Reboots without a desktop manager. The demo/demo login no longer works.

How did you create the demo user?

It comes as the default with the VirtualBox appliance.

Any ideas?

@obadz: wrong issue ref? The above commit seem unrelated.

@bjornfor, nope, I was deliberately trying to fix this issue.
I'm the problem was that the /etc/nixos/configuration.nix that was inside the image wasn't the same as the one that was used to generate the image. For instance the one in the image didn't have a demo user…
Feel free to reopen if you can reproduce the issue but I think it's fixed.


[config] Set PATH as ENV instead of hook

Summary
This change improves devbox.json and plugin jsons by allowing PATH to be set as an env variable instead of a hook.
For example, it allows "PATH": "$PWD/dist:$PATH".
In general any environment variable that is defined at the time of parsing is accessible. This means for plugins, the HOST environment is accessible, and for devbox.json the HOST environment and also the plugin environment is accessible. In practice this allows the user to override any plugin environment using an existing variable as base. On the other hand, the plugin environment variables will not take into account any changes that are made in the devbox.json
Some benefits of this change:

We no longer need to export init hooks. One of the main use cases of init hooks is now moved to env instead.
refresh no longer breaks changes to PATH. This is because init hooks don't get run by refresh, but the environment is reset correctly.

Related fixes:

Removed code that was adding virtenv//bin to path. This is not used.
Removed code that was creating env files for each plugin. This is no longer used.
Added hash -r to refresh functions
No longer fetch plugin env vars when starting a service (this was only needed previously when adding a package while in shell would add it to profile but would not add env vars to current shell. Today refresh does this)

How was it tested?
devbox shell
echo $PATH
devbox add ruby
refresh
echo PATH

elated to this, should we also rerun init hooks? As an example, the export GOROOT="$(go env GOROOT)" command needs command substitution so it can't go in env. If you install a different version of Go, you'd want that hook to run again to pick up the new GOROOT.

I'm mixed about re-running them. In this particular case, running refresh does not remove GOROOT, but you are correct that installing a new go version will not be captured correctly. The main reasons I lean towards not rerunning:

Performance, some hooks could be slow.
It forces hooks to be idempotent. I think generally it is good practice to make init hooks idempotent, but having them explicitly break if they are not idempotent could be bad UX.

Finally, once we wrap binaries with shellenv, it means we would need another solution for re-running init hooks, or just leave that responsibility to the user (which I don't think is that unreasonable)


contributing doc - redeux & how to rebuild the doc

I have had a second go at the contributing documentation, now that it is more accessible thanks to #10
turns out some of my initial concerns are still to be addressed
so I have restarted from scratch and put myself in a new potential contributor's shoes
and came across a few further glitches

the doc itself

the doc still does not address running the tests, which is one of the first things one would want to do
it does not either address rebuilding the doc itself
it could profitably mention the creation of a virtual env

more importantly, I could not find a way to rebuild the doc locally (more on this below)

about 1. : to illustrate all this you can take a look at this page here:
https://github.com/parmentelat/IKPLS/blob/contrib-doc/CONTRIBUTING.md
note: I was about to create a PR from that material, but refrained from doing so because I can  neither read nor write nor preview reStructuredText, so  I've had to move to markdown, which is maybe not what you'll want to do... regardless, the contents is what matters here anyways
about 2. : for rebuilding the doc, I had to mess with docs/Makefile like here
https://github.com/parmentelat/IKPLS/commit/3f9a8329ff2393a670e6842e76cd71ee59aec654
as I can't access the builds page on readthedocs, I can't say whether the builds pass over there but it feels unlikely ?

as an aside, since in #15 you mention running benchmarks, it may be worth giving the recipe in this doc as well

and oops I forgot to link the meta-issue
https://github.com/openjournals/joss-reviews/issues/6533

Hi @parmentelat
Thank you for the feedback, and thank you for the aid with the docs/Makefile.
I will address each of your points here:
1.

the doc still does not address running the tests, which is one of the first things one would want to do

This was actually addressed in CONTRIBUTING.rst in step 4 under the headline "You want to make some kind of change to the code base".
However, I admit that it was not very visible. Therefore, I have updated it to be more visible and put a more elaborate guideline under the headline "Run the test suite" in CONTRIBUTING.rst. Additionally, I updated the guidelines to use poetry which is also what the GitHub actions are using.

it does not either address rebuilding the doc itself

I have created a section named "Build the documentation" in CONTRIBUTING.rst to address this.

it could profitably mention the creation of a virtual env

Creating a virtual environment is not required for installation or usage of the ikpls package. Although, I agree using virtual environments is good practice, it really is up to a user whether or not they want to use them. Furthermore, setting up and managing virtual environments depend on the platform a user is working on - and there are many of these. There are resources available online for each of these platforms. As such, I believe a user is better off going to the primary source of information instead of me writing something that may be potentially be outdated in the future and which also has to be quite elaborate to accommodate all the possible platforms. With these points in mind, I urge you to reconsider this suggestion.
2.

about 2. : for rebuilding the doc, I had to mess with docs/Makefile like here
https://github.com/parmentelat/IKPLS/commit/3f9a8329ff2393a670e6842e76cd71ee59aec654

Thank you for catching this. I have changed the docs/Makefile and docs/Make.bat to use "." as the source dir instead of docs/source.

as I can't access the builds page on readthedocs, I can't say whether the builds pass over there but it feels unlikely ?

On readthedocs, the build actually passed perfectly in spite of the docs/Makefile not working as intended locally. I guess readthedocs uses something else to build the docs on their end. However, as I mentioned above, I have updated the Makefile, and the build still passes on readthedocs. You should be able to verify it with this badge: https://readthedocs.org/projects/ikpls/badge/?version=latest.

as an aside, since in https://github.com/Sm00thix/IKPLS/issues/15 you mention running benchmarks, it may be worth giving the recipe in this doc as well

I have added a "Benchmarking" section to CONTRIBUTING.rst to address this. It simply points the reader to paper/README.md.

Hi @parmentelat ,
I believe this issue is resolved with the changes mentioned in my previous comment in this thread and those we discussed over in #10 and #19 . If you agree, then we can close this issue.

agreed, thanks for this work, I appreciate the new layout, and believe the repo will be more readily usable for potential contributors


Intuition behind choice of input points, ball query radius, nsamples and spatial-stride

Dear @hehefan ,
From the train-msr.py file, I see the default values
input points = 2048,
ball query radius = 0.7,
nsamples = 32,
spatial-stride = 32
On a given point cloud frame that contains 2048 points, the farthest points sampled (FPS) i.e., 32 are sampled (smaller). Around each of them, a ball with a radius of 0.7 (bigger) is used to query 32 points (very small number).
I have a few questions to understand the setting.

Wouldn't the queried points (32) around the farthest point be very close to it since the overall object contains 2048 points(dense)?
What is the intuition behind choosing a bigger radius but querying only 32 points at each FPS point?

I suspect due to 2048 input points, but querying only 32 points around each of 32 farthest points, the points considered from a given frame at a time are limited to 32x32 i.e., 1024 points. And these points are clusters of 32 points around each of the 32 farthest points due to ball querying.
Please help me understand the intuition behind the design.
Thanks in advance.

Hi,
spatial-stride is the FPS down-sampling rate. This operation leads to 2048/32=64 anchor points.
For each anchor point, we search its neighbors within the radius(0.7).
Because points usually have different numbers of neighbours, within the ball query radius, we sample nsamples(32)  neighbors.
In summary, given a frame with 2048 points, we select 64 anchor points. For each anchor point, we sample 32 neighbors whose distances to the anchor point are less than 0.7.
Because points are significantly down-sampled,  we use a bigger radius to include more neighbours for each anchor point.
Best regards

Thank you @hehefan.
There will be a lot more than 32 points within the ball that are at a distance <= 0.7.
The CUDA code (of pointnet++) picks the nearest ones from the anchor point though this is a ball query and not a kNN query.
Your method would still work the same even if the radius was 0.2 (I will run this experiment).
Using a bigger radius alone will not fetch more neighbors unless the nsamples value is high. In your case, it is just 32.
Can you confirm if the queried points were picked randomly within the ball and not based on how near it is to the anchor point?

Hi,
To my understanding, the ball query ball_query_gpu.cu in PointNet++ searches neighbors from the first point to the last point in a cloud. If enough (nsample) neighbors are collected, the search stops. Therefore, the collected neighbors are related to their order in the cloud. Because point clouds are unordered and points are randomly selected in data preprocessing, we can consider the neighbor sampling to be random.
Best regards.


English Translations v1

First English Translations!

Probably my final fix for right now, it's ready!

@Potato1682

Some parts have not been translated.
Can I help you too?

Sure thing, this is only a v1 of translations, I will usually do waves of translating

It looks like we need to fix the conflict.

It looks like we need to fix the conflict.

where?

I think it's because I need write access to merge the pull request, I'm not sure.

You have edited the stable, but as you can see in Contributing, we're always editing develop.

You have edited the stable, but as you can see in Contribution guide, we're always editing develop.

Where can I go to fix that

It won't let me merge it to develop, wait I have an idea.

Merge your changes into develop of your forked repository. This requires creating a new PR, which creates conflicts, but can be fixed and merged into the latest source code.

Merge your changes into develop of your forked repository. This requires creating a new PR, which creates conflicts, but can be fixed and merged into the latest source code.

I can't pull it to development first though, idk how to use command line (CL)

Create a PR from stable to develop in your forked repository. There should be a link to display the git commands near "Fix conflicts".

Create a PR from stable to develop in your forked repository. There should be a link to display the git commands near "Fix conflicts".

I'm there, but where do I put these commands?

is there a server that uses this plugin, i want to see more

Do you have git? If not, you will need to do it from the installation.
Paste the git commands into your shell (Command Prompt).
You should be able to paste it by right-clicking at Command Prompt.

Do you have git? If not, you will need to do it from the installation.
Paste the git commands into your shell (Command Prompt).
You should be able to paste it by right-clicking at Command Prompt.

instaling right now

This isn't working

Can you move my branch to stable and then I will continue development in develop @Potato1682

you there?

I am going to refork under development due to it being easier.


Simplify class assignability check

I did this in the wrong project!  Did it now in the right one: https://github.com/camunda/camunda/pull/23172


⚠ ClamAV has degraded performance

In cd430eb, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 66 ms

Resolved: ClamAV performance has improved in 69573a1.


Use valid reusable workflow paths in example yml

Fix for #15480
The docs currently state:

Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the .github/workflows directory of a repository. Subdirectories of the workflows directory are not supported.

But the example yml then presents the path uses: ./.github/actions/my-action which doesn't follow the initial advice about location of workflow files.
Change is to use uses: ./.github/workflows/my-action to make example valid, but this is assuming the Creating a reusable workflow section is also accurate.

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@Layoric
Thanks so much for opening a PR! I'll get this triaged for review :zap:

Oops!  Good catch @Layoric - thanks for the fix!  👍


Opal links point to online casino website for opal.org domain

The https://opalrb.org should point to https://opalrb.com
You can find the issue on this page http://ruby-hyperloop.org/docs/components/docs/
How is it even allowed to have *rapware under a .org TLD ?!?

Now you get this

thanks... doc site is being redone... thanks for reporting

Wow - thanks for reporting that, I wonder how that happened!


Fix for self-registration link bug

Related Issue or Background Info

The self-registration links have never included PUBLIC_URL, which they need to be valid in deployed envs. Right now they are missing /app. This will fix that

Changes Proposed

Use the getUrl util to get baseUrl for self reg links

Additional Information

decisions that were made
discussion of tradeoffs / future work
complaints about how bad the code is

Screenshots / Demos
Checklist for Author and Reviewer
Infrastructure

[ ] Consult the results of the terraform-plan job inside the "Terraform Checks" workflow run for this PR. Confirm that there are no unexpected changes!

Design

[ ] Any UI/UX changes have a designer as a reviewer, and changes have been approved
[ ] Any large-scale changes have been deployed to test, dev, or pentest and smoke-tested by both the engineering and design teams

Content

[ ] Any content changes (including new error messages) have been approved by content team

Support

[ ] Any changes that might generate new support requests have been flagged to the support team
[ ] Any changes to support infrastructure have been demo'd to support team

Testing

[ ] Includes a summary of what a code reviewer should verify

Changes are Backwards Compatible

[ ] Database changes are submitted as a separate PR

[ ] Any new tables that do not contain PII are accompanied by a GRANT SELECT to the no-PHI user
[ ] Any changes to tables that have custom no-PHI views are accompanied by changes to those views
(including re-granting permission to the no-PHI user if need be)
[ ] Liquibase rollback has been tested locally using ./gradlew liquibaseRollbackSQL or liquibaseRollback
[ ] Each new changeset has a corresponding tag

[ ] GraphQL schema changes are backward compatible with older version of the front-end

Security

[ ] Changes with security implications have been approved by a security engineer (changes to  authentication, encryption, handling of PII, etc.)
[ ] Any dependencies introduced have been vetted and discussed

Cloud

[ ] DevOps team has been notified if PR requires ops support
[ ] If there are changes that cannot be tested locally, this has been deployed to our Azure test, dev, or pentest environment for verification

Deployed to test WITH the react router changes, confirmed that it works. Now that we have reverted, I will just include this change with the next attempt to upgrade react router


Refactor python steps in nmk-python plug-in -- Resolves dynod/nmk#142

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

Coverage data is based on head (ec80a50) compared to base (9d702e5).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          129       129
  Branches        17        17
=========================================
  Hits           129       129

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

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


Make radio and checkbox (option) labels editable again

Trello card

Closing this pull request because it doesn't seem to have all the change (there are waaaaay more changes than shown).
Will investigate.


[DROOLS-978] avoid to evaluate an agenda item in the eager list when an incremental compilation removed the corresponding rule

Looks good @mariofusco . +1 to merge.


If installed, skip setup screen

If the hub is already installed skip showing the setup screen and instead take the user to a dashboard.

This is no longer valid.


Fixed coding error near link 72643 for 2040 warm start

Hi Kyle,
I fixed the bug that prevent you from running 2040 warm start. I did it in a temporary branch because the network edits v1.3 branch has way more edits after you started the warm start. This branch will be deleted after merge. I will fix this bug in the final v1.3 network and v2 network, knowing when they are merged into dev, a conflict will happen. Please begin your 2040 warm start run with this fix.
Thanks,
Si

@Si-Shi should we close this? I assume the change was minor and you may have already repeated the fix in the 1.3 branch I just merged into dev. If not, I recommend branching off from dev now, re-fixing it, and then merging it in.
In other words let me know either:

dev is now good to go after I just approved the 1.3 PR into dev and I can delete this PR or
You need to redo this fix to the link layer now in dev and I should hold off on warm start runs.

@Si-Shi OK sounds good. I recommend deleting this branch (both locally and on github). I'll let you do that, though.


Binding a stream to collection property

This error occurs: error: cannot invoke 'bindTo' with an argument list of type '(CollectionProperty<Array>)'
I can do observeNext and replace, but that defeats the purpose slightly. Is there a way to do this?
let counterArray = Stream.sequence([[1, 2, 3],[4, 5, 6],[7, 8, 9]])
let va:Property<Array<Int>> = Property([])
//works
counterArray.bindTo(va)

let vac:CollectionProperty<Array<Int>> = CollectionProperty([])
// does not work
counterArray.bindTo(vac)

This is not supported with ReactiveKit 3.


Another r.row bug

Gist:
https://gist.github.com/thelinuxlich/7d7acfbcba8cc39fcf60
Error:
https://gist.github.com/thelinuxlich/00661fcd1cec7a91ec56
On RethinkDB Web UI it works

Shipped in 1.16
Thanks!