Animation disappears

When the apng of an acyclic animation is used, there is no problem with the first loading, and then the animation with < img > appended disappears
`function addImg() {
var imgD = new Image();
imgD.src = ""
document.body.appendChild(imgD)
}
setInterval(function() {
addImg();
}, 3000)
`

Could you provide the minimal example code on codepen.io or on similar service?

Oh, I found out it was my own problem. I'm sorry.


[1.12] Enchantment Applicator/Extractor - Interaction with Mystical Ag Armors

**Industrial Foregoing Version: **
industrialforegoing-1.12.2-1.12.13-237
**TeslaCoreLib Version: **
tesla-core-lib-1.12.2-1.0.15
Hello!  I'm playing with your mod within the modpack Dungeons Dragons & Space Shuttles v6.3, and noticed that none of the Mystical Agriculture armors can be used with your Enchantment Extractor or Applicator.  Could they be added?  Thanks in advance!

:wave: Sorry but Industrial Foregoing has ended support for version 1.12. I'm closing this issue as it will no longer be updated for that version. Thanks for playing with the mod.


chore(gitlab-mr-action): remove deprecation of projectid for template…

projectid is now passed through the query parameter project in the repoUrl. It still allows people to not use the projectid and use the repoUrl with the owner and repo query parameters instead. This makes it easier to publish to repositories instead of writing the full path to the project.
Changed the parseUrl function so it uses a switch-case statement which makes the function more readable than having several if-else statements.
Created an auxiliary function called checkRequiredParams. The function checks if the required parameters (given as arguments) are present in the URL.
The function parseUrl uses checkRequiredParams to verify that all the required query parameters are present in the repo's URL. This replaces the if-else mess with a switch statement for better readability.

Signed-off-by: Borja González<EMAIL_ADDRESS>:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hello @jhaals ! I thought of providing some test cases and the outcome of those in order to hopefully proof to you that the frontend is passing the projectid through query parameters.

Successfully creating MR with projectID:
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>?project=<some_gitlabID>'
The output of the template action is:

Successfully creating MR with projectPath (owner and repo as query parameters):
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>?owner=<some_owner>&repo=test01'
The output of the template action is:

Unsuccessfully creating MR without query prameters:
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>'
The output of the template action is that the owner is missing, as expected:

Unsuccessfully creating MR with owner stated as a query parameter, but not repo:
We have the following in the repoUrl field of the publish:gitlab:merge-request:
repoUrl: '<gitlab_host>?owner=<some_owner>'
The output of the template action is that the repo is missing, as expected:

Hope that this is enough to satisfy your first question :)

@satrox28 can you take a look at this PR and see if this makes sense? I'm a little lost on this one to be honest, and I don't have much knowledge on Gitlab

Hello @benjdlambert ! I can give you a little bit of context:
Maybe you remember this PR where the projectID for publishing GitLab MRs was deprecated because of redundancy between the projectID and the projectPath: https://github.com/backstage/backstage/pull/11946
The inconvenience that this brought to us, is that we couldn't use the projectID for GitLab projects at all and were forced to pass owner and repo as query parameters in order to specify the location of the GitLab project we wanted to publish a MR into, which we don't really like.
Because of this, we wanted to bring the functionality of using the projectID back, and at the same time, allow users to use the RepoUrlPicker if they want (i.e. passing owner and repo as query parameters), but to simplify things, we decided to pass the GitLab Project ID to the project query parameter... otherwise we would have to pass the projectID field into the parseUrl function, which would have involved more changes in all the places that call that function.
Hopefully this gave a little bit more of insight of the changes that I made :)

Also @jhaals I am confused with the changeset thing, because in one of your first comments, you suggested me to remove it, but now you ask for a changeset with minor changes, and that is what I had in the beginning 🙊.

Also @jhaals I am confused with the changeset thing, because in one of your first comments, you suggested me to remove it, but now you ask for a changeset with minor changes, and that is what I had in the beginning 🙊.

Sorry if I was unclear. The changeset is still needed and is what end up in the CHANGELOG.md for this individual package. It's good to keep that text short and sweat and only mention what's necessary for the user of the package to know.
If I try to summarise this for end users I would suggest something like:

Removed deprecation of projectid from the publish:gitlab:merge-request action as this field is still used.

What happened internally in the utils with the switch refactor is too detailed information for the consumers of this package :)

Hello @jhaals! Regarding your comment here: https://github.com/backstage/backstage/pull/14019#discussion_r1004142770, it is the second option. The INPUT FIELD projectID would be deprecated, BUT it will be passed via the repoURL input field :)

Thank you very much for your help @jhaals ! :)

Thank you for contributing during Hacktoberfest 🍂! You can claim the Backstage Hacktoberfest Holopin at https://bck.st/hacktoberfest-holopin 🙌🏻


[Feature Request] Username case insensitive

Just want the username to be case insensitive so that User and user would both work. Its a small thing, but it gets annoying since mobile tends to automatically capitalize things.

The username for non-root users are already case-insensitive by default. You can try this on the demo site by logging in with username tEsT and password 1234 and it will still log you right in.
For root users on the other hand, we can't do case-insensitive because the hash will not match otherwise. In our documentation, we encourage users to set up a secondary account and mark the second account as an Admin user even if they are the only user in the system. see here
The username for root users will remain case-sensitive because we hash both username and password of the root user to ensure highest level of security, see Technical Docs

Thank you for the detailed write up and links. I appreciate the thought put into it the docs.


Non Contaminated Packing into trl

Hi, I'm trying to merge your custom non packing implementation into trl. And I'm facing some issues in getting it to work. is it possible to use the packedDataset class alone without having to merge all your code into trl?
Please look at my PR and sample colab notebook (I know the implementation isn't right without flash attention but I cant get a running training loop)
The error I get is
[/usr/local/lib/python3.10/dist-packages/transformers/trainer.py](https://localhost:8080/#) in compute_loss(self, model, inputs, return_outputs)
   2807         else:
   2808             if isinstance(outputs, dict) and "loss" not in outputs:
-> 2809                 raise ValueError(
   2810                     "The model did not return a loss from the inputs, only the following keys: "
   2811                     f"{','.join(outputs.keys())}. For reference, the inputs it received are {','.join(inputs.keys())}."

ValueError: The model did not return a loss from the inputs, only the following keys: logits. For reference, the inputs it received are input_ids,attention_mask.

Hi nivibilla,
I think there is a bug in your PR, I have just made a comment in your PR: https://github.com/huggingface/trl/pull/1235#discussion_r1457699675
If you fix this as I suggested, you won't run into error any more. And if you run with flash-attention, it will work well. I already tested and saw it working.
Let me know if you have any questions !


AzureAD: Missing Group Parameters

Feature Request
I'm new to this world (I am more of an ops guys).
I've been using Terraform's AzureAD provider and was noticing little things about the AzureAD groups that can be set in the portal, but not via Terraform and the go sdk.
When I create a group, there is not an option to:

Set a description
Specify the membership type (assigned, dyn user, dyn device)
License assignment

Are these things that are not available in the SDK or api spec? (I'm not sure how to check the api spec for this but I would be interested to know how).
Azure/azure-sdk-for-go: group create
Azure/azure-sdk-for-go: GroupCreateParameters

Hi @midacts there is a AdditionalProperties in GroupCreateParameters struct, maybe you can use this map to store these additional properties.


mongo_gem needs make package

Please install the make package before building an extension:
==> shard11: chef_gem[bson_ext] (mongodb::mongo_gem line 20) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
==> shard11: ---- Begin output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: STDOUT: Building native extensions.  This could take a while...
==> shard11: STDERR: ERROR:  Error installing bson_ext:
==> shard11: 	ERROR: Failed to build gem native extension.
==> shard11:
==> shard11:     /opt/chef/embedded/bin/ruby -r ./siteconf20150304-10675-1bhk51p.rb extconf.rb
==> shard11: checking for asprintf()... yes
==> shard11: checking for ruby/st.h... yes
==> shard11: checking for ruby/regex.h... yes
==> shard11: checking for ruby/encoding.h... yes
==> shard11: creating Makefile
==> shard11:
==> shard11: make "DESTDIR=" clean
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make "DESTDIR="
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make failed, exit code 127
==> shard11:
==> shard11: Gem files will remain installed in /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/bson_ext-1.12.0 for inspection.
==> shard11: Results logged to /opt/chef/embedded/lib/ruby/gems/2.1.0/extensions/x86_64-linux/2.1.0/bson_ext-1.12.0/gem_make.out
==> shard11: ---- End output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: Ran /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" returned 1
==> shard11:
==> shard11: Cookbook Trace:
==> shard11: ---------------
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:20:in `block in from_file'
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:19:in `each'
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:19:in `from_file'
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/replicaset.rb:24:in `from_file'
==> shard11:
==> shard11: Relevant File Content:
==> shard11: ----------------------
==> shard11: /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:
==> shard11:
==> shard11:  13:  end
==> shard11:  14:
==> shard11:  15:  package sasldev_pkg do
==> shard11:  16:    action :nothing
==> shard11:  17:  end.run_action(:install)
==> shard11:  18:
==> shard11:  19:  node['mongodb']['ruby_gems'].each do |gem, version|
==> shard11:  20>>   chef_gem gem do
==> shard11:  21:      version version
==> shard11:  22:    end
==> shard11:  23:  end
==> shard11:  24:
==> shard11:
==> shard11: [2015-03-04T16:20:34+00:00] ERROR: Running exception handlers
==> shard11: [2015-03-04T16:20:34+00:00] ERROR: Exception handlers complete
==> shard11: [2015-03-04T16:20:34+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> shard11: [2015-03-04T16:20:34+00:00] ERROR: chef_gem[bson_ext] (mongodb::mongo_gem line 20) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
==> shard11: ---- Begin output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: STDOUT: Building native extensions.  This could take a while...
==> shard11: STDERR: ERROR:  Error installing bson_ext:
==> shard11: 	ERROR: Failed to build gem native extension.
==> shard11:
==> shard11:     /opt/chef/embedded/bin/ruby -r ./siteconf20150304-10675-1bhk51p.rb extconf.rb
==> shard11: checking for asprintf()... yes
==> shard11: checking for ruby/st.h... yes
==> shard11: checking for ruby/regex.h... yes
==> shard11: checking for ruby/encoding.h... yes
==> shard11: creating Makefile
==> shard11:
==> shard11: make "DESTDIR=" clean
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make "DESTDIR="
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make failed, exit code 127
==> shard11:
==> shard11: Gem files will remain installed in /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/bson_ext-1.12.0 for inspection.
==> shard11: Results logged to /opt/chef/embedded/lib/ruby/gems/2.1.0/extensions/x86_64-linux/2.1.0/bson_ext-1.12.0/gem_make.out
==> shard11: ---- End output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: Ran /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" returned 1
==> shard11: [2015-03-04T16:20:34+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
==> shard11: chef_gem[bson_ext] (mongodb::mongo_gem line 20) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
==> shard11: ---- Begin output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: STDOUT: Building native extensions.  This could take a while...
==> shard11: STDERR: ERROR:  Error installing bson_ext:
==> shard11: 	ERROR: Failed to build gem native extension.
==> shard11:
==> shard11:     /opt/chef/embedded/bin/ruby -r ./siteconf20150304-10675-1bhk51p.rb extconf.rb
==> shard11: checking for asprintf()... yes
==> shard11: checking for ruby/st.h... yes
==> shard11: checking for ruby/regex.h... yes
==> shard11: checking for ruby/encoding.h... yes
==> shard11: creating Makefile
==> shard11:
==> shard11: make "DESTDIR=" clean
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make "DESTDIR="
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make failed, exit code 127
==> shard11:
==> shard11: Gem files will remain installed in /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/bson_ext-1.12.0 for inspection.
==> shard11: Results logged to /opt/chef/embedded/lib/ruby/gems/2.1.0/extensions/x86_64-linux/2.1.0/bson_ext-1.12.0/gem_make.out
==> shard11: ---- End output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: Ran /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" returned 1
==> shard11:
==> shard11: Cookbook Trace:
==> shard11: ---------------
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:20:in `block in from_file'
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:19:in `each'
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:19:in `from_file'
==> shard11:   /var/chef/cache/cookbooks/mongodb/recipes/replicaset.rb:24:in `from_file'
==> shard11:
==> shard11: Relevant File Content:
==> shard11: ----------------------
==> shard11: /var/chef/cache/cookbooks/mongodb/recipes/mongo_gem.rb:
==> shard11:
==> shard11:  13:  end
==> shard11:  14:
==> shard11:  15:  package sasldev_pkg do
==> shard11:  16:    action :nothing
==> shard11:  17:  end.run_action(:install)
==> shard11:  18:
==> shard11:  19:  node['mongodb']['ruby_gems'].each do |gem, version|
==> shard11:  20>>   chef_gem gem do
==> shard11:  21:      version version
==> shard11:  22:    end
==> shard11:  23:  end
==> shard11:  24:
==> shard11:
==> shard11: [2015-03-04T16:20:34+00:00] ERROR: Running exception handlers
==> shard11: [2015-03-04T16:20:34+00:00] ERROR: Exception handlers complete
==> shard11: [2015-03-04T16:20:34+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> shard11: [2015-03-04T16:20:34+00:00] ERROR: chef_gem[bson_ext] (mongodb::mongo_gem line 20) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
==> shard11: ---- Begin output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: STDOUT: Building native extensions.  This could take a while...
==> shard11: STDERR: ERROR:  Error installing bson_ext:
==> shard11: 	ERROR: Failed to build gem native extension.
==> shard11:
==> shard11:     /opt/chef/embedded/bin/ruby -r ./siteconf20150304-10675-1bhk51p.rb extconf.rb
==> shard11: checking for asprintf()... yes
==> shard11: checking for ruby/st.h... yes
==> shard11: checking for ruby/regex.h... yes
==> shard11: checking for ruby/encoding.h... yes
==> shard11: creating Makefile
==> shard11:
==> shard11: make "DESTDIR=" clean
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make "DESTDIR="
==> shard11: sh: 1: make: not found
==> shard11:
==> shard11: make failed, exit code 127
==> shard11:
==> shard11: Gem files will remain installed in /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/bson_ext-1.12.0 for inspection.
==> shard11: Results logged to /opt/chef/embedded/lib/ruby/gems/2.1.0/extensions/x86_64-linux/2.1.0/bson_ext-1.12.0/gem_make.out
==> shard11: ---- End output of /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" ----
==> shard11: Ran /opt/chef/embedded/bin/gem install bson_ext -q --no-rdoc --no-ri -v "1.12.0" returned 1
==> shard11: [2015-03-04T16:20:34+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

this could be a fix:
https://github.com/edelight/chef-mongodb/pull/370


crazy timestamp bug in feather?

Hello the dream team,
Thanks for this wonderful package. I was playing with feather and some timestamps and I noticed some dangerous behavior. Maybe it is a bug.
Consider this
import pandas as pd
import feather
import numpy as np

df = pd.DataFrame({'string_time_utc' : [pd.to_datetime('2018-02-01 14:00:00.531'),
                                  pd.to_datetime('2018-02-01 14:01:00.456'),
                                  pd.to_datetime('2018-03-05 14:01:02.200')]})

df['timestamp_est'] = pd.to_datetime(df.string_time_utc).dt.tz_localize('UTC').dt.tz_convert('US/Eastern').dt.tz_localize(None)

df
Out[17]:
          string_time_utc           timestamp_est
0 2018-02-01 14:00:00.531 2018-02-01 09:00:00.531
1 2018-02-01 14:01:00.456 2018-02-01 09:01:00.456
2 2018-03-05 14:01:02.200 2018-03-05 09:01:02.200

Here I create the corresponding EST timestamp of my original timestamps (in UTC time).
Now saving the dataframe to csv or to feather will generate two completely different results.
df.to_csv('P://testing.csv')
df.to_feather('P://testing.feather')

Switching to R.
Using the good old csv gives me something a bit annoying, but expected. R thinks my timezone is UTC by default, and wrongly attached this timezone to timestamp_est. No big deal, I can always use with_tz or even better: import as character and process as timestamp while in R.
> dataframe <- read_csv('P://testing.csv')
Parsed with column specification:
cols(
  X1 = col_integer(),
  string_time_utc = col_datetime(format = ""),
  timestamp_est = col_datetime(format = "")
)
Warning message:
Missing column names filled in: 'X1' [1]
>
> dataframe %>% mutate(mytimezone = tz(timestamp_est))
# A tibble: 3 x 4
     X1 string_time_utc         timestamp_est
  <int> <dttm>                  <dttm>
1     0 2018-02-01 14:00:00.530 2018-02-01 09:00:00.530
2     1 2018-02-01 14:01:00.456 2018-02-01 09:01:00.456
3     2 2018-03-05 14:01:02.200 2018-03-05 09:01:02.200
  mytimezone
  <chr>
1 UTC
2 UTC
3 UTC

Now look at what happens with feather:
> dataframe <- read_feather('P://testing.feather')
>
> dataframe %>% mutate(mytimezone = tz(timestamp_est))
# A tibble: 3 x 3
  string_time_utc         timestamp_est           mytimezone
  <dttm>                  <dttm>                  <chr>
1 2018-02-01 09:00:00.531 2018-02-01 04:00:00.531 ""
2 2018-02-01 09:01:00.456 2018-02-01 04:01:00.456 ""
3 2018-03-05 09:01:02.200 2018-03-05 04:01:02.200 ""

My timestamps have been converted!!! pure insanity.
Am I missing something here?
Thanks!!

Can you report in Apache Arrow? Someone will need to investigate once we get R fully moved over from this codebase

hi wes you mean on the JIRA? can you send me the link? thx!

https://issues.apache.org/jira/browse/ARROW

done

Thanks. It will need a more descriptive / objective title

like "INSANE timestamp ERROR - win 400$ click here" I guess

We have hundreds of issues. We need to be able to understand the nature of the problem from the title

sure i was kidding :)


Closes Issue #550

Issue #550: MultiDirChooser cannot handle paths with spaces.
Fix: instead of the general formatter, use formatters.multiFileChooser, which handles spaces in paths without problems.

Whoops, branched from 1.0.4 after my other change. I'll get you a cleaner one.


UI enhancements

I've made some improvements to UI by using a color palette. It fixes #42

Improved the design of login, signup and home page.
Display success messages when authentication - Login, Logout
Display an info message when user registers with name that already exists.
Display an error message when password doesn't match confirm password during signup

Here's a gif,

Here is a Screenshot of home page

I've made some improvements to UI by using a color palette. It fixes #42

Improved the design of login, signup and home page.
Display success messages when authentication - Login, Logout
Display an info message when user registers with name that already exists.
Display an error message when password doesn't match confirm password during signup

Here's a gif,

Here is a Screenshot of home pag

I've made some improvements to UI by using a color palette. It fixes #42

Improved the design of login, signup and home page.
Display success messages when authentication - Login, Logout
Display an info message when user registers with name that already exists.
Display an error message when password doesn't match confirm password during signup

Here's a gif,

Here is a Screenshot of home page

Amazing work!! @hariramjp777

Thank you @diyajaiswal11


Overwrite service

Adds a new command 3scale update to copy changes from one existing service to another

Companion to 3scale/3scale-api-ruby#20

I've added a bit of structure to see the different steps of the copy process better.
Also, 95% of these steps are exactly the same as used in the copy command, so I think it could be worth extracting the logic somewhere (now it's ServiceUpdater class, but can be renamed/moved).
There is an option added to only copy the mapping rules (--rules-only), and to optionally delete the existing mapping rules on target before copying the ones from source (-f).


fix(README): Updating command help in README

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


ModuleNotFoundError: No module named 'utils'

from utils.dataset import ijgiDataset as Dataset
SITSMamba-main/Main_SITSMamba.py
Possible fix please @VSainteuf

Hi @clotilda-0 I don't think your issue refers to the utae-paps repository as it does not contain an ijgiDataset nor a Main_SITSMamba.py script.


(maint) Fixing typo

Fixing a minor typo in the name of the flag provided to puppetserver ca.

Can one of the admins verify this patch?

Waiting for CLA signature by @wintermanc3r
@wintermanc3r - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html


add functions for float64, bool and array

thanks for this!
LGTM other than those minor comments

squashed and pushed to master in 50593fd

thanks!


Shift from framework to library

So.. this approach is good on paper but causes many problems in practice for development of pex-renderer. What about moving to more of a library than framework approach with pex-shaders? So pure utils only and all the setup and wrapper code would move back to pex-renderer? Basically all chunks with main() in them... that would allow us develop new features in pex-renderer and move out to pex-shaders when stable.

@dmnsgn any thoughts on this? My initial idea for pex-shaders was more of Lygia than removing every single line of GLSL from pex-renderer.  Ideally this lib would have only pure functions and everything requiring uniforms or setup would be left in pex-renderer for faster iteration and prototyping. So pex-shaders is more like glsl-utils than pex-renderer-glsl

Standard vert/frag will have a big git diff so that would be a "rip-off the bandaid" point (ie. git history will be meh but it has to happen at some point

Because of change to GLSL 300?


Values are frozen from time to time

Last update: 10.02.2034

Configuration
configuration.yaml.log.log
Describe the bug
From time to time, the values from the heating pump are not updated (e.g. temperatures, power (even if the heating pump is running). Adjusting the parameters (single value loading, timing to 5 minutes, ...) are not successfully. Time for interrupts are not equal. Please see screenshot with external temperature attached.

Debug log

home-assistant_idm_heatpump_2024-02-20T09-31-33.409Z.log

The screenshot is weird indeed... But it shows the time frame 12. Feb to 18. Feb and the logs you provided are from 20. Feb 07:07 to 10:31. Do these weird gaps happen during the time frame of the logs too? If so when?
Also, can you rule out network issues? At first glance the screenshot seems like the heat pump is not reachable and the Modbus requests from Home Assistant fail.

Added a screenshot with a more focussed event: Start @~09:06
The heat pump is connected via ethernet and I am not aware of any connection issues. In case I have seen a frozen value in HA, I still have access to the IDM system via the app or the browser.

Ah okay, I'm guessing you're using an older Raspberry Pi or something similarly slow (or your network connection is incredibly slow). Seems you're hitting the 10 second timeout for an update. I'll see what I can do about that. In the meantime turning of the "Read sensors individually" ("Sensoren einzeln laden") option might at least improve things.

In v0.8.0 the timeout is now 30s by default and can be configured via the integration's config UI. Also the logs (even without debug logging) now explicitly state when an update was aborted because of a timeout.
Depending on your setup, you may need to set a timeout higher than 30s. If you need an excessively large value to make it work, please open another issue with some details about your setup.


bigquery: Honor NOT NULL on import (fixes #45)

For imports that required a custom SELECT to fix up the data, we used to
lose NOT NULL declarations on the columns, because we used SELECT to
create the destination table, and there's no way to represent NOT NULL.
This patch rips all that out and replaces it with multi-statement SQL
scripts that include explicit CREATE TABLE statements.
This cleans up a bunch of dodgy logic in bigquery::write_remote_data
that I didn't really like. The whole business with if_exists and
upserts is now less hackish.

I'm going to merge this now and let it be reviewed later.


SRP Swagger Updates for Jan23 [2023-01-01] Api Version GA

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

/azp run

  "post": {

you cannot do POST on a resource insteance , ARM semantics do not allow for this operation. in ARM a POST can only be called as an action on top of a resource instance ..

Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-01-01/storage.json:903 in a96115f. [](commit_id = a96115fe27e34a8b50924fc43a8d42c0568335ac, deletion_comment = False)

Please review the failures from : https://github.com/Azure/azure-rest-api-specs/pull/23918/checks?check_run_id=13445755848and fix newly introduced errors

  "post": {

you cannot do POST on a resource insteance , ARM semantics do not allow for this operation. in ARM a POST can only be called as an action on top of a resource instance ..
Refers to: specification/storage/resource-manager/Microsoft.Storage/stable/2023-01-01/storage.json:903 in a96115f. [](commit_id = a96115f, deletion_comment = False)

This is POST being called as an action, storage account is the resource instance and migration is the action

Please review the failures from : https://github.com/Azure/azure-rest-api-specs/pull/23918/checks?check_run_id=13445755848and fix newly introduced errors

I have updated the swagger to address most of the errors, had a couple of questions on the following:
200 response for a LRO POST operation must have a response schema specified.
Location: Microsoft.Storage/stable/2023-01-01/storage.json#L903
-This looks like a new requirement. Currently, this operation does not have any response. My understanding is that there is a standard response returned by the sdk for async operations currently, and we do not define the response schema for them elsewhere in the swagger. Why is this operation different?
validate is a query parameter. Post operation must not contain any query parameter other than api-version.
Location: Microsoft.Storage/stable/2023-01-01/storage.json#L914
-currently in the swagger we have query paramater for post operation, for example for "/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.Storage/storageAccounts/{accountName}/hnsonmigration". Why can we not follow that pattern here?
Error response content of long running operations must follow the error schema provided in the common types v2 and above.
Location: Microsoft.Storage/stable/2023-01-01/storage.json#L954
-other long running operations have the same schema for error response as this one, can we continue to use the same?

/azp run

@rkmanda another PR I reassigned to you.

Can you please also fix the newly added swagger lint errors : https://github.com/Azure/azure-rest-api-specs/pull/23918/checks?check_run_id=14600114509

Can you please also fix the newly added swagger lint errors : https://github.com/Azure/azure-rest-api-specs/pull/23918/checks?check_run_id=14600114509

I had synced with Roopesh, he mentioned that in this case we can just specify 202 and that should be sufficient:
[6/27 12:25 PM] Roopesh Manda
when an API doesnt return a response body you should use 204 as the status code
[6/27 12:25 PM] Roopesh Manda
so you can specify just 202 as the status code in the swagger for now and that should be sufficient
[6/27 12:26 PM] Udit Sharma
But the guideline is for lro post to have both 200 and 202 specified, so are you saying we have to return a response?
[6/27 12:26 PM] Roopesh Manda
The guideline doesnt account for a case where there is no response in the end. We are in the process of fixing that rule
like 1

@microsoft-github-policy-service agree company="Microsoft"


Add set_all to layer_freezer

Signed-off-by: Jael Gu<EMAIL_ADDRESS>

Codecov Report

Merging #615 (64bca40) into training (dfce03d) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           training     #615      +/-   ##
============================================
+ Coverage     60.02%   60.06%   +0.04%
============================================
  Files           150      150
  Lines          6046     6050       +4
  Branches        905      907       +2
============================================
+ Hits           3629     3634       +5
  Misses         2163     2163
+ Partials        254      253       -1

Impacted Files
Coverage Δ

towhee/trainer/utils/layer_freezer.py
80.55% <100.00%> (+2.43%)
:arrow_up:

towhee/data/random_erase.py
90.47% <0.00%> (+4.76%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm
/approve


[BUG] Test data missing (extension.c files and more) missing in 70.1.0 sdist

setuptools version
70.1.0
Python version
3.12.4
OS
Gentoo Linux amd64
Additional environment information
No response
Description
The sdist archives for 70.1.0 are missing some of test data, particularly extension.c files needed by tests. This is causing test failures:
ERROR setuptools/tests/test_bdist_wheel.py::test_no_scripts - subprocess.CalledProcessError: Command '['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3', 'setup.py', 'bdist_wheel', '-b', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0', '-d', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0']' returned non-zero exit status 1.
ERROR setuptools/tests/test_bdist_wheel.py::test_unicode_record - subprocess.CalledProcessError: Command '['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3', 'setup.py', 'bdist_wheel', '-b', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0', '-d', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0']' returned non-zero exit status 1.
ERROR setuptools/tests/test_bdist_wheel.py::test_wheelfile_line_endings - subprocess.CalledProcessError: Command '['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3', 'setup.py', 'bdist_wheel', '-b', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0', '-d', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0']' returned non-zero exit status 1.
FAILED setuptools/tests/test_bdist_wheel.py::test_limited_abi - subprocess.CalledProcessError: Command '['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3', 'setup.py', 'bdist_wheel', '-b', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/build', '-d', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/dist']' returned non-zero exit status 1.

Expected behavior
Tests passing.
How to Reproduce
Unpack setuptools-60.1.0.tar.gz and run tests.
  Wait for command to complete.  If
        the exit code was zero then return, otherwise raise
        CalledProcessError.  The CalledProcessError object will have the
        return code in the returncode attribute.

        The arguments are the same as for the call function.  Example:

        check_call(["ls", "-l"])
        """
        retcode = call(*popenargs, **kwargs)
        if retcode:
            cmd = kwargs.get("args")
            if cmd is None:
                cmd = popenargs[0]
>           raise CalledProcessError(retcode, cmd)
E           subprocess.CalledProcessError: Command '['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3', 'setup.py', 'bdist_wheel', '-b', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0', '-d', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0']' returned non-zero exit status 1.

cmd        = ['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3',
 'setup.py',
 'bdist_wheel',
 '-b',
 '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0',
 '-d',
 '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0']
kwargs     = {}
popenargs  = (['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3',
  'setup.py',
  'bdist_wheel',
  '-b',
  '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0',
  '-d',
  '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0'],)
retcode    = 1

/usr/lib/pypy3.10/subprocess.py:369: CalledProcessError
-------------------------------------------------------- Captured stdout setup --------------------------------------------------------
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/complexdist
copying complexdist/__init__.py -> build/lib/complexdist
installing to /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
running install
running install_lib
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/complexdist
copying build/lib/complexdist/__init__.py -> /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/complexdist
running install_egg_info
running egg_info
creating complex_dist.egg-info
writing complex_dist.egg-info/PKG-INFO
writing dependency_links to complex_dist.egg-info/dependency_links.txt
writing entry points to complex_dist.egg-info/entry_points.txt
writing requirements to complex_dist.egg-info/requires.txt
writing top-level names to complex_dist.egg-info/top_level.txt
writing manifest file 'complex_dist.egg-info/SOURCES.txt'
reading manifest file 'complex_dist.egg-info/SOURCES.txt'
writing manifest file 'complex_dist.egg-info/SOURCES.txt'
Copying complex_dist.egg-info to /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/complex_dist-0.1-py3.10.egg-info
running install_scripts
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/complex_dist-0.1.dist-info/WHEEL
creating '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0/complex_dist-0.1-py3-none-any.whl' and adding '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0' to it
adding 'complexdist/__init__.py'
adding 'complex_dist-0.1.dist-info/METADATA'
adding 'complex_dist-0.1.dist-info/WHEEL'
adding 'complex_dist-0.1.dist-info/entry_points.txt'
adding 'complex_dist-0.1.dist-info/top_level.txt'
adding 'complex_dist-0.1.dist-info/RECORD'
removing /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/simpledist
copying simpledist/__init__.py -> build/lib/simpledist
installing to /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
running install
running install_lib
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/simpledist
copying build/lib/simpledist/__init__.py -> /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/simpledist
running install_egg_info
running egg_info
creating simple.dist.egg-info
writing simple.dist.egg-info/PKG-INFO
writing dependency_links to simple.dist.egg-info/dependency_links.txt
writing requirements to simple.dist.egg-info/requires.txt
writing top-level names to simple.dist.egg-info/top_level.txt
writing manifest file 'simple.dist.egg-info/SOURCES.txt'
reading manifest file 'simple.dist.egg-info/SOURCES.txt'
writing manifest file 'simple.dist.egg-info/SOURCES.txt'
Copying simple.dist.egg-info to /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/simple.dist-0.1-py3.10.egg-info
running install_scripts
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/simple.dist-0.1.dist-info/WHEEL
creating '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/dist0/simple.dist-0.1-py3-none-any.whl' and adding '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0' to it
adding 'simpledist/__init__.py'
adding 'simple.dist-0.1.dist-info/METADATA'
adding 'simple.dist-0.1.dist-info/WHEEL'
adding 'simple.dist-0.1.dist-info/top_level.txt'
adding 'simple.dist-0.1.dist-info/RECORD'
removing /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
running bdist_wheel
running build
running build_py
creating build
creating build/lib
copying headersdist.py -> build/lib
installing to /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
running install
running install_lib
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
copying build/lib/headersdist.py -> /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0
running install_headers
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/headers.dist-0.1.data
creating /tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/build0/headers.dist-0.1.data/headers
-------------------------------------------------------- Captured stderr setup --------------------------------------------------------
/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/lib/pypy3.10/site-packages/setuptools/__init__.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************

!!
  dist.fetch_build_eggs(dist.setup_requires)
warning: build_py: byte-compiling is disabled, skipping.

/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/lib/pypy3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()
warning: install_lib: byte-compiling is disabled, skipping.

[06/20/24 05:31:14] ERROR    listing git files failed - pretending there aren't any                                           git.py:26
warning: build_py: byte-compiling is disabled, skipping.

/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/lib/pypy3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!
  self.initialize_options()
warning: install_lib: byte-compiling is disabled, skipping.

[06/20/24 05:31:19] ERROR    listing git files failed - pretending there aren't any                                           git.py:26
warning: build_py: byte-compiling is disabled, skipping.

/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/lib/pypy3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

          Wait for command to complete.  If
        the exit code was zero then return, otherwise raise
        CalledProcessError.  The CalledProcessError object will have the
        return code in the returncode attribute.

        The arguments are the same as for the call function.    Wait for command to complete.  If
        the exit code was zero then return, otherwise raise
        CalledProcessError.  The CalledProcessError object will have the
        return code in the returncode attribute.

        The arguments are the same as for the call function.    Wait for command to complete.  If
        the exit code was zero then return, otherwise raise
        CalledProcessError.  The CalledProcessError object will have the
        return code in the returncode attribute.

        The arguments are the same as for the call function.  Example:

        check_call(["ls", "-l"])
        """
        retcode = call(*popenargs, **kwargs)
        if retcode:
            cmd = kwargs.get("args")
            if cmd is None:
                cmd = popenargs[0]
>           raise CalledProcessError(retcode, cmd)
E           subprocess.CalledProcessError: Command '['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3', 'setup.py', 'bdist_wheel', '-b', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/build', '-d', '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/dist']' returned non-zero exit status 1.

cmd        = ['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3',
 'setup.py',
 'bdist_wheel',
 '-b',
 '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/build',
 '-d',
 '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/dist']
kwargs     = {}
popenargs  = (['/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/bin/pypy3',
  'setup.py',
  'bdist_wheel',
  '-b',
  '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/build',
  '-d',
  '/tmp/portage/dev-python/setuptools-70.1.0/temp/pytest-of-portage/pytest-0/popen-gw0/test_limited_abi0/dist'],)
retcode    = 1

/usr/lib/pypy3.10/subprocess.py:369: CalledProcessError
-------------------------------------------------------- Captured stdout call ---------------------------------------------------------
running bdist_wheel
running build
running build_ext
building 'extension' extension
creating build
creating build/temp.linux-x86_64-pypy310
x86_64-pc-linux-gnu-gcc -march=znver2 --param=l1-cache-size=32 --param=l1-cache-line-size=64 -O2 -pipe -frecord-gcc-switches -fPIC -I/tmp/portage/dev-python/setuptools-70.1.0/work/setuptools-70.1.0-pypy3/install/usr/include -I/usr/include/pypy3.10 -c extension.c -o build/temp.linux-x86_64-pypy310/extension.o
-------------------------------------------------------- Captured stderr call ---------------------------------------------------------
cc1: fatal error: extension.c: No such file or directory
compilation terminated.
error: command '/usr/lib/ccache/bin/x86_64-pc-linux-gnu-gcc' failed with exit code 1

Thanks!

I will cut a release soon.


Set default purchase order status to draft upon creation

Set default purchase order status to draft upon creation

Fixed via 22d679a96d0f4dde653a733c8704f79c017e49c1


Error when switching from virtualized to non-virtualized table

material-react-table version
v1.9.1
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it
Following the recommendation of not using the virtualized grid if the set of rows is small I decided to set the "enableRowVirtualization" property dependent on the size of the dataset since I receive a variable number of rows. The problem comes when the previous render the property was false (a small number of rows), and the next render it receives a larger number of rows switching into virtualized mode, in that case the component will cause the next warning:
Warning: React has detected a change in the order of Hooks called by MRT_TableBody. This will lead to bugs and errors if not fixed. For more information, read the Rules of Hooks: https://reactjs.org/link/rules-of-hooks

   Previous render            Next render
   ------------------------------------------------------
1. useMemo                    useMemo
2. useMemo                    useMemo
3. undefined                  useReducer
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

that will turn into this error:
Uncaught Error: Rendered more hooks than during the previous render.
    at updateWorkInProgressHook (react-dom.development.js:16507:1)
    at updateReducer (react-dom.development.js:16568:1)
    at Object.useReducer (react-dom.development.js:17898:1)
   ....

Minimal, Reproducible Example - (Optional, but Recommended)
Simply set the property "enableRowVirtualization" to some conditional like
enableRowVirtualization={data.length > 200}
Then as you start the app pass it an empty array as usual, and after that load a dataset larger than 200 rows
Screenshots or Videos (Optional)
No response
Terms

[ ] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

The docs explicitly say that this is not supported

WARNING: Don't enable row or column virtualization conditionally. It may break React's Rule of Hooks, and/or cause other UI jumpiness.

@DiegoBM The only other option would be for me to have the virtualizer always on internally. So react-virtual would run whether or not it was needed or was being used to virtualize the rows. This is all because useVirtualizer is a react hook, and cannot be called conditionally.
Here is the relevant code where this happens internally in MRT if you are curious or have suggestions: https://github.com/KevinVandy/material-react-table/blob/main/packages/material-react-table/src/body/MRT_TableBody.tsx#L121

after this convo, I realize this probably should be refactored/improved, but it will be a bit of a bundle size increase to implement.

Thanks for the feedback @KevinVandy. I was reviewing that code this evening when I realised that it came from there. The only thing I could think of was to always call useVirtualizer even if it's result is not used later on, since being a hook should never be called conditionally anyways, but I presume that you made it conditional because there is some sort of noticeable overhead resulting of calling useVirtualizer?.
Otherwise I guess that the only option would be either to recreate the table with keys as I did, or to render two different tables for the virtualized and non-virtualized case, which we can do on our end as well.

Another option is to pass an "on/off" prop to the virtualizer hook. Not ideal, but it's a possible solution.
My issue is that the error doesn't match the issue. It doesn't say "don't use the virtualizer dynamically", it says something about useReducer which isn't clear.
I had an infinite-scrolling table which dynamically kicked in the virtualizer past 50 items and don't remember seeing this error, but in another app with 200 entries per page, this error was causing his app to error.

After even more consideration over the past year, I think we're going to keep the requirement that virtualization can never be enabled conditionally. It already causes other CSS/feature changes under the hood depending on whether or not it is enabled, and having it switch between different css layout modes at a certain row count is jolting. It's just best to always have it enabled if you think you need it.
The warning in the docs about it causing extra overhead is slightly true, but it is there mostly to discourage anyone who is already using pagination set to 10 rows to enabling it for now good reason.
Still open to suggestions (though I don't really want to have MRT always running virtualization logic even when it's not being used), but will close this for now.


What is implemented?

Could you please detail what are OData features and versions implemented in package?

Hi @renanwilliam at the moment we have extensive read only support for V3, at the moment data requests are sorted, exposure of models is automatic with a trait. and we have setup a system to simulate singletons through odata functions.
we are dedicating most of our time at the moment to extending feature support and stabilizing write support in the parent POData project. But if there are any specific features that you are looking for @CyberiaResurrection is the ideal contact for laravel side, and i would be the best person to contact for any oData related bits.

Hi,
I think that is a good ideia keep some control like this in README.md file:
Support Feature

[ ] Full CRUD Support
[ ] $count
[ ] $filter

[ ] Comparison Operators

[ ] eq
[ ] ne
[ ] lt
[ ] le
[ ] gt
[ ] ge

[ ] Logical Operators

[ ] and
[ ] or
[ ] not

[ ] Comparison Operators

[ ] has

[ ] String Functions

[ ] indexof
[ ] contains
[ ] endswith
[ ] startswith
[ ] length
[ ] substring
[ ] tolower
[ ] toupper
[ ] trim
[ ] concat

[ ] Arithmetic Operators

[ ] add
[ ] sub
[ ] mul
[ ] div
[ ] mod

[ ] Date Functions

[ ] year
[ ] month
[ ] day
[ ] hour
[ ] minute
[ ] second
[ ] fractionalseconds
[ ] date
[ ] time
[ ] totaloffsetminutes
[ ] now
[ ] mindatetime
[ ] maxdatetime

[ ] Math Functions

[ ] round
[ ] floor
[ ] ceiling

[ ] $select
[ ] $top
[ ] $skip
[ ] $orderby
[ ] $expand
[ ] $metadata generation (Nonstandard)

It will be important to mensure how mature is the repository and will attract more contributors.

@CyberiaResurrection I think he is onto something here, I think we should implement that on this and the parent project.

Yes, that is a damn good idea - given ancestral claims of "full OData v3 support, guaranteed" have shown to be a little hollow.  @renanwilliam is on fire today.

@renanwilliam we are adding your list at the moment, I just wanted to ask what you mean by  $metadata generation (Nonstandard) ?

@c-harris non-standard $metadata is not relevant I think, in other repositories it's show a document using another format that isn't the described in OData specification and is used in a start level of development just for tests. Your package already the standard $metadata format and that is the most important feature.


Allow to use Symfony 4

Also dropped unmaintained version <2.7 from supported.
Fixes #82.

@stloyd anything i can help to get this one merged?

@ElectricMaxxx I will check this during this week. There is small BC as you can see in tests that I need to address.

I guess once this is fixed and released, we can re-run https://github.com/liip/LiipMonitorBundle/pull/151

thanks Joseph  👍


Sauce ss local domain

This addresses #452.
SauceLabs uses a not-fully-reliable, slow proxy solution to work around
issues with testing remotely against localhost domain in Internet
Explorer (and Safari).

Use 'samplestack.local' domain for Sauce-based e2e tests.
Add this domain to hosts file in travis.
Update readme with instruction.

BREAKING CHANGE: users will need to configure such a domain, typically
in their hosts file, to point to <IP_ADDRESS>
(Note, this PR also includes one totally inconsequential docs change change that was missed in previous merge)
Gaurav: I have added the hosts file entry to engrlab-128-218 and tested -- it works.
I have put in an IT request to add it to rh6-intel64-80-qa-dev-2. It will also be need to be added to the Mac testing machine (and any machine on which people want to run tests with SauceLabs).
/cc @popzip

Hold the show... looks like the change to Travis might not have worked.... investigating.

We've now gotten a successful travis test on all browsers with this PR, though it is still hit or miss each time it runs, so we're good to merge once approved.

Please go ahead with the checkin . Thanks

I kept this notification in my inbox because i was copied but i'm not really clear on what this is or why specific heads up to me....

I cc'ed you because the change impacts developers -- they need to add the mentioned entry to their hosts file if they want to test against IE in SauceLabs.  No action required.

Ahh okay thanks. Should that be added to readme?

Already done: https://github.com/marklogic/marklogic-samplestack/commit/44f610a85ef7d5365e17e8e6314acea509c689e7#diff-6c553da8165c139f5c774e716ad334da


Global location for plugins

Enable /resources/plugins/[plugin-name].html as a global location for plugins.  Respond will first look in the /public/sites/[site-name]/plugins/[plugin-name].html folder and then look in /resources/plugins/[plugin-name].html.

Coming in beta4.

Added as part of R6 beta 4.


Show that functionality is polyfilled

First off, thanks for an amazing library! It's easy to use and just a pleasure to work with.
I am creating my own library, where I want to warn the developer (in development) when this polyfill isn't loaded while not being supported by the browser. Basically, if the developer has forgot to add your polyfill.
Looking at the source code, I can't tell how to actually accomplish this. Is there a flag or something I could look for? I'd be more than happy to contribute a pull request if this is something you want to support.

Have the same problem, please, make a flag in the window.


Dependabot alert: glob-parent before 6.0.1 vulnerable to Regular Expression Denial of Service (ReDoS)

Hi team,
My project use mocha as the test framework, we found it has a dependabot alert about the glob-parent. When we try to upgrade it, it tell us<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>via<EMAIL_ADDRESS>Could you please check this alert and upgrade it?
Best regards

The alert is false, report this to GitHub: https://github.com/github/advisory-database/pull/531


fix flaky test com.ctrip.framework.apollo.configservice.service.AppNa…

Issue:
In the course of test execution, the testAppNamespace within AppNamespaceServiceWithCacheTest advances to a point at line 197 in AppNamespaceServiceWithCache.
https://github.com/ThugJudy/apollo/blob/5e49df687c64cf6f64f0210ba3ebc13084468757/apollo-configservice/src/main/java/com/ctrip/framework/apollo/configservice/service/AppNamespaceServiceWithCache.java#L197
Here, it retrieves a set of keys, generating a hash result from the following that appears to be nondeterministic. The same hash in line 201 is partition divides the array into subarrays of a given size. When the order changes we can expect different subarrays.
The following command can be used to reproduce assertion failures and verify the fix:
mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl apollo-configservice -Dtest=com.ctrip.framework.apollo.configservice.service.AppNamespaceServiceWithCacheTest#testAppNamespace

Proposed Solution:
To address this issue effectively, we propose sorting the values in the line 197 of AppNamespaceServiceWithCache to be inserted into the list.
List<Long> ids = appNamespaceIdCache.keySet().stream().sorted().collect(Collectors.toList());
This approach ensures the stability of the test, by making sure that the list has a maintained order, thereby mitigating any potential flakiness.
Test Environment:
openjdk version "1.8.0_351"
Apache Maven 3.6.3
Operating System: macOS
Product Version: 13.5.2

Please let me know if you have any concerns or questions.

Hello,
I think it is good to mention how to reproduce the issue and try to make the PR easier to read like 1. Problem description 2. Solution ... .

Hello, I think it is good to mention how to reproduce the issue and try to make the PR easier to read like 1. Problem description 2. Solution ... .

Hi I have made the changes as per your suggestions. Kindly let me know if it is fine

LGTM

Nice work. Looks valid to me.
A small suggestion is that not every developer knows what is NonDex, so it would be better if a link to Nondex is included in the PR

Nice work. Looks valid to me.
A small suggestion is that not every developer knows what is NonDex, so it would be better if a link to Nondex is included in the PR

Done. Can u kindly check it now?

Nice work. Looks valid to me.
A small suggestion is that not every developer knows what is NonDex, so it would be better if a link to Nondex is included in the PR

Done. Can u kindly check it now?

Yes. Looks good now


[5.2] Introduce deleteIfExists($path) method to filesystem

This adds deleteIfExists($path) to the Filesystem.
I often find myself writing something like this:
if (Storage::disk('my-disk')->exists('my-file.txt')) {
    Storage::disk('my-disk')->delete('my-file.txt');
}

This looks a lot clearer to me though:
Storage::disk('my-disk')->deleteIfExists('my-file.txt');

I'm a little confused because you modified Illuminate\Filesystem\Filesystem which is not what Storage is accessing. Storage uses Illuminate\Filesystem\FilesystemAdapter.

Damn, you're so right. That comes from working on multiple things at the same time. 🙈
I'll submit a new PR later.


Pathfinder: Wrath of the Righteous abnormally poor performance

Game: Pathfinder: Wrath of the Righteous
Unusually poor performance or GPU underutilization most of the time (FPS hovering at around 10-15), DXVK HUD/MangoHUD both reporting 100% GPU utilization, GPU temperatures suggest that is not the case. Another user on Steam with the same GPU has reported identical behavior.
However sometimes when launched the game performs as it should (FPS is a stable 60 throughout), I have been trying to reliably replicate this for the past day with no success.
With WineD3D the game performs as it should (hovers at around 40-50 FPS on average), but the game crashes on the first loading screen after the main menu.
I have attached d3d11.log files for both properly and poorly performing P:WotR, a dxgi.log file and an Apitrace .trace, which like WineD3D crashed on the first loading screen after the main menu.
System information

OS: Kubuntu 20.04
GPU: Nvidia GTX 1050 2GB
CPU: AMD Ryzen 3 1200 (4) @ 3.700GHz
RAM: 8GB DDR4 @ CL15 2666
Driver: 460.91.03
Wine version: Tested with Wine Staging 6.16 / Lutris Wine 6.13, 6.14, 6.0 / Proton Experimental, 6.3-6 / Proton GE 6.16, 6.13, 6.8
DXVK version: Mostly 1.9.1, earlier versions bundled with Lutris Wine, Proton & GE exhibit identical behavior.

Apitrace file(s)

https://mega.nz/file/n44wQAwQ#iL3yBw8t4MFKrZ2xUDn0dpZV5kQmhVZCTLCKnci85eQ

Log files

d3d11.log (Proper performance): Wrath_d3d11.log
d3d11.log (Poor performance): Wrath_d3d11.log
dxgi.log(File is identical for proper/poor performance): Wrath_dxgi.log

2GB of VRAM is not enough to run this game on DXVK, when replaying the trace I already see usage go up to 2.4GB. This is especially problematic on Nvidia where VK_EXT_memory_priority is not supported and the game cannot use video memory that's already in use by background processes.

Thank you for the swift response!
I suppose I'll likely have to play it on Windows then, though I still find it odd that when it works it works perfectly, with 2GB VRAM on the GPU and all.

I still find it odd that when it works it works perfectly, with 2GB VRAM on the GPU and all.

Nvidias Windows D3D11 driver actually has memory management unlike DXVK (doubly so on the Nvidia Linux Vulkan driver).


Drop jellyfish-jellyscripts dep

Change-type: patch
Signed-off-by: Josh Bowling<EMAIL_ADDRESS>

@balena-ci I self certify!


Mac OS 10.12 Beta (16A238m)

Bracket crash after a while, everythings gets blank

Do you know if Chrom49 works with that OS?

Relabeling native-shell just to check if evrything will work with newer version of it.


Improve unity/nounity description in linux doc

Jenkins Build Summary
Built from this commit
Built at 20180516 - 00:28:50
Test Results

Build Type
Log
Result
Status

docs
logfile
1 cases, 0 failed, t: 2s
PASS :white_check_mark:

clang.debug.unity
logfile
1021 cases, 0 failed, t: 250s
PASS :white_check_mark:

coverage
logfile
1021 cases, 0 failed, t: 619s
PASS :white_check_mark:

clang.debug.nounity
logfile
1019 cases, 0 failed, t: 145s
PASS :white_check_mark:

clang.debug.unity, PARALLEL_TESTS=false
logfile
1021 cases, 0 failed, t: 481s
PASS :white_check_mark:

gcc.debug.unity
logfile
1021 cases, 0 failed, t: 242s
PASS :white_check_mark:

msvc.debug
logfile
1017 cases, 0 failed, t: 561s
PASS :white_check_mark:

gcc.debug.nounity
logfile
1019 cases, 0 failed, t: 484s
PASS :white_check_mark:

clang.release.unity
logfile
1020 cases, 0 failed, t: 328s
PASS :white_check_mark:

gcc.debug.unity -Dstatic=true
logfile
1021 cases, 0 failed, t: 242s
PASS :white_check_mark:

gcc.release.unity
logfile
1020 cases, 0 failed, t: 352s
PASS :white_check_mark:

msvc.debug, PROJECT_NAME=rippled_classic
logfile
1017 cases, 0 failed, t: 1169s
PASS :white_check_mark:

msvc.release
logfile
1016 cases, 0 failed, t: 508s
PASS :white_check_mark:

Codecov Report

Merging #2535 into develop will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #2535      +/-   ##
===========================================
- Coverage    70.66%   70.64%   -0.03%
===========================================
  Files          696      696
  Lines        54405    54405
===========================================
- Hits         38448    38436      -12
- Misses       15957    15969      +12

Impacted Files
Coverage Δ

src/ripple/basics/DecayingSample.h
77.77% <0%> (-8.34%)
:arrow_down:

src/ripple/server/impl/BaseHTTPPeer.h
87.03% <0%> (-3.09%)
:arrow_down:

src/ripple/protocol/impl/STVar.cpp
86.07% <0%> (-2.54%)
:arrow_down:

src/ripple/core/impl/Workers.cpp
98.88% <0%> (-1.12%)
:arrow_down:

src/ripple/core/impl/JobQueue.cpp
89.04% <0%> (-0.48%)
: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 f31ca28...2c161c0. Read the comment docs.

In 1.1.0-b2


Add test for prometheus handler

Coverage increased (+0.6%) to 20.791% when pulling 91191b079c7f166b263ced038c6a73606616c46a on prometheus_test into 711c879a19d8d63a0c24b154f6a1b518f7ca1025 on master.


temporary AZ fix

Same as #67 but with fudged dates, reverting 6a32fdb will fix the dates

Pull Request Test Coverage Report for Build 222

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

Totals

Change from base Build 220:
0.0%

Covered Lines:
925

Relevant Lines:
1391

💛  - Coveralls


403 XD

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[X] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
now i to have this pronlem
Bloxstrap Log
Bloxstrap_20241003T182630Z.log

Read. Other. Posts.

Read. Other. Posts.


Feature: text align

I think calculate some text align will not be easy part.
I have some labels as "status" messages, and those will be handy to have in center, but problem is status messages have different length, so fixed position is not good.

The Label widget supports only left alignment. However you can display text using the Writer or CWriter object - the stringlen method returns the length of the string in pixels. You can therefore determine the start location for centre alignment. One approach might be to subclass Label although I haven't considered this in detail.

I have pushed an update: the Label widget now supports a justify constructor arg allowing left, centre and right justification. Thank you for the suggestion: it proved easy to implement and is a worthwhile enhancement.


Issue with vscode macos popup while in zoom screenshare

While Zoom screen share is active, have the terminal in vscode request to control google chrome to open a new tab
The pop up cannot be dismissed while the zoom screen share is active, vscode cannot rescind the request, macos cannot grant or deny the request
once zoom screen share is ended the popup can either be dismissed or granted

/duplicate of #157338

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


[6.0][Concurrency] Don't allow erasing global actor isolation when the function value crosses an isolation boundary.

Explanation: The actor isolation checker allows erasing global actor isolation in function conversions when the conversion happens in the same isolation domain and the destination type is not Sendable under the assumption that the function value will never cross an isolation boundary. This is an important rule, because it allows calling synchronous higher order function APIs with global actor isolated function values as long as you're calling from a global actor isolated context. However, the actor isolation checker was allowing the conversion in cases where the function value crosses an isolation boundary:
func crossIsolationBoundary(_ closure: () -> Void) async { closure() }

@MainActor func test() async {
  let closure = { @MainActor @Sendable in
    MainActor.assertIsolated()
  }

  await crossIsolationBoundary(closure)
}

This PR diagnoses the function conversion that loses actor isolation if the function conversion is an argument to a call that crosses an isolation boundary.
We still need to fix this case under region isolation:
func crossIsolationBoundary(_ closure: () -> Void) async { closure() }

@MainActor func test() async {
  let closure = { @MainActor @Sendable in
    MainActor.assertIsolated()
  }

  let erased: () -> Void = closure

  await crossIsolationBoundary(erased)
}

Currently, the above code is "fine" because the function conversion itself isn't crossing an isolation boundary, and from the perspective of region analysis, erased is in a disconnected region. I think the way to solve this is to merge erased to the main actor region due to the function conversion that erases main actor isolation.

Scope: Only impacts isolated-to-non-Sendable function conversions that cross isolation boundaries.

Risk: Low due to narrow scope.

Testing: Add a test case.

Reviewer: @xedin

Main branch PR: https://github.com/apple/swift/pull/72607

@swift-ci please test


django quick fix

VSCode Version:1.47.3
OS Version: windows 10

Steps to Reproduce:
1.quick fix feature  in python django framework is not working
2.

Does this issue occur when all extensions are disabled?: Yes/No

❣


Extension causes high cpu load

Issue Type: Performance
Extension Name: cpu-load
Extension Version: 0.0.11
OS Version: Darwin x64 18.5.0
VSCode version: 1.34.0-insider

:warning: Make sure to attach this file from your home-directory:
:warning:/Users/isidor/jrieken.cpu-load-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@isidorn @jrieken do you have a way to trigger this? I just opened https://github.com/microsoft/vscode/issues/73419 because I'd really like to get a profile of my extensions startup, but I can't find a way (users sometimes trigger this, but I can't). If there's something I can do to force it, it'd allow me to get a trace to more easily measure the impact of my changes.

Never mind, I was able to force it like this:
const time = Date.now();
let i = 0;
while (Date.now() - time < 3000) {
	i++;
}
console.log(i);

My trace doesn't have anywhere near the tree of loading that the users does though.. I'll have to do some more digging into why that is :/


[kiosk] Yet another take on extensions

Description
Another attempt to implement a fail-safe Extensions API with a minimal set of introduced changes.
Test Plan
Tests to be added along with a set of extensions.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes
TBD

@sblackshear I've been thinking about this implementation for some time and I see a potential to make it even more generic, abstracting (generalizing) away the Extension from the Kiosk. Practically speaking, the only "base" feature of the extensions API is to provide "permissions" and access to protected actions.
Perhaps, we could try something of kind:
module sui::kiosk {
    // ...

    struct ExtensionKey<phantom Ext> has store, copy, drop {}

    public fun add_extension<Ext: drop, Extension: store>(
        _ext: Ext,
        kiosk: &mut Kiosk,
        extension: Extension
    );

    public fun extension_mut<Ext: drop, Extension: store>(
        _ext: Ext,
        kiosk: &mut Kiosk,
    ): &mut Extension;

    public fun remove_extenstion<Ext: drop, Extension: store>(
        _ext: Ext,
        kiosk: &mut Kiosk,
    ): Extension;
}

Wonder what you think and also where the permissions could live. I think we could even create a dynamic field with permissions on the side. So one would be for the Extension and one for the ExtensionConfig. Principally it's the choice between having everything pre-defined + giving a Bag for custom data vs not having anything defined but permissions.

Thank you for the review! @amnn @manolisliolios @sblackshear
I've addressed your comments, re-requesting to get a stamp if everyone agrees.


feat(events): add new registerScreenPoppedListener

BREAKING CHANGE:  RNN version was upgraded to 4.0.7
This PR closes #15

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[dwarf] Remove documentation on outdated dwarf extensions

Complimentary to  https://github.com/D-Programming-Language/dmd/pull/4732

http://dtest.thecybershadow.net/artifact/website-0e46c104c07b98c60b77c04788d52fa2df77cf55-53967985a6a4362b26872bb529a62d2c/dlangspec.html
Looks unstyled.  All other HTML looks fine.

I don't see how that has anything to do with my changes. :)

http://dtest.thecybershadow.net/artifact/website-0e46c104c07b98c60b77c04788d52fa2df77cf55-53967985a6a4362b26872bb529a62d2c/dlangspec.html

Was intended for @CyberShadow.  There's not much to this PR, so the only thing that really needs checking is the DDoc and formatting.

All other HTML looks fine.
I took a look at the DDoc and HTML generated as a result of your changes, and I didn't see any problems like missing parens etc...

Sorry if I'm making noise, I just want to try and get some of this stuff moved along.

dlangspec.html is an intermediate file used for building the specfication ebook.


feat: easy floor placing

This PR implements the Easy Floor Placing Shape Up
https://github.com/decentraland/js-sdk-toolchain/assets/2781777/19b8339d-988b-48d0-a926-f5b78fa68c10
New stuf

[x] Add "paint bucket" icon to assets of category "ground"
[x] Implement setGround operation
[x] Add new event SET_GROUND to analytics
[x] Wire setGround on drag-n-drop of asset
[x] Wire setGround on layout change (via Scene settings)
[x] Add new icons for entity tree:

Entity Group: Four Hexagons
Smart Item: Lightning
Tile: Paint Bucket

[x] Support for placing single tiles when holding SHIFT key (and tooltip showing the functionality while dragging).

Old stuff, fixes and tech debt

[x] Fix entities that are locked are still selectable from the renderer when clicking on them
[x] When assets are drag n dropped, the drag preview (the transparent image attached to the mouse while dragging) sometimes gets cut if the asset is below the fold
[x] Cyberpunk ground goes out of bounds, model needs to be fixed
[x] Locking/Unlocking or Hiding/Unhiding a parent entities does not apply the given action to their children.
[x] Added new events LOCK and HIDE to analytics

great work 🚀


Yazi leaves random core dump files

What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
Kitty 0.32.0
Yazi version
0.2.1
Did you try the latest main branch to see if the problem has already been fixed?
Tried, but the problem is still present
Describe the bug
Sometimes I find random core dump files in my folders, generated by yazi.
Expected Behavior
Of course, these files should not appear. Not in every folder, at least.
To Reproduce
They might occur because of unfinished operations in yazi when closing, but I can not say for sure.
Configuration
{ pkgs, ... }:

{
    programs.yazi = {
        enable = true;
        settings = {
            manager = {
            layout         = [ 1 4 3 ];
            sort_by        = "natural";
            sort_sensitive = true;
            sort_reverse   = false;
            sort_dir_first = true;
            linemode       = "none";
            show_hidden    = true;
            show_symlink   = true;
            };

            preview = {
            tab_size        = 2;
            max_width       = 600;
            max_height      = 900;
            cache_dir       = "";
            ueberzug_scale  = 1;
            ueberzug_offset = [ 0 0 0 0 ];
            };

            tasks = {
            micro_workers = 5;
            macro_workers = 10;
            bizarre_retry = 5;
            };

            log = {
            enabled = false;
            };

            opener = {
                edit = [
                    { exec = "nvim \"$@\""; block = true;  for = "unix"; }
                    { exec = "code \"%*\"";    orphan = true; for = "windows"; }
                ];
            };
        };
        keymap = {
            manager.keymap = [
                { exec = "shell 'dragon -x -i -T \"$1\"' --confirm"; on = [ "<C-d>" ]; }
                { exec = "arrow -1"; desc = "Move cursor up"; on = [ "<Up>" ]; }
                { exec = "arrow 1"; desc = "Move cursor down"; on = [ "<Down>" ]; }
                { exec = "paste"; desc = "Paste the files"; on = [ "p" ]; }
                { exec = "escape"; on = [ "<Esc>" ]; }
                { exec = "quit"; on = [ "q" ]; }
                { exec = "close"; on = [ "<C-q>" ]; }
                { exec = "shell \"$SHELL\" --block --confirm"; on = [ "<C-z>" ]; }

                # Navigation
                { exec = "arrow -1"; on = [ "u" ]; }
                { exec = "arrow 1"; on = [ "e" ]; }

                { exec = "arrow -5"; on = [ "U" ]; }
                { exec = "arrow 5"; on = [ "E" ]; }

                { exec = "leave escape --visual --select"; on = [ "<Left>" ]; }
                { exec = "enter escape --visual --select"; on = [ "<Right>" ]; }

                { exec = "back"; on = [ "N" ]; }
                { exec = "forward"; on = [ "I" ]; }

                { exec = "peek -5"; on = [ "<C-u>" ]; }
                { exec = "peek 5"; on = [ "<C-e>" ]; }

                { exec = "arrow -99999999"; on = [ "g" ]; }
                { exec = "arrow 99999999"; on = [ "G" ]; }

                # Selection
                { exec = "select --state=none arrow 1"; on = [ "<Space>" ]; }
                { exec = "visual_mode"; on = [ "v" ]; }
                { exec = "visual_mode --unset"; on = [ "V" ]; }
                { exec = "select_all --state=true"; on = [ "<C-a>" ]; }
                { exec = "select_all --state=none"; on = [ "<C-r>" ]; }

                # Operation
                { exec = "open"; on = [ "<Enter>" ]; }
                { exec = "open --interactive"; on = [ "<C-Enter>" ]; }
                { exec = "yank escape --visual --select"; on = [ "y" ]; }
                { exec = "yank --cut escape --visual --select"; on = [ "x" ]; }
                { exec = "paste"; on = [ "p" ]; }
                { exec = "paste --force"; on = [ "P" ]; }
                { exec = "link"; on = [ "l" ]; }
                { exec = "link --relative"; on = [ "L" ]; }
                { exec = "remove escape --visual --select"; on = [ "d" ]; }
                { exec = "remove --permanently escape --visual --select"; on = [ "D" ]; }
                { exec = "create"; on = [ "a" ]; }
                { exec = "rename"; on = [ "r" ]; }
                { exec = "shell"; on = [ ";" ]; }
                { exec = "shell --block"; on = [ ":" ]; }
                { exec = "hidden toggle"; on = [ "h" ]; }
                { exec = "search fd"; on = [ "s" ]; }
                { exec = "search rg"; on = [ "S" ]; }
                { exec = "search none"; on = [ "<C-s>" ]; }
                { exec = "jump zoxide"; on = [ "z" ]; }
                { exec = "jump fzf"; on = [ "Z" ]; }

                # Linemode
                { exec = "linemode size"; on = [ "m" "s" ]; }
                { exec = " linemode permissions"; on= [ "m" "p" ]; }
                { exec = "linemode mtime"; on = [ "m" ]; }
                { exec = "linemode none"; on = [ "n" ]; }

                # Copy
                { exec = "copy path"; on = [ "c" "c" ]; }
                { exec = "copy dirname"; on = [ "c" "d" ]; }
                { exec = "copy filename"; on = [ "c" "f" ]; }
                { exec = "copy name_without_ext"; on = [ "c" "n" ]; }

                # Find
                { exec = "find --smart"; on = [ "/" ]; }
                { exec = "find --previous --smart"; on = [ "?" ]; }
                { exec = "find_arrow"; on = [ "-" ]; }
                { exec = "find_arrow --previous"; on = [ "=" ]; }

                # Sorting
                { exec = "sort alphabetical --dir_first"; on = [ "," "a" ]; }
                { exec = "sort alphabetical --reverse --dir_first"; on = [ "," "A" ]; }
                { exec = "sort natural --dir_first"; on = [ "," "n" ]; }
                { exec = "sort natural --reverse --dir_first"; on = [ "," "N" ]; }
                { exec = "sort created --reverse --dir_first"; on = [ "," "c" ]; }
                { exec = "sort created --dir_first"; on = [ "," "C" ]; }
                { exec = "sort modified --reverse --dir_first"; on = [ "," "m" ]; }
                { exec = "sort modified --dir_first"; on = [ "," "M" ]; }
                { exec = "sort size --reverse --dir_first"; on = [ "," "s" ]; }
                { exec = "sort size --dir_first"; on = [ "," "S" ]; }

                # Tabs
                { exec = "tab_create --current"; on = [ "t" ]; }
                { exec = "tab_switch -1 --relative"; on = [ "<C-n>" ]; }
                { exec = "tab_switch 1 --relative"; on = [ "<C-i>" ]; }
                { exec = "tab_switch 0"; on = [ "1" ]; }
                { exec = "tab_switch 1"; on = [ "2" ]; }
                { exec = "tab_switch 2"; on = [ "3" ]; }
                { exec = "tab_switch 3"; on = [ "4" ]; }
                { exec = "tab_switch 4"; on = [ "5" ]; }
                { exec = "tab_switch 5"; on = [ "6" ]; }
                { exec = "tab_switch 6"; on = [ "7" ]; }
                { exec = "tab_switch 7"; on = [ "8" ]; }
                { exec = "tab_switch 8"; on = [ "9" ]; }
                { exec = "tab_swap -1"; on = [ "<" ]; }
                { exec = "tab_swap 1"; on = [ ">" ]; }

                # Tasks
                { exec = "tasks_show"; on = [ "w" ]; }

                # Goto
                { exec = "cd ~"; on = [ "g" "h" ]; }
                { exec = "cd ~/.config"; on = [ "g" "c" ]; }
                { exec = "cd ~/Downloads"; on = [ "g" "d" ]; }
                { exec = "cd /tmp"; on = [ "g" "t" ]; }
                { exec = "cd --interactive"; on = [ "g" "<Space>" ]; }

                # Help
                { exec = "help"; on = [ "~" ]; }

                ];

                tasks.keymap = [
                    { exec = "close"; on = [ "<C-q>" "<Esc>" "w" ]; }
                    { exec = "arrow -1"; on = [ "u" ]; }
                    { exec = "arrow 1"; on = [ "e" ]; }
                    { exec = "inspect"; on = [ "<Enter>" ]; }
                    { exec = "cancel"; on = [ "x" ]; }
                    { exec = "help"; on = [ "~" ]; }
                ];
                select.keymap = [
                    { exec = "close"; on = [ "<C-q>" "<Esc>" ]; }
                    { exec = "close --submit"; on = [ "<Enter>" ]; }
                    { exec = "arrow -1"; on = [ "u" ]; }
                    { exec = "arrow 1"; on = [ "e" ]; }
                    { exec = "arrow -5"; on = [ "U" ]; }
                    { exec = "arrow 5"; on = [ "E" ]; }
                    { exec = "help"; on = [ "~" ]; }
                ];
                input.keymap = [
                    { exec = "close"; on = [ "<C-q>" ]; }
                    { exec = "close --submit"; on = [ "<Enter>" ]; }
                    { exec = "escape"; on = [ "<Esc>" ]; }
                    { exec = "backspace"; on = [ "<Backspace>" ]; }
                    { exec = "insert"; on = [ "k" ]; }
                    { exec = "insert --append"; on = [ "a" ]; }
                    { exec = "visual"; on = [ "v" ]; }
                    { exec = "move -1"; on = [ "n" ]; }
                    { exec = "move 1"; on = [ "i" ]; }
                    { exec = "move -999"; on = [ "N" ]; }
                    { exec = "move 999"; on = [ "I" ]; }
                    { exec = "move -999 insert"; on = [ "<C-n>" ]; }
                    { exec = "move 999 insert --append"; on = [ "<C-i>" ]; }
                    { exec = "backward"; on = [ "b" ]; }
                    { exec = "forward"; on = [ "w" ]; }
                    { exec = "forward --end-of-word"; on = [ "h" ]; }
                    { exec = "delete --cut"; on = [ "d" ]; }
                    { exec = "delete --cut move 999"; on = [ "D" ]; }
                    { exec = "delete --cut --insert"; on = [ "c" ]; }
                    { exec = "delete --cut --insert move 999"; on = [ "C" ]; }
                    { exec = "delete move 1 --in-operating"; on = [ "x" ]; }
                    { exec = "yank"; on = [ "y" ]; }
                    { exec = "paste"; on = [ "p" ]; }
                    { exec = "paste --before"; on = [ "P" ]; }
                    { exec = "undo"; on = [ "l" ]; }
                    { exec = "redo"; on = [ "L" ]; }
                    { exec = "help"; on = [ "~" ]; }
                ];
                help.keymap = [
                    { exec = "escape"; on = [ "<Esc>" ]; }
                    { exec = "close"; on = [ "q" "<C-q>" ]; }
                    { exec = "arrow -1"; on = [ "u" ]; }
                    { exec = "arrow 1"; on = [ "e" ]; }
                    { exec = "arrow -5"; on = [ "U" ]; }
                    { exec = "arrow 5"; on = [ "E" ]; }
                    { exec = "filter"; on = [ "/" ]; }
                ];
                completion.keymap = [
                    { exec = "close"; on = [ "<C-q>" ]; }
                    { exec = "close --submit"; on = [ "<Tab>" ]; }
                    { exec = "arrow -1"; on = [ "<C-u>" ]; }
                    { exec = "arrow 1"; on = [ "<C-e>" ]; }
                    { exec = "help"; on = [ "~" ]; }
                ];
        };
        theme = {
            manager = {
            border_symbol = " ";
            };
        };
    };
}

Anything else?
No response

Please upload your core dump file.

Is Yazi behaving normally when generating these files - any crashes? I used lldb to investigate, and it's possible that the generation of these files is caused by a crash, but I'm not sure about the reason for the crash yet...

Yes, it does

It crashes right?

I presume that it may be because of unfinished operations left when forcibly closing yazi

How do you force quit? Through the system task manager, or the kill command, or by pressing q in yazi? If exiting from yazi, calling std::process::exit(0) without waiting for the remaining tasks/threads to finish is the current way, but I'm not sure if it might lead to the creation of those files.

but instead it would show something like "2 left" on the bottom right

Press w to see what was happening

It crashes right?

Sorry, I was not clear enough. No, it does not crash whatsoever. It works perfectly, yet these core dumps still appear.

How do you force quit?

I simply kill the console with killactive through a keybind. I also start yazi directly through a keybind.
bind = $mainMod, E, exec, kitty yazi
bind = $mainMod, W, killactive,

Press w to see what was happening

Execute `nvim core` with `/home/user/Documents/core`
Execute `nvim core` with `/home/user/Documents/core`

Sorry, this is definitely a problem that needs to be addressed, but unfortunately, I'm not sure how to fix it at the moment - I can't reproduce it on my system, and I'm not sure what is causing these files to be generated.
Could you please try using the latest Yazi v0.2.2 and, before executing the killactive command, terminate Yazi with pkill yazi or quit Yazi by pressing q within Yazi, then observe for a while to see if the problem still. Maybe we can further narrow down this problem.

Sure, I will contact the maintainer of the yazi package from nixpkgs to kindly update the package. Until then, I'll change the keybind as per your instructions.
I'll come back with further info when I'll have it.

Okay. Also please comment out the following lines during the build so that more debugging information can be seen in case of another core dump:
https://github.com/sxyazi/yazi/blob/087448fd94df495a6a659c86519b8d74668159b7/Cargo.toml#L5-L9

Please reopen if the problem still

It seems to crash every time when  I kill the terminal window where yazi lives.
https://github.com/sxyazi/yazi/assets/95308907/34bfe1db-d5d8-4e8e-9888-a1355eac4480

I ended up figuring why the problem occured. It was because of an option I had enabled at some point, which put the core dumps in the same directory as the crashes which were happening.

Hi, another user feedback that the issue has been fixed in Yazi v0.2.2, see https://github.com/sxyazi/yazi/issues/618#issuecomment-1924718819


Multithread initial approach

Marie Kondo

Codecov Report

Merging #126 (4f19772) into foxy (8e41732) will decrease coverage by 0.03%.
The diff coverage is 45.45%.

@@            Coverage Diff             @@
##             foxy     #126      +/-   ##
==========================================
- Coverage   50.39%   50.36%   -0.04%
==========================================
  Files          35       35
  Lines        1502     1503       +1
  Branches      307      306       -1
==========================================
  Hits          757      757
- Misses        519      522       +3
+ Partials      226      224       -2

Impacted Files
Coverage Δ

rmw_microxrcedds_c/src/rmw_publish.c
46.34% <ø> (ø)

rmw_microxrcedds_c/src/rmw_request.c
65.38% <ø> (ø)

rmw_microxrcedds_c/src/rmw_response.c
65.21% <ø> (ø)

rmw_microxrcedds_c/src/types.c
58.51% <ø> (ø)

rmw_microxrcedds_c/src/rmw_uros_options.c
39.80% <33.33%> (-0.98%)
:arrow_down:

rmw_microxrcedds_c/src/memory.c
100.00% <100.00%> (ø)

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 c9733a6...4f19772. Read the comment docs.

Merging on Tuesday 4th May


Release 2.0.1

What's Changed

Updated basic example to include payload by @paul-sachs in https://github.com/connectrpc/connect-query-es/pull/492
Ensure createconnectQueryKey validates input types by @paul-sachs in https://github.com/connectrpc/connect-query-es/pull/493
Update dependencies to support react 19 by @paul-sachs in https://github.com/connectrpc/connect-query-es/pull/495

Full Changelog: https://github.com/connectrpc/connect-query-es/compare/v2.0.0...v2.0.1

Included react 19 specifically since it feels like it's nice to show in release notes and we had active questions about it, even if it was just a dependency update. Not a strong opinion, open to removing it.


Webpack compilation error when code splitting

When using webpack code splitting the compiler will flag an error for missing webpackJsonp function:
asyncCommons.part.js:2 (JSC_UNDEFINED_VARIABLE)
variable webpackJsonp is undeclared
webpackJsonp([0],{

is there a way to tell the compiler that a global variable/function will be available on runtime?
Thanks

@kruczy What you need is an externs file for Webpack. I don't remember seeing one off the top of my head though.

What is webpackJsonp? You may be able to add an externs file that looks like this-
/** @externs */

/**
 * @param {!Array<number>} first
 * @param {!Object} second
 */
var webpackJsonp = function() {};

webpackJsonp is a callback that is called from dynamically loaded chunks to declare all the modules so they can be imported
externs seems like the correct way to do this
Thanks alot


Add SAKURA Cloud Service Discovery

ADD SAKURA Cloud Service Discovery!
SAKURA Cloud is also called to as "sacloud" .
SAKURA Cloud provide by SAKURA Internet Inc.
SAKURA Internet is one of a server provider in Japan.

We're not currently accepting new service discovery integrations, instead I'd recommend you integrate with file_sd.

🙆

Yes, it's mentioned in the readme of the discovery directory.


Text Bug with Atelier Rorona

Using Version 0.5 of the sync fix on Atelier Rorona The Alchemist of Arland DX makes the text bug out. This happens on both the Japanese and English language versions.

While the sync fix isn't required for this game, as the performance is good without it. I felt that it was worth noting since this is still another D3D11 based Atelier game on what seems to be the same engine as the rest of the series.

This is likely caused by shadow resources not getting updated on Map/Unmap.  Ayesha DX had similar issues with text.
I have a hacky fix on my branch targeting older Atelier games in 98b5c9bdb934fa2d74ad17c026bb50598d522cc6, but it's the minimal amount of work to get Ayesha working and makes plenty of assumptions about how the game uses Map/Unmap (e.g. that the game only ever has one resource mapped at a time), so probably isn't wanted here.