[usb_fs_nb_pe] Move to usbdev or hw/vendor

It just occurred to me that usb_fs_nb_pe is actually not a real comportable IP, but rather something like a vendored in IP with some patches applied. It would therefore make more sense to move this under hw/vendor with an associated patch repository - or if that is not an option, move the files under usbdev.
WDYT?

i think it would be nice to clean this up, but i'm not really sure it's worth doing at the moment.
there have been fixes made to the block itself, and going back to re-create all the patches at this point seems a bit overkill.
If we have to move it I would suggest under usbdev.

Realistically, we've hard forked this module from its roots. The original module looks very different in a lot of places, and we have no intention of following upstream (different use case). Thus, I don't think vendoring this module is the best path.
Does that make sense? Am I missing a good reason for it?

Ok, that makes sense. In that case I would suggest we collocate it together with the usbdev files, since it is not a comportable IP in itself. Does that make sense?

Ok, that makes sense. In that case I would suggest we collocate it together with the usbdev files, since it is not a comportable IP in itself. OK?

SGTM.

I know it is not used in the current OT, but this code is also used by the usbuart IP. That is why it was put as its own directory.
(Of course usbuart has probably decayed because nobody has been testing it for interface or primitive changes. I was doing that for a while, but probably not in 15 months.)
I agree this is now very different code from its upstream (which was usb_fs_pe, i.e. had the buffers that the nb non-buffered version removed) and has been fixed for coding convention.

it probably makes sense to move this under usbdev and give it its own core file in case we want finer granularity re-use in the future.


Fix Ownership and Tier Processing (#9356)

fix(DI): Owner perc. and tiers

fix(DI): pylint

(cherry picked from commit b3160130f290a4c8e7bfc716524409cfde2ea658)

we will rebase from main


Access rights

How can I set this APIM protection to specific users?

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

ID: 823eb96f-e5f1-0832-b175-0b31009be92f
Version Independent ID: 330085ae-dcf6-e930-86a8-0e4a60ab1314
Content: Protect an API by using OAuth 2.0 with Azure Active Directory and API Management
Content Source: articles/api-management/api-management-howto-protect-backend-with-aad.md
Service: api-management
GitHub Login: @miaojiang
Microsoft Alias: apimpm

I mean AD users

Thx for your answer. I think those users under APIM aren't really AD users, am I right? I found some settings under enterprise application settings ('Users and groups', after 'User assignment required' is enabled and 'Who can consent' is set to 'Admins and users'). Then only specified users are allowed to access application from APIM...

@Majo4443 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Add a test:schemas rake task

This rake task only runs tests that have the word "schema" in them. We can run this task instead of the full test (which takes 8 minutes) when testing as a downstream build from govuk-content-schemas.
Having "schema" in the test file is obviously going to cause false positives, but hopefully no false negatives - which would be worse.
This test run takes 10s to complete.

I'm going to have a quick look at how this affects the effectiveness of the tests, also, the name of the task in the commit message is wrong.

@cbaines updated.


WIP: Map Event Sync

PR Checklist

Please check if your PR fulfills the following requirements:

[ ] All new classes have class-level documentation comments, if there are any at all
[ ] Tests for the changes have been added (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation update
[ ] Other... Please describe:

What is the current behaviour?

MapEvents are not synced
What is the new behaviour?

Resolves #

MapEvent starts and ends are synced. Results of said MapEvent are also synced.
Other information

Crashes when client touches a mountain bandit

Also results need to be synced

Ops, request re-review on wrong PR

Crashes when client touches a mountain bandit

Hmm, I'm not seeing this behavior.

Currently waiting for Party creation/removal to be synced as parts of this is dependent on that.


Docker Setup Instructions

Added

Instructions to setup docker and run the images for the application

This was meant to be a part of #15 but I forgot to include it before merging.
Now, v0.2.0 has some documentation for running the application.


Latest version of gem relies on a very old version of Nokogiri

In the latest ruby gem release for 1.10.1, I think there's a regression for the Nokogiri version. https://rubygems.org/gems/ruby-saml/versions/1.10.1
It now requires Nokogiri ~1.5, whereas version 1.10 of this gem required nokogiri >= 1.8.2
I discovered this trying to install the gem into a Rails project I have:
Bundler could not find compatible versions for gem "nokogiri":
  In Gemfile:
    rails (~> 5.2.0) was resolved to <IP_ADDRESS>, which depends on
      actionmailer (= <IP_ADDRESS>) was resolved to <IP_ADDRESS>, which depends on
        rails-dom-testing (~> 2.0) was resolved to 2.0.3, which depends on
          nokogiri (>= 1.6)

    ruby-saml (~> 1.10, >= 1.10.1) was resolved to 1.10.1, which depends on
      nokogiri (<= 1.5.11)

That the recent commit that forced to use at least version 1.8.2
https://github.com/onelogin/ruby-saml/commit/325a444b4d67c121fb7d7d9c6f13ff20624cf008#diff-7cb020d23c0a838b83644b2dad8ad05c
But if you installed ruby-saml using the nokogiri-1.5.gemfile then you will have the conflict you see.

Have the same problem:
NEW https://rubygems.org/gems/ruby-saml/versions/1.10.1
1.10.1 requires nokogiri <= 1.5.11
PREVIOUS https://rubygems.org/gems/ruby-saml/versions/1.10.0
1.10.0 requires nokogiri >= 1.8.2

Hi,
The gem cli also shows the same issue:
$ gem dependency -r ruby-saml -v '1.10.1' --source https://rubygems.org
Gem ruby-saml-1.10.1
  minitest (~> 5.5, development)
  mocha (~> 0.14, development)
  nokogiri (<= 1.5.11)
  rake (~> 10, development)
  ruby-debug (~> 0.10.4, development)
  shoulda (~> 2.11, development)
  simplecov (>= 0, development)
  systemu (~> 2, development)
  timecop (<= 0.6.0, development)
  uuid (>= 0)

That is very strange.
Forcing nokogiri to be 1.8.2, when possible, was introduced on the 1.10.1 version:
https://github.com/onelogin/ruby-saml/commit/325a444b4d67c121fb7d7d9c6f13ff20624cf008
No idea why that change affected Rubygem.
I guess that Rubygem takes the lower ruby version supported (1.8.7) and then verifies its dependencies where nokogiri < 1.5.11
Not sure why 1.10.0 returns nokogiri 1.8.2 and 1.10.1 returns <= 1.5.11
Maybe something changed on Rubygem?

I dug a bit more and the metadata packed with the gem might be the culprit:
- !ruby/object:Gem::Dependency
  name: nokogiri
  prerelease: false
  requirement: &id002 !ruby/object:Gem::Requirement
    requirements:
    - - <=
      - !ruby/object:Gem::Version
        version: 1.5.11

ok, I fixed it on 1.10.2
gem dependency -r ruby-saml -v '1.10.1' --source https://rubygems.org

Gem ruby-saml-1.10.2
  minitest (~> 5.5, development)
  mocha (~> 0.14, development)
  nokogiri (>= 1.5.10)
  pry-byebug (>= 0, development)
  rake (~> 10, development)
  shoulda (~> 2.11, development)
  simplecov (>= 0, development)
  systemu (~> 2, development)
  timecop (<= 0.6.0, development)

It seems that the dependencies listed on the metadata of the gem depend on the env where you built the gem, and I generated it on an old env 1.8.7 that requires nokogiri <= 1.5.11  and that requirement was added to Rubygem.

ok, I fixed it on 1.10.2
gem dependency -r ruby-saml -v '1.10.1' --source https://rubygems.org

Gem ruby-saml-1.10.2
  minitest (~> 5.5, development)
  mocha (~> 0.14, development)
  nokogiri (>= 1.5.10)
  pry-byebug (>= 0, development)
  rake (~> 10, development)
  shoulda (~> 2.11, development)
  simplecov (>= 0, development)
  systemu (~> 2, development)
  timecop (<= 0.6.0, development)

It seems that the dependencies listed on the metadata of the gem depend on the env where you built the gem, and I generated it on an old env 1.8.7 that requires nokogiri <= 1.5.11 and that requirement was added to Rubygem.

Now I'm thinking about this, wouldn't it defeat the purpose of enforcing a version of nokogiri per ruby version(s) unless one uses a git repo as source, as the metadata is generated for one version of ruby only and no matter what version of ruby you'd use, it would pull the same metadata file?

I think is different the restriction that came from Rubygem, that the restriction defined on the ruby-saml.gemspec itself.
For example if you review Travis, you will see that:

Ruby 1.8.7 env build installed native nokogiri 1.5.11
Ruby 1.9.3 env build installed nokogiri <IP_ADDRESS>
Ruby 2.0 env build installed nokogiri <IP_ADDRESS>
Ruby 2.3 env build installed nokogiri 1.10.3

I totally agree that if you install the gem with
gem 'ruby-saml', :github => 'onelogin/ruby-saml'

No matter what version of ruby you use, you'll end up with the correct version of Nokogiri or at least the one you've defined in your gemspec.
Correct me if I'm wrong but let's take JRuby < <IP_ADDRESS> for this example:
gem 'ruby-saml', '~> 1.10.2'

This https://github.com/onelogin/ruby-saml/blob/master/ruby-saml.gemspec#L34 dependency will never be met because when you generate the gem for one version, you can only do it with a specific version of ruby and the dependencies in the metadata reflects this.
Additionally, I'm not entirely sure but I suspect that for ruby < 2.1, https://github.com/onelogin/ruby-saml/blob/master/ruby-saml.gemspec#L42 won't be met either and will pull the latest version of Nokogiri to date (1.10.3) and would be above the highest version you specified (<= <IP_ADDRESS>), as the metadata is specifying nokogiri (>= 1.5.10).
What do you think?

Yes, you are right, if in a Ruby 2.0 environment I try to install the ruby-saml gem with a:
gem install ruby-saml

I will get a
Fetching: nokogiri-1.10.3.gem (100%)
ERROR:  Error installing ruby-saml:
	nokogiri requires Ruby version >= 2.3.0.

But If I install the required nokogiri version that appears on the gemspec for that version:
gem install nokogiri -v <IP_ADDRESS>

later I'm able to install ruby-saml
gem install ruby-saml
Fetching: ruby-saml-1.10.2.gem (100%)
Successfully installed ruby-saml-1.10.2

Do you know a way to improve the current way to handle this?

I don't have much experience in that area so take it with a grain of salt but from what I've seen from other projects, I can suggest the following option:
If you want to keep supporting all these ruby versions, having a major version per requirement would be the way to go (a bit like rails with their stable branches). That way, you can still backport patches until you decide you want to remove the support for older ruby versions.
It's more complicated to maintain but you might have your reasons as to why you want to support these old ruby versions.
It would be easier to support only versions of ruby down to those which are still in a security maintenance status at least (2.4 as of today). This solution has some downsides though, some people might not be able to update to a more recent version of ruby and are relying on this paying service to get security patches (I can't remember the name). If they want to use your gem, they might be left out in that case.
Ultimately, it's up to you as you are spending your time to maintain this gem for the community. I don't know how much time you are willing to spend on this so having to spend even more time because of a more complicated versioning model, might not be an option for you.

`» bundle audit
Name: nokogiri
Version: 1.10.2
Advisory: CVE-2019-11068
Criticality: Unknown
URL: https://github.com/sparklemotion/nokogiri/issues/1892
Title: Nokogiri gem, via libxslt, is affected by improper access control vulnerability
Solution: upgrade to >= 1.10.3
`


[SPARK-36137][SQL] HiveShim should fallback to getAllPartitionsOf even if directSQL is enabled in remote HMS

What changes were proposed in this pull request?

Change HiveShim.getPartitionsByFilter to always fallback to use getAllPartitionsMethod even if hive.metastore.try.direct.sql is set to true in the remote HMS.
Why are the changes needed?

At the moment getPartitionsByFilter in HiveShim only fallback to use getAllPartitionsMethod when hive.metastore.try.direct.sql is disabled in the remote HMS, and will fail the query otherwise. However, in certain cases the remote HMS will fallback to use ORM (which only support string type for partition columns) to query the underlying RDBMS even if this config is set to true. In this scenario, currently Spark will not be able to recover from the exception and will just fail the query.
For instance, we encountered this bug HIVE-21497 in HMS running Hive 3.1.2, and Spark was not able to pushdown filter for date column.
Does this PR introduce any user-facing change?

Yes, now if Spark is querying partitions from a remote HMS which throws exception even if hive.metastore.try.direct.sql is set to true, Spark will fallback to list all partitions and do the pruning on client side, instead of failing the query.
How was this patch tested?

Tested locally with a HMS instance running 3.1.2. It's pretty hard to add a unit test for this since we don't have a mock HMS.

cc @wangyum @cloud-fan @dongjoon-hyun @viirya

Test build #141114 has started for PR 33382 at commit b56d888.

At the moment getPartitionsByFilter in HiveShim only fallback to use getAllPartitionsMethod when hive.metastore.try.direct.sql is enabled

Do you mean "when hive.metastore.try.direct.sql is disabled"?

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45627/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45627/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45627/

At the moment getPartitionsByFilter in HiveShim only fallback to use getAllPartitionsMethod when hive.metastore.try.direct.sql is enabled

Do you mean "when hive.metastore.try.direct.sql is disabled"?

Oops my mistake. Updated.

Could you share us your opinion about the performance regressions for the non-failed queries, @sunchao ?

I'm not sure we should call it a regression since it switch the behavior from failing the query (with no workaround at the moment) to letting it succeed. If there are huge number of partitions, the cost for fetching partition metadata from HMS could increase as we are returning all the partitions instead of the filtered ones. However normally this also means there are more data to be processed so the increased planning time could be amortized in the total job execution time.

If possible, I'd like to make this as a disabled configuration instead of enforcing it. For normal users which has successful queries don't need to bother with this. And, for the failed queries, can we give a directional guide at the error message to enable this? Is it difficult?

Test build #141114 has finished for PR 33382 at commit b56d888.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141114/

Test build #141174 has started for PR 33382 at commit 69514ff.

If possible, I'd like to make this as a disabled configuration instead of enforcing it. For normal users which has successful queries don't need to bother with this. And, for the failed queries, can we give a directional guide at the error message to enable this? Is it difficult?

Hmm you mean introduce another configuration in Spark, and only if that turned on, we'd fallback to getAllPartitionsMethod when hive.metastore.try.direct.sql is true?
        val tryDirectSql = hive.getMSC.getConfigValue(tryDirectSqlConfVar.varname,
          tryDirectSqlConfVar.defaultBoolVal.toString).toBoolean
        try {
          getPartitionsByFilterMethod.invoke(hive, table, filter)
            .asInstanceOf[JArrayList[Partition]]
        } catch {
          case ex: InvocationTargetException if ex.getCause.isInstanceOf[MetaException] &&
              !tryDirectSql && !enableFallback =>
            getAllPartitionsMethod.invoke(hive, table).asInstanceOf[JSet[Partition]]
          case ex: InvocationTargetException if ex.getCause.isInstanceOf[MetaException] &&
              tryDirectSql || enableFallback =>
            throw QueryExecutionErrors.getPartitionMetadataByFilterError(ex)
        }

Test build #141174 has finished for PR 33382 at commit 69514ff.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141174/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45686/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45686/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45686/

Yeah, I think we can have a configuration in Spark, that's disabled by default.

Test build #141789 has started for PR 33382 at commit 869f66f.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46302/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46302/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46302/

Test build #141789 has finished for PR 33382 at commit 869f66f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141789/

Thanks @cloud-fan . Addressed the comments and also added one more test. Also brought back getPartitionMetadataByFilterError so users will get a more informative error message.

Test build #141960 has started for PR 33382 at commit 32fc005.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46471/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/46471/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/46471/

Test build #141960 has finished for PR 33382 at commit 32fc005.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/141960/

Thanks! Merging to master.

Thanks all for the review!


Visdom plot do not update after 1800 iterations

When I show the losses on visdom, my plot do not update after 1800 iterations. Can anyone help me with this? Thank you.

My codes are here:
def update_vis_plot(iteration, loss1, loss2, loss3, window1, window2, update_type,
                    epoch_size=1):
    viz.line(
        X=torch.ones((1, 4)).cpu() * iteration,
        Y=torch.Tensor([loss1, loss2, loss3, loss1 + loss2 + loss3]).unsqueeze(0).cpu() / epoch_size,
        win=window1,
        update=update_type
    )

The update type is append.
update_vis_plot(iteration, loss1.item(), loss2.item(), loss3.item(),
                                    iter_plot, epoch_plot, 'append')

Hi @gszh - are you sure nothing is being plotted, or is it just that the zoom has stopped updating? You can try using the plotly interface controls on the frontend or set axis bounds with the python client as shown in the demo.

Sorry for not replying sooner. My zoom just stopped updating. I will try to set axis bounds and see how it goes.

Did you manually zoom into the plot at any point? #522 was introduced so that zoom would be retained even when new data was appended because it was frustrating behavior to lose manual zoom settings when zoomed in on a live graph.


Remove text justification in table cells

@andralex requested this.

Before:

After:

Your screenshot is fine. There are places affected by this change where justification didn't hurt, but it doesn't look bad without justification either. I think this is fine.
(Full disclosure: this is also a step away from automatic hyphenation, which I subjectively dislike and think shouldn't be used on web pages favoring readability and utility over presentation, so I'm personally in favor of this change.)


Could not find module 'SnapKit' for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator

New Issue Checklist
🚫 If this template is not filled out your issue will be closed with no comment. 🚫

[x] I have looked at the Documentation
[x] I have read the F.A.Q.
[x] I have filled out this issue template.

Issue Info

Info
Value

Platform
iOS

Platform Version
Mac OS  Monterey M1 12.3.1

SnapKit Version
5.0.1

Integration Method
cocoapods

Issue Description
⚠ Replace this with the description of your issue. ⚠

@robertjpayne  Hi, please give me a hand to fix it

Fix it, the solution as below:
In your Podfile  , please add these and then executed the command :
pod install
post_install do |installer_representation|     installer_representation.pods_project.targets.each do |target|         target.build_configurations.each do |config|             config.build_settings['ONLY_ACTIVE_ARCH'] = 'NO'             config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'         end     end end
For me it works!


Feature/its all about fonts

[x] Icons for overlay windows and settings widget
[x] Vertical align the icon font
[x] Emoji font 🤣 because why not (Windows 10 and above)
[x] Monospace font for the console
[x] Expose monospace font to mods ImGui.GetMonoFont(), ImGui.PushFont() #768
[x] Option for custom monospace font
[x] Reload font during runtime
[x] GUI for changing font settings #488
[x] Enumerate system font
[x] Remove the glyph range option. ~Instead, load every glyph in the supplied font.~
[x] Merge the default NotoSans fonts for better multilingual support.
[x] Logs
~Font preview~ (maybe later)
[x] Dynamic glyph range, instead of loading all glyphs

Dynamic glyph ranges todo list:

[x] console logs
[x] console inputtext
[x] lua binding inputtext wrapper
[x] expose AddTextGlyphs() to lua
[x] pre-cache ".lua", ".txt", ".json", ".yml", ".yaml", ".toml", ".ini" files in mod folders
[x] pre-cache all path strings in the mod folders
[x] dynamically load icon glyphs from mods
[x] add files opened by mods (io.open, io.lines) to glyph ranges builder

Use monospace font from lua:
ImGui.PushFont(ImGui.GetMonoFont())
ImGui.Text("This is how the monospaced font looks like")
ImGui.PopFont()

Display multilingual string:

New settings panel:

Do you consider this complete?

Do you consider this complete?

yes


Metrics validation

Remember to check period and length from discovery job level, when metrics are validated. (https://github.com/ivx/yet-another-cloudwatch-exporter/issues/219)
Adds discovery jobs type or static jobs name into config validation messages (makes troubleshooting faster)
Adds metric name into config validation messages (makes troubleshooting faster)

Awesome thanks for your contribution!


fix(material/datepicker): improve color contrast in calendar header

Fixes that the color contrast of the calendar header's text was too low.
Fixes #23511.

Caretaker note: this will generate some screenshot diffs in the calendar.


Finetuning says: "not enough parallel segments in the tmx"

Hi,
when I want to fine-tune the model with a TMX from a (Wordfast) project it says: "not enough parallel segments in the TMX".
It has more than 600 bilingual segments (so about 1300 segments in total if you count source and target language segments separately) from a finished project. Is this really not enough? How many do you need?

It needs at least 1000 TUs

Hi, the finetuning needs a bit of data to work on, so there's a minimum requirement of 1000 translation units (pairs of source and target language segments). This is an arbitrary number, and you probably need more than 1000 to have a noticeable effect.  If you still want to try it with 600 translation units, you can change the FinetuningSetMinSize setting in the OpusCatMTEngine.exe.config file.

Hi, thanks for the answers @all. I actually tried instead the function to upload a source and a corresponding target file derived from the same TM and it worked, it improved the translations even with this small size. But I might also try this other setting, thank you.

Hello HMueller007 and all
What I sometimes do to get around this is to import a simple two column TB (glossary) into memoQ for the same job as the translation job I'm doing and then export all that to the TB for the same job. The segments are small of course but they are very relevant to the job and as Opus does not have any TB function at present to instruct the MT engine, this feels like an intuitive way to proceed. This often gets the TB to exceed the minimum number of segments restriction setting

@SafeTex That's a good tip, will try this, thanks.


Ensure select input view displays default

Always select the first item if no blank item is present.

Coverage remained the same at 99.031% when pulling 14aaafe04926d82282687ddb3aa483815ae8d55d on tf:select-input-default into a6402da686f6907277caa8c48e2626ac27287d96 on codevise:master.

Coverage remained the same at 99.031% when pulling 14aaafe04926d82282687ddb3aa483815ae8d55d on tf:select-input-default into a6402da686f6907277caa8c48e2626ac27287d96 on codevise:master.


add speculatice decoding to opea

Description
Add one micro-service speculative decoding draft code.
Issues
speculative decoding support on cpu and gpu.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ * ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)
[ ] Others (enhancement, documentation, validation, etc.)

Dependencies
Used forked vLLM from https://github.com/jiqing-feng/vllm.git
Tests
Have tested on the test/test_spec_decode_text-generation_vllm.sh

Hi @ClarkChin08 , thanks for contributing.
The code structure of this PR should align with llm/text-generation/vllm/langchain.
Note:

Create a langchain folder inside spec_decode/text-generation/vllm.
Reorg all files in spec_decode/text-generation/vllm/langchain folder.
Create a dependency folder in the deepest folder, move vllm dependency Dockerfile, xx.sh into it.
Rename all Dockerfiles refer to the link above.
Add a spec_decode folder in tests and move the test script into it.

Thank you : )


Add option to use Analyzer in Strong mode

and perhaps even default to Strong? I think people experimenting with Dart will have a better experience if they get more warnings about their code.
Possibly depends on #694 being completed?

I think independent from #694 (though that would be nice too). I think @lukechurch has done some investigating for adding strong mode support to the backend (dart-services). Most of the work would happen there. The front-end may or may not get a toggle or a mode, depending on how we expose it.

Yeah, I'm looking into this as we speak (Tracking issue: https://github.com/dart-lang/dart-services/issues/265). The stress tests are finding a few issues as soon as I've chased those down it should be a fairly easy land.

https://github.com/dart-lang/dart-pad/pull/731

Wow that is so cool! This is a huge feature, and an awesome way to help people learn Strong Mode. Thanks!


apply_polygons: rename polygons parameter to geometries

apply_polygons has a polygons argument:
https://github.com/Open-EO/openeo-processes/blob/965bbaebd4d5984203a0437076c85a66a72a23e0/proposals/apply_polygon.json#L19-L20
This is not in line with comparable processes that use geometries for the same concept, like aggregate_spatial, filter_spatial, filter_vector, vector_buffer. Note that mask_polygon also doesn't use polygons.
It also appears to be confusing users about how MultiPolygons are supported

Fine for me, would be breaking though. So is it also fine for VITO to have a breaking change here?

Would you mind creating a PR for this in openeo-processes? @soxofaan


Calculation goes wrong when setting other offset

https://github.com/stamat/jquery.youtube-background/blob/f9ad26d3aacc40b73d744f6d1fbcc9c8122a7ad0/src/youtube-background.js#L194
When i set the div attributes to for example:
data-ytbg-fit-box="false" data-ytbg-offset="20"
the width would be set to 192020px instead of 1940px.

Thanks for emailing me dude! lol I guess it just concatenates a string instead of adding the two numbers 🤣  I'll look into it! Glad you like the plugin!

Ah self.iframe.parentNode.offsetHeight + self.params.offset; since param is set via attribute it's a string not a number, so I just need to update this with parseInt(self.params.offset, 10)
Thanks for catching this! ❤

thanks, we'll update when fixed :)


github api

REST: https://developer.github.com/v3/
or
GraphQL: https://developer.github.com/v4/

decide to use v3 REST with retrofit for now.
will migrate to v4 GraphQL with Apollo later, maybe.


Upgrade qiskit to 0.31.0

Fixes #203.
This PR addresses the upgrade of the Qiskit dependency to version 0.31.0 in the pytket-qiksit extension.
All test pass locally.

Can you add an entry in the changelog please?


[LUIGI-765] S3FlagTarget now uses == to check slash

Fixes #765.

Good catch. I wish we had more tests for S3. LGTM


Do we need the JIRA instance anymore?

Please share any additional details on this topic
@tykeal was doing some maintainence on the ASWF JIRA instance, and noticed there hasn't been activity for some time.
Detail what actions or feedback you would like from the TAC
Determine if this resource is needed anymore.
How much time do you need for this topic?
5 minutes or less

I'll add to that. From what I can tell, the Jira has never actually been used! Confluence is used semi-regularly, but not Jira.

Gut feeling is that projects prefer using GitHub Issues which are more readily discoverable and better integrated with GitHub centric dev process, and may not require full power / complexity of JIRA project management tools?
If it isn't used, I personally say we should take it down.

We have no interest in using Jira with OpenEXR. Our team is not big enough and development is not active enough to need anything more than GitHub Issues
We use Confluence for TSC meeting notes (avoids polluting the source repo), and a few other things with very low traffic like project ideas.

@yarille Can you do a vote on this with the TAC via email?

Did this vote ever finish?

@tykeal we still need a couple votes for a quorum. I will send a reminder.

Approved by TAC vote on 5/22.

@yarille approved for removal?


[SPARK-15112][SQL] Disables EmbedSerializerInFilter for plan fragments that change schema

What changes were proposed in this pull request?
EmbedSerializerInFilter implicitly assumes that the plan fragment being optimized doesn't change plan schema, which is reasonable because Dataset.filter should never change the schema.
However, due to another issue involving DeserializeToObject and SerializeFromObject, typed filter does change plan schema (see SPARK-15632). This breaks EmbedSerializerInFilter and causes corrupted data.
This PR disables EmbedSerializerInFilter when there's a schema change to avoid data corruption. The schema change issue should be addressed in follow-up PRs.
How was this patch tested?
New test case added in DatasetSuite.

@cloud-fan

Test build #59520 has started for PR 13362 at commit 5b8362a.

LGTM

Test build #59520 has finished for PR 13362 at commit 5b8362a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59520/
Test FAILed.

Test build #59556 has started for PR 13362 at commit edce7a6.

Test build #59556 has finished for PR 13362 at commit edce7a6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59556/
Test PASSed.

Test build #59563 has started for PR 13362 at commit 4099d69.

Test build #59563 has finished for PR 13362 at commit 4099d69.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59563/
Test PASSed.

Merged build finished. Test PASSed.

Merging to master and branch-2.0. Thanks for the review!


Feature top three

If patient doesn't have TopThreeThings - we have button create and form for creating.
In opposite case button "Create" is empty

@kbeloborodko this PR needs your input and review please

@tony-shannon I am communicating with @BogdanScherban to resolve conflicts between the current feature branch and the develop branch, we can merge the code afterwards.


Add test for cross-contract reentrancy

Type of change

Improvement (refactoring, restructuring repository, cleaning tech debt, ...)

Changes
The following changes have been made:

added a new test case
added supporting new contract & abi
added new functions on existing contracts & abis

Notes
The test case added performs the following steps:

The Attack contract's launch_thwarted_attack_3() function is triggered by a contract call from the SDK.
The Attack contract calls into the Target contract's cross_contract_reentrancy_denied() function.
The Target contract calls back to the Attack contract's evil_callback_4() function.
The Attack contract calls into the Attack Helper contract's attempt_cross_contract_reentrancy() function.
(attack vector) The Attack Helper contract attempts to re-enter by calling into the Target contract's cross_contract_reentrancy_denied() function(which hasn't finished execution of the initial call from the Attack contract).
The attack is thwarted by the reentrancy_guard() function in place.

Seems fine but is there something preventing a 2 contract interaction over 3 contracts?

@Braqzen I'm not quite sure what you're getting at here.
If the reentrancy_guard() function is not used, given 2 Contracts A & B:

A can call into B can call into A can call into B can call into A can call into B ... until the gas runs out.
The compiler just warns us if the CEI (Checks, Effects, Interactions) pattern is violated. It doesn't strictly prevent reentrant function calls.

Seems fine but is there something preventing a 2 contract interaction over 3 contracts?

@Braqzen I'm not quite sure what you're getting at here. If the reentrancy_guard() function is not used, given 2 Contracts A & B:

A can call into B can call into A can call into B can call into A can call into B ... until the gas runs out.
The compiler just warns us if the CEI (Checks, Effects, Interactions) pattern is violated. It doesn't strictly prevent reentrant function calls.

By "non-reentrant func" I meant to use the guard in that function, I should have been clearer, my mistake.


[ci:component:github.com/gardener/etcd-druid:v0.3.0->v0.4.0]

*Release Notes:
Added CLI-flags (`max-call-send-message-size`, `max-request-bytes` and `max-txn-ops`) to enable restoration for delta snapshots with large amount of data (large number of events or events with large data).

Validator now double checks latest revision by starting an embedded etcd if DB-based revision check fails. This can potentially avoid unnecessary data restoration when etcd terminates abnormally.

Fix missing alternate full snapshots for some unhibernating shoots.

Revendor etcd library to v3.4.13 and change import paths to `go.etcd.io/etcd` for etcd and `go.etcd.io/bbolt` for bbolt.

Added support for OpenShift Container Storage (OCS) S3 storage type.

Fixed the issue with consecutive restoration if backup-restore sidecar doesn't restart in between.

Added support for OpenShift Container Storage (OCS) S3 storage type.

Add support for **Dell EMC ECS** object store with `S3` protocol

Add TestMachinery integration.

Integration tests can be executed on any given Kubernetes cluster using the `make integration-test-cluster` target against the cluster pointed to by the environment variable `INTEGRATION_TEST_KUBECONFIG`.

Clarify manual backup restore process

Fix snapshot metric initialization.

/invite @amshuman-kr @shreyas-s-rao
/assign @amshuman-kr @shreyas-s-rao
/hold until v1.13 is released

@rfranzke Can you add the following release note to the PR? I don't have edit rights on the PR.
Upgraded etcd version from `v3.3.17` to `v3.4.13` and moved from `quay.io/coreos/etcd` to Gardener-specific custom etcd image `eu.gcr.io/gardener-project/gardener/etcd`. :warning: This will cause an etcd restart.


Ignore specific expressions in LabeledExpression

Expected Behavior
Allow specifying e.g. an array ignoreExpressions for LabeledExpression.
Current Behavior
It's possible to ignore labels, but not specific expressions themselves.
Context
We'd like to be able to partially allow LabeledExpression for only this@, but not in other cases.

Can you provide an example?

You mean for when I'd want to use this@? Sure (adapted from real life, but close match):
fun State.assignShippingNumbers(itemId: ItemId): State {
    val shippingDate = orders.getValue(orderId).getShippingDate()
    return updateItems(itemId) {
        assignShippingNumber(this@assignShippingNumbers, shippingDate)
    }
}

At the same time, we don't want to use labels to jump out of loops.

This issue is stale because it has been open 90 days with no activity. Please comment or this will be closed in 7 days.

Can this bot be configured to only mark an issue as stale if the last comment was by a contributor? I'm not quite sure how I could add to it in a useful way.

I would say that this boy also help us to drag attention over this issues that weren't answered. But we could open an issue or conversation to talk about the bot.
About the issue: I'm not sure if it is worth the effort to implement and maintain this. The idea of this rule is that the labeled expressions are more difficult to follow. And I think that your example is not an exception. If there is not other way, that's a good reason for a suppress. But I see different options:

Don't use the same name for the extension and the method.
Make the extension function a top level extension function. This way you don't even have the option to use @this.

So, to me this rule is doing what is meant to do so I wouldn't add it. Anyway you can always copy the rule and modify it to your needs as a third party rule.

This issue is stale because it has been open 90 days with no activity. Please comment or this will be closed in 7 days.

Closing this for the reasons described above.


IndexError: too many indices for array

Im currently running SVO on a subset of the Euroc datasets by ignoring the first 10 timesteps to avoid initialization errors i.e. rosbag play <file.bag> -s 10.
I record the estimated trajectory and extract to a text file.
For the ground truth I use the supplied ground truth in ASL format and parse it using the supplied matlab code.
As a result, there is a mismatch in the number of steps in estimate vs ground truth.
I assume that for the trajectory evaluation to work, there must be equal number of steps in both?
Can anyone confirm whether this is the case?

I met the same question,
****Traceback (most recent call last):
File "./analyze_trajectory_single.py", line 53, in
traj = Trajectory(args.result_dir)
File "/home/ rpg_trajectory_evaluation/scripts/../src/rpg_trajectory_evaluation/trajectory.py", line 68, in init
self.load_data()
File "/home/rpg_trajectory_evaluation/scripts/../src/rpg_trajectory_evaluation/trajectory.py", line 87, in load_data
self.accum_distances = traj_utils.get_distance_from_start(self.p_gt)
File "/home/rpg_trajectory_evaluation/scripts/../src/rpg_trajectory_evaluation/trajectory_utils.py", line 18, in get_distance_from_start
distances = np.diff(gt_translation[:, 0:3], axis=0)
IndexError: too many indices for array

I found that the timestamp of groundtruth and the timestamp of trajectory estimated are totally different.

I met the same issue. But I dont think the estimated and the groudtruth must have equal number of time steps cuz the example they have in the "laptop" folder has different number of timesteps.

nevermind, I printed out the length of the groundtruth and estimated datasets they provided and they are of the same length.

Hello, I solved the issue by reformatting my stamped_traj estiamte.txt file. First, the groundtruth and estimated file do not have to have the same length (the examples provided in the "laptop" folder have different length for the groundtruth and estimated files.). I believe the code provided does some pre-processing of the data such that even if they aren't the same length, the tool still works.
I tried to make sure that the file format are excatly the same as provided in the example. Specifically, I changed my file to space separated and convert my float to have scientific representation of the same scale.
To debug, you can print out the shape of the array (using .shape) in File "/home/rpg_trajectory_evaluation/scripts/../src/rpg_trajectory_evaluation/trajectory.py", line 87, in load_data
good luck

Hello, I solved the issue by reformatting my stamped_traj estiamte.txt file. First, the groundtruth and estimated file do not have to have the same length (the examples provided in the "laptop" folder have different length for the groundtruth and estimated files.). I believe the code provided does some pre-processing of the data such that even if they aren't the same length, the tool still works.
I tried to make sure that the file format are excatly the same as provided in the example. Specifically, I changed my file to space separated and convert my float to have scientific representation of the same scale.
To debug, you can print out the shape of the array (using .shape) in File "/home/rpg_trajectory_evaluation/scripts/../src/rpg_trajectory_evaluation/trajectory.py", line 87, in load_data
good luck

Thanks for your answer, it's very helpful. It's the problem of timestamps .I think it's necessary to study the paper of this tool to understand how this tool works.

also, make sure the first line of the estimated file is "# time x y z qx qy qz qw".

Hello, I solved the issue by reformatting my stamped_traj estiamte.txt file. First, the groundtruth and estimated file do not have to have the same length (the examples provided in the "laptop" folder have different length for the groundtruth and estimated files.). I believe the code provided does some pre-processing of the data such that even if they aren't the same length, the tool still works.
I tried to make sure that the file format are excatly the same as provided in the example. Specifically, I changed my file to space separated and convert my float to have scientific representation of the same scale.
To debug, you can print out the shape of the array (using .shape) in File "/home/rpg_trajectory_evaluation/scripts/../src/rpg_trajectory_evaluation/trajectory.py", line 87, in load_data
good luck

Thanks for your answer, it's very helpful. It's the problem of timestamps .I think it's necessary to study the paper of this tool to understand how this tool works.

You're welcome. I got this tool to work with the ASL format EuroC dataset. Could you specify more on the timestamps issue? I had an issue that my timesteps are not of the same scale with the groundtruth data. I just convert them to the same scientific notation format and it seems to work fine for me.


PEP 517 error during installing line-profiler

I was trying to install line-profiler using pip I got this errors, I did update setup tools wheel and installed visual studio setup tools trying to install the package using it but also not working with the same error
`ERROR: Command errored out with exit status 1:
command: 'C:\Users\amr.bibars\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.7_qbz5n2kfra8p0\python.exe' 'C:\Users\amr.bibars\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.7_qbz5n2kfra8p0\LocalCache\local-packages\Python37\site-packages\pip_vendor\pep517_in_process.py' build_wheel 'C:\Users\AMR~1.BIB\AppData\Local\Temp\tmpjvuu6hvb'
cwd: C:\Users\AMR~1.BIB\AppData\Local\Temp\pip-install-7l24xs0j\line-profiler
Complete output (162 lines):
Not searching for unused variables given on the command line.
-- The C compiler identification is unknown
CMake Error at CMakeLists.txt:3 (ENABLE_LANGUAGE):
No CMAKE_C_COMPILER could be found.
Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "C:/Users/amr.bibars/AppData/Local/Temp/pip-install-7l24xs0j/line-profiler/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/amr.bibars/AppData/Local/Temp/pip-install-7l24xs0j/line-profiler/_cmake_test_compile/build/CMakeFiles/CMakeError.log".
Not searching for unused variables given on the command line.
CMake Error at CMakeLists.txt:2 (PROJECT):
Generator
  Visual Studio 15 2017 Win64

could not find any instance of Visual Studio.

-- Configuring incomplete, errors occurred!
See also "C:/Users/amr.bibars/AppData/Local/Temp/pip-install-7l24xs0j/line-profiler/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
Not searching for unused variables given on the command line.
-- The C compiler identification is unknown
CMake Error at CMakeLists.txt:3 (ENABLE_LANGUAGE):
The CMAKE_C_COMPILER:
  cl

is not a full path and was not found in the PATH.

To use the NMake generator with Visual C++, cmake must be run from a shell
that can use the compiler cl from the command line.  This environment is
unable to invoke the cl compiler.  To fix this problem, run cmake from the
Visual Studio Command Prompt (vcvarsall.bat).

Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "C:/Users/amr.bibars/AppData/Local/Temp/pip-install-7l24xs0j/line-profiler/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/amr.bibars/AppData/Local/Temp/pip-install-7l24xs0j/line-profiler/_cmake_test_compile/build/CMakeFiles/CMakeError.log".
Not searching for unused variables given on the command line.
-- The C compiler identification is unknown
CMake Error at CMakeLists.txt:3 (ENABLE_LANGUAGE):
The CMAKE_C_COMPILER:
  cl

is not a full path and was not found in the PATH.

To use the JOM generator with Visual C++, cmake must be run from a shell
that can use the compiler cl from the command line.  This environment is
unable to invoke the cl compiler.  To fix this problem, run cmake from the
Visual Studio Command Prompt (vcvarsall.bat).

Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "C:/Users/amr.bibars/AppData/Local/Temp/pip-install-7l24xs0j/line-profiler/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/amr.bibars/AppData/Local/Temp/pip-install-7l24xs0j/line-profiler/_cmake_test_compile/build/CMakeFiles/CMakeError.log".

-- Trying "Ninja (Visual Studio 15 2017 Win64 v141)" generator

--

-- Trying "Ninja (Visual Studio 15 2017 Win64 v141)" generator - failure

-- Trying "Visual Studio 15 2017 Win64 v141" generator

--

-- Trying "Visual Studio 15 2017 Win64 v141" generator - failure

-- Trying "NMake Makefiles (Visual Studio 15 2017 Win64 v141)" generator

--

-- Trying "NMake Makefiles (Visual Studio 15 2017 Win64 v141)" generator - failure

-- Trying "NMake Makefiles JOM (Visual Studio 15 2017 Win64 v141)" generator

--

-- Trying "NMake Makefiles JOM (Visual Studio 15 2017 Win64 v141)" generator - failure

scikit-build could not get a working generator for your system. Aborting build.
Building windows wheels for Python 3.7 requires Microsoft Visual Studio 2017.
Get it with "Visual Studio 2017":
https://visualstudio.microsoft.com/vs/

ERROR: Failed building wheel for line-profiler
Failed to build line-profiler
ERROR: Could not build wheels for line-profiler which use PEP 517 and cannot be installed directly`

Thanks for the report! Unfortunately, this is not the correct place for it. This tracker is only for issues with the software that runs https://pypi.org itself. It cannot help with software installed from there (for example, using pip install <SOME PACKAGE>). You'll need to contact the maintainers of that software instead. This contact information can often be found on the PyPI project page (https://pypi.org/project/<SOME PACKAGE>).
That said, it looks like you need to have Visual Studio installed in order to build this software. The error message even provides a link.

Thanks Jamadden,  I already have visual studio installed on my machine and i tired to install it using visual studio environment tool but i got the same error, I will post the link you mentioned.


added e3dc-rscp

New adapter, see Tester Forum

RE-CHECK!

Automated adapter checker
ioBroker.e3dc-rscp

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "e3dc-rscp" in latest repository

ioBroker.froeling

:thumbsup: No errors found
ioBroker.lg-thinq

:thumbsup: No errors found
ioBroker.openhab

[ ] :heavy_exclamation_mark: [E104] No common.titleLang found in io-package.json
[ ] :heavy_exclamation_mark: [E150] No common.connectionType found in io-package.json
[ ] :heavy_exclamation_mark: [E152] No common.dataSource found in io-package.json
[ ] :heavy_exclamation_mark: [E140] width and height of logo are not equal
[ ] :heavy_exclamation_mark: [E301] Tests on Travis-ci.com are broken. Please fix.
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2017-2022 bluefox<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2017-2022 bluefox<EMAIL_ADDRESS>at the start of LICENSE
[ ] :eyes: [W113] Adapter should support compact mode
[ ] :eyes: [W505] setTimeout found in "main.js", but no clearTimeout detected

ioBroker.rainbird

[ ] :heavy_exclamation_mark: [E150] No common.connectionType found in io-package.json
[ ] :heavy_exclamation_mark: [E152] No common.dataSource found in io-package.json
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2022 Marius Burkard<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2022 Marius Burkard<EMAIL_ADDRESS>at the start of LICENSE

Add comment "RE-CHECK!" to start check anew

Hi, I am trying to bring in e3dc-rscp.
I see the message 👀 [W400] Cannot find "e3dc-rscp" in latest repository
Am I right that this is not an error because e3dc-rscp is new and therefore not in latest repo so far?

Hi, I am trying to bring in e3dc-rscp. I see the message 👀 [W400] Cannot find "e3dc-rscp" in latest repository Am I right that this is not an error because e3dc-rscp is new and therefore not in latest repo so far?
You're right. There are no errors automatically found.

Close https://github.com/ioBroker/AdapterRequests/issues/676 after review

hi,
here some review comments:

(optional) If you like you can remove all the encrypt/decrypt stuff and use the automatic solution ... see best practices in Readme of this repo for infos. YOu just need to add an "encrptedNative" and "protectedNative" sections to io-package and add a propoer admin globalDependency.
please remove https://github.com/git-kick/ioBroker.e3dc-rscp/blob/master/io-package.json#L67 if you do not offer a tab, also remove https://github.com/git-kick/ioBroker.e3dc-rscp/blob/master/admin/%40tab_m.html
You use sentry. Please add an info about it to Readme on top, please see https://github.com/ioBroker/plugin-sentry#how-can-i-get-my-sentry-account-as-a-developer
https://github.com/git-kick/ioBroker.e3dc-rscp/blob/master/main.js#L4-L19 should not be needed because the sentry plugin already does that, see the plugin readme for the way to access the Sentry instance if needed
The timeout here https://github.com/git-kick/ioBroker.e3dc-rscp/blob/master/main.js#L525 can not be cleared in unload  -also make sure that not multiple such timers run in parallel
Please also close the network connection in on unload ... Best try to test the adapter stop in compact mode

Thank you for checking and adjuting

Hi, for Sentry:

I think you are rthe first one to track "transactions" in sentry :-), but in fact as described in https://github.com/ioBroker/plugin-sentry#send-own-additional-events-to-sentry you can use (in on.ready) such code to get the internally used Sentry instance. Then you simply do not fo "Sentry.withScope" but your command

For Compavt mode:

The interesting stuff happens when you stop the adapter ... then check your log (maybe set to debug or such to gain more logs) if still logic is executed. Same for start adapter again after stopping (or restart) and check pot errors loggen that could mean overlaps (but in your case most likely nothing seen because you just connect to another service ...

Did that help?

Hi, thanks for your reply, yes it helps.
Sentry: I removed the plugin for now. It was only a trial effort. I put it to the backlog.
Compact mode: adapter falls back to normal mode, and I cannot find out the reason, see new topic.
All timers are now reset onUnload(), also tcpConnection ist closed/destroyed.
How is the way forward? On hold until the topic is solved?

loading files relatively like you do in https://github.com/git-kick/ioBroker.e3dc-rscp/blob/master/main.js#L8 can break beause formally this depends on the "working directory of the started nodejs process". This works for require because they always load rerative to the "script file that has the require in".
So use:
eval(fs.readFileSync(__dirname + "/admin/words.js").toString());
(ok, better is to require the path library and execute path.join(__dirname, 'admin/words.js)... that should do the trick

@Apollon77: Many thanks, it works using __dirname as you suggested.
Testing e3dc-rscp in Compact Mode was successful, no issues detected.
I think this completes my answers concerning your review comments. Or did I miss something?

Then all fine, please update npm and I will be happy to merge :-)

v1.0.0 is on npm, but I have some trouble passing the github tests - getting different error messages for every attempt, kind of strange.
I will update here as soon as testing is ok.

If you need support also just poke here or in Discord/Telegram

Ups, never think @Apollon77 gives you a minute to edit your post :-D
My third attempt on github worked, all tests passed now, npm updated.

Ups, never think @Apollon77 gives you a minute to edit your post :-D

lol :-)))
Welcome in the repo!

Danke für den super Support, Ingo!
-Uli

20.01.2022 18:01:28 Ingo Fischer @.***>:

Ups, never think @Apollon77[https://github.com/Apollon77] gives you a minute to edit your post :-D
lol :-)))
Welcome in the repo!
—
Reply to this email directly, view it on GitHub[https://github.com/ioBroker/ioBroker.repositories/pull/1589#issuecomment-1017717318], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ACEE4SQYEPJBWCSH4RX46XDUXA5R3ANCNFSM5LTGUJAQ].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].
You are receiving this because you authored the thread. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEIAAABCCAYAAADjVADoAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAnSURBVHic7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAAPBjRFIAASHKmKkAAAAASUVORK5CYII=###24x24:true###][Verfolgungsbild][https://github.com/notifications/beacon/ACEE4SWO7TMAZ3FDZX6MCKDUXA5R3A5CNFSM5LTGUJA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHSUSERQ.gif]

Many thanks!
For proceeding to stable, I need a discovery interface - could you guide me to some how-to, I failed when searching the forum.

You do not "need to" have a discovery ... If your dapter integrates devices that can be discovered then it would be great to add to discovery adapter.
So IF it is possible then you need to do a PR for https://github.com/ioBroker/ioBroker.discovery/tree/master/lib/adapters and addyour file there to detect  a device.
In fact discovery will scan all IPs in the network but can also do mdns or udp


Add health checks

Make the balancer able to tell if a connection is still up and skip connections that are down.

Splitting the issue in two. Health checks are already done.
Readiness checks will be done as part of #9.

Splitting the issue in two. Health checks are already done.
Readiness checks will be done as part of #9.


The JVM startup parameters for release packages and Docker files are not uniform

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
JVM startup parameters are not uniform and difficult to maintain. It is hoped that the JVM parameters can be maintained in only one place.
release package：
https://github.com/seata/seata/blob/develop/distribution/bin/seata-server.sh
docker image startup parameters by jib
https://github.com/seata/seata/blob/0cdaa08ec8f1ad060bb01a770cbc5d02c3ed6350/server/pom.xml#L279
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :
Seata version:
OS :
Others:

fixed in https://github.com/seata/seata/pull/5529


Fixes address padding and validation error positions

Description

Related Issue(s)

closes #2520

Verification/QA

Manual functionality testing

[ ] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added/updated
[ ] Cypress E2E test(s) have been added/updated
[ ] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[ ] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[ ] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[ ] This change/feature does not require any changes to Altinn Studio

Sprint board

[ ] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[ ] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

Takk @cammiida  Camilla! Vet du hvilken release av "altinn-app-frontend" npm-pakke dette blir med ut i?


V12 Cosmwasm Stargate queries

We need to decide what are the stargate queries we want to support in v12 and add these.

I can go ahead and try to make an initial list for now, and then we can review together in what we want to add or take out.

@mattverse let me know if I can help out (lots of queries to review!)


how do you send data from a form using ajax to mysqlserver please provide and example?

** PLEASE READ THIS BEFORE FILING AN ISSUE **
Feature Requests / Breaking Changes in mdl-1.x
The MDL core team has actively begun work on the next major version of MDL, dubbed MDL v2. Because we are a small team that's hyper-focused on delivering the best Material Design Library possible for the web, it is highly unlikely that we will be actively working on new features or making backwards-incompatible changes for MDL as it currently exists.
If there is a non-breaking feature you would like to see implemented in mdl-1.x and are willing to contribute, we'd be happy to offer assistance with you doing so. But we will not personally be actively working on said features.
While we are just getting started with our next version of MDL, you can see our current progress on master as well as an overview of the direction we're headed in our (WIP) developer guide as well as our initial POC branch for our new architecture.
If you're interested in information for a specific MDL v2 component, check out our v2-component issues to see which v2 milestone it's associated with and feel free to subscribe to that issue for updates.
Bugs
Please include the following information with your bug report:

What MDL Version are you using? (please be specific, e.g. major.minor.patch)

What browser(s) is this bug affecting (including version)?

What OS (and version) are you using?

What are the steps to reproduce the bug? Can you create a plunker/codepen/jsfiddle which reproduces it?

What is the expected behavior?

What is the actual behavior?

Any other information you believe would be useful?

Any description?

This issue tracker isn't for general support. It is only for problems with the code provided by Material Design Lite's code.


Import shadcn/ui does not success

Describe the bug
I using the command npm to install shadcn and even follow the tutorial, but the folders and files does not successfully create under the "./compoenents/ui/"
Even run rm -rf node_modules && rm package-lock.json and npm install to reinstall it still wont create.
https://ui.shadcn.com/docs/installation/vite
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-fuvw8d
Steps to reproduce
1.ask the bolt AI to install and use the shadcn, but failed.
2.self install by follow the https://ui.shadcn.com/docs/installation/vite tutorial in cmd, wont import
Expected behavior
after run the installation, the files and folder should be succesfully import.
Screen Recording / Screenshot

Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

I manually fix my issue by using the command line to create the folder "./src/components/ui" and touch files that does not import success, plus those configuration the bolt AI does not able to apply itself, so please take note if others user new project not able to add "shadcn/ui" in their project.


documentation??

where i could find some documentation about this module?

+1

Can someone guide me on how to run this project?


Settings overlap between woo-poly and Polylang

Currently there are various points of confusion about the settings relationships between Polylang and woo-poly which are only partly addressed through the documentation pages.
When changes are made in Polylang admin screens "Languages, Settings", some of these settings are or were silently reset again by woo-poly, other settings take precedence over woo-poly settings and are not reflected in the woo-poly settings page.
Settings reset in Polylang
These settings are or were forced set in Polylang on every page load:  you can change in Polylang Languages Settings and in the screen save is successful but on next page load, setting is immediately reset.
Product Category and Product Tag
Actually these translation options are no longer forced set in Polylang on every page load, but this is confusing for new users (#180 and https://wordpress.org/support/topic/categories-dont-translate/)  The behaviour change is caused by the removal of manageTaxonomiesTranslation which was forcing all Product Attributes to be translated on every page load, whereas now individual Attributes can be turned on and off for translation in Polylang Settings without being overwritten on next page load.
Possible Options:

[ ] Remove from woo-poly settings page: instead, register and set on initial plugin activation only, and redirect user to Polylang's Languages, Settings page to manage these settings
[ ] Synchronize on Save of Polylang settings as well as on save of woo-poly, so latest edit will win.  - [ ] Eliminate the synchronization issue by read/write always from the Polylang setting, so there is no second setting in wpi options which could become unsynchronized.
[ ] put back manageTaxonomiesTranslation just for Product Categories and Tags which would then be reset on each page load...  as is similarly still done in manageProductTranslation() and manageOrderTranslation()

Products
translation is currently forced on and required for woo-poly, there was a support ticket about this, possible solutions may include:

[ ] only turn on Products translation on initial activation of woo-poly.  If Products translation is later found to be turned off, then deactivate woo-poly or show warning message if Products translation is turned off in Polylang.  This could be added to canActivate() tests
[ ] disable Products translation checkbox in Polylang settings

Settings which independent or conflict between Polylang and woo-Poly
Now covered in documentation page these woo-poly settings are [mostly] ignored since the Polylang settings are used instead:

Menu Order (Polylang, Settings, Synchronization, Page order)
Thumbnail Id (Polylang, Settings, Synchronization, Featured image)
Comment Status (Polylang, Settings, Synchronization, Comment Status)

Possible solutions may be:

[ ] Remove these settings from woo-poly
[ ] Add filter hooks to allow these settings to apply to Products only, whereas the Polylang settings will apply to other Post types.

## Settings which must be set in Polylang
In addition to Products translation which must be on, the setting Languages, Settings, URL Modifications, " The language is set from content" must be not selected, so the same approach should apply.
Simply resetting the value after the user has changed it would just cause confusion, so the option should be disabled or cause woo-poly to deactivate with warning message.

For settings which need to be shown in both places, the complexity is the current woo-poly settings page is built from framework which is expecting to read the values from wpi-features and it may not be easy to redirect this to use Polylang setting.
A filter could probably be added as eg
add_action('update_option_wpi-features', function( $old_value, $value ) {
     //....
}, 10, 2);

and then save the relevant settings to Polylang,
However a full solution would also hook the Polylang update_option and update wpi-features so these values are reflected in woo-poly settings  (while avoiding a recursive loop).
Simpler to remove the duplicated setting?

As well as Polylang, there is settings overlap with WooCommerce.
For example, if stock management is turned off in WooCommerce, Settings, Products, Inventory, Manage Stock, then what happens if Stock Sync is turned on in Settings, WooPoly?
if Stock is on in WooPoly then stock.php is loaded which must be unnecessary and inefficient, and actually could potentially have undefined/unexpected results.

closing as various related changed and documentation improvements in the wiki mean this is not a real issue


Wayfire package is missing dependencies

Describe the bug
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:

Enable wayfire with programs.wayfire.enable = true
Launch wayfire from the terminal (it doesn't need a display manager, and I couldn't get one to work but that's irrelevant here)

Expected behavior
Wayfire launches
Additional context
It gives the following error
II 24-06-24 20:25:09.655 - [src/main.cpp:348] Starting wayfire version 0.8.1
II 24-06-24 20:25:09.655 - [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
II 24-06-24 20:25:09.655 - [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
EE 24-06-24 20:25:09.657 - [libseat] [libseat/backend/logind.c:317] Could not activate session: Permission denied
II 24-06-24 20:25:09.657 - [libseat] [libseat/libseat.c:76] Backend 'logind' failed to open seat, skipping
II 24-06-24 20:25:09.658 - [libseat] [seatd/seat.c:39] Created VT-bound seat seat0
II 24-06-24 20:25:09.658 - [libseat] [seatd/server.c:145] New client connected (pid: 2770, uid: 1000, gid: 100)
II 24-06-24 20:25:09.658 - [libseat] [libseat/backend/seatd.c:633] Started embedded seatd
EE 24-06-24 20:25:09.658 - [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
EE 24-06-24 20:25:09.658 - [libseat] [seatd/seat.c:61] Could not open tty0 to update VT: Permission denied
II 24-06-24 20:25:09.658 - [libseat] [seatd/seat.c:170] Added client 0 to seat0
EE 24-06-24 20:25:09.658 - [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
EE 24-06-24 20:25:09.658 - [libseat] [seatd/seat.c:72] Could not open terminal for VT 0: Permission denied
EE 24-06-24 20:25:09.658 - [libseat] [seatd/seat.c:461] Could not open VT for client
EE 24-06-24 20:25:09.658 - [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
EE 24-06-24 20:25:09.658 - [libseat] [seatd/seat.c:86] Could not open terminal to clean up VT 0: Permission denied
II 24-06-24 20:25:09.658 - [libseat] [libseat/libseat.c:73] Seat opened with backend 'builtin'
II 24-06-24 20:25:09.658 - [backend/session/session.c:109] Successfully loaded libseat session
II 24-06-24 20:25:09.658 - [backend/backend.c:84] Waiting for a session to become active
II 24-06-24 20:25:11.077 - [src/main.cpp:127] Got SIGINT, shutting down
EE 24-06-24 20:25:11.077 - [libseat] [common/terminal.c:162] Could not open target tty: Permission denied
EE 24-06-24 20:25:11.078 - [backend/backend.c:94] Failed to wait for session active: wl_event_loop_dispatch failed: Interrupted system call
EE 24-06-24 20:25:11.078 - [libseat] [seatd/seat.c:86] Could not open terminal to clean up VT 0: Permission denied
EE 24-06-24 20:25:11.078 - [backend/backend.c:359] Failed to start a DRM session
II 24-06-24 20:25:11.078 - [libseat] [seatd/seat.c:524] Closed client 0 on seat0
EE 24-06-24 20:25:11.078 - [src/main.cpp:140] Fatal error: Segmentation fault
II 24-06-24 20:25:11.078 - [libseat] [seatd/seat.c:192] Removed client 0 from seat0
II 24-06-24 20:25:11.078 - [libseat] [libseat/backend/seatd.c:645] Stopped embedded seatd

However, if I also enable sway:
programs.wayfire.enable = true;
programs.sway.enable = true;

Then wayfire launches as intended.  Clearly sway installs some dependencies (e.g. wlroots or something) that are required by wayfire that the package does not. It would be cleaner to allow only installing wayfire and not have to also install sway.
Notify maintainers
@alyssais
@wucke13
@wineee

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.34, NixOS, 24.05 (Uakari), 24.05.1695.dd457de7e08c`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

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

This seems not to be a bug in the wayfire package, but with the  nixos wayfire module.
It seems @wineee is the relevant maintainer for programs.wayfire.
wayfire does not import wayland-session.nix, that sets up required services like graphics and xdg, but sway does.
See #322312 for a quick fix

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/diary-of-a-new-nixos-user-thoughts-impressions-obstacles/47637/5


I am unable to install angular material -2 in Vs 2015 getting errors

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files (x86)\nodejs\\node.exe" "C:\Program Files
x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install" "@ng2-material/all"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.4
npm ERR! code E404
npm ERR! 404 Not found : @ng2-material%2fall
npm ERR! 404
npm ERR! 404 '@ng2-material%2fall' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!
npm ERR! 404 It was specified as a dependency of 'angular2-quickstart'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR!     F:\AppTy\UIFrame\UIFrame\npm-debug.log

From a glance, this doesn't look like a TypeScript-specific problem at all. I think StackOverflow or an Angular-related site/chat might be a better place to ask about this.


Is this package compatible with @types/json-schema?

Error in typescript lint. the definitions field is imcompatible.
Is there any plan to support @types/json-schema in type ?
import type { JSONSchema7 } from "json-schema"
import { zodToJsonSchema } from "zod-to-json-schema"
const schema: JSONSchema7 = { ... }
const validator = zodToJsonSchema(schema) // error

Unfortunately not. This will be addressed in v4 if I end up making it. It's safe to cast though - the data structure itself is compatible.


add icon with number of warnings/errors into dandisets listing

ie a yellow "drives with x" followed by number, mimicing

which if not 0 to go after size in those listings

For users it would provide some immediate feedback on either a dataset is "clean", and for developers (like ourselves) it could help to spot problematic dandisets without going through each one

I like this idea but we should only display this on dandisets owned by the user in question (or for us admins, all of them).

anon user sees those warnings when goes to DLP (tested in incognito on https://gui.dandiarchive.org/#/dandiset/000026) , I do not see a reason to make dandisets listing anyhow usertype specific then

On reconsidering this, I am against promoting the error status of dandiset validation into the main listing. I am not sure what value it adds, plus it will (at least in the short term) make the archive look universally worse (since currently, all new dandisets fail initial validation due to not having a license specified).
If someone gives me a good argument as to what value would outweigh this airing of dirty laundry, we can of course add this feature.

@yarikoptic, could you weigh in? My vote is to close this issue since I don't see what value comes from broadcasting the validation status in the dandiset listing.


Is the behavior of macrocase right?

macrocase("My URL") returns MY_UR_L (note the underscore between R and L). I would expect MY_URL
Regarding the word boundaries I would expect a result similar to cobolcase, snakecase, and kebabcase.
cobolcase("My URL") returns MY-URL
>>> from caseconverter import *
>>> cases = [str, macrocase, cobolcase, kebabcase, snakecase]
>>> for case in cases:
...     t = f"{case.__name__: <15}"
...     for s in ["My New URL", "My NewURL", "My URL", "My IP", "My MACRO"]:
...         t += f"{case(s): <15}"
...     print(t)

str            My New URL     My NewURL      My URL         My IP          My MACRO
macrocase      MY_NEW_UR_L    MY_NEW_U_R_L   MY_UR_L        MY_IP          MY_MA_C_R_O
cobolcase      MY-NEW-URL     MY-NEW-URL     MY-URL         MY-IP          MY-MACRO
kebabcase      my-new-url     my-new-url     my-url         my-ip          my-macro
snakecase      my_new_url     my_new_url     my_url         my_ip          my_macro

delims_only solves only part of the problem.
IMHO the whole issue is how we define macrocase. AFAICS the definition fo macrocase is not analogous to the other definitions.
One possible definition of could be snakecase(s).upper() or cobolcase(s).replace('-', '_').
macrocase has though a different behaviour. See example with s = "My NewURL" below:
>>> from caseconverter import *
>>>
>>> def snake_upper(s):
...     return snakecase(s).upper()
...
>>> def cobol_underscore(s):
...     return cobolcase(s).replace('-', '_')
...
>>> for case in [macrocase, cobolcase, kebabcase, snakecase, snake_upper, cobol_underscore]:
...     t = f"{case.__name__: <20}"
...     s = "My NewURL"
...     if case == macrocase:
...         t += f"{case(s, delims_only=True): <15}"
...     else:
...         t += f"{case(s): <15}"
...     print(t)
...
macrocase           MY_NEWURL
cobolcase           MY-NEW-URL
kebabcase           my-new-url
snakecase           my_new_url
snake_upper         MY_NEW_URL
cobol_underscore    MY_NEW_URL


Unable to compile: AtomicPtr and Unused parameter

Hello! I'm trying to get this to on a Leonardo board, and I'm getting the following exception at build:
❯ cargo check
    Checking usb-device v0.2.9
error[E0432]: unresolved import `core::sync::atomic::AtomicPtr`
   --> /Users/s.cargo/registry/src/index.crates.io-6f17d22bba15001f/usb-device-0.2.9/src/bus.rs:6:26
    |
6   | use core::sync::atomic::{AtomicPtr, Ordering};
    |                          ^^^^^^^^^
    |                          |
    |                          no `AtomicPtr` in `sync::atomic`
    |                          help: a similar name exists in the module: `AtomicI8`
    |
note: found an item that was configured out
   --> /Users/s/.rustup/toolchains/nightly-2023-08-08-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:186:12
    |
186 | pub struct AtomicPtr<T> {
    |            ^^^^^^^^^
    = note: the item is gated behind the `ptr` feature

error[E0432]: unresolved import `core::sync::atomic::AtomicPtr`
   --> /Users/s/.cargo/registry/src/index.crates.io-6f17d22bba15001f/usb-device-0.2.9/src/endpoint.rs:4:26
    |
4   | use core::sync::atomic::{AtomicPtr, Ordering};
    |                          ^^^^^^^^^
    |                          |
    |                          no `AtomicPtr` in `sync::atomic`
    |                          help: a similar name exists in the module: `AtomicI8`
    |
note: found an item that was configured out
   --> /Users/s/.rustup/toolchains/nightly-2023-08-08-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/sync/atomic.rs:186:12
    |
186 | pub struct AtomicPtr<T> {
    |            ^^^^^^^^^
    = note: the item is gated behind the `ptr` feature

error[E0392]: parameter `B` is never used
   --> /Users/s/.cargo/registry/src/index.crates.io-6f17d22bba15001f/usb-device-0.2.9/src/lib.rs:241:27
    |
241 |     struct DummyClass<'a, B: UsbBus> {
    |                           ^ unused parameter
    |
    = help: consider removing `B`, referring to it in a field, or using a marker such as `PhantomData`

error[E0392]: parameter `B` is never used
  --> /Users/s/.cargo/registry/src/index.crates.io-6f17d22bba15001f/usb-device-0.2.9/src/test_class.rs:27:26
   |
27 | pub struct TestClass<'a, B: UsbBus> {
   |                          ^ unused parameter
   |
   = help: consider removing `B`, referring to it in a field, or using a marker such as `PhantomData`

error[E0392]: parameter `B` is never used
  --> /Users/s.cargo/registry/src/index.crates.io-6f17d22bba15001f/usb-device-0.2.9/src/control_pipe.rs:31:28
   |
31 | pub struct ControlPipe<'a, B: UsbBus> {
   |                            ^ unused parameter
   |
   = help: consider removing `B`, referring to it in a field, or using a marker such as `PhantomData`

Any help would be much appreciated!

https://github.com/Rahix/avr-hal/issues/40#issuecomment-740626847

Yeah, that's pretty much what I was going to suggest. I couldn't reproduce this in this repo; I tried using the default toolchain and latest nightly, and it all works:
rustup update
git clone https://github.com/agausmann/atmega-usbd.git
cd atmega-usbd
cargo check
cargo build --release
cargo clean
cargo +nightly check
cargo +nightly build --release

That error usually happens if your target configuration is not right. You have to use this target JSON file for atmega32u4. The important part is "max-atomic-width": 16  to enable the AtomicPtr type, which is not present in the JSON files from avr-hal.
Glad you figured it out!

Sadly I had to remove USB entirely from my project. I can't get Serial to work at all and that's all I really needed it for. I think regular UART should be fine.
Thanks for the help anyway!


Mallory/coadd2

Adding coadd_decoder, test_coadd_decoder, and example_coadd_decoder

Did not pull from master / origin. Closing this to start a new branch.


Add null-safety support

Cool package! Would be awesome to migrate it to null-safety

yes @raulmabe i will be doing this also tried doing it but seems that there was no marginal changes, currently i'm busy with some stuff once that finishes will do this asap.

Made a PR #2!


Support for Spring Cloud

can servicedirectory be used for Spring Cloud's  Service Registry Discovery？

Reducing priority while waiting for reply.

It’s preview status and available in “com.google.cloud:google-cloud-servicedirectory-spring-starter”
https://github.com/GoogleCloudPlatform/spring-cloud-gcp/blob/main/spring-cloud-previews/README.md


[Linux] Support new theming api by freedesktop

Use case
Current theming api for linux and detection of system theme is not good and doesn't work all the time, In fact freedesktop foundation have announced a new api to solve all these things and get a better understanding of system theme for the app.

Proposal
The freedesktop api let's the application decide whether they have any preferred theme, if not then it let's it use the system-wide preference.
I don't have enough knowledge to implement this but have read from this article that:
Manually accessing the portal is a bit tedious, and so we wrap it into an
easy to use API. Here’s where things differ more from the original
elementary preference.

I think if it has to be done, then it has to be done manually as flutter is still using gtk-3.
Reference

https://blogs.gnome.org/alexm/2021/10/04/dark-style-preference/
https://blog.elementary.io/the-need-for-a-freedesktop-dark-style-preference/
https://gitlab.gnome.org/GNOME/gtk/-/issues/1919

As far as I know, the theming is done in flutter engine. Following the first link posted by @prateekmedia, I have started implementing a draft solution here using the gsettings key org.freedesktop.appearance.color-scheme.
This change removes the need to detect the theme by checking the color of the police, as it is currently done. If anyone feels like improving my draft, please go for it: I haven't tested or compiled it yet and I don't have org.freedesktop.appearance.color-scheme in my system yet since it is coming with Gnome42.

@MalcolmMielle If you are going to implement this then please also keep it backward compatible, so that the system without it like Ubuntu 20.04 can also use the old api to detect dark theme.
You can do it easily by checking if org.freedesktop.appearance.color-scheme exist on not.

@MalcolmMielle If you are going to implement this then please also keep it backward compatible, so that the system without it like Ubuntu 20.04 can also use the old api to detect dark theme.

[https://gitlab.gnome.org/exalm/color-scheme-simulator

@MalcolmMielle If you are going to implement this then please also keep it backward compatible, so that the system without it like Ubuntu 20.04 can also use the old api to detect dark theme.

You can actually use this API on other systems that don't support the API using the color-scheme-simulator's xdg-desktop-portal-impatience. Works like a charm for me when using libadwaita apps on Sway, inc. Flatpak apps.
I just run gsettings set org.gnome.gitlab.exalm.Impatience color-scheme "prefer-dark"; once xdg-desktop-portal-gnome or xdg-desktop-portal-wlr support the API I'll switch the schema from org.gnome.gitlab.exalm.Impatience to org.freedesktop.appearance.


[deployment.toml] "file" in the truststore configuration need to be changed as "file_name"

Location :
https://apim.docs.wso2.com/en/3.1.0/install-and-setup/upgrading-wso2-api-manager/upgrading-from-300-to-310/
https://apim.docs.wso2.com/en/3.1.0/install-and-setup/upgrading-wso2-api-manager/upgrading-from-260-to-310/
https://apim.docs.wso2.com/en/3.1.0/install-and-setup/upgrading-wso2-api-manager/upgrading-from-250-to-310/
https://apim.docs.wso2.com/en/3.1.0/install-and-setup/upgrading-wso2-api-manager/upgrading-from-220-to-310/
https://apim.docs.wso2.com/en/3.1.0/install-and-setup/upgrading-wso2-api-manager/upgrading-from-210-to-310/
https://apim.docs.wso2.com/en/3.1.0/install-and-setup/upgrading-wso2-api-manager/upgrading-from-200-to-310/
New Configuration :
[truststore]
type= "JKS"
file_name = "modified-client-truststore.jks"
password= "modified_password"
Please double check with the product team.

This issue is already fixed in 3.2.0 and latest migration documents, issue has been fixed in 3.1.0 and 3.0.0 with https://github.com/wso2/docs-apim/pull/2660 and https://github.com/wso2/docs-apim/pull/2662


Breakfast hash, super bacon

A pretty good regular breakfast regimen.

Nice, please add prep etc:
- ⏲ Prep time: 10 min
- 🍳Cook time: 30 min
- 🍽 Servings: 4


Error loading config from kube config when it contains credentials created by gcloud

When a kube config file contains credentials created from gcloud container clusters get-credentials ... it has a time in the users block. Loading this config file fails. I've narrowed down the issue to this specific piece of code: https://github.com/abonas/kubeclient/blob/master/lib/kubeclient/config.rb#L28, particularly YAML.safe_load(File.read(filename). Changing this to YAML.load fixes the issue, but I'm not sure that is the best approach. I've submitted an upstream bug report in psych, which can be found here: https://github.com/ruby/psych/issues/362
irb(main):005:0> config = Kubeclient::Config.read(ENV['KUBECONFIG'] || ENV['HOME'] + '/.kube/config')
Traceback (most recent call last):
       16: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:6:in `accept'
       15: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in `visit'
       14: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:162:in `visit_Psych_Nodes_Mapping'
       13: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `revive_hash'
       12: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each_slice'
       11: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in `each'
       10: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:338:in `block in revive_hash'
        9: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:32:in `accept'
        8: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:6:in `accept'
        7: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in `visit'
        6: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:123:in `visit_Psych_Nodes_Scalar'
        5: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:60:in `deserialize'
        4: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/scalar_scanner.rb:62:in `tokenize'
        3: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/scalar_scanner.rb:123:in `parse_time'
        2: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/class_loader.rb:28:in `load'
        1: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/class_loader.rb:97:in `find'
Psych::DisallowedClass (Tried to load unspecified class: Time)

users:
- name: gke_username
  user:
    auth-provider:
      config:
        access-token: redacted
        cmd-args: config config-helper --format=json
        cmd-path: /Users/tannerbruce/opt/google-cloud-sdk/bin/gcloud
        expiry: 2018-07-07T18:25:36Z
        expiry-key: '{.credential.token_expiry}'
        token-key: '{.credential.access_token}'
      name: gcp

Wow, thanks for catching this!!
My fault, It's a regression in 3.1.1.  I wasn't sure how to really test switch to safe_load (#334).  I was sure kubeconfigs shouldn't contain !!ruby ... classes but didn't occur to me safe_load might also exclude a builtin yaml type like date/time...
For an immediate workaround, use 3.1.0 (assuming you don't take config from untrusted sources.
It seems YAML.safe_load(yaml, [Date, Time]) should do the trick, working on PR...

Wow, Thanks for catching this!!
For now, use 3.1.0 instead of 3.1.1.
чт, 7 июн. 2018 г., 20:41 tanner-bruce<EMAIL_ADDRESS>
When a kube config file contains credentials created from gcloud
container clusters get-credentials ... it has a time in the users block.
Loading this config file fails. I've narrowed down the issue to this
specific piece of code:
https://github.com/abonas/kubeclient/blob/master/lib/kubeclient/config.rb#L28,
particularly YAML.safe_load(File.read(filename). Changing this to
YAML.load fixes the issue, but I'm not sure that is the best approach.
I've submitted an upstream bug report in psych, which can be found here:
ruby/psych#362 https://github.com/ruby/psych/issues/362
irb(main):005:0> config = Kubeclient::Config.read(ENV['KUBECONFIG'] || ENV['HOME'] + '/.kube/config')
Traceback (most recent call last):
16: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:6:in accept'        15: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in visit'
14: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:162:in visit_Psych_Nodes_Mapping'        13: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in revive_hash'
12: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in each_slice'        11: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:336:in each'
10: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:338:in block in revive_hash'         9: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:32:in accept'
8: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:6:in accept'         7: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/visitor.rb:16:in visit'
6: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:123:in visit_Psych_Nodes_Scalar'         5: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/visitors/to_ruby.rb:60:in deserialize'
4: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/scalar_scanner.rb:62:in tokenize'         3: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/scalar_scanner.rb:123:in parse_time'
2: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/class_loader.rb:28:in load'         1: from /usr/local/Cellar/ruby/2.5.1/lib/ruby/2.5.0/psych/class_loader.rb:97:in find'
Psych::DisallowedClass (Tried to load unspecified class: Time)
users:

name: gke_username
user:
auth-provider:
config:
access-token: redacted
cmd-args: config config-helper --format=json
cmd-path: /Users/tannerbruce/opt/google-cloud-sdk/bin/gcloud
expiry: 2018-07-07T18:25:36Z
expiry-key: '{.credential.token_expiry}'
token-key: '{.credential.access_token}'
name: gcp

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/abonas/kubeclient/issues/337, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQtGM3ubanpznSQ-HU-wM5H1IEKobsUks5t6WXdgaJpZM4Ue1b0
.


feat: add cleanup fixtures for test_evaluate

This PR adds @pytest.mark.usefixtures("_cleanup_after_test") to test_evaluate on tests that do not have.

@Klaijan, I checkout out to this branch and ran pytest test_unstructured/metrics/test_evaluate.py and the extra files still appeared


Confusing error message when trying to extend an interface

This is a somewhat cosmetic/quality of life issue, but I found the compiler error in this particular case could have been much more helpful.
TypeScript Version: 1.8.9
Code
interface A { }
class B extends A { }

Expected behavior: An error alluding to the fact that A cannot be extended because it is an interface.
Actual behavior:
a.ts(2,17): error TS2304: Cannot find name 'A'.

We should do the same check we do in other places where we resolve a value-name and get nothing (so look for a namespace-name or type-name instead to give a better error)

duplicate of https://github.com/Microsoft/TypeScript/issues/7900

and https://github.com/Microsoft/TypeScript/issues/102 covers the namespace one.


My Latest version of the processing code.

Support for gridding data through pyart.map.grid_from_radars
Check if azimuth is correct (some files have some weird stuff in them, their azimuth is constant...)
A bunch of verification if ouput directories exist (and creating them if not)
Reworked the whole PHIDP and DOPPLER correction in case of wrong folding (i.e. folding by half the nyquist).
Spawn a logfile for each separate radar file, because only one for the whole is unreadable when used with multiprocessing. It's a mess!
Working multiprocessing !!!


Update broken tests

This updates tests to specify at least one scope (failing to do so became an error with #403). CI could be much more helpful in catching problems like this before PRs merge; see #393.

@chlowell - I gave you admin access to the repo, please feel free to make any changes you see fit to the CI and to the release ceremony (but pls keep us in the loop)


Stack smash in test framework

[x] tests are added or updated

Fix a stack smash that occurs when memory compares are made that are larger than the on stack temporary buffers.  The bounds update wasn't accounting for the hex conversion that takes place.

The entire memory buffer is displayed on failure.
If the malloc fails, the code falls back to a truncated display.

Ready for (re)confirmation in light of #3156 comments

LGTM, but @dot-asm okay?

Fixed the test failed.

Reformatted.

I'd like to insist on two separate commits...

Elsewhere I kind of argued that appearance of error message is not necessarily unify-able. To give an example in the context, it's hard to spot difference in ERROR: (memory) out a8061dc1305136c6c22b8baf0c0127a9 [16] != expected a8061dc1305136c6c2268baf0c0127a9 [16] @ test/poly1305_internal_test.c:1566. [Original output was aligning expected and wrong outputs vertically to counter this.] Now imagine if you compared 1K. How helpful would that message be? I'm not saying that original printout was perfect in every sense, but I fail to see why new code has to produce less [and less] friendly output. If anything, it should produce better one. For example emphasizing differences somehow, e.g. 1234*65*78. And if it's long vector, chop it to multiple lines and even interleave wrong and expected. Or show just portion that is different...

@dot-asm, I've some ideas around that. Will get back about it tomorrow

This is a good example of where we need to add automation to the comparison - what you were doing visually is something which should be automated - lining things up for manual inspection indicates an opportunity to do a more automated approach IMHO.

To clarify, I'm not insisting on improving output in this request.

Agreed, it'll be for another PR.

Requested changes are in.
As for the output format, it is rough and crude.  There will have to be discussion about the best way to present the output and probably a couple of iterations.  At least now it is possible to change it globally.

And while you are at it, indentation is wrong in first if in test_mem_ne().

Looking at test_test output. It reads
...
ERROR: (string) "abc" [abc] != buf [abc] @ test/test_test.c:245
...

I reckon that it should read ==. It looks like messages in test_str_eq and test_str_ne are mixed up. There might be more mixups, haven't looked for more...

Requested changes made.

This needs re-base and approval from somebody else (as expression of "Andy, you're talking rubbish").

Whether you're talking rubbish or not, @dot-asm, shouldn't stop this PR, IMHO.  Keep the discussion alive (perhaps by recording an issue) or propose a change (in another PR) that enhances the display of these messages (I have some ideas of a better display of mem dumps, so there will be another PR related to what has been discussed here).
I'll approve this PR, but I want to see a rebase and successful build first.

Whether you're talking rubbish or not, @dot-asm, shouldn't stop this PR, IMHO.

That's exactly what I'm saying. I still stand by my words that I'd be "reluctant to let question[s] be without some kind of agreement about further steps to be taken," but it doesn't mean that progress can't be made.

Rebased version committed.

Scratch that, I stuffed up the merge.

Twice wrong, I got it right the first time :(

I've created #3341 so the suggestions here don't got lost or waylaid.

Good thing.

Hmmm, it appears this was already merged...  but not a peep here :-/

peep.