Unable to upgrade k6

Brief description of your issue
winget lists an available upgrade for k6 but then doesn't let me actually install it.  Instead, it just keeps complaining that the upgrade is available.
Steps to reproduce
winget upgrade lists the following:
Name Id    Version Available Source
-----------------------------------
k6   k6.k6 0.50.0  0.51.0    winget
1 upgrades available.

Then attempting winget upgrade k6.k6 gives this:
No applicable upgrade found.
A newer package version is available in a configured source, but it does not apply to your system or requirements.

Expected behavior
If an upgrade is listed as available, it should be installable.
Actual behavior
The upgrade is listed as available but then refuses to install.
Environment
Windows Package Manager v1.7.11261
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.4529
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.11261.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Big question:  If the available package does not "apply to [my] system or requirements" then why is winget upgrade listing it as an available upgrade and trying to install it.  Even doing winget upgrade --all throws the same error.

2024-06-21 09:50:07.076 [CLI ] Installer [X64,wix,User,en-US] not applicable: Installer scope does not match currently installed scope: User != Machine
2024-06-21 09:50:07.085 [CLI ] Terminating context: 0x8a15002b at C:\__w\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:bc

Looks like maybe k6 published the installer only in the "user" scope and I have this installed in "machine" scope?  If that's true, then why isn't winget upgrade filtering this out properly?  If the scopes don't match, it shouldn't be returned as needing an update.

Hey, same problem happened with NeoVim
My main problem with that was that I had to dig through the logs to get the problem instead of winget stdout
(same happened with WinRAR but the problem there was Locale)
not printing it in the cli make no sense

when trying to run K6 manually I was able to find out that I'm already upgraded to latest edition for my current operation system (Windows 10). May be K6 has its latest versionf or Windows 11 only.
I got following output when trying to run


[Zlib] Building zlib error [BUILD_FAILED]

OS : Mac
I'm trying to install vcpkg but with no luck.
it turned out that I can not install zilb successfully .
here is my failure log but I can not understand the error at all.
-- Installing: /Users/harryz/cs106L/cs106L-assignment1/vcpkg/packages/zlib_arm64-osx/share/zlib/vcpkg-cmake-wrapper.cmake
-- Fixing pkgconfig file: /Users/harryz/cs106L/cs106L-assignment1/vcpkg/packages/zlib_arm64-osx/lib/pkgconfig/zlib.pc
CMake Error at scripts/cmake/vcpkg_fixup_pkgconfig.cmake:135 (message):
  /path/to/pkg-config --exists zlib failed with error code: No such file or
  directory

      ENV{PKG_CONFIG_PATH}: "/Users/harryz/cs106L/cs106L-assignment1/vcpkg/packages/zlib_arm64-osx/lib/pkgconfig:/Users/harryz/cs106L/cs106L-assignment1/vcpkg/packages/zlib_arm64-osx/share/pkgconfig:/Users/harryz/cs106L/cs106L-assignment1/vcpkg/installed/arm64-osx/lib/pkgconfig:/Users/harryz/cs106L/cs106L-assignment1/vcpkg/installed/arm64-osx/share/pkgconfig"
      output:
Call Stack (most recent call first):
  scripts/cmake/vcpkg_fixup_pkgconfig.cmake:200 (z_vcpkg_fixup_pkgconfig_check_files)
  ports/zlib/portfile.cmake:43 (vcpkg_fixup_pkgconfig)
  scripts/ports.cmake:147 (include)

error: building zlib:arm64-osx failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+zlib
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[zlib]+Build+error
Include '[zlib] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
    vcpkg-tool version: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
    vcpkg-scripts version: 4efb7ed62 2023-01-25 (10 hours ago)

Please use the prefilled template from /Users/harryz/cs106L/cs106L-assignment1/vcpkg/installed/vcpkg/issue_body.md when reporting your issue.

It will be really appreciated if anyone can help me with the problem.

Having the same issue ... tried anything I could find on SO and gitHub. Any help would be greatly appreciated ... following is the issue md:
Package: zlib[core]:arm64-osx -> 1.2.13
Host Environment

Host: arm64-osx
Compiler: AppleClang <IP_ADDRESS>00029
vcpkg-tool version: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
vcpkg-scripts version: 36fb23307 2023-02-10 (24 hours ago)

To Reproduce
vcpkg install zlib
Failure logs
-- Using cached madler-zlib-v1.2.13.tar.gz.
-- Extracting source /Users/keithmglassford/Development/vcpkg/downloads/madler-zlib-v1.2.13.tar.gz
-- Applying patch 0001-Prevent-invalid-inclusions-when-HAVE_-is-set-to-0.patch
-- Applying patch 0002-skip-building-examples.patch
-- Applying patch 0003-build-static-or-shared-not-both.patch
-- Applying patch 0004-android-and-mingw-fixes.patch
-- Using source at /Users/keithmglassford/Development/vcpkg/buildtrees/zlib/src/v1.2.13-f30d2a168d.clean
-- Configuring arm64-osx
-- Building arm64-osx-dbg
-- Building arm64-osx-rel
-- Installing: /Users/keithmglassford/Development/vcpkg/packages/zlib_arm64-osx/share/zlib/vcpkg-cmake-wrapper.cmake
-- Fixing pkgconfig file: /Users/keithmglassford/Development/vcpkg/packages/zlib_arm64-osx/lib/pkgconfig/zlib.pc
CMake Error at scripts/cmake/vcpkg_find_acquire_program.cmake:617 (message):
  Could not find pkg-config.  Please install it via your package manager:

      brew install pkg-config
Call Stack (most recent call first):
  scripts/cmake/vcpkg_fixup_pkgconfig.cmake:197 (vcpkg_find_acquire_program)
  ports/zlib/portfile.cmake:43 (vcpkg_fixup_pkgconfig)
  scripts/ports.cmake:147 (include)

Additional context

您好，您发送的邮件我已收到，谢谢！    I have received your e-mail,thank you!                                                                  ——Harry张

brew install pkg-config

install pkg-config,then it can work

Having same issue but with openal-soft_arm64-osx on my new M2 MBP. Trying to install SFML with Vcpkg manifest file, but I get the same error, even after installing pkg-config with brew.

Ok, figured it out ... I had already installed pkg-config using brew as the directions said, but still got the same problem. This led me to think that it was a path issue. Given that for the new M1 MacBook, brew moved the install location and so this could be the issue as I had migrated my disk from an Intel based system and the path could be pointing to the wrong version. I poked around the zlib install scripts and found that it can take an environment variable for pkg-config.
In addition, using a locate pkg-config revealed that there were multiple versions across the system from various installs and so I chose to first update the env to verify:
$ export PKG_CONFIG=/opt/homebrew/Cellar/pkg-config/...
where ... is my local version and remainder of the path to the bin, and then ran the install:
$ vcpkg install zlib
and it compiled successfully. As such, it appears that either zlib hasn't been updated to look in the new homebrew location or my path was all messed up and the install was looking in the wrong place. Either way, I cleaned up my path, rebooted for fun, and all works now as before.
Hope this helps someone else with the same issue ...

@keithglassford  Hey I believe I have the same issue as you, and was wondering how you were able to fix your path so it worked properly.

@pateruu I just added the following line to my ~/.bash_profile
export PKG_CONFIG=/opt/homebrew/Cellar/pkg-config/0.29.2_3/bin/pkg-config
where you can find you actual version and associated path to put in the above using:
$ locate pkg-config
and then finding the correct version; just remember to either open a new shell or do a
$ source ~/.bash_profile
As for the path, just examine your current path using:
$ echo $PATH
to see if there is any changes that you need to do in terms of ordering in you ~/.bashrc or ~/.bash_profile if you are setting any $PATH variables there.
... also, this depends up on you shell and environment as I am working on a Mac with the old bash shell.

I am getting the same error when trying to build for windows, anyone know a fix for it?
Package is: zlib:x64-windows


merchant listing request

hi
we want to be listed as merchant
https://monovm.com
regards

Bounty Low shared by issues #218 #217 #216 #215 #152

navcoin/navcoin-org,
Your email to our support system could not be accepted because it was not recognized as coming from an email address belonging to one of our customers. If you need assistance, please email from the address you registered with us that you use to login to our client area.

Claimed.


Add support for custom sql queries in v3 Great Expectations API

Problem
The old support for Great Expectations' custom sql datasource wasn't applied to the support for the V3 checkpoints API. This fixes support for custom SQL statements and adds an extra unit test to verify.

Note: All schema changes require discussion. Please link the issue for context.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
Checklist

[X] You've signed-off your work
[X] Your pull request title follows our guidelines
[X] Your changes are accompanied by tests (if relevant)
[X] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

Codecov Report

Merging #1025 (97b4787) into main (dcf34ea) will increase coverage by 0.63%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #1025      +/-   ##
============================================
+ Coverage     84.64%   85.28%   +0.63%
============================================
  Files            79       57      -22
  Lines          3563     3160     -403
  Branches         22        0      -22
============================================
- Hits           3016     2695     -321
+ Misses          517      465      -52
+ Partials         30        0      -30

Impacted Files
Coverage Δ

...neage/common/provider/great_expectations/action.py
83.43% <100.00%> (+0.82%)
:arrow_up:

...neage/common/provider/great_expectations/facets.py
100.00% <100.00%> (ø)

.../openlineage/client/DefaultConfigPathProvider.java

...a/io/openlineage/client/transports/HttpConfig.java

integration/dagster/openlineage/dagster/cursor.py

.../java/io/openlineage/client/OpenLineageClient.java

...o/openlineage/client/transports/ConsoleConfig.java

...o/openlineage/client/transports/HttpTransport.java

...a/src/main/java/io/openlineage/client/Clients.java

...lineage/client/transports/ApiKeyTokenProvider.java

... and 14 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Maintaining Consistent Numbering for Improved Readability

What changed? Why?
**Incorrect numbering can confuse the reader, especially in lengthy or complex documents. Consistent numbering makes it easier to locate the desired sections quickly.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

@brendan-defi I reviewed all MD files and fixed critical numbering issues to prevent reader confusion. The docs will soon be flawless, and everything is almost ready. Thanks!

@sky-coderay thanks for catching this. i've approved and initiated CI. will merge later today

@sky-coderay merged the change in, thank you again for your contribution!


Fix printing IllegalStateException

Task/Issue URL: https://app.asana.com/0/1200204095367872/1207700638247735/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4704  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joshliebe and the rest of your teammates on  Graphite


Update README.md

Added PR Welcome badge, License badge and Table of contents

thanks for this PR but at the moment the main README is rather short, I don't think it needs a table of contents since everything mostly fits on a single screen; perhaps later if it gets to be longer than a screen we can add this.


About the dataloader

line
if img.size == gt.size

This condition filters out Pseudo labels. No pseudo labels can be read when generating pseudo labels or training with pseudo labels. Do I need to remove this condition?

The shape of pseduo label is same as the shape of image. So the dataloader would not filter out the pseudo labels.

Thank you for your reply. Does this mean that I need to further process the pseudo label dataset myself?Similar to this issue

You need to resize them but not to crop them.

got it，thanks！


Allow using settings.json for launch configs broken in version 1.9.0-beta8

You can provide launch configurations in your settings.json file by wrapping in launch key. This works fine in 1.9.0-beta7 but was broken in 8. An example configuration is below.
"launch": {
        "configurations": [
            {
                "type": "brightscript",
                "request": "launch",
                "name": "BrightScript Debug: Launch 4K",
                "host": "<IP>",
                "password": "<PASS>",
                "files":[
                    "manifest",
                    "source/**/*.*",
                    "components/**/*.*",
                    "fonts/**/*.*",
                    "images/**/*.*",
                    "config.json"
                ],
                "rootDir" : "${workspaceFolder}"
            }
        ]
    }

I found the issue. When you run a launch configuration from user settings, vscode doesn't know which workspace you are launching it for, so the folder variable is undefined. That causes this line to fail.
This is fixed, so it should land in the next beta release.

With this specific scenario, I had to code a few different ways to try and get at the workspace folder path.

Use folder param if provided (should be present anytime a launch.json debug is started)
If there's only one workspace loaded in vscode, use that workspace (should catch almost everything else)
If there are more than one workspaces open, prompt the user to specify which workspace they wish to use.

If the user gets to number 3 and is annoyed, their only recourse is to create a launch.json, but I think that's a fair tradeoff.

This was fixed in languageserver-beta10


implement ellery's suggestions about using time-based constructs for loadgen, etc.

Acceptance criteria:

[ ] Get rid of printStatsEveryNRequests and replace it with a Duration; we then print the stats every n seconds rather than after a certain number of requests.
[ ] Get rid of totalNumberOfOperationsToExecute and replace it with a Duration; we then run the benchmark for (approximately) that Duration rather than stopping after a certain request count.

These are very desirable UX improvements because with the current setup, if the user changes maxRequestsPerSecond or numberOfConcurrentRequests, it will have a big impact on how often (in wall clock time) the stats are printed, as well as how long the program will run for.  That's not intuitive for users.

@cprice404 @eaddingtonwhite  What were the suggestions?

@schwern sorry, I will update the description of this ticket now (but it was basically what I already captured in your other ticket).

@schwern updated description, hopefully it's useful now :)

I also made sure the stats print when the run finishes, just in case totalMs is not a multiple of printStatsEveryNMs.


Port "Time Parameterization" tutorial

Port tutorial to ROS2.

This is more of a concept, should move to concepts:
https://moveit.picknik.ai/main/doc/examples/time_parameterization/time_parameterization_tutorial.html


Rename ToString to ToDatalog for IR objects that become Datlog facts.

This leaves structures below the level of a Datalog fact (such as
AccessPathSelectors) as ToString for now.

This is relevant to (and, depending upon what reviewers think, may completely fix) #105 .


MSP -  30 New Science Packs

Have you checked whether this mod or set of mods has already been requested?
Check here
If you find the mod you're looking for, add a "thumbs-up" reaction or a comment to the issue.
What mod set are you requesting?
E.G. "Bobs and Angels", "Pyanodons", "Seablock", etc.
**Is this mod set compatible with the latest version of Factorio?"
Yes or no. If no, please list the last version that it is compatible with.
What mods are included in this mod set?
E.G. list all the distinct mods that should be included from the mod portal.

So to clarify, the calculator already supports "MoreScience" by lovely_santa. "MSP - 30 new Science Packs" is, according to its author, just the same mod "I just increased the factorio version and added a fix mod".
Do you still think it's necessary to add support for this one? It seems far less popular (1711 downloads vs 21728 for "More Science")

Closing this issue - feel free to comment later if you would still like this to be added.


some artwork providers fail on mobile

some providers throw a Failed to fetch or enqueue images: Could not find required element, but it only seems to happen on mobile. known providers are Bandcamp and YouTube. I've also tested Spotify and Apple Music, but those two worked
Firefox Android with Tampermonkey

Related: #655


User option for selecting worker cores range for device post processing

Option for choosing worker cores to be considered in postproc for device profiling data.
One example would be python -m tracy -r --worker-cores [(1,1)] -m pytest (test)
As per @acejkov's suggestion, this can also be used to ignore core misalignments for example caused by soft resets.

#7116 needs to be done to do this cleanly


Wrong instance returned by RecurrenceSetIterator

While iterating through instances using RecurrenceSetIterator, if start time provided is not a valid instance, then start time is also returned as one of  the instance. Is this expected ? If Yes, can some way be suggested to find only valid dates ?
Example code :
  public static void main(String[] args) throws InvalidRecurrenceRuleException {
    ZonedDateTime startTime = ZonedDateTime.parse("2022-04-27T00:38:20Z", DateTimeFormatter.ISO_OFFSET_DATE_TIME);
    String rrule = "FREQ=WEEKLY;INTERVAL=1;BYDAY=TH";
    String timezone = "UTC";
    ZoneId zoneId = ZoneId.of(timezone);
    RecurrenceSet recurrenceSet = new RecurrenceSet();
    RecurrenceRule recurrenceRule = new RecurrenceRule(rrule);
    recurrenceSet.addInstances(new RecurrenceRuleAdapter(recurrenceRule));
    RecurrenceSetIterator it = recurrenceSet.iterator(TimeZone.getTimeZone(timezone), startTime.toInstant().toEpochMilli());
    for (int itr = 0; itr < 10; ++itr) {
      ZonedDateTime instant = Instant.ofEpochMilli(it.next()).atZone(zoneId);
      System.out.println("Instant " + itr + ", date: " + instant + ", day: " + instant.getDayOfWeek());
    }
  }

Outputs :
Instant 0, date: 2022-04-27T00:38:20Z[UTC], day: WEDNESDAY
Instant 1, date: 2022-04-28T00:38:20Z[UTC], day: THURSDAY
Instant 2, date: 2022-05-05T00:38:20Z[UTC], day: THURSDAY
Instant 3, date: 2022-05-12T00:38:20Z[UTC], day: THURSDAY
Instant 4, date: 2022-05-19T00:38:20Z[UTC], day: THURSDAY
Instant 5, date: 2022-05-26T00:38:20Z[UTC], day: THURSDAY
Instant 6, date: 2022-06-02T00:38:20Z[UTC], day: THURSDAY
Instant 7, date: 2022-06-09T00:38:20Z[UTC], day: THURSDAY
Instant 8, date: 2022-06-16T00:38:20Z[UTC], day: THURSDAY
Instant 9, date: 2022-06-23T00:38:20Z[UTC], day: THURSDAY

But wednesday is not a valid instance.
When i expand instances by adding same input on : https://recurrence-expansion-service.appspot.com/ , then instances provided are correct, can you please suggest the correct way used in website above ?

While iterating through instances using RecurrenceSetIterator, if start time provided is not a valid instance, then start time is also returned as one of the instance. Is this expected ? If Yes, can some way be suggested to find only valid dates ? Example code :
  public static void main(String[] args) throws InvalidRecurrenceRuleException {
    ZonedDateTime startTime = ZonedDateTime.parse("2022-04-27T00:38:20Z", DateTimeFormatter.ISO_OFFSET_DATE_TIME);
    String rrule = "FREQ=WEEKLY;INTERVAL=1;BYDAY=TH";
    String timezone = "UTC";
    ZoneId zoneId = ZoneId.of(timezone);
    RecurrenceSet recurrenceSet = new RecurrenceSet();
    RecurrenceRule recurrenceRule = new RecurrenceRule(rrule);
    recurrenceSet.addInstances(new RecurrenceRuleAdapter(recurrenceRule));
    RecurrenceSetIterator it = recurrenceSet.iterator(TimeZone.getTimeZone(timezone), startTime.toInstant().toEpochMilli());
    for (int itr = 0; itr < 10; ++itr) {
      ZonedDateTime instant = Instant.ofEpochMilli(it.next()).atZone(zoneId);
      System.out.println("Instant " + itr + ", date: " + instant + ", day: " + instant.getDayOfWeek());
    }
  }

Outputs :
Instant 0, date: 2022-04-27T00:38:20Z[UTC], day: WEDNESDAY
Instant 1, date: 2022-04-28T00:38:20Z[UTC], day: THURSDAY
Instant 2, date: 2022-05-05T00:38:20Z[UTC], day: THURSDAY
Instant 3, date: 2022-05-12T00:38:20Z[UTC], day: THURSDAY
Instant 4, date: 2022-05-19T00:38:20Z[UTC], day: THURSDAY
Instant 5, date: 2022-05-26T00:38:20Z[UTC], day: THURSDAY
Instant 6, date: 2022-06-02T00:38:20Z[UTC], day: THURSDAY
Instant 7, date: 2022-06-09T00:38:20Z[UTC], day: THURSDAY
Instant 8, date: 2022-06-16T00:38:20Z[UTC], day: THURSDAY
Instant 9, date: 2022-06-23T00:38:20Z[UTC], day: THURSDAY

But wednesday is not a valid instance.
When i expand instances by adding same input on : https://recurrence-expansion-service.appspot.com/ , then instances provided are correct, can you please suggest the correct way used in website above ?

Have you solved the problem? I have the same question

@401error no

This is a duplicate of #35.

I have rewritten the recurrence set iterator code. Now you can chose to iterate or omit the first instance if it's not synchronized with the rule. Hope this works for everyone.
Please check out README.md for guidance and let me know if you have any questions.


helm: add Orchestrator 3.0 using raft

Since this is my first time using Orchestrator, I'm going to document my workflow here to try and make a review easier.
After running a diff from the original helm config for orchestrator against the valid config entries, here are items that are no longer configurable.
"ActiveNodeExpireSeconds": 12
"AgentAutoDiscover": false
"AuditPageSize": 20
"AuditPurgeDays": 365
"BufferBinlogEvents": true
"DatabaselessMode__experimental": false
"DiscoveryPollSeconds": 5
"HttpTimeoutSeconds": 60
"MaintenanceExpireMinutes": 10
"MaintenanceOwner": "orchestrator"
"MaintenancePurgeDays": 365
"MySQLTopologyMaxPoolConnections": 3
"ReadLongRunningQueries": true
"RecoveryPollSeconds": 10
"SlaveStartPostWaitMilliseconds": 1000
"StatusSimpleHealth": true

LGTM


Don't forget to clenaup tmpdir in TestFileSpecPlugin()

Also remove redundant code.
Signed-off-by: Zefan Li<EMAIL_ADDRESS>

@lizf-os  janky is showing a real error

@duglin  Now Fixed. Thanks for reviewing the changes!

LGTM
ping @calavera

LGTM


Unsure of which service messages to use to move joints and gripper using rospy

We would like to service messages to move the joints and gripper of the OM using rospy under this new package. In the older package version (i.e. open_manipulator_with_tb3), we manage to do this with '/arm/moveit/set_joint_position' and '/om_with_tb3/gripper'. However, for this newer package, we are clueless which service messages to use to perform these tasks. we have check out the available service messages while running the Gazebo and the move_group nodes, and we cannot find anything that is relevant to move the joints and gripper of the OM under the move_group section (below).

Please kindly assist and guide us in this matter. Thank you and much appreciate your time.
On a side note, the RViz and GUI functions are working well for us; just unsure which service messages to use to move the arm under this new package. And we think the command given in your website to run the Gazebo for TB3 with OM is not updated; it should be:
$ roslaunch turtlebot3_manipulation_gazebo turtlebot3_manipulation_gazebo.launch
instead of
$ roslaunch turtlebot3_manipulation_gazebo turtlebot3_manipulation.launch
This launch file also has some minor syntax error that you might want to rectify as of the time we updated and installed this package (i.e. a few days ago).

@nicholashojunhui
Thank you for reporting the wrong command in the eManual.
The recent changes in turtlebot3_manipulation package, moveit planning interface is adopted for more general purpose.
Unlike the previous code where we used messages, you should inherit moveit interface classes.
Please refer to below section where gripper control is implemented in the GUI program.
https://github.com/ROBOTIS-GIT/turtlebot3_manipulation/blob/master/turtlebot3_manipulation_gui/src/qnode.cpp#L200

@ROBOTIS-Will
Thank you for your response. Noted, I will try it. Much appreciated your time

@ROBOTIS-Will
I have tried the method that you have mentioned on Gazebo as well on the Physical TB3_with_OM, and it works well. Took reference from this website: http://docs.ros.org/kinetic/api/moveit_tutorials/html/doc/move_group_python_interface/move_group_python_interface_tutorial.html
Thank you and much appreciated your time in this matter.


"DOLHASCA" is listed in the drop-down menu

Description:
"DOLHASCA" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "DOLHASCA" in the search bar.

Expected results
The location is listed in the drop-down menu as "Oraș DOLHASCA , SUCEAVA (DOLHASCA)".


zhmccli: fix no_verify for nested context

If is_flag is set to True Click defaults to False. Therefore the check
if no_verify is None:
no_verify = ctx.obj.no_verify
will always fail. Fix this by setting the default to None for the click option
and apply the actual default later.
Signed-off-by: Marc Hartmayer<EMAIL_ADDRESS>

I'm not an expert regarding Click... So please take a closer look.


Crud api

This forms the basic skeleton for any CRUD based API

Task linked with #82 issue

can i work on this issue


[FLINK-5625] [kinesis] Let Date format for timestamp-based start position in Kinesis consumer be configurable

The patch let user define their own pattern for parsing date string.
If ConsumerConfigConstants.STREAM_TIMESTAMP_DATE_FORMAT is specified then FlinkKinesisConsumer will only use this format to parse date string.

[v] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[v] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[v] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

Typo on the task id. > <
Close and open another one to make ASF GitHub Bot can track this PR correctly.

Make a mistake again because I am not familiar with JIRA. Sorry for that. orz


[BUG]: how used ffmpegoptions : with gui

Program version
v4.6.3
Operating System
Windows
Type
GUI
Service
All
Command used
ffmpegoptions :
Show ID
GYZJ43JMR
Episode
1, 2, .....
Console Output
'[DEBUG] Got download options: {"id":"GRE50KV36","q":0,"e":"1","dubLang":["jpn"],"dlsubs":["fr"],"fileName":"[${service}] ${showTitle} - S${season}E${episode} [${height}p]","dlVideoOnce":false,"all":false,"but":false,"noaudio":false,"novids":false,"simul":false,"ids":["G69P9MD9Y"],"title":"Asta and Yuno","parent":{"title":"Black Clover","season":"1"},"image":"https://www.crunchyroll.com/imgsrv/display/thumbnail/1200x675/catalog/crunchyroll/8a285ca29aadb33852da5f78d661afc9.jpe","episode":"1"}'
i tried to transcoding but is not recognized

'ffmpegOptions: "-c:v hevc_amf -preset fast -b:v 3000k -c:a copy -bsf:a aac_adtstoasc" '

some one help me :D

Additional Information
No response

manualy it's working to transcod by cmd bash
ffmpeg.exe -i "I Was Reincarnated as the 7th Prince so I Can Take My Time Perfecting My Magical Ability - S01E01 - I Reincarnated as the Seventh Prince].mkv"-c:v hevc_nvenc -preset fast -b:v 3000k -c:a copy -bsf:a aac_adtstoasc  test.mkv
how to integrate this command whith gui ?

You are using the option wrong,
use it like this:
ffmpegOptions: ["-c:v hevc_amf", "-preset fast", "-b:v 3000k", "-c:a copy", "-bsf:a aac_adtstoasc"]
forceMuxer: "ffmpeg"

It's working
Can you add this option inside gui ?


buildFHSEnv: rewrite env building

This replaces the mess of buildEnvs with a single Rust binary that spits out a mostly-complete root filesystem for an fhsenv.
The main goal is to have includeClosures, as we want all of the dependencies to be in the fhsenv to avoid Steam's (and others') LD_LIBRARY_PATH shenanigans, but without 32-bit libraries leaking into lib64 when a 64-bit package like mangohud depends on a 32-bit version of itself.
We "fix" this by actually looking at the files and explicitly moving 32-bit stuff to $out/lib32. This could be avoided if we had recursive Nix, or at least system info in exportReferencesGraph, but alas.
For some reason this also shrinks the fhsenvs massively, even though there's currently no layout optimization (e.g. a package with paths like lib/foo/{bar,baz} will produce two symlinks in the output, even when it's more optimal to symlink lib/foo to $out/lib/foo directly).

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I assume the best way to test this is to point my nixpkgs at this branch?

That would be the easiest.

How do I test this?

Ideally you'd rebuild your entire system against this branch.

Ideally you'd rebuild your entire system against this branch.

Tested by cherry-picking this commit into nixos-unstable, several games work again. gamemoderun can also be correctly found from systemPackages.
🎉 This does fix #341219 (comment) for me.

uhh how can i cherry pick this? sorry searching shows a few pages but they show how to apply patches or use overlays for specific packages :sob:

seems to work for me

Does that mean the game that is currently broken for you works on this branch?

Yes, Factorio is up and running. Testing other linux native games (CS2 and TF2), they also seem to work. I tried rolling back to nixos-unstable and they don't work there still, so yeah.

Just tested on my Plasma 6 nvidia system, and native games behave properly again.  (Tested Valheim, RimWorld, and Project Zomboid.)  It is also possible to use nested gamescope (by changing the Steam game command to something like gamescope -e -W 2560 -H 1440 -f --mangoapp -- %command% with this branch, while it crashes on nixos-unstable).


fix None mimetype

Overview
This PR fixes issue #619.
Changes:

Updated app/Process.py to cope with None mimetype.
Added test test_assync_inout to validate this patch.

Related Issue / Discussion
#619
Additional Information
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[ ] I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
[x ] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

Coverage remained the same at 0.0% when pulling 962e880c496ec03e84f1a089c27b43a738c3cd19 on cehbrecht:fix-619-mimetype into 20147561c6985525c26b31ee9eac86192487b07e on geopython:main.


fix(fluent bit): make input plugin read from head of file

Description: This change updates the Fluent Bit input plugin to make it read from the head of the log file rather than the tail. Reading from the tail was causing the first few logs to be missed.

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [x]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
no, no

Codecov Report

Merging #2158 (795fe04) into main (224ef8f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2158   +/-   ##
=======================================
  Coverage   57.89%   57.89%
=======================================
  Files         145      145
  Lines        6030     6030
=======================================
  Hits         3491     3491
  Misses       2536     2536
  Partials        3        3

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 224ef8f...795fe04. Read the comment docs.

lgtm

Would be great to catch this scenario in an e2e test as a follow up.

@michelleN agreed, I've been trying to figure out how to test this but haven't been able to find an efficient way yet. Opened this issue to track it #2159


[BUG] From 1.24.0 the exception RevisionIdWasChanged is raised differently from 1.23.6

Hi, this fix is broken a testcase that dont brake in 1.23.6. From this PR, an exception
"        except DuplicateKeyError:

      raise RevisionIdWasChanged

E           beanie.exceptions.RevisionIdWasChanged"
is raised on my POST route in .save() method
As you see below:

Runnings test with 1.23.6

Runnings test with 1.24.0

Anything changed between the two tests, only beanie version, I read that problem can occur with race condition code, but is not the case, the exception is raised on inside the POST I save an "Machine" (my entity) instance.

On test, machine is created:

My API only gets the "machine" and updates a field:

Model is a common Document model (TimestampedDocument is just a class with updated_at and created_at fields):

Factory also is a common factory:

All stack error
============================= test session starts ==============================
platform linux -- Python 3.11.5, pytest-7.4.4, pluggy-1.4.0
rootdir: /workspace/cz-coordinator-api
configfile: pyproject.toml
plugins: anyio-3.7.1, asyncio-0.21.1, Faker-22.6.0, cov-4.1.0, httpx-0.26.0, fastapi-deps-0.2.3, celery-0.0.0
asyncio: mode=Mode.STRICT
collected 1 item
tests/drivers/test_api.py F                                              [100%]
=================================== FAILURES ===================================
___________________ test_post_session_status_history_success ___________________
data = OrderedDict([('_id', '36'), ('revision_id', Binary(b"\xa0Q\xb1V?\xceJ\x84\x92\xd8\xf1\xd3\xfd'\xc3U", 4)), ('created_a..., ('external_id', 'kjdvqxmfejcvHlaFvhlG'), ('last_appeal_token_at', datetime.datetime(2024, 2, 22, 2, 6, 36, 767000))])
args = (), kwargs = {}
@wraps(fn)
def wrapper(data, *args, **kwargs):
    try:

      return fn(data, *args, **kwargs)

/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/mongomock_motor/patches.py:56:

self = Collection(Database(mongomock.MongoClient('localhost', 27017), 'coordinator'), 'Machine')
data = OrderedDict([('_id', '36'), ('revision_id', Binary(b"\xa0Q\xb1V?\xceJ\x84\x92\xd8\xf1\xd3\xfd'\xc3U", 4)), ('created_a..., ('external_id', 'kjdvqxmfejcvHlaFvhlG'), ('last_appeal_token_at', datetime.datetime(2024, 2, 22, 2, 6, 36, 767000))])
session = None, ordered = True
def _insert(self, data, session=None, ordered=True):
    if session:
        raise_not_implemented('session', 'Mongomock does not handle sessions yet')
    if not isinstance(data, Mapping):
        results = []
        write_errors = []
        num_inserted = 0
        for index, item in enumerate(data):
            try:
                results.append(self._insert(item))
            except WriteError as error:
                write_errors.append({
                    'index': index,
                    'code': error.code,
                    'errmsg': str(error),
                    'op': item,
                })
                if ordered:
                    break
                else:
                    continue
            num_inserted += 1
        if write_errors:
            raise BulkWriteError({
                'writeErrors': write_errors,
                'nInserted': num_inserted,
            })
        return results

    if not all(isinstance(k, str) for k in data):
        raise ValueError('Document keys must be strings')

    if BSON:
        # bson validation
        BSON.encode(data, check_keys=True)

    # Like pymongo, we should fill the _id in the inserted dict (odd behavior,
    # but we need to stick to it), so we must patch in-place the data dict
    if '_id' not in data:
        data['_id'] = ObjectId()

    object_id = data['_id']
    if isinstance(object_id, dict):
        object_id = helpers.hashdict(object_id)
    if object_id in self._store:

      raise DuplicateKeyError('E11000 Duplicate Key Error', 11000)

E           pymongo.errors.DuplicateKeyError: E11000 Duplicate Key Error
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/mongomock/collection.py:516: DuplicateKeyError
During handling of the above exception, another exception occurred:
self = Machine(id='36', revision_id=None, created_at=datetime.datetime(2017, 3, 5, 9, 19, 7, 719000), updated_at=datetime.dat...46, 791000), external_id='kjdvqxmfejcvHlaFvhlG', last_appeal_token_at=datetime.datetime(2024, 2, 22, 2, 6, 36, 767415))
ignore_revision = False, session = None, bulk_writer = None, skip_actions = []
skip_sync = None
args = ({'$set': {'_id': '36', 'revision_id': UUID('a051b156-3fce-4a84-92d8-f1d3fd27c355'), 'created_at': datetime.datetime(2...0), 'external_id': 'kjdvqxmfejcvHlaFvhlG', 'last_appeal_token_at': datetime.datetime(2024, 2, 22, 2, 6, 36, 767415)}},)
pymongo_kwargs = {'upsert': True}
arguments = [{'$set': {'_id': '36', 'revision_id': UUID('a051b156-3fce-4a84-92d8-f1d3fd27c355'), 'created_at': datetime.datetime(2...atetime(2024, 2, 22, 2, 6, 36, 767415)}}, <beanie.odm.operators.update.general.SetRevisionId object at 0x7f0604aebe50>]
use_revision_id = True, find_query = {'_id': '36', 'revision_id': None}
new_revision_id = UUID('a051b156-3fce-4a84-92d8-f1d3fd27c355')
@wrap_with_actions(EventTypes.UPDATE)
@save_state_after
async def update(
    self,
    *args,
    ignore_revision: bool = False,
    session: Optional[ClientSession] = None,
    bulk_writer: Optional[BulkWriter] = None,
    skip_actions: Optional[List[Union[ActionDirections, str]]] = None,
    skip_sync: Optional[bool] = None,
    **pymongo_kwargs,
) -> DocType:
    """
    Partially update the document in the database

    :param args: *Union[dict, Mapping] - the modifications to apply.
    :param session: ClientSession - pymongo session.
    :param ignore_revision: bool - force update. Will update even if revision id is not the same, as stored
    :param bulk_writer: "BulkWriter" - Beanie bulk writer
    :param pymongo_kwargs: pymongo native parameters for update operation
    :return: None
    """
    arguments = list(args)

    if skip_sync is not None:
        raise DeprecationWarning(
            "skip_sync parameter is not supported. The document get synced always using atomic operation."
        )
    use_revision_id = self.get_settings().use_revision

    if self.id is not None:
        find_query: Dict[str, Any] = {"_id": self.id}
    else:
        find_query = {"_id": PydanticObjectId()}

    if use_revision_id and not ignore_revision:
        find_query["revision_id"] = self.revision_id

    if use_revision_id:
        new_revision_id = uuid4()
        arguments.append(SetRevisionId(new_revision_id))
    try:

      result = await self.find_one(find_query).update(

            *arguments,
            session=session,
            response_type=UpdateResponse.NEW_DOCUMENT,
            bulk_writer=bulk_writer,
            **pymongo_kwargs,
        )

/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/documents.py:662:

/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/queries/update.py:351: in await
update_result = yield from self._update().await()
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/queries/update.py:319: in _update
result = await self.document_model.get_motor_collection().find_one_and_update(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/mongomock_motor/init.py:31: in wrapper
return getattr(proxy_source, method_name)(*args, **kwargs)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/mongomock/collection.py:1309: in find_one_and_update
return self._find_and_modify(filter, projection, update, upsert,
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/mongomock/collection.py:1349: in _find_and_modify
updated = self._update(query, update, upsert)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/mongomock/collection.py:892: in _update
upserted_id = self._insert(existing_document)

data = OrderedDict([('_id', '36'), ('revision_id', Binary(b"\xa0Q\xb1V?\xceJ\x84\x92\xd8\xf1\xd3\xfd'\xc3U", 4)), ('created_a..., ('external_id', 'kjdvqxmfejcvHlaFvhlG'), ('last_appeal_token_at', datetime.datetime(2024, 2, 22, 2, 6, 36, 767000))])
args = (), kwargs = {}
@wraps(fn)
def wrapper(data, *args, **kwargs):
    try:
        return fn(data, *args, **kwargs)
    except DuplicateKeyError as exc:

      raise _provide_error_details(collection, data, exc)

E           pymongo.errors.DuplicateKeyError: E11000 Duplicate Key Error, full error: {'keyValue': {'external_id': 'kjdvqxmfejcvHlaFvhlG'}, 'keyPattern': {'external_id': 1}}
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/mongomock_motor/patches.py:58: DuplicateKeyError
During handling of the above exception, another exception occurred:
auth_client_api_key = <starlette.testclient.TestClient object at 0x7f0604d04190>
session = Session(id='GNfLujMGQdWngpYjtThE', revision_id=UUID('a0f34b40-24c2-4a36-8cb4-21ffc0e058b4'), created_at=datetime.datet...status_event_at=None, sync_info=None, qrcode_info=None, finish_info='a3ac571b', channel=<Channel.WHATSAPP: 'whatsapp'>)
new_post_session_status_history = PostSessionStatusHistory(event_type=<SessionStatusEventType.APPEAL_TOKEN: 'appeal_token'>, event={})
async def test_post_session_status_history_success(
    auth_client_api_key: TestClient,
    session,
    new_post_session_status_history: PostSessionStatusHistory,
):
    await MachineFactory.create_async(id=session.machine_id)

    sessions_history = await SessionStatusHistory.find_all().to_list()
    assert len(sessions_history) == 0

  response = auth_client_api_key.post(

        f"/api/v1/drivers/sessions/{session.id}/status-history", json=new_post_session_status_history.model_dump()
    )

tests/drivers/test_api.py:426:

/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/testclient.py:590: in post
return super().post(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/httpx/_client.py:1132: in post
return self.request(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/testclient.py:465: in request
return super().request(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/httpx/_client.py:814: in request
return self.send(request, auth=auth, follow_redirects=follow_redirects)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/httpx/_client.py:901: in send
response = self._send_handling_auth(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/httpx/_client.py:929: in _send_handling_auth
response = self._send_handling_redirects(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/httpx/_client.py:966: in _send_handling_redirects
response = self._send_single_request(request)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/httpx/_client.py:1002: in _send_single_request
response = transport.handle_request(request)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/testclient.py:342: in handle_request
raise exc
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/testclient.py:339: in handle_request
portal.call(self.app, scope, receive, send)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/anyio/from_thread.py:277: in call
return cast(T_Retval, self.start_task_soon(func, *args).result())
/home/matheus/.pyenv/versions/3.11.5/lib/python3.11/concurrent/futures/_base.py:456: in result
return self.__get_result()
/home/matheus/.pyenv/versions/3.11.5/lib/python3.11/concurrent/futures/_base.py:401: in __get_result
raise self._exception
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/anyio/from_thread.py:217: in _call_func
retval = await retval
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/fastapi/applications.py:292: in call
await super().call(scope, receive, send)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/applications.py:122: in call
await self.middleware_stack(scope, receive, send)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/middleware/errors.py:184: in call
raise exc
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/middleware/errors.py:162: in call
await self.app(scope, receive, _send)
src/middlewares/correlation_id/middleware.py:91: in call
await self.app(scope, receive, handle_outgoing_request)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/middleware/cors.py:83: in call
await self.app(scope, receive, send)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py:79: in call
raise exc
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/middleware/exceptions.py:68: in call
await self.app(scope, receive, sender)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py:20: in call
raise e
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/fastapi/middleware/asyncexitstack.py:17: in call
await self.app(scope, receive, send)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/routing.py:718: in call
await route.handle(scope, receive, send)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/routing.py:276: in handle
await self.app(scope, receive, send)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/starlette/routing.py:66: in app
response = await func(request)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/fastapi/routing.py:273: in app
raw_response = await run_endpoint_function(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/fastapi/routing.py:190: in run_endpoint_function
return await dependant.call(**values)
src/apps/drivers/api.py:251: in post_session_status_history
await machine.save()
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/actions.py:219: in wrapper
result = await f(self, *args, skip_actions=skip_actions, **kwargs)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/utils/state.py:66: in wrapper
result = await f(self, *args, **kwargs)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/utils/self_validation.py:12: in wrapper
return await f(self, *args, **kwargs)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/documents.py:545: in save
return await self.update(
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/actions.py:219: in wrapper
result = await f(self, *args, skip_actions=skip_actions, **kwargs)
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/utils/state.py:66: in wrapper
result = await f(self, *args, **kwargs)

self = Machine(id='36', revision_id=None, created_at=datetime.datetime(2017, 3, 5, 9, 19, 7, 719000), updated_at=datetime.dat...46, 791000), external_id='kjdvqxmfejcvHlaFvhlG', last_appeal_token_at=datetime.datetime(2024, 2, 22, 2, 6, 36, 767415))
ignore_revision = False, session = None, bulk_writer = None, skip_actions = []
skip_sync = None
args = ({'$set': {'_id': '36', 'revision_id': UUID('a051b156-3fce-4a84-92d8-f1d3fd27c355'), 'created_at': datetime.datetime(2...0), 'external_id': 'kjdvqxmfejcvHlaFvhlG', 'last_appeal_token_at': datetime.datetime(2024, 2, 22, 2, 6, 36, 767415)}},)
pymongo_kwargs = {'upsert': True}
arguments = [{'$set': {'_id': '36', 'revision_id': UUID('a051b156-3fce-4a84-92d8-f1d3fd27c355'), 'created_at': datetime.datetime(2...atetime(2024, 2, 22, 2, 6, 36, 767415)}}, <beanie.odm.operators.update.general.SetRevisionId object at 0x7f0604aebe50>]
use_revision_id = True, find_query = {'_id': '36', 'revision_id': None}
new_revision_id = UUID('a051b156-3fce-4a84-92d8-f1d3fd27c355')
@wrap_with_actions(EventTypes.UPDATE)
@save_state_after
async def update(
    self,
    *args,
    ignore_revision: bool = False,
    session: Optional[ClientSession] = None,
    bulk_writer: Optional[BulkWriter] = None,
    skip_actions: Optional[List[Union[ActionDirections, str]]] = None,
    skip_sync: Optional[bool] = None,
    **pymongo_kwargs,
) -> DocType:
    """
    Partially update the document in the database

    :param args: *Union[dict, Mapping] - the modifications to apply.
    :param session: ClientSession - pymongo session.
    :param ignore_revision: bool - force update. Will update even if revision id is not the same, as stored
    :param bulk_writer: "BulkWriter" - Beanie bulk writer
    :param pymongo_kwargs: pymongo native parameters for update operation
    :return: None
    """
    arguments = list(args)

    if skip_sync is not None:
        raise DeprecationWarning(
            "skip_sync parameter is not supported. The document get synced always using atomic operation."
        )
    use_revision_id = self.get_settings().use_revision

    if self.id is not None:
        find_query: Dict[str, Any] = {"_id": self.id}
    else:
        find_query = {"_id": PydanticObjectId()}

    if use_revision_id and not ignore_revision:
        find_query["revision_id"] = self.revision_id

    if use_revision_id:
        new_revision_id = uuid4()
        arguments.append(SetRevisionId(new_revision_id))
    try:
        result = await self.find_one(find_query).update(
            *arguments,
            session=session,
            response_type=UpdateResponse.NEW_DOCUMENT,
            bulk_writer=bulk_writer,
            **pymongo_kwargs,
        )
    except DuplicateKeyError:

      raise RevisionIdWasChanged

E           beanie.exceptions.RevisionIdWasChanged
/home/matheus/.cache/pypoetry/virtualenvs/cz-coordinator-api-Lp1F0DE3-py3.11/lib/python3.11/site-packages/beanie/odm/documents.py:670: RevisionIdWasChanged
=========================== short test summary info ============================
FAILED tests/drivers/test_api.py::test_post_session_status_history_success - ...
============================== 1 failed in 1.34s ===============================

Hi, I came here after my code raised RevisionIdWasChanged error when I tried to create a document with the same value on a unique index field. I wonder why RevisionIdWasChanged is raised upon a DuplicateKeyError. Can any of you explain this?
How should I distinct that what should I handle then?
Cheers!

@roman-right I don't want to open another issue but could you please explain why is this behaviour implemented? Can't we just let the original DuplicateKeyError to be raised on an actual duplicate key error?

@roman-right I don't want to open another issue but could you please explain why is this behaviour implemented? Can't we just let the original DuplicateKeyError to be raised on an actual duplicate key error?

I have the same question. Not sure if this is the intended behavior

Problem: when you try to create 2 documents with the same value on the unique field, beanie raises RevisionIdWasChanged exception instead of DuplicateKeyError.
Solution:

This happens because save() was called. Since save() will try to update the document if it's already there, it will raise the RevisionIdWasChanged exception due to the unique constraint, as can be seen from the source code.
Therefore, instead of using save(), use insert(), then you will get the DuplicateKeyError when the unique constraint is violated.

@tdoan2010 Interesting. However, what should we use then when we updating an entry?

@martincpt in that case, just call .save. It won't throw the error when we update a document and the unique constraint is not violated. It works as expected in my application.

Here .save() causes the RevisionIdWasChanged exception instead of DuplicateKeyError, I need to use .replace() to not have this exception, but I have a pre-lookup with custom conditions to check if the record exists and .replace() also does this , in this case I have two polls after the update and it is not good for performance.

@RempelOliveira yes, but only if you call .save() to create a document.
In my case, I called .insert() for creation and .save() for update. By doing so, I didn't get the RevisionIdWasChanged exception.

@tdoan2010
For me the exception also occurs when updating. Please share your code so we can see why the exception wasn't thrown for you?!

Same issue here.
https://github.com/BeanieODM/beanie/issues/833
#833 has a reproducible snippet.

I'm having this issue as well


Corrected Incentive Calculation

current incentive calculation is  not accurate because it is calculating the incentive without considering 'Model.target_error'.  Its assumes the target_error =0.
Here it considers the 'target_error' to calculate incentive.

Not sure if anyone actually put any thoughts into how the bounty should really be calculated.
Please make sure the PR does not break the build.

if a new_model reduces error lesser than the target_error, what will its incentive be?

Closing as there is conflict in ModelRepository.sol, will issue a new PR.


ADD: Latex useful guides

Introduction
Dear bualpha,
I'd like to add a resource to the library, which I think would be useful to people interested in Quantitative Finance. Here is a description of the resource
Resource Type

[ ] Math
[ ] Statistics
[x] Computer Science
[x] Finance

Resource
Title:
Author(s)
Author(s):
Reason for Adding This Resource
Sincerely,
[my_github_username]

@PrestonYadegar Can you squash your commits and list out the Titles, Authors, etc?


⚠ Bofrost.de has degraded performance

In 8b12183, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1592 ms

Resolved: Bofrost.de performance has improved in 8445f8e after 6 minutes.


hello , how i can make this script responsive ?

hi, you have nice script it's good but i need to add something to make it responsive please tell me how ,it must show the current view of panoramic image as full size of div or window
when i make window size big than 500px it show me the image as tile images i want to make it as fill image of window
Best Regards

Use CSS to set the background image to no-repeat and set it to % dimensions.
Sent from my iPhone

On Jan 25, 2015, at 4:08 PM, Mohammed<EMAIL_ADDRESS>wrote:
hi, you have nice script it's good but i need to add something to make it responsive please tell me how ,it must show the current view of panoramic image as full size of div or window
when i make window size big than 500px it show me the image as tile images i want to make it as fill image of window
Best Regards
—
Reply to this email directly or view it on GitHub.

The demo is responsive http://blog.n42designs.com/pano/

I think I see what you're saying.  Yeah, you can't make it larger than the actual size of the image.  It doesn't scale the image up.  It needs to repeat-x in order for the viewer to move the image into view.  So if you need it larger you'll need a larger/higher res version of the image.


TensorFlow Lite for Inception v3 - Squeeze operator isn't supported

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No, I haven't used any custom code for this.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04
TensorFlow installed from (source or binary):
source
TensorFlow version (use command below):
r1.5 (6c5063a3f099c302412fcefa17edb2efa9921f01)
Python version:
3
Bazel version (if compiling from source):
0.9.0
GCC/Compiler version (if compiling from source):
gcc4.4
CUDA/cuDNN version:
9.0/7.0
GPU model and memory:
GTX 1080 8GB
Exact command to reproduce:

bazel-bin/tensorflow/contrib/lite/toco/toco \
  --input_file=inception-retrained-graph_freezed.pb \
  --input_format=TENSORFLOW_GRAPHDEF  --output_format=TFLITE \
  --output_file=inception-retrained-graph.tflite --inference_type=FLOAT \
  --input_type=FLOAT --input_arrays=input \
  --output_arrays=InceptionV3/Predictions/Reshape_1 --input_shapes=1,299,299,3

Describe the problem
I tried to use the above command to convert a retrained inception v3 model into the new tflite format. The input graph has already been freezed. The general process is described in this tutorial. However, I'm not able to finish the conversion as the tool complains that the Squeeze operator isn't supported. According to this guide the script should be able to remove the squeeze operation. This comment suggests that it may not always be possible to remove it. The inception v3 architecture is guaranteed to work though. Am I safe using the --allow_custom_ops flag?
Some final note:
I retrained the inception net using the slim model rather than just retraining the last layer using the freezed graph version. May this be the cause of the additional squeeze problem?
Source code / logs
This is the complete log as returned by the toco script:
W tensorflow/contrib/lite/toco/toco_cmdline_flags.cc:178] --input_type is deprecated. It was an ambiguous flag that set both --input_data_types and --inference_input_type. If you are trying to complement the input file with information about the type of input arrays, use --input_data_type. If you are trying to control the quantization/dequantization of real-numbers input arrays in the output file, use --inference_input_type.
2018-02-07 01:23:50.754337: I tensorflow/contrib/lite/toco/graph_transformations/graph_transformations.cc:39] Before general graph transformations: 1074 operators, 1657 arrays (0 quantized)
2018-02-07 01:23:50.826283: I tensorflow/contrib/lite/toco/graph_transformations/graph_transformations.cc:39] After general graph transformations pass 1: 126 operators, 317 arrays (0 quantized)
2018-02-07 01:23:50.827683: I tensorflow/contrib/lite/toco/graph_transformations/graph_transformations.cc:39] Before dequantization graph transformations: 126 operators, 317 arrays (0 quantized)
2018-02-07 01:23:50.828908: I tensorflow/contrib/lite/toco/allocate_transient_arrays.cc:313] Total transient array allocated size: 11139584 bytes, theoretical optimal value: 8297856 bytes.
2018-02-07 01:23:50.829206: I tensorflow/contrib/lite/toco/toco_tooling.cc:269] Estimated count of arithmetic ops: 11.4574 billion (note that a multiply-add is counted as 2 ops).
2018-02-07 01:23:50.829493: F tensorflow/contrib/lite/toco/tflite/export.cc:303] Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If you have a custom implementation for them you can disable this error with --allow_custom_ops. Here is a list of operators for which you will need custom implementations: Squeeze.
[1]    16187 abort (core dumped)  bazel-bin/tensorflow/contrib/lite/toco/toco   --output_format=TFLITE

I just figured out that the commit which is required for the squeeze support was actually added after the v1.5 release. Using the latest master commit works just fine. However, it should be considered to backport this feature as the 1.5 docs already list the squeeze operator as supported (more precisely it's listed as removable).

Unfortunately, I still can't use any inception model that I retrained on my own. Using the master branch fixes the above error and allows using the precompiled inception-v3 slim model. The latter implies that there shouldn't be any problem with the slim version in general. It doesn't work with mine though. The tflite conversion seems to be completed without any errors now, but if I want to use the graph in the Android example app, I always get the following crash log:
02-07 17:32:06.651 18636-18651/android.example.com.tflitecamerademo E/AndroidRuntime: FATAL EXCEPTION: CameraBackground
                                                                                Process: android.example.com.tflitecamerademo, PID: 18636
                                                                                java.lang.IllegalArgumentException: Invalid handle to Interpreter.
                                                                                at org.tensorflow.lite.NativeInterpreterWrapper.getInputDims(Native Method)
                                                                                at org.tensorflow.lite.NativeInterpreterWrapper.run(NativeInterpreterWrapper.java:82)
                                                                                at org.tensorflow.lite.Interpreter.runForMultipleInputsOutputs(Interpreter.java:112)
                                                                                at org.tensorflow.lite.Interpreter.run(Interpreter.java:93)
                                                                                at com.example.android.tflitecamerademo.ImageClassifierFloatInception.runInference(ImageClassifierFloatInception.java:103)
                                                                                at com.example.android.tflitecamerademo.ImageClassifier.classifyFrame(ImageClassifier.java:107)
                                                                                at com.example.android.tflitecamerademo.Camera2BasicFragment.classifyFrame(Camera2BasicFragment.java:664)
                                                                                at com.example.android.tflitecamerademo.Camera2BasicFragment.-wrap0(Camera2BasicFragment.java)
                                                                                at com.example.android.tflitecamerademo.Camera2BasicFragment$4.run(Camera2BasicFragment.java:559)
                                                                                at android.os.Handler.handleCallback(Handler.java:739)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:95)
                                                                                at android.os.Looper.loop(Looper.java:158)
                                                                                at android.os.HandlerThread.run(HandlerThread.java:61)

It doesn't help to recreate the input graph using the current TensorFlow version. I also tried to start the conversion using python instead of the command line, but it doesn't help either.
Any thoughts?

The java exception seems to imply that file you are trying to read is invalid. I'd say loading failed at https://github.com/tensorflow/tensorflow/blob/d4ad9c73969c45d1a224ebfc43eb645b9860216b/tensorflow/contrib/lite/java/src/main/native/nativeinterpreterwrapper_jni.cc#L296 but I can't tell exactly why.

Thanks for your answer. Yes, it states that my model file seems to be invalid, but I don't see a reason why. Unfortunately, I'm not really familiar with the native code parts. Can someone give me some hints how to debug this appropriately?

Nagging Assignee @andrehentz: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @andrehentz: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @andrehentz: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @andrehentz: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Hi @Johnson145 any chance you can try this again? I'm hoping the new versions will give you a better error message and help debug.

Nagging Assignee @andrehentz: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @andrehentz: It has been 45 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Could you try this again? Can you confirm that toco succeeds and a non-zero file is created?

Nagging Assignee @andrehentz: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @andrehentz: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Closing it, please reopen if you still see this issue


Circular Dependency with GameObjectContext

Hello.
There is a problem with circular dependencies between a Subcontainer in a GameObjectContext and a type in the scene context
Main -> Foo (Main in GameObjectContext)
Foo-> Main (Foo in SceneContext)
In older versions, this caused that the GameObjectContext to be instantiated several times.
I have seen that now this is prevented by SubContainerCreatorCached._isLookingUp.
But I think the real issue is here:
public DiContainer CreateSubContainer(List<TypeValuePair> args, InjectContext context)
{
		if (_subContainer == null) // <======HERE
		{
			Assert.That(!_isLookingUp,
				"Found unresolvable circular dependency when looking up sub container!  Object graph:\n {0}", context.GetObjectGraphString());
			_isLookingUp = true;

			 // <===== AND HERE===========>
			_subContainer = _subCreator.CreateSubContainer(new List<TypeValuePair>(), context);

			_isLookingUp = false;

			Assert.IsNotNull(_subContainer);
		}

		return _subContainer;
}

_subCreator.CreateSubContainer has two parts, the creation and the injection, but the _subContainer reference is got after the injection, so

Resolve Main. We are in CreateSubContainer.
Instantiate GameobjectContext
To Resolve Main, we have to resolve Foo
To Resolve Foo, we have to resolve Main (circular dependency)
Resolve Main. We are in CreateSubContainer again
Because we still are inside the flow of the first resolve main, CreateSubContainer hasn't finish and _ subContainer is still null
if (_subContainer == null) returns true
In older versions, other GameobjectContext is instantiated twice. In the new versions, a exception is throw.

I think a solution to this could be to split CreateSubContainer in two parts.
The first part would be to instantiate the gameobject context, create a subcontainer, set it to the gameobject context and get the reference in SubContainerCreatorCached.
After this, we inject the gameobject context. This way, if we enter again in CreateSubContainer because of a circular dependency, _subContainer is no longer null
I have done a very dirty prototype just to illustrate what I mean.
What do you think?
Thank you
public DiContainer CreateSubContainer(List<TypeValuePair> args, InjectContext context)
{
		if (_subContainer == null)
		{
			SubContainerCreatorByNewPrefab creatorByPrefab = (SubContainerCreatorByNewPrefab)_subCreator;
			DiContainer sub = null;
			GameObjectContext goContext = null;
			creatorByPrefab.CreateRawSubContainer(new List<TypeValuePair>(), out sub, out goContext);
			_subContainer = sub;
			creatorByPrefab.InjectSubcontainer(goContext);

			Assert.IsNotNull(_subContainer);
		}

		return _subContainer;
	}
}

        public void CreateRawSubContainer(List<TypeValuePair> args, out DiContainer subcontainer, out GameObjectContext context)
        {
            Assert.That(args.IsEmpty());
            Object prefab = _prefabProvider.GetPrefab();

            bool shouldMakeActive;
            GameObject instance = _container.CreateAndParentPrefab(prefab, _gameObjectBindInfo, null, out shouldMakeActive);
            instance.SetActive(shouldMakeActive);
            context = instance.GetComponent<GameObjectContext>();
            context.SetContainerForCircularDependencyWorkarround(_container.CreateSubContainer());
            subcontainer = context.Container;

        }

        public void InjectSubcontainer(GameObjectContext context)
        {
            _container.InjectGameObject(context.gameObject);
        }

Yeah that makes sense to me.  Triggering injection of the game object context after storing the _subcontainer reference would help solve this problem.  This same pattern is used in other provider classes (like CachedProvider) specifically to allow for circular dependencies.  So we should do the same in this case as well

Ok this should be fixed now.  This change should address a lot of other existing problems with circular dependencies + FromSubContainerResolve too


Extension Blocked By Chrome

Hi
The extension is blocked by Chrome as it is no longer downloadable from the Chrome store.  Chrome will not let me manually enable it, even in Developer mode.
Any advice on what to do?
Many thanks.
VBC

Hey,
To install the extension as of now, you don't even need to be in Developer Mode. All you have to do is download the latest extension from the Releases section, ensure it is in the default Downloads Directory on your computer, and then drag-and-drop it to your extensions page.
Let me know if this works for you. I will clarify the instructions on the README to make this clearer.

I am facing the same issue in Chrome 71.  I am not able to enable the extension after following the process listed in README

@kungpao42 Can you please confirm that you are in developer mode and that the .crx file downloaded is in the default download directory? I am on Chrome 71 as well, and I tested on both MacOS and Windows and it works for me.

@VeryNaughtyCat FT does look like it's broken, can you create a new issue (so I can reference commits) there?

I fixed my issue by moving back to the normal release channel of Chrome, I was on beta.  Additionally, I am running OSX...so I deleted my preference files, etc:
rm -rf ~Library/Google
That caused the extension to load and was no longer blocked in the UI.

@kungpao42 Thanks for sharing. @VeryNaughtyCat are you on the beta channel by any chance?

Hi, still experiencing this issue with Chrome Beta 84.
This resolved my issue: https://www.ghacks.net/2014/05/28/unsupported-extensions-disabled-re-enable-blocked-extensions-chrome/

extract the extension file (.crx) on your system for this to work. The easiest way to handle this is to download the extension again from the developer website. Right-click the extension again and extract it to a folder on your system... (eg with 7zip)
Now that you have extracted the extension, click on load unpacked extension and select the folder that you have extracted the extension files to.
The extension will be installed and won't be removed on the next start of the browser. Chrome will display a "disable developer mode extensions" notification though in the browser, but you can cancel that to skip it. Note that it will display the message on every start of the browser.


Follow ducks-like architecture

I don't agree with the naming conventions, but overall it would be nice to group flux pieces together (constants/reducers/actions).

agreed! i'm actually the one who initially restructured erik's universal example. i would propose something similar without the naming conventions (ie. namespacing constants for action types is unnecessary)
this is roughly how my projects are structured:
/redux
    /middleware
    /modules   [grouped redux logic aka "ducks"]
    /selectors [reselect helpers - probably not necessary for starter-kit]
    createStore.js

Cool, I also really like the modules naming convention over ducks or whatever else. Thanks for the link, too.
On an unrelated note, I've been thinking about switching away from the airbnb-config base to something closer to a mix of ract/standard. Any opinions on this? Biggest thing would probably just be removal of semi colons.

:+1: rackt config
"space-before-function-paren": [ 2, { "anonymous": "always", "named": "never" } ]

are you gonna be ok with this one? lol

Removal of semi-colons still feels wrong to me. Call me a classicist :)
On 10 Dec 2015, at 23:51, David Zukowski<EMAIL_ADDRESS>wrote:

Cool, I also really like the modules naming convention over ducks or whatever else. Thanks for the link, too.
On an unrelated note, I've been thinking about switching away from the airbnb-config base to something closer to a mix of ract/standard. Any opinions on this? Biggest thing would probably just be removal of semi colons.
—
Reply to this email directly or view it on GitHub.

@justingreenberg I will fight that rule until the day I die; it separates function definitions from invocations, and just makes the code look so much nicer.
@mtsr I was the same way until my new team forced it upon me haha. The other big debate now is "use trailing commas or not" or, if you're nuts like me, "leading commas?!"

@justingreenberg could you offer up an explanation as to what exactly lives under /middleware? I thought it would be actual middleware (i.e. for the redux life cycle), but your comment about moving the DevTools component there threw me off.

@davezuko i'm sorry i can see how that was confusing  /middleware is totally for redux lifecycle stuff!
so using the createDevtools HOC over monitors instantiates a container, but we still have to import and invoke an instance method to inject the middleware hooks into the redux store. so it's not really a container, it's more like a factory (which is why i proposed renaming to createDevtools.js)
maybe something like:
/redux
    /middleware
    /modules   [grouped redux logic aka "ducks"]
    /devtools/createDevToolsContainer.js
    /devtools/createDevToolsWindow.js
    createStore.js

imho, this just seems much more intuitive and puts some distance between project code and devtools

Thanks for the explanation. I actually missed the fact in your previous comment that everything was nested within a redux folder... I'm not actually sold on that just yet, but I'm going to run out for a few minutes and mull it over. The big thing is that modules are now nested in e.g. ~/src/redux/modules/counter, so I might like to pull that up a level (~/src/modules/counter).

the case for a redux folder is to establish a clearly defined boundary between state management and presentation, with the added benefit of (mostly) encapsulating redux integrations
i feel like many redux projects end up spreading out state logic between connected containers/components, devtools, etc. which is probably muscle memory from using flux with a bunch of stores... it ends up making things more difficult to reason about than they need to be with a single store.
since we're talking about using "ducks" (redux modules!!), that boundary is actually within reach
./src
    /components
    /containers
        Root.js  # point of contact for devtools, code unchanged
    /layouts
    /routes
    /redux *
        /middleware
        /modules
            counter.js
        /helpers
            createDevToolsContainer.js
            createDevToolsWindow.js    # uses createDevToolsContainer.js
            createReducer.js
        configureStore.js
    /styles
    /views
    app.js  # point of contact for store / redux router
    index.html

the only points of contact between ./redux and the application are Root container (for devtools), any other connected containers, and app.js (an idiomatic redux app could thread action creators via props)
some food for thought... i support the restructure and "redux modules" either way!


preparing release 2.0.0

Coverage remained the same at 46.667% when pulling 963eaf6efa5d30651b2d2c7bd0b54c0ccc0529b9 on release/2.0.0 into 3b613294d93d5b3c26caeaa90357a671a74e5e4f on develop.


Frontend Traces Linking To Backend Traces

## Description
We have enabled frontend observability for our Angular application using the Grafana Faro Web SDK and Faro Web Tracing CDN. The frontend traces are being sent to Grafana Tempo via Grafana Alloy, and they are visible in Tempo.
For our Java backend services, we are using the OpenTelemetry Operator with auto-instrumentation. Both the frontend and backend traces are being generated successfully but are appearing separately in Grafana Tempo.
According to the documentation, trace propagation should automatically link the frontend and backend traces, but this linkage is not happening in Grafana Tempo. We have confirmed that the traceparent header is present in the backend API request and matches the frontend trace. Despite this, no trace linkage is observed between the frontend and backend traces.
## Steps to reproduce
Versions:
Grafana Faro Web SDK : 1.10.2
Faro Web Tracing CDN : 1.10.2
OpenTelemetry Operator Helm Chart : v0.94.0
Java Auto-instrumentation Agent : 1.32.1
Frontend Setup:
We integrated the Grafana Faro Web SDK and Faro Web Tracing CDN into the index.html of our Angular application. The app initiates a GET API call to a backend service for data.
The Angular app sends traces correctly, and they are visible in Grafana Tempo. Below is the index.html setup used to initialize Faro:
<script>
  window.addEventListener('environmentLoaded', (event) => {
    const { app_name, app_namespace, app_env } = event.detail;

    window.faro = window.GrafanaFaroWebSdk.initializeFaro({
      url: 'https://tempo.com/collect',
      apiKey: 'your-api-key',
      app: {
        name: app_name,
        namespace: app_namespace,
        environment: app_env,
        version: '1.0.0',
      },
      instrumentations: [...window.GrafanaFaroWebSdk.getWebInstrumentations()],
    });

    window.addTracing();
  });

  window.addTracing = () => {
    if (window.GrafanaFaroWebSdk && window.GrafanaFaroWebTracing) {
      const tracingInstrumentation = new window.GrafanaFaroWebTracing.TracingInstrumentation();
      window.faro.instrumentations.add(tracingInstrumentation);

      const { trace, context } = window.faro.api.getOTEL();
      const tracer = trace.getTracer('default');
      const span = tracer.startSpan('initialization');

      context.with(trace.setSpan(context.active(), span), () => {
        span.setAttribute('page_url', window.location.pathname);
        span.end();
      });
    }
  };
</script>

Observations:
When a frontend API call is made, we can see the traceparent header in the request headers sent to the backend service, and it matches the frontend trace:
traceparent: 00-74jfk49nslkc0485b0859djsc5-3ldskskxcc-01
this trace id send request headers to backend is same as frontend generate trace. but backend service generating new traceid for this request.
the traces do not link in Grafana Tempo.
Backend Setup:
We are using OpenTelemetry Operator with the following configuration for auto-instrumenting our Java backend services:
yaml
apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: java-instrumentation
spec:
  exporter:
    endpoint: "http://centralcollector.tracing.svc.cluster.local:4317"
  propagators:
    - tracecontext
    - baggage
    - b3
  sampler:
    type: always_on
  java:
    image: "imagepath/tracing/autoinstrumentation/java:1.32.1"
    resources:
      limits:
        cpu: 500m
        memory: 450Mi
      requests:
        cpu: 150m
        memory: 230Mi
  env:
    - name: OTEL_METRICS_EXPORTER
      value: none
    - name: OTEL_LOG_LEVEL
      value: debug

## Expected behavior
We expect Grafana Tempo to show the complete trace flow, from the frontend request in the Angular application to the backend response in the Java service. The traces from the frontend and backend should be automatically linked using trace propagation.

Hi there,
maybe it helps; for me the problem was my Backend did not attach the "server-timing" header back to the response:
Grafana Cloud Docs
I solved this via the recommended approach of integrating the middleware in my backend: https://grafana.com/docs/grafana-cloud/monitor-applications/frontend-observability/apm-integration/#nodejs-example
Statement from the docs:

After the server sends a server-timing header, the RUM instrumentation automatically picks it up. From the user session view, you can navigate directly to the trace that generated the response.
In this example, the initial navigation links to the request loading the page. Click the Services action to the right of the row to continue the investigation in the Application Observability space.

Hi there,
maybe it helps; for me the problem was my Backend did not attach the "server-timing" header back to the response:
Grafana Cloud Docs
I solved this via the recommended approach of integrating the middleware in my backend: https://grafana.com/docs/grafana-cloud/monitor-applications/frontend-observability/apm-integration/#nodejs-example
Statement from the docs:

After the server sends a server-timing header, the RUM instrumentation automatically picks it up. From the user session view, you can navigate directly to the trace that generated the response.
In this example, the initial navigation links to the request loading the page. Click the Services action to the right of the row to continue the investigation in the Application Observability space.

Hi,
Thank you for your response.
After investigating further, we identified the issue was related to trace propagation. In our setup, both the frontend and backend are auto-instrumented, but the frontend was using the tracecontext format (generating traceparent), while the backend was using the b3 propagation format.
To resolve this, we updated the configuration at the OpenTelemetry Collector level to convert and align the traceparent format with b3 propagation. With this change, the propagation issue is now resolved.
For reference added collector deployment file format with updated attributes.
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: centralcollector
  labels:
    {{- include "opentelemetry-operator.labels" . | nindent 4 }}
    {{- with .Values.CollectorServiceLabels }}
      {{- toYaml . | nindent 4 }}
    {{- end }}
spec:
  mode: deployment
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
            endpoint: <IP_ADDRESS>:4317
          http:
            cors:
              allowed_origins:
              - "*"
            endpoint: <IP_ADDRESS>:4318

    processors:
      memory_limiter:
        check_interval: 1s
        limit_percentage: 75
        spike_limit_percentage: 15

      attributes:
        actions:
          - key: "traceparent"
            action: "insert"
            value: "00-${x-b3-traceid}-${x-b3-spanid}-01"
          - key: "x-b3-traceid"
            action: "delete"
          - key: "x-b3-spanid"
            action: "delete"
    exporters:
      logging:
        loglevel: debug
      otlphttp:
        endpoint: {{ .Values.endpoint }}
        tls:
          insecure: false

    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: [memory_limiter, attributes]  # Order matters
          exporters: [logging, otlphttp]

Thank you for your help.


Update README.md

Description

How and where has this been tested?

How this was tested:
Browser(s) and OS(s) this was tested with:

Screenshots

To-do list

[x] If my change impacts other components, I have tested to make sure they don't break.
[x] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

[x] This pull request is ready to merge.

Thanks, but we don't want to bold this text.


vscode.startDebug with type "node" does not work, regardless of protocol

"vscode.startDebug" does not respect type: "node2" when the configuration supplies type: "node", as it happens in the embedded extension for node.js debugging.
Background
Visual Studio Code tracing shows that the embedded extension for node.js debugging actually uses type: "node2", even when the auto-generated file "launch.json" provides type: "node". Moreover, type: "node" if supplied to the "complex command" "vscode.startDebug" does not work anymore (see steps to reproduce below).
This is very confusing and not documented. The cases of "node2" and "node" should be merged to eliminate "node2". In worst case, this peculiarity should be thoroughly documented.
Related to 24762.
Steps to Reproduce:
0) Use node.js 8.1.4
1) Try node.js debugging with "launch.json":
{
    "version": "0.1.0",
    "configurations": [
        {
            "name": "Launch Extension",
            "type": "extensionHost",
            "request": "launch",
            "program": "${file}",
            "protocol": "auto" // anything but "legacy"
            ],
        }
    ]
}

It does work.
2) Now, in some extension code:
        const launchConfiguration = {
            type: "node", // a real confusion! found by tracing Visual Studio Code
            name: "Launch Extension",
            request: "launch",
            stopOnEntry: false,
            protocol: "auto"
        };
        vscode.commands.executeCommand("vscode.startDebug", launchConfiguration);

It shows the error:

[DEP0062] DeprecationWarning: node --debug and node --debug-brk are invalid. Please use node --inspect or node --inspect-brk instead

Even when the protocol is specified explicitly, the problem is the same:
        const launchConfiguration = {
            type: "node", // a real confusion! found by tracing Visual Studio Code
            name: "Launch Extension",
            request: "launch",
            stopOnEntry: false,
            protocol: "inspector"
        };
        vscode.commands.executeCommand("vscode.startDebug", launchConfiguration);

By documentation and logically, the type "node" should work. See also below.
3) The workaround:
Change type: "node" to type: "node2". It works. But this is not a real solution, because "officially", only type: "node" is supported. I do understand that operation with type: "node2" may eventually fail with some VSCode update.

Reproduces without extensions: No (the problem appears in extension, more exactly)

Please use the new proposed debug API "vscode.debug.startDebugging". It has the identical semantics as a manual launch of a launch config. Specifically it will run the same code in the extension that probes for the node.js version and picks the correct implementation of the protocol.
The current "vscode.startDebug" command will be deprecated and replaced by the official debug API "vscode.debug.startDebugSession". This is the low-level API which should only be used by debug extension authors.

"vscode.debug.startDebugging" should be available in Monday's Insiders build as proposed API.

Thank you, Andre.
It sounds really good.
I hope I can safely wait for production release, as my product is public. If the lifetime of temporary "code2" functionality overlaps with some beginning period of time after introduction of "vscode.debug.startDebugging" in a production release, new dependency records in my package will resolve the situation by requiring this newer VsCode version before 'code2" goes out of production.
Is it supposed to work this way? Can you give me a rough idea of a typical time frame for transition of a feature from Insiders to production?
Now, looking at the proposed code you pointed out: how about getConfiguration2 and WorkspaceConfiguration2? Are they really supposed to stay with their "2" names?
Thank you.
—SA

@SAKryukov as you can see in "vscode.proposed.d.ts": getConfiguration2 and WorkspaceConfiguration2 are gone.

Andre,
As of VSCode 1.15.0,  vscode.debug.startDebugging(launchConfiguration) does work, but it looks like having a defect.
when a configuration is passed as the parameter launchConfiguration, such as
const launchConfiguration = {
            type: "node",
            name: "Launch Extension",
            request: "launch",
            stopOnEntry: false,
            protocol: "auto"
        };

In this case, the UI request for launch configuration, a choice from the predefined list. despite the fact the configuration is already passed. When "node.js" is selected from the list, debugging starts to work. It stops working when launch.json file is prescribed in the target workspace, which is understandable though. Don't you think this is a defect which should be reported?
—SA

@SAKryukov sounds like a bug to me. Please file an issue.


Use tags to specify which tests scripts to run.

I love the work you're doing! Its really awesome!
It would be nice if there was a way to tag tests so that only certain tests are run. For example, having tags in the test file as follows:
Feature('My Awesome Feature', ['MOBILE', 'RETAIL', 'HOMEPAGE']);
This could allow tests to be run as follows rather than using --grep.
codeceptjs run . -tags="MOBILE"
This would allow all tests with the mobile tag to be executed. Any thoughts?

Good idea, I like it.
As a workaround, currently you can specify tags inside scenario or feature titles like @mobile @api and execute specific group by running --grep mobile.

This would be ah-mazing. Wholehearted "yes please!"

There is powerful grep from mocha implementation that we recommend to use http://codecept.io/advanced/#groups


Add simple standalone example data

We don't necessarily need a full tutorial or anything, but it would be nice to have an example in the README that uses data files included in this repository. Maybe setting these up as a subfolder in docs/moving-pictures (e.g. docs/moving-pictures/standalone-example-data/) would be easiest.
Newick and BIOM files are both pretty commonly used and clearly defined elsewhere, fortunately -- so I suspect the main "ambiguity" for many users will be in determining how the TSV metadata files should be formatted, since maybe some people would think that the samples should be columns or something. The easiest way to explain that is probably via example. (The main difference with the sample_metadata.tsv used in the repo right now is that the #q2:types row should be removed, as #499 points out.) Similarly, the skbio OrdinationResults format is probably unfamiliar to many people, so having an example of that would be nice.

"issue #500" hits different :pensive:


:sparkles: Add kai-eval avgs and minor improvements

Added average values for kai-eval metrics for easier integration with the visualizaer
Added kantra analysis of coolstore app output to the repository
Logging format improvements

@sshveta @midays Could you please review this PR? Thanks!


MAINT: remove support for non event data model

Description
This PR removes support for OTLP protocol as internal data transfer in trace ingestion.
Note:

the trace-analytics sample app in examples/dev works but the one in examples fail at this moment as this is a breaking change.

Issues Resolved
Resolves #1272
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1689 (abac532) into main (255f89d) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1689      +/-   ##
============================================
- Coverage     93.44%   93.36%   -0.08%
  Complexity     1297     1297
============================================
  Files           170      170
  Lines          3798     3798
  Branches        301      301
============================================
- Hits           3549     3546       -3
- Misses          178      181       +3
  Partials         71       71

Impacted Files
Coverage Δ

.../org/opensearch/dataprepper/pipeline/Pipeline.java
88.57% <0.00%> (-4.29%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

At a high level - Do we need to provide users with instructions for migrating as part of deprecating the old model?
Let's say a user upgraded to 2.0 but never switched to using the new internal model. What errors are going to be thrown when they use plugins which no longer exist? Will this be intuitive for the user to resolve on their own?
What happens if they set the event type to in the otel_trace_source? Will this fail or will they get a warning that it has been deprecated?

I think we should have added a warning in 1.4. But, I'd suggest that once a feature is removed we clear out all code related to it. One reason for removing features is to make it clearer to users what they should do. Another is it clean-up code.
We may want to have a document with specific instructions for migrating from 1.5 to 2.0


leaderelection: set release on cancel to true

This will cause faster operator upgrades as we release the leader when the context that we pass to all control loops in operators is cancelled (typically on graceful shutdown).

The new race to consider is the time between the release and the process exit. This should be small and all users of leader election need to handle cases of control loops taking time to shut down.  Similar to the original 3.x rules, an accidental active/active scenario should result in update conflict, backoff, status detection, skip.  The end result is a lot of stormy, conflicty work, but no wrong actions taken.
/lgtm