[wip] Support autoscaling

Fix https://github.com/vexxhost/magnum-cluster-api/issues/3

I believe in this case you've actually ran the auto scaler on the workload cluster with a kubeconfig file to talk to the management cluster
even if things can be secure and locked down, this could be a security issue down the road. Therefore, I think it's better to run the auto scaler on the management cluster talking to the workload instead.
So I think you'll have to remove it from the ClusterResourceSet and get rid of the kubeconfig option, for the actual deployment in the management cluster, you can mount the clustername-kubeconfig secret to get access to the cluster directly.

I believe in this case you've actually ran the auto scaler on the workload cluster with a kubeconfig file to talk to the management cluster
even if things can be secure and locked down, this could be a security issue down the road. Therefore, I think it's better to run the auto scaler on the management cluster talking to the workload instead.
So I think you'll have to remove it from the ClusterResourceSet and get rid of the kubeconfig option, for the actual deployment in the management cluster, you can mount the clustername-kubeconfig secret to get access to the cluster directly.

when we run autoscaler in mgmt cluster, i wonder it means we need to deploy one autoscaler per one magnum cluster
That was my concern and the reason why i chose autosacler in workload cluster and tried to create clusterrole with resourceName binding.

I believe in this case you've actually ran the auto scaler on the workload cluster with a kubeconfig file to talk to the management cluster
even if things can be secure and locked down, this could be a security issue down the road. Therefore, I think it's better to run the auto scaler on the management cluster talking to the workload instead.
So I think you'll have to remove it from the ClusterResourceSet and get rid of the kubeconfig option, for the actual deployment in the management cluster, you can mount the clustername-kubeconfig secret to get access to the cluster directly.

when we run autoscaler in mgmt cluster, i wonder it means we need to deploy one autoscaler per one magnum cluster That was my concern and the reason why i chose autosacler in workload cluster and tried to create clusterrole with resourceName binding.

yes, indeed, actually we will need to create a autoscaler per CAPI cluster on the control plane, but I think the load added of this is kinda negligible so we can be OK with it.

Ok, I have changed the clusterAPIMode as you mentioned.
Also I used flux helmrelease for autoscaler deployment.


Update repo when the current submit has better performance than previous submit

First of all, I love this tool, it is way too cool! Besides, could we have a feature as title? Meanwhile what is the current workaround for this?
The scenario would be:
1st submit of the solution gets 100 ms of runtime. The code is committed into the repo.
2nd submit of the solution gets 80 ms of runtime. The code is not updating into the repo with this better result.

fixed, see - #127
will take up to a week to get updated on chrome webstore.


Opening code in GitLab does not highlight the specified line

Describe the bug
Opening a line in GitLab uses the URL in the format of https://gitlab.com/{path}/blob/{sha}/file.extension#L1-L1. This does not highlight the lines as expected, as the format should be https://gitlab.com/{path}/blob/{sha}/file.extension#L1-1
To Reproduce
Steps to reproduce the behavior:

With a GitLab repository, right click on a line and Open in Git...
Browser opens with the URL https://gitlab.com/{path}/blob/{sha}/file.extension#L1-L1
The line number 1 is not highlighted

Expected behavior
Line number 1 should be highlighted.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS
Browser Chrome

Have you configured GitLab as the host in the plugin settings? Preferences -> Other Settings -> Git Link

Thanks! Turns out it was still GitHub. I had an impression that it was already configured.


Create styles1.css

the css file to the templete.html file

Stylesheet should be in the same PR as in template. styles are present in styles.css file. style1.css is not being used in the code. Closing this PR for now


How does jraph support large scale graph neural network training?

HI,
We note that DeepMind team use jraph to win the 2021 KDD OGB MAG240M-LSC Track.
As I found that, this OGB dataset contain 100 million nodes, so I want to say, how does jraph support this large scale gnn model training? The jraph documentation is too simple, could you please provide some more details about the MAG240M-LSC Track and the large scale gnn training? thx.

Hi,
Please take a look the released repository for MAG:
https://github.com/deepmind/deepmind-research/tree/master/ogb_lsc/mag


surgicalGuideBases for mandible

@cmfsx, can you create a surgical plan with two surgicalGuideBases (one for each mandibleResectionPlane) using the segment editor?

@mauigna06 Sure will give it a go.

Thanks. I couldn't create one I liked

I found some pictures we can use as example:

And here there is also an example of a mandibleSurgicalGuide (and an iliacCrestSurgicalGuide):
https://www.xilloc.com/products-and-services/surgical-guides/


add script for building pythons

this appears to work on:

macos arm64
linux aarch64

I will be following up with CI, validation

This looks fine to me. There's potentially some code in here that could be used as a shared Python library across the board.

indeed!  though as it's written right now it needs to be one dependencyless file so the linux build stuff works properly

I don't know if it will matter but a lot of the files and directories are considered to have been created in the past:

the timestamps are intentional!  that's the "reproducible tar" bits here: https://github.com/getsentry/prebuilt-pythons/pull/1/files#diff-da524db6fe8040689c21d15fefe6256f16cf263e57eafb4bae3116a3eaf28981R436


Isomorphism breaks due to Websockets when using SSR

Bug report
Describe the bug
When importing createClient into a SvelteKit project, the following error is raised:
5:49:56 PM [vite] Error when evaluating SSR module /node_modules/websocket/lib/browser.js?v=f34fcf64:
Error: Could not determine global this
    at /node_modules/websocket/lib/browser.js?v=f34fcf64:7:28
    at instantiateModule (/home/ixxie/repos/minex/node_modules/vite/dist/node/chunks/dep-66eb515d.js:69030:166)

It seems to come from this block of code in the Websockets package.
To Reproduce
npm init svelte@next
npm install
npm install --save-prod @supabase/supabase-js
sed -i "s/<script>/<script>\n\timport { createClient } from '@supabase\/supabase-js';/" ./src/routes/index.svelte
npm run dev

Expected behavior
Import should work without error
Screenshots
If applicable, add screenshots to help explain your problem.
System information

Version of supabase-js: 1.11.2
Version of Node.js: 14.15.4

Additional context
This was discovered after resolving https://github.com/supabase/supabase-js/issues/153, after which @kiwicopple recommended I create a new issue.

I've now tried a similar minimal example using es5-ext/globaldirectly and it seems the root of the issue is there. It seems this package is abandoned (not github activity for a year) and perhaps an alternative should be suggested to the websocket maintainers but I am not sure what it would be...

Perhaps https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis could be used if it's available

@benmccann this is what I suggested and this was already released into websockets by its maintainer (see https://github.com/theturtle32/WebSocket-Node/issues/415).

Okay so: the fix I mentioned resolved the globalThis issue, but revealed a deeper underlying issue: websockets - which seems to come into supabase-js through realtime-js btw - is not isomorphic, as far as I can tell. The npm package description literally states it is for Node.
I suppose the solution is to switch to an isomorphic library like isomorphic-ws; however, I am not qualified to make this sort of decision.
Would you like me to post a separate issue to realtime-js?

We originally used globalThis in gotrue and had to polyfill it: https://github.com/supabase/gotrue-js/issues/38
I find this a bit odd though, because our supabase-js client is isomorphic. We already use it in a node environment and it works fine 🤔

Anyway, this issue seems fixed by<EMAIL_ADDRESS>so at most we'd need to upgrade package.json and then can close this

I'm not sure if it's related to the globalThis issue, but once the globalThis issue is fixed I encounter another issue that seems to be a Vite bug: https://github.com/vitejs/vite/issues/2995

OK I bumped to the latest. I'll leave this open if anyone can confirm the fix?

:tada: This issue has been resolved in version 1.11.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Thanks! There's multiple issues left running Supabase with SvelteKit, but they're pretty clearly issues with Vite so we'll work on those in that repo. Thanks for all your help!


Added fcns for automatic AIF selection + demo. Tests will be added later.

Hi @JonathanArvidsson,
Thanks for your DSC contribution. To me this looks good and according to the guidelines.
kind regards,
Petra


LORA fine tuning inside a container:  The client socket has failed to connect to any network address

I am trying to finetune with lora inside a container, but the script throw that The client socket has failed to connect to any network address
(openvla) root@6968782:/workspace/openvla# torchrun --standalone --nnodes 1 --nproc-per-node 1 vla-scripts/finetune.py   --vla_path "/workspace/openvla/openvla-7b"   --data_root_dir "/workspace/openvla/data"   --dataset_name bridge_orig
/root/miniconda3/envs/openvla/lib/python3.10/site-packages/_distutils_hack/__init__.py:55: UserWarning: Reliance on distutils from stdlib is deprecated. Users must rely on setuptools to provide the distutils module. Avoid importing distutils or import setuptools first, and avoid setting SETUPTOOLS_USE_DISTUTILS=stdlib. Register concerns at https://github.com/pypa/setuptools/issues/new?template=distutils-deprecation.yml
  warnings.warn(
2024-08-29 20:02:34.172269: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-08-29 20:02:34.172370: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-08-29 20:02:34.173312: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-08-29 20:02:34.179339: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-08-29 20:02:34.943015: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
**[W socket.cpp:697] [c10d] The client socket has failed to `connect `to ?UNKNOWN? (errno: 110 - Connection timed out).
[W socket.cpp:697] [c10d] The client socket has failed to connect to ?UNKNOWN? (errno: 110 - Connection timed out).
[E socket.cpp:753] [c10d] The client socket has failed to connect to any network address of (6968782, 41093).**
Traceback (most recent call last):
  File "/workspace/openvla/vla-scripts/finetune.py", line 42, in <module>
    from prismatic.models.backbones.llm.prompting import PurePromptBuilder, VicunaV15ChatPromptBuilder
  File "/workspace/openvla/prismatic/__init__.py", line 1, in <module>
    from .models import available_model_names, available_models, get_model_description, load
  File "/workspace/openvla/prismatic/models/__init__.py", line 1, in <module>
    from .load import available_model_names, available_models, get_model_description, load, load_vla
  File "/workspace/openvla/prismatic/models/load.py", line 16, in <module>
    from prismatic.models.materialize import get_llm_backbone_and_tokenizer, get_vision_backbone_and_transform
  File "/workspace/openvla/prismatic/models/materialize.py", line 12, in <module>
    from prismatic.models.backbones.llm import LLaMa2LLMBackbone, LLMBackbone, MistralLLMBackbone, PhiLLMBackbone
  File "/workspace/openvla/prismatic/models/backbones/llm/__init__.py", line 1, in <module>
    from .base_llm import LLMBackbone
  File "/workspace/openvla/prismatic/models/backbones/llm/base_llm.py", line 33, in <module>
    overwatch = initialize_overwatch(__name__)
  File "/workspace/openvla/prismatic/overwatch/overwatch.py", line 147, in initialize_overwatch
    return DistributedOverwatch(name) if int(os.environ.get("WORLD_SIZE", -1)) != -1 else PureOverwatch(name)
  File "/workspace/openvla/prismatic/overwatch/overwatch.py", line 54, in __init__
    self.logger, self.distributed_state = ContextAdapter(logging.getLogger(name), extra={}), PartialState()
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/accelerate/state.py", line 211, in __init__
    torch.distributed.init_process_group(backend=self.backend, **kwargs)
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/c10d_logger.py", line 86, in wrapper
    func_return = func(*args, **kwargs)
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/distributed_c10d.py", line 1177, in init_process_group
    store, rank, world_size = next(rendezvous_iterator)
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/rendezvous.py", line 246, in _env_rendezvous_handler
    store = _create_c10d_store(master_addr, master_port, rank, world_size, timeout, use_libuv)
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/rendezvous.py", line 174, in _create_c10d_store
    return TCPStore(
torch.distributed.DistNetworkError: The client socket has failed to connect to any network address of (6968782, 41093). The client socket has failed to connect to ?UNKNOWN? (errno: 110 - Connection timed out).
[2024-08-29 20:07:02,381] torch.distributed.elastic.multiprocessing.api: [ERROR] failed (exitcode: 1) local_rank: 0 (pid: 68404) of binary: /root/miniconda3/envs/openvla/bin/python
Traceback (most recent call last):
  File "/root/miniconda3/envs/openvla/bin/torchrun", line 8, in <module>
    sys.exit(main())
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 347, in wrapper
    return f(*args, **kwargs)
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/run.py", line 812, in main
    run(args)
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/run.py", line 803, in run
    elastic_launch(
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 135, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/root/miniconda3/envs/openvla/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 268, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
vla-scripts/finetune.py FAILED
------------------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-08-29_20:07:02
  host      : 6968782
  rank      : 0 (local_rank: 0)
  exitcode  : 1 (pid: 68404)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html

This problem doesn't seem directly related to OpenVLA, but a more generic issue with running PyTorch DDP in your environment.
Could you check whether the training runs for you outside of docker on the same machine if that's an option?
I googled your error and it seems that you may need to open a certain port to be accessible for the train script, so it can use it for synchronization between the different processes in distributed training. If this continues to be a problem, maybe you can raise it in the PyTorch forum or google how to run PyTorch DDP with docker. I assume you'd encounter the same error if you tried to run the PyTorch DDP tutorial example in your Docker (ie it's not related to something OpenVLA specific).
Btw, if you want to only train on single GPU (like your current command indicates) you could run the finetuning script without torchrun, simply by calling it directly via python vla-scripts/finetune.py ... that may avoid the headache with process communications.

Hi, have you solved this problem? I met the same problem as you


Revert "Initial framework support for iOS platform views."

Reverts flutter/flutter#23412
This broke the build, landing a revert TBR.

RSLGTM


TypeError: # is not a constructor

I'm getting this error the first time using this package. I'm using the ethers Web3Interface
TypeError: #<Object> is not a constructor
    at _construct (useMetamask.js:18:1)
    at _callee$ (useMetamask.js:137:1)
    at tryCatch (runtime.js:63:1)
    at Generator.invoke [as _invoke] (runtime.js:294:1)
    at Generator.next (runtime.js:119:1)
    at asyncGeneratorStep (useMetamask.js:32:1)
    at _next (useMetamask.js:34:1)
    at useMetamask.js:34:1
    at new Promise (<anonymous>)
    at useMetamask.js:34:1

How can I resolve this issue?

@chackerian
await connect(ethers.providers.Web3Provider);

Seems like it resolved, I am closing this issue, please re-open if reply above didn't help.


Error running Multik 0.2.0-dev-5 on Github Actions with ubuntu-latest

It looks like you are preparing for a new release of multik. Tests pass locally on MacOS/ARM64, but I encountered the following error when trying 0.2.0-dev-5 on Github's CI server:
java.lang.UnsatisfiedLinkError: /tmp/jni_multik7503611758506959258/libmultik_jni-linuxX64.so: /tmp/jni_multik7503611758506959258/libmultik_jni-linuxX64.so: ELF load command address/offset not properly aligned
            at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
            at java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)
            at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)
            at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)
            at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2389)
            at java.base/java.lang.Runtime.load0(Runtime.java:755)
            at java.base/java.lang.System.load(System.java:1953)
            at org.jetbrains.kotlinx.multik.openblas.JvmLoader.load(Loader.kt:72)
            at org.jetbrains.kotlinx.multik.openblas.JvmNativeEngine.<init>(JvmNativeEngine.kt:7)
            at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
            at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
            at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
            at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
            at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:789)

These are the versions I am currently using:
        val multikVersion = "0.2.0-dev-5"
        implementation("org.jetbrains.kotlinx:multik-core:$multikVersion")
//  implementation("org.jetbrains.kotlinx:multik-core-linuxx64:$multikVersion")
//  implementation("org.jetbrains.kotlinx:multik-kotlin-linuxx64:$multikVersion")
        implementation("org.jetbrains.kotlinx:multik-core-jvm:$multikVersion")
        implementation("org.jetbrains.kotlinx:multik-default:$multikVersion")
        implementation("org.jetbrains.kotlinx:multik-openblas-jvm:$multikVersion")
        implementation("org.jetbrains.kotlinx:multik-openblas:$multikVersion")
//  implementation("org.jetbrains.kotlinx:multik-native:$multik_version")

When I added multik-core-linuxx64, I received the following error:
Execution failed for task ':kspKotlinJvm'.
> Error while evaluating property 'filteredArgumentsMap' of task ':kspKotlinJvm'
   > Could not resolve all files for configuration ':jvmCompileClasspath'.
      > Could not resolve org.jetbrains.kotlinx:multik-kotlin-linuxx64:0.2.0-dev-5.
        Required by:
            project :
         > No matching variant of org.jetbrains.kotlinx:multik-kotlin-linuxx64:0.2.0-dev-5 was found. The consumer was configured to find an API of a library, preferably optimized for standard JVMs, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' but:
             - Variant 'linuxX64ApiElements-published' capability org.jetbrains.kotlinx:multik-kotlin-linuxx64:0.2.0-dev-5 declares a library:
                 - Incompatible because this component declares a usage of 'kotlin-api' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed an API of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm'
                 - Other compatible attribute:
                     - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)

I am currently unsure how to proceed, any feedback you might have would be appreciated. Thanks!

Tests pass locally on MacOS/ARM64, but I encountered the following error when trying 0.2.0-dev-5 on Github's CI server:

What is the actual version of Ubuntu?
There is a known bug with Ubuntu 18.04 and older (link1, #107, #98). I tested on 20.04, 22.04, and multik ran without errors.

When I added multik-core-linuxx64

You have added a native artifact to jvm dependency. These artifacts are needed for multiplatform projects.
For jvm the following dependency:
implementation("org.jetbrains.kotlinx:multik-core:$multikVersion")

or
implementation("org.jetbrains.kotlinx:multik-core-jvm:$multikVersion")

Hi @devcrocod, thank you for your reply! I tried both of those options, however am still receiving the aforementioned errors. In case it helps, here are the full stack traces for the JVM and the multiplatform dependencies. It looks like ubuntu-latest is currently on 20.04.

I am using Kotlin/JS with the IR compiler, however this error occurs in a JVM test. Strangely, it does not occur locally on macosArm64, only linuxX64 on the build server.

I took your repository galoisenne and tested. Tested on macosX64, Ubuntu 20.04, Ubuntu 22.04. On macos and ubuntu 22 all tests passed.
Native library bug for dependency jvm was reproduced on ubuntu 20.04. I have already made changes to fix this error. The fix is already expected in the 0.2.0 release early next week.
There was an error for JS, as I said about the IR compiler. Fixed when I added JS (IR). Fixed when I added JS. After that, all the tests in my docker passed, except for those that require a browser.


[FEATURE} Clearer distinction between offensive and defensive Masteries under the equipped items

Random Masteries under the equipped items are displayed the same wether they're elemental or resistance masteries. It would be nice if something was made to distinguish them.
One solution would be to put a small sword:

and a small shield:

next to them.

Fair point. I'll see what I can do with the limited space there is. A small icon like that isn't a bad idea. I'll add it to the priority list.


Do not use datetime.datetime.utcnow()

There are multiple locations where this function is used. It is documented as being potentially dangerous and should be replaced with datetime.datetime.now(tz=datetime.timezone.utc): https://docs.python.org/3/library/datetime.html#datetime.datetime.utcnow
This came up in https://github.com/Open-MSS/MSS/pull/2177#issuecomment-1933712007.
Related to #2122.

i love to work on this issue, can you please assign me ?

Sure.

There are more instances of utcnow() remaining:
$ git grep -n 'utcnow'
mslib/mscolab/models.py:184:    created_at = db.Column(db.DateTime, default=datetime.datetime.utcnow)
mslib/mscolab/models.py:208:    created_at = db.Column(db.DateTime, default=datetime.datetime.utcnow)
mslib/msui/wms_control.py:478:            datetime.utcnow().replace(hour=0, minute=0, second=0, microsecond=0)))
mslib/msui/wms_control.py:480:            datetime.utcnow().replace(hour=0, minute=0, second=0, microsecond=0)))
mslib/msui/wms_control.py:843:                        end_time = datetime.utcnow()

We have to be carefully not to create a dependency to mscolab in the mswms code parts.

Hey @ReimarBauer , Can I work on the remaining issue and could you please assign it to me?


Dashboard customer delete causes checkout session to timeout

Bug report

firestore-stripe-payments
firestore-stripe-web-sdk

Describe the bug
A user signs up + pays for a subscription. Then if the customer is deleted in the Stripe Dashboard the customer information continues to exist Firestore. Once the user tries to signup for the subscription again, using the firestore-stripe-web-sdk, the web sdk will simply timeout.
If you manually delete the customer documents in Firestore after deleting in the Stripe Dashboard everything works as expected.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

In browser customer pays + signs up for subscription using firestore-stripe-web-sdk
Firestore Documents are created for customer. Everything works as expected
Go into the Stripe Dashboard and delete the customer
Customer tries to re-subscribe using firestore-stripe-web-sdk
firestore-stripe-web-sdk timesout

Expected behavior
Customer data in Firestore is automatically deleted when the stripe customer data is deleted.
System information

macOS
Chrome

Additional context
Manually deleting the customer documents fixes the issue.

I'm also dealing with this same issue. From what I can gather the customer id in stripe is tied to firebase auth. So when you delete a customer in stripe and then they try to pay again, it uses the same customer id which is now a deleted customer. In firebase there is an error stored in the doc "No such customer: 'cus_XXXXXXXXXXXXXX'" would be nice if that's the case, a new customer_id could be generated.
I tried to see if Stripe customer service could restore the deleted customer but they can't. They referred me here.


Crash when debugging Code-OSS, and start an extension debugging session

This scenario has been pretty unstable for a while, but lately it just basically never works.
Steps:

Start debugging VS Code from source
Open an extension folder to debug in the resulting VS Code window
Start debugging the extension
:bug: Both the Extension Development Host window and the debugged VS Code window will crash (very often immediately)

OS: Windows 10

I just went through the steps and I'm unable to reproduce the issue. Does it still happen on the latest Insiders?


Error: Cannot find module '../build/Debug/nodegit.node'

macOS High Sierra (ver. 10.13.6)
Node: 11.9.0
NPM: 6.7.0
Observation
Attempting to run the w4kit command after installing the module results in a fatal exception:
HOST$ npm install -g w4kit-cli
/Users/brossi/.npm-packages/bin/w4kit -> /Users/brossi/.npm-packages/lib/node_modules/w4kit-cli/index.js
+<EMAIL_ADDRESS>updated 1 package in 2.901s
HOST$ w4kit
internal/modules/cjs/loader.js:611
    throw err;
    ^

Error: Cannot find module '../build/Debug/nodegit.node'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:609:15)
    at Function.Module._load (internal/modules/cjs/loader.js:535:25)
    at Module.require (internal/modules/cjs/loader.js:663:17)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Object.<anonymous> (/Users/brossi/.npm-packages/lib/node_modules/w4kit-cli/node_modules/nodegit/dist/nodegit.js:19:12)
    at Module._compile (internal/modules/cjs/loader.js:734:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:745:10)
    at Module.load (internal/modules/cjs/loader.js:626:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:566:12)
    at Function.Module._load (internal/modules/cjs/loader.js:558:3)

Resolution

After flailing around a bit, I uninstalled w4kit-cli and then reinstalled with no issues.
Attempting to re-run the w4kit command still failed.
After monkey patching w4kit-cli's package.json manifest to use nodegit-v0.24.0 instead of the default nodegit-v0.22.2, I cleaned out and rebuilt the node_modules directory with npm install.
Re-run w4kit; success:

I'm not exactly sure if this is something affecting all macOS installations or if it is a local ENV issue on my side, but in case it helps anyone else, here's a bug report and steps to fix. I've submitted a pull request with the single line version correction, but I'm not knowledgeable enough to know if nodegit-v0.22.2 was specified for a particular reason, or if it was simply a dependency which had not been updated in a while.


Allow Text to be inline

Currently, Text is returning a <p /> element. Some times we need to use it but in an inline fashion.
So, maybe by adding an optional prop isInline can do the trick and return a <span /> instead.
<Text size="md" isInline /> // -> span
<Text size="md" /> // -> p

This feature was already implemented.


Better error display

Improve error message (that display the native error code)

fix error in 'CredRead' message
another commit of cleaning/refactoring (that should not change behavior)

@pmiossec I am going to close this, and we can make one merge with #23?


Add cshollingsworth to ARI WG as a Docs approver

@cshollingsworth would like to be added as an approver in the Docs working group.
Significant PRs authored:

https://github.com/cloudfoundry/docs-cloudfoundry-concepts/commit/2ce4aa26ca1e558f98d0d8d45199daa73c48d8c6
https://github.com/cloudfoundry/docs-cloudfoundry-concepts/commit/2beb7c8cdfd736fd7a45ab7234184662e413a1d2
https://github.com/cloudfoundry/docs-cloudfoundry-concepts/commit/84e3fb70244ffc30b9fe787c6ee0827de561da2e
https://github.com/cloudfoundry/docs-cloudfoundry-concepts/commit/8fb755eba16ffb4573063b6b4d455bb64f61a733
https://github.com/cloudfoundry/docs-dev-guide/commit/b0117590aedac6c863249fecf5e5674d48f6d748
https://github.com/cloudfoundry/docs-dev-guide/commit/d5aa107b97f525a3f9dcfa1d88881c946c2ab583
https://github.com/cloudfoundry/docs-dev-guide/commit/b260593ff5a26ccb2e25f7bb065b2f076b78572c
https://github.com/cloudfoundry/docs-dev-guide/commit/8602bbf2ffe3c6468deee975db0e2308477477f1
https://github.com/cloudfoundry/docs-dev-guide/commit/69dea3146ff39ed7c253c795c2eb043a5851482d
https://github.com/cloudfoundry/docs-dev-guide/commit/df94c99452ca4f81f19a0ff9f74758769eedd596
https://github.com/cloudfoundry/docs-dev-guide/commit/16bc9a55f16e63396491775f76dcfaa5493468e6
https://github.com/cloudfoundry/docs-dev-guide/commit/aeefe38b247e20b29b01fbf1906b4e1887de019f
https://github.com/cloudfoundry/docs-dev-guide/commit/1785231e7d623474fcd480c53aad8abe3ff67bbc
https://github.com/cloudfoundry/docs-dev-guide/commit/5be24659105b93a629d6702225191af269e8afcf
https://github.com/cloudfoundry/docs-dev-guide/commit/f3274ea7d7c5c748110faff380ea0f2d143b251c
https://github.com/cloudfoundry/docs-dev-guide/commit/a3ec1fa1c687455163f65ef690423a5a9daf316c

Significant PRs reviewed:

https://github.com/cloudfoundry/docs-cf-cli/commit/7c3ca24aac06c2e9549e642c8d42337087c76eb0
https://github.com/cloudfoundry/docs-cloudfoundry-concepts/commit/17ad89de063bb3468d73e67cd43187198efe8424
https://github.com/cloudfoundry/docs-cloudfoundry-concepts/commit/282d3510725e553378fbdd83e4683f03a5cc25a6
https://github.com/cloudfoundry/docs-cloudfoundry-concepts/commit/e417da29efc9d0ffe9edd9d5ef387f300e9292a6
https://github.com/cloudfoundry/docs-dev-guide/commit/3414542ee7fa1eaec2bb0cbdec7755fd04c4972f
https://github.com/cloudfoundry/docs-dev-guide/commit/5257bbe7457c5121b6ca3b861d556acd67e638bb

cc: @Gerg

The docs group does not currently have active contributors. As working group lead, I approve this promotion.


add a count to spop

resolved issue #411

Thanks for contribution, please fix the above issues and I'll merge it.

Thanks for your help

Thanks

Hello! Thanks @KostSvitlana!
Question: when i install the package via pip this commit is not visible, aioredis version == 1.2.0

Hello! Thanks @KostSvitlana!
Question: when i install the package via pip this commit is not visible, aioredis version == 1.2.0

It's because this changes will be in next release

Hello, I was going to reopen this issue because I reach this bug, is it possible to release it?


Redis: Using JedisPool instead of Jedis

Hi, I am one of the Jedis Reviewers. When I used YCSB to write large amounts of data (over 100 million) to Redis, I encountered a failure when the connection is abnormal (even if the insertionRetryLimit is configured). After reading the YCSB code, I found that YCSB uses Jedis instead of JedisPool. When Jedis encounters a connection timeout or disconnection, it cannot be restored. In order to run the long-term stable test, I introduced JedisPool. This PR mainly includes:

Replace Jedis with JedisPool
Exception is processed and Status.ERROR is returned
Upgrade the Jedis version to 3.6.0 (the latest stable version)

@busbey please have a look when you have time, thanks.


Wrong "Prev" button title for legacy mode

Thank you for your pr. I'll check it in some days.

merged on master

Damn, I cannot build master branch with macOS Catalina. I'm receiving weird errors.
Do you need this fix in v.7.x.x or could you wait for 8.0.0?

Damn, I cannot build master branch with macOS Catalina. I'm receiving weird errors.
Do you need this fix in v.7.x.x or could you wait for 8.0.0?

Sure

"Sure" is about version 8.0.0 or 7.x.x? :)

8.0.0


Deterministic flags and other globals do not get transferred to spawned processes

🐛 Bug
When using the ddp-spawn strategy, global flags like the torch.use_deterministic_algorithms flags set by the Trainer do not get transferred to the worker processes. The reason is that torch gets re-imported when spawning the workers (naturally) and thus the globals are back to defaults.
To Reproduce
import os

import torch
from torch.utils.data import DataLoader, Dataset

from pytorch_lightning import LightningModule, Trainer

class RandomDataset(Dataset):
    def __init__(self, size, length):
        self.len = length
        self.data = torch.randn(length, size)

    def __getitem__(self, index):
        return self.data[index]

    def __len__(self):
        return self.len

class BoringModel(LightningModule):
    def __init__(self):
        super().__init__()
        self.layer = torch.nn.Linear(32, 2)

    def forward(self, x):
        return self.layer(x)

    def training_step(self, batch, batch_idx):
        assert torch.are_deterministic_algorithms_enabled()
        loss = self(batch).sum()
        return {"loss": loss}

    def configure_optimizers(self):
        return torch.optim.SGD(self.layer.parameters(), lr=0.1)

def run():
    train_data = DataLoader(RandomDataset(32, 64), batch_size=2)
    model = BoringModel()
    trainer = Trainer(
        default_root_dir=os.getcwd(),
        limit_train_batches=1,
        limit_val_batches=1,
        limit_test_batches=1,
        num_sanity_val_steps=0,
        max_epochs=1,
        enable_model_summary=False,
        enable_progress_bar=False,
        strategy="ddp_spawn",
        devices=2,
        accelerator="cpu",
        deterministic=True,
    )
    trainer.fit(model, train_dataloaders=train_data)

if __name__ == "__main__":
    run()

Expected behavior
See assertion in the code.
Environment
PyTorch 1.10 and 1.11
PL 1.6 (master)
Additional context
I dreamed about it last night (no kidding) and checked this morning and the bug turned out to be real.
This applies to all globals from torch, not just deterministic flags. We already handle this problem for the seed in the DDPSpawnStrategy._worker_setup() method.
cc @justusschock @kaushikb11 @awaelchli @akihironitta @rohitgr7

Seeing this now for the first time. I'd say this is a huge bug. Do you have any ideas on how to fix this?

Yes, this can be fixed in the multiprocessing launcher directly. Had a branch on this, will dig it out.


Can't paste into login dialogue

Being unable to paste makes it difficult to use with password managers.
This is with a fresh unzip of the 0.3.0 Windows version.

Doesn't Ctrl + V work for you?

Yea, the hotkey did it. I don't know why I assumed it wouldn't after right-clicking failed. I guess that turns this into a mild convenience thing instead of a usability concern.


Allow CR to handle manifest patches

Problem
The custom resource (CR) for the knative operators should allow for tweaking all the resources deployed at the Kuberneters spec level. For example, allow for Affinity, Envs, HPA, Image pull policy, Annotations, Replicas, probes (readiness, liveness, startup), LifeCycle, Priority class, Tolerations, Request sizes...
For example, there are cases where the default deployment needs to be tweaked for a specific usage.
In one case we needed to add a Lifecycle preStop to a deployment to allow it more time to shutdown.
An example of how Istio handled this in the CR looked like this:
    ingressGateways:
    - name: istio-ingressgateway
      enabled: true
      k8s:
        overlays:
        - kind: Deployment
          name: istio-ingressgateway
          patches:
          - path: spec.template.spec.containers.[name:istio-proxy].lifecycle
            value:
              preStop:
                exec:
                  command: ["sleep", "25"]

Where ingressGateways in the high level CR component and istio-ingressgateway is the section of the manifest we are interested in patching.
The patch is straight forward, just a basic spec path and values to patch in there.
Which persona is this feature for?
integrator
Exit Criteria
See the deployment yaml output changed to include the patched values.
Time Estimate (optional):
not sure.
Additional context (optional)
Refs:
https://istio.io/docs/setup/install/standalone-operator/
https://istio.io/docs/setup/install/istioctl/#customize-kubernetes-settings

Related: https://github.com/knative/serving-operator/issues/302

We would like implement on a use case based approach, instead of offering one powerful way to override everything.
Another related topic: https://github.com/knative-sandbox/operator/issues/5


docs: initial github container registry integration guide

An initial guide to how to push to container images into GHCR from Dagger running in GitHub Actions.

CI failure seems unrelated to this change?

I've not reviewed in depth but a few questions off the top:

Why don't we incorporate this into the existing GitHub Actions integrations page? This would avoid duplicating the GHA workflow. Having two workflow examples risks user confusion, as it's then not clear which version is canonical.
The file should be called ....go instead of ...go.txt. You could place it in a separate subdir of snippets and include the dagger.gen.go and go.mod files, and then you would not need to import dagger in the Go code. Example structure here.

CI failure seems unrelated to this change?

CI error is failed to get edge: inconsistent graph state which does indeed seem unrelated.

Yeah, happy to move it into the GHA page as a sub-section if you think that's best!

@lukemarsden OK to push changes directly to your PR?

Sure please do!
lukemarsden.net
@.***
@lmarsden https://twitter.com/lmarsden
On Wed, 17 Apr 2024 at 20:39, vikram-dagger @.***>
wrote:

@lukemarsden https://github.com/lukemarsden OK to push changes directly
to your PR?
—
Reply to this email directly, view it on GitHub
https://github.com/dagger/dagger/pull/7088#issuecomment-2062082594, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACATUVE2IAPT56QUZ4N2CDY53FVTAVCNFSM6AAAAABGEBRLNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRSGA4DENJZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Updated the module reference to point to daggerverse/dagger-ghcr-demo instead of lukemarsden/dagger-ghcr-demo
This LGTM

Ping @kpenfound for review


[Libevent] include headers fails on x64-windows, using CMAKE

I'm doing a minimum test using libevent on WIN10 x64 with VS2017. What I've done is just

add fowlling to the CMakeSettings.json

  "variables": [
    {
      "name": "CMAKE_TOOLCHAIN_FILE",
      "value": "[vcpkg]/scripts/buildsystems/vcpkg.cmake"
    }
  ]

tell CMAKE to find libevent package, in CMakeLists.txt

  find_package(Libevent CONFIG REQUIRED)
  include_directories(${LIBEVENT_INCLUDE_DIRS})
  add_executable (hello ...)
  target_link_libraries(hello PRIVATE event_shared event_core_shared event_extra_shared)

When I include <event2/event.h> in the main.cpp, and build the project, Visual Studio reports a failure to open the header file. So I go to the [vcpkg]\installed\x64-windows\share\libevent\LibeventConfig.cmake to find out. And I made a little change from:

set(LIBEVENT_INCLUDE_DIRS "${LIBEVENT_CMAKE_DIR}/${CMAKE_CURRENT_LIST_DIR}/../../include")

to:

set(LIBEVENT_INCLUDE_DIRS "${LIBEVENT_CMAKE_DIR}/../../include")

So in this way the everything works fine.
My question is that is it a bug, that the package gave me the wrong LIBEVENT_INCLUDE_DIRS, or I'm using it in a wrong way?

Hi @blizardxsi, thanks for reporting this issue!
It's definitely a bug, we need to fix it.
Thanks.

Hi @blizardxsi  Since PR has been merged.
I close this issue now, please update vcpkg and rebuild it.
Thanks.


Adding a link to UC Browser's A2HS docs page to our docs page

Adding a link to UC Browser's A2HS docs page to our docs page.

[ ] This has been reviewed and approved by (NAME)
[ ] I have run gulp test locally and all tests pass.
[ ] I have added the appropriate type-something label.
[ ] I've staged the site and manually verified that my content displays correctly.

CC: @petele

:tada: This has been pushed live to https://developers.google.com/web/


Anvil RPC cache not working on docker

Component
Anvil
Have you ensured that all of these are up to date?

[ ] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (8d8bc28 2022-09-26T17:49:28.998299391Z)
What command(s) is the bug in?
anvil
Operating System
Linux
Describe the bug
When running anvil in docker (foundry:latest) we see that RPC cache is not created and not being used for other forks created on the same docker.
From looking at the file system - the path ~/.foundry/cache/rpc/ doesn't exit
the command we are running:
anvil -f https://eth-mainnet.alchemyapi.io/v2/xxxxx-xxxxxxxxxxxx-xxx_xxxxxx_xx --fork-block-number 15811946

is this the container path?
what if you map your host volume to the container?


API: return value for the bounds of an empty geometry?

From https://github.com/Toblerity/Shapely/pull/983#discussion_r496530155
With current Shapely, you get an empty tuple for the bounds of an empty geometry:
>>> from shapely.geometry import Polygon
>>> p = Polygon()
>>> p.bounds
()

In PyGEOS, we return 4 NaNs, instead:
In [1]: import pygeos

In [2]: pygeos.bounds(pygeos.Geometry("POLYGON EMPTY"))
Out[2]: array([nan, nan, nan, nan])

For the vectorized ufuncs, I think this makes sense. And actually also the only possible solution, because when applying this operation on multiple points, we need to be able to put the results in a single array with consistent dimension:
In [3]: pygeos.bounds([pygeos.box(0, 0, 1, 1), pygeos.Geometry("POLYGON EMPTY")])
Out[3]:
array([[ 0.,  0.,  1.,  1.],
       [nan, nan, nan, nan]])

So the question is then: for the scalar .bounds attribute on the geometry objects, do we keep the current empty tuple () result, or do we chagne to 4-length tuple (nan, nan, nan, nan) as well?
I would personally propose to change to 4 NaNs for the scalar attribute: 1) consistency with the vectorized operation, 2) consistency in the length of the returned value (eg p.bounds[0] will always work)

I agree to the proposed changes for the reasons provided above. Hopefully folks are testing the empty attribute to evaluate emptiness of geometries rather than the length of the bounds attribute.
For now, we'll need to make an API changes section in the docs (done here).

Probably not a big deal overall, but just to add a real use case, this change breaks a common algorithm for comparing geometry bounding boxes, something I personally do often for quick intersection-ish checks when I don't need a full R-tree:
from shapely.geometry import MultiPoint

def bbox_intersects(b1, b2):
    """https://gamedev.stackexchange.com/a/913"""
    return not (b2[0] > b1[2] or b2[2] < b1[0] or b2[3] < b1[1] or b2[1] > b1[3])

g1 = MultiPoint([[0, 0], [1, 1]])
g2 = MultiPoint([[0.5, 0.5], [1, 1])
g3 = MultiPoint([[3, 3], [4, 4]])
nan_bounds = [float('nan')] * 4

bbox_intersects(g1.bounds, g2.bounds)  # True
bbox_intersects(g1.bounds, g3.bounds)  # False

# Currently this would raise for an empty geometry, with nan bounds it will return True
bbox_intersects(g1.bounds, nan_bounds)

I guess I expect the bounds of an empty geometry to be empty, in the same way I'd expect the bounds of a dataset with no spatial component to be "empty"? Maybe I'm biased by past Shapely behavior, though.

Probably not a big deal overall, but just to add a real use case, this change breaks a common algorithm for comparing geometry bounding boxes, something I personally do often for quick intersection-ish checks when I don't need a full R-tree:
from shapely.geometry import MultiPoint

def bbox_intersects(b1, b2):
    """https://gamedev.stackexchange.com/a/913"""
    return not (b2[0] > b1[2] or b2[2] < b1[0] or b2[3] < b1[1] or b2[1] > b1[3])

g1 = MultiPoint([[0, 0], [1, 1]])
g2 = MultiPoint([[0.5, 0.5], [1, 1])
g3 = MultiPoint([[3, 3], [4, 4]])
nan_bounds = [float('nan')] * 4

bbox_intersects(g1.bounds, g2.bounds)  # True
bbox_intersects(g1.bounds, g3.bounds)  # False

# Currently this would raise for an empty geometry, with nan bounds it will return True
bbox_intersects(g1.bounds, nan_bounds)

I guess I expect the bounds of an empty geometry to be empty, in the same way I'd expect the bounds of a dataset with no spatial component to be "empty"? Maybe I'm biased by past Shapely behavior, though.

@tomplex thanks for that example use case. I agree that silently passing this as True is a worse behaviour.
Another option could be to simply raise an error for the scalar .bounds if the geometry is empty. As a user, you would still need to handle this error then (if you want to be robust for empty geometries), but basically you now also need to handle this case to watch out for len-0 tuples (and an explicit error about empty geometry not having bounds will be more informative than an "IndexError: tuple index out of range")

We discussed this last week, and were thinking to go with the tuple of length 4 (consisting of NaNs) option. That ensures consistency between the top-level vectorized method and the attribute. Opened a PR to update this -> https://github.com/shapely/shapely/pull/1416


[WEBSITE-935] Add routes testing

Created shared examples to help test the more generic routes
Added specs for all the routes and routing methods

@C-N-J can you rebase this? Unfortunately, the ID tests will fail now


Add support for "View Full Screen" for Dashboard Live chart

Add support for "View Full Screen" for Dashboard Live chart

Should we create different issue for managing performance for the live chart ?

Should we create different issue for managing performance for the live chart ?

Can you elaborate what is the performance issue for live chart?


Fix powered_by CI

@ben can you link the failed job please ?

it's here : https://github.com/massalabs/as/actions/runs/4859613255/jobs/8662451003


OAS: Fix discriminator field definition for Artifact

This fixes an improper polymorphic type definition by moving its discriminator to the composing types.
There's also a small fix for ignoring coverage.html, that is generated when running make test-cover.
Description
This problem was spotted while using the Kiota generator, and can be traced back to the following pattern,
which is incompatible with JSONSchema.
How Has This Been Tested?
Following the same steps laid out on the last PR referencing OAS #17:
make FORCE_SERVER_GENERATION=true clean build
make test

then,

start an MLMD server
run make proxy
run robot test/robot/ && TEST_MODE=python robot test/robot/MRandLogicalModel.robot

Merge criteria:

[ ]  The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
[x]  Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x]  The developer has manually tested the changes and verified that the changes work

@isinyaaa I noticed this PR is moving the discriminator to derived types. How does that help, or what is the difference?

@isinyaaa I noticed this PR is moving the discriminator to derived types. How does that help, or what is the difference?

IIUC, having the discriminator field defined on Artifact doesn't imply that it's present on the composing types, as there's no such thing as "required properties" that have been inherited. Thus, artifactType should be required on all the "composing" classes.
Just updated the broken link on the description which I think also highlights the point.

/lgtm
Thank you so much, this is great complementary work to make our OpenAPI contract more robust to be consumed by clients


fix: removed appLabels prefix from localization labels

@irmastnt could you please close this if it's no longer maintained please ? thanks


docs: get started on documentation

Contributor checklist

[x] My commit messages follow the Conventional Commit Message Format
For example: fix: Multiply by appropriate coefficient, or
feat(Calculator): Correctly preserve history
Any explanation or long form information in your commit message should be
in a separate paragraph, separated by a blank line from the primary message
[x] Bug fixes include regression tests
[x] Features include unit/acceptance tests

Pull Request Test Coverage Report for Build 11034733f7edb669a00c5f02c33b23588c763671-PR-15

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

Totals

Change from base Build 07b7a71b4740bedaef87e6bb87a91a78d006e071:
0.0%

Covered Lines:
0

Relevant Lines:
286

💛  - Coveralls


Module Upgrades

Having trouble upgrading the modules. Updating the image doesn't seem to bring redisgraph to latest version of its container

Figured it out by manually loading the modules.


Update BDI_DataImportFLSService to always consider Master-Detail fields update-able.

This set of changes enables the BDI_DataImportFLSService to always
consider Master-Detail fields as valid when checking their isUpdateable
property - in order to avoid the "You do not have permissions to modify field ..."
error when Master-Detail fields are mapped as target fields in Batch
Data Import Advanced Mapping.
Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-036222

Tracking W-036222

Ok, I created static instances in both the Permissions and Describe classes, and made a few updates to use the permissions instance for permissions calls in the isValid method.  I made a few methods on the Permissions class public and added one canCreate method to have consistency re: how those methods are called from the FLS validator class.

Approved, except then I noticed that something is going on with the tests? @kenlewis-sfdo

@ptewson-sfdo Looks like one change (to go back to calling the static getFieldDescribe method) didnt get into the last commit.  Fixed and pushed - tests re-running now.


Implement FormlessParser

Hey tommy-muehle,
in my case i have formless log files. Your parsers expect a strict line structure so i implemented a "FormlessParser". Now you're able to parse log files like this:
[10-07-2016] Cronjob "handleOrders" started
[10-07-2016] Cronjob "handleOrders" failed cause ....

kind regards,
ukrator

Thx @ukrator for this PR!


Add support for AVI videos

Hi there,
I'm very glad I found your project but since I had a bunch of AVI files I didn't really understand why you were hardcoding only mp4 as a support video filename since there's nothing really preventing the original creation date from being applied to these files as well.
The process worked fine for me. Here's the output after I modified the SUPPORTED_MEDIA_FILE_EXTENSIONS constant to temporarily only list ['.mp4'] (might be a neat feature, filter by only specific types):
$ yarn start --inputDir /Volumes/Monolith/Takeout/Google\ Photos/ --outputDir /Volumes/Monolith/Takeout/Clean/
yarn run v1.22.10
$ ./bin/run --inputDir '/Volumes/Monolith/Takeout/Google Photos/' --outputDir /Volumes/Monolith/Takeout/Clean/
--- Finding supported media files (.avi) ---
--- Found 0 JPEGs, 0 GIFs and 0 MP4s and 55 AVIs ---
--- Processing media files ---
Copying file 0 of 55: /Volumes/Monolith/Takeout/Google Photos/20070801/SNC10339.AVI -> SNC10339.AVI
Copying file 1 of 55: /Volumes/Monolith/Takeout/Google Photos/20070802/SNC10342.AVI -> SNC10342.AVI
Copying file 2 of 55: /Volumes/Monolith/Takeout/Google Photos/20070812/SNC10360-1.AVI -> SNC10360-1.AVI
Copying file 3 of 55: /Volumes/Monolith/Takeout/Google Photos/20080823/SNC10386.AVI -> SNC10386.AVI
...
Copying file 53 of 55: /Volumes/Monolith/Takeout/Google Photos/Trash/MVI_0231.avi -> MVI_0231.avi
Copying file 54 of 55: /Volumes/Monolith/Takeout/Google Photos/Trash/MVI_0232.avi -> MVI_0232.avi
--- Processed 55 media files (0 JPEGs, 0 GIFs and 0 MP4s and 55 AVIs) ---
--- The file modified timestamp has been updated on all media files ---
--- We did not edit EXIF metadata for any of the files. This could be because all files already had a value set for the DateTimeOriginal field, or because we did not have a corresponding JSON file. ---
Done 🎉
✨  Done in 10.05s.

The output files were correct as well:

Thanks for the PR @olivierlacan! I'm glad the tool has proved helpful to you. I'll merge your change so that others can benefit from it working on AVIs too 👍
With hindsight I'm not quite sure whether limiting the scope to specific hardcoded formats was a good idea or not. If it helps clarify, my original thinking was that this would make it less destructive for any other files that might come along for the ride (e.g. only touching stuff I know is compatible with exif metadata seemed safer than blindly attempting to modify every file it finds). I might make some additional tweaks soon to make it easier to customise the supported file types in one centralised place.


Attempting to use pyquil v4 on rigetti jupyter notebook

I am currently using the rigetti jupyter notebook, I tried running the sample code using pyquil v4, but ran into errors. I then ran the jupyter notebook using pyquil v3 and the code worked fine. I am also using qiskit 1.0.2 as I have qiskit code that requires that version. Is there a way to use pyquil v4 with rigetti-qiskit? If not, then is there a huge difference from pyquil v3?

Apologies, if you downgrade your qiskit dependency to ~0.46.0 it should be compatible with pyquil >=4.0. But since you are unable to due to needing >=1.0 features, you should track #53


Run stress test on the farming module

[ ] Measure gas usages with many farmers

duplicated https://github.com/tendermint/farming/issues/76


[ISSUE] ROSA integration tests are failing due to missing secret

Describe the issue:
The last run of ROSA integration tests is failing : https://github.com/camunda/camunda-platform-helm/actions/runs/10482775419
The error seems to be related to a missing secret integration-test that has been created at August 1 on the permanent cluster.

Actual behavior:
The tests are failing and the secret is absent
Expected behavior:
The tests should work and the missing secret should be imported in the on-demand cluster.
How to reproduce:
Run the on-demand tests
Logs:

Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

Platform: ROSA
Helm CLI version:
Chart version:
Values file:

We need to validate whether this issue is still present, and this issue needs to be updated with information from the failing build.  I can fill that in myself later, or you can @leiicamundi .

apiVersion: v1
data:
  admin-password: someBase64String
  client-secret: someBase64String
  connectors-secret: someBase64String
  console-secret: someBase64String
  identity-firstuser-password: someBase64String
  keycloak-secret: someBase64String
  management-password: someBase64String
  operate-secret: someBase64String
  optimize-secret: someBase64String
  password: someBase64String
  postgres-password: someBase64String
  smtp-password: someBase64String
  tasklist-secret: someBase64String
  zeebe-secret: someBase64String
kind: Secret
metadata:
  name: integration-test
type: Opaque

This is the shape of the referenced secret.  add this in the namespace that's failing for you, and you should be set.

@leiicamundi anything else to be done here?


chore: bump temp-write fixes #11960

Bump temp-write to latest version, so as to remove the deprecated dependency on uuid
Fixes https://github.com/prisma/prisma/issues/11960

Closing as our updates are managed by Renovate bot, though this version upgrade is blocked


FR_lfw::load() is not implemented

fr_lfw.cpp has its implementation in FR_lfwImp::load().
The author seems to forget to add it to FR_lfw::load().
This cause segmentation fault during execution of fr_lfw_benchmark.cpp.

FR_lfw::create() returns instance of FR_lfwImp, which actualy do the job.
The cause of your crash somewhere else, I can suppose that you do something wrong with data.
Please, see usage here: http://docs.opencv.org/3.0-last-rst/modules/datasets/doc/fr_lfw.html


Add the ability to hold a pulley in place with redstone

Right now pulleys can only pull rope up or release rope, depending on whether or not mechanical power is applied. There is currently no way to hold a pulley at a specified location, which this would allow (and make multi-floor elevators possible)

That is already the case but only when powered from the top or if redstone runs into the block from the side. redstone torches or redstone blocks directly next to the pulley for some reason seem to not cause it to hold in place (might be a bug for those cases?)

 I do think that it could maybe do with being allowed to accept indirect power instead of requiring direct power.


Evaluate kubernetes for managed services

Implementation sketch:

https://github.com/CloudCredo/kubernetes-release
https://github.com/trustedanalytics/kubernetes-broker

Tasks:

[ ] Update k8s-release to current etcd, docker, k8s
[ ] Deploy k8s-release to staging
[ ] Deploy k8s-broker to staging

Can you give an update as to how this work is going? It looks like a research story, but there's no timebox on it, and it's hard to see what other backlog work is implied.

Long since done.


Elixometer 1.1

Preparing for 1.1 release; updated docs and bumped version. Hex.PM stuff looks good.
@jparise

:+1:


pymn.MetaNeighborUS(tasic, 'study_id', 'primary_type',trained_model=biccn_subclasses) with "NaN" in tasis.uns["MetaNeighborUS"]

I have do the same data with the pepline in "https://github.com/gillislab/pyMN/blob/master/notebooks/protocol2_pretrained_reference.ipynb", but all the values in the asis.uns["MetaNeighborUS"] is "NaN", why?

with python3.8.11 and scanpy 1.8.2

Hi, the quick fix is to set symmetric_output=False in the MetaNeighborUS call. I will aim to fix that in  protocol2_pretrained_reference.ipynb as it should be corrected to set that flag.


DrawerWidth for permanent Drawer returning undefined

Describe the bug
Line 87 of Drawer.js results in 100% * .45 which returns `NAN, this breaks the permanent drawer type since the position of the main content is determined by this value.
Additional context
Update to this
    let drawerWidth = Platform.OS == 'web' ? this.state.drawerWidth : screenWidth * (widthPercentage || 0.45);`

Because width should default to 240 on web according to Material Docs

closed by #345


Improve development experience

This PR adds a simple Posix-compliant Shell script that build base image and runs development container at once.
Apart from reducing the number of commands needed to run dev container, this script also reduces startup time because it reuses already-created development container and its base image.
So, starting dev container now is as simple as running
$ ./dev

The first launch will be slow because it will build base image and create dev container, but all subsequent launches will be very fast.
The only caveat is that you'll need to remove connectable-dev container each time you change arguments to docker create inside dev script, or change path of the repo directory:
$ docker rm connectable-dev

This PR depends upon #33, but I can rebase it if #33 get declined for some reason.

This is great, but I think I have a pattern for this already. I'll have to look it up ... but for now I'm ok with bringing this in ... except I don't understand the IS_CONNECTABLE_SELF part. That seems unnecessary. The role of this code really shouldn't have any effect on the connectable code itself.

@progrium, I've rebased this onto master and removed the magic variable.

Merging this with the expectation it could change based on how I've solved this previously in other projects! :)

It would be really interesting to see how you've solved that, I'm pretty sure it is much better than this solution :)


Move back jandex dependency and update its version

https://issues.jboss.org/browse/ISPN-5431
https://issues.jboss.org/browse/ISPN-5432

Pulling ...

Integrated. Thanks @vjuranek !


Fix slow patch checking with commits that add or remove many files

Running git update-index for every individual file is slow, so add and remove everything with a single git command.
When such a big commit lands in the default branch, it could cause PR creation and patch checking for all open PRs to be slow, or time out entirely. For example, a commit that removes 1383 files was measured to take more than 60 seconds and timed out. With this change checking took about a second.
This is related to #27967, though this will not help with commits that change many lines in few files.

Side notes: This is a good example of avoiding too many file paths in the git command, using stdin.


[INLONG-1531]Go SDK should init the flow control item of the partition

Signed-off-by: Zijie Lu<EMAIL_ADDRESS>Title Name: [INLONG-XYZ][component] Title of the pull request
where XYZ should be replaced by the actual issue number.
Fixes #1531
Motivation
Explain here the context, and why you're making that change. What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

Codecov Report

Merging #1532 (cf40d78) into INLONG-25 (7ca091d) will increase coverage by 0.02%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             INLONG-25   #1532      +/-   ##
==============================================
+ Coverage         7.48%   7.51%   +0.02%
  Complexity         479     479
==============================================
  Files              267     267
  Lines            29500   29500
  Branches          4843    4843
==============================================
+ Hits              2209    2216       +7
+ Misses           26816   26810       -6
+ Partials           475     474       -1

Impacted Files
Coverage Δ

.../java/org/apache/flume/sink/tubemq/TubemqSink.java
55.42% <0.00%> (+4.00%)
:arrow_up:

Continue to review full report at Codecov.

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


WC2-603_WC2-604: ETL debug page not showing first visit or shows exit date for ben not yet exited

Explain what problem this PR is resolving
Related JIRA tickets : WC2-603, WC2-604
Self proofreading checklist

[x] Did I use eslint and black formatters
[ ] Is my code clear enough and well documented
[ ] Are my typescript files well typed
[ ] New translations have been added or updated if new strings have been introduced in the frontend
[ ] My migrations file are included
[ ] Are there enough tests
[ ] Documentation has been included (for new feature)

Changes
Fixed ETL to store both admission and followup visits linked to beneficiary.  The bug was mainly appearing for Nigeria data.
How to test
From the local instance with wfp coda database, run ETL script to generate data for:

Nigeria:  docker compose run iaso manage etl_ng
South Sudan: docker compose run iaso manage etl_ssd

Then, try to access to debug page for beneficiary belongs to account:

Nigeria: http://localhost:8081/wfp/debug/684/
South Sudan: http://localhost:8081/wfp/debug/323/

You should see all visits linked to beneficiary and correct exit date when beneficiary has discharged.
Print screen / video
1. Nigeria

2. South Sudan

@bramj @butofleury is there a way to test this on dev or on QA please ?

@Fleury @bramj , both debug pages are accessible while connected to a South Sudan account, is this the desired effect ?


Feature/remove crud enforcement

Proposed changes
Remove restriction in the required operations so resources only exposing POST and GET are also considered. See the issue raised for more detials.
Type of change
What type of change does your code introduce to the provider? Please put an x (w/o heading/trailing white spaces)
in the boxes that apply:

[ ] Bugfix (change that fixes current functionality)
[x] New feature (change that adds new functionality)

Does this Pull Request resolve any open issue? If so, please make sure to link to that issue:
Fixes: #16
Checklist
Please put an x (w/o heading/trailing white spaces) in the boxes that apply:

[x] I have read and followed the CONTRIBUTING guidelines
[x] I have made sure code compiles correctly
[x] I have run 'Lint' and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added/updated necessary documentation (if appropriate)

👍


"Invalid state" error in mergeSelectionSets when merging InlineFragment.

Describe the bug
I have two fragments that overlap in the data they query. That is normally fine, but when they both query a union type using an  inline fragment, an "Invalid state." error is throw by mergeSelectionSets.
To Reproduce
Here is a minimal reproduction, which does not use fragments.
https://codesandbox.io/s/bitter-brook-tg5hw

My GraphQL schema:

type Query {
    user(id: ID!): User!
}

type Online {
    onlineSince: Float!
}

type Offline {
    offlineSince: Float!
}

union Status = Online | Offline

type User {
    id: ID!
    status: Status!
}

My GraphQL operations:

query user {
    user(id: 1) {
        id
        status {
            ... on Online {
                onlineSince
            }
        }
         status {
            ... on Online {
                onlineSince
            }
        }
    }
}

My codegen.yml config file:

schema: schema.graphql
documents: document.graphql
generates:
  types.ts:
    plugins:
      - typescript
      - typescript-operations```

Expected behavior
The types from the two fragments should be merged.

not sure if it's the exact same issue I'm facing, but it works on "@graphql-codegen/typescript-operations": "1.18.4"

I didn't realize the template codesandbox was not up to date on the dependencies and I didn't change it. However, the issue still exists in the latest versions. I updated the repro to the latest dependencies and it still throws "invalid state".
@correttojs can you link to the issue you have?


[Code lens] Wrong signature

One more sample

No CodeLens for Property
Incorrect for field

    type ``Rewrite me``() =
        [<Microsoft.FSharp.Core.DefaultValue>]
        val mutable _field : System.DateTime

        member x.Property
            with get () = x._field
            and set (v) = x._field <- v

One more sample

type MyType =
    static member requireType (actual, expected, fn) =
        match actual with
        | expected -> fn()
        | _ -> failwith ""

FSAC returns wrong range for _field, which results with wrong "tooltip" request:

{
        "UniqueName": "Rewriteme_1_of_1",
        "Name": "_field",
        "Glyph": "Field",
        "GlyphChar": "F",
        "IsTopLevel": false,
        "Range": {
          "StartColumn": 26,
          "StartLine": 5,
          "EndColumn": 41,
          "EndLine": 5
        },
        "BodyRange": {
          "StartColumn": 26,
          "StartLine": 5,
          "EndColumn": 41,
          "EndLine": 5
        },
        "File": "e:\\github\\Test1\\Test1\\Test2.fs",
        "EnclosingEntity": "C",
        "IsAbstract": false
      }

Fixed in FCS here https://github.com/fsharp/FSharp.Compiler.Service/pull/662 and in Ionide

Fixed in https://github.com/ionide/ionide-vscode-fsharp/pull/251


Duplicate definition of searchQuery module

Saw this in the console:
Duplicate definition of module 'vs/workbench/parts/search/common/searchQuery'

@joaomoreno I do not see any such logs in the console.
But, when I searched for this module in code, I do not see any indication of duplicates.
But, I saw some commented lines in workbench.main.ts
// require.config({
// 	ignoreDuplicateModules: [
// 		'vs/workbench/parts/search/common/searchModel',
// 		'vs/workbench/parts/search/common/searchQuery'
// 	]
// });

I do not know if it is somehow related.

@sandy081 yes, I think @alexandrudima did this and it is related


Fix typo in parsing of max connections per thread from config file

Good idea, done. BTW I wonder what is min_threads option useful for?
$ grep -Rn min_threads
etc/openwsman.conf:48:min_threads = 4
README.md:61:    min_threads = 1
src/server/wsmand-daemon.c:98:static int min_threads = 4;
src/server/wsmand-daemon.c:204: min_threads = iniparser_getint(ini, "server:min_threads", 1);
src/server/wsmand-daemon.c:358:int wsmand_options_get_min_threads(void)
src/server/wsmand-daemon.c:360: return min_threads;
src/server/wsmand-daemon.h:84:int wsmand_options_get_min_threads(void);
It seems that it can be safely removed.

Yeah, min_threads is unused indeed it seems. It probably never was used.


Fix google maps when displaying directions with sourceLatitude/source…

@tschoffelen This is a quick fix and some adjustments. I introduced the sourceLatitude/sourceLongitude but there was an error with the iPhone Google maps. Now it's fixed and tested in real devices.

@tschoffelen 👍


A question about clustering

Thank you for sharing this work!
Actually, I have a question about the clustering process in mmt_train_kmeans.py file.
       dict_f, _ = extract_features(model_1_ema, cluster_loader, print_freq=50)         cf_1 = torch.stack(list(dict_f.values())).numpy()         dict_f, _ = extract_features(model_2_ema, cluster_loader, print_freq=50)         cf_2 = torch.stack(list(dict_f.values())).numpy()         cf = (cf_1+cf_2)/2
Here, I find mean-nets of model1 and model2 are used to generate features for clustering and initializing classifiers. But it seems that current models( model1 and model2) in every epoch are used instead of mean-net to compute features for clustering in the MMT paper. Does using mean-net here provide better performance? Could you give some explanations about it? Thanks!

Yes, we adopted mean-nets to extract features for clustering in each epoch. The features extracted by mean-nets are more robust. I did not remember the performance gaps. You could have a try to replace it with current nets.

Got it. Thank you so much for the reply! May I ask one more question?
In the OpenUnReID repo, the implementation of MMT should be MMT+, right? In that repo, source_pretrain/main.py uses only source domain data for pretraining, not like using both source and target(only forward) in the MMT repo.
Meanwhile, for target training, it uses both source(labeled) and target(pseudo label) to conduct MMT training in OpenUnReID with a MoCo-based loss and DSBN, right? Please correct me if there is a misunderstanding. Thanks!

MMT+ in OpenUnReID does not adopt source-domain pre-training. It uses two domains' images to conduct MMT training from scratch (ImageNet pre-trained). The MoCo loss is not adopted and DSBN is used. The MoCo loss only appears in the repo for VisDA challenge.

Thanks for the help!


New mailing list: transition-team

Claudio is admin. Publicly listed but closed membership.

Created and configured.


DVC tracked reports an error when there are no DVC-tracked files

On this repo https://github.com/shcheklein/ensemble-dvc-template/commit/c463042affec65b1ebca65e2588a8520d4637b1d

Extension version: 0.5.7
DVC version:
DVC version: 2.32.0 (pip)
---------------------------------
Platform: Python 3.9.13 on macOS-12.6-arm64-arm-64bit
Subprojects:
        dvc_data = 0.22.0
        dvc_objects = 0.11.0
        dvc_render = 0.0.12
        dvc_task = 0.1.4
        dvclive = 0.12.1.dev8+g243ae28.d20221030
        scmrepo = 0.1.2
Supports:
        http (aiohttp = 3.8.3, aiohttp-retry = 2.8.3),
        https (aiohttp = 3.8.3, aiohttp-retry = 2.8.3)
Cache types: reflink, hardlink, symlink
Cache directory: apfs on /dev/disk3s1s1
Caches: local
Remotes: None
Workspace directory: apfs on /dev/disk3s1s1
Repo: dvc, git

We need to check if it affects the onboarding flow when there are no DVC-tracked files.

Can't reproduce this anymore. I think this is fixed now.


Date Range using input with clear button Not Working

const [dateRange, setDateRange] = React.useState([null, null]);
const [startDate, endDate] = dateRange;
function updateExecutionList(date): void {
setDateRange(date);
//  props.updateExeList(date);
}
<DatePicker
selectsRange={true}
            ref={datepicker}
            startDate={startDate}
            endDate={endDate}
            isClearable={true}
            className="inputField expstart"
            placeholderText="Date"
            dateFormat="d MMM, yyyy"
            highlightDates={highlightWithRanges}
            onChange={(update): void => {

                updateExecutionList(update)
              }}

           // customInput={<ExampleCustomInput />}
        >

When first date select calender get closed and also slected value is not showing.
any one help if i am doing somthing wrong

I have the same problem as @UnikoveNeeraj
I'm using the sample code from the official site where it works.

But in my component code, displaying the selected range doesn't work. There is also no clear values button. As you can see from the logs, the selected values are perfectly passed through the callback function in the array format.

I use "react-datepicker": "3.8.0" and "react": "16.8.4".
Me component code:
import React from "react";
import PropTypes from "prop-types";
import DatePicker from "react-datepicker";

function DateRangePicker(props) {
	const [dateRange, setDateRange] = React.useState([null, null]);
	const [startDate, endDate] = dateRange;

	/* Logging values */
	React.useEffect(() => props.onChange(dateRange), [dateRange]);

	return (
		<DatePicker
			selectsRange
			endDate={endDate}
			isClearable={true}
			startDate={startDate}
			onChange={(dates) => setDateRange(dates)}
			shouldCloseOnSelect={false}
		/>
	);
}

DateRangePicker.propTypes = {
	onChange: PropTypes.func.isRequired,
};

DateRangePicker.defaultProps = {

};

export default DateRangePicker;

I am also facing the same issue, on selecting date range its not displaying selected date in Input field. here is the code, we are using
https://codesandbox.io/s/blissful-blackwell-bk56e?file=/src/App.js

I am also facing the same issue (Dates and clear button isn't displayed after selection). Used the same example from the docs. https://reactdatepicker.com/#example-date-range-using-input-with-clear-button

I am experiencing the same issue and had to implement the workaround from @sharanya5 (Thanks!).
However I am also experiencing issues with the popper closing when selecting "startDate", and as such I have to open the popper again to select "endDate". I have to set "shouldCloseOnSelect" to false to keep the popper open, but then I have to manually close the popper when selecting "endDate". I expect "shouldCloseOnSelect" should be true and the popper should close only when both "startDate" and "endDate" has been filled?

I am having exactly this issue.  When I select the first date, the calendar closes. It then re-opens to select the second date. The date range does not display in the input field, however. And no clear button shows up.  My code is essentially the same as the demo code, except for where I store and retrieve the dates.  I'm happy to give details as needed, but the examples above pretty much capture it.

same issue with the start selection closes the popper.

On version 4.1.1 the date range selection functionality works correctly!
Thanks!
function DateRangePicker() {
	const [startDate, setStartDate] = React.useState(null);
	const [endDate, setEndDate] = React.useState(null);
	const onChange = (dates) => {
		const [start, end] = dates;
		setStartDate(start);
		setEndDate(end);
	};

	return (
		<DatePicker
			selected={startDate}
			onChange={onChange}
			startDate={startDate}
			endDate={endDate}
			selectsRange
			isClearable
		/>
	);
}


Uncaught TypeError: Cannot read property 'duration' of undefined

Hiya!
I'm loving choo & choo-log, but just started seeing this error show up in console:
Uncaught TypeError: Cannot read property 'duration' of undefined at renderPerformance (bundle.js:1541) which comes from window.performance.getEntriesByName('choo:render') returning an empty array.
Let me know if having my app would help repro, but I'm guessing it's just some sort of race with the performance mark/measure stuff in choo proper.
Thanks!

This happens if you call render before DOMContentLoaded is called.
To solve it i wrapped adding my models in a .on('DOMConentLoaded', /* effects and models */)
app.use((state, emitter) => { emitter.on('DOMContentLoaded', () => {
  app.use(todos)
})})


Allow Filter to be Done on Vaccination Center's Name

Usually, in case of cities, searching by PIN or District works fine because of less Geographical Area. However, in case small towns or village, it is pretty difficult just to get slot based on PIN or District as there are scenarios where CVCs (Covid Vaccination Centres) are around 30km apart still share the same PIN Code. In that case, it makes sense to give the User ability to Filter on CVC's Name.
Name of the CVC can be found from COWIN's Portal:

For Example, in the above scenario, the name of the CVC is  > Apollo Hospital Modern School

Feature Added with e503dbc45d2ecdc214c9678785525ab461f69e6d.
@PSuyog97 Please review the change. Shall be integrated in the next release.

Changes integrated in Latest Version with Release v3.0.0
and deployed, hence closing the Issue

can we filter multiple vaccines centers of different pincodes ??
like x in z pincode
y in j pincode
i in o pincode

Hi,
As of now, the feature of searching by Multiple Centre Names is not there.
You can only search for a particular centre within PIN/District.
Adding mapping of Names with PIN would be a bit challenging, but can be done
Sent from my iPhone

On 20-May-2021, at 1:50 PM, jayeshp004 @.***> wrote:

can we filter multiple vaccines centers of different pincodes ??
like x in z pincode
y in j pincode
i in o pincode
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

can we filter multiple vaccines centers of different pincodes ??
like x in z pincode
y in j pincode
i in o pincode

Working on the feature, shall be deployed soon. Shall let you know

can we filter multiple vaccines centers of different pincodes ??
like x in z pincode
y in j pincode
i in o pincode

Hi @jayeshp004 The feature is added and shall be released today with v4.2.0.


I can't find any tin in my world

nevermind i found two ores at y85, can you make describe the distribution of resources?


Version 2.x : add support for symfony 3.1

I've this construction:
// $formBuilder = \Symfony\Component\Form\FormBuilder
                $formBuilder
                    ->add('translations', TranslationsType::class, array(
                            'exclude_fields' => array(

                            ),
                            'fields' => array( // Explicitly set labels for a2lix_translations
                                'title' => array(
                                    'label' => 'input.title',
                                ),
                                'introduction' => array(
                                    'label' => 'input.introduction',
                                ),
                                'contents' => array(
                                    'label' => 'input.contents',
                                ),
                            ),
                        )
                    );

Which worked fine in symfony 2.8, but after upgrading to 3.1, I get these errors:

The options "exclude_fields", "fields" do not exist. Defined options are: "action", "allow_extra_fields", "attr", "auto_initialize", "block_name", "by_reference", "compound", "constraints", "csrf_field_name", "csrf_message", "csrf_protection", "csrf_token_id", "csrf_token_manager", "data", "data_class", "disabled", "empty_data", "error_bubbling", "error_mapping", "extra_fields_message", "inherit_data", "invalid_message", "invalid_message_parameters", "label", "label_attr", "label_format", "mapped", "method", "post_max_size_message", "property_path", "required", "translation_domain", "trim", "upload_max_size_message", "validation_groups".

After I remove those non-existing options, my site loads a bit further, but now I get these errors:

Notice: Undefined index: fields

Might have to do with:

You have to use configureOptions() from OptionsResolver instead of setDefaultOptions() from OptionsResolverInterface

Well, it turns out this bundle already has support for symfony 3.x but the installation instructions make it so only versions 2.0.0 up to 2.1.0 are installed. The support has been added in 2.1.0 and up.
Change in your composer.json
"a2lix/translation-form-bundle": "~2.0.0",
to
"a2lix/translation-form-bundle": "^2.1",

actually I'm still facing this issue even changin the bundle version


Specify versions of ios and android plugins

Adds ability to specify the versions of the cordova-ios and cordova-android plugins

@godrei can you confirm the reason the check failed is due to the cordova console plugin being present in the config.xml? https://issues.apache.org/jira/browse/CB-13164.  It manifests itself by throwing a linker error:
...steps-ionic-archive/_tmp/platforms/ios/build/emulator/libCordova.a(CDVLogger.o)
ld: 2 duplicate symbols for architecture x86_64

I'm not sure if it's feasible to explicitly remove the plugin from the sample project or not

@nhammond101, I understand that at the moment cordova-ios master branch is ideal, but once Apache releases 4.5.2, latest will likely be the better choice going forward (and should probably be the default?).

@bayssmekanique the default (leaving the version empty) should be (and is) the pinned version for the ionic/cordova version, as ionic cordova platform add ios and ionic cordova platform add ios@latest install different versions

You're right, I was looking at the changes to the test-step.

Thanks for the PR :) We will review this asap.

Everything looks good now.  Some issues with the latest version of Android, but that's an issue with the testing image.  I would recommend reinstating the cordova_android_version attribute in the test to something like 6.2.3 (prior to Android 26 target), but otherwise I think the PR is stable (I've been running in production for a few days without issue).

@nhammond101 and @bayssmekanique thanks for the update! I will notify you once the new version is available in the steplib.

@nhammond101 and @bayssmekanique the new version (1.1.0) is available in the steplib.


[Removal]: Request removal from denylist

Hotspot Name
Brief Coffee Raven
Hotspot b58 Address
11jYbyqa3BZkNE422YsroVYbBwsDX6C1mwq5Umbxn83uAa4bWtT
Discord Handle
Terek#1129
Hotspot Manufacturer
Bobcat
Removal Reason
Purchased this minor (Bobcat) from the manufacture added a external 8dbi antenna and mounted it 8m off the ground in the backyard on to a tree where I then deployed it.
Modifications
Yes
Extra forwarders
No
Extra antennas
No
Additional Information
Only modification was adding the external 8dbi antenna and placing it outside in the backyard as high as I could. I am no gamer and would like to request removal of this hotspot from deny list to contribute to the real network to prosper it.
Look forward to Helium Support Team to resolve this matter.

It's not on the denylist


Correction of Typos in the Chinese Document in appendix.md

Purpose of the pull request

Correct typos in docs/zh/guide/task/appendix.md
Brief change log

Change "不在重复执行" to "不再重复执行"
Verify this pull request
The current request only modified the documentation and did not change the code.

Issue：https://github.com/apache/dolphinscheduler/issues/16035


Find missing pairs, check nesting of brackets

Sometimes you just forget the closing pair in a line:
No nesting:
" without "
< without > in ""
Nesting possible, check as well:
[ without ]
( without )
And in different lines (but the same file):
Random without Random (in the same scope)
sceneStart without sceneEnd (in the same file)

split random/scene into separate issue

split random/scene into separate issue


[Program]: Write a R program to convert octal to hexadecimal

Description
Write a R program to convert octal to hexadecimal
Octal is a base-8 number system. It uses only eight digits: 0, 1, 2, 3, 4, 5, 6, and 7. The digits are called octits. An octit is the smallest unit of information in a computer. An octit can be used to represent a single value, such as 0, 1, 2, 3, 4, 5, 6, or 7, or it can be used to represent a single state, such as on or off.
Hexadecimal is a base-16 number system. It uses sixteen digits: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, and F. The digits are called hexits. A hexit is the smallest unit of information in a computer. A hexit can be used to represent a single value, such as 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, or F, or it can be used to represent a single state, such as on or off.
To convert an octal number to hexadecimal, we can use the following algorithm:

Convert the octal number to decimal.
Convert the decimal number to hexadecimal.

Input  : 12
Output : A

How to contribute

Save the solution in program/program/convert-octal-to-hexadecimal/convert_octal_to_hexadecimal.r file

please assign this issue to me sir.


x/website: replace "reference type" in maps article

I think it would be better to do without the term "reference type" in the article Go maps in action. I have been trying to research what a reference type exactly is supposed to be and found no explanation from the resources of the Go project, however contradicting ones elsewhere.
In the light of this commit (https://github.com/golang/go/commit/b34f0551387fcf043d65cd7d96a0214956578f94), I think it would be more consistent to also dispense using this term in the blog.

cc @dmitshur
note there's an entire section on Reference Types in the json article: https://blog.golang.org/json#TOC_6.

https://en.wikipedia.org/wiki/Value_type_and_reference_type

@ianlancetaylor: please explain what you want to say with your comment. I am having a hard time guessing.

@Tiffilore Sorry for being confusing.  In the initial post on this issue you said "I have been trying to research what a reference type exactly is supposed to be."  My comment was pointing you to the Wikipedia page that explains what a reference type is.  It's a standard term in computer science.

@ianlancetaylor Thank you for answering. But I think you misunderstand my initial post on the issue. You are certainly quoting me wrong. My sentence does not end where you let it end.
I wrote that I have found no explanation from the resources of the Go project, however contradicting ones elsewhere.
I am not sure that you have read the Wikipedia article you are suggesting.
Well, I have and for several reasons, I do not really see that that could settle the matter.
That a term is a standard term does neither imply that it has a clear definition most people or the relevant group for the matter at hand agree upon nor that it is useful for certain purposes like for the purpose of classifying types in Go.
Let's look at slices for example: some consider them reference types, some don't and I think it really depends on the definition, who is right.
While I could not find a definition of "reference types" by the Go project (no, there is also no definition in the json article @dmitshur referred to),  I found the commit I have referred to: "spec: Go has no 'reference types'" (https://github.com/golang/go/commit/b34f0551387fcf043d65cd7d96a0214956578f94). So there is no need to argue about what a reference type is or what a reference type is in Go or what types are reference types, since the matter has been already settled there. (I think it is worth looking at this commit in more detail).
Both blog articles, Go maps in action and JSON and Go have been written prior the commit I was referring to and thus, I think it is most likely that their use of the term "reference types" is outdated and should be changed therefore.

@Tiffilore It's true that I truncated the sentence in my quote, but I don't understand why the truncation makes any difference to my reply.  There are many standard computer science terms that are not also documented by the Go project.  There is no reason for the Go project to document them.
Let's move forward and focus on what, if anything, should change.  Personally I think the blog post you mention (https://blog.golang.org/maps) is clear.  The sentence from the blog is "Map types are reference types, like pointers or slices, and so the value of m above is nil; it doesn't point to an initialized map.".  This uses "reference types" with the standard computer science meaning, and expands on it by explaining that map types are similar to pointer types and slice types.
It's true that the term "reference types" was dropped from the language specs, but I don't see why that affects less format documentation like the blog post.
So I don't see a problem here.  Can you give an example of a specific change that you think should be made?  Thanks.

@ianlancetaylor: obviously, there are still some misunderstandings, so I will try to restate my argument again and subdivide this discussion into separate points.
(1) Consistency
No, the term "reference types" was not simply dropped from the language spec, it was dropped for a reason. That reason was given in the commit message, "spec: Go has no 'reference types'" to quote it again.
My main argument is asking for consistency. If the decision has been made that there are no reference types in Go, please be consistent and do not continue claiming that there are in the blog.
You seem to have a different view on that and less of a problem with inconsistencies.
(2) Reference types in Go
Instead you want to re-open the discussion again whether classifying certain types in Go as "reference types" is a good idea or not. Although this is certainly an interesting discussion, I am unsure whether this is the right place to do that. Maybe commenting on the commit I have been referring to would be more suitable.
I do not know why exactly it was decided that there are no reference types in Go, I could only speculate and am unsure whether I am really suited to do so and whether this is the right place to do so, so I will refrain from it.
However, I have already indicated that the issue is more contentious than it might seem at first sight, a claim which you have chosen to ignore. Let me nevertheless give you a very small example to back up my claim:  In this post, Dave Cheney claims that "unlike map and chan types slices are value types".
(3) Specific changes
I think I was pretty clear from the beginning: I suggested to dispense using the term "reference type" in the go blog. Again, I am not sure that I am the right person to offer a specific solution, whereas I am pretty sure that I am not obligated to offer a specific solution in raising an issue, but I can certainly think about it.

Clearly my contributions to this discussion are not helping, so I will step aside.  Thanks for your interest in Go.

  I'm doing my best, and I will try to do better in the future.  There are many other people on the Go team who can carry this issue forward.

Personally, I think the blog posts are fine and the spec should be changed.
Right now, the spec's non-use of "reference type" or any equivalent term makes its descriptions of the semantics of the relevant types fairly unclear: #5083.
I know that some folks don't like referring to certain Go language features as "reference types". I have an impression that it's because of the ambiguity between (1) "reference types", the general concept as described on the wikipedia page, which includes any type of pointer; (2) "references", the specific C++ feature; and (3) "pass by reference", which is supported by some other languages but not by Go. However, we need some term to refer to the concept, and as the blog post and other documents show, that term will be "reference type" unless someone comes up with a different Go-specific word for us to use.

There are some dilemmas for Go to make a clear decision to whether or not to use the reference type term.
Sometimes, the term is helpful to make some explanations,. But sometimes, it brings more confusions.
That is why the term was in the spec but removed later.
There are still many articles, either official ones or unofficial ones, which are using this term.
There are some possible definitions for this term.

Types each of whose values may contain an underlying indirect part.

This excludes pointer types as reference types.
However, personally, I think this is the simplest and clearest definition.

Reference types just mean pointer types.

This needs to explain map / slice / channel / function / string / interface contain pointers in implementation internal.
This definition is implementation depended, so it is not perfect in syntactical view.

Types each of whose values may contain an underlying indirect part and types which explicitly contain pointers.

In other words, types contain (either explicitly or implicitly) pointers are called referenced types.

The latter two definitions need to mentions that values of some reference types may also represent non-reference properties.

Since @ianlancetaylor has thanked me for my interest in Go, I would like to thank him for representing Go they way he did. I always wondered how this comes about and your conduct helped me to understand why, so I sincerely thank you.