Present the proposal again?

This proposal got rejected five years and a half ago based on concerns that, from the outside, seem fairly hard to understand. Perhaps it would lead to the same result, but I feel like it's at least worth discussing it again.
I know there's at least one question I'd like to ask of people who previously rejected it: are your concerns worth five years of incorrect manual escaping in users' code? Given that this feature borders on security, similar to SQL injections, it's not a rhetorical question: it seems important for this to be answered.

I am happy to work on this again but suspect the results will be the same if the same people block it in the committee.

I would encourage folks to revisit this proposal, as five years has offered perspective into certain arguments blocking the proposal the first time around.
Summary: A safer and more powerful template literal tag is coming soon.

A short term fix that become a long term hazard is a common development strategy and often appears in libraries that become de facto standards. When no good long term solution is known at the time, they often become de jure standards as well.
However, when a better long term solution is known at the time, and subsumes all the functionality and convenience of the short term fix, I think the committee would be failing the community to admit the short term fix merely because the good long term solution is more work.
— https://github.com/benjamingr/RegExp.escape/issues/37#issuecomment-126722885

Has a better long term solution materialized? I’m not aware of RegExp.tag or anything like it shipping.
Summary: A less safe version is easy enough to invent as needed

The general feeling was that to be completely safe you need a context-dependent join operation. The feeling was then that if author code wants to do unsafe escaping, the function is easy to write, but if something is going to be standardized, it must be completely safe.
— https://github.com/benjamingr/RegExp.escape/issues/37#issue-98309281

Excusing the manner of safety to the former point, has it been easy or is it now easier to write this escaping function? If easy implied simple or obvious, then I think it would be hard to prove that developers well versed in RegExp would naturally write out /[\\^$*+?.()|[\]{}]/g or something totally equivalent once they realized they needed to escape dynamic text. If easy implied familiar or consistent, then I think these differing implementations across popular developer mediums demonstrate otherwise:
From this proposal:
/[\\^$*+?.()|[\]{}]/g

From MDN:
/[.*+\-?^${}()|[\]\\]/g

From the accepted StackOverflow answer:
/[-\/\\^$*+?.()|[\]{}]/g

I can probably just try and PR this into Node as a static utility since TC39 rejected it - would that help you two at all or are you  browser focused?

Having a version in node might help the living ecosystem develop a standardised solution. It's a good punt.

@domenic do you think having a utility for this in Node.js is fine or would that be seen as bad faith / detrimental to standardisation efforts?
(Just asking for your opinion/advice)
@oliverfoster
Bikeshedding, something like util.escapeRegExp?

Util seems about the only place sensible to my tiny brain.
util.escapeRegExp or util.escapeStringRegexp as it in the immensely well-used library escape-string-regexp? I'm sure you'll get feedback in any pr you make. Don't worry too much about the name.

OK, I want to do this with Domenic's blessing though - so let's give him a week to respond :]

I can probably just try and PR this into Node as a static utility since TC39 rejected it - would that help you two at all or are you browser focused?

I’m unfamiliar of the relationship between Node and TC39, so my opinion will be based on whether TC39 can revisit rejected proposals. My uninformed opinion is that this must go through TC39.
If TC39 does not revisit rejected proposals, then I like your idea to PR this to Node, for the ecosystem rationale shared by @oliverfoster. I am also browser focused. I don’t like it, tho.
If TC39 can revisit rejected proposals, then I strongly oppose this idea. Specifically, I wholly reject the idea of twisting the arm of our own browser and develop allies by knowingly forcing a compatibility issue upon them.
I hope my answer is sufficiently long and nuanced. 😅

@benjamingr i think putting anything in an engine that belongs in the language is detrimental, even if it means it takes longer to get the proper solution.
@jonathantneal anything can be revisited at any time.

@ljharb

@benjamingr i think putting anything in an engine that belongs in the language is detrimental,

I agree, which is why we are only discussing this after this feature was rejected from the language and we've gotten continuous requests for it by users.
@jonathantneal

I’m unfamiliar of the relationship between Node and TC39

Mostly respectful, some of the same people in both orgs. Node.js doesn't do stuff that isn't valid JavaScript and when we do stuff that might be problematic from the language standpoint (like recently the cancellation APIs) we coordinate it with TC39.
Moreover, a lot of the people there are knowledgeable so it's less of a matter of "what Node must do" (note, I don't speak to Node I'm one person working on Node) but "what Node should do".

Specifically, I wholly reject the idea of twisting the arm of our own browser and develop allies by knowingly forcing a compatibility issue upon them.

Node.js can add to its own exported modules whatever it wants though? IIUC - Adding a utility to core does not in any way "twist" anyone's arm nor would Node.js ever do things that "twist" the arms of spec bodies. I consider that extremely counterproductive and and faith.
In my experience good faith collaboration is what has worked well in the past.
Though note in this proposal I am "Benjamin, proposal author for a TC39 proposal" and not "Benjamin, Node.js collaborator" or whatever. I wasn't even in Node.js when I worked on this I think ^^.

Node.js can add to its own exported modules whatever it wants though? IIUC - Adding a utility to core does not in any way "twist" anyone's arm nor would Node.js ever do things that "twist" the arms of spec bodies.

I think the concern here is that if node adds util.escapeRegExpString and later TC39 arrives at wanting RegExp.escapeString, we either a) get two very similar functions with slightly different functionality, a loss for the ecosystem, or b) TC39 specifies the exact same behaviour so that node can export const escapeRegExpString = RegExp.escapeString. Avoiding scenario A will put pressure on TC39 to accept the precedent. It's not a lot (esp. since node can introduce a change to util with any major release), but still.

@bergus as soon as a language level solution exists* I'm sure Node will happily soft deprecate the utility:

Once it lands in V8 - expose it and put the util in "pending deprecations"
Next major - docs-deprecate the utility
Next major, runtime deprecate the utility (warning that can be silenced)
Next major - remove the utility.

I don't think this in Node.js will pressure TC39 TBH? Libraries that expose this functionality (needed almost every time working with dynamic RegExp) are very popular, every other language I checked implements this feature in the language or in its platform. I don't consider TC39 "pressured" 😅
My unwillingness to work on this without the "blessing" of Domenic boils down to:

I don't want to make a mistake and ship something broken.
I am not in TC39 so I don't know if there is background I am not aware of here.

*(less likely - and again I have very little motivation to push this as a util in Node without Domenic's blessing).

A TC39 member has reached me in private following this thread and indicated willingness to pick this up. I'll wait until the next TC39 meeting (January?) to give this another chance in spec land.

@domenic do you think having a utility for this in Node.js is fine or would that be seen as bad faith / detrimental to standardisation efforts?

Totally fine, and makes sense to me. Especially if you keep it in require("util").
Monkeypatching it onto RegExp as a static would be a bit more controversial, but if you're interested in doing that, we could open a discussion on whatwg/html about making sure all web global environments do the same thing. But I take it your proposal is for require("util"), so that's probably not necessary.

I hope you’ll forgive me. Sorry, I was errantly reacting to the idea that you would patch RegExp.escape into Node, and I see now that your suggestion was to add something behind a module. That’s a great idea, and I have no issues with it.

@benjamingr do you know when the committee meeting is going to happen?

@benjamingr do you know when the committee meeting is going to happen?

@mdevils 25.01.2021 - 28.01.2021

@mdevils 25.01.2021 - 28.01.2021

I've added an agenda item to this meeting's agenda.

I've added an agenda item to this meeting's agenda.

Today's TC39 decided to reactivate this proposal at stage 1, to explicitly investigate the problem area - not yet endorsing any particular solution (RegExp.escape is one possible one, as is a template tag function).
I'll update the readme to reflect that shortly, and this issue can now be closed.

Today's TC39 decided to reactivate this proposal at stage 1, to explicitly investigate the problem area - not yet endorsing any particular solution (RegExp.escape is one possible one, as is a template tag function).
I'll update the readme to reflect that shortly, and this issue can now be closed.

Here are the relevant TC39 28 January, 2021 meeting notes for those interested in the details of the decision to reactivate this proposal at stage 1:

Rendered: https://github.com/tc39/notes/blob/master/meetings/2021-01/jan-28.md#revisiting-regexp-escape
Permalink: https://github.com/tc39/notes/blob/ef7ebbb7c5ccf608486e705d1402928b881bc862/meetings/2021-01/jan-28.md?plain=1#L113-L206

What I found surprising reading that was that there didn't seem to be much discussion of use cases or the breakdown of how people are using it most often today. Perhaps this is only because those things had been discussed a lot previously, but (skipping a few steps of speculation) it made me wonder if objections to escape as proposed in this repo would soften if it had a very explicit name like escapeLiteralSequence.

I don’t believe there’s any need to further explain the use cases, not do i think the naming matters. Those objecting to the escape solution do so because they believe it’s a potentially dangerous footgun, even if that never comes up in practice.


DO NOT MERGE: Revert "Merge pull request #70 from openshift-bot/art-consistency-ope…

…nshift-4.19-ose-gcp-cloud-controller-manager"
This reverts commit c192187f00edfade3d4805be794f0e405f599bfe, reversing changes made to 7b60fffb9eabb5a27163213a1e9c995357d47c4c.

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-upgrade #2156 openshift/cloud-provider-gcp#71

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-upgrade openshift/kubernetes#2156


Fix controller setting

Checks

[ ] Debugging completed
[ ] Please debug me

Related Issue
This PR closes #129.

Codecov Report
Base: 82.76% // Head: 82.77% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (7a0f2cf) compared to base (b98c54b).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage   82.76%   82.77%
=======================================
  Files          50       50
  Lines        2240     2241    +1
=======================================
+ Hits         1854     1855    +1
  Misses        386      386

Impacted Files
Coverage Δ

necst/ctrl/antenna/pid_controller.py
87.50% <100.00%> (+0.13%)
:arrow_up:

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.

駆動試験済み


Removed Primary and Secondary from tailwind config

and replaced with blue-500 and red-500 where it was used

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


There are two bugs in monitoring all attributes of a responsive data defined by reactive

Vue version
3.2.37
Link to minimal reproduction
https://sfc.vuejs.org/#eNp9UrtuwzAM/BVCixPAD3QrHCdAf6BT0UmLYtOJA70gyc5g+N9LWWkatEEHGxTveEeRmtmbteU0IqtZ41s32AAew2gPXA/KGhdgBod9Tj/RhmHCHK4itGdYoHdGQUa1GddcSwxgZPcuFMI+lmyybBuB1mgfwKLzRq9I0tnMmqg1ZB9GZTmIE8Uvr8t2B1wDfavLJpXlsNF4/RRyJHsyWaMt7A8wR/KP7TdWRu0IRXMjsZTm9Exix/WSw9wh2hp6IT1SA7HppkrDoDHQIaCyUgSkE0AzaDsGmAplOpR7zlKPyZJBlUhHdwu8FfpA1pCuO88P9GUhn4g/KaEe7yW3Cz7Qm+reE8tZ2lShhC0vpE27XOfCb4DnjFRiJuZoYfHM2TkE6+uq8n0bX8DFl8adKopKN+owKCzRq+LozNWjI2HO8geNipITusKh7tCh+0/zF/WPbpRdaBVs+QIi+OMo
Steps to reproduce
1, create a reactive object
2, watch the object
3,change the object
3,display and compare the object new value and old value
What is expected?
oldValue is Old value
What is actually happening?
oldValue is new Value
System Info
No response
Any additional comments?
No response

You want to get the old value in the callback method parameter of watch, not just the new value

There are two bugs in monitoring all attributes of a responsive data defined by reactive: 1. The oldvalue cannot be obtained correctly; 2. The deep monitoring is forcibly turned on, and setting the deep configuration is invalid

Both of theer things are expected behavior and documented.

这是来自QQ邮箱的自动回复邮件。您好，我已收到您发给我的邮件，我会尽快给您回复。


[iOS][2.0.0] Not awake closed app when received voip call.

We use voip-push-notification & react-native-callkeep on iOS to awake app from background mode / closed state when received a voip call.
It work fine in background mode. But when app in closed state. Nothing happen, no notifcation, no automation awake app.
We met this issue from version 2.0.0 and react native 0.60.6. V1 and react-native 0.59 work fine.
any ones met the same issue with us? Can we resolve this problem?

Have you got any workaround for this?

Please read the new notes in the readme to see if there any missed part.
https://github.com/react-native-webrtc/react-native-voip-push-notification/blob/master/README.md#important-note

@william-normann  pls for me know how to create voip  to test react-native-voip-push-notification

same issue

Have you find the cause? I know ios 13.3 seems have issues, butsolved after upgrade to ios 13.4

I'm running into a similar issue. It seems like VoipPushNotification.wakeupByPush is false, and I'm not sure why.

Have you got any workaround for this?

As a workaround you can import { AppState } from 'react-native' and then basically just check that Platform.OS === 'ios' && AppState.currentState === 'background' instead of checking wakeupByPush.

Have you got any workaround for this?

As a workaround you can import { AppState } from 'react-native' and then basically just check that Platform.OS === 'ios' && AppState.currentState === 'background' instead of checking wakeupByPush.

It's the problem with iOS version < 13, I checked with iOS 12.
My work around is to send double voip notification (and of cause handle the duplication on client code, for me, I send APN messages with a flag to mark if a notification is a duplication one), so far it's working for me. Btw, ios 3 is working as expected, no need to apply the workaround.

It's the problem with iOS version < 13, I checked with iOS 12.
Btw, ios 13 is working as expected, no need to apply the workaround.

I was having the issue when testing on iOS 13.4

It's the problem with iOS version < 13, I checked with iOS 12.
Btw, ios 13 is working as expected, no need to apply the workaround.

I was having the issue when testing on iOS 13.4

Hi, I have the same issue in iOS 13.4.1 i can't wake up app.

did you guys even managed to use it with the app minimized? I'm struggling with it and dont find anything to make it work :(

The problem is that the method didReceiveIncomingPushWithPayload in AppDelegate.m doesn't get called when the app is in the background. This results in the system trying to invoke Callkit a few times but fails and it then drops all attempts to start your application on a background push (the console log will just show "Dropped on the floor").
To enable the retries to call this method you need to reinstall your application.
I'm really new at iOS-development so I have no idea why this method doesn't get called or how you call it from a push.

It's the problem with iOS version < 13, I checked with iOS 12.
My work around is to send double voip notification (and of cause handle the duplication on client code, for me, I send APN messages with a flag to mark if a notification is a duplication one), so far it's working for me. Btw, ios 13 is working as expected, no need to apply the workaround.

How exactly did you get this workaround to work? I've been trying this and it gives me weird bugs when the call is closed before the duplicate comes in

It's the problem with iOS version < 13, I checked with iOS 12.
My work around is to send double voip notification (and of cause handle the duplication on client code, for me, I send APN messages with a flag to mark if a notification is a duplication one), so far it's working for me. Btw, ios 13 is working as expected, no need to apply the workaround.

How exactly did you get this workaround to work? I've been trying this and it gives me weird bugs when the call is closed before the duplicate comes in

It's a little bit tricky that the duplicated push should be sent just after the 1st one came, like: send the 1st one, delay 1s, then send the 2nd one. 2 notification should contain the same uuid and in the code, you should call the api to show the incoming call UI with the same UUID ( that means 2nd one will be ignored if the UI is still showing because of the 1st one)
Hope this helps.

Finally got it to work.
RNCallKeep.setup(options).then(accepted => {
});
Needs to be setup in index.js. Or else everything just fails silently.

Finally "solved" it. I know nothing about iOS-development so my "solution" is probably pretty shitty. The problem is that the OS is waking the application before the javascript code initializes this lib.
I went into node_modules and this project (will have to upload the changes into a local git repo later) and then I changed the method voipRegistration to be static (+ instead of -) and removed
dispatch_async(dispatch_get_main_queue(), ^{
[self voipRegistration];
});
from RCT_EXPORT_METHOD(registerVoipToken) since this can not be called from the instance anymore.
Then instead of setting up voip from this library, you call it from didFinishLaunchingWithOptions in AppDelegate.m in your own project so that your app has time to set it up before didReceiveIncomingPushWithPayload comes.
So just add this line:
[RNVoipPushNotificationManager voipRegistration];
Somewhere before the return in didFinishLaunchingWithOptions.

Finally "solved" it. I know nothing about iOS-development so my "solution" is probably pretty shitty. The problem is that the OS is waking the application before the javascript code initializes this lib.
I went into node_modules and this project (will have to upload the changes into a local git repo later) and then I duplicated the method voipRegistration into a static one as well (+ instead of -).
Then I called it from didFinishLaunchingWithOptions in AppDelegate.m in my own project so that the app had time to set it up before didReceiveIncomingPushWithPayload came.
In conclusion:

Duplicate voipRegistration-merthod in RNVoipPushNotificationManager into another static one (+ instead of -)
Call [RNVoipPushNotificationManager voipRegistration];
Somewhere before the return in didFinishLaunchingWithOptions in your AppDelegate.m.

please check discussion in #59 and the test the fix in PR #69

Released 3.0.0, this should be fixed. Please check doc and test, especially didLoadWithEvents part.


Issues when comparing byte[] to byte[] in queries

This is probably related with #13260
byte[] is a reference type and 2 arrays of bytes aren't equal when they refer to different arrays. This is all fine, but it becomes a problem when using byte[] as a primary key.
MySQL (among others) do not have a data type to store GUIDs, so we store them as byte(16). EFCore translates this to byte[]...
The MySQL provider does compare byte[] correctly with another byte array (probably because they have internally made it a different type). The InMemory database does not, which is what we use for unit testing.
The "SequenceEqual" method does work on the InMemory implementation, but I'm not sure if this is a correct workaround.
In the past, Linq to SQL we had System.Data.Linq.Binary for this. This class implemented a implicit comparison to byte[].
Further technical details
EF Core version: 8.0.13
Database Provider: Microsoft.EntityFrameworkCore.InMemory
Operating system: Windows
IDE: Visual Studio 2017 15.9.4

@jeroenlandheer We fixed several issues with byte[] properties and the in-memory database for the 2.2 release. You say you are using version "8.0.13" but that's not an EF Core version. What version of the NuGet package do you have installed in your project? If it's not 2.2, then can you update to that and check whether or not the issues you are seeing are fixed?

@ajcvickers Thank you for your response. Don't know where that weird version number came from, but the package is EFCore v2.2. I've upgraded the app (and test project to v2.2 as well, but the issue is still there.
If I try .SequenceEquals(byte[]) I have no issues, when I use "==" it doesn't work.
I store the GUID in a table as a byte[] array, next the repository class compares that with a Guid from a different instance that it converts to bytes using ".ToByteArray()" The array's contents are the same but the references to the arrays are different.
    public async Task<SomeObject> GetAsync(Guid someId)
    {
        using (var entities = new SomeContext(configuration))
        {
            var item = await entities.SomeTable.SingleOrDefaultAsync(x => x.SomeObjectId == someId.ToByteArray());
            ...
	// item == null with the InMemoryDatabase and is not null with MySql database
        }
    }

If I do this then it works for both the InMemoryDatabase and the MySql database:
    public async Task<SomeObject> GetAsync(Guid someId)
    {
        using (var entities = new SomeContext(configuration))
        {
            var item = await entities.SomeTable.SingleOrDefaultAsync(x => x.SomeObjectId.SequenceEquals(someId.ToByteArray()));
            ...
	// item contains a record of SomeTable
        }
    }

Maybe this helps?

@jeroenlandheer I'm having trouble following exactly what you are doing. In EF Core 2.2, assuming the provider is working correctly, a GUID property should be automatically converted to a byte array if the provider does not natively support GUIDs. Does this not work, or did you not try it? If it doesn't work, then explicitly configuring a value converter should work--see https://docs.microsoft.com/en-us/ef/core/modeling/value-conversions
If none of this helps, then probably the best way forward would be for you to create a simple runnable project/solution or complete code listing such that there is no ambiguity and we can dig into whatever is not working.

@ajcvickers  I've created a repo with a unit test demonstrating the issue with the InMemory database.
https://github.com/jeroenlandheer/efcore-22-inmemorydb
I'll give your suggestions a try, I wasn't aware that there was a conversion for GUIDs in place.

@ajcvickers - Is this different from #13260?

@smitpatel Looks like a duplicate.

2.2 still fails to compare byte arrays using equals or sequenceequal

@jjxtra Indeed. This issue is a duplicate of an issue in the backlog that has not yet been fixed.


location.query changes on link hover, for effects inside link preload functions

Describe the bug
If I reference location.query from inside a route preload function, I'll see that signal change every time the user hovers over a link, even if they don't click that link.
This only happens for effects that live inside the preload function. Anything I return from the preload function behaves normally when accessed from the route component.
Your Example Website or App
https://stackblitz.com/edit/solidjs-templates-evsys4?file=src%2FApp.tsx
Steps to Reproduce the Bug or Issue

Create a route preload function
Create an effect that logs the signal location.query, provided by the arguments to the preload function
Observe that if you hover over any link on the page, the signal changes, even if the page's query params haven't actually changed.
Return location.query, or some derived value, from the preload function. Observe that it does not react to link hover in the component's scope.

Expected behavior
Signal only changes when address bar changes. Signal always reflects value in address bar.
Screenshots or Videos
No response
Platform

OS: Linux
Browser: Vivaldi, Chromium

Additional context
I discovered this while creating a resource that refreshes when the query params change.

Oh, bonus bug (or same one?): if the route preload function returns a resource that uses location.query as its source signal, the component never sees that resource update: Stackblitz

There are a couple things going on here. We support reactivity in the preload function as backwards compat with pre 0.10 versions. In those cases you should turn off preload globally. It just won't work properly. I don't believe it is the createEffect logging that is causing the additional logs but that we just run the whole function whenever you hover. This just run the preload function is at odds with the previous approach, but its why the previous approach never did preloading.
Under new best practices you shouldn't be making reactive primitives or returning stuff from preload function. It is basically only for legacy support.
location.query isn't the signal but the query is a getter object itself. So we don't detect if the query changes but rather if individual fields change. This is why stringify works as it accesses all the fields. Otherwise I would just recommend listening to the field you care about.

Ah, I didn't catch the semantic change with the move to load preload.
Re: createEffect: yep, now that I know what to look for, I can see that it's just the whole preload function running over and over.
Can you clarify what you mean by not "returning stuff" from preload functions? The docs (including the migration docs you linked) show returning a resource. What specifically is the legacy behavior I should avoid?

Can you clarify what you mean by not "returning stuff" from preload functions? The docs (including the migration docs you linked) show returning a resource. What specifically is the legacy behavior I should avoid?

Basically everything in that section of the docs. That was a bandaid to get the existing behavior back for those who couldn't upgrade.
What you should be doing now is use cache functions in preload and pass those to createAsync calls in the components.

Got it, thanks!


[Bug]: useCaseSensitiveFileNames is not provided to ServiceHost, leading to issues in case-sensitive OSes

Version
latest
Steps to reproduce

This needs to be run in a case-sensitive OS like WSL, Linux, or MacOS
Clone my repo here: https://github.com/ferdaber/ts-jest-case-sensitivity
Ensure that the cloned repo has at least one uppercase letter in its absolute file path
Run npm install, which will copy over some mock packages into node_modules
Run npx jest, and also run npx tsc
Verify that npx jest fails via a ts-jest diagnostic error, and npx tsc does not.

Expected behavior
There should be no error via npx jest since it should mirror how TSC typechecks
Actual behavior
The TS language service created by ts-jest was unable to resolve a specific
Debug log
{"context":{"call":null,"logLevel":10,"namespace":"ts:serviceHost","package":"ts-jest","version":"28.0.5"},"message":"readFile","sequence":173,"time":"2022-07-01T20:18:52.201Z"}
{"context":{"cacheHit":false,"logLevel":10,"namespace":"ts-compiler","normalizedFileName":"/home/fbudhidharma/dev/Case-Sensitive-resolution-issue/node_modules/typescript/lib/lib.scripthost.d.ts","package":"ts-jest","version":"28.0.5"},"message":"getScriptSnapshot(): cache miss","sequence":174,"time":"2022-07-01T20:18:52.201Z"}
{"context":{"call":null,"logLevel":10,"namespace":"ts:serviceHost","package":"ts-jest","version":"28.0.5"},"message":"readFile","sequence":175,"time":"2022-07-01T20:18:52.201Z"}
{"context":{"cacheHit":false,"logLevel":10,"namespace":"ts-compiler","normalizedFileName":"/home/fbudhidharma/dev/Case-Sensitive-resolution-issue/node_modules/typescript/lib/lib.dom.iterable.d.ts","package":"ts-jest","version":"28.0.5"},"message":"getScriptSnapshot(): cache miss","sequence":176,"time":"2022-07-01T20:18:52.203Z"}
{"context":{"call":null,"logLevel":10,"namespace":"ts:serviceHost","package":"ts-jest","version":"28.0.5"},"message":"readFile","sequence":177,"time":"2022-07-01T20:18:52.203Z"}
{"context":{"call":null,"logLevel":20,"namespace":"hoist-jest","package":"ts-jest","version":"28.0.5"},"message":"visitSourceFileNode(): hoist jest","sequence":178,"time":"2022-07-01T20:18:52.464Z"}
{"context":{"fileName":"/home/fbudhidharma/dev/Case-Sensitive-resolution-issue/src/index.test.ts","logLevel":20,"namespace":"ts-compiler","package":"ts-jest","version":"28.0.5"},"message":"_doTypeChecking(): computing diagnostics using language service","sequence":179,"time":"2022-07-01T20:18:52.484Z"}
{"context":{"diagnosticCodes":[2688],"diagnosticText":"\u001b[96msrc/index.test.ts\u001b[0m:\u001b[93m1\u001b[0m:\u001b[93m23\u001b[0m - \u001b[91merror\u001b[0m\u001b[90m TS2688: \u001b[0mCannot find type definition file for 'package-with-exports/globaltypes'.\n\n\u001b[7m1\u001b[0m /// <reference types=\"package-with-exports/globaltypes\" />\n\u001b[7m \u001b[0m \u001b[91m                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\u001b[0m\n","logLevel":20,"namespace":"TSError","package":"ts-jest","version":"28.0.5"},"message":"created new TSError","sequence":180,"time":"2022-07-01T20:18:52.485Z"}
{"context":{"logLevel":20,"namespace":"ts-jest-transformer","package":"ts-jest","version":"28.0.5"},"message":"created new transformer","sequence":181,"time":"2022-07-01T20:18:52.491Z"}

Additional context
I was only able to successfully replicate this in a simple project via a type reference into a package that is using the new exports package.json field, and with a node resolution of nodenext, but in my team's more complicated set up, the same error appears using nodenext but via a simple import { Value } from 'package' where package is only using the legacy main/types package.json fields.
After tracing through the TS compilation, it looks like the issue comes from how some lookups (depending on which code path within TSC it goes through) will attempt to call getCanonicalFileName to read files. This causes failures (again, depending on the code path which was very difficult to reliably replicate due to multiple layers of caching).
getCanonicalFileName relies on useCaseSensitiveFileNames to be passed in to the ServiceHost instance when creating the TS service host. Currently it is not being passed in so TSC will default to lower-casing all filepaths. This is what causes the typechecking errors because TSC ends up being unable to properly read files.
I was able to verify in my own code (and in the replication repo) that passing in the useCaseSensitiveFileNames method resolved all issues:
const fs = require('fs'), process = require('process');
const isCaseSensitive =
  process.platform === 'win32' || process.platform === 'win64'
    ? false
    : fs.existsSync(__dirname) !== fs.existsSync(__dirname.toUpperCase())

Environment
System:
    OS: Linux 5.10 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
  Binaries:
    Node: 14.19.0 - ~/.nvm/versions/node/v14.19.0/bin/node
    Yarn: 1.22.5 - /mnt/c/Program Files (x86)/Yarn/bin/yarn
    npm: 6.14.16 - ~/.nvm/versions/node/v14.19.0/bin/npm
  npmPackages:
    jest: ^28.1.2 => 28.1.2

I'm happy to drop in a PR since it's a fairly straightforward change. I do notice that all the code regarding the compiler is inside a legacy directory so I'm not sure if the plan is to move away from using the TS compiler programmatically

@ferdaber feel free to open a PR. We still support bug fix for legacy:)

Ah I was stuck on figuring out how to test this so never submitted the PR. Thank you for fixing it! <3

I didn’t know how to test it either because following your reproduce steps I didn’t get anywhere so I just blindly fixed it 😅


Copy /paste placeholder text in fields

Composer has detailed examples inside the properties fields, but they cannot be selected (copy paste to use as a starting point) and once anything has been typed in there, the original suggested text cannot be brought back
Expected: ability to use placeholder text from the property fields as a starting point that can be edited (and or copied/pasted)

@mareekuh we are using the placeholder property from the HTML5 specification. I would assume that all browsers do not allow copying these values, but it is not something we can control.
We could use those values as default values, but that wouldn't be helpful in most cases. Some other options to consider are adding the examples to the field intellisense (they would show up as suggestions when editing the field) or adding the examples to the field tooltip where user's can copy them.

Closing as designed


Contributors page

Made the frontend of the contributor's page, as it an open-source helps the user to track the people who contributed to the projects.

design for the page is given below
it should be responsive
try to make it with the same font.

Can I work on this issue?

@Palak-137 should this contributors page be linked to CREDITS, and i am assuming that top three contributors be displayed in the contributors page, please let me about my assumption

No @rakeshhotker, It will display all contributors
You have to make a template and we will a design page for storing those github username, pic and name.
For now make it static

Latter in #124 We will make it dynamic

should i link the contributors page to credits, so as to display that page when credits is clicked?

Yes

@BRAVO68WEB am having to rebuild the whole app after making changes to be able to see them, is there way to do hot reloading, without changing the backend, as am just following the guidelines for making changes to frontend and thus i cd'ed to frontend and working on frontend

@BRAVO68WEB should i hardcode the contributors or use github api to fetch and display contributors data

Hardcode

But as a function template to which we need to pass array and it automatically create cards
If you can't then also it's ok

@BRAVO68WEB made the contributors page following the design, the cards can be created using array.map and passing the details to the divs mentioned, although i hard coded it for now. should i create a pull request? do let me know what all i should take care of before creating a pull request

@all-contributors please add @rakeshhotker  for code


Add video to main README to show it off!

I want to work on this issue , Can you guide me through to which video needs to be added to the Readme file ?

This isn't really an issue, more like a todo that I need to take on.

done!


multiple plans!

Finish implementing the multiple plans feature!

Format modals according to Figma
Add TextInputModal.vue that saves a text input. Component of CopyPlanModal.vue, and EditPlanModal.vue
Write methods that will be used to call firestore functions
Call firestore functions to create/edit/delete plans
Confirmation modals when plans are correctly added/renamed/removed
Fix bug so that Firebase doesn't randomly delete plans anymore
Fix bug where the correct plan is not displayed

Remaining TODOs:

Write Cypress e2e frontend tests

Documentation will be here: https://www.notion.so/courseplan/Multiple-Plans-c01b61f8a7a9473781539dc4ec24a5d9

this PR is quite large haha, is this meant to be branched off of something else other than main? like https://github.com/cornell-dti/course-plan/pull/858

Couple of things:

I think the renaming probably should disallow for empty strings, and also, I didn't get a screen recording of this, but when I first logged in, my plan was 'undefined' so maybe changing the default to be 'Plan #1' or something?
https://github.com/cornell-dti/course-plan/assets/53061040/3c51eb17-da5b-4e93-8465-e08528afb6e0

when the name is empty and I try to copy it, it looks like I don't have anything selected, even though I have the empty name plan selected, so disallowing the text to be empty solves this too!

A few frontend nits but the spacing on the left is a little small

I think it'd be best when creating a blank template that we still create 8 empty semesters instead of the user having to go in and making them one by one

Otherwise, this is looking awesome!! Very excited 😄


Support LaunchImage and Blurr together in IOS

Merged from stevenspiel and made some changes to make both LaunchImage and Blur work together (Image on top of Blur)

Hi @eddyuan any updates for this PR? Is it read to merge?


Emph with custom class

Can Emph be made take a custom Attr?
I would like this capability in order to define FontAwesome icons when using Semantic UI which requires the HTML tag to be <i> (rather than anything else, say <span>).
In other words, can the following be generated from a Pandoc AST?
<i class="icons tag" />

Found a workaround with direct font-awesome style.


Dose cosine decay speed up the training?

I noticed that the original YOLOv3 uses steps decay,and  your v2 has a faster training than the original YOLOv3. Or just because you use tensorflow and the original use darknet?

@gooodooo  I don't know ...

I think Adam works,original yolov3 use SGD


Is it possible to have an FnOnce action closure

In the code there is a trait bound that suggests that the action closure needs to be na FnMut. Is there a reason an FnOnce could not be used instead?

Hi! Given that the action will be executed one or more times, it needs to be at least FnMut for this to work. FnOnce will cause the closure to be consumed on the first execution, which prevents re-running the action on retry. Hope that helps!

Oh of course, that make sense. Thanks for explaining this


Consider replacing cosine similarity with string distance measure

I'm a bit dubious about cosine similarity as the most appropriate string distance metric for initial deduplication (we implement it because it was Hangen and O'Brien's approach) - we're not interested in semantics, but simpler character distance. (And, at least intuitively, cosine similarity may cause erroneous matches when portions of the address appear in the LLC name, etc.)

Retained cosine similarity, but moved to an approach where we deduplicate names with cosine similarity, but then constrain those clusters by grouping with address and linking to a naive match (to address cases where a naively matched name is linked to the same address).


Am I installing correctly?

Hello, I am new to NixOS and thus appreciate the installation script. However, when I run it and reboot, i am directed to a hyprland screen with a message saying that i'm using an autogenerated config and nothing else has changed.
What am I doing incorrectly?
Thanks

Did you perhaps install this on a system that was already using hyprland before? In that case, the config files under ~/.config/hypr already exist and the installation cannot overwrite them. Basically, home-manager would create the file ~/.config/hypr/hyprland.conf based on the nix code, but it cannot overwrite existing files. Try to delete the files and possibly port all your changes into the necessary nix files (found in the repository at modules/home/hyprland) in case you already have some custom options set for hyprland.


link to LICENSE in README

Thanks dude!

Happy contributing! :smile: Love that you're a part of Mozilla! I was too, once upon an intern.


Check the gateway version when loading configurations from redis

Coverage decreased (-0.09%) to 74.419% when pulling 881d712340441b9e311d0511366c38d9d1c2b876 on thiagobustamante:master into b172142fb103a1ace5790cc9eed75c068c03f7aa on Leanty:master.


As a forgetful user, I want to track my expenses using the app

I want to know how much money I have spent over a period of time / overall use of the app

Closed. Refer to PR #99.


Feature/school choice

I wonder if we can't use the Async Creatable from this example. This gets us the advantage of a built-in loading message, and prevents creating a new school whilst the list is loading.
loadOptions would need to make the API call, and then in .then(...) do the transformation currently done in the useEffect watching schoolSearchResults. This would return the promise that the async-creatable can then use to determine the loading stuff.
formatCreateLabel could be used to change the Create ... text to be Use '...' as your school name. We may eventually want a warning that these won't count for events etc.


fixuse isManagedTable instead of check table type

Proposed changes
Issue Number: close #xxx
The TableType of olap table is OLAP, and the TableType of materialized view is MATERIALIZED_VIEW. Many functions of olap are required for materialized views, but many previous functions filtered out materialized views by determining whether the TableType is OLAP and need to be changed to using TableIf.isManagedTable() to determine
not allow recycle mv
not allow recycle partition in mv
will ignore mv when recycle db
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run feut

run cloud_p1

run buildall


Slack notification functionality on fail

This add's the ability to send a slack notification to a slack webhook, when the dependency analyze fails

Hey - thanks for the PR! I will be merging this before the next release.  I just need to update the documentation in the primary ODC repo - I'll be leaving this open as a reminder until I get the documentation updated.

Just to make sure I am creating the correct documentation - for this to work people would have to create their own web hook for slack to receive and post these messages?

Yes, you have to create an incoming webhook and you have to specify that in the slack configuration block. In this example the slackweb hook url is a system propertie
  dependencyCheck {         format = 'ALL'         failBuildOnCVSS = 7         suppressionFiles = ["$rootDir/gradle/owasp/exclude.xml"]         outputDirectory="build/reports/owasp"         slack {             def slackWebhookUrl = project.gradle.startParameter.systemPropertiesArgs['slackWebhookUrl']             enabled = slackWebhookUrl?true:false             webhookUrl = slackWebhookUrl         }     }


GROOVY-8843: Fix illegal reflective access within o.c.g.vmplugin.v7.J…

…ava7

I wish the PR could be refined and merged soon, massive warnings drive me crazy 😖

I will add it soon and it gets rid of one set of warnings but only to
reveal the next set which we haven't progressed yet.
On Tue, Dec 11, 2018 at 11:37 AM Daniel.Sun<EMAIL_ADDRESS>wrote:

I wish the PR could be refined and merged soon, massive warnings drive me
crazy 😖
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/groovy/pull/811#issuecomment-446040029, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AARF0OjDDoa4XJUwuheTurxXBZdgHkTaks5u3wxXgaJpZM4Xbzw5
.

Hello, I'm trying to implement the API test automation using rest assured in a project where Java 11 have been used.
and I'm having the following warning when I execute the code

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/C:/Users/myildirim/.m2/repository/org/codehaus/groovy/groovy/2.5.6/groovy-2.5.6.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

The code is simple as follows

package com.fieldcode.absenceservice;
import org.junit.Test;
import static io.restassured.RestAssured.given;
public class AbsenceApiTEST {
@Test
public void absencesAvailability(){
given()
.when()
.head("http://localhost:8082/rest/absences/")
.then()
.assertThat()
.statusCode(200);}}

related dependencies

<dependency>
  <groupId>io.rest-assured</groupId>
  <artifactId>rest-assured</artifactId>
  <version>4.0.0</version>
  <scope>test</scope>
</dependency>
<dependency>
  <groupId>io.rest-assured</groupId>
  <artifactId>json-schema-validator</artifactId>
  <version>4.0.0</version>
  <scope>test</scope>
</dependency>
<dependency>
  <groupId>junit</groupId>
  <artifactId>junit</artifactId>
  <version>4.12</version>
  <scope>test</scope>
</dependency>

@emre-yildirim @paulk-asert
Current solution still tries to access private Lookup(Class<?> lookupClass, int allowedModes), so the illegal access warnings will still appear. I suggest to forbidden illegal access when using indy since Groovy 3.0.0.

 You can safely ignore them or if using the command line tools, you might want to use the GROOVY_TURN_OFF_JAVA_WARNINGS environment switch.

This does not work for me... I have set the environment variable and still get the warnings...
$ env | grep GROOVY
GROOVY_TURN_OFF_JAVA_WARNINGS=true

...and when I run FileBot I get...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/usr/share/filebot/jar/groovy.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Here is my system information...
FileBot 4.9.0 (r6899)
JNA Native: 4.0.1
MediaInfo: 19.09.20200314
p7zip: p7zip Version 9.20 (locale=en_GB.UTF-8,Utf16=on,HugeFiles=on,4 CPUs)
unrar: UNRAR 5.30 beta 2 freeware
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2020-03-02 (r625)
Groovy: 2.5.8
JRE: Java(TM) SE Runtime Environment 13.0.2
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM

Thanks,
Paully

Please try 3.0.2

How do I do that for FileBot which requests the groovy amc plugin remotely?
https://github.com/filebot/scripts
Thanks,
Paully

The general answers to your question are:

use JDK8
move to a later Groovy version
ignore the warnings (they don't affect any operation)
alter the startup scripts to turn off warnings (FileBot seems to have some of this in place already, maybe it could be extended)

I don't really know much about FileBot. You could contact the authors and ask them to upgrade Groovy. But just having a quick look, it does look like a FileBot install (I looked at portable version) has a jar directory. You could simply replace the 9 groovy jars in that directory. You could try with 2.5.10 first and if that doesn't work, try 3.0.2. Make sure to back up your install before tweaking it.

Thanks for your suggestions, I tried both of those versions and neither helped.
I also updated FileBot to the very latest version which now uses Groovy 3.0.2 by default and that still had the WARNINGS when using Oracle Java 12.
So, I have gone back to OpenJDK 8 for the time being and all is fine now.
Paully

When you used Groovy 3.0.2, what warnings did you see?
Could you submit a JIRA issue to track it?

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/usr/share/filebot/jar/groovy.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

How do I submit a JIRA issue?
Newbie :-)

How do I submit a JIRA issue?

Here is the link to JIRA:
https://issues.apache.org/jira/projects/GROOVY/summary
Please provide a sample code to reproduce the issue. Thanks!

Please provide a sample code to reproduce the issue. Thanks!

Do you mean tell the how to use FileBot ?!

The target of the sample code is to reproduce the issue

The GROOVY_TURN_OFF_JAVA_WARNINGS environment flag would have only worked if FileBot called into the Groovy startup scripts which it doesn't. You'd need to change possibly one of the ini files in FileBot to try to do similar things to what Groovy's startup scripts do.
With respect to steps to reproduce, yes it would be helpful if you could give us some simple steps we can follow to reproduce the issue, e.g.:

install FileBot (link to instructions)
run this command: 'some command here'

I don't think any of us has used FileBot before and this would speed up our ability to reproduce locally so we can debug further.


Fix errors in 'build' script directory

Fix errors in 'build' script directory and reenable in CI build.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 44.314%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/book/bookTreeView.ts
2
38.71%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
31527

Relevant Lines:
65981

💛  - Coveralls

Fixing build break from vscode merge.


Broken examples due to new apiCheck.js release

Hi,
I'm new to angular-formly and was looking into some examples today on angular-formly.com site and wanted to let you know that examples are broken since some hours probably due to new release of apiCheck probably as dist files name changed - at least that's what it complaining first.

Thanks for letting me know. apiCheck just had a breaking change and I forgot that all the examples run off of master. I'll go fix those now!

Fixed. Thanks again! I really need to develop a better way to keep all of the examples dependencies in one place. It may be nice to have them all run on the latest stable version somehow...

Thanks to you for ultra quick response and maintaining this nice looking library and all your other Angular activities as well... time for some squats! ;)

:smiley: haha! which talk did you see?

"JSON Powered Forms" from NG-NL 2015 - not live sadly (via YT) but squats are done ;)

Haha! The exercise lives on! Thanks for using angular-formly. Please let me know if you have any other needs!


Make sure steeef always updates git information

Please follow Zim's code style guidelines.
steeef would not update the git information if we stayed in the same directory. Fixes #66

I'm not sure what your intention using PR_GIT_UPDATE was in the first place, but I don't think only updating the git status on cd is a good thing to have.

I was not the creator of this prompt, I merely integrated it into zim. I understand the issues with it only updating the git status when a literal git command is called, which is exacerbated by the fact that many people use the git aliases. The ultimate solution here is to update the git repository status like (I think every?) other prompt updates. I'd really like to make them consistent.

Yes agreed. This is just a dirty fix, but in my opinion its enough for a fast hotfix.

Ah, now that I've had time to read the code in context, I approve of this change. From the short diff in GitHub I thought it was just setting an empty variable in an if statement for no reason. I'll PR shortly and close this and #66. Thanks for the fix!


fix: fix slice init length

What this PR does / why we need it:

The intention here should be to initialize a slice with a capacity of len(res.Report[0].LV rather than initializing the length of this slice.
The online demo: https://go.dev/play/p/q1BcVCmvidW
Does this PR need to be backport to the previous release branch?:
NONE

/lgtm


Add the secp256k1 and secq256k1 curves

Description
Relies on https://github.com/arkworks-rs/algebra/pull/469. When that one is merged, we will need to update the Cargo.toml to point to the master branch of algebra.
A change is needed to fix the constraint tests.
Closes: #36
It also makes the branch secp256k1 obsolete. @npwardberkeley

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

N/A:

[ ] Wrote unit tests
[ ] Updated relevant documentation in the code

Instead of implementing it on BigInt320, how about we port the techniques from the crrl library? That avoids allocating an extra limb.
Also, we can port the specialized arithmetic from the base field over.

@Pratyush Let me create an issue to cover this topic, and probably for this PR we will just let it be this.

This PR is ready.

Sources added.

Fixed. I incorrectly put the secq one in the secp. Now it is fixed. For secq I think that thread is the citation that we generally use when referring to secq.

I deleted the secp256k1 branch as well. (@npwardberkeley Nick Ward's  previous attempt)


problem about train

when i run gan_lstm.py,a problem happened.
AttributeError: 'generator' object has no attribute 'next'

@zhangbaijin
Good day!
Does it fix your problem?
https://stackoverflow.com/questions/48848081/attributeerror-generator-object-has-no-attribute-next

yeah，thanks a lot------------------ 原始邮件 ------------------
发件人: "Trinh Quoc<EMAIL_ADDRESS>发送时间: 2019年12月13日(星期五) 中午12:47
收件人<EMAIL_ADDRESS>抄送: "zhangbaijin"512631874<EMAIL_ADDRESS>主题: Re: [crashmoon/Progressive-Generative-Networks] problem about train(#5)
@zhangbaijin
Good day!
Does it fix your problem?
https://stackoverflow.com/questions/48848081/attributeerror-generator-object-has-no-attribute-next
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Couldn't implement multiple loaders

Couldn't implement multiple loaders in multiple components on a single page through web services. Getting error as:  Cannot find the loader of undefined.
Please help!!
Thanks

Hi @varpitoo, can you provide any code example, use case or live example like stackblitz please?

Hey @maximelafarie , thanks for replying.
I want to implement multiple loaders on various components of a page  which I implemented using different identifiers.
Is there any way that we can accomplish it using one identifier or any other better way..!?
Thanks

Hi @varpitoo, after this long time, it has been officially fixed in #12, and a new 2.0 release will be published really soon! 👌
Cheers! 🖖


Cannot bind argument to parameter 'LiteralPath' because it is null.

The 'home' environment variable do not exist in Windows 10 ?
Tested on MS Azure :
Microsoft Windows [Version 10.0.10586]
Microsoft Windows [Version 10.0.10240]

This declaration resolve the problem :
$env:home='C:\Users\Laurent'

That's a dumb mistake on my part.  It should be just $Home.  I'll fix that tonight.

This line is not affected ?
 $gitConfigPath = Join-Path $env:Home '.gitconfig'

Yes it is.  Late night fix for the last one - missed this one. It is fixed now.  Thanks!


docs: readme fix, use jwt_svids instead of jwt_svid_file_name

the jwt config vars have changed,
the documentation in the stanza above is correct but the examples still reference the older config options
this

this commit seems to be where the fields changes, https://github.com/spiffe/spiffe-helper/commit/8d4d3ab0cd911adf77c3329474e3eb4a0d7db1a3

happy to help.
we're making great use of spiffe-helper w/ our federated oidc.  the jwt features were really needed by us


case sensitivity - try # 2

this is a second attempt to do case sensitivity
the thing im most unsure about is the fact that when some unicode characters are "lowercased" they become strings. since this library is built on the idea of single characters only, the code just Panics if you try to lowercase one of those unusual unicode characters that becomes a string, and you have full "case insensitive" enabled (as opposed to case-insensitive-ascii-only).
thanks

Thanks for revising the pull request!

the thing im most unsure about is the fact that when some unicode characters are "lowercased" they become strings.

A solution could be collecting whatever to_lowercase yields into a string and treating that as the character identifier. This would require changing the HashMap key type and updating the version number since it would change the library's interface.
In any case this is an improvement which is fully compatible with the previous version's interface, so I'll merge it and pass it through the rustfmt linter which is the only test that fails.
Great work!


Use torch.ao.quantization instead of torch.quantizaiton

Same as #4551 but without black conflicts
I just did some brutal sed -i "s/.../..." so I might have done something wrong. @z-a-f please double-check that these are the intended changes :)

We expect the torchvision main branch to work with pytorch nightly, we don't need it to be compatible with previous (or even currently stable) versions

The reason https://app.circleci.com/pipelines/github/pytorch/vision/11088/workflows/c3d06578-6137-4d13-8f38-7342e02c2148/jobs/853515 is failing is because there is a dependency on 1.11.dev09+.

I tried to investigate why this is failing. It seems that cmake on Windows with GPU installs a very old nightly of PyTorch (1.11.0.dev20210929) that possibly doesn't contain the necessary change on the quantization namespace.
It's worth noting that the Windows Cmake with CPU picks up today's nightly (1.11.0.dev20211111) and works without issues.
Upon further investigation, it seems that the last available release of win-64 with CUDA 10.2 happened on 20210929. Since Cmake builds using CUDA 10.2, we are having issues.

This should now hopefully be resolved after #4945


Add Title to signin.html

The new sign-in page looks awesome, but it lacks a title that displays our app name.
It would be better to have a title on the sign-in page above 'Sign In' and 'About This Project'.

Should've linked a pull request, but here is the commit:
https://github.com/sudokim/skku-web-chat/commit/127695b77b0866ced1914b1d239c5dda90514157


Github actions deploying only to production instead of preview environments

Describe the bug
I have noticed the last few github action builds have been deployed to the production website instead of the preview environment.
The workflow file hasn't changed and the branch is not the main branch.
This seems to have happened since the docker image at mcr.microsoft.com/appsvc/staticappsclient:stable was updated.
The last successful run was when github actions was using the docker image with a sha digest of:
6e8c2f7004cfd75ccbf2d1f5a402999432989eecd692d5536d47d46a07bb22ff
This issue started happening since the stable docker image was updated with a sha digest of:
870e5b73cf8d832615253d71b5834563b581a3fdf1a3defc26ccdfa264b37235
Github actions
- name: Build And Deploy
        id: builddeploy
        uses: Azure/static-web-apps-deploy@v1
        with:
          azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_BLUE_COAST_044CD3B03 }}
          repo_token: ${{ secrets.GITHUB_TOKEN }}
          action: "upload"
          app_location: "/"
          api_location: "api/api"
          output_location: "dist"
          production_branch: "main"

Screenshots
This is what used to happen:

And now it's not going to a develop preview environment:

Hopefully this issue can be fixed. Happy to provide more details if needed.
Really enjoying Static Web Apps by the way. Great work!

@andrewreeman Thanks for reporting this, we found the issue and working on the fix, should be out soon!

Thanks guys that's great to hear. Happy to test it out when it's available


vdk-heartbeat: trino ingestion test

The test sends object for ingestion and then verifies
whether the object has been ingested.
Testing: tested manually against ETL and Trino
Signed-off-by: Miroslav Ivanov<EMAIL_ADDRESS>

See if you can update the README to make it easier to users to use it in different scenarios. Maybe even describe the scenarios? But either way it looks good to me. Thanks for taking the change now we will have more confidence that ingestion works :)

Sure, thanks :)

See if you can update the README to make it easier to users to use it in different scenarios. Maybe even describe the scenarios? But either way it looks good to me. Thanks for taking the change now we will have more confidence that ingestion works :)

Sure, thanks :)

Done.


Adding flag to enable scripting languages to write a raw HTTP response

LGTM

looks good.  Maybe add sendRaw(body) and raw() as methods to response.js

Good suggestion, @mamaso.  Added that.

:ship:


[setup.bat] change NSTOOLS_URL in setup.sh/setup.bat

Hi and thanks a lot for this library and congrats for V2
I'm facing issue related to build nstools on windows (MSVC 2019 14.28)
For fetching nstools the below url is used
git@github.com:agenium-scale/nstools.git
Which seems to require some user specific key
Changing to
https://github.com/agenium-scale/nstools
Solve the pb

Hi Thomas,
Thanks, I hope that v2 will be useful to you. Cocnerning the issue you are right. I focused on the Linux part of it and forgot to change the Windows script. I will do it as soon as possible.


Weighted Pearson, Spearman, and R2 score

What does this PR do?
Fixes #1235

Before submitting

[x] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

Did you have fun?
Make sure you had fun coding 🙃

I’m adding a weighted version of Pearson right now and updated the pearson_corrcoef function to take in an additional optional argument weights. When testing, I am getting a failure due to pearson_corrcoef() got an unexpected keyword argument 'weights' even though I’ve modified the function definition for pearson_corrcoef.
I tried debugging test_pearson_corrcoef_functional  to check the signature of the imported pearson_corrcoef and got <Signature (preds: torch.Tensor, target: torch.Tensor) -> torch.Tensor> (missing weights: torch.Tensor).

@matsumotosan I have taken care of the testing now, such that inputs gets correctly send to the respective input.
Now the tests are only failing due to some values error in relation to the shape checking.

@matsumotosan @SkafteNicki, how is it going here? Could we have it for the next 1.1 release?

The docstring for final_aggregation contains an incomplete reference to some sort of equation to compute the aggregated statistics. Would anyone happen to know where this is?


Revert Cypress yarn.lock while trying to debug the issue the hanging issue

See some investigations here: https://github.com/cypress-io/cypress/issues/17627

jContent does not seem to be hanging anymore, closing the PR for now.


change excel format as Text using XLSX

i have issue when i create excel file i want to concert all file and all columns into text or set format text
in this module we have a option Cell Object int this there is a proper t set to ‘s’(Text) but example not given that how to set .
Please Check the concern

If you want to set the format to "Text" rather than "General", set the property z: "@" on the text cells (t: "s").  The z field is the "number format" and setting the format to @ treats the value like text.


bug [ionic5]: Swipeable Modal animation and overlap on parent page.

Bug Report
Ionic version:

[] 4.x
[x] 5.x
Current behavior:

Tested on: Iphone 6 iOS: 12.4.4
ISSUE:

Parent page -> it doesnt have smooth animation for border-radius.
Sometime modal will open without any animation.
Sometime modal will overlap parent page.

Reproduce Video: https://youtu.be/RMYudiq9Dlc?t=20
Expected behavior:

Parent page -> should have smooth animation for border-radius.
Everytime i open modal it should have animation.
It should not overlap parent page
Steps to reproduce:

Related code:

Repo: https://github.com/indraraj26/ionic4-starter-tabs-sidemenu/tree/ionic-5
Dashboard: Click on first ion-item to open swipeable modal.
insert short code snippets here

Other information:

Ionic info:

ionic info

Ionic:

   Ionic CLI                     : 5.2.3 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 5.1.0-dev.202003031524.f64b142
   @angular-devkit/build-angular : 0.801.3
   @angular-devkit/schematics    : 8.1.3
   @angular/cli                  : 8.1.3
   @ionic/angular-toolkit        : 2.0.0

Cordova:

   Cordova CLI       : 8.1.2<EMAIL_ADDRESS>   Cordova Platforms : ios 4.5.5
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 4.1.3, (and 4 other plugins)

Utility:

   cordova-res : not installed
   native-run  : 0.2.8 (update available: 0.3.0)

System:

   ios-deploy : 1.9.4
   NodeJS     : v12.13.0 (/usr/local/bin/node)
   npm        : 6.12.0
   OS         : macOS High Sierra
   Xcode      : Xcode 10.1 Build version 10B61

https://github.com/ionic-team/ionic/issues/20608

Thanks for the issue. Can you provide some clarification regarding the performance issues you are seeing? I am testing your repo on an iPhone 5s on iOS 12.4 and do not see the behavior you are reporting.

Hi @liamdebeasi  , Sometime i do not see parent page animation (border-animation transition) as you can see in video.
Reproduce Video: https://youtu.be/RMYudiq9Dlc?t=20
Lets wait for other to comment regarding this animation issue.

Thanks for the follow up. I understand the issue regarding the animation; however, I am unable to reproduce the issue. Can you double check the repo you have provided to ensure that it reproduces the issue?

https://github.com/ionic-team/ionic/issues/20851


tests: add name constraints integration test.

This is a follow up to https://github.com/rustls/webpki-roots/pull/39 that adds a basic integration test for trust anchors in webpki-roots with name constraints.
The general idea is that for each name constraints extension we:

parse the name constraints with x509-parser, verifying that the encoding is well formed and contains something approximating what we expect (e.g. at least one permitted subtree, no excluded subtrees).
convert the name constraints into the form rcgen expects for certificate generation parameters.
issue our own trust anchor CA certificate with the name constraints from the webpki trust anchor.
for each permitted subtree base dns name in the name constraints we use our generated CA to issue end entity certificates that will be permitted, and rejected by the name constraints.
we then translate our issued CA back to a webpki trust anchor, and use webpki to verify each of the permitted and rejected end entity certificates, asserting the result matches what we expect for the name constraint.

Checking out v0.25.1 and backporting this test identifies a problem with the KamuSM root name constraint, finding no subtrees after parsing:
running 1 test
test name_constraints ... FAILED

failures:

---- name_constraints stdout ----
thread 'name_constraints' panicked at 'empty permitted subtrees in constraints', tests/verify.rs:142:5

With the fix from https://github.com/rustls/webpki-roots/pull/39 the test passes.

cpu force-pushed the cpu-name-constraint-integration-tests branch from d817342 to 99c5e77

Sorry for the force pushes. Just tidying up small things (stale comments, bad var names, etc) I noticed reviewing this after opening the PR. All done now.

Going to merge this w/ one review since it's only test code. Thanks!


Add transition documents for current JotunnLib/ValheimLib users

We should add a section to the documentation, with code examples, that explains how to transition existing mods from ValheimLib and JotunnLib to the new combined Jotunn lib.
Requirements:

[ ] Transition guide for JotunnLib
[ ] Transition guide for ValheimLib

Redundant documentation. Anything that belongs in a "transition" document, also belongs in the tutorials. Just keep the documentation unified in one place instead of designing it around a slightly different approach. The developers already have existing code and the managers for the most part remain in the same style for JL, and entity abstractions are the same for VL. Any confusion for transition can be resolved in the existing documentation.

Yeah, we miss our core audience if we have no explicit transition document. we may have made "fresh start" easy, but devs wont be excited to make progress unless they can also transition easily.

Also: a quick start. "Create Environment.props, download nuget, ???, profit"
Without Env.props the project does not load anymore. Thats, ummmm, not beneficial?!

That can be resolved with a conditional import in the csproj

base is done in #165 and #166.


chore: switch to Std.HashMap and Std.HashSet almost everywhere

This removes every use except for ShareCommon which I will do as a follow-up.
This is very likely to break some users of the Lean API downstream.

!bench

!bench


[Coverity CID: 183486] Null pointer dereferences in /tests/net/traffic_class/src/main.c

Static code scan issues seen in File: /tests/net/traffic_class/src/main.c
Category: Null pointer dereferences
Function: address_setup
Component: Tests
CID: 183486
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

False positive


Speed up sync on big mysql table

Hi, is there any easy way to speed up importing data into ES? I have table with 2 500 000+ rows and it tooks more than week to sync. It's slow because of 2 causes:

mysql is slow on pagination, it tooks about 15sec just to get next 500 results when its at the end
it's not possible to split table into multiple processes while sync

So i think there could be solutions to this like

script it will take ID of last synced row and use WHERE id > $latestID
there could be possible to set starting and ending ID of rows

Do you have some script to achieve this, or ideas how to do that easely? thx

Hi @PayteR, you can use queues to speed up processing. Have a look here to learn how to configure a queue driver. Since you are using queues, you can scale processing power by increasing amount of consumers.

Hi,
In fact @PayteR is right, even if you use queue driver. Because when you use the queue driver, it will take very very long time to chunk all the results of a big mysql table. For my 6 millions rows table it took about 6 hours with queue driver to achieve.
I implemented a solution for this (this solution needs to use queue driver).
First create a job that will search some of your model instances and then creates MakeSearchable queues.
`
class SeedYourModelJob implements ShouldQueue
{
use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;
protected $yourModelIds;

/**
 * Create a new job instance.
 *
 * @param array $yourModelIds
 */
public function __construct($yourModelIds)
{
    $this->yourModelIds = $yourModelIds;
}

/**
 * Execute the job.
 *
 * @return void
 */
public function handle()
{
    $chunks = YourModel::find($this->yourModelIds)->chunk(config('scout.chunk.searchable'));
    foreach ($chunks as $chunk){
        $chunk->searchable();
    }
}

}
`
Then create a command that will package your ids and iterates on these packages od ids to send them to your job:
`
class ImportYourModel extends Command
{
/**
* The name and signature of the console command.
*
* @var string
*/
protected $signature = 'elastic:import-your-model';
/**
 * The console command description.
 *
 * @var string
 */
protected $description = 'Import your_model table content in Elasticsearch';

/**
 * Create a new command instance.
 *
 * @return void
 */
public function __construct()
{
    parent::__construct();
}

/**
 * Execute the console command.
 *
 * @return mixed
 */
public function handle()
{
    $chunkSize = config('scout.chunk.searchable')*10; // you can multiply by what you want to create more or less jobs
    $yourModelChunks = YourModel::all(['id'])->chunk($chunkSize);
    foreach ($yourModelChunks as $yourModelChunk){
        $yourModelIds = [];
        foreach ($yourModelChunk as $yourModel){
            $yourModelIds[] = $yourModel->id;
        }
        SeedYourModel::dispatch($yourModelIds);
    }
}`

By doing this I achieved import my 6 millions data in 45 minutes instead of 6 hours. You can improve performance by adding more workers (45 minutes was with only one worker)

If your table has an auto incremented ID, it's better to use that rather than queueing with chunk(). It's much more efficient, and is as fast in the beginning as it is at the end of the table.
Something like this would work:
$minId = TableToSync::query()->min('id');
$maxId = TableToSync::query()->max('id');

$chunkSize = 500;

for ($i = $minId; $i < $maxId; $i = $i + $chunkSize)
{
    $x = $i;
    $y = $i + $chunkSize;

    $rows = TableToSync::query()
        ->where('id', '>=', $x)
        ->where('id', '<', $y)
        ->get();

    // Do whatever with the rows
}

I suggest you guys not using the scout:import command for first sync of tables like that. Instead, you could use logstash to import the data from a csv file, it will be faster.
There's a few tricks to improve indexing performance, including ES settings too.
Not sure if scout:import allow you to choose what columns to load, also preload relationships, but it certainly will speed up your indexing most of times.

I finally found the problem on big tables. It is a scout problem, and it will be fixed in Scout 8.0 .
See this PR: https://github.com/laravel/scout/pull/360 . It has already been merged in master branch  of Scout.
In fact chunk occurs a huge performance issue on big tables. See this for more explanations : https://mattallan.me/posts/making-laravel-scout-64x-faster/
I hope @babenkoivan can update scout soon


Provide instructions how to upgrade Mac (dmg) release to latest version

Title says it all, pretty much.
It would be helpful if there were instructions on the start page on how to upgrade a dmg installation on a Mac (without loosing settings)... :)

Just reinstall (overwrite old version) by drag-n-droppping DBeaver into Applications.
Settings won't be lost (settings are store in separate folder .dbeaver4 in user home).
We'll add extra instructions on the download page, thanks for noticing.

It looks like this question was solved. It will be closed. If you think that it is actual just let us know.

This still needs mentioning at the bottom of the downloads page... :)

Agreed. Info on https://dbeaver.jkiss.org/download/ was updated


feat: Support maximum concurrency of Lambda Alias with SQS as an event source

Description
PR #402 introduced maximum concurrency to lambda functions.
As I use Aliases, I've added this feature to their module
This is also my first contribution to this repo.
Motivation and Context
Limiting lambda concurrency with SQS without setting reserved concurrency, while using Lambda Aliases
Breaking Changes

How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

not stale

This PR is included in version 5.1.0 :tada:


Can fastlne be used to change bundle identifier and target capabilities

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[ ] I searched for existing GitHub issues

Issue Description

Complete output when running fastlane, including the stack trace and command used

I read the documentation and could not figure out if fastlne allows to change bundle identifier and capabilities information.
From what I gather, bundle I'd needs to be changed in the project PBX file on iOS and plist just refers to that.

[INSERT OUTPUT HERE]

Environment

[INSERT OUTPUT HERE]

Hi @manujbahl 👋 This is not something fastlane is supposed to handle. You can use for example
https://github.com/CocoaPods/Xcodeproj


fix: adding filter check for removing disabled options for checkbox group

The commit message should start with the scope, so fix(legi-shared): ... 😉


Fix to a mistake before that makes the current version not work

Sorry, I am new to forking and before I committed something that I did not want merged by mistake.
I know reversed the commits and bumped the version number, can you please remerge?

You mean the gem name on the spec file? I updated that after merging your PR.

Yes it's what I meant. OK great, so ignore the PR. :)
On Mon, Feb 29, 2016 at 10:43 AM, Fernando Mendes<EMAIL_ADDRESS>wrote:

You mean the gem name on the spec file? I updated that after merging your
PR.
—
Reply to this email directly or view it on GitHub
https://github.com/frmendes/rails-template-cache/pull/3#issuecomment-190104707
.

--
בברכה,
רובי


Port to python 3

continuation of PR #17 up to correct commit.

The fixes in this PR work for python3, thanks @kobbled

To clarify: this works for python3.11.
With python3.12 kransw.py throws the following error:
ktransw.py:404: SyntaxWarning: invalid escape sequence '\w'
  '"\\n%\w"', # the macro start sequence


Fix dbatools issue 2192 for UNC share paths

Also brings style & formatting of function and help content (including grammar & spelling) in line with dbatools convention.

yeahhh thanks @alevyinroc !


Hide autogenerated node names from the tree view

Seeing all those c-1-12-3-123-12 names isn't helpful. Adding #30 will prevent them from appearing too often, but some nodes won't be able to be automatically named here or there. Render effects especially.
So what's left should just be hidden to not hurt the user's eyes. And displayed only in the details panel—if the user wants to have something to identify the node by. In the logs for example.

If https://github.com/solidjs/solid/pull/1255 gets merged, we could only display the names of nodes that has been named by users, components and autonames by a bebel plugin.

Changed in solid in https://github.com/solidjs/solid/pull/1460


[CT-1393] Macro in BigQuery takes no keyword argument 'relation'

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Have created 2 python models and 2 sql simple models, dbt version == 1.3.0.
When trying to launch "dbt compile --profiles-dir C:\Users\path_to_profile_file" or "dbt run" with profiles dir got the following:
Runtime Error
  Compilation Error in operation project_name_-on-run-start-0 (.\dbt_project.yml)
    macro 'dbt_macro__create_schema' takes no keyword argument 'relation'

    > in macro create_udfs (macros\bigquery_udfs\create_udfs.sql)
    > called by macro create_schema (macros\bigquery_udfs\create_schema.sql)
    > called by operation project_name_-on-run-start-0 (.\dbt_project.yml)

Expected Behavior
Successful models running and compilation within dbt=1.3.0.
The SQL models were launched within dbt version == 1.0.0, and there vere no issues, as usual.
dbt run -m stg_sql_model
   Running with dbt=1.0.0

Steps To Reproduce

Upgrade DBT version, 1.3.0
Create python and sql models in 'models' folder
Have local "profiles.yml" in .dbt folder
Compile or run models setting --profiles-dir

Relevant log output
(dbt-env) C:\Users\User_name\project_name>dbt compile --profiles-dir C:\Users\User_name\.dbt
12:11:53  Running with dbt=1.3.0
12:11:53  Found _ models, _ tests, _ snapshots, _ analyses, _ macros, _ operation, _ seed files, _ sources, _ exposures, _ metrics
12:11:53
12:11:54  Concurrency: 4 threads (target='dev')
12:11:54
12:11:56  Encountered an error:
Runtime Error
  Compilation Error in operation project_name-on-run-start-0 (.\dbt_project.yml)
    macro 'dbt_macro__create_schema' takes no keyword argument 'relation'

    > in macro create_udfs (macros\bigquery_udfs\create_udfs.sql)
    > called by macro create_schema (macros\bigquery_udfs\create_schema.sql)
    > called by operation project_name--on-run-start-0 (.\dbt_project.yml)

Environment
- OS: Windows 10
- Python: 3.9.13
- dbt: 1.3.0

Which database adapter are you using with dbt?
bigquery
Additional Context
Macro create_udfs
{% macro create_udfs() %}

{% do adapter.create_schema(api.Relation.create(database=target.database, schema="user_defined_functions")) %}

{{f_beauty_string_source()}}
{{f_process_json_source_proxy()}}
{{f_decode_uri_component()}}

{% endmacro %}

hi @Larchenko-Ksenia, I wasn't able to reproduce this -- are you thinking that this is related to Python models, the --profiles-dir option, or something else? can you provide more details why?
I copied over the macro to macros/create_udfs.sql, but had to comment out the custom macros:
{% macro create_udfs() %}

{% do adapter.create_schema(api.Relation.create(database=target.database, schema="user_defined_functions")) %}

{#
{{f_beauty_string_source()}}
{{f_process_json_source_proxy()}}
{{f_decode_uri_component()}}
#}

{% endmacro %}

I created a couple .sql and .py models with effectively select 1 as id statements. I added in dbt_projects.yml:
on-run-start:
  - "{{ create_udfs() }}"

for good measure, I also called the macro from one of the SQL models. in all cases, with or without --profiles-dir profiles/, where I'd copied over my ~/.dbt/profiles.yml file, everything ran successfully on 1.3 using BigQuery and Dataproc Serverless for the Python models
are there any more details you can provide to help us investigate and ideally reproduce?

What's the output of dbt --version

Unable to reproduce myself.

Hello, @lostmygithubaccount, @jtcohen6, @jeremyyeo, @dataders,
Thanks for your reply!
I see some additional details are needed to be provided to reproduce the issue above. Currently I'm trying to figure them out. Will answer as soon as possible.

thanks! will throw the awaiting_response label back on

@Larchenko-Ksenia from @jtcohen6 internally -- summarizing, the create_schema macro was added in v1.3 for BigQuery so this might be a naming collision:

Ah - could be related to the fact that, in v1.3 for the first time, dbt-bigquery will actually use/respect a custom create_schema macro (previously dbt created schemas via bq client API, and skipped Jinja-SQL entirely): https://github.com/dbt-labs/dbt-bigquery/pull/183

So the fact is, their custom version of the create_schema macro takes a keyword argument named schema_name, whereas the built-in version takes a keyword argument named relation. And there must be places in the codebase where we pass in the keyword argument by its expected name (relation)

let us know if that's the issue

I'm experiencing the same issue with the exact same use case (creating UDFs in BigQuery). Did you solve this, @Larchenko-Ksenia?


Double-click pinned tab allow user to enter alias for pinned tab

I request that double-clicking a pinned tab allow user to enter an alias for the file name.  Please, keep the current three options ("shrink", "compact", "normal"), but if tabs are compact or shrink, then assigning an alias makes that tab "aliased" and show full alias value (without ellipses).

Reason for requesting:
None of the current options are entirely satisfactory.  I want my pinned tabs to be very narrow but distinguishable.  Lots of files start with the same word or prefix.  For example, say there was:

tablesFooterComponent.js
tablesHeaderComponent.js
tablesBodyComponent.js

These are our current options:
Current options are these:
       tablesFooterComponent.js | tablesHeaderComponent.js | tablesBodyComponent.js
       tables | tables | tables
       js | js | js
It would be great if we could do something like this:
       HEAD | BODY | FOOT
       H | B | F

Other features/options

User can choose:

aliases auto-rearrange by alphabetical order (default to false)
choose if aliased tabs are grouped together (and separately from the shrunk, normal, or compact tabs) (default to "true")
if "grouped" and not "alphabetical", order aliased tabs in the group by creation order.

Context menu option "remove alias".
Context menu option "assign alias" (alternative to or substitute for double-clicking)

/duplicate https://github.com/microsoft/vscode/issues/43806


go get doesn't install v2

When running go get github.com/hekmon/transmissionrpc/v2, the follow message is returned.
go get: module github.com/hekmon/transmissionrpc@upgrade found (v1.1.0), but does not contain package github.com/hekmon/transmissionrpc/v2

Thank you for the report !
Indeed the go module was left behind (tagging alone does not work). Should be fixed with v2.0.1, let me know if this is not the case.


[PE-D][Tester B] Wrong usage message

Message usage for search role doesn't match the correct usage for the command.

Labels: type.FeatureFlaw severity.Low
original: JeremyYong128/ped#3

Previously, the error message shown is not clear at all when an invalid format for searchrole is inputted. And based on the incorrect error message, the user is unable to get the correct format of searchrole which can make searchrole unusable. Hence, this bug fix is allowed.


Include alpha version changelog in the final version

Clear and concise description of the problem
Hi
When I'm release many alpha version and then final version, the changelog (in github and other place) not include alpha version
Suggested solution
include all alpha changes in final version
Alternative
No response
Additional context
No response
Validations

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

When you use conventional changelog, all these changelogs are created by 3rd party library conventional-changelog not by Lerna itself. You also did not provide any repro and I did alpha releases in the past and never had any problems, so this issue will be closed unless you provide a full repro

When you use conventional changelog, all these changelogs are created by 3rd party library conventional-changelog not by Lerna itself. You also did not provide any repro and I did alpha releases in the past and never had any problems, so this issue will be closed unless you provide a full repro

This is my changelog
## [6.9.3](https://github.com/njfamirm/soffit-order/compare/v6.9.2...v6.9.3) (2024-10-20)

### Bug Fixes

* **app/send-otp:** enable sitemap ([c6defec](https://github.com/njfamirm/soffit-order/commit/c6defec8c37aaa305d4b1697be10ff5a55000238)) by @

## [6.9.2](https://github.com/njfamirm/soffit-order/compare/v6.9.1...v6.9.2) (2024-10-20)

### Miscellaneous Chores

* correct color theme based logo changes ([7618244](https://github.com/njfamirm/soffit-order/commit/76182443d10b1da16c0604cc8f32c01c90d502b6)) by @

## [6.9.1](https://github.com/njfamirm/soffit-order/compare/v6.9.0...v6.9.1) (2024-10-20)

### Bug Fixes

* **app/robots:** allow sign in send otp page ([338ff1b](https://github.com/njfamirm/soffit-order/commit/338ff1b412fd90dcaa469fffa463ccfe8e74cfb0)) by @

### Miscellaneous Chores

* add release info ([f3af625](https://github.com/njfamirm/soffit-order/commit/f3af625a2bc1c5dadc681f057b1532cbab930e89)) by @

## [6.9.0](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.9...v6.9.0) (2024-10-20)

**Note:** Version bump only for package @alwatr/order-app

## [6.9.0-alpha.9](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.8...v6.9.0-alpha.9) (2024-10-20)

**Note:** Version bump only for package @alwatr/order-app

## [6.9.0-alpha.8](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.7...v6.9.0-alpha.8) (2024-10-20)

### Bug Fixes

* add __dev_mode__ for package tracer ([01e9d40](https://github.com/njfamirm/soffit-order/commit/01e9d40f90f485059794b09274df07fbf2020646)) by @njfamirm
* use /* @__PURE__ */ for non side effect parts ([a119fca](https://github.com/njfamirm/soffit-order/commit/a119fca8c76bbe45abba45d36595355ffa8e2b5f)) by @njfamirm

## [6.9.0-alpha.7](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.6...v6.9.0-alpha.7) (2024-10-20)

### Features

* **common/theme-builder:** fucking awesome custom color support ([db31d55](https://github.com/njfamirm/soffit-order/commit/db31d5573e4a9c74e91975a732e37ee2745ac385)) by @njfamirm
* **pwa:** enhance install process ([c38d039](https://github.com/njfamirm/soffit-order/commit/c38d0390617e21864c0b58d443df35045ba678f9)) by @njfamirm

### Code Refactoring

* use custom green color ([47aa84d](https://github.com/njfamirm/soffit-order/commit/47aa84d1780bd7b7b02306424a4452ddd2deae65)) by @njfamirm

### Miscellaneous Chores

* rename function ([479babf](https://github.com/njfamirm/soffit-order/commit/479babf55f3217ea241eea1f4d99b196b2d1d591)) by @njfamirm

## [6.9.0-alpha.6](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.5...v6.9.0-alpha.6) (2024-10-20)

### Features

* **app:** Added summary page to review orders ([e8b3ea6](https://github.com/njfamirm/soffit-order/commit/e8b3ea64213e0ad7c10c0f9a86430288f0118514)) by @arashagp

### Bug Fixes

* **app/cart:** don't watch for hash change on child mode ([9537550](https://github.com/njfamirm/soffit-order/commit/953755095cd0fdd37f9192cf642954ecb756e52a)) by @njfamirm
* **app/orders/draft/summary:** correct machine ([401e200](https://github.com/njfamirm/soffit-order/commit/401e2002d1ec96b4c743cad7510b062464ab3530)) by @njfamirm
* **app/orders/draft:** remove extra padding ([53af300](https://github.com/njfamirm/soffit-order/commit/53af3000d908f110945de6d2522f2e38b1f37a6f)) by @njfamirm
* **app:** undo to functionally submit function ([de9c451](https://github.com/njfamirm/soffit-order/commit/de9c451df4ef8811edd0263a6227006cb246f622)) by @arashagp

### Code Refactoring

* **app/draft/summary:** move submit order to fab ([ad2a233](https://github.com/njfamirm/soffit-order/commit/ad2a2339408330c5f50f96625e7eb4b84df5ee04)) by @njfamirm
* **app/orders/summary:** remove extra parts ([ee63eee](https://github.com/njfamirm/soffit-order/commit/ee63eee4f336344b1d5ae3030d99090191d12c31)) by @njfamirm
* **app/shipping-info:** remove unnecessary comment's ([ded4612](https://github.com/njfamirm/soffit-order/commit/ded4612f2970e39ab34c3f293571146a134a13f4)) by @arashagp
* **app/summary:** change some of the store  state to correct store state ([c2b6d25](https://github.com/njfamirm/soffit-order/commit/c2b6d25dacf5d1ee98a8ecae684864b4bd2c7c40)) by @arashagp
* **app:** commented some of options for summary ([7f7f784](https://github.com/njfamirm/soffit-order/commit/7f7f78428846b0826259fa2abbfc65478af46efa)) by @arashagp

### Miscellaneous Chores

* formatting and building directory ([54eeb4e](https://github.com/njfamirm/soffit-order/commit/54eeb4e5cbd32711d006c137cf1d65eee63b6a4f)) by @arashagp

## [6.9.0-alpha.5](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.4...v6.9.0-alpha.5) (2024-10-17)

### Bug Fixes

* add url to robots ([f8b7faf](https://github.com/njfamirm/soffit-order/commit/f8b7faf39b5ff42162d8d168a08271565e9419a0)) by @njfamirm
* **app/install-pwa-guide:** top padding ([2c65e0a](https://github.com/njfamirm/soffit-order/commit/2c65e0a44a28817f85ef88de9244df4ab473867f)) by @njfamirm

### Code Refactoring

* remove car type from shipping info ([6f70733](https://github.com/njfamirm/soffit-order/commit/6f70733d2d7b825bb6b91251079b7592da3bec93)) by @njfamirm

## [6.9.0-alpha.4](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.3...v6.9.0-alpha.4) (2024-10-16)

### Features

* **app:** support old link ([0247aee](https://github.com/njfamirm/soffit-order/commit/0247aee91666c2e352f7ecad29bdc0360cbdc5bf)) by @

## [6.9.0-alpha.3](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.2...v6.9.0-alpha.3) (2024-10-16)

**Note:** Version bump only for package @alwatr/order-app

## [6.9.0-alpha.2](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.1...v6.9.0-alpha.2) (2024-10-16)

### Bug Fixes

* review issue ([a12aaf3](https://github.com/njfamirm/soffit-order/commit/a12aaf32450c33a54e5cddae1724078c09996267)) by @

## [6.9.0-alpha.1](https://github.com/njfamirm/soffit-order/compare/v6.9.0-alpha.0...v6.9.0-alpha.1) (2024-10-16)

### Bug Fixes

* reported sign in issue ([f0a1710](https://github.com/njfamirm/soffit-order/commit/f0a1710e846224f78cf02d42124a7bc9327157f4)) by @

## [6.9.0-alpha.0](https://github.com/njfamirm/soffit-order/compare/v6.8.3...v6.9.0-alpha.0) (2024-10-16)

### Features

* **api/api-server-util:** require token ([f151988](https://github.com/njfamirm/soffit-order/commit/f15198808aca402edd38c29a8f13272b09100991)) by @njfamirm
* **api:** fucking sign in with otp ([3d4c080](https://github.com/njfamirm/soffit-order/commit/3d4c0805e1f1fe4fa28e1fd7f5fbc32e1ad91bd0)) by @njfamirm
* **app/install-guide:** support more browser ([12ecff8](https://github.com/njfamirm/soffit-order/commit/12ecff88b29f9d522c2c626005522ceaefb40ce2)) by @arashagp
* **app/install-pwa-guide:** put safari info ([f396484](https://github.com/njfamirm/soffit-order/commit/f396484fd52187d453c11a132d3fa36f1862b51b)) by @njfamirm
* **app/sign-in:** handle before signed in ([fbc9160](https://github.com/njfamirm/soffit-order/commit/fbc9160ecbe096691a671423cbc4d414b05815e6)) by @njfamirm
* **app:** add isValid variable for property errorHandler inputs, change title of the inputs and buttons ([ebc78b8](https://github.com/njfamirm/soffit-order/commit/ebc78b8b65fad6bcc4b4fdaa75b8224361c5108e)) by @arashagp
* **app:** structure of validating with phone number ([b9d67bb](https://github.com/njfamirm/soffit-order/commit/b9d67bb5ae07c0c6024fa946e3f750a846ea3691)) by @arashagp
* **app:** write and change structure of validating user with phone number, add one more machine, one more page and one more request ([877d479](https://github.com/njfamirm/soffit-order/commit/877d4793dcdb3cc181df1a18ed80402d9b959e7c)) by @arashagp

That is how conventional-changelog create the changelogs and commits are only visited once and will never be revisited more than once even if it's alpha. That's also not a Lerna/Lerna-Lite issue but rather a conventional-changelog issue, but I'm pretty they won't do anything about it.  I'm closing this as Work as Intended.

ok, thanks bro


You mister are a genius

I mean it. This idea is so simple that it's just genius. Thanks a lot. From all of us that are stuck with require.js - yes Magento 2, I'm looking at you.

Thanks, you just made my day ;)
I'm glad it helped!