Trying to update via Toolbox, not working

Hi,
Tryin g to update this tool via XRM Toolbox, but it just stubbornly won't update. I've even downloaded the zip directly. Still shows as needing an update in the library. Am I missing something?

Hi,
I have noticed this issue 2 days back, I will try to resolve it ASAP

@aboodh95, the issue is still there. Could you just push a new Nuget package with the same version as the assembly so that it fixes it.

@MscrmTools I have updated the version and pushed the new one, now it showing as not installed

@aboodh95 Your assembly is not under a Plugins folder in your Nuget package...

@MscrmTools Can you check it now, i made it in the Plugins folder, but now it's not getting the latest version in Tool Library

I will check on Monday


docs: add missing composer.json in Mandatory File Changes

Description
If a user installed CI4 manually, and installed a Composer package,
Composer package Kint 4.x is installed and used.
And it is not compatible with the updated Config file for Kint 5.x.
See https://github.com/codeigniter4/framework/commit/f83c211996d1bbe5e76ce9af5e71f900bfba1c32#diff-d2ab9925cad7eac58e0ff4cc0d251a937ecf49e4b6bf57f8b95aab76648a9d34
Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[x] User guide updated
[] Conforms to style guide

Removing "kint-php/kint" is not enough.
Because after removing it if we run composer update,
"post-update-cmd" will remove Kint in system/ThirdParty/.
--- a/composer.json
+++ b/composer.json
@@ -9,7 +9,6 @@
         "ext-intl": "*",
         "ext-json": "*",
         "ext-mbstring": "*",
-        "kint-php/kint": "^4.2",
         "laminas/laminas-escaper": "^2.9",
         "psr/log": "^1.1"
     },
@@ -51,9 +50,6 @@
         ]
     },
     "scripts": {
-        "post-update-cmd": [
-            "CodeIgniter\\ComposerScripts::postUpdate"
-        ],
         "test": "phpunit"
     },
     "support": {


[FLINK-34565] Enhance flink kubernetes configMap to accommodate additional configuration files

What is the purpose of the change
The purpose of this change is to empower users to effortlessly add additional files to the Flink ConfigMap, essential for running jobs in app mode on Kubernetes. Currently, the Flink Kubernetes client supports only a fixed set of files (flink-conf.yaml, logback-console.xml, log4j-console.properties) in the ConfigMap for JobManager and TaskManager Pods. However, in certain scenarios, users may need to include extra configuration files, such as user-defined job properties. Without this change, users are forced to employ workarounds, like manually creating and mounting ConfigMaps or Secrets, to incorporate dynamic configuration files into the JobManager and TaskManager Pods.
In my case, I aim to include log4j-cli.properties (for running specific Flink commands on each pod) and hive-site.xml (for metastore). A similar use case was discussed on the user mailing list: link to the mailing list thread
Brief change log
The method FlinkConfMountDecorator#getLocalLogConfFiles() provides a fixed set of files that need to be included in the ConfigMap. I have modified this method to incorporate an additional set of files, which is configured through the new property 'kubernetes.flink.configmap.additional.resources'. This property allows users to specify a semicolon-separated list of local files in the client Flink config directory that should be included in the Flink ConfigMap.
Verifying this change
This change added tests and can be verified as follows:

Added FlinkConfMountDecoratorTest#testConfigMapAdditionalResource() which will create two dummy extra files and configure the same files in 'kubernetes.flink.configmap.additional.resources'.
The test will verify if flinkConfMountDecorator is able to get the additional files as part of the ConfigMap or not.
The case when this property is not configured is already covered by an existing test case.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@gyfora , can you please review .

@surendralilhore , could you please fill out the pull-request template properly and provide a practical example that would highlight the need for such a feature?
And also show how this feature would help with that practical problem.

Thanks @gyfora.
I have updated PR template. Added detailed description.

Hi @zhuzhurk,
Please can you review this PR.


[material-ui] Refine extendTheme and CssVarsProvider API

closes #42887, closes #41070
📖 docs: Basic usage and Advanced config
Motivation
The experimental API was lacking some of the behaviors

It provides both light and dark modes by default. This is not a good behavior for apps with only light or dark mode. The way it should be is to start with light by default and let users configure params based on their usage.
It's not possible to use a class selector #42887
It's not possible to use @media prefers-color-scheme
The API to customize the selector is too hard to understand without documentation

Changes
Start with light by default
When using CssVarsProvider without a custom theme, the behavior is the same as ThemeProvider except that the theme CSS variables are generated.
See docs.
Switch to dark application
const theme = extendTheme({ defaultColorScheme: 'dark' });

<CssVarsProvider theme={theme}>

Light and Dark with CSS rule
To enable dark mode, set cssRule with media or string that represents CSS selector, e.g. .mode-%s or [data-mode-%s]

The basic usage shows the media option.
The custom selector is in advanced configuration.

Enabling system preference
The new enableSystem prop for CssVarsProvider will change the mode based on user preference. Inspired by next-theme
color-scheme
Css color-scheme is enable by default to use the right scheme based on the generated style-sheet, user can disable it with:
extendTheme({
  disableCssColorScheme: true,
})

Removed APIs
 <CssVarsProvider
-  defaultMode="..." // replaced by `defaultColorScheme` in the extendTheme
-  colorSchemeSelector="…" // replaced by `cssRule` in the extendTheme
/>

[x] I have followed (at least) the PR section of the contributing guide.

If I want only dark mode, I should use defaultColorScheme: 'dark'. This is confusing because "default" implies that there's another, non-default color scheme.

Thanks for the review, may be let's start with the simplest use case, only one color scheme.
Are you agree that by calling extendTheme() without parameters, the built-in light color scheme will be provided?
Next, what parameters do you expect the provide to the extendTheme(…) so that it returns only the dark color scheme? I am thinking of this instead of defaultColorScheme: 'dark':
extendTheme({
  colorSchemes: { dark: true }, // `light` will not be created.
})

Finally, do you think CssVarsProvider should have a default theme (using extendTheme()) or the theme prop is required?
// a: CssVarsProvider will create a default theme using `extendTheme()`
<CssVarsProvider>

// b. User need to always call `extendTheme(…)`
const theme = extendTheme() // params is optional
<CssVarsProvider theme={theme}>

Another use case, opt-in to light and dark color schemes:
With the above proposal, it will look like this if I want to use built-in light and dark color schemes:
extendTheme({ light: true, dark: true });

and if the user wants to override the default tokens, they do this:
extendTheme({ light: { palette: { primary: { main: '#ff5252' } }}, dark: true });

Are you agree that by calling extendTheme() without parameters, the only built-in light color scheme will be provided?

Yes, no problem with that 👍🏼

Do you think CssVarsProvider should have a default theme (using extendTheme()) or the theme prop is required?

No hard preference. If I had to choose one I would go with having a default theme as that's what users are used to.
Proposed API
This is the proposed API for the use cases you mention
interface ExtendThemeParameters {
    /**
     * Array indicating the available color schemes:
     *
     * @examples
     * - ['dark'] for dark only
     * - ['light', 'dark'] for both
     *
     * @default ['light']
     */
    colorSchemes: ('light' | 'dark')[],
    /**
     * Object indicating the color scheme overrides.
     * It has two top-level keys: 'light' and 'dark'
     *
     * @examples
     * { light: { palette: { primary: { main: '#ff5252' } }} }
     *
     */
    colorSchemeOverrides: {
        light: {
            // ...
        },
        dark: {
            // ...
        },
    },
    /**
     * String indicating the color scheme selector
     *
     * @examples
     * - '.mode-%s' for a class selector
     * - '[data-mode-%s]' for a data selector
     * - 'media' to use prefers-color-scheme
     *
     * @default '.mui-mode-%s'
     */
    colorSchemeSelector: string,
}

This is the proposed API for the use cases you mention

I agree with colorSchemeSelector 👍.
But for colorSchemes and colorSchemeOverrides, I think it should be just one field that user concern. In case of a custom color scheme, user has to provide 2 places:
extendTheme({
  colorSchemes: ['light', 'dark', 'comfort'],
  colorSchemeOverrides: {
    comfort: { … } // 'comfort' is a new color scheme, not an override
  }
})

I think this could be simpler with just colorSchemes field.
extendTheme({
  colorSchemes: {
    light: true,
    dark: true,
    comfort: { … }
  },
})

Less character to type, one field to understand and result is still the same.

Next discussion, how to change between color schemes.
Default method

Manually setting the color scheme should be enabled by default and users can opt-out by using

I don't agree with this, I think the simplest method ('media') should be the default because user can achieve light & dark modes without creating a toggle button and deal with SSR.
I found that TailwindCSS also uses 'media' as the default.
Media method
I think there is nothing to be discussed for media because it's already explicit that the result will be @media (prefers-color-scheme).
Manual method
I think enableSystem prop can be removed to clear the confusion. If you set colorSchemeSelector to class or data-attribute, the system preference should be enabled by default.
I think there is no need to add disableSystem prop to opt-out because if you want to force a specific part of the app to be light or dark, adding the color scheme selector to the element is a lot easier.

But for colorSchemes and colorSchemeOverrides, I think it should be one field that user should concern. In case of a custom color scheme, user has to provide 2 places:

Ok 👍🏼 that makes sense

I don't agree with this, I think the simplest method ('media') should be the default because user can achieve light & dark modes without creating a toggle button and dealing with SSR.
I found that TailwindCSS also uses 'media' as the default.

Ok as well 🙌🏼

I think enableSystem prop can be removed to clear the confusion. If you set colorSchemeSelector to class or data-attribute, the system preference should be enabled by default.

Agreed

Some follow-up questions:

in colorSchemes, the light and dark objects will contain tokens that are only related to color? Or are there other tokens?
If the user needs to manually set the colors scheme, then system would be the fallback, right? In other words, if they don't set the color scheme via useColorScheme's setMode, we'll use system?
What do you think about adding a utility to enable manual toggling without setting the selector? We could call it enableManualColorScheme which is false by default. I think there are a lot of people that would want to toggle it manually but don't care about the selector, for which we could have a default '.mui-mode-%s'.

in colorSchemes, the light and dark objects will contain tokens that are only related to color? Or are there other tokens?

Not just colors, the built-in tokens contain overlays in dark but nothing in light (for Paper component). User can add anything to each color scheme (they have to manage the type with module augmentation).
extendTheme({
  colorSchemes: {
    light: {
      palette: {
        randomNode: {
          …
        }
      }
    }
  }
})

If the user needs to manually set the colors scheme, then system would be the fallback, right? In other words, if they don't set the color scheme via useColorScheme's setMode, we'll use system?

Yes, I think that should be the default behavior.

What do you think about adding a utility to enable manual toggling without setting the selector? We could call it enableManualColorScheme which is false by default. I think there are a lot of people that would want to toggle it manually but don't care about the selector, for which we could have a default '.mui-mode-%s'.

This reminds me of Tailwind CSS config where you use selector instead of media.
Instead of adding new enableManualColorScheme, should we add more value to colorSchemeSelector: 'class'?

Not just colors, the built-in tokens contain overlays in dark but nothing in light (for Paper component). User can add anything to each color scheme (they have to manage the type with module augmentation).

I was asking because colorSchemes implies that the tokens are only color related. themes might be a more appropriate key if there's tokens that are not color related. What do you think?

Since enableManualColorScheme is doing the same thing as colorSchemeSelector, how about supporting more value, e.g. class to colorSchemeSelector?

That makes sense, so the possible values for colorSchemeSelector would be

"media" (default)
"class"
"selector"
string for overriding it, i.e. ".mode-%s" or "[data-mode-%s]"

so the possible values for colorSchemeSelector would be

"class" is obvious but what do you expect to be for "selector"? if it's a data-attribute, may be "data" is better?

"class" is obvious but what do you expect to be for "selector"? if it's a data-attribute, may be "data" is better?

Yes, "data" would be better. I'll let you decide if it's necessary or not. "class" might be enough.

"class" is obvious but what do you expect to be for "selector"? if it's a data-attribute, may be "data" is better?

Yes, "data" would be better. I'll let you decide if it's necessary or not, "class" might be enough.

Thanks, I'll go with data as well.
The PR is ready for another review.


Trusting whitelist breaks a unit test

9ddcf54b1d991aeb9b2a41850eecab9aafcceda5 breaks
WMComponent_t/JobSubmitter_t/JobSubmitter_t.py:JobSubmitterTest.testD_WhiteListBlackList
Will investigate.

Part of #5743

Was wrong. Commit is 031bdcb488b405b7e17ae4de1d84868dc0c7c217 it seems.

@hufnagel can you take a look at the unit test WMComponent_t/JobSubmitter_t/JobSubmitter_t.py:JobSubmitterTest.testD_WhiteListBlackList which is broken by the above PR. I can't tell if this is intentional, but what's happening is that at https://github.com/dmwm/WMCore/blob/master/test/python/WMComponent_t/JobSubmitter_t/JobSubmitter_t.py#L701 submitting jobs with a whitelist of T2_US_Namibia does not automatically fail those jobs.

I guess this test was either removed or turned into another test, since I can no longer find it in the JobSubmitter test class. Closing it.


Adding calibration and registration tools to examples.

Fixes
Description of the changes:

Adding python code leveraging OpenCV to calibrate any given camera.
Adding python code to perform registration (extrinsics) between two cameras, also reports registration error.
Adding example data for users.
Adding a README.md to describe how to use the tools
Adding three different Charuco templates for users, with example data using the mid size one.
Output a json with calibration and registration data between cameras.

Before submitting a Pull Request:

[x] I reviewed CONTRIBUTING.md
[x] I built my changes locally
[x] I ran the unit tests
[x] I ran the functional tests with a device
[x] I ran the performance tests with a device

I tested changes on:

[x] Windows
[x] Linux

hi, great to see this, a much needed function!
I wonder what's the accuracy like? Is the calibrated parameters close to the factory calibration?

hi, great to see this, a much needed function!
I wonder what's the accuracy like? Is the calibrated parameters close to the factory calibration?

@seigeweapon The accuracy of the calibration from this tool is as good, if not better than the factory calibration. You can use this tool to calibrate a device, and then use the tools in the examples/depth_eval_tools folder to evaluate the calibration quality for the depth sensor.

hi, great to see this, a much needed function!
I wonder what's the accuracy like? Is the calibrated parameters close to the factory calibration?

Yes, this calibration is as good as factory.

/azp run


[Bug]: Subnormals resulted from decimal operations should be treated as ZERO

Description
The decimal operations result in subnormal values should return the decimal value zero according to the IEEE 754-2008 ANSI X3.274.
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Related front-end issue https://github.com/ballerina-platform/ballerina-lang/issues/33879


Fix get message notification

This fixes issues when getting notification message details. Two main issues fixed: 1) OBEX Body does not have null ending and 2) BT socket stream reader and writer reinitialization during request.

The notification problem stills exist, tested on Android and iPhone.
Opcode: GetAlter
Req packet sent. Waiting for reply...1

Stuck on waiting reply.

I will merge this PR anyway since the base branch have been changed to xtremehpx/refactor-map-demo.

Future commits should be push to xtremehpx/refactor-map-demo branch

The notification problem stills exist, tested on Android and iPhone.
Opcode: GetAlter
Req packet sent. Waiting for reply...1

Stuck on waiting reply.

You are correct, the problem remains. I tried again and here was the reason I thought problem was fixed early. The first time running the code, I have step-by-step debug enabled, specially I set a break point at ReadFromStream. I only need to enable the debug for the first incoming message, and then getting the rest of the incoming messages are fine. I feel like the MNS service needs to be in a standalone service app.
Body: <?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<MAP-event-report version="1.0"><event type="NewMessage" handle="95F86559724B7A3" folder="telecom/msg/inbox" msg_type="SMS_GSM"/></MAP-event-report>
Sending GetMessage request
Sending request packet: 1
ConnectionId: 19-60-46-30
Opcode: GetAlter
Req packet sent. Waiting for reply...1
ResponseCode: Success
Message received: test get message from notification 2

Opcode: PutAlter
Type: 78-2D-62-74-2F-4D-41-50-2D-65-76-65-6E-74-2D-72-65-70-6F-72-74-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
ApplicationParameters: 0F-01-00
MASInstanceID: 00
EndOfBody: ***
Body: <?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<MAP-event-report version="1.0"><event type="NewMessage" handle="F294197EE62A05C" folder="telecom/msg/inbox" msg_type="SMS_GSM"/></MAP-event-report>
Sending GetMessage request
Sending request packet: 1
ConnectionId: 19-60-46-30
Opcode: GetAlter
Req packet sent. Waiting for reply...1
ResponseCode: Success
Message received: test get message from notification 3

Opcode: PutAlter
Type: 78-2D-62-74-2F-4D-41-50-2D-65-76-65-6E-74-2D-72-65-70-6F-72-74-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
ApplicationParameters: 0F-01-00
MASInstanceID: 00
EndOfBody: ***
Body: <?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<MAP-event-report version="1.0"><event type="NewMessage" handle="B008F57D7A4E298" folder="telecom/msg/inbox" msg_type="SMS_GSM"/></MAP-event-report>
Sending GetMessage request
Sending request packet: 1
ConnectionId: 19-60-46-30
Opcode: GetAlter
Req packet sent. Waiting for reply...1
ResponseCode: Success
Message received: test get message from notification 4


Items not showing lootbeam when spawning.

I have Seaweed spores in my highlight list so I notice where they are when they spawn, at one point in the near past it stopped showing the lootbeam when they spawn in. Only When they spawn, if i drop them the lootbeam is still present.
When I drop them:

When they spawn in:

Duplicate of #11601


test interaction of makeskin and MPFB

assignAsNodesMaterialForObj()  number of arguments changed (uses scene, object and a load flag instead of object, because of scene all parameters attached as custom properties to scene are no longer needed)
I simply did not know that MPFB also uses the functionality :(
... I will create an own branch of MPFB and hope I get the thing working soon ...
(I took an issue to communicate maybe because I have no idea to answer another way), hope it is okay

I changed code for MPFB a tiny bit, on my box it works ... I also tried a merge request for punkduck-devel but it looks like when I press the button it is already merged. So since you want them fitting all together best do all three merges then. I don't want to produce chaos ;)

Ok, things work for me too now, when I have punkduck_devel checked out in all plugins locally.
So I'll merge everything now.


Move operator subfolder to the root folder of the repository

The module-manager operator resides inside an operator subfolder at the moment. Since this abstraction is not required we can get rid of the operator folder and offer the operator (with the library in pkg/) in the root folder.
AC:

[x] module-manager/operator/ -> module-manager/
[x] Adjust pipelines in test-infra
[ ] Update the CLI

Waiting for the: https://github.com/kyma-project/module-manager/issues/174

tech writer review missing on cli... has to be merged on Monday


Successful event load, but can not see in calendar

using php7, and download from 3-31.
$data = date('2013-03-22 08:00');
$data1 = date('2013-03-22 09:00');
echo  " ".date('Y m d H:i:s',strtotime($data));
//exit;
$out[] = array(
 	'id' => 777,
	'title' => 'Test 1',
	'url' => 'example.com',
	'class' => 'event-important',
	'start' => strtotime($data).'000',
	'end' => strtotime($data1).'000'
);

returns:
Time=1490968161 2013 03 22 08:00:00{"success":1,"result":[{"id":777,"title":"TEST ","url":"example.com","class":"event-important","start":"1363939200000","end":"1363942800000"}]}
I can verity the unix timestamp to 3-22-3013 where the other events are, but I am unble to locate it on the calendar for 3-22 or any other event. Does the above look ok ?

Thanks for the tip. I will work it that way...
Cheers,
Wynn
On Mon, Feb 26, 2018 at 10:59 AM, OwenCalzadilla<EMAIL_ADDRESS>wrote:

Have you tried making 'start' and 'end' date numeric instead of strings,
all seems right except that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Serhioromano/bootstrap-calendar/issues/713#issuecomment-368571403,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANMTwXMCSGPg0xS3iA3DTSdt6JYca8Kiks5tYuLhgaJpZM4Mvsnw
.


[SP-2531][PDI-14653] - Using export option with kitchen.sh

fixed current directory resolving when resources exporting
added unit/integration tests

@akhayrutdinov @brosander review please. It's a backport of #2249.

@pamval, @pedrofvteixeira, run WM for this PR please

wingman

similar to #2249, tests pass, code styling is acceptable -- merged


[WIP] add backends doc page

Ref #3011
This is a WIP PR - I will be rebasing it as I go
Anyone watching, feel free to comment/commit/PR-to-this-branch additional lines/details
This is handy: https://www.tablesgenerator.com/markdown_tables

Nice.  This page is long overdue.
I might split up client and server, as we could start to talk about more attributes for each.  Things like client proxy support, HTTP/2 support, constraints required. #3276 is already starting this process.  I'm afraid the table would get too wide if we cram client and server together.

@rossabaker Merge, I'd say. I don't have a ton of time to keep going, and having something will make it easier for the community to perform drive-by contributions

All of this is true in 0.21, so I'm going to do the cherry-pick dance.

Cherry-picked. And I learned how to add co-authors in magit! :tada:

Things like :white_check_mark: look nice on the GitHub markdown, but they're not rendered on the actual site:
https://http4s.org/v1.0/integrations/
Also, my understanding was that Blaze was non-blocking?


albert's ppp

Codecov Report
Base: 61.87% // Head: 61.87% // No change to project coverage :thumbsup:

Coverage data is based on head (8ea16b9) compared to base (b6aa24d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #219   +/-   ##
=========================================
  Coverage     61.87%   61.87%
  Complexity      637      637
=========================================
  Files           112      112
  Lines          2371     2371
  Branches        314      314
=========================================
  Hits           1467     1467
  Misses          775      775
  Partials        129      129

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


com.alipay.remoting.DefaultConnectionManager.scan throws NPE

Describe the bug
throws a NPE when DefaultConnectionManage.scan
Actual behavior
2023-05-29 18:03:28,746 ERROR [RpcTaskScanner$1#58] [RpcTaskScannerThread-2-thread-1] Exception caught when scannings.
java.lang.NullPointerException: null
at com.alipay.remoting.DefaultConnectionManager.scan(DefaultConnectionManager.java:443)
at com.alipay.remoting.rpc.RpcTaskScanner$1.run(RpcTaskScanner.java:56)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
Steps to reproduce
暂不知道如何复现
Minimal yet complete reproducer code (or GitHub URL to code)

Environment

SOFARPC version: 5.7.7
JVM version (e.g. java -version): openjdk version "1.8.0_332"
OS version (e.g. uname -a): Debian GNU/Linux 11

I write the following code to indicate that the iterator pattern is not thread safe:
 public static void testConcurrent(){
        ConcurrentHashMap<String, String> map = new ConcurrentHashMap<>();
        map.put("a","b");
        Iterator<String> iterator = map.keySet().iterator();
        if (iterator.hasNext()) {
            map.remove("a");
            String next = iterator.next();
            System.out.println(map.get(next));// it prints null
        }

    }

More measures need to be taken to ensure thread safety. I will fix it in sofa-bolt project.

Please upgrade SOAFRPC version or  bolt version. This bug is fix at https://github.com/sofastack/sofa-bolt/pull/230 . Bolt version should greater than 1.6.1.

I write the following code to indicate that the iterator pattern is not thread safe:
 public static void testConcurrent(){
        ConcurrentHashMap<String, String> map = new ConcurrentHashMap<>();
        map.put("a","b");
        Iterator<String> iterator = map.keySet().iterator();
        if (iterator.hasNext()) {
            map.remove("a");
            String next = iterator.next();
            System.out.println(map.get(next));// it prints null
        }

    }

More measures need to be taken to ensure thread safety. I will fix it in sofa-bolt project.

I will take a look at it. BTW, are you using SOFA-RPC community version in production environment ?

Yes, is there anything special I should pay attention to?

Okay, we'll do the upgrade, Thanks!

If so , you can sign your company name in https://github.com/sofastack/sofa-rpc/issues/375 .


SideCar black screen on my iPad Pro 2020 12.9

Configuration

HaC Mini version : 2.7
OSX version : 10.15.4
NUC model : NUC8i7HNK
Boot SSD model and protocol: Samsung SSD 970 EVO Plus 1TB
Second SSD model and protocol: INTEL SSD PEKKW 512G8
First DIMM model: DDR4-2666 16GB
Second DIMM model (if installed):
Display port(s) used :HDMI
Display resolution(s) :4K

config.docx

I just updated the latest vision of Hac-Mini, the SideCar finally works now!
Really appreciated!!


validation for verify status

[x] created new route called /get-qrcode-device-info?user_id = {user_id}
[x] functions related to that which is filtering according to the authorization status
[x] Test

Raised a different PR https://github.com/Real-Dev-Squad/website-backend/pull/1400


Chicken being detected wrongly

In the hunter job i was doing some testing.
Jobs is recognising Chicken as RAW_CHICKEN:
      Chicken:
        income: 4.0
        points: 4.0
        experience: 5.0

to test this check out the action page or use the ingame editor to edit the hunter job. You can clearly see raw chicken. This could explain why killing chickens doesn't pay in the hunter job.

6fd856a5132c5622a3fb7acbe68c243662f44d8b


[FALSE-POSITIVE] cs-portalintranet.com

Domains or links
https://cs-portalintranet.com/
More Information
How did you discover your web site or domain was listed here?
Incorrectly marked as Phishing on virustotal.
Have you requested removal from other sources?
We've requested removals from a handful of other providers, but they don't provide links / references to the removal request.
Additional context
Please can you remove the cs-portalintranet.com site from your block list. This site is associated with the CybSafe PHISH product, which is a security training and awareness tool designed to simulate phishing scenarios for the purpose of training individuals to recognise and respond appropriately to phishing threats. We’d greatly appreciate it if you could remove it from your lists. If you require more information, then please feel free to get in touch with us by replying here or emailing support AT cybsafe.com.


UnsupportedOperationException when use getPlayer in PaginatedViewSlotContext

Is there an existing issue for this?

[X] I have searched the existing issues

🐛 Describe the bug
When you try to use getPlayer in PaginatedViewSlotContext it throws a UnsupportedOperationException
✔ Expected behavior
It should return the player who opened the view
👣 Steps to Reproduce

💻 Platform

[X] Bukkit
[ ] Sponge
[ ] Other

⭐ Versions
MC 1.8.9, IF 2.5.2
✍ Additional context
No response

@kauepalota Being worked on #183. You download the new possibly fixed artifact from Generate Artifacts workflow (scroll down) or try out 5bfb11ad26 library version.


Duplicate user zooniverse_id

I found this when I was reviewing things from the Ouroboros side.
Some of the id's are from duplicate/deleted users, or from nearly identical records

zooniverse_id
count

1025
2

115818
2

1231718
2

1248842
2

1276473
2

1315964
2

1360717
2

1391611
2

1426357
2

1456050
2

1460880
2

1518287
2

1598703
2

163171
2

1645120
2

1670968
2

1728590
2

1743021
2

1749392
2

1760425
2

1761957
2

1767800
2

1772665
2

1777646
2

1781498
2

1860940
2

1868986
2

1877364
2

1892085
2

1907911
2

1911330
2

1915361
2

1919491
2

1926316
2

1927350
2

1937794
2

1938898
2

1951678
2

1954550
2

1967214
2

222152
2

234900
2

316034
2

328994
2

37827
2

420431
2

50638
2

5309
2

59339
2

640813
2

642714
2

843140
2

849936
2

878282
2

Which db was this in? Panoptes prod?

Production

Thanks - these look like deleted users that we then re-imported, will clean them up.

I have cleaned all these up.


feat: Test (#000)

Pull Request Template
Description
Please include a summary of the change and why it is needed.
Fixes # (issue)
Type of change

[ ] 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 not work as expected)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Pull Request contain one commit. I squash my commits

Screenshots (if appropriate):
Additional context
Add any other context or screenshots about the feature request here.

/recheck


Command line option to control whether the bar is at the top or bottom?

Currently hard-coded and changed often while debugging.

Hello! Maybe a future user of this lib (:
I'd be interested in this as well.
Also: the readme does not mention the cli you're talking about in this issue, what does the cli do? Simply run the bar? Or does it have other features?

This issue refers to the bin/cnx.rs that's included in this repository, which is intended as an example and something used for testing. An argument to toggle the position would be useful for this, as I often set it to Top in the code when testing (whereas my 'real' bar is on the bottom), but then forget and accidentally commit my change.
There's no configurable CLI for this program. The intent is that you depend on cnx as a library, and then create your own CLI, similar to how it's done in bin/cnx.rs.
Please be aware that the code in master is currently unreleased, so doesn't work on Linux at the moment. The version on crates.io should be useable.

Oh okay that makes more sense, thanks!

master is currently unreleased, so doesn't work on Linux at the moment

Thanks for the info, what does not work for Linux? (maybe create a separate issue for this?)

I've re-written a number of widgets in the master branch to use APIs available only on OpenBSD. I need to boot back into Linux in order to add Linux support back to them before I can release the next version. If you stick with the 0.2 version on crates.io, this shouldn't be a problem.


LXD keeps adding NICs and breaking

Required information

Distribution: Ubuntu
Distribution version: Xenial

config:
core.https_address: <IP_ADDRESS>:8443
core.proxy_ignore_hosts: <IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,2001:41d0:800:74d::,::1,localhost
core.trust_password: true
api_extensions:

storage_zfs_remove_snapshots
container_host_shutdown_timeout
container_stop_priority
container_syscall_filtering
auth_pki
container_last_used_at
etag
patch
usb_devices
https_allowed_credentials
image_compression_algorithm
directory_manipulation
container_cpu_time
storage_zfs_use_refquota
storage_lvm_mount_options
network
profile_usedby
container_push
container_exec_recording
certificate_update
container_exec_signal_handling
gpu_devices
container_image_properties
migration_progress
id_map
network_firewall_filtering
network_routes
storage
file_delete
file_append
network_dhcp_expiry
storage_lvm_vg_rename
storage_lvm_thinpool_rename
network_vlan
image_create_aliases
container_stateless_copy
container_only_migration
storage_zfs_clone_copy
unix_device_rename
storage_lvm_use_thinpool
storage_rsync_bwlimit
network_vxlan_interface
storage_btrfs_mount_options
entity_description
image_force_refresh
storage_lvm_lv_resizing
id_map_base
file_symlinks
container_push_target
network_vlan_physical
storage_images_delete
container_edit_metadata
container_snapshot_stateful_migration
storage_driver_ceph
storage_ceph_user_name
resource_limits
storage_volatile_initial_source
storage_ceph_force_osd_reuse
storage_block_filesystem_btrfs
resources
kernel_limits
storage_api_volume_rename
macaroon_authentication
network_sriov
console
restrict_devlxd
migration_pre_copy
infiniband
maas_network
devlxd_events
proxy
network_dhcp_gateway
file_get_symlink
network_leases
unix_device_hotplug
storage_api_local_volume_handling
operation_description
clustering
event_lifecycle
storage_api_remote_volume_handling
nvidia_runtime
container_mount_propagation
container_backup
devlxd_images
container_local_cross_pool_handling
proxy_unix
proxy_udp
clustering_join
proxy_tcp_udp_multi_port_handling
network_state
proxy_unix_dac_properties
container_protection_delete
unix_priv_drop
pprof_http
proxy_haproxy_protocol
network_hwaddr
proxy_nat
network_nat_order
container_full
candid_authentication
backup_compression
candid_config
nvidia_runtime_config
storage_api_volume_snapshots
storage_unmapped
projects
candid_config_key
network_vxlan_ttl
container_incremental_copy
usb_optional_vendorid
snapshot_scheduling
container_copy_project
clustering_server_address
clustering_image_replication
container_protection_shift
snapshot_expiry
container_backup_override_pool
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
tls
environment:
addresses:

<IP_ADDRESS>:8443
architectures:
x86_64
i686
certificate: |
-----BEGIN CERTIFICATE-----
MIIFYjCCA0qgAwIBAgIRAN6QvwI5HJiB5oQ41Ka72/owDQYJKoZIhvcNAQELBQAw
NzEcMBoGA1UEChMTbGludXhjb250YWluZXJzLm9yZzEXMBUGA1UEAwwOcm9vdEBy
ZXNlYXJjaDEwHhcNMTgwNjIxMTA1NjIzWhcNMjgwNjE4MTA1NjIzWjA3MRwwGgYD
VQQKExNsaW51eGNvbnRhaW5lcnMub3JnMRcwFQYDVQQDDA5yb290QHJlc2VhcmNo
MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALp3MTnuEB0C6RaAfvl0
EDlr1G1cEs1QtHCp84Fx7wQdRCAzaRd+mLSN9ncW9Swzaamh/W7NSMqGjDBfQmDA
d2bb3AK99wtD1/NHGycyw4/RWCs56LoCKivZP65VO35W5CONe5zni6XYwzyNtY2c
nJRY8Q23gZzan9vUpWPe8pKLubzmDu/Sf4M9z8jYYq2cFXUHGdy7pKc40iTWbJy/
jAhT3c7QFEduUWpzT7arVGa239X+YsBwnbRZt4gGsWcEmOpOTMSXVUFGANXfab1C
YQ5CD+WevDZgm8+e7YGr80iWIhoofQdZmKmjCgjsIICwdf/JpOsAYEsY60Us3RK2
cBulppcw7+NloDNy3klLR5voASefc1Obq6hC9NQo9XW2g+VK2FXFlvFDXAtX7x/5
IDvSV8KnefXH4tNDSnT96OdvZC1LwxiOMgy0Nw9t4N1cGldLWec2qJqwYb7D4N+T
rQohn3EJB1Q8jY1UShAeOoRKxvocaS3kdDVDbaYYuScsjugwWy/+rFDzWVf7fJcj
oyf5ze6ItUP2F50QLda41inevZsmEh730Bl9zzRlzzWi3cM43XK/wZGFAlaunKlK
N411JSOW0QxTaHaCjQpp+5Mk038JoEUOyOmajoD+4mEmKRH5Mc0oBnZb7ROp0ABF
P+o1/ZC8Oc6ac5GvAaAU2ZBXAgMBAAGjaTBnMA4GA1UdDwEB/wQEAwIFoDATBgNV
HSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMDIGA1UdEQQrMCmCCXJlc2Vh
cmNoMYcEke/9gocQIAFB0AgABIIAAAAAAAAAAIcECgAAAjANBgkqhkiG9w0BAQsF
AAOCAgEAn/+Zz7ALPkcLEYP6IWU53YVoWKHZEQnrfEQKqFWwGJK3jFUcLt/zGmGp
c3QMBv8kaCaM3R4jEFodwBWPRpHdUnwfx7ZH8f3tq6SyqWAXfZWx3WytsYlW3mar
+VvAjVlODRQS9NzbhMQ5XH0jyCqmy0G/Cc55AqSZFgEPQmpsA43hJjYx0HhJPYq6
HmRDzVf1NTnToAaWB19kr+k+ZavrcorCts+q8OcLbY26AVNi8fhUCSzolVnnCCNU
Uz1gCpKgSLGgv6eK4MrUQiisK7B+bZH+eE1qODW6gJleIgw71rOSLwFUg+aJqzIp
sZ+B5wby7FpG7AYwJHaxetpg2Pmmy//V2+k2V+8WQOkrl1caCUFp8S04h5Q4ttLE
PdEJlQAlgPoAOsb0UjGK3iz3HE7MjFSErcgAcRyElo6onkXaP/UgEd2EMmOTsJwT
JreBYKZG3g/OcBLzap8/bdXaYnb4/KM+BBWkSVyQLSauf8s3Jt0HyzjIyVzVfeiF
hxyybJum9GVT3SNThUYmojftekMcFXZEUkoPWScci8+oU9DZZP1xBGXVwvga/UCO
8avzL+fCCSTHdnz2oELWrmktWE0q2voheJ+ZiDUCHXQsQh2U0Ud/3biT3LxSQH1m
VT/0zUGDS3+HlGbxo3tPB42v/sTJgbWzRiX9vB4XTED7sHgVtkc=
-----END CERTIFICATE-----
certificate_fingerprint: 576ffd08268d33f35e39f3b5fa31e1c66a5fb249017e7a9f3e304ab7f6111334
driver: lxc
driver_version: 3.1.0
kernel: Linux
kernel_architecture: x86_64
kernel_version: 4.15.0-23-lowlatency
server: lxd
server_pid: 1470
server_version: "3.10"
storage: dir | zfs | ceph
storage_version: 1 | 0.7.5-1ubuntu15 | ceph version 10.2.11 (e4b061b47f07f583c92a050d9e84b1813a35671e)
server_clustered: false
server_name: research1
project: default

Issue description
I have no idea how to reproduce this but for the last couple of days my standalone LXD snap install keeps adding (slowly) 99 nics to the default profile, then everything stops running cause it has no nic space left....
Yesterday a snap refresh stopped it for a while, now its back.

Can you show that default profile?
lxc profile show default

I wiped the nics out a few minutes ago so they're currently in the growth phase. But there are no containers running....
config:
  environment.http_proxy: ""
  user.network_mode: ""
description: Default LXD profile
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth1:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth2:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth3:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth4:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth5:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth6:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth7:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth8:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth9:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth10:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth11:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth12:
    nictype: bridged
    parent: lxdbr0
    type: nic
  eth13:
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
name: default
used_by:
- /1.0/containers/nexus2
- /1.0/containers/meteoritewww
- /1.0/containers/saikucommunitywww
- /1.0/containers/juju-33b9f4-0-lxd-11
- /1.0/containers/juju-33b9f4-0-lxd-7
- /1.0/containers/juju-33b9f4-0-lxd-8
- /1.0/containers/juju-33b9f4-0-lxd-9
- /1.0/containers/norwichdata
- /1.0/containers/norwichb2b
- /1.0/containers/saiku4
- /1.0/containers/importexport
- /1.0/containers/moodle
- /1.0/containers/iesnextcloud
- /1.0/containers/jupyter
- /1.0/containers/license4jcontainer
- /1.0/containers/spiculedocs
- /1.0/containers/drilltest2
- /1.0/containers/licenseserver
- /1.0/containers/spiculewww
- /1.0/containers/jupyter2

Can you run lxc monitor and wait until you see the events causing a profile update?

LXD doesn't really do things like that, in general, it's not capable of generating new devices on its own, so I'm pretty sure Juju or another API client is messing with you here. That lxc monitor output should confirm it.

Hmm I don't know how to grok this so here's a big dump:
`
metadata:
action: container-updated
source: /1.0/containers/jupyter2
timestamp: "2019-02-14T00:45:15.598506458Z"
type: lifecycle
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:15.683505621Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:15.68466765Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:15.685685276Z"
type: logging
metadata:
context:
ip: '@'
method: PUT
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:15.686664587Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:18.701380448Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:18.706190457Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0/profiles/default
level: dbug
message: handling
timestamp: "2019-02-14T00:45:18.710085764Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0/networks/lxdbr0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:18.716863252Z"
type: logging
metadata:
context:
ip: '@'
method: PUT
url: /1.0/profiles/default
level: dbug
message: handling
timestamp: "2019-02-14T00:45:18.733144758Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/nexus2
timestamp: "2019-02-14T00:45:19.003229198Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/meteoritewww
timestamp: "2019-02-14T00:45:19.19287542Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/saikucommunitywww
timestamp: "2019-02-14T00:45:19.442781997Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth6e4d9b95 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:19.586502947Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth2bdbcf9e has been added: updating network priorities'
timestamp: "2019-02-14T00:45:19.660729589Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-11
timestamp: "2019-02-14T00:45:19.689277041Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth9b2ae182 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:19.829002309Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth5c34d6fb has been added: updating network priorities'
timestamp: "2019-02-14T00:45:19.903962761Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-7
timestamp: "2019-02-14T00:45:19.961660502Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth946138a4 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:20.179565634Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth07266ca8 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:20.26474727Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-8
timestamp: "2019-02-14T00:45:20.29200353Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: vethd33b41c8 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:20.43423039Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: vethb9b5ddb6 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:20.515193603Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-9
timestamp: "2019-02-14T00:45:20.569956486Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/norwichdata
timestamp: "2019-02-14T00:45:20.859651418Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/norwichb2b
timestamp: "2019-02-14T00:45:21.042099346Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/saiku4
timestamp: "2019-02-14T00:45:21.223171649Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/importexport
timestamp: "2019-02-14T00:45:21.786723718Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/moodle
timestamp: "2019-02-14T00:45:22.047631461Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/iesnextcloud
timestamp: "2019-02-14T00:45:22.242061098Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/jupyter
timestamp: "2019-02-14T00:45:22.434167782Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/license4jcontainer
timestamp: "2019-02-14T00:45:22.692521199Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: Checking if RBD storage volume for container "spiculedocs" on storage pool
"lxd-pool1" is ready
timestamp: "2019-02-14T00:45:22.851357699Z"
type: logging
metadata:
context: {}
level: dbug
message: RBD storage volume for container "spiculedocs" on storage pool "lxd-pool1"
is ready
timestamp: "2019-02-14T00:45:22.906703022Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/spiculedocs
timestamp: "2019-02-14T00:45:22.906864676Z"
type: lifecycle
metadata:
context:
name: spiculedocs
rootfs: /var/snap/lxd/common/lxd/containers/spiculedocs/rootfs
level: warn
message: Unable to update backup.yaml at this time
timestamp: "2019-02-14T00:45:22.906840035Z"
type: logging
metadata:
context: {}
level: dbug
message: Checking if RBD storage volume for container "drilltest2" on storage pool
"lxd-pool1" is ready
timestamp: "2019-02-14T00:45:23.126419807Z"
type: logging
metadata:
context: {}
level: dbug
message: RBD storage volume for container "drilltest2" on storage pool "lxd-pool1"
is ready
timestamp: "2019-02-14T00:45:23.184124606Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/drilltest2
timestamp: "2019-02-14T00:45:23.184308832Z"
type: lifecycle
metadata:
context:
name: drilltest2
rootfs: /var/snap/lxd/common/lxd/containers/drilltest2/rootfs
level: warn
message: Unable to update backup.yaml at this time
timestamp: "2019-02-14T00:45:23.184289364Z"
type: logging
metadata:
context: {}
level: dbug
message: Checking if RBD storage volume for container "licenseserver" on storage
pool "lxd-pool1" is ready
timestamp: "2019-02-14T00:45:23.326439099Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:23.379510465Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0/profiles/default
level: dbug
message: handling
timestamp: "2019-02-14T00:45:23.382215362Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/licenseserver
timestamp: "2019-02-14T00:45:23.397211009Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: RBD storage volume for container "licenseserver" on storage pool "lxd-pool1"
is ready
timestamp: "2019-02-14T00:45:23.397136982Z"
type: logging
metadata:
context:
name: licenseserver
rootfs: /var/snap/lxd/common/lxd/containers/licenseserver/rootfs
level: warn
message: Unable to update backup.yaml at this time
timestamp: "2019-02-14T00:45:23.397203696Z"
type: logging
metadata:
context: {}
level: dbug
message: Checking if RBD storage volume for container "spiculewww" on storage pool
"lxd-pool1" is ready
timestamp: "2019-02-14T00:45:23.523692339Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/spiculewww
timestamp: "2019-02-14T00:45:23.583395315Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: RBD storage volume for container "spiculewww" on storage pool "lxd-pool1"
is ready
timestamp: "2019-02-14T00:45:23.583233033Z"
type: logging
metadata:
context:
name: spiculewww
rootfs: /var/snap/lxd/common/lxd/containers/spiculewww/rootfs
level: warn
message: Unable to update backup.yaml at this time
timestamp: "2019-02-14T00:45:23.58337547Z"
type: logging
metadata:
context: {}
level: dbug
message: Checking if RBD storage volume for container "jupyter2" on storage pool
"lxd-pool1" is ready
timestamp: "2019-02-14T00:45:23.727586169Z"
type: logging
metadata:
context: {}
level: dbug
message: RBD storage volume for container "jupyter2" on storage pool "lxd-pool1"
is ready
timestamp: "2019-02-14T00:45:23.781761336Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/jupyter2
timestamp: "2019-02-14T00:45:23.789495383Z"
type: lifecycle
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:23.875536075Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:23.876735721Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:23.877691544Z"
type: logging
metadata:
context:
ip: '@'
method: PUT
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:23.878662989Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:26.893459245Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:26.897971249Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0/profiles/default
level: dbug
message: handling
timestamp: "2019-02-14T00:45:26.901842394Z"
type: logging
metadata:
context:
ip: '@'
method: GET
url: /1.0/networks/lxdbr0
level: dbug
message: handling
timestamp: "2019-02-14T00:45:26.908719529Z"
type: logging
metadata:
context:
ip: '@'
method: PUT
url: /1.0/profiles/default
level: dbug
message: handling
timestamp: "2019-02-14T00:45:26.925162259Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/nexus2
timestamp: "2019-02-14T00:45:27.176160968Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/meteoritewww
timestamp: "2019-02-14T00:45:27.350606048Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/saikucommunitywww
timestamp: "2019-02-14T00:45:27.541954163Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth9c8e4576 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:27.687705896Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth652f7d66 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:27.760522358Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-11
timestamp: "2019-02-14T00:45:27.81779346Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: vethdccfb051 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:27.9521453Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth7cb4b290 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:27.982935711Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-7
timestamp: "2019-02-14T00:45:28.052380964Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth45933786 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:28.186538104Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth88d9d2fc has been added: updating network priorities'
timestamp: "2019-02-14T00:45:28.217195621Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-8
timestamp: "2019-02-14T00:45:28.275396518Z"
type: lifecycle
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth0947b6a2 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:28.420835876Z"
type: logging
metadata:
context: {}
level: dbug
message: 'Scheduler: network: veth60902674 has been added: updating network priorities'
timestamp: "2019-02-14T00:45:28.493968842Z"
type: logging
metadata:
action: container-updated
source: /1.0/containers/juju-33b9f4-0-lxd-9
timestamp: "2019-02-14T00:45:28.52292199Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/norwichdata
timestamp: "2019-02-14T00:45:28.709852177Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/norwichb2b
timestamp: "2019-02-14T00:45:28.951418611Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/saiku4
timestamp: "2019-02-14T00:45:29.173290753Z"
type: lifecycle
metadata:
action: container-updated
source: /1.0/containers/importexport
timestamp: "2019-02-14T00:45:29.375418158Z"
type: lifecycle
`

metadata:
  context:
    ip: '@'
    method: PUT
    url: /1.0/profiles/default
  level: dbug
  message: handling
timestamp: "2019-02-14T00:45:26.925162259Z"
type: logging

This shows an API query coming over the UNIX socket to update the default profile, quickly followed by all your containers getting updated due to a new NIC being added.
So you have something on your system which is asking LXD to do that.

Thats amazing! Literally all this box does is run a few LXD containers, some of which are connected to Juju, some aren't... how bizarre.

Yeah, my money is currently on Juju, I'm grabbing their code to see if they have logic which would create such devices. LXD doesn't have a logic that would cause an increasing ethXX device name so that's clearly something external doing that.

And bingo, those device names match those generated by generateNICDeviceName in ./container/lxd/network.go in the Juju codebase.
Closing as this is a Juju issue, LXD is doing as it's told.

Ah ha... does look juju related:
machine-0: 01:09:00 WARNING juju.provisioner not stopping machine agent container watcher due to error: setting up container dependencies on host machine: running lxd init --auto: : exec: "lxd": executable file not found in $PATH
machine-0: 01:09:00 ERROR juju.provisioner starting container provisioner for lxd: setting up container dependencies on host machine: running lxd init --auto: : exec: "lxd": executable file not found in $PATH
machine-0: 01:09:04 INFO juju.provisioner initial container setup with ids: [0/lxd/8 0/lxd/9 0/lxd/11 0/lxd/7]
machine-0: 01:09:04 INFO juju.container.lxd LXD snap is installed; skipping package installation
machine-0: 01:09:09 WARNING juju.provisioner not stopping machine agent container watcher due to error: setting up container dependencies on host machine: running lxd init --auto: : exec: "lxd": executable file not found in $PATH
machine-0: 01:09:09 ERROR juju.provisioner starting container provisioner for lxd: setting up container dependencies on host machine: running lxd init --auto: : exec: "lxd": executable file not found in $PATH
machine-0: 01:08:07 INFO juju.provisioner initial container setup with ids: [0/lxd/8 0/lxd/9 0/lxd/11 0/lxd/7]
machine-0: 01:08:07 INFO juju.container.lxd LXD snap is installed; skipping package installation

Yet
root@research1:~# which lxd
/snap/bin/lxd
anyway major hack:
root@research1:~# ln -s /snap/bin/lxd /usr/bin/ :)

Sounds like Juju is running in an environment where /snap/bin isn't in PATH


if video has uploader-added-subtitle, subtitle extractor will fail

$ youtube-dl http://tvple.com/208230 --write-sub
[tvple] 208230: Downloading webpage
[tvple] playurl_208230: Downloading webpage
[tvple] clouds_xml: Downloading webpage
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/bin/youtube-dl/__main__.py", line 19, in <module>
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 410, in main
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 400, in _real_main
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1666, in download
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 661, in extract_info
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 290, in extract
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/tvple.py", line 96, in _real_extract
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 1318, in extract_subtitles
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/tvple.py", line 67, in _get_subtitles
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/tvple.py", line 59, in _convert_sub
AttributeError: 'NoneType' object has no attribute 'group'

$ youtube-dl http://tvple.com/208230
[tvple] 208230: Downloading webpage
[tvple] playurl_208230: Downloading webpage
[download] Destination: 소환사 협곡의 개새끼-208230.mp4
[download] 100% of 6.74MiB in 00:00

sample cloud xml file
newcloud.txt

fixed!
f4a7e38


Why does my program will be blocked when I use dsl_pipeline_component_remove to remove one source?

@popcornGit my apologies for the late response. Can you please provide me with more information.

Jetson or dGPU?
Deepstream version?
How many sources are you using?
When the program blocks, is it on the first call to component-remove, or is it when removing the last source?
Is the main-loop running when you remove the source?

Please provide a full log-file of the scenario. Please enable logging with
export GST_DEBUG=1,DSL:4

and direct the logs to a file with the following
export GST_DEBUG_FILE=./dsl.log

Thanks


User Settings Specs

Issue #63

A reference to the authentication specs should be added for the change password, change two-factor auth, etc use cases.

This is being worked on by killasnake0

@killasnake0: How's this coming along?

I'm taking this over.


Epoll: handling of EPOLLHUP and EPOLLERR (and maybe other more obscure flags)

The most obvious requirement of handling EPOLLHUP and EPOLLERR comes from unix pipes: when the sender is closed, the receiver gets an EPOLLHUP (and only EPOLLHUP); when the receiver is closed, the sender gets an EPOLLOUT | EPOLLERR. (See this helpful list of OS event details: https://github.com/tokio-rs/mio/pull/1091#issuecomment-535598561.) Currently there's no way to detect the former situation (see the example below, this program simply gets stuck) and no easy way to detect the later either (because we want to be notified of only EPOLLERR).
So at least, I think EPOLLHUP should be considered readable.
But it's not clear to me how to handle EPOLLERR (or other more obscure flags, like EPOLLPRI). One way of handling EPOLLERR is marking the event both readable and writable. This is often quite useful, because any further IO operating on the fd would probably return the error. For (sender) pipes specifically, this allows detecting receiver closed events by waiting in read_with (This should work, but I have not verified it myself). But maybe we should provide a more flexible API that is capable of handling more obscure flags as well, e.g. EPOLLPRI.
// [dependencies]
// futures = "0.3.5"
// smol = { path = "../smol" }
// anyhow = "1.0.31"
// nix = "0.17.0"

use smol::Async;
use std::{time::Duration, io};
use futures::prelude::*;

fn main() -> anyhow::Result<()> {
    smol::run(async {
        smol::Task::local(async {
            let (pr, pw) = nix::unistd::pipe()?;
            let mut pr = Async::new(PipeFd::new(pr))?;
            let pw = Async::new(PipeFd::new(pw))?;
            std::thread::spawn(move || {
                std::thread::sleep(Duration::from_secs(1));
                drop(pw);
            });
            let mut buf = vec![0u8; 32];
            pr.read(&mut buf).await?;
            Ok(())
        }).await
    })
}

struct PipeFd {
    fd: i32,
}

impl io::Read for PipeFd {
    fn read(&mut self, buf: &mut [u8]) -> io::Result<usize> {
        nix::unistd::read(self.fd, buf).map_err(|e| {
            match e {
                nix::Error::Sys(e) => e.into(),
                e => io::Error::new(io::ErrorKind::Other, e),
            }
        })
    }
}

impl io::Write for PipeFd {
    fn write(&mut self, buf: &[u8]) -> io::Result<usize> {
        nix::unistd::write(self.fd, buf).map_err(|e| {
            match e {
                nix::Error::Sys(e) => e.into(),
                e => io::Error::new(io::ErrorKind::Other, e),
            }
        })
    }

    fn flush(&mut self) -> io::Result<()> {
        Ok(())
    }
}

impl PipeFd {
    fn new(fd: i32) -> PipeFd {
        PipeFd {
            fd
        }
    }
}

impl Drop for PipeFd {
    fn drop(&mut self) {
        let _ = nix::unistd::close(self.fd);
    }
}

impl std::os::unix::io::AsRawFd for PipeFd {
    fn as_raw_fd(&self) -> i32 {
        self.fd
    }
}

By the way, I have fixed the wepoll-binding not returning event flags issue: https://gitlab.com/yorickpeterse/wepoll-binding/-/merge_requests/3

For (sender) pipes specifically, this allows detecting receiver closed events by waiting in read_with (This should work, but I have not verified it myself).

So I tried this with #134. Calling write with an empty slice returns Ok even after the receiver is closed. Then I figured, I can poll for POLLERR in read_with. (It's quite interesting, using non-blocking poll inside an epoll event loop.)
use smol::Async;
use std::os::unix::io::AsRawFd;
use std::{io, time::Duration};

fn main() -> anyhow::Result<()> {
    smol::run(async {
        smol::Task::local(async {
            let (pr, pw) = nix::unistd::pipe()?;
            let pr = Async::new(PipeFd::new(pr))?;
            let mut pw = Async::new(PipeFd::new(pw))?;
            std::thread::spawn(move || {
                std::thread::sleep(Duration::from_secs(5));
                drop(pr);
            });
            pw.read_with_mut(|pw| {
                let mut poll_fds = [nix::poll::PollFd::new(
                    pw.as_raw_fd(),
                    nix::poll::PollFlags::POLLERR,
                )];
                if nix::poll::poll(&mut poll_fds, 0).map_err(|e| match e {
                    nix::Error::Sys(e) => e.into(),
                    e => io::Error::new(io::ErrorKind::Other, e),
                })? > 0
                    && poll_fds[0]
                        .revents()
                        .unwrap_or_else(nix::poll::PollFlags::empty)
                        .contains(nix::poll::PollFlags::POLLERR)
                {
                    Ok(())
                } else {
                    Err(io::ErrorKind::WouldBlock.into())
                }
            })
            .await?;
            Ok(())
        })
        .await
    })
}

struct PipeFd {
    fd: i32,
}

impl io::Read for PipeFd {
    fn read(&mut self, buf: &mut [u8]) -> io::Result<usize> {
        nix::unistd::read(self.fd, buf).map_err(|e| match e {
            nix::Error::Sys(e) => e.into(),
            e => io::Error::new(io::ErrorKind::Other, e),
        })
    }
}

impl io::Write for PipeFd {
    fn write(&mut self, buf: &[u8]) -> io::Result<usize> {
        nix::unistd::write(self.fd, buf).map_err(|e| match e {
            nix::Error::Sys(e) => e.into(),
            e => io::Error::new(io::ErrorKind::Other, e),
        })
    }

    fn flush(&mut self) -> io::Result<()> {
        Ok(())
    }
}

impl PipeFd {
    fn new(fd: i32) -> PipeFd {
        PipeFd { fd }
    }
}

impl Drop for PipeFd {
    fn drop(&mut self) {
        let _ = nix::unistd::close(self.fd);
    }
}

impl AsRawFd for PipeFd {
    fn as_raw_fd(&self) -> i32 {
        self.fd
    }
}


Fix badges

Updated coveralls and looks like circleci picked up the new name on the push (thankfully; this used to be a real pain!).  I cherry picked this commit into master so we'll get the new badges on github.

(Obviously npm will be invalid until we publish, but the path is updated...)


Fetch all SM offerings and plans

Fetch all service offerings from SM. Previously we used to filter them by broker id, but sometimes this made the URL too long > 9000 chars
Fetch all service plans from SM in a single call to improve performance.
Less is more 😋

Coverage increased (+0.9%) to 86.012% when pulling 0e36e751c3ed5c7c9259812f8fce311c003cd6f1 on optimize-sm-plans into 534bef9f0ae839c79d3863610827b40e1ae9628a on master.


NM symbol unit

https://github.com/openlayers/openlayers/issues/13497
please check if it is enough ...

thanks @ahocevar   ... i try to understand where it's fail and how to correct .... but not sure i am able to do .....

Thanks @jipexu. See the stack trace in the failing test. ol/test/browser/spec/ol/control/scaleline.test.js:224 is the place to fix it in the tests.

thanks ok i see now !

seems to be ok

welcome
so this can be closed
https://github.com/openlayers/openlayers/issues/13497


TourModule Blocks rendering

In my case I have a shared module that generate a list and make some options available, like a checkbox to select entries. That is implement in a lazy loaded module. The TourModule works fine if I only add this to the lazy load module, if I implement the TourModule in the shared module the entries won't be rendered. I must take some clicks or scroll the window to render the full page.

After scrolling all Elements looks like the first you see.
Have anybody a suggestion which problem is going on.
Versions
ngx-tour: 2.0.0
Angular: 5.2.11

What happens if you comment the TourModule code out of your app completely?
I have a suspicion that your code was depending on one of the ngx-tour directives to fire change detection for you and when it was removed your component doesn't see the changes.
Try adding this code in your component:
export class MyComponent implements OnInit {
  constructor(private changeDetectorRef: ChangeDetectorRef) {}
  ngOnInit() {
    setTimeout(() => this.changeDetectorRef.detectChanges());
  }
}


Predefined prefix for metrics

Hey,
I've added an option to prefix all the metrics with const value.
This is necessary for services like HostedGraphite where the api key should be the first sent data.

I've updated the PR according to what you suggested.

Thanks!


Entity tag: small mismatch between border and content in Chrome

At 125% size in my Chrome (Chrome at 100% and 150%, as well as Firefox at all sizes, is fine), the border line of the entity tag does not match the content - some white line appears, and the vertical line separating the entity type abbreviation from the label does not go all the way down.

Seems like a known issue in chrome -- due to rounding on subpixel calculations (https://stackoverflow.com/questions/64478453/rendering-rounding-issue-in-chrome-when-zooming), not sure we can do anything about it, apart from waiting on a a fix in some newer chrome version


Add initial GitHub issue templates

Initially users can open a bug report, feature request, or misc request.
Bug reports and feature requests will have the "kind" label
automatically added.

/hold
I want to create a dummy repo with these files to test it out before merging.

/hold cancel
/assign @damemi @ingvagabund
I tried out the issue templates using repo, https://github.com/seanmalloy/test-repo. Feel free to open an issue in that repo if you want to try it out.

@ingvagabund I fixed the spelling error. Let me know if you see any other changes that are needed.

@ingvagabund I fixed the spelling error. Let me know if you see any other changes that are needed.
Nope, all set!!!

/lgtm


C_CPP : Introduction to Friend function with examples

Description 📜
Added introduction to friend function along with examples and explanation in documentation format.
Fixes (https://github.com/girlscript/winter-of-contributing/issues/883)

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] C/CPP

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@Saviour1001 Sorry for tagging but please review this PR. I have followed all the step-by-step procedures you have said in the meeting but I don't know why I am seeing other's commits and other's files changed in mine. Can you please see this and tell me what I made wrong 🙁

@shreya dont worry about the changed files by others, we'll see only the last 2 made by you

@shreya0204 dont worry about the changed files by others, we'll see only the last 2 made by you

Thanks for the confirmation, I was worried thinking about what I made wrong :)

@shreya0204 Since that time much has changed in the repo
Do this in your PR branch:  Fetch > Compare > pull from girlscript/C_CPP to your main branch

@shreya0204 Acually your worries were correct...
Do this in your PR branch: Fetch upstream > Compare > pull from girlscript/C_CPP to your friend-function branch

Yes, I have fetched and merged in my branch do I have to make a new PR?

@shreya0204 Not from girlscript:main 🤦🏻
From girlscript/C_CPP branch
Do this in your PR branch: Fetch upstream > Compare > pull from girlscript/C_CPP to your friend-function branch

@Suvraneel Sorry 😅Yeah It's done now, I have merged from C_CPP branch to friend-function branch

@Suvraneel Thanks. It's done 👍

@shreya0204 GG ❤ :octocat: 💯

@Suvraneel Yay yay! Thank you so much!


handle bridge errors in UI

Current dependencies on/for this PR:

main

PR #101   👈

This stack of pull requests is managed by Graphite.


After the last update, Iam stopped working

Hello, after the last update, Iam stopped working and when I try to configure it, only a message appears: {"message":"Invalid handler specified"}

just reverted back to v1.0.12 and started back working....

Thanks for your feedback,this error was fixed in v1.0.14.
Should using "space" instead of "tab" in code format.


Is it possible to handle user generated small-talk  through Bing & Cortana features from LUIS

I am implementing a chatbot which can help users fill a form and get relevant leads contacting the user. Now as part of this, there is a possibility that the user may come up with some small talk like "How are you?" "Who are you" "What is your name?" etc.
Though I have answers for the same, I cannot think of an efficient way than training each of these sentences as a separate LUIS intent. But since LUIS is backed by Bing and Cortana, can I utlize them to better handle small talk generated within the chat?

Either you can train as separate intent in LUIS, or you could use http://qnamaker.ai to create a database of the question/answer pairs you want  to use and combine them using scorable.

Hi chrimc62, thanks for pointing towards qnamaker.ai
Can the model created under qnamaker.ai be invoked from within an existing LUIS model. I am thinking that if we create an intent for small talk in LUIS and then invoke the model created under qnamaker.ai to answer them?
Is such a thing possible?
Thanks


chore: remove unused workflow files

Description
This pull request changes the following:

Removes unused workflow files to avoid confusion and reduce the potential attack surface.

Related Issues

Closes #134

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

Project coverage is 61.79%. Comparing base (8069475) to head (c4a8df7).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #145   +/-   ##
=======================================
  Coverage   61.79%   61.79%
=======================================
  Files           6        6
  Lines          89       89
  Branches       11       11
=======================================
  Hits           55       55
+ Misses         34       33    -1
- Partials        0        1    +1

see 1 file with indirect coverage changes


Fix: Page Freeze Issue When Using Back/Forward of Browser History with Query Parameter Only Changes

Fix #16

I appreciate your effort in developing this awesome library.
By the way, it's pretty simillar change with #19. (it was related with hash, but mine is query params)
The page freezes (no interaction available) for a couple of seconds when i hit the back or forward,
where only the query parameters in the url are changed.
To reproduce

Add any query parameter to where ViewTransition is applied.
NOT changing the pathname, change the query param only.
Change to the other query param.
hit the back and forward button of browser (it also stucks with window.history.back() / .forward() method.)

Before fixing
https://github.com/user-attachments/assets/7bb561f9-74cf-43fe-bb1e-5784f93be6c1
After fixing
https://github.com/user-attachments/assets/07d71f2f-fe18-4b98-bd9f-8ecd74141895
I'm looking forward to this pull request being merged.
Thanks.
P.S. Sorry for bad changes of demo page 😂

Using useSearchParams() hook might have conflict because it is client-side hook. NVM
That's why i closed this PR.


⚠ ClamAV has degraded performance

In 6dab448, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in 33d1331.


Cannot create MistralAI embeddings from pdf or urls

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
from langchain_chroma import Chroma
from langchain_mistralai import MistralAIEmbeddings
from langchain_text_splitters import RecursiveCharacterTextSplitter
from langchain_community.document_loaders import PyPDFLoader
import requests
from pathlib import Path

# Get data from url
url = 'https://camels.readthedocs.io/_/downloads/en/latest/pdf/'
r = requests.get(url, stream=True)
document_path = Path('data.pdf')

document_path.write_bytes(r.content)
# document_path = "camels-readthedocs-io-en-latest.pdf"
loader = PyPDFLoader(document_path)
docs = loader.load()

# Split text
text_splitter = RecursiveCharacterTextSplitter(chunk_size=1000, chunk_overlap=200)
splits = text_splitter.split_documents(docs)

# Create vector store
embeddings = MistralAIEmbeddings()
vectorstore = Chroma.from_documents(documents=splits, embedding=embeddings)

Error Message and Stack Trace (if applicable)
An error occurred with MistralAI: 'data'
Traceback (most recent call last):
  File "/home/tda/GenAICourse/RAG/ragbot_langchain/embeddings.py", line 24, in <module>
    vectorstore = Chroma.from_documents(documents=splits, embedding=embeddings)
  File "/home/tda/miniconda3/envs/ragbot2/lib/python3.10/site-packages/langchain_chroma/vectorstores.py", line 1128, in from_documents
    return cls.from_texts(
  File "/home/tda/miniconda3/envs/ragbot2/lib/python3.10/site-packages/langchain_chroma/vectorstores.py", line 1089, in from_texts
    chroma_collection.add_texts(texts=texts, metadatas=metadatas, ids=ids)
  File "/home/tda/miniconda3/envs/ragbot2/lib/python3.10/site-packages/langchain_chroma/vectorstores.py", line 508, in add_texts
    embeddings = self._embedding_function.embed_documents(texts)
  File "/home/tda/miniconda3/envs/ragbot2/lib/python3.10/site-packages/langchain_mistralai/embeddings.py", line 222, in embed_documents
    return [
  File "/home/tda/miniconda3/envs/ragbot2/lib/python3.10/site-packages/langchain_mistralai/embeddings.py", line 225, in <listcomp>
    for embedding_obj in response.json()["data"]
KeyError: 'data'

Description
Ì'm trying to create MistralAI embeddings from a pdf document but I get the mentioned error. Are there flags or parameters of  RecursiveCharacterTextSplitter or MistralAIEmbeddings which could avoid such issue? Thanks in advance,
System Info
System Information

OS:  Linux
OS Version:  #134~20.04.1-Ubuntu SMP Tue Oct 1 15:27:33 UTC 2024
Python Version:  3.10.0 (default, Mar  3 2022, 09:58:08) [GCC 7.5.0]

Package Information

langchain_core: 0.3.14
langchain: 0.3.5
langchain_community: 0.3.3
langsmith: 0.1.138
langchain_chroma: 0.1.4
langchain_mistralai: 0.2.0
langchain_openai: 0.2.4
langchain_text_splitters: 0.3.1

Optional packages not installed

langgraph
langserve

Other Dependencies

aiohttp: 3.10.10
async-timeout: 4.0.3
chromadb: 0.5.16
dataclasses-json: 0.6.7
fastapi: 0.112.4
httpx: 0.27.2
httpx-sse: 0.4.0
jsonpatch: 1.33
numpy: 1.26.4
openai: 1.53.0
orjson: 3.10.10
packaging: 24.1
pydantic: 2.9.2
pydantic-settings: 2.6.0
PyYAML: 6.0.2
requests: 2.32.3
requests-toolbelt: 1.0.0
SQLAlchemy: 2.0.36
tenacity: 9.0.0
tiktoken: 0.8.0
tokenizers: 0.20.1
typing-extensions: 4.12.2

The KeyError: 'data' in the issue occurs due to a 429 Too Many Requests response, which prevents some documents from being processed and results in payloads that lack the data key. To reveal the actual error and improve clarity, I propose adding a check with raise_for_status() to handle cases where the status code is not 200. This will ensure that the code only attempts to access the data key when the response is successful.

@jamesev15 please see my PR. I have implemented a simple retrying mechanism to account for this, rather than just raising the error which works.

Sure! I like your approach


[release-v1.13] Add owning-component annotation to config-openshift-trusted-cabundle ConfigMap

Adds a label to our injected CA cluster bundle to avoid operator reconciliation war on OCP 4.15
Values have to line up with cluster-network-operator as in https://github.com/openshift/cluster-network-operator/pull/2111

Not a real issue ATM, as we don't reconcile and update the config-openshift-trusted-cabundle CM, but to be prepared (following our discussions at slack)...
/assign @matzew @ReToCode

/cherry-pick release-v1.12

/cherry-pick release-v1.11

Please create a separate one for 1.11


In ttype, how does List differ from Tuple?

I assume List is homogeneous and Tuple is heterogeneous, as suggested (if not implied ?!?) by the arguments. Otherwise, they're both ordered collections, start-index 0, with duplicate entries allowed?
ttype
    = Integer(int kind, dimension* dims)
...
    | Set(ttype type)
    | List(ttype type)   --- homogeneous
    | Tuple(ttype* type)  --- heterogeneous
    | Struct(symbol derived_type, dimension* dims)
...

Proposition:
If ttype* types in Tuple denotes a sequence of types for a heterogeneous tuple, then ttypes* must denote a sequence (the ASDL is ambiguous), and the length of any tuple that conforms to the spec must be equal to the length of the ttypes*.
Remark:
The length of conforming tuples is implied by the length of the ttypes*. I consider this spec to be implied and explicit, rather than implicit, with implicit meaning "not evident from the manifest text." This spec for Tuple, once ttypes* is clarified as a sequence, is therefore acceptable under the tenet that all MASR specs must be explicit.

I assume List is homogeneous and Tuple is heterogeneous, as suggested (if not implied ?!?) by the arguments. Otherwise, they're both ordered collections, start-index 0, with duplicate entries allowed?

Yes. Tuple has compile time length and types for each element. List has a compile time type, the same for each element, and the length is runtime (you can append / remove from it).
The documentation for all ASR nodes is here: https://github.com/lfortran/lfortran/tree/c648a8d824242b676512a038bf2257f3b28dad3b/doc/src/asr/asr_nodes and please do not close this issue until I document this there.

roger. Pinned the link, btw. ty :)


Rename Machine into Node

Hi there,
Headscale maintainer here :)
FYI, we are renaming Machine into Node - to better fit the internal naming of Tailscale. This might impact this project.
You can track the status of the change here https://github.com/juanfont/headscale/pull/1553

Thanks for the heads up, I don't think that affects the UI as it's always been referring to machines as devices :).
Unless it affects the API at least. Any changes to the API will meet swift and decisive ~swearing~ updates to the UI.

It will affect the API, unfortunately.
Any mention of machine is changed into node.
On Sat, Sep 23, 2023, 01:33 routerino @.***> wrote:

Thanks for the heads up, I don't think that affects the UI as it's always
been referring to machines as devices :).
Unless it affects the API at least. Any changes to the API will meet swift
and decisive swearing updates to the UI.
—
Reply to this email directly, view it on GitHub
https://github.com/gurucomputing/headscale-ui/issues/115#issuecomment-1732126490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABMGQ3QYJVX543EYE5RMELX3YN5FANCNFSM6AAAAAA5C2A4VA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks @juanfont.
I've updated the API endpoints and it is working fine. Once the changes are verified, the pull request should be merged into the master.

Noting for anyone that might encounter this that it's still broken in the current release.
The api can be manually corrected by replacing "machine" with "node" in ./web/_app/immutable/chunks/apiFunctions-60f89b05.js

Unfortunately that's not the only file. Performing a grep turned up the following:
./_app/immutable/chunks/apiFunctions-60f89b05.js
./_app/immutable/components/pages/devices.html/_page.svelte-ad198750.js
Also, for some reason I now get a 404 error when attempting to view routes.
@juanfont has the API changed for the /api/v1/node/#/routes path?

Ok, it appears that /api/v1/node/1/routes no longer works.
Is this a bug?

If you're trying to modify post-compiled svelte code you're going to have a bad time.
If you want to test headscale ui with the alpha headscale release, you will need to check out this branch and compile a release. Once the headscale release is in beta or RC I will start compiling beta releases.

If you're trying to modify post-compiled svelte code you're going to have a bad time.
If you want to test headscale ui with the alpha headscale release, you will need to check out this branch and compile a release. Once the headscale release is in beta or RC I will start compiling beta releases.

Thanks @routerino. It helps to do things right from the beginning.

still got requests to  /api/v1/machine from UI using latest docker image of headscale-ui. any updates on issue?

still got requests to /api/v1/machine from UI using latest docker image of headscale-ui. any updates on issue?

Believe it or not, I'm not in the habit of creating a release that would break the production version of headscale to accommodate the alpha version.
All the current pull requests do not dynamically detect or account for both versions. I'll accept a pull request that does so, or make up one myself when it hits beta.

still got requests to /api/v1/machine from UI using latest docker image of headscale-ui. any updates on issue?

Believe it or not, I'm not in the habit of creating a release that would break the production version of headscale to accommodate the alpha version.
All the current pull requests do not dynamically detect or account for both versions. I'll accept a pull request that does so, or make up one myself when it hits beta.

Had no idea if this beta or alpha, sorry. Docker hub just show version 23, but not the "alpha" mark. Will be w8ing for update.


Reference more use cases for consistent resolution

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.


Database structure and access patterns

I think we can use the following schema

Key
Entity Type
Contains

quiz|<SECRET>
quiz
secret, questions, url, ...

quiz|<SECRET>|submission|<ID>
quiz_submission
id, answers, ...

where SECRET and ID are UUIDs.

I'm assuming the secret is the admin key?
Should we not be able to fetch the quiz without the secret?
Ex. GET /api/v1/quiz/<uuid>
Then have secret be a query param for admin GET
Ex. GET /api/v1/quiz/<uuid>?secret=asdfasdfasdf
We can fetch the record with the uuid and then verify the secrets match afterwards, they don't necessarily have to be int he key.

That is right. Was an oversight.

And the admin stuff should be it's own route. Prefixed with admin?


Add a simplified export

Currently, a lot of the fields in the export are not used in further processing. Create an option to choose for a simplified export with only a selection of the fields.

Priority: 5.


about SHAs

Hello. I am new here. I want to ask you, what is SHAs?

Hi Nori-li - thanks for checking in! SHAs are unique identifiers of commits. This video goes into a bit more detail: https://teamtreehouse.com/library/introduction-to-git/commit-shas-and-undoing-commits#:~:text="SHA" stands for Simple Hashing,checksum uniquely identifies a commit.
Hope that helps!

Thank you，haha.


Discussion: DatArchives sending "signals" to each other

Could it be possible for DatArchives to send "signals" to one another.
Implementation Suggestion:
An experimental API that behaves similar to creating a JS custom event, e.g.:
// Target of the datSignal
var otherArchive = new DatArchive(otherArchiveLocation);

// Create a Custom datSignal
var updateSignal = experimental.datSignal("Update");

// Dispatch the datSignal
updateSignal.dispatchTo(otherArchive);

And on the front-end side this doesn't event need to be implemented, but the JS event system could be used instead.
Say, in that otherArchive the updateSignal is received by an EventListener updateEvent attached to document, and when the archive receives that signal it just fires off that updateEvent.

Is the idea that these signals would go over the network, and the signals would go to the dat owners?

Or is the idea that these are just custom events that you could fire on the objects within your app?

The former. The signal would be dispatched to the target archive which would receive it and fire it off as a JS event inside of its own html page.
Also I can see one problem in this and that is that archives aren't available all the time, so there might not be an archive to receive the signal. A solution might be to implement/reuse a watcher (just like the one used for the Beaker Watchlist) and dispatch the signal when the archive becomes available.

@mikister yeah that's a solid idea, basically using Dats as identities. We've got some tools for messaging in the works with https://github.com/beakerbrowser/beaker-core/pull/6 so we might be able to accomplish that kind of stuff.


Custom password for mongo or redis password is not injected into api, els, das

The connectionstrings are not updated in any way to reflect the password that's been set.
With configuration like:
      mongodb:
        enabled: true
        auth:
          enabled: true
          existingSecret: passwords
      redis:
        enabled: true
        auth:
          enabled: true
          existingSecret: passwords

Is there a workaround available for this? Would an acceptable approach be to override the connection string directly? Or can the password be injected by some other environment variable to the services?
Edit: If auth is disabled, mongodb is configured to be used without a password, but the connection strings still specify the password as the default "password". So one must explicitly specify enable auth and then set rootPassword to password.

@krokofant Thank you for your interest in our project. We strongly recommend using external data sources, especially in a production environment. If you need to use Redis and MongoDB in Kubernetes, you could set your own values.yaml according to bitnami. Our default settings are intended for quick deployment of Featbit in k8s, and they are not recommended for production environments.


New rule to ensure .ts extension is at the end of all imports

e.g.:
import foo from './bar';

should be:
import foo from './bar.ts';

and
import foo from './bar-dir';

should be:
import foo from './bar-dir/index.ts';

Requires #98 to be done either concurrently or beforehand.


Error message in Issues

Frontend version: d2d0a59 May 13, 2020 8:46 AMBackend version: 8c4b64f May 16, 2020 5:12 AM
at https://data.catalogue.life
When I click on count figure for the issue, I got an error message:
Request failed with status code 500
There was an error processing your request. It has been logged (ID 60cfa9b36f0cab66).
HTTP method: GET
https://api.catalogue.life/dataset/2130/nameusage/search?catalogueKey=3&facet=rank&facet=issue&facet=status&facet=nomstatus&facet=type&facet=field&issue=unmatched name brackets&limit=100
Verbatim reports work well.

Urf, we need to update the search index. That takes 3-6 hours, I'll start it right now

Ive reindexed the Collembola dataset which now works.
Ill reindex all other datasets too, but now you can at least continue working ;)

Thank you @mdoering!
Error message gone now. But report lists are empty for all issues, like that:

Sth is still wrong. Some issues do yield results, many dont, others yield too little.
Maybe the reindexing did not fully work.
@thomasstjerne there is also an oddity that the UI does not show any results for issues when you follow the link from the issues page for dataset 2130, e.g. for inconsistent name
But when you go to the workbench manually and select the respective issue filter you do get one result. There should be more, probably an ES index bug, but what puzzles me is that you get different results then the one linked from the Issue page

Sth is still wrong. There are only 29 documents indexed, Ill debug the indexing.
@thomasstjerne there is also an oddity that the UI does not show any results for issues when you follow the link from the issues page for dataset 2130, e.g. for inconsistent name
But when you go to the workbench manually and select the respective issue filter you do get one result. There should be more, probably an ES index bug, but what puzzles me is that you get different results then the one linked from the Issue page

This should work now


Works on iOS

Hooray! http://www.reddit.com/r/golang/comments/2tq6w0/ios_port_of_go_complete_to_hopefully_be_included/

Now Ebiten basically works on iOS!


测试外部发PR

Coverage increased (+0.02%) to 27.019% when pulling ab59681cc74d2851ee119aee6a951ded4539a8ad on xieyaowu:patch-2 into cdab3c073dd66a64d8179c67e15d7efe3d90cea2 on sentsin:master.


UI Settings override defaults

Hey! I wanted to change the UI for everything to better align with the games UI and stick out less.

Thanks again!

There are definitely UI overrides.  You can drop things into cactbot/user/raidboss.css and it will include after the built in CSS.
Let me know if this doesn't work for you or if there's more stuff you want to change.  Some folks have needed more things exposed to customize everything.

Hey Thanks! I found the stuff you have already included for overrides. I'll close this for now!


fix: chains: check attestation and signature

Description
a follow-up on https://github.com/redhat-appstudio/e2e-tests/pull/526
Issue ticket number and link
https://issues.redhat.com/browse/RHTAPBUGS-276
HACBS-2223
Type of change

[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 not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
ginkgo --label-filter="ec" --v ./cmd -- --config-suites=$PWD/tests/e2e-demos/config/default.yaml

Checklist:

[X] I have performed a self-review of my code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

TODO

[x] fix unit tests

/test all

/test all

tests passed

/lgtm
/approve


Failing to persist Explorer folder expanded/collapsed state

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.93.1 (Universal)
OS Version: macOS 14.6.1 (23G93)

Steps to Reproduce:

Launch code . on a project with some directories with very many files.

Unfortunately, VSCode insists on expanding every directory in the Explorer at launch. I often interact with projects with a large number of assets lexicographically earlier than implementation code in the project file tree.
This means that the less relevant files always appear in the Explorer, and I have to scroll down, down, down to get the relevant files. That's a frustratingly cumbersome workflow.
I can collapse the folder. But VSCode never persists the expanded vs collapsed state of Explorer folders. The state resets at every launch.
I've tried setting various VSCode settings recommended online, but none appear to have an effect. Honestly, the design is questionable. Most are limited to always-expand vs always-collapse logic, but that's not what I want.
I want every folder expanded by default, unless I have manually elected to collapse it, in which case, I want that remembered until the very day that I delete my project's VSCode cache.

Update:
VSCode is able to persist the expanded/collapsed state of the grandparent folder. But the intermediate parent folder's state is ignored when relaunching VSCode.