Migrating multiple streams

Hi,
This is a great tool! Thanks for the work you have done here.
I am migrating a fairly big product that contains several streams - several maintenance and one master. Do you have any recommendations for migrating multiple streams?

Hi vivshankar
We had a similar situation. We made a plan, which stream goes in which git repo.
For each planned git repo, we migrated all the planned streams in there.
Then we distributed the git repo and proceeded with the next streams/repos.

Thanks. So you ended up releasing multiple github repos each mapping to one RTC stream? That's what I am doing now, because I can see no way of building a linked commit history. I can see that, if you have a solid set of snapshots/baselines, this could be possible, in theory.
You would migrate the master stream and tag each baseline. Then branch out of each baseline and migrate the left over changesets from each maintenance stream. Of course, you lose the commit linking at that point, but it is better than nothing. Unfortunately, my RTC repo doesn't look that beautiful :-D

Yes, we released multiple git repos each mapping to one or more RTC Streams. Usually all the streams which belongs together we migrated in one git repo.
We grouped up to about 5 Streams in one repo. Sometimes one stream = one repo (if it contains a lot of binary files for example - allthough we tried to filter them out)
I think the baselines will be converted in tags, but not 100% sure.
We migrated also the maintancestreams into the same git repo but in a separate branch if I remember correctly.

I see. Thanks!


With vcpkg stack overflow

I used -DCMAKE_TOOLCHAIN_FILE=/Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake
CMakeLists.txt add find_package(OpenSSL REQUIRED) will stack overflow
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  /Users/apple/vcpkg/installed/arm64-osx/share/openssl/vcpkg-cmake-wrapper.cmake:37 (_find_package)
  /Users/apple/vcpkg/scripts/buildsystems/vcpkg.cmake:788 (include)
  CMakeLists.txt:35 (find_package)

I don't known the bug is the CPM or Vcpkg

This is work
find_package(OpenSSL REQUIRED)
include(${CPM_DOWNLOAD_LOCATION})
CPMAddPackage(name nghttp2_asio GITHUB_REPOSITORY fesily/nghttp2-asio GIT_TAG af3405e5869cd0b63658d63694a6ae757da99951)


Number of layers and nodes

I see the default configuration for the NN use 512/1024 nodes and variety of layers (3 to 6). But, is there any formula on how to decide the number of layers and nodes in the neural networks? Is it related to the number of features used? Thanks

AFAIK, that is a general problem with DNN, there is no formula. it is just a matter of trying and see if you are reaching an overfitting situation


Draw labels on top of lines. Fixes  #94.

I've split out the label from the line drawing, and added a second loop for this phase of drawing.

Chart.js 2.9.0 will have a concept of z-index: https://github.com/chartjs/Chart.js/pull/6262. It would be nice to make this utilize the same concept

Given the way callbacks are currently being handled, I'm not sure that refactoring the entire draw loop is in scope for this issue - you'd have to delegate all drawing back to the chart controller.

@kurkle you might be interested in this one given your work in the main repo

Hold off on this please. I've just noticed a side-effect where axis values aren't being redrawn when datasets are toggle on or off.

Ok, phew, fixed that.

This is a step towards layers, looks quite good. Should work without the 2nd transition.

Hi, I except the same enhancement. Is it still in progress ?


[Feature] Add support for EIP4844 transactions to consensus crate

Component
consensus, eips, genesis
Describe the feature you would like
Add both EIP4844 variants to
https://github.com/alloy-rs/alloy/tree/main/crates/consensus/src/transaction
https://github.com/paradigmxyz/reth/blob/add3c6a3a2ae0cecd8627533bbc5688a456435ad/crates/primitives/src/transaction/eip4844.rs
https://github.com/paradigmxyz/reth/blob/add3c6a3a2ae0cecd8627533bbc5688a456435ad/crates/primitives/src/transaction/sidecar.rs#L48-L58
with and without sidecar
Additional context
No response

Closed with #185


chore(master): release 1.49.0

:robot: I have created a release beep boop
1.49.0 (2024-08-05)
Features

add field in app space and consent (1bd9501)
add field in app space and consent (84ffc81)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/indykite/indykite-sdk-python/releases/tag/v1.49.0 :sunflower:


Update attach-gpu-to-linux-vm.md

OpenSSH is built into Windows, so there's no need to recommend 3rd party downloads.

@pronichkin : Thanks for your contribution! The author(s) have been notified to review your proposed change.


fix: calendar not updating on month change

I checked your code and fixed #2
Proof that it works: https://gfycat.com/helpfulgenerousemperorpenguin

I've been affected by this bug, thank you for fixing it. Trying out your branch going forward.
Too bad it seems this project isn't very active anymore :(


:fire: remove requirements.txt

Codecov Report

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

@@            Coverage Diff            @@
##            master      #398   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          505       505
=========================================
  Hits           505       505

Continue to review full report at Codecov.

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


Consider adding an environment variable for dynamic linking

Would you be ok with an environment variable that could be used to specify dynamic linking ?
At the moment dynamic linking relies on the "pkg-config" feature.
having the condition include also an environment variable would

make it easy to use dynamic linking in a dev environment (even for dependencies of dependencies). It could save precious compile time
Make it easy for some linux distributions to avoid static compilation and rely on dynamic linking (where static compilation fails for some reason, you could rely on a pre-built version, (one example of this is nixos).

if you are ok with this, I would be happy to make a PR.
how about the name CARGO_ZSTD_SYS_DYNAMIC_LINKING for the environment variable ?
Last but not least, thanks a lot for the great library!

another dev from nixpkgs who came to find if there was a way to not need to patch nushell to make it's dependency use pkg-config checking in :)


Add auto-generate sample for Confluent and ConnectedVMwarevSphere

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


custom y-axis value labels

I'm trying to display Y-Axis labels in a certain way where the intervals aren't equal.  Like this screenshot example.
Any tips or ideas?

Hi, currently there is no way of doing this. In an ideal world what spacing options would you have?

Ideally extending the array of label strings to an array of label/value pairs (the string label and their corresponding values), and plotting those at the appropriate place y axis position.


Add PAYG instructions to v2.8

Fixes #[issue_number]
Reminders

See the README for more details on how to work with the Rancher docs.

Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.

If the pull request is dependent on an upcoming release, remember to add a "MERGE ON RELEASE" label and set the proper milestone.

Description

Comments

@jeremy-moffitt Referring to https://github.com/rancher/rancher-docs/issues/1354, should we recommend users be on Rancher v2.8.4? Should the v2.7 docs be kept or removed? (https://ranchermanager.docs.rancher.com/v2.7/integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration)

Regarding 2.7 support, any existing customers running PAYG on 2.7 are still in support and do not have to migrate, so I'm hesitant to remove the 2.7 docs at this point. We could add a note indicating the listings have been updated to 2.8.4 and customers are encouraged to remain current with the listing to get the latest features and security fixes.

@jeremy-moffitt Referring to #1354, should we recommend users be on Rancher v2.8.4? Should the v2.7 docs be kept or removed? (https://ranchermanager.docs.rancher.com/v2.7/integrations-in-rancher/cloud-marketplace/cloud-marketplace-payg-integration)

@LucasSaintarbor anything you need from me or my team on this? We'll be starting the updates to 2.9.1 in a couple weeks so we'll have a new request... for now the 2.8.4 info is current.

@LucasSaintarbor anything you need from me or my team on this? We'll be starting the updates to 2.9.1 in a couple weeks so we'll have a new request... for now the 2.8.4 info is current.

Hey @jeremy-moffitt, sorry for the late reply. May you review my latest update (https://github.com/rancher/rancher-docs/pull/1374/commits/393aac003f1d7a91440ff7eec50516a788422ae6)?

Please let me know if I need to track down another reviewer from my team. I'm assuming one of the doc writers will perform a review aimed at catching non-content issues. Thanks.

FYI, the AWS Rancher PAYG listings are now up to 2.9.1, with Azure to follow shortly.

Azure is stuck on 2.8.4 for now, but per my previous comment AWS is updated to 2.9.1... let me know if you need more info for the doc update. thanks!


: vertical-align prop

add vertical align as a global configuration

➤ Артем Ломако commented:
I can’t add prop for vertical align because this component AwTableBuilder don’t know anything about columns inside (AwTableCol) if you want to align content there. The prop for vertical align there is in the component AwTableCol already.

➤ Артем Ломако commented:
https://git.awescode.com/awes-io/ui/merge_requests/17 ( https://git.awescode.com/awes-io/ui/merge_requests/17 )


Sync sets file to 0 bytes when source path is same as destination path

Expected Behavior
Gradle skips commands to copy files that have the exact same source and target paths.
Current Behavior
Gradle attempts to overwrite the target file with itself, which results in a file with 0 bytes (on Windows at least).
Context
The build I've got configured uses a fairly complex Sync task that pulls from other project's tasks to gather a whole wide array of built files into a single location. It uses a generic task name to find all tasks of a certain type, and because the project the Sync task belongs to also has a task of that name, it gets some source == target copies.
Steps to Reproduce (for bugs)
Make a Sync task that copies from and into the same location.
Your Environment
Windows 7, 64-bit, JDK 1.8, Gradle 4.0

Also, this possibly relates to https://github.com/gradle/gradle/issues/1643

I think the behavior of a task like this should be to fail the build.  It seems like a mistake in the configuration of the task. The task would never be up-to-date and the semantics of a task that deletes and copies its outputs as inputs would be undefined.
If you're doing something like this:
task sync(type: Sync) {
    from(allprojects.collect {
        tasks.withType(Sync).matching { it.name == "sync" }
    })
}

You could filter by the current task, so it won't rely on the outputs of itself. e.g.,
task sync(type: Sync) { thisTask ->
    from(allprojects.collect {
        tasks.withType(Sync).matching { it.name == "sync" && it != thisTask }
    })
}

This is a little hokey still. It would be better to model this as publications from the projects instead of reaching into the tasks, but we're working on making that sort of thing better with variant-aware dependency management.

A failure works if you think this is an invalid configuration. As long as Gradle doesn't pretend everything works when it wrote 0 byte files, I'm happy and I'll continue to clean up the build as I find better ways of doing things.

I ran into the same problem (also on windows) when collecting projects outputs into a directory that was incidentally the output directory of one of those projects. This happens with both Sync and Copy.
I know this is wrong, but it took me a while to hunt this down (blaming imported Ant task at first) and I would have appreciated the fail-fast behaviour gradle usually exhibits when trying something that cannot work.


How to use puppeteer without nodejs and vscode ?

Hi everyone,
I have made a bot to automate a task using puppeteer and nodejs, but i want to use this on another computer where we dont have vscode etc. Is it possible to use puppeteer without it, may be chrome extension or a webpage with node installed on remote server, kindly help me.

Convert it to .exe

You can use https://chrome.agenty.com/


UI now showing broker list when DISABLELOGDIRSCOLLECTION=true

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[ ] Manually (please, describe, if necessary)
[x] Unit checks
[x] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

checked with docker-compose with KAFKA_CLUSTERS_0_DISABLELOGDIRSCOLLECTION: "true" set
broker list is still empty:

,

verified, working fine now

@kamsharipova thank you <3


Transparent configuration input validation

Hi all. I have received a feature request that I would like to share with you:
It would be nice if a syntax check is done before processing (configuration) information and a more meaningful error message is displayed. E.g.: "error parsing json of config" or "invalid value for ids:connectorDeployMode". This should usually be just another if/else or try/catch code block and is very helpful for debugging.

Didn't know whether to create the issue here or in the framework. Feel free to move/link it.

I have just tested what happens if there are incorrect values in the configuration, there a pretty good error messages meanwhile:

Will close this request now, since the error messages issued in the meantime by the infomodel-serializer-parser within the infomodel-serializer provide quite good infos, which value within for example a configuration is faulty and why the config can't be parsed.


Removed redundent assignment

I believe the intent was list_pr.body.opa = LV_OPA_COVER;
Certainly the behavior would be LV_OPA_COVER.

Thank you!


Unable to resolve Swashbuckle.SwaggerModel.ISwaggerProvider while activating middleware

I'm not sure if this is a bug, so please let me know if I'm doing something dumb. I've followed the docs and done the startup.cs config items listed below:
ConfigureServices
  public void ConfigureServices(IServiceCollection services)
  {
         services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1);
         //Redacted stuff here for authentication, and connection string factory

         services.AddSwaggerGen(c =>
         {
            c.SwaggerDoc("v1", new Info { Title = "TestSwagger API", Version = "v1" });
            c.ExampleFilters();
         });
  }

Configure
     public void Configure(IApplicationBuilder app, IHostingEnvironment env)
     {
         if (env.IsDevelopment())
         {
             app.UseDeveloperExceptionPage();
         }
         else
         {
             app.UseHsts();
         }

         app.UseHttpsRedirection();

         app.UseAuthentication();

         app.UseMvc();
         app.UseSwagger("swagger/{documentName}/swagger.json");

         app.UseSwaggerUI(c =>
         {
             c.SwaggerEndpoint("/swagger/v1/swagger.json", "TestSwagger Api V1");
             c.RoutePrefix = string.Empty;
         });
   }

However, when I run, I get the following:
InvalidOperationException: Unable to resolve service for type 'Swashbuckle.Swagger.Model.ISwaggerProvider' while attempting to activate 'Swashbuckle.Swagger.Application.SwaggerMiddleware'.
Microsoft.Extensions.Internal.ActivatorUtilities+ConstructorMatcher.CreateInstance(IServiceProvider provider)

I've also tried this without the ExampleFilters() stuff, and I'm getting the same issue. I'm wondering whether something is out of order in one of the methods. I've tried moving stuff around, but I'm not really sure how to proceed. Is there something obviously incorrect that I'm doing?

Which version of Swashbuckle.AspNetCore are you using?
It's bizarre to see the namespace Swashbuckle.Swagger.Model.ISwaggerProvider being surfaced as that namespace is defined in the [Web API version of Swashbuckle] (https://github.com/domaindrivendev/Swashbuckle) BUT NOT the ASP.NET Core version.

It's using 4.0.1 for Swashbuckle.AspNetCore.

Ok well you must have something else weird going on because the types your exception is referencing are not contained within Swashbuckle.AspNetCore 4.0.1.
Perhaps start from a fresh project to find the simplest possible repro?

InvalidOperationException: Unable to resolve service for type 'Swashbuckle.AspNetCore.Swagger.ISwaggerProvider' while attempting to Invoke middleware 'Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware'.

I'm still seeing this with a fresh project:
InvalidOperationException: No constructor for type 'Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator' can be instantiated using services from the service container and default values.
.net core 3.0 preview 9
Swashbuckle.AspNetCore 5.0.0-rc2

@chrisipeters if you have
Services.AddMVC()
to your ConfigureServices method that may fix it. Worked for me. The .NET Core 3 migration docs say not to call AddMVC, but Swashbuckle seems to need it.

@williamwgant - are you still seeing this with the latest version (5.6.3 at time of writing)? If not, please close the ticket. If so, please create a minimal app (i.e. starting from empty proj) that repro's the issue and post to github so I can pull down and troubleshoot.

@williamwgant - are you still seeing this with the latest version (5.6.3 at time of writing)? If not, please close the ticket. If so, please create a minimal app (i.e. starting from empty proj) that repro's the issue and post to github so I can pull down and troubleshoot.

Closing due to inactivity


Connect44 scraper is inactive on scraper.peviitor.ro

ENVIRONMENT: windows
URL: https://scrapers.peviitor.ro/src/connect44/index.html/
Browser: chrome
Device: Laptop
OS: Windows 11
STEPS TO REPRODUCE:
Open the URL in the browser
1.We open browser
2.We insert the url
3.we write "Connect44" company
4.we Run the scraper
Expected results: We should have a result with company jobs
Actual results: Scraper is not loading . Server inactiv

@andreireporter13 remove unnecessary lines of code

Same result.


Switch URL fetcher from fetching the plain URL to https://api.allorigins.win/

AllOrgins allows CloudLink TURBO to connect to sites that don't allow GET requests.
Example:

I'll look in to it, but it's unlikely I'll use it.

Working on 1.1, adding this in.

This may need to be delayed, as it'd break certain parts of the code.

Done in SWB, not possible in SWB+ because SWB+ renders the HTML.


(DO NOT MERGE) [BEAM-12383] Adding Kafka IO to Gradle cross-language test suites.

With this change, cross-language tests should automatically run on the the Cross-Language PostCommit test suites on Jenkins.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Note this is intended as a followup to #15093 and shouldn't be merged in until after that's reviewed and merged.

 All the failures in the cross-language tests seem to be due to BEAM-12805, and the actual Go SDK tests are all passing at this point.
R: @lostluck

R: @ihji

I did a spot check and agree that the new Go validatesCrossLanguageRunnerGoUsingJava tasks are not the cause of the failures, and are certainly executing.

@youngoli - What is the next step on this PR?

My bad, I totally forgot about this PR for a while. I'll address Heejong's comments and try to wrap this up.

Yep, let's do it.


Remove svg.svg class, restore .rss-icon

Fix regression from https://github.com/go-gitea/gitea/pull/24476 where the svg.svg class misaligns SVG icons across the site and streched buttons unintentionally in vertical height.
Before (button 30.3px):

After (button 30px):

vertical-align: middle is not suitable to align icons to text because

Aligns the middle of the element with the baseline plus half the x-height of the parent.

Example of vertical-align: middle from MDN:

So I think the existing vertical-align: text-top is generally still the best bet:

Sorry I can't really see a different here.

I would suggest to have a framework level solution for "button svg icon margin magic", instead of adding a lot of "gt-xxx", it doesn't look good to me.

As I said, it's likely not possible to satisfy all cases with a "global" style. The only true vertical centering is align-content: center which only works in flexbox so is not applicable everywhere.


Add support for S/MIME working group ballot SMC-08

Resolves #99 and #100.

Blocked pending successful IPR for SMC-08 and publication of SMBR v1.0.6.


Bullet needed for SetAccessors

In 'How the state property accessor methods work' section, another bullet is required for set accessors.
I am also not able to edit this particular file in GitHub because of 404 error. Kindly have a look.

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

ID: a1795c22-9e0f-8a69-a517-ffbe38a2cd30
Version Independent ID: 9d2c1569-6d6f-97fa-881d-b4a0f61623a2
Content: Managing State - Bot Service
Content Source: articles/v4sdk/bot-builder-concept-state.md
Service: bot-service
Product: bot-framework
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

Closing it as I have found it fixed in live-sync branch.


Disable logging in development mode?

Is there a way to just console.log() when in development mode? so i can see it in the terminal and not push the logs to the cloud

#22 works! but now i'm getting bunch of extra context, system details logged as well, is there a way to log the text only?

Hi @nooblyf!
Thank you for reaching out!
Currently, there is no built-in option to customize the output as the output is intended to be consumed by Better Stack.
I can suggest two approaches here:

Make structured logs easier to read by getting rid of deeply nested fields:
Set contextObjectMaxDepth: 1 option when initializing Logtail logger.

Replace logtail functions in development with console.log

logtail = {};
logtail.fatal = console.log;
logtail.error = console.log;
logtail.warn = console.log;
logtail.info = console.log;
logtail.debug = console.log;
logtail.flush = function() {};

Let me know if either of those workarounds would work for you 🙏
Have a great weekend!

got it, thanks!


Add instrumentation (Part 1)

This first PR adds instrumentation to Typst, among the features of this first iteration are:

Logging enabled using a -v verbosity flag
Flamegraph based on instrumentation using the --flamegraph argument
Instrumentation of most the compiler, layout system, PDF exporter functions
Few log messages (disabled by default)
A new backtrace function printing a backtrace into the console, this is for debugging purposes.

Additionally, this PR fixes a rare bug where recursive calls could cause the stack to overflow. This is now solved by using the stacker crate which is used and maintained by the rust-dev teams, long term support should therefore not be an issue. Instrumentation increased the usage of the stack space, making this error more common. Therefore, this should hopefully fix it for good.

I am wondering whether I should move the backtrace function into a separate debug environment that is only enabled using a CLI flag for now.

Thanks!


I want to save a pinned item id so that I can set the item pinned later automatically.

Set an item pinned by swiping left.
Save that pinned item's id somewhere (probably SharedPreferences) from onItemPinned(int position) callback.
Turn the application off.
Turn it back again.
At this moment, I want the pinned item be pinned without my touch.

What should I do?

Nevermind, solved myself. Just called this
if (mLastSelectedItemIndex >= 0 && mLastSelectedItemIndex < mAdapter.getItemCount()) {
    ViewHolder viewHolder = mRecyclerView.findViewHolderForAdapterPosition(mLastSelectedItemIndex);
    mAdapter.onPerformAfterSwipeReaction(viewHolder, mLastSelectedItemIndex, RecyclerViewSwipeManager.RESULT_SWIPED_LEFT, RecyclerViewSwipeManager.AFTER_SWIPE_REACTION_MOVE_TO_SWIPED_DIRECTION);
}

Thanks for the great awesome library!


fix(pgadmin4): helm install usage

What this PR does / why we need it:
Fixes some helm commands in the README.

 Sorry for that. Updated the README with Helm 2 / 3 variants.

@aslafy-z please also bump the chart version if you make an adjustment.

I thought it was not needed as I only touch the README. But for sure, will do.


MSAuthTokenContext authTokenHistory - Failed to retrieve history state or none was found. Note: this is happening only on FIRST launch after install

I have severe issue on iOS preventing from app being loaded and stuck on the splash screen. This is the error:
2019-11-08 12:32:01.751569+0200 MYAPP[2503:103445] [AppCenter] WARNING: -[MSAuthTokenContext authTokenHistory]/210 Failed to retrieve history state or none was found.
Note: this is happening only on FIRST launch after install.
I am not using any auth service from Appcenter.

Hello, would you mind reaching out to our support team? You can contact us from the App Center portal directly. Thank you.


Add Logging

Set up slog for structured logging https://pkg.go.dev/log/slog.
Allow setting appropriate log levels, and right output formats based on flags.
Ensure development uses debug, anything else can be what ever it set via flag (default flag option should be "info" level).

DONE


HIP/HCC: Struggling with 128-bit store/load instructions

I am struggling to utilize global/flat load/store dwordx4 instructions via HIP / HCC under ROCm 1.7. The problems are as follows:
1. dwordx4 instructions are apparently not generated for (some?) HIP vector types
Without writing inline assembly, the obvious way to get the compiler to emit 128-bit memory instructions would be to use 128-bit wide types. This did not work for me with ulonglong2 and I think neither with uint4. The only type that reliably gets dwordx4 ops is __uint128_t, which is not portable to CUDA.
2. Writing dwordx4 inline asm gives "invalid in/output constraint"
Even with __uint128_t, directly writing asm to do a 128-bit mem instructions (because you want to add glc/slc flags, maybe) does not work.
__uint128_t dst;
asm volatile( "global_load_dwordx4 %0, %1, off glc slc" : "=v" (dst) : "r" (address) );

This code gives "unable to allocate register for output constraint". Same for the store instruction. The only way I’ve found to make this work is to explicitly move your 32-bit pieces into contiguous registers before the instruction, and then just use them explicitly, like this:
uint32_t data[4];
fill_data(data);
asm volatile(
                "v_mov_b32 v27, %1\n\t"
                "v_mov_b32 v28, %2\n\t"
                "v_mov_b32 v29, %3\n\t"
                "v_mov_b32 v30, %4\n\t"
                "global_store_dwordx4 %0, v[27:30], off\n\t"
                :
                : "r" (address), "v" (data[0]), "v" (data[1]), "v" (data[2]), "v" (data[3])
                : "v27", "v28", "v29", "v30", "memory" );

Which is obviously pretty clunky and costs you registers.
3. (How) does the explicit register constraint work?
In the LLVM Language Reference Manual there is a small note about AMDGPU asm constraints.

r: A 32 or 64-bit integer register.
[0-9]v: The 32-bit VGPR register, number 0-9.
[0-9]s: The 32-bit SGPR register, number 0-9.

I’ve tried to utilize it like this (to get around problem number 2), but to no avail:
uint32_t data[4];
fill_data(data);
asm volatile(
                "global_store_dwordx4 %0, v[6:9], off\n\t"
                :
                : "r" (address), "6v" (data[0]), "7v" (data[1]), "8v" (data[2]), "9v" (data[3])
                : "memory" );

The error message is

invalid input constraint '6v' in asm

If you need more complete code samples in order to reproduce this, please let me know. :)

hcc defines some short vector types in hc_short_vector.inl.
To use them, add #include hc_short_vector_vector.hpp and you declare a vector of 4 integers as
hc::short_vector::int4 my_int4_vector;
The load/store of this vector would leverage the dwordx4 mem ops.
You could also take a look at this code example using short vector types: https://github.com/RadeonOpenCompute/hcc/blob/clang_tot_upgrade/tests/Unit/AmpShortVectors/hc_short_vector_device2.cpp

Thank you, but I am using HIP, not HCC directly. Hence this also lacks portability in a way, although of course I can just do a typedef depending on #ifdef __HCC__, using the native CUDA types (or HIP types) otherwise.
(As an aside: Why doesn’t HIP pull in the native HCC/CUDA types directly, rather than defining its own?)
I also get plenty of errors trying to #include <hc_short_vector.hpp> in my code right now. I think this is due to trying to include HCC headers side by side with HIP/hcc_detail headers.

Another way to get around this is to create a type with the vector extension in llvm:
// short vector type of 4 integers
typedef int myint4_t  __attribute__((ext_vector_type(4)));
myint4_t v1;
v1.x = 0;
For the HIP related question, I'd suggest creating a new issue under HIP because that's the forum to discuss this kind of issues.
https://github.com/ROCm-Developer-Tools/HIP

I filed a quite straightforward bug with HIP two weeks ago and haven’t got a response since, so I got the impression that this repo was the best place the report all issues pertaining any of the ROCm-projects. Anyhow I’ve checked and HIP’s uint4 actually works fine; it’s only ulonglong2 that results in two 64-bit loads.
Still, the direct asm does not work. Should I file a bug with HCC for that?

What is the source where you aren't getting 128-bit loads? That is a more important problem. I'm guessing you're trying to access a flat pointer kernel argument

@arsenm I want to set glc / slc flags (as shown in the example) and afaik there is no way to do this without asm; correct me if I’m wrong.

These are set for some atomic operations, and non temporal accesses from the IR. I'm not sure what the source looks like for hcc to use those

In my case glc improves performance (even if I have to issue 4 additional v_mov_b32 to be able to use it) – semantically it is not needed. Hence there probably isn’t a specific way to write my code without asm and still get glc set in the eventual isa asm output.
Another use case for issuing load/store in asm is to fine-tune s_waitcnt vmcnt(n) calls. Without asm, the compiler will (always?) use float_op_dwordx4 over global_op_dwordx4 (maybe because it just can’t tell where the data is, or because it’s not been updated with these gfx900 opcodes, no idea) and then issue s_waitcnt vmcnt(0), presumably according to the ISA guide which says:

9.2.2. Importing Timing Consideration
Since the data for a FLAT load can come from either LDS or the texture cache, and because
these units have different latencies, there is a potential race condition with respect to the
VM_CNT and LGKM_CNT counters. Because of this, the only sensible S_WAITCNT value to
use after FLAT instructions is zero.

However, if I know that none of my data is in LDS, I can call s_waitcnt vmcnt(n) with n > 0 step-by-step, as I consume the data from loads I have issued, which is obviously faster than blocking until all memory ops have completed before consuming the first bit of loaded data.


EmbeddedResourcePath Regex Parser Bug

Take FormFactory as example, following step 2 in this link adding
<link href="/Content/FormFactory/FormFactory.css" rel="stylesheet" type="text/css"/>

EXPECT:      FormFactory.css to load correctly
ACTUAL:      404 not found
The embedded resource namespace is FormFactory.Content.FormFactory.FormFactory.css
The EmbeddedResourcePath Regex Parsing code on line 17 incorrectly produce directory name as Content.FormFactory and therefore I have to use the url becomes ~/Content.FormFactory/FormFactory.css
SUGGEST to fix this simply by replacing any dots with slashes on the parsed directory name on line 43

What's your assembly name?
On Thu, 13 Sep 2018 at 03:15, Billy<EMAIL_ADDRESS>wrote:

Take FormFactory as example, following step 2 in this link
http://formfactoryaspmvc.azurewebsites.net/ adding

EXPECT:      FormFactory.css to load correctly
ACTUAL:      404 not found
The embedded resource namespace is
FormFactory.Content.FormFactory.FormFactory.css
The EmbeddedResourcePath Regex Parsing code on line 17
https://github.com/mcintyre321/EmbeddedResourceVirtualPathProvider/blob/2f38cf2bc0e72052e03b4f36483d4ff45809fc45/EmbeddedResourceVirtualPathProvider/Vpp.cs#L17
incorrectly produce directory name as Content.FormFactory and therefore I
have to use the url becomes ~/Content.FormFactory/FormFactory.css
SUGGEST to fix this simply by replacing any dots with slashes on the
parsed directory name on line 43
https://github.com/mcintyre321/EmbeddedResourceVirtualPathProvider/blob/2f38cf2bc0e72052e03b4f36483d4ff45809fc45/EmbeddedResourceVirtualPathProvider/Vpp.cs#L43
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mcintyre321/EmbeddedResourceVirtualPathProvider/issues/41,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQ0-iIn5j-lIwkAfZiseDNeIRodKOLqks5uab-pgaJpZM4WmdID
.

Oh you're talking about FF. :)
It looks to me that the FormFactory example site is using <link href="/Content/FormFactory/FormFactory.css" rel="stylesheet" type="text/css"/> and it is working fine?
There's a problem which is that making something an Embedded Resource is a lossy action - both / and . are mapped to . which makes it difficult to tell the difference between a directory and a javascript filename with multiple .s in it. The startup code, which scans the assemblies for ERs, should take the assembly name into account.


GuiCheckBox always return 0 (false)

As I understand it the function should return 1 (true) when the checked state is changed, so that the calling function can handle the checkbox changed event.
The function in question:
https://github.com/raysan5/raygui/blob/25c8c65a6e5f0f4d4b564a0343861898c6f2778b/src/raygui.h#L2193C11-L2193C11
Perhaps just setting result to 1 here would fix it: https://github.com/raysan5/raygui/blob/25c8c65a6e5f0f4d4b564a0343861898c6f2778b/src/raygui.h#L2231C13-L2231C82

As I understand it the function should return 1 (true) when the checked state is changed, so that the calling function can handle the checkbox changed event.

 All controls have been redesigned to return internal-states as required but most of those internal-states have not been implemented yet because I was not sure what were the most convenient states to return for every control. Checkbox value change status seems quite useful! Just sent a commit!
Also note that some functions comments could be off at the moment, from previous version.


Smoking cooking mode

Give user full control of the flips. Timer starts in 00:00:00 and goes up indefinitely until the user marks a flip (lap).

Partially addressed by #19. For a real smoking option we need to figure out how to keep the timer running in the background even when the app is closed. This would be needed as you need to do things throughought the day and use the watch for other purposes. When the timers expire there is hopefully a way to trigger an alarm and bring the barbecue boss app back to the screen for user attention.

Quoting @nilsbenson

I agree - I think it makes more sense to have a pop-up notification of sorts if we are running as a widget. I haven't looked at the restrictions on them though, so I don't know if we can. Ideally, in that case, it would work similar to the built-in timer in that when it goes off, it pops itself up and lets you do what you need. For grilling this makes less sense, but for smoking/baking/long term cooking it makes more so you don't have to watch it the entire time and can just set-and-forget.

The smoking/baking functionality could be a new app. Blending the two functions into one may be cumbersome.

https://forums.garmin.com/developer/connect-iq/f/discussion/5439/widget-app
according to this, a widget can't be exposed by a watch app / they have to be two different apps in the store with different manifest IDs. We can support building both out of the same codebase but they won't be able to communicate settings with each other.
I think the widget/glance view would be super useful for quick checks on smoking, but without some kind of shared data storage it will be difficult. I think we should long term consider a companion app to smooth over some of these rough edges (in particular - for devices without direct bluetooth API access we still want to be able to communicate meat probe info to the app).
I think for now we move forward with implementing smoking in the app with support for "background" timers and get it working. once we have a workable solution we can look at maybe a companion app or apps.
I also think that since this smoking mode is a different mode/use case/model than the grilling we should maybe look at having the user access the functionality by "nextPage" from the welcome screen. I will see if I can mock up a screenshot of what I'm thinking.

Closing as widgets are more constrained than apps.


Remove Unlatch to Home Assistant ?

Hi everyone,
Thank a lot for your works !
I'm beginner with Nuki Hub 9.0 and i have only one little problem. I can't disable the "Unlatch" discovery to my home assistant. My door can't do this and i want to disable the button on home assistant.
How i can do it ?
I have "unceck" "Unlatch" in nuki hub but nothing happen..
Thank a lot :)

Closing for not following the issue template.
You can reopen once you have filled in the template


[WIP] mobile/ci: Always run CC compile-time-options tests in PRs

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

this is not quite right - i will test it in staging

updated and tested


EAP-FAST failing in generation of ClientHello with 1.1.1-pre1

It looks like something in OpenSSL 1.1.1-pre1 broke EAP-FAST support. SSL_connect() is now failing on the client side when trying to prepare ClientHello (debug logs from wpa_supplicant):
EAP-FAST: No PAC found - starting provisioning
EAP-FAST: Enabling authenticated provisioning TLS cipher suites
OpenSSL: cipher suites: DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-SHA:AES128-SHA:RC4-SHA
SSL: (where=0x10 ret=0x1)
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:before SSL initialization
OpenSSL: TX ver=0x0 content_type=256 (TLS header info/)
OpenSSL: Message - hexdump(len=5): 15 03 01 00 02
OpenSSL: TX ver=0x304 content_type=21 (alert/)
OpenSSL: Message - hexdump(len=2): 02 50
SSL: (where=0x4008 ret=0x250)
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error
EAP: Status notification: local TLS alert (param=internal error)
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in error
OpenSSL: openssl_handshake - SSL_connect error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available
This is what this looks like in a successful run (from a build with OpenSSL 1.1.0f):
EAP-FAST: No PAC found - starting provisioning
EAP-FAST: Enabling authenticated provisioning TLS cipher suites
OpenSSL: cipher suites: DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-SHA:AES128-SHA:RC4-SHA
SSL: (where=0x10 ret=0x1)
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:before SSL initialization
OpenSSL: TX ver=0x0 content_type=256 (TLS header info/)
OpenSSL: Message - hexdump(len=5): 16 03 01 00 63
OpenSSL: TX ver=0x303 content_type=22 (handshake/client hello)
OpenSSL: Message - hexdump(len=99): 01 00 00 5f 03 03 0d 86 19 ca 1e 86 c9 9c ee 4e 8e ab 67 4c 13 0d 13 ec 0d 70 78 49 4e 8e c2 76 74 47 85 e1 40 4d 00 00 0a 00 39 00 33 00 35 00 2f 00 ff 01 00 00 2c 00 0d 00 20 00 1e 06 01 06 02 06 03 05 01 05 02 05 03 04 01 04 02 04 03 03 01 03 02 03 03 02 01 02 02 02 03 00 16 00 00 00 17 00 00
SSL: (where=0x1001 ret=0x1)
SSL: SSL_connect:SSLv3/TLS write client hello
SSL: (where=0x1002 ret=0xffffffff)
SSL: SSL_connect:error in SSLv3/TLS write client hello
SSL: SSL_connect - want more data

Have you read https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/?

Have you configured your own list of ciphers?  IF so, did you disable TLS 1.3?  If not, that's an error.
See this for details: https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/

@kroeckx hah ;)

I read an earlier TLSv1.3 blog post, but did not realize that there would be additional requirement to explicitly disable v1.3 in such a case. I do actually disable various TLS versions with older OpenSSL versions, but that was for another issue and that code was apparently conditional on OPENSSL_VERSION_NUMBER, so it did not get included here. I did even go through the CHANGES document before opening this issue, but somehow managed to miss the connection between the TLS v1.3 item and the EAP-FAST needs to change the ciphersuite list.
Adding an explicit SSL_set_options(ssl, SSL_OP_NO_TLSv1_3) does indeed resolve this. I think that it would have been nicer if OpenSSL were to still allow TLS v1.2 to be used in this type of case where all TLS protocols were enabled and the selected cipher suites would work with v1.2, but not v1.3.. Anyway, now that I know what to search for, the first CHANGES file entry does explain this very specific case and implies that 1.1.1 is not automatically backwards compatible with the past on this front.

Yes, or should we use it as a hook to rediscuss the compatibility issue?  Right now, if you set your own ciphers and don't set any of the SSL options, your application will break.  I think that's pretty wrong.
When phrased this way, I think we should reconsider the policy.  @mattcaswell and others?

So I think we discussed this before and came to the current policy as the least-bad option.
Options I can think of are:

Don't check if we have TLSv1.3 capable ciphers until we actually negotiate a TLSv1.3 connection and then fail

If we have no TLSv1.3 capable ciphers then automatically disable TLSv1.3

Do what we do now: Check early whether we are configured to allow TLSv1.3 but have no TLSv1.3 capable ciphers and bail out if so (regardless of whether TLSv1.3 is actually negotiated)

We actually originally had option 1 (more by accident than design). The problem with this approach is that everything seems to be working just fine until you actually negotiate TLSv1.3 and then you get a failure. To start with at least, successful TLSv1.3 connections may be few and far between - which means you end up getting spurious failures which are difficult to track down what the problem is (this was why we decided to move to option 3).
Option 2 is also possible. The big problem with this approach is that you think you have enabled TLSv1.3 and are getting all of its benefits but in actual fact you will silently never negotiate it. You can imagine tens of thousands of mis-configured clients and servers out there for years to come which believe they are running the latest OpenSSL version and are therefore using the latest TLS version, but are actually using an out-of-date version of the protocol.

Which is worst: An upgrade break things or it keeps using TLS 1.2
(I have no good answer for this.)

There is nothing known to be wrong with TLS 1.2, why force people off it?
There is something pretty bad about a "dot dot 1" release breaking applications.
I probably agreed with the current behavior but I have changed my mind and I prefer option two.

There is nothing known to be wrong with TLS 1.2, why force people off it?

Not right now...but what about in the future. I think it is a real problem to have people think they are using TLSv1.3 when they silently never will.

I probably agreed with the current behavior but I have changed my mind and I prefer option two.

I think option 2 is the worst out of all three of them. If we change the current behaviour I would prefer to go with option 1.

How many year until TLS 1.2 is "risky"?  The ciphers it uses are basically the same as 1.3.  1.3 adds 0rtt and not much else cryptographically.
Option 1 is the same as option 3, except the breakage happens at connection time, not object creation time.
Option 2 is the only one, if you don't want to break existing users and if you are not worried about TLS 1.2 being broken in the next five years.

There is also option 4, which is to treat TLS 1.3 ciphers as different animals from TLS 1.2 ciphers (like ECDH curves are different animals from ciphers) and either always enable them or, if they must be configurable, make them configurable via a separate mechanism.
This is what BoringSSL switched to doing very early on, based on experience attempting to deploy TLS 1.3 in existing code.

The ciphers it uses are basically the same as 1.3. 1.3 adds 0rtt and not much else cryptographically.

TLS 1.3 adds quite a lot cryptographically. There is more to crypto than just muttering AES-GCM. The TLS 1.2 handshake uses a number of primitives wrong. The ServerKeyExchange signature, for instance, does not cover anywhere near what it should be covering, which is why we needed the server_random anti-downgrade hack in TLS 1.3 to begin with. It's a workaround for a flaw in TLS 1.2.

Option 4 is probably not feasible for a dot-dot release.  Yes, I glossed over the crypto.  When do you think TLS 1.2 will be risky enough to be deprecated?

Why is option 4 not feasible for a dot-dot release? It seems the most compatible option. Compatibility dictates that adding new capabilities (TLS 1.3 ciphers) is generally okay, but changing the semantics of existing ones (cipher configs that, to date, never precluded a higher TLS version) is questionable. Our deployment experience suggested this was the most compatible approach.
The root cause is that TLS 1.3 is the first time that ciphers have been removed in a version of TLS, and so by whitelisting TLS versions, you implicitly whitelist future newer TLS versions that your library may add. If you recall way back when the cipher suite negotiation was being revised from weirdly repurposing TLS 1.2 ciphers (PSK in particular) to new bespoke ones, this was a big part of the motivation. By separating them completely, it becomes much easier to consider them orthogonal, which was the cleanest way to deal with this issue.
(Re TLS 1.2: TLS 1.2 will likely be around for some time, for practical purposes, just as other legacy TLS settings are still around. That's how deployments work. The old things take a long time to fall off the conveyor belt. The immediate corollary here is downgrade protection is absolutely critical, which is why we've been so pushy about not adding another client fallback.)

Hmmm, option 4 does sound quite attractive. What does the API look like for this in Boring?

Oh, we went the hardcoded behavior route and didn't bother making them separately configurable. There's all of three ciphers.
But there's nothing stopping them from being configurable separately (or even some magic token in the existing cipher language to opt out of default 1.3 behavior, I dunno). We just generally don't add this sort of thing until a need comes up and we better understand what people are trying to do. And if a need never comes up, yay less work. :-)

Yeah, option 4 with the ciphers always enabled seems like a fine position, on first read.

Yeah, option 4 with the ciphers always enabled seems like a fine position, on first read.

Currently working on it. Although I do think we're going to need an API to control which ones are enabled. Our test suite relies on that all over the place at the moment.

I expect the FIPS 140 certification to require that you can disable non-FIPS crypto. Maybe that can be done with just a FIPS switch per session?  But if others have similar needs, at least the ability to enable and disable ciphers will be required.

So we went with option 4 - now in master.


OADP-3260: Change operator image pull policy to IfNotPresent

The related issue is about performance right? Changing the value of the field can speed up some scenarios?
My concern is if can break anything? (ideally no, if we always tag images with different tags in each release, right? but on master we use latest, so probably better to just apply this change to release branches?)

My concern is if can break anything? (ideally no, if we always tag images with different tags in each release, right? but on master we use latest, so probably better to just apply this change to release branches?)

Or address this in downstream bundle automation.

As discussed in scrum we will be going ahead with the changes only in downstream csv.


Addition of standalone wrappers for image downloading & formatting with ImageMagic

PR contained two wrappers for Obtaining and processing species images:

Download a set of one or more species images from wikipedia, using species name(s) as the sole input. This differs from the main static pipeline wrapper based on core_dbs & RefSeq URLs. Useful for when we need to update/modify images and licensing information for already existing species on e! main
A wrapper to format and convert species images from wikipedia to be correctly formatted into PNG and resized, using appropriate background colours etc (options to wrapper).

Vasily approved merge on this PR. Thank you @vsitnik


can't correctly process filenames with square brackets

Description:
Any files with square brackets in filename will be ignored. Both rimage.exe *.jpg and rimage.exe aaa[bbb].jpg result the same.
Additional info:

OS: Win11
Shell: Powershell
Version 0.8.1

This will be fixed in new release, if it cant expand glob pattern, will use input as default.


AttributeError: 'Tokenizer' object has no attribute 'tokenizer'

I was try to use this module but i am getting this type of error
AttributeError: 'Tokenizer' object has no attribute 'tokenizer'

so that i copied our code in readme file that also doesn't work.

I've got the same problem

You can solve the problem by installing this version of openai-whisper :
pip install openai-whisper==20230117


EFCDelay inaccuracy

hi,In the blueprint of 4.25, using ECFDelay event delayed by 1 minute, the time is much slower than delay.

Won't fix because of the lack of information :(


Can this be used in production level?

Hi,
We want to use Azure IoT Edge as an identity translation gateway with the protocol translation gateway. Because we are working with an OBD-II device that strictly uses TCP/IP as communication protocol. We can only add IP, PORT, and APN in the device nothing else.
We want to use these devices with the Azure IoT Hub. As we know Azure IoT hub works only with MQTT, AMQP, and HTTPS.
We want to use Identity translation for:

Creating IDs for these lots of devices from the IoT edge and register them in IoT Hub.
If possible, we want to automatically make the device to Azure IoT Hub communication via IoT Edge.

We want to use protocol translation for:

Acting as a medium to communicate between the Devices working on the TCP/IP and the Azure IoT Hub, which supports MQTT, AMQP, and HTTPS communication protocol.

We want to have a Bi-directional communication with the Azure IoT cloud. So we can send messages back to the devices when needed and do FOTA.
My Questions:

Is there a module available for the TCP/IP implementation?
Does this repository can be used for production-level implementation for the above?
Is there any full detailed documentation like this sample for implementing the actual asked for production level?
Does this Implementation way provides two-way communication? Device to edge to cloud and then Cloud to edge to the device?
Do we have to create manually each device in the gateway as the real devices and do manual registration for each of them?
This means If I have 1000 devices in real-time, do I have to create 1000 virtual devices in the gateways manually and then register them manually on the IoT Hub?
Is this identity translation gateway in development and is actually not fully blown for the production purpose?
Is there any working example or a full developer guide for Implementing Azure IoT Edge gateway as an Identity translation gateway with protocol translation gateway?

Hi @rajdpandey I have answered your question in StackOverflow:
https://stackoverflow.com/questions/68342852/azure-iot-edge-as-a-translation-gateway-for-tcp-ip-based-obd-ii-device/68889668#68889668


Add asymmetric authentication features for public-key

[x] Validate a digital signature from a robot user associated with a public-key. Let a robot user be successful log-in if the validation is valid (then the robot user can interact with some APIs such as to generate or refresh an access token (JWT))
[x] Add new API for robot user to generate/refresh associated access token (in form of JWT)

Been done in the PR #315


Add slovak (sk) language to weblate

Please add slovak language (sk) to the weblate.
Thank you.

Hello misa, I added Slovak to sober of the main components:
https://translate.johnromanodorazio.com/projects/liturgical-calendar/-/sk/
Thank you for contributing, just a reminder that the names of the liturgical memorials and feasts should correspond with the Roman Missal published in the region.
May I ask what brought your interest to this project? How are you thinking of using the project?


Widescreen support is very poor

Widescreen support is very poor

The logo for balance and stake grows very big
The action column grow out of proportion

Part of #45


Too much unsed private methods in HtmlRenderer

See example

They are not unused. They are actually used in templates.

See https://github.com/yiisoft/yii-web/blob/d7d5fb8eb58a0c5d976ac19016e1141eda87cb19/src/ErrorHandler/templates/exception.php#L417

Do you think there's a better way to do it?

Decided to make these methods public.


Understand complexFilter method

Someone to help me to understand how complex filters works?
I'd like to use this filter with complexFilter method: https://stackoverflow.com/a/30832903/8118350
I don't know how I can cutting this:
[0:v]scale=ih*16/9:-1,boxblur=luma_radius=min(h\,w)/20:luma_power=1:chroma_radius=min(cw\,ch)/20:chroma_power=1[bg];[bg][0:v]overlay=(W-w)/2:(H-h)/2,crop=h=iw*9/16

TL;DR: You should split the string it using the ; as delimiter, and pass the resulting array as argument of complexFilter()

Here is some general info about complex filters if you ever need to use it again:

Each complex filter command is a combination of input(s)-filter(s) (and sometimes -output(s))

if no output is specified, then the output will be the one given at the end of the FFmpeg command
you don't need to specify an output unless you plan to use it as an input for more filters -> the output of a first combination can be the input of the second one

[ ] indicates input or output information for filters

an input with a number like [0:v] means we take the first input given with the -i option earlier in the command
an input with no number like [bg] means we take the output of a previous group as input

: separates filter options
, separates filters
; separates groups of input(s)-filter(s)-output(s)

And a more detailed explanation of the string you want to split, with newlines at each :, , and ;:
// First group
  // This is the input for the first batch of filters
  [0:v]
    scale=
      // These are options for the scale filter
      w=ih*16/9:
      h=-1,
    boxblur=
      // These are options for the boxblur filter
      luma_radius=min(h\,w)/20:
      luma_power=1:
      chroma_radius=min(cw\,ch)/20:
      chroma_power=1
  // This is the output of [0:v] going through the 2 filters
  [bg];
// Second group
  // These are the 2 inputs required for the overlay filter
  [bg][0:v]
    overlay=
      // These are options for the overlay filter
      x=(W-w)/2:
      y=(H-h)/2,
    crop=
    // These are options for the crop filter
      h=iw*9/16
  // No output is given here as it will use the one from the FFmpeg full command

[
{
"filter": "scale",
"options": "ih16/9:-1",
"inputs": "[0:v]",
"outputs": "[scaled]"
},
{
"filter": "boxblur",
"options": {
"luma_radius": "min(h\,w)/20",
"luma_power": 1,
"chroma_radius": "min(cw\,ch)/20",
"chroma_power": 1
},
"inputs": "[scaled]",
"outputs": "[bg]"
},
{
"filter": "overlay",
"options": "(W-w)/2:(H-h)/2",
"inputs": ["[bg]", "[0:v]"],
"croph=iw9/16"
}
]


Base64 decoding

Is base64 string data type supported with this library?
Thanks

@realivanjx could you expand on what you mean by this? There's not (as far as I know) a base64 encoding scheme built into QR codes (https://en.wikipedia.org/wiki/QR_code#Encoding). You can of course store binary data directly, or store base64 encoded strings as text.
If you have a QR code with a base64 encoded string as the content, jsQR will just return the encoded string (since there's no indication that it's base64), but you can of course decode it as you normally would decode a base64 string (atob on the client, using Buffer in node JS).
If I'm misunderstanding the question, or if there is example you can show around what you mean I'd love to understand. Thanks!

@realivanjx anything?

Sorry for the super late response. I have been busy lately. What i mean is if i have an image stored as base64 string can i use this lib to read it and get its qr code string? Hope that makes sense. Thanks...

I'm looking for this too.
I have this image:

And this is the representative value Base64:
data:image/png;base64,[encoded data, 4900 characters]
It would be great if we can decode the qrcode without render the image in an img object.

I am looking for the same.

This is the nearest code that I have to solve my problem (rendering the image)
  public jsQR_fromBase64(base64: string): Promise<QRCode> {
    return new Promise<QRCode>((resolve, reject) => {
      const image: HTMLImageElement = document.createElement('img');
      image.onload = () => {
        const canvas: HTMLCanvasElement = document.createElement('canvas');
        var context: CanvasRenderingContext2D = canvas.getContext('2d');

        canvas.width = image.width;
        canvas.height = image.height;
        context.drawImage(image, 0, 0);

        try {
          const imageData: ImageData = context.getImageData(0, 0, image.width, image.height);

          const qrCode: QRCode = jsQR(imageData.data, imageData.width, imageData.height);
          resolve(qrCode);
        } catch (e) {
          reject(e);
        }
      };
      image.src = base64;
    })
  }

@cozmo
Can we include this one or similar into the library?

I'm also very interesting. This is exactly what did I do, using canvas.getContext('2d'), but it sounds suboptimal create new canvas just to render picture and read it again into Uint8ClampedArray format. Is there a way to read picture on frontend directly into format which jsQR can accept the image? Perhaps way to convert HTMLImageElement to Uint8ClampedArray?

any update?

this solution doesn't work in web-workers

Since this library doesn't seem to be maintained anymore, you can get base64 data url support (and more) out of the box with this one instead: https://github.com/nimiq/qr-scanner (Note: I am not the author)

You can also do the following for a full server side implementation:
import { getSync as getImageDataFromBuffer } from '@andreekeberg/imagedata';
import jsQR from 'jsqr';

const qrcodeImage= 'base64stringhere';
const qrcodeBuffer = Buffer.from(qrcodeImage, 'base64');
const qrArray = getImageDataFromBuffer(qrcodeBuffer);
const code = jsQR(qrArray.data, qrArray.width, qrArray.height);

Different definitions of "maintained" I guess - jsQR never has had any desire to in include random image decoding functionality. As @zanechua pointed out there are libraries that do that, and bloating this library is an anti design pattern IMO.
Better to take in image data from any source and let the consumer pass it in as they wish IMO.

I think it's good to have choices. If you prefer an all-in-one package, then perhaps something else may suit you. Otherwise I would just respect the maintainer's wishes on their vision of the package as they've contributed their free time to it. At the end of the day, it's just personal preferences. 😊
That being said, I understand where @adamreisnz is coming from when he uses the metrics to determine if a project is maintained.
However as I've seen in the OSS community, sometimes packages just don't need an update as long as they are working well or have reached full maturity in their intended use case.
I went with this package as I needed something to run in a node backend and not having access to the browser specific js code.
Honestly the library works as intended as @cozmo is following the imageData spec and I think that's a good choice as you have a standard that anyone can refer to.

thanks @JaviRpo it worked


Support libc property in package.json for optional dependencies

For example:
https://www.npmjs.com/package/@swc/core-linux-arm64-musl?activeTab=code
https://registry.npmjs.org/@swc/core-linux-arm64-musl
https://registry.npmjs.org/@swc/core-linux-arm64-gnu

Actually, this seems to not be implemented in npm at the moment, so closing this until it is.


Add ategt game

This is a silly zombie game that I made in honor of Halloween.

Your pull request needs further work because of the following reason(s):

You changed a file called zombies.css, this is not one of the three allowed names.
You changed a file called zombies.html, this is not one of the three allowed names.
You changed a file called zombies.js, this is not one of the three allowed names.
Your main.js file was not found, it is a requirement (even if empty)
Your main.css file was not found, it is a requirement (even if empty)
Your index.html file was not found, this one should exist and be nonempty

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

7b5ee7960ddd442f2e84fcb43f4f6d6593c6a539

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

Your JS file potentially has references to foul language.
These submissions must be checked manually because of the potential complexity of submissions, if you've reached this point in the process you're most likely a valid submission.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

9c04d752b1f3f9c754ac6368bd72f6d7d0a0ef98


user: Expand checks in getHaveServerData.

The one check we had would be perfectly sufficient in a world where
we used a reliable form of storage for keeping data from the server
on the device between runs of the app.  It does not suffice given
our model with redux-persist.
This doesn't fix the problem -- that will take something more
fundamental -- but it hopefully mitigates the worst consequences.
In particular, empirically we already reasonably gracefully handle
in the unreads view and the PM-conversations view a situation where
either state.unreads or state.pmConversations refers to streams,
subscriptions, or users that we don't have data about:
https://chat.zulip.org/#narrow/stream/48-mobile/topic/Android.3A.20White.20screen/near/1151982
Fixes: #4587

Thanks, LGTM! Merged.


feat/popover

Implements the Popover widget.
The popover is already ready, but in the example I want to add an Input, which is not ready yet.
Will merge after integrating the Input widget

[ ] Double check the style before merging

Random:
I would recommend using the Figma Shadcn Presets for getting the internal stylings. instead of digging through source code.
https://www.figma.com/file/kMH2pLL9dE6ScmjSpELx6p/shadcn-ui-Design-System-Community?type=design&is-community-duplicate=1&fuid=

@dickermoshe the figma is not updated with the last changes unfortunately

Dang it.
That was the source of truth for the default text theme. I'll need to confirm their values later


Incompatible with<EMAIL_ADDRESS>

Reproduction https://github.com/jlarmstrongiv/colorjsio-ts

Hi @jlarmstrongiv, is this about the dev branch or the currently released v0.5.0?

@LeaVerou this issue is about<EMAIL_ADDRESS>with<EMAIL_ADDRESS>

Ah okay. We've made some major changes wrt typing in v0.6.0 and we’re still not done. We’ll do an alpha soon, please check it out to see if you still have this issue?

Sure 👍 Let me know when you make an alpha release of v0.6.0 or a patch release of 0.5.1 and I’ll give it a go

@jlarmstrongiv Could you check whether this error still happens on v0.5.2?

@MysteryBlokHed thank you!  I can confirm the error is resolved on v0.5.2 👍


chore(deps): Bump @untemps/vocal from 1.2.1 to 1.3.0

Closes #50

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update rustup manifest.

A few things here:
The manifest will now check the Cargo.toml for the rustup github project on its master branch, which will have the same version that the exe from the url provides. The tags on the github repo were behind and did not match the executable at the url in the manifest.
The VC2015 redistributable dependency turned out to be unnecessary. To use the MSVC ABI, rustup actually requires the Visual Studio 2015/2017 Build Tools. I'm working on a manifest to install the build tools, but it needs more testing. Defaulting to the stable-gnu toolchain allows users to build rust programs without having to install the Visual Studio Build Tools immediately. This is always available in Rustup.
The ?version=$version in the url is unnecessary and doesn't actually do anything. It can be removed, but I'm not sure what to do about the autoupdate. If the autoupdate section is removed then checkver.ps1 doesn't update the version tag in the manifest when there is a new version. Is there a way to let scoop update the version tag in the manifest and nothing else?
What do you think?

"url": "https://win.rustup.rs/#/rustup-init.exe",
"autoupdate": {
    "url": "https://win.rustup.rs/#/rustup-init.exe"
},

This should work. autoupdate has to be present.

Thanks for your help there! I pushed the changes you suggested.


chore: update release workflow go version to stable

Ensure the library can be compiled and is compiled using latest stable version of Go.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (cf554bf) to head (b5d912f).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #349   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines         3696      3696
=========================================
  Hits          3696      3696

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update Doc For modal

For all components that use modal, the partial is no longer needed.

the modal partial inclusion no longer appears in the documentation


Alert manager configuration

What did you do?
Follow the different example to configure alert manager
Example:
   _config+:: {
     alertmanager+: {
       config: importstr 'alertmanager-config.yaml',
     },
   },
 }).alertmanager.secret +

I've tried both approach, external and normal
What did you expect to see?
I expected to see a new file in the manifest after I run
jsonnet -J vendor -m manifests ${1-snim.jsonnet} | xargs -I{} sh -c 'cat $1 | gojsontoyaml > $1.yaml; rm -f $1' -- {}
What did you see instead? Under which circumstances?
Nothing in my manifest has changed. I can tell because GIT does not see any change.
Environment

Kubernetes version information:

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T12:22:21Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

kube-aws
I'm sure I'm doing something wrong but can't find what it is. What sort of file should it produce?

Thanks a lot for reporting this!
My suspicion is that you're going to need to remove the .alertmanager.secret, as having that will just render the Alertmanager secret. But to make sure, could you share your whole jsonnet file?
When I wrote this I wasn't sure whether that's more confusing or better as the jsonnet command will run faster. If you think this was confusing then I'm more than happy to change it to something else!

If I remove .alertmanager.secret, the secret file gets updated but no other change.

Isn't that the change we want? The Alertmanager config is in that Secret.

oh, I didn't realise that. Interesting. I'll give it a go tomorrow (Melbourne time here)

Ok so I got it working. Happy to close this ticket? should we update the doc?

I'm not sure if related but since I've added the config above I see errors in prometheus-1 pod (not in 0)
level=warn ts=2018-07-04T05:57:50.867914921Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: node:node_memory_bytes_available:sum\nexpr: sum by(node) ((node_memory_MemFree{job=\"node-exporter\"} + node_memory_Cached{job=\"node-exporter\"}\n  + node_memory_Buffers{job=\"node-exporter\"}) * on(namespace, pod) group_left(node)\n  node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"
level=warn ts=2018-07-04T05:57:50.875798014Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: node:node_memory_bytes_total:sum\nexpr: sum by(node) (node_memory_MemTotal{job=\"node-exporter\"} * on(namespace, pod)\n  group_left(node) node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"
level=warn ts=2018-07-04T05:57:50.895352773Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: 'node:node_memory_utilisation:'\nexpr: 1 - sum by(node) ((node_memory_MemFree{job=\"node-exporter\"} + node_memory_Cached{job=\"node-exporter\"}\n  + node_memory_Buffers{job=\"node-exporter\"}) * on(namespace, pod) group_left(node)\n  node_namespace_pod:kube_pod_info:) / sum by(node) (node_memory_MemTotal{job=\"node-exporter\"}\n  * on(namespace, pod) group_left(node) node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"
level=warn ts=2018-07-04T05:57:50.906524844Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: node:node_memory_swap_io_bytes:sum_rate\nexpr: 1000 * sum by(node) ((rate(node_vmstat_pgpgin{job=\"node-exporter\"}[1m]) + rate(node_vmstat_pgpgout{job=\"node-exporter\"}[1m]))\n  * on(namespace, pod) group_left(node) node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"
level=warn ts=2018-07-04T05:57:50.917692767Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: node:node_disk_utilisation:avg_irate\nexpr: avg by(node) (irate(node_disk_io_time_ms{device=~\"(sd|xvd|nvme).+\",job=\"node-exporter\"}[1m])\n  / 1000 * on(namespace, pod) group_left(node) node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"
level=warn ts=2018-07-04T05:57:50.928829316Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: node:node_disk_saturation:avg_irate\nexpr: avg by(node) (irate(node_disk_io_time_weighted{device=~\"(sd|xvd|nvme).+\",job=\"node-exporter\"}[1m])\n  / 1000 * on(namespace, pod) group_left(node) node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"
level=warn ts=2018-07-04T05:57:50.941201105Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: node:node_net_utilisation:sum_irate\nexpr: sum by(node) ((irate(node_network_receive_bytes{device=\"eth0\",job=\"node-exporter\"}[1m])\n  + irate(node_network_transmit_bytes{device=\"eth0\",job=\"node-exporter\"}[1m])) * on(namespace,\n  pod) group_left(node) node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"
level=warn ts=2018-07-04T05:57:50.951370703Z caller=manager.go:339 component="rule manager" group=node.rules msg="Evaluating rule failed" rule="record: node:node_net_saturation:sum_irate\nexpr: sum by(node) ((irate(node_network_receive_drop{device=\"eth0\",job=\"node-exporter\"}[1m])\n  + irate(node_network_transmit_drop{device=\"eth0\",job=\"node-exporter\"}[1m])) * on(namespace,\n  pod) group_left(node) node_namespace_pod:kube_pod_info:)\n" err="many-to-many matching not allowed: matching labels must be unique on one side"

What could be going on?

It’s actually unrelated, but there is already a PR to fix some of these on the Kubernetes monitoring mixin.
If you have suggestions on how to improve the docs we would be more than happy with accepting those!

working for me.


Style validator

Fail to compile if a method is missing javadocs or something
Could use adventure as reference iirc

Did some research for a while and didn't really find anything that seemed fitting so I'm deeming this as too much of a hassle and ignoring for now


Move store init to config

Hi!
First of all, thanks for your work! But playing with the samples I noticed that I have some SQL related issue. I digged into the code a bit and found that I tried to queue a job, but the job table is not created yet. So, I thought since the code defines the usage of SQL as a store via configuration, maybe it would be a good idea to initialize it there.
If you think that this is not the issue (or this behaviour is intentional), please feel free to close/remove this PR and branch.

Ah, the problem is when trying add jobs before starting the engine, because then the database hasn't been initialized.
I agree, putting the InitAsync call in the configuration solves the problem, and makes much more sense.
I will merge your PR, thanks!


Script fails when run in docker container on Jenkins

Hi. I've been trying to to troubleshoot this issue for days with no success.
When I run the script inside docker container on my local machine, everything works as expected, I get:
- Processing layers: ...
- Processing recipes: ...

Uploading scan to Black Duck server ...
Scan file uploaded successfully
Black Duck project '[redacted]' created.

However when ran in the same docker container, but under Jenkins, the result I get is:
- Processing layers: ...
- Processing recipes: ...

Uploading scan to Black Duck server ...
ERROR: Unable to upload scan file

After adding debug output, it is clear that Black Duck server responds with HTTP code 500 for unknown reason. It is also apparent that this is not related to authorization or the server since:

No issues running locally
Synopsys Detect in the same container on the same Jenkins worker doesn't have this issue.

This is obviously an environmental issue related to the software and packages available with the docker container as against a full O/S installation.
Synopsys Detect uses unrelated technology so is not relevant here.
Please confirm:

The utility/script version you are using
That you are using the latest available version
The Python version available both outside and inside the container
How you are installing the utility (using pip or running the script standalone)
That you are correctly using Python virtual envs
The Python Requests package version within the virtual env after installation

Thanks

Yes, I understand that Detect is unrelated, just to point out the fact that it shouldn't have issues authenticating.

I'm using import_yocto_bm script version 2.7
I may not have been clear enough, but I ran script inside docker container in both cases, the difference being that whether this docker container is ran on my machine, or on Jenkins, so both use same packages.
I installed it standalone
I don't use virtualenv
Inside both docker containers requests 2.28.1 is installed.

There still isn't enough information to determine what's going on.
Clearly there is something different between the containers/environments as
otherwise the issue would not exist.
The script uses standard python packages so it is highly likely that there
is a comms error in 1 environment, potentially a proxy or certificate issue
which is not exposed by Synopsys Detect. Again I have no information on how
you are configuring Synopsys Detect so this doesn't help.
The utility is provided under OSS licensing without warranty or liability
(and not covered by standard support), so the right (only) approach here is
for you to debug what is going on in your environment. I suggest adding
some debug statements and running as a script.
For future comms on this, please email me at @.***
Please also confirm in the email which organisation you work for, and your
current Black Duck license information.
Thanks
On Tue, 12 Jul 2022 at 20:13, Daniel ひっかもりい @.***>
wrote:

Yes, I understand that Detect is unrelated, just to point out the fact
that it shouldn't have issues authenticating.

I'm using import_yocto_bm script version 2.7
I may not have been clear enough, but I ran script inside docker
container in both cases, the difference being that whether this docker
container is ran on my machine, or on Jenkins, so both use same packages.
I installed it standalone
I don't use virtualenv
Inside both docker containers requests 2.28.1 is installed.

—
Reply to this email directly, view it on GitHub
https://github.com/blackducksoftware/import_yocto_bm/issues/13#issuecomment-1182318338,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AED5THCHYBQ7KUXDXXSZW6LVTW7WBANCNFSM53L6CSMQ
.
You are receiving this because you commented.Message ID:
@.***>


Update to HDR::capture

https://github.com/zivid/cpp-extra-samples/blob/54bf513806f72f2e782cc620ccd4e85db96d50b3/source/Camera/Basic/CaptureHDR/CaptureHDR.cpp#L24
is not our recommended method.

Note! This is a copy of the SDK version. Modification should be made in the SDK first.

Can we close this @torbsorb? Not relevant in SDK 2.0 I think.


-M(M) does not find all included files

As noted in f3674d7f, the output of -MM currently only includes direct %INCLUDEs. ktransw does not try to recursively resolve includes of includes.
ktrans.exe does support multiple levels of %INCLUDEs, so this should be fixed.

Fixed in 5c03c241f5beb69ebf6ee2ed0b5d1b31c06a82ae.


v1.0.3 errors in trace - request headers missing

Hi @rathnapandi,
In Issue #7 you fixed the problem with services not showing up in dynatrace, but I am still seeing the errors in the api gateway trace.  This doesn't appear to be serious as I see the same data as on v1.0.1 in our production environment.
Every request shows errors like this in api gateway:
FATAL	4/17/23, 07:45:03.600	DynatraceModule :[75696d6e] can't set fieldname 'requestHeader': must be done before node is being started.
INFO	4/17/23, 07:45:03.600	                                Dynatrace :: outgoing x-dynatrace header FW4;-4620968c8991c29f777e55a794257110;7hcdd19af4f30a68b2
FATAL	4/17/23, 07:45:03.600	                                DynatraceModule :[84a097] can't set fieldname 'requestHeader': must be done before node is being started.
FATAL	4/17/23, 07:45:03.600	                                DynatraceModule :[84a097] can't set fieldname 'requestHeader': must be done before node is being started.
FATAL	4/17/23, 07:45:03.600	                                DynatraceModule :[84a097] can't set fieldname 'requestHeader': must be done before node is being started.
FATAL	4/17/23, 07:45:03.600	                                DynatraceModule :[84a097] can't set fieldname 'requestHeader': must be done before node is being started.
FATAL	4/17/23, 07:45:03.600	                                DynatraceModule :[84a097] can't set fieldname 'requestHeader': must be done before node is being started.
I noticed we only get the "Trace ID" and "Span ID" request headers in dynatrace (v1.0.1 and v1.0.3) so I wonder if this is related.
Thanks,
Jeremiah

Hi Jeremiah,
The error is coming from Dynatrace, the initial version wed did not implement Dynatrace loggingcallback (https://github.com/Dynatrace/OneAgent-SDK-for-Java#troubleshooting). it was added recently and it printes the above errores.
Can you check with Dynatrace support team? based on their feedback we can fix if needed.

Thanks @jschutte27, I will merge pull request.  Can you share some details on what is missing on request headers?

Hi @jschutte27,
I have updated the code under the branch https://github.com/Axway-API-Management-Plus/dynatrace-apim-oneagent/tree/issue10. could you please test it?

Hi @rathnapandi,
The headers are inconsistently coming into Dynatrace.  It feels like Dynatrace might be filtering them somewhere.  I see the Accept and Authorization header, but not Content-Type, Content-Length, Host, User-Agent, ect.  I have Authorization and KeyId redacted in Axway api gateway, but this seems to pick it up anyway.  I can mask the data in dynatrace, but it might be nicer to filter those header out in this module so they are not sent.
The headers are not a critical feature for us so I would be fine leaving it as is, but would like to filter out the sensitive ones.
I will try your updates shortly.  Did you see my note about the info trace messages?
Thanks,
Jeremiah

I tried the issue 10 branch and it reverted the change that removed the header errors so I get this in the trace:
DEBUG	4/27/23, 11:07:30.135	Dynatrace :: Starting around consumer
DEBUG	4/27/23, 11:07:30.135	Dynatrace :: Consumer Headers before proceed: {Host=[devwebapi.xxx.com], User-Agent=[Mozilla/5.0 (Windows NT; Windows NT 10.0; en-US) WindowsPowerShell/5.1.17763.3770], X-Forwarded-For=[xx]}
INFO	4/27/23, 11:07:30.135	DynatraceModule :[6dabb282] can't set fieldname 'requestHeader': must be done before node is being started.
INFO	4/27/23, 11:07:30.135	DynatraceModule :[6dabb282] can't set fieldname 'requestHeader': must be done before node is being started.
INFO	4/27/23, 11:07:30.135	DynatraceModule :[6dabb282] can't set fieldname 'requestHeader': must be done before node is being started.
The addOutgoingHeaders call has to be before outgoingWebRequestTracer.start(); based on thy dynatrace documentation.
https://github.com/Axway-API-Management-Plus/dynatrace-apim-oneagent/blob/75ff612954c8bf56336249990f9cde36d03e880f/src/main/java/com/axway/oneagent/utils/OneAgentSDKUtils.java#L65
That made the errors go away and it was adding some headers, but not all with it that way.  Now with the errors we are not seeing any headers come through to dynatrace.

Hi @jschutte27,
Thank you for validating, i have added a log message on info level to print app id and name.  Removed other log messages to avoid IO operations.
Also, adding all header additions before outgoingWebRequestTracer.start() method.   Please validate it once you test i will merge to main branch.

Thanks for the log entry.  Could you add a space some delimitor between the values?
INFO	4/27/23, 13:07:56.382	Dynatrace :: Application Id :6617bb2d-3580-xxxx-b98c-e60bb7ee6af7Application Name :testapp-dev
I am getting this error now:
DEBUG	4/27/23, 13:18:12.354	Dynatrace :: Starting around consumer
DEBUG	4/27/23, 13:18:12.354	Dynatrace :: Consumer Headers before proceed: {redacted}
INFO	4/27/23, 13:07:56.382	Dynatrace :: Application Id :6617bb2d-3580-xxxx-b98c-e60bb7ee6af7Application Name :testapp-dev
ERROR	4/27/23, 13:07:56.382	DynatraceModule :custom request attribute failed: not on path
ERROR	4/27/23, 13:07:56.382	DynatraceModule :custom request attribute failed: not on path
ERROR	4/27/23, 13:07:56.382	DynatraceModule :custom request attribute failed: not on path
ERROR	4/27/23, 13:07:56.382	DynatraceModule :custom request attribute failed: not on path
I'm guessing it is because addRequestAttributes(appName, orgName, appId, null); is before outgoingWebRequestTracer.start();.  I'll test that out and see what happens.
I do see all the headers in dynatrace now though:
Accept	[application/json]
Cdn-Loop	[cloudflare; subreqs=1]
Cf-Connecting-Ip	[xx.1xx.120.70]
Cf-Ew-Via	[15]
Cf-Ipcountry	[US]
Cf-Origin-Https	[on]
Cf-Ray	[7be90ef3c4eeeae9-DFW]
Cf-Visitor	[{"scheme":"https"}]
They are all in arrays which isn't serious, but would look nicer if it was a simple string.
Would it make sense to add a list of header names to exclude that is configurable in the jvm.xml file?

Thanks @jschutte27 ,
Added space and delimiter for logs and moved addRequestAttributes after start(), can you review the code base and confirm?

I will add the feature to exclude http headers.

I have this new version running and so far it seems good.  Would it work to try convert the header values to string so they don't have the brackets in dynatrace?

Done.

The headers look good.  Thanks!
I noticed that the x-dynatrace header on outgoing requests was empty and that the outgoingTag was empty.  This was causing the backend request not to be linked to the axway request in dynatrace.  I reordered the requests and it looks like this works correctly:
try {
            addOutgoingHeaders(outgoingWebRequestTracer, headers);
            outgoingWebRequestTracer.start();
            String outgoingTag = outgoingWebRequestTracer.getDynatraceStringTag();
            Trace.debug("Dynatrace :: outgoing x-dynatrace header " + outgoingTag);
            if (headers != null) {
                headers.setHeader(OneAgentSDK.DYNATRACE_HTTP_HEADERNAME, outgoingTag);
            }
            addRequestAttributes(appName, orgName, appId, null);
            Trace.debug("Dynatrace :: Get Message Attributes");
            getAttributes(message);
            pjp.proceed();
}

Done, can you please do the final validation?

I believe this looks good.  Thanks a lot!

@jschutte27
Merged the changes to master


Expect error for invalid factory parameter

Version: 0.65.0
type Reducer<S, A> = (S, A) => S;
const makeReducer = <S, A>(is: S, r: Reducer<S, A>): Reducer<S, A> =>
  (s, a) => (s === undefined ? is : r(s, a));

// $ExpectError: because r() suppose to return string
const reducer = makePlainReducer('', () => {});

So i expect error here, because parameter r i'm passing to factory should return state (according to Reducer type).
Unfortunately, cannot repro as try service seems to be down

Event the simpler example:
/* @flow */

type Reducer<S, A> = (S, A) => S;
declare function makeReducer<S>(initialState: S): Reducer<S, *>;

const reducer = makeReducer('');

// $ExpectError: but NO error
reducer(1);

It's now complaining that A is underconstrained, which is expected.


fix: add boolean types to set() and state

it's better to add strict type to set() to avoiding confusion for who uses it.
It will be weird if the set value filled with string or anything and Boolean() it out, its better outside of the hooks.

Agreed, initially I thought it would be neat if you can pass any boolean-ish values. LGTM.


New version: Hyperopt v0.4.2

Registering package: Hyperopt
Repository: https://github.com/baggepinnen/Hyperopt.jl
Created by: @baggepinnen
Version: v0.4.2
Commit: 0a4adb98f0ac5f6274c9018d8b925b02d9916560
Reviewed by: @baggepinnen
Reference: https://github.com/baggepinnen/Hyperopt.jl/issues/2#issuecomment-782882255

I think IRTools is in the stack of Hyperopt, this is the only package failing because of that.


Adding solc-verify

Solc-verify is a new modular verifier built on top of the solidity compiler:

paper: https://arxiv.org/abs/1907.04262
description: https://github.com/SRI-CSL/solidity/blob/boogie/SOLC-VERIFY-README.md

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


Error when uploading video: Cannot read properties of undefined (reading 'dataset')

Maybe related to post from #213 but the error log is different. Happens in v2.0.11 only.
*EDIT: happens in v2.0.10 as well.

Similar error I just started getting:

Since Sanity migrated to @sanity/client v5 this started. The migration happened at v3.4.0 so if you rollback Sanity to v3.3.1 you should be able to use sanity-plugin-mux-input normally.

Issue fixed with latest release v.2.0.15


Support more than 2 levels in aggregation find function

What is this issue about?
If it's about AggregationValue::find(), then it's in ESB bundle and it's already working with multiple levels.


haskell.compiler.ghcHEAD: 9.7.20221224 -> 9.7.20230217

Description of changes

[ ] test js backend
[ ] test cross build on linux
[ ] test cross build on darwin
[ ] test normal build
[ ] (test static build)
[ ] changelog entry for js rename

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

@ofborg pkgsCross.gnu32.buildPackages.haskell.compiler.ghcHEAD

@ofborg build pkgsCross.gnu32.buildPackages.haskell.compiler.ghcHEAD

cc @alyssais, @amjoseph-nixpkgs, @Ericson2314 for lib/platform changes.

As an update:

Building a cross-compiler with hadrian should now work on darwin, as upstream fixed their ar bug.
JS backend is less broken now that we disable shared libs correctly, however building libraries still doesn't work as llvm-ranlib crashes: https://github.com/llvm/llvm-project/issues/60949. I brought this up in #ghc, but not sure how aware upstream is of this problem.
pkgsStatic.buildPackages.haskell.compiler.ghcHEAD gets further now, but eventually explodes when hadrian tries to build a debug+shared version of the RTS libHS – to be debugged, but this is not a regression. Not using fully_static definitely turns out to be the right call, since that also tries to statically link the GHC executable which doesn't work in pkgsStatic.buildPackages.

The JS problem is known and not actionable and there's an issue for pkgsStatic – I'll figure it out eventually. For now we can merge this update given that we are okay with renaming js-unknown-ghcjs to javascript-unknown-ghcjs.

Fixed the lib tests!


BC Intorduced in one of last commits

After last refactors it has been introduced a break compatibility with symfony/config < 5.x .
I've updated travis file to lock sf version dependencies, with symfony-flex, to be compliant together in a test running.
This PR is only a Failure test. We could discuss about a solution.

Something's wrong with this PR: Travis build is failing :/

@DamienHarper I've update travis to raise an error.
You have declared RoutingAnnotationLoader that it is compliant with symfony/config:5.x but not previous.

To complete the scope of this PR, it's introduce an update on travis file to test all versions of Symfony using SYMFONY_REQUIRE to be sure to load all 3.x versions or all 4.x versions of Symfony packages.

Hi @DamienHarper have you done a look to my PR?

Hi @giovannialbero1992 ! I had a quick look at your PR. Tests still seem to fail.
I'm currently working quite hard to rewrite the bundle to support more features, sorry for the delay.

@DamienHarper the failure test is a desired behaviour.
I've locked symfony packages version to avoid cases where a symfony package is at version 5.x and another 4.x etc.

@giovannialbero1992 I don't think this PR is still relevant so I close it now. Feel free to re-submit a new PR if needed.


Add automatic management of Network Activity Indicator on iOS.

Fixes #74
Depends on #82
Just subscribe it to the network indicator.

Other than that the overall solution looks good. I'm not super keen on just using NSNotificationCenter all over the place, especially because it makes things harder to test/mock. Thoughts on having a Parse-specific NSNotificationCenter instance, that we can inject? Maybe its overkill.