auto_loading model and library problem

I have changed the line in autoload.php file. I am trying to call the this model in my controller. This is not working.
$autoload['model'] = array("M_functions"=>"function");
If I call this model in the controller manually. It works fine.
 $this->load->model("M_functions","function");

Error
`
A PHP Error was encountered
Severity: Notice
Message: Undefined property: Diagnose::$function
Filename: controllers/Diagnose.php
Line Number: 21
Backtrace:
File: /var/www/html/hfs/application/controllers/Diagnose.php
Line: 21
Function: _error_handler
File: /var/www/html/hfs/index.php
Line: 315
Function: require_once
Fatal error: Call to a member function password_generator() on null in /var/www/html/hfs/application/controllers/Diagnose.php on line 21
A PHP Error was encountered
Severity: Error
Message: Call to a member function password_generator() on null
Filename: controllers/Diagnose.php
Line Number: 21
Backtrace:
`
I have function name password_generator() in the M_functions model.  Same thing is happening for libraries also. I have manually load the session, form_validation library.
###For input library.
$autoload['libraries'] = array('database','../core/input','encrypt');

I have  to call the library like this. If I was trying to call without relative path. input library is also not working.
I have CodeIgniter 3.1.0. I have compared my Loader.php file with latest developed branch and 3.1.0 branch file. Both are same.
someone suggest this solution.

when I try to autoload the library session.
I have this error.
Unable to locate the specified class: Session.php

Due to autoloading problem. I am unable to load the use hooks in my application properly.

Please post this on our forums instead, this is a bug tracker.

why don't you answer these kind of question which are related to bug.

@hsali When you have an error, it is not necessarily a bug :P that's why you should try on forums.

But, it's kind of bug. Because I have tried mostly answers. Those didn't work for me.


gpt: make system message limit gpt response to 3 sentences

so the text-to-speech loading doesn't take too long

this is now possible using the system_prompt field in database.json by using that string to say something like "keep responses to 3 sentences or less"


Prl 4846 Manage order - Judge approval journey- Approval scenarios

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/PRL-4846
Change description
Manage order - Judge approval journey- Approval scenarios
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Created 1775, closing this since no longer required


Fix Browserify+Babel issues

There are two separate issues being fixed here: inNodeJS is useful for request logic, but
shouldn't be used to determine how we export Tabletop, since Browserify
still uses module.exports. I eliminated the global variable, since it causes failure when coupled with Babel (which rewrites its modules into strict mode).
Second, Browserify will happily bundle 1.5MB of extra stuff we don't
need if we use the browser-request module, even though we have our own
well-tested AJAX code. So we need to prevent its static require
analyzer from seeing the module load, while still letting this work in
Node itself. trim() seems like a simple enough way to do this, without
having to include browser-specific packaging (in other words, rather
than shim it, just don't actually require anything).
After this fix, the bundled JavaScript size dropped to about 30KB, which seems normal, and it was still exported correctly for Browserify.

Incidentally, this also addresses the issues raised in #82 in a succinct way, which would let you close that as well.

:+1:
Otherwise Browserify builds a lot of extra stuff

I have no idea how I missed this for so long - thanks a ton!


posion unlearning update only adpoted in a hvp_batch_size

Hi @alewarne , thanks for your insightful work and code sharing. When I read the codes, I found that for the poison unlearning parts, both first-order and second-order unlearning updates only run in a hvp_batch https://github.com/alewarne/MachineUnlearning/blob/1968fd604147887b69f1adc9d808904fb02498d8/Applications/Poisoning/unlearn/common.py#LL99C9-L99C9.
What if the whole changed size is far larger than hvp_batch, i,e., len(dedelta_idx) >> hvp_batch_size? In this case, a 1024 or 512-size unlearning update may not work well.

Hi,
not sure if I get your question right: Firstly, a general insight of our paper is that the accuracy of the update gets worse if the size of delta rises (see Figure 9 in the paper. However, the update can be calculated if the hvp_batch_size is smaller than the total number of points to change, in this case the update is repeatedly applied until convergence of the LISSA algorithm. Does this answer your question?

Thanks for your reply! I now understand this operation.


Create extensible widget for opening zarr/hierarchical data

Goals
Make a widget that displays a zarr in a tree view widget and provide extensible right-click context menus so it is easy to add new functions that act on datasets in the zarr (e.g. new readers, alternative renderers, etc.).
An outline of an implementation is provided in https://github.com/kephale/napari-multiscale-rendering-prototype/blob/1109e7693fce9fcca81c521ba11ce556dafb1bc5/src/napari_multiscale_rendering_prototype/multiscale_rendering_ui.py.
The specific expectation is that we will use this as a way to compare napari's behavior with different rendering implementations:

current multiscale rendering
tiled 2D multiscale rendering
tiled 3D multiscale rendering
potentially alternative non-vispy renderers

Each of these renderers will be exposed in the context menu, and they will be tested on multiscale image data. The renderers will be developed independently of this task.
It is important to note that the primary goal of this UI is to support development and early-stage user testing, not to be a fully polished ship-able feature.
In detail

Show the contents of a zarr (and hdf5) file in a hierarchical tree view.

This is a screenshot from napari-hierarchical showing an HDF5 file that contains 1 group.

Provide right-click context menus for multiple readers.

This is a screenshot of the right-click context menu from napari-hierarchical that shows an entry for "Load arrays."
In napari-hierarchical, Load arrays ultimately displays the selected data as a normal Image layer. However, we want to provide multiple options in this context menu for displaying data with different renderers.

A minimal example should match the descriptions and outline here:

https://github.com/kephale/napari-multiscale-rendering-prototype/blob/1109e7693fce9fcca81c521ba11ce556dafb1bc5/src/napari_multiscale_rendering_prototype/multiscale_rendering_ui.py#L1-L47
References:

a tree view widget that works with napari https://github.com/BodenmillerGroup/napari-hierarchical/blob/main/src/napari_hierarchical/widgets/_group_tree_view.py

Also see this https://github.com/xulman/ome-zarr-fiji-ui

An initial set of rendering methods that can already be included:
Text mode: don’t visualize, just log properties of the dataset to console (e.g. shape, dtype, chunksize)
Original 2D mode: add_image, ensure viewer is in 2D mode
Original 3D mode: add_image, ensure viewer is in 3D mode


quickstart: sync soroban-rpc and horizon

What ?
This PR attempts to ensure that the same code repository that was used for the building of the horizon would also be used as the source of the soroban RPC.
This eliminate the risk of having the soroban-rpc ingestion mismatch with the horizon ingestion.

I'm assuming the set -e in the script will cause the makefile to bail if there is an error.

I'm assuming the set -e in the script will cause the makefile to bail if there is an error, but haven't tried that. Some errors could show up as git rev-parse not printing anything, or the grep being empty (which would fail, but print nothing?), which could be confusing to debug. Might be nice to catch that case and print something more specific.

The challenge here is that we don't want to output errors out. Maybe outputting potential errors to stderr while leaving stdout clear in that case.
I'll try to refactor this to have more concise error handling down the road; there are few scenarios that I can think of that would be a good test cases here.


[Feature]: Allow devs to enable/disable autofill in the email and password type inputs

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Devs should be able to disable the autofill in the input widget password and email fields.

Add a new field called "Allow autofill" in email and password type inputs and set it to true by default

Why should this be worked on?
Devs in financial companies would like to ensure this is a choice as they suggest it might be a safety concern for them.

Some more details on the field

Field name should be "Allow autofill"
This field should be a part of general section
It should be a switch field turned on by default
When on the email or password input will accept autofill from the end-user's browser
When off the email or password input will not accept autofill from the end-user's browser

Hi @dilippitchika these changes apply to V2 version alone?

Yes @vsvamsi1 only to v2 of input.

We will be supporting for json form text fields as well.
@dilippitchika @chandannkumar


Multiple lights on same board

I wish to control multiple lights on the same board. Could someone give me an example of the edits for this sketch (mostly how to set topics for publish and subscribe). I am very new to mqtt and hassio so any help would be greatly appreciated.  I was able to get this example working for the single control and have tried to edit sketch for two lights.  Thanks in advance..

Hi @89merkur,
Someone asked me the same question a few months ago. Just look at this issue, a example is provided.
Sam


[Vertex AI] Add Decodable conformance for FunctionResponse

Added decoding support for ModelContent.Part.functionResponse. Although FunctionResponse parts are never returned from the backend, Decodable conformance allows this type to be serialized/deserialized from disk. See #13593 for an example use case.
#no-changelog

Nice! Does this need a release note?

@ncooke3 I'm not certain that it's noteworthy enough for a release note but to err on the side of caution I've added one now (easier to prune it out later than remember to add it later).


Need help for close game.

When I init app and client, it run game. I only want to get game install path but after that game is still running due to init process, how I could close game or stop init ?

@Avocadocs Did you ever find a solution for this? I am having similar issues.

@TheOftedal No sadly I didn't get it working, keep me updated if you do :)

Could you clarify the issue and perhaps provide some example code. Dropping the initialized Client should shutdown the Steamworks SDK cleanly.

Could you provide example of how to drop the client ?

Rust dropping occurs when a variable goes out of scope. It can be at the end of an if statement, a function etc. You can explicity drop it by moving the client out of the current scope with drop(my_client)


[Add] CenterPoint compatibility with KITTI

This PR consists of two contributions

Modifies the code of CenterPoint's head (mmdet3d/models/dense_heads/centerpoint_head.py) to make it compatible with datasets having bbox annotations with 7 values (new, KITTI-like) or 9 values (current, nuScenes-like).
Adds KITTI configuration files for CenterPoint.

Motivation
Currently, there exists no official implementation for KITTI with CenterPoint while several issues have requested an implementation (see https://github.com/open-mmlab/mmdetection3d/issues/486, https://github.com/open-mmlab/mmdetection3d/issues/225, https://github.com/open-mmlab/mmdetection3d/issues/190). KITTI is a standard benchmarking dataset, and think it is of value to be able to refer to an official implementation and benchmark results when comparing CenterPoint with other models.
Modification
The code incenterpoint_head.py is restrained to how annotation bboxes are generated within two functions; def get_targets_single() and def loss().
For def get_targets_single(), the number of bbox annotation elements is set dynamically according to the config file (i.e. gt_annotation_num = len(self.train_cfg['code_weights']). The torch.Tensor annotation box (anno_box) is created either as a 7 or 9 element tensor depending on gt_annotation_num.
For def loss(), the annotation box is restructured first based on universal elements, in addition to the velocity components (vx, vy) if such elements exist.
These changes allow centerpoint_head.py to work with both nuScenes and KITTI configurations without requiring any further code changes.
The new KITTI configuration file parameter values are the same as in https://github.com/open-mmlab/mmdetection3d/issues/871.
The modifications are currently being validated with two experiment runs; nuScenes is validated using the existing config file centerpoint_0075voxel_second_secfpn_dcn_circlenms_4x8_cyclic_20e_nus.py, and KITTI is validated using the new config file centerpoint_01voxel_second_secfpn_dcn_circlenms_4x8_cyclic_20e_kitti.py. Results will be reported once available.

Here is the result of the (partly ongoing) experiment runs. By the looks of it, as the output is not garbage, the code modifications likely works.
Noticed that the reported results in https://github.com/open-mmlab/mmdetection3d/issues/871 have several different parameters values like 80 epochs and batch size 8, so I'll run another experiment with corresponding parameters to see if the performance numbers will match better.
KITTI experiment (20/20 epochs, voxel size 0.05 x 0.05 x 0.10)
Pedestrian<EMAIL_ADDRESS>0.50, 0.50:
bbox AP:58.8907, 53.7964, 51.8120
bev  AP:52.6117, 47.6410, 44.5468
3d   AP:48.8790, 43.1561, 39.0406
aos  AP:1.85, 2.11, 2.57
Pedestrian<EMAIL_ADDRESS>0.25, 0.25:
bbox AP:58.8907, 53.7964, 51.8120
bev  AP:66.8690, 62.5275, 59.8175
3d   AP:66.6481, 62.3058, 59.5542
aos  AP:1.85, 2.11, 2.57
Cyclist<EMAIL_ADDRESS>0.50, 0.50:
bbox AP:76.2551, 68.4002, 64.8945
bev  AP:72.6522, 61.4727, 58.4541
3d   AP:69.2906, 58.7568, 55.5770
aos  AP:0.33, 0.99, 0.96
Cyclist<EMAIL_ADDRESS>0.25, 0.25:
bbox AP:76.2551, 68.4002, 64.8945
bev  AP:75.4667, 66.3259, 62.4743
3d   AP:75.3724, 66.0972, 62.3836
aos  AP:0.33, 0.99, 0.96
Car<EMAIL_ADDRESS>0.70, 0.70:
bbox AP:90.3484, 88.7091, 80.3441
bev  AP:89.2393, 83.8527, 78.9589
3d   AP:85.4495, 75.3621, 67.9366
aos  AP:0.12, 0.53, 0.75
Car<EMAIL_ADDRESS>0.50, 0.50:
bbox AP:90.3484, 88.7091, 80.3441
bev  AP:90.4089, 89.5775, 86.4906
3d   AP:90.4022, 89.4933, 85.6491
aos  AP:0.12, 0.53, 0.75

Overall AP@easy, moderate, hard:
bbox AP:75.1647, 70.3019, 65.6835
bev  AP:71.5011, 64.3221, 60.6533
3d   AP:67.8731, 59.0916, 54.1847
aos  AP:0.77, 1.21, 1.43

nuScenes experiment (1/20 epochs)
mAP: 0.4224
mATE: 0.3379
mASE: 0.2769
mAOE: 0.5464
mAVE: 0.5787
mAAE: 0.2133
NDS: 0.5159
Eval time: 104.8s

Per-class results:
Object Class	AP	ATE	ASE	AOE	AVE	AAE
car	0.765	0.219	0.166	0.307	0.451	0.202
truck	0.372	0.397	0.241	0.192	0.412	0.250
bus	0.566	0.407	0.192	0.224	0.999	0.313
trailer	0.237	0.534	0.222	1.060	0.411	0.165
construction_vehicle	0.094	0.703	0.425	1.172	0.138	0.345
pedestrian	0.735	0.204	0.312	0.691	0.493	0.133
motorcycle	0.240	0.238	0.260	0.544	1.374	0.271
bicycle	0.114	0.195	0.264	0.623	0.350	0.027
traffic_cone	0.529	0.191	0.408	nan	nan	nan
barrier	0.573	0.291	0.279	0.105	nan	nan

The follow-up KITTI experiment results (80 epochs, voxel size 0.05 x 0.05 x 0.10, batch size 8, dual GPU)
Overall AP@easy, moderate, hard:
bbox AP:82.2772, 76.9228, 74.9812
bev  AP:77.8708, 69.9044, 66.6681
3d   AP:73.7784, 63.2037, 59.4934
aos  AP:0.83, 1.40, 1.70

The results improved and are now comparable to those reported in https://github.com/open-mmlab/mmdetection3d/issues/871, though in general 0.5~1.0 points lower. Will update the previous CenterPoint-KITTI  config files to reflect the changes.
Overall AP@easy, moderate, hard:
bbox AP:85,4418, 76.7482, 75.1310
bev  AP:78.1172, 70.6400, 67.5259
3d   AP:74.7528, 63.4462, 60.6359
aos  AP:0.77, 1.21, 1.43

Did not find any parameter differences studying a diff with the config file in https://github.com/open-mmlab/mmdetection3d/issues/871, leading me to attribute it to stochasticity in the training process. Or do you have some intuition for a reason as to the small but consistent difference?
Attaching the training log and processed config file for your reference
20210911_090425.log
centerpoint_kitti_baseline.txt

The follow-up KITTI experiment results (80 epochs, voxel size 0.05 x 0.05 x 0.10, batch size 8, single GPU)
Overall AP@easy, moderate, hard:
bbox AP:84.4814, 75.5839, 73.6057
bev  AP:76.4759, 68.6294, 65.4713
3d   AP:72.9873, 61.9473, 59.5183
aos  AP:0.87, 1.64, 1.90

The results improved and are now comparable to those reported in https://github.com/open-mmlab/mmdetection3d/issues/871, though in general 1~2 points lower. Will update the previous CenterPoint-KITTI  config files to reflect the changes.
Overall AP@easy, moderate, hard:
bbox AP:85,4418, 76.7482, 75.1310
bev  AP:78.1172, 70.6400, 67.5259
3d   AP:74.7528, 63.4462, 60.6359
aos  AP:0.77, 1.21, 1.43

Modified further inconsistencies with the config file in https://github.com/open-mmlab/mmdetection3d/issues/871 and launched a new run trying to match the result values.

sample_groups=dict(Car=12, Pedestrian=10, Cyclist=10) <--> sample_groups=dict(Car=12, Pedestrian=6, Cyclist=6))

post_center_range=point_cloud_range <--> post_center_limit_range=[-10, -50, -10, 80.4, 50, 10]

Optimizer parameters: betas=(0.95, 0.99)

Attaching the training log and processed config file for your reference
20210917_211652.log
centerpoint_005voxel_second_secfpn_4x8_cyclic_80e_kitti.txt

Results of the latest experiment.  Improved to be in general 0.5 - 1 points lower than values reported in https://github.com/open-mmlab/mmdetection3d/issues/871.
Overall AP@easy, moderate, hard:
bbox AP:83.4772, 77.5470, 74.7893
bev  AP:76.3518, 69.0049, 65.9117
3d   AP:73.1059, 62.9784, 59.6075
aos  AP:0.84, 1.59, 1.83

Planning on pushing a version of the config modifications that do not modify the base dataset config file configs/_base_/datasets/kitti-3d-3class.py.
Log and compiled config file
20210918_171159.log
centerpoint_005voxel_second_secfpn_4x8_cyclic_80e_kitti.txt

just a comment, it seems the output stride is important for centerpoint performance on KITTI. In current configs (nusc exps), we use 8x for voxelnet, but I found that 4x works a bit better (though slower and a bit more memory during training). I can get to about 78 moderate in this repo https://github.com/tianweiy/CenterPoint-KITTI/issues/9

@tianweiy Thank you for sharing your insight and your work on CenterPoint x KITTI!
Will try out your recommendation and check out the repository.
By the way, can you confirm if the feature map dimensions are appropriate for the KITTI point cloud data range? :thinking:
Comparing the visualization of the 3D point cloud and the target centre points plotted on the feature map, only a small subset of the feature map seem to be relevant. I also visualized an (unrelated) feature map in RGB that indicate the same concern.
I have not changed parameters relating to the feature map dimensions, at least intentionally.
Point cloud visualization

Target center points in feature map coordinates

Feature map visualization

By the way, can you confirm if the feature map dimensions are appropriate for the KITTI point cloud data range?

Which part do you want me to confirm? I agree that the center map seems super sparse compared to the whole map. Here the feature map dimension 8 and as I said above 4 should work slightly better.

Which part do you want me to confirm? I agree that the center map seems super sparse compared to the whole map. Here the feature map dimension 8 and as I said above 4 should work slightly better.

Ah, I just meant to ask if you found this odd as well. Understand now that it is likely related to the feature map dimension 8 --> 4 difference. Will confirm and thank you again :+1:

@tianweiy Tried out implementing the out_size_factor = 4 modification as you suggested.
Changing the value 8 --> 4 modifies the target feature map dimensions (200, 176) --> (400, 352). However, the feature map outputted by 'SparseEncoder' (middle encoder) remains (200, 176).
==> I modified the stride number 2 --> 1 in the second-last encoder convolution in order to increase the 'SparseEncoder' output feature map dimension to (400, 352) and reduced the output channels by 1/2 to conserve the same total amount of elements and thus feature dimension when rearranging the output tensor into shape (N, 256, 400, 352).
Does this correspond to your implementation? Sorry if I misunderstood something.
Currently running an experiment. Needed to reduce batch size 8 --> 2 to fit the model into memory, so I'm having doubts about the correctness of my implementation.
    pts_middle_encoder=dict(
        type='SparseEncoder',
        in_channels=4,
        sparse_shape=[41, 1600, 1408],
        output_channels=64,  <-- REDUCED FROM 128
        order=('conv', 'norm', 'act'),
        encoder_channels=((16, 16, 32), (32, 32, 64), (64, 64, 128), (128, 128)),
        encoder_strides=(2, 2, 1, 1),  <-- DROPS SECOND-LAST STRIDE 2 CONV
        encoder_paddings=((0, 0, 1), (0, 0, 1), (0, 0, [0, 1, 1]), (0, 0)),
        block_type='basicblock'),

@robin-karlsson0 Awesome work! Here is just a kind reminder that the aos number also seems strange. Please check whether the orientation estimation needs to be adjusted (possibly with opposite directions). After your benchmark is ready, we will help you review the code and transfer the benchmark to our refactored coordinate systems of v1.0.0.dev0.

@robin-karlsson0  I didn't change the 3d backbone and only add a 2x upsample at the end of the 2d backbone (before detection head). This should take less memory.
    pts_middle_encoder=dict(
        type='SparseEncoder',
        in_channels=4,
        sparse_shape=[41, 1600, 1408],
        order=('conv', 'norm', 'act')),
    pts_backbone=dict(
        type='SECOND',
        in_channels=256,
        layer_nums=[5],
        layer_strides=[1],
        out_channels=[128]),
    pts_neck=dict(
        type='SECONDFPN',
        in_channels=[128],
        upsample_strides=[2],
        out_channels=[128]),

@robin-karlsson0 I didn't change the 3d backbone and only add a 2x upsample at the end of the 2d backbone (before detection head). This should take less memory.

OK, thanks for sharing! Will try out just upscaling too, and compare with the modified 3D backbone experiment currently running (epoch 68/80, ETA 8h).

@Tai-Wang @KickCellarDoor Hello and sorry for the long absence. Worked on this as part of a part-time work, which I left after having acquired financial support. In the mean time I've been focusing on my primary research incl. a publication DL. Recalled these half-finished Open-MMLab  PRs and I'm again available to work towards completing them.
Please allow me some time to catch up and I'll address the reviews above :+1:

Hi @robin-karlsson0 @Tai-Wang @KickCellarDoor, thank you for your work on this feature, when do you think it will be merged?


traceroute command in the build/run image

Hello Team,
Can we please include the traceroute command in the run image ?
It will be easy to troubleshoot the network and FW related issue.
-Sameer

can somebody help on this ?

@doddisam hey there Sameer, can you discuss a bit more about your use case for needing this at run-time? Would it be helpful for all types of apps, or specific ones?
We usually take a conservative approach to adding new packages to the stack images in order to limit vulnerability surface area, so I'd really like to understand fully what the benefit will be here.
I see some associated CVEs with this package, like https://ubuntu.com/security/CVE-2023-46316, in which a fix is only available in the ESM (expanded security maintenance) version of the package which we cannot ship in the project.

@sophiewigmore Thanks for the reply.
I will be helpful  if we have in all types of apps which uses this stack. In our environment many DEV teams deploy apps and they connect to external database, messaging and redis etc. Quite often there will be some network related issue or FW issue and it will be helpful to have traceroute for troubleshooting. App teams can work with network or FW team directly and provide traceroute outputs to destination server.

@doddisam I'm not sure about this. I can see why including traceroute might be useful for debugging, but I'm also hesitant to add a package with a considerable CVE surface area to the stack when it would only be there for troubleshooting, and not for producing production-ready builds. @robdimsdale would you be able to weigh in?


[Feature request] Read /etc/sysctl.conf when starting Docker-Desktop in WSL

Tell us about your request
WSL does not automatically read sysctl.conf on startup. A service in a docker container might depend on a parameter set in sysctl.conf. Please have Docker-Desktop read and accordingly process sysctl.conf on startup.
Which service(s) is this request for?
Docker-Desktop for windows
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
https://stackoverflow.com/q/69214301/10071239
Are you currently working around the issue?
https://stackoverflow.com/a/69294687/10071239 Adding an according line, e. g. below, to .bashrc makes a workaround:
wsl.exe -d docker-desktop sh -c "sysctl -w vm.max_map_count=262144"
Additional context
Add any other context or screenshots about the feature request here.

The thread you linked suggests that this can be done in .wslconfig. Isn't that a better approach, because it makes it explicit and at the choice of the user? Or did you reject that approach for some reason?

Thanks for submitting your issue. This is not something Docker is considering working on and as such I'll close this issue.


Fix bump

null
Closes #733

@pitmonticone , ready to merge?

@teorth Yes, I've just merged main so let's wait for CI.


I think we should follow this guy's advice: https://github.com/isaacs/github/issues/750#issuecomment-242220908

I think we should follow this guy's advice: https://github.com/isaacs/github/issues/750#issuecomment-242220908

Actually, my advice there is somewhat outdated.  The current best practice is to search https://github.com/github/feedback/discussions: if you find a discussion for this, chime in there, & refer here (if not already linked); else, open 1 up to do that.
Originally posted by @TPS in https://github.com/isaacs/github/issues/750#issuecomment-872563253
Originally posted by @mail731212 in https://github.com/mail731212/kun731020/issues/8

Please submit the correct information, invalid information will cause the issue to close


Build pipeline

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

Pull with latest changes

Thanks


Maya: "Look" instance inside "Render" Instance causes Collecting errors during Pyblish of the Look/Render

I wanted publish look instance and also render turntable of the look via "Render" instance. So I did following...
Creating Look instance and Render instance using Creator in maya scene and then afterwards putting "Look" instance inside "Render" instance in Outliner (see Hierarchy below)
-RenderingMain
-LookMain
...caused following collecting errors:

Message:
'NoneType' object has no attribute 'group'
Line:
115
Traceback:
Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\collect_render.py", line 115, in process
AttributeError: 'NoneType' object has no attribute 'group'

[cuID:OP-3941]

Good catch!
To fix your particular case - that lookMain should go into the actual layer you'd like to attach it to. So for example into that Main set inside.
Nonetheless - this shows that the logic and error logging can be improved for the end user.
Likely it's best to log a clearer message self.log.warning("Ignoring invalid member of 'renderingMain': {}".format(layer)) or alike.
And potentially highlight to the user that it should maybe be moved into the layer-specific sets inside of it.

@LiborBatek was this issue resolved with #3816 and did that improve the logging message enough to be clear for the user?

I did try both cases putting Look instance into RenderMain and next to it and gives no warning at all :) just publishes ok in both cases.
But I think it was resolved to work in both cases.


Indicators_list and IPTT reports: If target is zero and actual is > zero, % Met field should say N/A

Affects: Indicator_list page and IPTT reports
While we do not permit LoP targets of zero, we do permit periodic targets of zero. This means that you can sometimes have a periodic target of zero and a periodic actual of > 0. Right now we do different things in different places. On the indicators_list page, we display a zero in % Met, but on the IPTT we leave it blank.
What we want to do in both cases when target = 0 and actual > 0 is to display N/A in the % Met field.
Please make sure this is the case for all target frequencies including LoP only, Midline/Endline and Event frequencies.

Looks like this works on indicator_list but not the Target vs Actuals IPTT.

Validated on the Target vs Actuals IPTT -- tested on both Annual and Midline/Endline, all 3 scenarios for each.


Adjusting inactivity timeout to keep-alive signal

Gnip sends a keep-alive signal each 30 seconds, so it is recommended that the stream reconnects if it takes longer than that to receive the signal.

bump


Wagtail 4

Release notes:
https://docs.wagtail.org/en/stable/releases/4.0.html

Fixed imports
Added support for wagtail 4
Updated documentation
Updated github workflows

Tests pass OK
Found 13 test(s).
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
.............
----------------------------------------------------------------------
Ran 13 tests in 0.104s

OK

@katdom13 could you please define WAGTAILADMIN_BASE_URL in the test app settings to sort out the warning you see in you tests run example?

Hi @zerolab ,
I have defined this in the test app settings. Please see this commit below.
https://github.com/torchbox/wagtail-content-import/pull/50/commits/cbeb53bc96c07dda5fbbfc24bf9dae7f27a00b52
Thank you!

Hi @zerolab,
I have attempted to fix some code for testing with postgres in the workflows. Can you please run the tests again? Thank you!

Left a few notes, nothing blocking from a Wagtail 4.x perspective, but the gist of it is we want to test against 4.1 as a freshly released LTS (but that can happen in a separate PR)

I have created some separate follow up PRs for including black in linting and testing wagtail 4.1.
I have left some comments on those PR for the relevant changes. If this could be merged, the changes there should be minimal.
Thank you!


Remove wildcard copies from docker

Alternative to #802

doesn't a directory like bootkube/manifests/manifests look strange :) ?

/assign @sttts
it seems like we have competing approaches on how to fix the issue. We need to choose one :)

/close
in favour of https://github.com/openshift/cluster-kube-apiserver-operator/pull/802


nixos/triggerhappy: add module for triggerhappy hotkey daemon

Motivation for this change
While actkbd is quite similar and we already have a NixOS module for it, triggerhappy allows specifiying keys by their names instead of keycodes which is much simpler. It is equally light and needs only one process for all input devices as new devices are added using an udev rule and announcing them to the triggerhappy daemon.
Things done
The new triggerhappy module is based on the actkbd module.

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

cc @taha

@GrahamcOfBorg build triggerhappy

Success on aarch64-linux (full log)
Attempted: triggerhappy
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0
shrinking /nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0/bin/th-cmd
shrinking /nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0/bin/thd
gzipping man pages under /nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0/share/man/
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0/bin
patching script interpreter paths in /nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0
checking for references to /build in /nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0...
/nix/store/hqxap8x9y8mn54x6i7rs4m2xpl0rdnh5-triggerhappy-0.5.0

Success on x86_64-linux (full log)
Attempted: triggerhappy
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0
shrinking /nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0/bin/th-cmd
shrinking /nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0/bin/thd
gzipping man pages under /nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0/share/man/
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0/bin
patching script interpreter paths in /nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0
checking for references to /build in /nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0...
/nix/store/kqlkn85f312kklnppvx21spkl5kg6zx6-triggerhappy-0.5.0

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: triggerhappy
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


Feature | Asynchronous requests

Introducing support for Guzzle's asynchronous requests in Saloon! 🎉
This PR introduces a new sendAsync method on the request/connector that you can use to return a Guzzle Promise.
$request = new GetUserRequest(userId: 1);
$promise = $request->sendAsync();

$promise->then(
    function (SaloonResponse $response) {
        // Handle successful response...
    },
    function (SaloonRequestException $exception) {
        $response = $exception->getSaloonResponse();

        // Handle unsuccessful response...
    },
)

Important Note
Typically, Saloon will return a response with the error inside of the response, however with promises, if an error occurs - Saloon will return the response in the rejection chain instead. Should this be the case? Or should we only reserve rejection for exceptions like ConnectException and always return responses, even if errored in the resolve callback?

@Sammyjo20 Regarding your note, and the way you handle the onRejection - I've only ever seen Exceptions returned, not thrownd.
Curious as I am, however, I started digging more into Guzzles code.
I can't fully grasp the whole flow (at least not by browsing it on GitHub), but.. it's interesting if throwing an Exception, like you do, would create a RejectionPromise, and, when returning instead, the FulfilledPromise is created (including for Exceptions).
Did you happen to test this scenario?
This would explain a super-annoying thing I had with Laravel the other week, when the onFulfilled callback received an Exception instead of the Response I was expecting.

Yes, so it follows the A+ standard for promises, one of the rules states that if something is thrown in the reject handler, it will be passed to the reject handler of the next "then", however if something is returned in the reject handler, it will be passed to the resolve of the next handler, how confusing! So sadly I can only have an exception in the "reject"...

Thanks for the clarification. That does explain the issue I had.
I can see the use for either case. But both works for me.
Thanks for looking into async requests so quickly. 🙂

I was going to see if I can also roll pools into this too, as it would help the other guy who originally posted the issue.
No problem! I wanted to tackle it but I didn’t know what it was admittedly, so thank you for the learning opportunity!


After parsing the XML string, the decode method fails

I use the following code to parse the XML string into SVG and render it to the DOM node
/**
 * @type renderXmlType
 */
export type renderXmlType = (this: instanceObject, xml: string) => void;

export const renderXml: renderXmlType = function (xml: string) {
    const xmlDoc = new DOMParser().parseFromString(xml, 'text/xml');
    // const xmlDoc = xmlUtils.parseXml(xml);
    const decoder = new Codec(xmlDoc);
    decoder.decode(xmlDoc.documentElement, this.graph.getDataModel());
};

const container2 = document.createElement('div');
container2.style.flex = '1';
document.body.appendChild(container2)
const _graph2 = graph.init(container2);
const xml = `<GraphDataModel><root><Cell id="0"><Object as="style"/></Cell><Cell id="1" parent="0"><Object as="style"/></Cell><Cell id="2" value="test1" vertex="1" parent="1"><Geometry _width="100" _height="100" as="geometry"/><Object align="right" shape="halfCircle" as="style"/></Cell><Cell id="3" value="test2" vertex="1" parent="1"><Geometry _x="300" _y="100" _width="100" _height="100" as="geometry"/><Object shape="halfCircle" as="style"/></Cell><Cell id="4" value="test2" vertex="1" parent="1"><Geometry _y="220" _width="100" _height="100" as="geometry"/><Object as="style"/></Cell><Cell id="__edge_1__" value="edge1" edge="1" parent="1"><Geometry relative="1" as="geometry"/><Object as="style"/></Cell><Cell id="__edge_2__" value="edge2" edge="1" parent="1"><Geometry relative="1" as="geometry"/><Object as="style"/></Cell><Cell id="__edge_3__" value="edge3" edge="1" parent="1"><Geometry relative="1" as="geometry"/><Object as="style"/></Cell></root></GraphDataModel>`;
_graph2.renderXml(xml);

But it did not succeed
I debug the source code to get this Code:
    decode(node, into) {
        this.updateElements();
        let obj = null;
        if (node != null && node.nodeType === NODETYPE.ELEMENT) {
            let ctor = null;
            try {
                // @ts-ignore
                ctor = window[node.nodeName];
            }
            catch (err) {
                // ignore
            }
            const dec = CodecRegistry.getCodec(ctor);

            if (dec != null) {
                obj = dec.decode(this, node, into);
            }
            else {
                obj = node.cloneNode(true);
                obj.removeAttribute('as');

            }
        }
        return obj;
    }

Where ctor = window [node. NodeName]; In this code, ctor is undefined because node.nodename is the method name. For example, when resolving < GraphDataModel>, node NodeName === 'GraphDataModel', but the "GraphDataModel" class does not exist on the window object, so the subsequent parsing fails, including the possibility of obtaining "Cell" and "Geometry " methods.
My solution is:
import { Cell, Geometry, GraphDataModel } from "maxgraph"
declare global {
    interface Window {
        GraphDataModel: typeof GraphDataModel;
        Cell: typeof Cell;
        Geometry: typeof Geometry;
    }
}
window.GraphDataModel = GraphDataModel;
window.Cell = Cell;
window.Geometry = Geometry;

After this configuration, it can be displayed normally
Thank you for reading

The encode/decode XML feature has not been fully migrated from mxGraph and AFAIK, this part has not been tested a lot.
ctor = window[node.nodeName]; is directly taken from the mxGraph implementation that put all its object values in the window instance.
In maxGraph, the object values aren't (and will never be) available there. So the decode implementation should be fixed probably with the following code  (if aliases are still working) - there no guarantee at all this works:
const ctor = node.nodeName;
const dec = CodecRegistry.getCodec(ctor);

I have noticed that in the encoded xml provided in the description of the issue that some objects are not correctly encoded, for instance the style. This should also be fixed.
<Cell id="4" value="test2" vertex="1" parent="1">
   <Geometry _y="220" _width="100" _height="100" as="geometry"/>
   <Object as="style"/>
</Cell>

When using mxGraph, the xml contains the style information in an attribute of mxCell
<mxCell id="5rR2ExFde4BuYNg8DIuo-1" value="Shape 1"
              style="rounded=0;whiteSpace=wrap;html=1;fillColor=#E6E6E6;dashed=1;" parent="1" vertex="1">
    <mxGeometry x="120" y="119" width="120" height="50" as="geometry"/>
</mxCell>

The encode/decode XML feature has not been fully migrated from mxGraph and AFAIK, this part has not been tested a lot.
ctor = window[node.nodeName]; is directly taken from the mxGraph implementation that put all its object values in the window instance. In maxGraph, the object values aren't (and will never be) available there. So the implementation should be fixed probably with the following code (if aliases are still working) - there no guarantee at all this works:decode
const ctor = node.nodeName;
const dec = CodecRegistry.getCodec(ctor);

I have noticed that in the encoded xml provided in the description of the issue that some objects are not correctly encoded, for instance the . This should also be fixed.style
<Cell id="4" value="test2" vertex="1" parent="1">
   <Geometry _y="220" _width="100" _height="100" as="geometry"/>
   <Object as="style"/>
</Cell>

When using mxGraph, the xml contains the style information in an attribute of mxCell
<mxCell id="5rR2ExFde4BuYNg8DIuo-1" value="Shape 1"
              style="rounded=0;whiteSpace=wrap;html=1;fillColor=#E6E6E6;dashed=1;" parent="1" vertex="1">
    <mxGeometry x="120" y="119" width="120" height="50" as="geometry"/>
</mxCell>

ok, Thank you for your reply

May be fixed by #125


Use isNull rather than eq when checking for null.

Query.eq with a null value does not do as expected; use the more specific Query.isNull restriction.

This should me merged before #2 .


Why do I get close to 0 rmsd for all the compounds I am testing?

Hi,
For almost all of the compounds I am testing on, the RMSD is almost close to 0 for all of them, but it is extremely unlikely that this is accurate.
I've checked if it is because the compounds I'm testing are already in the training set. I downloaded the latest version of pdbbind. It is true that for some of the compounds, they are in the training set, but for most of them they are not.
I also want to mention that I am performing diffdock with frozen torsion angles as per issue raised previously: https://github.com/gcorso/DiffDock/issues/142#issue-1807791164
The compounds I am docking are originally obtained from bound co-crystals and separated into two molecules. This is likely to reduce rmsd, but I don't expect it to reduce it to near zero (most of the values are around 0.00xxx).
Is there any possible explanation for this? Did freezing the torsion angles as per the linked issue somehow remove the randomness used for docking?
Thanks in advance

Hi,
any suggestions as to why this is? I still can't seem to figure out what the problem is. Random initialization at the start seems to be done properly, and the diffusion process looks to be working from the visualization. The results look highly suspicious though.

How are you getting this value "0.00xxx"
The filenames should only have two decimal points, if I recall correctly.
Do you have negative controls in your experiment?
You could also try something like PoseBusters to check the feasibility of the docks - https://posebusters.readthedocs.io/en/latest/

The numbers reported in your original paper seem much more reasonable.
Have you also tested with the same compounds, what the results would be if the torsion angles were frozen? Is it possible that most of the errors are actually from incorrect torsion angles, and if it is frozen, it aligns in fact very well?

My bad, something was wrong with my RMSD calculation


Ignore "time_continue" parameters in youtube's URL

In some cases we exploring webpages and see a youtube video. It's interesting and we click the Youtube Logo to watch the video on youtube's own site.
In these cases the url will mostly have another parameters "time_stamp=xxx", like:
https://www.youtube.com/watch?time_continue=50&v=qbcppLD0Kl0
It will make a error if you paste the url directly to youtube-dl in command line.
Imho it should be enough just ignoring the parameter, making the url to be https://www.youtube.com/watch?time_continue=50&v=qbcppLD0Kl0.

It's already ignored.

Well, that might be the other error, then. I'm using the version 2<IP_ADDRESS> for windows.

https://github.com/rg3/youtube-dl#video-url-contains-an-ampersand-and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command


nydus performance tracing

We need a mechanism to collect the time and resource consumption of nydus at each stage of build time and run time to give us insight into the performance impact of development iterations, identify performance bottlenecks, etc. The main requirements are as follows.

The ability to count the time consumed by nydus-image/nydusd at each stage in span format.
Statistics on memory usage, CPU, and network requests.
The ability to present performance data in report form and compare it with the previous result.

It should be noted that when adding a tracepoint, it is as least invasive to the code as possible and does not lose too much performance, or there is a switch to control the trace.
Referenceable tools or libraries:

https://github.com/tikv/minitrace-rust
https://opentelemetry.io/
https://www.jaegertracing.io/
https://developer.aliyun.com/article/799040

Is there anyone working on this? Maybe I can help with it. @imeoer

Hi Qi, I'm working on it. But we can collaborate. @yawqi

Is there anyone working on this? Maybe I can help with it. @imeoer

Hi Qi, I'm working on it. But we can collaborate.

@yawqi @wraymo Thanks! We can split it into the two sub-tasks, "trace collection" and "cpu/memory/network requests statistics", Which one you prefer?

I'd prefer "trace collection"

OK, I will look into the "cpu/memory/network requests statistics".

@wraymo @yawqi Thanks! Any specific design doc can be committed here first and discussed together.

Hello 👋 I haven't seen any of the tracing bits land yet, is there a plan to use something like opentel for this. Do you need anything, I am happy to help out on this as we could really use better insight into these bits, especially:

The ability to count the time consumed by nydus-image/nydusd at each stage in span format.

Hello 👋 I haven't seen any of the tracing bits land yet, is there a plan to use something like opentel for this. Do you need anything, I am happy to help out on this as we could really use better insight into these bits, especially:

The ability to count the time consumed by nydus-image/nydusd at each stage in span format.

@lilic Are you talking about network performance trace? You can try using the nydusctl metrics backend --sock /nydusd.sock command to inspect the number of HTTP requests called by nydusd, as well as metric info such as read time distribution.

@imeoer thank you! That is good to know! But we need a way to send tracing data so we can see performance over time, so open-tel tracing for example or more metrics would be useful for us.

@lilic nydusd exported some metrics by an API, this is also the data source of nydusctl:
https://github.com/dragonflyoss/image-service/blob/f3cdd071b01ea5d2086e376a7b2bfee3ee233360/api/openapi/nydus-api-v1.yaml#L241
But indeed we'd better make it get in open tracing, unfortunately no one is doing the job yet. :(

@lilic Here is an example to get the backend metric:
https://github.com/dragonflyoss/image-service/blob/f3cdd071b01ea5d2086e376a7b2bfee3ee233360/smoke/tests/tool/nydusd.go#L384C18-L384C18

@imeoer I see, I thought it was Prometheus metrics so I was confused why I couldn't find them when looking at /metrics endpoint. Thanks for that. Sadly that doesn't work for me, still looking into it. But I get the following error when trying that:
~ # nydusctl --sock=/run/containerd-nydus/system.sock --raw metrics backend
Error: deserialize: trailing characters at line 1 column 5

We can move this to slack so I don't spam this issue.
I did want to look into adding tracing to at least our fork and if it works for us, then contributing it to here.


NPE while trying to get connectionId

I'm trying to use stheto with glide, but images is not loading.
I starting to look into source code and looks like there is npe while trying to get connection id:
StethoInterceptor.java:49
response = chain.proceed(request);  // now connection is closed

StethoInterceptor.java:62
Connection connection = chain.connection(); // so this is null now

NetworkEventReporterImpl.java:137
// and this is triggers npe in connectionId()
responseJSON.connectionId = response.connectionId();

That seems reasonable, but strange we aren't seeing this more commonly.  Seems easy enough to fix however by just sampling the connection id before proceed and then recalling it.

@jasta thanks
I looked again, maybe it is not really a bug. But maybe something that could be nice to fix anyway.
So I've been trying stetho for some time, and it didn't work for me with glide, so I start trying to use interceptors() and networkInterceptors() and today I decided to try it again and updated all libs: stetho, glide-okhttp, okhttp, and looks like I left interceptors().
Changing it to networkInterceptors() helped, now it works!


Update tools.html for "CSAF Perl Toolkit"

To add "CSAF Perl Toolkit"
fixes #62

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


"LVGL.Simulator" The name has a bug

GIT commands do not support stripes '.' The directory path of

This issue is fixed by renaming the project name to LvglWindowsSimulator.
https://github.com/lvgl/lv_port_win_visual_studio/commit/aea18daaab864499576da29a60f82c6d579cc851
Kenji Mouri


Add Indonesian localization

This PR will add Indonesian localization and solved #2331.

Great, thanks for the contribution!
I will wait for a bit and see if there are any other Indonesian users who would like to cross-check this translation. At the same time, will hire someone to check the translations! Thanks!

@danninov @mary-ext @Thinkbyte1024 How do we feel about the state of this localization right now? Are there any pending discussions to be resolved? Or is it good to be merged?

@danninov Do you use other apps in Indonesian? For example, I did the translations for Hindi and I kept a lot of english words because the translations weren't used often in other apps. Would be good to check other apps.

@danninov And do those apps use the word "Feed"?


Forced Pod install creates recursive check that creates build issues

Using Flutter master
Mac OS
flutter build will run pod install which creates a Framework Search Paths entry that is recursive. i.e.: $(PODS_ROOT)/**. With certain plugins (e.g. Firebase) this will lead to the following build error:
Argument list too long: recursive header expansion failed at /<ios project directory>/Pods/.symlinks/plugins/firebase_storage-0.1.4/android/build/intermediates/classes/debug/com/google/firebase/storage/api.

Removing the recursive entry will allow the build to complete successfully.

cc @mravn-google, may be related to #14748

@lukef I cannot reproduce with current Flutter master, Cocoapods 1.5.0, Xcode 9.3,
dependencies:
  google_sign_in:
  firebase_admob:
  firebase_analytics:
  firebase_auth:
  firebase_core:
  firebase_messaging:
  firebase_storage:
  flutter:
    sdk: flutter

If you can still reproduce, please provide more details on your setup.


Draco support

The auditor doesn't seem to be able to process glTF (non-binary) and GLB with Draco compression.

Thanks for the report. I think I found the source of the issue and asked the Babylon.js team for help: https://forum.babylonjs.com/t/what-pluginextension-string-should-be-used-for-draco-compression-with-base64-data-in-sceneloader-appendasync/39074


BleWinrtDll.cpp:501 SubscribeCharacteristicAsync catch: The attribute cannot be written.

hi when i press subscribe it returns this error
is there any solution for this
thanks

For investigation, you can download and run the Microsoft's Bluetooth Low Energy sample and see whether subscribing works there. If the demo works, it should be fixable in this repo.
Did you already try subscribing with another platform/program?

I was able to subscribe in Microsoft's sample, but I have the same error in Unity

Does this mean in Microsoft's sample the subscription failed with the same error?

I had problem in Unity (The attribute cannot be written), then I've checked Microsoft's sample and everything was working there and after that for some reason error in Unity disappeared. However I still cannot get characteristc values from some BT devices.


Allow negative NavigationAgent2D path debug line_width for thin lines

Allows the line_width for NavigationAgent2D path debug to go negativ for thin line rendering.
2D line rendering has this quirk where on a low resolution game even a 1 pixel line is gigantic and it only stays a thin line at any resolution while negativ.

LGTM, assuming 3D doesn't have a similar quirk.

3D has no line width rendering.

This should be cherry-picked for Godot 4.0 cause the 2D NavigationAgent path debug is currently not useable with small resolution games.

@YuriSizov
What you linked uses the RenderingServer::canvas_item_add_line() function that added a more complex 4 point line draw, e.g. what is used by canvas item draw line function. It also uses the -1 workaround for the quirk cause with width below 0 it reduces to a two point line render.
The NavigationAgent2D is a node, not a canvas item, and it uses RenderingServer::canvas_item_add_polyline() which is more efficient for long, multi-segment lines with width cause that is what a typical navigation path usually is. This functions also uses a two point line render when width is < 0.

Indeed it does also use the negative trick. It's just doesn't feel correct to expose a float that can go to -1.0 to trigger this trick. In fact, why does it need to be a float, if we hint it with the step of 1? (And same with debug_path_custom_point_size)

@YuriSizov We need to use a negative number because it triggers a difference in behaviour. Positive floats are used to specify a line width that scales while anything below 0 is used to flag that hardware lines should be used which have a fixed width of 1 regardless of scale. That's exactly what https://github.com/godotengine/godot/pull/73897 is doing. By passing -1.0 it flags for the rendering to use hardware lines (2-point primitves) instead of quads (4-point primitives).
Do you have a suggestion for a way to expose this in the NavigationServer that would be more correct in your view?

The debug uses a float for the width because the RenderingServer canvas functions also all use floats.

Do you have a suggestion for a way to expose this in the NavigationServer that would be more correct in your view?

You what now? What has the NavigationServer to do with this.

Changed the steps from 1 pixel to 0.01, also allowed or_greater.
When point size is set to zero the rect render gets disabled now.

The debug uses a float for the width because the RenderingServer canvas functions also all use floats. Sure can remove the 1 pixel step, this was just added cause I expected 2D users to want to stick with pixels.

@smix8 I wasn't suggesting we should remove the step, quite the opposite 🙃 I understand that the low level API uses floats, I'm just concerned with how we expose a high level setting to the end user. It's fine-ish that this awkward API exists in the RenderingServer, it's not what most would interact with.
But I guess there is no good solution to the high level usability within the scope of this PR right now.

Thanks!

Cherry-picked for 4.0.1.


Fix Python 3.10 wheel for Windows

For some reason the wheel build process fails for Python 3.10 on Windows: https://github.com/severinsimmler/chaine/runs/5529016996?check_suite_focus=true

Looks like it's not really related to Windows: https://github.com/severinsimmler/chaine/runs/6025884755?check_suite_focus=true


Provide a relative path to api specification file

At this moment we have to provide an absolute path to read specification file.
Let's fix this.

:+1:


doesn't work with readthedocs theme

It seems to me that if i set my theme to readthedocs, it simply doesn't work. The code seems to be injected in each page (i can see <script src="../js/open_in_new_tab.js"></script> in the body of the pages), but yet pages are opened in the same tab.
If i change the theme to material it doesn't occur.

Hi, please try it after package upgrade.
I have fixed path starting with / → <script src="/js/open_in_new_tab.js"></script>

https://pypi.org/project/mkdocs-open-in-new-tab/1.0.6/

amazing, this fixed it for me! Thank you!


moor  near "ON": syntax error on insertOnConflictUpdate method

I am trying to use moor on my project . This is my table:
@DataClassName("LocationTable")
class LocationTables extends Table {
  TextColumn get locationUuid => text()();
  RealColumn get latitude => real()();
  RealColumn get longitude => real()();
  TextColumn get locationCatUid => text()();
  TextColumn get title => text()();
  TextColumn get mobile => text().nullable()();
  TextColumn get phone => text().nullable()();
  TextColumn get description => text().nullable()();
  DateTimeColumn get createdAt => dateTime()();

  @override
  Set<Column> get primaryKey => {locationUuid};
}

and this is it's dao:
@UseDao(tables: [LocationTables])
class LocationDao extends DatabaseAccessor<Database> with _$LocationDaoMixin {
  final Database db;
  LocationDao(this.db) : super(db);

  Future insertTask(Insertable<LocationTable> location) =>
      into(locationTables).insert(location);

  Future insertOrUpdateLocation(Insertable<LocationTable> location) =>
      into(locationTables).insertOnConflictUpdate(location);

Now I am trying to use insertOrUpdateLocation . In android emulator everything is fine and I didn't get error but when I am using My mobile (Samsung A31) I got this error:
I/flutter (15938): Moor: Sent INSERT INTO location_tables (location_uuid, latitude, longitude, location_cat_uid, title, mobile, phone, description, created_at) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)   ON CONFLICT(location_uuid) DO UPDATE SET location_uuid = ?, latitude = ?, longitude = ?, location_cat_uid = ?, title = ?, mobile = ?, phone = ?, description = ?, created_at = ?' args [02e98b69-df0e-4f35-a667-c5a27ac925e9, 35.73528356437848, 51.487202763671874, b5671816-1e48-4c80-a2e1-c6700d4f5dc2, ubbj, 666666, 6633, htyh,<PHONE_NUMBER>, 02e98b69-df0e-4f35-a667-c5a27ac925e9, 35.73528356437848, 51.487202763671874, b5671816-1e48-4c80-a2e1-c6700d4f5dc2, ubbj, 666666, 6633, htyh,<PHONE_NUMBER>]}
E/flutter (15938): #0      wrapDatabaseException
package:sqflite/src/exception_impl.dart:11
E/flutter (15938): <asynchronous suspension>
E/flutter (15938): #1      BasicLock.synchronized
package:synchronized/src/basic_lock.dart:34
E/flutter (15938): <asynchronous suspension>
E/flutter (15938): #2      SqfliteDatabaseMixin.txnSynchronized
package:sqflite_common/src/database_mixin.dart:346
E/flutter (15938): <asynchronous suspension>
E/flutter (15938): #3      _ExecutorWithQueryDelegate._synchronized
package:moor/…/helpers/engines.dart:25
E/flutter (15938): <asynchronous suspension>
E/flutter (15938): #4      InsertStatement.insert.<anonymous closure>
package:moor/…/statements/insert.dart:70
E/flutter (15938): <asynchronous suspension>
E/flutter (15938): #5      InsertStatement.insert
package:moor/…/statements/insert.dart:69
E/flutter (15938): <asynchronous suspension>
E/flutter (15938): #6      PersistUserLocationInfoViewModel.saveUserInfoLocation
package:easy_life/…/persist_user_location_info/persist_user_location_info_view_model.dart:46
E/flutter (15938): <asynchronous suspension>
E/flutter (15938):

I am using `  moor_flutter: ^3.1.0` and  `moor_generator: ` . and my flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.0.2, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0-rc1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.54.3)
[✓] Connected device (3 available)

• No issues found!

Additionally I have a moor file for this table:
import'package:easy_life/database/location_tb.dart';

CREATE INDEX location_uuid_index ON location_tables (location_uuid);

And I added moor file to database class :
@UseMoor(include: {
  'index.moor'
}, tables: [
  LocationTables,
  LocationCategories,
], daos: [
  LocationDao,
  LocationCategoriesDao,
])
class Database extends _$Database {
  Database()
      : super(FlutterQueryExecutor.inDatabaseFolder(
            path: 'db.sqlite', logStatements: true));
  @override
  int get schemaVersion => 1;

  @override
  MigrationStrategy get migration => MigrationStrategy(
        onCreate: (m) async {
          return m.createAll();
        },
        onUpgrade: (migrator, from, to) async {},
        beforeOpen: (details) async {
          await customStatement('PRAGMA foreign_keys = ON;');
        },
      );
}

Interesting! I'm wondering if that device uses an old sqlite3 version without support for upserts. The minimum required sqlite version is 3.24.0, released on 2018-06-04. Can you run and print a custom query with select sqlite_version(); to find out?
If it turns out to be because of an old version, I think the only way around that is to use sqlite3_flutter_libs together with the moor/ffi.dart library. It uses dart:ffi to bind to an sqlite3 version you ship with your app, instead of using the one from the OS.

Moor: Sent SELECT COUNT(chats.total_unread) FILTER (WHERE chats.is_active = ?) AS "c0" FROM chats; with args [1]
E/SQLiteLog( 8884): (1) near "AS": syntax error in "SELECT COUNT(chats.total_unread) FILTER (WHERE chats.is_active = 1) AS "c0" FROM chats;"
this error appear to my when i used emulator with android version 30 and also appear to me when i used my phone Samsung Note8.
so, How  use sqlite3_flutter_libs together with the moor/ffi.dart in pubspecl file
i used
  moor: ^4.2.0
  moor_flutter: ^4.0.0-nullsafety
  sqflite: ^2.0.0+3
  sqlite3_flutter_libs: ^0.4.1

Note :
this way i used to open connection
AppDatabase() : super(FlutterQueryExecutor.inDatabaseFolder(path: 'db.sqlite', logStatements: true));

The filter syntax was added in sqlite version 3.30.0, released on 2019-10-04. That's still fairly recent considering Android's pace of keeping up with things, it looks like Android 11 ships version 3.28.0.
There's some documentation on how to migrate from moor_flutter to moor/ffi here.

Interesting! I'm wondering if that device uses an old sqlite3 version without support for upserts. The minimum required sqlite version is 3.24.0, released on 2018-06-04. Can you run and print a custom query with select sqlite_version(); to find out?
If it turns out to be because of an old version, I think the only way around that is to use sqlite3_flutter_libs together with the moor/ffi.dart library. It uses dart:ffi to bind to an sqlite3 version you ship with your app, instead of using the one from the OS.

After replacing moor-flutter with moor/ffi.dart now sqlite version is 3.34.1 and On my Samsung A31 my problem is gone . I just replace
  moor: ^3.0.0
  sqlite3_flutter_libs: ^0.4.1

instead of
moor_flutter: ^3.1.0
and replace all  import 'package:moor_flutter/moor_flutter.dart'; to import 'package:moor/ffi.dart'

@tazik561 was your app in production when you migrated from moor_flutter to moor? Did you faced any issues?

@tazik561 was your app in production when you migrated from moor_flutter to moor? Did you faced any issues?

I do not try in production yet but in developing and testing mode I didn't  faced with any error

Okay. So you just changed the packages in pubspec.yaml and updated your database connection.

Okay. So you just changed the packages in pubspec.yaml and updated your database connection.

yes, I mentioned here https://github.com/simolus3/moor/issues/1106#issuecomment-805645479

Okay. Thanks


Redraw on item list custom bg/fg colour change

Updating an ItemList items custom background or foreground colour was not redrawing.

Thanks!

Cherry-picked for 3.4.


Converted audio bitrate does not match the parameters

Hello there,
I have some files that have DTS 5.1 tracks in them with a bit rate of ~1500 kb/s.
My ini file is set to convert them to AC3@384kbps but after the convertion, if I check the file with MediaInfo, the audio track is at 640kbps.
max-audio-channels =
audio-codec = ac3
audio-language =
audio-default-language = eng
audio-channel-bitrate = 384
audio-filter =

How can I ensure they will be set to the bitrate I specified?
Or maybe I'm using the settings wrong?
Thanks!

It should be based on the channel bitrate * the number of channels. Are you sure the track isn't being converted to less channels?
Additionally AC3 usually has a much smaller bitrate for the same quality level as DTS, so I wouldn't aim to have your AC3 tracks have the same bitrate as DTS, its probably wasting space.

Hello and thanks for your answer.
Yes, I can confirm that the number of tracks has been preserved (6 channels, AC3).
I understand the bitrate differences between DTS and AC3, hence my preference for the smaller AC3 tracks sacrificing little quality in the process in favour of a smaller file. I found that 384kbps is a good compromise. I also have compatibility issues with my hardware setup here that I need to take into consideration.
In any case, based on your formula, the final calculation is not correct in my case, since 384*6 is 2304, but the final file has an AC3 track of 640kbps
By the way, could you kindly tell me what is the command line you use for the conversion? If I remember correctly, there was a bug with ffmpeg that would mixup the channel orders when converting audio tracks from DTS to AC3.
Thank you!

Hello again, it's all good! Thanks.
On a side note, I have some MKV/MP4 with AC3 tracks but with higher bitrates (640kbps)
I noticed that the script simply copy the track over without downmixing, even though it's in the parameters.
Is there a way to force downmixing to my desired bitrate?
Thanks!


Add status field to Orders

To facilitate creating pledges for collectives (see opencollective/opencollective#1168), this PR adds a status field to Orders:

PENDING (default)
PAID (one-time completed orders)
ACTIVE (subscriptions)
CANCELLED
REJECTED
ERROR

The migration also includes code to update existing Orders.

Coverage increased (+0.04%) to 71.156% when pulling b2a9f0ce27f3b1758c58fdef428240f799220418 on order-status into db778be1e0b8f12231b0b39ee7371f9542d03ebf on master.


Installing from NPM - example is not plug and play

There's a few issues that I had to fix before the example file worked. When I do 'npm install package' I expect to go into the example folder and be able to run the examples instantly, and I wanted to make it known what needs to be fixed:
Line numbers refer to example/index.html

this package is not self-containing, and doesn't contain any node_modules folder, therefore angular.js was not included correctly in the example/index.html initially. In my case, I am on an httpS apache server and lines 293 and 294 failed to load, couldn't fetch from http: while on https. Perhaps nitpicky, but npm packages tend to themselves have node_modules folders.

the .js file 'js/libs/angucomplete-alt.js' file referenced in line 295 DNE, that should instead point to '../angucomplete-alt.js'

the .css file 'css/angucomplete-alt.css' referenced in line 11 DNE, it should point to '../angucomplete-alt.css'

angular and angular-touch ngTouch are not listed as devDependencies in package.json

I can create a pull request for these issues but not at this moment in time, perhaps tonight

Updated README about how to run examples.


Custom migration dir

New Features
Allow customizing the migration directory in sea-orm-migration CLI. This allow embedding migrations to an existing crate (and/or inside a subdirectory) instead of enforcing a separate crate.
This also aligns the behavior of the tool with sea-orm-cli, where the migration directory is already customizable.
Changes
The entrypoint was adjusted as to facilitate testing, and tests are added for the migrate command.
The migration directory can be specified via command line argument or environment variable, but the same default value (./) is still used if unspecified.

@tyt2y3 @billy1624 could you check this one please?

Closing due to no response / lack of interest

thats so sad :/


Correlation Id for Update Options via PowerShell  - eg Update-AzureRMvm

Hi, I am trying go grab the correlation Id from resource update/modification operations performed via PowerShell, how can I code that. - Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8ffeaaf5-1859-90e1-6451-aca6d7fb34b1
Version Independent ID: 43849bff-28fe-661c-be86-d8d355ac0584
Content: Deployment operations with Azure Resource Manager
Content Source: articles/azure-resource-manager/resource-manager-deployment-operations.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@SharmainePopov Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

@SharmainePopov - thanks for the good question. Here is how you get the correlation ID:
(Get-AzureRmResourceGroupDeployment -ResourceGroupName mygroup -DeploymentName azuredeploy).CorrelationId
I'll add that the article.

Hi, please don’t close this. As per my previous response – when I use powershell to update a vm with update-azurermvm, there is no deployment or deployment name to reference.
Thanks
Sharmaine Popov
Cloud Solution Architect |Microsoft Canada Inc. | sharmaine.popov<EMAIL_ADDRESS>|<PHONE_NUMBER>
From: PRMerger15<EMAIL_ADDRESS>Sent: Friday, September 28, 2018 4:43 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Sharmaine Popov<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Correlation Id for Update Options via PowerShell - eg Update-AzureRMvm (#15816)
Closed #15816https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F15816&data=02|01|Sharmaine.Popov%40microsoft.com|f5a048c3b813467356e608d62582e9d8|72f988bf86f141af91ab2d7cd011db47|1|0|636737641531834731&sdata=SWnbDleoetMBDfeSOvAzItADoZ9osg53R1zUpGbe0so%3D&reserved=0 via 7b86dd86a15019d1e43278068477886e220292d9.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F15816%23event-1874425152&data=02|01|Sharmaine.Popov%40microsoft.com|f5a048c3b813467356e608d62582e9d8|72f988bf86f141af91ab2d7cd011db47|1|0|636737641531844743&sdata=f1SOY2bgwjgR1IDxhBfxqgKnYZVo%2B4b%2BZLOVmuM5exg%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAhFW2nQr0K8L6d6VH8Wupi9RFT_JjagJks5ufom2gaJpZM4W-w98&data=02|01|Sharmaine.Popov%40microsoft.com|f5a048c3b813467356e608d62582e9d8|72f988bf86f141af91ab2d7cd011db47|1|0|636737641531854756&sdata=v0598NIlCJ3E9CtqZoab1FqVcFe3kTejwRFUwR%2Btut0%3D&reserved=0.

You can see correlation IDs through the
Activity Log

Well yes but we need to automate extraction/capture  of those correlation ids as part of the powershell scripts doing the update.  Looking them up manually is not a solution. How can I get the correlation id associated with an update in an automated way?
Sharmaine Popov
Cloud Solution Architect |Microsoft Canada Inc. | sharmaine.popov<EMAIL_ADDRESS>|<PHONE_NUMBER>
From: Tom FitzMacken<EMAIL_ADDRESS>Sent: Saturday, September 29, 2018 7:49 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Sharmaine Popov<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Correlation Id for Update Options via PowerShell - eg Update-AzureRMvm (#15816)
You can see correlation IDs through the
Activity Loghttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-resource-manager%2Fresource-group-audit&data=02|01|Sharmaine.Popov%40microsoft.com|9d2504bf5a5a471c520008d6260188e7|72f988bf86f141af91ab2d7cd011db47|1|0|636738185361086597&sdata=lSxY%2Bq33PYL59A4MJFgESkHsgKwGAeHSz2UXKjOWKII%3D&reserved=0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F15816%23issuecomment-425638912&data=02|01|Sharmaine.Popov%40microsoft.com|9d2504bf5a5a471c520008d6260188e7|72f988bf86f141af91ab2d7cd011db47|1|0|636738185361096602&sdata=Uv7OrsxLzGabFPbTAVX1LdcfKDIzDa8OUCncg%2BKLjEs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAhFW2srojN1RGqldw2zZLiO67vPynbJxks5uf14mgaJpZM4W-w98&data=02|01|Sharmaine.Popov%40microsoft.com|9d2504bf5a5a471c520008d6260188e7|72f988bf86f141af91ab2d7cd011db47|1|0|636738185361106614&sdata=oTZZP5QR8IiQ9mWGG2ZP7PPrHe84O2G%2FMeznFyPnKXA%3D&reserved=0.


add reddit link to socials

Wee have a (tiny) Reddit now in case someone neeeds it. Please add it to the socials and widen them to 5/row instead of the current 4/row.
Additional context
https://www.reddit.com/r/IdrinthApiBench/

Hi, I can handle it, please assign me

sure, go right ahead! @KirilCycle


make main functions GPU compatible; not tested; next Q, R, S functions

Purpose
Make coalescence computations gpu compatible.
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.
I have read and checked the items on the review checklist.

Make moments a Tuple of Tuples (as in condensation/sedimentation tendencies) instead of SMatrix
Use M from the new style of CoalescenceTensor to get the order of the moments needed
In get_finite_2d_integrals, consider doing two maps: first, just compute the lower right triangle; second, copy those to the upper right triangle
Maybe try to make the Q, R, S computations a bit more reasonable? Consider adding helper functions

Let's also check on the 3_modes and 4_modes test cases to make sure they are working as expected

Let's also check on the 3_modes and 4_modes test cases to make sure they are working as expected

There was a minor bug in the constructor of CoalescenceData: it used to normalize kernels twice. Now the results look correct again.


Release v0.1.31

Do you have some news about this release please?
Thanks in advance!

@rsicart waiting for someone to merge this. I can't self-merge.

@tylerauerbeck @fishnix can you check this out?

If that can help,
Comparing with the diff of the last release, LGTM :+1:


Fuzz resources

Coverage increased (+0.01%) to 78.977% when pulling 061777d7831182a52a0a04991590ace28b29961f on fuzz-resources into 682fb874a4a754b04cba0c9cb4be38c30057e99f on develop.


add pipeline, random numbers, create simple trips, split out how it w…

…orks, and lots of little clean-up

Coverage remained the same at 96.61% when pulling 0ee60bb2fa0b35c710fae583862dec19adbadf58 on major-doc-cleanup into e2e397e04427cb5c5cccc45cee6c3244f158e511 on master.


[Feature Request] Add Transparent or semi transparent Monitors

Describe your idea
Glass like Monitors that can display the same content as the Monitors / Advanced Monitors in CC:T
Describe alternatives you've considered if you've any
I was not able to see or find any alternative solutions to this
Additional context
Like in the description said those monitors should be transparent or semi transparent. Having Glass or even Glass Pane like monitors could be a way to get more stunning looking builds. The overall functionality should be the same as the normal monitors in CC:T. They may or may not be also colored in different ways like normal glass would
Linked Issues
No response

I would like you open this feature request on CC:T, but not on this project because the author said he won't work on monitors change

Yeah, I will not work on new monitors
Maybe in the far future
But to be fair, adding/changing the model/texture of the monitors would be a far simpler thing than adding new features to them


Querystring serialize bug

incorrect serialization of nested objects
{foo: {bar: {baz: 100}}}

to
foo=[object Object]

fixed  with qs module
added some tests for nested objects

How do you expect these to be serialized?
This opens the larger issue of using the qs module on the client which increases the client size (non trivially I think).
Not against this overall, just want to make sure that we benefit wisely from a larger library size.

I check size with webpack
var request = require('superagent');

without uglify
27.9 KB for version 1.1.0 without qs module
36.4 KB with qs module
with uglify plugin
9 KB for version 1.1.0 without qs module
12.3 KB with qs module

BTW, you can get around this by using qs yourself and passing the result string to .query.
superagent.get('/foo').query(qs.stringify({foo: {bar: {baz: 100}}}));

If i just start using superagent and don't know about qs module, this is a hidden bug
superagent.get('/test').query({foo: {bar: {baz: 100}}).end(...);

// GET /test?foo=[object Object]
// WTF!?

We can do recursive serialize and parse for GET-params.
But if qs module do same better and has no dependencies, why not use it?
Okay, you win :)
If you don't want use qs for browser, add example to documenatation and close this pull request
superagent.get('/foo').query(qs.stringify({foo: {bar: {baz: 100}}}));

I am not against making this better but we have trade offs.
On Monday, March 23, 2015, AlekZonder<EMAIL_ADDRESS>wrote:

If i just start using superagent and don't know about qs module, this is a
hidden bug
superagent.get('/test').query({foo: {bar: {baz: 100}}).end(...);
// GET /test?foo=[object Object]// WTF!?
We can do recursive serialize and parse for GET-params.
But if qs module do same better and has no dependencies, why not use it?
Okay, you win :)
If you don't want use qs for browser, add example to documenatation and
close this pull request
superagent.get('/foo').query(qs.stringify({foo: {bar: {baz: 100}}}));
—
Reply to this email directly or view it on GitHub
https://github.com/visionmedia/superagent/pull/593#issuecomment-85325970
.

We can develop our stringify and parse in superagent, but why?
If qs module works good, covered by tests and has no large dependencies.
We can develop same functional, but without tests.
OR we can detect: if query object is nested, throw error 'use qs module for nested objects in query' :)

We have implemented a way to serialize and deserialize nested query parameters in BackboneORM with little code, but we also force a strict JSON interpretation of query parameters to allow for couch-like query syntax by URL.
serialize: https://github.com/vidigami/backbone-orm/blob/master/src/lib/json_utils.coffee#L75
deserialize: https://github.com/vidigami/backbone-orm/blob/master/src/lib/json_utils.coffee#L61
I could be wrong, but are nested queries not a standard meaning wouldn't developers need to find/implement and include custom query parsers on the backend of their choice to match the query-string implementation? eg. maybe this better left to user-land

@kmalakoff I think you are correct in that nested queries are not a standardized thing and both the parser and serializer need to match.
The node side of this library already uses qs because size is not an issue but the client size version doesn't obviously. I am inclined to lean the behavior as is and add documentation indicating what to do when this happens. The throw could also work but I am less inclined to do that because those tend to break other js execution.

It's tough because of the current asymmetric behaviour between browser and server. People expect consistency (https://github.com/visionmedia/superagent/issues/549).
One could argue that this should be treated at the middleware or user-land level both for node and the browser to enforce consistency. If superagent is easy to configure at a library level (https://github.com/visionmedia/superagent/issues/591), it shouldn't be a problem for someone to register query-string once on browser and once on the server for all the instances they control (or whatever their case use may be) and then match the parsing with the backend of their choice.
Alternatively, instead of throw, you could log a warning with an explanation of the inconsistency for the reason of bloat-control.


Fix NY: demand spreadsheets for historical data or parse PDFs

After negotiating an expanded timeframe with the NY WARN coordinator (going back to 2006), at her request I foiled a FOIL for the data in electronic spreadsheet format. Today the FOIL office gave me back these:
FL-22-0165 Release Letter .pdf
FL-22-0165 Records for Release_Part1.pdf
FL-22-0165 Records for Release_Part2.pdf
FL-22-0165 Records for Release_Part3.pdf
So, I should either plan to see if they'll give me spreadsheets instead, or resign myself to parsing these well-structured PDFs. And I plan to update the docs for NY.

I'm going to leave it at PDFs, but not able to write a parser just yet. Open for anyone.


BadDeviceToken after download app from App Store

I build app from source code. APNS works and no delay
After I publish my app to App Store regirstration_id gives me this error
In [17]: APNSDevice.objects.filter(user__username__icontains='duck', registration_id='c2e9d4ec4c769314fef2175d47324be3292732d44
    ...: 8a12e1c58021906958a92a1').send_message("Test7")
Out[17]: [{'c2e9d4ec4c769314fef2175d47324be3292732d448a12e1c58021906958a92a1': 'BadDeviceToken'}]

In [18]: APNSDevice.objects.filter(user__username__icontains='duck', registration_id='798a23a46169e405c41a0c9f44faa0acd39a65119
    ...: 960b973acd248a6de1d624e').send_message("Test8")
Out[18]: [{'798a23a46169e405c41a0c9f44faa0acd39a65119960b973acd248a6de1d624e': 'Success'}]

Is there any one here can shed me the light please?

Hard to tell, but I would guess one of the following:

The device was registered on your sandbox environment and is using a stored device token. Try deleting the app from the device, ensuring all user data and keychain entries are erased, then re-install from the App Store. Then remove the device registration from your Django Admin.
Perhaps you're using a sandbox certificate in production? Less likely from the error given, but check you're definitely using your production certificate.

@nlittlejohns Yes you are right
PUSH_NOTIFICATIONS_SETTINGS['APNS_USE_SANDBOX'] = False
I was confused with doc and code base

@elcolie I recommend you use python-decouple for things like this (if you're not already!)
https://simpleisbetterthancomplex.com/2015/11/26/package-of-the-week-python-decouple.html
    "APNS_USE_SANDBOX" : config('APNS_USE_SANDBOX', default=False, cast=bool),


Ensure that the same version of PDF.js is used in both the API and the Viewer (PR 8959 follow-up)

Given that we're now accessing certain API-functionality directly in this file, e.g. the AnnotationStorage and Optional Content configuration, ensuring that there's not a version mismatch definitely seem like a good idea to prevent any subtle future bugs.

/botio-linux preview

Good idea!


KFserving explanations fail when used with authenticated kubeflow

/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
I am using kfserving deployments in a kubeflow cluster with an authentication specified by the arrikto config. https://github.com/kubeflow/manifests/blob/master/kfdef/kfctl_existing_arrikto.yaml. When I make explanation requests with relevant headers(for auth) I get a 404 response, but the prediction works. I am using this sample from the docs https://github.com/kubeflow/kfserving/tree/master/docs/samples/explanation/alibi/income
After some debugging, we found that the explainer is unable to get an output from the predictors as the istio-ingress gateway redirects these requests to a Dex URL for login. (Even the requests internal to the cluster).
What did you expect to happen:
The explainer should have responded with the relevant explanation.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The service type for the default predictor is ExternalName instead of ClusterIP.
Environment:

Istio Version:
Knative Version:
KFServing Version:
Kubeflow version:
Minikube version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

I suspect this should be fixed by Knative 0.9, since internal call should go through Istio local gateway not the ingress gateway

When do we plan to have Knative 0.9 as the required install for kfserving? Are there any kubeflow blockers to moving to 0.9?

I used knative 0.9 from beginning and now even use knative v0.10.0, so far so good.

I am using Kubeflow Deployment with kfctl_k8s_istio
I get the same error when doing tensorflow example
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8080 (#0)
> POST /v1/models/flowers-sample:predict HTTP/1.1
> Host: flowers-sample.default.example.com
> User-Agent: curl/7.64.1
> Accept: */*
> Content-Length: 16201
> Content-Type: application/x-www-form-urlencoded
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 302 Found
< location: /dex/auth?client_id=kubeflow-oidc-authservice&redirect_uri=%2Flogin%2Foidc&response_type=code&scope=profile+email+groups+openid&state=MTU3NjMxMTIxMHxFd3dBRUdWWE1XZGtaMVZXUkhORlYwbzNOMkU9fF5YgT2Qxe7W3PdcmhpqI5ug9CwGBTxwTd1c9FARs9Br
< date: Sat, 14 Dec 2019 08:13:29 GMT
< content-length: 0
< x-envoy-upstream-service-time: 20
< server: istio-envoy
< connection: close
<
* Closing connection 0

the request is redirected to the dex/auth

@pugangxa Hi, may I know how do you deploy your kubeflow? like which version of kfctl you are using? Thanks!

@pugangxa Hi, may I know how do you deploy your kubeflow? like which version of kfctl you are using? Thanks!

I did not use this kind of auth but for knative 0.9+ it do use cluster local gateway. Please refer to PR #561 to install cluster local gateway and have a try.

Please check https://github.com/kubeflow/kfserving/blob/master/docs/samples/istio-dex/README.md
/close


Remove std.typelist

"Please use std.typecons instead. This module will be removed in March 2015."
I think it's time.

https://github.com/D-Programming-Language/phobos/pull/2541 is where it was "deprecated", that was less than a year ago, and after the release of 2.066.0. So the first time anyone has seen it being deprecated in a released version is March 2015. I think we should wait at least until after 2.068 to remove this.

Perhaps we need to fix our deprecation messages to not spit out a date and instead a version number.

Nobody uses it anyway, and it never was a part of build. I'd say just kill it.

Regardless, if we ship it, it's possible people use it. I think we still need to wait at least one release, then kill it.


feat: adding settings for mapping aws lex bot events

feat: handle incoming event from bot intent
resolves #1377

Description

GitHub Issues

Coverage decreased (-0.4%) to 73.423% when pulling a61b4a17456bf1088d3bda5fcdd0a44f69872f5f on jnoortheen:master into 07a615c21742d886bb165556e0dbb270ee8f5c0b on Miserlou:master.

Coverage decreased (-0.4%) to 73.423% when pulling a61b4a17456bf1088d3bda5fcdd0a44f69872f5f on jnoortheen:master into 07a615c21742d886bb165556e0dbb270ee8f5c0b on Miserlou:master.

This actually looks okay, could do with a test.. can somebody confirm working?

I will add tests to it. I've tested the configuration on actual AWS environment and able to get results from lambda. Only thing is, I need to configure the initialisation hook the to the lambda function created by zappa. I've added that as a todo thing in future in docs.

@Miserlou I've added a test the PR.


error: couldn't connect to server: unknown (code -1)

Hi,
When running Bitcoind on my raspibolt, I always get stuck at this error when calling bitcoin-cli getblockchaininfo

error: couldn't connect to server: unknown (code -1)
(make sure server is running and you are connecting to the correct RPC port)

All my connections and the RPC port are in order (followed by the provided guide).
This is my debug.log file:

2018-10-09 10:48:08 Cache configuration:
2018-10-09 10:48:08 * Using 12.5MiB for block index database
2018-10-09 10:48:08 * Using 8.0MiB for chain state database
2018-10-09 10:48:08 * Using 79.5MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2018-10-09 10:48:08 init message: Loading block index...
2018-10-09 10:48:08 Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index
2018-10-09 10:48:08 Opened LevelDB successfully
2018-10-09 10:48:08 Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index:<PHONE_NUMBER>000000
2018-10-09 10:48:34 LoadBlockIndexDB: last block file = 1393
2018-10-09 10:48:34 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=94, size=90416721, heights=544619...544805, time=2018-10-06...2018-10-07)
2018-10-09 10:48:34 Checking all blk files are present...
2018-10-09 10:48:35 LoadBlockIndexDB: transaction index disabled
2018-10-09 10:48:35 : You need to rebuild the database using -reindex to change -txindex.
Please restart with -reindex or -reindex-chainstate to recover.
2018-10-09 10:48:35 Aborted block database rebuild. Exiting.
2018-10-09 10:48:35 Shutdown: In progress...
2018-10-09 10:48:35 scheduler thread interrupt
2018-10-09 10:48:35 Shutdown: done

Thanks in advance for helping me out.
Kind regards

Please check your bitcoin.conf file.
Do you have have txindex=1in your config?

Yes, the hdd has a fully indexed blockchain.
This is my bitcoin.conf file:

server=1
daemon=1
txindex=1

Was the blockchain copied from another computer?
If yes, was txindex enabled on that computer when you were building the blockchain?
Appears to be an indexing error.

Please refer to this thread as well...
https://bitcoin.stackexchange.com/questions/60709/when-should-i-use-reindex-chainstate-and-when-reindex

Yes, the blockchain is copied  from my laptop with index=1 (fully sync.). There it worked perfect without errors. After it, I copied everything to the HDD (blocks, chainstate, index, ...)

Is a reindex recommend, taking in consideration the cpu power a raspberry only has?

To be honest, never faced such an issue.
I did the same thing as you, copied the blockchain on HDD...and it ran without a hitch.
So cannot recommend anything specifc.
But I will take my chances with reindex-chainstate...could be a while on pi though.
Another option is to sync the chain again on your laptop and try copying again...see if that fixes it.

No problem. Thanks for the help.
Regarding the slack, I'm not a member of the BTC slack. I will try. Thx

Btw reindex-chainstate on laptop seems to be a good idea...I will try posting your issue on Bitcoin slack. Will let you know if there is an update.

Thanks, really appreciate it!

I got Bitcoind running, but still got the same issue. Also after rebuilding it with reindex-chainstate. When calling Bitcoin-cli getblockchaininfo, I got another error message (maybe this is not related to the above problem):

error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set.  See -rpcpassword and -stdinrpcpass.  Configuration file: (/home/admin/.bitcoin/bitcoin.conf)

What version of Bitcoind are you running on rpi?
What was the version on the mac?

On the rpi, it's  v0.16.3. On my laptop it's v0.17 I believe.

Hi, sorry for a late response. Life keeps on intervening!
Hoping your problem is addressed now.
I've had to re-index on testnet chains when I upgraded to 0.16.3. But didnt do that on rpi mainnet chain.
If you've not already, you can try updating rpi to 0.17 and see if that helps.
If not, let me know what error your getting. Will try to engage again with Bitcoin slack.

Hey guys,
I am getting the same errors. I reindexed on my laptop and upgraded the pi to 17.0 (same as laptop) but get the following:
2018-10-29T20:59:16Z Bitcoin Core version v0.17.0 (release build)
2018-10-29T20:59:16Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-10-29T20:59:16Z Assuming ancestors of block<PHONE_NUMBER>000000002e63058c023a9a1de233554f28c7b21380b6c9003f36a8 have valid signatures.
2018-10-29T20:59:16Z Setting nMinimumChainWork=0000000000000000000000000000000000000000028822fef1c230963535a90d
2018-10-29T20:59:16Z Using the 'standard' SHA256 implementation
2018-10-29T20:59:16Z Default data directory /home/bitcoin/.bitcoin
2018-10-29T20:59:16Z Using data directory /home/bitcoin/.bitcoin
2018-10-29T20:59:16Z Using config file /home/bitcoin/.bitcoin/bitcoin.conf
2018-10-29T20:59:16Z Using at most 40 automatic connections (1024 file descriptors available)
2018-10-29T20:59:16Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2018-10-29T20:59:16Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2018-10-29T20:59:16Z Using 8 threads for script verification
2018-10-29T20:59:16Z scheduler thread start
2018-10-29T20:59:16Z HTTP: creating work queue of depth 16
2018-10-29T20:59:16Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2018-10-29T20:59:16Z HTTP: starting 4 worker threads
2018-10-29T20:59:16Z Cache configuration:
2018-10-29T20:59:16Z * Using 2.0MiB for block index database
2018-10-29T20:59:16Z * Using 12.2MiB for transaction index database
2018-10-29T20:59:16Z * Using 8.0MiB for chain state database
2018-10-29T20:59:16Z * Using 77.8MiB for in-memory UTXO set (plus up to 47.7MiB of unused mempool space)
2018-10-29T20:59:16Z init message: Loading block index...
2018-10-29T20:59:16Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index
2018-10-29T20:59:16Z Opened LevelDB successfully
2018-10-29T20:59:16Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index:<PHONE_NUMBER>000000
2018-10-29T20:59:28Z LoadBlockIndexDB: last block file = 1413
2018-10-29T20:59:28Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=79, size=72452666, heights=547557...547695, time=2018-10-27...2018-10-28)
2018-10-29T20:59:28Z Checking all blk files are present...
2018-10-29T20:59:28Z Opening LevelDB in /home/bitcoin/.bitcoin/chainstate
2018-10-29T20:59:28Z Opened LevelDB successfully
2018-10-29T20:59:28Z Using obfuscation key for /home/bitcoin/.bitcoin/chainstate: 7505727cceec2d5b
2018-10-29T20:59:29Z : Error initializing block database.
Please restart with -reindex or -reindex-chainstate to recover.
2018-10-29T20:59:29Z Aborted block database rebuild. Exiting.
2018-10-29T20:59:29Z Shutdown: In progress...
2018-10-29T20:59:29Z scheduler thread interrupt
2018-10-29T20:59:29Z Shutdown: done
2018-10-29T20:59:30Z
Any help would be greatly appreciated.

It's essential to run the same version of Bitcoin Core to download the blockchain and on the Pi. Please refer to this answer here:
https://github.com/Stadicus/guides/issues/257#issuecomment-439680005
If you copy the v0.16 blockchain to the Pi that is running 0.17, it will automatically upgrade the internal data structure (can take a few hours).
If you copy the 0.17 blockchain to the Pi that is running 0.16, just upgrade your Pi to use the latest Bitcoin Core binaries (see FAQ: https://github.com/Stadicus/guides/issues/257#issuecomment-439680005)

Hi, my apologies for my delayed response. When updating to 0.17, the errors got fixed. Thanks for helping me out with this.


WalkTime for Multinet

Hi,
my question is why tool for Multinet does not include WalkTime impedance vs the one existing for Navstreets?

Hi @chritomix.  My apologies on the delay in this response.
The WalkTime cost attribute created by the NAVSTREETS tool uses a constant walking speed that defaults to 5 km/h, but can be configured at solve time.  Because it's a constant speed for all street segments, this cost attribute behaves identically to the distance attributes that are also created; the only difference being the units of impedance being reported.  The WalkTime cost attribute is created to accompany the Walking restriction attribute in the Walking Time travel mode created by the NAVSTREETS tool.
Unlike the NAVSTREETS data, the MultiNet data does not have any pedestrian restriction information, so there is no need to create any pedestrian-specific travel modes, and there is no need to create a cost attribute that behaves nearly identically to the distance attributes already created by the MultiNet tool.
Please let me know if you have any further questions.  Thanks!

It's been three months, and there has been no response on this issue, so I'm closing it.  If you're still having problems, feel free to re-open.