Business Central Sandbox Publish problem

When I publish an extension from Visual Studio Code to Sandbox enviroment I get no error but the extensions does not publish
Debugger Console does not shoot any error:

VS Version: 1.39.2
AL Language: 4.0
Business Central: 14.0

This GitHub repository is dedicated to handling issues and feedback for the latest Developer Preview releases of the AL development tools for Dynamics 365 Business Central.
If you can reproduce the problem on the latest Business Central Developer preview version we will be happy to look further into it. Otherwise please contact the regular support channel.
You can open Support Request to CSS through PartnerSource portal or contact your Service Account Manager (SAM) in the local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also step by step direct you how to open a support request or how to get credentials if this is the first time for you / your company.
For more details please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions#i-found-an-issue-on-nav-2018-what-do-i-do

In the VS Code, View > Command Palette >  type : Clear Credentials.
Restart VS Code and then try publishing again :)

Thank you ashikivor, I have cleared credentials several times.

Then, you should open reset your Sandbox environment and try publishing the package again.
Go to Production > Search 'Sandbox' > Click on the reset button.

Thank you very much.
But If I Reset Sandbox enviroment, will I lose the data introduced in that enviroment? Actually we have introduced many data such as configurations and data for trainings and we can not lose it.

I do not think there is any other option.


Adding nanostores

I tried to fork your project and add nanostores in order to be able to share states between microfrontends, it doesnt works, when I update my state from my X microfronted and try to retrieve the state from another Y microfrontend (usign useEffect to see realtime results) im not able to get the updated value.
Do you have any suggestion for it? The only way that works is to use the PostMessage method

Strange, are using nanostores from esm.sh? The apps have to share the same instance of nanostores, so you have to add it to the importmap.
I've tried nano-events and it worked just fine, again, imported from esm.sh. Localstorage should also work.


Add brightness adjustment

Require a slider (UI).

Would you be open to pull requests with plugins that implemented additional behaviors like this?


Documentation domain lapsed

The "Sending E-Mail" help page links to gopostal.io which appears to have lapsed or never existed.
Is it possible to restore it or put the documentation into another github repository?

I actually don't think that page ever existed and we should remove the link to it from the UI itself.

Sorry - I lied - the documentation for that link is here: https://github.com/atech/postal/wiki/Using-the-API

Thanks!


linux can't make

Desktop (please complete the following information):

OS: [Deepin OS V20]
AppCUI Version [branch master]

Describe the bug

Hello, @Yurri-huang,
Please attach the log for AppCUI/build/vcpkg-bootstrap.log.
Usual the problem is self-explanatory in the log, for example:
root@e949772cd302:/home/repo/AppCUI# cat /home/repo/AppCUI/build/vcpkg-bootstrap.log
Could not find curl. Please install it (and other dependencies) with:
On Debian and Ubuntu derivatives:
sudo apt-get install curl zip unzip tar
On recent Red Hat and Fedora derivatives:
sudo dnf install curl zip unzip tar
On older Red Hat and Fedora derivatives:
sudo yum install curl zip unzip tar
On SUSE Linux and derivatives:
sudo zypper install curl zip unzip tar
On Arch Linux and derivatives:
sudo pacman -S curl zip unzip tar cmake ninja
On Alpine:
apk add build-base cmake ninja zip unzip curl git
(and export VCPKG_FORCE_SYSTEM_BINARIES=1)


Update readme.markdown

Mention flip-tape in the section "other". 🦊

So is this the (deprecated in every other language and testing framework) "should" approach, where it polyfills matchers onto every value?
Does it work with Object.create(null) or with objects from other realms? What if I'm doing for..in over an object, won't the presence of the matchers suddenly break my code?

It only attaches tapes methods to the String prototype (see lines marked with // eslint-disable-line https://github.com/pguth/flip-tape/blob/master/index.js).
So in the case of a for...in loop over a String object your code would probably break. However I don't think for...in-ing over a String is a likely case. Nonetheless I should point that out in the readme.

aha, i misunderstood. so you're just doing description.matcher(…) instead of matcher(…, description).
That's definitely much less problematic, so I no longer have a concern about including it in the readme. (I'm still confused why you wouldn't want matcher(description, …) to avoid any issues with screwing with String.prototype)


trimToLimit does not work with utf-8 encoding

Hi,
trimToLimit function (in file p_guerrilla_db_redis.go) does not work with utf-8 encoding. This function is also used in the file p_sql.go.
It should be like this to correct operation.
func trimToLimit(str string, limit int) string {
	ret := strings.TrimSpace(str)
	if len([]rune(str)) > limit {
		ret = string([]rune(str)[:limit])
	}
	return ret
}

Thanks.

Thanks!


Enable User ID in environment and advanced model configuration

the general concept is that if a USER_ID is set then it will be applied to both OpenAI and Helicone

Thanks for submitting. I'll be ooo for the week (yearly travels), will merge after.

See #180


How to pass environment variables

Hi,
Is there any ability to define load tests once and then run those against various hosts? We have a number of environments that need to be load tested, and there does not seem to be any ability to inject variables into URL e.g.

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

ID: 4c5348c1-4b41-0644-ce16-91c6969d8ffb
Version Independent ID: 51530f61-b72e-c09a-57e7-df5e0501fbf4
Content: Get Application Insights performance data with load tests
Content Source: docs/test/load-test/get-performance-data-for-load-tests.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

Thank you for your feedback. I have passed this on to the product team for advice.

@stevozilik - context parameters are the glue to passing information and changing values for those parameters as desired.

Parameterize URLs in your webtest
Add a context parameter in your load test runsettings (right click Active runsettings in load test editor -> add context parameter)

If you are running load tests in the CI/CD pipeline where the URL of the app may change from environment to environment, we recently enhanced the cloud load test task that allows you to override the context parameter value from the task UI and use any environment variables of the pipeline to pass in the desired information.
@alexhomer1 - Can you add this to the documentation, please?

Thank you for your feedback. I will update the topic to include your recommendations.

@PBoraMSFT - thank you, I agree that works, I've discovered all of that in last few days. I assume you mean having the load tests defined in a solution and checked in source control.
Are there any plans to make the VSTS UI richer to be able to define these via the web interface (cut out checking in code/Visual Studio)?

@stevozlilik - no, enhancing the VSTS UI capabilities is not on the backlog for the foreseeable future.


Remove PDFViewerApplication.setScale and further simplify the scalechange event handler (issue 6158)

This finally fixes #6158.

/botio-linux preview

Thank you for the patch!


[Helix] Kestrel H2SpecTests.RunIndividualTestCase fail on everything but OSX/Windows

Tracking for skipped test:
These fail on all non OSX/Windows helix queues
Failed   RunIndividualTestCase
Error Message:
 System.ComponentModel.Win32Exception : Permission denied
Stack Trace:
   at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean throwOnNoExec)
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Interop.FunctionalTests.H2SpecCommands.EnumerateTestCases() in /_/src/Servers/Kestrel/test/Interop.FunctionalTests/H2SpecCommands.cs:line 50
   at Interop.FunctionalTests.H2SpecTests.get_H2SpecTestCases() in /_/src/Servers/Kestrel/test/Interop.FunctionalTests/H2SpecTests.cs:line 62
Results File: /home/helixbot/dotnetbuild/work/32dcc8b8-82df-4dd5-a871-9c071b0cfad6/Work/a0bfc0a8-4bfc-4323-839e-b6a701682461/Exec/TestResults/_a000P73_2019-02-06_06_35_35.trx

For some reason, this is now being done in test discovery and the skip condition isn't being evaluatated:
https://mc.dot.net/#/user/aspnetcore/pr~2Faspnet~2Faspnetcore/ci/20190409.32/workItem/Interop.FunctionalTests-netcoreapp3.0/wilogs
dotnet-install: Installation finished successfully.
Exception thrown during test discovery.
Microsoft (R) Test Execution Command Line Tool Version 16.0.1
Copyright (c) Microsoft Corporation.  All rights reserved.

The following Tests are available:
[xUnit.net 00:00:00.81] Interop.FunctionalTests: Exception thrown during theory discovery on 'Interop.FunctionalTests.H2SpecTests.RunIndividualTestCase'; falling back to single test case.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ComponentModel.Win32Exception: Permission denied
   at System.Diagnostics.Process.ForkAndExecProcess(String filename, String[] argv, String[] envp, String cwd, Boolean redirectStdin, Boolean redirectStdout, Boolean redirectStderr, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Interop.FunctionalTests.H2SpecCommands.EnumerateTestCases() in /_/src/Servers/Kestrel/test/Interop.FunctionalTests/H2SpecCommands.cs:line 42
   at Interop.FunctionalTests.H2SpecTests.get_H2SpecTestCases() in /_/src/Servers/Kestrel/test/Interop.FunctionalTests/H2SpecTests.cs:line 63
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, BindingFlags invokeAttr, Binder binder, Object[] index, CultureInfo culture)
   at System.Reflection.RuntimePropertyInfo.GetValue(Object obj, Object[] index)
   at Xunit.MemberDataAttributeBase.GetData(MethodInfo testMethod) in C:\Dev\xunit\xunit\src\xunit.core\MemberDataAttributeBase.cs:line 66
   at Xunit.Sdk.DataDiscoverer.GetData(IAttributeInfo dataAttribute, IMethodInfo testMethod) in C:\Dev\xunit\xunit\src\xunit.core\Sdk\DataDiscoverer.cs:line 25
   at Xunit.Sdk.TheoryDiscoverer.Discover(ITestFrameworkDiscoveryOptions discoveryOptions, ITestMethod testMethod, IAttributeInfo theoryAttribute) in C:\Dev\xunit\xunit\src\xunit.execution\Sdk\Frameworks\TheoryDiscoverer.cs:line 212
    Http2
    RunIndividualTestCase
+ _commandExitCode=1
+ exit 1

Is it happening reliably? Could there be a chmod problem? Maybe h2spec isn't properly marked as executable?

Closing in lieu of https://github.com/aspnet/AspNetCore-Internal/issues/2225


FPET-46 caselist improvements

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/FPET-46
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Closing this PR as looks to be failing in pipeline and behaving abruptly

Closing this PR as looking to be behaving abruptly


Test bulk create of objects

Codecov Report

Merging #23 into master will increase coverage by 0.97%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage   44.89%   45.87%   +0.97%
==========================================
  Files          10       10
  Lines         715      715
==========================================
+ Hits          321      328       +7
+ Misses        394      387       -7

Impacted Files
Coverage Δ

django_hana/compiler.py
78.78% <100%> (+6.06%)
:white_check_mark:

django_hana/operations.py
49.11% <ø> (+0.59%)
:white_check_mark:

django_hana/base.py
65.76% <ø> (+1.08%)
:white_check_mark:

Continue to review full report at Codecov.

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

Codecov Report

Merging #23 into master will increase coverage by 0.97%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage   44.89%   45.87%   +0.97%
==========================================
  Files          10       10
  Lines         715      715
==========================================
+ Hits          321      328       +7
+ Misses        394      387       -7

Impacted Files
Coverage Δ

django_hana/compiler.py
78.78% <100%> (+6.06%)
:white_check_mark:

django_hana/operations.py
49.11% <ø> (+0.59%)
:white_check_mark:

django_hana/base.py
65.76% <ø> (+1.08%)
:white_check_mark:

Continue to review full report at Codecov.

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


Allow benchmark specific flags

./pkb.py --config_override="benchmarks=[{iperf: {flags: {iperf_sending_thread_count: 2}}}, {iperf: {flags: {iperf_sending_thread_count: 4}}}]" --parallelism=2
.....
.....
.....
-------------------------PerfKitBenchmarker Results Summary-------------------------
IPERF:
  receiving_machine_type="n1-standard-1" receiving_zone="us-central1-a" runtime_in_seconds="60" sending_machine_type="n1-standard-1" sending_zone="us-central1-a"
  Throughput                         1919.000000 Mbits/sec                      (ip_type="external" sending_thread_count="4")
  Throughput                         1993.000000 Mbits/sec                      (ip_type="internal" sending_thread_count="4")
  Throughput                         1955.000000 Mbits/sec                      (ip_type="external" sending_thread_count="4")
  Throughput                         1992.000000 Mbits/sec                      (ip_type="internal" sending_thread_count="4")
  Throughput                         1909.000000 Mbits/sec                      (ip_type="external" sending_thread_count="2")
  Throughput                         1997.000000 Mbits/sec                      (ip_type="internal" sending_thread_count="2")
  Throughput                         1758.000000 Mbits/sec                      (ip_type="external" sending_thread_count="2")
  Throughput                         1997.000000 Mbits/sec                      (ip_type="internal" sending_thread_count="2")
  End to End Runtime                  496.858173 seconds
  End to End Runtime                  518.701941 seconds

-------------------------

@cmccoy Would you mind taking a look?

This could use a README update, and a note in #525.

Still need to move the FlagValuesProxy class (I'll do it on Monday), otherwise fixed everything - thanks for the review - looks much cleaner now

PTAL

I tried something different (replaced flags.FLAGS with the flag proxy) - can you PTAL?

I like the latest. A few documentation / testing nits, otherwise LGTM.

PTAL

LGTM. Two more nits, sorry. Feel free to merge after that.


[KARAF-5614] Add HTTP ProxyService

@gnodet I did a refactoring to use a generic ProxyServlet instead of the Jetty one. Can you take a look please ? Thanks !

Looks good to me.

Thanks, waiting Jenkins green light to merge (just in case ;)) and updating the documentation.


float test error

hi, all
i have porting clfft fftw3 on qualcomm paltform,  when i run the Test, float test is failed.
[ RUN      ] accuracy_test_pow2_single.single_point_1D_forward_complex_to_complex
Floating point exception
but example test fft1d/ 2d/ 3d is ok
what's the reason might be?
thanks in advance!

You would have to debug on your own; not familiar with this hardware unfortunately we are unable to help.


Update notification.rb

#168 opening pr as i need the header in one of the apps i support

Can you link the corresponding documentation?

@dankimio hey yes, to be honest i don't think this PR actually modifies the header i am sort of confused as to how to encode that header with whats currently there do you mind helping?
https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns

@ab320012 Headers are a bit different from the payload.

@dankimio yes i am aware wondering how i can get it done or if you are going to do add the header as it will break houston for ios13 which is already out

It looks like Houston currently uses the legacy, binary notification format instead of the HTTP/2 api. Apple so far has not provided any documentation on how to supply this parameter with the legacy notification, or if one is even required. Has someone been able to test that pushes through Houston are actually rejected from an iOS 13 device, or are we just going off of possibly inaccurate documentation?

@dankimio yes, to be honest i don't think this PR actually modifies the header i am sort of confused as to how to encode that header with whats currently there do you mind helping?
https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns

The documentation seems to have changed.


Update and Stage Contracts

Issue to be solved
Contracts that we control need to be updated and staged on various networks
Suggest A Solution
Staging:

[ ] FUSD

[x] Testnet
[ ] Mainnet

[x] LockedTokens

[x] Testnet
[x] Mainnet

[x] StakingCollection

[x] Testnet
[x] Mainnet

[ ] USDC

[ ] Testnet
[ ] Mainnet

[ ] NFTStorefront

[x] Testnet
[ ] Mainnet

[ ] NFTStorefrontV2

[ ] Testnet
[ ] Mainnet

[ ] NFTCatalog

[x] Testnet
[ ] Mainnet

[ ] Hybrid Custody

[ ] Testnet
[ ] Mainnet

[ ] PrivateReceiverForwarder

[x] Testnet
[ ] Mainnet

[ ] TokenForwarding

[x] Testnet
[ ] Mainnet

Previewnet Deployment/Upgrading
Some of these haven't been deployed and some have an old Cadence 1.0 version, so they need to be upgraded.

[x] FUSD
[x] LockedTokens
[x] StakingCollection
[ ] USDC
[ ] NFTStorefront
[ ] NFTStorefrontV2
[ ] NonFungibleToken

Updated, but doesn't include the ownedNFTs field yet
Will need another upgrade or deployment to a new address

[x] MetadataViews
[x] FungibleToken
[ ] NFTCatalog
[ ] Hybrid Custody

What are you currently working on that this is blocking?
No response

Missing keys for previewnet NFTStorefront v1 and v2, nft catalog, and usdc
Missing keys for testnet NFTStorefrontV2 and USDC.
Everything else is updated as of now


functionalComponentEmits not be used

new VueWrapper(app, vm, setProps, functionalComponentEmits) functionalComponentEmits is aways {} and not change,
so I try to delete functionalComponentEmits, then run the test case, it is successful, so I want to ask the purpose of functionalComponentEmits.
whether we lose the test case for functionalComponentEmits?

It looks like since this https://github.com/vuejs/vue-test-utils-next/commit/84d41efaf06313424ddcbacb480e5540cb425cd5 from @lmiller1990 it might not be necessary indeed.
@gzponline You can open a pull request to remove it if you want and we'll review it :)

Good catch... we don't need this anymore, since we catch emits by wrapping functional components and intercepting the emits (see here https://github.com/vuejs/vue-test-utils-next/blob/951c5018698363d91e37fcadcef1f59d994c604b/src/mount.ts#L251)
Yep, a PR removing this would be great. Thanks!

@cexbrayat  OK I will pull a request 😄 I tried to understand the purpose, but discover it is not used

It's purpose is to be deleted 👍


[BUG] Issue with OpenSearch Snapshot Deletion When Multiple Snapshots Exist in AWS S3 Repository

Describe the bug
We are running OpenSearch of version 2.15.0 and backing up OpenSearch data to AWS S3.

When multiple snapshots exist in snapshot repo and delete one of the snapshot by API, it will return 400 with error groupSize must be greater than 0 but was -1, but the snapshot is successfully deleted.
When only one snapshot exist in snapshot repo, the snapshot deletion will succeed and return 200.

Related component
Storage:Snapshots
To Reproduce

Register snapshot repository
Take multiple snapshots
Delete one of the snapshot by API DELETE _snapshot/{snapshot-repository}/{snapshot}

Expected behavior
Although multiple snapshots exist in snapshot repository, we could delete the snapshot successfully.
Additional Details
Error:
{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "groupSize must be greater than 0 but was -1"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "groupSize must be greater than 0 but was -1"
  },
  "status": 400
}

[Catch All Triage - 1, 2, 3, 4, 5]


Add Open Stack Authentication for Swift Backend

Summary
As "developer"
I want "to configure open stack authentication"
So that "I can use open stack swift backends"
Context
Currently the swift backend only accepts a path and a container and authentication is handled by adding global variables.
It would be interesting to provide another field like "openStackAuthSecret" which points to a kubernetes secret, containing all the required env variables defined by open stack:
Example:

OS_AUTH_URL
OS_IDENTITY_API_VERSION
OS_USER_DOMAIN_NAME
OS_PROJECT_DOMAIN_NAME
OS_TENANT_ID
OS_TENANT_NAME
OS_USERNAME
OS_PASSWORD
OS_REGION_NAME

Out of Scope
No response
Further links

https://docs.openstack.org/zh_CN/user-guide/common/cli-set-environment-variables-using-openstack-rc.html

Acceptance Criteria
No response
Implementation Ideas
Example secret:
apiVersion: v1
kind: Secret
metadata:
  name: "open-stack-secret"
stringData:
  OS_AUTH_URL: ""
  OS_IDENTITY_API_VERSION: "3"
  OS_USER_DOMAIN_NAME: "Default"
  OS_PROJECT_DOMAIN_NAME: "Default"
  OS_TENANT_ID: ""
  OS_TENANT_NAME: ""
  OS_USERNAME: ""
  OS_PASSWORD: ""
  OS_REGION_NAME: ""

Example backend config with backend swift
apiVersion: k8up.io/v1
kind: Backup
metadata:
  name: k8up-test
spec:
  tags:
    - prod
    - archive
    - important
  failedJobsHistoryLimit: 4
  successfulJobsHistoryLimit: 0
  backend:
    repoPasswordSecretRef:
      name: "backup-encryption"
      key: "password"
    swift:
      path: /archive1
      container: home-cloud-backups
      openStackAuthSecret: open-stack-secret

Hello, I have opened a PR #657 that allows for Open Stack authentication, or any authentication method that uses environment variables in fact.


Support zooming images that are rendered via other components

Is your feature request related to a problem?
When using internal components that use tags like <Image> on MDX files, zoom does not work.
# src/components/themedImage.astro
---
import { Image } from 'astro:assets';

interface Sources {
  light: string;
  dark: string;
}
interface Props {
  alt: string;
  sources: Sources;
}

const inferSize = true;
const { alt, sources } = Astro.props;
---

<div>
  <Image
    inferSize={inferSize}
    alt={`${alt}-light`}
    class={"dark:sl-hidden"}
    src={sources.light}
  />
  <Image
    inferSize={inferSize}
    alt={`${alt}-dark`}
    class={"light:sl-hidden"}
    src={sources.dark}
  />
</div>

import ThemedImage from<EMAIL_ADDRESS>
<ThemedImage
  alt="test"
  sources={{
    light: "light-image",
    dark: "dark-image",
  }}
/>

Resulting images using this approach cannot be zoomed.
Describe the solution you'd like
Make it possible to zoom rendered images even if they're not expressed via <Image> or <Picture> directly on the mdx file.
Describe alternatives you've considered
Maybe allow specifying which components should also be overriden
Additional Context
No response

Thanks for the feedback.
This is a similar issue as #16 where this limitation was also discussed recently. The issue contains a workaround that should work for you as well and as I mentioned in the issue, I'm starting to think about potentially shipping a component providing that workaround out of the box depending on the feedback I get regarding this specific use-case.

@HiDeoo,
I can confirm that zoom works as intended when using the <starlight-image-zoom-zoomable> tag inside the component. It is also pretty straightforward:
---
import { Image } from 'astro:assets';

interface Sources {
  light: string;
  dark: string;
}
interface Props {
  alt: string;
  sources: Sources;
}

const inferSize = true;
const { alt, sources } = Astro.props;
---
<starlight-image-zoom-zoomable>
  <Image
    inferSize={inferSize}
    alt={`${alt}-light`}
    class={"dark:sl-hidden"}
    src={sources.light}
  />
</starlight-image-zoom-zoomable>
<starlight-image-zoom-zoomable>
  <Image
  inferSize={inferSize}
  alt={`${alt}-dark`}
  class={"light:sl-hidden"}
  src={sources.dark}
  />
</starlight-image-zoom-zoomable>

I would advise adding documentation about this tag.
Thank you so much.


Script editor: Fix crash when root script is null

Bug introduced in #40746.

Cherry-picked for 3.2.3.


Unable to bind Ctrl+Shift+U

VSCode Version: 1.38.1
OS Version: Ubuntu 18.04.3 LTS

Steps to Reproduce:

Open the Keyboard Shortcuts editor.
Select a command.
Try to bind Ctrl+Shift+U.

Pressing Ctrl+Shift displays Ctrl+Shift+ in the edit box, pressing U clears the box.
Even if I edit the keybindings file by hand, the shortcut still doesn't work.
This is the default binding in real Visual Studio for converting the selected text to uppercase.
Does this issue occur when all extensions are disabled?: Yes

And once again it seems this is a shitty linux issue.


Same flexibility in synth of ($ f x) as of (@ p r).

Currently it will not work unless both sides are of the form ($ f x) at the same time.

@favonia Ah, good point.

Let me think about this a bit; it would help if you could give an example that was problematic.
In the case of path application, IIRC this was necessary because there is a non-computational equality p @ 0 = foo for any path; but what is the analogous thing for functions?

I don't have a concrete example yet, but I suppose we might want to prove ($ f x y) and ($ g y) are equal?

@favonia In this case, it would suffice to show that ($ f x) = g; I guess under the current state of affairs, it would be necessary to prove this before hand.
For better or for worse, the idea behind the synth stuff is that it represents a phase where only structural equality is considered. Sometimes structural equality is not the right choice...

@jonsterling The point is that Fun.EqApp would call Synth on ($ f x) and g, and then that would result into a Match exception without further explanation. Even manual refine would not work. This probably means we have to rewrite one side first, and I feel it is a little bit too demanding.

@favonia Hmm, that's a reasonable point. My thinking before was that synth should figure out sufficient conditions for two neutral terms to be equal, but maybe instead it should not try to do equality, and should only try to figure out membership.


ImportError: cannot import name 'build_import_method_request'

Package Name: azure-mgmt-sql
Package Version: 4.0.0b17
Operating System: Linux
Python Version:  3.12

Describe the bug
Version 4.0.0b17 includes an import for a function that doesn't exist.
To Reproduce
Steps to reproduce the behavior:

pip install azure-mgmt-sql==4.0.0b17
python -c 'from azure.mgmt.sql.aio import operations'

❯ python -c 'from azure.mgmt.sql.aio import operations'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/jcline/.virtualenvs/az-sql/lib64/python3.12/site-packages/azure/mgmt/sql/aio/__init__.py", line 9, in <module>
    from ._sql_management_client import SqlManagementClient
  File "/home/jcline/.virtualenvs/az-sql/lib64/python3.12/site-packages/azure/mgmt/sql/aio/_sql_management_client.py", line 20, in <module>
    from .operations import (
  File "/home/jcline/.virtualenvs/az-sql/lib64/python3.12/site-packages/azure/mgmt/sql/aio/operations/__init__.py", line 12, in <module>
    from ._databases_operations import DatabasesOperations
  File "/home/jcline/.virtualenvs/az-sql/lib64/python3.12/site-packages/azure/mgmt/sql/aio/operations/_databases_operations.py", line 33, in <module>
    from ...operations._databases_operations import (
ImportError: cannot import name 'build_import_method_request' from 'azure.mgmt.sql.operations._databases_operations' (/home/jcline/.virtualenvs/az-sql/lib64/python3.12/site-packages/azure/mgmt/sql/operations/_databases_operations.py). Did you mean: 'build_import_request'?

Expected behavior
It doesn't crash.
Screenshots
Additional context
I hit this when attempting to update the azure-cli in Fedora which requires this version of azure-mgmt-sql. As part of the standard build check it attempts to import all the public modules in the package, which found this particular issue. I'd recommend introducing a similar check to your CI so you catch this sort of thing before publishing. The script used in Fedora is here: https://src.fedoraproject.org/rpms/python-rpm-macros/blob/rawhide/f/import_all_modules.py

Hi @jeremycline, thank you for reporting this issue. I'll tag the appropriate folks to look into fixing this.

Hi, we will take an investigation soon.

Hi @jeremycline Please help try latest version https://pypi.org/project/azure-mgmt-sql/4.0.0b18/

Works for me, thanks!


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:55:11)
StatusBarSummaryView.render (/Users/****/.atom/packages/linter/lib/statusbar-summary-view.coffee:11:21)

Closing as dupe of #343.


environment problem

Hello, I am a newbee, and trying to build your project in local, but confronted with the problem below:
I follow the README and run python IKRL.py, but it prompt these:

I target the break point at this function call, probably, which is in TrainDataLoader.py

I guess it may have some problem to do with Base.so. Do you have any hint how to resolve this?

Sorry, I can not reproduce your error. This problem may be related to the environment configuration. You could consult IKRL for guidance on configuring the environment and attempt to test if it can successfully execute using their program.

ok...Thanks for reply


Support a Column of Arrays in UDTFs

The following example should be supported:
@omnisci('int32(Column<Array<double>>, RowMultiplier, Column<double>)')
def array_sum(x, m, y):
    for i in range(x):
        y[i] = sum(x[i])

An attempt is made in https://github.com/omnisci/omniscidb-internal/tree/pearu/array-column but according to Slack discussion https://quansight.slack.com/archives/CHSDG1C9W/p1613589094079000 the columnarization of columns of arrays will be problematic due to inflexibilities in ColumnarResult. So, the issue is put to hold.


fix repo and issue buttons, fixes#53

I have tested this on a local version of the book. It works, so fix #53


Discards article: Fix the section about the discard pattern

Fixed two issues:

Discard pattern is not supported by the is operator (if (o is _) { } doesn't compile; neither case _ within the switch statement compiles). So, only by the switch expression. Also added the link to it.
Example has been updated but its description - not. Changed the mention of is operator to switch expression, which is used in the example.

closing and reopening for a fresh build.


This is awesome, I'm weaving it into my setup. How difficult would it be to implement a JSON serializer?

Hello,
Thank you for the interest given to the project.
The JSON serialization should not be so hard, I saw that there exists some libraries for that purpose written in lua.
I do not have much time lately because of work, but I would gladly accept a Pull Request :)
Otherwise, if you are not in a hurry, I can probably do that around beginning of December.


Update Readme.md, adding 'default' instructions

Hi guys,
I saw in the commit history that the 'default' command had been added, so thought I'd update Readme.md to include it.
Thanks for your work,
Andrew

not sure that's quite how this works...
the default task is the task that is run when you just type powder - it should return a list of options. Does it not for you? Are you using the latest version?

I installed the latest pow available on rubygems.
When I type 'powder default' this is the output I expected and got:
andrew@Mal:testapp(master) andrew$ powder default
Your application(testapp) is now default at http://localhost/

When I visit http://localhost/ it correctly serves me the contents of ~/.pow/default

I think we might be talking about different things but with the same vocab, sorry!
Here is the output when I type powder on it's own:
andrew@Mal:testapp(master) andrew$ powder
Tasks:
  powder always_restart  # Always restart current pow
  powder applog          # Tails in current app
  powder cleanup         # Clean up invalid symbolic link
  ...

my bad! thanks!


Receive sound not working in Linux snap

BB version: <IP_ADDRESS>_Linux_Snap
OS: Ubuntu 22.04.4 LTS
Kernel: Linux 6.1.0-1034-oem x86_64 GNU/Linux
Settings -> Conversation Settings -> Sounds -> Change Receive Sound
Send sound is working but receive sound doesn't work in chat view or with BB minimized. I set an mp3 for both sounds.

I'm having this problem for both send and receive. no sound at all
BB ver: <IP_ADDRESS>_Linux_Flatpak
OS: EndeavourOS Linux x86_64
Kernel: 6.9.5-zen1-1-zen


Prism.languages['markup-template'] is undefined in 1.14.0

Run create-react-app
Add prismjs v1.14.0 to dependencies
Import prismjs in App.js
Try outputting if Prism.languages['markup-template'] exists

Issue:
Prism.languages['markup-template'] is undefined even though it is being accessed in prism-php.js
Test repo:
https://github.com/carlovirtucio/prismjs-bug-test
This is being used in prism-php.js, which was somehow being used when I generate code snippets in a proprietary project I'm working on. I can't share the code so I made the simple test app. For Prism JS v1.14.0, this causes a crash in line 121 of prism-php.js

The PHP language has a dependency on markup-templating, which you'd previously have to import manually. However, I recently put together a babel plugin to manage these internal dependencies for you. If you're using create-react-app, you should be able to use it pretty easily. Check out the documentation and open up any issues you find on that repo.

For those who are also having difficulties figuring out how to actually import markup-templating, the correct syntax is:
import 'prismjs/components/prism-markup-templating';


update packages --force upgrade

Description
As it says

FYI @cbracken in case the Fuchsia roll is affected.

Ahh, I didn't see the new dep. Will update

Actually I think since this is transitive we'll be okay, we don't include all of the transitive deps in build.gn


Firewall blocking autoortho_win.exe

autoortho_win.exe is being blocked because the exe respawns itself into temporary folder and launches.
For example: C:\users<username>\appdata\local\temp\onefile_3696_133350554859507474\autoortho_win.exe
The firewall is simplewall. It denies the process, and autoautho exits before I can allow it.
The question is, why is is the exe respawning itself into a temp and hidden directory? Can this behaviour be changed?

Each Virus protection software handles .exe in different ways. The default Windows Defender does not have this issue at all. Have you tried to create exclusions so that  your virus software does not try and block the executable from running? You should have not be running the software in order to allow exclusions.

I got around the problem by downloading the complete zip package and
installing into its own folder. Previously I just had the exe in my x-plane
folder, and it appears the exe was respawning itself into a temporary
directory, and a different one every time, making it impossible for my
firewall to deal with it.
As I originally mentioned, the exe would exit way too quickly on no network
access, so my firewall would ask for permission, but by the time I could
say yes, the application had already exited. Then on the next attempt, the
exe was in a different temp folder and the problem repeated.
Anyhow, downloading the latest complete zip file and installing into it's
own folder seemed to solve the problem. Maybe you could document that
somewhere.
On Sat, Jul 29, 2023 at 11:49 PM dpdurst @.***> wrote:

Each Virus protection software handles .exe in different ways. The default
Windows Defender does not have this issue at all. Have you tried to create
exclusions so that your virus software does not try and block the
executable from running? You should have not be running the software in
order to allow exclusions.
—
Reply to this email directly, view it on GitHub
https://github.com/kubilus1/autoortho/issues/297#issuecomment-1656735627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATT4QY4WGBZYVHDQUECJCN3XSUIGHANCNFSM6AAAAAA24BVOFI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm guessing the re-spawning is because the exe is actually unpacking it self then running python


Dead symlink handling

Add handling for dead symbolic links. Fixes: #6, #19

I'm not certain about is the icon choice for a link. Not familiar enough with FontAwesome.
This PR also adds a few new properties (is_symlink and exists) that can be used in the display template.

#19 ended up being due to another type of unreachable symbolic link, so adding the fix into this branch.
The cause of the issue is that the is_dir/is_file methods of DirEntry throw PermissionErrors when used on a walled-off symbolic link.

Phrasing question: "Dead Symbolic Link" or "Unreachable Symbolic Link"? I'm used to saying "dead", but that could just be a casual habit.


GeckoLib support

Issue tracker rule checks (please read carefully)

[X] I have checked that this feature is not already asked.
[X] I have checked that this feature is not already implemented.

Feature description
Can you bring back the GeckoLib support ? It is very usefull for animating and can’t really without it. Nerdy’s mcreator plugin is only for forge.

That's the issue. I don't know anything but APIs.
Geckolib is hard as you need to add Procedures too.. & I guess know nothing about procedures... Also, it won't make any sense that I added API but not procedures, then it is just waste of time too. Plus, my exam are going on... so yeah...
Just waiting for a PR (who makes a PR that means he/she is Godsent, atleast for me though)


Change deploy to publish in sql project codebase

This PR fixes #10774. The UI strings were changed from deploy to publish in a previous PR. This changes the rest of the codebase to be consistent and use publish too.

Coverage increased (+0.07%) to 35.397% when pulling 59f05e89679bc7fec7991939073cc0531417f0f3 on kisantia/publish into 93a88e38fe7cd18e833ddf3e690aefbcca913abc on main.


POST request body is empty

I just noticed that with a worker being run through vite-plugin-cloudflare, any POST body data is empty.
export default {
  fetch: async (request) => {
    console.log(`worker request ${request.url}`, `"${await request.text()}"`)

    return new Response("hello")
  },
}

Then if I go to the page and make this request:
fetch("/test", {
    method: "POST",
    body: "test",
})

This is what gets logged:
worker request http://localhost:8787/test ""

If I run the exact same worker code directly through Miniflare however, it works.
This might have to do with VPC doing some kind of body parsing beforehand?
Sample repo: https://github.com/alexturpin/vpc-test

Oh, it seems as if toRequest simply doesn't handle bodies at all?
https://github.com/Aslemammad/vite-plugin-cloudflare/blob/main/packages/vite-plugin-cloudflare/src/utils.ts#L5


Typescript and absolute import paths in server bundle

I'm scratching my head, hoping someone can point me in the right direction.
After upgrade to TypeScript 2.1 and webpack2-beta27, I've started using non-relative imports, aka
import * from 'store/foo'
with the help of TsConfig settings

 // when importing with relative path 'some/module', start from web root directory
    "baseUrl": ".",

    // instruct the compiler to try resolve; starting from root with baseUrl
    "paths": {
      "*": [
        "*"
      ]
    }

For webpack client bundles this works great, offering a more refactor friendly approach then the relative imports.

Now, for server rendering, using aspnet-prerendering@2, I'm getting webpack errors (ts-loader?) like

Module not found: Error: Can't resolve 'store/foo' in  'C:(......)\app\shared\feature\bar' @ ./app/shared/feature/bar.tsx

From
What I've tried:

using resolve.modules
resolve.alias
removing (tsconfig) "module": "es2015" (tree-shaking) but to no luck.

Server bundle config

var serverBundle = {
    resolve: {
      mainFields: ['main'],
      extensions: [ '.js', '.jsx', '.ts', '.tsx' ],
      alias:{
        app: path.resolve(__dirname, 'app')
      },
      modules: [
           path.resolve(__dirname, '.'),
           path.resolve(__dirname, 'app'),
           path.resolve(__dirname, 'node_modules')
        ]
    },
    module: {
        rules: [
            { test: /\.json$/, include: /app/, loader: 'json-loader' },
            { test: /\.tsx?$/, include: /app/, loader: 'babel-loader' },
            { test: /\.tsx?$/, include: /app/, loader: 'ts-loader', query: { silent: true } },
            { test: /\.scss$/, exclude: [ /(node_modules)/], loader: 'style-loader!css-loader!sass-loader' },
            { test: /\.png$/, loader: "url-loader?limit=100000" }
        ]
    },
    entry: { 'server': './app/infrastructure/boot-server.tsx' },
    plugins: [
        new webpack.DllReferencePlugin({
            context: __dirname,
            manifest: require('../wwwroot/dist/vendor-manifest.json'),
            sourceType: 'commonjs2',
            name: './vendor'
        })
    ],
    output: {
        libraryTarget: 'commonjs',
        path: path.join(__dirname, '../wwwroot', 'dist'),
        filename: '[name].js'
    },
    target: 'node',
    devtool: 'inline-source-map'
};

I'm not sure what the issue is in your setup, but I tried setting up the same thing and it appeared to work fine.
Could you compare your implementation to the following to determine the issue? https://github.com/aspnet/JavaScriptServices/commit/acdf18f19e3cd7860de766e90fe5168c8318e1c0

Seems like webpack context: __dirname + upgrade to ts-loader 1.3 did the trick.
Thank you very much, I really appreciate the quick response!


cluster-autoscaler cannot count migrated PVs and cannot scale up on exceed max volume count

How to categorize this issue?

/area quality auto-scaling
/kind bug
What happened:
cluster-autoscaler cannot count migrated PVs -> cannot scale up on exceed max volume count. Pod(s) hangs forever in Pending state.
What you expected to happen:
cluster-autoscaler to properly count migrated PVs and to scale up appropriately on scheduling failures with reason exceed max volume count.
How to reproduce it (as minimally and precisely as possible):

Create a cluster with K8s that does not have CSI enabled (for example AWS cluster with K8s 1.17)
For machine type select a one that allows 25 volume attachments - for example m5.large
Autoscaler should be also enabled for this cluster. An example worker spec:
 workers:
   - cri:
       name: containerd
     name: worker-nq600
     machine:
       type: m5.large
       image:
         name: gardenlinux
         version: 318.8.0
     maximum: 2
     minimum: 1
     maxSurge: 1
     maxUnavailable: 0
     volume:
       type: gp2
       size: 50Gi
     zones:
       - eu-west-1c
     systemComponents:
       allow: true

Make sure that you have a single Node. Its allocatable volume attachments should be 25.
$ k get csinode

spec:
  drivers:
  - allocatable:
      count: 25
    name: ebs.csi.aws.com

Create dummy StatefulSet and scale to 20 replicas
apiVersion: v1
kind: Service
metadata:
  name: nginx
  labels:
    app: nginx
spec:
  ports:
  - port: 80
    name: web
  clusterIP: None
  selector:
    app: nginx
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: web
spec:
  selector:
    matchLabels:
      app: nginx # has to match .spec.template.metadata.labels
  serviceName: "nginx"
  replicas: 3 # by default is 1
  template:
    metadata:
      labels:
        app: nginx # has to match .spec.selector.matchLabels
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - name: nginx
        image: k8s.gcr.io/nginx-slim:0.8
        ports:
        - containerPort: 80
          name: web
        volumeMounts:
        - name: www
          mountPath: /usr/share/nginx/html
  volumeClaimTemplates:
  - metadata:
      name: www
    spec:
      accessModes: [ "ReadWriteOnce" ]
      resources:
        requests:
          storage: 1Gi

$ k scale sts web --replicas=20

This will create 20 Pods and PVs (note that PV are created with the internal volume driver).

Update to K8s version with CSI enabled (for example AWS cluster with K8s 1.18)
After completing this spec you should have 20 "migrated" PVs (PVs that are provisioned with the in-tree volume plugin).

Scale the StatefulSet to 26 replicas
$ k scale sts web --replicas=26

Make sure that the 26th replica (Pod web-25) fails to be scheduled (as expected) but cluster-autoscaler never triggers a scale up
Events:
Type     Reason            Age   From               Message
----     ------            ----  ----               -------
Warning  FailedScheduling  54m   default-scheduler  0/1 nodes are available: 1 node(s) exceed max volume count.
Warning  FailedScheduling  54m   default-scheduler  0/1 nodes are available: 1 node(s) exceed max volume count.

(If you perform this steps to reproduce on a cluster without any migrated PVs, the cluster-autorscaler then is able to trigger the expected scale up)
Logs of cluster-autoscaler:
I1124 14:44:02.817569       1 csi.go:178] Persistent volume had no name for claim default/www-web-25
I1124 14:44:02.817584       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817592       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817599       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817606       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817612       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817615       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817629       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817634       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817641       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817644       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817649       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817652       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817659       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817662       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817668       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817671       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817678       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817685       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817691       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817694       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817700       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817705       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817713       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817721       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817729       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817732       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817738       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817741       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817751       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817759       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817766       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817769       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817774       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817778       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817787       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817791       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817797       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817800       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817806       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817809       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume
I1124 14:44:02.817818       1 scheduler_binder.go:241] FindPodVolumes for pod "default/web-25", node "ip-10-250-28-64.eu-west-1.compute.internal"
I1124 14:44:02.817842       1 scheduler_binder.go:819] No matching volumes for Pod "default/web-25", PVC "default/www-web-25" on node "ip-10-250-28-64.eu-west-1.compute.internal"
I1124 14:44:02.817852       1 scheduler_binder.go:883] Provisioning for 1 claims of pod "default/web-25" that has no matching volumes on node "ip-10-250-28-64.eu-west-1.compute.internal" ...
I1124 14:44:02.817868       1 filter_out_schedulable.go:118] Pod default.web-25 marked as unschedulable can be scheduled on node ip-10-250-28-64.eu-west-1.compute.internal (based on hinting). Ignoring in scale up.
I1124 14:44:02.817878       1 filter_out_schedulable.go:132] Filtered out 1 pods using hints
I1124 14:44:02.817884       1 filter_out_schedulable.go:170] 0 pods were kept as unschedulable based on caching
I1124 14:44:02.817888       1 filter_out_schedulable.go:171] 1 pods marked as unschedulable can be scheduled.
I1124 14:44:02.817894       1 filter_out_schedulable.go:79] Schedulable pods present
I1124 14:44:02.817913       1 static_autoscaler.go:402] No unschedulable pods
I1124 14:44:02.817929       1 static_autoscaler.go:449] Calculating unneeded nodes

Anything else we need to know?:
From what I managed to track in the autoscaler repository, the autoscaler creates a new scheduler framework and "simulates" whether the Pod is really unschedulable (most probably using default scheduling config). This was something new for me.
I1124 14:44:02.817868       1 filter_out_schedulable.go:118] Pod default.web-25 marked as unschedulable can be scheduled on node ip-10-250-28-64.eu-west-1.compute.internal (based on hinting). Ignoring in scale up.

The above log entry makes it clear that the Pod is unschedulable according to the kube-scheduler (exceed max volume count) but the same Pod is schedulable according to the cluster-autoscaler. The differences comes from the NodeVolumeLimits filter in the scheduler - kube-scheduler obviously has the required CS migration feature gates set and can correctly count migrated volumes. cluster-autoscaler current does not have any such config, hence it cannot count migrated volumes:
I1124 14:44:02.817806       1 csi.go:205] CSI Migration of plugin kubernetes.io/aws-ebs is not enabled
I1124 14:44:02.817809       1 csi.go:158] Could not find a CSI driver name or volume handle, not counting volume

I believe this is exactly the issue we hit when we enabled SeedKubeScheduler feature gate on our landscapes.
Environment:

Gardener version: v1.36.0
Kubernetes version (use kubectl version): v1.17 and v1.18 (see steps to reproduce)
Cloud provider or hardware configuration:
Others:

/cc @AxiomSamarth @himanshu-kun

@ialidzhikov I think there is a similar issue on upstream autoscaler. Link to issue

@ialidzhikov I think there is a similar issue on upstream autoscaler.

Link to issue
Also this

I will some time around this to understand the reason and to find a solution if any tomorrow. In the meantime, these links can be of some help to you.

I am not super convinced that these are the same issue. We are not applying any custom max volume limit or any custom scheduling config (is this even possible/supported?). I think the default volume limit and the default scheduling config are used.
PS. If it is really not possible to apply a custom scheduling config to the cluster-autoscaler, then this sounds like yet another blocker issue for #4741.

Yes, AFAIK, custom scheduling configurations are not possible in CA. It runs the default ones. Also, it does not interact with the actual scheduler binary running in the cluster, instead imports some of the scheduling codes and runs it within CA. So, there are high chances that the behaviour may vary.

I think the default volume limit and the default scheduling config are used.

@ialidzhikov  I think the default scheduling config is not used because

gardener CA is inline with upstream CA v1.20 which uses scheduler v1.20
the CSIMigrationAWS feature gate is not enabled by defualt in scheduler v1.20 as per this doc but you have enabled it.

Because of this the CA scheduling algo hits this code.
Doesn't look like we can enable/disable feature gates in CA scheduler algo as per this comment.

Any fresh inferences or conclusions arrived at wrt this issue?

If it is really not possible to apply a custom scheduling config to the cluster-autoscaler, then this sounds like yet another blocker issue for #4741.

@ialidzhikov I wouldn't say blocker, but it's generally bad. Reasoning:

When we speak about #1455 (I would probably rather drop the current custom scheduler code behind #4617 and map #4741 to #1455 if we anyway offer that for end users), we will offer it as alpha feature anyway for certain "big players" and they can test their scenarios specifically before going (or not going) for this feature.
I wholeheartedly agree that the primitive way how CA deals with the entire subject matter (own simulation of scheduler logic that always trails behind instead of finding some common ground/making the core kube-scheduler scheduling logic  reusable and using it in CA) is very bad, but we actually "only" want to switch to bin-packing in #1455 and that isn't making things worse, I believe (the bug is, but not the difference in this single scheduling "flag"), because:

If the pod can be scheduled to a node that is highly utilised but still has capacity, CA is not invoked and everything runs smoothly.
If the pod cannot be scheduled at all, the CA should see that error and the simulation should find that a new node is required and create it so that the pod can be scheduled. But as you wrote, it doesn't and that seems to be a bug rather than the problem of the improper simulation.

All in all, I would be even OK to go on with #1455 and put a fat disclaimer to that alpha feature: Doesn't work properly on clusters with migrated volumes (this issue) and may cause kubelet issues (cgroup setup issue).
But, I would rather want to find a way to resolve this and the cgroups issue first, of course.
So, that bug and our seeds are certainly blockers for #4741 (not necessarily for #1455), but the poor simulation in general (without that bug) is probably not a blocker, but as bad as it was also before (years ago I was shocked that CA has implemented a simulation of their own - it was always awful that the community went down this troubling path, but probably scheduling was much simpler back then when the first version of CA was short-sightedly released).

@himanshu-kun @AxiomSamarth How can we help to make this "bug" disappear and go on with the bin-packing feature that will probably safe all users tons of money and help reduce the ecological footprint the default spread scheduling has?
Yes, I got that it's not really a proper bug (from @himanshu-kun analysis in https://github.com/gardener/gardener/issues/5064#issuecomment-979424468), because it's primarily a "misalignment" between what the scheduler sees/does (as @ialidzhikov reported) and the CA that doesn't have these insights, but we have a fork. Can we make a tweak (we already have a bunch of patches that we have to back-port when we upgrade to new upstream versions) in the case of Gardener that works for all our clusters (old and new versions)?

For this particular issue I created https://github.com/kubernetes/autoscaler/issues/4517. The issue was discussed yesterday in the SIG Autoscaling meeting. I will give a try to follow-up on this issue and check what needs to be done.
While we talk about volume limits and scaling on volume limits, there is also https://github.com/kubernetes-sigs/aws-ebs-csi-driver/issues/1139 - volume limits maintained by aws-ebs-csi-driver for a lot of nitro instance types is wrong.
For the concern raised in https://github.com/gardener/gardener/issues/5064#issuecomment-978062759 (the cluster-autoscaler scheduling config vs the kube-scheduler scheduling config) I created https://github.com/kubernetes/autoscaler/issues/4518. The reply from a cluster-autoscaler maintainer was that the cluster-autoscaler runs only kube-scheduler Filters. In theory, if we only have custom config for the Scoring, and use the default Filters, this should not affect us. But I haven't played with it yet.

Wrt to the 1st issue from https://github.com/gardener/gardener/issues/5064#issuecomment-993657306, folks from the upstream community asked me to try out with latest cluster-autoscaler (that vendors K8s v1.23.0) because some of the CSI feature gates are enabled by default with K8s v1.23.0. How I am supposed to do this when our forked cluster-autoscaler vendors K8s v1.18? @AxiomSamarth @himanshu-kun do plan anytime soon to update the cluster-autoscaler fork (https://github.com/gardener/autoscaler/issues/91, https://github.com/gardener/autoscaler/issues/89)?

Could you try these steps out locally on our Gardener fork (machine-controller-manager-provider branch) and rebase with latest upstream master? Steps are here & these steps are yet to be merged in the FAQ of the repo via this PR
Currently, we are not planning on upgrading it to latest because there could be multiple version jump. This will have to be done as a careful exercise as the CA rebasing is a bit tricky.

Could you try these steps out locally on our Gardener fork (machine-controller-manager-provider branch) and rebase with latest upstream master? Steps are here & these steps are yet to be merged in the FAQ of the repo via this PR
Currently, we are not planning on upgrading it to latest because there could be multiple version jump. This will have to be done as a careful exercise as the CA rebasing is a bit tricky.

That's disappointing.

What is the update/sync strategy for out forked CA? Because the current strategy from your reply seems to be "we don't want to do it right now because it is painful".
What is the versioning policy and compatibility promises of our forked CA? Why we don't maintain a version for each and every K8s release? The upstream CA does this (https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler#releases). Why our forked CA does not follow the same approach?
With this issue we see that we depend actually on the K8s version that is vendored by CA because of the kube-scheduler feature gates that have different values for each and every release. As a "happy" consumer of our forked CA I would like to use a concrete CA version per K8s version (for example CA version v1.22 only for K8s).
I don't see any continuous effort invested in this fork wrt to updating it and rebasing it to the upstream. Obviously it is easy to fork and "make the things work" but do we think in longterm what is impact of having such fork and maintaining it?

And @vlerenc above suggesting for yet another hack in our a fork:

Can we make a tweak (we already have a bunch of patches that we have to back-port when we upgrade to new upstream versions) in the case of Gardener that works for all our clusters (old and new versions)?

Sorry, that's too much and this is not how I imagine the things to work. Your approach seems to be "fork the thing", "hack it in ugly way if needed" and "don't invest any effort about rebasing/syncing the fork". Ideally we should be investing into getting rid of this fork..

Currently, we are not planning on upgrading it to latest because there could be multiple version jump.

Can you explain me what is the plan plan forward with this CA fork?

What is the update/sync strategy for out forked CA? Because the current strategy from your reply seems to be "we don't want to do it right now because it is painful".

It is painful, I agree. But, I beg to differ with you with respect to why we do not want to do it right now. It is not because it is painful, but because there is one important release around scale to zero which is awaited immediately. When we started working on CA a couple of months back and when we did, the first exercise we did was to rebase with the upstream to a version (or to a commit-hash to be more precise) where things weren't breaking see here and before this, it was done in December 2020 by colleagues before see here. So, there is indeed a debt.

Can you explain me what is the plan forward with this CA fork?

Current plan would be to cut a release with scale to zero feature & then rebase the fork with latest upstream (version by version).
We have a process already to keep the fork up to date which is not documented yet. We plan to pick it up as next step.
Also we shall work on introducing a release matrix as you suggested (just like it is in upstream). Thank you for this!

why we do not want to do it right now

Sure @AxiomSamarth, the general statement/recommendation always is to finish topics before picking up new ones. So, let's get scale-to/from-zero done first before tackling something new.

Your approach seems to be "fork the thing", "hack it in ugly way if needed" and "don't invest any effort about rebasing/syncing the fork". Ideally we should be investing into getting rid of this fork..

@ialidzhikov Please don't rush with your statements. Often people have reasons.

Current plan would be to cut a release with scale to zero feature & then rebase the fork with latest upstream (version by version).

I created the following issue (https://github.com/gardener/autoscaler/issues/107) with my expectations/proposal.

https://github.com/kubernetes/autoscaler/pull/4539 was merged, looking forward to gardener/autoscaler#107.

I now verified once again (this time with the above-linked changes in the extensions and the new cluster-autoscaler images) that this issue gets resolved (scale-up happens when the volume limit is reached for the Node).

We can close this issue now, all above-linked PRs are merged.
/close


Registry-based eventlog monitoring

This one solves #36
Tested and working in production at CO.

I know this works in PROD, OK to merge


Fixed an error that occurred when using the ifcountd function in a user-defined field

Description
Fixed an error that occurred when using the ifcountd function in a user-defined field.
Related Issue : None
How Has This Been Tested?

Create a dashboard utilizing the Sales data source.
Create a user-defined column of measure type.
Create a expression using the ifcountd function, enter an arbitrary column name, and create a column. ex. IFCOUNTD( [Region]  != 'East',  [Region] )

Create a chart using this column.
Confirm that the chart is displayed without errors.

Need additional checks?

Check that no other aggregate functions are working.

Types of changes

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

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have added tests to cover my changes.

Additional Context

run build
deploy to 1

@kyungtaak
I think some results of ifcountd are not intended.
It should be calculated as;
(Total count) - (Count of matching an if statement) = (Count of not matching an if statement)
Am I misunderstanding this formula? 😮

@alchan-lee :) The ifcountd function uses a cardinality aggregator in druid engine internally, unlike the countd function. As mentioned in the link, this cardinality aggregator may be less accurate. This part requires work on the engine separately, which seems to be out of line with the current issue.

 In the created chart screen, when i apply Year( [action_date] ) function on a timestamp field [action_date], i obtain just only one value (-1).
This function is OK when i apply this function on a single timestamp value. Can u help me.


added correct redis command in compose to read conf file on startup

Description of PR

What component(s) does this PR affect?

[X] Back-End (Database, Detection/Configuration/etc. Microservices)
[ ] Front-End (Flask, API, UI, etc)
[ ] Monitor (RIPE RIS, BGPStream RV/RIS/CAIDA, etc.)
[ ] Docs
[ ] Build System

Does the PR require changes on other components? If yes, please mark the components:

[ ] Back-End (Database, Detection/Configuration/etc. Microservices)
[ ] Front-End (Flask, API, UI, etc)
[ ] Monitor (RIPE RIS, BGPStream RV/RIS/CAIDA, etc.)
[ ] Docs
[ ] Build System

Related Issue

Resolves #558
Solution

Type

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Docs update
[ ] None of the above

Checklist:

[X] I have read the contributing guide and my code conforms to the guidelines.
[ ] This change requires a change in the documentation.
[ ] I have updated the documentation accordingly.

@slowr do you agree with this PR? Any suggestions/comments? After I merge it we can check the other one that uses redis key expiry events to restart taps that do not receive any data for certain time periods.

@slowr do you agree with this PR? Any suggestions/comments? After I merge it we can check the other one that uses redis key expiry events to restart taps that do not receive any data for certain time periods.


helm: Fix invalid type for Certificate spec.ipAddresses

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

Certificate spec.ipAddresses field must be an array, but will be null if
an empty array is specified in values.yaml. This will be reported as an
invalid type by validator such as kubeconfirm or kubeval.
The difference from the master branch is as follows:
$ git show -q
commit 774a91f0e7497d9c9085234005ec81f1065c3783 (HEAD -> master, origin/master, origin/HEAD)
Author: Daniel Borkmann<EMAIL_ADDRESS>Date:   Fri Mar 18 15:50:16 2022 +0000

    bpf: Add trace reason for TRACE_TO_PROXY

    TRACE_TO_PROXY was missing the trace reason argument in bpf_lxc. Given
    we just got it from CT lookup anyway, pass it onwards.

    Signed-off-by: Daniel Borkmann<EMAIL_ADDRESS>
$ helm template cilium install/kubernetes/cilium \
--set hubble.tls.auto.enabled=true \
--set hubble.tls.auto.method=certmanager \
--set hubble.tls.auto.certManagerIssuerRef.group="cert-manager.io" \
--set hubble.tls.auto.certManagerIssuerRef.kind="ClusterIssuer" \
--set hubble.tls.auto.certManagerIssuerRef.name="ca-issuer" \
--set hubble.relay.enabled=true \
--set hubble.relay.tls.server.enabled=true >/tmp/cilium-master.yaml

$ git show -q
commit 2832e8eb438746645670a01b475b892f081e3f5a (HEAD -> fix-cert-ipAddresses-null)
Author: Kazuki Suda<EMAIL_ADDRESS>Date:   Mon Mar 21 22:29:23 2022 +0900

    helm: Fix invalid type for Certificate spec.ipAddresses

    Certificate spec.ipAddresses field must be an array, but will be null if
    an empty array is specified in values.yaml. This will be reported as an
    invalid type by linter such as kubeconfirm or kubeval.

    Signed-off-by: Kazuki Suda<EMAIL_ADDRESS>
$ helm template cilium install/kubernetes/cilium \
--set hubble.tls.auto.enabled=true \
--set hubble.tls.auto.method=certmanager \
--set hubble.tls.auto.certManagerIssuerRef.group="cert-manager.io" \
--set hubble.tls.auto.certManagerIssuerRef.kind="ClusterIssuer" \
--set hubble.tls.auto.certManagerIssuerRef.name="ca-issuer" \
--set hubble.relay.enabled=true \
--set hubble.relay.tls.server.enabled=true >/tmp/cilium-fix-cert-ipAddresses-null.yaml

$ diff -u /tmp/cilium-master.yaml /tmp/cilium-fix-cert-ipAddresses-null.yaml
--- /tmp/cilium-master.yaml     2022-03-21 22:46:08.035415103 +0900
+++ /tmp/cilium-fix-cert-ipAddresses-null.yaml  2022-03-21 22:45:24.622872275 +0900
@@ -925,7 +925,6 @@
   commonName: "*.hubble-relay.cilium.io"
   dnsNames:
   - "*.hubble-relay.cilium.io"
-  ipAddresses:
   duration: 26280h
 ---
 # Source: cilium/templates/hubble/tls-certmanager/server-secret.yaml
@@ -943,5 +942,4 @@
   commonName: "*.default.hubble-grpc.cilium.io"
   dnsNames:
   - "*.default.hubble-grpc.cilium.io"
-  ipAddresses:
   duration: 26280h

Using kubeconform to validate the Certificate object, we can see that there are no errors in the manifest generated on this branch, compared to errors in the manifest generated on the master branch.
$ mkdir -p crd_schemas && cd crd_schemas
$ wget https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml
$ wget https://raw.githubusercontent.com/yannh/kubeconform/v0.4.13/scripts/openapi2jsonschema.py
$ python openapi2jsonschema.py cert-manager.crds.yaml
JSON schema written to certificaterequest_v1.json
JSON schema written to certificate_v1.json
JSON schema written to challenge_v1.json
JSON schema written to clusterissuer_v1.json
JSON schema written to issuer_v1.json
JSON schema written to order_v1.json
$ curl -s -L https://github.com/yannh/kubeconform/releases/download/v0.4.13/kubeconform-linux-amd64.tar.gz | tar xvzf
- kubeconform
kubeconform

# The branch of this PR
$ cat /tmp/cilium-fix-cert-ipAddresses-null.yaml | ./kubeconform -strict -schema-location "certificate_v1.json" | grep Certificate

# The master branch
$ cat /tmp/cilium-master.yaml | ./kubeconform -strict -schema-location "certificate_v1.json" | grep Certificate
stdin - Certificate hubble-relay-server-certs is invalid: For field spec.ipAddresses: Invalid type. Expected: array, given: null
stdin - Certificate hubble-server-certs is invalid: For field spec.ipAddresses: Invalid type. Expected: array, given: null

I don't think full test is required, this only contains helm changes, which is tested in github action.


[TableHeaderColumn][TableRow][TableRowColumn] Remove props.key calls

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Calls to props.key will throw a warning in React v15 (see here).
This commit removes calls to props.key in TableHeaderColumn, TableRow, and TableRowColumn.  TableRow children are given an auto-generated key, and children of TableHeaderColumn and TableRowColumn can define their own keys as needed.  As far as I can tell, passing a component's key prop down to the root element of that component is unnecessary, even if a key is required for the component.
This PR is referenced here:  https://github.com/callemall/material-ui/pull/3913#issuecomment-207823360

Contributes to #3642.

@mbrookes This looks good to me... however I had some issues with the complex example table demo in the docs. But it seems as though that example is even buggy on 0.14.4.
Can you confirm my findings? if so this can be merged.

@nathanmarks - yes, I've noticed that before, but was too afraid to go near it! :smile:


Remove console.logs

Please remove console calls

Please provide some info backing your issue (use case, pros/cons etc).

I think polluting console is not acceptable from any library. We use console to collect errors and logs from user side. Other libraries use debug flag and/or custom loggers defaultly connected to console to log.

Why was this closed? It only removes the console.logs when this is included as a module. I don't want to include it as a module but do want to turn off logging in production as it is just noise there.

if you are not using this as a dependency, can't you simply remove the single console.log.apply line?

@fippo I could. But then I'd have to do that everytime I updated this (which I'm including through bower).

My 2 cents: I find some of the logging useful (how constraints are translated on an older browser), and other logging not so useful (This is firefox? get out).
How about adapter.js only emit to console when it actually does something? That way, one can silence it by being spec compliant.

I'd still prefer an option to completely silence it if I wanted, even if it did do something.

I will add a logging switch to Adapter.js 2.0.

@KaptenJansson Thanks for committing to fixing this. I think this issue should be re-opened (and not closed till actually addressed).
Can this be done in a release sooner than adapter.js 2.0? A polyfill that is intended to be included in the browser should absolutely not console.log by default. I would love to be able to include adapter.js as a dependency in an npm project, without having to fork it.


Finetuning the bottleneck features model based on InceptionV3 - strange behavior

I have a very similar problem to this one: https://gist.github.com/fchollet/7eb39b44eb9e16e59632d25fb3119975#gistcomment-2315777 or this one:
https://datascience.stackexchange.com/questions/25227/fine-tuning-accuracy-lower-than-raw-transfer-learning-accuracy.
Here's what I'm doing:

Creating InceptionV3 instance without top layer and with imagenet weights.
Saving bottleneck features.
Building the "top layer" (classifier) model and training it on bottleneck features. Model receives about 82% accuracy
Saving predictions of validation-based bottleneck features.

Now I want to take these weights and make a new full InceptionV3 model, opening some of the layers for training and retraining them. So I'm creating the model (see code below) and try to make predictions on my validation set.
First thing I see is that these predictions are different from my bottleneck-features model (point 4), even though the weights were just loaded from that model.
When I try to fine-tune this model I start from very low train accuracy (and quite high validation accuracy), which despite many epochs (20-30) never reaches the level of the bottleneck features model.
From what I've seen on the keras blog(https://blog.keras.io/building-powerful-image-classification-models-using-very-little-data.html). The accuracy during fine tuning should get higher than from bottleneck-features model, and start from similar accuracy as bottleneck-features model ended up with. And that's what was happening on the same data with VGG16 model. But it doesn't with InceptionV3, and since this model gives different predictions than bottleneck-features model I don't know whether I can safely deploy any of them.
Any Ideas where's the mistake / error? Any help would be appreciated, especially that the previous topics have not been answered, so I guess I'm not the only one having these problems.
Here's the code:

datagen = ImageDataGenerator(rescale=1. / 255,horizontal_flip=True,
                            rotation_range=5)

model = InceptionV3(weights='imagenet', include_top=False)

generator_train = datagen.flow_from_directory(
    train_data_dir,
    target_size=(img_width, img_height),
    batch_size=batch_size,
    class_mode=model_type,
    shuffle=False)

bottleneck_features_train = model.predict_generator(generator_train, train_labels_len // batch_size)
np.save(models_location + '/bottleneck_f_train_inception.npy', bottleneck_features_train)
datagen = ImageDataGenerator(rescale=1./255)

generator_valid = datagen.flow_from_directory(
    validation_data_dir,
    target_size=(img_width, img_height),
    batch_size=batch_size,
    class_mode=model_type,
    shuffle=False)

bottleneck_features_validation = model.predict_generator(generator_valid, valid_labels_len // batch_size)
np.save(models_location + '/bottleneck_f_validation_inception.npy', bottleneck_features_validation)

model = Sequential()
model.add(GlobalAveragePooling2D(name='avg_pool', input_shape=train_data.shape[1:]))
model.add(Dense(1, activation='sigmoid'))
print(train_data.shape[1:])
model.compile(optimizer=optimizers.SGD(lr=learn_r)
              , loss=loss_type
              , metrics=['accuracy'])

history= model.fit(train_data, train_labels[:int(np.floor(len(train_labels)/batch_size)*batch_size)],
          epochs=epochs,
          batch_size=batch_size,
          validation_data=(validation_data, validation_labels), callbacks= [mcp, early_stopping])

model.save_weights(top_model_weights_path_modelSDG)

base_model = InceptionV3(weights='imagenet', include_top=False, input_tensor = Input(shape=(299,299,3)))

# build a classifier model to put on top of the convolutional model
top_model = Sequential()
top_model.add(GlobalAveragePooling2D(name='avg_pool', input_shape=train_data.shape[1:]))
top_model.add(Dense(1, activation='sigmoid'))

top_model.load_weights(top_model_weights_path_modelSDG)

# add the model on top of the convolutional base
model_new = Model(inputs= base_model.input, outputs= top_model(base_model.output))

### Different predictions!
model_predict_valid = model.predict(validation_data)
model_new_predict_valid = model_new.predict_generator(generator_valid)

print(model_predict_valid[1])
print(model_new_predict_valid[1])

[0.6749178]
[0.8031555]

@TroubleMak3r OMG, even I am stuck with exactly same issue. Were you able to find the reason for different accuracy?

f

I'm having the same problem. From some research it seems like it's to do with batch normalization layers which are turned off when creating the bottlenecks and turned on during the finetuning stage. So the bottleneck layer values during finetuning are actually different from the ones cached in the initial bottleneck layer training step. Not sure what the solution is really, other than passing images through the entire network during the first stage and not caching bottleneck values, which will slow things down a lot... Did you work anything out?


Markdown markup appearing

I am seeing things like ![Azure Traffic Manager 'Priority' traffic-routing method][1] in this document.

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

ID: fec705c3-1ca3-f5e7-d5ff-3e2baa11a5e8
Version Independent ID: 3936b98a-94e1-8781-15de-d8fa6fd552b7
Content: Azure Traffic Manager - traffic routing methods
Content Source: articles/traffic-manager/traffic-manager-routing-methods.md
Service: traffic-manager
GitHub Login: @KumudD
Microsoft Alias: kumud

@duncansmart Thanks for bringing this to our attention! I have fixed the issue.
#please-close

@duncansmart We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


redux-oidc middleware catches all unhandled exceptions

Great work on the project! The only issue I'm having is that all my thrown errors seem to get caught by the middleware and presented (incorrectly) as oidc middleware errors. I think the issue is coming from this line:
https://github.com/maxmantz/redux-oidc/blob/b8f7f7b371c1e447f80857d01d1435b4e0a3bc17/src/oidcMiddleware.js#L50
What do you think? Is there a way to have my own code's exceptions bubble to the top without getting caught?

This is a "bug" in a sense that the error messages are indeed unclear. The only alternative I can think of is dropping the catch part of the middleware. I will look into this.

Fixed in v3.0.0-beta.6


Session store not set on request

500 internal server errors when logging in.
{message: "Session store not set on request.", exception: "RuntimeException",…}
exception: "RuntimeException"
file: "E:\php\laravel-vue-boilerplate\vendor\laravel\framework\src\Illuminate\Http\Request.php"
line: 483
message: "Session store not set on request."
trace: [{file: "E:\php\laravel-vue-boilerplate\app\Http\Controllers\Auth\LoginController.php", line: 72,…},…]

Thanks @devstorm321, helpful 👍 , hope your PR get merged soon!

I found the solution from https://laracasts.com/discuss/channels/laravel/sanctum-throws-session-store-not-set-on-request

I was able to resolve this by adding \Illuminate\Session\Middleware\StartSession::class to the api middleware group in Kernel.php


A Pokemon with 0 HP in the first party slot can still battle

I had my lead Pokemon faint then started another battle and it was sent out with 0 hp and could survive one hit before fainting again. After this when I started another battle it did not get sent out. To reproduce have a party of two Pokemon and have the first one faint then start a battle.

Fixed by https://github.com/FullScreenShenanigans/BattleMovr/pull/34


Creat AddressBook.json

Does not make sense to add project, which was created few days back and it does not have any stars, interactions, reputation and not verifiable manual builds. Easily infectable release artefacts.


Update to roc-toolkit 0.4.0

coverage: 95.034% (-0.4%) from 95.429%
when pulling 50562acc2e2bf8c93466cf9ff077fd4d054a8b48 on gavv:main
into 07933d7a45dd7da29a1de6ddbcd65ac32d2de95e on roc-streaming:main.

coverage: 95.034% (-0.4%) from 95.429%
when pulling 9975409c2c0089ca087a222d4070aecf4a230125 on gavv:main
into 07933d7a45dd7da29a1de6ddbcd65ac32d2de95e on roc-streaming:main.


RF: fix tests, enabling predict_proba

/intelci: run

CI might be bound from this PR We don't have to run CI twice

/intelci: run
set repo=https://github.com/agorshk/daal.git
set branch=dev/agorshk-forest_feature_filtering

/intelci: restart
set repo=https://github.com/agorshk/daal.git
set branch=dev/agorshk-forest_feature_filtering

/intelci: restart
set ext_build=ebe5366e-233d-f1c1-a04c-8cdcd4b6d2c4

@Mergifyio rebase


how can i hook the event just after i get the data?

I have a setting.
dataSource: 'http://192.168.xx.xx:xxx/filepath/get/all'
Then get my server data like
{"id": 131, "text": "root", "path": "c://", "type": "folder"}
Then i want to set the imageUrl by the param "type" before it begin to do databind

Hello,
You can use one of the following configuration options:
http://gijgo.com/tree/configuration/imageUrlField
http://gijgo.com/tree/configuration/imageHtmlField
http://gijgo.com/tree/configuration/imageCssClassField


Add possibility to put every class in separate file

Suggestion
I suggest to add possibility to put every class in separate file although they belong to one module and TypeScript must generate one module with these classes.
Use Cases
Because it is a standard and convenient way to develop classes.
Examples
Java, C#?
Checklist
My suggestion meets these guidelines:

[X] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. new expression-level syntax)

You can already accomplish this today by re-exporting the classes.

 I found examples only here https://stackoverflow.com/questions/29168813/typescript-how-to-export-two-classes-in-separate-files-in-one-module but they all suppose extending in final module classes that are in separate files.

The question about this was asked on StackOverflow https://stackoverflow.com/questions/52570738/how-to-merge-two-classes-in-separate-files-into-one-es6-module-using-typescript


Downgrade the severity of SoCoFault logging

It seems reasonable to keep the log quiet when users cannot do anything about the situation.

I believe the logging level for this was set in the hope that users might contact us with information about the warning, so we can adjust the parser.

Ah, I didn't realize that. Is this enough information for such an adjustment?
Event contains illegal metadatafor 'enqueued_transport_uri_meta_data'.
Error message: 'Unknown UPnP class: object.container.playlistContainer.tracklist'
The result will be a SoCoFault.

This is when playing via Spotify Direct.

Well, it isn't enough to make an adjustment, but enough to know roughly what we're looking at.
It seems like Spotify has created a PlaylistContainer.tracklist subclass, which isn't included in the Didl-Lite specification. It should probably be treated as a PlaylistContainer, like a .# unofficial subclass.
To be sure, could you please log the value variable in events.py line 154 and post the result here?

Sure:
<DIDL-Lite xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:r="urn:schemas-rinconnetworks-com:metadata-1-0/" xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/">
 <item id="" parentID="-1" restricted="true">
  <dc:title></dc:title>
  <upnp:class>object.container.playlistContainer.tracklist</upnp:class>
  <desc id="cdudn" nameSpace="urn:schemas-rinconnetworks-com:metadata-1-0/">SA_RINCON2311_X_#Svc2311-0-Token</desc>
  <upnp:albumArtURI></upnp:albumArtURI>
  <r:contentService id="9" name="Spotify"/>
 </item>
</DIDL-Lite>

Well, it isn't enough to make an adjustment, but enough to know roughly what we're looking at.
It seems like Spotify has created a PlaylistContainer.tracklist subclass, which isn't included in the Didl-Lite specification. It should probably be treated as a PlaylistContainer, like a .# unofficial subclass.
To be sure, could you please log the value variable in events.py line 154 and post the result here?

Wow, that's some really peculiar metadata. It has an empty item id, negative parent id, empty title and a r:contentService subelement with only attributes (which we always ignore).
It should probably not be treated like a playlistContainer. Instead, we could create a playlistContainerTracklist class for this, or put the playlistContainer.tracklist Didl class on a list of classes to ignore.
What do you think?

Since we do not know how it should be used, it seems okay to ignore it.
This event always follows two object.item.audioItem.musicTrack events that contain the current/next track information.

Closing this in preference of #645.


Provisinonning first with python2 then switching to 3 does not work.

If you first provision a box with python 2 and later on decide to switch to python 3, you will have the following issue :
TASK: [python | make symlink from pip-3.2 to pip] *****************************
failed: [default] => {"failed": true, "gid": 0, "group": "root", "mode": "0755", "owner": "root", "path": "/usr/bin/pip", "size": 281, "src": "/usr/bin/pip-3.2", "state": "file", "uid": 0}
msg: refusing to convert between file and link for /usr/bin/pip

Don't know what the best course of action is in this case, uninstall the other version ? force the symlink ?
@OdyX @sephii  what do you think ?

What about putting the symlink in /usr/local/bin instead? It should have precedence over /usr/bin. This would be less invasive, and afaik we only need that for Ansible's pip module. Another solution would be to skip the symlink creation entirely and explicitly set the executable option when using the pip module, but this would be quite annoying.

It seems "risky" to me to have two different version of pip with the same binary name. Depending on the PATH, this could lead to some strange things.
Also, any script expect pip to be in usr/bin it will raises some nasty issues.
I think I would personally ensure that only the 2 or 3 versions of the package is installed and uninstall the other.

In most cases we need to have both Python 2 and 3 installed in order to use tox, so being able to have only one version of Python would be very limiting.

I am not saying removing python2 entirely, but just the packages that were installed by the role : https://github.com/team-rawbot/rawbot-virtualization/blob/master/provisioning/roles/python/tasks/main.yml#
I think having the pip and virtualenv version for both python2 and python3 will only lead to issues and confusion. Even more if /usr/bin/pip is v2 and /usr/local/bin/pip is v3.
I would say there should be only one pip and one virtualenv at anytime on the system.
BTW, we should also maybe fill a debian bug so that the pip version can be managed via [debian alternatives][https://wiki.debian.org/DebianAlternatives]. wdyt ?

Maybe creating a symlink /usr/bin/pip for pip3 is just not the right way to do it. At the moment we're using the pip module only in the django role, and we could easily set the pip version to use (via the executable parameter of the pip module) to create a Python 2 or Python 3 virtualenv depending on the Python version set in the parameters.
Filing a bug to use alternatives to manage pip would mean doing the same to manage Python and this would be quite a big change I guess.
If you think having pip3 available as pip is that important, I agree that we could just make sure only Python 2 or Python 3 pip is installed and create a symlink if necessary. This would probably be the easiest solution.

After more thinking I don't think tox will be able to create the necessary virtualenv for Python 2 if Python 2's pip is not installed. In my opinion we just shouldn't do anything about it.

This should be fixed by https://github.com/team-rawbot/rawbot-virtualization/commit/facd8deced97fa3d0a178a72e7ea4147b781274d.
Note that when switching to Python 3 your virtualenvs (if any) won't be recreated so you'll have to do destroy them and re-provision.

Also note that the django role won't work on wheezy because of the unavailability of the python3-venv package. Another solution would be to pass the virtualenv_python option when creating the virtualenv but this will unfortunately only be supported starting in Ansible 2.0.
Anyway since wheezy doesn't have Python 3.4 and Django 1.9 will only support Python >= 3.4 I don't think this is much of an issue.

@sephii concerning your commit facd8deced97fa3d0a178a72e7ea4147b781274d , are you sure the installation of python3 venv on Wheezy is correct ?
Since both python2 and python3 are installed, it seems to me that you have to precise the pip executable to use to target python3.
Also, I don't get the issue with Django and Wheezy, are we not installing virtualenv through pip there ?
Maybe talk about that IRL next week ?

There's no Python 3 virtualenv package on Wheezy. So we install the Python 2 package and we can then specify which Python interpreter should be installed in the virtualenv when creating it. We might run a few additional tests to ensure it's working on Wheezy, especially since Ansible's pip module only allows the virtualenv_python parameter to be passed since version 2.0.
As for the issue with Django and Wheezy, the issue is just what I mentioned: we can't use the virtualenv_python option when creating the virtualenv because it's only available in Ansible >= 2.0.
Maybe we could install virtualenv through pip though. Let's discuss that IRL next week.

Closing this as the inital issue was resolved. See #29 for the remaining issue of python3 on Wheezy


ARMv7/armhf support?

This project looks really promising! I see there's only binaries for amd64 and arm64/ARMv8, do you plan to support ARMv7/armhf as well with precompiled binaries? If not, would it be possible to compile from source and use that same binary myself for all ARMv7 devices?

You should be able to download the ARMv6 Go compiler and compile this project from source to run on ARMv7. As far as I know, ARMv6 binaries also work on ARMv7.  Please report back how it goes so that I can refer this issue to other people with a similar use case.

One apparently easily can cross compile on any go installation (no specific installation is needed) using GOOS=linux GOARM=7 GOARCH=arm go build ./cmd/upterm/main.go and the result ./main is executable in an armv7 device.


only do auth check for TiDB (cherry-pick of #2489)

What problem does this PR solve?
This is an cherry-pick of https://github.com/pingcap/tispark/pull/2489
What is changed and how it works?
Only do auth check for tables in TiDB.
We will check the catalog name of operation.
If it doesn't use tidb_catalog, we won't do auth check for it.
This check only work for select and use database
Check List
Tests

Unit test
Integration test

/run-all-tests

/run-all-tests

/merge


Slash in URL Slug causes problems

Describe the bug
I wanted to create the slug edent/supertinyicons - that works.
When I view it, It displays as edent%2Fsupertinyicons - that also works.
When I try to edit it, it breaks, and goes to
https://opencollective.com/edent/supertinyicons/edit
I have to manually edit the URL to
https://opencollective.com/edent%2fsupertinyicons/edit in order to be able to edit the repo.
To Reproduce
Steps to reproduce the behavior:

Go to https://opencollective.com/edent%2Fsupertinyicons?
Click on "Edit collective"
See error

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

Desktop (please complete the following information):

OS: Ubuntu
Browser Firefox
Version 67

Additional context
Add any other context about the problem here.

Thank you for reporting this. We should have been more strict in slug validation and should not have allowed to have a slash in it. I suggest to change your slug.
On our side, we will check the validation to avoid that in the future.

Will do! Cheers :-)

This is a duplicate of https://github.com/opencollective/opencollective/issues/1476, though you've added way more details and helpful context. Thank you for that @edent, I'm closing https://github.com/opencollective/opencollective/issues/1476 in favor of yours.
Also let's keep in mind that this is not only about / character, we need to ensure slug is always alphanum + dash only. An entry in validate for the slug of the Collective model is probably the way to move forward with it.
While doing the change, we have to take a decision about what to do with UTF8 characters for slug: two users have special slugs. Do we want to migrate them, or do we want to support it?

晃羽田
иванк

The query:
SELECT slug FROM "Collectives"
WHERE slug NOT SIMILAR TO '%[a-zA-Z0-9]%'

The majority of the world are more diverse than ASCII 😊
I'd certainly vote to keep UTF-8 - but escape any URL special characters.


Try move auth

This is the PR for the move auth from solid-ui to solid-logic. Start with this module.

@theRealImy could you replace fetcher by _fetch for example

done.