IgnoreCollectionOrder is broken

Hi guys,
I'm not sure I'm using it right, but it seems that the IgnoreCollectionOrder doesn't work.
I'm using the latest version (I've also tried lower versions).
public void CheckIgnoreCollectionOrder()
        {
            var config = new ComparisonConfig { IgnoreCollectionOrder = true };
            var compareLogic = new CompareLogic(config);

            var actual = new Foo[] { new Foo(2), new Foo(1) };
            var expected = new Foo[] { new Foo(1), new Foo(2) };

            var result = compareLogic.Compare(expected, actual);

            Assert.IsTrue(result.AreEqual);
        }

        public class Foo
        {
            public int Prop { get; }

            public Foo(int prop)
            {
                this.Prop = prop;
            }
        }

Hi, I think that your problem lies in the fact that your property doesn't have a setter, just add set; to Prop and your example should work.
The secret seems to be in IgnoreOrderLogic.cs at line 281, where it says that a property must have "CanWrite" to true to be elligible to compose the key.
Another solution could be to set up a specific key for your object, as in there:
https://github.com/GregFinzer/Compare-Net-Objects/wiki/Comparing-Lists-of-Different-Lengths
I'm not sure if which properties are elligible to compose the fallback key is missing in the documentation or is an actual bug.
Hope this help!

@Onzi12 Put on a CollectionMatching Spec:
        [Test]
        public void CheckIgnoreCollectionOrder()
        {
            Dictionary<Type, IEnumerable<string>> collectionSpec = new Dictionary<Type, IEnumerable<string>>();
            collectionSpec.Add(typeof(Foo), new string[] { "Prop" });

            var config = new ComparisonConfig { IgnoreCollectionOrder = true, CollectionMatchingSpec = collectionSpec };
            var compareLogic = new CompareLogic(config);

            var actual = new Foo[] { new Foo(2), new Foo(1) };
            var expected = new Foo[] { new Foo(1), new Foo(2) };

            var result = compareLogic.Compare(expected, actual);
            Console.WriteLine(result.DifferencesString);
            Assert.IsTrue(result.AreEqual);
        }

Hi Greg,
Thanks for your quick reply!
The CollectionMatching solution is not so maintainable\scalable\user-friendly, as it removes the abstraction from the object under test - which is the main reason I use the framework.
Is there a C#.NET limitation that prevents it from being comfortable as standard objects comparison?
By the way, the IgnoreCollectionOrder worked out of the box in early versions (really early, somewhere between v1-v2)
Regards,
On Albilia.

It is a design choice to ignore properties without setters.  My thinking is that get only properties are calculated fields that should not be compared.  I have also had a bad experience with poorly implemented getters at companies.  If you wish to create an option to compare get only properties, please create a config option, the implementation, and tests with your pull request.


Security System: Turn off the zones together when the alarm is disarmed

Scenario: the alarm is set to "Away". One of the zones is triggered by one sensor. The alarm is now "Alarm". Turn the alarm to Off. Turn the alarm to "Away" again will automatically go to "Alarm" because one or more zones are still activated. We should give the option to automatically turn off / reset the zones when turning off the alarm.

I got the same issue of alarm turning right back on but i dont use zones. I suspect the “Alarm triggered” switch should be reset too.

@Darko2 can you please list the steps to reproduce? so I can have a look into it.

I ran some simulations to try to replicate the issue.
I tried to repeat the steps manually, my automations would ordinarily do, and this is what I got:

security system state = disarmed
all security system switches to off (stay, away, night, triggered)
alarm triggered switch to on
arm away switch (or any other arm switch) to on
Alarm is immediately triggered.

Alarm is not triggered if the alarm triggered switch is left on while in arm state:

security system state = arm away
alarm triggered switch to on (alarm is triggered)
disarm alarm
arm away switch to on

I get now that an error in my automation behavior is the root cause of the problem, setting the trigger to on even when the alarm was disarmed should not happen.
Still, If alarm is disarmed (either with turning off the arm switches, or with setting the system state to disarm) the alarm triggered switch should be reset to off and if the alarm system state is changed from disarm to arm, the alarm triggered switch should first be set to off then the system should be armed.
Hope this helps. Thanks!

The reason of this PR is exactly that: fixing automations.  It worked but re-enabling the alarm was going straight in "Alarm" mode. The reason is: a race condition in the plugin. You can run a single change at the time, because the plugin is trying to store the settings on disc (async). If you change two or more accessories at once (with an automation), some will not be stored in the internal state and the UI will be out of sync. This PR solves my issue to start. I would ask @grover to think about a long term solution :)


Add support for Django 1.10

Coverage decreased (-0.07%) to 95.889% when pulling 0a87f49455815579f9b2911ad982f4cb03823f22 on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage increased (+0.07%) to 96.028% when pulling 1717ccf6ba0632e6a30700cb50a707e455cd3c1d on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage increased (+0.07%) to 96.028% when pulling 1717ccf6ba0632e6a30700cb50a707e455cd3c1d on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage increased (+0.07%) to 96.028% when pulling 1717ccf6ba0632e6a30700cb50a707e455cd3c1d on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage increased (+0.07%) to 96.028% when pulling 1717ccf6ba0632e6a30700cb50a707e455cd3c1d on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage increased (+0.07%) to 96.028% when pulling 1717ccf6ba0632e6a30700cb50a707e455cd3c1d on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Current coverage is 92.47% (diff: 100%)

Merging #342 into develop will increase coverage by 0.13%

@@            develop       #342   diff @@
==========================================
  Files            25         25
  Lines          1435       1435
  Methods           0          0
  Messages          0          0
  Branches        181        181
==========================================
+ Hits           1325       1327     +2
+ Misses           58         57     -1
+ Partials         52         51     -1

Powered by Codecov. Last update 19872a7...1717ccf

Coverage decreased (-0.2%) to 95.752% when pulling a0c363b3e1c7a2fc267c0681a74049b03f1099ce on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage decreased (-0.07%) to 95.891% when pulling a0c363b3e1c7a2fc267c0681a74049b03f1099ce on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage increased (+0.08%) to 96.036% when pulling 2dff9fb9f389ca49f84fbb062c1d1adef071b591 on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.

Coverage increased (+0.08%) to 96.036% when pulling 2dff9fb9f389ca49f84fbb062c1d1adef071b591 on feature/django110 into 19872a711ae318be99b68fe958e2f82d7d894223 on develop.


Service killed by Android

I have a start and stop button in my app to register or unregister the background service. It works like a charm even when the app is killed (that's the intent of the plug-in), but for some reasons, after 10-15 min the notification disappears.
Is the service sticky? Because I guess it should start again everytime it gets killed, right?
I'm using a Huawei honor 10.

The service is sticky and the whole purpose of the notification is to keep the service alive. It would be a great help if you can provide more information, code or logs;

I think the problem is ... Huawei !
Their OS ignores Android's battery optimization settings and kills the background service if the app is not manually whitelisted in the phone settings. I haven't found any solution to avoid this problem on Huawei devices.
The service worked perfectly on a Samsung device.

This could be Huawei, But I can see some battery apps keep their service alive on Huawei. I'm looking into it;

After what I've read, it seems to be a problem on most Chinese phones ... I haven't found a solution yet.

I couldn't find any solution for Huawei phones, so I'm closing this issue, but feel free to open it anytime;


Update error message for index 0 input

Codecov Report

Merging #360 (e0adf7d) into master (e133f2b) will increase coverage by 3.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #360      +/-   ##
============================================
+ Coverage     58.16%   61.18%   +3.02%
- Complexity      685      715      +30
============================================
  Files           126      126
  Lines          2878     2878
  Branches        369      369
============================================
+ Hits           1674     1761      +87
+ Misses         1060      982      -78
+ Partials        144      135       -9

Impacted Files
Coverage Δ

...rc/main/java/dash/model/task/CompletionStatus.java
50.00% <0.00%> (+8.33%)
:arrow_up:

...ogic/commands/personcommand/FindPersonCommand.java
86.53% <0.00%> (+17.30%)
:arrow_up:

src/main/java/dash/logic/parser/ParserUtil.java
87.32% <0.00%> (+18.30%)
:arrow_up:

...sh/logic/commands/taskcommand/FindTaskCommand.java
86.27% <0.00%> (+29.41%)
:arrow_up:

.../parser/personcommand/FindPersonCommandParser.java
75.51% <0.00%> (+40.81%)
:arrow_up:

...ogic/parser/taskcommand/FindTaskCommandParser.java
69.69% <0.00%> (+43.93%)
:arrow_up:

Continue to review full report at Codecov.

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


Rendering before the load function is returned, adding "asyncLoad"

Describe the problem
Preface: I'm terrible at searching on GitHub so if this has already come up I apologize!
Sometimes you want to get data that doesn't necessarily need to be rendered on the server or isn't needed until later. One use-case could be for example when you're going from a landing page to something that shows some dynamic data in a table. You might want to load everything else and only show a spinner while the data is loading.
This currently has to be done in user land inside your svelte components. It would be great if we could do this in our load functions by passing in some boolean (problematic since we're now just returning data), or in an asyncLoad. If you go with the latter you could at some point even combine the two if you need something to load before render, and something else after.
The big win however, is that we always know where our data is located, in our +page.js or +page.server.js files! :)
Describe the proposed solution
It could look something like this:
// +page.js
export const asyncLoad = async ({ locals }) => {
   const res = await getUsersFromDB()
   const users = await res.json()
   if (!res.ok) {
       throw error(404, 'No users found')
   }

   return {
       users
   }
}

The users object would be returned as a promise that you can use in your code.

{#await data.users}

...waiting

{:then users}

		{#each users as user}

{user}

		{/each}

{:catch error}

{error.message}

{/await}

Alternatives considered
Doing it in user land like you normally would.
Importance
nice to have
Additional Information
The use of {#await} is just to quickly show an example. Personally wouldn't use it.

Apparently you can already do this 🤯 https://kit.svelte.dev/docs/load#promise-unwrapping
You blink and the docs have changed! ❤


When building react app using esbuild, devtools reports that it cannot find QueryClient

Describe the bug
I am using esbuild to build my react app, however, in development I get an error saying that QueryClient is not available:
QueryClientProvider.js:36 Uncaught Error: No QueryClient set, use QueryClientProvider to set one
    at HJr (QueryClientProvider.js:36)
    at devtools.js:267
    at ZA (react-dom.development.js:14985)
    at THe (react-dom.development.js:17044)
    at HHe (react-dom.development.js:19098)
    at HTMLUnknownElement.no (react-dom.development.js:3945)
    at HTMLUnknownElement.ps.__trace__ (inline-script-content.js:146)
    at Object.gm (react-dom.development.js:3994)
    at cp (react-dom.development.js:4056)
    at uSe (react-dom.development.js:23964)

My app is following standard practice:
export function App(): ReactElement {
    return (
        <QueryClientProvider client={queryClient}>
            <AppContent />

            <ReactQueryDevtools initialIsOpen={false} />
        </QueryClientProvider>
    );
}

My esbuild configuration is also pretty straight forward:
build({
    bundle: true,
    define: {
        "process.env.NODE_ENV": "'development'",
    },
    entryPoints: ["./src/index.tsx"],
    inject: ["src/react-shim.ts"],
    loader: {
        ".ts": "ts",
    },
    minify: true,
    outfile: "./dist/main.js",
    plugins: [
        lessLoader({
            javascriptEnabled: true,
        }),
    ],
    sourcemap: true,
    target: "es2020",
}).catch(() => process.exit(1));

When I use my webpack build, everything is working as expected. When I build in production mode or remove devtools everything is working as normal.

We are tracking this here: https://github.com/tannerlinsley/react-query/issues/1936
seems to be an issue with a separate version of react-query being used for the devtools, and so they are using different contexts. Let’s please keep the discussion over there


In React native, an error occurs if there is no px in margin.

Environment

## System:
 - OS: macOS 10.14.6
 - CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
 - Memory: 631.96 MB / 16.00 GB
 - Shell: 5.3 - /bin/zsh
## Binaries:
 - Node: 10.15.3 - /usr/local/bin/node
 - Yarn: 1.15.2 - /usr/local/bin/yarn
 - npm: 6.9.0 - /usr/local/bin/npm
 - Watchman: 4.9.0 - /usr/local/bin/watchman
## npmPackages:
 - babel-plugin-styled-components: ^1.10.6 => 1.10.6
 - styled-components: ^4.3.2 => 4.3.2

Reproduction

https://www.webpackbin.com/bins/-KeeZCr0xKfutOfOujxN
https://codesandbox.io/s/rkmNRByE4
Could not find module in path: 'styled-components' relative to '/Wrapper.js' ...
Steps to reproduce
This is an error.
import styled from 'styled-components/native';

const Section = styled.View`
  margin: 16;
  margin-top: 8;
  margin-bottom: 8;
`;

This is not an error.
const Section = styled.View`
  margin: 16px;
  margin-top: 8;
  margin-bottom: 8;
`;

Expected Behavior
I think it should work without the px in margin props.
Actual Behavior
error
Error: Failed to parse declaration "margin: 16"

This error is located at:
    in StyledNativeComponent (created by Styled(View))
    in Styled(View) (at HaulerServiceItem.tsx:27)
    in RCTView (at View.js:45)
    in View (at TouchableHighlight.js:397)
  ...

Needs the units. This is css
On Thu, Sep 19, 2019 at 3:01 AM Bugtype(Jerry<EMAIL_ADDRESS>wrote:

Environment
System:

OS: macOS 10.14.6
CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
Memory: 631.96 MB / 16.00 GB
Shell: 5.3 - /bin/zsh

Binaries:

Node: 10.15.3 - /usr/local/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman

npmPackages:

babel-plugin-styled-components: ^1.10.6 => 1.10.6
styled-components: ^4.3.2 => 4.3.2

Reproduction
https://www.webpackbin.com/bins/-KeeZCr0xKfutOfOujxN
https://codesandbox.io/s/rkmNRByE4
Could not find module in path: 'styled-components' relative to
'/Wrapper.js' ...
Steps to reproduce This is an error.
import styled from 'styled-components/native';
const Section = styled.View  margin: 16;   margin-top: 8;   margin-bottom: 8;;
This is not an error.
const Section = styled.View  margin: 16px;   margin-top: 8;   margin-bottom: 8;;
Expected Behavior
I think it should work without the px in margin props.
Actual Behavior
error
Error: Failed to parse declaration "margin: 16"
This error is located at:
in StyledNativeComponent (created by Styled(View))
in Styled(View) (at HaulerServiceItem.tsx:27)
in RCTView (at View.js:45)
in View (at TouchableHighlight.js:397)
...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/2755?email_source=notifications&email_token=AAELFVRPQE4IQSKI35QEJFDQKLFM3A5CNFSM4IYFFZTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HMJBNDA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAELFVXKM34UC7ZVTLKZE7TQKLFM3ANCNFSM4IYFFZTA
.

Oh, I see. Thank you.
But… The margin-top and margin-bottom works normally without the unit.
When there is no unit, shouldn't there be an error?

I'm experiencing the same issue. using margin-top and others, styled-component is passing through its internal checks. but it seems like margin: 16; it is going through the normal pipeline

@bugtype I think this is a bug in css-to-react-native... I would consider opening an issue there. styled-components itself does not manipulate the CSS you provide


DBZ-2120 SQL Server Slow Query

https://issues.redhat.com/browse/DBZ-2120

@hoanglinh0710 LGTM, thanks! Could you please create the PR against master not 1.1? Also do you know why is there the performance difference? Was the stored function called for each row?

I will create PR against master. I have not found the root cause yet, but I think it related to SQLServer query plan.
I write a simple java console to test query.

But i do not reproduce problem in SSMS.


API Endpoint - Add Transmitter Transducer Accuracy Data

Add an API Endpoint to create/add Transmitter Transducer Accuracy Data
Testing Reference Only:
Low Level Accuracy (Text)
Low Level Accuracy Spec Code (Dropdown)
Mid Level Accuracy (Text)
Mid Level Accuracy Spec Code (Dropdown)
High Level Accuracy (Text)
High Level Accuracy Spec Code (Dropdown)

Test Case: TC1095

Test Passed


I expected creation of the PVC in the another file system

Hi @sHaggYcaT
Thank you for reporting the issue. In order to stay backwards compatible, this feature has been added since MicroK8s 1.25. For older versions of MicroK8s, it is still possible to use, but you need to do the following to manually update the hostpath provisioner to version 1.4.0 or newer:
sudo microk8s kubectl set image deploy/hostpath-provisioner -n kube-system hostpath-provisioner=cdkbot/hostpath-provisioner:1.4.0

@neoaggelos thank you! After upgrade, it works as expected


Android R8 issue with Ser

Hello,
When using https://github.com/JakeWharton/ThreeTenABP on Android (which depends on threetenbp) we are having an issue that Android Release builds that are minimized using Google R8 throws an exception due to the default constructor of the class org.threeten.bp.Ser being removed by R8
Can you add a R8 proguard file in the library so R8 will not perform the optimization?
-keepclassmembers class org.threeten.bp.Ser {     <init>(); }
Cfr: https://github.com/JakeWharton/ThreeTenABP/issues/122

Feel free to raise a PR


feat: support using map as the externals root

What kind of change does this PR introduce?
Related discussion: https://github.com/webpack/webpack/discussions/16272.
Support fine-grained control of external types using an external category in a map format.
While the current external function type can achieve this to somehow, it has a major drawback: the string and regex checks must be overridden in the function type to perform these judgments.
The external type of map is added here to prevent the ongoing spread of subsequent types like 'module-import' We can imagine that the 'module-import' type no longer exists. Instead, we use the new external type map, which we can implement easily as follows.
externals: {
  module: 'module',
  import: 'import',
}

In the future, when there are more similar requirements of 'A-B', we can use map to solve it.
Overview changes:

add map form of externals type, and divide it in right before creating ExternalModule
add the category to external function params

Did you add tests for your changes?
Yes.

Does this PR introduce a breaking change?
I believe not, 'externalsType' just adds a new non-string type.

What needs to be documented once your changes are merged?
Yes, if this could be merged.

@alexander-akait Friendly ping 😊. If this PR changes too many scopes and may not be merged, we could consider adding a new commonjs-import external type. It reserves import() while changing other external requests to require. And won't change too much code.
The most essential demand is to reserve dynamic import for CJS as it's supported since 13.2.0. Dynamic import could allow user to import an ESM module, whereas require can't. I think this is commonly used in Node.js targeted scenes.
esbuild support emit import() if target is above node 13.2.0 and could disable this behavior by --supported:dynamic-import=false.


ignore unknown event EVT_CHAR for wxTextCtrl

when I generate python code, the warning comes out. As a result, no python code is created; what is worse, wxGlade deletes EVT_CHAR when I save wxg file.
But in fact, wxTextCtrl supports the EVT_CHAR event

For one of the next versions I'm planning to support additional events.

In my app, I can't use self.Bind(wx.EVT_CHAR, self.onTextDeviceIdInput, self.textDeviceID), but self.textDeviceID.Bind(wx.EVT_CHAR, self.onTextDeviceIdInput) works
maybe I misunderstood. But these two make same sense for me.

I did not try, but I would think that EVT_CHAR is derived from wx.Event and does not propagate to the window as it's handled by the control itself. I.e. you can catch the EVT_CHAR for the widget, but if it's not handled, the text control will handle it and insert the character.
EVT_TEXT on the other hand is derived from wx.CommandEvent and will propagate to the parent window.
I think you should see some info here:
https://wxpython.org/Phoenix/docs/html/events_overview.html#how-events-propagate-upwards

I'm not sure this issue was fully understood.
I added an "EVT_CHAR" entry to my frame with an on_char handler.
The project seems to save ok, and I can see an entry in the wxglade project file.
            <handler event="EVT_CHAR">on_char</handler>

However, when generating code I get an error message:
WARNING: Ignore unknown event EVT_CHAR for Main_Frame_WXG

and there is no generated code for this event (due to the "error").
I can manually add the event to my derived frame class and the code does capture any key presses.
        self.Bind( wx.EVT_CHAR, self.on_char )

So, I think it is a bug in wxglade not supporting all known event types.

Ah, OK. Yes, this is work in progress and only in the repository.
The plan is eventually to have pop-up menus or something similar to choose from available events. Generating and grouing the available events is non-trivial, though, so it will take some time.
I will implement at least the code generation soon such that the handler is generated and bound in your case. Give me a few days or weeks.

I think that such events are also not restored when loading from a .wxg file. I will fix this first...

OK, basic support is now in the repository.
To be done: Modify code generation for preview to handle non-existent events.

I think that now everything should be fine:

save/load should work
binding should work
on editing and loading, event names EVT_... should be converted to uppercase
preview code has an exception handler which just prints a note to the console

Yes, that seems to work ok now.  That was a very fast "few days or weeks" !!  Tip of that hat to you Dietmar.

Well, it turned out to be easier than expected. All the refactorings of the internal structures are paying off.

1.0.0a1 is online.


@gqlType apparently wants to use the whole dockblock as the type's name

/**
 * @gqlType
 *
 * This is a note for myself
 */
export type Query = unknown;

/** @gqlField */
export function queryField(_: Query): string {
  return ''
}

Dumps this error

# ERROR MESSAGE
# =============

# Grats playground bug encountered. Please report this error:
#
#  l@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2504646
# o@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2550813
# q@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2554958
# z@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2597543
# y@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2592981
# S@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2599039
# 8284/ue/r<@https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:41216
# ue@https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:41897
# 8284/qe/</o<@https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:43569
# 8284/qe/<@https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:43763
# 7781/run/<@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2227204
# run@https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2227180
#

Playground link
The error dump doesn't give us much to work with, however, if we use this code:
/**
 * @gqlType
 *
 * ThisIsANoteForMyself
 */
export type Query = unknown;

/** @gqlField */
export function queryField(_: Query): string {
  return ''
}

We get this as the resulting schema:
type ThisIsANoteForMyself {
  queryField: String
}

Maybe @gqlType needs to take only until the next newline to extract the type's new name?

I think TypeScript's docblock parsing assumes the description comes before any tags. We can double check by logging what we see on this line in this case. Does it give multiple sections of description? If it does, I think your suggestion is good. We could use just the first line as our GraphQL name.
Assuming TypeScript only looks for the description before the tags:
What if we just check the typename value for any non-GraphQL-identifier characters (spaces/linebreaks) and report a helpful error right away rather than waiting for GraphQL validation.
That would prevent the error of us generating a name that's so broken is causes stuff to break. It could also let us provide a helpful error:

Unexpected invalid GraphQL name. If you are trying to define a GraphQL description, it must be placed it before any @ tags.

We should also document this limitation in this page: https://grats.capt.dev/docs/resolvers/descriptions

Aside. When I open the playground link you provided, I get a slightly different error message. It's basically the same, but also includes the actual error message from GraphQL JS. Maybe it got truncated/mangled by your copy/paste?
# ERROR MESSAGE
# =============

# Grats playground bug encountered. Please report this error:
#
#  GraphQLError: Names must only contain [_a-zA-Z0-9] but "This is a note for myself" does not.
#     at o (https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2550813)
#     at new q (https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2554958)
#     at z (https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2597543)
#     at y (https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2592981)
#     at S (https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2599038)
#     at https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:41216
#     at ue (https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:41897)
#     at https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:43569
#     at https://grats.capt.dev/assets/js/8926b418.0a75dbcb.js:1:43763
#     at https://grats.capt.dev/assets/js/7492.5eb44cb1.js:28:2227204

Aside. When I open the playground link you provided, I get a slightly different error message. It's basically the same, but also includes the actual error message from GraphQL JS. Maybe it got truncated/mangled by your copy/paste?

Actually seems to be a browser bug. I mainly use Firefox, and I got the "truncated" error. When I opened the playground link with Chrome, I got the same error text as you did.


Semantics of length and size switched?

I was trying to use this for backing a d3.js graph, and after a bit of debugging found that (to me) it looks like the semantics of .length and .size are the wrong way around. That is to say, for a "plain" JS Array, .length is (usually, except for some edge cases) the number of elements in the array, what is CBuffer.size here.
For using CBuffer as a "drop-in" replacement for a plain old Array, exchanging these meanings might be helpful. What do you think?

Cool. Want to open a PR?


Example for Refreshing Token still sets the new Refresh Token

Hi,
In your example for refreshing the access token, you set the refresh Token of the spotifyAPI to the given refresh token of the AuthorizationCodeCredentials. The problem is that refresh code of this AuthorizationCodeCredentials is null, which you stated in an old issue. Please update the example so that others don't get misleaded like me.

Which issue are you referring to?


To send font names in UTF-8

Scintilla 3.5.3 interpret font names in UTF-8.
In previous versions, font names were sent in ANSI.

I've chosen Goong-seo font. Maybe you can see the difference.

In r940, even if I choose Goong-seo font, I can see system default font.

(Not Goong-seo font, it called Gulim font, old and ugly system default font)
Applying patch, I can see Goong-seo font correctly.

What baffles me is if the WideCharToMultiByte is needed now at all...


Modify the typos in the document

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
nothing

@steve-liuxu it seems you have merged branch steve-liuxu/master in a wrong direction multiple times.
Restore your master branch to be the same as yiisoft/yii2:master, apply changes and create PR again. Thank you

OK. If I want to fix the docs of 2.1 branch,would i create PR on 2.1 branch?

Yes. Checkout 2.1 first, then branch off it.

Thanks.


Line break rules (on binary operators)

Python version: 3.7.1
Black version: 18.9b0
Does also happen on master: Yes
For a code snippet like
conv1_out = model.conv1.forward(input_onehots).detach().numpy() - model.conv1.bias.detach().numpy().reshape(-1, 1)

currently, it will be formatted as
conv1_out = model.conv1.forward(
    input_onehots
).detach().numpy() - model.conv1.bias.detach().numpy().reshape(-1, 1)

and (online black formatter on the master branch)
conv1_out = model.conv1.forward(
    input_onehots
).detach().numpy() - model.conv1.bias.detach().numpy().reshape(
    -1, 1
)

These look wired. Shall we make it to be
conv1_out = (
    model.conv1.forward(input_onehots).detach().numpy()
    - model.conv1.bias.detach().numpy().reshape(-1, 1)
)

Another example where this proposal would lead to an improvement IMO:
-                    args = self.axes.transData.frozen().to_values()[:4] + (0, 0)
+                    args = self.axes.transData.frozen().to_values()[:4] + (
+                        0,
+                        0,
+                    )

I poked around the Black source code and found a fairly minimal change that seems to fix this. Take a look at #918 if you're interested.

I understand that you have a particular example which could be made better. However, the change you're proposing would make many other examples look worse (like the assert tests you had to change in your proposed pull request).
In particular, Black does not promise to make very complex lines always "optimally beautiful" (or, "as least ugly as possible"). In such cases many users tend to refactor the code just a bit to make it both easier to read to the human and easier to format by our simple tool.
For example:
conv1_out = model.conv1.forward(input_onehots).detach().numpy()
conv1_out -= model.conv1.bias.detach().numpy().reshape(-1, 1)

IMO that wins over either formatting.


Cancellable requests

This is probably a dependency of #8

Implemented in #51

This is possible now that #51 is merged


(AH) video implementation

Solution: Video will be embeded into our own server space and with the “video element“ on top of the main page
-> B&A:  decesion how to style the image on top of the page
-> Guide: Edits CSS
Question: No adding of cookie window or further data privacy is needed, correct?

@GuidaGG The video will be set as on the dev-page, the thing I would like you to do is to reduce the top hight.
It says 10rem, please change it to 7, just below the gradiant.

Hey Guida
Thank you for testing! Cool, thank you for the preview.
If they go for this option:

Can we also fit the video to the width? I think this makes more sense and also I don’t like the white edges.
Autoplay – definitivley we can add a button.
Can the video also only appears on the main page?

Best
Astrid

Am 22.10.2024 um 14:11 schrieb Guida Ribeiro @.***>:
Dear Astrid,
can you check if the example I did is what you expect?
the video takes always the height accordingly to the screen size; in some cases so that the video fits in height and the subtitles are showned, the width is slightly smaller than the screen
I think the autoplay will not always work, depends on browser and security. Maybe we could have a default play button in case?
https://dev.vielfaeltig-bremen.de/
to implement this properly I need between 2-3 hours.
—
Reply to this email directly, view it on GitHub https://github.com/GuidaGG/vielfaeltig/issues/60#issuecomment-2429111144, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5UY52RE3WLIUZQP3H7PRNDZ4Y6G7AVCNFSM6AAAAABQDDL65KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZGEYTCMJUGQ.
You are receiving this because you authored the thread.

the thing is, because the video has a specific format, if i put it 100% of the width, the height will be a lot of times bigger than the height of the screne, which means the subtitles/bottom part of the video is cut. It is a decision you have to make, either priority of the height or of the width,
yes, the idea is to have it just on homepage, but i didnt implemented it.
can you make the button play like the arrow buttons we use?

I see, this was not a problem for me, because on my screen it fits perfectly. The only thing i can imagine having a full width would be to use a mask and crop not the bottom of the video but the top, in case the screen does not have the hight.
Dies this makes sense?

I will try some options when we implement it.

Clever woman because we go for the other option :)
The easier on. For this, I would like you to reduce the spacing above the video as I mentioned in the second commment here. Also I will create an icon for “Play“

here are the icons of you desire

@ah-bas-und-aer can you check the implementation?
space and buttons are on.

@GuidaGG I uploaded the mp4 video file, can we use this as suggested in case the webm is not working?

Hi Astrid,
Can you please test if the video is now working?
so the implmentation of the sources and the buttons are not default from the video-block, so I will post here the code that you need to use whenever you would like to use a video. We still need to confirm this is working but I will already leave here the code, because at least for the buttons it is necessary

<video autoplay controls muted>
<source src="https://dev.vielfaeltig-bremen.de/wp-content/uploads/2024/10/CND-1135_vielfaeltig_Imagespot_Master_4K_webM.webm">
<source src="https://dev.vielfaeltig-bremen.de/wp-content/uploads/2024/10/CND-1135_vielfaeltig_Imagespot_Master_4K_med_Q_UT.mp4">
</video>

You can have the code view of the page by going to:


Composer fix

Fixed Studio version and updated composer.lock

Did the Composer dependencies install successfully without this? I'm a bit hesitant, because I was going to do some Studio maintenance this week anyway, so we'll have a lot of changes in this direction anyway.

No, unfortunately not, Composer show:
The requested package franzl/studio could not be found in any version, there may be a typo in the package name.
Can we use 0.9.5 version or there may be problems?

Thanks!


abrupt masks

I use my dataset to train and notice that the masks usually have different colors than the parts around them.They are easy to distinguish with naked eyes.
So if there are some effective post processing methods?

I use my dataset to train and notice that the masks usually have different colors than the parts around them.They are easy to distinguish with naked eyes. So if there are some effective post processing methods?

I also encountered this problem, what data set did you use for training? Is the inconsistent color a shade of black?

I use my own dataset, but mine is in a variety of colors, mostly a bit of light green

I use my dataset to train and notice that the masks usually have different colors than the parts around them.They are easy to distinguish with naked eyes. So if there are some effective post processing methods?

I also encountered this problem, what data set did you use for training? Is the inconsistent color a shade of black?

Did you use the pre_trained model? I found that maybe the way I use the load_checkpoint maybe wrong.My email is<EMAIL_ADDRESS>we can communicate more.

Hi!
Could you add examples to illustrate your question?


Multiple blog posts per day

Blog posts currently support ddmmyyyy when being listed - should also consider hhmmss (or at least hhmm) to allow multiple blog posts per day.

I've not tested it but using the format yyyymmdd_hhmm-post.md should in theory work.


Remove BSARDRetrieval task for French?

Problem
This task seems to be very hard for almost all models, ndcg@10 is ~0-3%.
Dataset information
The paper introducing the dataset have been published in ACL, so I supppose the quality of the dataset is good, see paper and HF dataset card.
Realted to: https://github.com/embeddings-benchmark/mteb/issues/334
Is it a good idea to keep it? @KennethEnevoldsen @MartinBernstorff @Muennighoff

We should probably start checking if the dataset contains a bug

Agree with Kenneth.
In the abstract they mention 74.8% R@100; I assume our benchmarks are much worse than that? If so, I see two options:

Our baseline models are much worse than theirs for this task, or
There is a bug in their evaluation (e.g. target leakage), or
There is a bug in the dataset they created, or
There is a bug in the dataset on huggingface

We probably want to find out which is true before adding it to the benchmark 👍

I did some testing yesterday here: https://colab.research.google.com/drive/1QMoEDoBlsGQlieSStvbSIShvZz44_o5z?usp=sharing
And I was able to produce good results with TF-IDF (recall@100 around 47% comparable to the paper)
I also tested sentence-camembert-base and the results were way higher than what we had
I think I found the bug and I am opening a PR to fix it.

Also, should we change the main score to recall@100? Seems to be the metric that the authors are pushing.

Wonderful @wissam-sib, I believe both changing the score to be in accordance with the authors seems relevant as well.

The fix did the trick: https://github.com/embeddings-benchmark/mteb/pull/615/files#diff-8b79d2850b7ba2ac2e003f1ed995b02db503a83401c7769bd0e8ad0a3f2dc936 🎉


proton

According to README.md, when Preprocess dataset, there is a problem, as follows：

But the “tables.bin” does not exist in the original spider dataset.
Thank you！

Thanks for your question.
In order to control the generation of "tables.bin", we have two arguments: "--raw_table_path ${table_data}" and "--table_path ${table_out}".
"${table_data}" refers to "table.json" and "${table_out}" refers to "table.bin".
These arguments can be found in the "run_processing.sh" file.
The generation of "${table_out}" depends on the presence of "${table_data}".
If "${table_data}" is not provided, "${table_out}" will not be generated.
Could you please confirm whether you have provided "${table_data}"?

Thank you for your answer!
I have provided the original ${ table _ data }" of the spider dataset as follows：
丁可欣
@.***

------------------ 原始邮件 ------------------
发件人:                                                                                "AlibabaResearch/DAMO-ConvAI"                                                                                @.>;
发送时间: 2023年3月7日(星期二) 中午11:35
@.>;
<EMAIL_ADDRESS>主题: Re: [AlibabaResearch/DAMO-ConvAI] proton (Issue #17)
Thanks for your question.
In order to control the generation of "tables.bin", we have two arguments: "--raw_table_path ${table_data}" and "--table_path ${table_out}".
"${table_data}" refers to "table.json" and "${table_out}" refers to "table.bin".
These arguments can be found in the "run_processing.sh" file.
The generation of "${table_out}" depends on the presence of "${table_data}".
If "${table_data}" is not provided, "${table_out}" will not be generated.
Could you please confirm whether you have provided "${table_data}"?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@ddd146 could you provide more detailed information ?


jQuery 3.x Compatability

I'm currently updating a code base to use jQuery 3.4.1 with the assistance of the jQuery Migrate tool. It is flagging up a deprecation issue within idletimer.
Run the following JSFiddle with the dev tools open and you'll see the warning "JQMIGRATE: jQuery.fn.bind() is deprecated".
http://jsfiddle.net/3x2sqzb1/ (it wouldn't allow direct CDN to idletimer, so I had to paste it for demo purposes).
The instructions advise updating the call from "bind" to "on" - https://github.com/jquery/jquery-migrate/blob/master/warnings.md.
Is this something that can be updated and pushed out so we can continue using this library without risk of it becoming obsolete?
Thanks!

is it as simple as replacing bind with on? or is there other testing needed?

As far as I am aware, and according to the documentation, that is all you should need to do. It is what I did with our codebase. See https://github.com/jquery/jquery-migrate/blob/master/warnings.md#jqmigrate-jqueryfnbind-is-deprecated:

In general, the .bind() and .unbind() methods can be renamed directly to .on() and .off() respectively since the argument orders are identical.

There's also a call to trim that needs to be addressed.

JQMIGRATE: jQuery.trim is deprecated; use String.prototype.trim
Cause: Older versions of IE & Android Browser didn't implement a method to trim strings so jQuery provided a cross-browser implementation. The browsers supported by jQuery 3.0 all provide a standard method for this purpose.
Solution: Replace any calls to jQuery.trim( text ) with text.trim() if you know text is a string; otherwise, you can replace it with String.prototype.trim.call( text == null ? "" : text ).

I'm working on upgrading libraries for our product to support JQuery3, if you need some assistance, I can take a look and do a pull request.

Please do a pull
Sent from Yahoo Mail on Android
On Tue, Jun 23, 2020 at 8:06 PM, Steve<EMAIL_ADDRESS>wrote:
There's also a call to trim that needs to be addressed.
JQMIGRATE: jQuery.trim is deprecated; use String.prototype.trim
Cause: Older versions of IE & Android Browser didn't implement a method to trim strings so jQuery provided a cross-browser implementation. The browsers supported by jQuery 3.0 all provide a standard method for this purpose.
Solution: Replace any calls to jQuery.trim( text ) with text.trim() if you know text is a string; otherwise, you can replace it with String.prototype.trim.call( text == null ? "" : text ).
I'm working on upgrading libraries for our product to support JQuery3, if you need some assistance, I can take a look and do a pull request.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I submitted PR, build tools are kind of outdated - I updated them locally, but didn't update the coverage support.  Do you want a PR for that as well?

PR submitted with build tool updates.  Looks like CI integration still has some issues though.

I will accept those tonight, thanks
Sent from Yahoo Mail on Android
On Thu, Jun 25, 2020 at 3:26 PM, Steve<EMAIL_ADDRESS>wrote:
PR submitted with build tool updates. Looks like CI integration still has some issues though.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Is there something in the PR you need me to change?  I see it hasn't been accepted yet.

This looks like it was merged can this ticket be closed?


What-if fails with "Processing of the what-if request has exceeded system limitations"

Bicep version
run bicep --version via the Bicep CLI, az bicep version via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep
v0.26.54
Describe the bug
A clear and concise description of what the bug is vs what you expected to happen
Recently, we have started getting issues running what-if. Some templates are timing out, others fail after a short time saying the request has "exceeded system limitations". I have no idea what that means in this context, but we have tried deploying a previous known to be good version of the template as well, and it fails the same way.
We do get a correlation ID fa70476e-a9a2-4367-8f9e-2e728f70586f'.. I wonder if this is a bug in some recent development with improving what-if (which I have seen is a highly requested improvement) or if it's something else?
Here is the full error we are getting:
az deployment sub what-if --location westeurope --name $deploymentName --template-file .\main.bicep --parameters config/prod.json --no-prompt

ERROR: DeploymentWhatIfLimitExceeded - Processing of the what-if request has exceeded system limitations. Diagnostic information: timestamp '20240326T063149Z', scope '/subscriptions/<subscription id>', tracking id '9d836932-cc25-4a5d-995f-7a07b78bce99', request correlation id 'fa70476e-a9a2-4367-8f9e-2e728f70586f'.
March 26th 2024 07:31:59Error
OperationStopped: Failed with exit code 1

To Reproduce
Steps to reproduce the behavior:
We simply do a what-if operation on our templates.
I cannot share the templates on a public forum -- if it's needed, please give me a secure place to upload it and I'll provide it.
Additional context
Add any other context about the problem here.
Correlation ID: fa70476e-a9a2-4367-8f9e-2e728f70586f'.
Timestamp: 20240326T063149Z

If it is in West Europe may be it is the ongoing issue happening with ARM there currently.

I'm experiencing the same in West Europe.

Same here. Problems have started overnight.

The problem was indeed due to a transient provider registration issue within the ARM service in West Europe.


No running

┌──(kali㉿kali)-[~/LittleBrother-GUI-]
└─$         python3 start.py
Traceback (most recent call last):
File "/home/kali/LittleBrother-GUI-/start.py", line 1, in
from Guis.gui import lay
File "/home/kali/LittleBrother-GUI-/Guis/gui.py", line 3, in
from core import layout_decision, loading
File "/home/kali/LittleBrother-GUI-/core/layout_decision.py", line 3, in
from Guis import signin_layout,create_account_layout,forgot_password_layout
File "/home/kali/LittleBrother-GUI-/Guis/signin_layout.py", line 4, in
from core import main
File "/home/kali/LittleBrother-GUI-/core/main.py", line 1, in
import pyrebase
ModuleNotFoundError: No module named 'pyrebase'
(ON LINUX)

sudo apt install git python3 #on distributions using APT (like the Debian family)
git clone https://github.com/Ankesh054-official/LittleBrother-GUI-.git
cd LittleBrother-GUI-
python3 -m pip install -r requirements.txt
Try This


[Azure] Ops manager endpoint is open to the world with public IP

Maybe need to restrict with private IP or with Network Security Group?

Hi @kamoljan, thank you for creating this issue. Since we've completed the story to make the Ops Manager IP configurable, I plan on marking this issue as done. Please let me know if any issues with that. Thanks.

@abbyachau thank you!


Instead of deleting the file, the counter starts going up

I've been monitoring my first ever Maintainerr rule which has been slowly counting down from 30. 6 days ago, a whole bunch of movies SHOULD have been deleted from my server. Instead, nothing happened and the counter which would normally count down has started to count up. The number is now 6 as it has increased by 1 every day since the deletion was supposed to take place.
To Reproduce

Create a new rule to unmonitor and delete files and set up rules to pick up some movies
Wait for the movie to reach it's last day of activity before deletion
Check the next day to find the counter has gone up, rather than be deleted.

Expected behavior
The file should have been unmonitered and deleted from my file system.
Screenshots

Device (please complete the following information):

OS: Ubuntu
Version: 1.6.10

That's odd.. Is there anything in your container log that might indicate what happened? You could try tailing the log and manually running the collection handling. Perhaps it fails to connect to a service and skips the removal. (Maintainerr will only start the actual removal if all configured services are present)
I would think the UI badges would show -1, -2,.. in that case, but apparently not.

[Nest] 396  - 12/11/2023, 12:00:05 PM     LOG [CollectionsService] Removing media with id 14610 from collection.. /opt/server/dist/modules/collections/collection-worker.service.js:285             const tvdbidPlex = plexData.Guid.find((el) => el.id.includes('tvdb'));                                              ^ TypeError: Cannot read properties of undefined (reading 'find')     at CollectionWorkerService.tvdbidFinder (/opt/server/dist/modules/collections/collection-worker.service.js:285:46)     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)     at async CollectionWorkerService.handleMedia (/opt/server/dist/modules/collections/collection-worker.service.js:153:34)     at async CollectionWorkerService.handle (/opt/server/dist/modules/collections/collection-worker.service.js:90:25) Node.js v20.10.0 error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 2023-12-11 12:00:06,328 WARN exited: server (exit status 1; not expected) 2023-12-11 12:00:07,366 INFO spawned: 'server' with pid 411 yarn run v1.22.19 $ cd server && node dist/main 2023-12-11 12:00:08,699 INFO success: server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) [Nest] 436  - 12/11/2023, 12:00:08 PM     LOG [NestFactory] Starting Nest application... [Nest] 436  - 12/11/2023, 12:00:08 PM     LOG [PlexApiService] Plex API isn't fully initialized, required settings aren't set
Is the issue because it can't find the same Movie / TV show inside of Radarr / Sonarr? There's also another line here about the Plex API not being fully initialised but I can confirm it is connected.

Looks like you managed to crash the server portion. Maintainerr expects something to be available in Plex’s metadata API response, but it’s not. I’ll try to fix it tomorrow

Guess i'll need to wait as it seems I can't update to the 'develop' tag due to using arm64 processor rather than amd64

Oh, you’re actually the first person i speak to that’s using the arm64 tag. How does it run?
I don’t test the arm64 image myself, since i don’t own a arm64 device.  But i’d love to find out if it has any flukes.

Apart from this particular issue, I haven't noticed any problems with the tool! It seems to run as expected, but then again i've not had it long enough to know whether there are any further issues.


Refactor: wikidta models

Part of an ongoing code refactoring to move all models to a common models package.
Fixes #4782
Moved wikidata models to data.models package.
Tested debug on Pixel 4 (Emulator) with API level 30.

There is an issue with the code in master @madhurgupta10

There is an issue with the code in master @madhurgupta10

Correct, I have created an issue for this (https://github.com/commons-app/apps-android-commons/issues/4927) hope it gets resolved soon.

Hi, is this PR sleeping @ben-mathu ?:)

This (and the other 10 PR's associated with refactoring model classes) seem to have stalled since February.  Is this work that is wanted or fair to call it abandoned?  If the work is needed, you want me to pull the changes onto a single feature branch get the tests cleaned up and submit a single PR that could be reviewed and merged so these 11 can be closed?

Hi @psh , nice to see you again! :) Unfortunately testing and reviewing large refactors is probably not something that we have the capacity for at the moment. As the PR authors have not gotten back to us, I would actually suggest closing all the stale PRs, and we can revisit the issue and take up your offer in the future if we have a reviewer who can volunteer their time for it. @neslihanturan what do you think?

Closing: 2 years old and looks abandoned.