hike dependency

Hi. I have the following error when running some RSpec specs:
[~/stormz (myworkshops *$% u=)]$ rspec spec/controllers/items_controller_spec.rb
/home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rack-1.3.4/lib/rack/backports/uri/common_192.rb:53: warning: already initialized constant WFKV_
/home/jd/.rvm/gems/ruby-1.9.2-p290@global/gems/activesupport-3.1.0/lib/active_support/dependencies.rb:240:in `require': no such file to load -- hike (LoadError)
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@global/gems/activesupport-3.1.0/lib/active_support/dependencies.rb:240:in `block in require'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@global/gems/activesupport-3.1.0/lib/active_support/dependencies.rb:225:in `load_dependency'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@global/gems/activesupport-3.1.0/lib/active_support/dependencies.rb:240:in `require'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/sprockets-2.0.0/lib/sprockets/environment.rb:8:in `<top (required)>'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@global/gems/actionpack-3.1.0/lib/sprockets/railtie.rb:20:in `block in <class:Railtie>'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/railties-3.1.0/lib/rails/initializable.rb:25:in `instance_exec'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/railties-3.1.0/lib/rails/initializable.rb:25:in `run'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/railties-3.1.0/lib/rails/initializable.rb:50:in `block in run_initializers'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/railties-3.1.0/lib/rails/initializable.rb:49:in `each'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/railties-3.1.0/lib/rails/initializable.rb:49:in `run_initializers'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/railties-3.1.0/lib/rails/application.rb:92:in `initialize!'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/railties-3.1.0/lib/rails/railtie/configurable.rb:30:in `method_missing'
	from /home/jd/af83/ucengine-storm/config/environment.rb:5:in `<top (required)>'
	from /home/jd/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /home/jd/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /home/jd/af83/ucengine-storm/spec/spec_helper.rb:7:in `block in <top (required)>'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/spork-0.9.0.rc9/lib/spork.rb:24:in `prefork'
	from /home/jd/af83/ucengine-storm/spec/spec_helper.rb:4:in `<top (required)>'
	from /home/jd/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /home/jd/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
	from /home/jd/af83/ucengine-storm/spec/controllers/items_controller_spec.rb:1:in `<top (required)>'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/configuration.rb:419:in `load'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/configuration.rb:419:in `block in load_spec_files'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/configuration.rb:419:in `map'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/configuration.rb:419:in `load_spec_files'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/command_line.rb:18:in `run'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/runner.rb:80:in `run_in_process'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/runner.rb:69:in `run'
	from /home/jd/.rvm/gems/ruby-1.9.2-p290@ucengine-storm/gems/rspec-core-2.6.4/lib/rspec/core/runner.rb:11:in `block in autorun'

I added hike in my Rails's Gemfile and the spec runs fine. Is there any missing dependency on sprocket?

Nope:
https://github.com/sstephenson/sprockets/blob/master/sprockets.gemspec#L12


WindowShouldClose(), reset shouldClose flag when window is inited

Similar issue with: https://github.com/raysan5/raylib/pull/3410
Window shouldClose flag does not reset after closing and opening another window. So for the subsequent windows WindowShouldClose always return true.

This was a regression with platform split work. In version 4.5.0, desktop platform even reset the flag just after the WindowShouldClose. So it was possible to ignore the flag and continue next frame. But that was not consistent with other platforms. So I hope this little change is fine.

@maksut thanks for the review!


added Encoding property for consoleTarget + ColorConsoleTarget

Closes #676
No unit tests added as it is a small addition.
The property has a side effect (static property on Console), but I think we can live with that.

Looks good, but I think the using should be moved inside the !IF SILVERLIGHT block like the rest of them

I will update my PR.

@Xharze I don't understand your comment I think:

ColoredConsoleTarget is already in #if !SILVERLIGHT
Encoding is available in Silverlight? (see FileTarget) - for ConsoleTarget

I've tried to add as a line comment :)

Thanks, I fixed it :)
Including also some doc/newlines stuff


implement post training

Does this look right?

So the purpose of post_training is to recreate the original module with the trained weights. Ideally, you would add an original_class variable to the __init__ and save that for later. Then once you are done training, post_training is called to make your checkpoint compatible with the original model - so the idea here would be that original_class=MixtralSparseMoeBlock.

Is this closer?

Can you provide more details please about what this solves? Sorry that I'm not understanding from the provided changes et.

@winglian this is supposed to solve the conversion back from the fused MoE into the original architecture.

I am trying to help get the branch to a usable state because I wanna start training a model with it


Status: Published showing for published documents despite saving new drafts

Link to reproduction
No response
Environment Info
Binaries:
Node: 22.6.0
npm: 10.8.2
Yarn: 1.22.22
pnpm: 9.7.1
Relevant Packages:
payload: 3.0.0-beta.111
next: 15.0.0-canary.173
@payloadcms/db-mongodb: 3.0.0-beta.111
@payloadcms/email-nodemailer: 3.0.0-beta.111
@payloadcms/graphql: 3.0.0-beta.111
@payloadcms/live-preview: 3.0.0-beta.111
@payloadcms/live-preview-react: 3.0.0-beta.111
@payloadcms/next/utilities: 3.0.0-beta.111
@payloadcms/plugin-cloud: 3.0.0-beta.111
@payloadcms/plugin-cloud-storage: 3.0.0-beta.111
@payloadcms/plugin-form-builder: 3.0.0-beta.111
@payloadcms/plugin-nested-docs: 3.0.0-beta.111
@payloadcms/plugin-redirects: 3.0.0-beta.111
@payloadcms/plugin-seo: 3.0.0-beta.111
@payloadcms/richtext-lexical: 3.0.0-beta.111
@payloadcms/storage-vercel-blob: 3.0.0-beta.111
@payloadcms/translations: 3.0.0-beta.111
@payloadcms/ui/shared: 3.0.0-beta.111
react: 19.0.0-rc-3edc000d-20240926
react-dom: 19.0.0-rc-3edc000d-20240926
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 23.5.0: Wed May  1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020
Available memory (MB): 16384
Available CPU cores: 12
Describe the Bug
When saving a draft of an already published document, the document status in the CMS is showing Published instead of Changed. This is also making it so that the document cannot be published without making further changes.
https://github.com/user-attachments/assets/f1dd203e-1556-42de-83ff-5d891502e7fa
Reproduction Steps

Navigate to the edit view of an already published document
Edit the document and save a draft
See status shows "Published" and the publish button is disabled.

Adapters and Plugins
db-mongodb, storage-vercel-blob, richtext-lexical, plugin-seo, plugin-redirects, plugin-form-builder, email-nodemailer

With SQLite (same environment) it will always auto save, whether you just opened it or just published, it still auto saves and shows it as changed. Worse yet, if you open a collection/global and it auto saves before the fields load the data it's overwritten as empty or partial data.

I am unable to recreate this issue, I believe I am following the steps outlined above.
https://github.com/user-attachments/assets/1209c0e4-fa19-4b85-b346-1ff111edbd4c

I guess ignore my comment on this. It was about publishing not saving drafts and made a separate issue.

@JarrodMFlesch I'm going to close this as I think it's being caused by some version documents that have objectID type IDs and some with string, both with latest: true. This was something I saw in our website, and we had ran into other issues with that and I think the database just needs to be cleaned up a bit. I'll reopen if it persists.


Expose Button/Axis ID value

This makes it substantially easier to work with the new API.

Is this blocked on something?

Closing in favor of #211


Demo no working

Hi, I am trying test your angular carrousel component  but right now not working, the output error is:
Unhandled promise rejection  TypeError: r.scriptLanguage is undefined Stack trace: generateConfig@https://c.staticblitz.com/assets/engineblock-bc7b07e99ec5c6739c766b4898e4cff5acfddc137ccb7218377069c32731f1d0.js:3:13655 start@https://c.staticblitz.com/assets/engineblock-bc7b07e99ec5c6739c766b4898e4cff5acfddc137ccb7218377069c32731f1d0.js:3:22715 me@https://c.staticblitz.com/assets/preview-fe7237b13d780dbf847da.js:1:23893 [1262]/window._preboot/<@https://c.staticblitz.com/assets/preview-fe7237b13d780dbf847da.js:1:24408 u@https://c.staticblitz.com/assets/common-dd6c1ca1865a48151a33a.js:1:23777 T/<@https://c.staticblitz.com/assets/common-dd6c1ca1865a48151a33a.js:1:23899 f@https://c.staticblitz.com/assets/common-dd6c1ca1865a48151a33a.js:1:26604
Test in Mozilla 60.0.2

@CarMoreno Hi,
try this https://stackblitz.com/github/sheikalthaf/ngu-carousel

@sheikalthaf thanks, this new link working.


fix: trigger

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ACMEv1 is disabled - Upgrade to ACMEv2?

I have this error:
Error occurred: Status: 403, Detail: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details., Type: urn:acme:error:unauthorized

i have same error in whm

We have all same error,
Please update it

We have all same error,
Please update it


Revert "[#1009] [graph] bug fix on layer names "

Reverts nnstreamer/nntrainer#1013

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #1021. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

To contributor, We have used 'Signed-off-by:' notation by default to handle the license issues, that result from contributors. Note that 'Is there a Signed-off-by line?' is important because lawyers tell us we must have to it to cleanly maintain the open-source license issues even though it has nothing to do with the code itself.

:octocat: cibot: @nnstreamer, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.


UIDocumentInteractionController menu does not dismiss.

Description:
I have an issue with UIDocumentInteractionController which is used to open a PDF document.
The problem at this point is when user interacts with the menu my clicking on the Open in {app_name} action, the menu itself fails to close after user interaction leaving the menu open when user comes back to the app.
Dismissing the menu at this point requires user to tap twice on the X in order for menu to be dismissed.
I also tried to close the menu dynamically when app returns to active state by running dismissMenuAnimated on UIDocumentInteractionController instance but it does not work in this case, it does however dismiss the dialog if no interaction was made on it and the method is called.
One note, this issue is only present on never iOS version 13+. On older OS the menu is closed after interaction as expected.
React Native version:
System:
    OS: macOS High Sierra 10.13.6
    CPU: (4) x64 Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
    Memory: 34.29 MB / 4.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 8.3.0 - ~/.nvm/versions/node/v8.3.0/bin/node
    npm: 6.8.0 - ~/.nvm/versions/node/v8.3.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
  IDEs:
    Xcode: 10.1/10B61 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5
  npmGlobalPackages:
    create-react-native-module: 0.13.0

Steps To Reproduce
It can be reproduced by using the function provided by the module rn-fetch-blob module.
https://github.com/joltup/rn-fetch-blob/wiki/iOS-API#iosopendocumentpathstring
I also tried different approach by writing by own code which has the same result.
@property (nonatomic, strong) UIDocumentInteractionController *documentInteractionController;
@property (atomic) CGRect rect;

RCT_EXPORT_METHOD(openDocumentInteractionControllerWithFileURL:(NSURL *)fileURL){
    if (!fileURL) {
        // Return NO because there was no valid fileURL.
        return;
    }

    UIViewController *rootCtrl = [[[[UIApplication sharedApplication] delegate] window] rootViewController];

    // Open "Open in"-menu
    self.documentInteractionController = [UIDocumentInteractionController interactionControllerWithURL:fileURL];
    self.documentInteractionController.delegate = self;

    BOOL sucess; // Sucess is true if it was possible to open the controller and there are apps available

    sucess = [self.documentInteractionController presentOpenInMenuFromRect:self.rect inView:rootCtrl.view animated:YES];

    if(!sucess){
        // Inform app that the activity has finished
        // Return NO because the service was canceled and did not finish because of an error.
        // http://developer.apple.com/library/ios/#documentation/uikit/reference/UIActivity_Class/Reference/Reference.html
    }
}

RCT_EXPORT_METHOD(dismissDocumentInteractionController){
    // Hide menu
    [self.documentInteractionController dismissMenuAnimated:YES];
}

Expected Results
The menu should be dismissed after any user interaction.

If I'm understanding correctly, this isn't a problem with [rn-fetch-blob]https://github.com/joltup/rn-fetch-blob/wiki/iOS-API#iosopendocumentpathstring) or react-native-document-controller modules, but something you can also reproduce by calling directly. And that this is true starting with iOS 13+.  Were there any changes in the native behavior in that version? Is this an RN issue or a change in the platform?

@chrisglein You guessed it correctly, it's an issue that occurs on iOS 13+ version.
I can't tell if its a react-native issue or just a general platform issue. Some things have most certainly changed in the platform as well since the UI of the dialog has changed a bit, but the API did not, as war as I could tell.
But based on the official documentation and behavior it has on the prior platform version, the menu itself should be auto-dismissed after any user interaction. which fails in this case.
I did not try it again after with never version of react-native nor the platform, so the issue may no longer persist, and if it was platform based I supposed it may be resolved.


Re-order lectures 3-5

Looks like links in README are borked after this. Feel free to just fix on master.

Hrm - I just clicked through lectures 1-7, no probs
what link was busted?


Light is automatically turning on (sometimes) if automation has turned it off

Hi all,
I've a weird problem using zigbee2mqtt in Home Assistant where my light is turning itself on after it's turned off by a automation

Home Assistant 2021.1.5
Zigbee2mqtt latest
HA runs in VM using Slaesh's CC2652RB stick
Motion detection Xiaomi human
Kitchen lights are 3 grouped Ikea Tradfri GU10 lights (grouped in Zigbee2mq2tt to have 1 entity in HA)

---
platform: mqtt
schema: json
name: kitchen
command_topic: "zigbee2mqtt/Kitchen/set"
state_topic: "zigbee2mqtt/Kitchen"
color_temp: true
brightness: true

So I have this simple automation for turning kitchen light on which is working flawlessly.
---
alias: Lampen - Turn on kitchen lights by movement
description: ''

trigger:
  - entity_id: binary_sensor.kitchen_motion_occupancy
    platform: state
    from: 'off'
    to: 'on'

condition:
  condition: or
  conditions:
    - condition: numeric_state
      entity_id: sensor.kitchen_motion_illuminance_lux
      below: 101

action:
  - service: light.turn_on
    data:
      entity_id: light.kitchen

And this automation to turn light off when no motion detected:
---
alias: Lampen - Turn off kitchen light
description: ''

trigger:
  - entity_id: binary_sensor.kitchen_motion_occupancy
    platform: state
    to: 'off'
    for:
      minutes: 1

condition: []

action:
  - service: light.turn_off
    data:
      entity_id: light.kitchen

Weirdly; sometimes when the light turns off automatically by the automation; the light is turning on again. And I don't know why. When checking out the logbook in HA something is weird. As the screenshot says: 'Keuken (which is kitchen in English' turned on by service.light.turn_on'. So that seems to me that there's no other automation that is triggering this randomly turned off light.

These are the zigbee2mqtt logs. The first line is automation that's beiing triggered to turn the light off. A few seconds after that; for some reason the light is turning on itself.
 How can I debug this even further?

Might be better to report this on https://github.com/Koenkk/zigbee2mqtt/issues

@ciotlosm Will do; thanks! https://github.com/Koenkk/zigbee2mqtt/issues/6239


Missing requirements for running build

Clean win10 machine requires additional packages to be able to build and run tests.
Running the fuse installer (1.0.2) resolves the issue, most likely VCRedist?
PS C:\Users\Marius\fuselibs-public\fuselibs-public-master> Stuff\uno --trace doctor
Uno 1.1.0 (build 5395) Windows 10 x64 706c6d5
Found 69 projects, 69 are out of date
Building 1/69: Android.ActivityUtils
FATAL ERROR: Failed to load 'C:\Users\Marius\fuselibs-public\fuselibs-public-master\Stuff\bin\x64\uAsset.dll'. The speci
fied module could not be found (pass --trace for stack trace)
(0.2 s)

Yeah, this is probably some version of the VCRedist. uAsset.dll is a native C++ library, which will depend on the version of the CRT it was built against. I don't think we have any proper tracking of what version that is, @mortend do you know?

After starting over; i've come to the followings steps are needed to run tests (on a clean windows install):
choco install git vcredist2013
git clone git://github.com/fusetools/fuselibs-public
cd fuselibs-public
.\stuff\stuff install stuff
.\stuff\uno --trace doctor
.\Stuff\uno --trace test -tDotNet Source

If running on a computer without a OpenGL 2.1 context available (e.g. virtual machines), you need an alternative OpenGL implementation (same that is used for the appveyor tests)
Invoke-WebRequest http://downloads.fdossena.com/geth.php?r=mesa-latest -OutFile mesa.zip
Expand-Archive mesa.zip mesa
Get-ChildItem -Path Source -Recurse -Include *Test.unoproj | Select-Object -ExpandProperty DirectoryName | Foreach-Object {
        $buildDir = Join-Path $_ build\Test\DotNet
        New-Item -Force -ItemType directory -Path $buildDir | Out-Null
        Copy-Item -Path mesa\opengl32.dll -Destination (Join-Path $buildDir opengl32.dll)
      }

This is mostly based on the appveyor-config, so i would suggest that a section on how to build/run tests should be updated.
Requires Admin-privileges to build it seems currently (no error is thrown during the install/config phase, but you might get some errors related to Network access, because the files originate from a non-trusted internet zone by default.)

This was fixed in 014916cb0b16b6f3d3dd9593f1c08dc25f1b4eea.


Remove enviroment.ts related code from bundle

Command
build
Description
If I have my environment file
export const environment = {
  production: true,
  featureAEnabled: false,
};

Then in a component
if (environtment.featureAEnabled) {
// Doing stuff
}

This will still be a part of the bundle even do it will never be used, right?
I have little to none knowledge of the compiler so apologies if I'm totally of here :)
Describe the solution you'd like
If this is never to change, remove it :)
Describe alternatives you've considered
N/A

@JoostK do you know if there are some more details to read on this topic?
To me it seems strange not to remove code that will never run in that build. I assume that the reason for it is because of limits in the compiler but I would like to understand why as these case seems rather clear and straight forward :)

Code elimination in these scenarios require code folding (aka inlining) of the condition expression to arrive at if (false), but there are limits to how deep the inlining goes. With the environments file there is an indirection through a module import, which is supposedly too much for the optimizer to fully inline. I don't know the full extent of the inlining process (this is implemented in esbuild) and its limitations.
You may be able to achieve the desired elimination by using the CLI's recently introduced define option for the application builder, see #27047. This requires a bare identifier to be used as if condition expression as it won't replace expression (just variable names), but you can maybe achieve it with an intermediate variable assignment.


Installing Raven without a DSN causes it to swallow uncaught exceptions

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Installing Raven without a DSN causes it to swallow uncaught exceptions.  We do this in our dev environment.  Here is some sample code that will show the failure:
var Raven = require('raven');
var dsn = undefined;
Raven.config(dsn);
Raven.install(function (sentToSentry, err) {
  console.error('Uncaught Error:', err.message);
  process.exit(1);
});

throw new Error('oops');

Result:
$ node test.js
<EMAIL_ADDRESS>alert: no DSN provided, error reporting disabled
<EMAIL_ADDRESS>alert: uncaughtException: e2dd6808a0634382a2608a66c6a7641d

Note it does not call my callback (which logs, then exits), and it does not exit the process.
(In this example, the process actually exits, but only because there's nothing else to do.  In the real world if you're running an express server or something, the process will not exit).
What is the expected behavior?
It should call the provided callback with sentToSentry=false, thus allowing me to log the error and call process.exit(1);

As a workaround, for now, I'm doing:
var Raven = require('raven');
var dsn = undefined;
Raven.config(dsn);
if (dsn) {
  Raven.install(function (sentToSentry, err) {
    console.error('Uncaught Error:', err.message);
    process.exit(1);
  });
}

throw new Error('oops');

Similar to #288 which points to #257

This behavior is fixed after #308. Refer to this comment for a rundown of the new behavior.
Please let me know if you have any other scenarios or use cases that the new behavior doesn't accommodate.

Can we get a release with this fix?

@francisdb will publish tomorrow as per #314

@francisdb 2.0.0 has been published

Thanks!


Horizontal tag component

NEW tag list displayed horizontally, including magazine search to the right. This should show the 5 (or fewer) "promoted tags selected by editors ( https://github.com/equinor/energyvision/issues/1226 ), This tag list should also be implemented to the magazine template page.
For reference: #1251 https://www.figma.com/file/F2OnKFEoMwFaANMgeGRGqE/CMS?node-id=5977%3A90557

@NickHaggerty1 @meols Quick question here. The horizontal bar in the magazine template page should display the tags that are added to that page. Is this correct? or should we have separate tag list to display?

@padms @meols @fernandolucchesi   It could be done separately like you have with a NEW display on each template. However this would mean the horizontal bar on each article would be editable. Correct? This is not really what we want. We were thinking more that in the MAGAZINE TAGS (where we create the tags) there would be a hierarchy option there instead (tick on /off to display in magazine bar for example) with a maximum display of 5. So Editor could choose/tick 5 from the list of magazine tags and this would display on ALL mag templates bars. If editor decides to change one, then has to deselect one in order to add one. By editing here instead, the editor wouldnt need to go through every template to change. And we ensure consistency by not having option to change at an article level... Make sense? Doable?

Note we would still like the option to add other magazine tags to an article as you have already set up, so this doesn't change.

@NickHaggerty1
Created a menu item for this, which will be applied to all magazine pages.

@padms This looks excellent I think @meols agree?

Can you review this @fernandolucchesi?

@padms,

the border color you used is too dark compared to the ones in the design. In the design it is used #D3D7DA, we need to find a color var that is close to that.
when navigating from a magazine page to a tag that has no results (like innovation), the ALL tag is the one highlighted:

When navigating back and forth on the browser / clicking on tags, an error is displayed on the console:

left comments in your commits. once you fix those i'll do a 2nd round of review

1,2 and 3 fixed.

Hi @padms, left a suggestion.
Otherwise, for #1, the color should be (--grey-30). I know the figma file says slate blue but if you look at the hex code it is actually from the grey-30.
Also when inside a magazine the "ALL" is always selected. I think the correct would be no tags selected, OR the tags belonging to the magazine itself selected.

@fernandolucchesi  Please check now

Looks good! ✅

@meols @NickHaggerty1  Magazine tag bar is ready to be reviewed now. This component can be updated in the magazine index page, and will be reflected in all the magazine pages.

Approved. Thanks


how to create a folder in IOS

I'm unable to create a folder directory which also shows in gallery,

Cordova CI Build has completed successfully.
Commit     - Link
Dashboard - Link

This is not the place to file issue reports. Please do so over at issues.cordova.io. Thanks!


Remove Variant criteria from topic check

The TokenLoader class iterates over affected Vairants, per push job, and on EACH variant it checks if the request is a FCM/GCM topic request (e.g. does it have categories, or are there no criterias).
So, inside of a variant (used as topic any ways), it's not making sense, but instead returns false result.

I need to write a test case...

Testcase added
@odra @ziccardi mind to review ?

LGTM


Creating a cluster with kubeadm

Following command :
kubectl taint nodes --all node-role.kubernetes.io/control-plane- node-role.kubernetes.io/master-
should be replaced with :
kubectl taint nodes --all node-role.kubernetes.io/control-plane node-role.kubernetes.io/master
"-" removed

/assign

@sudipju I believe "-" should be there.

I am probably missing the logic. Can you please help me to understand?

To add, subsequently in the page,  following statement was described - "This will remove the node-role.kubernetes.io/control-plane and node-role.kubernetes.io/master". This doesn't include either control-plane- or master-. So, my recommendation is to remove "-" after control-plane and master as I recommended below:
kubectl taint nodes --all node-role.kubernetes.io/control-plane node-role.kubernetes.io/master

Adding - at the end removes a taint which is the section for single node clusters.
I don't see a problem in the docs here?

/priority awaiting-more-evidence

/close
closing as "won't fix", documentation is accurate.
if you have usage problems please join #kubeadm on k8s slack.


Add cases for interlocked execution modes to Execution mode parser

Using functionality provided by GL_ARB_fragment_shader_interlock inside an SPV module resulted in spvReflectCreateShaderModule() returning error code 20 (SPV_REFLECT_RESULT_ERROR_SPIRV_INVALID_EXECUTION_MODE);
Pull request adds cases for SpvExecutionModePixelInterlockOrderedEXT, SpvExecutionModePixelInterlockUnorderedEXT, SpvExecutionModeSampleInterlockOrderedEXT and SpvExecutionModeSampleInterlockUnorderedEXT within ParseExecutionModes() similarly to other extensions.

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


Which is more accurate? 3DDFA or PRNet?

I saw that you credited PRNet in this repo. Can I know if you have any idea which is more accurate? Thanks.

As for this repo and officail PRNet, the performance of the latter one is better, but the former maybe 20x faster than the latter one.

@cleardusk Is the reason why this repo is faster than prnet is because it uses a smaller input image size and a smaller model（mobilenet）？

You can see the updated readme. This improved version can run at a very fast speed with even better performance than PRNet. Relevant work is under review.

@cleardusk Any estimate when the relevant work will be published and be uploaded to GitHub? Is it correct that it will provide better 3D reconstruction than PRNet?


shippable recent builds are suddenly failing while installing go

This step: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/shippable.yml#L16-L21
source $HOME/.gvm/scripts/gvm;
 if [[ $SHIPPABLE_GO_VERSION == "tip" ]]; then gvm install tip; gvm use tip; fi
 if [[ $SHIPPABLE_GO_VERSION == *release* ]]; then gvm install release; gvm use release; fi
/root/1b9a1da4-6608-422e-ac92-6b887d443ddd.sh: eval: line 92: syntax error in conditional expression

https://app.shippable.com/builds/558da4718f3d3c0c00e71d81
https://app.shippable.com/builds/558da12e37e4f10c00f2db55
https://app.shippable.com/builds/558d9eba8f3d3c0c00e6c7e9
https://app.shippable.com/builds/558da2c68f3d3c0c00e70bfb
https://app.shippable.com/builds/558d98178f3d3c0c00e63d42
cc @ric03uec @manishas @ixdy @jlowdermilk

We'll take a look ASAP. Tagging @avinci

The last successful build was about 7 hours ago.

@minedanese Builds on Shuppable should be working now.  Thanks!

we're looking into this further....

OK we have 2 issues. We upgraded our backend to run on top Kube. For some reasons our eval scripts started failing and we fixed that. That resolved GO install.
Second, we had put in timeouts to be more aggressive than our prior versions. There was a bug on that one ended up timing out about 10 of Kube builds. We fixed that and now builds are running.
On the latest build https://app.shippable.com/builds/558debfa5b023e0c0087cc74 we are seeing this behavior

KUBE_TEST_API_VERSIONS="v1",KUBE_TEST_ETCD_PREFIXES="registry" is passing
KUBE_TEST_API_VERSIONS="v1beta3",KUBE_TEST_ETCD_PREFIXES="kubernetes.io/registry" is failing with this error
ResourceVersion:"420", FieldPath:"implicitly required container POD"}): reason: 'started' Started with docker id /k8s_POD.450 F0627 00:33:18.033576 33736 integration.go:880] FAILED: pod never started running timed out waiting for the condition I0627 00:33:18.565718 33736 kubelet.go:1736] Periodic sync I0627 00:33:18.791504 33736 kubelet.go:1736] Periodic sync !!! Error in ./hack/test-integration.sh:49 '"${KUBE_OUTPUT_HOSTBIN}/integration" --v=${LOG_LEVEL} --api-version="$1" --max-concurrency="${KUBE_INTEGRATION_TEST_MAX_CONCURRENCY}"' exited with status 255 Call stack:

I am not sure if this is our error. Can someone help me with this?

@avinci @manishas Thanks for all your work! We have had a build succeed again so the error you saw may be a flake by our test. I will kick it and see if they problem goes away.
https://app.shippable.com/builds/558dee152799150b00218baf

awesome. Apologize for the craziness today. We are on Kube 100% now and its a huge upgrade from our poor mans orchestration that we had. Hopefully the timeouts should reduce significantly now :-)

@avinci Love that you're on Kubernetes. Very cool.
Given that, it's in our interests to ensure it works well for you. :-)  Was the eval script failure somehow caused by Kubernetes?

@bgrant0607 It has to do with the version of python and ubuntu we are running. Nothing to do with Kube. But very strange that double quotes and single quotes had the problem...
This surfaced as we had new machines we provisioned for the new versions...

@avinci That is awesome you are using Kubernetes! Kubernetes CI on Kubernetes. Very meta. I see green builds now so I'm closing.

Reopening as many of our builds are still experiencing timeouts. What is the new timeout duration? Are our builds taking to long now that the build timeout has been reduced?
https://app.shippable.com/builds/558ffcdfec761d0b001c8db4
https://app.shippable.com/builds/55904fa5ec761d0b001fdb73
https://app.shippable.com/builds/55909990ec761d0b00217372
https://app.shippable.com/builds/5590942479f14d0b00ead53d

our timeout patch was reverted due to newer deploys. We have it permanently added now and should not occur. Please let me know if otherwise..

Thanks @avinci. We aren't seeing timeouts this morning but a many of our integration tests are failing which I'm currently trying to debug. The problem could very well be on our side. Were any other configurations changed (e.g. memory_limit reduced)?

no, we are doing 4GB/2 core..
One thing we are seeing is kubelet is shooting up in CPU util on the host machines. there is a bug I am tracking. Not sure if this has any effect... https://github.com/GoogleCloudPlatform/kubernetes/issues/10451

Okay thanks for info. We will keep digging. cc @dchen1107

We had to revert back to our old orchestration due to issues similar to #10451 and also https://groups.google.com/forum/#!topic/google-containers/aoWv7wCd4uk
We're debugging further but for now builds should be back to normal. We're watching the builds very closely.

Currently KUBE is freezing all the running containers on a minion which causes our builds to timeout as they are run only once pods. This happens when kubelet starts to eat up CPU for no reason as described by the bug above...

@avinci thanks for reporting. We are looking into it. what cloud provider are you using, GKE? What version of kubernetes are you running? How much cpu/memory do the nodes have? How many pods usually run per node?

AWS c4.X8Large I think its 36 cores with 60GB memory and we have a Provisioned IOPS disk of 1TB with 6000io

We have reverted back to our old systems and kube builds have been running 20mins each mostly green since last 6-8 builds

I updated #10451 which has the same cause as this one. This is known issue because heapster collects /stats too frequently. PR #9809 was merged for v0.20 release should mitigate the issue.
@yujuhong did measurement on today's kubelet, and measurement can be found at https://github.com/GoogleCloudPlatform/kubernetes/issues/10451#issuecomment-117268016

any idea why this happens?
https://groups.google.com/forum/#!topic/google-containers/aoWv7wCd4uk

any idea why this happens?
https://groups.google.com/forum/#!topic/google-containers/aoWv7wCd4uk

@avinci, the error message means that the system was running out of inotify watches. There was some discussion in #7815 related to this topic.
How many containers were you running on the machine?

We currently are running around 30-40 containers out of which atleast 30% of the containers are Kube containers like pause etc.
again on c4.x8 machine. we are seeing tons of other scale issues, space not found, not available resources all sorts of just runtime operational issues...

@avinci are you using the aws cloud provider scripts or do you have a custom deployment of kubernetes?
We should maybe increase sysctl limits with salt config. I've seen people run into limits for fs.inotify.max_user_watches, net.ipv4.netfilter.ip_conntrack_max, fs.file-max and ulimit.

@avinci There are two issues reported from the link you were referring at: https://groups.google.com/forum/#!topic/google-containers/aoWv7wCd4uk

Both error messages are come from cadvisor. In Kubernetes environment, cadvisor is running as part of kubelet for better integration in the future.
The first one: cadvisor tries to run du to get disk usage of each docker container, and report it as part of per container metrics even kubernetes haven't utilize such information yet. Sometimes du failed due to the race between garbage collecting dead containers and cadvisor queries the stats. Again, we should improve the integration between cadvisor and kubelet in a long run to prevent such race, but cadvisor does handle such failure gracefully today. That error message is just red herrring here.
The second one related to inotify. The cadvisor issue is filed at https://github.com/google/cadvisor/issues/703 and fixed by https://github.com/google/cadvisor/pull/726. Kubernetes include such fix through pr: https://github.com/GoogleCloudPlatform/kubernetes/pull/9750, which is in v0.20.X release.

cc/ @vmarmol and @rjnagal @vishh on cAdvisor. Please correct me if the timeline is wrong.


Compatibility issue with semantic-ui-react

I spent the past few hours debugging and fixing odd behaviour of react-sortable-hoc when used in conjunction with semantic-ui-react. This should save time whoever tries this next.
TL;DR Always use disableAutoScroll prop when using with semantic-ui-react
The list items snap back to original position and overlap with helper thus making sorting unachievable. The reason is auto scroll timer keeps firing and adjusting sortableOffset.top value when drag is active (even if it is not moving). Basically react-sortable-hoc falls into a vicious loop when drag is active.

Would you mind putting together a CodeSandbox replicating the issue?

Closing this issue for now until you can show me what the issue is.

@clauderic :wave:
Thanks for the great library. Works like a charm, but I witnessed some problems / glitching when combined with Semantic UI.
Here's a sandbox with the problem reproduced: https://codesandbox.io/s/hungry-bhabha-14ovk
Try dragging from the last list. It glitches & does not behave properly.
The problem occurs when there are more than 1 list on a single page.

Also, can confirm that adding disableAutoScroll={true} fixes the issue (@vineet89)
<SortableContainer disableAutoScroll={true}>
    ....

Actually, sorry, disableAutoScroll does not fix the issue. I've updated the sandbox from above :+1:

Okay, final one from me, setting useWindowAsScrollContainer={true} on the container actually fixes the issue.
Haven't updated the sandbox - https://codesandbox.io/s/hungry-bhabha-14ovk - so people can see the actual problem :raised_hands:


[BUG] Cannot run AppInstaller generated

:information_source: Info

Version: 3.6.3
:speech_balloon: Description

I tried to package to AppInstaller, so I run the following command.
flutter pub run msix:publish

Output:
running "flutter build windows"...     38.3s
building msix files...                 18.5s
packing msix files...                  12.6s
publishing...                          0.2s
appinstaller created: .\build\windows/flutter_application_1.appinstaller

The file successfully generated, but when opening the installer:

An error Cannot open app package occur with the reason Error in parsing the app package.
Note: I run the .msix installer without problem.
:scroll: Pubspec.yaml

name: flutter_application_1
description: A new Flutter project.

publish_to: "none"

version: 1.0.0+1

environment:
  sdk: ">=2.17.6 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  cupertino_icons: ^1.0.2

dev_dependencies:
  flutter_test:
    sdk: flutter

  msix: ^3.6.3
  flutter_lints: ^2.0.0

flutter:
  uses-material-design: true

msix_config:
  display_name: My meow app
  publisher_display_name: Muhammad Fareez Iqmal
  identity_name: fareez.meow.app
  msix_version: <IP_ADDRESS>
  logo_path: ".\\assets\\logo\\app-logo.png"
  app_installer:
    publish_folder_path: ".\\build\\windows"
    hours_between_update_checks: 0
    automatic_background_task: true
    update_blocks_activation: true
    show_prompt: true
    force_update_from_any_version: false
  capabilities: "internetClient"
  certificate_path: "C:\\Users\\Iqmal\\CERTIFICATE.pfx"
  certificate_password: 1234

Hello @iqfareez
You need to set in publish_folder_path: the full path (not a reletive path) of some existing folder where you want to publish versions of the application.

This still doesn't work


Community Team - Week - 1

📝 Weekly Report For TNB Team
Basic Details

🏟 Name of the TNB Team: Community
📅 Report Date: 02-19-2021
📜 Team Work Report

✅ Accomplishments this week

Technical doc improvements
Documentation around governance and network sync

🚩 Goals for next week

Get people to where they need to be. Greet, welcome, guide

🔭 Long term goals
Same as above. The Community team will most likely have the same goals every week since there are no projects or tasks like engineering or design.
❗❓ Concerns
Nope
👨💻👩💻 Team Members Contribution Details

Team Member 1: Bucky
GitHub Username 1: buckyroberts
Tasks of Member 1

Governance docs - https://docs.google.com/document/d/1GcGg-uWijwD4A2boSPPFFh5Ras0UMk7syiyZB4l_bLk/edit?usp=sharing
Network sync writeup - https://github.com/thenewboston-developers/thenewboston-python/issues/74
Lot's of architecting and problem solving around the governance and sync architecture, notes are in my physical notebook

Team Member 2: Vyz
GitHub Username 2: led76marx
Tasks of Member 2

Editorial pass and updates on Guides - https://github.com/thenewboston-developers/Website/pull/1293
Lot's of additional suggestions around improving our tech docs, a lot of which was done over video call and translated into design tickets - https://github.com/thenewboston-developers/Design/issues

🖹 Feedback (Optional)
None

approved


Documentation and implementation do not align on default protocols used

https://github.com/wojtekmach/req/blob/bfabe15f9a82d5d59b5e0ab9d514fad287861ca3/lib/req.ex#L297-L298
Documented to use both http1 and http2
https://github.com/wojtekmach/req/blob/bfabe15f9a82d5d59b5e0ab9d514fad287861ca3/lib/req/steps.ex#L983-L984
Implementation default is just http1

Good catch, implementation is wrong and we should be sending to Finch protocols: [:http1, :http2] by default.

FYI I've temporarily switched back to protocols: [:http1] due to https://github.com/sneako/finch/issues/265. The plan is to go back to http1+http2 once that's fixed.


chore(deps): update devdependency vite to ^5.2.10

This PR contains the following updates:

Package
Type
Update
Change

vite (source)
devDependencies
patch
^5.2.9 -> ^5.2.10

Release Notes

vitejs/vite (vite)
v5.2.10
Compare Source

revert: perf: use workspace root for fs cache (#15712) (#16476) (77e7359), closes #15712 #16476
fix: add base to virtual html (#16442) (721f94d), closes #16442
fix: adjust esm syntax judgment logic (#16436) (af72eab), closes #16436
fix: don't add outDirs to watch.ignored if emptyOutDir is false (#16453) (6a127d6), closes #16453
fix(cspNonce): don't overwrite existing nonce values (#16415) (b872635), closes #16415
feat: show warning if root is in build.outDir (#16454) (11444dc), closes #16454
feat: write cspNonce to style tags (#16419) (8e54bbd), closes #16419
chore(deps): update dependency eslint-plugin-n to v17 (#16381) (6cccef7), closes #16381

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Hywax Assistant.

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

Project coverage is 100.00%. Comparing base (5fb444e) to head (e73e100).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #33   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          146       146
  Branches        25        26    +1
=========================================
  Hits           146       146

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


"Integration requires reconfiguration" After restart always asking for credentials user/password only

Hello,
Thanks for all your work !!! It is working nice, but i have problem with expired session or something.

Of course after enter user and password all starting to work, but it is annoying to do it every day/restart.
Can you please check it?

More details:
Logger: custom_components.vaillant_vsmart
Source: helpers/update_coordinator.py:366
Integration: Vaillant vSMART (documentation, issues)
First occurred: 09:46:16 (1 occurrences)
Last logged: 09:46:16
Authentication failed while fetching vaillant_vsmart data: ('Access token is invalid or expired. Refresh the access token and try again.', {'method': 'POST', 'url': URL('https://api.netatmo.com/api/getthermostatsdata'), 'body': b'device_type=NAVaillant&data_amount=app&sync_device_id=all&access_token=&'}, {'status_code': 403, 'url': URL('https://api.netatmo.com/api/getthermostatsdata'), 'body': b'{"error":{"code":2,"message":"Invalid access token"}}', 'duration': datetime.timedelta(microseconds=77999)})

Ten błąd pochodzi z niestandardowej integracji.
Logger: custom_components.vaillant_vsmart.config_flow
Source: custom_components/vaillant_vsmart/config_flow.py:65
Integration: Vaillant vSMART (documentation, issues)
First occurred: 09:46:16 (1 occurrences)
Last logged: 09:46:16
("Server processed the request and returned a 4xx response. Don't retry the request without changing the arguments as the new request will fail again with the same error.", {'method': 'POST', 'url': URL('https://api.netatmo.com/oauth2/token'), 'body': b'username=&password=&app_version=<IP_ADDRESS>&grant_type=password&client_id=na_client_android_vaillant&client_secret=929a9f6253babbee1a6e8d4bd51745f0&scope=read_thermostat+write_thermostat'}, {'status_code': 400, 'url': URL('https://api.netatmo.com/oauth2/token'), 'body': b'{"error":"invalid_request","error_description":"Missing parameters, \"username\" and \"password\" are required"}', 'duration': datetime.timedelta(microseconds=59633)})
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/vaillant_netatmo_api/errors.py", line 79, in client_error_handler
yield
File "/usr/local/lib/python3.12/site-packages/vaillant_netatmo_api/base.py", line 55, in _post
resp.raise_for_status()
File "/usr/local/lib/python3.12/site-packages/httpx/_models.py", line 759, in raise_for_status
raise HTTPStatusError(message, request=request, response=self)
httpx.HTTPStatusError: Client error '400 ' for url 'https://api.netatmo.com/oauth2/token'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/vaillant_vsmart/config_flow.py", line 65, in _async_step_all
data = await self._get_config_storage_data(user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/vaillant_vsmart/config_flow.py", line 155, in _get_config_storage_data
await client.async_token(
File "/usr/local/lib/python3.12/site-packages/vaillant_netatmo_api/auth.py", line 74, in async_token
body = await self._post(
^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tenacity/_asyncio.py", line 88, in async_wrapped
return await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tenacity/_asyncio.py", line 47, in call
do = self.iter(retry_state=retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/tenacity/init.py", line 314, in iter
return fut.result()
^^^^^^^^^^^^
File "/usr/local/lib/python3.12/concurrent/futures/_base.py", line 449, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
File "/usr/local/lib/python3.12/site-packages/tenacity/_asyncio.py", line 50, in call
result = await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/vaillant_netatmo_api/base.py", line 47, in _post
with client_error_handler():
File "/usr/local/lib/python3.12/contextlib.py", line 158, in exit
self.gen.throw(value)
File "/usr/local/lib/python3.12/site-packages/vaillant_netatmo_api/errors.py", line 90, in client_error_handler
raise RequestClientException("Server processed the request and returned a 4xx response. Don't retry the request without changing the arguments as the new request will fail again with the same error.", e.request, e.response) from e
vaillant_netatmo_api.errors.RequestClientException: ("Server processed the request and returned a 4xx response. Don't retry the request without changing the arguments as the new request will fail again with the same error.", {'method': 'POST', 'url': URL('https://api.netatmo.com/oauth2/token'), 'body': b'username=&password=&app_version=<IP_ADDRESS>&grant_type=password&client_id=na_client_android_vaillant&client_secret=929a9f6253babbee1a6e8d4bd51745f0&scope=read_thermostat+write_thermostat'}, {'status_code': 400, 'url': URL('https://api.netatmo.com/oauth2/token'), 'body': b'{"error":"invalid_request","error_description":"Missing parameters, \"username\" and \"password\" are required"}', 'duration': datetime.timedelta(microseconds=59633)})

I am using all latest: v.0.9.0 and
HA
Core 2024.2.0
Supervisor 2024.01.1
Operating System 11.5
Interfejs użytkownika 20240207.0

Same problem here, starting from february 2024 versions and above.

I'm sorry to hear that you have issues with the integration. I tried reproducing this, but I can't. I don't have any disconnects and I get reauth request almost exclusively after I work on this locally, thus generating a lot of tokens, making them invalid. Other than that, I don't get any issues.

Dear @MislavMandaric,
I am experiencing the same problem; the Vaillant system disconnects approximately every half hour.
Here is the error I receive:

These are my settings:

When I re-add the system, everything works fine for a short time, but then the issue recurs.
Could you kindly advise on how to resolve this?
Thank you for your excellent work and assistance!
Best regards,
Toni

I'm sorry to hear that you have issues with the integration. I tried reproducing this, but I can't. I don't have any disconnects and I get reauth request almost exclusively after I work on this locally, thus generating a lot of tokens, making them invalid. Other than that, I don't get any issues.

Hi Mislav,
I have the same problem too.
I tried uninstalling and reinstalling, but it didn't work.
It seems that I can't save the credentials and that at each session I need to re-authenticate... so this integration is not usable... can we provide you with some more information to debug?
Thanks for your support.

Update... i find this in my log:
2024-12-17 17:58:54.589 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'vaillant_vsmart' creates a new entry in a 'reauth' flow, when it is expected to update an existing entry and abort at custom_components/vaillant_vsmart/config_flow.py, line 85: return self.async_create_entry(title=user_input[CONF_USERNAME], data=data). This will stop working in Home Assistant 2025.11, please create a bug report at https://github.com/MislavMandaric/home-assistant-vaillant-vsmart/issues

This solution not working for me:

source: https://githubhelp.com/MislavMandaric/home-assistant-vaillant-vsmart


Module not found: Can't resolve 'atropos/react'

Hi,
I'm trying to implement Atropos in a project but it seems it can't find the module.
I installed the package via npm i atropos and imported it in my component like indicated in the guide:
import Atropos from 'atropos/react'.

@Frhazz Was looking through the old closed Issues  #4, tried importing "atropos/react/atropos-react.esm" instead of "atropos/react" and it seems to find the module.

@Frhazz @asyam1
The solution is to use a newer version of nodejs which supports es modules. Try to use the lib with node >= 14 for example. Everything works exactly as expected (already tested it with react, Vue and vanilla js) :)

I'm using node 16 - doesn't work... Module not found

Having the same problem here with Node 18.2.0.


[Bug] Call verify_database only to selected schemas

Is this a new bug?

[X] I believe this is a new bug
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
dbt fails to run if two models have the same schema and table names even though they target different databases.
Expected Behavior
A successful dbt run as the models are not referencing each other and they target different databases.
Steps To Reproduce

Create a dbt project with two independent models having the same alias and schema names. Use a different database for each. First model would be materialized into "db1".some_schema.some_table and the second into "db2".some_schema.some_table.
Run dbt for one of the models, i.e.:
dbt run --select first_model
Check it fails with:

Runtime Error
  ERROR: Cross-db references not allowed in postgres (something vs postgres)

Relevant log output
Runtime Error
  ERROR: Cross-db references not allowed in postgres (something vs postgres)

### Environment

```markdown
- OS: macOS 14.4
- Python: 3.8.13
- dbt-postgres: 1.7.11

Additional Context
By looking at this dbt-core pr I can infer multi-db is somehow supported in one single project. However, the caching behavior in the postgres adapter is not letting it as it assumes one db per project. The critical part seems to live here where all node entries in the manifest are getting matched against the expected database, even if the dbt run command doesn't target those entries (models). Using --cache-selected-only doesn't bypass this issue since it will fetch all relations from the manifest here anyway and a few steps further verify_database will be called against these. The only way I made this work was to call --no-populate-cache because it will completely stop this verify_database step from happening. However, that doesn't look ideal.
I'm opening this issue because I've noticed we can change _link_cached_relations to accept an optional cache_schemas parameter and that would be utilized here since those schemas already exist in that context. If verify_database would be called only against the selected models the dbt run would run just fine.

hi @pevidex! yeah cross-database queries are disabled in postgres because it isn't support (yet).
So this is really an enhancement rather than a bug. Can you share the postgres service and/or extensions you're using where you expect it to be working?
If there's significant interest/demand for supporting multi-db scenarios, this is something that we could do.
At the very least, we could enable a parameter similar to dbt-redshifts ra3_node (docs), which is an override for the .verify_database method you reference.

So this is really an enhancement rather than a bug.

Hey, @dataders, thanks for the answer.
I've signaled this as a bug because, even with --cache-selected-only enabled, we're calling verify_database against all nodes loaded in the manifest. I assumed this is not the intended behavior but I may be missing some context and I noticed dbt-redshift has the same behaviour. So maybe enhancement fits it better.

Can you share the postgres service and/or extensions you're using where you expect it to be working?

I'm not doing any cross-db reference in my specific use case, just using a simple postgres instance. Due to project constraints, I've to use a single dbt project for two sets of models that target different dbs but don't reference each other. I select the target dbs using the dbt_project.yml +database keyword (docs). I managed to workaround it by using --no-populate-cache. I was not expecting this to work just by disabling this feature so that's why I reported it.

At the very least, we could enable a parameter similar to dbt-redshifts ra3_node (docs), which is an override for the .verify_database method you reference.

That could work but I think that feature would suit better in situations where real cross-db references are happening. In this case, I was thinking more on how to call .verify_database against the selected models only.

I'm so glad you found a workaround! Unfortunately at this time, we are unable to prioritize this for our roadmap so I'm going to close this issue for now.


Backward derivatives in ltc_instructions.py

In backward_pass macro of the simple example (https://github.com/michaelkhany/liquid_time_constant_networks/blob/main/ltc_instructions.py#L78), shouldn't A parameter appear in the dL/dtheta derivatives?
As one has; S(t)=(I(t) * Thetat0(t) + x(t)* Theta1(t))*x(t)*A
I would have expected that:
dL_dtheta_0 = dL_dy_prime * w * input_value * x_t * A
dL_dtheta_1 = dL_dy_prime * w * x_t * x_t * A

Am I missing something, or is my interpretation of S(t) wrong?

In the context of the Liquid Time-Constant (LTC) Neural Networks, your question regarding whether the parameter A should appear in the derivatives dL/dθ0 and dL/dθ1 is insightful. Given the equation:
S(t)=(I(t)⋅θ0 (t)+x(t)⋅θ1 (t))⋅x(t)⋅A,
it seems reasonable to expect A to influence the gradients since it appears in the expression for the state S(t).
Your expectation for the gradients is:

dL/dθ0 =dL/dy' ⋅w⋅input_value⋅x t ⋅A
dL/dθ1 = dL/dy' . w . x_t . x_t . A

This interpretation assumes that A directly scales the contributions of I(t) and x(t) in the computation of S(t).
However, the appearance of A in the gradient expressions depends on its treatment within the implementation, whether A should appear in the derivatives dLθ0 and dL/dθ1 depends on its role in the computation. If it's directly involved in the calculation of S(t) and is not absorbed into other constants or parameters, then it should appear in the derivatives. Otherwise, it might be handled differently within the implementation.


Find-DbaSimilarTable

This is my first pull request. Please do be hard on me where I am not meeting team standards but also help me where it is necessary as this is my first online collaborative effort.

@SQLJana there is no changes included in your PR (no files).
Just a general question though what is the purpose of the command you are submitting? What issue/problem is it trying to solve? Can you provide examples of how it would be used, with screenshots would also help?

Shawn, Sorry that the PR did not have any files. I am having trouble making a PR to development branch from my local branch. Anyway, the function helps find tables/views that have a similar structure by matching column names as described in detail here - https://sqljana.wordpress.com/2017/03/31/sql-server-find-tables-with-similar-table-structure/
In the PowerShell version of the function, everything is optional except the InstanceName parameter in which case it shows all tables/views that have common column names with the matched column name percent. Given a table/view name, it helps identify other tables/views that have similar column names. This is helpful when you are trying to find the archive version of a table for example.

We have a templates repo under the this org but I've had not a chance to a lot of examples of the various logic. One thing on my to do list.

Ok.  Thank you.
Please let me know if there is anything else you need. Hopefully, I this time around, I pushed the changes properly.

Thank you for the PR @sqljana! And thank you for taking care of this, @wsmelton. Before merging, I'd like to confirm the name with the name master, @PowerDBAKlaas. Please allow me time to confirm.

I would say something like Find-DbaMatchingTable or Find-DbaIdenticalTable would sound better than "Similar". I mean the synoposis and columns both reference matching.

Identical may be too strong of a word to use...

I agree. "Identical" is too strong. I like both "matching" and "similar". Also, should we say TableOrView instead of just Table?

Although ...TableOrView... may be more correct, I feel it will lead to strange names. It would also create a precedent. @SQLJana do you think this function is easily adapted to include nonclustered indexes or stored procedures? If not, I'd stick to ...Table...
@wsmelton maybe I don't grasp the semantics correctly, but 'matching' makes me think of regexp and meaning 'this and optionally more, but not less'

So are you saying make it Find-DbaTable @powerdbaklaas?

That would be the nicest name, but not consistent with other Find- functions I believe. Don't de others have options for looking for keywords, or the owner or such things?
Also, will this function likely remain as is, or is there a possibility it will work on stored procedures or nonclustered indexes too?
For now, I think Find-DbaSimilarTable sounds as the best description to me.

Agreed, I will create a test and merge 👍 with name Find-DbaSimilarTable

Thanks again @SQLJana, love this command! I made one commit with 4 changes

added your website to the description 👍
changed it so that -Database will work for system dbs without specifying an additional param
Added two columns that have the fully qualified table names, plus i moved the matchingpercent column up closer. This way, I find the info I need is immediately available.
Updated the column names to say "Original" for the columns that were not "Matching"

I also created a Pester test and will ping you on the PR 💃 This is not expected of new team members but thought you may be interested to see an integration test.
Welcome to the team! I'll be adding you to dbatools.ip/team shortly.

@PowerDBAKlaas We can't call this command Find-DbaTable because it does not offer a search ability. It is comparing a base table to the rest of the tables in any database or all databases.

yes that too
BTW has there been any performance testing on this? Comparing all tables on the whole sqlinstance can take a few days, can't it?
Shouldn't there be a warning about that?

It outputs as it goes along, so the person can just cancel if they get frustrated, eh?

Thank you @wsmelton, @PowerDBAKlaas  and @potatoqualitee!
@PowerDBAKlaas, regarding "possibility it will work on stored procedures or nonclustered indexes too", it would be a difficult for stored procedures as what constitutes similarity could be different for different users (count by keywords, tables/views used, code similarity, return columns similarity etc). For NC indexes, using system views outside the INFORMATION_SCHEMA, it may not be hard.
Regarding performance testing, I did tests on small databases and it returns immediately. The one test that I did on a database with about 1000 tables and around 1000 views took 90 seconds for the raw SQL to return about 1 million rows in SSMS on an instance with 300 GB of memory (with no conditions from parameters). From PowerShell, the time taken on a client PC (SQL host is no a different server) for the same conditions is about the same time to start returning the rows..and the user can always cancel before it finishes returning everything as @potatoqualitee said (or) it may exhaust the memory.


Possible ratelimiting introduced by Spotify

When shuffling between tracks too fast, I get the error message below while fetching the audio_key for decryption:
Error { kind: Unavailable, error: AesKey }
I had not run into such errors a few days ago, and I have seen other people report the same error recently on discord servers.

Spotify might be sending a retry after header like it does for most rate limited endpoints.
The header, if it is sent, needs to be exposed.

IIRC I did implement "retry after" in dev, no?

A retry mechanism for the audio keys is direly needed as the rate limiting almost makes my entire project unusable.

If you're a developer yourself,  a PR would be welcome.

If you're a developer yourself,  a PR would be welcome.

I'm a golang developer and my first and only rust project is using this library 😅
I do intend to learn rust and contribute to this project, but for now I'll wait for someone more knowledgeable and well versed with the project's codebase to work on it.

Is there a good reason for the rate limiting? Or could the reason for the rate limiting be addressed instead of adding retry?

Is there a good reason for the rate limiting? Or could the reason for the rate limiting be addressed instead of adding retry?

My project revolves around curating music after experiencing the "vibe" of a song, almost in a speedrun manner. (Might be the most cringe description)
To do so, I let the user quickly shuffle between tracks in a playlist, and automatically jump to a random position (somewhere around the middle of the track) and play it for a couple of seconds, giving the user the option to add it to their playlist should they have liked the preview.
The whole idea is that time is precious and a playlist can never be long enough ;)
As to why Spotify introduced the rate limiting that did not exist before, I do not know why. Probably they just discovered the lapse while pushing the other changes they had made to the API lately.
I cannot really "address" the cause of my project being rate limited due to the very nature of it. However, I'll still be happy to have it working as before while complying to Spotify's rate limit policies which I have yet to see stated with actual limits anywhere on their documentation.

Ok, sounds like a good reason to be rate limited 😄. Your application certainly is not typical behaviour, and from their point of view it might look like someone trying to mass download music files. Why else would a normal user try to get tracks in quick succession? Your application is out of the ordinary.
Whether they changed rate limiting recently or not, we can only speculate. But if I were a service provider, I'd probably block this kind of pattern, too.

Ok, sounds like a good reason to be rate limited 😄. Your application certainly is not typical behaviour, and from their point of view it might look like someone trying to mass download music files. Why else would a normal user try to get tracks in quick succession? Your application is out of the ordinary.
Whether they changed rate limiting recently or not, we can only speculate. But if I were a service provider, I'd probably block this kind of pattern, too.

I do know that my application is in the grey area in regards to spamming requests for tracks one after the other in short intervals.
But that is... kind of the appeal of it. To help the user take shortcuts in the process and save some time.
Sure, I get how Spotify might view my application as a batch downloader of sorts, and I admit that my use case may be mildly abusive, but I want to adhere to their rate limits so as to not face failed requests nor get my account banned.
Retry-After would fix my application:
Once the user requests a shuffle, I'll send a request to fetch the next song,
and if I'm already rate limited, I'll wait for the Retry-After interval to be reached, and until then I'll continue playing the current track and notify the user that the shuffle will be done in x seconds.

In Mercury, which is just TCP-based, there is no retry after header. Until someone adds rate limiting there in librespot (you could mostly copy it from the way it's done with HTTP) I suggest that you do it on the caller end (your end).

a better fix if we could get the Retry-After header

What header? From where? There are no headers for Mercury requests like this.
I don't recall any rate limited playback issues here but perhaps these are downstream problems from projects doing weird things that we don't hear about.

a better fix if we could get the Retry-After header

What header? From where? There are no headers for Mercury requests like this.
I don't recall any rate limited playback issues here but perhaps these are downstream problems from projects doing weird things that we don't hear about.

Apologies. I missed roderick's earlier message stating that there are no Retry-After headers.
In that case, I guess I'll just have to modify my code to fetch the preview files and fall back to the actual track if the preview file is not found.
Feel free to close this issue if any retry implementation is not planned for such edge cases.

FWIW: I'm seeing this here, as I'm trying to skip through a playlist. I could actually imagine this would happen to "real users", too: play playlist; "don't like that track - next"; repeat previous step a few times.

Can someone give me an example of how much skipping needs to be done? I was trying to reproduce this earlier by manually skipping and I failed.

Took me 32 skips. Thought it was fewer yesterday. All I tried was to jump to the end of the list, and clicking the last item in the queue wouldn't do the trick for whatever reason.
Now I'm wondering how long it'll take before I can skip again.

FWIW: I'm seeing this here, as I'm trying to skip through a playlist. I could actually imagine this would happen to "real users", too: play playlist; "don't like that track - next"; repeat previous step a few times.

As I had mentioned in my earlier messages, "real users" are also likely to hit this issue, and everyone would benefit some kind of workaround for this.
However, it has been impossible to decipher the ratelimit. Although, I too hit my errors somewhere around the 32 track mark.

FWIW: real user here, just hit this issue while manually skipping around tracks inside ncpsot.


[SPARK-50430][CORE][FOLLOW-UP] Keep the logic of manual putting key and values in Properties

What changes were proposed in this pull request?
This PR proposes to actually more conservatively preserve the original code of creating new properties instead of cloning.
Why are the changes needed?
Previous codes only copied the key and values but clone actually copies more fields in Properties. cloneProperties is being used in Spark Core, and all other components so I propose to keep the logic as is.
Does this PR introduce any user-facing change?
This is more a fix of a potential bug.
How was this patch tested?
No, it is difficult to add a test.
Was this patch authored or co-authored using generative AI tooling?
No.

Thank you for keeping making an effort to stablize this.
I'm wondering if this can mitigate the recent concurrency-related flakiness as the final solution.
Or, do you think we need to revert to the original code back if this doesn't help much?

Let me merge it first, and investigate it a bit more. I think the CI flakiness isn't related to this (or previous) change ... from a cursory look ..

Merged to master.

After I released rc2, all PRs related to SPARK-50430 in branch-3.5 were reverted. Will this affect the correctness?  @HyukjinKwon

That's fine - even if it affects sth, it should really be a corner case. I just wanted to keep it as is.

That's fine - even if it affects sth, it should really be a corner case. I just wanted to keep it as is.

Thank you~

Ya, thank you for reverting this from branch-3.5.

https://github.com/apache/spark/commit/0fbe292774a856ae49c436e9eb83441e9c38f7de


Change from DiffEqBase to SciMLBase

DiffEqBase is the lowest common denominator for the DiffEq packages, not necessarily the whole SciML ecosystem, and so it has a lot DiffEq dependencies. These are generally not required by downstream packages. If what you're looking for is a way to define problems without having most dependencies, we recommend you use SciMLBase as the dependency since everything like ODEProblem, SteadyStateProblem, etc. is defined there. We basically recommend depending on SciMLBase for problem definitions, and solver packages for specific solvers, but generally most non-SciML packages should not be depending on DiffEqBase directly (given the split of SciMLBase in 2021)
For more details see: https://diffeq.sciml.ai/stable/features/low_dep/ and https://discourse.julialang.org/t/psa-the-right-dependency-to-reduce-from-differentialequations-jl/72757
Let me know if you need any help updating this, though for almost all dependents here it should be a trivial name change as you're actually using pieces from SciMLBase.

@ChrisRackauckas thanks for the note. We can't remove DiffEqBase since Callbacks and CallbackSet are defined in DiffEqBase and not in SciMLBase

Callbacks and CallbackSet are defined in SciMLBase. https://github.com/SciML/SciMLBase.jl/blob/master/src/callbacks.jl

fixed via #175


overload FFTpower to accept Complex input

overload FFTpower to accept Complex input

actually it looks like many more methods would be useful.
come back later and redesign the API


Add lifetime to PyAny etc

This is a working implementation of PyAny<'a>.
By working - I mean tests pass on my machine (except doctests). I think the code is still heavily WIP, because I ended up making a few hacks to make things compile. I wanted to get to a point where we could have something to play with to assess ergonomics, and how it feels versus the new proposal in #679.
Some initial observations:
Owned, Borrowed and Lifetimes

Owned pointers are now obviously owned in docs - they are PyAny<'py>
Borrowed pointers are also very straightforward - they are &'a PyAny<'py>

The lifetime 'a is the lifetime of the PyAny we're borrowing from.

Because there are now more input lifetimes to functions, there are a few more cases where Rust asks for lifetime annotations. We might want to make the recommendation that users return Py<T> owned pointers always to avoid lifetime complexity.
Reference counting
As well as ownership above, incrementing and decrementing reference counts is done by PyAny::clone() and PyAny::drop() respectively.
PyAny deref
After making PyAny<'py>, I also was able to make e.g.
struct PyDict<'py>(PyAny<'py>);

This means that all native types now implement deref to PyAny. I think this provides an opportunity for us to remove ObjectProtocol and put all its methods directly on PyAny, which is a nice API simplification.
Py<T>
Py<PyTuple> broke by adding lifetimes, and not even Py<PyTuple<'static>> worked. To solve this problem, I added type markers, which are ZSTs without lifetimes which take on the role of type information for Py. Now you can write.
use pyo3::type_marker::Tuple;

struct Foo {
    t: Py<Tuple>
}

To avoid confusion with PyTuple and Py<Tuple> I think it would be wise to rename Py to PyRc (maybe not right now, but in the near future).
To avoid needing complex lifetime rules in the proc macros, I also had to change it so that you write #[extends=Dict] instead of #[extends=PyDict]. We might be able to undo this change with some careful implementation in the proc macros.
I rather hacked together the type marker idea in general because I wanted to get to a point where things compile. There's a lot of cleanup I think can be done here.
TODO:

[ ] Needs a lot of documentation updated
[ ] Benchmarking!
[ ] Much tidying up:

[ ] Remove GILPool's owned and borrowed tracking.
[ ] Can we remove lifetimes from any traits
[ ] Type marker idea can maybe be cleaned up / merged with pytuple.
[ ] What other traits become irrelevant in this new system?
[ ] Rename Py to PyRc?

Amazing, thank you!

how it feels versus the new proposal in #679.

About this, I'll make a draft implementation. Please wait for a bit.

I'm going to close this PR; it's a big pile of changes which I think we decided we don't want right now (instead opting for #887 as fast enough for now).
This PR is so big it will fall out of date quickly and become hard to rebase.
Some things I think I learned from this PR:

PyAny<'py> interacts really badly with Py<PyAny>, because writing the lifetimes inside Py is strange and doesn't have an easy solution.
This PR might be easier in the future when Rust has working Generic Associated Types. I had to add lifetimes to a lot of traits for this PR which I think won't all need to change if we had GATs.
Making this change didn't give particularly massive performance boosts, so for now if we have performance concerns we should focus on the rest of the pyO3 codebase.


Can't add price with cents/fractions

Steps to reproduce

Edit price of a variant
Type in fractional price, in example 19,50
After saving see the price rounded down to 19

Price is saved in database as 1900, should be 1950.

I can't seem to reproduce this issue. Can I get you to try again with latest admin release?

@olivermrbl Could this be it?
https://github.com/medusajs/admin/blob/a33ed20214297ffdbd2383f809dddd4870f5dad9/src/domain/products/details/variants/variant-editor.tsx#L92

@olivermrbl I have found the culprit of it. I have put a console.log here
https://github.com/medusajs/admin/blob/master/src/domain/products/product-form/sections/prices.tsx#L69
                      <CurrencyInput.AmountInput
                              label="Amount"
                              onChange={(amount) =>
                                console.log({ amount }) ||
                                onChange({ ...value, amount })
                              }
                              amount={value?.amount}
                            />

And I can see that if I add anything past the , it ingnores it in the onChange
Typing 50      => logs 5000
Typing 50,50 => logs 5000
That's because the amount inputs ignores the comma as decimal seperator.
I bet you have in Denmak dot as the decimal seperator
To test this with comma you might want to simulate location in devtools.
Ctrl+Shift+P => Show sensors
Select Berlin from predefined locations as it has comma as decimal seperator too.
https://www.aleksandrhovhannisyan.com/blog/changing-locale-in-chrome-with-dev-tools/

Hi @chemicalkosek,
Thanks for reporting the issue, and sorry for being so slow to act on it. I've just confirmed that this is the case, and will push a fix later today.
We actually also use commas as the decimal separator, so it's a bit strange that we haven't encountered it ourselves, but we must all have our locale set to the US 😅

Fixed with #698, and working in the development branch


Sending multiple response to a received request

It is not a bug report, it is a help request.
I want to implement simple network protocol like following diagram:
+--------+           +--------+
| Client |           | Server |
+---+----+           +---+----+
    |                    |
    |       PING         |
    |  +-------------->  |
    |                    |
    |                    |
    |       ACK          |
    |  <--------------+  |
    |                    |
    |                    |
    |                    |
    |                    |
    |       PONG         |
    |  <--------------+  |
    |                    |
    |                    |
    +                    +

I implemented simple server with simple codec that can decode ping messages, I can get the ping request and send the ack response, but I don't know how should I send the pong response.
I'm using netcat nc <IP_ADDRESS> 6142 to interact with the server, server send ACK response well.
Here is the source code and repo:
extern crate bytes;
extern crate futures;
extern crate tokio;

use bytes::BufMut;
use bytes::BytesMut;
use tokio::codec::{Decoder, Encoder};
use tokio::io;
use tokio::net::TcpListener;
use tokio::prelude::*;

// Ping-ack-Pong Protocol Message
struct Ppm;

enum Msg {
    PING,
    PONG,
    ACK,
}

impl Encoder for Ppm {
    type Item = Msg;
    type Error = io::Error;

    fn encode(&mut self, item: Msg, dst: &mut BytesMut) -> io::Result<()> {
        let res = match item {
            Msg::PONG => "PONG",
            Msg::PING => "PING",
            Msg::ACK => "ACK",
        };
        dst.put(res);
        dst.put("\n");
        Ok(())
    }
}

impl Decoder for Ppm {
    type Item = Msg;
    type Error = io::Error;

    fn decode(&mut self, src: &mut BytesMut) -> io::Result<Option<Msg>> {
        match &src[..] {
            b"PING\n" => {
                src.clear();
                Ok(Some(Msg::PING))
            }
            _ => {
                src.clear();
                Ok(None)
            }
        }
    }
}

fn main() {
    let addr = "<IP_ADDRESS>:6142".parse().unwrap();
    let listener = TcpListener::bind(&addr).unwrap();
    let server = listener
        .incoming()
        .map_err(|_| println!("failed to accept socket"))
        .for_each(|socket| {
            println!("new connection");
            let (tx, rx) = Ppm.framed(socket).split();

            let task = rx
                .inspect(|_| {
                    println!("new message received");
                }).map(|msg| match msg {
                    Msg::PING => Msg::ACK,
                    _ => Msg::PING,
                }).forward(tx)
                .then(|_| Ok(()));

            tokio::spawn(task)
        });
    tokio::run(server);
}

@carllerche this issue has been resolved, should I close it or I should make a docs for it?

@alishir sorry for the delay, do you have thoughts on how the docs (Tokio guides) could be improved to cover this case?


About WindowExplorer plugin and x86 processes

When running x64 version of Process Hacker, certain details about the windows of x86 applications are missing, eg. the address of window procedure. If I understand correctly, this is due to limitation of Windows API and you're employing a trick involving DLL injection in a process of interest to get this information in its context.
While I don't know if there's a trick that could be used to display this information in the x64 version, which would certainly come in handy sometimes, given that the x86 version of Process Hacker is bundled along with the x64 version (installer version), maybe the WindowExplorer plugin could be added to it for completeness sake. It does seem to work.

@dmex Any hopes to get it fixed? I did think to be a failure of my system...

you're employing a trick involving DLL injection in a process of interest to get this information

The injection was removed entirely a few years ago when Google Chrome was silently uninstalling Process Hacker via it's built-in "Chrome Cleanup Tool".
I'm closing this ticket since this feature won't be coming back. The procedure address won't be available for now using the pervious implementation.


Error installing Operator

When trying to deploy the Operator using Helm commands given in the README, I am getting following error:
$ kubectl get pods
NAME                             READY     STATUS             RESTARTS   AGE
mysql-operator-77bb98ff7-hcv72   0/1       CrashLoopBackOff   5          4m
mysql-operator-orchestrator-0    1/1       Running            3          4m
kubectl logs mysql-operator-77bb98ff7-hcv72
{"level":"info","ts":1554660708.7858343,"logger":"mysql-operator","msg":"Starting mysql-operator..."}
{"level":"info","ts":1554660708.8846366,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"mysqlbackup-controller","source":"kind source: /, Kind="}
{"level":"error","ts":1554660708.8852034,"logger":"kubebuilder.source","msg":"if kind is a CRD, it should be installed before calling Start","kind":"MysqlBackup.mysql.presslabs.org","error":"no matches for kind "MysqlBackup" in version "mysql.presslabs.org/v1alpha1"","stacktrace":"github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start\n\t/go/src/github.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source/source.go:89\ngithub.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Watch\n\t/go/src/github.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:122\ngithub.com/presslabs/mysql-operator/pkg/controller/mysqlbackup.add\n\t/go/src/github.com/presslabs/mysql-operator/pkg/controller/mysqlbackup/mysqlbackup_controller.go:76\ngithub.com/presslabs/mysql-operator/pkg/controller/mysqlbackup.Add\n\t/go/src/github.com/presslabs/mysql-operator/pkg/controller/mysqlbackup/mysqlbackup_controller.go:54\ngithub.com/presslabs/mysql-operator/pkg/controller.AddToManager\n\t/go/src/github.com/presslabs/mysql-operator/pkg/controller/controller.go:29\nmain.main\n\t/go/src/github.com/presslabs/mysql-operator/cmd/mysql-operator/main.go:94\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201"}
{"level":"error","ts":1554660708.888549,"logger":"mysql-operator","msg":"unable to setup controllers","error":"no matches for kind "MysqlBackup" in version "mysql.presslabs.org/v1alpha1"","stacktrace":"github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/go/src/github.com/presslabs/mysql-operator/cmd/mysql-operator/main.go:95\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201"}
Kubernetes versions:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:00:57Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Hi @devdattakulkarni, what version of helm do you have installed?
Helm is responsible for installing CRDs, we use helm capabilities API which are available from version 2.2.0.

Thanks. This is good info. My Helm version is:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Btw, the issue has been intermittent. After deleting my Minikube VM and trying operator installation again, things have been working. You can close the issue. But I wanted to report it in case any code level changes need to happen.

I have the exact same problem using an AKS cluster with helm v2.9.1.
@AMecea can you reopen the issue ?
$ kubectl get pods
NAME                             READY     STATUS             RESTARTS   AGE
mysql-operator-547cfc796-2d6l2   0/1       CrashLoopBackOff   503        1d
mysql-operator-orchestrator-0    1/1       Running            1          1d

{"level":"error","ts":1559749695.6542397,"logger":"mysql-operator","msg":"unable to setup controllers","error":"no matches for kind \"MysqlBackup\" in version \"mysql.presslabs.org/v1alpha1\"","stacktrace":"github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/go/src/github.com/presslabs/mysql-operator/cmd/mysql-operator/main.go:95\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201"}

$ kubectl logs mysql-operator-547cfc796-2d6l2
{"level":"info","ts":1559749695.5175185,"logger":"mysql-operator","msg":"Starting mysql-operator..."}
{"level":"info","ts":1559749695.6539948,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"mysqlbackup-controller","source":"kind source: /, Kind="}
{"level":"error","ts":1559749695.6540716,"logger":"kubebuilder.source","msg":"if kind is a CRD, it should be installed before calling Start","kind":"MysqlBackup.mysql.presslabs.org","error":"no matches for kind \"MysqlBackup\" in version \"mysql.presslabs.org/v1alpha1\"","stacktrace":"github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start\n\t/go/src/github.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source/source.go:89\ngithub.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Watch\n\t/go/src/github.com/presslabs/mysql-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:122\ngithub.com/presslabs/mysql-operator/pkg/controller/mysqlbackup.add\n\t/go/src/github.com/presslabs/mysql-operator/pkg/controller/mysqlbackup/mysqlbackup_controller.go:76\ngithub.com/presslabs/mysql-operator/pkg/controller/mysqlbackup.Add\n\t/go/src/github.com/presslabs/mysql-operator/pkg/controller/mysqlbackup/mysqlbackup_controller.go:54\ngithub.com/presslabs/mysql-operator/pkg/controller.AddToManager\n\t/go/src/github.com/presslabs/mysql-operator/pkg/controller/controller.go:29\nmain.main\n\t/go/src/github.com/presslabs/mysql-operator/cmd/mysql-operator/main.go:94\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201"}
{"level":"error","ts":1559749695.6542397,"logger":"mysql-operator","msg":"unable to setup controllers","error":"no matches for kind \"MysqlBackup\" in version \"mysql.presslabs.org/v1alpha1\"","stacktrace":"github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/go/src/github.com/presslabs/mysql-operator/cmd/mysql-operator/main.go:95\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201"}

We use crd-install helm hook to install CRDs. This hook is introduced in helm version v2.10.0 and above.
Please let me if updating helm to newer version fixes your problem.

@AMecea It works.
Maybe we could update the note in the README.md to includes the minimum version of helm. I could make a PR if you want for that.
The note in question:

NOTE: MySQL operator 0.2.x requires at least Kubernetes 1.11.x (or 1.10.x with alpha features) while version 0.1.x is known to work with Kubernetes up 1.9.x. To upgrade, check the 0.2.x upgrade notes as some additional steps are required.

It's a good idea. I will be happy to merge that PR!

I have the exact same problem using an bare-metal k8s cluster with helm v3.0.0-alpha.1.

Helm version 3 introduced major changes. We didn't test the mysql-operator chart with helm version 3 yet because helm is still in alpha.
If you spot the incompatibilities in the helm chart please open another issue to upgrade chart to be comptible with helm 3. Thanks!

Hello,
It still doesn't work with Helm3 :
{"level":"error","ts":1576852138.0194187,"logger":"mysql-operator","msg":"unable to setup controllers","error":"no matches for kind \"MysqlBackup\" in version \"mysql.presslabs.org/v1alpha1\"","stacktrace":"github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/presslabs/mysql-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/go/src/github.com/presslabs/mysql-operator/cmd/mysql-operator/main.go:95\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}
best practice for crds in helm 3 : https://helm.sh/docs/topics/chart_best_practices/custom_resource_definitions/


Add notice in documents when  multi-row insert list and retrieve the auto-generated keys

Fix #1113
Add notice in documents when  multi-row insert list and and retrieve the auto-generated keys

Hi @lovepoem ,
Thanks for the PR !
I am actually writing a patch that improves the behavior.
I'll let you know when it's ready.

Close this via https://github.com/mybatis/mybatis-3/pull/1249


Implement Connector.

What change does this introduce?
This PR adds the Connector type which is an implementation of the TargetObserver interface. Whenever it is notified of a new target it attempts to dial a gRPC connection to that target. If it is successful it notifies a ConnectionObserver (an interface also introduced in this PR).
If/when the target is "undiscovered" it notifies the ConnectionObserver that connection is now unavailable then closes it.
Why make this change?
This is part of the migration from configkit.  The connector is organised as a separate component so that the responsibility for dialing discovered gRPC targets is separated from the discovery logic itself.
Is there anything you are unsure about?
~No~ Edit: I'm not sure if this is the best decision, but I have made the ConnectionObserver interface work with connections via the grpc.ClientConnInterface interface, as opposed to accepting a *grpc.ClientConn directly.
The rationale for using the interface is that it insulates the observer from specifics of the connection implementation. The observer should be able to use the connection to construct specific service clients, but it should not be able to close the connection.
What issues does this relate to?
Partially addresses #1.

Might make another quick change to this before you review.

Actually, nevermind!


adding pull_request event for CI/CD

Pull Request Test Coverage Report for Build 550900862

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

Totals

Change from base Build 550894947:
0.0%

Covered Lines:
1712

Relevant Lines:
1760

💛  - Coveralls


allow addCardLink to be string as well as component

it helps to change only text instead of passing component

my mistake

replaced with clean PR


Updated TranslationData model in Nuget Package

Hi,
When we could have a new package in Nuget with this PR https://github.com/LordMike/TMDbLib/pull/408 ?
Current version is 1.9.2, and is not working.
I tried to download the package from
https://nuget.pkg.github.com/LordMike/index.json and https://api.nuget.org/v3/index.json
And it doesn´t work, but when I build code directly it works fine.
Thank you

I've marked the latest as 2.0.0 (because of breaking changes), it should be available soon.


Adding django3 testing in tox matrix.

Using this package extensively. So it would be helpful if new version release with django3.2 support.
Tests are not running.
Since June 15th, 2021, the building on travis-ci.org is ceased. Please use travis-ci.com from now on.

@sergei-maertens Please review.

Sorry for the quiet and thanks for the contributions! Hopefully I can take
a look this weekend :-)
On Fri, 9 Jul 2021, 09:14 Awais Qureshi, @.***> wrote:

@sergei-maertens https://github.com/sergei-maertens Please review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bigjason/django-choices/pull/73#issuecomment-876970860,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKDJVVHYMATFUF4XGYWVMDTW2OXFANCNFSM47UHZU5A
.

@awais786 thanks for the contribution! was very busy and this constantly fell of the radar. I'll migrate to Github actions in the next couple of hours, and will include your changes to the build matrix.

@awais786 I'm going to close this PR since I've included the content in the Github Actions migration. Feel free to add yourself to CONTRIBUTORS.md though, as you provided valuable input!


expose Tileset TileMode to GDScript

closes #18066

Thanks!

Now that Godot 3.1 has been released, we don't plan to cherry-pick new features and enhancements to the 3.0 branch, unless there is very strong support in favor of it. Removing cherrypick label for 3.0.


Please clarify documentation about zones and nat gateway

[Enter feedback here]
tested , aks cluster created with zones 1 2 3 , enabled was able to communicate.
please clarify in documentation , aks NAT gatway will work fine for outbound traffic when multiple availability zones are used
az aks create --resource-group myresourcegroup --name natcluster --node-count 1 --outbound-type managedNATGateway --nat-gateway-managed-outbound-ip-count 1 --nat-gateway-idle-timeout 30 --zones 1 2 3

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

ID: e3ea12e7-6e6d-cfa1-b094-2f33e2e7b64b
Version Independent ID: cd0f7701-6a0a-425c-1da2-29683db39ef9
Content: Managed NAT Gateway (preview) - Azure Kubernetes Service
Content Source: articles/aks/nat-gateway.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: juda

Thanks for the feedback! We are currently investigating and will update you shortly.

#reassign:schaffererin

Hi, @porrascarlos802018, thank you for your feedback. I apologize for the delay in receiving a response.
I've looked into your feedback, and I concur - it'd be useful to make mention of defining availability zones when creating the NAT gateway resource. I created and signed off on a PR with an update to the doc regarding zones. I will now close this GitIssues. Thank you again!
#please-close


Documentation: Clarify dates option in flag_imputation argument for derive_vars_dt()

Please select a category the issue is focused on?
No response
Let us know where something needs a refresh or put your idea here!

Definition of Done

[ ] Documentation is update to clarify argument options
[ ] Verify if updates to other Date/Time functions need updates
[ ] Review vignettes and templates to see if updates are needed.

A good solid update!  @pharmaverse/admiral any takers?

@PoojaKumari05 can you complete this by the end of the week?  We have a soft release on Monday December 4th

@PoojaKumari05 can you complete this by the end of the week? We have a soft release on Monday December 4th

Sure @bms63 - Will get the PR created by Friday morning.