fix(build errors): The project now builds without making any modifica…

About the PR

Updates bevy_serialization_extras from version 0.3 to 0.3.1
Crates that were using {path = "../../../bevy_serialization_extras"} now use the crates.io version
Crates that were using {path = "../../../bevy_serialization_urdf"} now use the crates.io version
closes #17
Why / Balance

#17
Project should build with just cargo run
Technical details

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

bevy_serialization_extras and bevy_serialization_urdf gets updated fairly frequently,  set the toml to pull locally as a work around to this:
https://github.com/rydb/bevy_serialization_extras/issues/1#issue-2143334963
until that is solved, this part of the project is liable to break across multiple computers.


Starting a research while another research is already ongoing

This is a minor bug, but you can start another research in the same time if you :

Create a new colony while you are doing a research
Create a lab on the new colony ( with the same research ongoing )
Start a research on the new colony ( even if you are already researching )

Hum, on my test: the research would be added to the queue correctly.


fix: Fix hard coded pull secret name

Fixes https://github.com/kubecfg/kubit/issues/231

We need to invest some time in adding real tests around all of this


QUICKSTEP-127 Data provider thread

Thread used for receiving block requests from clients and sending the
contents of a block back to the client.

@zuyu Question: How do you run tests for distributed quickstep on Travis?

We do not test the distributed version in CI due to previous time-out issue while installing grpc by source code.

Right now, the new code is included only in the distributed version. It need not be the case, as the only dependency for Data Provider Thread is for GRPC and Networked TMB.

Hi @zuyu I have made the changes. The code in this PR will be invoked only with a compile time flag ENABLE_NETWORK_CLI. Earlier it was dependent on ENABLE_DISTRIBUTED, which was not correct. I am working on interfacing this feature with our frontend, another PR will be coming soon which will have an end-to-end working of this feature.

LGTM!

@hbdeshmukh Hi Harshad, can you rebase the branch so I can help merge this PR.

Hi @jianqiao
I have rebased and addressed style concerns by @zuyu. Thanks!


5.3.201 Issue when opening 2 times the same panel

Hi Roman,
in 5.3.201, we are not able to open 2 times the same panel.
The "On modulator value change" methods are fired on the second instance and not stopped.
Do you have a solution for that?
Is there a way to uniquely identify an instance and to query it?
Tried by generating a random number but even if the number is indeed different by instance, I don't succeed to stop the run of the methods.
I attach a simple example panel.
Test instance.zip
Let me know if you have maybe solved/improved that behaviour in more recent versions.
Thx and take care...Dominique

It's probably worth talking to Martin Tarenskeen.
When I helped informally beta test his Yamaha PSS panels, there was a problem with random number generation.  What worked on one version of Ctrlr, didn't work on another, and vice versa.
The workaround involved using two or three different generation methods, and adding the results together, IIRC, maybe involving modulo arithmetic to keep the result in a useful range.
I'm currently on Version = 5.4.52, and I think I probably was at the time, but I can't be sure.
Let me know if there's anything specific I should try, to see what happens with this version.

Andy

Hi Andy, the random number generation is working fine in the panel above.
I checked with the console and I got indeed 2 different numbers.
The issue is that the OnChange methods are still fired on the second instance of the same panel and that we don't find a way to prevent that.

I see.  I'm still not sure how I'd check if that is happening, but let me know if you want me to try anything in the version I have installed.
Is this how it should look?  I only see one control, but two labels:

FYI, I solved this issue by testing on source=6 and source=1 at the beginning of the OnChange methods.
But this is just a subcase of a more general issue that when an OnChange method is triggered in one panel (source=4) it is also triggered in the other opened panels but with source=1.
So, this is a mess when opening different panels with the same method names.


Support SNI authentication with async CertificateCredential

Is there any update on the progress/status of this issue?


I can not export animation from Blender to glTF

Describe the bug
When I export without animation it do it correctly. But with animation it gives this error:
Python: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\__init__.py", line 628, in execute
    return gltf2_blender_export.save(context, export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 35, in save
    json, buffer = __export(export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 52, in __export
    __gather_gltf(exporter, export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 66, in __gather_gltf
    active_scene_idx, scenes, animations = gltf2_blender_gather.gather_gltf2(export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather.py", line 34, in gather_gltf2
    animations += __gather_animations(blender_scene, export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather.py", line 91, in __gather_animations
    animations_, merged_tracks = gltf2_blender_gather_animations.gather_animations(obj_uuid, merged_tracks, len(animations), export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animations.py", line 128, in gather_animations
    animation = __gather_animation(obj_uuid, blender_action, export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animations.py", line 171, in __gather_animation
    channels=__gather_channels(obj_uuid, blender_action, export_settings),
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animations.py", line 208, in __gather_channels
    return gltf2_blender_gather_animation_channels.gather_animation_channels(
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_cache.py", line 38, in wrapper_cached
    result = func(*args, **kwargs)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channels.py", line 106, in gather_animation_channels
    channel = gather_animation_channel(
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channels.py", line 266, in gather_animation_channel
    __target= __gather_target(obj_uuid, channels, export_settings, bake_bone, bake_channel, driver_obj_uuid)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channels.py", line 359, in __gather_target
    return gltf2_blender_gather_animation_channel_target.gather_animation_channel_target(
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_cache.py", line 38, in wrapper_cached
    result = func(*args, **kwargs)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channel_target.py", line 29, in gather_animation_channel_target
    path=__gather_path(channels, blender_object, export_settings, bake_bone, bake_channel)
  File "C:\Program Files\Blender Foundation\Blender 3.2\3.2\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channel_target.py", line 92, in __gather_path
    target = [c for c in channels if c is not None][0].data_path.split('.')[-1]
IndexError: list index out of range

To Reproduce
Steps to reproduce the behavior:

Export glTF.
The Error.

Expected behavior
It should be exported!
Screenshots
https://prnt.sc/Nurs4KGP_3sQ
.blend file/ .gltf
If applicable, a zipped folder containing a .blend file for exporter issues and a .gltf file for importer issues. Please take care to include all resources, such as textures in the .zip file.
Version

Windows 10 x64
Blender Version 3.2.1

Additional context
In 2.91 version was the same error

Trying to find solution: https://docs.blender.org/manual/en/3.2/addons/import_export/scene_gltf2.html
But no results...

Hello, You have 3 invalid drivers on your model. Remove them will solve the issue.
I will add some checks to ignore invalid drivers.

Where are those drivers? I don't see there any drivers, I deleted all drivers.
Can you tell me what you mean telling drivers? Maybe names of drivers?
Where are those drivers? On mesh? On armature? I don't see there any drivers!

Here, on Unicorn_A mesh:

I also encountered this problem, how to find invalid drivers

@xixiluoke Can you please create a new ticket with your file attached?

So sad, the company rules can not upload all kinds of files, can you tell me how to check


[5.7] Changed description for authenticate method

Changed description for authenticate method, since check method has the same description.

resubmit of https://github.com/laravel/framework/pull/25632#issuecomment-421830826

I just re-wrote myself. Thanks.


ci(integration): add layered docker caching

blocked by https://github.com/satackey/action-docker-layer-caching/issues/37

superseded by #342


Update Puppet Forge releases

While a whole load of work has been done on the module and a bunch of merge requests have been merged, the latest version is still stuck at 2.1.0 which is 8 months old.
Will you be pushing a new release to the Forge anytime soon?

Yes, we need to add the new features for 0.26 version of sensu first. I added a milestone to get this out the door.

@jaxxstorm any news on when the mythical 2.2.0 module will be released? 0.26 has been out for a pretty long while and none of us puppet users can upgrade because the module doesn't support 0.26 :cry:

@poolski I'm hoping to find some time to release it next week. I apologise for the delay. If you use the latest commit of this repo, it should work.

For those watching this, thanks for your patience. I hope to release a new module to the forge this weekend, time permitting.


Link platforms guide

Needs https://github.com/kubernetes/community/pull/8194
/hold

/unhold

/lgtm
/approve


No Touchscreen implementation ?

Is it made or could be made to work with touchscreen such as ipad and tactile screens ? Thank you

A touch enabled version will follow later. Can't tell at the moment when.
But, yes, should be done.


Looks like when webp is set to false it keeps converting the image to webp

Looks like when webp is set to false it keeps converting the image to webp
{
        test: /\.(png|webp|jpg|jpeg|gif|svg)$/,
        loader: 'img-optimize-loader',
        options: {
          name: '[path][name].[ext]', //'[path][name]-[contenthash].[ext]'
          compress: {
            // This will take more time and get smaller images.
            mode: 'lossless', // 'high', 'low'
            disableOnDevelopment: true,
            webp: false,
          },
        },
      },

@a2nt It has been fixed at the latest version,thank you.

Thank you


tool/charts: Allow 2 or more versions of the same chart

This feature was alluded to in https://github.com/grafana/tanka/issues/508 but only validation was added in the end to prevent conflicts. We'd really like to be able to specify 2 versions of the same chart in the same repo since we have multiple Environments using it at the same time and it would be nice to be able to promote chart upgrades through them rather than having to update them all at once.

You can, you have to specify different directories:
directory: charts
repositories:
- name: fluxcd-community
  url: https://fluxcd-community.github.io/helm-charts
requires:
- chart: fluxcd-community/flux2
  version: 1.2.0
  directory: '1.2.0'
- chart: fluxcd-community/flux2
  version: 1.6.0
  directory: '1.6.0'
version: 1

Still needs to be documented


[FEATURE] Make routes relative

Description
Currently, the routes are absolute paths. I want to make them relative such that they will have a simple route setup and also common layout would be shared easily. Currently, we have to add seperate CSS on every page to make it compatible with sidebar and navbar.
I want to remove all those CSS and centralize it.
Screenshots
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Description
Currently, the routes are absolute paths. I want to make them relative such that they will have a simple route setup and also common layout would be shared easily. Currently, we have to add seperate CSS on every page to make it compatible with sidebar and navbar. I want to remove all those CSS and centralize it.
Screenshots
No response
Additional information
No response
Record

[x]  I agree to follow this project's Code of Conduct
[x]  I have checked the existing issues
[x]  I'm a GSSoC'23 contributor
[x]  I want to work on this issue

that'd be really awesome!!

This requires / corresponds to refactoring as well so I think this should be level 3


[WIP] python: Update python style guide

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>Commit Message: python: Update python style guide
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Partial fix for #15403 , ref #15479
[Optional Deprecated:]
[Optional API Considerations:]

re mypy the biggest issue that it introduces is py version.
we are currently pegged to >=3.8
more recent versions of python - esp 3.9 have increasingly better lang-level support for some of the type hinting
older versions of python require use of the typing lib

@phlax I like the idea of preferring f-strings (and other Python 3+ isms).


tf.math.argmin and tf.math.argmax don't support complex

System information

OS Platform and Distribution: Windows10 1909
TensorFlow installed from : binary
TensorFlow version: 2.2.0rc2
Python version: 3.8.0
CUDA/cuDNN version: None

Describe the current behavior
The documentation says that input of argmax must be one of the following types: float32, float64, int32, uint8, int16, int8, complex64, int64, qint8, quint8, qint32, bfloat16, uint16, complex128 , half, uint32, uint64.
However, I encounter problem when I use complex tensors as input.
Standalone code to reproduce the issue
argmin
a = tf.constant([1j], dtype=tf.complex64)
b = tf.math.argmin(a)

argmax
a = tf.constant([1j], dtype=tf.complex64)
b = tf.math.argmax(a)

Output
2020-07-16 10:27:30.370246: F tensorflow/compiler/xla/literal_util.cc:289] Unhandled primitive type 15
Aborted (core dumped)

tf.math.argmax : Returns the index with the largest value across axes of a tensor.
tf.math.argmin  : Returns the index with the smallest value across axes of a tensor.

But complex numbers can't tell the larger one and the smaller one....
I think that's the reason why they don't support complex64 and complex128

tf.math.argmax : Returns the index with the largest value across axes of a tensor.
tf.math.argmin  : Returns the index with the smallest value across axes of a tensor.

But complex numbers can't tell the larger one and the smaller one....
I think that's the reason why they don't support complex64 and complex128

Though complex numbers cannot be ordered, many numerical computational softwares, such as numpy and matlab, compare the real part of complex numbers.

Agreed with @jstzwj , I think the library should be consistent with numpy.

I tried in colab with TF 2.2, 2.3-rc1 and i am seeing the session is crashed.Please, find the gist here.Thanks!

Could reproduce the error with Tensorflow Version 2.4.1. Please find the Gist. Thanks!

I tried this using tf-nightly version ,got no error as reported .Please check this gist....Thanks !

Closing this issue as it is fixed in latest version of TensorFlow. Please feel free to reopen the issue if you still have a concern. Thanks!


2751: Fix pull to refresh for maps

Short description

Fix pull to refresh for maps.
Proposed changes

Fix pull to refresh for maps in full screen bottom action sheet
Only render RefreshControl if a refresh function is passed

Side effects

No pull to refresh is possible anymore if no refresh function is passed.
Resolved issues

Fixes: #2751.

I can't refresh on my iPhone on the maps page. If I pull the BottomActionSheet all the way to the top of the page, and then pull down anywhere, I just lower the BottomActionSheet again.

Does it work on android for you? Maybe you are pulling down from too much in the top?

I can't refresh on my iPhone on the maps page. If I pull the BottomActionSheet all the way to the top of the page, and then pull down anywhere, I just lower the BottomActionSheet again.

Does it work on android for you? Maybe you are pulling down from too much in the top?

Interestingly, it doesn't work on Android either, though that's just the emulator. I click pretty exactly where Svenja tapped in her video (just under the top of the BottomActionSheet) and pull, and it just does nothing. If I do the same thing on my real iPhone, I close the BottomActionSheet 🤷

I can't refresh on my iPhone on the maps page. If I pull the BottomActionSheet all the way to the top of the page, and then pull down anywhere, I just lower the BottomActionSheet again.

Does it work on android for you? Maybe you are pulling down from too much in the top?

Interestingly, it doesn't work on Android either, though that's just the emulator. I click pretty exactly where Svenja tapped in her video (just under the top of the BottomActionSheet) and pull, and it just does nothing. If I do the same thing on my real iPhone, I close the BottomActionSheet 🤷

@f1sh1918 @ztefanie can you please test this as well? I had the same issue as @LeandraH at some point but its now all working for me. I thought its just because of starting the gesture in a slightly different place.


lodash: changed _.clone() and _.cloneDeep() methods

https://lodash.com/docs#clone
https://lodash.com/docs#cloneDeep
https://lodash.com/docs#_ (description of the chainable wrapper)

@chrootsu thanks mate!


Navbar Title off center when dynamically loading iOS or Material theme

When using the example of how to maintain Material and IOS in a single app from here:
http://www.idangero.us/framework7/tutorials/maintain-both-ios-and-material-themes-in-single-app.html
The title in the navbar in iOS starts uncentered.
This can be corrected by running myApp.sizeNavbars('.view-main');, but you can't do it right away as soon as the app is initialised. If you do it a tad later (say 'deviceready' in PhoneGap) then there is a visible "jump" when the title corrects to the center.

Ok, played a bit with it. Find the pretty weird behavior, or didn't know it works like that. So when we append styleshets in my-app.js browser loads them asynchronously, but if we load it in another file or directly in HTML before my-app.js it loads them synchronously. So part with stylesheets should be removed from my-app.js and order should be the following:
<body>
    ...
    <script type="text/javascript" src="js/framework7.min.js"></script>
    <script>
      (function () {
        if (Framework7.prototype.device.android) {
              Dom7('head').append(
                  '<link rel="stylesheet" href="css/framework7.material.min.css">' +
                  '<link rel="stylesheet" href="css/framework7.material.colors.min.css">' +
                  '<link rel="stylesheet" href="css/my-app.material.css">'
              );
          }
          else {
              Dom7('head').append(
                  '<link rel="stylesheet" href="css/framework7.ios.min.css">' +
                  '<link rel="stylesheet" href="css/framework7.ios.colors.min.css">' +
                  '<link rel="stylesheet" href="css/my-app.ios.css">'
              );
          }
      })();
    </script>
    <script type="text/javascript" src="my-app.js"></script>
</body>

I will update tutorial with this snippet

Interesting. This will clash with a Content Security Policy (that doesn't allow 'unsafe-inline'), so I might personally look for a build-time solution just for those stylesheets.
However, as a general fix for the guide, this looks like a good solution. Thanks :)

Note: It turns out the snippet above can be used in an external JS file, as long as it is loaded before my-app.js as above.
<script type="text/javascript" src="js/framework7.min.js"></script>
<script type="text/javascript" src="js/init-styles.js"></script>
<script type="text/javascript" src="my-app.js"></script>

Yes, should be anywhere but before my-app.js. To be honest i don't really understand why browser does like that :)


compare_output() fails on Windows due to different line endings

I described the issue in rust-lang/rust before (link).
As noted in that issue, all one needs to do is to create a .gitattributes that forces LF line endings on checkout.
Do you agree that a .gitattributes file should be added to this repo? It might also be a good idea to make this information part of the docs.
I can open a PR if you want me to.

Hi @fkohlgrueber I totally missed this issue being posted, I'm sorry!

Do you agree that a .gitattributes file should be added to this repo? It might also be a good idea to make this information part of the docs.

If that's all it takes to fix it, I have no problem with it, but I don't really have a good way of testing it myself.

I can open a PR if you want me to.

Please do :-)


Hardcoded datetime

https://github.com/airene/vitepress-blog-pure/blob/28b63536637e21e9ab0ab1012c592ab0c9bc0e0c/.vitepress/theme/components/Page.vue#L7
datetime here should not be hardcoded.

fix it


Sign up returns error even though account is registered successfully

I'm getting error even though account is successfully registered.
Here's my code and the error:

I'm using 0.0.4 and I have no problem when using the account to sign in.

Hi @grsouza  here

hi @grsouza  any update on this? Thanks!

@mhaezaragoza this has been fixed on #16 but I still need to do some more work on this PR before it lands.
If you wish you could give it a try, a lot of things changed in this PR as we dropped support for older OS versions.


Document import: feature

 import: feature should go to README.md

The README.md is instance_path of the flask?

it took me quite a while to find this gem of a feature.


Storage operations within checkpoint manager did not utilize the blob_prefix.

Adds functionality such that if the prefix is defined, it is used.  lease path previously would simply be / even if prefix was defined, will now be //
Adds unit tests to validate this as well.
NOTES:

This will need to be validated in Track2 as well.  This is a note to myself to ensure I've done so or created an issue to track this task, before I merge this. (Posted here in case someone can say "it's fine" that I can check this off)
There are two nitpicks I'd call out as well.

The logic looks like it initially wanted the non-prefix case to render as //  However due to the bug in question, it's only /.  For backwards compatibility, I have NOT changed this to include the consumer group, otherwise users who did not define the prefix would suddenly find their lease checkpoint paths "missing"
VERY pedantically, I've put the blob_path generation within the trys, but not pushed the full path to all of the error logs (many still only detail the partition).  Shout if others would prefer a different semantic.

I'm wondering the correct behavior of storage_blob_prefix as there is no comment for this parameter.
which one is the expected path for the blob?
1. {consumer_group}_{consumer_group}/{partition_id}
2. {storage_blob_prefix}/{consumer_group}/{partition_id}
3. {consumer_group}/{storage_blob_prefix}_{partition_id}

@KieranBrantnerMagee @annatisch thoughts on this?

@yunhaoling So here's the conundrum I faced when trying to determine the proper semantics there.
In a perfect world I'd do {optional prefix (which can itself optionally contain slashes}{consumer_group}/{partition}
However, consumer_group_directory was never used in the past, so in order to maintain backwards compatibility, (and this really forces our hand since a break would be painful) you can't change where the lease file is located.
Now, even with that limitation your question is still relevant, so I'd echo your ping to @annatisch if there's any precedent.  (perhaps we should ask the other language folks?)

I feel like there's almost two separate features here:

storage_blob_prefix and it's use and behaviour
consumer group as a subdirectory.

Given that, as mentioned, the original self.consumer_group_directory was never utilized, I think we can treat these as separate without breaking people.
We could add an additional parameter as use_consumer_group_as_directory=False
Then maybe something like:
....
self.consumer_group_directory = self.host.eh_config.consumer_group if use_consumer_group_as_directory else ""
self.blob_prefix = storage_blob_prefix
....

def _get_blob_path(self, partition_id):
    blob_name = partition_id
    if self.blob_prefix:
        blob_name = self.blob_prefix + "_" + partition_id
    return "{}/{}".format(self.consumer_group_directory, blob_name)

This would return:

"/0" in the default scenario
"$default/0" in the consumer group scenario
"/custom_0" or maybe "/custom/0" in the blob_prefix scenario
"$default/custom_0" for a combined scenario

.....am I over thinking this....? I don't want to over design a feature in a deprecated library.... >_<

I like the design, it exposes a more intuitive and more flexible grid of outcomes without much added complexity.  Simple enough that I don't feel too bad about the deprecated part.  Will adjust.
(to be pedantic re: your sample that for backcompat, the base case of just partitionId can't have a leading /)


Does this crate support Responses with type parameters?

I'd like to be able to use the following generic structs:
#[derive(Response)]
pub struct SingleResponse<T> where T: Serialize {
    pub item: T
}

#[derive(Response)]
pub struct MultiResponse<T> where T: Serialize {
    pub items: Vec<T>
}

But I get the following compilation error:
 --> src/services/api/mod.rs:8:10
  |
8 | #[derive(Response)]
  |          ^^^^^^^^ expected 1 type argument

Is what I want to do possible, and if so how?

It should! I will investigate.

#144 should fix this.
You shouldn't need the bound on the struct.


Optimize MySQL DDLStatement Visitor

Fixes #3914.
Optimize MySQL DDLStatement visitor:

Consider to simply visitCreateTable in MySQLDDLVisitor
Consider to simply visitAlterTable in MySQLDDLVisitor
Consider to simply createColumnDefinitionSegment in MySQLDDLVisitor

Changes proposed in this pull request:

Simply visitCreateTable in MySQLDDLVisitor
Simply visitAlterTable in MySQLDDLVisitor
Simply createColumnDefinitionSegment in MySQLDDLVisitor

Codecov Report

Merging #4209 into master will decrease coverage by 0.15%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master    #4209      +/-   ##
============================================
- Coverage     60.85%   60.69%   -0.16%
  Complexity      352      352
============================================
  Files          1013     1013
  Lines         16922    16966      +44
  Branches       2983     2991       +8
============================================
  Hits          10298    10298
- Misses         5972     6016      +44
  Partials        652      652

Impacted Files
Coverage Δ
Complexity Δ

...dingsphere/sql/parser/visitor/MySQLDDLVisitor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 9389

0 of 116 (0.0%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 64.6%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

shardingsphere-sql-parser/shardingsphere-sql-parser-mysql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/MySQLDDLVisitor.java
0
116
0.0%

Files with Coverage Reduction
New Missed Lines
%

shardingsphere-sql-parser/shardingsphere-sql-parser-mysql/src/main/java/org/apache/shardingsphere/sql/parser/visitor/MySQLDDLVisitor.java
1
0%

sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/util/IpUtils.java
3
76.0%

Totals

Change from base Build 797:
-0.2%

Covered Lines:
10960

Relevant Lines:
16966

💛  - Coveralls

Hi @SteNicholas Thanks for this optimization. It seems this class becomes much better.  Althought more optimization could be done, one point concerns me much is the name of some rules, like CreateDefinitionClause_.
Our instruction tells us CreateDefinitionClause is standard one, since we visited it in our Visitor.class, so i suggest to review any rule name ending with _ in MySQLDDLVisitor.java.
I'd like to see your another PR concerning this. Welcome your opinions. 😃  Good job!


Add reqwest TLS pass thru feature

Thanks for all the hard work! I am really excited for the new APIs! I have been waiting for the new reqwest based client to add GCP functionality to an app, and it looks like its getting close!
What do you think about having pass through reqwest features like rustls-tls etc?

Thanks a bunch (CC @ggriffiniii  who wrote all the API generation code) :)!
To my mind, implementing your suggestion would be very desirable.
All the code you would be interested in is here, do you think you could supply a PR?

Yeah, I’ll open one soon.


Power Shell deployment reliability

PS deployment process stuck after successful authentication without any reasons

After several attempts, the deployment was failed
Different reasons the last one was this^

Hi @Mikhail2k15,
Thanks for raising the query, we're looking into the issue with PS deployment, will get back to you as early as possible with response.

Hi @Mikhail2k15 ,
Thank you for submitting this issue, as we work to ensure consistent responses with items logged in our issues list, we are working to address these items that did not get responses. Please let us know if you still require assistance and we will be happy to discuss. If no further action is needed at moment and no response is received, we will close out the issue in 3 business days. You may also always open a new issue or respond here if something does come back up.


Detect mouse clicks

Has the circle which detects mouse clicks become smaller? Is there a way to change the size of it? Cheers.

I believe so because I was fiddling with that part of the code.
Currently there's no way to change the size of the circle.


Is it possible to build the framework for macOS instead of iOS?

Is it possible to build the framework for macOS instead of iOS? If so, can you please provide some guidance? Thank you so much!!!

I'm just speculating, but I think you can do that by tweaking the framework build phase.
But sorry, I really can't provide guidance on this since I'd need time to experiment with it.
If you do find that it's possible, then PRs are welcome.


Brian goalert

My changes
Image built and pushed to quay.io/bsmit/configure-alertmanager-operator:latest.  No idea if it works or not

/lgtm


moved bad aircraft tracks and added cube to timeseries data

The aircraft data previously residing in 'timeseries' had multiple coordinates, so was technically not a timeseries dataset.  this has all been moved to 'aircraft_tracks_multidim'.
Also, I found a 3-dimensional dataset from 'model', then collapsed the x and y dimensions to create a dataset with a time coord and scalar coords for x and y (x and y coords are now a single minimum value from original file).  This is technically a timeseries dataset which I can use in tests, so I have popped it into 'timeseries'.

I'll check whether the mystery aircraft files load at all, if not I'll remove them.  Thanks.

The files now in aircraft_tracks_multidim will load using iris, but they are still multidimensional cubes as they have auxilliary coords.  Let's not get too deep into that, but it means that I cannot use them for timeseries tests.
I am happy leaving them in this renamed directory (I have a strong feeling we will need them for other tests) and adding my modified file to timeseries.
Thank you!!


fix: lint again

🏠 Internal
Fix another hundred or so of lint warnings. Down from 199 warnings to 40+.

Btw, why does superset-ui-connection has it's own eslintrc?

Btw, why does superset-ui-connection has it's own eslintrc?

Good question. I am not aware of this either. cc @williaster


How to run the demo code for my own images?

I am interested in running the Demo.ipynb for my own images. However, I am not sure where to create these .pkl files?

[812147:3298 0:1481] 04:37:55 Thu Dec 31 [mona@goku:pts/1 +1] ~/research/code/DJ-RN
$ fd hbox.pkl
script/demo/hbox.pkl
9201/31772MB
[812147:3298 0:1482] 04:38:01 Thu Dec 31 [mona@goku:pts/1 +1] ~/research/code/DJ-RN
$ rg hbox.pkl
script/test.py
18:hbox     = pickle.load(open('demo/hbox.pkl', 'rb'))

script/Demo.ipynb
59:    "hbox     = pickle.load(open('demo/hbox.pkl', 'rb'))\n",

and:

[812147:3298 0:1482] 04:38:01 Thu Dec 31 [mona@goku:pts/1 +1] ~/research/code/DJ-RN
$ rg hbox.pkl
script/test.py
18:hbox     = pickle.load(open('demo/hbox.pkl', 'rb'))

script/Demo.ipynb
59:    "hbox     = pickle.load(open('demo/hbox.pkl', 'rb'))\n",
9201/31772MB
[812147:3298 0:1483] 04:38:09 Thu Dec 31 [mona@goku:pts/1 +1] ~/research/code/DJ-RN
$ rg *pkl
script/Download_result.sh
7:python script/Download_data.py 10nUe9ruH7ZPTEh8WuV7lRCrRMCGFocKz ./-Results/400000_DJR_ambiguous.pkl.tar.gz
9:tar -xvzf 400000_DJR_ambiguous.pkl.tar.gz
10:rm -rf 400000_DJR_ambiguous.pkl.tar.gz

README.md
224:`python ./-Results/Evaluate_ambiguous.py ./-Results/400000_DJR_ambiguous.pkl DJR_ambiguous/`
9201/31772MB

How do you create them for custom images and not coco images? (imagine these custom images have COCO objects).
We have the following in one of the Demo.ipynb cells:

args     = Arguments(gender='male', smplx_path='/home/mona/research/code/DJ-RN/models/smplx/')
obj_name = 'keyboard'
result   = pickle.load(open('demo/result.pkl', 'rb'))
hbox     = pickle.load(open('demo/hbox.pkl', 'rb'))
obox     = pickle.load(open('demo/obox.pkl', 'rb'))
mesh       = 'demo/human.obj'
img        = 'demo/sample.jpg'

For humans, we should prepare the human bounding boxes (hbox.pkl) and human 2D pose keypoints following our data format (or you can adjust the format yourself but ensure all the inputs are provided for Simplify-x).
Openpose is recommended to support both body, hands, and face keypoints.
As for objects not in the range of coco 80, you could use other detectors that can afford the detection of your objects, or given just the objectness proposals from RPN. Similarly, you need to follow the input format or adjust the data loader.

For humans, we should prepare the human bounding boxes (hbox.pkl) and human 2D pose keypoints following our data format (or you can adjust the format yourself but ensure all the inputs are provided for Simplify-x).
Openpose is recommended to support both body, hands, and face keypoints.
As for objects not in the range of coco 80, you could use other detectors that can afford the detection of your objects, or given just the objectness proposals from RPN. Similarly, you need to follow the input format or adjust the data loader.

@DirtyHarryLYL for COCO objects could you please share with me their object.obj files?

@DirtyHarryLYL for COCO objects could you please share with me their object.obj files?

Notice that we simplify the objects as a sphere, as in #19, the object.obj is automatically generated.

Notice that we simplify the objects as a sphere, as in #19, the object.obj is automatically generated.


"Undefined local variable" error when refering to it in a constant

Bug Report
This code fails :
path = Path["dir1/dir2/file1.csv"]
FILENAME = "#{path.parent}/#{path.basename[0..-4]}.updated.csv"
puts FILENAME

With the following error :
In test.cr:7:15

 7 | FILENAME = "#{path.parent}/#{path.basename[0..-4]}.updated.csv"
                   ^---
Error: undefined local variable or method 'path' for top-level

Modifying the constant by a regular variable works as expected :
path = Path["dir1/dir2/file1.csv"]
filename = "#{path.parent}/#{path.basename[0..-4]}.updated.csv"
puts filename

Here's my environment :
❯ crystal -v
Crystal 1.1.1 [6d9a1d583] (2021-07-26)

LLVM: 10.0.1
Default target: x86_64-unknown-linux-gnu

What would be a bug here? The error is correct and expected. Constant's can't reference local variables.

Hum ok. Sorry, it comes from my background of dynamic languages where you can do whatever you want 😅.
Maybe the error could be more user friendly then ? Because it's kind of unclear IMO.

Maybe the error could be more user friendly then ?

Agreed. As a bit of a longer explanation, constants are values computed statically during compilation and that's why they can't refer to variables.

For reference you could do this:
FILENAME = begin
  path = Path["dir1/dir2/file1.csv"]
  "#{path.parent}/#{path.basename[0..-4]}.updated.csv"
end

puts FILENAME

What would be a bug here? The error is correct and expected. Constant's values can't reference local variables.

Is this restriction documented? I didn't see it in the "Constants" page in the docs website.
I was under the same impression that @pyrsmk was, that it was just assigning a value to an immutable binding that was accessible from anywhere in the app. I ran into this for the first time this evening and thought I was losing my mind.

Yeah, maybe pointing to a doc link, which has the explanations of what a constant is and what can be done and not, like here they can't depend on runtime values.


Provide a property to choose between iOS and iOS simulator

What about CI - 2 (or maybe even 3) archs in single build?

Just two separate steps, one for sim and one for device.

Why separate? Single command to build all is very useful.

Maybe, but current tooling cannot cope with multiple targets at the moment.

Well, you can add arm32 target and run ./gradlew linkReleaseFrameworkIos32 linkReleaseFrameworkIos64 linkReleaseFrameworkIosSim to get 3 frameworks (before this merge).


On the way to v1.0

This issue is supposed to be a place to discuss what needs to be implemented for version 1.0.
These should include show-stoppers but can also include nice-to-haves. We'll need to decide which ones belong to which group.
Everyone is encouraged to share their ideas and suggestions. I'll start.

Multithreading support: mull itself is multithreaded, but if the program under test is multithreaded, then Mull may produce non-deterministic results. Currently, Mull gathers the code coverage based on call trees. In a single-threaded program (most of the time) the call tree is deterministic (i.e., the order of the calls is the same from run to run). A possible solution is to use another, 'linear' coverage approach: to only collect whether the function was executed or not. It has some drawbacks but will give the most deterministic behavior.
TLS support: this is being in the works currently #745.
Diff reporter: Mull has several reporters (mutation elements, SQLite, CLI). it would be very nice to also have a reporter that produces git-like patches so that they can be applied to the source code or used as part of CI integration. Related #587.
CI integration: mull can be run as part of the CI process, but the integration is not trivial and does not have smooth CI integration.  Directly related to #738.
Diff-based mutation filter: at the moment, Mull does not respect version control systems. For better CI integration it is essential to filter out mutants that are unrelated to a pull or merge request.
Non covered mutants: as described here #636.
More test frameworks: it would be nice to have more test frameworks supported. Related #174 #175 #191 #492 #746. More suggestions are very welcome.

The above list is not exhaustive and may be extended.

Smooth junk detection: currently, Mull requires a user to provide 'implicit' C/C++ header search paths manually. It would be nice if we can automate this process in a transparent way.

Great to collect all the important features in one ticket. Would it be useful to also create a v1.0 Label or Milestone to mark PRs and issues which are part of this effort?

That's a good idea. I'll create a milestone and a label. I guess for the milestone to work I'd also need to create an issue per each feature/task.

About the diff filter, are we talking something like clang-tidy-diff?
https://clang.llvm.org/extra/doxygen/clang-tidy-diff_8py_source.html

About the diff filter, are we talking something like clang-tidy-diff?
https://clang.llvm.org/extra/doxygen/clang-tidy-diff_8py_source.html

That is correct.

Vote for "Add ability to catch mutants using tests written on other languages #778"

More test frameworks: it would be nice to have more test frameworks supported. Related #174 #175 #191 #492 #746. More suggestions are very welcome.

It is definitely good for those who use these frameworks. But I believe it would be a nightmare for Mull maintainers to support and test all of these frameworks. I would suggest to generalize integration with test frameworks (no ideas how) or simplify integration that will allow users easily integrate without changing Mull source code.
Also there is a report published by Jetbrains where developers answered on question "Which unit-testing frameworks do you regularly use, if any?". Below is a distribution of different unit testing frameworks for C and C++:

Source: C language:

Source: C++ language

Dropping JIT is certainly on the list #798.

Yet another follow-up: since the JIT is gone there is no special need for multithreading and TLS support. Also, we cannot have/don't need explicit test frameworks support anymore.
I edited the original comment to reflect the current state.


Error on preview in DrRacket

I opened the "8-image.rkt" example and tried to preview it in DrRacket with the toolbar button. The result was this error:
avcodec-open2: Invalid Argument
  context...:
   /home/asumu/code/video/video/private/ffmpeg-pipeline.rkt:593:4: open method in mux%
   /home/asumu/code/video/video/render.rkt:552:11

Hey Asumu, thanks for submitting this issue. Can you tell me what OS you were using when you found this issue? I presume some form of debian?

Yeah this is on Debian stable.
The more detailed error turns out to be AVCodecContext: Specified sample format fltp is invalid or not supported. The following patch gets rid of the problem for me, but I don't know if it's really the right fix. (maybe it should detect what to use based on the system?)
From 8760499f2e4491ab1e1e2425616059cd413d7d14 Mon Sep 17 00:00:00 2001
From: Asumu Takikawa<EMAIL_ADDRESS>Date: Mon, 11 Sep 2017 19:20:23 -0700
Subject: [PATCH] Use s16 sample format by default

---
 video/private/ffmpeg-pipeline.rkt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/video/private/ffmpeg-pipeline.rkt b/video/private/ffmpeg-pipeline.rkt
index c0bf393..be28625 100644
--- a/video/private/ffmpeg-pipeline.rkt
+++ b/video/private/ffmpeg-pipeline.rkt
@@ -50,7 +50,7 @@
 (define DEFAULT-MAX-B-FRAMES 8)
 (define DEFAULT-SAMPLE-FREQ 44100)
 (define DEFAULT-PIX-FMT 'yuv420p)
-(define DEFAULT-SAMPLE-FMT 'fltp)
+(define DEFAULT-SAMPLE-FMT 's16)
 (define DEFAULT-CHANNELS 2)
 (define DEFAULT-CHANNEL-LAYOUT 'stereo)

--
2.11.0

Here's a potentially relevant bug thread from elsewhere: https://trac.ffmpeg.org/ticket/3107

Oh, that actually makes a lot of sense. The problem being that @jbclements 's portaudio package only works with s16, and the preview button isn't properly setting that as the output. (Where as the preview command is.)
So, the solution is not to set the default to s16, (because fltp seems to be more common for storing videos, but to have the preview button set it to s16, which is more common for live previews.)
Thank you for finding this.

Can you send me the output you get when running:
racket -W debug -l raco video -p 8-image.rkt

Thanks.

Oops, missed this one. It doesn't look to me like there's any action required on my part, but let me know if I'm misreading this.

@jbclements Yup, this is correct. About the only thing I can think of is putting in a feature request to support other formats. But nah, there's no bug. Thanks though. :)
@takikawa Okay, I think I have traced the origin of this bug down to the same source as the one resizing one. I will push a fix shortly.

@takikawa I think I fixed the bug, can you test it again to make sure?

@LeifAndersen Just pulled and it looks to be fixed, thanks!

Cool. Thank you.


feat: Add CLI interface

Here's a CLI interface example with click that could be later expanded in scikit-build or other plugins as needed.
TODO:

[ ] Add specific implementation
[ ] Add basic CLI/module/click tests. I've heard that it is possible to write tests common for all three interfaces, but I don't know of an example of how to do that
[ ] Add subcommand tests
[ ] Fix mypy check for reusable options
[ ] Conform to code-style
[x] Documentation:

https://github.com/click-contrib/click-man
https://github.com/click-contrib/sphinx-click

Issues:

[x] CI fail because scikit_build_core.cli is being imported. Not sure why it is imported in those tests, but I was trying to make it an optional dependency

Closes: #517
I am not sure yet how to approach all of these, but I wanted to at least make some placeholders for what CLI options would be useful for packaging and gradually work our way up.

Should I add scikit-build-core[cli] as a dependency for [tests]? cli is meant to be an optional runtime dependency anyway and it should satisfy those checks.

Don't worry about it too much, once it's ready (or maybe further down the line, like the setuptools plugin) we might move it to scikit-build-cli.

I've put the current code into https://github.com/scikit-hep/scikit-build-cli and invited you.


MAUI application in release mode crashing on navigate

I created a basic demo application that works fine in debug mode but crashes during page navigation in release mode.
I've attached the crash log from Android and the project files in case they're needed for troubleshooting.
The specific code where the issue occurs is within PostView.razor:
private Task NavigateToDetailsAsync()
{
    return Navigation.NavigateToAsync($"/details/{Post.Id}");
}

Ok probably found out the problem. The AOT and Trimming is causing this issue, it converts the property removing the setter
// Before
public NavigationManager NavigationManager { get; set; }

// After
public NavigationManager NavigationManager { get; }

This causes the dependency injector to give the error found in the crashlog. I've solved this issue inside my project using the combination of TrimmingRootDescriptors
<ItemGroup>
	<TrimmerRootDescriptor Include="Roots.xml" />
</ItemGroup>

<linker>
	<assembly fullname="Microsoft.AspNetCore.Components" preserve="all" />
</linker>

With the file Roots.xml to avoid entirely trimming the Microsoft.AspNetCore.Components package. Probably is worth doing this even inside the nuget package.

Thanks a lot for your research!
I assume this is iOS?

Thanks a lot for your research!
I assume this is iOS?
UPDATE: Ok, I see that's Android...

Thanks a lot for your research! I assume this is iOS?

Sorry I was in a hurry I didn't mention that is android, but i think IOS suffer this issue as well

Yeah, I thought it's iOS, as Android doesn't use AOT compilation with MAUI.
But maybe it does use trimming.


adding password for connect to mysql

@ardinusawan thanks!

plz keep maintenance this code :)
this is great work :D


Log level

Adding a log level is a must have on a framework which use networking stuff (avoiding basic sniffing/spoofing)
Morover, SignalR-Objc....

It would be nice to be able to have a set log level outside of debug builds, or just in general.

SRLog.h
#define SRLogError(frmt, ...)      do{ NSLog((frmt), ##VA_ARGS); } while(0)  - Change these lines to #define SRLogError(frmt, ...)      do{ } while(0).
The NSLog can be added for only the type of logs which we are expecting.


Icon for SVG is a RSS icon

Is this intended? It’s a little weird, made me think it was a .rss file.

@paulozoom, it's not intended. These icons are courtesy of Seti ST3. I'll see what I can do about replacing this with something that actually resembles .svg format.

Thanks!

On 04 Jun 2015, at 23:00, Karel Vuong<EMAIL_ADDRESS>wrote:
@paulozoom https://github.com/paulozoom, it's not intended. These icons are courtesy of Seti ST3 https://github.com/ctf0/Seti_ST3. I'll see what I can do about replacing this with something that actually resembles .svg format.
—
Reply to this email directly or view it on GitHub https://github.com/karelvuong/st-primer/issues/31#issuecomment-109049097.


fix: linter tests

🦟 Bug fix
Fixes #
Summary

fix some linter tests
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@chapulina I appreciate it if you do bloom-release to rolling/humble distribution after merging this PR.


Hot reload of @tool scripts stops working after first reload

Tested versions

Reproduces in v4.3.stable.official [77dcf97d8]
Fixed in v4.4.dev.custom_build [621cadcf6] (confirmed fixed in this commit; prior commit still has issue)

System information
Godot v4.3.stable - macOS 14.6.1 - Vulkan (Forward+) - integrated Apple M3 Max - Apple M3 Max (16 Threads)
Issue description
@tool scripts do not hot reload after the first hot reload when using an external editor.  During the first hot reload the following error is generated:
modules/gdscript/gdscript.cpp:745 - Condition "!p_keep_state && has_instances" is true. Returning: ERR_ALREADY_IN_USE

Note this is not the same issue as #97238 which is 4.4 specific.
Steps to reproduce

Create a new project

Add a Node3D

Attach a script to that Node3D

Make script a @tool script, and add a print to the _ready() function; save it

Switch back to godot editor

Save & reopen scene in editor (seems to be necessary on macos right now)

Confirm print from _ready()

Edit script to change print message; save script

Switch back to godot editor

Godot will display the ERR_ALREADY_IN_USE error

Close and reopen scene and updated _ready() message will be printed

Edit script, changing the print message again: save script

Switch back to godot editor

Godot will not print any new message

close & reopens scene and the message from the previous edit will be shown

Minimal reproduction project (MRP)
hot-reload-issue.zip

Thank you for your report, consolidating in:

https://github.com/godotengine/godot/issues/97138

This has been fixed, and will be available in 4.4.dev3

@AThousandShips This bug is present in 4.3.  I put a comment in #97168 asking for a cherry-pick to 4.3.1, and they asked for a separate 4.3 issue.

My bad, reopening, didn't notice

Prior to that commit, the problem still reproduces.

Did you confirm it was actually occurring in between? Or did you cherry-pic the commit to 4.3?

@AThousandShips bah, you're right.  I only confirmed it was fixed on 4.4 branch.  I'll see if I can cherry pick it.

Since this was bisected to [9fd431f078d7560835da2642c9efe9e235618fe9] it's unlikely to be exactly the same, as the bug didn't occur prior to that commit, but a cherry pick will confirm if it fixes it
I'd say the bug was instead fixed at some point between 4.3 and that commit, to check you should also test in the latest 4.3.x development branch in case it might have been cherry picked then

I cherry-picked<PHONE_NUMBER>6cbc131fbc2640ba6ba238c53017c0 onto 4.3-stable and the fix worked.
I'll test 4.3.x branch clean, and then cherry-picking it onto there.

One important node about #97168 is that they went through looking for other places reload(false) and I think that's why I'm seeing the fix on 4.3.
https://github.com/godotengine/godot/pull/97168#issuecomment-2364072932

That implies a 4.3 specific fix is better than a cherry pick as we want to avoid any unforeseen issues from that

confirmed broken in 4.3 branch as of v4.3.1.rc.custom_build [6699ae789]
cherry-pick<PHONE_NUMBER>6cbc131fbc2640ba6ba238c53017c0 onto 4.3 does have merge conflicts.  Working through them.

That implies a 4.3 specific fix is better than a cherry pick as we want to avoid any unforeseen issues from that

Agreed.  I'll see if I can narrow down  9638220 to the specific changes needed for 4.3.

@AThousandShips I went through<PHONE_NUMBER>6cbc131fbc2640ba6ba238c53017c0 and tried to cut out anything that was specific to 4.4, but couldn't pinpoint anything that didn't also apply to 4.3.
@Hilderin as the author of #97168 can you think of anything in the fix that is 4.4 specific, and should be dropped from a backport to 4.3?

After some digging, I found the source of the issue for tool script reload outside the editor. This is a regression from #89261 which was merged for 4.3. This PR reintroduce the reload call without the true parameter.
We have 2 ways to fix the issue for 4.3.1:
First option

Chery pick #96002
Then cherry pick #97168 since it's basically a fix for a regression introduce in #96002
If you take all the modifications from #97168 but not the modifications from #96002, the external modified scripts that are not already in memory will not be reloaded because of the modifications in EditorFileSystem::_update_scan_actions in the first PR (#96002).

Second option

Only take the modifications in Script::reload_from_file from #97168

Personally, I think we need a bit more testing to cherry pick both PRs into 4.3.1 right now, It already created some problematic regressions. It really depends on when 4.3.1 is coming out and how much it was tested.

@Hilderin thanks for taking a look.
Tomorrow I’ll cherry pick both of those commits on top of the 4.3 branch and use it as my primary godot version while I work on tool scripts. If there’s anything explicit you’d like me to test let me know.

Cherry-picked 46edd6df5581098d8494f9b51a9791dcdabd0ee4 & 46edd6df5581098d8494f9b51a9791dcdabd0ee4 on to the 4.3 branch. There's a merge conflict cherry-picking the second one, but it's a minor change.
They resolve my issue, but I'll continue using this build to see if anything else breaks.

Ok, y'all are gonna think I'm nuts, but this is a cursed build when used in combination with godot-cpp (4.3-stable).
I cherry-picked the following commits onto 6699ae7897658e44efc3cfb2cba91c11a8f5aa6a:

ac6f8c50fc5edd557c23489d23c770ebf8dd6a20
f2c5daecdc0377622de9933b501c2dc0812c2050

I'm working on a gdextension providing hexagon gridmaps.  I've spent probably the last 8 hours trying to figure out why cpu cycles are seemingly lost returning from random functions in the extension.  For example the function says it took 150us, the calling function says it took 3ms.  The place it went really sideways is that if I renamed one of the functions this happened to, the issue went away.  This happened with multiple functions -__-.
This is related to the build because swapping back to 4.3-stable everything resolved itself.  I need to figure out if the issue is that my godot-cpp is technically out of sync with the 4.3.1 godot branch.
I'll try that tomorrow.

I'm really not an expert in godot-cpp, but did you build the engine build with production these scons parameters: production=yes optimize=speed lto=full. I suggest you create a new issue or ask in contributor chat about that if you still have issue.

@Hilderin I had doubts, but yea, you were right.  Switching to the production build did cause all of those inexplicable hangs to disappear.  I am baffled by what could have been causing the repeatable delay that was resolved by renaming my function.
I've been running the production release with the hotfixes for the past few days, and haven't seen any issues.  I only use an external editor (nvim), so I cannot say what other behavior may be impacted by the changes.

Just an update; I've spent the past few days actively developing scripts, and everything is still working great.
Is there anything else y'all would like tested to ensure this gets into the 4.3.1 release?

Cherry-picked 46edd6d & 46edd6d on to the 4.3 branch. There's a merge conflict cherry-picking the second one, but it's a minor change.

You listed two of the same commits, I assume by mistake. Could you please tell us what the second commit was?

Cherry-picked 46edd6d & 46edd6d on to the 4.3 branch. There's a merge conflict cherry-picking the second one, but it's a minor change.

You named the same commit twice; I assume by mistake. Could you please tell us what the second commit was?

I edited it in the original comment when I first posted, but here again:
I cherry-picked the following commits onto https://github.com/godotengine/godot/commit/6699ae7897658e44efc3cfb2cba91c11a8f5aa6a:
https://github.com/godotengine/godot/commit/46edd6df5581098d8494f9b51a9791dcdabd0ee4
https://github.com/godotengine/godot/commit/96382204736cbc131fbc2640ba6ba238c53017c0

And I've been running that build for the past 3 weeks or so with on issues.


Loop

Hello Jacques,
Firstly, let me thank you for producing this code for the SHT2x sensor.
At first I was getting the same error as some others due to not changing the i2c to bus 1 near the end of your code - but now I have it running on SHT25 sensor on bus 1. I did not have to change anything else so your code works just fine on the newer sensor too and I guess it would also for the SHT7x.
I have some code which returns results from 2 other sensors, a MCP9808 Temp sensor and MS5611 Barometric Pressure sensor. Neither written by me but I did manage to integrate them together into one and they run in a loop indefinitely and return results every 10 seconds.
When I try to integrate your code or loop your code, it goes crazy and returns results very quickly no matter what time.sleep I use.
My question is, if I may, and I hope you will forgive me as I am very new to all this:
If you could shed any light on anything obvious which would cause problem with looping? For my project I need to get results returning from my sensor array 24/7 at regular intervals.
Hope it is ok to contact you here, there is no issue with your code but I thought I would give you a try.

Hello,
Glad to hear that it runs on a SHT25 and that you've been able to get it to work.
I'm not sure what could be going wrong, but if you send it through I could take a look and see if I can see anything.
Thanks for the feedback, most appreciated.
Richard.

Hey Jacques,
I tried it two ways, firstly the code I am using for my other two sensors runs within a loop:
while True:

time.sleep(10.0)
when I add your code, the program runs but only returns results for one of the sensors (MCP9808 temp) which happens to be the first sensor the code deals with. Instead of a 10 second delay it also returns results very rapidly.
I tried running your code stand alone within the same loop and get the same result, IE no 10 second delay just a rapid return of results.
Here is the full code, yours and from two other sources which I have only made minor changes to, I have not edited yours in any way except to change to i2c bus 1.
#! /usr/bin/python
Note this script does require Root to run.
Created By: Jonny Fosnight
Date: 2013-03-18
Updated: 2015-04-20
Email<EMAIL_ADDRESS>
Feel free to use the script however you want.
Usage:

##sensor = MS5611()
##sensor.setElevationFt(354.33)
##sensor.read()
##sensor.printResults()

Alternatively all the values can be passed into the initialize function
sensor = MS5611(0,   0x76, 432.8    )
bus, i2c,  elevation
sensor.read()
sensor.printResults()
while True:
import time
import math
## Import Libraries that let python talk to I2C devices
from smbus import SMBus

import Adafruit_MCP9808.MCP9808 as MCP9808

# Define a function to convert celsius to fahrenheit.
def c_to_f(c):
return c * 9.0 / 5.0 + 32.0

Default constructor will use the default I2C address (0x18) and pick a default I2C bus.

For the Raspberry Pi this means you should hook up to the only exposed I2C bus
from the main GPIO header and the library will figure out the bus number based
on the Pi's revision.

For the Beaglebone Black the library will assume bus 1 by default, which is
exposed with SCL = P9_19 and SDA = P9_20.
sensor = MCP9808.MCP9808()

Optionally you can override the address and/or bus number:
#sensor = MCP9808.MCP9808(address=0x20, busnum=2)
Initialize communication with the sensor.
sensor.begin()

temp = sensor.readTempC()
print ""
print "Press CNTRL-C to exit"
print ""
print(time.strftime("Time                      %H:%M:%S"))
print(time.strftime("Date                      %a %d/%m/%Y"))
print ""
print "MCP9808 Temperature:      {0:0.3F} C".format(temp, c_to_f(temp))
print "                          {1:0.3F} F".format(temp, c_to_f(temp))
print ""

class MS5611:
    """Driver for reading temperature/pressure MS5611 Pressure Sensor."""

    def __init__(self, bus = 1, i2c = 0x77, elevation = 103):
        """Initialize the Driver.

        Default bus is 1.  If you have a Rev 1 RPi then you will need to use bus 0.
        A bus object can also be passed in if you are sharing it among other modules

        Arguments (All optional):
        bus -- 0, 1, or a bus object
        i2c -- I2C address
        elevation -- Elevation in meters"""

        if(bus == 0 or bus == 1):
            self.bus = SMBus(bus)
        else:
            self.bus = bus
        self.i2c = i2c
        self.elevation = elevation

    def setElevation(self, elevation):
        self.elevation = elevation

    def setElevationFt(self, elevation):
        self.elevation = elevation / 3.2808

    def setI2c(self, i2c):
        self.i2c = i2c

    def read(self):
        ## Get raw pressure
        self.bus.write_byte(0x77, 0x48)
        time.sleep(0.05)

        D1 = self.bus.read_i2c_block_data(0x77, 0x00)
        D1 = D1[0] * 65536 + D1[1] * 256.0 + D1[2]
        time.sleep(0.05)

        ## Get raw temperature
        self.bus.write_byte(0x77, 0x58)
        time.sleep(0.05)
        D2 = self.bus.read_i2c_block_data(0x77, 0x00)
        D2 = D2[0] * 65536 + D2[1] * 256.0 + D2[2]
        time.sleep(0.05)

        ## Read Constants from Sensor
        if hasattr(self, 'C1'):
            C1 = self.C1
        else:
            C1 = self.bus.read_i2c_block_data(0x77, 0xA2) #Pressure Sensitivity
            C1 = C1[0] * 256.0 + C1[1]
            self.C1 = C1
            time.sleep(0.05)

        if hasattr(self, 'C2'):
            C2 = self.C2
        else:
            C2 = self.bus.read_i2c_block_data(0x77, 0xA4) #Pressure Offset
            C2 = C2[0] * 256.0 + C2[1]
            self.C2 = C2
            time.sleep(0.05)

        if hasattr(self, 'C3'):
            C3 = self.C3
        else:
            C3 = self.bus.read_i2c_block_data(0x77, 0xA6) #Temperature coefficient of pressure sensitivity
            C3 = C3[0] * 256.0 + C3[1]
            self.C3 = C3
            time.sleep(0.05)

        if hasattr(self, 'C4'):
            C4 = self.C4
        else:
            C4 = self.bus.read_i2c_block_data(0x77, 0xA8) #Temperature coefficient of pressure offset
            C4 = C4[0] * 256.0 + C4[1]
            self.C4 = C4
            time.sleep(0.05)

        if hasattr(self, 'C5'):
            C5 = self.C5
        else:
            C5 = self.bus.read_i2c_block_data(0x77, 0xAA) #Reference temperature
            C5 = C5[0] * 256.0 + C5[1]
            self.C5 = C5
            time.sleep(0.05)

        if hasattr(self, 'C6'):
            C6 = self.C6
        else:
            C6 = self.bus.read_i2c_block_data(0x77, 0xAC) #Temperature coefficient of the temperature
            C6 = C6[0] * 256.0 + C6[1]
            self.C6 = C6
            time.sleep(0.05)

        ## These are the calculations provided in the datasheet for the sensor.
        dT = D2 - C5 * 2**8
        TEMP = 2000 + dT * C6 / 2**23

        ## Set Values to class to be used elsewhere
        self.tempC = TEMP/100.0
        self.tempF = TEMP/100.0 * 9.0/5 + 32
        self.tempK = TEMP/100.0 + 273.15

        ## These calculations are all used to produce the final pressure value
        OFF = C2 * 2**16 + (C4 * dT) / 2**7
        SENS = C1 * 2**15 + (C3 * dT) / 2**8
        P = (D1 * SENS / 2**21 - OFF) / 2**15
        self.pressure = P/100.0

        ## Calculate an offset for the pressure.  This is required so that the readings are correct.
        ##   Equation can be found here: http://en.wikipedia.org/wiki/Barometric_formula
        altOffset = math.exp( (-9.80665 * 0.0289644 * self.elevation) / (8.31432 * self.tempK) )
        self.pressureAdj = ( P/altOffset ) / 100.0

    def getTempC(self):
        return self.tempC

    def getTempF(self):
        return self.tempF

    def getPressure(self):
        return self.pressure

    def getPressureAdj(self):
        return self.pressureAdj

    def getBus(self):
        return self.bus

    def printResults(self):
        print ""
        print "MS5611  Temperature:     ", round(self.tempC, 2), "C"
        print "                         ", round(self.tempF, 2), "F"
        print ""
        print "Pressure Absolute:       ", round(self.pressure, 2), " hPa"
        print "         Adjusted:       ", round(self.pressureAdj, 2), "hPa"
        print "         Adjusted:       ", round(self.convert2In(self.pressureAdj), 2), "  inHg"
        print "----------------------------------------------------------------------------------------"

    def convert2In(self, pressure):
        return pressure * 0.0295301

    class SHT21:

#control constants
        _SOFTRESET = 0xFE
        _I2C_ADDRESS = 0x40
        _TRIGGER_TEMPERATURE_NO_HOLD = 0xF3
        _TRIGGER_HUMIDITY_NO_HOLD = 0xF5

        #From: /linux/i2c-dev.h
        I2C_SLAVE = 0x0703
        I2C_SLAVE_FORCE = 0x0706

def __init__(self, device_number=1):

    self.i2c = open('/dev/i2c-%s'%(device_number),'r+',0)
    fcntl.ioctl(self.i2c, self.I2C_SLAVE,0x40)
    self.i2c.write(chr(self._SOFTRESET))
    time.sleep(0.050)

def read_temperature(self):

    self.i2c.write(chr(self._TRIGGER_TEMPERATURE_NO_HOLD))
    time.sleep(0.250)
    data = self.i2c.read(3)
    if self._calculate_checksum(data,2) == ord(data[2]):
        return self._get_temperature_from_buffer(data)

def read_humidity(self):

    self.i2c.write(chr(self._TRIGGER_HUMIDITY_NO_HOLD))
    time.sleep(0.250)
    data = self.i2c.read(3)
    if self._calculate_checksum(data,2) == ord(data[2]):
        return self._get_humidity_from_buffer(data)

def close(self):
    """Closes the i2c connection"""
    self.i2c.close()

def __enter__(self):
    """used to enable python's with statement support"""
    return self

def __exit__(self, type, value, traceback):
    """with support"""
    self.close()

def _calculate_checksum(self, data, nbrOfBytes):
    """5.7 CRC Checksum using teh polynomial given in the datasheet"""
    # CRC
    POLYNOMIAL = 0x131 # //P(x)=x^8+x^5+x^4+1 = 100110001
    crc = 0
    #calculates 8-Bit checksum with given polynomial
    for byteCtr in range(nbrOfBytes):
        crc ^= (ord(data[byteCtr]))
        for bit in range(8,0,-1):
            if (crc & 0x80):
                crc = (crc << 1) ^ POLYNOMIAL
            else:
                crc = (crc << 1)
    return crc

def _get_temperature_from_buffer(self, data):
    """This function reads the first two bytes of data and returns the temperature
    in C by using the following function:
    T = =46.82 + (172.72 * (ST/2^16))
    where ST is the value from the sensor
    """
    unadjusted = (ord(data[0]) << 8) + ord(data[1])
    unadjusted *= 175.72
    unadjusted /= 1 << 16 # divide by 2^16
    unadjusted -= 46.85
    return unadjusted

def _get_humidity_from_buffer(self, data):
    """This function reads the first two bytes of data and returns the relative humidity
    in C by using the following function:
    RH = -6 + (125 * (SRH / 2 ^16))
    where SRH is the value read from the sensor
    """
    unadjusted = (ord(data[0]) << 8) + ord(data[1])
    unadjusted *= 125
    unadjusted /= 1 << 16 # divide by 2^16
    unadjusted -= 6
    return unadjusted

if name == "main":
try:
with SHT21(1) as sht21:
print "SHT25 Temperature: %s"%sht21.read_temperature(), "C"
print "SHT25 Humidity: %s"%sht21.read_humidity(), "%"
print ""
except IOError, e:
print e
print 'Error creating connection to i2c.  This must be run as root'
sensor = MS5611()
sensor.read()
sensor.printResults()
time.sleep(10.0)

I am sorry that ended up getting formatted and looking a complete mess, I wasn't expecting that.
At the moment the program is simply printing results to the screen.
Ultimately I wish to take several readings a minute for each sensor, take an average for each and have them added to some kind of database and upload the readouts to a webpage, so a minute average for each sensor.

Ok, no worries.  In Markdown (the formatting engine that github uses for comments) if you add an indent of say 4 spaces everything will format like code.
It looks to me like the whole file isn't in the loop.  In python whitespace is important, and if the if __name__ == "__main__": line isn't in the main loop as it's not indented.  This is why the final sleep isn't working.
I would recommend not doing quite so much in the main loop of the program.  I suggest splitting it out into separate files.  Here I've got sht21.py untouched in the same folder.  If you move the code for the MS5611 code as well you might find it easier to deal with.
I'm not able to run any of this code I include below, as I don't have a pi to hand, but hopefully you get the idea.  If this proves to work, try moving the MS5611 code out as well and uncommenting the 3 lines to create the class, read the temperature and print the value.
Let me know if you get stuck.
Richard.
    #! /usr/bin/python
    import time
    import math
    from smbus import SMBus
    import Adafruit_MCP9808.MCP9808 as MCP9808

    #this line needs sht21.py to be in the same folder
    #I don't think you'll need to change anything in it.
    import sht21

    #setup all three sensors
    sht25 = sht21.SHT21(1)  #open on /dev/i2c-1

    mcp9808 = MCP9808.MCP9808()
    mcp9808.begin()

    # if you move the code for the MS5611 class into a file called ms5611.py in the same folder
    # python will understand that as a module, and you'll be able to create an instance of that
    # class like this, I'll leave it commented out for now, just to keep things simple.
    #ms5611 = ms5611.MS5611()

    print 'Press Ctrl-C to quit.'
    while True:
            mcp_temp = mcp9808.readTempC()
            sht_temp = sht25.read_temperature()
            #ms5611.read()

            print 'MCP9808 Temperature: {0:0.3F}*C'.format(mcp_temp)
            print 'SHT25   Temperature: {0:0.3F}*C'.format(sht_temp)
            #print 'MS5611  Temperature: {0:0.3F}*C'.format(ms5611.tempC)

            time.sleep(1.0)

In case you were curious I've just recently made a similar module for the new SHT31 sensor, and tested it on raspberry pi 2 model b. The code isn't particularly clean yet and I'm definitely an elementary programmer, but it works. If you wanted to see the code I can post it here.

I am one of the unfortunate ones for which sht21.py does not work. I'm trying find the reason. @nadanks7 and @Prod69 can I ask what your Revision numbers are in the output of cat /proc/cpuinfo ? Mine is 000e and, like I said, it doesn't work for me.

i2cdetect -y 1  gives me UU instead of b30 so I guess that's my issue. It's not sht21.py


Observations stop at 2022

Describe the bug
Observations stop at 2022 while "df_timeseries.Rdata" contains data also for 2023.
At least "df_ts"  at the end of 05_occurrence_indicators_preprocessing.Rmd does. For example Oryctolagus cuniculus (taxonKey 2436940) has at least an observation in grid cell 1kmE3843N3089 for 2023.
To Reproduce
Steps to reproduce the behavior:

Build app in docker
Click on 'global indicators'
filter taxa for 'Oryctolagus cuniculus'
See part of the error ea last observed == 2022 while it should be 2023
click on observations
See other part of the error ea observations go to 2022 while they should go to 2023.

Expected behavior
Observations & last observed should be data driven and based on the occurrence cubes (ea df_timeseries). In case of  'Oryctolagus cuniculus' & many more like it this should be 2023.
Screenshots

For the main table, it is based on the file "data_input_checklist_indicators.tsv" which seems to have last observed year 2022:
> exotenData[grepl("Oryctolagus cuniculus", exotenData$scientificName), c("scientificName", "last_observed", "locality")]
                           scientificName last_observed
1: Oryctolagus cuniculus (Linnaeus, 1758)          2022
2: Oryctolagus cuniculus (Linnaeus, 1758)          2022
3: Oryctolagus cuniculus (Linnaeus, 1758)          2022
4: Oryctolagus cuniculus (Linnaeus, 1758)          2022
                         locality
1:                         België
2: Brussels Hoofdstedelijk Gewest
3:                     Vlaanderen
4:                       Wallonië

For the histogram, it is based on the file "be_alientaxa_cube.csv", which seems to have last observations in 2021:
> rawData = fread(file.path("~/git/alien-species-portal/dataS3", "be_alientaxa_cube_aspbo.csv"), stringsAsFactors = FALSE, na.strings = "", drop = "min_coord_uncertainty")
> table(rawData[rawData$taxonKey == 2436940, "year"])
year
1912 1930 1931 1933 1934 1936 1937 1938 1939 1940 1945 1947 1948 1949 1950 1951
   2    3    1    2    3    8    7   11   21   13    7    3   16   11    5    2
1952 1953 1954 1960 1961 1967 1975 1976 1981 1982 1984 1985 1986 1987 1988 1989
   1    4    2    3    3    2    2    9    1   10    5   11   36    9    2   10
1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005
  36   18   40   84  104  446  267  342  377  280  208  182  217    5    5    7
2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021
  62   32   86  315  287  339  314  326  427  391  443  411  391  470  544  665

For the timeseries though, we have indeed observations in 2023:
> table(timeseries[timeseries$taxonKey == 2436940, "year"])

1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966
6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663
1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982
6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663
1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998
6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663
1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014
6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663 6663
2015 2016 2017 2018 2019 2020 2021 2022 2023
6663 6663 6663 6663 6663 6663 6663 6663 6663

@SanderDevisscher It looks like these files in https://github.com/inbo/aspbo/tree/uat/data/output/UAT_processing need an update?
Data sources

For the main table, it is based on the file "data_input_checklist_indicators.tsv" which seems to have last observed year 2022:
> exotenData[grepl("Oryctolagus cuniculus", exotenData$scientificName), c("scientificName", "last_observed", "locality")]
                           scientificName last_observed
1: Oryctolagus cuniculus (Linnaeus, 1758)          2022
2: Oryctolagus cuniculus (Linnaeus, 1758)          2022
3: Oryctolagus cuniculus (Linnaeus, 1758)          2022
4: Oryctolagus cuniculus (Linnaeus, 1758)          2022
                         locality
1:                         België
2: Brussels Hoofdstedelijk Gewest
3:                     Vlaanderen
4:                       Wallonië

The checklist will probably lagg behind the cube since it is not data driven. Maybe we can overwrite the last_observed based on the be_alientaxa_cube.csv.

For the histogram, it is based on the file "be_alientaxa_cube.csv", which seems to have last observations in 2021:
> rawData = fread(file.path("~/git/alien-species-portal/dataS3", "be_alientaxa_cube_aspbo.csv"), stringsAsFactors = FALSE, na.strings = "", drop = "min_coord_uncertainty")
> table(rawData[rawData$taxonKey == 2436940, "year"])
year
1912 1930 1931 1933 1934 1936 1937 1938 1939 1940 1945 1947 1948 1949 1950 1951
   2    3    1    2    3    8    7   11   21   13    7    3   16   11    5    2
1952 1953 1954 1960 1961 1967 1975 1976 1981 1982 1984 1985 1986 1987 1988 1989
   1    4    2    3    3    2    2    9    1   10    5   11   36    9    2   10
1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005
  36   18   40   84  104  446  267  342  377  280  208  182  217    5    5    7
2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021
  62   32   86  315  287  339  314  326  427  391  443  411  391  470  544  665

I've only updated the timeseries based on the be_alientaxa_cube.csv but never the be_alientaxa_cube.csv itself. I'll include some logic in the timeseries flow to export the cube as well.

For the timeseries though, we have indeed observations in 2023:
> table(timeseries[timeseries$taxonKey == 2436940 & timeseries$obs >= 1, "year"])

1951 1952 1953 1954 1960 1961 1967 1975 1976 1981 1982 1984 1985 1986 1987 1988
   2    2    4    2    4    4    2    2   12    2   10    6   11   34    9    2
1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004
  12   46   17   42   86  103  374  255  325  478  280  210  198  217    5    4
2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020
   5   64   39   79  326  377  516  607  553  837  808<PHONE_NUMBER> 1366 1512
2021 2022 2023
1453 1096 1347

@SanderDevisscher It looks like these files in https://github.com/inbo/aspbo/tree/uat/data/output/UAT_processing need an update? Data sources

update

The data for 2023 is now included however 2023 cannot be selected

I've reverted the be_alientaxa_cube because the spread just isn't correct (see https://github.com/trias-project/indicators/issues/124)


Added HTML focused Questions with Answers

Will be adding more, please review the 10 added.

Please merge it in October as then only it will help me in Hacktoberfest :)

Sure would be updating them in October :)


datalog: The "header" timestamp should be enable even without calling log.set_labels()

The log.set_labels() feature has a default value for the timestamp argument, currently log.MILLISECONDS.
When the set_labels() function is called this default unit for the timestamp is correctly applied. However, we also want to make sure that the timestamp is set with the default value even if set_labels() isn't called.
So this small programme should log the temperature with a timestamp, which it currently doesn't do:
import log

log.add(temp=temperature())

Related:

https://github.com/microbit-foundation/micropython-microbit-v2/issues/92

Is it correct to just call uBit.log.setTimeStamp(TimeStampFormat::Seconds) when the device starts up?  Will that add a new header each time the micro:bit is reset?

Is it correct to just call uBit.log.setTimeStamp(TimeStampFormat::Seconds) when the device starts up? Will that add a new header each time the micro:bit is reset?

I'm not sure, @JohnVidler do you know the answer to this question?

I've had a dig and it looks like if you call setTimeStamp(...) it'll mark the headers as dirty, and the micro:bit will write them to the log when the next actual bit of real data is written; so as the initial value is None, if you set it to anything else you'll get a new header row as soon as you write new data.

So, if MicroPython calls setTimeStamp(...) on startup, but it never adds new data it doesn't add any data to the log file, is that right?
Do you know if it also trigger the MY_DATA.HTM file to appear?

Btw, the MakeCode source code can be found here:

C++ side https://github.com/microsoft/pxt-microbit/tree/v4.1.17/libs/flashlog
Extension https://github.com/microsoft/pxt-microbit/tree/v4.1.17/libs/datalogger

Looks like a CODAL programme only doing this will still trigger the MY_DATA.HTM file:
#include "MicroBit.h"

MicroBit uBit;

int  main() {
    uBit.init();

    uBit.log.setTimeStamp(TimeStampFormat::Seconds);

    while (true) {
        uBit.display.print("hello world!");
    }
}

So the only way to avoid this might be to start each log module function with a "if not init: initialise()" as it's currently done in MakeCode.
Another option might be to run that on import? Although import side effects are generally frown upon, but at least we are not constantly running an if at each function call.
Do we have any other options?

Another option might be to run that on import? Although import side effects are generally frown upon, but at least we are not constantly running an if at each function call.

Considering that import radio now turns the radio on, I think it's fair enough that import log sets the default timestamp.

Doing import log now sets the default timestamp format to seconds, see 6c511644812a0b15671a7c846d897afeadf3072c


Teams Service Administrator role seems to be all sufficient for a Teams Admin except for assigning a service number to a resource account

Teams Service Administrator role seems to be all sufficient for a Teams Admin except for assigning a service number to a resource account. Could you please fix (add ability to this role) or advise what additional role is required to avoid needing Global Administrator role to perform this task?
Many Thanks

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

ID: 6b434530-6bf2-6e00-6eae-6fa043d022ce
Version Independent ID: caab785f-e3a4-831a-87d8-26934a9f834f
Content: Use Microsoft Teams administrator roles to manage Teams - Microsoft Teams
Content Source: Teams/using-admin-roles.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@SvenBell Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @SvenBell, thank you for your feedback.
Teams Service Administrator should be enough to assign a service number to a resource account. Are you using Direct Routing?

@SvenBell  Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

We are not using direct routing (we are using call plans). Still no update on doco page with what roles are required to achieve assigning number to resource account. You cannot do it from CSP (DAP) TAC portal. Please resolve,


account authentication failed

I got this error after press start button in-game at main menu screen of bdo.

your client might be out of date

I am . i just update the game yesterday with the main launcher. your launcher works well but after i changed the region from eu to na in your launcher i got this error in both region now

ok, I was able to reproduce this issue, working on it now, thanks for letting me know

version 1.1.3 should address this issue, feel free to open up this issue if doesn't.


(PUP-4952) Use vendored curl in concurrency acceptance test

Previously, the concurrent catalog request test was failing in
SLES 10 due to an old version of cURL on the system. This commit
updates the test to use our vendored cURL when it is present, or
fall back to the system cURL if it is not.

Tested locally in SLES 10, SLES 11, RedHat 7, CentOS 5, Debian 8, Oracle 6 and Ubuntu 1004. The test is currently skipped in Windows and OSX.

I'd normally suggest using beaker's host['pathseparator'] instead of hardcoding ':', but since the test is confined to skip on windows, would require significant work to get it working, and we don't support windows master platforms, I'd say don't worry about it.


Missing tether.min.js

GET http://localhost:3000/components/tether/dist/js/tether.min.js 404 (Not Found)
On every site in the chrome js console

fixed with 5fe85c3
Please rerun bower install


Remote Jupyter Kernels started by VS Code do not have same names as Jupyter Notebook/Lab

When starting a kernel session from VS Code (against AzML remote jupyter), then name of the session should be similar to what Jupyter notebook generates (today jupyter extension uses a GUID, as a result the links to open the notebook does not work in AzML)

Let’s keep one issue, closing as a duplicate of #13424


add vote.alphadao.money

Hi! What is your PR about?

[ ] Add or edit a skin
[x] Add a custom domain for your space
[ ] Add an alias to migrate your space

Updated requested changes

There is a conflict in your PR since the domains.json file has been updated, can you resolve it?
To prevent conflicts, it is recommended to add your subdomain between two existing domains rather than at the end or beginning of the list.

updated, moved our entry a few lines up


Debug npm pack

Change-type: patch

@klutchell this is the best I was able to come up with. Seems like at least in versionbot's instance, npm pack puts the tgz in the current working directory. Could be something weird with permissions/etc., but the error is silent and would be tricky to debug further. There is a closed issue in GH node/npm archive about "inconsistent npm pack output", but no resolution.

I kind of suspect this is due to using an old npm version on node 12, checking the npm 6 docs I don't see the --pack-destination: https://docs.npmjs.com/cli/v6/commands/npm-pack

I kind of suspect this is due to using an old npm version on node 12, checking the npm 6 docs I don't see the --pack-destination: https://docs.npmjs.com/cli/v6/commands/npm-pack

Yeah, it's definitely a node12 thing, since I was able to replicate locally. Should we keep this hack or take it out and assume node12 builds will fail? @Page- @klutchell


Change error strings to not be capitalized

This is to follow Rust's and Go's guidelines.
Possible sources of these error strings:

string_of_* functions

Completed as part of Timedesc 3.1.0 release


Join with --prefix-components-with-info-prop does not produce any output since version 1.9.0

Describe the bug
redocly-cli crashes on join if schema property contains a null value
To Reproduce
Steps to reproduce the behavior:

Given the two OpenAPI file(s)

openapi1.yaml
openapi: '3.0.2'
info:
  title: API1
  version: '1.0'
servers:
  - url: https://api.server.test/v1
paths:
  {}
components:
  schemas:
    Schema1:
      type: string

openapi2.yaml
openapi: '3.0.2'
info:
  title: API2
  version: '1.0'
servers:
  - url: https://api.server.test/v1
paths:
  {}
components:
  schemas:
    Schema2:
      type: string
      default: null
      nullable: true

Run redocly join --prefix-components-with-info-prop title openapi1.yaml openapi2.yaml
No output is provided

Expected behavior
Join works as it did before version 1.9.0 was released.
Redocly Version(s)
1.9.0

Taking a look. Thanks for reporting!

@simon-spinner could you confirm the issue got resolved in v1.9.1?


Signature of Array#slice! is incorrect

Fix for https://github.com/sorbet/sorbet/issues/1988
Updates the type signature.
Motivation
Per the docs and current Ruby behavior, Array#slice! can return nil.
See https://ruby-doc.org/core-2.6.4/Array.html#method-i-slice-21

@DarkDimius that sounds great!

go/SlmyadJ0


ISSUES WITH atexit(), on_exit(), AND pthread_cleanup_pop()

  Description: These functions execute with the following bad properties:

               1. They run with interrupts disabled,
               2. They run in supervisor mode (if applicable), and
               3. They do not obey any setup of PIC or address
                  environments. Do they need to?
               4. In the case of task_delete() and pthread_cancel() without
                  deferred cancellation, these callbacks will run on the
                  thread of execution and address context of the caller of
                  task_delete() or pthread_cancel().  That is very bad!

               The fix for all of these issues it to have the callbacks
               run on the caller's thread as is currently done with
               signal handlers.  Signals are delivered differently in
               PROTECTED and KERNEL modes:  The delivery involves a
               signal handling trampoline function in the user address
               space and two signal handlers:  One to call the signal
               handler trampoline in user mode (SYS_signal_handler) and
               on in with the signal handler trampoline to return to
               supervisor mode (SYS_signal_handler_return)

               The primary difference is in the location of the signal
               handling trampoline:

               - In PROTECTED mode, there is on a single user space blob
                 with a header at the beginning of the block (at a well-
                 known location.  There is a pointer to the signal handler
                 trampoline function in that header.
               - In the KERNEL mode, a special process signal handler
                 trampoline is used at a well-known location in every
                 process address space (ARCH_DATA_RESERVE->ar_sigtramp).
  Status:      Open
  Priority:    Medium Low.  This is an important change to some less
               important interfaces.  For the average user, these
               functions are just fine the way they are.

Close this, let's track the issue in https://github.com/apache/incubator-nuttx/issues/1263.


"cargo owner --add" doesn't seem to work with teams

Problem
We've tried a few different ways of adding a team to grant the publishing rights to Nushell's repo, but haven't been able for this to work.
Here's what we're seeing:
〉 cargo owner --add github:nushell:publishing
error: failed to invite owners to crate `nu` on registry at https://crates.io

Caused by:
  the remote server responded with an error: could not find the github team nushell/publishing

The team does exist on github:

Steps

see above

Possible Solution(s)
It'd be nice to perhaps give a better error to help add a team if there's an issue with adding the specific team. Otherwise, I think this should work based on the name of the org + team.
Notes
No response
Version
cargo 1.66.0 (d65d197ad 2022-11-15)
release: 1.66.0
commit-hash: d65d197ad5c6c09234369f219f943e291d4f04b9
commit-date: 2022-11-15
host: aarch64-apple-darwin
libgit2: 1.5.0 (sys:0.15.0 vendored)
libcurl: 7.84.0 (sys:0.4.55+curl-7.83.1 system ssl:(SecureTransport) LibreSSL/3.3.6)
os: Mac OS 13.0.1 [64-bit]

Sorry about that. Looks like you hit this issue. Have you tried following that steps?

Yes, I think that ultimately was it. I had to revoke permissions, then have crates.io ask for them again after revoking them (log out then log back in, and then it asks), then make sure that nushell was in the grant for the permissions it asked for.
Something that would help a lot here is to show some screenshots of the github and crates.io side. I read through the text a bunch but it didn't click what exactly was meant since I kept seeing crates.io listed in the oauth apps that had permission. It was only after the 5th read it finally hit me that it was too old to have the proper permissions granted.

I could take over this issue if wanted :)

@VincentWo go ahead! I guess adding one or two screenshots as what JT said under this paragraph is sufficient. You may need an org account to reproduce the error.

Will do - thank you for the pointer.
But I wonder whether it would also be a goal to improve the error message

Oh yup. Nice suggestion! We could also provide a link to https://doc.rust-lang.org/cargo/reference/publishing.html#github-permissions in the error message.

As discussed in #12511, I have opened a PR against crates.io here: https://github.com/rust-lang/crates.io/pull/8593

I am actually not sure if the documentation is wrong or incomplete. Somebody with a GitHub org account should try to first login with a key without the read:org scope, and then figure out what needs to be cleaned up in order to get things working.