Set source based on Platform

I thought the inclusion of a Platform check in the sample code might be helpful to those new to react-native
Thanks for the lib ❤ 🚀 😄

Seeing this now, is there a chance this is actually confusing to people since it doesn't seem to be required to strip the file prefix? (at least I don't think so, I'm not an it works)

@jakecraige that part of the README is a little dated. If you can confirm that the same uri works on both iOS and Android I suppose we can remove it.

Hmmm not sure, came across this a while ago so Im not 💯 that the url will work in Android without stripping the file prefix.
I mainly made this update because it was confusing to me to see const source be redefined without a conditional Platform check. If the url works without the prefix, then no worries rolling back this commit and settling on a single line 🌈

I can test it out when I get some time.

awesome 🙌 , thanks for the lib 🌮  super helpful ✨

Sounds great. It's been working well for me without it which Is why I brought this up. Definitely test for yourself to make sure I'm not crazy thought 😄

Just confirmed @jakecraige, good call. Updating the README/Example project now!


Added Danish translation for python files

@kimusan Thank you very much; again, I've renamed here dk => da

Ahh sorry. I understood it the other way around


Increased organization, easier proxying and UI Buttons.

Overview:

All MonoBehaviour components related to proxying in-game components now reside in MappingComponents/
Editor scripts are in the Editor/ directory
Scripts that execute in-game are in the Runtime/ directory
Renamed the 'Generic' level type to 'Sandbox' (Including the namespace for it's mapping components)
Added a ComponentProxy class that makes it easier to create new component proxies.
Added a mapping component for making functional in-game UI buttons (PointableButton)
Added a class that makes getting references to in-game objects much easier (ObjectReferences)

Component Proxy:
This is a simple abstract class that enables the code to GetComponentsInChildren() and let the derived class resolve the proxy in it's own class. See the new button class for an example. Additionally, it has an virtual OnExport() method that can be used for one time calculations right before the map is exported (Some proxied components have Editor functions that can be emulated here instead of at run-time)
ObjectReferences:
This class will find static fields with the ObjectReference attribute and searches the scene for a GameObject that matches the name filter and the component type. The search is the first thing that happens when a scene is loaded to make sure nothing gets deleted before a reference can be taken. For example:
// Reference to the first GameObject in the scene that has a name containing "Destructobin"
[ObjectReference("Destructobin")]
public static GameObject DestructobinReference;

// Reference to the first SosigSpawner component found in the scene (You can also filter by name here too)
[ObjectReference]
public static SosigSpawner SosigSpawnerReference;

This is very useful when proxying components since we usually need to borrow values from existing game objects or components, so being able to automatically search for these references makes getting those values much easier.

You have correctly come to the conclusion that my organization is completely terrible, and I really do appreciate the efforts in trying to piece it into something that isn't quite as idiotic. The only problem with that is it nukes backwards compatibility. If these changes are pushed out, old levels stop working. Monobehaviour FileIDs are generated like this. If you break that mapping by changing a class name or namespace, loading an old scene produces missing components and everything breaks.
If I'd internalized that a bit better when I was puking out classes, maybe I would've spent a bit more time actually organizing things properly. Ah well. Breaking changes like this were the kind of things I was hoping to save for when Anton inevitably breaks the whole mod with the release of the second TNH map.
I'm a big fan of ComponentProxy. I'd planned something similar as I watched the Loader class bloat, it was just a matter of sitting down and porting everything. I'm perfectly happy to merge that in alongside your PointableButton proxy. ObjectReferences, too. That's a cool shortcut, I'm a fan. All that will help clean things up.

Yeah I was aware this would break existing maps, they just outright crash the game when loading with these changes.
That could be something to look into, not letting the player load a map that isn't compatible just in case.
As for all the other changes, did you want me to open a different PR with just the ComponentProxy, PointableButton and ObjectReference classes in the meantime?

Yeah, I'll gladly merge those files, and then I'll get around to porting existing proxies hopefully soon.

Moved the other changes to another branch. This PR has only the desired classes.


dart format and update the readme

run dart format on the repo (to see if this fixes the CI)
add a badge to the readme file

Thanks for merging! I think you'll need to re-enable github actions:

Let me try.
I have no idea what Github actions are, so maybe I should just disable it entirely. Doesn't seem important for such a simple package.

Ah, github actions is just the name for the continuous integration system available from github. The configuration file for it in this repo - https://github.com/lrhn/charcode/blob/master/.github/workflows/ci.yml - is a little harder to read then it needs to be for what it does.
For every PR, and every merge into master, it runs pub get, verifies that the source is formatted, analyzes the code, and runs the tests. It's definitely a value add :)


ci(dependabot): fix incorrect username for Arnaud

Self explanatory.

Sorry for the inconveniance @amimart

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


add exclude to skip files.

module.exports = {
baseLocale: "",
locales: [""],
localePath: "",
openAIApiKey: "",
overrides: {},
exclude:[]
};

namespaceGlob option can do this job

namespaceGlob option can do this job

seems not working in glob documention，I will resolve it later

  baseLocale: 'en',
  locales: ['zh-CN', 'zh-TW'],
  namespaceGlob: ['!(common.json)']

Try setting it up like this. @WeslleyDeSouza 。Also, I have already updated the readme.md。learn more about glob


CLUSTERDOWN for read  - Replica stuck in recovery

Replicas are marked as recovering after they receive CLUSTER REPLICATE and before they attach to primary to snapshot. However, if primary is down and sync is requested, replica will reset it's state but not recovery flag. If it's assigned as primary later, it will accept writes but not reads and report CLUSTERDOWN as per https://github.com/microsoft/garnet/blob/main/libs/cluster/Session/ClusterSlotVerify.cs#L33
Repro:
1. Start N1 primary and replica N2.
2. Issue `CLUSTER REPLICATE`<node id of N1> to N2. (N2 transitions to secondary state)
3. Kill N1 (there might be a race and this needs to happen quickly)
4. N2 will revert to unassigned state if N1 fails initial checkpoint request but is stuck in recovery state.
5. Assign N2 as primary with some slots
6.  Send read request to N2
7. CLUSTERDOWN reported

Though a node can still be stuck in recovery after this stage - it will atleast transition to secondary if this step completes. As a result, we can take corrective action  - ideally good idea would be to expose metric like Redis's  master_sync_last_io_seconds_ago so admin can take corrective action.

Great catch! I think there are two issues here, one is the replica remains in recovering state when CLUSTER REPLICATE fails, and the other is how do we expose metrics related to syncing on the replica side including master_sync_last_io_seconds_ago.
The first should be fairly easy to correct. I will provide some context below if you want to take a stab at it.
Fixing the stuck in recovering state bug
The ReplicaReceiveCheckpoint.cs contains all the operations executed from the replica side to complete syncing with the primary. InitiateReplicaSync is where we wait for the primary to complete sending the checkpoint and if that fails because connection is interrupted then we will reset the role of the local node back to primary. There I think we should be resetting the recovering variable back to false. We might need to check up the call stack to see if any other points of failure might end up resulting in the same race condition.
Exposing metrics
For the second part, we might to keep track of a collection of metrics related to replication. That will require some refactoring of the current replication code from the replica side. I imagine we should have a ReplicateSession that contains the related operations under ReplicaReceiveCheckpoint.cs and also a struct with all the associated metrics for that ReplicateSession.
Below are all the associated metrics. Do you have any specific requirements, or we just need to add the one metric mentioned above?

master_sync_total_bytes: Total number of bytes that need to be transferred. this may be 0 when the size is unknown (for example, when the repl-diskless-sync configuration directive is used)
master_sync_read_bytes: Number of bytes already transferred
master_sync_left_bytes: Number of bytes left before syncing is complete (may be negative when master_sync_total_bytes is 0)
master_sync_perc: The percentage master_sync_read_bytes from master_sync_total_bytes, or an approximation that uses loading_rdb_used_mem when master_sync_total_bytes is 0
master_sync_last_io_seconds_ago: Number of seconds since last transfer I/O during a SYNC operation


01-02-AbhinavU29

file edited

created a branch, created a file and made a commit, and opened a pull
request

change

mainn added

merged


Release 1.0 fixcolumnlayout

** Briefly describe changes and the motivation behind them here **
This PR contains:

[ ] Changelog
[ ] Documentation
[ ] Tests

@mortoray: Would you mind filling in the PR-template?

@kusma Done.


Ladybird WebContent Crash

Summary
We visiting http://www.zed.com and allowing the site to load. When moving the cursor over the menubar or the hero section that highlights the elements, the site crashes.
I removed the JS from the SingleFile and it still crashed, leading me to assume the issue could be CSS related given the animation is what causes the crash.
Operating system
macOS
Steps to reproduce

Go to http://www.zed.com
Once loaded move the cursor over the menu bar/hero section to enable interactive element highlighting

Expected behavior
Menu bar/Hero section link highliting
Actual behavior
Website crash.
URL for a reduced test case
https://gist.github.com/seth-wood/18836d31d028cbb49c2dd4673a06a3a0
HTML/SVG/etc. source for a reduced test case
N/A

Log output and (if possible) backtrace
46514.146 WebContent(19406): (js log) "JQMIGRATE: Migrate is installed, version 3.4.0"
46514.161 WebContent(19406): No property (from 4 properties) matched Token: Comma
46514.161 WebContent(19406):     animation-direction
46514.161 WebContent(19406):     animation-play-state
46514.161 WebContent(19406):     animation-delay
46514.161 WebContent(19406):     animation-fill-mode
46514.161 WebContent(19406): No property (from 4 properties) matched Token: Comma
46514.161 WebContent(19406):     animation-direction
46514.161 WebContent(19406):     animation-play-state
46514.161 WebContent(19406):     animation-delay
46514.161 WebContent(19406):     animation-fill-mode
46514.485 WebContent(19406): ResourceLoader: Filtered request to: "https://www.googletagmanager.com/gtag/js?id=UA-114649197-1"
46514.495 WebContent(19406): HTMLScriptElement: Refusing to run script because the element's result is null.
46514.650 WebContent(19406): ResourceLoader: Failed load of: "https://www.zed.com/wp-includes/js/font.js", Error: Load failed (status: 404 Not Found), Duration: 165ms
46514.650 WebContent(19406): HTMLScriptElement: Refusing to run script because the element's result is null.
46514.656 WebContent(19406): ResourceLoader: Filtered request to: "https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.5"
46514.658 WebContent(19406): HTMLScriptElement: Refusing to run script because the element's result is null.
46515.798 Ladybird(19301): WebContent process crashed! Last page loaded: https://www.zed.com/
46515.798 Ladybird(19301): Consider raising an issue at https://github.com/LadybirdBrowser/ladybird/issues/new/choose

*****************************************

Local Reduction.html log (with JS removed):
GrMtlRenderPipeline: 0x157138800 (4 refs)
GrMtlDepthStencil: 0x6000011c77f0 (2 refs)
GrMtlRenderPipeline: 0x16082ba00 (3 refs)
GrMtlSampler: 0x6000005dc2c0 (1 refs)
GrMtlRenderPipeline: 0x160839400 (3 refs)
../src/335264b559-747e4e3c5f.clean/src/gpu/ganesh/GrManagedResource.h:61: fatal error: "check(0 == fHashSet.count())"
47510.664 WebContent(19573): FIXME: Implement 'content-security-policy' http-equiv state
47518.521 Ladybird(19301): WebContent process crashed! Last page loaded: file:///Users/sethwood/Downloads/Reduction.html
47518.521 Ladybird(19301): Consider raising an issue at https://github.com/LadybirdBrowser/ladybird/issues/new/choose

Screenshots or screen recordings
No response
Build flags or config settings
No response
Contribute a patch?

[ ] I’ll contribute a patch for this myself.

Reduced the crash to this:

target

Crashes when hovering a transformed pseudo-element.


Add model for AWS Step Functions state machine

This PR is a first attempt at providing support for AWS StepFunctions. For now, this PR only adds a new class StateMachine to represent a state machine entity.
Background: We're using moto's domain model to support CloudFormation deployments in LocalStack. Currently the code in this PR is also included in the LocalStack repo, but in fact it should really live in this repo (in moto).
The main reason we'd like to migrate this code into this repo is that moto makes certain assumptions about the location (module) of classes that derive from BaseModel, which requires models to be in a package in the first level under the root package (whereas we generally keep model classes in the second level under the root package):
service = cls.__module__.split(".")[1]

Hopefully you guys can accept this PR, and perhaps it can be useful as a first step towards supporting AWS StepFunctions in moto.

Coverage decreased (-0.3%) to 92.54% when pulling 1280e20df09136a0a76c7d9dfa0d37c1ae98a509 on whummer:feat/add-statemachine-model into b4fcbd79d8bdd3bd834c83cbb1d8782ddd50760e on spulec:master.


Error with namespaced deployment

Hi all,
I want to deploy the redis-cluster operator in the default namespace without clusterRoles.
I set .operator.namespace: "default"
But the pod is crashing:
[root@localhost charts]# kubectl get po
NAME                                      READY   STATUS             RESTARTS   AGE
redis-cluster-operator-7cf988795f-jq9bt   0/1     CrashLoopBackOff   5          5m56s

While from the logs I can see:
[root@localhost charts]# kubectl logs redis-cluster-operator-7cf988795f-jq9bt
{"level":"info","ts":1617693268.2716427,"logger":"cmd","msg":"Go Version: go1.13.3"}
{"level":"info","ts":1617693268.2716968,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1617693268.271701,"logger":"cmd","msg":"Version of operator-sdk: v0.13.0"}
{"level":"info","ts":1617693268.2717068,"logger":"cmd","msg":"Version of operator: 0.1.1+0000000"}
{"level":"info","ts":1617693268.2719927,"logger":"leader","msg":"Trying to become the leader."}
{"level":"error","ts":1617693268.9286208,"logger":"k8sutil","msg":"Failed to get Pod","Pod.Namespace":"default","Pod.Name":"redis-cluster-operator-7cf988795f-jq9bt","error":"pods \"redis-cluster-operator-7cf988795f-jq9bt\" is forbidden: User \"system:serviceaccount:default:redis-cluster-operator\" cannot get resource \"pods\" in API group \"\" in the namespace \"default\": RBAC: clusterrole.rbac.authorization.k8s.io \"redis-cluster-operator\" not found","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\ngithub.com/operator-framework/operator-sdk/pkg/k8sutil.GetPod\n\t/go/pkg/mod/github.com/operator-framework/operator-sdk@v0.13.0/pkg/k8sutil/k8sutil.go:128\ngithub.com/operator-framework/operator-sdk/pkg/leader.myOwnerRef\n\t/go/pkg/mod/github.com/operator-framework/operator-sdk@v0.13.0/pkg/leader/leader.go:160\ngithub.com/operator-framework/operator-sdk/pkg/leader.Become\n\t/go/pkg/mod/github.com/operator-framework/operator-sdk@v0.13.0/pkg/leader/leader.go:67\nmain.main\n\t/src/cmd/manager/main.go:99\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}
{"level":"error","ts":1617693268.9287992,"logger":"cmd","msg":"","error":"pods \"redis-cluster-operator-7cf988795f-jq9bt\" is forbidden: User \"system:serviceaccount:default:redis-cluster-operator\" cannot get resource \"pods\" in API group \"\" in the namespace \"default\": RBAC: clusterrole.rbac.authorization.k8s.io \"redis-cluster-operator\" not found","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\nmain.main\n\t/src/cmd/manager/main.go:101\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}

but roles are correctly deployed
[root@localhost charts]# kubectl describe rolebindings.rbac.authorization.k8s.io  redis-cluster-operator
Name:         redis-cluster-operator
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  meta.helm.sh/release-name: redis-cluster-operator
              meta.helm.sh/release-namespace: default
Role:
  Kind:  ClusterRole
  Name:  redis-cluster-operator
Subjects:
  Kind            Name                    Namespace
  ----            ----                    ---------
  ServiceAccount  redis-cluster-operator  default
[root@localhost charts]# kubectl describe roles.rbac.authorization.k8s.io  redis-cluster-operator
Name:         redis-cluster-operator
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  meta.helm.sh/release-name: redis-cluster-operator
              meta.helm.sh/release-namespace: default
PolicyRule:
  Resources                      Non-Resource URLs  Resource Names    Verbs
  ---------                      -----------------  --------------    -----
  configmaps                     []                 []                [create get list patch update watch delete]
  events                         []                 []                [create get list patch update watch delete]
  pods/exec                      []                 []                [create get list patch update watch delete]
  services                       []                 []                [create get list patch update watch delete]
  deployments.apps               []                 []                [create get list patch update watch delete]
  replicasets.apps               []                 []                [create get list patch update watch delete]
  statefulsets.apps              []                 []                [create get list patch update watch delete]
  jobs.batch                     []                 []                [create get list patch update watch delete]
  poddisruptionbudgets.policy    []                 []                [create get list patch update watch delete]
  *.redis.kun                    []                 []                [delete deletecollection get list patch update watch]
  redisclusterbackups.redis.kun  []                 []                [delete deletecollection get list patch update watch]
  persistentvolumeclaims         []                 []                [get list watch delete create patch update]
  secrets                        []                 []                [get list watch delete create patch update]
  endpoints                      []                 []                [get list watch delete]
  pods                           []                 []                [get list watch delete]
  namespaces                     []                 []                [get list watch]
  deployments.apps/finalizers    []                 [redis-operator]  [update]

Am I doing anything wrong?
Thanks

Changes from https://github.com/ucloud/redis-cluster-operator/pull/78 fixed the issue


Added chunk streaming docstrings and samples

This resolves https://github.com/Azure/azure-sdk-for-python/issues/17149 and https://github.com/Azure/azure-sdk-for-python/issues/11009

Aside from the changes being +99 lines (my ocd really kills me here lol), I love it :)
Thanks!

Well some changes were made now we're a little further away from that 100 :laughing:


Can't type anything if failed to parse ~/.XCompose file in Wayland

Which operating system does the issue occur on?
Archlinux
If on linux, are you using X11 or Wayland?
Wayland
With ~/.XCompose file below, alacritty opens but I can't type anything in it. This issues only occurs in Wayland, only when I have the ~/.XCompose file.

I've never used cage before. Does running Alacritty as a normal application work as expected?

These look like xkbcommon errors. I've never used XCompose before, but is the syntax actually correct? xkbcommon is telling you that your file contains too many errors, so I'd assume you'd probably want to fix those?
Does this work without any of these faulty binds set?

I've never used cage before. Does running Alacritty as a normal application work as expected?

Sorry, cage is just an example. I've reproduced the issue in sway and (the newly released) wio.

These look like xkbcommon errors. I've never used XCompose before, but is the syntax actually correct? xkbcommon is telling you that your file contains too many errors, so I'd assume you'd probably want to fix those?
Does this work without any of these faulty binds set?

The syntax is right. It just does't like the keysyms. It only fails after more than 10 of those errors.
The issue I wanted to raise is that alacritty should provide better diagnostics. It should just exit (with a good error message) if xkbcommon fails with parse error. I don't see the point of opening a window if I can't type in it. It confuses the user on what's going on.
I also find it strange that it works in X11 but not in Wayland.

We have absolutely nothing to do with how xkbcommon parses its config files.
That also means there's no way for us to tell if things will work or not. If the user breaks his system, there's little Alacritty can do to stop them.
If you desire xkb to handle the XCompose file without failing and falling back to a saner mode of operation by default, this should probably be addressed with xkb.
An error in Alacritty's configuration file should always be properly handled by Alacritty and never lead to failure, but with an error in system setup there's nothing Alacritty has control over.


Makes navbar sticky

Fixes Issue

Closes #137
Changes proposed

Make Navbar accessible when scrolling (Desktop and Mobile)
When scrolling, background colour is set to white
When having scrolled to top, background colour is reset to transparent
Navbar component now contains code for both desktop and mobile navbars

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Scrolling (Desktop)

Scrolled to top (Desktop)

Scrolling (Mobile)

Scrolled to top (Mobile)

Note to reviewers

Hi @reactdeveloperske. Is there any further action needed on this?

hey @octaviookumu could you run the following commands locally, related to the failing action, on your environment then push it in a new commit?

hey @octaviookumu could you run the following commands locally, related to the failing action, on your environment then push it in a new commit?

Okay. Let me do that. Thanks.

Btw I noticed some existing tests are failing. Also happening on develop branch.

Btw I noticed some existing tests are failing. Also happening on develop branch.

There seems to be an issue with webkit, thats why it's failing. Actively looking into it.

LGTM ✅


show more than 25 options, only show active options

show up to 50 Options (Sales Channels, Payment Methods, Shipping Methods) instead of default 25
only show active ShippingMethods, PaymentMethods and SalesChannels

Hi @bnussbau , thanks for your pull request. I will merge it.
This feature is implemented on the core of Shopware since 6.4.0 version, then I highly recommend using the feature in core instead of using this plugin.

Hi @bnussbau , thanks for your pull request. I will merge it.
This feature is implemented on the core of Shopware since 6.4.0 version, then I highly recommend using the feature in core instead of using this plugin.

There are still many shops that are not yet ready for 6.4. For some this plugin solves a big problem 👍

Hello @leduc92,
can you please elaborate which feature is contained in Shopware 6.4.x core? Is the whole plugin obsolete now? Can't find any reference to a similar functionality in the Shopware documentation.

Hi @Guite , there are a lot of new fields are added to Order in version 6.4.


karma "TDD Style"

I tried to run this on TDD style npm script, and

Problem 1: it with all my various test errors, it ran once and then hung.
Problem 2: If I stopped the task (ctrl+c) and ran it again, it had to find the next available port each time, so these instances were stacking up

FWIW: I was running in git bash on Windows 10.

That is weeird. Sadly I don't have any Windows box to debug.

Was hoping some other windows user would come on and say, "All you have to do us _____." I guess I'll have to try to debug it when I get the chance.

It's right after the console output of the coverage report that it hangs, so I wonder if that's where the issue is... In a way, I'm not as concerned about coverage while I'm writing the unit test - at each iteration, I minimally need it to run the test of the file I'm saving, or the test-file that I'm saving. The whole-shebang with coverage report,etc. I, for one, would be okay with running once at a time.

You can remove the coverage reporter at karma.

I added a karma.tdd.conf.js to my project, without either coverage report task, and it worked just fine as a watch / TDD task. I'm not sure that really solves the issue I was having, but it was a good workaround for getting things done.

We iterated a lot since here Sam. Is this still an issue? If so, open a new issue and we fix it.


update npm package to v2

updated to the free v2 set (380 icons)
removed a lot of not needed files
removed filled set (will work on this in the future)

update free npm icon package to v2


docs: improve cross-referencing with intersphinx

Closes #202
The commit 911ea15 is opinionated: it switches from autosummary to sphinx-apidoc.

Advantage: inherited members get documented as well and the API follows the code more closely (like if you add a new function, this set-up will automatically let it appear in the API).
Downside: the main API page looks less nice (can be improved a bit with jinja templates) and the pages are split up per module, not per function.

The commit can be reverted/kicked out if the disadvantages outweigh the advantages.

Another idea: switch to MyST. It is a superset of restructurettext and also allows the source code for the documentation to be formatted (with Prettier). More importantly, with MySt, Jupyter notebooks can also make use of intersphinx.

Also I'm the creator/maintainer of https://github.com/matplotlib/matplotlib-extension-cookiecutter so I'll happily merge any similar changes there if you want to contribute them (or any other opinions you have about how that should work)

Also I'm the creator/maintainer of https://github.com/matplotlib/matplotlib-extension-cookiecutter so I'll happily merge any similar changes there if you want to contribute them (or any other opinions you have about how that should work)

Ah yes, you mentioned. Ok, I'll keep an eye on it.
This PR was partially motivated though while trying out #201 and because I noticed intersphinx didn't work well with the API of mpl-interaction.

I have been wanting to do this for awhile but never got to it. Is it easy to switch over and get working on RTD? Also what's the breakdown of MYST vs jupyterbook they can both be used to generate docs and book builds on myst? Finally, would this be in addition to this PR or in-place of?

Oh and, good to hear! Nah can be done later on. That would indeed be a next 'upgrade'. For clarity:

MyST is just a Markdown flavour that has all functionality of restructured text (see myst-parser).
Then there is myst-nb, which extends that to Jupyter notebooks and can replace nbsphinx
Jupyter book is kind of an easier way to document things with notebooks and markdown files only, but it hides all the sphinx stuff and is therefore (afaik) less suitable for documenting a python package.
sphinx-book-theme mitigates that: you keep the same set-up, but get the fancy layout.

I think myst-nb and sphinx-book-theme can be implemented separately from switching to myst files.

Awesome - thanks for the explanation! Are you happy with where this is now?

Awesome - thanks for the explanation! Are you happy with where this is now?

Yep, looks fine I think.
Perhaps the contributing section needs to be rewritten a bit, but what is written there now is not invalid. I could write some words there later, perhaps it's better to tackle https://github.com/ianhi/mpl-interactions/pull/203#issuecomment-884417143 first.

Regarding switching to myst: that can be done easily with https://rst-to-myst.readthedocs.io

Perhaps the contributing section needs to be rewritten a bit, but what is written there now is still valid. I could write some words there later, perhaps it's better to tackle #203 (comment) first.

Yup. That sounds fine, plus I think the way described there will still work.
Thanks again!


Suggestion for new page in client side development

Introduction to using Webpack in ASP.NET Core
I think this would be useful like the gulp, grunt pages.

@danroth27  do we want this?
@damienbod  would you be interested in writing this?
[@]SteveSandersonMS  will review outline.

yes, should I start?

@damienbod  Yes, Post the outline first.

Document Outline:
1 Introducing Webpack
2 Preparing the application
..1. Using Webpack with npm
..2. Using Webpack with yarn
3 Configuring Webpack
..1. Production, Development builds, wwwroot
..2. Modules Typescript
..3. Modules SASS, LESS, CSS, HTML
..4. Chunking
..5. Hot Module Replacement
..6. Plugins UglifyJsPlugin, CleanWebpackPlugin, HtmlWebpackPlugin, CopyWebpackPlugin
4 Debugging with Webpack

@SteveSandersonMS @danroth27  please review

Regarding this list of topics, do you think they could be phrased in terms of things that are unique to ASP.NET? As it stands, it sounds like general-purpose Webpack docs that could apply to any web application platform.

@SteveSandersonMS
I did this, because this is how the gulp and grunt docs are written, which I think are done well. I decided to follow the same style. The contents will be ASP.NET Core or Visual Studio specific like the grunt/gulp docs.
Greetings Damien

Hey, @damienbod and me just talked about that.
Maybe the document could fulfill the unique ASP.NET  case in having the app in one folder inside Visual Studio (Code), building it into wwwroot, triggering it with a binding on starting or building the project and starting the production and development build out of Visual Studio.
Would that be worth a document?
Would love to help btw.
Fabian

I did this, because this is how the gulp and grunt docs are written, which I think are done well.

Can't we just point to their well written docs? We should just be documenting what's unique to ASP.NET Core.

@Rick-Anderson yes/no, I only want the documentate what you need to do inside Visual Studio to get Webpack working, or specific webpack configurations when working with an ASP.NET Core project, or publishing inside VS with ASP.NET Core or just using Webpack inside VS.
I was refering to the titles, which are as @SteveSandersonMS pointed out general. The titles are just subtitles. My suggestion for the title is "Introduction to using Webpack in ASP.NET Core" and the subtitles are the document outline.
Also I was thinking of documentating everything for Visual Studio, didn't think about Visual Studio Code.
?

@damienbod It would be great to include VS Code.

We do want to start moving the content around JavaScriptServices, which includes a bunch of webpack related functionality, but we should avoid trying to redocument webpack itself.

We had some proposed outlines in https://github.com/aspnet/Docs/issues/2461 that we should take into account.

@Rick-Anderson @SteveSandersonMS @FabianGosebrink @danroth27 @shanselman
I would like to start with this, if you want it. I suggest we continue with the document outline, and I will only add Visual Studio, Visual Studio Code, ASP.NET Core content. I will add links to the webpack docs as required. I would create an angular 4 template as a demo (not using JavaScriptServices) and demonstrate how to configure and use within Visual Studio/Visual Studio Code.
I have be maintaining an angular template for Visual Studio for a while (with @FabianGosebrink and @robisim74 ) and a lot of users seem to have problems setting up and using webpack, npm, yarn, typescript together with Visual Studio, Visual Studio code. I think it would be good that the typical problems be documented here.
https://github.com/damienbod/AngularWebpackVisualStudio
Greetings Damien

@damienbod  @FabianGosebrink  @fiyazbinhasan - we need to reconcile this with  Document using ASP.NET Core with Angular 2  #2461

agree on two separate docs; one which will only focus on using angular 2/4 with aspnet core and another, only focusing on using webpack. @damienbod can start on the webpack doc and in the using angular 2/4 with aspnet core @FabianGosebrink and me can refer to that doc whenever something related to webpack pops up. we wont go explaining stuff related to webpack in that using angular doc. We need a new modified outline for Document using ASP.NET Core with Angular 2 #2461
whats your suggestion @Rick-Anderson ?


OnStartCountdown triggers when players press the nuke button even if it's already counting down

Its intended so that you can cancel it with ev.Cancel

Oh, that makes sense, didn't think of that.


IPFS_PATH Folder Compatibility

Inside my go-ipfs generated ~/.ipfs folder, which is conected to a private IPFS network, I have the following item. I'd like to make sure we go through these one at a time with @vmx and/or @stebalien's guidance and determine which files or folders need to be compatible with js <-> go <-> rust.

api
config
datastore_spec
version
repo.lock
blocks
datastore
keystore
swarm.key

I'll get the ball rolling with my initial thoughts, which are:
The following feel like they're easy to make compatible, so we should:

api
version
swarm.key

The following probably doesnt need to be compatible:

datastore_spec
blocks
datastore

Special considerations:

keystore: should probably be compatible
repo.lock: may not be necessary, but if it is then its easy
config: as compatible as possible, considering fairly minor things like go-ipfs/go-libp2p protobuf encoded base64'd privatekey

That sounds right. Definitely keep api. Note:

go-ipfs is renaming the keys in the keystore, base32 encoding the names to avoid platform specific issues.
repo.lock: I'd definitely include this one.
config: depends on how much compatibility you want.

Also note, if you're planning on majorly breaking repo compatibility, I'd store your repo in a different directory (i.e., not IPFS_PATH/~/.ipfs).

Also note, if you're planning on majorly breaking repo compatibility, I'd store your repo in a different directory (i.e., not IPFS_PATH/~/.ipfs).

Alternatively, make sure it's possible to re-implement your changes in other languages. E.g., if you're going to change how something is encoded/formatted, call it a different thing so another IPFS implementation doesn't get confused.

@Stebalien Thank you for this insight! Super helpful and validating to know that we're mostly on the right track here.
When you say "call it a different thing" do you mean internally or at the public API level e.g. ipfs dag put should be ipfs dag putSomethingElse?
Maybe it's more case by case...

It depends. If you change how private keys are encoded in the config, call it something else (or, even better, don't store them in the config). If you decide to use toml/cbor to encode the config, call it config.{toml,cbor}.

Makes sense to me

Started looking at json compatible config in #95 which can be made to work, but I currently have no clue on how to get the openssl working on all platforms. The config crate, if we ever want to migrate to any other encodings as it might handle those quite transparently. Currently all of this is in the http crate so it exists mostly for the tests. Implementing the PrivateKey support was quite a chore.
Collecting the files from above under $IPFS_PATH (again, in the order of "easy to impl"):

api is filled in and truncated already
config as above, trying, generating rsa keys require openssl at the moment
repo.lock not set/checked yet, could easily do, same as api
version not set/checked yet
swarm.key nothing yet for this or private networks
keystore nothing yet, unsure if there are tests
datastore_spec, blocks, datastore nothing yet

swarm.key and keystore are completly out of grant scope, I think.
There is also consideration if the we mostly aim to provide a library to be used, could the configuration be provided all in rust and keep the "sort of compatible" stuff under "http". Even if going mostly-rust configuration, the repo.lock checking and setting might be good to catch misuse early when running conformance tests.

making the stores compatible seems like more effort than it's worth, and I don't see that it's within the grant scope as the grant is about http api compatibility if I understand correctly.

@dvc94ch You are correct. @Stebalien and @koivunej I've updated the issue description based on the consensus in this thread.

The updated description looks ok except for the version. I am hesitant to put anything in that file until (if ever) we are compatible with any of the repo versions.
This deliberation is valid currently only in the scope of rust-ipfs-http, perhaps we could even remove/rename the default impls in the library to pub fn from_env() or something like that and so that while an end developer can have the rust-ipfs point to a $IPFS_PATH this needs to happen deliberately. I'd see this being in line or an alternative solution to earlier:

[...] if you're planning on majorly breaking repo compatibility, I'd store your repo in a different directory (i.e., not IPFS_PATH/~/.ipfs).

Good point @koivunej. Moving that to "Does not need to be compatble"
I do having a way to report the datastore version may come in handy if other applications are doing reads on what's inside the IPFS_PATH folder. It doesn't need to match what Go or JS uses, it can be whatever and could may likely include rust or some signifier. e.g. 1.2-rust for the version

Closing this as I believe we have a good understanding here. Feel free to re-open if there are new thoughts, or open a new specific issue.

No cause to reopen but to document:

the /api/v0/version already returns empty string for repo, something I thought up above
I've already tried to connect two instances using the same keypair which resulted in difficult to debug situation with secio rejecting communications so we should get that repo.lock going :)

Indeed!


Make testnet faucet page more efficient by adding input validation

Telos testnet faucet page is inefficient. When content with wrong format is inputted, the page allows the user to submit them. This process is time consuming. Instead, the button should be disabled until the user enters the content in correct format.

Testnet Faucet URL: https://app.telos.net/testnet/developers

This page is already in being redesigned here: https://github.com/telosnetwork/app-telos-native/pull/335

Done in this PR


Can I render a book in landscape orientation?

I'm writing a book in kao and I'd like to generate a version of the book for desktop and tablet reading in landscape. If it's not a thing that can be easily implemented, how much effort would it take?

Hi, yes, it should be easy enough because the class has a way to globally choose a scale for the horizontal and a scale for the vertical dimensions. In the latest commit, I have made some stylistic enhancements and I have added the "a4paperlandscape" option as a proof of concept.
If you are OK with the A4 paper size, you can just download the latest from GitHub and make sure that the first line of the main.tex reads something like:
\documentclass[a4paperlandscape]{kaobook}

Otherwise, the easiest thing would be to implement another option for the paper size that you require; if you send me the the dimensions of the paper I can do that. You can also do it yourself taking inspiration from the "a4paperlandscape" option defined at line 115 of the file styles/kao.sty.

Oh, Thank you. A4 works for me just fine.


TOMEE-3846 improve documentation

this is the "per-version" comparison page for v8

ready for review and open to feedbacks

commits squashed

Sorry, I forget to click "submit" on my PR comments yesterday.

i was able to take into account all these feedbacks, thank you again


It is a compile-time error to use "return;" without value.

Tests:
language_2/void/return_future_or_void_sync_error4_test/none
language_2/void/return_future_future_or_void_async_error1_test/none
language_2/void/return_future_or_future_or_void_sync_error2_test/none
language_2/invalid_returns/async_invalid_return_03_test/none
language_2/invalid_returns/async_invalid_return_02_test/none
language_2/invalid_returns/sync_invalid_return_01_test/none
language_2/invalid_returns/sync_invalid_return_04_test/none
language_2/invalid_returns/async_invalid_return_01_test/none
language_2/invalid_returns/sync_invalid_return_02_test/none
language_2/invalid_returns/sync_invalid_return_05_test/none
language_2/invalid_returns/sync_invalid_return_03_test/none
language_2/invalid_returns/async_invalid_return_00_test/none
language_2/invalid_returns/sync_invalid_return_00_test/none
language_2/invalid_returns/async_invalid_return_04_test/none
co19_2/Language/Errors_and_Warnings/static_warning_t01
co19_2/Language/Statements/Return/no_expression_function_t01
co19_2/Language/Statements/Return/no_expression_function_t16
co19_2/Language/Statements/Return/no_expression_function_t10
co19_2/Language/Statements/Return/many_return_statements_t02
co19_2/Language/Statements/Return/no_expression_function_t07
co19_2/Language/Statements/Return/no_expression_function_t11
co19_2/Language/Statements/Return/no_expression_function_t04
co19_2/Language/Statements/Return/no_expression_not_function_t01
co19_2/Language/Statements/Return/no_expression_function_t08
co19_2/Language/Statements/Return/no_expression_function_t09
co19_2/Language/Statements/Return/no_expression_function_t05
co19_2/Language/Statements/Return/no_expression_function_t02
co19_2/Language/Statements/Return/no_expression_function_t03

It's valid if the return type is void, dynamic, or Null (or if the flattened return type is for asynchronous non-generator functions).  For the other cases, we have been discussing with the language team that this will probably have to continue to be a warning, because making it an error is a breaking change.
I guess the issue for the language team is to make a decision and update the feature spec at https://github.com/dart-lang/sdk/blob/master/docs/language/informal/invalid_returns.md.

@kmillikin, you mention updating invalid_returns.md, but it's not obvious to me what we'd make a decision about. Could you elaborate?

Yes, exactly.  It was decided that return; from a function with a return type other than void, dynamic, or Null would be a warning and not an error.  The feature spec does not say that (it says "is an error" which seems wrong unless it's just being vague and you mean it's a warning.)
The feature spec needs a number of other updates:
It does not say what happens for an invalid return in the first part.  Is it a compile-time error?  Warning?  Runtime error?  Something else?  It should be made clear.
It only characterizes the valid returns and does not ever say "and all other returns are invalid" which it should.
The second part says that the invalid returns are errors.  Are they compile-time errors?  Runtime errors?  If it's meant to be an alternative and equivalent treatment then each part should stand alone.  As I mentioned above, it should be explicit about which are errors and which are warnings.

Indeed, thanks! I hadn't seen that return_without_value was among those, and we certainly need to update several documents (I thought that it would only involve dartLangSpec.tex). Added a note about this to #34349.

This CL adjusts dartLangSpec.tex such that the compile-time error mentioned above is changed to a warning.

Said CL was landed as e4e82da85d8b12916dcd54480b019dca76c12bc5.
@kmillikin wrote:

status .. confusing .... rename .. to invalid-returns.md

The status is now 'background material .. please consult the language specification'. This would be less ambiguous, and it makes the need to rename less urgent, so I'll consider those issues to be resolved at this point.

invalid returns are errors. Are they compile-time errors? Runtime errors?

The language specification text is explicit on this topic, for example, so I think this has been resolved as well:
It is a compile-time error if $s$ is \code{\RETURN{};},
unless $T$ is \VOID, \DYNAMIC, or \code{Null}.

I believe that there are no remaining 'area-language' issues here, so I'll remove that label.

The treatment of warnings in Dart is currently being revisited by the language team, cf. #36126 and #36127, so I'm marking this issue as blocked until it has been decided exactly which situations will be errors and which ones will be warnings (if any).


XRPL asset list

Hello,
I'm trying to compile a list of tokens which are available on the XRPL.
I can't seem to find an API method to answer this question. It seems, I would need to iterate over all accounts on the XRPL and call account_currencies method?  Any suggestions on the best approach?
Thanks!

Not really an issue of this library, but you can find a list here: https://xrpl.services/tokens


[Bug]: The git connect  doesnt seems to be working in air gapped instance

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The git connect  doesnt seems to be working in air gapped instance

Steps To Reproduce

first pull the image docker pull ankitakinger/appsmith:airgap
now switch off the internet
now docker run -e APPSMITH_AIRGAP_ENABLED=true -e KEYGEN_LICENSE_VERIFICATION_KEY=b2b98c313548c14cb22ddb4afb9124553c4c829c290d8a3cbf01ff8ee57624dc -d --name appsmith-airgap -p 80:80 -v "$PWD/stacks:/appsmith-stacks" ankitakinger/appsmith:airgap
Also run docker run --name appsmithted -d -p 22:22 -p 5001:5001 -p 3306:3306 -p 28017:27017 -p 5432:5432 -p 25:25 -p 5001:5001 -p 3001:3000 -p 6001:6001 appsmith/test-event-driver
Now do the set up
add air gapped license key
go to home page
Go to edit mode click on the connect  git button
follow below setps in video to connect to git

https://user-images.githubusercontent.com/45958978/232005467-6a8b80a0-63bb-4f58-bae9-72e0b631ffb1.mov
Public Sample App
No response
Environment
Release
Issue video log
No response
Version
release

This was set up problem not a issue closing the issue


encryptAsync thread never exits

When calling:
Future<KeyOperationResult> result = vc.encryptAsync(keyIdentifier, JsonWebKeyEncryptionAlgorithm.RSAOAEP, byteText);
The one thread created never exists even after the result is returned from
KeyOperationResult keyoperationResult = result.get();
and the main thread has ended

@pomortaz

the KeyVault client library is not in this repo anymore, so if this is still an issue, it should go there:
https://github.com/azure/azure-keyvault-java


Add corral to windows .dockerfile images

Currently only has ponyc.

@kulibali ping to put this on your list.


I SCREWED UP...

Hacking the two Gran Turismo 5 online trophies I made a mistake and put the wrong month in one of them. Now that trophy is dated before I created my psn account and it was synchronized.
Opinions? Anyone in the same or similar situation?
Thanks.

I think we can get throphy before you create PSN account.

Yes, the problem is that these two trophies are online and require a connection to PSN.


Recommend to keep the visibility of the top-level identifiers

If the new package starts with ".", All top-level identifiers will have prefixes to prevent conflicts, and their uses will also be updated.
for example, I use ".int" package name to generalize queue, the "New" function will rewrite to "intNew", this changed the visibility of the template function "New". If I used ".Int", it may changed the visibility of those identifiers started with lower case character. So I recommend to keep the visibility of the top-level  Identifiers.

I think this issue only applies to .result package target.
Do you have a suggestion to keep top-level identifiers to be exported while we still have prefixing?
For me, it is nice to have all top-level identifiers unexported:

prefixed identifier name is ugly for exported API.
Although it was exported, it might not be needed to be exported after rewrite under the new package.

If it is needed, I often create aliases in the current package in another file like:
func New() *IntQueue {
   return intNew()
}

I think the simple rule is : if top level identifier start with lower case character, then Chang the prefix first letter to Lower case, vice versa.

prefix in general should be all lowercase yyy. Could you explain more about your idea if the generic package has uppercase top-level identifiers, like Xxx? The current behavior is yyyXxx.


WebVR demo doesn't detect Microsoft Edge

Tried the WebVR demo with Edge (on an Acer HMD) and it shows "No VR Device Detected". Other WebVR demos seem to work OK so it doesn't seem like a generic Edge issue.

The WebVR spec is in flux, and the demo hasn't been updated in a while. However, it looks like the getVRDevices API has been replaced with getVRDisplays in the most recent spec.
Can you try changing that in the demo and see if it works? Unfortunately, I can't do it myself because I don't have access to a VR device running Edge. I've tried the demo in a Google Pixel and it works (possibly because the older API is still supported).
Feel free to send a pull request if you manage to fix it!

I've updated the WebVR demo to work with the latest spec, and tested it on a Google Cardboard. Note that the demo on http://www.marzipano.net is still the old version; only the GitHub master branch is up to date.
Please reopen if it still doesn't work with other WebVR displays.


Windows path prevents vue-test-loader from working

When building any project using vue-test-loader in windows, the way index.js is written (line 4 uses a hard-coded '/' instead of node's path module), the full path is used when building the destination.
To fix this and make it compatible with all operating systems, replace the latest index.js with this (adding path, using it in const filename = and changing the const path to const dest at the bottom):
const fs = require('fs')
const path = require('path')
module.exports = function(source) {
const filename = require('path').parse(this.resourcePath).name
const extension = '.spec.js'
const dir = ${this.context}/${this.options.extension || '__tests__'}
if (!fs.existsSync(dir)){
fs.mkdirSync(dir);
}
const dest = ${dir}/${filename}${extension}
fs.writeFileSync(dest, source.replace(/('../)/g, "'../../").replace(/('./)/g, "'../").trim())
return source
};

The fix is released in 0.4.1 😀


TestMetricDbSizeDefrag fails in proxy test mode

--- FAIL: TestMetricDbSizeDefrag (2.51s)
	metrics_test.go:84: when db size is growing, db size (196608) and db size in use (192512) is expected to be equal

https://jenkins-etcd.prod.coreos.systems/job/etcd-proxy/4091/console
in proxy tests

@gyuho Can I see the detail of the test case? (Can I run the test locally?)

@yudai Sorry, don't have much details, another failure
=== RUN   TestMetricDbSizeDefrag
WARNING: 2018/02/08 18:05:00 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: Error while dialing context canceled"; Reconnecting to {localhost:77032179972776892950 0  <nil>}
WARNING: 2018/02/08 18:05:00 grpc: addrConn.transportMonitor exits due to: context canceled
--- FAIL: TestMetricDbSizeDefrag (2.60s)
	metrics_test.go:84: when db size is growing, db size (200704) and db size in use (196608) is expected to be equal

Seems machine-specific, can't reproduce either in my local machine:
go test -v -tags cluster_proxy -run TestMetricDbSizeDefrag

@gyuho Thanks for the info.
From the log, apparently the db size varies every time.
If I understand correctly, even when +build cluster_proxy,  it replaces just toGRPC
I guess that there are concurrent test cases running at the same time, or the  db is not cleaned up when the test case starts. Getting those two metrics are not an atomic operation, so it can be not equal when there are other requests from the out side of the test case.

I think I succeeded to reproduce the test failure without the tag.
The test case issues 25 put requests. When they are handled by a single batchTX in the backend, that's fine. However, when there are some slow requests (maybe because the machine is just slow?), unsefePut() calls for those requests are committed by multiple transactions. In this case, boltdb shows a bit inefficient behavior that leaves some free pages.
I think, it turned out that  "when db size is growing, db size and db size in use is expected to be equal" is not always true, so we can simply remove this check from the test case.


Fix/translation functions fixes (#8)

I see - checks are failing with "E501 line too long (116 > 100 characters)", ie:
https://github.com/ezrajrice/django_advanced_password_validation/actions/runs/5528529600/jobs/10095161044#step:6:20
I have reformatted source files with black lets see result of checks now

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

13 of 13 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
228

Relevant Lines:
228

💛  - Coveralls

The tests are now passing. It looks like there might be something wrong with the Lint action using Black. I need to go in and check it. I don't think you need to do anything else on your end. Thanks for the PR!

Black started failing within GH Actions. Since the code was formatted with Black locally before pushing, I'm okay with merging this now.

@ezrajrice thanks for quick action and merging


Reset fields does not work without validation rules(even empty works)

ElementUI version
1.1.6
OS/Browsers version
Windows 8/Chrome 56
Vue version
2.1.10
Reproduction Link
http://jsfiddle.net/0bsw8uta/1/
Steps to reproduce
Create any form without validation rules and call resetFields
What is Expected?
The fields should get reset to empty values
What is actually happening?
Nothing happens. The reset works only if there are validation rules attached(even empty dummy ones)

Validation rules are not required for resetFields to work. You just need to add the prop attribute on el-form-item: http://jsfiddle.net/0bsw8uta/2/

Thank you. I thought adding prop needed validation rules. If you don't mind me asking, what is the purpose of the prop field?

https://github.com/ElemeFE/element/blob/dev/packages/form/src/form-item.vue#L151
https://github.com/ElemeFE/element/blob/dev/packages/form/src/form-item.vue#L24
You can see it for yourself :)


Uncaught TypeError: parsedResponse[2] is undefined

No hostname is shown, no current working directory, in Console tab in developer tools this error on calling getShellInfo();. PHP is installed.

It seems like request.responseText is an empty string. Could this be a server misconfiguration?


CI failing

The CI is failing with the following errors

[!] [2022-06-28 04:31:44] unable to get container ohp_sshserver_strong_password IP address
[+] [2022-06-28 04:31:44] Network capture is getting stored in, /home/runner/work/Python-Honeypot/Python-Honeypot/pcapfiles/captured-traffic-1656390704.pcap
[X] [2022-06-28 04:31:44] Interrupting the application because "ohp_sshserver_strong_password" container(s) is(are) not alive!

@dhirensr @Ali-Razmjoo do you have any idea regarding this

merge master to your old branch, the bug is fixed now.

What was the issue


[22280] Add documentation for preferred_key_agreement property

Description

This adds documentation for the new property allowing the selection of the preferred key agreement algorithm.

Related implementation PR:

eProsima/Fast-DDS#5413

Contributor Checklist

[x] Commit messages follow the project guidelines.
[x] Code snippets related to the added documentation have been provided.
[x] Documentation tests pass locally.
[ ] Applicable backports have been included in the description.

Reviewer Checklist

[x] The PR has a milestone assigned.
[x] The title and description correctly express the PR's purpose.
[x] Check contributor checklist is correct.
[x] CI passes without warnings or errors.

@Mergifyio backport 3.1.x


fix: LG file diagnostics not always sync.

Description
Our current LG re-parse would only triggered by it's content change. for example

update 'common.lg', re-parse 'common.lg',
update 'hello.lg', re-parse 'hello.lg';
to keep minimal re-parse will improve client performance.

But the issue happens in scenarios need cross file validation, do the following steps:

in 'hello.lg', refer a template named 'Welcome' imported from 'common.lg'
change a template name from 'Welcome' to 'Welcome1' in 'common.lg'.

'hello.lg' would not be able to update it's diagnostics, cause re-parse only happen on 'common.lg'
The solution is

when update on 'common.lg', re-parse all lg files. because 'common.lg' maybe referred by other lg files.
when update on 'hello.lg', still only re-parse 'hello.lg' itself. because 'hello.lg' suppose to be standalone.

it can reduce file diagnostics not sync issue, but not totally solve it.

Task Item
close #3884

Screenshots

Coverage increased (+0.02%) to 55.181% when pulling 252a3e60b568b204909e0579f0cd9ebd8c8db6db on zhixzhan:zhixzhan/lgfiles-reparse into 9ae72371adaa327086534a18232e4f3217e48071 on microsoft:main.


fixed Japanese garbled page

Japanese strings in DI server:
http://localhost:9080/pentaho-di/kettle/status
are garbled.
normal strings:

garbled strings:

@mattyb149 @brosander @pentaho-nbaker Please review and consider including especially since this is a very small change and that there a 2 useful unit tests being added...

As mentioned right in the ServletResponse javadoc, writing character data into the response should be done by obtaining the Writer. Good fix!
http://docs.oracle.com/javaee/5/api/javax/servlet/ServletResponse.html.

Thanks, David and Nick!


flow not parsing global declarations in top-file comment

// @flow
/* global requestAnimationFrame */
...
requestAnimationFrame(gameloop)

src/index.js:175
175: requestAnimationFrame(gameloop)
     ^^^^^^^^^^^^^^^^^^^^^ identifier `requestAnimationFrame`. Could not resolve name

Is this intended? Or a bug?
In case of it not being supported, is it because it's not a "standard" or?
Cheers!

https://github.com/facebook/flow/blob/master/lib/dom.js#L2963
include requestAnimationFrame

@hufeng Can you show what you are suggesting? Is it a change on the flowconfig file?

use flow 0.37.3

If you can't  upgrade to flow 0.37.3 yet, you could just do this:
Create a libdef file overriding / adding the requestAnimationFrame declaration:
// flow-typed/override-dom.js

declare function requestAnimationFrame(callback: (timestamp: number) => void): number;

And make sure the  .flowconfig picks up the flow-typed directory:
[libs]
flow-typed

Restart flow and now you should have proper typings for requestAnimationFrame

@ryyppy cool!

Is it possible to declare an object? Another global that exhibits this same behavior in Flow is Intl but its an object rather than a function.

declare var Intl: Object

seems to do the trick!


RFC - Interval for schedules

I would like to be able to run tasks on custom intervals, such as every 6 hours, or every 2 weeks, etc. The Minutes schedule type has this feature in that a schedule can be run every specified set of minutes.
In my mind, it would be useful to generalize the "minutes" field to an Interval field so that all schedules types could be run on custom intervals. This would be a backwards incompatible change if the "minutes" column was removed, so I thought I'd ask if there's any interest in such a feature. If there is, I'd be interested in submitting a PR.
Any thoughts?

I like the idea of having a custom interval.
I don't mind having backwards incompatible changes not sure how @Koed00 thinks about it.


GH-36483: [C++] Make UTF8StringToUTF16 and UTF16StringToUTF8 accept string_views

Rationale for this change
As @kou pointed out in #36366, it's better to pass read-only string data via  as string_views than as const references. I recently submitted two new functions called UTF8StringToUTF16 and UTF16StringToUTF8, both of which accept const references. This PR changes the signatures of those functions to accept string_views.
What changes are included in this PR?
Changed the function signatures of UTF8StringToUTF16 and UTF16StringToUTF8:

arrow::Result<std::u16string> UTF8StringToUTF16(const std::string& source) ->
arrow::Result<std::u16string> UTF8StringToUTF16(std::string_view source)

arrow::Result<std::string> UTF16StringToUTF8(const std::u16string& source) ->
arrow::Result<std::string> UTF16StringToUTF8(std::u16string_view source)

Are these changes tested?
Uses existing tests in utf8_util_test.cc

Are there any user-facing changes?
No.
Only the MATLAB Interface uses these functions, so  I don't expect these changes to break anyone's code:

Search results for UTF8StringToUTF16
Search results for UTF16StringToUTF8

Closes: #36483

I believe the failures are unrelated to the changes in this PR.


Files all marked as Viewed before reviewing them

Testing #3985

Authenticate
Refresh the GitHub view
Before browsing any file, reload the window
After window reload, all files are marked as viewed

I'm not able to reproduce this. Are you able to reproduce it consistently?


fix: strip dotgit to repo url

Why
I use a slightly different mechanism to access the repos. Instead of doing
repo = Repo(dir)

I do
    repo = Repo.clone_from(repo_url)

This adds a .git to the end of the repo name, and then fails all the API calls which should not be made with the .git url (such as https://github.com/irgolic/AutoPR/blob/57186dc5b1515b7e8ab6fe5c6f3908933f5bfc55/autopr/services/publish_service.py#L39-L48)
How
Stripping the .git works. We could also swap the raw API calls with more use of the GitPython library, but it's a slightly larger change.

Hey, thanks so much for the contribution <3
Could you replace rstrip with removesuffix? rstrip actually removes all characters matching any of the characters in the argument, while removesuffix only removes the argument itself.

Oh wow, I had been using rstrip wrong all my life ... Thanks


Added optional secret name for private registry

When someone is using private registry (eg, gitlab) we need to create secret so we can execute pull on the specific ingres-nginx-backend image.

 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.Pawel Grzesik seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Should this be closed?


[Questtion] How do I make a mutually exclusive key?

I would like to have a config with either a value or an object, but with a name that matches the type - e.g., userId: z.string() XOR userIds: z.object(). I need exactly one of them to exist, like an XOR of keys. Is there a way I can express this type with zod?
{
    // input can be a single value for all options, or specify a different value for each option
    "userId": "abcd",
    "userIds": {
        "xyzw": "abcd",
        "ijk": "hjkl"
    }
}

I suppose I could wrap the entire thing in a z.union(), but that feels pretty unwieldy, especially if/when the number of fields (and thus the number of combinations) explodes:
const schema = z.object({
    myMultiFormThing: z.union([
        z.object({ /* machineId = string, userId = string, groupId = string */ }),
        z.object({ /* machineId = string, userId = string, groupIds = array */ }),
        z.object({ /* machineId = string, userIds = array, groupId = string */ }),
        z.object({ /* machineId = string, userIds = array, groupIds = array */ })
    ])
});

Fortunately my config is not that complex yet, and worst case scenario I guess I can live with having the same key name for an object and value, but it would be nice if I can use the correct plurality for the key name.

I think I'd recommend just using the same key in this circumstance. Otherwise you're kinda working against TypeScript, since it can't represent XOR types natively.
Alternatively you can implement the XOR logic in a refinement but it isn't reflected in the static type signature - both fields are optional in this scenario.
z.object({
  userId: z.string(),
  userIds: z.string().array(),
}).refine(
  (val) => {
    // XOR
    return !!val.userId ^ !!val.userIds;
  },
  { message: "Specify userId or userIds" }
);

I have similar problem.
I need to write a schema for a query which can be {} or { project: 123 } or { task: 123 }. In this query project and task can not be present together in the same query. Then I can have other parameters like { archived: false } which can be present in any query.
Currently what I am doing is:

const mutuallyExclusiveKeys = [ 'project', 'task'] as const

const QuerySchema = z
  .object({
    project: z.string().optional(),
    task: z.string().optional(),
    archived: ZodStringToBoolean.optional(),
  })
  .refine(
    (data) => {
      const presentKeys = keys.filter((key) => data[key] !== undefined)
      return presentKeys.length <= 1
    },
    {
      message:
        `Only one of ${mutuallyExclusiveKeys.join(', ')} can be present in the query`,
    }
  )

Is there a better way to achieve this ?


Added local to avoid confusion regarding location

Location of file isn't clear: in WRDS cloud or local

Thanks for the note! I've added "local" to the README in order to clarify that we meant on the user's machine, not on wrds-cloud.


features that might be useful

Source name
not the actual scan
Source language
English
Describe your suggested feature
wouldn't it be better if we could lock the pages we choose?
Other details
I mean, in this application we can add several other pages besides the main page, wouldn't it be better if there was a page privacy feature, to protect user privacy.
So I can put some manhwa that only I can open on this phone, I'm just annoyed when other people open my 2nd page just because of the manhwa genre they don't like.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I have updated the app to version 0.15.3.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

This is an extension repo, not an app, go check with them instead.


Upload gobang to Some package management systems

[ ] Homebrew (not tap)
[ ] AUR
[ ] scoop
[ ] Ubuntu package

https://github.com/TaKO8Ki/gobang/issues/97

In Ubuntu
Is it not good to put binary execute file (not ZIP) generated by compiling for static linking  in releases ?
If so, we can install by the following commands
sudo curl -Lo /usr/bin/gobang  https://github.com/TaKO8Ki/gobang/releases/XXXX
sudo chmod +x /usr/bin/gobang


[AutoPR applicationinsights/resource-manager] Java tags1

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3324

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/2166


[BUG] Doc broken links Contribute to this page

Bug report
It seems all the links to Contribute to this page are broken.
e.g.
Contribute to this page

Thought I fixed this, thanks for reporting the issue!
It seems something is adding a / before the . in the file name (index.md => index/.md)

I just DMed to your twitter telling I will be happy to contribute to the doc using Flowbite-Svelte. If you are interested, please let me know. If you are not, that's fine too. 😁

Thanks for reaching out, but I'm fine with what I got right now. I'm done with the docs for now and want to avoid major changes to it. For the sake for transparency, please avoid DMs (both on Twitter and on Discord). Also, it would've been better to open a new issue since it's unrelated to the original issue.

I would like to contribute to resolving this issue

Seems like its something in the BaseLayout

Still not resolved.


Typings for module

I'm going to use your module in application node+typescript.
What about *.d.ts file for 'array-uniq'?
Is it possible to add typings?

Sorry, it's better to publish them to DefinitelyTyped https://github.com/sindresorhus/ama/issues/439

I now accept TypeScript definitions if anyone looking is interested in submitting it here.
See: https://github.com/sindresorhus/ama/issues/439#issuecomment-414212229
Please follow this guide: https://github.com/sindresorhus/typescript-definition-style-guide


Use sanitize() instead of a regex to sanitize latex output

Fixes #107.

Looks good to me. Thanks!


pascal's triangle in c

🚀 Feature
pascal's triangle in c
Have you read the Contributing Guidelines on Pull Requests?
yes
Motivation
pascal's triangle is a triangle of binomial coefficients
Pitch
pascal's triangle has lots of applications in mathematics and computer science

/assign


cmake.cmakePath does not resolve environment variables from cmake-tools-kits-json

Brief Issue Summary
From cmake-tools-kits.json we use this entry
{
"name": "Ipetronik-Logger (x86 Develop)",
"environmentVariables": {
"IPE_CMAKE_TARGET": "x86",
"IPE_EMBLX_PATH": "/home/fabrice/embeddedLinux/Develop/x86_build_develop"
},
"toolchainFile": "/home/fabrice/embeddedLinux/Develop/x86_build_develop/host/usr/share/buildroot/toolchainfile.cmake",
"isTrusted": true
},
Try to use the environment variables "IPE_EMBLX_PATH" and "IPE_CMAKE_TARGET" in settings.json like this
"cmake.cmakePath": "${env:IPE_EMBLX_PATH}/build/host-cmake-3.16.9/bin/cmake",
"cmake.buildDirectory": "${workspaceFolder}/build/${buildType}/${env:IPE_CMAKE_TARGET}",
"IPE_CMAKE_TARGET" in cmake.buildDirectory is correctly resolved. But "IPE_EMBLX_PATH" in cmake.cmakePath is always empty
Bad CMake executable: "/build/host-cmake-3.16.9/bin/cmake". Check to make sure it is installed or the value of the "cmake.cmakePath" setting contains the correct path
There are already simular issues around the substitution of environment variables. But I'm not sure if this point fits in anywhere.
CMake Tools Diagnostics
{
  "os": "linux",
  "vscodeVersion": "1.82.0-insider",
  "cmtVersion": "1.14.34",
  "configurations": [
    {
      "folder": "/home/fabrice/IPEmotionRT/DevelopNeu/IPEmotionRT",
      "cmakeVersion": "unknown",
      "configured": false,
      "generator": "unknown",
      "usesPresets": false,
      "compilers": {}
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [
      "file:///home/fabrice/IPEmotionRT/DevelopNeu/IPEmotionRT/packages/PcixcanxlinDriver/drivers/ipetronik/pcixcanxlin/hwpcixcanxlin.c"
    ],
    "responses": [],
    "partialMatches": [],
    "targetCount": 204,
    "executablesCount": 41,
    "librariesCount": 104,
    "targets": []
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": null
    }
  ]
}

Debug Log
No response
Additional Information
No response

Thanks for the report. cmake.cmakePath is documented as supporting ${env:...} substitution, but it's possible that the kit environment variables aren't being applies before evaluating the substitution. I'm marking this as a bug that we hope to investigate in the 1.16 release.

Hi, @pickard1.
Due to having zero upvotes from the community and the niche scenario, rather than implementing this addition to our ${env:<>} expansion for the cmake.cmakePath, we would suggest that if you want to have configuration specific cmake executables, to switch to CMakePresets! Configure Presets in CMake Presets allows you to specify configuration specific cmake executables through the cmakeExecutable field. https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#configure-preset
Closing as won't fix. Please create an issue for any problems you hit if you switch to CMakePresets!
A very simple stub for a Configure Preset would be the following (you'll likely want to add more information to fully control what compilers you use, etc.)
{
            "name": "Ipetronik-Logger",
            "displayName": "Ipetronik-Logger (x86 Develop)",
            "environment": {
                "IPE_CMAKE_TARGET": "x86",
                "IPE_EMBLX_PATH": "/home/fabrice/embeddedLinux/Develop/x86_build_develop"
            },
            "cmakeExecutable": "${env:IPE_EMBLX_PATH}/build/host-cmake-3.16.9/bin/cmake"
        }


IdFromPlayer(player) and IdFromConnection(connection) library functions

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/15770354-idfromplayer-player-and-idfromconnection-connection-library-functions?utm_campaign=plugin&utm_content=tracker%2F6855523&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F6855523&utm_medium=issues&utm_source=github).

Covalence will be replacing library functions, so this won't be needed.


Config overriding location should already be created

/mnt/wso2/carbon-home is used as a manual extension location where overridden files relative to CARBON_HOME is copied from. Currently this location is not created in the Dockerfiles. This should be created and readied for the derivative Dockerfiles to use COPY instructions.

Not exactly. This is a mount point to which a volume or host folder can be mounted.


Add env based configurations

Codecov Report

Merging #53 into develop will increase coverage by 1.48%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop      #53      +/-   ##
===========================================
+ Coverage    95.59%   97.08%   +1.48%
===========================================
  Files           21       23       +2
  Lines          409      446      +37
===========================================
+ Hits           391      433      +42
+ Misses          18       13       -5

Impacted Files
Coverage Δ

src/config/sandbox.js
100% <ø> (ø)

src/config/staging.js
100% <100%> (ø)

src/services/AuthService.js
94.33% <100%> (ø)
:arrow_up:

src/routes/userRoutes.js
100% <100%> (ø)
:arrow_up:

src/config/develop.js
100% <100%> (ø)

src/routes/fhirRoutes.js
100% <100%> (ø)
:arrow_up:

src/routes/authRoutes.js
100% <100%> (ø)
:arrow_up:

src/routes/documentRoutes.js
76.92% <100%> (ø)
:arrow_up:

src/services/ZeroKitAdapter.js
98.19% <100%> (+7.17%)
:arrow_up:

src/lib/EncryptionUtils.js
100% <100%> (ø)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Source and Target handle getting null

Describe the Bug
While trying to add the edges using onConnect where we are using the hook to add the edges its throwing a warning like
"Couldn't create edge for source handle id: "object-0.6916853697528522-handle-bottom-e1045f27-c677-4048-a78b-1c79adaacc17", edge id: edge-0.5969621633747138." and from the documentation its found that we have added the id property for the source handles as well.
On further debugging its found that the sourceHandle and targetHandle is getting null value due to which its throwing the error.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Create two custom nodes
Add multiple handlers
Use a hook for the onConnect Props to add edges.
Try to draw an edge from one source handler to target handler
Edges are not visible.

Expected behavior
As a user expect to see the edges from one node to another.
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]
OS :Windows
Browser: Chrome

Additional context
No response

Can you please create a Sandbox with a reproduction for this? You can also fork an example if that's easier.

@peterkogo Can you please help us to resolve the issue. We have added the code to code sandbox.

Your sandbox has a number of issues that prevent one from even seeing the app :(
After I did some manual patches to get it working and looking at it (although still not quite working correctly) I believe your issue comes from the fact that you simply remove <Handle> components from the DOM when there's no selectedLink anymore.
That's not gonna work.
Edges need to have a <Handle> - it's not optional.
If you want to "hide" the handles, use opacity: 0 for example. That way the handle is not visually not present but still in the DOM and can be used for calculations etc.

Thank you for your help, you were right.
I changed my customNode handle logic from this :
{!isEmptyObject(selectedLink) && data && data.handleIds && (
        <>
          <Handle type="target" position={Position.Top} id={data.handleIds.top} />
          <Handle type="source" position={Position.Bottom} id={data.handleIds.bottom}  />
          <Handle type="target" position={Position.Left} id={data.handleIds.left}  />
          <Handle type="source" position={Position.Right} id={data.handleIds.right}  />
        </>
      )}

to that
{data && data.handleIds && (
        <>
          <Handle
            type="target"
            position={Position.Top}
            id={data.handleIds.top}
            style={{ opacity: !isEmptyObject(selectedLink) ? 1 : 0 }}
          />
          <Handle
            type="source"
            position={Position.Bottom}
            id={data.handleIds.bottom}
            style={{ opacity: !isEmptyObject(selectedLink) ? 1 : 0 }}
          />
          <Handle
            type="target"
            position={Position.Left}
            id={data.handleIds.left}
            style={{ opacity: !isEmptyObject(selectedLink) ? 1 : 0 }}
          />
          <Handle
            type="source"
            position={Position.Right}
            id={data.handleIds.right}
            style={{ opacity: !isEmptyObject(selectedLink) ? 1 : 0 }}
          />
        </>
      )}

and it works perfectly.


investigate valgrind failure in CI coming from Nokogiri_wrap_xml_node_set

Describe the bug
CI picked up a valgrind failure that's concerning for two reasons:

the stack walkback shows it's happening in Nokogiri code
the rest of the stack walkback is suspiciously similar to the stacks we're suppressing, which means maybe we're getting false positives

To Reproduce
Occurrence is here: https://ci.nokogiri.org/teams/nokogiri-core/pipelines/nokogiri-pr/jobs/ruby-libxmlruby-valgrind/builds/57
Stack walkback is:
==9855== Invalid read of size 8
==9855==    at 0x49279A0: mark_locations_array (gc.c:4682)
==9855==    by 0x4930090: gc_mark_stacked_objects (gc.c:5503)
==9855==    by 0x4930090: gc_mark_stacked_objects_incremental (gc.c:5537)
==9855==    by 0x4930090: gc_marks_step (gc.c:6442)
==9855==    by 0x4930090: gc_marks_continue (gc.c:6502)
==9855==    by 0x4930090: heap_prepare (gc.c:2018)
==9855==    by 0x4930090: heap_get_freeobj_from_next_freepage (gc.c:2035)
==9855==    by 0x4930090: heap_get_freeobj (gc.c:2074)
==9855==    by 0x4930090: newobj_slowpath (gc.c:2218)
==9855==    by 0x4930090: newobj_slowpath_wb_unprotected (gc.c:2236)
==9855==    by 0xB6F02FD: Nokogiri_wrap_xml_namespace (xml_namespace.c:84)
==9855==    by 0xB6F32D3: reify_node_set_namespaces (xml_node_set.c:393)
==9855==    by 0xB6F32D3: Nokogiri_wrap_xml_node_set (xml_node_set.c:415)
==9855==    by 0xB6F7944: evaluate (xml_xpath_context.c:236)
==9855==    by 0x4AAA168: vm_call_cfunc_with_frame (vm_insnhelper.c:2514)
==9855==    by 0x4AAA168: vm_call_cfunc (vm_insnhelper.c:2539)
==9855==    by 0x4AB53C1: vm_sendish (vm_insnhelper.c:4023)
==9855==    by 0x4AB53C1: vm_exec_core (insns.def:801)
==9855==    by 0x4ABAEDB: rb_vm_exec (vm.c:1920)
==9855==    by 0x4AC6CA2: invoke_block (vm.c:1044)
==9855==    by 0x4AC6CA2: invoke_iseq_block_from_c (vm.c:1116)
==9855==    by 0x4AC6CA2: invoke_block_from_c_bh (vm.c:1134)
==9855==    by 0x4AC6CA2: vm_yield (vm.c:1179)
==9855==    by 0x4AC6CA2: rb_yield_0 (vm_eval.c:1227)
==9855==    by 0x4AC6CA2: rb_yield_1 (vm_eval.c:1233)
==9855==    by 0x4AC6CA2: rb_yield (vm_eval.c:1243)
==9855==    by 0x487C2CB: rb_ary_each (array.c:2135)
==9855==    by 0x4AAA168: vm_call_cfunc_with_frame (vm_insnhelper.c:2514)
==9855==    by 0x4AAA168: vm_call_cfunc (vm_insnhelper.c:2539)
==9855==    by 0x4AB547F: vm_sendish (vm_insnhelper.c:4023)
==9855==    by 0x4AB547F: vm_exec_core (insns.def:782)
==9855==    by 0x4ABAEDB: rb_vm_exec (vm.c:1920)
==9855==    by 0x4AC6CA2: invoke_block (vm.c:1044)
==9855==    by 0x4AC6CA2: invoke_iseq_block_from_c (vm.c:1116)
==9855==    by 0x4AC6CA2: invoke_block_from_c_bh (vm.c:1134)
==9855==    by 0x4AC6CA2: vm_yield (vm.c:1179)
==9855==    by 0x4AC6CA2: rb_yield_0 (vm_eval.c:1227)
==9855==    by 0x4AC6CA2: rb_yield_1 (vm_eval.c:1233)
==9855==    by 0x4AC6CA2: rb_yield (vm_eval.c:1243)
==9855==    by 0x4881DDB: rb_ary_collect (array.c:3065)
==9855==    by 0x4AAA168: vm_call_cfunc_with_frame (vm_insnhelper.c:2514)
==9855==    by 0x4AAA168: vm_call_cfunc (vm_insnhelper.c:2539)
==9855==    by 0x4AC2A3B: vm_call_method_each_type.part.410 (vm_insnhelper.c:2925)
==9855==    by 0x4AC31D4: vm_call_method_each_type (vm_insnhelper.c:3026)
==9855==    by 0x4AC31D4: vm_call_method (vm_insnhelper.c:3053)
==9855==    by 0x4AB547F: vm_sendish (vm_insnhelper.c:4023)
==9855==    by 0x4AB547F: vm_exec_core (insns.def:782)
==9855==    by 0x4ABAEDB: rb_vm_exec (vm.c:1920)
==9855==    by 0x4ABC5EB: invoke_iseq_block_from_c (vm.c:1116)
==9855==    by 0x4ABC5EB: invoke_block_from_c_proc (vm.c:1216)
==9855==    by 0x4ABC5EB: vm_invoke_proc (vm.c:1238)
==9855==    by 0x4ABC5EB: rb_vm_invoke_proc (vm.c:1259)
==9855==    by 0x49E071B: rb_proc_call (proc.c:971)
==9855==    by 0x491378E: exec_end_procs_chain (eval_jump.c:105)
==9855==    by 0x491378E: rb_ec_exec_end_proc (eval_jump.c:120)
==9855==    by 0x4913ABD: rb_ec_teardown (eval.c:142)
==9855==    by 0x4913CBD: rb_ec_cleanup (eval.c:209)
==9855==    by 0x4914032: ruby_run_node (eval.c:335)
==9855==    by 0x10910A: main (main.c:50)
==9855==  Address 0x1ffeffe7e0 is on thread 1's stack
==9855==  160 bytes below stack pointer
==9855==

Environment
{"warnings"=>[],
 "nokogiri"=>"1.10.4",
 "ruby"=>{"version"=>"2.7.0",
          "platform"=>"x86_64-linux",
          "description"=>"ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux]",
          "engine"=>"ruby"},
 "libxml"=>{"source"=>"packaged",
            "patches"=>["0001-Revert-Do-not-URI-escape-in-server-side-includes.patch",
                        "0002-Remove-script-macro-support.patch",
                        "0003-Update-entities-to-remove-handling-of-ssi.patch",
                        "0004-libxml2.la-is-in-top_builddir.patch"],
            "compiled"=>"2.9.10",
            "loaded"=>"2.9.10"},
 "libxslt"=>{"source"=>"packaged",
             "patches"=>[],
             "compiled"=>"1.1.34",
             "loaded"=>"1.1.34"}
}

I believe this valgrind error was from #1952 which has been fixed by #2186 in v1.11.2.


Cache all the gems in buildkite

Signed-off-by: Tim Smith<EMAIL_ADDRESS>

Closing due to lack of response


adding markers with click events

Is it possible to add markers to a map without hard coding lat, long coordinates? I'd like a user to click anywhere on the map to drop a marker.

Have you seen what you you receive in onClick event? Or just seen this https://github.com/istarkov/google-map-react#onclick-func

I must be blind. Thanks.


iOS build failing

Hey,
Just tried out to build the spinning cube example form ios. Unfortunately it is not building using cargo-lipo and the required toolchain.
Any advise?
Kind regards,
Schreda

Tried on macOS Catalina 10.15.2 with XCode 11.3.1, can confirm that this is happening with the current master branch. The stacktrace seems to indicate that this is a bindgen issue:
stack backtrace:
   0: std::sys_common::at_exit_imp::push
   1: core::fmt::ArgumentV1::show_usize
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::default_hook
   5: <std::panicking::begin_panic::PanicPayload<A> as core::panic::BoxMeUp>::get
   6: std::panicking::continue_panic_fmt
   7: std::panicking::try::do_call
   8: std::panicking::begin_panic
   9: std::panicking::begin_panic
  10: core::hash::sip::SipHasher13::new_with_keys
  11: bindgen::ir::context::BindgenContext::new
  12: bindgen::Bindings::generate
  13: bindgen::args_are_cpp::{{closure}}
  14: build_script_build::header_binding::generate
             at gdnative-sys/build.rs:69
  15: build_script_build::main
             at gdnative-sys/build.rs:7
  16: std::rt::lang_start::{{closure}}
             at /rustc/_/src/libstd/rt.rs:61
  17: std::panicking::try::do_call
  18: panic_unwind::dwarf::eh::read_encoded_pointer
  19: std::panicking::update_count_then_panic
  20: std::rt::lang_start
             at /rustc/_/src/libstd/rt.rs:61
  21: build_script_build::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Possibly relevant bindgen issue: https://github.com/rust-lang/rust-bindgen/issues/1211

@Schr3da I have created a patch in #286 that should allow building for iOS with cargo-lipo. Could you try and see if it works on your machine?

Hm unfortunately Im unable to install llvm-config using brew install --with-toolchain llvm. Brew does not resolve the option :(

llvm-config is normally installed by brew without any additional options. You can find it in $(brew --prefix)/opt/llvm/bin. The warning shouldn't normally affect building, and I have managed to build the example without setting LLVM_CONFIG_PATH with the PR I linked. Could you please try building the example with the PR applied?

Great job - works !!!
We can close the item.


Add permission to approve csr

The related task: https://github.com/open-cluster-management/backlog/issues/11279

/approve

/lgtm


Use setOutput instead of exportVariable

Hi!
Useful Action, thanks! I see you're using exportVariable (GitHub docs, Function definition).
I'm wondering whether you intended to use this instead of setOutput (GitHub docs, Function definition), as the latter seems more appropriate for the functionality you're implementing.
What are your thought?

Hi @SvanBoxel!
Indeed, I think you're right and setOutput is more appropriate. Will fix ASAP.


feat: group components by vendor and name

This was actually an idea by @tschmidtb51 during a call we had a while back when looking at one of our CSAF documents:
Currently, there's a _components_ branch which is a flat list of all the components that are not a product in SecObserve.
Example:

If the components have a Purl, we can actually parse it and then group the components by vendor and product name, so it looks like this:

This PR implements that feature, it's a draft because it's probably not guaranteed here that every component has a Purl. At our company that's the case, so we actually use this implementation, but I'm not sure if this is a useful general solution (or if it's worth implementing a more generalized solution). Just wanted to mention the idea here, this doesn't change anything technically, it just looks a bit nicer, especially when there are a lot of components in that branch.

Thank you @dervoeti, I will have a look at it soon


[VL] Enable unix_seconds Spark function

What changes were proposed in this pull request?
Enabling unix_seconds Spark function.
(Fixes: #ISSUE-ID)
How was this patch tested?
Added a UT.

@PHILO-HE can you please review this? Thank you!

@acvictor, looks good! Please rebase the code and resolve conflict. Thanks!

@acvictor, looks good! Please rebase the code and resolve conflict. Thanks!

Done, thank you!

Looks good. Thank you.
@PHILO-HE can you update the function number metric

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_5602_time.csv
log/native_master_05_06_2024_72e787c64_time.csv
difference
percentage

q1
37.60
36.58
-1.026
97.27%

q2
24.03
23.74
-0.294
98.78%

q3
36.85
38.97
2.120
105.75%

q4
38.42
38.09
-0.331
99.14%

q5
71.97
68.56
-3.411
95.26%

q6
5.72
6.78
1.065
118.63%

q7
84.73
83.29
-1.438
98.30%

q8
85.59
87.34
1.755
102.05%

q9
118.35
122.36
4.019
103.40%

q10
44.29
46.26
1.979
104.47%

q11
20.06
20.36
0.292
101.46%

q12
27.63
27.48
-0.152
99.45%

q13
56.51
54.80
-1.712
96.97%

q14
19.63
20.20
0.569
102.90%

q15
29.91
30.34
0.434
101.45%

q16
13.74
15.88
2.138
115.56%

q17
103.75
101.90
-1.853
98.21%

q18
145.12
146.06
0.943
100.65%

q19
13.72
14.65
0.934
106.80%

q20
27.75
26.35
-1.405
94.94%

q21
287.18
291.97
4.785
101.67%

q22
14.73
15.01
0.282
101.91%

total
1307.29
1316.98
9.693
100.74%

Looks good. Thank you.
@PHILO-HE can you update the function number metric

@FelixYBW, Yes, I have recoded this function in internal OneNote. And will update the metric per month.


using -DBUILD_SHARED_LIBS=ON results in build error

After cloning the repository and successful
make && make install PREFIX=$HOME/usr/local
I have been trying to build a shared library for openblas using the cmake option  -DBUILD_SHARED_LIBS=ON
Starting with cmake and the options files generated in the first build --successful after specifying the fortran compiler, I enabled the options for building RELAPACK and DYNAMIC_ARCH: still building successfully. But the when I ran
cmake -DBUILD_SHARED_LIBS=ON ..
from the build directory, the make exited with this error:
relapack/src/CMakeFiles/relapack_src.dir/lapack_wrappers.c.o: In function `stgsyl_':
lapack_wrappers.c:(.text+0xd70): multiple definition of `stgsyl_'
CMakeFiles/openblas.dir/lapack-netlib/SRC/stgsyl.f.o:stgsyl.f:(.text+0x0): first defined here
relapack/src/CMakeFiles/relapack_src.dir/lapack_wrappers.c.o: In function `dtgsyl_':
lapack_wrappers.c:(.text+0xdf3): multiple definition of `dtgsyl_'
CMakeFiles/openblas.dir/lapack-netlib/SRC/dtgsyl.f.o:dtgsyl.f:(.text+0x0): first defined here
relapack/src/CMakeFiles/relapack_src.dir/lapack_wrappers.c.o: In function `ctgsyl_':
lapack_wrappers.c:(.text+0xe76): multiple definition of `ctgsyl_'
CMakeFiles/openblas.dir/lapack-netlib/SRC/ctgsyl.f.o:ctgsyl.f:(.text+0x0): first defined here
relapack/src/CMakeFiles/relapack_src.dir/lapack_wrappers.c.o: In function `ztgsyl_':
lapack_wrappers.c:(.text+0xef9): multiple definition of `ztgsyl_'
CMakeFiles/openblas.dir/lapack-netlib/SRC/ztgsyl.f.o:ztgsyl.f:(.text+0x0): first defined here
collect2: error: ld returned 1 exit status
CMakeFiles/openblas.dir/build.make:129643: recipe for target 'lib/libopenblas.so.0.3' failed
make[2]: *** [lib/libopenblas.so.0.3] Error 1
CMakeFiles/Makefile2:116: recipe for target 'CMakeFiles/openblas.dir/all' failed
make[1]: *** [CMakeFiles/openblas.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2

Am I right in thinking that this has to do with the 'dynamic architecture' option and that the shared libs and dynamic architecture options cannot be used at the same time?
EDIT -- it seems to be the other way round. switching on RELAPACK breaks the build when building shared libraries. with DYNAMIC_ARCH on it does build. The question remains: is there a reason why some options clash with building shared libraries?

Shared libs and dynamic architecture should definitely be able to coexist, in particular as dynamic_arch "only" adds individual sets of blas microkernels for the various supported cpus but uses a common lapack. This looks more like a conflict between RELAPACK and the generic LAPACK, perhaps the linking tricks used there do not (or no longer) work with cmake or your compiler/linker version.

Seems the ReLAPACK build currently works only with plain make, not cmake. The difference is that the plain Makefiles use ar to build the library (where it is possible to tell it to override earlier symbols) while cmake invokes the linker on all object files directly. Still need to find if/when/why this changed - at least I am fairly certain that this combination of options used to work with cmake in the past.

Actually it appears that this never worked for building the shared library - should be solved by the addition of the appropriate linker option in #2044 unless I overiooked something (again)...

Id does work now.


add test workflow

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7e26999). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   67.37%
=========================================
  Files             ?        9
  Lines             ?      472
  Branches          ?        0
=========================================
  Hits              ?      318
  Misses            ?      150
  Partials          ?        4

Continue to review full report at Codecov.

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


What is the ground-truth mask used during training?

Hi
I saw in the file train_pano_joint.lua that you use somekind of mask to increase the loss at some poisitions.
I couldn't find any reference to that neither in the paper or throughout the repository.
Could you please explain what is the mask, how it is generated and why is it needed?
Thanks
    gtMsk = torch.mul(gtMsk, 4)
    gtMsk = gtMsk:cuda()
    gtMsk_w = torch.cmul(loss_d_1, gtMsk)
    loss_d_1 = torch.add(gtMsk_w, loss_d_1)
    gt2Msk = torch.mul(gt2Msk, 4)
    gt2Msk = gt2Msk:cuda()
    gt2Msk_w = torch.cmul(loss_d_2, gt2Msk)
    loss_d_2 = torch.add(gt2Msk_w, loss_d_2)

@jackaceuser You can refer to the ground-truth masking in Section 3.3, last sentence in the third paragraph. Since our ground-truth layout edge and corner map contains >95% zero values even after gaussian smoothing, to ease the learning process we re-weight the back propagated gradients of the background pixels by multiplying with 0.2.


Added Contributing guide #5

#5  CONTRIBUTING.md file added

@Sai-Adarsh PR reviewed. Please take the necessary action.

Merging this


[Grade] - Use "versions.gradle" to organize dependencies

@vanniktech

@vanniktech Updated. Let me know what you think.


Find the right frequency for refreshing the each dataset

At #277, @ajeanmahoney requests that the RFC dataset be updated at least once every 12 hours. I'm wondering if the community will want the updates to appear even more rapidly, and suggest we look at the cost of an update once per hour.
We should tune this for all the datatasets.
Is there a quick link to point to what the current configuration is?

Two notes:

Reindex delay is the same for all data sources (https://bib.ietf.org/static/docs/howto/auto-reindex-sources.html)
Having a source reindexed more often than it is rebuilt (specified in GHA) will not provide any improvement.

A data source should be rebuild more frequently first, and then reindexing can be made more frequent.

Bulk-indexable sources are generally not designed to provide near-real-time availability. For realtime availability it’s more appropriate to configure an external source for RFCs, the way individual I-Ds are retrieved from Datatracker or DOIs from Crossref. (See docs for the distinction between external and indexable sources).

@strogonoff is exactly right. Other than those considerations, we also want to make sure that overlapping fetching and indexing processes don't happen simultaneously.