plugin: Move (*AutoscaleEnforcer).checkSchedulerName() outside of locks

I think this was a holdover from when we still had live config reloading, which was removed in #87.
Split off from #653.

I'm not sure how I can make sure we're not causing any problem by moving this out of lock.

Opened #668 to document the existing locking behavior.


Update to go install and module to v2

You can create a patch from my fork here. You didn't fork from yudai/gotty so I can't send a PR with the changes.
https://github.com/ghthor/gotty/commit/9aea12400659d78a070bf1f8a1caff59bcf19f01

I had originally forked from yuday/gotty, but got Github to remove that link. There was too much tooling that assumed that the focus of development was his fork.
I realized that the v2 stuff was a mistake, in part because of the problem you're highlighting. It's just a bad user experience to have to add the /v2/ bit when you're installing and gotty isn't a library. SemVer isn't very important for gotty. Now that 1.4.0 is out, I'm going to try to see if I need to retract any of the v2+ stuff and get this sorted out once and for all.

I left some comments on the linked commit. :)


Assignment of negative values to signals

Attempting to assign a signal to a negative value causes the parser to error. For example, paste the below text into the parser to create this issue
10:
A = -1
=> 10

I just updated the grammar to allow unary minus:
https://github.com/aebabis/factorio-state-machine/commit/30797a208671d2eb71b13584dbdbbdb49313211b
Tested in game and produces negative values. Have a good weekend.


📚 DOCS: Improve buttons documentation

Codecov Report

Merging #5 (9c210b1) into main (95f5d9e) will increase coverage by 6.62%.
The diff coverage is 57.89%.

@@            Coverage Diff             @@
##             main       #5      +/-   ##
==========================================
+ Coverage   74.20%   80.82%   +6.62%
==========================================
  Files          10       10
  Lines         756      772      +16
==========================================
+ Hits          561      624      +63
+ Misses        195      148      -47

Flag
Coverage Δ

pytests
80.82% <57.89%> (+6.62%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sphinx_design/icons.py
72.81% <52.94%> (+12.14%)
:arrow_up:

sphinx_design/badges_buttons.py
89.90% <100.00%> (+37.57%)
:arrow_up:

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 95f5d9e...9c210b1. Read the comment docs.


Use tf.function for model prediction in RasaModel.

Proposed changes:

Use tf.function in RasaModel to improve inference speed.

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

The regression test report failed due to changes in the infrastructure on main. However, comparing the generated report manually with the scheduled run on Metabase showed no significant difference in model performance on the Sara dataset:
BERT + DIET(seq) + ResponseSelector(t2t)

Task
main
this branch

Entities (microF1)
0.79
0.792

Intent (microF1)
0.71
0.714

Responses (accuracy)
0.78
0.78

Sparse + DIET(bow) + ResponseSelector(bow)

Task
main
this branch

Entities (microF1)
0.79
0.795

Intent (microF1)
0.67
0.671

Responses (accuracy)
0.78
0.791


demo error

======== Exception caught by widgets library =======================================================
The following LateError was thrown building MotionTabBar(dirty, dependencies: [Directionality], state: _MotionTabBarState#0dda9):
LateInitializationError: Field 'labels' has not been initialized.

======== Exception caught by widgets library ============
The following LateError was thrown building MotionTabBar(dirty, dependencies: [Directionality], state: _MotionTabBarState#0dda9):
LateInitializationError: Field 'labels' has not been initialized.

@yanashenyang motion_tab_bar: ^2.0.4 released with the fix.


rpcserver+lnrpc: make graph node addresses consistent

This commit adds a []*lnrpc.NodeAddress typed node_addresses field
on the NodeUpdate message of SubscribeChannelGraph to mirror the
addresses field in the LightningNode message of DescribeGraph.
Fixes https://github.com/lightningnetwork/lnd/issues/4084
Pull Request Checklist

[X] If this is your first time contributing, we recommend you read the Code
Contribution Guidelines
[X] All changes are Go version 1.12 compliant
[X] The code being submitted is commented according to Code Documentation and Commenting
[ ] For new code: Code is accompanied by tests which exercise both
the positive and negative (error paths) conditions (if applicable)
[ ] For bug fixes: Code is accompanied by new tests which trigger
the bug being fixed to prevent regressions
[ ] Any new logging statements use an appropriate subsystem and
logging level
[X] Code has been formatted with go fmt
[X] Protobuf files (lnrpc/**/*.proto) have been formatted with
make rpc-format and compiled with make rpc
[ ] New configuration flags have been added to sample-lnd.conf
[X] For code and documentation: lines are wrapped at 80 characters
(the tab character should be counted as 8 characters, not 4, as some IDEs do
per default)
[X] Running make check does not fail any tests
[X] Running go vet does not report any issues
[X] Running make lint does not report any new issues that did not
already exist
[X] All commits build properly and pass tests. Only in exceptional
cases it can be justifiable to violate this condition. In that case, the
reason should be stated in the commit message.
[X] Commits have a logical structure according to Ideal Git Commit Structure

Good nit, fixed, thank you for taking a look


Progress text of BackgroundTaskThreads that raise exception persists

If a BackgroundTaskThread raises an exception, the progress text in the status bar sticks around. Additionally, it does not look like any other BackgroundTaskThread can change the progress text afterwards.

Do you have an example of this?

class MyBackgroundTask(BackgroundTaskThread):
    def run(self):
        for i in range(10, 0, -1):
            self.progress = f"{i}..."
            raise Exception("Test")

You'll see that the progress text sticks around. If you try a different background task after this, the progress text will not change.


alexis/util/struct: lexical context and using define-struct-updaters within another macro

Right now, it seems like the identifiers generated by define-struct-updaters have the lexical context of the outer parens, instead of the struct id or the result of (syntax-local-introduce #'here), or something.
Did you intend that, and if not would it be a good idea to change that to use either the struct id or syntax-local-introduce, and document that so that other macros can compose with it more easily? Or if that was what you meant to do, should you document that anyway?

By the way I'm going by this racket users list thread, and more specifically this, this, and this.

That's a reasonable point. I've changed it to use the lexical context of the struct id in 23141965df8364235ca433f5e894fad14ae6d0c6. Thanks for the report.

Thanks!


Item drop problem with mods

I am currently running

SpongeForge version: 1.12.2-2611-7.1.0-BETA-2925
SpongeVanilla version: No
Java version: 1.8.0_162
Operating System: Windows

Plugins/Mods:
Plugins(6): Minecraft, Minecraft Coder Pack, SpongeAPI, SpongeForge, CmdBuilder, CmdControl
Mods(26): Minecraft, Minecraft Coder Pack, Forge Mod Loader, Minecraft Forge, SpongeAPI, SpongeForge, BetterQuesting, CraftTweaker2, CreativeCore, IronChest, JourneyMap, JEI, LittleTiles, Malisis Advert, Malisis Doors, Malisis Core, Mantle, ModControl, MrCrayFish Furniture Mod, NetherPortalFix, Pixel Extras, Pixelmon, Tinker's Construct

Issue Description
Problem is with item drop. Example: In mod Pixelmon are Berries (example: pixelmon:starf_berry), if you want to collect them, you need to right click on them. Berries just disappear without any drop.
Another example with mod Tinker's Construct and Lumberaxe. When player use lumberaxe (like regular axe, but with ability to cut a whole tree) to cut a tree, tree just disappear without any drop (regular axe works).
I tried to every build from newest to oldest till working one. Last working build for this is 1.12.2-2611-7.1.0-BETA-2916.
Should be not necessary, but here is fml-junk-earlystartup.log: https://gist.github.com/Krosta8/bbf825370bf063f3878b967fa6a7ec1d

wrong repo and a dupe, please use the spongeforge tracker for mod related issues
https://github.com/SpongePowered/SpongeForge/issues/2015


nuxtApp.$i18n.locales has type LocaleObject[] but is ComputedRef<LocaleObject[]>

Environment

Operating System: Darwin
Node Version:     v16.14.0
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      srcDir, modules, i18n, piniaPersistedstate, googleFonts, colorMode, postcss, build, vite
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
// nuxt.config.js

import messages from './src/i18n';

export default defineNuxtConfig({
    i18n: {
        strategy: 'prefix_except_default',
        defaultLocale: 'fr',
        locales: [
            {
                code: 'fr',
                name: 'Français',
                iso: 'fr-CA',
                momentLocale: 'fr-ca',
            },
            {
                code: 'en',
                name: 'English',
                iso: 'en-CA',
                momentLocale: 'en',
            },
        ],
        vueI18n: {
            legacy: false,
            messages,
        },
    },
});

// plugin/moment.js

import moment from 'moment';
import 'moment/dist/locale/fr-ca';
import momentDurationFormatSetup from 'moment-duration-format';

export default defineNuxtPlugin((nuxtApp) => {
    const locale = nuxtApp.$i18n.locale.value;
    const momentLocale = nuxtApp.$i18n.locales.value.find((l) => l.code === locale).momentLocale;
    momentDurationFormatSetup(moment);
    moment.locale(momentLocale);

    nuxtApp.$i18n.onBeforeLanguageSwitch = (oldLocale, newLocale, isInitialSetup, nuxtApp) => {
        const momentLocale = nuxtApp.$i18n.locales.value.find((l) => l.code === newLocale).momentLocale;

        moment.locale(momentLocale);
    };

    return {
        provide: {
            moment,
        },
    };
});

Describe the bug

Parameter 'oldLocale' implicitly has an 'any' type.
Parameter 'newLocale' implicitly has an 'any' type.
Parameter 'isInitialSetup' implicitly has an 'any' type.
Parameter 'nuxtApp' implicitly has an 'any' type.

Property 'code' does not exist on type 'string | LocaleObject'.

Parameter 'l' implicitly has an 'any' type.

Additional context
I see in the source code that the types for onBeforeLanguageSwitch, but they don't seem to be infered correctly in a Nuxt 3 plugin.
I tried adding the types manually on the parmas like so, but nuxtApp type is not found.
nuxtApp.$i18n.onBeforeLanguageSwitch = (oldLocale: string, newLocale: string, isInitialSetup: boolean, nuxtApp: nuxtApp) => {
    const isoLocale = nuxtApp.$i18n.locales.value.find((l) => l.code === newLocale).momentLocale;

    moment.locale(isoLocale);
};

I tried importing it manually, but it also doesn't work.
import type { NuxtApp } from '#imports'

I get this message:

Module '"#imports"' has no exported member 'NuxtApp'.

Logs
No response

I partially solved the problem, the type NuxtApp is on #app, not #imports.

Now I have 2 new errors:
For this code:
    nuxtApp.$i18n.onBeforeLanguageSwitch = (oldLocale: string, newLocale: string, isInitialSetup: boolean, nuxtApp: NuxtApp) => {
        const momentLocale = nuxtApp.$i18n.locales.value.find((l: LocaleObject) => l.code === newLocale).momentLocale;

        moment.locale(momentLocale);
    };

I have this error:

Property 'value' does not exist on type 'string[] | LocaleObject[]'. Did you mean 'values'?
Property 'value' does not exist on type 'string[]'.

For this code:
const nextLocale = computed(() => {
  const index = locales.value.findIndex((l: LocaleObject) => l.code === locale.value);
  const nextIndex = index !== locales.value.length - 1 ? index + 1 : 0;

  return (locales.value.at(nextIndex) as LocaleObject).code;
});

I have:

Argument of type '(l: LocaleObject) => boolean' is not assignable to parameter of type '((value: string, index: number, obj: string[]) => unknown) & ((value: LocaleObject, index: number, obj: LocaleObject[]) => unknown)'.
Type '(l: LocaleObject) => boolean' is not assignable to type '(value: string, index: number, obj: string[]) => unknown'.

Ok, I also fixed the second issue in my previous message.
I had to define the type correctly:
 const index = (locales.value as LocaleObject[]).findIndex((l) => l.code === locale.value);
instead of:
const index = locales.value.findIndex((l: LocaleObject) => l.code === locale.value);.
So there is only the first error left, which seems like a bug while the other were me just being a TypeScript noob I guess.

My last idea was to change the type to as ComputedRef<LocaleObject[]>, but I get

Conversion of type 'string[] | LocaleObject[]' to type 'ComputedRef<LocaleObject[]>' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
Type 'LocaleObject[]' is missing the following properties from type 'ComputedRef<LocaleObject[]>': value, [ComputedRefSymbol], effect, [RefSymbol]
So I will just use as any for now as everything is working.

    nuxtApp.$i18n.onBeforeLanguageSwitch = (
        oldLocale: string,
        newLocale: string,
        isInitialSetup: boolean,
        nuxtApp: NuxtApp,
    ) => {
        const locales = (nuxtApp.$i18n.locales as ComputedRef<LocaleObject[]>).value
        const momentLocale = locales.find((l: LocaleObject) => l.code === newLocale)?.momentLocale;

        moment.locale(momentLocale);
    };
    ```

Hi, thanks for opening an issue on this repository. Sharing your updates as you work through this issue is really appreciated, and type definitions will be looked into ASAP!

No problem, I can also open a new clean issue without all the noise if necessary.
It seems like a very minor problem., but for someone new to Vue3/Nuxt3/TypeScript, I was at a lost haha.

This seem fixed in @nuxtjs/i18n-edge, but not 100% sure.
If I do const locales = nuxtApp.$i18n.locales.value;, it thinks locales is string[] | LocaleObject[].
So I did const locales = (nuxtApp.$i18n.locales as ComputedRef).value; and now it works in Edge.
It is not working in "@nuxtjs/i18n": "^8.0.0-beta.7" as it says the 2 types do not overlaps.
Now I see the new type is (string[] | LocaleObject[]) & ComputedRef<string[] | LocaleObject[]>


Object Detection and OpenCV

Hi,
I am following through the tutorial of object detection. I have installed opencv and am able to import cv2 when I run it on Python script, but it errors when DIGITS's python trying to import it.
What's requirements about opencv? Or what other things would you recommend checking?
Traceback (most recent call last):
File "/home/ai2-c3p0/Documents/code/nv_caffe/python/caffe/layers/detectnet/clustering.py", line 3, in
import cv2 as cv
ImportError: /home/ai2-c3p0/anaconda2/lib/python2.7/site-packages/cv2.so: undefined symbol: _ZN2cv11arrowedLineERNS_3MatENS_6Point_IiEES3_RKNS_7Scalar_IdEEiiid
Thanks,

Hi @suhalim9 I think there is a mismatch on your system between the version of OpenCV that was used to build Caffe and the version of OpenCV that was used for installing OpenCV Python bindings. You might be able to reproduce this error if you do:
$ export PYTHONPATH=/path/to/caffe/python
$ python
>>> import caffe
>>> import cv2

If I'm correct then the solution is to install the version of the OpenCV Python bindings that matches the version you used to build Caffe.


[RAINCATCH-942] Updates to contributing guide

Motivation
Supply additional information the the contribution guide in the documentation website via per-repository files.
Description

Move CONTRIBUTING.md to the top level
Move CODE_OF_CONDUCT.md to the top level
Add link from main README
Update bits of information (gitter chat room, etc.)

Changes Unknown when pulling 43ef10ece0918f66538bd335beb8635e586aeab2 on RAINCATCH-942-contributing into ** on master**.

Changes Unknown when pulling 43ef10ece0918f66538bd335beb8635e586aeab2 on RAINCATCH-942-contributing into ** on master**.

@paolobueno we hold all files in .github folder to not populate global scope. Why this change?

@wtrocki I thought moving CONTRIBUTING (and now CODE_OF_CONDUCT) to the root would give those files better visibility. Nevertheless linking them from the main readme is also important. The same reasoning can be seen here for example
Rebased and moved code of conduct file.

Changes Unknown when pulling 126442c89039c14240d127820cb6a1ad6098a740 on RAINCATCH-942-contributing into ** on master**.

Changes Unknown when pulling 126442c89039c14240d127820cb6a1ad6098a740 on RAINCATCH-942-contributing into ** on master**.


SD Card image

Can you provide your SD card image again, the image file is invalid！ Baidu network disk or Google drive is OK

Hello, you can download the image file here: https://1drv.ms/u/s!Av71xxzl6mYZgdZxDoxDnxR-sOERSw?e=S2o1uR


Remove intermediate ngram vector

The code was repeatedly copying part of the pattern into std::vector. We can avoid these copies by taking a view (pointer and length) on the pattern.

@guillaumekln Have you checked that the output on a large translation memory is the same ?

Yes, I verified the same matches are returned for 10k sentences when using a large index (> 2GB).


fixes #29, fixes #31, and fixes #34

uses literature update from 8-8-19 (with abstracts) to test functionality

whoops! I had datetime in there for another thing. -removing.
and good call on window.destroy, I'll just incorporate it directly.

I ran it. It has no parentheses

Clarification, it breaks with parentheses.


Playwright error: no filters were found

Describe the bug
When switching from selenium to playwright, all checks get the error:
Warning, no filters were found, no change detection ran - Did the page change layout? update your Visual Filter if necessary.
Version
0.45.1
To Reproduce
Steps to reproduce the behavior:
1:
Use the following docker-compose:
version: '3.2'
services:
    changedetection:
      image: ghcr.io/dgtlmoon/changedetection.io
      container_name: changedetection
      hostname: changedetection
      network_mode: host
      environment:
        - PORT=5001
        - PLAYWRIGHT_DRIVER_URL=ws://<IP_ADDRESS>:3000/?stealth=1&--disable-web-security=true
#        - WEBDRIVER_URL=http://<IP_ADDRESS>:4444/wd/hub
      volumes:
        - changedetection-data:/datastore
      restart: unless-stopped
      depends_on:
#        browser-chrome:
#          condition: service_started
        playwright-chrome:
          condition: service_started

    playwright-chrome:
      hostname: playwright-chrome
      image: browserless/chrome
      network_mode: host
      restart: unless-stopped
      environment:
        - SCREEN_WIDTH=1920
        - SCREEN_HEIGHT=1024
        - SCREEN_DEPTH=16
        - ENABLE_DEBUGGER=false
        - PREBOOT_CHROME=true
        - CONNECTION_TIMEOUT=300000
        - MAX_CONCURRENT_SESSIONS=10
        - CHROME_REFRESH_TIME=600000
#        - DEFAULT_BLOCK_ADS=true
        - DEFAULT_STEALTH=true

#    browser-chrome:
#      hostname: browser-chrome
#      image: selenium/standalone-chrome-debug:3.141.59
#      network_mode: host
#      environment:
#        - VNC_NO_PASSWORD=1
#        - SCREEN_WIDTH=1920
#        - SCREEN_HEIGHT=1080
#        - SCREEN_DEPTH=24
#      volumes:
#          - /dev/shm:/dev/shm
#      restart: unless-stopped

volumes:
  changedetection-data:

Set up the following monitor:
https://changedetection.io/share/d0qlVgD8rgsa

In global "Fetch Method" have wait seconds set to 20.
Expected behavior
To have the monitor run, and successfully get the CSS Selector's value.
Desktop (please complete the following information):

OS: Ubuntu Server 22.04.3
Browser: Firefox

more than likely playwright couldnt get the page for some reason ,check the logs, maybe some JS didnt run or other


[incubator/kube-downscaler] - Add priorityClassName and update image tag

Signed-off-by: Lord-Y<EMAIL_ADDRESS>Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Hey @Lord-Y , thank you for this PR! 👍
Could you please only add the priorityClassName in the podspec if it's defined? Something like:
    {{- if .Values.priorityClassName }}
      priorityClassName: "{{ .Values.priorityClassName }}"
    {{- end }}

It seems to be the preferred way to do it across other charts, and is explicit about only adding this line when needed!

Hey @Lord-Y , thank you for this PR! 👍
Could you please only add the priorityClassName in the podspec if it's defined? Something like:
    {{- if .Values.priorityClassName }}
      priorityClassName: "{{ .Values.priorityClassName }}"
    {{- end }}

It seems to be the preferred way to do it across other charts, and is explicit about only adding this line when needed!

@Pluies I updated the deployment accordingly.

/lgtm


Create unit tests for broad phase

[ ] Check that spatial hashing method calculate averageMaxBodiesSize.
[ ] Check that broad phase method calucalte AABB.
[ ] Check result of all public method.


[Designer] Add i18n support to designer

Description
Add i18n support to designer. Not complete yet (was going through files alphabetically and stopped at designer-peers.ts).
@dclaux - before I got too far, I wanted to see what you thought about this approach. I think I want to restructure the translation file a bit, but haven't done that yet. Also, I know that this isn't the framework we talked about, but i18n isn't suited for browser apps.
Microsoft Reviewers: Open in CodeFlow

I've been thinking more about this, and my conviction is that the designer should not take a direct dependency on i18n nor any other external localization library for that matter. I strongly believe the designer, as a component, should:

Continue to provide default, out of the box strings (the English strings we already have) without the developer having to do anything including hosting a file
But at the same time also provide a way for host applications to plug in their preferred localization system

Overall I'm OK with the resource JSON as you have it even though neither the string identifiers nor the parameters are discoverable via IntelliSense. I think it's acceptable in the name of flexibility.
I think we should have a version of that JSON built into our code, and we should have our own built-in logic to read string values from it. Converting a dotted path (say "newCard.dialog.title") into a field accessor isn't difficult, nor is the logic for simple parameter substitution like "{{action}}" (we already do it in the renderer for DATE and TIME functions.)
Beyond that, we can allow a host application to provide its own "localization provider" so they can use their preferred system or the one they already use for the rest of their app.
So I suggest we do something along these lines:
export var strings = {
	"cardElements": "CARD ELEMENTS",
	"cardEditor": "CARD PAYLOAD EDITOR",
	"cardPreview": "Card Preview",
	"sampleEditor": "SAMPLE DATA EDITOR",
	"sampleData": "Sample data",
	"elementProperties": "ELEMENT PROPERTIES",
	"ellipsis": "...",
        etc.
};

export abstract class LocalizationProvider {
    abstract localize(identifier: string, parameters: object): string;
}

export var localizationProvider?: LocalizationProvider;

export function localizeString(identifier: string, parameters: object): string {
    // If the host app has defined a custom localization provider, use it
    if (localizationProvider) {
        return localizationProvider.localize(identifier, parameters);
    }

    // Otherwise, use our built-in localization
    return <run our own logic to read the value from the global strings variable>;
}

The designer package would not have any dependency on i18n (not even external). The designer code would call localizeString exclusively:
new containers.WebChatContainer(localizeString("hostContainer.names.webChat"), "containers/webchat-container.css"),

For the site, if you deem it practical, you'd simply implement an i18n provider:
class i18nProvider extends LocalizationProvider {
    localize(identifier: string, parameters: object): string {
        return __(identifier, parameters);
    }
}

localizationProvider = new i18nProvider();

Only the site code would have a dependency on i18n.
What do you think?

Bump to reset staleness

@paulcam206 - is this PR still desired or should it be closed?

this should probably be resurrected in the near future, but the PR can be closed for now


How long is analytics data stored for in storage?

How long is analytics data stored for in storage?
The page states a maximum of 730 days
Raw data points (that is, items that you can query in Analytics and inspect in Search) are kept for up to 730 days. You can select a retention duration of 30, 60, 90, 120, 180, 270, 365, 550 or 730 days. If you need to keep data longer than 730 days, you can use Continuous Export to copy it to a storage account during data ingestion.
https://docs.microsoft.com/en-us/azure/azure-monitor/app/data-retention-privacy#how-long-is-the-data-kept
The below page contradicts the above page and states that logs can be retained in the storage account indefinitely
After the categories have been selected, in the Retention days field, type in the number of days of retention you need of your log data. By default, this value is 0, which means that logs are retained in the storage account indefinitely
https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/quickstart-azure-monitor-route-logs-to-storage-account#archive-logs-to-an-azure-storage-account
Which is correct please?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c4cb6c8f-80a5-3a49-3cc1-e194e5b98b16
Version Independent ID: ef9c64e5-466d-9be2-df6a-39de8c76b1ad
Content: Data retention and storage in Azure Application Insights - Azure Monitor
Content Source: articles/azure-monitor/app/data-retention-privacy.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @AaronMaxwell
Microsoft Alias: aaronmax

@jayinoz99 , thank you for your feedback. We'll review this and get back to you shortly!

@jayinoz99, Please note the links are for different settings/data retention.
Link 1 is for retention period detail of Log Analytics workspace, where Azure Monitor stores the logs.
Link 2 is for archival of logs to Storage account from Archive Azure AD logs (this is not the same as Log Analytics workspace).
Hope this clarifies the information. Please let me know if you have any questions.

@jayinoz99, We will now proceed to close this thread as we have not heard back from you. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.

Thanks very much for looking in to this, much appreciated
On Thursday, 30 June 2022 at 07:50:59 BST, Anurag Singh @.***> wrote:
@jayinoz99, We will now proceed to close this thread as we have not heard back from you. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


The mod No LoD, that disables the Level of Detail models for Sonic and Shadow no longer works.

Keep getting errors even after I reinstalled SA2.


Car Bomb

text: If an "action ends (uncusessfully)" this is ruled as äquivalent to "the action fails" therefore Ruling #2 does not apply here, as this is about actions that simply "end", see kiss of ra.
link: https://www.vekn.net/forum/rules-questions/79389-when-does-nra-apply-not-apply?start=6#103563

The ruling has to do with NRA, not with the ability of playing further modifiers or not. AFAIK the ruling on ended actions still stands. Feel free to ask a confirmation/infirmation on the forum.

My bad (cf. ANK 20221205 & ANK 20220118). Fixed now


await Fade_in/out() makes the addon ignore any parameters

Using Godot v4.2.1.stable.official.b09f793f5.
Fade.fade_in(1, Color.WHITE, "Diagonal"), for example, works fine on its own. The problem comes when you add await Fade.fade_in().finished on the next line. It immediately defaults to, well, the default parameters when you add it.
https://github.com/KoBeWi/Godot-Universal-Fade/assets/110701935/b933e933-f8f2-45dc-a1c8-450090b9a3f9
The same applies to Fade.fade_out() of course.
It sucks, the only workaround I can think of for it is to have a oneshot timer that starts alongside the Fade, and emits a timer_stopped signal around the same time as it ends, but I don't want to keep doing that when I use this addon a lot.

Your code is wrong, it should be await Fade.fade_in(1, Color.WHITE, "Diagonal").finished without the second line.

AH my mistake, thanks!


feature/kakao-map : Add KakaoMap component

Add KakaoMap component.

I moved the componentDidmount and removed empty lines


Font color mixing with background

What did you expect to happen?
Just installed Doom Emacs on Mac OS 12.2:
Right after starting emacs I should be able to see the main starting page with the DOOM logo.
What actually happened?
Instead of seeing the logo, it appears that the font color is mixing with the background. Only when the text is highlighted with the cursor appears visible. Even when typing (e.g. Spc-. ) to find a file, text is blind.
However, it works perfect with other terminal emulators

Describe your attempts to resolve the issue
Toggled themes between doom-one, doom-one-light, etc.... no change.
Doom Emacs seems to work well on the native Terminal for Mac OS

.
Steps to reproduce

Open any terminal Emulator
run "emacs"

System Information
https://pastebin.com/v1iCwDzV

This occurs because alacritty supports 24-bit color, but Emacs has only partial 24-bit support without some help. Visit this guide for details on how to fix it.
As this is a terminal issue, rather than Doom or Emacs, I will close this, but feel free to follow up here.

FYI, a super quick solution is to just to modify alacritty.yml file to the following elements:
env:
     TERM: alacritty-direct
This will enable 24-bit color support.


Use purescript-media-types

@garyb made purescript-media-types yesterday. I guess the plan is that purescript-affjax would use it at some point. If it's :+1: I can make a PR.

I'd like to break out the methods, headers, and status codes too, so perhaps we should do them all at once.
I'm not sure what the breakdown of these things should be though, maybe all 3 of those just need to go into a new library rather than being split any further?

Should we also try and use this library for halogen? (media types are used in the html stuff)

Doing them all at once would be of course better.
I guess it won't hurt to have extra granularity, but at the moment I can't come up with a good use case where you would need only one of those modules.

@jonsterling :+1:
@zudov I'll sort something out tonight.

I believe this was addressed in https://github.com/slamdata/purescript-affjax/commit/86e85687f8184bcb07c201e21569793e825a9978