Fix for 'No geofence has been added to this request' OnConnected

only call addfences if fences are present (this method is called from OnConnected).

Stack trace from app crash:
java.lang.IllegalArgumentException: No geofence has been added to this request. 	at com.google.android.gms.common.internal.zzx.zzb(Unknown Source) 	at com.google.android.gms.location.GeofencingRequest$Builder.build(Unknown Source) 	at com.google.android.gms.location.internal.zzf.addGeofences(Unknown Source) 	at com.cowbell.cordova.geofence.AddGeofenceCommand.ExecuteCustomCode(AddGeofenceCommand.java:52) 	at com.cowbell.cordova.geofence.AbstractGoogleServiceCommand.onConnected(AbstractGoogleServiceCommand.java:72)
referenced https://github.com/domoticz/domoticz-android/blob/9ea23c298abbc8ffe64d327fb7ec09edf021f602/app/src/main/java/nl/hnogames/domoticz/Utils/SharedPrefUtil.java#L757 for similar code


Post-publication styling changes

Pull request overview
I've made a few modifications largely around the cosmetics of the dashboard:

using accordions to improve layout on the pupil page
switching reactable tables in place of datatables
bringing in the shinyGovstyle cookie banner

The above have all be reviewed on the development deploy of the dashboard by @artonbaleci and Liam, and a few small updates have been made based on their feedback.
Largely as part of the above this has meant some underlying changes to the nuts and bolts of the dashboard:

using bslib and phasing out shinydashboard
updates to the css related to the bslib switch
bringing in dfeshiny package
setting up some basic UI tests with shinytest2

Pull request checklist
Please check if your PR fulfils the following:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Tests have been run locally and are passing (run_tests_locally())
[x] Code is styled according to tidyverse styling (checked locally with tidy_code())

Changes approved by team via e-mail


no pellet in dashboard only wood - unica nobis fire

I apologize.. perhaps I expressed myself badly in the previous message.
Today I turned it on remotely (obviously in pellet mode) but in the dashboard I always see wood as the setting, shouldn't I see pellets? Am I doing something wrong or is it stuck?
I have already tried restarting Home Assistant.
thank you so much
well, not so if I explained myself.
In the image I should see pellets and no wood, but instead I always see wood (at the moment pellets are burning)

Please send a diagnostics file from when the stove is burning pellets.

forgive my ignorance.. where do I find the file you want me to send you?
Now it s burning pellets

Go to the integration in settings. Click your device and then on download diagnostics.

config_entry-aguaiot-a475d1b727a4297411d5fb74935c487a.json.txt.json

@jipem01 Is the switching of the climate entity between modes functioning correctly for your stove? I am currently checking on power_wood_enable but now it seems I should check on real_power_wood_enable.

..i dont  undestand..it s a my setting or other?

Download the newest version (0.3.0), should be fixed there.

I confirm the bug.
I've created a templated sensor to watch mode and it stay all the time to wood (i've just checked history)
Didn't notice before as I use mainly wood.

Another questione...my remote control has sensor temeperature...i whact it and is 99 grades temperature..it is a problem of remote control or may be a problem of compatibility agua iot?

@vincentwolsink  i confirmed, solved with 0.3.0.
@merlino1975 if the remote display 99 you should check with your stove resseller. HA and micronova plugin should have no impact on it.

yes...I just do it...I called my dealer....but...I don't know...everyone says what is useful to them...well...now...it's so complicated . ..I try to use the wood mode..but often when the wood runs out the "wood is running out" alarm doesn't sound and the pellets start burning again...
I think I have a problem with the stove.... I hope to resolve it under warranty... but it's hard
I tried turning off home assistant (obviously also agua iot) to check if there was a possibility that some interactions could create conflicts. But it seems to behave the same way


Rename master branch to some other naming

Following the previous issue, we should also think about remaining master branch to something other like main.
Suggestions are welcomed for the naming ofc.
Some references:
https://dev.to/_garybell/why-github-renaming-master-is-good-4b64/
https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/
https://www.cnet.com/news/microsofts-github-is-removing-coding-terms-like-master-and-slave/

What with WP Core still using SVN, I have a feeling that trunk would be an intuitive alternative name for master to consider for this repo.
For the practical side of things:

Follow the steps outlined here: https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
Adjust the Travis script to make sure any conditions for the stages and such match against the new name.
Adjust the references in the badges in the Readme.
Do a repo-wide search to see if there are other references which need adjusting.

Based on this proposal in core, I'd recommend we stick with trunk: https://make.wordpress.org/core/2020/06/18/proposal-update-all-git-repositories-to-use-main-instead-of-master/

I've just added this to the 3.0.0 milestone as this could be considered a breaking change for those people using git clone or non-version based Composer restraints, like dev-master.
I suggest we hash out the name in the near future and make the actual change just before the 3.0.0 release and annotate it clearly in the Changelog.

As we're getting closer to being able to release 3.0.0, I think we need to hash out what the new name for the branch will be so it can be renamed ahead of the release (just before, see comment above).
For the actual renaming, we can use the GH native branch rename functionality (wasn't available at the time the issue was opened, but is now).
Options:

main - Pro: used a lot elsewhere and allows for auto-complete of the branch name on the CLI.
stable - Pro: goes well together with the develop branch, clear indication what's what.
trunk - Pro: used by Core and other WP projects. Con: confusing as trunk is used by Core for the develop branch, not for the stable release branch.

Are there other options we should consider ?
Opinions welcome.

I'm always for main as that's the most used naming for a production-ready branch in almost all the projects I know of.

main is fine with me.


Switches from 1 minute to 9 minutes. Same with hours or days.

please help

Sadly this project is incomplete and currently abandoned. I never got around to fixing the timing bugs and eventually lost interest.

Sadly this project is incomplete and currently abandoned. I never got around to fixing the timing bugs and eventually lost interest.


AUI-1995 Source formating

Just started reviewing :) :octocat: Sent from GH.

Just started reviewing :) :octocat: Sent from GH.


Missing keys: ['pos_embed', 'pos_embed_temporal']

[03/18/24 05:16:36] INFO     colossalai - colossalai - INFO:
/home/aiscuser/.conda/envs/opensora/lib/python3.10/site-packages/colossalai/initialize.py:6
7 launch
INFO     colossalai - colossalai - INFO: Distributed environment is initialized, world size: 1
./pretrained_models/t5_ckpts/t5-v1_1-xxl
Loading checkpoint shards: 100%|██████████████████████████████████████████████████████████| 2/2 [00:24<00:00, 12.07s/it]
Missing keys: ['pos_embed', 'pos_embed_temporal']
Unexpected keys: []

What is the cuda version of your machine? I also encountered the same problem.

12.0

What is the cuda version of your machine? I also encountered the same problem.

12.0

I did not debug and ran it directly using the command. Have you debugged it?

What is the cuda version of your machine? I also encountered the same problem.

12.0

I did not debug and ran it directly using the command. Have you debugged it?

No. I ran it directly using the command too. I have no idea how to debug

The same Q. It drives me crazy! What a difficult project to reproduce!

The same Q. It drives me crazy! What a difficult project to reproduce!

这个不是bug，代码里有输出Missing keys: ['pos_embed', 'pos_embed_temporal']的语句

The same

Have anyone solved this problem?

Have anyone solved this problem?

别看中文的介绍，他写错了。  看英文的

Both the pos_emd are not learnable. Hence it is expected that they are not in the saved checkpoints.

[03/18/24 05:16:36] INFO colossalai - colossalai - INFO: /home/aiscuser/.conda/envs/opensora/lib/python3.10/site-packages/colossalai/initialize.py:6 7 launch INFO colossalai - colossalai - INFO: Distributed environment is initialized, world size: 1 ./pretrained_models/t5_ckpts/t5-v1_1-xxl Loading checkpoint shards: 100%|██████████████████████████████████████████████████████████| 2/2 [00:24<00:00, 12.07s/it] Missing keys: ['pos_embed', 'pos_embed_temporal'] Unexpected keys: []

No worry. This is not an error and is expected. So just ignore this.


feat: Add SchedulerTask which will be notified once cancelled.

Motivation:
refs: https://github.com/apache/pekko/issues/1579
Tests is still missing

I'm not sure that we could add this in a v1.1 patch. I'd prefer if we delay this till v1.2.0.

I'm fine with this, but as the current method is add as a default method, it should be fine too.

I'm quite worried that these tests will be brittle in CI. The CI agents can often suffer from performance issues and tests can take longer to run than on laptops, etc.


New function for FieldRef: DataClassification :=   FieldRef.DataClassification()

Feature request for GDPR general improvement
This is not an issue but an improvement for more general GDPR functionality
Access DataClassification with AL
Like there is already Class :=   FieldRef.Class()
returning the fields class I would like a function to be added to the FieldRef data Data Type, e.g.:
DataClassification :=   FieldRef.DataClassification()
Return Value:
 -   DataClassification
 -   CustomerContent
 -   EndUserIdentificationInformation
 -   AccountData
 -   EndUsePseudonymousIdentifiers
 -   OrganizationIdentifiableInformation
 -   SystemMetadata
 -   ToBeClassified
This makes it possible to take customer specific actions on fields that have a special DataClassification
:alembic:
https://eugdpr.org/

Thank you for the suggestion @louagej !

Hi! Thank you for your suggestion. We are working on focusing the activity in this repository on addressing issues related to the AL development tools.
As this issue appears to require changes across multiple areas of our product and the runtime, we recommend that you post this on our Ideas forum at aka.ms/BCIdeas, or vote up the idea if its already there.
We are constantly monitoring top ideas and will consider them for a future release.


Illustrate subresource method usage in DropwizardResourceConfigTest

This adds a test case to DropwizardResourceConfigTest that ensure that subresource methods are supported. This functionality was called into question in #1716.

Actually, I was able to reproduce the error, I'll have a PR up in a couple mins.

Coverage remained the same at 82.298% when pulling df1cf7c32c497c01519dba8fcdcdc3e0f60b62d0 on evnm:dropwizard-jersey/add-subresource-test into 68b1af93bf8bbed5e84751de0b9dac4665131506 on dropwizard:master.


Update the references to federation control plane images/binaries in the federation admin guide.

thanks, LGTM.
Not sure if master is the right branch to change or is there a 1.4 branch.
Maybe @pwittrock knows?

@jaredbhatti Where should 1.4 docs go?

We should start a 1.4 branch.
On Aug 1, 2016 11:45 AM, "Phillip Wittrock"<EMAIL_ADDRESS>wrote:

@jaredbhatti https://github.com/jaredbhatti Where should 1.4 docs go?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/pull/936#issuecomment-236670085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF3LgsKjH9q7JTEXwMCkDSUforCXMrVgks5qbj7VgaJpZM4JZ3VB
.

@jaredbhatti Should I send a new PR (with the changes here) targetting the 1.4 branch?

@madhusudancs If this is for a feature being developed for 1.4, the PR should go to the 1.4 branch.

@pwittrock Sure, thanks.
Superseded by #945. Closing this PR.


SSR Support?

Ive tried to use this plugin within my SSR bundle config & It seems to be not supported on the server side with this error:-
window.__REACT_ERROR_OVERLAY_GLOBAL_HOOK__=window.__REACT_ERROR_OVERLAY_GLOBAL_HOOK__| {},window.__REACT_ERROR_OVERLAY_GLOBAL_HOOK__.iframeReady=function ({re=!0,te=!1,ve()},"production"===process.env.NODE_ENV&&console.warn("react-error-overlay is not meant for use in production. You should ensure it is not included in your build to reduce bundle size.")}])})); ReferenceError: window is not defined at Object.<anonymous> ($PATH/node_modules/react-error-overlay/lib/index.js:1:216)

I am sorry, I don't actively maintain this project. Feel free to submit a PR to fix it, else I can't help.


Reuse frames in profile

Currently we just insert every frame in the profile, however we can lower the payload size by not doing that and reusing identical frames (which in most applications are the first few frames of every stack) making the payload a lot smaller. This saves on data we need to transmit saving on ms spend sending to Sentry and saving Sentry on storage.
From some googling for benchmarks I found that md5(serialize($frame)) would be a good tradeoff between correctness (collisions) and speed.
As a very non-scientific test I deployed this to a production app and looked at similar length (time) and same amount of sample profiles of the same transaction and saw a reduction from 145 KB to 44 KB when downloading the profile JSON from the Sentry UI which I thougt was pretty neat 😄

Is there a measurable CPU overhead with this approach?
But I would imagine that the saving in data sending would cover that...

That makes a lot of sense, thanks for linking to another implementation, didn’t even look for one… will take a look at the stack dedupe too, makes sense!

Thanks @phacops and @armcknight for the suggestions, implemented stack re-using too (same method).


Update dircolors.vim

Fix xterm bug wich replace first character with 'g' when editing file

Coverage decreased (-0.01%) to 62.257% when pulling 5c4971293f9d9f02a8a05f5eda26badc9c7e034b on DarkStar1973:bugxterm into 13ddc5c35921efa69e980284117b6db6465e019c on vim:master.

please contact the syntax script maintainer and discuss the issue with him. Thanks.

(I'm the maintainer)
This doesn't look right to me. First of all that function should only be called in GVim, not in xterm, since it checks has('gui_running'). And second, the r and b values don't make sense at that point in the code – they are only used by the preceding loop. The values that the loop in question sets are greyscale values where all of the components are supposed to be the same (I guess that part could have benefited from a comment).
Are you saying that the code is running for you even in xterm? And if yes, could you please give some more information about how exactly this can be reproduced?

Ok, i explain.
Excuse me i'm french, so my english isn't perfect.
Me and colleague at work have a bug with vim since ubuntu xenial (same with debian sid).
When we open a file, after a short delay the first character is replace by the character 'g', with TERM=xterm.
So i try to find why. And when i see your code i was thinking you made a mistake (ggg instead of rgb). But with this patch, i don't have the bug of first character replace by g.

Hi DarkStar1973,
2016-5-31(Tue) 16:47:02 UTC+9 DarkStar1973:

Ok, i explain.
Excuse me i'm french, so my english isn't perfect.
Me and colleague at work have a bug with vim since ubuntu xenial (same with debian sid).
When we open a file, after a short delay the first character is replace by the character 'g', with TERM=xterm.
So i try to find why. And when i see your code i was thinking you made a mistake (ggg instead of rgb). But with this patch, i don't have the bug of first character replace by g.

What version of Vim are you using?
What terminal emulator are you using?
When you using Vim version from 7.4.757 to 7.4.769, A problem occurs that you have reported.
Please see the following threads.
Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'
https://groups.google.com/d/msg/vim_dev/JB0oocqMel8/ml6ayeSmLnsJ
FS#45535 - [vim] latest version inserting g character upon opening file looks still broken
https://groups.google.com/d/msg/vim_dev/_Q26KGKB5nk/YtUM0QA9aFMJ
Patch 7.4.757
https://groups.google.com/d/msg/vim_dev/LLGjKaEzNUY/z8WvrFoxtD0J
Patch 7.4.770
https://groups.google.com/d/msg/vim_dev/BTuBkjUcoUw/KHtRSyXiRk8J
--
Best regards,
Hirohito Higashi (a.k.a. h_east)

looks invalid, closing. If you still have the problem, please send a mail to vim-dev list, stating your environment (terminal, vim version) and we'll try to reproduce/fix it


Remove the dependency from vimbufsync

Like this fork of Coquille had done. See this commit: https://framagit.org/tyreunom/coquille/commit/3323c46cfa521395c88ece0b854bbdc9f8399672

One potential problem I see with that method is it assumes that the change happened at the cursor, which isn't always the case (e.g. call append(0, ["abc"])). Using TextChanged does seem like a good solution though if I can find a way of detecting where a change actually occurred. Maybe :changes could help?


The interface overview should show a terminal hint

The interface overview doesn´t show the terminal. I suggest to also show a hint to open the integrated terminal.

// fyi @chrisdias @seanmcbreen

A fake terminal, actually opening a terminal might be a bad idea as on Windows a notification will pop up and on some environments the terminal will immediately close (like if a sysadmin sets $SHELL to /bin/false. There's no way of detecting if it will fail ahead of time.

Adding a hint (no fake terminal for now).


Remove docs/ output from the source code

Problem
I've added the generated static html documentation from mdbooks in the source code to release fast. This is highly inconvenient as it pollutes the pull requests reviews with conflicts. Those are easy to deal with, by cleaning docs and running mdbooks build, but are still disturbing.
Solution
Create workflow to build the documentation in a separate repository, handled by github pages.
Alternatives
Any trick that would make the pages being built and presented the same way it is now, without storing the html result in the source code repo would be ok.
Additional context
Github pages is convenient, it would be better to keep using it.

I think it is better to keep the doc, part of the repo.
By the way we can move the pictures at the root of the project into a images folder. Root will be cleaner.

Do you mean keeping the html generated doc ? Don't you think it's a mess to have it there ?
I was not thinking about moving the docs_src folder, but just build the docs one with github actions, to not include the resulting files in the git history.


Annotate input properties

Hi!
Now the plugin will print something like
* What went wrong:
A problem was found with the configuration of task ':generateRustDocHighlightingLexer'.
> No value has been specified for property 'targetClass'.

if the user forgets to specify the property, instead of silently specifying wrong task outputs.

Wait a second, there's https://docs.gradle.org/3.3/javadoc/org/gradle/api/tasks/InputFile.html which can simplify things a tiny bit!

Ah, InputFile won't work nicely because it requires the user to type file("src/foo/bar") instead of just "src/foo/bar".


Grading: Filtering grading table by group does not work

Typing a group in the grading search bar does not filter correctly:

Expected: filters entries by anything that matches the search query
Actual: Does not seem to check the group field for matching entries (resulting in no results found assuming the search query is only present in the "Group" column)

Clicking a group from a table entry does correctly add (and apply) the filter, though:

@RichDom2185 We aren't able to replicate this issue, but it may just be an unclear issue. Could you check if this still exists and if so, could you give us a more detailed explanation of the error?

@RichDom2185 We aren't able to replicate this issue, but it may just be an unclear issue. Could you check if this still exists and if so, could you give us a more detailed explanation of the error?

I just tested again, seems to be fixed now. Probably some bug with the library that fixed itself in one of the commits since this issue was created. Thanks and sorry for the trouble!
I'll proceed to close the issue now.


chore: add bump:version script

Description

update 1.0.0 version of package in package.json
add bump:version script

I suggest fix:  otherwise release will not be triggered, and bump in package.json will not take place, and bump in projects that use this package will not take place

@derberg which projects? I update version in package-lock.json manually,

which projects?

sorry, I understood from past conversations that your requirement for problem to be completed is to use it in some project.
anyway, I guess you can merge then

@magicmatatjahu feel free to merge when you are ready

@derberg

sorry, I understood from past conversations that your requirement for problem to be completed is to use it in some project.

Yeah, we tested that package but using transformed lib folder in the server-api.

/rtm


Add Radium Reforged mod

Add Radium Reforged v0.8.2. This mod makes a number of general performance-oriented modifications to various parts of the vanilla code-base.

We already use Canary, another fork of the Fabric mod Lithium, and these two mods conflict. Some people report regular mod conflicts when using Radium Reforged, so we'll stick with Canary for now.


Merge Uat ke Master 10 Nov 2017

Coverage decreased (-0.009%) to 75.549% when pulling eaef922363b71bbdaf60d2f958e03aa2e2ca4dea on uat into cfaa3031973b40caee169ba7b17debede443ad19 on master.

Coverage increased (+0.07%) to 75.631% when pulling 7336f64cf67869251ad36cde06f6f40bc017c670 on uat into cfaa3031973b40caee169ba7b17debede443ad19 on master.

Coverage increased (+0.07%) to 75.631% when pulling c1cfae1a3eebe842d6879d31461abae119578747 on uat into cfaa3031973b40caee169ba7b17debede443ad19 on master.

Coverage increased (+0.3%) to 75.827% when pulling e7b06b9e10177a2afe0431761492a27e9755eaa6 on uat into cfaa3031973b40caee169ba7b17debede443ad19 on master.

Coverage increased (+0.3%) to 75.827% when pulling 96d033a61bd08abf9f22b32b8b6256e5765d7e4c on uat into cfaa3031973b40caee169ba7b17debede443ad19 on master.

Coverage increased (+0.3%) to 75.879% when pulling 74c441b686abee16a28bed67bb3039736dd070fd on uat into cfaa3031973b40caee169ba7b17debede443ad19 on master.


[ffi] Add support for abi-specific integer sizes

We should consider exposing our Abi enum and allow users to have ABI-specific types. This would avoid us having to continuously increase the set of types we support in the core dart:ffi library. It would also allow a ffi bindings generator to produce ABI agnostic bindings.
We would support the primitive integer, double and pointer types in dart:ffi anything else can be user defined.
One option would be using non-function type aliases (see https://github.com/dart-lang/language/issues/65), which could look like this:
typedef WChar = AbiSpecificType<Int8, Int16, ...>;

class MyStruct extends Struct {
  @WChar()
  int char;
}

void foo(Pointer<WChar> chars);

where dart:ffi would have
class AbiSpecificType<ABI1, ABI2, ...> {}

When the VM compiles code it will know which ABI it runs on and can use the corresponding type from the instantiated AbiSpecificType.
One downside here is that we would have a hard time adding more ABIs in the future (though in reality we rarely add new architectures / operating systems / compilers)
/cc @dcharkes wdyt?

@dcharkes There is actually a way to make this more extensible to future ABIs:
abstract class WChar implements LinuxArmHardFp<Int8>,
                                LinuxArmSoftFp<Int16>,
                                WindowsX64FastCallAbi<Int32>,
                                ... {}

Adding a new Abi would then just add a new class to dart:ffi which is not breaking compatibility. When running the program on an Abi that WChar was not implemented the VM could throw an exception (or a compile-time error).

I like it! We might still need to make it extend AbiSpecificInteger or make all those individual ABIs do that, in order to be able to have Pointer<WChar> and be able to store/load from it through extension methods.
This also means we would not have to wait on generalized typedefs (or result to subtyping) to be able to reuse the type in multiple places.

There's also a design choice: In C code two typedefs are compatible and assignable to each other. If we do the generalized typedef approach we will have the same behavior, if we go with a separate class then one needs to explicitly cast in Dart (but not in C).

True, if the one package decides to call wchar_t WChar and another package decides on WCharT they wont match.
Maybe we should preempt that by adding some of those to package:ffi, and have people make PRs for adding more common types.

We also need something for structs. We cannot merge the two concepts in one Dart type, because the int loads/stores only work for ABI-sized integers, and the struct field loads/stores only work for structs.

Not sure how common it is in C to have a typedef to be integer typed on one platform and non-integer on another. Maybe that is not worth adding support for.

abstract class WChar implements LinuxArmHardFp<Int8>,
                                LinuxArmSoftFp<Int16>,
                                WindowsX64FastCallAbi<Int32>,
                                ... {}

Adding a new Abi would then just add a new class to dart:ffi which is not breaking compatibility. When running the program on an Abi that WChar was not implemented the VM could throw an exception (or a compile-time error).

That looks pretty great.

True, if the one package decides to call wchar_t WChar and another package decides on WCharT they wont match.
Maybe we should preempt that by adding some of those to package:ffi, and have people make PRs for adding more common types.

Yes, these really should be provided by the Dart project in one form or another. You'd want to avoid the situation with e.g. Java JNA when there's a bunch of different definitions of the same common types (e.g., ssize_t), and nobody knows which type they ought to be using.

@mkustermann The typedef solution does not work for struct fields (annotation constructor calls cannot have type arguments), so that solution also requires subtyping.
I've prototyped three API variants in https://gist.github.com/dcharkes/8d41b7def9bf82c74bf0b7f8a1d66a6c.
@lrhn @eernstg Any feedback from a language design point of view on the possible APIs?

Just to make sure we are considering this. Original FFI Vision document "dictionary" based portability design. I think we should consider going the same way instead of trying to use types to express things which are not types (this makes it to C++esque). More concretely we could use something along the lines of:
enum Os { Linux, Windows, MacOS }
enum Cpu { X64, IA32, ARM32, ARM64 }
enum FP { Soft, Hard }

class IfAbi {
  final Os os;
  final Cpu cpu;
  final FP fp;
  const IfAbi({this.os, this.cpu, this.fp});
}

class Typedef {
  const Typedef(Map<IfAbi, Type> mapping, {Type default_});
}

@Typedef({
  IfAbi(os: Os.Linux, cpu: Cpu.X64): Int64,
  IfAbi(os: Os.Windows, cpu: Cpu.X64): Int32,
}, default_: Int32)
abstract class WChar {}

Similar approach can be taken to ABI specific structure layouts.

I like @mraleph's approach, but I'm wary about using enums for something which isn't naturally bounded. There are more than three operatings systems, and more than four CPUs. We might not support them yet, but baking the list into our libraries makes it harder to expand for third-party users. If they make the SDK compile on FreeBSD on PowerPC, they would still have to edit all the right places to make it recognizable. (Does X32 count as a CPU?)
So, I think I'd rather use strings. Maybe skip the IfAbi class too, and allow free-form patterns:
@Typedef(Int32, {
   {os: "linux", cpu: "x64"}: Int64,
   {os: "windows", cpu: "x64"}: Int64,
   {os: "bsd", cpu: "power" : Int64
})
...

Then there'd be some way to figure out the current configuration, and perhaps even override it.
Maybe allow -Dffi.os=windows to override the os detection for testing.
(On the other hand, I don't want to introduce a new micro-language for specifying constraints like "osVersion": "<10", which is where this could end if taken too far).

Annotations work, yes. Not sure why I wasn't thinking of them.
One downside is that one cannot enforce the constraint that all of the possible native types for the typedef should be _NativeIntegers. In case of WChar we want to ensure it is an integer type, so we can write
class Foo extends ffi.Struct {
  @WChar
  int character;
}

I guess if we wanted to surface this we would need to have the special analyzer + CFE logic to issue additional compile-time errors based on examining the evaluated typedef constant annotation.
There's also the question whether we want to support mixed type definitions (e.g. typedefs where it's a pointer on one OS and integer on OS). The types in Dart would then be dynamic I assume and the program has to test abi at runtime and do a dynamic cast (In C code accessing such fields would be if/def'ed out)

One downside is that one cannot enforce the constraint that all of the possible native types for the typedef should be _NativeIntegers.

It is true that we would not be able to enforce this requirement with just through normal Dart typesystem.
But in any approach there would need to be some logic somewhere actually evaluating what WChar stands for - that logic can do enforcement of type consistency.
This unfortunately means we would need analyzer changes - which maybe otherwise would not be required.
I also realised that
class Foo extends ffi.Struct {
  @WChar
  int character;
}

would not actually work out of the box in either approaches. You need to do:
@Typedef({...})
class WChar {
  const WChar();
}

@WChar()
int character;

Which is a bit of mouthful - but I think the best we can get now. If only we could use annotations  on function type parameters, then we could just go for:
const WChar = Typedef({...});

But this approach sadly does not work with our approach to the NativeFunction<...> type.
@lrhn

So, I think I'd rather use strings. Maybe skip the IfAbi class too, and allow free-form patterns:

My original design was using simple language for conditions - but I agree that that would be too much. The idea behind using IfAbi was to make it self documenting. Using maps as conditions is an interesting variation, though one would have to write:
// Keys need to be strings
{'os': "linux", 'cpu': "x64"}: Int64

// Alternatively we could have markers
enum AbiKey { os, cpu, fp }
{os: "linux", cpu: "x64" } // Map<AbiKey, String>

Abi-specific types use
Note that the ABI-specific types also need to extend NativeType in order to use them in function signatures, and that ABI-specific integer types need to extend AbiSpecificInteger in order to be able to use them in loads and stores.
extension AbiSpecificIntegerPointer on Pointer<AbiSpecificInteger> {
  int get value => 0;
  void set value(int value) {}
  int operator [](int index) => 0;
  void operator []=(int index, int value) {}
}

In short, the user-defined types and consts need to work in:

Pointer type arguments
native function signatures
struct field annotations
loads / stores (for integers)
field loads / stores (for structs #42816)

Whether the definition per architecture is defined as type arguments, const fields, or annotations does not matter too much for that functionality.
Abi-specific types definition
Using types, const fields, or annotation matters for how much manual checking (with manual error messages) we want to add.
It also matters for whether we have an open-world vs closed-world assumption, and whether we require the user defining the type to define it for all known Dart target ABIs. I see three options here:

Closed-world, user has to define all types:

We know all types are provided. (Though, the user might fill in garbage for ABIs he does not know about, causing segfaults.)
We need to do a breaking change when we add a target ABI. Or as @lrhn mentioned when someone else targets Dart to a new ABI.
We can enforce this without extra rules in the type system.

Closed-world, user can define types for a subset of target ABIs:

Trying to run your FFI code on a different target ABI might cause compile errors because of missing typedefs.
We error on target ABIs we don't know about, preventing typos in the definition. (Using enums or types helps here.)
Anyone extending Dart to a new target ABI would need to extend the closed-world.

Open-world, user can define types for a subset of target ABIs:

Same, but we don't error on unknown ABIs.
This is fragile, a mistype of target ABI that the user is not testing on will go unnoticed.

Hello.
Interested to know if there is any work going on this ?
This is a big issue currently for binding to a C API using types with different sizes regarding the target architecture.
Thanks

Offline discussion with @mkustermann earlier: We should go for open world, to avoid breaking changes when ABIs are added.
As for an API, I've prototyped const objects as keys in the mapping used in annotations (not types or strings as suggested earlier in the thread). @lrhn wdyt about the API below?
In dart:ffi:
/// Application binary interface.
///
/// The Dart VM can run on a variety of [Abi]s.
class Abi {
  /// The operating system of this [Abi].
  final _OS _os;

  /// The architecture of this [Abi].
  final _Architecture _architecture;

  external factory Abi.current();

  const Abi._(this._architecture, this._os);

  @override
  String toString() => '${_os.name}_${_architecture.name}';
}

const androidArm = Abi._(_Architecture.arm, _OS.android);
const androidArm64 = Abi._(_Architecture.arm64, _OS.android);
const androidIA32 = Abi._(_Architecture.ia32, _OS.android);
// ...

/// The supertype of all [Abi]-specific integer types.
///
/// [Abi]-specific integers should extend this class and annotate it with
/// [AbiSpecificIntegerMapping] to declare the integer size and signedness
/// for all [supportedAbisOrdered].
///
/// For example:
///
/// ```
/// /// Represents a `uintptr_t` in C.
/// ///
/// /// [UintPtr] is not constructible in the Dart code and serves purely as
/// /// marker in type signatures.
/// @AbiSpecificIntegerMapping({
///   androidArm: Uint32(),
///   androidArm64: Uint64(),
///   androidIA32: Uint32(),
///   androidX64: Uint64(),
///   fuchsiaArm64: Uint32(),
///   fuchsiaX64: Uint64(),
///   iosArm: Uint32(),
///   iosArm64: Uint64(),
///   linuxArm: Uint32(),
///   linuxArm64: Uint64(),
///   linuxIA32: Uint32(),
///   linuxX64: Uint64(),
///   macosArm64: Uint64(),
///   macosX64: Uint64(),
///   windowsIA32: Uint32(),
///   windowsX64: Uint64(),
/// })
/// class UintPtr extends AbiSpecificInteger {
///   const UintPtr();
/// }
/// ```
class AbiSpecificInteger extends NativeType {
  const AbiSpecificInteger();
}

/// Mapping for a subtype of [AbiSpecificInteger].
///
/// See documentation on [AbiSpecificInteger].
class AbiSpecificIntegerMapping {
  final Map<Abi, NativeType> mapping;

  const AbiSpecificIntegerMapping(this.mapping);
}

User code:
/// Represents a native unsigned pointer-sized integer in C.
///
/// [UintPtr] is not constructible in the Dart code and serves purely as marker in
/// type signatures.
@AbiSpecificIntegerMapping({
  androidArm: Uint32(),
  androidArm64: Uint64(),
  androidIA32: Uint32(),
  androidX64: Uint64(),
  fuchsiaArm64: Uint32(),
  fuchsiaX64: Uint64(),
  iosArm: Uint32(),
  iosArm64: Uint64(),
  iosX64: Uint64(),
  linuxArm: Uint32(),
  linuxArm64: Uint64(),
  linuxIA32: Uint32(),
  linuxX64: Uint64(),
  macosArm64: Uint64(),
  macosX64: Uint64(),
  windowsArm64: Uint64(),
  windowsIA32: Uint32(),
  windowsX64: Uint64(),
})
class UintPtr extends AbiSpecificInteger {
  const UintPtr();
}

That looks horribly verbose for the user. Will package:ffi have this UintPtr declaration, or will users have to write it themselves?
You say that the ABI should be open, but it should match supportedAbisOrdered? Is that "open" in some sense, or is it simply all combinations of architecture and OS (themselves closed enums?) that the dart:ffi library supports?
(If so, if someone ports Dart to another architecture/OS and extends supportedAbisOrdered, it won't help people who have already written the large map annotation above.)
Could the Abi class contain a "default integer size" as well, so:
const androidArm = Abi._(_Architecture.arm, _OS.android, _IntegerSize.bits32);
const androidArm64 = Abi._(_Architecture.arm64, _OS.android, _IntegerSize.bits64);
...
const fucsiaArm64 = Abi._(_Architecture.arm64, _OS.fucsia, IntegerSize.bits32);
...

and you only have to explicitly write a type for AbiSpecificIntegerMapping when the size differs from the default?

Thanks for your input @lrhn!
Some notes from our discussion:

We introduce an Abi concept that we can reuse. We start with an opaque one with the 18 const instances. This way it works a bit like an enum.

We use a Map<Abi, NativeInteger> rather than 18 named parameters for AbiSpecificIntegerMapping. The downsides are extra { and } on the use sites, and no editor completion. However, the upsides are that the keys refer to the Abi concept, and that if we ever add Abis it is in one place instead of many. (Also, users will likely copy-paste the example in the comment, which contains all the keys of the map.)

Verbosity. This approach is verbose. But we expect to land 5-10 ones in package:ffi and have users maybe write one or two in their own code.

We dismissed the idea of a default value and only specifying the Abis deviating from that, because if the default is wrong, end users will get segmentation faults instead of useful exceptions that a mapping is missing.

Open-world: We do not error out on missing Abis at compile time, but throw at runtime when running on said Abi. That way adding new Abis is not a breaking change.

We dismissed using strings as keys instead of const instances. That would allow users to add mappings for Abis that are not part of dart:ffi yet. But it would also lead to typo's not being spotted until users using it on an Abi that is then all of a sudden missing.

const supportedAbisOrdered -> static const Abi.values.

Let me know if I missed anything.


DefaultEncoder.canonicalize() does not properly decode percent-encoded values.

Junit test:
	@Test
	public void testESAPIPercentEncoding() {
		String input = "%E2%84%A2";
		String expected = "™";
		Encoder e = ESAPI.encoder();
		assertEquals(expected, e.canonicalize(input));
	}

Hello,
I think this issue should be move to esapi-java-legacy (version 2.x) issue tracker. This repository is ESAPI version 3.x project which is under development. Just close this issue and open a new one in https://github.com/ESAPI/esapi-java-legacy/issues for ESAPI team to be able to fix it

Just noticed this again @xeno6696 -- Did you open this issue for ESAPI/esapi-java-legacy? If so, I will close it here.
Thanks,
-kevin

This one was opened against the wrong project.


[ENH] Compaction manager

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

This PR adds a compaction manager that gets a list of collections to compact and orchestrate the execution of compaction tasks.
It uses FuturesUnordered to await the compaction tasks and allow them to run in parallel.
We will add retry and timeout in follow up PRs.

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

@HammadB I am merging this PR for now. Happy to address review comments in future PRs. I have tested with unit tests and local integration tests.


fix: bump auth-js to v2.66.1

What kind of change does this PR introduce?

Changelog - https://github.com/supabase/auth-js/releases/tag/v2.66.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

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

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
99

Relevant Lines:
129

💛  - Coveralls


fix(make_entry): path display truncates directory when grouped = true

Fixes regression bug related to #208.
When grouped = true, the entries passed to make_entry don't have a os separator at the end.
This was resulting in directories being displayed like so with the last letter being truncated:

thanks :)


[SPARK-42884][CONNECT] Add Ammonite REPL integration

What changes were proposed in this pull request?
This PR adds Ammonite REPL integration for Spark Connect. This has a couple of benefits:

It makes it a lot less cumbersome for users to start a spark connect REPL. You don't have to add custom scripts, and you can use coursier to launch a fully function REPL for you.
It adds REPL integration for to the actual build. This makes it easier to validate the code we add is actually working.

Why are the changes needed?
A REPL is arguably the first entry point for a lot of users.
Does this PR introduce any user-facing change?
Yes it adds REPL integration.
How was this patch tested?
Added tests for the command line parsing. Manually tested the REPL.

@dongjoon-hyun officially is a bit a broad term. As far as I am concerned ammonite is just a way to use the connect JVM client, it is not meant as a change for all of Spark (although I do think it might make sense). We use other libraries all the time, and I don't think we have ever discussed those in the mailing list.
As it stands there are two reasons for using ammonite:

It is a better and easier to use REPL than the Scala REPL ever was.
It is easier to customize. Connect is a good illustration, for the Scala REPL I will probably need to the same thing as we did for the spark REPL project and that is fork the source code. In ammonite this was a minor modification.

I do intent to add support for the regular REPL at some point, this was just easier to get started with.
If you feel strongly about this then I am happy to send a message to the dev-list.

Ya, I'm not against this nice improvement. Just shoot one email to the dev mailing list to give a headup. That's what I'm thinking that we need.

@dongjoon-hyun I send the email.

Thank you so much, @hvanhovell .

Interesting!

Merging this one.


addslide

when i use it its show error
Error:(20, 13) error: cannot find symbol method addSlide(FirstSlide,Context)
addSlide(new FirstSlide(), getApplicationContext());

U nedd to add fragmemts name FirstSlide and pass their instance here
There is a predefined method when u create fragments in android studio (new instance) i can just call the method in addSlide() it takes 2 strings as parameters and u r done

Can you please explain in a step by step process i am new to android development..

i dont think my answer is something you are looking for but u can try this
https://github.com/mohak1712/AppIntro

thanku

Still same error
and
addSlide in in red state in android studio

Make sure that ur fragment import class is android.support.v4.fragment and not something else thats the last thing i can think of!

import android.content.Intent;
import android.os.Bundle;
import android.view.View;
import android.widget.Toast;
import com.msrkumar.tracker.rtcinfo.Main;
import com.msrkumar.tracker.rtcinfo.slides.FirstSlide;
import com.msrkumar.tracker.rtcinfo.slides.SecondSlide;
import com.msrkumar.tracker.rtcinfo.slides.ThirdSlide;
/**

Created by msrkumar on 7/10/2015.
*/
public class Intro extends Main{
public void init(Bundle savedInstanceState){
addSlide(new FirstSlide(), getApplicationContext());
addSlide(new SecondSlide(), getApplicationContext());
addSlide(new ThirdSlide(), getApplicationContext());
}
private void loadMainActivity(){
Intent intent = new Intent(this, Main.class);
startActivity(intent);
}
public void onSkipPressed(){
loadMainActivity();
Toast.makeText(getApplicationContext(),"Introduction Skipped",Toast.LENGTH_SHORT).show();
}
public void onDonePressed() {
loadMainActivity();
}
public void getStated(View v){
loadMainActivity();
}

}
addslide i red marked in my code

https://www.quora.com/How-do-i-fix-this-problem-in-android-code


Create a Footer component

What
Create a site-wide footer component based on the GOV.UK Design System component but only with the "meta" section for now
The component utilises a JSON data file for it's links data.
PR also contains minor HTML markup fixes and updated stylesheet to avoid leaking element styles into components.
Note: this component is lacking tests. Here's an upcoming story to set up a testing framework
Visual changes
Before

After

How to review

clone project
optional: install node if you don't have it already
install dependencies with npm install
run npm run dev to build the app
go to http://localhost:3000 to check the footer is looking as per https://design-system.service.gov.uk/components/footer#footer-with-links-to-meta-information (for now we're only using this variant
review the code for any improvements

The footer looks off to me, our current product page has the background a #dee0e2 and here it seems to be #f3f2f1. I'm not certain which is correct.

@LeePorte  #f3f2f1 as per https://design-system.service.gov.uk/components/footer/ which is the new light grey :)


Installation to Layout

How Can I add this to main layout file so that I can use this in all pages ?

You can load HideSeek plugin at the footer of your document or in the head section of your HTML page.


Sync Messages with RegEx

Remove Message for WeakEmail RegEx
Add Message for ZipCode RegEx
Add Message for Phone RegEx

Thank you. Merged this manually in the v2 repo: https://github.com/aldeed/node-simple-schema/commit/2b8f902e0d8d84eb923f9cf0cca2124f03f41cf8


blade extension @role() displays as string on my blade page

First take a look at the following

https://github.com/jeremykenedy/laravel-roles#opening-an-issue
https://github.com/jeremykenedy/laravel-roles/issues?q=is%3Aissue+is%3Aclosed

Please describe what you are needing help with below:
I am working on an already developed site with role management implementation which was not this package. I grabbed the latest version of this package, and after doing all the necessary configurations and changes, in my blade file, blade extensions like @role()  @permission() all show as string instead of it being processed. Please help me, is there anything I'm missing out?
Laravel version is 5.8 and this is my my current composer.json file
{
    "name": "laravel/laravel",
    "type": "project",
    "description": "The Laravel Framework.",
    "keywords": [
        "framework",
        "laravel"
    ],
    "license": "MIT",
    "require": {
        "php": "^7.1.3",
        "africastalking/africastalking": "^2.2",
        "egulias/email-validator": "^2.1",
        "fideloper/proxy": "^4.0",
        "freshbitsweb/laratables": "^2.1",
        "jeremykenedy/laravel-roles": "^3.0",
        "kingflamez/laravelrave": "^1.1",
        "laravel/framework": "5.8.*",
        "laravel/tinker": "^1.0"
    },
    "require-dev": {
        "beyondcode/laravel-dump-server": "^1.0",
        "filp/whoops": "^2.0",
        "fzaninotto/faker": "^1.4",
        "mockery/mockery": "^1.0",
        "nunomaduro/collision": "^3.0",
        "phpunit/phpunit": "^7.5"
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": "dist",
        "sort-packages": true
    },
    "extra": {
        "laravel": {
            "dont-discover": []
        }
    },
    "autoload": {
        "psr-4": {
            "App\\": "app/"
        },
        "classmap": [
            "database/seeds",
            "database/factories"
        ]
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "minimum-stability": "dev",
    "prefer-stable": true,

}

I cannot replicate this issue.


Invalid links to GitHub market place

On the page https://pnp.github.io/cli-microsoft365/user-guide/github-actions/#reference there are 3 links to the GitHub market place. The last 2 of them guide to user to a non existing page (since CLI renamed from O365 CLI to CLI for Microsoft 365).
Links to update
Microsoft 365 Deploy App
View on GitHub Marketplace --> should reference URL https://github.com/marketplace/actions/cli-for-microsoft-365-deploy-app
Microsoft 365 Run Script
View on GitHub Marketplace --> should reference URL https://github.com/marketplace/actions/cli-for-microsoft-365-run-script

hello ,i would like to work on this issue can you assign this to me @milanholemans

Certainly @cyrilckurian thank you! 👏

If I update link in https://github.com/pnp/cli-microsoft365/blob/main/docs/docs/user-guide/github-actions.md , will it reflect on the web page?

If you build the docs locally, you will see the updated link. However this seems a bit overkill for this issue.
Just update it locally and check in a Markdown viewer (like VS Code) if it works as expected. When that is done, you can create a PR.
When the PR is accepted, the links will change on the live environment.

OK

#3696 Check this out @milanholemans

Looking good @cyrilckurian 👍


GEN0305 uss_qualifier checks to verify ASTM F3548-21

As part of #274, we should check GEN0305.
One possible approach:
Ask for versioning endpoints for both test env and deployment env (accept resources for "test env versioning API" and "deployment env versioning API"), query both and compare.  When a group test is conducted, it should be ok for one participant to have a different version ("except when testing an update").

We were discussing this topic with @mickmis and @barroco last week and ended up with these questions:
Implementation wise, would this look like an additional endpoint that returns the version currently deployed in the test environments as well as the version returned in production (ie, a single endpoint that returns two versions),
or: would each environment have an endpoint that we can query and which returns a single version? (I believe we are not supposed to have any interaction with the production environment, but I'm not entirely sure).
A separate question: should we impose any format on the version (such as SemVer or CalVer). My guess is we should not (the question arised from wondering how we can know when the prod and test version may be different, see below)
Finally, how do we determine when versions are allowed to be different? You mention "group test": how is this different from a 'normal' test? Is this easy to determine? Does it require the test operator to set a particular flag in the configuration?
To solve this I was wondering if the endpoint that returns the version(s) could also include a boolean in the result that tells the qualifier "a new version is being tested".
Draft Proposal
From my current understanding, here is a simple proposal for a new endpoint, which could be added to the test harness:
GET <test_harness_api_base>/versions:
returns {
   test_version: string
   production_version: string
   new_release_under_test: boolean
}


Staging - get domain endpoint hangs

When I go to this page (https://staging.crossfeed.cyber.dhs.gov/domain/fdf597c5-c3b8-45ec-b28b-2fbffd3c86e7), which was linked to from the original domains page, the get domain endpoint just hangs and eventually times out:

@cablej , are you seeing this issue too?

The new link is https://staging.crossfeed.cyber.dhs.gov/inventory/domain/fdf597c5-c3b8-45ec-b28b-2fbffd3c86e7.
It works for me fine now.


Grenade crafting recipes

These can be tweaked later, but these are good to have.

Could you create another PR to add crafting for gas grenades

Sure, if you want.
I refrained from adding the gas grenades because they kind of feel unfinished, but can add them.

Sure, if you want.
I refrained from adding the gas grenades because they kind of feel unfinished, but can add them.

No it's fine I talked with Paneedah and they need to be overhauled before being craftable.


[WIP] EKB and eventing-core version alignment

Currently we install the eventing-core version which is set by SO in https://github.com/openshift-knative/serverless-operator/blob/b4ba45f6bc8858202ea6342207cec1f7de1499f4/olm-catalog/serverless-operator/project.yaml#L44-L46, even when a newer EKB version is installed/tested.
This PR addresses it and aligns the eventing-core version which gets installed with the to-be-installed EKB version.
Test run on release-next branch in #996
/hold
for test runs in #996
/cc @pierDipi @mgencur @maschmid

Closing in favor of #1025


Integrate Plausible Analytics with nextra

Discussed in https://github.com/shuding/nextra/discussions/2938

Originally posted by shankiflang June 18, 2024
Hi guys,
I'm using Plausible (https://plausible.io/) as my main analytics manager and I wanted to know how can I add my nextra doc in it ?
Thanks for the help

I'll take the liberty of asking you again! Does anyone have any idea how I can do this?

closing since what works with Next.js - works with Nextra, so just follow Next.js examples for Pages router for your analytics


dataloading bug in transformer example

During testing, reference file follows original order, but model's output has been shuffled. (got a blue score 0.53)
python bleu_main.py --reference=data/en_vi/test.vi --translation=temp/test.output.spm

https://github.com/asyml/texar-pytorch/blob/026163887f1bca450f51a4730986a953d940050c/examples/transformer/transformer_main.py#L69-L84
Should set valid and test dataset 's hparams {'shuffle': False}, default is True
I wrote a simple but not elegant one.
    def update_hparams(hparmas, split):
        new_hparmas = hparmas.copy()
        new_hparmas['shuffle'] = True if split is "train" else False
        return new_hparmas

    datasets = {
        split: data_utils.Seq2SeqData(
            os.path.join(
                config_data.input_dir,
                f"{config_data.filename_prefix}{split}.npy"
            ),
            hparams=update_hparams(data_hparams, split),
            device=device
        ) for split in ["train", "valid", "test"]
    }

Thanks for the issue! This is indeed a bug, we will address this in the next update.

Resolved in #156


fatal error: vision_msgs/msg/detail/header__struct.hpp:

In file included from /home/tianbot/yolov5_ws/build/vision_msgs/rosidl_typesupport_cpp/vision_msgs/msg/detection2_d__type_support.cpp:7:
/home/tianbot/yolov5_ws/build/vision_msgs/rosidl_generator_cpp/vision_msgs/msg/detail/detection2_d__struct.hpp:19:10: fatal error: vision_msgs/msg/detail/header__struct.hpp: 没有那个文件或目录
19 | #include "vision_msgs/msg/detail/header__struct.hpp"

That’s an odd issue. Can you try a clean build? Perhaps somethings updated on your system that made the cache invalid.
What ros version and os? Did you update binaries recently? Can you reproduce it anywhere else?

HI,
I am having a similar issue with this:
/home/jainish/ros2_ws/build/webots_ros2_msgs/rosidl_generator_cpp/webots_ros2_msgs/msg/detail/camera_recognition_object__struct.hpp:23:10: fatal error: vision_msgs/msg/detail/bounding_box2_d__struct.hpp: No such file or directory
23 | #include "vision_msgs/msg/detail/bounding_box2_d__struct.hpp"
The other packages like geometric_msgs works fine though.


cookbook typo

https://amznlabs.github.io/ion-docs/cookbook.html
On this page is this example:
void rewrite(String text, IonWriter writer) throws IOException {     IonReader reader = SYSTEM.newReader(textIon);     writer.writeValues(reader); }
It looks like textIon should be text.

Yes it should be. Thanks for catching that. It has been fixed.


[example] sample config file for starting the server

Observed this option for starting the server with config file, would be great to have a sample config file.
if maybe I have missed it while looking at the code, please share the path

Standard options:
--print-args                : Print the command line arguments (to stderr) (bool, default = true)
--help                      : Print out usage message (bool, default = false)
--config                    : Configuration file to read (this option may be repeated) (string, default = "")

Thank you!

If you use
./a.out --foo=bar --baz=apple

Then you can use
./a.out --config=./foobar.abc

where ./foobar.abc is a text file containing
--foo=bar
--baz=apple # you can add a comment to a line like this

This approach is inherited from Kaldi, as the C++ code is copied directly from Kaldi.

Alright!, Thanks for the info!


linux: add x32 subarchitecture for x86_64-linux

The x32 subarchitecture is basically x86_64, but with ILP32. This option doesn't force all programs to use the x32 ABI, but instead on a per-program basis when the ELF header is set to use both x86_64 AND 32 bits. Debian's kernel already has built-in support for the x32 ABI, but has to be manually enabled via editing the GRUB configuration, last time I tried.
To be honest, I want this to be enabled because I made a set of hand-golfed x86_64 programs, with a port to the x32 ABI to save more bytes. I do have it set in my config, but it is annoying to recompile the kernel every time a new kernel version releases, which takes an hour or so.
Fixes #1579, the third oldest issue currently open as of now.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
See below
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

Ran out of space on my NixOS partition

[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
x32 is not used by many people, so I wouldn't consider the change to be major.
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

My impression is that x32 never really got off the ground. There is extensive upstream discussion from 2018 about whether to deprecate it that I haven’t read more than one email of, although Wikipedia also reports that it gained support for shadow stacks this year.
In light of that, my main question is whether there are any potential security risks associated with enabling this. It exposes a new kernel ABI surface to potentially‐malicious programs; given that the x32 syscall layer is most likely unused and neglected enough that it doesn’t have the kind of maintainer attention required to sniff out and fix vulnerabilities, the question I have is whether it’s complex enough that we should expect such vulnerabilities to likely exist?
Implementing a bootloader‐level opt‐in toggle like Debian may be a way to resolve these concerns and provide x32 support for people to experiment with, without putting the vast majority of users at any additional risk.

Added the option config.security.enableX32Abi

It appears I need to push this to staging. I will close and reopen this to staging.

You can retarget the PR to staging by editing at the top.

Oh.

open

Oh. It looks like it doesn't work since I already force-pushed the branch.


Failed - Agent couldn't be set up

hello, I am sorry to bother you, but I trully have trouble with the evaluation. Here is the problem:
I already set up the Carla,

and then set up the run_evaluation.sh, but it seems doesnot work

when I see the sample_result.json, it shows

Failed - Agent couldn't be set up

And I have already installed timm

I have already fixed it, just delete the sample_result.json generated at last time.

maybe you should complied timm by youself, use the python file under folder interfuse named setup.py, as the readme said


Reducible, nested tree paths to set dynamic nodes

A somewhat common use of a Monkey is to lookup an item from a list based on a "current" id, i.e.
var tree = Baobab({
  currentEventid: 12,
  events: {
    12: { info: 'about event 12' },
  },
  event: monkey({
    cursors: {
      currentEventid: [ 'currentEventid' ],
      events: [ 'events' ],
    },
    get: function(c) {
      return c.events[c.currentEventid],
    }
  }),
});
console.log(tree.get([ 'event' ]);
// prints: { info: 'about event 12' }

Works great for getting the current thing, not so great for setting some property of the current thing.  I was thinking about something like this as a compact way to set information on the thing looked up by the monkey:
tree.set([ 'events', [ 'currentEventid' ], 'info' ], 'different info on 12!');
console.log(tree.get(['event']));
// prints: { info: 'different info on 12!' }

I've done it outside Baobab thus far like this:
var reducePath = function(tree, state_path) {
  return _.map(state_path, function(p) {
    if (!_.isArray(p)) return p;
    if (_.find(p, _.isArray)) {
      p = reducePath(tree, p);
    }
    return tree.get(p);
  });
};
tree.set(reducePath(tree, [ 'events', [ 'currentEventid' ], 'info']), 'different info!');

Is it worth considering adding support to Baobab (if it doesn't already exist?) for nesting arrays of paths inside tree paths?

Hello @aultac. This seems like a fine idea. Let me bring @jacomyal in this conversation.

+1

I took a step back here and remembered that I already implemented something of the kind in v1 and it ended up to be a chaotic mess. Will need a lot of thinking before re-implementing something of the kind.

@Yomguithereal Can I ask what some of those issues were?

@Yomguithereal Can I ask what some of those issues were?

Issues with dependencies.  That is to say you would expect such cursor to update whenever either its path or the reduced path is updated. And this is recursive.

Perhaps implementation could be simplified by treating the nested paths as monkeys themselves?  That's what I have to do manually now in a tree for such lookups.  The advantage here is that full knowledge of the path should allow for a '2-way' monkey that supports set as well as get

Would it be the case to create a set method in the monkey? As I was reading, this idea came to my mind:
var tree = Baobab({
  currentEventid: 12,
  events: {
    12: { info: 'about event 12' },
  },
  event: monkey({
    cursors: {
      currentEventid: [ 'currentEventid' ],
      events: [ 'events' ],
    },
    get: function(c) {
      return c.events[c.currentEventid],
    },
    set: function(path, data) {
       // In here you can do whatever updates to the tree you may possibly wish for, eg.:
        var currentEventid = tree.get('currentEventid');
        tree.set(['events', currentEventid, path], data)
    }
  }),
});

tree.select([ 'event' ]).set('info', 'different info!');

Just food for thought...

You don't need set in monkeys to perform what you want to do. Just listen to a cursor or a watcher and perform writes on the tree on their update events.


Add animation support to generated amp-story

Update the amp-story generation logic so page level animations are parsed and rendered using our AMPWrapper animation system.

I think this completes this task:
https://github.com/google/web-stories-wp/pull/1846
@mariano-formidable

I think this completes this task:
#1846
@mariano-formidable

Oh no, that other PR just added support for AMP animations using our animation pattern, but I haven't updated the actual amp-story generation logic to include animations.  I favored testing in a storybook amp-story instead of updating the generation logic because that would affect all stories going forward.
This issue is specifically about updating the story generation code.

Ahh I see. right on. cool.

Just dropping a note there that this would be a great use case for the toBeValidAMP assertions we have.

Testing instructions required - thanks

The connected PR #2268 has all the testing instructions. However, since this is behind a feature flag, there's actually no need for QA.
Therefore skipping & merging.
Reminder for the QA process: https://docs.google.com/document/d/1oZXjSJX30JLsIgCqOaER0Uff3Y_Tr-NCiQIfrYUnX9Y/edit?ts=5ebc211a#


What did you expect to happen?
I expected Dash to Dock's intelligent autohide to be turned on
Output of rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-unverified-image:oci:/var/ublue-os/image
                   Digest: sha256:e36a0548e12a9f22560cd1c1234e279c98d6af6c3088b798b4959b1c8e3c191f
                  Version: 38.20231027.0 (2023-11-26T10:25:13Z)

  ostree-unverified-image:oci:/var/ublue-os/image
                   Digest: sha256:e36a0548e12a9f22560cd1c1234e279c98d6af6c3088b798b4959b1c8e3c191f
                  Version: 38.20231027.0 (2023-11-26T10:25:13Z)

Extra information or context
It's possible that this is just the default expected behavior, but in that case it should be easy to turn it on, as opposed to right clicking the grid icon then going to Dash to Dock settings then turning it on. The setting is hard to find and if I didn't know it was there, I probably would have had no idea, especially as there's no option to do this in the settings app.

Yeah that is the default, I could document it in the docs though if that helps?
Also not related, I see you're still on the /var/ublue-os/image - you should do a just update to get on an updated image (or you could just wait until the automatic update kicks in, just thought I'd let you know!)


add chatify prompts and langchain

changelog
i've made a few updates:

replace guidance with langchain
updated prompts.json
decrement python version to 3.10 (from 3.11) to support langchain
updated requirements with packages required for langchain

note that pydantic-settings requires a version of pydantic that isn't compatible with langchain.  therefore the config.py file cannot report pydantic-settings.  since config.py contains an API key that can't be shared publicly, i'll email you the config.py file i'm using rather than sharing here.
broken stuff

i'm not sure whether i've set up prompts.json incorrectly, or whether i'm not reading in that file, or what.  i expected this to work:

curl -X 'POST' \
        http://<IP_ADDRESS>:9900/q44yic3bwec36ax3k04xrrp7h6bb4c2n/response \
        -H 'accept: application/json' \
        -H 'Content-Type: application/json' \
        -d '{
"user_text": "lambda x: x ** 2"
}'

but that request returns a "not found" message:
{"detail":"Not Found"}%

because i can't seem to get the prompts to be referenced correctly by their ID codes, i haven't been able to test whether the get_response function is working correctly.

Nice! Checking out the code now to see if I can figure out why it's not pulling prompts correctly.


Suppress 'unhandled property' messages for some known new event props

What it says.  This is to clean up the logs a bit.  I noted a TODO item that these properties could actually be useful in the future.

Do we have a JIRA task for revisiting this?

@pineapplespatula  No JIRA task.  After thinking about it further, I think these props are not immediately useful since we use the actual profile returned by pixmap (in case conversion to sRGB was included).


Remove well-known functionality from crawler and document python script for getting .well-known

We must remove the .well-known functionality from web crawler implemented in Jan. 2024. Instead, we will be using a Python script to collect this well-known data so testing and documentation is needed for that as well.

I added the well-known python script to the repo. In order to run this, you will also need to have redo-original-sites.csv and redo-sites.csv in the selenium-optmeowt-crawler folder. Since these files change each crawl, I'm not putting them into the repo. They can be found in the Crawl_Data_Feb_2024 and Crawl_Data_Dec_2023 folders, for the February and December crawls, respectively. This information and instructions of how to start the script are in the python script. I'll add a section to the readme repeating this information.

I updated the readme to include a section on running the well-known python script. I took out the well known column + description from the readme. I added a few steps to the wiki to explain how the data should be saved in order for it to integrate with the colabs.
Updated architecture diagrams:
web-crawler-architecture.pptx

Note to update the Wiki with SQL command not including a well-known column when creating the 'entries' database after this functionality is stripped from the crawler.


MSID: 95901 Version: 2 DOI: 10.1101/2<IP_ADDRESS>01711

MSID: 95901
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>01711
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=95901
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>01711

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/95901v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>01711
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/95901/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: [journal-ref-article-title] This journal reference (id c45) has no article-title element.

heading fixed on hypothesis, waiting for changes on sciety


Add note to guide trap handler design

@gfavor @aswaterman

if there is no code path because there is no code

Then it causes an access fault or a page fault. The guidance says - do not cause exceptions in your trap handler.

there is no code because the trap handler (or the address of the trap handler) has not been set up yet

There is no "valid" for the stvec or mtvec - it may be pointing to an address that may cause an access fault or page fault - this follows "write your trap handler to not cause an exception in your trap handler" i.e. do not enable interrupts or trigger exceptions.

as above: you keep talking about a trap handler, but there isn't a trap
handler in these situations. No code is executed.
On Wed, Apr 24, 2024 at 1:44 PM Ved Shanbhogue @.***>
wrote:

if there is no code path because there is no code
Then it causes an access fault or a page fault. The guidance says - do not
cause exceptions in your trap handler.
there is no code because the trap handler (or the address of the trap
handler) has not been set up yet
There is no "valid" for the stvec or mtvec - it may be pointing to an
address that may cause an access fault or page fault - this follows "write
your trap handler to not cause an exception in your trap handler" i.e. do
not enable interrupts or trigger exceptions.
—
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/pull/1208#issuecomment-2075808876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHPXVJSIPBJQY5Z6UDSUK73Y7AKTRAVCNFSM6AAAAABCP7JFFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVHAYDQOBXGY
.
You are receiving this because you commented.Message ID:
@.***>


Correct consumer timeout

It seems that no consumer timeout was the default a while ago.
Relates https://github.com/rabbitmq/rabbitmq-server/pull/2990

Good catch, thank you!


add ability to detect iptables mode in edgemesh-agent image

fix issue: #30
This solution is based on kube-proxy fix to the same issue:
https://github.com/kubernetes/kubernetes/pull/82966

/lgtm
/approve


oic client sample: pass destination addr via cmd line.

Signed-off-by: Gustavo Lima Chaves<EMAIL_ADDRESS>

+1

Thanks, merging.


Mega 2021 Update

Move to go modules
Update to latest Cuberite
Update to latest Docker
Use golangci-lint for linting
Fix lint errors
Profit

Signed-off-by: Dave Tucker<EMAIL_ADDRESS>

I'm impressed it still works :joy:

Fixed a couple of Cuberite APIs that were deprecated. I'm going to open an issue about BroadcastSoundEffect but this should be good to merge.

And that's fixed to... :tada:

Thanks a lot for that PR! When do you think it will be ready for merge?

How can I run this staff on mc 1.17.1 ?

@mmggmmgg Cuberite only supports 1.8 - 1.12.2 versions at the moment. See https://cuberite.org/


bump helm version to 3.13.3

see: https://github.com/helm/helm/releases/tag/v3.13.3

/cc @xiaomudk


can't build sources

Describe the bug
Trying to follow dev tutorial - https://datahubproject.io/docs/developers/
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/datahub-project/datahub
cd datahub
./gradlew build
Error:

Task :buildSrc:compileJava FAILED
H:\datacatalog\buildSrc\src\main\java\io\datahubproject\OpenApiEntities.java:11: error: package com.linkedin.metadata.models.registry.config does not exist
import com.linkedin.metadata.models.registry.config.Entities;

Expected behavior
Code compiled, auto-generated and so on, no any errors
Desktop (please complete the following information):

windows 10

I checkout old version (v0.9.6) and seems it work as expected - it load dependencies for last hour. After import will be finished, will checkout not so old version.

yes, it work under linux

I got the same error on Linux environment.
> Task :buildSrc:compileJava
buildSrc/src/main/java/io/datahubproject/OpenApiEntities.java:9: error: package com.linkedin.metadata.models.registry.config does not exist
import com.linkedin.metadata.models.registry.config.Entities;


Sometimes Flow reports error without indication of its location

function onClick(e: SyntheticMouseEvent & {target: HTMLElement}) { /* ... */ }
function render(callback: (e: SyntheticMouseEvent) => void) { /* ... */ }
render(onClick);

will result in the following error message:
test.js: inconsistent use of library definitions
[LIB] dom.js:64:1,68:1: EventTarget
This type is incompatible with
[LIB] dom.js:392:1,425:1: HTMLElement

Note that the error message gives no indication as to where the error has actually occurred. If the source file is sufficiently big, locating this error becomes extremely hard. And if the functions are defined in separate external files -- nearly impossible...

This should no longer be an issue. If you are still having a problem with this please let us know 😊


[BUG]: Split installation workflow into two

Describe the bug
The current installation workflow is deploying infra + DRISTI in one go. However, the install doc talks about updating values in environment files in between the steps. Eg. DB hostname and URLs to be updated after infra creation but before the services are deployed/configured. Currently, this is managed in a single workflow with some portions commented out after the first time running it.
We should have:

Two separate workflows - for infra creation and deployment of DRISTI services.
Installation doc should talk about running the infra creation workflow first
Update values in the env file post infra creation
Then, run the deployment workflow.

This will be a blocker for scaling or when someone new sets up the environment.

@subhashini-egov , I have created two workflow. One for infra creation and another sample workflow for pucar installation.


Fix scroll position bug

I did some digging in the Atom codebase and learned that Atom buffers some UI operations such as scrolling and changing the cursor before actually updating the UI.
Atom just renders the final result at the end. It turns out the option { center: true } gets lost at some point.
This seemed like the quickest fix. But I wonder if there's a bug on Atom core, regarding the way it flushes all these UI operations.
Fixes https://github.com/atom/go-to-line/issues/29

@50Wliu should I add unit tests for this?

Yes please!

Before:

After:

hey @50Wliu.
Is there anything else I need to do to get this merged?

@nettofarah Someone just needs to test this out to make sure everything's working correctly.  Unfortunately there's a long review queue, so sorry about that!

That's totally ok, @50Wliu! Thank you for the heads up

hey, @50Wliu anything I can do to help you expedite this?

I'll put this on my list for over the weekend...no guarantees that I'll get to it though.

Just tested this and it seems fine to me: @atom/feedback any objections to merging?

@50Wliu I don't have a problem with merging this. Go for it!

Thanks @nettofarah!

Thank you @50Wliu. Super happy to help


Issues with error handling v3.2.1

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>at startup:
[5/18/2020, 10:07:35 AM] [WeatherPlus] Error retrieving weather report and forecast
[5/18/2020, 10:07:35 AM] [WeatherPlus] Error Message: SyntaxError: Unexpected end of JSON input

Could u start homebridge with debug and post the log?
Linux: DEBUG=homebridge-weather-plus homebridge -D
Windows: set DEBUG=homebridge-weather-plus & homebridge -D

HWP_log.txt

Done
On Mon, May 18, 2020 at 10:41 AM Arne<EMAIL_ADDRESS>wrote:

Could u start homebridge with debug and post the log?
Linux: DEBUG=homebridge-weather-plus homebridge -D
Windows: set DEBUG=homebridge-weather-plus & homebridge -D
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/naofireblade/homebridge-weather-plus/issues/128#issuecomment-630335218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF7ZD563CVEGMQ37AGNORYDRSFXMJANCNFSM4NEIPE3Q
.

Apparently fixed in 3.2.2


Scala port?)

Hello, do not want to port your project to scala, just recently we have been discussing (https://github.com/KayJamLang/core) services of this type, and for free!)

If you would want to do this, you can, but it using scala would be just a burden for me without any benefits.

ok


Release 1.4.0

docket:

Complete manylinux support in pex. (#480)
Add manylinux wheel support and fix a few bugs along the way (#316)
Skip failing tests on pypy shard. (#478)
Bump travis image to Trusty. (#476)
Mock PATH for problematic interpreter selection test in CI (#474)
Skip two failing integration tests. (#472)
Better error handling for missing setuptools. (#471)
Add tracebacks to IntegResults. (#469)
Fix failing tests in master (#466)
Repair isort-check failure in master. (#465)
Repair style issues in master. (#464)
Fixup PATH handling in travis.yml. (#462)

notably, this release ships with full support for #281

this is complete: https://pypi.org/project/pex/1.4.0


Revert "feat: added istioctl aliase with namespace and context"

Reverts Comcast/k8sh#10

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


Explanation of the functionality on the first page (preferably animation based)

Won't fix at this time, README explains what's happening and how to use. Will also be adding a reference to the README in the settings to help users find usage instructions


Add simplified Chinese translation

Add simplified Chinese translation

This is an automated message from CI:
Docker Image for build 1 is available on DockerHub as jc21/nginx-proxy-manager:github-pr-2052
Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes.

The translation doesn't work, the language is fixed to en in the front-end code, I hope this can be fixed.
Related source code

This version 2 doesn't have a language switcher in the UI, despite having the foundations for language support. Verison 3 does have this however, but it's still work-in-progress.

@xiaoxinpro 可以翻译下v3吗，v3上周刚发布了一个版本

@leic4u V3版本目前还处于测试阶段，请等待官方发布Releases版本，根据情况会及时展开翻译工作。

@leic4u V3版本目前还处于测试阶段，请等待官方发布Releases版本，根据情况会及时展开翻译工作。

兄弟   你还在翻译此项目嘛

我已经换 Nginx-UI https://github.com/0xJacky/nginx-ui 了


Further simplify the plugin installation process.

re: https://github.com/Unidata/netcdf-c/pull/2431
Hat tip to DWesl and opoplawski for their help.
With some help, I found out how to get rid of the tmp_LTLIBARIES
hack and replace it with check_LTLIBRARIES.
Using check_LTLIBRARIES means also that the test libraries are not
built until "make check" is executed.
This PR replaces the one above.

This seems to work for me.  Thanks.

@DennisHeimbigner some conflicts have crept in, and Github is (again) not letting me resolve them.  I'll try to sort that out, but are you able to make changes and/or have a moment to address them?

Ok, let me see what I can do.

This PR was apparently made moot by other, later PRs.


Reproducing the result

hi, great job!
I want to reproduce the result. But  the net seems collapsed after about 2400 iters every time.
I have tried vox-256.yaml and vox-adv-256.yaml.
I used one gpu: RTX 2080TI , and the batch size is 8.
Has anyone encountered this kind of problem。

You should use pytorch==1.0.0 as explained in README.md


Add new visibility APIs for List/Scan/CountWorkflowExecutions

https://github.com/uber-go/cadence-client/pull/716


Short video tutorial

Many users aren't familiar with command-line usage.
This would be really useful.
Alternative would be making a front-end tool e.g. adding an export function to a desktop .vols player.

it's on the Volograms youtube - https://www.youtube.com/watch?v=PJ8_ZCduqLY


typescript support

added types for typescript.

it seems the CI is broken

Hi @chuv!
Thanks for the contribution... yeah I was looking at that. I noticed I was working on updating the script (a while back, I guess I forgot about it) to change the testing framework and update the code. I didn't finish it.
I guess that update won't change these files since the output will still be the same. So I'll go ahead and merge it.


WSL2 unable to ping host machine

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If you have a feature request, please post to the UserVoice.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues.  Please direct all Windows crashes and security issues to<EMAIL_ADDRESS> Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".
Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
10.0.18917.100

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
ping host machine, whose IP was obtained from /etc/resolv.conf.

What's wrong / what should be happening instead:
Ping timed out. Additionally, I can ping <IP_ADDRESS>, but not www.google.com.

Same issue. I'm running Windows 10.0.18932.1000 + WSL 2 with Debian.
The exact commands:
λ ~/ cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver <IP_ADDRESS>
λ ~/ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6257ms

λ ~/

I am able to ping google.com/external sites in general - just not the host machine.

I can't ping anything.
This problem has bothered me for two days.
Finally I solved this by performing a Network Reset in Settings > Network & Internet > Status > Change your network settings.
I think this problem is caused by wrong mask in ip address and wrong routing table after upgrade to WSL 2.

Version 10.0.18995.1
Command : ping <IP_ADDRESS> (My PC's IP)
I can ping <IP_ADDRESS>, www.google.com, <IP_ADDRESS>, <IP_ADDRESS>(Raspberry Pi).
but I cannot ping <IP_ADDRESS>.
I tried "Reset Network" but did not improve anything.

In WSL2, I was able to access the web server started on Windows side using w3m with IP address specification (<IP_ADDRESS>), but I could not connect to VcXsrv.
Ubuntu recognizes the existence of the X server, but says "Connection refused".
In summary, HTTP was possible, but X and Ping were not possible.
WSL1 all worked on the same Windows version.

@mikuta0407 make sure to disable access control when starting up your X server, this will allow it to accept external connections and will likely resolve your 'Connection refused' error.

same here, "Reset Network" didn't help.

The Windows Firewall is blocking all traffic, except HTTP per default. In order for VcXsrv to work, you need to allow all inbound rules (private and public) for "VcXsrv windows server" under advanced settings in the windows firewall section of Windows Security. (Or select the public and private checkbox on the windows firewall prompt that appears if you run VcXsrc for the first time.)

In order for ping to work, you need to create a new rule. Click on Action/New Rule and select custom rule.

Select Next on the Program step. Then select ICMPv4 as protocol type.

Select Next until you end up in the Name section, then enter any name and click Finish.

If you now try pinging your host ip from wsl2, it should work as expected.
For every other connection between your wsl2 and your host, you have to allow the inbound rules for private and public networks or if they don't exists manually create the rules for the corresponding UDP/TCP port, but be aware that this might impact your security, if you use your computer in public networks.

It works for me , thanks @BBJip

The Windows Firewall is blocking all traffic, except HTTP per default. In order for VcXsrv to work, you need to allow all inbound rules (private and public) for "VcXsrv windows server" under advanced settings in the windows firewall section of Windows Security. (Or select the public and private checkbox on the windows firewall prompt that appears if you run VcXsrc for the first time.)

In order for ping to work, you need to create a new rule. Click on Action/New Rule and select custom rule.

Select Next on the Program step. Then select ICMPv4 as protocol type.

Select Next until you end up in the Name section, then enter any name and click Finish.

If you now try pinging your host ip from wsl2, it should work as expected.
For every other connection between your wsl2 and your host, you have to allow the inbound rules for private and public networks or if they don't exists manually create the rules for the corresponding UDP/TCP port, but be aware that this might impact your security, if you use your computer in public networks.

It worked! thanks a lot.
I will just add that in the "scope" step, I added the group of IP that I am using to reach my WSL instance and the host IP block to reduce the security issues.

all you need to do is change your windows firewall settings,and allow hyper-v access

PLEASE HELP ME OUT !!PLEASE PLEASE!!
I have fresh install of win10 Entr and I went through the process of installing wsl2 and successfully installed kali as my default wsl version2  OS. It all worked fine and and was smooth till i logged into my Kali shell.
I did my apt update && apt upgrade -y and installed all the tools I needed and it was perfect. I was trying to set up my Kali box for the HTB machines and once I set up the PVN connection I was successfully able to ping all the HTB machines pretty straightforward. I was able to nmap and do other enumerations like gobuster and so on.. on any machine. However when it comes to getting a reverse shell from a pwn box, I symply do not get any connection what so ever.
I tried everything I found on the web; I tried to reset all the PC connections, WSL2 connections, tried to unable and then disable the Virtualization on the BIOS, added IP rules on the Win firewall, playing around with the HyperV WSL adapter and such and such....I tried anything I could find to get this working. After messing around for a while I disinstalled and deacativated everything from WSl2 to HyperV settings for the last time  and then REinstalled and got running kali back again. Now not only I CANNOT get a reverse connection from a VPN connected machine(HTB), but I cannot even ping to Windows host!! PLease point me in the right direction.
 I keep going through Microsoft WSL2 documentation and guidelines and could not really get any useful information on this specific issue.  I tried follow up with discussions in focrums and blogs but it seems no one came accross my same issue.  Please if you think you could have any useful information point me in the right direction. I really appreciate any kind of help. I'm not just trying to solve the problem but I really want to fully understand what is the root of the problem.
Thanks in advance to everyone.

Same issue. I'm running Windows 10.0.18932.1000 + WSL 2 with Debian.
The exact commands:
λ ~/ cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver <IP_ADDRESS>
λ ~/ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6257ms

λ ~/

I am able to ping google.com/external sites in general - just not the host machine.

I meet the same problem.

After trying all the methods above, what worked for me was uncheck "Block all connections, including those in the list of allowed apps"
I understand this can be considered not a "security best practice" as you are allowing incoming connections to apps on public network but this issues was fixed for me after doing so.

FYI,
in WSL2, the firewall setting name is Virtual Machine Monitoring

After enabling the inbound rules, pinging windows host works fine.

This is definitely something can be easily missed. Seems for some newly installed Windows 10, it would be default enable "Block all incoming connections, including those in the list of allowed apps".

FYI, in WSL2, the firewall setting name is Virtual Machine Monitoring
After enabling the inbound rules, pinging windows host works fine.

It did not work for me, I had to also remove the CAP_NET_RAW setting on my Debian distro:
    sudo setcap cap_net_raw+p /bin/ping

See for more info:  https://github.com/microsoft/WSL/issues/5109#issuecomment-616320311

Thank you @ChaosZh , you saved my day!

If you're using McAfee like me you have to enable here

If anyone bumps into this issue - one more thing to check is disable VPN connection on the host machine (if any)

For the record, WSL is considered 'PUBLIC' from windows guys (I haven't figured out why). That means if you just try to simply disable the firewall of the your current profile (which in my case 'Private') to check if it's a firewall issue, that's not gonna work.

For the record, WSL is considered 'PUBLIC' from windows guys (I haven't figured out why). That means if you just try to simply disable the firewall of the your current profile (which in my case 'Private') to check if it's a firewall issue, that's not gonna work.

Thank you to pointing me into the right direction, because I tried to disable the defender or add custom rules and it did not work. What actually has worked is when I went to Windows Defender Firewall Properties and unchecked vEthernet WSL from being protected for all the profiles.

dasdasd

I faced this problem but I didn't want to open firewall options for Public networks.

Then set the connection related to WSL2 to private
Set-NetConnectionProfile -InterfaceIndex 4 -NetworkCategory Private
Check the change worked

FYI, in WSL2, the firewall setting name is Virtual Machine Monitoring
After enabling the inbound rules, pinging windows host works fine.

this works for me

For the record, WSL is considered 'PUBLIC' from windows guys (I haven't figured out why). That means if you just try to simply disable the firewall of the your current profile (which in my case 'Private') to check if it's a firewall issue, that's not gonna work.

Thank you to pointing me into the right direction, because I tried to disable the defender or add custom rules and it did not work. What actually has worked is when I went to Windows Defender Firewall Properties and unchecked vEthernet WSL from being protected for all the profiles.

Thank you for this! This worked

FYI, in WSL2, the firewall setting name is Virtual Machine Monitoring
After enabling the inbound rules, pinging windows host works fine.

It worked! Now in my settings there is a Virtual Machine Monitoring (ICMPv4-In). I only enabled it and then my ping works fine.

I have implemented that hard coded DNS solution by adding the DNS hosts directly to /etc/resolv.conf locked with chattr etc done swap=0 in Windows home area .wslconfig file and all sorts and it is a lot better, but WSL2 still looses it's DNS and entire network connection even if you disconnect briefly and reconnect your IPsec VPN. Once that happens still have to reboot.
(I am running WSL2 on top end Dell laptop with up-to-date bios and Windows 10 up to date patches and drivers.)
It is NOT just DNS because you can't ping via raw IP address. All windows apps network capability is retained whilst WSL2 JUST BREAKS and ABSOLUTLY NO SOLUTION BUT TO REBOOT - a bug 10 YEARS OLD!!!!!!!
Setup /etc/wsl.conf to use /etc/resolv.conf (which is protected by chattr).  Sure it works after reboot but any network disruption triggers the BUGS WRITTEN BY WINDOWS PROGRAMMERS WHO CAN'T CODE LINUX NETWORK CODE TO SAVE THEIR LIVES - AND CLOSE THE BUG REPORTS OVER AND OVER AND OVER AND OVER - THOUSANDS OF THEM!!!!!!!!

/etc/wsl.conf

WSL2 runs without hyper-v, but WSL1 used hyper-v.  NOTE: WSL1 had the exact same BROKEN NETWORK BUG!
NEVER FIXED AND IT IS KILLING MICROSOFTS Linux reputation to the tune of at least $30 BILLION - NO JOKE!
When running ordinary applications under Windows or on a Linux PC, any disconnection of the network and reconnection allows all applications to reconnect to the network no problem; not so with WSL2 it's still got a fragile broke WSL network that fails to ping! When running WSL, DNS resolution is lost even with a brief disconnection or the lease time on the network driver laps and reconnects (which is normal), after that you can’t connect or even ping devices unless you reboot! This is specifically a WSL Linux bug that was coded brilliantly by Windows network programmers and they have closed THOUSANDS of similar bug reports; that is WEIRD!
Even with millions of complaints, and thousands of bug reports, this bug has been persistent for almost a decade and NOT FEXED IN JULY 2023! This is so serious many developers avoid all Docker development under WSL and Windows.
When Windows programmers write Linux network code, what could possibly go wrong?
WSL team members even close bug reports rather than combine the data from thousands of similar reports. When reports are closed so that others can’t comment the geniuses have magically fixed the major bug right? NOT! The use of Docker Desktop makes it 100 times worse, but fortunately Docker Desktop is NOT Docker and many people run WSL2 without Docker Desktop.

FYI, in WSL2, the firewall setting name is Virtual Machine Monitoring
After enabling the inbound rules, pinging windows host works fine.

It worked! Now in my settings there is a Virtual Machine Monitoring (ICMPv4-In). I only enabled it and then my ping works fine.

It works for me, tks very much.


Use actionAuthentication instead of authentication deprecated hook

Questions
Answers

Description?
Use a non-deprecated hook.

Type?
improvement

BC breaks?
no

Deprecations?
no

How to test?
n/d

Thank you @PrestaEdit