No such module 'CioMessagingPushFCM'

SDK version: customerio-reactnative": "4.1.0"
Are logs available?
Logs available in the screenshot
Describe the issue
The 'CioMessagingPushFCM' pod is not recognized in the import of the MyAppPushNotificationsHandler.swift file (as suggested in the documentation).
The podfile is correctly configured and the pods were installed successfully.
Screenshots

Additional context
Integration of push notifications based on FCM and Objective-C. The documentation is not quite clear, please review.

Thank you very much for your prompt reply, I will give you more details:

Yes, MyAppPushNotificationsHandler has been added to the main target.

Here goes my Podfile:

require File.join(File.dirname(`node --print "require.resolve('expo/package.json')"`), "scripts/autolinking")
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

platform :ios, '14.0'
prepare_react_native_project!

def node_require(script)
  require Pod::Executable.execute_command('node', ['-p',
    "require.resolve(
      '#{script}',
      {paths: [process.argv[1]]},
    )", __dir__]).strip
end

node_require('react-native/scripts/react_native_pods.rb')
node_require('react-native-permissions/scripts/setup.rb')

flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.disabled

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'MyApp' do
  use_expo_modules!

  post_integrate do |installer|
    begin
      expo_patch_react_imports!(installer)
    rescue => e
      Pod::UI.warn e
    end
  end

  config = use_native_modules!
  use_frameworks! :linkage => :static
  $RNFirebaseAsStaticFramework = true
  pod "react-native-heap", path: "../node_modules/@heap/react-native-heap"

  # Flags change depending on the env values.
  flags = get_default_flags()

  # Pods required by Customer.io
  pod 'customerio-reactnative/fcm', :path => '../node_modules/customerio-reactnative'

  use_react_native!(
    :path => config[:reactNativePath],
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    :flipper_configuration => flipper_config,
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  setup_permissions([
    'Camera',
    'Notifications',
    'FaceID',
  ])

  # target 'MyAppTests' do
  #   inherit! :complete
  #   # Pods for testing
  # end

  ENVFILES = {
    'Debug' => '$(PODS_ROOT)/../../.env.development',
    'Release' => '$(PODS_ROOT)/../../.env.production',
  }

  post_install do |installer|
    react_native_post_install(
      installer,

      :mac_catalyst_enabled => false
    )

    __apply_Xcode_12_5_M1_post_install_workaround(installer)

    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|

        config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']

        if target.name == 'react-native-config'
          config.build_settings['ENVFILE'] = ENVFILES[config.name]
        end

        if target.name == "React-Codegen"
          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
        end

        if target.name == 'BoringSSL-GRPC'
          target.source_build_phase.files.each do |file|
            if file.settings && file.settings['COMPILER_FLAGS']
              flags = file.settings['COMPILER_FLAGS'].split
              flags.reject! { |flag| flag == '-GCC_WARN_INHIBIT_ALL_WARNINGS' }
              file.settings['COMPILER_FLAGS'] = flags.join(' ')
            end
          end
        end
      end
    end
  end
end

target 'NotificationServiceExtension' do
  use_frameworks! :linkage => :static
  pod 'customerio-reactnative-richpush/fcm', :path => '../node_modules/customerio-reactnative'
  pod "FirebaseMessaging"
end

I followed the FCM/Objective-C documentation step by step, there are confusing steps, for example:
a) Step 3 of the documentation says to configure MyAppPushNotificationsHandler.swift with the siteId and apiKey but none of these variables appear in the proposed code.
b) Step 9 of the documentation talks about creating a NotificationServiceExtension.m file when the target creates a .Swift file. Also, the example code shows a NotificationService.m file. Which is extremely confusing. It also does not talk about the need to set up a bridge if Swift and Objective-C files are used.

Thanks for clarifying my questions! 🙏

Thank you for the detailed response @isavega-neat. This is really helpful. Appreciate the thorough explanation.
Your Podfile looks correct. Can you please try the following steps:

Remove all cached versions and project build folders
Reinstall all React Native dependencies
Run pod install again to ensure the dependencies are fetched properly

If the issue persists, please drop us an email at<EMAIL_ADDRESS>with following details so we can help you better:

Podfile and Podfile.lock
Files showing errors during the build (e.g., MyAppPushNotificationsHandler) or any other files with errors
Complete pod install logs, build logs, and the full error message
Any additional details you think might help us
A link to this GitHub ticket for reference

Regarding your documentation feedback, you're absolutely right. The summary is outdated, as we now only require cdpApiKey. Thanks for pointing that out, we'll update it soon.
Thank you for your patience and understanding!

Ok, I will write you an email with the details!
Thanks for the support, best regards

Closing this for now. We'll continue helping through support once requested details are shared via email. Even though the issue is closed, please feel free to reach out with any additional questions you may have.


v0.0.12

Changelog
Bug fix release
This release includes fix for https://github.com/redhat-developer/odo/issues/746.

LGTM.


Add Israel localization (Hebrew Language)

Add new localization, Israel, accurately hebrew translation following step-by-step to add a new localization.
Accomplished:

[x]  Copy one of the directories in locales and rename the new directory into your language's code.
[x] Open common.json and config.json inside the directory.
[x] Start translating the strings. Make sure to follow your language's plural rules for translation keys with an object as the value (e.g. those that require {{ count }}).
[x] Copy one of the README files and name it README.[code].md, e.g. README.id.md and translate the content. Add your language to the bottom of the new README and all the existing READMEs.
[x] Edit i18n.tsx and update the following variables:
[x] availableLanguages: include your language code and name.
[x] dateFormatters, shortDateFormatters, shortDateYearFormatters, and relativeTimeFormatters: include new objects with your language code, following the existing languages.
[x] Edit i18n.json and include your language.
[x] In all of the aforementioned files, make sure that the language list is sorted by the language code.
[x] Create a PR with your localization updates.

Thanks, I've rebased, squashed, and made minor edits (sort the language list alphabetically and add he to the rtlLanguages list.


Update README.md

name: Pull Request
about: Submit a pull request
title: ''
labels: ''
assignees: '@boz @gosuri'

Description

Motivation and Context

[ ] I have raised an issue to propose this change (required)
[ ] My issue has received approval from the maintainers or lead with the design/approved label

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I've read the CONTRIBUTION guide
[ ] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This pull request is with a view to amending the Become a validator link to https://akash.network/validators/
Also the link for target workload definition spec is leading to an error page https://docs.akash.network/sdl


Python: enable deserialization to Python classes

Problem
There's no out-of-the-box solution that would allow deserialize OL events into Python classes. As the continuation of the effort made to generate Python facets out of JSON schemas this PR aims to enable such serialization.
Solution

Use old type annotations to enable Python 3.8 compatibility.
Add global variable that registers and holds keys under which facets should be stored in the structure.
Add logic to properly deserialize nested types into proper classes.

Few additional points

attrs are limited to accept attributes names that Python can assign into variables. Therefore, e.g. for my-facet.great key in event payload this is going to be sanitized into my_facet_great and original named would be stored in attr.field(metadata={"name":"my-facet.great"})
above lacks tests
for unresolved types there are basic types created with additional attributes (e.g. run->facets->custom would be RunFacet with some additional attributes)
one can register their own custom facets using utils.register_facet_key to enable richer deserialization
after couple approaches Pydantic didn't turn out to solve issues with deserializing nested fields into proper classes. e.g. anything under run->facets goes into generic RunFacet. After some discussion with @mgorsk1 I still don't see clear way how Pydantic could be significantly better for deserialization task. https://github.com/OpenLineage/OpenLineage/pull/2630#discussion_r1605762463 might work but is complicated and does not leverage to use Pydantic instead

Checklist

[x] You've signed-off your work
[ ] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (not required for changes to tests, docs, or CI config)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2024 contributors to the OpenLineage project

True, pydantic approach, cleaner as it is, hit the same issue attrs approach had and after working on it for quite a while I also did not found quick solution. However, what I think is the root origin of all these issues (both attrs/pydantic) is OpenLineage.json model. For example, the way events are modeled now, there is no connection between any of the facet (like ParentRunFacet, ErrorMessageFacet) and Run.facets object. That's why any approach to turn this model into attrs/pydantic/dataclasses models will require custom workarounds.

What's next? Hope this PR can be reviewed soon.

@JDarDagran does this PR works with Airflow without any particular changes?

In what way it could work/not work with Airflow?
It sure needs extra deserialize - I don't think we want to install cattrs by default.

Airflow integration does not use deserialization, IIRC.
Regarding deserialize extra, this looks great. Could you remove Draft mark, please?


Handling for transaction fee > pool fee

With the new payment code in #207, the pool is going to cover reward payment transaction fees using its own portion of the mining reward. The amount of mining reward claimed by the pool is configurable, any value above zero is allowed. This enables a scenario which is not currently covered - the pool fee is too small to cover the transaction fees. We need special handling for this case because with the current code, no reward payments will ever be sent

The payment code in #207 is still being tinkered with, I initially thought it'd make the most sense to deduct the tx fees from the pool fees collected on the block. But after noticing this issue in your review and thinking about it some more I think the best way to handle it is to have the participating accounts pay transaction fees instead. It is implicit that the pool fee would cover the costs involved in publishing the payout transaction on the network, therefore having the participating accounts pay for it is reasonable regardless of the percentage set for the pool fee. Each participating account will pay a percentage of the transaction fees based on the ratio of the amount it is being paid relative to the total payouts going out to participating accounts.

Yep this seems reasonable to me. This would mean that we need to put some kind of upper limit on the pool fee percentage, at the moment anything under 100% is accepted. We could reduce it to maybe 90%, just to take a potential footgun away from the pool operator.
Would be happy to see the change in a new PR tbh, 207 is already quite big and very nearly complete afaict

Noted, I think we need to discuss that further on what the limits (lower and upper) should be. Also I already worked in the changes into #207 :grimacing:, the tests for payDividends will be in a new PR though.


ENH: Add asset dispatch to data portal.

Combine the equity and future readers into asset dispatch readers, so
that simulations that use both asset types can access data for each.
This patch enables history for future assets in algorithms; however,
it does not add extra coverage in the test_data_portal or test_history
to cover future assets. Those tests will follow, however putting this in
separately since it shows that the wrapping of the readers in the asset
dispatch reader does not break existing equity strategies.

Coverage increased (+0.08%) to 86.394% when pulling 40c7deb697bbcdbe65b5cef33afebd640be3a590 on use-dispatch-reader-in-data-portal into c460af0a400d9fe0de530ca4ebc907e516905e2c on master.

Coverage increased (+0.08%) to 86.394% when pulling 40c7deb697bbcdbe65b5cef33afebd640be3a590 on use-dispatch-reader-in-data-portal into c460af0a400d9fe0de530ca4ebc907e516905e2c on master.

Coverage increased (+0.08%) to 86.394% when pulling 40c7deb697bbcdbe65b5cef33afebd640be3a590 on use-dispatch-reader-in-data-portal into c460af0a400d9fe0de530ca4ebc907e516905e2c on master.


Don't know how to make

Can someone help me out by making a tutorial video?

 Did you check the prerequisites? For devkitPro you can use this link: https://devkitpro.org/wiki/Getting_Started.
What happens when you try to run the makefile?

I'm sorry for bothering you but but I managed to build it

Glad to hear!


Climate docs for generic_thermostat contain invalid default config

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.27.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
climate.generic_thermostat
Description of problem:
Hi,
The component page for climate generic_thermostat is misleading/wrong. As per the blog post for 0.27 release https://home-assistant.io/blog/2016/08/28/notifications-hue-fake-unification/ upgrading is supposed to be as easy as just changing thermostat: to climate:
However, component name has also changed
So instead of
thermostat
  - platform: heat_control

or (as per component docs https://home-assistant.io/components/climate.generic_thermostat/
climate:
  - platform: heat_control

we have to use
climate:
  - platform: generic_thermostat

I'd just create a pull request for docs but currently am away from my home PC.
Expected:
No error during configuration validation when using default config specified on component page

Enter default config from component page
hass --script check_config

Traceback (if applicable):
Testing configuration at /var/opt/homeassistant
16-09-01 02:52:02 ERROR (MainThread) [homeassistant.loader] Unable to find component climate.heat_control
16-09-01 02:52:02 ERROR (MainThread) [homeassistant.bootstrap] Unable to find platform climate.heat_control
Failed config
  General Errors:
  - Platform not found: climate.heat_control

Additional info:

Fixed: https://github.com/home-assistant/home-assistant.github.io/commit/4570ed9e57ffd3ff09e020942447c90b1d2634c2

That was quick, thanks!


MemoryLogger logs whole objects rather than serialized fields

When trying to write unit tests for an ActionType I was surprised that I was getting the logged object in the logger, rather than the serialized form.
I've written a failing test that shows this.
I'm not 100% sure it's a code bug though, because while writing this I found MemoryLogger.serialize, which seems to get me the behaviour I want.  At the very least, it's a documentation bug, because the page on unit testing your logging is silent on the subject of serialization.

I believe this is intentional because it is often useful to have access to the to-be-serialized object rather than the lossy serialized data.
Although being able to test against the serialized task is useful too, which #95 addresses.

Well, there's a serialize method, which would address it too, and with less code than #95. Although it would still need to be documented somewhere other than the source code.
If it's intentional behaviour, then the guide on unit testing your logging should probably be updated.


Cyclic mod dependency

Hi Mlie,
I seem to be getting a cyclic mod dependency warning starting from this mod. When I enable it, several others - Common Ailments (Continued), Emporium (Continued), and Fermenter (Continued) - go red.
Not sure if it's an issue on my end, so I thought I'd let you know.
EDIT: Same with utility supplements. Weird.

Should be fixed now. There were cyclic dependencies between the mods in the patches and I did not notice it.
I have moved all patches to the dependent mod in each case so there should be no problems any more.
Thanks for reporting!

Thank you for all the great work you're doing!

Hi! Still experiencing some issues, this time between Apothecary, Utility Supplements, Medical Supplements and Emporium. I redownloaded them all from GitHub (using GoG version of Rimworld, so no automatic updates for me) and the problem persists. Disabling Apothecary removes the issue, though according to the report, the cyclical dependency starts with Medical Supplements.
Do you think it's a problem on my end?

Im not sure I can replicate this, Here is the mod-order in my test that has no issues:

If you are using the github versions I might suggest using the ModCheck-mod as all my mods have support for it:
https://github.com/KiameV/rimworld-modsync-rw/releases/latest

First of all, thanks for the prompt response. I can't imagine how many questions you get all the time.
Secondly, wow, this ModSync tool is fantastic, thanks. But all my mods were already updated (except SYR_Naga, but it's unrelated.)
Thirdly, unfortunately I'm still getting nowhere. After enabling Medical Supplements, what I'm getting is this:

These mods were fine before enabling Medical Supplements. And enabling Apothecary disables Medical Supplements.
When messing around with load order, I get different errors.
If you're sure your mods are fine, then it's something on my end and I'll bugger off... But I can't think of any particular issue, sorry.

I see, I didnt know you had the other mods as well. Should be fixed now.
Been a few hectic days fixing all 25 mods of pelador so I must have missed testing all together, thanks for reporting!

Again, many thanks for your patience for one random player. I'm also a modder (though not for RW) and I totally get how overwhelming it can be when lots of random people demand a little bit of your attention. :)
I have updated everything I could, but darn, still plagued by various cyclic dependencies. I'll probably drop some mods to avoid the issue - I can live without Common Ailments, for example. But if there's anything I can do to help - provide logs or whatever - please let me know.
BTW is this normal that my ModSyncRW window looks like this?

I'm like 20% down the list, and the list ends... Might be something like that bug with the trade screen when the list disappears after you slide to a certain place?

From what I can see from your update-window the Apothecary-mod is still the first release?
Can you check the Manifest-file or the ModSync-file and verify that it is the 1.0.3-version downloaded?

Apothecary version is <IP_ADDRESS>, according to Manifest.xml.

Great to hear!


Problem while adding resources to container

I am getting an error when adding members to a container:
this code is working completely fine:
@Override
	public void initialize(WriteSession session) {
		LOGGER.info("Initializing Application...");
		try {

			ContainerSnapshot containerSnapshot = (ContainerSnapshot)session.find(ResourceSnapshot.class, this.parkingContainerName,ParkingContainerHandler.class);
			containerSnapshot.addMember(NamingScheme.getDefault().name("test1"));
			containerSnapshot.addMember(NamingScheme.getDefault().name("test2"));
			containerSnapshot.addMember(NamingScheme.getDefault().name("test3"));

			session.saveChanges();
			LOGGER.info("Application initialization completed.");
		} catch (WriteSessionException e) {
			LOGGER.warn("Application initialization failed.",e);
			throw new IllegalStateException(e);
		}
	}

However, just replacing the 3 line for adding members by a loop causes an error:
@Override
	public void initialize(WriteSession session) {
		LOGGER.info("Initializing Application...");
		try {

			ContainerSnapshot containerSnapshot = (ContainerSnapshot)session.find(ResourceSnapshot.class, this.parkingContainerName,ParkingContainerHandler.class);

			int i = 0;
			while (i<4){
				String resourceName = "test"+i;
				containerSnapshot.addMember(NamingScheme.getDefault().name(resourceName));
			}

			session.saveChanges();
			LOGGER.info("Application initialization completed.");
		} catch (WriteSessionException e) {
			LOGGER.warn("Application initialization failed.",e);
			throw new IllegalStateException(e);
		}
	}

When using a loop to add the members, i'm getting the following error:
SEVERE: Exception sending context initialized event to listener instance of class org.ldp4j.server.setup.BootstrapContextListener
java.lang.IllegalStateException: Transient resource should be new
	at com.google.common.base.Preconditions.checkState(Preconditions.java:176)
	at org.ldp4j.application.session.DelegatedWriteSession.newTransient(DelegatedWriteSession.java:309)
	at org.ldp4j.application.session.DelegatedResourceSnapshot.newChildResource(DelegatedResourceSnapshot.java:170)
	at org.ldp4j.application.session.PersistencyState$BasePersistencyState.addMember(PersistencyState.java:247)
	at org.ldp4j.application.session.PersistencyState$PersistentResourceState.addMember(PersistencyState.java:369)
	at org.ldp4j.application.session.DelegatedContainerSnapshot.addMember(DelegatedContainerSnapshot.java:76)
	at org.ldp4j.tutorial.frontend.MyApplication.initialize(MyApplication.java:112)
	at org.ldp4j.application.lifecycle.ApplicationLoader.initialize(ApplicationLoader.java:105)
	at org.ldp4j.application.lifecycle.ApplicationLoader.bootstrap(ApplicationLoader.java:98)

any idea of how I can solve this problem ?
thanks

You are missing the index variable increment (i++) inside the loop, thus you always attempt to add the very same member.
If it had not failed because of that exception, it would have exhausted the heap space and failed with an OutOfMemoryError.

Goodness, frankly, i spent at least 30 mins on this and didn't even see that infinite loop, thanks though !!

You're welcome. Please close the issue if solved.


Ability to disable status + address bar per-website colorization

Is your feature request related to a problem? Please describe.
When Kiwi Browser's theme is set to "System default" or "Light", the status bar and address bar change color to that of whatever website is currently open. For example, https://swappa.com, a predominately green website, makes the status and address bars green.
It can be a little blinding sometimes.

Describe the solution you'd like
A setting to disable the dynamic colorization of the status + address bars.
Describe alternatives you've considered
I can't think of any alternatives at the moment...
Additional context
Kiwi Browser's "Dark" theme solves the problem by simply keeping the status and address bars pure black across all websites, but that's not ideal for the same reasons I had described in #791.

Something similar was discussed in #388
Additionally you can use this extension
https://github.com/d3ward/mti

Additionally i would suggest dev to remove support for  just like Microsoft Edge, DDG..


Remove version: ApeCloud.kbcli version 0.5.0

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

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

Verifying, package is 404.


[CI][MATLAB][Packaging] Update MATLAB CI and crossbow packaging workflows to build against MATLAB R2024b

Describe the enhancement requested
MATLAB R2024b is now available for use with the matlab-actions/setup-matlab GitHub Action.
We should update the matlab.yml CI workflow, as well as the crossbow packaging workflows for the MATLAB MLTBX files to build against R2024b.
Component(s)
Continuous Integration, MATLAB, Packaging

Issue resolved by pull request 44704
https://github.com/apache/arrow/pull/44704


added option to pass redirect_uri

Addresses this issue https://github.com/howdyai/botkit/issues/27

@lambtron #35 is clearly a duplicate of this. Seems like naming is the biggest difference. Do you have any strong opinions about if we should merge this one or #35?

Let's go with this one - though the is one place in the docs that will need to be updated to match the new redirectUri parameter name.


MTK-6771 BLU Vivo XI+ Runtime error - Default config is missing

When running script main.py; the Powershell and the python3 IDLE both produce 2 errors and exits.
python.exe main.py
Error message that I cannot seem to resolve:

python.exe main.py
[2022-07-20 11:20:45.121342] Waiting for device

Environment:
Windows 10 Pro (21H1)
Python 3.10

Steps taken:
Updated pip and installed pyusb pyserial json5
python.exe -m pip install --upgrade pip
pip install wheel
pip install pyusb pyserial json5
OUTPUT:
_> Collecting pyusb

Downloading pyusb-1.2.1-py3-none-any.whl (58 kB)
---------------------------------------- 58.4/58.4 KB 3.2 MB/s eta 0:00:00
Installing collected packages: pyusb
Collecting pyserial
Downloading pyserial-3.5-py2.py3-none-any.whl (90 kB)
---------------------------------------- 90.6/90.6 KB 5.0 MB/s eta 0:00:00
Collecting json5
Using cached json5-0.9.8.tar.gz (22 kB)
Preparing metadata (setup.py) ... done
Building wheels for collected packages: json5
Building wheel for json5 (setup.py) ... done
Created wheel for json5: filename=json5-0.9.8-py2.py3-none-any.whl size=18604 sha256=cdf4e660eb0cf1a08c0028c4a859d633f3d216fdc70fedebacb27c48984a7c07
Stored in directory: c:\users\choll\appdata\local\pip\cache\wheels\71\1a\c7\4fdc7a3d57e8dfa411ad739c67e72c1c8007c0acc95d5b030b
Successfully built json5
Installing collected packages: json5
Successfully installed pyusb-1.2.1 pyserial-3.5 json5-0.9.8
_

Extracted the contents of bypass_utiltiy directly into the python folder
Extracted the exploits directly into the python folder - errored the first time
From power off I held the 'volume down' button, while connecting the USB -C cable
This model seems to want to be3 in test mode to show up

When it does it shows up with the com port as required:

Get it here: https://github.com/MTK-bypass/exploits_collection


Expose SuppressTotals on Sales Order Subform

Describe the request
Please put the "SuppressTotals" boolean on page 46 "Sales Order Subform" as protected so we can excess this via extensions.
This is already the case for the same boolean on page 95 "Sales Quote Subform".
Quote:

Order:

Additional context
We want to disable the totals calculation on order, similar to what we made on quote. Currently we can only hide the fields, but not disable the calculation of them.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 14079.


[contracts] Fixed the bug with transfer value for delegate call

During the implementation of delegate_call, the case with the transfer of native token was missed.
If you transfer tokens to a call that does delegate_call inside, it causes a double-spend(or more if there are many delegate calls).
It is because for delegate_call we add a new frame(like for standard call) and pass value inside. On each new frame, we transfer tokens to the contract's account.
The fix is not to transfer tokens for frames caused by delegate calls.

bot merge


Pyca external test failing due RSA decryption change of behavior

Due to merge of #13817 the pyca external test is now failing on master branch. We need to resolve this urgently as the CI is broken because of that failure.

https://github.com/pyca/cryptography/commit/7e33b0e7739d633c77b8c478620167f693ed13f4 fixed it

Closing as pyca submodule is now updated.


RHBPMS-4526: Test case to reproduce deployment failure of kjar with .…

…bpmn suffix in the artifactId

jenkins retest this

jenkins retest this

jenkins retest this

jenkins retest this


Matching clusters against the NER entities in spaCy pipeline

This is not an issue. Didn't have the discussion option, hence asking this question here.
Is there a way to link the coref clusters to respective entities extracted with NER component? A simple string match/search doesn't work 100%. See the eg. below
Cluster
[{'text': 'Zappos, subsidiary of Amazon,',    'span': (913, 973)},   {'text': 'It', 'span': (2843, 2844)}]
In this case, the cluster entry has 2 entities ("Zappos" and "Amazon"), though it refers to "Zappos".  I would like to link entity "Zappos" to this cluster programatically.
Thanks

Hello, sorry for the late response I was on vacation.
Not sure I got the example you shared. this is the NER outputs? if so can you share NER output, coref outputs and desired outputs?

Hi @shon-otmazgin .  Thanks for the response.
Those were coreference clusters. Below is more detailed example.
from fastcoref import spacy_component
import spacy

nlp = spacy.load("./models/spaCy-en-large-model")
nlp.add_pipe("fastcoref")
text="Zappos, a subsidiary of Amazon, started its online presence in 2011. It expanded outside of Americas in the year 2020"
doc = nlp(text)
doc._.coref_clusters

[[(0, 31), (40, 43), (69, 71)]]
for ent in doc.ents:
    print(ent.text, ent.start_char, ent.end_char, ent.label_)

Zappos 0 6 ORG
Amazon 24 30 ORG
2011 63 67 DATE
Americas 92 100 GPE
2020 113 117 DATE

There is only one cluster in the example. The cluster head  "Zappos, a subsidiary of Amazon," (0,31) has 2 entities Zappos and Amazon. My question was, is there a way to identify that "Zappos" as the entity the cluster is referring to, though the cluster head has 2 entities?

So this is like a nested entity? The model should find also nested entities, can you try to run the LINGMESS model to see if it can predict the nested as well?
Regarding the cluster head - cluster head is not well defined. Some will consider one entity as the head and others something different. I usually takes the shortest entity which is also a Proper Noun, but that's my interpretation.

Yes, this is a nested entity. It can appear in many similar cases. "Jane Doe, supervisor of John Doe" etc.. Let me try LINGMESS. I have found a workaround by finding the main entity using dependency parse tree when more than one entity exists.


Chebi and UniProt API integration

Make requests to chebi and uniprot when initializing an Analyte object for meta data enrichment

resolved by #10


enable LongClistener on fab

Hi, i tried overiding your libray to enable longClickListener on the fab , the use case , i want it to act as a clickable button , so onLongClick --> donot expand --> dosomething (launch activity);
Is it doable ??
Thanks .

Of course it's doable, setOnLongClickListener is useless because i have not handle long click case in AllAngleExpandableButton class. I will study for it and solve the problem, thanks for your suggestion.

good project, I have learned a lot. And i am trying to let the menu item button rotating!


Switched to mainline gpstime (0.6.2) for Windows leap seconds fixes.

This resolves issues downloading/updating the leap seconds file when necessary, particularly on Windows machines.

Note: Holding off on merging this temporarily. gpstime switched to using setuptools_scm in 0.5.0. Unfortunately, setuptools_scm requires a complete git repo, so that means it's no longer possible to pull in our fork of gpstime using an HTTPS archive. Instead, the user is now required to have git installed on their machine.
We can potentially work around this with some complicated hoop jumping for setuptools_scm (https://github.com/pypa/setuptools_scm#git-archives), or by reverting back to hard-coding the version number into our fork of gpstime and removing setuptools_scm, however our remaining changes to gpstime have been submitted to the mainline in https://gitlab.com/jrollins/gpstime/-/merge_requests/1. Once they are merged, we can switch to using that through pip instead. That's preferable.

Update: Our gpstime fixes were mainlined in version 0.6.2 (see https://gitlab.com/jrollins/gpstime/-/merge_requests/1). Switching to version 0.6.2 on PyPI.


ReplyError: ERR unknown command 'time'

I'm getting the following error causing me a fatal error to my app!
ReplyError: ERR unknown command 'time'
at parseError (/myproject/socket-server/node_modules/redis-parser/lib/parser.js:163:12)
at parseType (/myproject/socket-server/node_modules/redis-parser/lib/parser.js:224:14)

I checked my code, but i'm not using TIME directly.
So it's probably more a case inside rsmq.
But with only these two lines of code i, or  the rsmq developer @smrchy (smrchy/rsmq#36), cannot help you.
So please help us and send us mor information.
An example code to reproduce this issue would help us most.

I have stopped using this module for now and create a queuing system in pure js (time was a real constraint!).
I'm using centos and I wonder if there is a minimum version number of redis that I should be running:
`[root@XXXXXXXXXXXX ~]# yum info redis
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile

base: mirror.vorboss.net
epel: mirrors.ircam.fr
extras: mirror.vorboss.net
updates: centos.hyve.com
Installed Packages
Name        : redis
Arch        : x86_64
Version     : 2.4.10
Release     : 1.el6
Size        : 668 k
Repo        : installed
From repo   : epel
Summary     : A persistent key-value database
URL         : http://redis.io
License     : BSD
Description : Redis is an advanced key-value store. It is similar to memcached but the data
: set is not volatile, and values can be strings, exactly like in memcached, but
: also lists, sets, and ordered sets. All this data types can be manipulated with
: atomic operations to push/pop elements, add/remove elements, perform server side
: union, intersection, difference between sets, and so forth. Redis supports
: different kind of sorting abilities.
`

Well, rsmq uses the TIME command.
http://redis.io/commands/time
As you can see this is available sind 2.6.0. You seem to be running 2.4.10 which is really old (from 2012). You should consider upgrading. Then maybe give rsmq another try.

Ok, that is fine, I'll have to resolve this. On the readme, could there please be a min requirement section that states the minimum redis version?

The main RSMQ repo has this Note. Added it to rsmq-worker as well.


Implement ZipkinService getTraceId functionality

Original work from https://github.com/slackhq/kaldb/pull/348
We should be able to visualize logs as traces in grafana. Not all log types will load currently because we don't ensure that all logs ingested have certain mandatory fields. However this is a best effort and has been tested locally with api-log E2E.
We might have to make minor edits for other log types to work but adding the required mandatory fields.

for the enum comment, I can't seem to reply on it but check out the post which has 144 upvotes on https://stackoverflow.com/questions/604424/how-to-get-an-enum-value-from-a-string-value-in-java . We use the same strategy here


Add architecture document

One of the Storybook maintainers asked for some details of how the Vite builder works, so I thought I'd take the chance to write up a bit of a document that might help other contributors start to understand how the code works.
It's still a WIP, but I'm opening the PR now so that @jonniebigodes can refer to it, and will have updated changes as I push them up.

Awesome!

@IanVS and @joshwooding I'm taking a pass at the docs and polishing them a bit if both of you are ok with it so that it not only helps me but also new contributors. I'll let you know once the changes are up so that we can continue to work on this. Sounds good?
Hope both of you have a great weekend!

@jonniebigodes Sounds good :)

@jonniebigodes what is the current status on this?

@IanVS, this is not forgotten. I just hadn't had the time to follow up on it. Next week when I come back, I plan on going through it and updating it. I'll ping you, and we can discuss it a bit more. Sounds good?

I'll just close this out, it's sat for too long, and it seems to be blocked on a review.


ZF2 fix #6725

@Qronicle ping... we need unit tests before we can merge.

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html
New issue can be found at: https://github.com/zendframework/zend-validator/issues/100


⚠ Bofrost.be has degraded performance

In e2f7795, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 882 ms

Resolved: Bofrost.be performance has improved in e13006c after 15 minutes.


ESP8266<->PZEM004T

Thanks heaps for your contribution.
I've managed to get it working with ESP8266, software serial works but i get a lot of "stack" info and the frequent Soft WDT reset  interrupts other operations related to wifi connection.
giving hardware serial a shot, believe the RX, TX pins for ESP8266 is 1,3 i've tried those (edited PZEM004T.CPP to accommodate that), i get correct reading sometimes, the rest is just -1.
 It can't read the voltage or anything please you tell how to connect this 2 module pls.


fixes #329 and #294

I don't understand why this fails, but I'm sure I found the root cause of the issue.
Perhaps this facilitates a proper fix from someone more knowledgeable than me.

Ahh, the first failures are because of additional newlines (test_anchor_only_link, Test absolute image URL's are correct for different base_urls, Test relative image URL's are the same for different base_urls)...
The 4 tests regarding the TOC may well fail since I changed a bit in that area, leaving Ensure that basic Markdown -> HTML and TOC works and Ensure that the fenced code extension is supported to be looked into...

Yup, looks like two new newlines at the start and the one at the end has been removed. Just updating the expected test output will be fine.

Looking again, there are some more serious failures. For example, in this test we have lost the full table of contents, which is the same problem that @jdhoek had in #294.
======================================================================
FAIL: test_flat_toc (mkdocs.test.TableOfContentsTests)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/travis/build/tomchristie/mkdocs/mkdocs/test.py", line 212, in test_flat_toc
self.assertEqual(str(toc).strip(), expected)
AssertionError: '' != 'Heading 1 - #heading-1\nHeading 2 - #heading-2\nHeading 3 - #heading-3'

In test.py (line 183), the order of variables needs to be reversed for post_process just like in build.py.

Fixed that, two more to go:
Ensure that basic Markdown -> HTML and TOC works. fails because somehow a
page_title: custom title
\n is inserted, must be some meta-related issue.
And fenced codeblocks fail, too:

print 'foo'
" != "
print 'foo'\n
"...
Working on it.

Where is the source file index.md that's used in test_copying_media?

The index.md file doesn't actually exist. It is essentially a mock or fake project.

4 failures and 1 error remain...
Failures

test_anchor_only_link
Test absolute image URL's are correct for different base_urls
Test relative image URL's are the same for different base_urls
test_dont_convert_code_block_urls

The first 3 are just about newlines and can be adapted later.
Error

test_copying_media

So that leaves us with one error and one failure, both of which I don't fully understand :-(

I've taken a look, but I can't see the issue obviously. I guess I'd need to take a look at the footnotes extension and see what is going wrong.

On a sidenote: It seems we don't need to care about inserting a [TOC] tag. From the toc extensions' documentation (https://pythonhosted.org/Markdown/extensions/toc.html):

If a marker is not found in the document, then the Table of Contents is available as an attribute of the Markdown class.

Footnotes are no longer an issue after applying #331


.xprr on multiple servers conflict issues.

I'm running a self hosted nadeko bot for a couple of servers I have, but the .xprr command seems to have issues across the two servers.
If I add '.xprr 5 Social' to server A, you can't add it to server B without an exception. .xprrs on server B doesn't show the role added. Also, removing a role from a level seems to prevent it from being re-added.
Stacktrace for Adding a role that exists on another server:
18:35:44 CommandHandler | Microsoft.EntityFrameworkCore.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> Microsoft.Data.Sqlite.SqliteException: SQLite Error 19: 'UNIQUE constraint failed: XpRoleReward.Level'.
   at Microsoft.Data.Sqlite.Interop.MarshalEx.ThrowExceptionForRC(Int32 rc, Sqlite3Handle db)
   at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.Execute(IRelationalConnection connection, String executeMethod, IReadOnlyDictionary`2 parameterValues, Boolean closeConnection)
   at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.ExecuteReader(IRelationalConnection connection, IReadOnlyDictionary`2 parameterValues)
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection)
   --- End of inner exception stack trace ---
   at Microsoft.EntityFrameworkCore.Update.ReaderModificationCommandBatch.Execute(IRelationalConnection connection)
   at Microsoft.EntityFrameworkCore.Update.Internal.BatchExecutor.Execute(Tuple`2 parameters)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(IReadOnlyList`1 entriesToSave)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.SaveChanges(Boolean acceptAllChangesOnSuccess)
   at Microsoft.EntityFrameworkCore.DbContext.SaveChanges(Boolean acceptAllChangesOnSuccess)
   at NadekoBot.Modules.Xp.Services.XpService.SetRoleReward(UInt64 guildId, Int32 level, Nullable`1 roleId) in /root/NadekoBot/src/NadekoBot/Modules/Xp/Services/XpService.cs:line 287
   at NadekoBot.Modules.Xp.Xp.<XpRoleReward>d__5.MoveNext() in /root/NadekoBot/src/NadekoBot/Modules/Xp/Xp.cs:line 80
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Discord.Commands.ModuleClassBuilder.<>c__DisplayClass6_1.<<BuildCommand>g__ExecuteCallback1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Discord.Commands.CommandInfo.<ExecuteAsyncInternal>d__41.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Discord.Commands.CommandInfo.<ExecuteAsyncInternal>d__41.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Discord.Commands.CommandInfo.<ExecuteAsyncInternal>d__41.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Discord.Commands.CommandInfo.<ExecuteAsync>d__40.MoveNext()

Ok it has nothing to do with corss server. It's just the fact that you can't readd the same role even after you removed it. Extremly odd.  I will fix it right away.

just fixed.


feat: allow working directory for Pulumi

@TriPSs this is now ready for review and merging.
I ended up with the simple approach. No change to the generators for now, might add that later. But for now I only need this for one of my projects, so I'll just update that one when this is merged.

Oh, I see a compile issue. Let me fix that.

There we go @TriPSs!

Thanks!


a-rate param

Should consider changing detune and frequency to a-rate params.
It highly depends on audio-through implementation, though.

Best way to do that is passing function to options like so
let oscillate = require('audio-oscillator')({ frequency: (i, t) => v  })

Covered by #20


Repository REST API

I'd like to be able to have a repository accessible via REST APIs rather than a signed MSIX package.
The API will need a full design. This will also have an impact on client behavior. The MSIX index package can become a backup mechanism if the APIs are offline, or the client is unable to connect.
Notes:
The client needs to be able to get the list of packages to enable "search"
The client needs to be able to get the manifest so it can "install"
This implies that the client will build a local cache of packages after retrieving the list so they can perform a local search.
In the future we may create a web based search API (TBD).
The contents of the Microsoft Community Package manager should be available via this API once it's built.

This aspect is super interesting to those of us in orgs that build and deploy internally built software.
As someone who has to manage chocolatey infrastructure: please please please keep this design simple.
As an operator I would love to be able to run a tool over "packages" to generate a static website. Assuming the API is of trivial complexity, the server might be about 20 or 30 lines of code in Go or I could use something like apache or nginx to serve the content. I could more easily leverage a CI/CD system to handle rebuilding the repo metadata when there is a change.
For example we looked into sleet but chocolatey speaks an older dialect of nuget and that ended up being non-viable.
I think other package managers like RPM and apt are great examples to draw inspiration from.
The tools for repo management should ideally be cross-platform so we could build or manage changes to repo metadata on either POSIX-based OSes or Windows.

@svmastersamurai That's great feedback. I like the idea of running the tool over the packages. Would you think in terms of UNC style path's to the binaries or would HTTP still be OK?
I'm thinking about a concept where you might have the installers in a structure that looks like the manifests directory in the repository here, and then having the manifests able to co-locate in the same structure. If the installers are MSIX, we can pull nearly all of the meta-data to generate the manifest based on what is found.

@denelon I think to generate a static website that makes perfect sense. This assumes that there will be adequate saturation of MSIX usage of course! There are a lot of legacy installers out there, so would this be able to also handle the usual suspects we know about?
Our team manages multiple operating systems so we tend to prefer HTTP since it is usable cross platform. We use the same webservers to serve installers for Windows that we do for Munki packages on MacOS and RPMs for our fedora fleet.
One thing we do for redundancy is have a few locations to retrieve the installers from. It appears the package spec supports this, so from a tooling perspective if I have 5 mirrors with different hostnames it would be nice to be able to have the tool aware of the mirrors (in a simplistic sense, I can just give it a list in a file for example) and be able to append those sources to the specs if they don't exist. From the winget-cli's perspective it could cycle through the mirrors until it finds one that is accessible. This would probably lead to templating within the package spec, which I admittedly haven't dived too much into this project to know if that's supported or if there was a plan for that already :smile:.

As an operator I would love to be able to run a tool over "packages" to generate a static website.

This deserves a separate ticket IMO and has nothing to do with REST interface to repository. Such tool would indeed be great for multiple reasons, one of which is that it allows anybody to keep their public list of packages and host it anywhere (i.e. github pages and friends).
Such tool might not be practical in producing all desired functionality of REST backend such as versioning and dependencies although it could go long way into that direction.

We are actively working on the REST API and our initial implementation in the client. The schemas for validating the new YAML syntax have been checked in, but may very well churn a bit. https://github.com/microsoft/winget-cli/tree/master/schemas/JSON/manifests/v1.0.0
The REST API will have it's own object structure, but is expected to be essentially conforming to the same meta-data.

We have a prototype with install and search. The Windows Package Manager v0.2.10771 Preview has an experimental implementation for install and search. As soon as we round out the other commands, we will share the swagger YAML.

I was wondering, in this first pass of the API spec, is there anything about authentication? Something that would be a dream feature is if there is a way it can use Azure AD SSO (or another SSO provider that uses the Windows Credential Provider API) to authenticate, so that we don't have to have the repo open to everyone on the network (or the internet). For now, of course, we could probably use the custom headers stuff to send a secret we get some other way, but at some point it would be nice to have something a bit more robust.

@jedieaston we don't currently have anything for authentication in the API yet. We've had several different suggestions for which mechanisms to use. I expect to create an "Issue-Feature" as soon as we open up the reference implementation repository. This is clearly a high-value use case. We do have a "getInformation" endpoint to query a source for the protocol versions supported. This may be a reasonable place to provide authentication mechanisms as well.

Hi @denelon
Is there any documentation to use Rest API?

It's coming soon [TM] with a reference implementation.

Thanks, where can we find the documentation when it was published?

It's another GitHub repository. I'll have copious documentation updates to make as soon as we flip the repository to public, Think in terms of days not weeks. It does include Swagger documentation.

@ghost1372 https://github.com/microsoft/winget-cli-restsource is where the reference implementation is.

Thank you❤

Hi @denelon, may I ask out of curiosity what the motivation for the REST API is vs. a UNC source of offline manifest files (#160)? What I don't understand is that it seems to me that a UNC source will always be easier to create and deploy than a REST API. What does the REST API give us in return, in terms of use cases that can be implemented?
Thank you!
Michael

@mherrmann we had more asks for a REST API during early feedback cycles with Microsoft MVPs and ISVs than a UNC implementation. The two primary use cases at the time were hosting repositories for software distribution by ISVs (to the public), and enterprise customers hosting internal repositories for a distributed workforce.

@denelon I see, thank you very much for the prompt response. I am working in a tangential space and would love to get a better feel for the industry opinion. Is there any chance the feedback cycles you mentioned are public or documented somewhere? If not, can you recommend people (eg. Microsoft MVPs) I might reach out to to find out more?
Thank you again!
Best,
Michael

@mhermann those early discussions were under NDA before the preview launched. I'd be willing to reach out via Twitter if you have some specific questions to get some feedback.

@denelon I understand, and thank you. I'd like to understand why people asked for REST APIs, when static files would be easier to host. I would love to understand which features people want that require a dynamic approach such as REST and cannot be implemented with static files.
My twitter is @m_herrmann. Thank you :pray:


refactor - remove Computed in favor of FinalStates

Remove Computed in favor of FinalStates,  as FinalStates is less error prone.
before:
Computed2<String, String, String>(
  name: 'computed',
  statesName1: 'states1',
  statesName2: 'states2',
  compute: (scope, it1, it2) {
    return '$it1|$it2';
  },
)

after:
FinalStates(
  name: 'computed',
  equal: (scope) => States.combine2<String, String, String>(
    states1: scope.get(name: 'states1'),
    states2: scope.get(name: 'states2'),
    combiner: (it1, it2) {
      return '$it1|$it2';
    },
  ).distinct(),
)

We first add @experimental annotation to Computed and test if it need to be removed.


[no jira][risk=no] update swagger to the latest

Addresses
Update to the latest swagger ui

Closing until tests can be sorted out more cleanly


Integration test flaky

The deploy test failed once, in teardown:
• Failure in Spec Teardown (AfterEach) [30.040 seconds]
Deploy
/home/mm/go/src/code.cloudfoundry.org/cf-operator/integration/deploy_test.go:8
  when correctly setup
  /home/mm/go/src/code.cloudfoundry.org/cf-operator/integration/deploy_test.go:9
    should deploy a pod [AfterEach]
    /home/mm/go/src/code.cloudfoundry.org/cf-operator/integration/deploy_test.go:17

    Expected error:
        <*errors.errorString | 0xc0000b38e0>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    not to have occurred

Can reproduce here:
$ time while make test; do echo next; done

• Failure in Spec Teardown (AfterEach) [42.934 seconds]
Deploy
/home/ettore/_git/cf-operator/integration/deploy_test.go:8
  when correctly setup
  /home/ettore/_git/cf-operator/integration/deploy_test.go:9
    should deploy a pod [AfterEach]
    /home/ettore/_git/cf-operator/integration/deploy_test.go:17

    Expected error:
        <*errors.errorString | 0xc0000c5900>: {
            s: "timed out waiting for the condition",
        }
        timed out waiting for the condition
    not to have occurred

    /home/ettore/_git/cf-operator/integration/deploy_test.go:14


Load position problem at the silos.

Load position problem at the silos.
The vehicle stops before reaching the correct position, to load the trailer, it seems that it calculates the nose of the tractor and not the trailer.
I tried in various ways, modifying the track, target point, but nothing to do. See photo

Is this a vanilla silo or barn or a mod?

Is this a vanilla silo or barn or a mod?

This is a mod, but today I have to do some more tests, since yesterday evening, with another trailer, also a mod, it unloaded and loaded regularly. I have the impression that it is related to the type of trailer, the one that worked unloads only from the back, while this little green one, original trailer, can unload also laterally.

I made a video, to try to show you what happens, I activated the debug, and did various tests, where as you can see, with a tractor (original) it always gets stuck in that position, while with the other, sometimes it works sometimes not, and finally I did a loading and unloading on the other silo, which are then identical, only the product changes, and as you can see in that one there are no problems. I also attach the log, and I add that, by activating the debug, then the game gets stuck in the closing phase, another problem, which however does not compromise the regular functioning. https://drive.google.com/file/d/17hFefIBV_XGryofZ3WAGXdt0Atm3dILX/view?usp=sharing

@Roby1164 the link requires me to request access. Please make the video publicly accessible.

I came across a similar but maybe not the same issue (I am not sure).
It happens to me with FED Mods Multisilo 4000. The tractor stands in front of the passing through and does not move any further. As soon as I deactivate the collision detection the tractor starts moving and after hitting the tricker the unloading process starts. It look like that auto drive is afraid of a possible collision although the route has enough space for the passing through.

@Roby1164 the link requires me to request access. Please make the video publicly accessible.

it is shared with everyone, but lately google drive, has some problems, since they changed the rules and some parameters.
Retry

After further tests, I found that the problem only occurs with some vehicles combined with some trailers, now I'm using another tractor with the same trailers and it seems to work.... I don't understand where the problem is, perhaps as floggydev said, it could be related to the collision detection, which on some vehicles gives problems...

I am using Fendt 1050 and Fendt Tigo 75 VR D both vanilla.

i was having the same problem with multiple vehicles and found a work around by turning off collision detection in the settings menu.

One problem is, that some modders seem to use wrong/outdated collision bits and therefore AD stops in front of the triggers. That's not an AD problem and the modders have to fix it.
If a Vanilla vehicle combination has a problem with a Vanilla silo, then please comment the whole vehicle combination here so that we check it: front weight, tractor, wheels with weights, trailer, etc.

Thanks for clarification, @Iwan1803.

One problem is, that some modders seem to use wrong/outdated collision bits and therefore AD stops in front of the triggers. That's not an AD problem and the modders have to fix it.
If a Vanilla vehicle combination has a problem with a Vanilla silo, then please comment the whole vehicle combination here so that we check it: front weight, tractor, wheels with weights, trailer, etc.

I don't think the problem is with the silo mod, but with the vehicle collision zone, which I don't know if it's for AD or the Giants one, in fact some vehicles and trailers have the problem while others don't, and then it's also random, sometimes they pass and do the job, while sometimes the same vehicle/trailer gets stuck. It seems like it's the pavement, the possible small difference in height. However, if we remove the collision detection from AD, which I still haven't understood if with that NO, it switches to a Giants collision detection or is deactivated completely, the problem disappears.
As soon as I can, I'll try to do a test with a vanilla silo...

Trust me: there are silo mods with wrong collision bits 😉
Also AD doesn't generate collision boxes by itselfe but uses the one from the vehicles.
If the same vehicle can drive to the trigger and sometimes not, then it maybe could be a problem of new terra forming from Giants. This also causes sometimes that waypoints slide into the ground or float in the air during creation. It's really strange...
Next time if a vehicle stops in front of the silo then try to change the collision height detection. Standard should be 0.5.
One last hint: if you hover with the mouse cursor over an AD option, a help text should appear next to it....

Trust me: there are silo mods with wrong collision bits 😉 Also AD doesn't generate collision boxes by itselfe but uses the one from the vehicles. If the same vehicle can drive to the trigger and sometimes not, then it maybe could be a problem of new terra forming from Giants. This also causes sometimes that waypoints slide into the ground or float in the air during creation. It's really strange... Next time if a vehicle stops in front of the silo then try to change the collision height detection. Standard should be 0.5.
One last hint: if you hover with the mouse cursor over an AD option, a help text should appear next to it....

Look here, if it can help you understand the problem.

@Roby1164 please reproduce the issue with a vanilla tractor, vanilla trailer and a vanilla silo.
Also, you still have not told us what kind of modded silo this is, so there is nothing we can do at this point.

Also, this might be related (and fixed by) #53

@Roby1164 please reproduce the issue with a vanilla tractor, vanilla trailer and a vanilla silo. Also, you still have not told us what kind of modded silo this is, so there is nothing we can do at this point.

The tractor and trailer are vanilla, while the silo is a mod, but nothing special, it is a drying silo, you put the grass and unload the hay, it has the same parameters as the vanilla silos. But there is a fact that leaves me perplexed, the strange fact is that, if it were a collision problem, it should be easier for the large trailer to have it, and not the small one, instead here the opposite happens, and it is always the small one that has the problem, a problem that I have partially solved, by slightly moving the path outwards (to the left in this case) in this way the problem does not arise, and the trailer proceeds and unloads/loads without problems. in this way, however, the small trailer, unloads laterally, since it has this possibility, while the large trailers, which unload only from the back, have difficulty unloading. and often stop not finding the unloading trigger. Today I will try with that modification you made, to see if it solves the problem.

Closing the ticket because the reporter is unwilling to share basic information we requested


Expanding Deep links by default

Submitting a deep link query to Bloom, is there a way to have the found node(s) appear totally expanded without user interaction (i.e. user does not have to hit return to see the resulting graph)?

hi @peterkva. We have gotten this request before but we are a bit worried because of security reasons.

Can you clarify a bit on what the security concerns are?
Also, does this mean that this feature is not planned to be implemented?

The main security concern is that running any kind of cypher using a search phrase could lead to undesired effect on the database, like destroying data. Forcing return we have better control of the type of the queries defined by the users. Currently, we don't have this feature in our roadmap but we continuously check the popularity of the users issues and reconsider including them in future implementations.

This has been possible since 1.5.1 by adding the query parameter run=true. Closing


Fix code to work with mashumaro 3.15

Resolves #11044
Problem
Mashumaro 3.15 caused some breakages in our code.
Solution
In a couple of cases, Unions had to be adjusted to de-serialize and serialize in the right order. Most of the effort went into refactoring the update node config code so that "from_dict" was not performed until after validation, so that config values were not converted to valid forms prior to being validated.  In general the pattern is that all sources of configs should be combined as dictionaries, then validated, then used to construct a valid config object.
dbt-common BaseConfig.update_from method had to be converted to a class method and the "from_dict" removed.
Since there were already a bunch of changes in core/dbt/context/context_config.py, I also took the opportunity to rename ContextConfig to ConfigBuilder, and replace variables and parameters using it in the rest of the parsing codebase.
Since the hooks needed to be fixed prior to validation in generate_node_config, I moved the hook fixing method to context_config.py and removed it from parser/base.py.
Checklist

[x] I have read the contributing guide and understand what's expected of me.
[x] I have run this code in development, and it appears to resolve the stated issue.
[x] This PR includes tests, or tests are not required or relevant for this PR.
[x] This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
[x] This PR includes type annotations for new and modified functions.

Also see https://github.com/dbt-labs/dbt-common/pull/228

https://github.com/Fatal1ty/mashumaro/issues/269


issue template for documentation

Signed-off-by: R.I.Pienaar<EMAIL_ADDRESS>

Anything else you'd like to prompt for in the new doc requests @ColinSullivan1 @gcolliso ?