wechat-uos: cannot launch: Segmentation fault

Describe the bug
Segmentation fault prevents wechat-uos from launching.
Steps To Reproduce
Steps to reproduce the behavior:

Install wechat-uos from master branch
Run command wechat-uos

[0717/011423.570562:ERROR:directory_reader_posix.cc(42)] opendir /home/ulysses/.xwechat/crashinfo/attachments/87ea53f2-53b6-4bcd-9fd8-2b455a4eb49d: No such file or directory (2)
/nix/store/b8j5hyg6pwa0ww3c48lamw2k3ayv6d87-wechat-uos-launcher: line 14:  6973 Segmentation fault      (core dumped) /nix/store/5jklq1cc6pskky719gh0f64sz9nlafwj-wechat-uos-<IP_ADDRESS>/opt/apps/com.tencent.wechat/files/wechat

Expected behavior
WeChat launches.
Screenshots
Additional context
1d2d850e works, so it is NOT #309435 that broke the package.
Notify maintainers

@pokon548
Metadata

system: "x86_64-linux"
host os: Linux 6.1.97, NixOS, 24.05 (Uakari), 24.05.2580.194846768975
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.18.4
channels(root): "nixos-24.05, nixos-hardware, nixos-unstable"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

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

https://matrix.to/#/!cacbMwUwsLZ6GKac:nichi.co/$g614RgC4xlu3GtyIPmf1mCBe0VEZmQwt-EKSq1Rj3rw?via=nixos.org&via=nichi.co&via=matrix.org
Seems to be caused by missing libxcb-icccm.so.4

I can determine that 655a58a72a6601292512670343087c2d75d859c1 is bad and  00d80d13810dbfea8ab4ed1009b09100cca86ba8 is good.
Since there is a Python package build failure between these two commits, bisect is almost impossible.
strace result seems to not support missing libxcb-icccm.so.4
coredump backtrace:
#0  __strlen_evex () at ../sysdeps/x86_64/multiarch/strlen-evex-base.S:81
No locals.
#1  0x000063592f4f027c in ?? ()
No symbol table info available.
#2  0x000063592f4f2c56 in ?? ()
No symbol table info available.
#3  0x000063592f4f92b9 in ?? ()
No symbol table info available.
#4  0x000063592f1f1ce3 in ?? ()
No symbol table info available.
#5  0x000063592f1f32f5 in ?? ()
No symbol table info available.
#6  0x000063592efedeb6 in ?? ()
No symbol table info available.
#7  0x000063592edbcf33 in ?? ()
No symbol table info available.
#8  0x00007b2fa5c74a42 in start_thread (arg=<optimized out>) at pthread_create.c:447
        ret = <optimized out>
        pd = <optimized out>
        out = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {135443649660608, -4459628139538850994, -1176,
                0,<PHONE_NUMBER>37296,<PHONE_NUMBER>68224,<PHONE_NUMBER>785748302,<PHONE_NUMBER>290052430},
              mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0,
              cleanup = 0x0, canceltype = 0}}}
        not_first_call = <optimized out>
#9  0x00007b2fa5cf405c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
No locals.

After building for days, I can now determine, it is #316761 that broken wechat-uos. The last commit that could run on master is ecefb310fea47a3373349139c7c4fc50ec21c82e

Also CC @xddxdd


Pipelines data validator integration

Integrating the IPT and Data Validator can help publishers to improve data before publishing it into GBIF, the data validator provides a consistent API with the running data ingestion platform, such API provides the necessary services to validate Occurrence, Checklist, and Metadata only datasets.
Basic functionality

Once a dataset/resource contains the desired metadata and its data has been uploaded or mapped, the user desires to validate it before publishing it to GBIF.
The IPT generates a DwC-A in a staging location accessible as an external URL and through the Data Validator API requests to validate it.

This can also be accomplished by using the Validator API to upload a file.
The authentication method must respect the implemented procedures for the IPT.

The Data Validator starts the validation process, returns the validation key for the requested archive, which will be used to track its progress.
Upon successful validation, the IPT should allow the user to publish the resource into GBIF.

Additional considerations

The IPT must provide a way to track the validation progress of an individual resource.
Multiple validation requests for the same resource must be prevented to happen by allowing only one validation running at a time per resource. The Data Validator, already imposes a suggested maximum validation a single user can run in parallel.
Once validation has finished the IPT must delete all temporary files and elements created.
For the IPT shouldn't be necessary to store other information than the validation identifiers executed for each resource, a specific endpoint for IPT validation can also be considered to relieve the IPT of storing additional data.

Wow, thanks to @ckotwn, I just became aware of this incredibly useful feature. Cannot wait to see it in production.
Meanwhile, I added a step for the publisher in the documentation suggesting them to manually check their data using the IPT. Here's the commit: https://github.com/gbif/ipt/compare/master...spalp:ipt:patch-2 I hope it makes sense.


Singular params with Array[String] in body does not render correct JSON

I hit a bug when trying to use this param declaration:
params do
  requires :tags, type: Array[String], documentation: { in: 'body' }
end

Expecting this to create a schema and tag it on the request, it actually did a formData instead:
{
  "in": "formData",
  "name": "tags",
  "type": "array",
  "items": {
    "type": "string"
  },
  "required": true
}

I've been using this successfully everywhere else so this threw me off. I experimented and realized that the requires with Array[String] does not work if it's the only one. It immediately works when you add a non array/string param:
params do
  requires :tags, type: Array[String], documentation: { in: 'body' }
  requires :lol, documentation: { in: 'body' }
end

Results in:
{
  "name": "V1PostMortemsReportsReportIdTags",
  "in": "body",
  "required": true,
  "schema": {
    "$ref": "#/definitions/putV1PostMortemsReportsReportIdTags"
  }
}

And the schema:
{
  "type": "object",
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "lol": {
      "type": "string"
    }
  },
  "required": [
    "tags",
    "lol"
  ],
  "description": "Add tags to a report"
}

What's also peculiar is that if you add multiple Array[String] to params it maintains the same bug, I've only been able to get to work the moment you add a non-array param.

This is similar or at least related to https://github.com/ruby-grape/grape-swagger/issues/721.

We hit this again today, where is a good place to look in the code base and provide a fix @dblock ?

I am not sure, @LeFnord might know more.

will have a look on it …

More info about this here: https://github.com/ruby-grape/grape-swagger/issues/721#issuecomment-595958967

I find a PR about my problem, but I don't understand why it is.

created a sample project to check it out … see how_to_array_params it works as expected

@LeFnord I put a few pictures, maybe it will be easier to understand, I

@LeFnord I used your sample project, and put some pictures about swagger_ui render, you can see the actual effect.
Picture 1
Pitcture 2

ah, now I see the point …
it will be documented correct as array
"parameters": [
  {
    "in": "body",
    "name": "names",
    "required": true,
    "schema": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  }
],

but grape accept it only with given name … this way
{
  "names": [
    "a", "b"
  ]
}

🤔

ok, checked it … the documentation above is correct and it must be used for body as above, for x-www-form-urlencoded it must be done a similar way via &names[]=a&names[]=b, so it seems the behaviour is correct

ok, checked it … the documentation above is correct and it must be used for body as above, for x-www-form-urlencoded it must be done a similar way via &names[]=a&names[]=b, so it seems the behaviour is correct

You mean that the documentation is correct, and the grape needs to support this form?

I'm facing the same issue with version 1.3.1
optional :booking_ids, type: Array, desc: 'Booking ID of Location'

Generate
curl -X GET ...... -d 'booking_ids=123&booking_ids=456' 'domain/api/v1/locations'

And
optional :booking_ids, type: Array, desc: 'Booking ID of Location', documentation: { param_type: 'body' }

Generate
curl -X GET ...... -d '["81852"]' 'domain/api/v1/locations'

I guest both above are not correct, it should be something like below: (with the [])
curl -X GET ...... -d 'booking_ids[]=123&booking_ids[]=456' 'domain/api/v1/locations'

I'm facing the same issue with version 1.3.1
optional :booking_ids, type: Array, desc: 'Booking ID of Location'

Generate
curl -X GET ...... -d 'booking_ids=123&booking_ids=456' 'domain/api/v1/locations'

And
optional :booking_ids, type: Array, desc: 'Booking ID of Location', documentation: { param_type: 'body' }

Generate
curl -X GET ...... -d '["81852"]' 'domain/api/v1/locations'

I guest both above are not correct, it should be something like below: (with the [])
curl -X GET ...... -d 'booking_ids[]=123&booking_ids[]=456' 'domain/api/v1/locations'

The issue is with the hack added in #553 that screws up the parameter  doc generation.
so it generates swagger docs expecting params of an un-named array.  [1,2,3]
If I disable that code, then the docs are still generated incorrectly, as they are generated as an array of objects with an array.
e.g. swagger is expecting this [{booking_ids: [1,2,3]}]
vs. what we all want to happen
{booking_ids: [1,2,3]}

Right now my fix for this issue is to simply turn off this "auto magic" completely as I NEVER use it, and IMHO it should be opt-in.
module GrapeSwagger
  module DocMethods
    class MoveParams
      def self.should_correct_array?(param)
        false
      end

      def self.build_definition(name, _params)
        @definitions[name] = object_type

        name
      end
    end
  end
end


Address GetDepthInMainChain TODO in PosMinting.cs

This PR addresses the GetDepthInMainChain TODO in PosMinting.cs.

I have synced the networks and see that we have trx in the memppol.
In the future @quantumagi please try to also include a test that covers the change, so we can start to get more test coverage.


Whiteboards broken

Info:

OS: macOS 12.6.3

Logseq ver: 0.8.17

Plugin ver: 1.6.13

Theme name: None

[ ] ⚠ Do i have issue with DISABLED my custom.css?

Description:
Plugin is breaking Whiteboards. I can see the list of all boards but when click on any or newly created UI elements are missing and no content.
To Reproduce:
Activate the plugin with default settings.
Expected behavior:
Working Whiteboards. :)
Screenshots

Attach files
Add (via drag-n-drop) .zip with .md files (if it needs) to help with bugfixind

only on 0.8.17? 0.8.16 was ok?

i think it's same bug https://github.com/yoyurec/logseq-awesome-ui/issues/44

Unfortunately, I am not aware if it worked OK with previous versions of Logseq because I had not installed it previously.

fixed!


Failed to download Valheim server from Steam

I'm not sure if it's relevant, but I'm trying run this container in podman, and it is giving the following message:
valheim-updater ERROR - Failed to download Valheim server from Steam - retrying later - check your networking and volume access permissions

I'm not all that familiar with podman or docker, so I apologize if I messed something up. Also, ENV variables from PATH to HOME seem to have been automatically added by podman.

I was able to resolve my issue. It seems to have been a couple of different issues. First, I had the volumes pointing to directories that were owned by root, which caused some issues. Second, when running through cockpit-podman, podman seemed to be running it as non-root, which doesn't allow it to connect to outside networks. Third, it's trying to run as what cockpit-podman calls "System" which seems to be breaking things.
My solution was to create the correct directory structure, then if I just run the command "podman run" with all of my options and ENV variables, it works correctly.

@DaleCavender glad you were able to figure it out. Consider contributing an update to the README so others can learn from your experience.


Add support for insert list objects and returns list ID's

Actually I get this error when try to get a id's list after insert or update a object's list:
Error running FloorGenerator
Update methods have to return a Future of either void or int but not a list.
Future<List> updateList(List entities);
│                     ^^^^^^^^^^
My code:
@insert
Future<List> insertList(List entities);
I found this related issue:  #44 , but I don't know how it work's.

I updated my version and now works fine.


NaN handling in the calculators

Prerequisites

[X] I am an Open Source Contributor
[X] I checked to make sure that this issue has not already been filed

Description
While going through all the applications for calculating age. I found out that there is no NaN handling. I want to work on this issue where I will use regex or input validations that will only allow numeric values.
Screenshots

Code of Conduct

[X] I follow Contributing Guidelines of this project.

I want to work on this issue and add a NaN handling section in your code.Please assign this to me under SWOC'24

Assigning you, Go ahead!!  @Sanchitbajaj02

I would like to, but currently I am a Project Admin as well. So it would be better if you assign this to a contributor :blush:

Sure, no issues @Sanchitbajaj02

Done


Impose a maximum value constraint on output_index?

The input[i].fulfills.output_index is the index of the output being fulfilled by input i. The value of output_index should be a small integer such as 0, 1, 2, 3, ...
Currently, the JSON Schema file for transactions (bigchaindb/common/schema/transaction_v1.0.yaml) includes the following snippets:
      fulfills:
        anyOf:
        - type: 'object'
          additionalProperties: false
          required:
          - output_index
          - transaction_id
          properties:
            output_index:
              "$ref": "#/definitions/offset"

and
definitions:
  offset:
    type: integer
    minimum: 0

In other words, transaction schema validation already ensures that output_index is an integer greater than or equal to zero, but it puts no upper bound (maximum allowed value) on it.
That's problematic because big integers can cause problems (which is why we changed amount from an integer to a string in pull request #1286 ).
Proposal
Impose a maximum value of 511 on output_index (in the JSON Schema file). Maybe higher but remember, it's meant to refer to the index of a transaction output. How many outputs could a transaction have, anyway?

Note: This would be a change to the transaction schema, so it would have to be made in a future version of the transaction model (i.e. 2.0 or later), and in bigchaindb/common/schema/transaction_v2.0.yaml or later.

I realized there are other checks we should do on the output_index values as part of transaction validation:

max(output_index) == len(outputs) - 1
There must be no duplicate values of output_index in outputs. (There are many ways to check this.)

Along with the constraints that the minimum value is 0, and the values are integers, all four constraints together ensure that the set of output_index values is {0, 1, 2, ..., N-1}, where N = len(outputs).


Questions about batch setting and out of memory.

I have a question: When I train my own dataset with joint_pose_nerf_training and train_sub = 6, it works fine. However when I train the network with nerf_training_w_gt_poses and train_sun=6, it shows out of memory.
So:

I wonder what differences about dataloaders between them two and what I can do to solve it.
I also wonder how I can set the batches in your networks. Thank you

Hi,
That is a bit strange, the dataloaders should be the same. I will check what could be different.
As for the batches, you need to change config.rand_rays in the configs and reduce that number.

您好，来信已收到，感谢您的邮件。

您好，来信已收到，感谢您的邮件。


Date Picker does not open anymore

The datepicker has worked fine all the time but suddenly stopped working. I don't know what I have changed, if I click in the date field, onOpenModal does get triggered but no datepicker is shown. no error is thrown either. How to debug now?
      <View style={{ paddingBottom: 25 }}>
        {locals.label ? <Text style={FormStyles.controlLabel.normal}>{locals.label}</Text> : null}
        <DatePicker
          style={{ flex: 1, minWidth: width - 30 }}
          date={locals.value}
          mode="datetime"
          placeholder="select date"
          format="YYYY-MM-DD HH:mm"
          minDate={moment().format('YYYY-MM-DD HH:mm')}
          confirmBtnText="Confirm"
          onOpenModal={() => { console.log('opened'); }}
          cancelBtnText="Cancel"
          customStyles={{
            dateIcon: {
              position: 'absolute',
              left: 0,
              top: 4,
              marginLeft: 0,
            },
            dateInput: {
              marginLeft: 36,
              flex: 1,
              borderRadius: 3,
            },
            dateText: {
              color: '#fff',
            },
            placeholderText: {
              color: '#fff',
            },
          }}
          onDateChange={(date) => {
            console.log(date);
            // this.props.onChangeDate(date);
          }}
        />
      </View>

I struggled a while with this too. In my case (react-native@0.42), the problem was related to this issue: https://github.com/facebook/react-native/issues/12515.
What worked for me: disabling remote debug. It seems to be resolved in in 0.42.2, so upgrading might help as well.

@rbaron You are right, it works when I disable the remote debugger. Thank you SO much. This caused a big headache!


Update Redis administration $somaxconn value

First of all, thank you for the awesome module you guys provide. Our company is doing the transition from our own in-house module to puppet-redis. I found today something that I figured a few months ago actually while reviewing our version and is related to the net.core.somaxconn kernel parameter.
if you include redis::administration, one of the changes that we introduce to the kernel are setting /proc/sys/net/core/sommax to 65535. regardless of the opportunity to alter this value, it doesn't affect much since Redis hardcodes this on the source code to 511. You get a warning in the log file and then falls back to your limit in case is lower than that:
# tail /var/log/redis/redis.log
30491:M 21 Aug 00:31:14.587 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

# checking listen socket for Redis
root@ip-172-18-13-185:~# ss -lin | grep 6379
tcp    LISTEN     0      128       *:6379                  *:*

Depending of your Distro, the default value most of the times is 128 (at least for Ubuntu AMI's in AWS). We tuned our kernels based on the stack and some performance analysis, however for a base line we took that number from Brendan's Gregg suggestion.

I'm not sure how to proceed here. It sounds like redis::administration is already doing what it's supposed to.

Due to its age and that it needs feedback, I'm going to close this issue. If there's still a problem, please reopen or open a new issue/PR.


Concatenate error when trying to train a two input one output network

Hi,
I'm trying to train a 2 input one output model using the Keras API. The model seems to be right and all but at the end when I try to train it shows an error when it tries to concatenate the two outputs of the branches. It says that a two-dimensional array is expected and it gets a (x,y,z) input.
Being 'x' my batch size and 'y' and 'z' the size of the image. I have already tried using a batch size of 1 and the same error happens.毕业真实版本=|彼得学院毕业证书-|剑桥大学真实原件文凭证书=英国文凭办理‖国外文凭办理→国外学历学位认证
I have also tried using add instead of concatenating but the same error shows.

Not sur ehow


Cannot read property 'matched' of undefined

When routes are an empty array, and you create the routes on the fly for example on the beforeCreate method like this :
beforeCreate () {
    let routes = []
    this.$modules = Object.assign(modules, this.$options.modules)

    for (var [name, module] of Object.entries(modules)) {
      if (module['routes']) routes.push(module.routes.reduce(r => r))
      if (module['store'] && !this.$store.state[name]) this.$store.registerModule(name, module.store)
    }

    // Add routes for all the modules
    this.$router.addRoutes(routes)
  }

You get an error:
Cannot read property 'matched' of undefined

in what way is that related to vue-devtools? IT sounds like a vue-router issue.
Can you share a repo with a working reproduction of that behaviour?

Actually the application is working like expected, but the vue-devtools are broken when you try this approach.
Tnx

Hey Boudy, can you boil down the error and provide a repro using this template? I created a test with an empty routes array but couldn't reproduce the error
Thanks for the PR btw!


shape mismatch

When I run ./scripts/extract_data.py, I got the error:
IndexError: shape mismatch: indexing arrays could not be broadcast together with shapes (201306,3) (201306,)

请问你解决这个问题了吗

Have you solved this problem?


TORCH_USE_CUDA_DSA

Training progress:   0%|          | 80/30000 [00:02<13:19, 37.41it/s, Loss=1.0910213, Depth Loss=0.2243882]
Training progress:   0%|          | 90/30000 [00:02<13:14, 37.65it/s, Loss=1.0910213, Depth Loss=0.2243882]Traceback (most recent call last):
File "E:\GSproject\gs\gaussian-splatting\train.py", line 755, in
training(lp.extract(args), op.extract(args), pp.extract(args), args.test_iterations, args.save_iterations,
File "E:\GSproject\gs\gaussian-splatting\train.py", line 563, in training
loss.backward()
File "E:\conda\envs\3dgs\lib\site-packages\torch_tensor.py", line 492, in backward
torch.autograd.backward(
File "E:\conda\envs\3dgs\lib\site-packages\torch\autograd_init_.py", line 251, in backward
Variable.execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
File "E:\conda\envs\3dgs\lib\site-packages\torch\autograd\function.py", line 288, in apply
return user_fn(self, *args)
File "E:\conda\envs\3dgs\lib\site-packages\diff_gaussian_rasterization_init.py", line 155, in backward
grad_means2D, grad_colors_precomp, grad_opacities, grad_means3D, grad_cov3Ds_precomp, grad_dc, grad_sh, grad_scales, grad_rotations = _C.rasterize_gaussians_backward(*args)
RuntimeError: CUDA error: invalid configuration argument
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Hi.
I'm not sure whether this issue is due to the fused-ssim implementation or this is an error due to the gaussian splatting rasterization backend that you're using. From your log, I see that the training happened for 90 iterations already. And since image size remains same during training, SSIM most likely should not cause an error in later iterations if it was successful in the first few ones.
Please can you elaborate more.

The current issue is that when I use：
pip uninstall diff-gaussian-rasterization -y
cd submodules/diff-gaussian-rasterization
rm -r build
git checkout 3dgs_accel
pip install .

I have segmented the large scene and also segmented the laser point cloud. For example, if 10 blocks are divided, about 5 of them can correctly complete 30000 rounds. But there were 5 times when an error was reported like this. An error occurred after several iterations. My computer is Windows 11

https://github.com/graphdeco-inria/gaussian-splatting/issues/1080

I think your rasterization speed is excellent, but there are bugs. My personal level is relatively low, and I hope the experts can fix it as soon as possible！

https://github.com/rahul-goel/fused-ssim/issues/6
I guess this might solve my problem? I will test it first and provide feedback once I have the results.

After modification, uninstalling and reinstalling still produces an error message


Fix root node replace in post processor

When trying to replace a root node in a post processor, an IllegalStateException is thrown.
The given node parent (which is the document for a root node) is not in the myClassifyingNodeTracker.
I'm not sure about the consequences of this change, so comments are welcome!

@CGNonofr, thank you for fixing it. The fix looks correct and I will merge it and do some testing.


Please help me

when I run this command:   $ python train_TextGNN.py --dataset mr --learning_rate 0.0001 --batch_size 4096 --num_epochs 150 --num_GNN_layers 2 --hidden_size 384 --model GatedGT,
an error occurred:
Traceback (most recent call last):
File "train_TextGNN.py", line 129, in
train_loss = train()
File "train_TextGNN.py", line 99, in train
torch.from_numpy(train_mask[idx]).float().to(device))
File "/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in call
result = self.forward(*input, **kwargs)
File "/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 155, in forward
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 165, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 85, in parallel_apply
output.reraise()
File "/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/torch/_utils.py", line 395, in reraise
raise self.exc_type(msg)
AttributeError: Caught AttributeError in replica 0 on device 0.
Original Traceback (most recent call last):
File "/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 60, in _worker
output = module(*input, **kwargs)
File "/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in call
result = self.forward(*input, **kwargs)
File "/home/zhang/compatibility_analysis/Graph-Transformer/TextGNN/model_MPGNN.py", line 62, in forward
graph_embeddings = torch.sum(x, 1) * torch.amax(x, 1)
AttributeError: module 'torch' has no attribute 'amax'
My torch version==1.5.0.
Can you help me solved this problem?

I used PyTorch >= 1.5.0 when I reimplemented UGformer for graph classification. But after that, I used PyTorch >= 1.7.0 when I implemented UGformer for text classification. You can use PyTorch >= 1.7.0 to solve the problem.

Thank you for your reply, and I have run it successfully!
But now I have a new question. When I run this command:python train_UGformerV1_UnSup.py --dataset PTC --batch_size 2 --degree_as_tag --ff_hidden_size 1024 --num_neighbors 4 --num_sampled 512 --num_epochs 50 --num_timesteps 2 --learning_rate 0.0001 --model_name PTC_bs2_dro05_1024_4_idx0_2_2
an error occurred:
ImportError: cannot import name 'LogUniformSampler' from 'log_uniform' (unknown location)
I found your previously reply in issues,
I run make in log_uniform directory,ang got information like this:
rm -rf build
rm -rf pycache
rm -rf log_uniform.cpp
rm -rf log_uniform.*.so
python3 setup.py build_ext --inplace
Compiling log_uniform.pyx because it changed.
[1/1] Cythonizing log_uniform.pyx
/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 'language_level' not set, using 2 for now (Py2). This will change in a later release! File: /home/zhang/compatibility_analysis/Graph-Transformer/UGformerV1_PyTorch/log_uniform/log_uniform.pyx
tree = Parsing.p_module(s, pxd, full_module_name)
running build_ext
building 'log_uniform' extension
creating build
creating build/temp.linux-x86_64-3.7
gcc -pthread -B /home/zhang/anaconda3/envs/Gra/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/numpy/core/include -I/home/zhang/anaconda3/envs/Gra/include/python3.7m -c Log_Uniform_Sampler.cpp -o build/temp.linux-x86_64-3.7/Log_Uniform_Sampler.o -std=c++11
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
gcc -pthread -B /home/zhang/anaconda3/envs/Gra/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/numpy/core/include -I/home/zhang/anaconda3/envs/Gra/include/python3.7m -c log_uniform.cpp -o build/temp.linux-x86_64-3.7/log_uniform.o -std=c++11
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from /home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1969:0,
from /home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
from log_uniform.cpp:807:
/home/zhang/anaconda3/envs/Gra/lib/python3.7/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
#warning "Using deprecated NumPy API, disable it with "
^~~~~~~
creating build/lib.linux-x86_64-3.7
g++ -pthread -B /home/zhang/anaconda3/envs/Gra/compiler_compat -Wl,--sysroot=/ -pthread -shared -B /home/zhang/anaconda3/envs/Gra/compiler_compat -L/home/zhang/anaconda3/envs/Gra/lib -Wl,-rpath=/home/zhang/anaconda3/envs/Gra/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.7/Log_Uniform_Sampler.o build/temp.linux-x86_64-3.7/log_uniform.o -o build/lib.linux-x86_64-3.7/log_uniform.cpython-37m-x86_64-linux-gnu.so
copying build/lib.linux-x86_64-3.7/log_uniform.cpython-37m-x86_64-linux-gnu.so ->
I don't know whether it make successfully.
And then I run this command:export PYTHONPATH="${PYTHONPATH}:~/compatibility_analysis/Graph-Transformer/UGformerV1_PyTorch/log_uniform"
Finally, it's failed too.
So,can you tell me which step I did wrong?

You should use the absolute path for PYTHONPATH and then you can verify whether compiling log_uniform...so is successful by running UGformerV1_PyTorch/log_uniform/test.py

Thank you for your reply,I have solved that problem.
But now, an new error happend:
notes.html#deprecations
eps=np.finfo(np.float).eps, copy_X=True, positive=False):
usage: UGformer [-h] [--run_folder RUN_FOLDER] [--dataset DATASET]
[--learning_rate LEARNING_RATE] [--batch_size BATCH_SIZE]
[--num_epochs NUM_EPOCHS] [--model_name MODEL_NAME]
[--sampled_num SAMPLED_NUM] [--dropout DROPOUT]
[--num_hidden_layers NUM_HIDDEN_LAYERS]
[--num_timesteps NUM_TIMESTEPS]
[--ff_hidden_size FF_HIDDEN_SIZE]
[--num_neighbors NUM_NEIGHBORS] [--fold_idx FOLD_IDX]
UGformer: error: unrecognized arguments: --degree_as_tag --num_sampled 512
I modify "--num_sampled" to "--sampled_num",
but I don't konw how to modify "--degree_as_tag"
Can you tell me  how to do this?

Thanks for pointing out this. The command you used is for TF version, not for PyTorch version. Please re-consider the updated README.

Thanks for your help！🤝


Choose bin size automatically

Choose bin size based on coverage. Few considerations:

Ratio of mean / std of coverage
Mean ploidy of the sample (Generally speaking a bin-size that on average has > 30 reads/fragments should suffice if the average ploidy is 2).

A bin size is selected based on the first chromosome information. Ratio of mean / std of coverage should be > 4 as a heuristic.


row template - conditional format

Wondering if there is a way to conditionally format the row template based off column value.

show/hide or enable/disable  button based off Boolean column value

Yes. You can use our column renderer to do that. You can see examples at http://gijgo.com/grid/configuration/column.renderer
You can also review http://gijgo.com/grid/events/rowDataBound


Unable to reference remote files

I'm not quite understanding the limitation on only referencing local files. As far as I understand it, this is only referenced from JavaScript (running locally) and (AFAIK?) this only runs against trusted input, assuming you trust your own markdown. Being able to reference a URL to a live hosted OpenAPI spec seems like a desirable feature so you can point it at a live server, but perhaps I'm missing something?

At first I thought about external hosting servers, which don't necessarily trust the markdown, in which case an external user adding !!swagger /etc/passwd!! would cause a copy of the file. That's why I blocked non-local paths.
Referencing a remote JSON however without it copying any file is totally safe and effects only the JS running on the end user's machine.
Thanks for your contribution :-)


Move away from env vars

To make sure that we don't forget. I think the IASQL_ENV var needs to be declared in the Dockerfile, too.


Add docs target to makefile

Similar to the other ones, we have the docs session in nox
https://github.com/pythonecuador/lira/blob/master/Makefile

Closed by https://github.com/pythonecuador/lira/pull/46


Change Series.divide/2 return float series and add quotient/2 and remainder/2 to Series

This is because we want to make it similar to the behaviour of Elixir
and Nx.
Related to #333

I'm still working on this. I'm going to add quotient and reminder in this PR.

Looking good!

@cigrainger please take a look again. I added the two new functions :)

@philss don't merge this yet, let's do a new v0.3.1 release with some fixes and then we merge it.


GH-1459: Pollable Consumer and Requeue

Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/1459
Requires https://github.com/spring-cloud/spring-cloud-stream/pull/1467

LGTM - merged.


commons-compress: 1.25.0 → 1.26.0

Direct dependency of plexus-archiver via coursier
Already updated upstream pending a release: https://github.com/codehaus-plexus/plexus-archiver/commit/6077fd7385965710ed8dd5918acf6c2079497e9d
https://mvnrepository.com/artifact/org.apache.commons/commons-compress/1.25.0 https://mvnrepository.com/artifact/org.apache.commons/commons-compress/1.26.0
Addresses:

CVE-2024-25710

Thank you for bringing this CVE to our attention. Since this is in a transitive dependency, which we already have a different control mechanism for, I took the opportunity to implement this differently. See PR https://github.com/com-lihaoyi/mill/pull/3049 .


Windows static build -  post-build validation invalid crt linkage

Hi,
I'm creating the port for popsift (#10979), a library for feature detection in computer vision.
Normally the library is cross-platform so as now there have been no issues on bulding/execution on the 3 platforms outside vcpkg.
The library only depends on CUDA.
I have a bit of a issue when building the static version under windows on vcpkg as I always receive this error at the post-build validation (building has no issue)
Expected Debug,Static crt linkage, but the following libs had invalid crt linkage:

    C:/alicevision/vcpkg/packages/popsift_x64-windows-static/debug/lib/popsiftd.lib: Release,Static

To inspect the lib files, use:
    dumpbin.exe /directives mylibfile.lib

So if I do the dumpbin I get something like:
File Type: LIBRARY

   Linker Directives
   -----------------
   /FAILIFMISMATCH:_MSC_VER=1900
   /FAILIFMISMATCH:_ITERATOR_DEBUG_LEVEL=2
   /FAILIFMISMATCH:RuntimeLibrary=MTd_StaticDebug
   /DEFAULTLIB:libcpmtd
   /FAILIFMISMATCH:_CRT_STDIO_ISO_WIDE_SPECIFIERS=0
   /FAILIFMISMATCH:_PPLTASK_ASYNC_LOGGING=1
   /FAILIFMISMATCH:ppltask_saved_frame_numbers=PPL_TASK_SAVE_FRAME_COUNT
   /include:?id@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@2V0locale@2@A
   /include:?id@?$numpunct@D@std@@2V0locale@2@A
   /DEFAULTLIB:LIBCMTD
   /DEFAULTLIB:OLDNAMES

   Linker Directives
   -----------------
   /DEFAULTLIB:LIBCMT                                       # <-- this one makes the post-build fail
   /DEFAULTLIB:OLDNAMES

   Linker Directives
   -----------------
   /FAILIFMISMATCH:_MSC_VER=1900
   /FAILIFMISMATCH:_ITERATOR_DEBUG_LEVEL=2
   /FAILIFMISMATCH:RuntimeLibrary=MTd_StaticDebug
   /DEFAULTLIB:libcpmtd
   /FAILIFMISMATCH:_CRT_STDIO_ISO_WIDE_SPECIFIERS=0
   /include:?id@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@2V0locale@2@A
   /include:?id@?$numpunct@D@std@@2V0locale@2@A
   /DEFAULTLIB:LIBCMTD
   /DEFAULTLIB:OLDNAMES

   Linker Directives
   -----------------
   /FAILIFMISMATCH:_MSC_VER=1900
   /FAILIFMISMATCH:_ITERATOR_DEBUG_LEVEL=2
   /FAILIFMISMATCH:RuntimeLibrary=MTd_StaticDebug
   /DEFAULTLIB:libcpmtd
   /FAILIFMISMATCH:_CRT_STDIO_ISO_WIDE_SPECIFIERS=0
   /include:?id@?$num_put@DV?$ostreambuf_iterator@DU?$char_traits@D@std@@@std@@@std@@2V0locale@2@A
   /include:?id@?$numpunct@D@std@@2V0locale@2@A
   /DEFAULTLIB:LIBCMTD
   /DEFAULTLIB:OLDNAMES
...

All the remaining  /DEFAULTLIB correctly point to LIBCMTD, only the second one (see above) points to the non debug version of the lib LIBCMT, which is making the test fail.
I've tried several things to fix this without success:

I made sure that all flags /MT and /MTd were correctly set. In the ninja build file I have

  LANGUAGE_COMPILE_FLAGS = /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP  /D_DEBUG /MTd /Z7 /Ob0 /Od /RTC1
  LINK_FLAGS = /machine:x64  /VERBOSE:LIB

Compared to other ports that pass the post-build there is basically no difference in terms of flags

I tried to add /NODEFAULTLIB:libcmt.lib but I got the same result.

The weird thing is that if I create the visual studio solution through cmake and build in VS I got a lib that is correct, ie no libcmt.lib in the dumpbin. And again there is no difference in terms of flags.
So you can understand why this thing is driving me crazy.
I'm not an expert in windows build, so it is possible that I'm missing something.
Any help would be really appreciated!

Ok I might have found the problem.
Since nvcc is involved, there is a intermediate linking step in which all the cuda objs are collected into a popsift_intermediate_link.obj.
While all the objs from the cuda files had the proper flags and the correct libcmtd, the intermediate file had the libcmt, which in the end made the post build check fail.
Now, the intermediate linking step is run through a batch file in which nvcc is called without the proper flag.
So in the end the problem is that the flags were not properly propagate in this intermediate step.
To overcome this I added in our code
if(MSVC)
  if(BUILD_SHARED_LIBS)
    if(CMAKE_BUILD_TYPE STREQUAL "Debug")
      set(PopSift_MVSC_LINKER "/MDd")
    else()
      set(PopSift_MVSC_LINKER "/MD")
    endif()
  else()
    if(CMAKE_BUILD_TYPE STREQUAL "Debug")
      set(PopSift_MVSC_LINKER "/MTd")
    else()
      set(PopSift_MVSC_LINKER "/MT")
    endif()
  endif()
  list(APPEND CUDA_NVCC_FLAGS   -Xcompiler ${PopSift_MVSC_LINKER})
endif()

which is ugly and probably has the side effect of duplicating the flag in the same command line.
But at least it works.
I cannot understand whose fault it is, there are too many layers, CMake, vcpkg, ninja... I don't know which one does not correctly propagate the flag.
Probably it is ninja, because I tried to generate the ninja project from cmake (outside vcpkg) and even there is a .bat file for the intermediate step and it has not the flags.

vcpkg will set different C_FLAGS / CXX_FLAGS according to the triplet and pass it to cmake. If the value is changed in CMakeLists.txt or *.cmake in the source, MT / MTD / MD / MDD may be overwritten. This can be seen in buildtrees/$PORT/install*.log.
So I think this issue should be fixed by adding patches, not vcpkg.

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

Hi,
I faced this issued also on a libraries using both C++ and CUDA and I stumbled on this issue from CMake : https://gitlab.kitware.com/cmake/cmake/-/merge_requests/3485
According to this post the issue was due to the way CMake treats MSVC runtime by default (going for /MD or /MDd).
Thus as vcpkg seems to update C_FLAGS and CXX_FLAGS to /MT in case x64-windows-static is used, it seems to leaves CUDA_FLAGS to default (/MD) which results in the aforementioned issued (invalid crt linkage).
Hacking with the flags as proposed by @simogasp did not work for me, so the solution I found was to use the CMake policy CMP0091 and to populate the variable CMAKE_MSVC_RUNTIME_LIBRARY before creating the targets.
For reference, here is the code snippet I used
cmake_minimum_required(VERSION 3.15)

# Activate usage of CMAKE_MSVC_RUNTIME_LIBRARY
cmake_policy(SET CMP0091 NEW)

project(whatever)

# Make sure MSVC runtime is consistent accross
# all languages (i.e. CXX, CUDA, etc, ...)
# cfr : https://gitlab.kitware.com/cmake/cmake/-/issues/19428
if(NOT DEFINED CMAKE_MSVC_RUNTIME_LIBRARY)
  if(BUILD_SHARED_LIBS)
    set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>DLL")
  else()
    set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreaded$<$<CONFIG:Debug>:Debug>")
  endif()
endif()

Please note that the CRT linkage of all ports in vcpkg should be configured according to the configuration of the triplet, and should not be mandatory.


Make this repository public

Not something we need to do right away, but I'd really like to see if we can make this repository public as a good example of setting up eoAPI, having ingestion scripts, etc.
@zacharyDez @geohacker @sunu do you see any issues with making this public?

This repo is now public


Virtual currency updates

Add virtual currency to money transfer section
Additions

Add virtual currency to money transfer section title & tooltip
Add option for a tooltip that differs from the section title

Testing

Check out branch
Navigate to http://localhost:8000/complaintdatabase/ and make sure the complaint section renders correctly & virtual currency has been added to the money transfer section title/tooltip

Review

@amymok
@cfarm
@higs4281

Screenshots

Todos

FormatNarrativesTest will need to be updated after @higs4281's changes in #7 are merged

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

…hat are different from section title

Screenshot matches stakeholder request! 👍
And thanks for catching the need to change the link text after the narrative as well.

👍

I'll resolve any test issues once this and PR7 are merged.

👍


Regenerate *.repr files using updated proper_repr for numpy ndarray.

Description of the issue
https://github.com/quantumlib/Cirq/pull/5991 updates proper_repr for numpy types. As a result, all repr files should be regenerated using the new proper_repr methods.  This issue is to unblock the PR and track the changes to .repr files independently.
See https://github.com/quantumlib/Cirq/pull/5991#discussion_r1156124945 for more details.

@tanujkhattar I'd like to take up this issue if no one is assigned to it.

@ozamanan For planning purposes, could you let us know the status of this item?


 Please consider more portable way
of path management. (e.g., Linux uses /usr/ as default top path of 3rd
party applications. FreeBSD uses /usr/local/ on that way. Other OSes
use other path as their default apps top path).

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 20 Sep 2010 at 3:10

Original comment by<EMAIL_ADDRESS>on 1 Apr 2012 at 2:16

Added labels: OpSys-FreeBSD


Heartbeat returns status up for invalid browser monitors

I added a monitor with an invalid script

Even though there is no script to run, it returns a summary document with status up and it also has duration field
here is the summary document
{
  "took": 12,
  "timed_out": false,
  "_shards": {
    "total": 3,
    "successful": 3,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 1,
      "relation": "eq"
    },
    "max_score": null,
    "hits": [
      {
        "_index": ".ds-synthetics-browser-default-2022.06.02-000001",
        "_id": "fKwSJYEBAC_vboWN8DfH",
        "_score": null,
        "_source": {
          "summary": {
            "up": 1,
            "down": 0
          },
          "agent": {
            "name": "cron-8a08fd4dc6451cea-27569740-pkqqf",
            "id": "28b5ffc5-359a-43f0-bfc8-fdbed6c6d722",
            "type": "heartbeat",
            "ephemeral_id": "0be94d23-8736-4b39-93ba-1716c0078703",
            "version": "8.3.0"
          },
          "synthetics": {
            "journey": {
              "name": "inline",
              "id": "inline",
              "tags": null
            },
            "type": "heartbeat/summary"
          },
          "monitor": {
            "duration": {
              "us": 1507
            },
            "name": "Test Monitor",
            "project": {
              "name": "",
              "id": ""
            },
            "id": "16a53c40-e288-11ec-bce8-11636fc91f48",
            "timespan": {
              "lt": "2022-06-02T15:50:06.215Z",
              "gte": "2022-06-02T15:40:06.215Z"
            },
            "check_group": "46c20de9-e28a-11ec-87d7-9a25d2fbdf87",
            "type": "browser",
            "status": "up"
          },
          "url": {},
          "observer": {
            "geo": {
              "continent_name": "North America",
              "city_name": "Iowa",
              "country_iso_code": "US",
              "name": "North America - US Central",
              "location": "41.8780, 93.0977"
            },
            "hostname": "cron-8a08fd4dc6451cea-27569740-pkqqf",
            "ip": [
              "<IP_ADDRESS>"
            ],
            "mac": [
              "9a:25:d2:fb:df:87"
            ]
          },
          "@timestamp": "2022-06-02T15:40:06.213Z",
          "ecs": {
            "version": "8.0.0"
          },
          "config_id": "16a53c40-e288-11ec-bce8-11636fc91f48",
          "data_stream": {
            "namespace": "default",
            "type": "synthetics",
            "dataset": "browser"
          },
          "event": {
            "agent_id_status": "auth_metadata_missing",
            "ingested": "2022-06-02T15:40:07Z",
            "type": "heartbeat/summary",
            "dataset": "browser"
          }
        },
        "sort": [
<PHONE_NUMBER>213
        ]
      }
    ]
  }
}

We've moved this to the backlog since it's an unusual thing for a regular user to do. Real users would write more complex syntax to try to actually test something. We should fix this, but it's not a high priority.


Add evidence form creates duplicate variant entries by forcing uppercase in variant name

For example:
If I try to add a new piece of evidence for: P25L (c.74C>T)
https://civic.genome.wustl.edu/#/events/genes/58/summary/variants/850/summary#variant
When I am adding evidence it allows me to specify the variant name "P25L (C.74C>T)".  This differs only by case. If I try to change the "C." to "c." it correctly suggests that variant name I want.  But when I select it the form is still populated with "C."
So when I submit this evidence it creates a new variant that differs by case only.
I'm not sure if we should force uppercase only on this field.  If we do, I guess we should force it everywhere.  Since we are able to edit variant names and make things lowercase, it creates issues like this...

Others can chime in if they feel strongly, but I vote for dropping the uppercase requirement for variant name in the add evidence form.
As curators we can encourage conventions on this.  In addition to this issue here, there are quite a few variant names where there is a strong convention with regard to use of case that we are not able to follow.

This is a simple change in the UI, the form field CSS class just does a text-transform to uppercase on all values. There's also an uppercase transform for displaying gene and variant names in the entity tabs control. I don't recall if we discussed at all or if it was just a design decision b/c the all-caps help to emphasize the relative importance of these labels in the UI.

The client Add Evidence form now allows variant names w/ lowercase letters. However, it appears that the server also enforces uppercase variant names after submission. I'll create a server issue to allow lowercase names on submit.


Update version 2.0.0 -> 2.1.0

The new version introduces new APIs thus requiring a minor version change.

@zhenlan as discussed I changed the version from 2.1.0 to 2.1.0-preview. Will merge since already approved.


CAMEL-17713: camel-aws2-s3 - Add support for S3 custom metadata in file uploads

Add support for providing custom metadata to files when uploading.
Makes use of the CamelAwsS3Metadata -header that is also used with the consumer endpoint.
As there is no specific user metadata field in the request model, this just adds all metadata from the CamelAwsS3Metadata -header into the metadata map.

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/main/CONTRIBUTING.md

Thanks a lot for taking time to fix this.

No problem! It was simpler to implement than I had initially thought. Thanks @oscerd for looking at this so quickly!

Thanks for the PR. I backported on camel-3.14.x, camel-3.11.x and merge on main.


Black screen for HTML5 video player in Android WebView

Description

Created new project

react-native init webview_example

Replaced text nodes with:

        <WebView
          javaScriptEnabled={true}
          style={{flex: 1}}
          source={{uri: `https://www.youtube.com/embed/IPV3rQtctkM`}}
        />

Run.

Video does not show (only black screen) but audio does play fine

Reproduction
Full source code is https://github.com/mehcode/rn-scratchpad/blob/master/index.android.js
Solution
I have no idea. I've been poking it for awhile.
Additional Information

React Native version: 0.40.0
Platform: Android v7
Operating System: Linux

Some more information. That example works 100% in Android <= 6. The bug seems to only exist in Android 7+. There must be a difference to WebView usage that we're not handling.

Another update. I've reduced this bug down to just raw android and have the same behavior.
https://github.com/mehcode/scratchpad

@mehcode  I have the exact same problem. The embedded video only has audio. Do you have any solution now?

I just gave up and use react-native-video

@mehcode
I'm on the verge of giving up the idea of embedding youtube video. How do you use react-native-video with online youtube url? Do you download the youtube clip first then play the mp4/flv with react-native-video?

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/black-screen-for-html5-video-player-in-android-webview

Did the original problem occur in the emulator and on actual device as well?


9.2 Release-Build

9.2 Release-Build

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: vishwanathan-m1:x: amitaG-HCLYou have signed the CLA already but the status is still pending? Let us recheck it.


Use FITS format

Julie to provide FITS files (replacing current jpg)

Sent email in regards to the links for the files.  Too large for me to upload to the gitlab data storage.  I will add more information to the wiki section in regards to this 2000 radio subject sample.

Description on the wiki section.

Resolved in #12.

In general, please try to make it easy for me to check by writing a clear comment about which notebook I need to look at. README should also have bullet points about which notebook to run for any particular function.


Remove border radius for document toggle button

From:

to:

Happens because new update to Chrome sets border radius to buttons by default on Mac

Can reproduce and have tested @einarlove pr that it works 👍

@einarlove @kevinsimper good catch guys, thanks for the help!


Add yup

General
https://yup.is — Real-time News with zero tracking/cookies

Hi @marban, thanks for your interest in this project.
Maybe I should state it clearly, but the search engines/services listed here are not just products with security or privacy in mind, but they are tools that an hacker effectively could use while performing security tests and other cybersec related activities.
So, I don't think the product you're suggesting fits well in the list, sorry I hope you can understand.
I appreciate so much this type of contribution, if you want you can submit all the issue/pull request you want :)
Have a nice day!


Stream Error Result: Failed

After the last update, I get this error after pressing the Start Stream button:
Greenlight version: 2.0.1

The problem was related to my modem. The problem was solved by restarting the modem and XBOX.


ansi escape codes not being omitted in vim shell

the ansi escape characters are not omitted, while other programs with color output works fine?

Currently Cargo doesn't do detection to see whether the shell supports colors, it simply checks $TERM != "dumb" and whether the output is a tty, and if both of those are true it emits colors.
Could vim be configured to set TERM=dumb if it doesn't support ansi codes?

+1

At this point, we check

CLICOLOR, NO_COLOR, CLICOLOR_FORCE
TERM=dumb
Whether stdout is TTY

Note: this is using anstyle-query and matches termcolors behavior with the last two items which is what ripgrep uses
Looking at another crate, supports-color, instead of assuming any terminal supports color if it isn't TERM=dumb, it checks a specific list of term values / prefixes.  As t his whole area is a hodgepodge, its hard to tell what is the most appropriate route to take.

Hmm, I just did !echo $TERM and I got back the result for my own terminal which means we don't have anything to go off of.  This was with vim 8.2.213.
Is there anything we can even do for this?  Are there examples of other programs that work better with vim that we could learn from?
btw we also have #11211 for changing TERM detection


Not an issues | Registrator Updated / Fork

Biggest changes

Removed module "github.com/fsouza/go-dockerclient" and using Official Docker SDK "github.com/docker/docker" !
Selected network by name or subnetwork !
Update Alpine to recent build !
Remove all locked dependecies (must be compatible with more recent tools. Not tested for all). Using go.mod.
Split packages to real Go modules.

Source
https://gitlab.com/dkr-registrator/registrator
Docker

Docker page => https://hub.docker.com/r/hypolas/registrator
Docker pull => hypolas/registrator
Pull command  => docker pull hypolas/registrator

Maybe that can help you.

We're also running our updated fork here: https://github.com/simplesurance/registrator

There is several forks of registrator. For example https://github.com/gliderlabs/registrator/issues/711


[suggestion] Kura inspector UX

Feature request
I believe that Kura inspector can be improved, because its current behavior is confusing:
$ ./target/debug/kura_inspector ./storage/ print

thread 'main' panicked at 'Index count is zero.
This could be because there are no blocks in the store: "./storage/"',

tools/kura_inspector/src/main.rs:70:5

$ ./target/debug/kura_inspector ./storage/blocks.index print

thread 'main' panicked at
'Failed to read index count from block store
{block_store_path:?}.: IO(Os { code: 20, kind: NotADirectory, message: "Not a directory" })',

tools/kura_inspector/src/main.rs:69:10

$ ./target/debug/kura_inspector ./storage/blocks.data print

thread 'main' panicked at
'Failed to read index count from block store
{block_store_path:?}.: IO(Os { code: 20, kind: NotADirectory, message: "Not a directory" })',

tools/kura_inspector/src/main.rs:69:10

Yesterday, while trying to find an answer to G. Bazior's question, I've copied the block data from Iroha 2, built Kura inspector and ran it with different options, supplying a path to a directory, a path to blocks.index and a path to blocks.data. None of the three worked. I assume path_to_block_store means it's a directory from the code, especially after seeing the impl StdFileBlockStore part, but not every user would look at it.
In my opinion, an ideal behavior would be to allow it to print the correct data in all three cases: if there are only two files, the path may be auto-corrected. It also needs to check data consistency and display a warning message when the file containing the blocks is damaged.
Also, "this could be because there are no blocks in the store" message is wrong. In my case, both files I copied from Docker were empty, so this wasn't detected.
The user wants to know the contents, but "Kura inspector" both fails and leaves actual contents to guessing. If there are no blocks, the utility should explain that. If there are, but another error had happened, this needs to be explained as well.
Motivation
I'd like the Kura inspector to be a more convenient tool.

In my case, both files I copied from Docker were empty, so this wasn't detected.

@6r1d, i think error message imply this no blocks => files are empty, perhaps we should rephrase it somehow.

an ideal behavior would be to allow it to print the correct data in all three cases

Perhaps we should write that kura_inspector expects path_to_blockdirectory where blocks.data and blocks.index lives in --help message.


Saving OAuth2.0 generated token to external db, to prevent invalidation of app install

I have written Slack Bolt bot in Python which I intend to distribute on the App Directory. This requires me to enable OAuth2.0 in my app, which I have done following the instructions in the docs.
I have hosted my app on heroku, and everytime I push a new release, the existing installation in my slack team gets invalidated.
I understand that this happens because the token is saved on the ./data directory (as in the documentation) and does not persist.
The docs mention that I have to modify the OAuthStateStore github, but that doesnt seem to do much.
I was wondering if there was an straightforward way to this, like Bolt for JS has for the same functionality

Any help or guidance is much appreciated!

Hey @amogh-jrules, thanks for reaching out! It sounds like you understand why this is happening - Heroku doesn't persist the filesystem between deploys, so the ./data directory is removed on each re-deploy.
The FileSystem/SQLite database is great for development, but not ideal for production since it only persists in memory and on the filesystem. Heroku has a decent (but dated) article explaining this is more detail.
For Python, I think you'll want to use the SQLAlchemyInstallationStore adapter, which uses SQLAlchemy. You can follow this example code to connect Bolt to a PostgreSQL database. And you can spin up a PostgreSQL database with Heroku.
Hope that helps and, please, let me know how it goes!

Hey @amogh-jrules, thanks for reaching out! It sounds like you understand why this is happening - Heroku doesn't persist the filesystem between deploys, so the ./data directory is removed on each re-deploy.
The FileSystem/SQLite database is great for development, but not ideal for production since it only persists in memory and on the filesystem. Heroku has a decent (but dated) article explaining this is more detail.
For Python, I think you'll want to use the SQLAlchemyInstallationStore adapter, which uses SQLAlchemy. You can follow this example code to connect Bolt to a PostgreSQL database. And you can spin up a PostgreSQL database with Heroku.
Hope that helps and, please, let me know how it goes!

@mwbrooks Thanks for the prompt response! Yeah that looks promising, I spent a lot of time trying to rewriting the Slack SDK OAuth classes inorder to find something that works.
I'll give this a spin and let you know how it came along, appreciate the effort 🙌🏽

@mwbrooks Thanks for the prompt response! Yeah that looks promising, I spent a lot of time trying to rewriting the Slack SDK OAuth classes inorder to find something that works.
I'll give this a spin and let you know how it came along, appreciate the effort 🙌🏽

@amogh-jrules aweeeeeesome! 🎉 Sorry to hear that you spent so much time rewriting the OAuth methods, but it's great to hear that you're good to go now 🙂

@amogh-jrules aweeeeeesome! 🎉 Sorry to hear that you spent so much time rewriting the OAuth methods, but it's great to hear that you're good to go now 🙂


enable readOnlyRootFilesystem on cluster permission pod

@xiangjingli also the stolostron org is a direct fork from this repo so no magic mirror just use the GitHub UI button to sync. Just a FYI.


Add install target

The install target dumps the bin into ~/.porter and symlinks it to /usr/local/bin.
Note that this doesn't work with porter until #139 is merged.

The install target runs build first, which is handling getting all of the mixins into bin before we dump the entire thing over to ~/.porter.
Here's what's in ~/.porter after I deleted my bin, and ~/.porter and then ran make install:
/Users/carolynvs/.porter
├── mixins
│   ├── azure
│   │   ├── azure
│   │   └── azure-runtime
│   ├── exec
│   │   ├── exec
│   │   └── exec-runtime
│   ├── helm
│   │   ├── helm
│   │   └── helm-runtime
│   └── porter
│       ├── porter
│       └── porter-runtime
├── porter
└── templates
    ├── porter.yaml
    └── run

Do you see anything missing?
Yeah, I originally expected that PORTER_HOME at the top of the Makefile would point to ~/.porter, then realized that it doesn't due to the CI tests. I will follow-up in another PR to change that so that it works like the other Makefiles (and still runs the CI tests from inside bin instead of against the system).

Ah, now I gotcha 👍.  Thank you for the detailed explanation.


Can't do inference

Hello,
I'm trying to use example.py on a french model (fr.22000 or fr-txt.large.19000)
But I have this error:
   raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format( RuntimeError: Error(s) in loading state_dict for Model:         Unexpected key(s) in state_dict: "bert.position_ids".
I also tried with the following command, same error in output.
python recasepunc.py predict fr.22000 < toto.txt > output.txt
Do you have any advice?
Thanks

Hello ,
I have the same issue with French model

It is likely a version mismatch of the transformers module. Are you using transformers==4.10.0?

Indeed it works better like that. Thank you


[QA] Replace setTimeout by adapter.setTimeout

Check code and replace native setTimeout with adapterSetTimout.
Same for clear, interval, ...

implemented with v2.3.0


Refactor the code to the working condition

I separated the code in files, and made it to work.
After this I could implement tests and I think we can publish it.
Notable changes:

Only the actions which have truthy action.meta.socket and action.payload.message properties and are not incoming messages (have action.meta.incoming falsy) will be sent through the socket:

export function isSocketAction (action) {
  return Boolean(
    action &&
    action.meta &&
    action.meta.socket &&
    action.payload &&
    action.payload.message
  )
}

export function isIncomingMessage (action) {
  return Boolean(action && action.meta && action.meta.incoming)
}

if (!isSocketAction(action) || isIncomingMessage(action)) {
  return next(action)
}

if action.payload.message is an object, middleware will JSON.stringify it:

export function normalizeMessage (action) {
  const { payload: { message } } = action

  switch (typeof message) {
    case 'object':
      return JSON.stringify(message)
    default:
      return message
  }
}

when onmessage is triggered, middleware tries to first parse message as json and if fails returns raw

Also, currently middleware doesn't next actions with meta.socket, and probably we should, because those actions may contain data you need in reducers, to show spinner or something

Probably we could send raw data by default and if user provides formatter, then decode/encode it using it.

@sch ping

Very nice work! I'm interested in the background that led to the message key of the payload. How are you using this field in your application?

You mean, why payload.message and not payload? I though one might want to include other data in payload. Also I think, actions meant to be sent through socket, should be also "nexted", if we do that, it would be convenient.
https://github.com/sch/redux-websocket-middleware/pull/3#issuecomment-310381950

How shall we proceed?

I'm afraid if you're not willing to collaborate, I'd have to move the code into my own repo


Team name

Hello everyone!
Is there a way to get players' team name from the DEMO?

Maybe you can get it by using steam 64ID in demo file and use an api to convert it


JSON encoding of floats does not match the documentation

Hello,
The documentation states that:

Starlark float values are encoded using decimal point notation, even if the value is an integer.

This suggests that float(1) should be encoded as 1.0, similar to Python:
>>> import json
>>> json.dumps([1.0])
"[1.0]"

However, Starlark uses %g formatting, which truncates trailing zeros and the decimal point. Hence:
>>> json.encode([1.0])
"[1]"

It appears that "encoding/json" module in Go exhibits the same behavior.
Even a comment in the Starlark source code misleadingly states that a float representation "always contains a decimal point":
https://github.com/google/starlark-go/blob/1207426daebd7ea8eb86b8d917a344a72cc5167b/lib/json/json.go#L150
In my opinion, since Starlark tries to be similar to Python, the JSON serialization should behave the same way and preserve the information about the floating-point type. I don't expect that changing the formatting will break existing code, but even so the current implementation will definitely lead to bugs. However, in case you decide not to change anything here, please update the documentation accordingly.
Thank you!

That is definitely a bug. Thanks for reporting it.


update native dependencies

In Cargo.toml, point the following to sequencer repo: starknet_api
blockifier
src/lib.rs: Update to match sequencer blockifier/src/transaction/objects.rs TransactionExecutionInfo::transaction_receipt
was changed to
TransactionExecutionInfo::receipt
Note: This will fail until corresponding update in sequencer is made.
Sequencer PR: NethermindEth/sequencer#11

Superseded by #2119


Single level crowdsim remake

Works with new building.yaml format (read and write).
Crowdsim UI remake.

Can you give us more details about what changed, in what way and what this PR addresses?

Originally, in building yaml file, crowdsim tag was a separate entity beside building. This pr brings crowdsim tag to under L1 (level 1) so that crowdsim settings are independent across each level. This serves as a preparation for independent multilevel crowdsim. Only L1 is supported at the moment. All non-static models for human are added under models tag, where originally they fall under crowdsim tag and dynamically generated and inserted to the model during runtime.
A word of caution: this pr has only been tested with single level map. There might be some unforeseen behaviour in multilevel map. Multilevel map will be tested in the next iteration of multilevel independent crowdsim.
Various python generation scripts are updated to accommodate new changes in building yaml file (see "Files changed").
Traffic editor UI sees new human properties tag specific to each vertex, so a user can select a vertex and add simulated human under the properties. In the past, a user have to manually specify coordinate for a particular vertex in the crowdsim configuration table.
Model type table and agent profile table are combined so that agent names - common to both tables - are edited in a single place.
Agents table are replaced with just a single text field for the external agent names (with default setting for external agent remain hidden to user), because the internal agents (simulated human) can be directly manipulated by selecting a particular vertex and changing its human properties.

Superseded by multilevel crowdsim pr.


Langflow not loading all required Environment variable mentioned in LANGFLOW_VARIABLES_TO_GET_FROM_ENVIRONMENT

Describe the bug
Trying to load 3 global variables from Environment. only the first variable is loaded and not the second
Browser and Version

Browser: Edge
Version: 126.0.2592.81

To Reproduce
Steps to reproduce the behavior:

my .env file: includes the lines:

LANGFLOW_STORE_ENVIRONMENT_VARIABLES = true
LANGFLOW_VARIABLES_TO_GET_FROM_ENVIRONMENT='["default_gcp_project", "default_gcp_location", "default_gcp_dataset"]'

launch Langflow: python -m langflow run  --components-path /src_backend_platform/ --env-file /env/.env
Only the first variable is loaded in Langflow: default_gcp_project

Screenshots

@dosu, I made sure the .env is as the following:
LANGFLOW_STORE_ENVIRONMENT_VARIABLES=true
LANGFLOW_VARIABLES_TO_GET_FROM_ENVIRONMENT='["default_gcp_location", "default_gcp_dataset", "default_gcp_project"]'

this is still resulting into loading only the first variable.

Unfortunately still not working! looks like it is a bug. Anyone else can confirm able to load multiple environment variable?

I just posted a bug #2717 a few hours ago which may relate to your issue.

Hi, @codenprogressive . How are you?
The issue has been fixed in PR #2971. I tested it and was able to load the environment variables you mentioned, as shown in the image:

If you encounter any other issues, please open a new issue!
Thank you very much for your collaboration!


Avoid incompatible *.dat files between Python 2 and 3

Proposed changes for #174.
In Babel 2.0, *.dat files use datetime.date class. However, pickle data format for the date class is incompatible between Python 2 and 3. Proposed changes remove uses of date class from *.dat files and add check for only babel.* classes in *.dat files.

Current coverage is 82.94%

Merging #188 into master will increase coverage by +0.02% as of 9ae7d05

@@            master    #188   diff @@
======================================
  Files           21      21
  Stmts         3770    3774     +4
  Branches         0       0
  Methods          0       0
======================================
+ Hit           3126    3130     +4
  Partial          0       0
  Missed         644     644

Review entire Coverage Diff

Powered by Codecov

hey, the first lines of your commit message are too long and will be capped by git. Could you take a look at http://coala.readthedocs.org/en/latest/Getting_Involved/Writing_Good_Commits/#how-to-write-good-commit-messages and adjust the messages accordingly so when problems with that code arise we can use git blame effectively?

Okay. I revised the commit message.

It's ok to me. @sils1297 any extra input here?

@erickwilder I'm not competent to approve this PR right now but it looks sane on first sight.

We should add tests for this somehow.

@mitsuhiko
Any suggestions on what kind of tests to add here in addition of the code added to test_core.py file?

@erickwilder @mitsuhiko might likely not reply when @'ed as he gets emails for every comment of babel implicitly. I suggest you ping him on IRC when things occur.

The change is simple and includes a unit test, it looks good to me!
I need this fix because I also have the bug #174 on the OpenStack Horizon project.


eduvpn-client: init at 4.2.0

Description of changes
VPN client used (among other I assume) by educational institutions.
I would love some feedback whether the common package that wraps a small go library in python should live in an extra package.
If yes, do I understand correctly that this would not work via the by-name set?
If no, is there a way to get the bot to update the nested package?
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

What a coincidence! I just packaged this too at #278944

Indeed thank you for the heads up, I didnt see a PR yesterday before I considered to package it after work...
I think I'll close my PR after taking a closer look at yours in the afternoon and doing a full review.
You can (if you want to) add me as an additional maintainer.
Also the license should be gplv3Plus and the python application could go into pkgs by-name (the latter is optional but I believe should be the new default).
On 6 January 2024 10:53:24 CET, Jeroen Wijenbergh @.***> wrote:

What a coincidence! I just packaged this too at #278944
--
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/278995#issuecomment-1879619725
You are receiving this because you authored the thread.
Message ID: @.***>

Thanks! I would say only close it if you believe my pr is better.
That being said, I have added you as maintainer in my pr too, thanks for the gpl3Plus hint, I wasn't aware nix had a licenses.gpl3Plus option. pkgs/by-name is not clear to me when a package should be there and when it shouldn't

Ah I think I understand pkgs/by-name now, https://github.com/NixOS/nixpkgs/blob/master/pkgs/by-name/README.md
done!

thanks! closing this in favor of https://github.com/NixOS/nixpkgs/pull/278944


chore(update): bch-wallet-starter maintenance

PR related to this trello task --> https://trello.com/c/PPVUrQLa

:tada: This PR is included in version 1.5.0 :tada:
Your semantic-release bot :package::rocket:


Upgrade deps

I have upgraded deps.
But one problem:
https://jsr.io/@std/path/doc/~/posix
https://jsr.io/@std/path/doc/~/win32
Both posix and win32 are deprecated.

I will fix the deprecated warnings.  Please wait.


ColecoVision 2 Players On-screen touch control layout for left/right handed people

Standard Controller and Super Action Controller

that's another reason why you should put game screen at top close to notch

add button transparency/opacity

driving controller
left foot and right foot
Why are those two buttons on the left side of the keypad, because when you actually install the steering wheel, its side will be blocked.  In theory, the two buttons still work, but they are hard to be pressed

or add outline

I improved the Driving controller to make it easier to use

I will keep this in mind.
However, Snepulator's ColecoVision support is not yet at the point where it is ready for an Android port.
Still missing is support for some of the extra controller types and video modes.
Getting those controller types and video modes working is something I intend to do. However, an exact timeline is not yet planned.


Backport import components

Summary
Support for using data from contentlayer/generated in markdown pages (that themselves are included in contentlayer/generated). This data is obtained in getStaticProps, which is called before next build but after contentlayer build, which means all the data from contentlayer/generated can be accessed and passed to consumer pages, and further to components used in them.
Consumer pages can define variables they need access to (e.g. to pass them to components) in their frontmatter, in newly added data field. This field is of type list<string>, which means you can define multiple variables you want to have access to.
Names of the variables in the list need to have a corresponding getter function created in content/getters folder.
These getters will be called by getPageData function in getStaticProps, so after contentlayer/generated has been populated. This means all getter functions can import from contentlayer/generated.
A page with names defined in frontmatter's data field will have access to variables under the same names (provided that corresponding getters exist).
Changes

create getPageData function that takes in an array of variable names , for each name it tries to import a getter of a corresponding name from content/getters, obtain the data, and return an object with a mapping from each name -> data returned from the getter
define a new contentlayer field: data of type list (default: [])
get value of data field  for each MD page in getStaticProps and call getPageData with it
pass the resulting object with mapping from each name from data field list to the result of running a corresponding getter function, as data prop to Page component in [[...slug]]
pass data object to MDX page

Example
Some MD page, which requires profiles and topics variables to render its CircularVis component.
---
data:
  - profiles
  - topics
---

import CircularVis from "components/ecosystem/CircularVis.jsx"
## Visualizing the Ecosystem by Topic

This visualization maps an overview of organizations grouped together by their primary topic. Click to zoom in or out. Hover over a circle to see its name.

<CircularVis profiles={profiles} topics={topics} />

We need to create corresponding content/getters/profiles.js and content/getters/topics.js, where we can import from contentlayer/generated E.g.:
// profiles.js
import { allProfiles } from 'contentlayer/generated';

export default function getProfiles() {
  return allProfiles.filter(
    (profile) => !(profile.curation_status.includes('N') || profile.curation_status.includes('?'))
  );
}

@olayway PR description is excellent (can become the docs i suspect!).
One minor comment about the PR is that we have a bit of noise from the linting stuff - in a perfect world that would be a separate PR (or just push those fixes to main directly) so that this PR is clean. Ok in the end as i looked at commits and commits are clean.

@olayway good to go IMO - just a couple of comments for discussion and my understanding of the code.


Add self to practitioners

Add my name to the middle of the list. Should the list be alphabetized?

I think people will get attached to ordinality :)


Broken link to terraform documentation

Describe what happened
droplet.d.ts contains a broken link to https://www.terraform.io/providers/digitalocean/digitalocean/latest/docs/resources/monitor_alert. To correct the link, replace "www" with "registry": https://registry.terraform.io/providers/digitalocean/digitalocean/latest/docs/resources/monitor_alert
You might want to look for other links in the documentation with a similar pattern.
Sample program
N/A
Log output
No response
Affected Resource(s)
No response
Output of pulumi about
N/A
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @cowwoc - thank you for filing this bug.
This is likely an issue with link stripping/replacing in the pulumi-terraform-bridge's docsgen - we don't usually link back to the upstream documentation; we'd want to link to monitoralert if anything.
We'll investigate.


mwc-select not present in npm registry

npm i @material/mwc-select

npm ERR! code E404
npm ERR! 404 Not Found: @material/mwc-select@latest

npm ERR! A complete log of this run can be found in:
npm ERR!     .npm/_logs/2018-05-14T09_06_41_487Z-debug.log
zsh: exit 1     npm i @material/mwc-select

Can you please add it to npm? The documentation for this element is also missing. Why there is no README file?

See https://github.com/material-components/material-components-web-components/issues/4


DS-3939 OAI-Harvester, skip item and continue if handle is missing

Allows OAI Harvester to continue if it encounters an Item missing a handle

Obvious fix, merging immediately.


Block unsupported Python versions when debugging

debugpy doesn't support versions below Python 3.7. However, the diagnostic that it prints out to the console is not reported by VSCode, and thus debugging simply fails with no explanation (see e.g. https://github.com/microsoft/vscode-python/issues/19427).
To prevent this, the extension should check Python version number for compatibility before spawning the adapter. To avoid hardcoding the version number, it can be parsed directly from dist-info/METADATA file in the debugpy package; it should contain a line like:
Requires-Python: >=3.7

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

We don't have the dist-info because we unpack the wheels ourselves:

dist-info is part of the wheel archive, so it should be possible to extract it with that intact.
But it it's too much hassle, we can add it to some known location in the debugpy package itself, so that it could be parsed from there.

Thank you to everyone who upvoted this issue! Since the community showed interest in this feature request we will leave this issue open as something to consider implementing at some point in the future.
We do encourage people to continue 👍 the first/opening comment as it helps us prioritize our work based on what the community seems to want the most.

I now get a modal dialog message indicating the fact that 3.6 is not supported.


External sources

Is it possible to make the installation of external applications to be done manually, instead of internal ones, such as the tachiyomi-extensions and Anyomi application?
Like on that next

I do plan on making sources external. Currently, I don't know how to do it in React Native.

I do plan on making sources external. Currently, I don't know how to do it in React Native.

Then atleast give us options to search from limited sources do not search in all it consume to much data for me and user like who have limited data access

Then atleast give us options to search from limited sources do not search in all it consume to much data for me and user like who have limited data access

You can pin the sources you want to use and turn off search all sources in browse settings and the app would only search pinned sources in global search.

Then atleast give us options to search from limited sources do not search in all it consume to much data for me and user like who have limited data access

You can pin the sources you want to use and turn off search all sources in browse settings and the app would only search pinned sources in global search.

Thank you

implemented in v2


Only one between pec and SDI code must be mandatory

Solve issue #3

We have to fix the Roave BC check...


set_resizable(false) does not make the window fully non-resizable on tiling window manager

I'm running dwm - a tiling window manager. All windows are sorted in a grid, which means all windows(if resizable) get resized to fit the amount of screenspace left.

As you can see in the screenshot, the window gets resized to fit half of the screen even though I set the dimensions to be 640x480 on line 6. Now, what if I don't want that and I'd like the window to keep it's intended size?
I messed around with the library a bit and found out I could do something like this:
impl WindowHandler for MyWindowHandler
{
    fn on_start(&mut self, helper: &mut WindowHelper, info: WindowStartupInfo) {
        helper.set_resizable(false);
    }
}

to make the window non-resizable.
And while doing that does make me unable to resize the window as a user, it still shows up like it did in the first screenshot.
I'm guessing the on_start method gets called some time after the window actually gets created, so the system resizes the window before it turns non-resizabe.

Thanks for reporting this! I'll add an API to the window creation options, to allow the window to be set as non-resizable during creation.

I've added this to the latest master, will be in v1.1 when that gets released.

v1.1.0 is now released :) Thanks again for the report.


Does the crawlee-python supports preNavigationHooks?

As the title, I want to know does the crawlee-python support the preNavigationHooks function?

Hello and thanks for your interest in Crawlee for Python! Pre-navigation hooks are not currently supported. Before we implement this, would putting the hook code into the request handler help? Or do you need to do something before the page is loaded?

Hello and thanks for your interest in Crawlee for Python! Pre-navigation hooks are not currently supported. Before we implement this, would putting the hook code into the request handler help? Or do you need to do something before the page is loaded?

OK, thank you, I want to change some browser properties before the page loaded, so I think it will be really helpful to support  the preNavigationHooks.

I want to do something before the page loads, such as aborting when loading some images or CSS, Is there any trick available to achieve this as of now?

Implementation from Crawlee JS:

preNavigationHooks
postNavigationHooks

@vdusek /assign

@vdusek /assign

We don't assign issues for hacktoberfest. If you want to contribute, open a PR whenever you're ready. First mergeable one gets merged.

@janbuchar Thank Mate

@janbuchar i have created a PR to solve the issue please view it #602


Added some extra test coverage

[x] Tests added / passed
[x] Passes pre-commit run --all-files

This is my first contribution to dask so thought I'd add some test coverage while I familiarize myself with the repo. I've added a test for an option to sort_values that wasn't previously tested, as well as a few other tests for lines in numeric.py and shuffle.py that weren't tested.

@lrjball thanks for your patience on this PR! Would you mind resolving the merge conflicts and merging main?

Or if you prefer one of us can do the rebase. Sorry this totally slipped through the cracks :(

No worries, I have resolved the merge conflict now

ok to test

Thanks @lrjball for opening this PR and congrats on your first contribution to dask!


drivers: regulator: pca9420: fix support for DVS modes

Fix support for DVS modes, as the dvs_state_set implementation previously had the mask and value parameters in the i2c_reg_update_byte_dt function swapped.
Also, record the active DVS state and update the voltage get/set and regulator enable/disable function to target the active DVS mode. This will enable a user to configure multiple run modes, and modify target voltages for those modes when in the new mode. When a user is utilizing the MODESEL pins, update the active state but return an error so that the application can still edit settings for the new DVS mode once it has reconfigured the appropriate pins.

Rebased to pick up fix for CI failure.

Rebased to pick up fix for CI failure.

interesting you didn't loose approvals :-)

interesting you didn't loose approvals :-)

I noticed that as well- perhaps github is getting smarter about when to dismiss them


Token: No response

After updating ioBroker to newest version Tesla Adapter does not let me get Token. Error Message "Could not retrieve token, Error from Tesla: No response"
Yesterday all was fine.

i have the same problem. also an downgrade doesnt work :( i tried it 20 time. How can we fix this?

Same issue here - did they change their API? -> no response for me too

Duplicate of #78
Please look into issue #78, in short: Tesla is playing around with its authentication rules and that causes these disturbances. Unfortunately, the problem relates to TeslaJS and can't be solved by the maintainer of this iobroker adapter. On the other hand, the problem affects a lot more users outside of iobroker, so we can hope to have a solution brought be Tesla anyday soon...

Duplicate of #78
Please look into issue #78, in short: Tesla is playing around with its authentication rules and that causes these disturbances. Unfortunately, the problem relates to TeslaJS and can't be solved by the maintainer of this iobroker adapter. On the other hand, the problem affects a lot more users outside of iobroker, so we can hope to have a solution brought be Tesla anyday soon...

i can manually generate a token and refresh token with a 3rd party app. Is there no way to use these valid tokens in the iobroker adapter? The token fields are greyed out, so i cannot manually add them...

Duplicate of #78
Please look into issue #78, in short: Tesla is playing around with its authentication rules and that causes these disturbances. Unfortunately, the problem relates to TeslaJS and can't be solved by the maintainer of this iobroker adapter. On the other hand, the problem affects a lot more users outside of iobroker, so we can hope to have a solution brought be Tesla anyday soon...

hi - just following up here. I really think this could be solved by enabling the user to provide his own tokens. In the adpater login screen I manually enabled the token fields by changing the code from readonly to write and enabled the save and close button. I then pasted my tokens and saved it. Now it is working again. Any work is appreciated. Thanks!

Duplicate of #78
Please look into issue #78, in short: Tesla is playing around with its authentication rules and that causes these disturbances. Unfortunately, the problem relates to TeslaJS and can't be solved by the maintainer of this iobroker adapter. On the other hand, the problem affects a lot more users outside of iobroker, so we can hope to have a solution brought be Tesla anyday soon...

hi - just following up here. I really think this could be solved by enabling the user to provide his own tokens. In the adpater login screen I manually enabled the token fields by changing the code from readonly to write and enabled the save and close button. I then pasted my tokens and saved it. Now it is working again. Any work is appreciated. Thanks!

Hi adultano,
is it possible to share the adjustments or share an short how to? I have no idea how I can change the settings to set the token manual. Thanks a lot!

Hi. Yes ill post a how to guide on Monday or Tuesday. Unfortunately i am in kind of an emergeny these days but i will come back early next week.

Looking forward to your reply on how to manipulate the json for a manually obtained token. However, please use #78 instead of this thread since it is a duplicate of an existing topic which has a bunch of people following the thread which may be interested also. Thank you. :-)

https://github.com/dbweb-ch/ioBroker.tesla-motors/issues/78#issuecomment-899238353


contract state is wrong after a transfer

Using the develop branch, commit 4fc24b1, I can complete a transfer but the final balances are wrong (0 on both sides).
This is the contract state of the sender after the transfer:
Loading descriptor from wallet wallet_0 ... success
Global:
  spec := (ticker=("USDT"), name=("USD Tether"), details=~, precision=0)
  terms := (text=("demo NIA asset"), media=~)
  issuedSupply := (2000)

Owned:
  assetOwner:
    amount=2000, utxo=bc:opret1st:ce620aa0b5ed49a36d8d72951d4c9242a835ea8fdedd067f5cbdcf84086036c1:1, witness=~ # owner unknown

This is the contract state of the recipient after the transfer:
Loading descriptor from wallet wallet_1 ... success
Global:
  spec := (ticker=("USDT"), name=("USD Tether"), details=~, precision=0)
  terms := (text=("demo NIA asset"), media=~)
  issuedSupply := (2000)

Owned:
  assetOwner:
    amount=1900, utxo=bc:opret1st:3cb6ddaad92b1e5536f7d9a7b1ccd00bf49583c1eb3385a705220329b247619a:0, witness=bc:3cb6ddaad92b1e5536f7d9a7b1ccd00bf49583c1eb3385a705220329b247619a # owner unknown
    amount=2000, utxo=bc:opret1st:ce620aa0b5ed49a36d8d72951d4c9242a835ea8fdedd067f5cbdcf84086036c1:1, witness=~ # owner unknown

Note: I have use the -a option to show all state.

Re-testing with the fix in 8b7506f (plus a cargo update of bp-wallet to include fixes up to 03bb754) the transfer command now fails with:
Loading descriptor from wallet wallet_0 ... success
thread 'main' panicked at ../rgb/src/store.rs:241:20:
error saving data: "unable to serialize wallet data as TOML file - map key was not a string"

Re-tested using commit d6c4228 and the issue is now fixed.


Modify main.html

Hi, How can I modify  or replace main.html . I need replace "Loading..." title and to add new meta tags.
Thanks!

You can't modify main.html unless you replace the whole telescope:core package, sorry. But if you want to add new meta tags you can just add a <head> section to any html file that's included in your project (you don't need the <template> tag) and it will get picked up automatically.


Update file upload styles and create a common component.

@keybase/react-hackers, this is ready for review.

@chrisnojima, this is ready for another look.

@keybase/react-hackers, bump.


How to get the response status code?

Suppose I have something like:
$response = Curl::to('localhost/foo/bar')
            ->withData($data)
            ->asJson()
            ->put();

How do I process the incoming status code (200, 400, etc.)?

Wrong repo. Sorry.


[AIRFLOW-XXX] Removing the renaming of TaskRunner from update

Description
In released version 1.10.0, default task runner is still BashTaskRunner. The change "Renaming of BashTaskRunner to StandardTaskRunner" is only in the master branch not in the 1.10.0 released version.
Removing the note from updating documentation.
https://github.com/apache/incubator-airflow/blob/v1-10-stable/airflow/task/task_runner/__init__.py

Codecov Report

Merging #3868 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3868   +/-   ##
=======================================
  Coverage   77.51%   77.51%
=======================================
  Files         200      200
  Lines       15815    15815
=======================================
  Hits        12259    12259
  Misses       3556     3556

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 7cd3a85...294d21b. Read the comment docs.

You are changing the docs for master where this change has happened. In addition it is marked under master in the updating documentation.


--download-archive file format extending

Checklist

[X] I'm reporting a feature request
[X] I've verified that I'm running yt-dlp version 2<IP_ADDRESS>. (update instructions)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
Is there any way to save additional information in additional columns?

episode url
file name in -o format (a.k.a. %(title)s [%(id)s].%(ext)s by default)
sha1 file checksum

As explained in https://github.com/yt-dlp/yt-dlp/issues/1172, download-archive's one and only purpose is to facilitate the "already recorded in archive" detection. It's formatting will not be expanded.
You can write whatever data you want to a separate file using --exec. Eg: --exec "echo %(extractor)s %(id)s %(filepath)s>videos.txt

Sometimes it is difficult to understand by Id if file already downloaded or not. E.g. same series from other source. Or source reupload series with new ID.
But thanks for --exec

--exec fired even for files which already downloaded before. It fired for files which not downloaded in current session. So it will be fired for old files each time when new episodes added to season page (my source doesn't have per episode link).

Use archive to prevent re-downloading of videos, use --exec if you want a human-readable database. There is nothing preventing you from using both at the same time


[Feature Request] OpenAI support to auto generate subject

💭 Describe the feature
Inspired by aicommits
#91

2023-2-17 update
provide command option czg --openai-token=sk- to setup token on $HOME/.config/.czrc

💡 Proposed Solution
Interaction

select types and get base information
generate AI commits and confirm prompt (yes or edit or retry or no)
if select edit the Al commits will be default value provide original prompt message

Configuration Item

useAI: Whether to enable AI auto generate subject
aiType: "OpenAI"
aiQuestionCB

Usage
czg:

if setting export CZ_OPENAI_TOKEN="xxxx" on .zshrc and .bashrc

provide subcmd: czg ai or git czg ai : Turn on openAI generate subject mode
if  useAI is true just run czg or git czg

if none setting .zshrc or .bashrc can use:

CZ_OPENAI_TOKEN="xxxx" czg ai or CZ_OPENAI_TOKEN="xxxx" git czg ai
or use bynpx: CZ_OPENAI_TOKEN="xxxx" npx czg ai

commitizen + cz-git:

if setting export CZ_OPENAI_TOKEN="xxxx" on .zshrc and .bashrc

czai=1 cz: Turn on openAI generate subject mode
if  useAI is true just run cz or git cz

if none setting .zshrc or .bashrc can use:

CZ_OPENAI_TOKEN="xxxx" czai=1 cz or CZ_OPENAI_TOKEN="xxxx" openai=1 git cz

demo is ready:

cz demo is ready. I will go on to finish czg, And I will release a next version:

2023-2-16 Update

Now most feature has finished

Next step is to to docs and website guide

And then will release v1.5.0

Next week target:

[ ] Add retry API

[ ] prompt edit feature, can use complete default subject value

The latest version 🌟(v1.5.0)🌟 should be resolve this issue request
More information and usage see: https://cz-git.qbb.sh/recipes/openai