icon doesn't show right, it turns into white block

Rules
To report a bug and help us to provide the solution as fast as possible, please follow the instructions below:
1 - Describe the bug
I set the right icon path in initialize function, and I set the right icon file in the right file. Notifications could be created and displayed, but the icon doesn't show right, it turns into white block.
2 - Provide us as much information as possible

Your plugins list inside the file pubspec.yaml (at least all notification plugins)
awesome_notifications: ^0.7.4+1
What platform did you found the issue
Android
How are you initializing the plugin

      AwesomeNotifications().initialize(
      'resource://drawable/launcher_icon',
      <NotificationChannel>[
        NotificationChannel(
          channelKey: keyRemindChannel,
          channelName: '提醒',
          channelDescription: '自律帮的提醒功能使用这个通知。',
          channelShowBadge: false,
          playSound: true,
          enableVibration: true,
          enableLights: true,
        ),
        NotificationChannel(
          channelKey: keyTimingChannel,
          channelName: '计时器',
          channelDescription: '自律帮的计时器提醒功能使用这个通知。',
          channelShowBadge: false,
          playSound: false,
          enableVibration: false,
          locked: true,
          onlyAlertOnce: true,
        ),
        NotificationChannel(
          channelKey: keyTimerFinishChannel,
          channelName: '计时到时提醒',
          channelDescription: '自律帮的计时到时提醒功能使用这个通知。',
          channelShowBadge: false,
          playSound: true,
          enableVibration: true,
          locked: true,
          onlyAlertOnce: true,
          enableLights: true,
        ),
      ],
    );

How are you creating the notification

        final TimeOfDay time = TimeOfDay(
          hour: int.parse(reminder.remindAt.substring(9, 11)),
          minute: int.parse(reminder.remindAt.substring(11)));
        AwesomeNotifications()
          .createNotification(
        content: NotificationContent(
          id: reminder.createdAt ~/ 1000,
          channelKey: keyRemindChannel,
          title: reminder.title ?? '无标题',
        ),
        schedule: NotificationCalendar(
          hour: time.hour,
          minute: time.minute,
          month: reminder.month,
          day: reminder.day,
          weekday: reminder.weekday,
          allowWhileIdle: true,
          preciseAlarm: true,
        ),
      )

The output of flutter doctor command
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.8, on macOS 13.2 22D49 darwin-arm, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.74.3)
[✓] Connected device (4 available)
[✓] HTTP Host Availability

3 - How To Reproduce the Error
Steps to reproduce the behavior:

Use Android physical or virtual device
Set the icon file and initialize
Create a notification
See error

4 - Expected behavior
A clear and concise description of what you expected to happen.

5 - Screenshots

6 - Additional context
my icon file

my folder screenshot

You must create your icon using transparency and it needs to be monochrome. You are using the same app icon in your notifications and this icon must be different. If the Android distribution accepts a different type of icon, like the colored icon you are trying to get in your example, Android itself will bring your app's icon and replace it, like xiaomi devices do. You don't have to do anything about it, it's beyond your control.

At yesterday afternoon, I think what you reply is the only way I can solve this question.
However, at yesterday night, the notification icon displayed on phone turned into colorful pattern as I expected. I can't know the reason, because I think I do nothing to it.
Anyway, the question has solved.
Thank you very much!


FEAT: add funding source fallback and VoidWallet warning for frontend

introduces a fallback to VoidWallet if the funding source is not responding after 30s on startup

only falls back if adminui is enabled!
makes the api come up even if the fundingsource is not responding
should not interfere with wallets that got disconnected after startup

Codecov Report

Merging #1559 (235513f) into main (6f194fe) will decrease coverage by 0.23%.
The diff coverage is 11.76%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1559      +/-   ##
==========================================
- Coverage   46.87%   46.65%   -0.23%
==========================================
  Files          48       48
  Lines        6842     6855      +13
==========================================
- Hits         3207     3198       -9
- Misses       3635     3657      +22

Impacted Files
Coverage Δ

lnbits/app.py
43.37% <0.00%> (-2.01%)
:arrow_down:

lnbits/settings.py
86.29% <33.33%> (-0.45%)
:arrow_down:

lnbits/helpers.py
67.92% <100.00%> (+0.30%)
:arrow_up:

lnbits/db.py
76.51% <0.00%> (-6.05%)
:arrow_down:

lnbits/commands.py
57.89% <0.00%> (-1.76%)
:arrow_down:

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


Keep RELEASENOTES.md updated

It would be awesome if you could keep the changelog updated - maybe take a look at https://github.com/conventional-changelog/standard-version for automatic changelog generation?
Thanks in advance guys & girls! 🚀

Yeah, I had plans to start using the same release scripts we use for the rest of projects at ionic in this one. Thanks for opening an issue.

@timbru31 first step: same script for publishing than the ionic framework:
npm run deploy

It will update package.json and sync plugin.xml

@manucorporat   RELEASENOTES.md remains outdated.
;)

Seems you guys are keeping the release notes up to date now. Awesome!


Update dependencies, bump version to v2.3.0

Updated all dependencies to latest except Stylelint, which is updated to v15.11 as v16 results in jest issues. We might want to switch to vitest.
This PR does not include the changelog or the npmrc file.

Thank you!


Migration Refresh On Dev

If you have allowed logging on local IPs (127.0.0.xxx etc) and try and do a Migration, it will fail.
I assume its cause its trying to log things which are not ready yet.
Although not a major problem, really it should be hard coded in, that if its migrating - all logging is disabled - even tho logging is on (as per installation instructions)

Well, I commented it:
'do_not_track_ips' => [
	// '<IP_ADDRESS>/24' /// range <IP_ADDRESS> - <IP_ADDRESS>
],

Then did a migrate:refresh and it worked :(
 $ a migrate:refresh
Artisan found at /var/www/tests/l4/artisan
**************************************
*     Application In Production!     *
**************************************

Do you really wish to run this command? y
**************************************
*     Application In Production!     *
**************************************

Do you really wish to run this command? y
Rolled back: 2015_02_23_183505_create_dummy_table
Rolled back: 2015_02_23_174214_create_users_table
Rolled back: 2015_02_23_173501_create_tracker_tables
Nothing to rollback.
**************************************
*     Application In Production!     *
**************************************

Do you really wish to run this command? y
Migrated: 2015_02_23_173501_create_tracker_tables
Migrated: 2015_02_23_174214_create_users_table
Migrated: 2015_02_23_183505_create_dummy_table

Could you, please, help me reproduce it?

Did you run any seeding?

No seeding.

I understand ´migrate:refresh´ could be a problem, because it does a ´migrate:reset´, which is supposed to drop all tables and having no tables it would raise an exception while trying to insert on them. Seeding comes after ´migrate´, it should not be a problem.

Closing for now, if you still need support, ask for a reopening. Thank you.


Autoplay animations if included in gltf file, fix arm26_elbow_flex.gltf

When you pick the model for marker data it now animates, we can use that to demo the trc, grf, c3d file conversion for now until models and animations are implemented

For your review @AlbertoCasasOrtiz Eventually we want to customize play speed/repeat/fade etc. with ui but that's useful to check if animations are exported properly

Not sure what you mean by weird movement, but if a gltf contains an animation it should autoplay, others should have no effect. Only file in repo with stored animation is the arm26 marker data file. Please let me know if anything else has changed.
The PR is still pending your approval.

pending approval @AlbertoCasasOrtiz

@aymanhab Sorry, I though I did this yesterday. I just approved it.


Remove remote debugging from dev menu

Summary:
This PR proposes the removal of the ability to use remote JS debugging (a.k.a Chrome Debugging) from the DevMenu.
This change has been suggested previously on the contributor's Discord server and it is motivated by the fact that generally speaking, this feature does not work with the new architecture and most of the popular modules these days. The remote JS debugging is basically broken if you use Turbo Modules, Fabric, or sync native module calls.
People tend to assume that if something is part of the dev tools UI, it is going to work reliably. However, when it comes to remote debugging using JSC that's increasingly unlikely to be the case. Having it continue to exist as an option has created some confusion, or at least that's what we've seen within the Expo community.
How to manually enable remote debugging
If your project depends on remote debugging, you can still enable it manually through the NativeDevSettings. E.g.
import NativeDevSettings from 'react-native/Libraries/NativeModules/specs/NativeDevSettings';

export default function App() {
  return (
    <Button
      title="Enable remote debugging"
      onPress={() => NativeDevSettings.setIsDebuggingRemotely(!true)}
    />
  );
}

Next steps
Once this has been released and we are sure that this doesn't cause a lot of problems for people we can remove the ability entirely in a follow-up PR
Changelog:
[General] [Removed] - Remove remote debugging from the dev menu
Test Plan:
Locally run rn-tester using JSC on Android and iOS and open the dev menu

iOSAndroid

cc @huntie, @voideanvalue who are working on debugger integrations

Personally I think we should probably keep this under the Old Architecture and only remove it for the New Architecture. cc also @cortinico for thoughts.

Personally I think we should keep this under the Old Architecture and only remove it for the New Architecture. cc also @cortinico for thoughts.

That's a good alternative to me. We'll be looking into alternatives for debugging within the New Architecture, so we might need to revive this solution (or a different one) in the near future.
But I totally agree with the intention that whatever shows up on the Dev Menu should reliably work otherwise it just creates more frustration.

I'm in favor of removing this option entirely, or if we do keep it, then we should update the text to indicate that it is unlikely to work. Most projects use modules that are incompatible with remote debugging these days, and I think it creates a bad experience to provide this as an option when it doesn't typically work.

Most projects use modules that are incompatible with remote debugging these days

@brentvatne could you clarify? My understanding is that the new architecture doesn't support remote debugging - are there popular modules that break debugging under the old architecture, as well? Or were you referring mainly to the difference between the new and old architecture?
More generally, can we put together a small matrix of supported configurations of RN and make sure we have a working debugging workflow for each one? e.g. for the following combinations of architecture and engine (which are all still supported in RN, AFAIK), I believe these are the best options we have to offer: (Please correct me where I have the facts wrong / missing)

New arch
Old arch

Hermes
Direct debugging over CDP
Direct debugging over CDP

JSC
Direct debugging with Safari?
Remote debugging?

My main point with regards to this PR is that we shouldn't take away remote debugging in configurations where there's no current alternative. Totally happy for us to remove it where it's properly superseded by something better, like direct debugging, but I'm not sure if we currently have the information required to render the appropriate dev menu for each configuration.
For context, @huntie is currently working on clarifying React Native's debugging docs & tooling integrations. We'd like to consider this (or a similar change) holistically as part of that.

@motiz88 - here is an example of one of the most popular react-native libraries not working with remote JS debugging with JSC: https://github.com/brentvatne/example-jsc-debugging. You can clone that repo and run npx expo run:ios (or npx react-native run-ios if that tickles your fancy), notice that the app works as expected, then once you enable remote JS debugging you won't get much more than red screens and crashes. Many libraries have migrated to using JSI and don't work with remote debugging and the failure mode is very frustrating.

I believe developers should use "Direct debugging with Safari" in both new and old architectures if they must use JSC. I confirmed that these instructions work well in the repo shared above.

@brentvatne Given that direct Safari debugging works well¹ in JSC, I'm not in principle opposed to deprecating remote JS debugging. From my perspective we'd need not just this dev menu change, but a docs change and a clear callout in the release announcement where this lands. Also following up to delete the remote debugger code (in a subsequent release?) would be great.
¹ FWIW, per the docs it does look pretty rough around the edges: no source maps out of the box and each reload disconnecting the debugger both sound like a clearly worse experience compared to remote debugging at its best, but I appreciate that that may be moot given the existence of popular libraries that hard-break remote debugging.

@motiz88 - agreed! we'll need to update the documentation for this change and also include it in the release notes. ideally this is cherry-picked in 0.72 - @gabrieldonadel is going to send a docs PR and will follow up with adding information to the release notes as well

@brentvatne Great! 👋🏻 I'm happy to review PRs and support this effort (currently also looking at our JS Debugging options).

@huntie @motiz88 I've just opened a PR (https://github.com/facebook/react-native-website/pull/3702) updating the docs to reflect this change and adding a few more sections about debugging

hey folks - maybe next time involve the release crew if you think of adding something last minute to the release that is in the works.
That said, the Direct debugging with Safari feature at least in the docs is mentioned specifically only for iOS; what about Android developers? Unless it actually works for Android too I don't think at the moment there is one compelling alternative that works out of the box with all platforms (Flipper? and I'm pretty sure we shouldn't be telling folks to double down on Flipper).
Also, since it's Safari bound, what about developers not on macos?

Flipper? and I'm pretty sure we shouldn't be telling folks to double down on Flipper?

Why not talk about flipper? The debug button on the dev menu is hard-coded to open it
https://github.com/facebook/react-native/blob/65f5cd79950f07ce54df89f0c837784e64384226/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/devsupport/DevSupportManagerBase.java#L412-L433
https://github.com/facebook/react-native/blob/65f5cd79950f07ce54df89f0c837784e64384226/packages/react-native/React/CoreModules/RCTDevMenu.mm#L266-L286
Users can also use debug JS on Hermes using Google Chrome's DevTools as stated here -> https://reactnative.dev/docs/hermes#debugging-js-on-hermes-using-google-chromes-devtools

Why not talk about flipper?

I'll let the Meta folks share more, but the gist is that there's an effort to rethink the entire debugging story and Flipper might not be part of that given how many troubles people have when using it (https://github.com/reactwg/react-native-releases/discussions/64). So we should not push people towards something that might not be the right long term option.

Users can also use debug JS on Hermes using Google Chrome's DevTools

That doesn't cover users on JSC or other engines.
Echoing what @huntie said in the other PR (https://github.com/facebook/react-native-website/pull/3702#pullrequestreview-1399502523) I think it's better to think of this effort as something for 0.73 and onward, to give time to come up with a solution that will allow all developers to use something viable.


Avoid loading node html if disableEditor set

[x] New feature (non-breaking change which adds functionality)

Proposed changes
This change modifies how nodes are loaded so that if disableEditor is set, we now skip loading the node html into memory.
This shaves a small amount off the startup time - not as much as I'd hoped. But it will save a bit of memory usage.
It still loads the locales files as a node may have runtime messages in its catalog.
Checklist

[x] I have run grunt to verify the unit tests pass
[x] I have added suitable unit tests to cover the new/changed functionality

Coverage decreased (-0.2%) to 77.072% when pulling 33855bcb8b40d519eec61eaa83c8c986c0f5d083 on skip-html into bcd85b11a13b3abed2e0c9ab5abd3d4d7e30529b on dev.


mismatch between railtime info and iRail

For several years now, I've been running a small website that keeps track of the delays users encounter when going to (and from) work on a daily basis. It's been working extremely well. It's similar to belate.be, with that exception that this app can process cross-overs ("overstap" in English?) between stations and does a few more things automatically for the end-users. I've been keeping it low-profile, because history teaches us that the NMBS likes to threaten juridically projects like these, as iRail no doubt knows. ;-)
Recently I've been looking into the iRail API again, to get the source data from, but I find that it deviates sometimes from the data published by infrabel. As an example (time limited due to infrabel's website), check out train 3639 from Landen to De Panne on 2015-01-05. Compare this to the third option in the list of possible routes between Aalst and Gent-Sint-Pieters from that same timestamp.
If needed, I'll try to find another example that is valid for another week.
Anyway: why is this data different? I don't know enough about the iRail code to know where it gets its source data from, even though I've been keeping the iRail project in my mind since the beginning of this app.
Edit: is it because I'm misunderstanding the iRail representation of data? That it doesn't take retardations into account?

Apologies for the late comment, I haven't been keeping up with the developments here for a while. I believe that this issue might be relevant for the scraper repository. (This repository is mostly front-end stuff and does some data conversions, experiments into hypermedia API etc.)
You can find the scraper repo here: https://github.com/iRail/iRail

Thanks for the redirect. I've opened the issue over there as number 39. Feel free to close this one.


Configuration error in custom extractor

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1568
Originally created by @Ayushj250 on 2020-01-15 07:22:32

Hi,
I am working with tap-postgres and target-postgres but having a configuration error in tap-postgres. I have already read the full tutorial and there is no info regarding the problem.
Can any one help me? I will be grateful to you.

View 4 previous comments from the original issue on GitLab


Netlify CLI is only compatible with Node 15 as of earlier today

Describe the bug
We use the netlify-cli package on our CI servers as part of our deployment process. As of earlier today it has started failing to install because of an incompatible Node version. The install log is shown below in the CLI output section.
To Reproduce
Steps to reproduce the behavior:

Install Node 14 or earlier
Install Netlify CLI

Configuration

If possible, please copy/paste below your netlify.toml.
Please enter the following command in a terminal and copy/paste its output:

Expected behavior
Netlify CLI installs and runs successfully.
CLI Output
yarn global add<EMAIL_ADDRESS>Failed in 00:27
yarn global v1.22.5 00:05
[1/4] Resolving packages... 00:05
warning netlify-cli > @netlify/plugin-edge-handlers > rollup-plugin-node-polyfills ><EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject. 00:07
warning netlify-cli > copy-template-dir > readdirp > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated 00:07
warning netlify-cli > copy-template-dir > readdirp > micromatch > snapdragon > source-map-resolve ><EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated 00:07
[2/4] Fetching packages... 00:27
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module. 00:27
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation. 00:27
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module. 00:27
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation. 00:27
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module. 00:27
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation. 00:27
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=15.0.0". Got "10.22.0" 00:27
error Found incompatible module.

Additional context
I'm running this on Semaphore CI in case that's useful.

Hi @Haegin, can you share the output of npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli?
<EMAIL_ADDRESS>is a dev dependency so it should not be installed.
Can you:

Update your npm version via npm install -g npm
Install via npm via npm install -g netlify-cli

I experienced this earlier today in github actions

Hi @Wyfy0107 this should be fixed in https://github.com/netlify/cli/releases/tag/v3.30.2.
Can you try via yarn add global netlify-cli?


Make Object Pool Size and Reuse Limit Tunable

Main Changes:

assign a size limit to an object pool to control the maximum objects an object pool can manage
throw an exception when an object pool cannot handout more objects
make object pool size_limit and reuse_limit tunable
add more object pool tests

I also changed AlignedByteAllocator implementation so that it doesn't allocate unnecessary memory when the size of the object is multiple of 8.

I also changed delta_record_test to avoid object pool exception introduced by the new code

Coverage decreased (-0.2%) to 97.812% when pulling e2e8c8ac890ad0a1b81f945e7af2a067605b99e7 on yangjuns:object_pool into 33f4af3ca523987eec42d5c05131c7c05f4b9f90 on cmu-db:master.

Seeing latches and concurrent data structures mixing together in the control flow concerns me. Let's white board this tomorrow and see if we can streamline the logic a bit.

By the way, at @mbutrovich's relentless request we are using posix_memalign like on this branch https://github.com/cmu-db/terrier/tree/tianyu-cleanup

FYI you still have doxygen failures on Travis


Fix error message, issue #2795

Updated message as suggestd

Changing \n to PHP_EOL would cause different response under windows. This would make it harder to tests. The response must always be the same, independent where the server is running.

We need to discuss further in #2795 before PRs are raised. Follow there


Fail fast on initializing with a different project's databaseUrl

Originally filed in https://github.com/firebase/firebase-functions/issues/1191 and on StackOverflow.
Hi all! Thanks for Firebase, it's great!
I recently tried to set up a Firebase Cloud Function to trigger on a Realtime Database owned by a different project: the Hacker News API. I passed databaseUrl: https://hacker-news.firebaseio.com/ to admin.initializeApp(), and it deployed fine, but it never triggered.
I eventually learned that Firebase just doesn't support triggering across projects like this. Fair enough. Could you consider failing fast and reporting an error in this case? That would have saved me a fair amount of debugging.
Code below. Thanks in advance!
const functions = require('firebase-functions')
const admin = require('firebase-admin')
admin.initializeApp({databaseUrl: 'https://hacker-news.firebaseio.com/'})

exports.itemUpdated = functions.database.ref('/v0/item/{id}').onCreate((snapshot, context) => {
      functions.logger.log('Item: ', context.params.id, snapshot.val())
      return null
})

Since the database URL doesn't always contain the project ID (you can create a new database with any random string in the URL) I don't think this is something we can check on the SDK side. Closing this as won't fix.


New Simple Scrobbler not working

Ever since Simple Scrobbler for Android was updated it doesn't scrobble anymore.
Once the logo of the icon changed I went to see if there are any changes only to find out I was logged out.
There are 5 things you can login into: Last fm, Libre fm, ListenBrainz, GNU-FM Server and ListenBrainz Server.
I have no idea what the last four are so I just logged in into my LastFM account.
But not only that any music I play isn't scrobbled, my profile is completely empty..
Last scrobble submitted at: Never
Last now playing notification submitted at: Never
Scrobbles in local cache:0
Total tracks scrobbled:0
Total now playing notifications: 0

Can I ask what permissions you have enabled?
Can I ask what version of Android you are running?

Can't connect to last.fm server, too, but it looks like Simple Scrobbler isn't to blame, since foobar2000 (Win 10) can't submit scrobbles either atm.
Log reads:
[11:27:16] Audioscrobbler: Internal Server Error (500)
[11:27:16] Audioscrobbler: Waiting 60 seconds to retry.
[11:28:00] Audioscrobbler: Still awaiting handshake. Cache contains 2 tracks.
[11:28:19] Audioscrobbler: Internal Server Error (500)
[11:28:19] Audioscrobbler: Waiting 120 seconds to retry.

Update: Everything is back to normal.

Nothing is back to normal for me. My Android version: 8.0.0
Sony Music Player and Winamp are two enabled apps.
I'm only logged into my Last.fm account.

Hi boiler-maker,
Is there anyway I can help you debug this problem?
If it can detect the music apps, usually it detects the music playing.
Any chance you'd be willing to run a debug log capture command?

You gonna have to help me with that cause I have no idea how to do that.


Replace deprecated AspNetCore dependencies

More specifically:

Microsoft.AspNetCore.StaticFiles
Microsoft.AspNetCore.WebUtilities

See https://github.com/dotnet/announcements/issues/217, waiting for updated packages to become available.
As the current versions can still be used and restored, this is not an urgent issue at the moment.

Solved this by adding a framework reference to ASP.NET Core and removing the deprecated libraries.
See https://github.com/basdijkstra/rest-assured-net/commit/3c5843f3924423c48d9cde30a42761536efe6319.


Scaffolding problem with BIT type fields

From @lm28 on September 13, 2018 7:56
Note: If filing an issue related to using Scaffolding within Microsoft Visual Studio, please file an issue on the Microsoft Developer Community instead of here. This can be accomplished from Visual Studio by clicking on Help > Send Feedback, and choosing the appropriate action.
Steps to reproduce:
When creating my tables (in SSMS) the script for one of my tables is as follows.

If the record is marked as 'Obsolete' then it will not be available for selection.
Now when I run 'Scaffold-DbContext' to create the model in my solution, the following related code is generated in the CONTEXT.cs file (I have removed references to all my other tables).
Notice that the Bit type fields (ReturnBit and Obsolete) are not listed here. Im not sure why?
```

public virtual DbSet AdmbuildingType { get; set; }
modelBuilder.Entity<AdmbuildingType>(entity =>
{
	entity.HasIndex(e => e.BuildingTypeCode)
		.HasName("UCbuildingType")
		.IsUnique();

	entity.Property(e => e.BuildingTypeCode).IsUnicode(false);

	entity.Property(e => e.BuildingTypeDescr).IsUnicode(false);

	entity.Property(e => e.LastUpdated).HasDefaultValueSql("(getdate())");

	entity.Property(e => e.ReturnStr)
		.IsUnicode(false)
		.HasDefaultValueSql("('')");

	entity.Property(e => e.Tstamp).IsRowVersion();

	entity.Property(e => e.UpdatedBy)
		.IsUnicode(false)
		.HasDefaultValueSql("('')");
});

``
`And....This is the MODEL that is created by EF.
	using System;
	using System.Collections.Generic;
	using System.ComponentModel.DataAnnotations;
	using System.ComponentModel.DataAnnotations.Schema;

	namespace RACEZ.Models
	{
		public partial class AdmbuildingType
		{
			[Column("AdmbuildingTypeID")]
			public int AdmbuildingTypeId { get; set; }
			[Required]
			[StringLength(20)]
			public string BuildingTypeCode { get; set; }
			[Required]
			[StringLength(150)]
			public string BuildingTypeDescr { get; set; }
			public int? ReturnInt { get; set; }
			public bool ReturnBit { get; set; }			//Hide this field to prevent the Create and Edit propblem.
			[StringLength(100)]
			public string ReturnStr { get; set; }
			[Column(TypeName = "datetime")]
			public DateTime? LastUpdated { get; set; }
			[Required]
			[Column("TStamp")]
			public byte[] Tstamp { get; set; }
			[StringLength(30)]
			public string UpdatedBy { get; set; }
			public bool Obsolete { get; set; }			//Hide this field to prevent the Create and Edit propblem.
		}
	}

Now I create a 'Pages\Adm\BuildingType' folder and then right-click and choose
\Add\ Razor Page \ Razor Pages using Entity framework (CRUD)
Once the process is complete, I rebuild my solution. Now the issues start appearing.
On both the Create.cshtml.cs and the Edit.cshtml.cs files, I am getting a CS1061 error that is related to each of the Bit fields.
The create.cshtml is generated as
	@page
	@model RACEZ.Pages.Adm.BuildingType.CreateModel

	@{
		ViewData["Title"] = "Create";
	}

Create

AdmbuildingType

			<form method="post">

					<input asp-for="AdmbuildingType.BuildingTypeCode" class="form-control" />

					<input asp-for="AdmbuildingType.BuildingTypeDescr" class="form-control" />

					<input asp-for="AdmbuildingType.ReturnInt" class="form-control" />

							<input asp-for="AdmbuildingType.ReturnBit" /> @Html.DisplayNameFor(model => model.ReturnBit))

							<input asp-for="AdmbuildingType.Obsolete" /> @Html.DisplayNameFor(model => model.Obsolete))

					<input type="submit" value="Create" class="btn btn-default" />

			</form>

		Back to List

	@section Scripts {
		@{await Html.RenderPartialAsync("_ValidationScriptsPartial");}
	}

and the create.cshtml.cs is generated as :
	using System;
	using System.Collections.Generic;
	using System.Linq;
	using System.Threading.Tasks;
	using Microsoft.AspNetCore.Mvc;
	using Microsoft.AspNetCore.Mvc.RazorPages;
	using Microsoft.AspNetCore.Mvc.Rendering;
	using RACEZ.Models;

	namespace RACEZ.Pages.Adm.BuildingType
	{
		public class CreateModel : PageModel
		{
			private readonly RACEZ.Models.FACEZContext _context;

			public CreateModel(RACEZ.Models.FACEZContext context)
			{
				_context = context;
			}

			public IActionResult OnGet()
			{
				return Page();
			}

			[BindProperty]
			public AdmbuildingType AdmbuildingType { get; set; }

			public async Task<IActionResult> OnPostAsync()
			{
				if (!ModelState.IsValid)
				{
					return Page();
				}

				_context.AdmbuildingType.Add(AdmbuildingType);
				await _context.SaveChangesAsync();

				return RedirectToPage("./Index");
			}
		}
	}

Incidentally, I also have a few other tables which, when I try to add a Razor (CRUD) page, ALL the cshtml.cs files in the 'Pages\Adm\tableName' folder report a 'CS0118 - tableName is a namespace, but is used like a type' error.
I have no idea yet what is causing that problem??  (The two tables that I have tested this on are name ActType and EnrStage)
Expected behavior:
Bit type fields should be available.
Actual behavior:
Additional information about the project being scaffolded, such as:
Target framework(s):  ASP.Net Core 2.1 EF Razor Page
Package version of Microsoft.AspNetCore.App  or Microsoft.AspNetCore.All (if applicable): 2.1.1
Package version of Microsoft.VisualStudio.Web.CodeGeneration.Design - this may be added to your project by scaffolding:
Copied from original issue: aspnet/Scaffolding#876

From @lm28 on September 15, 2018 3:39
Simplest sample. Create a table where one field type is a BIT, then run the scaffold tool.

From @Rick-Anderson on September 13, 2018 19:4
@lm28 can you come up with the simplest possible sample to reproduce the problem? It's helpful to put the sample on github. You have alot of complexity in your actual code that not necessary to reproduce the problem.

Since this is an issue with EF scaffolder (Scaffold-DbContext), moving to the EF repo.

@vijayrkn What is the EF error here? I don't see anything wrong until "\ Razor Pages using Entity framework (CRUD)" is used, which is not EF code.

@ajcvickers - This was the initial reported issue
Now when I run 'Scaffold-DbContext' to create the model in my solution, the following related code is generated in the CONTEXT.cs file (I have removed references to all my other tables).
Notice that the Bit type fields (ReturnBit and Obsolete) are not listed here. Im not sure why?

@vijayrkn Because they are mapped by convention and so do not need any additional configuration in OnModelCreating. If this is the only issue being reported, then this should be closed by-design, but it looks to me like things are failing later.

@lm28 - Does this answer your questions? If not, can you let us know what is failing during scaffolding? A sample project would definitely help.


php: 8.1.27 patch for libxml2.12

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

libxml currently breaks php 8.1 compilation on MacOS, this patches 8.1 as backporting fixes from 8.2 and 8.3 branches. As 8.1 is a security only release these fixes won't be back portedbackported

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

Hi !
Thanks for your contribution!
I'll leave it to @jtojnar

these are the packages are failed to build:
5 packages failed to build:
php81Extensions.memprof php81Extensions.pinba php81Extensions.zend_test php81Extensions.zend_test.dev php81Packages.php-parallel-lint

without this patch 168 packages failed to build, as php cannot be compiled. unfortunately I couldn't find what could be the solution for these. I also do not have the expertise to solve it, and I spent a full day on trying to find a solution. I let you decide if it's acceptable in its current form.

Question, where is this patch coming from ?

Question, where is this patch coming from ?

https://github.com/php/php-src/commit/0a39890c967aa57225bb6bdf4821aff7a3a3c082#diff-d7dc9f95676b123a308dbb7f3869c22b0fbb0afc5c3218ac01e6d6b48f1bbb73

How about directly using the upstream patch directly (https://github.com/php/php-src/commit/0a39890c967aa57225bb6bdf4821aff7a3a3c082.patch) then ?

line numbers are not matching the 8.1 code base, you can compare my patch with your link.
also I wasn't aware of this feature, so I learned something new. :)

I guess it would be better if we could use an upstream patch directly, does it exists somewhere ?

no, and there won't be any as 8.1 as security fixes only. I asked around, and they don't plan to back port libxml fixes.

@jtojnar WDYT ?

line numbers are not matching the 8.1 code base, you can compare my patch with your link.

Line numbers do not generally have to match, the patch application is slightly fuzzy – the context is what is important.

The patch is being correctly applied:

That looks like php unwrapped, not the soap extension:
building '/nix/store/2wb3binp3dhsil6b4s60sckk2gh1gsp5-php-soap-8.1.27.drv'...
Running phase: unpackPhase
unpacking source archive /nix/store/lijw0wmj09s6v23l4v927aqq7r98xvf1-php-8.1.27.tar.bz2
source root is php-8.1.27
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file php-8.1.27/win32/wsyslog.c
Running phase: patchPhase
Running phase: genfiles

Since this issue is only seen on darwin and not on linux, I wonder if the patch is the proper solution here.
I created an alternative draft PR at https://github.com/NixOS/nixpkgs/pull/285542
Feel free to let me know how it goes with it, I don't have a darwin machine at hand.

Sorry, I had a busy day today and couldn't help. Thank you very much for taking the time to refactor the solution.

It's totally fine, :) I'm so happy we finally came to an agreement!

@GrahamcOfBorg build php81 php81.extensions.soap


Name of useIsBrowser hook and ExecutionEnvironment is misleading and the example given in the documentation needs a note added

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
Hello,
Thanks for the amazing library.
The comment here states that useIsBrowser returns true only if the first hydration has completed.
But opening this Stackblits Example and checking the console, you see logs printed for the below code:
  const isBrowser = useIsBrowser();
  const traditionalIsBrowser = typeof window !== 'undefined';
  const testUrl = isBrowser ? new URL(window.location.href) : undefined;

  console.log('Has completed first hydration?', isBrowser);
  console.log('Are we actually on browser?', traditionalIsBrowser);
  console.log('Test URL:', testUrl);

Outputs before hydration, on first render:
Has completed first hydration? false
Are we actually on browser? true
Test URL: undefined

Outputs after hydration:
Has completed first hydration? true
Are we actually on browser? true
Test URL: URL {origin: 'https://githubev3fmt-xvco--3000.local-credentialless.webcontainer.io', protocol: 'https:', username: '', password: '', host: 'githubev3fmt-xvco--3000.local-credentialless.webcontainer.io', …}

So the name of useIsBrowser actually should be along the lines of hasHydrationCompleted.
When there are a lot of window references in a component, and you try to build the application, you get this error:
It looks like you are using code that should run on the client-side only.
To get around it, try using `<BrowserOnly>` (https://docusaurus.io/docs/docusaurus-core/#browseronly) or `ExecutionEnvironment` (https://docusaurus.io/docs/docusaurus-core/#executionenvironment).
It might also require to wrap your client code in `useEffect` hook and/or import a third-party library dynamically (if any).

ReferenceError: window is not defined

So naturally your first instinct as a developer is to add <BrowserOnly> and useIsBrowser to everywhere you see window references unless you also read about ExecutionEnvironment, which I did much much later after I've already wasted tons of time.
I did not read ExecutionEnvironment up until creating this ticket because the ExecutionEnvironment did not sound like something I might need (I am burnt out enough to skip reading about it even though the error basically tells you to read it) however it's name is also misleading, I understand that it has canUseDOM for such use case but maybe it should rather be something along the lines of CanUse with:

CanUse.DOM
CanUse.IntersectionObserver
CanUse.Viewport

What ExecutionEnvironment.canUseDOM does is actually what useIsBrowser should be doing therefore maybe these can be extracted into several hooks with appropriate names.
As a rule of thumb while naming things, I tend to name them according to what they are doing. So these would be:

useIsWindowDefined
useAreEventsInWindow
useIsIntersectionObserverInWindow
useIsScreenInWindow

When you have code like this:
const testUrl = new URL(window.location.href),
you end up making it (that is also what useIsBrowser documentation tells you to do)
const testUrl = isBrowser ? new URL(window.location.href) : undefined
But because you just added isBrowser and make it purposefully return something else such asundefined, the code dependent starts acting as it should not. Then if you have tons of code that relies on testUrl and you suddenly return undefined with it, you end up modifying the entire stack of code to compensate for testUrl being undefined.
Now on the same Stackblitz example change the URL to include ?params=test123. You will see in the page under "Docusaurus Tutorial - 5min" area, the value rendered is "defaultValue" which is wrong (actually correct in terms of how React works with useState however wrong in terms of the end business goal). The correct would be test123
You start digging into what might be the reason and come to realization that you actually don't need to put isBrowser ? there at all because window.location.href in the browser is actually defined because after all literally the log you see is being printed in browser's console so why useIsBrowser is false, you start to wonder. When you remove isBrowser ? the code starts working but then the build fails with the above message again. Then you either go back to the documentation to read about that non-bold part easy to miss or dig into the source code of Docusaurus like I did to learn about Perils of Hydration.
As it is very cumbersome that you have to not only compensate now for the value being undefined, you also need to compensate for the fact that it may have falled back to another value. You start adding isBrowser checks for those parts too like const someQueryParam = isBrowser ? useState(isBrowser ? then it starts to not feel the right thing to do and look for another solution. I ended up doing this Stackblitz example with a proxy. Include ?params=test123 in the URL and the value rendered is now the expected value. Just to remind you that I did not read about ExecutionEnvironment yet at this point but even if I did, I would still be forced to do this proxy implementation with ExecutionEnvironment.canUseDom instead of traditionalIsBrowser in that code.
I would normally suggest changing the implementation of useIsBrowser to typeof window !== 'undefined' because as the developer, the goal of yours is to have your app build successfully by bypassing window being undefined. You don't care about perils of hydration, you just want to get your app built. But I've run into the problem of mismatching rendered HTML tons of times in NextJS and I know how painful it is to debug that so it makes sense to keep the best practice and don't change the implementation.
So an alternative we can do is to change the name of useIsBrowser to useHasHydrationCompleted but that would lead to many dependent applications breaking on the next version. Then we could add another hook useIsWindowDefined that does typeof window !== 'undefined' and then document it together with hasHydrationCompleted so people that are just getting started could use them together. Existing applications could maybe utilize codemods, and on next upgrade of an existing application, the codemod could run automatically and rename it and if it is possible that the codemod can add, then also add the useIsWindowDefined automatically.  We can also link in the documentation simplified and shorter version of The perils of Rehydration article to help them explain why both of them need to be used.
Alternatively, if we don't change any names and leave it misleading as is, I have another suggestion in addition to having new hook called useIsWindowDefined (as changing name of ExecutionEnvironment, is yet another set of breaking changes and codemodes to write):

improve the error message printed when build fails due to window problems to also document useIsBrowser linking to the documentation

It looks like you are using code that should run on the client-side only.
To get around it, try using one of:

<BrowserOnly> (https://docusaurus.io/docs/docusaurus-core/#browseronly)
useIsBrowser and useIsWindowDefined hooks together (https://docusaurus.io/docs/advanced/ssg#useisbrowser)
ExecutionEnvironment (https://docusaurus.io/docs/docusaurus-core/#executionenvironment)

It might also require to wrap your client code in useEffect hook and/or import a third-party library dynamically (if any).

improve useIsBrowser section that explains after first client render part a bit more clearly:

You can also use the useIsBrowser() hook to test if the component has completed it's hydration. It returns false in SSR and true is CSR but only after first client render. If your build fails because window is undefined, and you actually need to check if you are in browser environment, you should combine this hook with useWindowIsDefined hook because this hook will return false when actually in browser environment and hydration has not completed and this may result in some of your code client side code that also rely on window not working properly. The example below kind of indicates that window.location.href is only available after first client render has completed, however it is actually already available when typeof window is defined, even before the first hydration has completed.
Use this hook if you only need to perform certain conditional operations on client-side, but not render an entirely different UI.

I can have a PR for this, but I am not a native English speaker thus the wording would require a review on the PR and also I just need confirmation which path to take, as what I think "may be right" could be wrong for someone else thus we should come up with an optimal solution as the community then create a PR for it
Self-service

[x] I'd be willing to address this documentation request myself.

Hey,
That's a lot of text, hard to follow and I'll only get back to Docusaurus next week.
Maybe try to explain in a concise way what you are trying to achieve exactly, and I'll look into it once I have time.
The useIsBrowser() is indeed false on the first client render/hydration.

I would normally suggest changing the implementation of useIsBrowser to typeof window !== 'undefined'

We can't do that because React server-side-render and first client-side-render must render exactly the same thing. The behavior of useIsBrowser() is actually a way to prevent you from shooting in your own foot by doing what you seem to want to do, which will lead to React hydration mismatch problems. These problems are not apparent on React 17 (Docusaurus v2), but will throw exceptions on React 18 (coming with Docusaurus v3)
There are many articles online about these problems, for example https://www.joshwcomeau.com/react/the-perils-of-rehydration/

I'm sorry, I didn't have time to analyze all of your text in depth this week, but will look into it next week. Please try to be concise and talk about a specific problem you are trying to solve, instead of trying to say what you think we should do. I'll explain to you why we have this behavior, and how to overcome your problem based on a more concrete use-case. A wall of text is hardly actionable from my perspective and is likely a time sink leading to long discussions, time that I'd rather spend on other more concrete tasks. Hope you understand.

@slorber yes I do understand that there are more pressing concerns and you'd prefer having the text shorter.
I can only do a TLDR as a comment because I do think the above wall of text, actually clearly describes the issue if you give it the time to read. There are nothing that says "you should do", it just says "I think this makes more sense and I am willing to contribute" and that you can only understand when you actually read the text. I think I did a good job of explaining the problem with enough examples and links to the appropriate areas and potential suggestions so that I can actually contribute by some guidance from you, as the maintainer. You could have actually saved minutes of your time trying to explain me things that I already explain myself as part of the description. Anyways the TLDR is:
"We" need to "improve" parts of the build error messages about window being undefined and the part that explains useIsBrowser in the documentation because clearly, as that huge wall of text tries to explain, useIsBrowser does a different thing then what it's name states. It does useHasHydrationCompleted kind of behavior.
Anyways I don't have any blockers and no further enquiry about this task, again want to thank you and the community for the awesome library. Please let me know if I can be of help.

@slorber I want to apologize for the huge wall of text. I created a PR with some code examples that explains the issue, it is obviously up to you to merge, my main motivation is to prevent another user from having the same confusion and be of help.
The huge wall of text is trying to actually explain the source problem whereas the PR is just a temporary remedy. It is up to the team and community to discuss further or not.

Hey @nynevi, I understand where you come from, how the name of this hook and all the hydration mismatch thing can be confusing sometimes.
For what it's worth, I think even if the name feels unintuitive, we document its behavior quite enough already:

https://docusaurus.io/docs/docusaurus-core#useIsBrowser
We could rename this hook to useHasHydrationCompleted but I think it's actually not too bad. If it was named useHasHydrationCompleted() then people may not find/use it and decide to use typeof window instead or something else we don't want.
We are not alone using a confusing name, the useSyncExternalStore exposes a getServerSnapshot() method that is also run on the 1st client hydration. This is IMHO a good way to encourage users to do the right thing and prevent hydration mismatches by default. See https://beta.reactjs.org/reference/react/useSyncExternalStore#usesyncexternalstore

You mention the introduction of a useful useIsWindowDefined() hook instead that would return true even on the first render. This is definitively an anti-pattern. Hooks are meant to be used in React components, and their return values are likely used in the render phase. We don't want that return value to be used in the render phase.
I tried to explain this briefly here: https://twitter.com/sebastienlorber/status/1615329010761842689
To clarify these 4 code snippets all lead to the exact same hydration mismatch problem:
function Comp() {
  const isBrowser = typeof window !== 'undefined';
  return isBrowser ?
 :
}

function Comp() {
  const [bool, setBool] = useState(typeof window !== 'undefined');
  return bool ?
 :
}

function Comp() {
  const isBrowser = useIsWindowDefined();
  return isBrowser ?
 :
}

function Comp() {
  const isBrowser = useIsWindowDefined();
  const [bool, setBool] = useState(isBrowser);
  return bool ?
 :
}

This hook is very likely to use to anti-patterns, unless the return value is only used in callbacks.
For callbacks, ExecutionEnvironment of typeof window is fine.
Hope this makes sense?


Request doesn't work in 4g !

New Issue Checklist

[x] I have searched for a similar issue in the project and found none

Issue Info
Platform: Android, Ios
Flutter: 1.17.4
Dio Version: 3.0.9
Issue Description and Steps
Hello, I have a problem with some users !
The api of the application was down during 3 hours, some who tried to use the application during this period and now can't make a request 3 days later in 4g, but in Wi-Fi it works !
Any idea why no more requests work for them after few days ?
Thank for your help 😇

It's strange but the problem was in the setting of ios => Mobile Data => (app) turn off
Ios have automaticaly turn off application data when the api was down !

I have the same problem，under the 4G network 🙋♂
I used network diagnosis, the result is DNS resolution failure
Flutter: 1.17.0
Dio Version: 3.0.9

Same problem, some iOS 14 users can not access my server under 4G , but can do with WIFI.
Is there any resolution or any one knows why ?

Same problem, some iOS 14 users can not access my server under 4G , but can do with WIFI.
Is there any resolution or any one knows why ?

@litang0908 same issue on android greater then 10, it work when connects using 4g with vpn and wifi but not on 4g

Any problem regarding this is not related to Dio.
Dio uses the Dart platform libraries on mobile devices, so will have the same problem with the plain Dart HttpClient.
You can maybe try the native_dio_adapter and see if that works.


[client-common] Missing rows_before_limit_at_least property in ResponseJSON<T> type

Describe the bug
It seems that the property rows_before_limit_at_least (described here in the docs) is missing from the ResponseJSON<T> type for the client-common library.
This leads to a property doesn't exists error in Typescript although the property can be accessed at runtime.
Current definition
packages/client-common/src/clickhouse_types.ts
export interface ResponseJSON<T = unknown> {
    data: Array<T>;
    query_id?: string;
    totals?: Record<string, number>;
    extremes?: Record<string, any>;
    meta?: Array<{
        name: string;
        type: string;
    }>;
    statistics?: {
        elapsed: number;
        rows_read: number;
        bytes_read: number;
    };
    rows?: number;
}

Expected definition
export interface ResponseJSON<T = unknown> {
    data: Array<T>;
    query_id?: string;
    totals?: Record<string, number>;
    extremes?: Record<string, any>;
    meta?: Array<{
        name: string;
        type: string;
    }>;
    statistics?: {
        elapsed: number;
        rows_read: number;
        bytes_read: number;
    };
    rows?: number;
    rows_before_limit_at_least?: number;
}

Code example
const response = await client.query({ query, query_params, format: "JSON" });
const data: ResponseJSON<T> = await response.json();

console.log({
    statistics: data.statistics,
    rows: data.rows,
    rows_before_limit_at_least: data.rows_before_limit_at_least // property doesn't exists
});

Configuration
Environment

Client version: 1.0.1
Language version: 5.4.5

Thanks for the report. Do you want to open a PR?

Sure can do :+1:

The fix will be released as 1.0.2 on Monday.


Explicitly set seccomp profile for nginx-ingress-controller

How to categorize this PR?

/area open-source security
/kind bug
What this PR does / why we need it:
After https://github.com/gardener/gardener/pull/6741 it is possible to enable cluster-wide seccomp defaulting. Also there is the seccomp defaulting webhook. These do not play well with the nginx-ingress-controller. The nginx-ingress-controller needs a customized seccomp profile which is not well documented (see ref). Also customized seccomp profiles are not trivial to distribute. Some options will be a daemonset or a security profiles operator. Adding the CAP_SYS_ADMIN capability ref can make it work, but this actually alters the provided seccomp profile by enabling additional syscalls. This is not ideal because the container also gains the capabilities of SYS_ADMIN. Read more on seccomp vs linux capabilities here.
This PR explicitly sets the seccomp profile for the nginx-ingress-controller to Unconfined. This is the also what the current default seccomp profile is in kubernetes.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

An issue causing the `nginx-ingress-controller` installed via the shoot's `nginx-ingress` addon to fail to start when cluster-wide seccomp defaulting is enabled is now fixed.

/kind bug

/assign

/test pull-gardener-e2e-kind


LSeg Feature and Evaluate

Hello, @pengsongyou ! Thanks for your great job! I implement my own LSeg feature and evaluate. But unfortunately, it has a big gap with using your multiview-lseg-feature for evaluation.
So I am curious about your implement of LSeg feature extraction. Have you ever used some tricks like multi-scale evaluation? How did you solve the problem that the (320,240) 'image_dim' (240 cannot be divided by 32.). (I just resize to (320,256) and after forward, I interpolate back to (320,240)
Thansk for your reply!

Can you share your lseg feature code, if convenient? My email is<EMAIL_ADDRESS>Thanks!

Hi @HustQBW , as shown in the TODO, the LSeg feature fusion is still under refactorization and cleaning. I will release as soon as it is ready. Stay tuned.


Travis CI: Authentication failed for git push to release-1.4

$ git config --global user.email ${GIT_EMAIL}
The command "git config --global user.email ${GIT_EMAIL}" exited with 1.
...
The command "git merge -s recursive -X theirs homebase/release-1.4 -m "Sync from homebase"" exited with 0.
$ git push
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:
  git config --global push.default matching
To squelch this message and adopt the new behavior now, use:
  git config --global push.default simple
See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)
remote: Anonymous access to kubernetes-v1-4/kubernetes-v1-4.github.io.git denied.
fatal: Authentication failed for<EMAIL_ADDRESS>The command "git push" exited with 128.

cc @pwittrock

log: https://travis-ci.org/kubernetes/kubernetes.github.io/builds/156069148

I believe I've fixed it. Travis will now pass in newer PRs merged into release-1.4, see https://github.com/kubernetes/kubernetes.github.io/pull/1128
But old PRs are still using old travis configs...

@jaredbhatti maybe know the answer?

It seems that it passed just because I commited #1128 with GitHub :/

@jaredbhatti it seems that people submitting PRs to release-1.4 need to send their git credential to travis env.global.secure to make travis pass?

In the failed travis build log, the following steps are missing
environment variables from repository settings
$ export encrypted_b7b6a058a6f4_key=[secure]
$ export encrypted_b7b6a058a6f4_iv=[secure]
Setting environment variables from .travis.yml
$ export GIT_EMAIL=[secure]
$ export GIT_NAME=[secure]
$ export GIT_USERNAME=[secure]
$ export GH_TOKEN=[secure]

I found the root cause https://github.com/travis-ci/travis-ci/issues/1500#issuecomment-26122631:

Secure environment variables are not included in pull request builds for security reasons. If they were, then anyone could submit a pull request and simply print out all the environment variables.

@jaredbhatti @pwittrock can we remove the travis script in release-1.4?

I removed .travis.yml in release-1.4 branch

looks like we are not using this any more


Cannot set both 'pageDescription' and use 'join' in query

Do I associate an object in the query and I can no longer perform pagination?
I got this error:
Bad state: Invalid query. Cannot set both 'pageDescription' and use 'join' in query

Ok,I found the solution.
Just don't use "pageBy"

Faced the same now, so here is a little tip:
use sortBy, fetchLimit and offset instead of pageBy and you will get the same behavior.


fonts

Which program can generate fonts in this format?

I am also looking for that.

But, you can try to use GLCD Font Creator, and migrate youself, its bit tricky but works....

The problem is that ILI9341_Draw_Char implementation supports maximum height of 8 pixels (bits).
I might be wrong on this...


ice pack

Long time no see.
When I took a picture of the ice pack, it looks like the image.
The part of the ice pack is white, but usually the part where the temperature is low should be black, so I wondered why. How can I solve it?

Hello, this is very likely related to the issue #1 : the offset of 1600 applied to the calibration image (see line 164) was chosen arbitrarily and was not tested on a wide range of values. This can cause an overflow as the image is unsigned and the substracted calibration image is not guaranteed to be smaller in than the current frame on all pixels. This is expected to happen on extreme values (cold or hot).
One simple workaround would be to cast the image in int32 instead of uint16 to allow negative values in the image, but this would mean that the image could contain negative values, which is unusual. A "cleaner" workaround would be to fully understand the ranges of the calibration image and the measured image and choose the types of the image and the value of the offset so that the resulting image is guaranteed to fall into the expected type without overflow, but i did not have the time to perform this study at the time.
I hope this will help you solve the issue. If you manage to do so, fell free to submit a pull request to contribute to this project.

I'm sorry I'm not good at English.
I changed code.
return status,np.frombuffer(ret,dtype=np.uint16).reshape... → np.int16
in [def grab(self):]


Fluid as liquid rendering engine

First of all, thank you for your hard work and great projects! I've noticed our NSwag generation can take quite a lot of time and when profiled a lot of time is being spent in generating the C# and TypeScript files (no surprise there).
Have you considered Fluid as template engine as it pretty much seems to be the fastest option.  The render time could be even 10x faster for some data sets.

If we can just switch libraries and all existing templates still work it would be feasible to change...

Thank you for confirmation, I'll try to find the time to create a POC with Fluid as underlying engine for you to review.

One problem I now see is that NJsonSchema supports down to netstandard1.3 and net451, is this something you want to keep going forward? I think Microsoft has stated that < netstandard2.0 is pretty much dead end and the oldest supported full framework is net461.

@RicoSuter please see #1346  . With the caveat of only supporting net4.6.1/netstandard2.0 and above but the performance benefits are very significant. I will continue to see how this integrates with NSwag and how performance reflects there.


Add options to set legend placement

Currently the legend is fixed in where it displays. This feature intends to add a parameter to Clustergrammer called legendOptions which would allow the user to change things like whether it's horizontal or vertical, min-max or max-min, and where the legend is positioned. Other options can be planned as comments on this issue.
(originally suggested by @WenheLI here)

Added some options in these commits: #1 #2 #3, currently you can pass:
legend?: {
  show?: boolean;
  x?: string | number;
  y?: string | number;
  side?: "left" | "right";
  height: string | number;
};

I'd like to add allowing for top-bottom, which would automatically make it go sideways. After that I think this could be called closed.


[Unbranded Client CodeGen]:  Support generating error models instead of reusing the model from core library

Clear and concise description of the problem
For unbranded client generation, today, we still use the models from core library when we see the following code which is not correct.
In the unbranded scenario, we should generate models for each Error decorated by @error .
@error
model ApiError {
  /** A machine readable error code */
  code: string;

  /** A human readable message */
  // https://github.com/microsoft/OpenAPI/blob/main/extensions/x-ms-primary-error-message.md
  @OpenAPI.extension("x-ms-primary-error-message", true)
  message: string;
}

### list of item for each language
- [ ] https://github.com/Azure/autorest.python/issues/2937
- [ ] https://github.com/Azure/autorest.java/issues/2991
- [ ] https://github.com/Azure/autorest.csharp/issues/5183
- [ ] https://github.com/Azure/autorest.typescript/issues/2931

Checklist

[x] Follow our Code of Conduct
[x] Read the docs.
[x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

@lirenhe @lmazuel I'd like to clarify the requirement here, when we talk about supporting error model generation, do we talk about the following 1 or both?

first we need to generate these customized error models and expose to end users
second our client should serlize to that error model if the error code is matching

It should be both, but currently, we don't generate error models so I am not sure the status of (2).
For those issues created for each emitter, I already added the verification of the range of the status code.

@lirenhe Hi!
Can you please provide some information about the "verification of the range of the status code"  and how to use it ?
Another question about generating erros models, and consider I'm new to this spec:
Could somehow an error model for the end users be described in the .tsp spec as a normal model, where after that the actual decaring of @error model would extend it or reuse as outer model ?

Spent some time today to confirm with @bterlson and @johanste
Today we consider errors based on a constant, but if intervals are applied to status code, we should be able to use them. For instance:
model Standard4XXResponse extends ApiError {
  @minValue(400)
  @maxValue(499)
  @statusCode
  statusCode: int32;
}

Means clearly "if in that range, use this model".
I create a Python issue with the Python design, linking it here if that helps:
https://github.com/Azure/autorest.python/issues/2940
This may requires some TCGC help, TBD with @tadelesh

Continued the talk, and ended up with this:
P0: "do no harm" behavior.
A client language can decide to ignore custom error type if it's not idiomatic to the language, and if their core library doesn't expose custom error code to customers.
In that case, the models must not be generated, as they are not used by anything.
P1: Support for custom error model
A client language can decide to parse an error received from the service according an error model defined in the TypeSpec. The right model can be discriminated the following way:

It uses a constant, like @statusCode statusCode: 400;
It uses an interval, like @statusCode @minValue(400) @maxValue(499) statusCode int32;
A model is tagged @error, but no status code constraints are provided. In this case, it counts as a default. Note that errors code are alwaays between 400 and 599.

Example of TypeSpec with those scenarios:
@jsonSchema
@error
model ApiError {
  /** A machine readable error code */
  code: string;

  /** A human readable message */
  message: string;
}

model Standard400Response extends ApiError {
  @statusCode
  statusCode = 400;
}

model Standard400Response extends ApiError {
  @statusCode
  statusCode = 400;
}

model Standard4XXResponse extends ApiError {
  @minValue(401)
  @maxValue(499)
  @statusCode
  statusCode: int32;
}

alias WithStandardErrors<T> = T | Standard400Response | Standard4XXResponse  | ApiError

Translate as:

If error code is 400, deserialize using Standard400Response
If error code is between 401 and 499, deserialize using Standard4XXResponse
For everything else, use ApiError (in practice, 500 to 599)

This would translate to the following Python code (to illustrate):
        if response.status_code not in [200]:
            error = None
            if response.status_code == 400:
                error = self._deserialize.failsafe_deserialize(_models.Standard400Response, pipeline_response)
            elif 401 <= response.status_code < 499:
                error = self._deserialize.failsafe_deserialize(_models.Standard4XXResponse, pipeline_response)
            else:
                error = self._deserialize.failsafe_deserialize(_models.ApiError, pipeline_response)
            raise HttpResponseError(response=response, model=error)

Note:

Union are not ordered in TypeSpec, so we need to pass through the union to check if there is a default error model
Garbage in garbage out. It's not the responsability of client emitter to check if the constant/range described cover all errors, or not overlap

There are a few cases in typespec-todo
@get op get(@path id: TodoItem.id): TodoItem | NotFoundResponse;

https://github.com/bterlson/typespec-todo/blob/9ef84051c675b913f0300bc66bbc876c9150580b/main.tsp#L254
It produces

200 with response body TodoItem as expected
404 without body as expected
all other status code as error but without model

  @delete op delete(
    @path id: TodoItem.id,
  ): WithStandardErrors<NoContentResponse | NotFoundResponse>;

alias WithStandardErrors<T> = T | Standard4XXResponse | Standard5XXResponse;

https://github.com/bterlson/typespec-todo/blob/9ef84051c675b913f0300bc66bbc876c9150580b/main.tsp#L260-L262
It produces

204 without body as expected
404 without body as expected
4xx (but exclude 404) as error with model Standard4XXResponse
5xx as error with model Standard5XXResponse
all other status code (practically, none) as error but without body model

There is also a nuance about Standard4XXResponse
model Standard4XXResponse extends ApiError {
  @minValue(400)
  @maxValue(499)
  @statusCode
  statusCode: int32;
}

On this tsp, there seems no need to have another Standard4XXResponse. But if we slight tweak it by adding a property, it is now needed.


PureScript 0.15-compatible release.

httpure is now compatible with PureScript 0.15 via the changes in #194. I'd love to get httpure updated in the package sets, but that requires a new release of the library (0.15.0, I suppose). Is there anything waiting to be done before a release can be made? cc: @cprussin, @davezuch

@thomashoneyman apologies, v0.15.0 has been tagged

also, can we just comment on how cool it is that the httpure v0.15.0 release is the one that aligns with purescript v0.15?

Lol I noticed that too.


Tackle deprecation warning generated by Gradle 4.x

In Gradle 4.x, the method getClassesDir() in SourceSetOutput has been
deprecated in favor of a new method getClassesDirs().
Use reflection to invoke this method, if it is available, so that
consumers using Gradle 4.x are spared the deprecation warning. Fall back
to the original method for consumers using Gradle 3.x.
Fixes #1686

 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.

@smoothreggae Thanks you very much for the pull request! Merged.


Installing the tooling dependencies is already in Prerequisites.

You can preview this docs PR at http://338.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.

Thanks for that pointer. At http://338.docs-pr.validatedpatterns.io/patterns/multicloud-gitops/mcg-getting-started/ I see the change applied. What are the next steps?

/lgtm

Thanks! :)


Added Solution

Added a solution for the challenge's "Get a Hint" documentation.

[X ] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X ] My pull request targets the master branch of freeCodeCamp.
[X] None of my changes are plagiarized from another source without proper attribution.
[X] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

LGTM @rabowlen and congratulations on your first PR 😄🎉
Thanks for contributing!

It passed the test. So is there a bug in the test?
On Mon, Oct 15, 2018 at 4:40 PM Aditya<EMAIL_ADDRESS>wrote:

@jonathan-grah https://github.com/jonathan-grah That solution doesn't
seem correct, Object.hasOwnProperty() doesnt take more than 1 parameter.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/pull/19367#issuecomment-430021064,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARCmPoz_NYz1Ed1dBvjgW2AnorIsf9Teks5ulQCzgaJpZM4XdJTY
.

@jonathan-grah That solution doesn't seem correct, Object.hasOwnProperty() doesnt take more than 1 parameter.

It passed the test. So is there a bug in the test?

@rabowlen Yep, there are only 3 tests and it's passing as long as you have any of the properties in that method so obj.hasOwnProperty("Alan"); passes as well, no need to check for other properties.
Will open an issue for this bug.

@ezioda004, yeah I should have looked at this in more depth, the tests would need improved.

In the class I set up hello world. not sure if I did it correctly
Mamie


Execute remote shell script in file

I have tried to execute a shell script file. I have all permissions on it and its a simple bash script. None of the above seems to work:
exec '/myfile.sh'
exec 'bash /myfile.sh'
exec 'sh /myfile.sh'

@acsadam0404 can you show the exception/error that you are getting?

I didn't got any exceptions, it just didn't execute. The script was creating a temp file with touch into /tmp  so I would see if it was executed. The main usage would be to execute tomcat's shutdown.sh and startup.sh scripts.

Can you share the script or provide a minimalistic script to reproduce the behavior?
Were the permissions missing from the script?
What was the target system you were testing against?

I have the same issue. I'm executing my script over a Debian server. I'm trying to execute the following command:
exec '/opt/tomcat/bin/shutdown.sh'
I previously executed exec "echo my-root-password | su -" and I know it was successful because of the output message. If I just execute the command to execute the sh file I get a Permission Denied exception. If execute it inside a prefix("sudo") nothing happens. It just gets stuck.
Thank you for any help.


The demo does not appear to work

Im on chrome Version 59.0.3071.115 (Official Build) (64-bit) and cant see anything in the demo for the editor.
i get this error in the console
pen.js:73 Uncaught TypeError: D3NE.NodeBuilder is not a constructor
    at pen.js:73:20

Now it works. The demo has been updated


EV charge port entity - unavailable

After latest update this happened. Am I the only one? IONIQ 5.

What version did you come from and what version are you on?
What region and brand?
Could you post your data sensor attributes?

Any update? @elektrinis

Not sure what happened, but one entity was not showing up for some time.

Most likely API server side.


Cleans up README to make it more compact

Based on Brandon's work

LGTM. @idvoretskyi and @goltermann your feedback was addressed.
I will wait on @aronchick, @apsinha or @idvoretskyi to review and merge.

LGTM.
@calebamiles @philips thank you.


Perhaps tracker should crash/quit/restart when disconnected for a long while?

Hi,
Impossible for me to say what you guys changed server-side, but my tracker registered "sys" for most of the weekend until I was able to have a look. It was some unable to connect message that I thought would be fixed by restarting the tracker, and indeed it connected immediately upon restart. I don't know how likely it is for such server-side changes to happen in the months and years to come, but if they might produce unsupported and unconnectable configurations, it is an idea to have the tracker terminate and/or restart somehow, for "correct state" to propagate.

If the tracker loses its connection to one of the servers it should failover to another server and keep trying until it reconnects.  Did the log files for that period show failover attempts?

I will try to back my reminiscences by log sleuthing, but for all I know the tracker was in some undefined state rather in some rotation.

The most recent installation guides have instructions on how to installing process monitoring to ensure bot zend and the nodetracker are up/restarted when needed.
Closed due to lack of activity.


Use hmac.compare_digest()

Need to import hmac, looks like? And where is force_bytes from?

Whoops, I went a bit too fast there.

Interesting:
from operator import _compare_digest as compare_digest

¯\_(ツ)_/¯


SPZ rendering quality improvement

boost color by SH C0 constant
fix math for sqrt

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15984/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15984/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15984/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15984/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15984/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15984/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15984/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15984/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15984/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15984/merge/testResults/webgpuplaywright/index.html

Visualization tests for WebGL 1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15984/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.


StarCraft 2 don't runs when D9VK is in use.

Hi! Yes, I know that D9VK is still in early development, so for the time being we should not expect too much from it, but I’ll just write in advance about this issue.
Software information
StarCraft 2 (Direct3D9-only game).
System information

OS: Arch Linux
GPU: AMD Radeon HD 7850
Driver: AMDGPU (manually enabled), Mesa-git
Wine version: Wine-tkg-git with latest Wine Staging git
DXVK version: winelib latest git from Wine-tkg-git

Apitrace file(s)

SC2_x64 Trace

Log files:
SC2_x64_d.zip

I haven't it, but Is this really necessary here in this case?

If it wasn't necessary, that section would not exist.
I do not own StarCraft 2, do you want me to pull a copy out my arse?

OK, I will try to do an apitrace later, because just now I, unfortunately have not a free time to do it.

I haven't it, but Is this really necessary here in this case?

If it wasn't necessary, that section would not exist.
I do not own StarCraft 2, do you want me to pull a copy out my arse?
Edit: Apparently the game is free now, but I would still not like to install it

@Joshua-Ashton @Kerrung Hi I made a trace for you guys =)
SC2_x64 Trace

@Joshua-Ashton @Kerrung Hi I made a trace for you guys =)
SC2_x64 Trace

Thank you very much!

Tell me, please, what else is missing or what is needed to solve this issue? Thanks you.

@Kerrung Just a lot of patience. Please don't waste precious time of the people that do the actual work with useless questions.

The game should work after commit 66a1d3ad19e0e4e9d264e985fa6c66907cdcfd0e.
You probably need to delete the state-cache in StarCraft II/Support64, if its still crashing after that commit.

Corrected by 66a1d3ad19e0e4e9d264e985fa6c66907cdcfd0e

The game should work after commit 66a1d3a.
You probably need to delete the state-cache in StarCraft II/Support64, if its still crashing after that commit.

Now, with ab57adc when I start the game, I see a black screen, against the background of which then after a few seconds a stylized mouse pointer from the game appears, but then crash still happens. Yes, I deleted what you told me to delete, but it did not help.
The new logs:
sc2_terminal_output.txt
SC2_x64_d3d9.log
SC2_x64_dxgi.log

The game should work after commit 66a1d3a.
You probably need to delete the state-cache in StarCraft II/Support64, if its still crashing after that commit.

Now, with ab57adc when I start the game, I see a black screen, against the background of which then after a few seconds a stylized mouse pointer from the game appears, but then crash still happens. Yes, I deleted what you told me to delete, but it did not help.

Corrected by 66a1d3a

So, can this bug report be reopened, please?
The new logs:
sc2_terminal_output.txt
SC2_x64_d3d9.log
SC2_x64_dxgi.log

Before I do that, can we do a very quick check:
Do you have the real, non-crap, native d3d9x and d3dcompilers installed? The Wine ones are completely broken.

@Kerrung can you also try wine-4.5 instead of 4.7? Its working fine for me on current d9vk master. I have the following native dlls that Josh suggested installed, but I am not sure if they are really needed.
Winetricks-verbs:
d3dcompiler_43
d3dx9

Before I do that, can we do a very quick check:
Do you have the real, non-crap, native d3d9x and d3dcompilers installed? The Wine ones are completely broken.

No, I haven't, I use a fresh and clean WINEPREFIX because SC2 works fine if I use wined3d or Gallium Nine Standalone instead of D9VK.
But how exactly should I install this?
$ winetricks -q d3dcompiler_43 d3dx9
I'm right?

SC2 works fine if I use wined3d or Gallium Nine Standalone instead of D9VK. I'm not interested in supporting the wine d3d9x and d3dcompiler's garbage and incorrect API usage and shader generation.
I think that command looks correct.

I just tested 66a1d3a deleted the state cache and it ran for me.
I'm using Lutris with a fairly old wine (esync-staging-pba-3.16)
It feels a little stuttery scrolling around the game, but for the most part it seemed to work ok on High settings, i did have esync enabled.  I may try disabling that see if it's any better.  I briefly tried Ultra but there was some visual glitching on the animated background in the menus.

SC2 works fine if I use wined3d or Gallium Nine Standalone instead of D9VK. I'm not interested in supporting the wine d3d9x and d3dcompiler's garbage and incorrect API usage and shader generation.
I think that command looks correct.

Unfortunately, but it too did not help to solve ...
sc2_terminal_output.txt
SC2_x64_d3d9.log
SC2_x64_dxgi.log

But I do not exclude that, perhaps, the reason may be in any new regressions of Wine, so I will also try to compile Wine without D9VK to try again SC2 with Wined3d.

Maybe try non-winelib builds... They have some peculiar rendering issues somehow.

Heres my log files, I'm using a newer LLVM and RADV driver.  Good luck =)
SC2_x64_d3d9.log
SC2_x64_dxgi.log

Heres my log files, I'm using a newer LLVM and RADV driver. Good luck =)
SC2_x64_d3d9.log
SC2_x64_dxgi.log

I do not use Lutris or anything like it. Only Wine, terminal and me. And now I use LLVM 8.0.0 and Mesa 19.0.3.

Can you try a non-winelib build please?

Maybe try non-winelib builds... They have some peculiar rendering issues somehow.

Good, but where can I get it?

Latest builds are available here:
https://git.froggi.es/joshua/d9vk/-/jobs

Latest builds are available here:
https://git.froggi.es/joshua/d9vk/-/jobs

I just tried the latest D9VK from your link, but it still the same...

Runs fine here with d9vk, d3dcompiler_43 and d3dcompiler_47 on wine-staging 4.7 with esync on.

Latest builds are available here:
https://git.froggi.es/joshua/d9vk/-/jobs

I just tried the latest D9VK from your link, but it still the same...

I downgraded my LLVM to 8 and stable mesa, radeon-vulkan, amgdpu drivers and I'm now getting the same crash.  I suggest you upgrade LLVM and drivers to the ones in the mesa-git repo.
Here's what I have installed:
xf86-video-amdgpu-git
vulkan-radeon-git
lib32-vulkan-radeon-git
mesa-git
lib32-mesa-git
llvm-svn
llvm-libs-svn
lib32-llvm-svn
lib32-libs-llvm-svn

Now works fine for me with mesa-git and llvm 8.0.0.
@Joshua-Ashton maybe you want to add to the documentation that Mesa 19.0.3 is not supported?
Or maybe you want to add Mesa 19.0.3 support?
Thank you very much!

Or maybe you want to add Mesa 19.0.3 support?

Yeah no, I don't really have time to go and find the issue with this old version of Mesa and work around it -- not do I care really.

Both 32-bit and 64-bit SC2 appears to work after 66a1d3a, without any winetricks applied. I'm using Lutris' wine 4.6, manual d9vk build and Nvidia 418.56.

Performance in extreme settings is increased from 20-40 fps to 70-130 compared with wined3d9 in the same scenario. Thanks for your great job!

@v21cesc : How is performance for you playing a longer match with many units ? I also have very good perf when games start but it is constantly decreasing (alos the gpu load is decreasing) the more action is ongoing.

The previous test was in the stage 3 of human compaign , a zerg-defending stage. I produced 200 units of marines and medics with a small number of SCVs and totally destroyed the zerg's base. The lowest fps was about 60 during the combat. No extra constant fps decreasing over time was found. Of course, the variety of units in this stage is too simple though. I'll do a further test later in the customize game mode with all kinds of units produced.

@pingubot
e3 1230 v2
16gb of ddr3 1600
gtx1660ti with 418.56 driver
512gb 860evo ssd
distro: Fedora 30, DE: gnome 3.32

@pingubot
In a customized game,  FPS can drop to 30 when a 200-vs-200 battle and will return to normal after eliminating a large number of units.
I also played another game in the same map under win10. The FPS drop to 30 can be reproduced by the same condition. So I think SC2 is heavily cpu-bound and d9vk performs quite well.


Winston console transport in raw mode omits the log message

Not sure if I'm doing something wrong, but when I try to enable raw mode on console transport, the log message prints only the log level and meta, but not the actual message.
var winston = require('winston');
var log = new winston.Logger({ transports : [ new winston.transports.Console({level:'debug'}) ] });
log.debug('foo');  // prints debug: foo
var log = new winston.Logger({ transports : [ new winston.transports.Console({level:'debug',raw:true}) ] });
log.debug('foo');  // prints {"level":"debug"}

It appears the problem seems to be the calling of function stripColors() on string which is extended by colors module.  But in config.js it requires colors/safe which does not extend string prototypes.  In the mean times I can just add require colors module before I require winston to have the extended string prototypes loaded, but do we want to change config.js to require colors instead of colors/safe?

Yes. This is a bug in our change of colors

Development<EMAIL_ADDRESS>has ceased. Please consider upgrading to<EMAIL_ADDRESS>If you feel strongly about this bug please open a PR against the 2.x branch.
In<EMAIL_ADDRESS>you can control colorization using built-in or custom formats. Please consider upgrading.
Thank you for using winston!


Error 404 with status report # 519

agentUserId: '5f5117a65ce867241bca0fcf' onSync and reportState
(node:26448) UnhandledPromiseRejectionWarning: {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
}

Have you confirmed that the device IDs are correctly stored in HomeGraph before running reportState?

Would HomeGraph be the "smart-home-dashboard-0.1.1" repository that I
should install on my server? if so, i installed the command that existed in
the README, it gives a fatal error, so I try with npm start and the
successful service, however, when executing any fatal browser error.
10% building modules 0/1 modules 1 active
...-dashboard/src/main/ngapp/src/main 10% building modules 1/2 modules 1
active ...board/src/main/ngapp/src/polyfills 10% building modules 2/3
modules 1 active ...shboard/src/main/ngapp/src/styles.Date:
2020-10-22T20:56:18.333Z
Hash: 20d2a764ec738bc8abf6
Time: 45359ms
chunk {0} polyfills.b8bb642eba73d16a2fc5.bundle.js (polyfills) 63.5 kB
[initial] [rendered]
chunk {1} main.fc6b0ed3210fa61fbbfa.bundle.js (main) 442 kB [initial]
[rendered]
chunk {2} styles.b7ae761de9f444e08063.bundle.css (styles) 46.8 kB [initial]
[rendered]
chunk {3} inline.318b50c57b4eba3d437b.bundle.js (inline) 796 bytes [entry]
[rendered]
https://github.com/actions-on-google/smart-home-dashboard/releases
https://developers.google.com/assistant/smarthome/develop/report-state#deploy-report-state-dashboard
Em qui., 22 de out. de 2020 às 13:54, Nick<EMAIL_ADDRESS>escreveu:

Have you confirmed that the device IDs are correctly stored in HomeGraph
before running reportState?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/actions-on-google/smart-home-nodejs/issues/519#issuecomment-714626335,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFVFJC2J4KLBPXZEHBUKELSMBPVLANCNFSM4S2NMLAQ
.

That is a software package that can use the Home Graph APIs, but you should verify that the report state uses the same device IDs that are in your SYNC response.

I also get this error. When I change the status of a device in the Google Home app, QUERY and EXECUTE work fine, but reporting the state back fails (even if the device IDs match). I set up a device using the smart-home-frontend package.

"intent": "action.devices.QUERY" -> "devices": { "1mqv": { "on": true, "online": true, "status": "SUCCESS" } }
"intent": "action.devices.EXECUTE" -> "devices": [ { "id": "1mqv" } ] -> OK
Reporting state payload for 1mqv { online: true, on: false } ->  "error": { "code": 404, "message": "Requested entity was not found.", "status": "NOT_FOUND" }

That is a software package that can use the Home Graph APIs, but you should verify that the report state uses the same device IDs that are in your SYNC response.

I solved the problem, I had to raise an application on the smart-home-dashboard part, only then I got access to https://smarthome-test-suite.appspot.com/

Eu também recebo esse erro. Quando eu altero o status de um dispositivo no app Google Home, QUERY e EXECUTE funcionam bem, mas o relato do estado falha (mesmo se os IDs do dispositivo corresponderem). Eu configurei um dispositivo usando o pacote smart-home-frontend.

"intent": "action.devices. QUERY " -> "devices": {" 1mqv ": {"on": true, "online": true, "status": " SUCCESS "}}
"intent": "action.devices. EXECUTE " -> "devices": [{"id": " 1mqv "}] -> OK
Relatório de carga útil de estado para 1mqv {online: true, on: false} -> " error ": {"code": 404, "message": "Requested entity was not found.", "Status": "NOT_FOUND"}

here you have to use a timout if your application is in node js
var timer = 20000
    setTimeout(() => {
        console.log('reportState' + timer);
        app.reportState(response_state);
    }, timer);


Uncaught TypeError: r.define Component is not a function

added in my view: Project.vue
import SvgSprite from "vue-svg-sprite";
components: { SvgSprite },
and in the markup:
<SvgSprite symbol="autorizatie-de-constructie" size="24" />
but getting the following error:
Uncaught TypeError: r.define Component is not a function
also tried to declare it globally, but still the same.
any ideas?

Hi @bogdanfer,
Thanks for using vue-svg-sprite.
Some minimal reproducible example would be appreciated!

Hi, this happens if you try to use the Vue 3 plugin with Vue 2. @bogdanfer will need to install version 1.4.3 for Vue 2 support.


Allow DefaultServiceBusNamespaceProcessorFactory  to use the shared serviceBusClientBuilder

Describe the bug
Today when spring boot/ spring cloud auto configuration, sub & producer factories are able to reuse the preconfigured serviceBuSClientBuilder and mark shareServiceBusClientBuilder  to true like here:
https://github.com/Azure/azure-sdk-for-java/blob/2b020724483dbb745531c113d78c4d900fcb52e4/sdk/spring/spring-cloud-azure-service/src/main/java/com/azure/spring/cloud/service/implementation/servicebus/factory/AbstractServiceBusSubClientBuilderFactory.java#L55
In the other hand the DefaultServiceBusNamespaceProcessorFactory  creates `` without passing any serviceBusClientBuilder instance, which result on creating a new instance that lacks any type of configurations that was done for the sub & producers. It will lack any configurations like proxy, custom-endpoint-address customization (reference issue: https://github.com/Azure/azure-sdk-for-java/issues/37930#issue-2026925790)
https://github.com/Azure/azure-sdk-for-java/blob/2b020724483dbb745531c113d78c4d900fcb52e4/sdk/spring/spring-messaging-azure-servicebus/src/main/java/com/azure/spring/messaging/servicebus/core/DefaultServiceBusNamespaceProcessorFactory.java#L189C40-L189C40
This line will call ServiceBusProcessorClientBuilderFactory without serviceBuSClientBuilder , which will result on calling another constructor passing null for serviceBuSClientBuilder  and result on a new instance lacking any type of configurations.
Exception or Stack Trace
Lack of configurations will result on an exception when creating the processor connection despite the sub & producer connections being created successfully.
[INFO ] 2023-12-05 11:17:40,371 ReactorConnection [reactor-executor-1] - {"az.sdk.message":"onConnectionShutdown. Shutting down.","connectionId":"MF_3cc3ca_1701803852833","isTransient":false,"isInitiatedByClient":false,"shutdownMessage":"connectionId[MF_3cc3ca_1701803852833] Reactor selectable is disposed.","namespace":"XXXXXXXXX.net"}

[ERROR] 2023-12-05 11:17:40,398 Operators [reactor-executor-1] - Operator called default onErrorDropped

reactor.core.Exceptions$ErrorCallbackNotImplemented: com.azure.core.amqp.exception.AmqpException: Connection refused: no further information, errorContext[NAMESPACE: XXXXXXXXX.net. ERROR CONTEXT: N/A]

Caused by: com.azure.core.amqp.exception.AmqpException: Connection refused: no further information, errorContext[NAMESPACE: XXXXXXXXX.net. ERROR CONTEXT: N/A]

            at com.azure.core.amqp.implementation.ExceptionUtil.toException(ExceptionUtil.java:85) ~[azure-core-amqp-2.8.4.jar:2.8.4]

            at com.azure.core.amqp.implementation.handler.ConnectionHandler.notifyErrorContext(ConnectionHandler.java:351) ~[azure-core-amqp-2.8.4.jar:2.8.4]

            at com.azure.core.amqp.implementation.handler.ConnectionHandler.onTransportError(ConnectionHandler.java:253) ~[azure-core-amqp-2.8.4.jar:2.8.4]

            at org.apache.qpid.proton.engine.BaseHandler.handle(BaseHandler.java:191) ~[proton-j-0.33.8.jar:?]

            at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:108) ~[proton-j-0.33.8.jar:?]

            at org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324) ~[proton-j-0.33.8.jar:?]

            at org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:291) ~[proton-j-0.33.8.jar:?]

            at com.azure.core.amqp.implementation.ReactorExecutor.run(ReactorExecutor.java:91) ~[azure-core-amqp-2.8.4.jar:2.8.4]

            at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68) ~[reactor-core-3.4.27.jar:3.4.27]

            at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28) ~[reactor-core-3.4.27.jar:3.4.27]

            at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]

            at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]

            at java.lang.Thread.run(Thread.java:833) ~[?:?]

[INFO ] 2023-12-05 11:17:40,411 ServiceBusConnectionProcessor [reactor-executor-1] - {"az.sdk.message":"Transient error occurred. Retrying.","exception":"Connection refused: no further information, errorContext[NAMESPACE: XXXXXXXXX.net. ERROR CONTEXT: N/A]","entityPath":"N/A","tryCount":0,"interval_ms":4511}

[INFO ] 2023-12-05 11:17:40,413 ReactorConnection [reactor-executor-1] - {"az.sdk.message":"onConnectionShutdown. Shutting down.","connectionId":"MF_3cc3ca_1701803852833","isTransient":false,"isInitiatedByClient":false,"shutdownMessage":"Finished processing pending tasks.","namespace":"XXXXXXXXX.net"}

[INFO ] 2023-12-05 11:17:43,068 ServiceBusReceiverAsyncClient [boundedElastic-1] - Removing receiver links.

To Reproduce
Steps provided above. This is for spring cloud stream auto aonfigurations.
Code Snippet
Added above
Expected behavior
Proccessor factory need to be able to use the preconfigured serviceBuSClientBuilder  similar to the sub & producer factories.
Setup (please complete the following information):

OS: Windows
IDE: IntelliJ
Library/Libraries: com.azure:azure-core:1.38.0
Java version: 17
App Server/Environment: Azure Function,
Frameworks:  Spring Boot & Spring Cloud Stream

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ X] Bug Description Added
[X ] Repro Steps Added
[X ] Setup information Added

Here you go: https://github.com/mohyeid/azure-sdk-processor-issue
Please, note tenantId, clientId, secret, proxy, etc.. are fake and for sample code only. You can debug the issue by putting these next breakpoints and noticing the differences:
AbstractServiceBusSubClientBuilderFactory:38
First run for sender & second run for reciever it uses the shared client
Third run for processor, it creates a new instance. Breakpoints at:
- DefaultServiceBusNamespaceProcessorFactory:125 Note it will pass null to ServiceBusProcessorClientBuilderFactory constructor line 24 which will result on creating a new client.
- AbstractServiceBusSubClientBuilderFactory:41  Note it's not using shared
Other helpful breakpoints:
ReactorHandlerProvider:57
- First & second runs for sender and receiver have valid isCustomEndpointConfigured as true. Remember it's set on my customizer in the code example  ApplicationConfiguration:39
- Third run for the processor isCustomEndpointConfigured will be false since it did not use the shared client.
Hope this helps, let me know if I can provide any extra details.

Now the DefaultServiceBusNamespaceProcessorFactory can support to custom the ServiceBusClientBuilder and sub builders through methods addXXXCustomizer,