P-2586 Youtube Component

@bluerssen I have a working custom definition of a youtube component that could be easily repurposed if needed lmk

maybe post the code or link to code here? I think Gunjan is going to update this next week, but if you have soething already please update this PR or post to the details to save time!
Brian
On Fri, Sep 9th, 2022 at 5:03 PM, Dave Sebek @.***> wrote:

@bluerssen ( https://github.com/bluerssen ) I have a working custom
definition of a youtube component that could be easily repurposed if
needed lmk
—
Reply to this email directly, view it on GitHub (
https://github.com/draftbit/react-native-jigsaw/pull/367#issuecomment-1242514484
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AADQZCZN2S5SH2XQVD6FBDTV5OX4VANCNFSM5IM67ZDQ
).
You are receiving this because you were mentioned. Message ID: <draftbit/react-native-jigsaw/pull/367/c1242514484
@ github. com>

I'm not sure this will work with this package, because react-native-web-webview is super old and likely conflicts.

https://www.npmjs.com/package/react_native_youtube_streamer

Closed in favor of https://github.com/draftbit/react-native-jigsaw/pull/596


[ko] Update outdated files in dev-1.26-ko.1 (M197-M200)

Signed-off-by: jongwooo<EMAIL_ADDRESS>Description
Related Issue: #38458
Updated outdated files in content/en/examples/.
4 files to be modified

[x] M197.  content/en/examples/application/deployment-scale.yaml | 1(+XS) 1(-)
[x] M198.  content/en/examples/application/mysql/mysql-statefulset.yaml | 1(+XS) 1(-)
[x] M199.  content/en/examples/controllers/daemonset.yaml | 6(+XS) 0(-)
[x] M200.  content/en/examples/security/kind-with-cluster-level-baseline-pod-security.sh | 1(+XS) 1(-)

/assign @seokho-son

감사합니다!
/lgtm

/approve


[DO NOT MERGE] added validate_clusters true

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

NONE

@ijsnellf: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
85974779c6443917e4da8e5d0681f7a935026c9c
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ijsnellf: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
e3ca17afce147fc390a2a96e7293582cc879bc77
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ijsnellf: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
a053b6147fc924d602724ad2bf2a5c6e563452e1
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Can someone make that PR pass so I can try the Sha with the 404 test?

@ijsnellf: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
f2dce08b2c2dde06d9974739a4cff51e8f444539
link
/test pilot-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I think we should still explore this option, at least confirm that the PR was generating the right config and it was used by envoy before dropping it

Right, validate_cluster is still something that we want to add in master.


Add support for "reflow"ing the Terminal buffer

Summary of the Pull Request
This PR adds support for "Resize with Reflow" to the Terminal. In conhost, ResizeWithReflow is the function that's responsible for reflowing wrapped lines of text as the buffer gets resized. Now that #4415 has merged, we can also implement this in the Terminal. Now, when the Terminal is resized, it will reflow the lines of it's buffer in the same way that conhost does. This means, the terminal will no longer chop off the ends of lines as the buffer is too small to represent them.
As a happy side effect of this PR, it also fixed #3490. This was a bug that plagued me during the investigation into this functionality. The original #3490 PR, #4354, tried to fix this bug with some heavy conpty changes. Turns out, that only made things worse, and far more complicated. When I really got to thinking about it, I realized "conhost can handle this right, why can't the Terminal?". Turns out, by adding resize with reflow, I was also able to fix this at the same time. Conhost does a little bit of math after reflowing to attempt to keep the viewport in the same relative place after a reflow. By re-using that logic in the Terminal, I was able to fix #3490.
I also included that big ole test from #3490, because everyone likes adding 60 test cases in a PR.
References

#4200 - this scenario
#405/#4415 - conpty emits wrapped lines, which was needed for this PR
#4403 - delayed EOL wrapping via conpty, which was also needed for this
#4354 - we don't speak of this PR anymore

PR Checklist

[x] Closes #1465
[x] Closes #3490
[x] Closes #4771
[x] I work here
[x] Tests added/passed
[n/a] Requires documentation to be updated

@Kaznov Honestly, I'm not sure which is right to use here. I think I want to gracefully keep going in this case, so I'd want the clamped one. I'm pretty sure if we're going to exceed SHORT_MAX, it'd be in TextBuffer::Reflow which would return a failure first. I think, I'm not super sure about this.
@miniksa thoughts here? Do you think this should be a checked or clamped cast?

@Kaznov Honestly, I'm not sure which is right to use here. I think I want to gracefully keep going in this case, so I'd want the clamped one. I'm pretty sure if we're going to exceed SHORT_MAX, it'd be in TextBuffer::Reflow which would return a failure first. I think, I'm not super sure about this.
@miniksa Michael Niksa FTE thoughts here? Do you think this should be a checked or clamped cast?

For the viewport ones? Clamped. But used ::base::saturated_cast<SHORT>(foo) instead of constructing a ClampedNumeric for the sake of immediately unboxing it.

The build utterly hates you tho.

I'd like @miniksa to sign off, but I do not want to trigger the AutoMerge policies.

Copy/paste across lines that were wrapped by conpty has newlines at the wrap point.

Okay clearly I wrote this PR like a month ago and haven't vetted it enough, like I did #4354. I thought back then, when I wrote this, that this was a magic bullet. It pretty clearly isn't, so I'll play with this more. Responses to some feedback below:

Resizing horizontally slowly horizontally causes shuddering as things move left and right and jump to the previous/next line

I'm worried that this might not totally fixable but it's definitely worse than before. I'll go back to investigating this.

I hit at least one instance of a resize moving my prompt up to the end of the previous line

Hmm this is odd, but maybe related to the above. It also might be related to WCL2EB. I'm going to investigate the missing part of that as well.

The issue with horizontal-split panes seems to still exist

The powershell one yes, isn't fixed by this. The opening a pane leads to artifacts, that is fixed.

Copy/paste across lines that were wrapped by conpty has newlines at the wrap point.

Oh that's really bad. This makes me thing it's WCL2EB as well. This is a good spot to investigate.

I encountered this glitch while playing with resizing the window a bit. It's probably introduced by this patch

That's actually the bug that this PR is designed to fix 😅

So I changed this PR a bit to hopefully fix all the issues that had apparently been in the original one (seriously what was I thinking).
I'll be updating the description with some additional notes from my investigation. @carlos-zamora, @miniksa, I'm dismissing your old approvals, since there's a good amount of new code. Fortunately, everything new is in a8913ce.

@miniksa I actually prefer the in-out-opt pointer version compared to the referenceboi. even if it's a std::optional<std::reference_wrapper<short>> (which would be more like what you're asking for). I feel like its intent is fairly clear

@miniksa I actually prefer the in-out-opt pointer version compared to the referenceboi. even if it's a std::optional<std::reference_wrapper<short>> (which would be more like what you're asking for). I feel like its intent is fairly clear

Fine, leave it the pointer way then. I was mildly worried about that when asking for it, but generally I can't tell whether it's going to look "confusing" or not until I try it.

Okay, I'm happy with how this looks and feels. @miniksa If your only comment is about the optional, Mike's willing to fix it tomorrow as a codehealth fix and I do not want to block further on that. I'd prefer a pointer or an optional ref wrapper, not a ref to an optional, but i don't care enough here.

OK. Reviewing RIGHT NOW.

IT'S HAPPENING
itshappening.gif

/azp run

old check cannot be cleared.


Fix debug support

per commit https://github.com/electron/electron/commit/eac2e7cc614d4e98e2828921f63d55f7b5e2c85c remote needs to be required as require('electron').remote
see discussion here:
https://github.com/electron/electron/issues/3755
should alleviate concerns in this discussion:
https://github.com/appetizermonster/hain/issues/77

Thanks for the pull request,
however, please change the target branch to develop, i'll merge it then

Done @appetizermonster
Sorry about that


empty object for strain: subclass_of

empty object for strain: subclass_of, e.g. in bacdive transform:
strain:108^Ibiolink:subclass_of^I^Irdfs:subClassOf^Ibacdive:140012$
Looks like 96 of these in the latest bacdive transform:
grep -E ‘of            ’ ../../kg-microbe/data/merged/20240702/bacdive_edges.tsv  |wc
96
A mix of cases:
strain:ZE-1     biolink:subclass_of             rdfs:subClassOf bacdive:16803
strain:of_NO_NCBITaxon_ID       biolink:subclass_of             rdfs:subClassOf bacdive:16401
@hrshdhgd

grep -E ‘of ’ ../../kg-microbe/data/merged/20240702/bacdive_edges.tsv |wc
96

It's 0 for me. Your version may be old.

A mix of cases:
strain:ZE-1 biolink:subclass_of rdfs:subClassOf bacdive:16803
strain:of_NO_NCBITaxon_ID biolink:subclass_of rdfs:subClassOf bacdive:16401

Does not exist in the latest versions

strain:108^Ibiolink:subclass_of^I^Irdfs:subClassOf^Ibacdive:140012$

This is the only one I found in the latest version ...fixing.


Fixing the moment when SS is set

without this change there's a problem with the time when the SS is set on a span. Currently it's done  in TraceFilter's finally block. The problem is that this code is executed after the response has been sent back to the client. Thus CR sometimes was set faster than SS (it doesn't make any sense from the logical point of view).
with this change we move setting the SS on the span to the TraceHandlerInterceptor.  We leave the mechanism of TraceFilter stamping the span SS as a fallback one. That means that if for some reason the TraceHandlerInterceptor wasn't executed then we need to try to save the situation.
also this change fixes ensures that the TraceHandlerInterceptor is available for Zuul. Until now even though we've added it to the list of interceptors it was never executed at runtime. That's why we're wrapping the ZuulHandlerMapping with our own wrapper and we're initializing the interceptors for it.
fixes #492 #431

Actually I have to close this cause it's not working ;)


Add missing export for Fd

We need to export Fd to be able to import it from the package. The export for OpenDirectory was also missing.
Apologies for opening yet another PR 😅

Released as v0.2.7.


Default connectionstrings and parameters

Hi,
I'm using settings/default to create global parameters to use through the whole test-suite for the system-under-test and assert tags (check code example below).
This is the test-suite xml which is failing:
<?xml version="1.0" encoding="utf-8" ?>
<testSuite name="testsuitename" xmlns="http://NBi/TestSuite">
	<settings>
		<default apply-to="system-under-test">
			<connectionString>Provider=MDX connection string</connectionString>
			<parameter name="DaysToGoBackMDX" >
			30
			</parameter>
		</default>
		<default apply-to="assert">
			<connectionString>sql connection string</connectionString>
			<parameter name="DaysToGoBackSQL" sql-type="int">
			30
			</parameter>
		</default>
	</settings>
	<test name="MDX R1 vs MDX 2 Value">
		<system-under-test>
			<execution>
				<query>
					MDX code
				</query>
			</execution>
		</system-under-test>
		<assert>
			<equalTo> <column  index="0" role="value" type="numeric"  />
				<query connectionString=mdx connection string>
					mdx code
				</query>
			</equalTo>
		</assert>
	</test>
</testSuite>

I have solved this by adding this piece of code to force a MDX parameter on the assert tag of one test case (MDX parameter which I'm not using for anything in this particular test case):
`	<parameter name="DaysToGoBackSQL">
		10
	</parameter>`

So, in conclusion, I'm defining a SQL connection string and a SQL parameter as the default for the assert tag in the settings. However, in this case, I have a test case where the assert tag will be done against a MDX connection so I changed the connection string for that particular case. For some reason, when I do this NBi will validate the parameters defined in settings for the assert tag and check that it is a SQL parameter (even if it's not used in that particular test case) and fails with the following error:
System.NotSupportedException : Specified method is not supported.

If I go the the settings to the assert tag and remove the data type of the parameter sql-type="int" the test will no longer fail, since I guess NBi now "thinks" that this is a MDX parameter (which is not what I want). The test does not fail, but this does not solve the problem.
As I've mentioned I've solved the problem by forcing a MDX parameter right in the test case, even if I'm not using it anywhere in the query.
Are you aware of this issue? Can you explain me why does this happen?
Somewhat related questions:
Am I allowed to create more than one connection string in settings per tag (e.g. assert)?
Am I allowed to create more than one parameter of different type (MDX, SQL) in settings per tag (e.g. assert)?
Are connection strings and parameters tied when defined at the settings level (for the same tag)?
I hope I've made myself clear. If you have any doubts please just ask.

To be honest, I've never tried or thought to use a SQL parameter when defining a MDX query :-)
I guess the exception is directly thrown by the .Net framework and not by NBi itself. You probably can't define a type for a MDX parameter. I don't know if it's a good idea (or not) that NBi skips the type of the parameter if the query is a MDX query and not a SQL.
The key point to understand is that when you define a parameter in the settings, the parameter is not associated to a type of query (MDX or SQL).
By redefining the parameter into the test, you're overriding the definition of this parameter and so you remove the type of the parameter. NBi has no definition for the type of this overridden parameter and so has no problem to set it for a MDX query. It's the expected behaviour for an unexpected case.
Without specific knowledge of your test-suite, I'd say that you're a bit abusing the concept of defining parameters into the defaults. This concept has been introduced to cover the cases where all your SQL or MDX queries will receive parameters to limit the range of the test. By example, I've quick test-suite where I're limiting to a few days and I can easily update the value of the parameters in the settings to change it to a slow test-suite where I'm limiting to a few years.
Could you tell me a bit more about your case: how many tests have you got? Your parameters are valid for how many tests? ... perhaps I'll be able to introduce a new feature to help you!
To answer your other questions:

Am I allowed to create more than one connection string in settings per tag (e.g. assert)?

You can create one unique default for a given scope (system-under-test, assert, ...). If your tests require more than one connection-string for a scope, you should take a look to the references but references don't accept definitions for parameters.

Am I allowed to create more than one parameter of different type (MDX, SQL) in settings per tag (e.g. assert)?

When you define a parameter in the settings, the parameter is not associated to a type of query (MDX or SQL) ... So no you can't define two parameters with the same name and hope than one will be used for SQL and the other for MDX queries.

Are connection strings and parameters tied when defined at the settings level (for the same tag)?

No they are not.

I guess I could not make myself totally clear.
You've understand most of my doubts, but I guess you've misunderstood one.
I don't think I'm abusing the concept of defining parameters into the defaults. I'm defining that the assert will always be used to connect to SQL, but, unfortunately, my test-suite will have a unique case where I need to connect to a cube ("MDX") in the assert tag. (the code sample I sent you only portrays that error, because, in fact, my test suite has 100 SQL to SQL comparison and one MDX to MDX which is the one that fails because of what I've mentioned earlier).
The problem is that, somewhat, he returns the error I've shared.
If you use the code I've sent and just change the code of the test to compare some random MDX query against the same MDX query you'll see that the test fails (the MDX connection can be exactly the same in settings - system-under-test and in the test case - assert; the SQL connection string can be any);
If you remove sql-type="int" from the settings assert parameter the tester will no longer fail (however it won't do what's needed since you need to use the parameter).
As I've told you, you have to override the parameter in the test case which is not very elegant (since you don't really need it for the query).
Maybe references, can be the solution for this particular case (but I really think this is a bug which I am not being capable of describing). I think that if you use my code you can reproduce it and you'll understand my problem better.

Hi bipedro,
is it clear to you that there is no connection between the connection string and parameters you define in the defaults?
If so, try to remove the connection strings in the defaults for a while and try using the parameters only. If you use the named parameters in your tests, do they work independently in MDX and SQL? If you don't type them as sql-int in the parameter definition already, you can use them as untyped strings and convert them to int in SQL or MDX queries with their respective functions itself?
Just some ideas, which may help? Maybe I misunderstand, too :)

Hi @bipedro,
Based on your description, I'd say that overridding the (unneeded) parameter is not elegant but the best approach (it's I'd do personnaly). I share your point of view that due to this overriding the test is not straightforward to read and it looks a bit cumbersome to define a parameter to explain to the framework that you don't want it.
I'll let this open and try to find an alternative to express that you don't want to inherit from a parameter. My goal will be to improve the readability of the test. What do you think about :+1:
       <assert>
            <equalTo> <column  index="0" role="value" type="numeric"  />
                <query connectionString="mdx connection string">
                    mdx code
                    <parameter name="DaysToGoBackSQL" action="remove">
                </query>
            </equalTo>
        </assert>

or something as
       <assert>
            <equalTo> <column  index="0" role="value" type="numeric"  />
                <query connectionString="mdx connection string" inherits-parameters="false">
                    mdx code
                </query>
            </equalTo>
        </assert>

Comments and suggestions for other syntax are welcome.

Hi,
@Seddryck, both approaches would work well. I personally don't have any suggestions, but I'm all in favor of readability (documentation would be paramount I guess). By the way, let me congratulate you and your team for the documentation provided which is very easy to follow and self-explanatory.
@FuegoArtificial, in truth I cannot really grasp the problem. Are you able to provide a easy explanation of why a parameter that I'm not using in a test is giving me problems?
Thanks for your suggestions. I could pass the parameter as a TEXT (string), but I guess that handling it in the SQL query would not be a very performance oriented option. However, in my particular case, this just happens for one of my tests, which is not a big problem for now. As I add more tests to the test suite this might become a problem.
I might try to use references to define global connection strings, but this would not be optimal. I guess I will maintain my "bogus" parameter for now as defined in the test case. If this becomes a real issue I'll take a look a it in the future.
Thanks for all your help.

@bipedro , @FuegoArtificial I've not been clear about why you had the problem. In fact all parameters defined (in the test or in the settings) are always transferred to the server: NBi doesn't parse your query to know if the parameter is needed or is not expected. It's usually not problem because a SQL server doesn't care about receiving pointless parameter but in your specific case, NBi tries to submit a SQL parameter to an MDX server.

Preview available at https://ci.appveyor.com/project/CdricLCharlier/nbi/build/1.13.0-ci.35
Supports:
 <assert>
            <equalTo> <column  index="0" role="value" type="numeric"  />
                <query connectionString="mdx connection string">
                    mdx code
                    <parameter name="DaysToGoBackSQL" action="remove">
                </query>
            </equalTo>
        </assert>


Replicate change to C# version

See https://github.com/dotnet/docs/issues/29730#issuecomment-1149321507
and #29734

ping @adegeo for review


Can't install package via git URL

@Xriuk @jorbascrumps
I'm using Unity 2021.3.18f1
I tried following the install instructions, by entering https://github.com/stonesheltergames/Unity-GUID.git in Package Manager's Add package from git URL option. But this makes Unity throw the following errors in the console:
[Package Manager Window] Cannot perform upm operation: Unable to add package [https://github.com/stonesheltergames/Unity-GUID.git]:
  [https://github.com/stonesheltergames/Unity-GUID.git] does not point to a valid package. No package manifest was found. [NotFound].
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()

[Package Manager Window] Error adding package: https://github.com/stonesheltergames/Unity-GUID.git.
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()

I believe the package.json and package.json.meta files should be moved to the root folder of the repository, to fix the issue.

As of now, I was able to install the package via Package Manager by entering this URL in Add package from git URL option:
https://github.com/stonesheltergames/Unity-GUID.git?path=/Assets/StoneShelter

Hi, you are welcome to submit a PR if you wish

Based on the common structure of other Package Manager git packages, I think even the "StoneShelter" folder could be deleted, then the GUID.cs and Editor folder would be directly located at the root.
I'm not sure, but maybe having that StoneShelter folder inside this package could cause conflicts with other packages that could also have a StoneShelter folder - I guess the usual Package Manager folder structure makes that folder redundant.

Thanks for the info, I'm preparing a PR right now. :)
Based on the common structure of other Package Manager git packages, I think even the "StoneShelter" folder could be deleted, then the GUID.cs and Editor folder would be directly located at the root (or inside a [root]\Scripts folder).
I'm not sure, but maybe having that StoneShelter folder inside this package could cause conflicts with other packages that could also have a StoneShelter folder - I guess the usual Package Manager folder structure makes that folder redundant.

True


Invalid {{contact}}

Hi,
Please feel free to redirect this issue to proper repo if needed.
Repro steps:

Go to https://cloud.digitalocean.com/registrations/email
Fill the fields, type as password '123456'
See "... {{contact}}"

Result:
"Please try your request again. If the problem persists {{contact}}."
Screenshot:

Best wishes,

Thank you for bringing this to our attention! We have relayed the message to our UI engineers.

Hi @danaelhe my pleasure! Thank you for quick action and message. ✨ Have a great day, best wishes


Allow seeing the whole Custom Background URL one is entering, like JOSM

Allow seeing the whole Custom Background URL one is entering, like JOSM.
JOSM has an entire huge box, but iD has just this tiny textbox which is never enough.

One needs to see the whole thing one entered, so one can be totally sure. Even if one can poke around the various parts.
Never mind my blue highlighting in the image.

What does it look like in JOSM?

https://josm.openstreetmap.de/wiki/Help/Preferences/Imagery

If we change this, we'd need to replace this window.prompt call with a new modal dialog box that can show a textfield.   (window.prompt can only do one line, and we don't have any options to customize it)
https://github.com/openstreetmap/iD/blob/73f78c3622b949270758306c88910214aeb41d37/modules/ui/background.js#L106-L109

If it is possible I would like iD to remember the custom URL templates for me.

tagging @vershwal - this is kind of the same as #4806

More context - this issue will be closed if we replace the window.alert box with a modal screen.  We'll be able to replace the single line input with an actual textarea that shows multiple lines.

This was done in #5207


centralizing device, manufacturer, etc

resolves #41
resolves #40
resolves #39
resolves #47

@saskiad You can see how as soon as Device becomes a shared concept, Manufacturer wants to as well.
I did a (very fast) pass at updating ophys and ephys, there may be some mistakes.

An additional thought is that we should remove type from the general Device class, since that is only ever getting overwritten by rig-specific classes.

An additional thought is that we should remove type from the general Device class, since that is only ever getting overwritten by rig-specific classes (and other times just doesn't exist).

Yeah, the DeviceType list is specific to microscopes and doesn't make sense being a field for a generic Device. We just need this list to get used appropriately.


Error with Vue lazy loading components

I am currently using vue to develop a layout framework, which is integrated into this framework after others develop applications. The specific way is to copy the resource path to an index.html after other applications are compiled. The vue components in each application are introduced through lazy loading. Each vue component is compiled into a separate .js file.
However, I found that conflicts will occur when different applications are integrated. As shown in the figure:

The above two pictures show building codes of different applications. Components with the same number are in conflict. If you open one and open the other, an error will be reported. For example, the FTKfwwyt in Figure 1 and the sjklgl in Figure 2 are numbered 1. Each component can only open one, and an error will be reported when opening the other. The error information is shown in the following figure:

I want to know what is the reason for this and how to solve it? What configuration can be used to make the component number unique？
Thanks very much！

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.


Support creating foreign tables with Postgres foreign data wrapper

Essentially, add the FOREIGN keyword to the DDL when creating models.
CREATE FOREIGN TABLE ...

As far as I understand it, it could be solved with a Postgres-specific materialization. Maybe not... though, this would be nice:
{{ config(materialized='foreign-table' }}

Related issues:

https://github.com/dbt-labs/postgres/issues/5
https://github.com/dbt-labs/postgres/issues/4

Thinking about it again, I think it doesn't work that way. CREATE FOREIGN TABLE defines a foreign table, i.e. makes it visible to the local postgres instance. Creating a new table on a remote server is a different thing.
I'm closing the issue.


PIP-200: Package Pulsar Trino distro and config in a dedicated folder

Mailing list thread: https://lists.apache.org/thread/s985ypf0r0hzcm0mx653n5h2rt7n273v
Motivation
After https://github.com/apache/pulsar/pull/16683 merged, we upgrade PrestoSQL dependency in Pulsar SQL to the first several Trino version. To handle the name change cases and gradually refactor Pulsar SQL as a self-contained module so that we can move it into a standalone repository, I find that there're three major issues to resolve.

Configs of Pulsar SQL go under the conf/ folder and mix with other Pulsar configs.
Pulsar Docker images (base and all) bundle Pulsar SQL.
Integration tests of Pulsar SQL are tightly coupled with the main repo (test infra).

This proposal focuses on the first step only.
It's to package Pulsar Trino distro and config in a dedicated folder; that is, to make the distro self-contained.
Goal
I have already prepared a draft to perform the changes as https://github.com/apache/pulsar/pull/17062. Generally, we move the config files under PRESTO_HOME and correspondingly update scripts.
In this way, all Trino distro artifacts are under the same home path, so that we can later move it out as a whole.
Compatibility
This change should not affect those who use Pulsar with the entry point script, but it changes the layout of the release artifact.
I'm going to write a release note about this change and also post it on the Pulsar SQL overview page as a caveat. Draft here:
# Caveat

If you're upgrading Pulsar SQL from 2.11 or early, you should copy the related configs from `conf/presto` to `trino/conf`, and `lib/presto` to `trino`. If you're downgrading Pulsar SQL to 2.11 or early from 2.12, do verse visa.

[x] #17576

Implementation
It's straightforward to inline in the "Goal" section.
I will move all artifacts now under conf/presto and lib/presto to a top-level folder trino, while keeping all conf files under trino/conf. Besides, all relevant references in scripts will be updated.
To minimize unnecessary changes, I tend to keep the module's name pulsar-presto-xxx as is.
Alternatives
I don't make a completed proposal to resolve all three issues listed above. Because I'm still unfamiliar with the latter two topics yet and I'd prefer to implement these improvements one by one since they're naturally independent. If I try to make a completed proposal at once, it's highly possible I give up halfway.
Anything else?
Previous discussion:

[DISCUSS] Move Pulsar SQL to a separated repository?

Closed as all subtasks done.
cc @codelipenghui @eolivelli perhaps we should note somewhere that this change need a release note. The ceveat is included in https://github.com/apache/pulsar/pull/17798/commits/33905b608abdd9d7d71054526e89ce04ba0759b3.


Add a convenience flag for upcalling on Exception subclasses

Currently, these tests both fail on 2.7 and only the latter fails on 3.6.
@attr.s
class E1(Exception):
    x = attr.ib()
    y = attr.ib()

def test_exception_init_called():
    e = E1(1, 2)
    assert e.args == (e.x, e.y) == (1, 2)

def test_exception_init_called_even_with_kw():
    e = E1(y=3, x=4)
    assert e.args == (e.x, e.y) == (4, 3)

If attrs is overriding __init__ then this makes sense; args is filled in by __init__ in 2.x and __new__ in 3.x, but only pulling from the *args and never **kwargs. I discussed this a bit with @markrwilliams but I'm not sure what the best way to handle an attrs-ified exception would be. Maybe it's okay to consider args vestigal.
Mostly I'm raising this on the issue tracker because there are some references to using attrs for exceptions, but only indirectly. It'd be nice to have some documentation on a suggested approach either way.

Is test_exception_init_called_even_with_kw a valid test?
The args attribute on Exception is documented as "The tuple of arguments given to the exception constructor."
And Exception itself doesn't accept kwargs.  So I think the behavior in the case of kwargs to init with respect to what goes into the args attribute is… undefined.  So I'd have no expectation of that test passing on exception classes generically.

I included it because of the usual attrs isomorphism:
class E1(Exception):
    def __init__(self, x, y):
        super(E1, self).__init__(x, y)
        self.x = x
        self.y = y

It might not abide strictly by the documentation of Exception that you'd end up with e.args == (e.x, e.y) but I wasn't sure if a case could be made since this is how one would write the class without attrs.

I guess what I'm saying is that it's not clear to me that when one calls the super init, that including the kwargs is a common practice.
That said, I find the args attribute's design to be severely lacking in clarity, basically a "tuple of whatever rando stuff the caller threw in here", so I'm rather sympathetic to the argument that it is vestigal.
The only reason to care about it as far as I'm aware is that it effects str(), and that's true even when using attrs, which leaves something to be desired:
>>> str(C(1,2))
'C(x=1, y=2)'
>>> str(C(x=1,y=2))
'C(x=1, y=2)'
>>> str(E1(1,2))
'(1, 2)'
>>> str(E1(x=1,y=2))
''

Here E1 is defined as in your example C is the same as E1 is the same without inheriting from Exception.

After running into #217 I came up with an @attrs_exception decorator that passes both of your tests on Python 2.7 (and probably 3.6):
import inspect

import attr

def attrs_exception(maybe_cls=None, *args, **kwargs):
    r"""
    A class decorator to eliminate boilerplate when creating Exceptions using
    :func:`attr.s`.

    Adds ``__str__`` (because Exceptions don't use ``__repr__``) and an
    ``__attrs_post_init__`` that calls ``Exception.__init__`` with the class's
    :func:`attr.ib`\ s. Without this, instances cannot be deepcopied on Python 2.

    ref: https://github.com/python-attrs/attrs/issues/217

    :param args: additional positional arguments to be passed to :func:`attr.s`
    :param kwargs: additional keyword arguments to be passed to :func:`attr.s`
    """
    def wrap(cls):
        def _attrs_post_init__(obj):
            Exception.__init__(obj, *attr.astuple(obj))

        existing_post_init = getattr(cls, '__attrs_post_init__', None)
        if (
            existing_post_init
            and (
                inspect.getsource(existing_post_init)
                != inspect.getsource(_attrs_post_init__)
            )
        ):
            raise TypeError(
                "'%s' already has an '__attrs_post_init__' method" % (cls,),
            )
        if not issubclass(cls, Exception):
            raise TypeError(
                "'%s' is not a subclass of Exception! Use 'attr.s' instead" % (cls,),
            )
        cls.__attrs_post_init__ = _attrs_post_init__

        kwargs['str'] = True
        kwargs['slots'] = True
        return attr.attributes(cls, *args, **kwargs)

    # maybe_cls depends on the usage of the decorator. It's a class if it's
    # used as @attrs_exception but None if it's used as @attrs_exception()
    if maybe_cls is None:
        return wrap
    else:
        return wrap(maybe_cls)

So, what we want here is basically:

@attr.s(str=True)
All fields additionally put into self.args?
Exceptions usually can’t be compared – so maybe also cmp=False?

I’d be sympathetic to add something like @attr.exc since I use it quite often myself.

Just hit this myself, blindly assuming Exceptions would work - @attr.exc (@attr.err?) would be very handy.

I took a stab at this in #500.
Please provide feedback so we can close this gaping hole.


adding vamp 0.8.5

Hi @aquamatthias creating this PR in response to your comment https://github.com/mesosphere/universe/pull/433#issuecomment-214786562

Thanks @dragoslav! Did you test your package on a 1.7 cluster?

Yes, by adding https://github.com/magneticio/universe/archive/vamp.zip (or vamp-0.8.5.zip in this particular branch) to the package list and then installing Vamp.
Since we need also both Elasticsearch and Logstash, I did deployment of them as described in http://vamp.io/documentation/installation/mesosphere_dcos/ (it's not possible to replace the custom ES image using just DC/OS UI installation).

Awesome, thanks @dragoslav — LGTM & merge.


failed invalid storage kind 'openstack' for component 'registry'

Ugh.
TASK: [openshift_facts | Verify Ansible version is greater than or equal to 1.9.4 and less than 2.0] ***
fatal: [ossdell-openshift-master-0.example.com] => Failed to template {% if persistent_volumes | length > 0 or persistent_volume_claims | length > 0 %} True {% else %} False {% endif %}: Failed to template {{ hostvars[groups.oo_first_master.0] | oo_persistent_volumes(groups) }}: |failed invalid storage kind 'openstack' for component 'registry'

FATAL: all hosts have already failed -- aborting

The packages for the ansible playbooks are not up to date yet. You need to use openshift-ansible from Git by setting the following stack parameters :
openshift_ansible_git_url: https://github.com/openshift/openshift-ansible.git
openshift_ansible_git_rev: master

Thank you.


bump-formula-pr: fix type of detected version

Relates to recent type signature additions, e.g. in #16886. Fixes #16917.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

Error is unrelated:
 Error: GitHub::search_issues queries GitHub issues with the passed parameters

Failure/Error: expect(results.first["title"]).to eq("Shall we run `brew update` automatically?")

  expected: "Shall we run `brew update` automatically?"
       got: "Shall we move more things to taps?"

Thanks @EricFromCanada!


editable team photos

for now there are 3 members with random pictures, the pages/about/index.md file should be edited before merging

👷 Deploy Preview for peaceful-meerkat-940447 processing.

Name
Link

🔨 Latest commit
5b659f2f828f44c3ba79425dd5a906600fa0786a

🔍 Latest deploy log
https://app.netlify.com/sites/peaceful-meerkat-940447/deploys/6453995d6644db000885ba7b


Script fails to launch  DayZ

I'm having an issue where the script won't launch DayZ. Looking at threads on reddit , it sounds as though it's a problem with steam. But just so others have this visibility, this is my output:
/home/frank/gaming/dayz-linux-cli-launcher/dayz-launcher.sh   --server <IP_ADDRESS>:2402   --port 27600   --launch   --name frank
[dayz-launcher.sh][info] Resolving steam
[dayz-launcher.sh][info] Using non-flatpak mode: steam
[dayz-launcher.sh][info] Querying API for server: <IP_ADDRESS>:27600
[dayz-launcher.sh][info] Launching DayZ
+ steam -applaunch 221100 '-mod=@1912237302-IRP_Land_Rover_Defender_110;@2158553597-Breachingcharge_Expansion_Compatibility;@1827241477-Breachingcharge;@2485015982-Radioactive_Animals;@1836257061-Banking;@2149462115-ZT_Vending_Machine;@1590841260-Trader;@1565871491-BuilderItems;@2350401726-King_of_the_Hill;@2303554682-Dogtags;@1646187754-Code_Lock;@2024889593-COCAs_NoVehicleDamageMOD;@2444247391-Inventory_Move_Sounds;@2501812949-Flying_Birds;@2470924704-Gas_Pump_Refueling;@2155726353-Mortys_Weapons;@2293907947-TruckSpeedFix;@1868236039-No_Glove_Or_Shoe_Damage;@2216645010-PristineRepair;@1797720064-WindstridesClothingPack;@1832448183-FlipTransport;@2098390861-No_Force_Weapon_Raise;@1932611410-CannabisPlus;@1991570984-MuchStuffPack;@2276010135-DayZ_Editor_Loader;@2545327648-Dabs_Framework;@2572331007-DayZ_Expansion_Bundle;@1566911166-Mass_sManyItemOverhaul;@2443122116-SNAFU_Weapons;@2754119488-CPBWeapons_Legacy;@1793351435-Remastered_Arma_Weapon_Pack;@1665082937-Trump_s_Wall_Server_Mod;@2116157322-DayZ_Expansion_Licensed;@1828439124-VPPAdminTools;@1564026768-Community_Online_Tools;@1559212036-CF' -connect=<IP_ADDRESS>:2402 -nolauncher -world=empty -name=frank
steam.sh[21055]: Running Steam on pop 20.04 64-bit
steam.sh[21055]: STEAM_RUNTIME is enabled automatically
setup.sh[21125]: Steam runtime environment up-to-date!
steam.sh[21055]: Steam client's requirements are satisfied

Then nothing happens. I've tried restarting steam, and I've tried only running:
steam -applaunch 221100 '-mod=@1912237302-IRP_Land_Rover_Defender_110;@2158553597-Breachingcharge_Expansion_Compatibility;@1827241477-Breachingcharge;@2485015982-Radioactive_Animals;@1836257061-Banking;@2149462115-ZT_Vending_Machine;@1590841260-Trader;@1565871491-BuilderItems;@2350401726-King_of_the_Hill;@2303554682-Dogtags;@1646187754-Code_Lock;@2024889593-COCAs_NoVehicleDamageMOD;@2444247391-Inventory_Move_Sounds;@2501812949-Flying_Birds;@2470924704-Gas_Pump_Refueling;@2155726353-Mortys_Weapons;@2293907947-TruckSpeedFix;@1868236039-No_Glove_Or_Shoe_Damage;@2216645010-PristineRepair;@1797720064-WindstridesClothingPack;@1832448183-FlipTransport;@2098390861-No_Force_Weapon_Raise;@1932611410-CannabisPlus;@1991570984-MuchStuffPack;@2276010135-DayZ_Editor_Loader;@2545327648-Dabs_Framework;@2572331007-DayZ_Expansion_Bundle;@1566911166-Mass_sManyItemOverhaul;@2443122116-SNAFU_Weapons;@2754119488-CPBWeapons_Legacy;@1793351435-Remastered_Arma_Weapon_Pack;@1665082937-Trump_s_Wall_Server_Mod;@2116157322-DayZ_Expansion_Licensed;@1828439124-VPPAdminTools;@1564026768-Community_Online_Tools;@1559212036-CF' -connect=<IP_ADDRESS>:2402 -nolauncher -world=empty -name=frank

But none of that changed the outcome. I'll follow up with a separate comment, containing your response from reddit
Distro:
Pop!_OS 20.04 LTS
Kernel:
5.16.11-76051611-generic
RAM:
32 GB
GPU Driver:
4.6 Mesa 21.2.2
GPU:
AMD Radeon R9 390 (HAWAII, DRM 3.44.0, 5.16.11-76051611-generic, LLVM 12.0.0)
CPU:
AMD Ryzen 7 3700X 8-Core
Proton: 7.0_1

Here was your response:

Then nothing happens.

As you can see, the launcher has done its job. Everything that comes next is up to Steam, so I can't really help here other than giving some suggestions according to my experience with Steam.

I've tried restarting steam, and I've tried only running: ...

 There are many ways for achieving this, and since Steam is proprietary closed source software, nobody except Valve can tell. Restarting Steam should however fix the singleton process detection. If it does not, then check

if running steam -applaunch 221100 alone works
if Steam has actually received the command passed to it via the secondary launch attempt. Fully close Steam, run it from your command line shell to be able to see its stdout/stderr, and then run the command with the applaunch stuff again.
if there are any running stale/zombie steam process in the background which break the singleton process mechanism. If so, kill them or restart your system.
if there are any .steampid files with bad process ID references in your home directory. If so, fully close Steam and delete those files, then start Steam again and re-run the launcher.

Running Steam on pop 20.04 64-bit

It's also possible that something else is going on on PopOS / Ubuntu / Debian. If that's the case, then I can help, because I don't use Debian based distros. Steam is working perfectly fine on Arch.
Once again, the launcher's job is to set up mods and to generate a command line with parameters necessary to launch the game via steam, and as can be seen in the log output, it has done that. If Steam refuses to start the game, you can always add the generated parameters to your game's launch options in Steam itself. If the custom launch options in Steam don't include the %command% keyword, then the entire input will be appended to the game's launch command interpreted by BASH, which is what you want.

Asking questions about the launcher on reddit is also not a good idea. That should ideally be done on the issue tracker on github, so everyone else can see. This answer will only be seen by people coming to reddit and finding this old thread.

So I tried to run steam -applaunch 221100 with steam open, and it failed. I closed steam and ran it, and it launched steam AND DayZ but it ran the dayz client (containing the server browsing tab, that launches the game once the mods are downloaded automatically). That client does not function, which is why I'm using this script.
So, is there a way to get the script, or dayz in steam, to launch straight into the game and bypass that client?

Thanks for reposting for visibility.

So I tried to run steam -applaunch 221100 with steam open, and it failed. I closed steam and ran it, and it launched steam AND DayZ but it ran the dayz client (containing the server browsing tab, that launches the game once the mods are downloaded automatically)

So it launched the official DayZ launcher, not the actual game client.
I forgot to tell that you need to pass the -nolauncher argument, so that the game starts the game client instead of the launcher. My launch script automatically sets the -nolauncher argument.
This should start the game client:
$ steam -applaunch 221100 -nolauncher
steam.sh[788431]: Running Steam on arch rolling 64-bit
steam.sh[788431]: STEAM_RUNTIME is enabled automatically
setup.sh[788505]: Steam runtime environment up-to-date!
steam.sh[788431]: Steam client's requirements are satisfied

Now that I'm on my computer again and had a quick look at the issue, I tried running your launch command, and it didn't work for me either.
According to this bug report on Steam-for-Linux's issue tracker, Steam seems to have issues with long launch commands, and it stops working:
https://github.com/ValveSoftware/steam-for-linux/issues/5753
Since the main problem seems to be the long list of mods, you could try and short the mod links with the following diff:
diff --git a/dayz-launcher.sh b/dayz-launcher.sh
index 021695f..15bb31c 100755
--- a/dayz-launcher.sh
+++ b/dayz-launcher.sh
@@ -242,7 +242,7 @@ setup_mods() {
     local modname="$(gawk 'match($0,/name\s*=\s*"(.+)"/,m){print m[1];exit}' "${modmeta}")"
     [[ -n "${modname}" ]] || err "Missing mod name for: ${modid}"
     debug "Mod ${modid} found: ${modname}"
-    modlink="@${modid}-$(echo "${modname}" | sed -E 's/[^[:alpha:]0-9]+/_/g; s/^_|_$//g')"
+    modlink="@${modid}"

     if ! [[ -L "${dir_dayz}/${modlink}" ]]; then
       msg "Creating mod symlink for: ${modname} (${modlink})"

This only sets the mod ID in the mod directory links and thus shortens the -mod= launch parameter.
Make sure that you restart Steam prior to this.

Thanks for the response.
steam -applaunch 221100 -nolauncher
Running that just launches the game, without mods enabled. Do I need to somehow include this command with:
/home/frank/gaming/dayz-linux-cli-launcher/dayz-launcher.sh   --server <IP_ADDRESS>:2402   --port 27600   --launch   --name frank

regarding your mod ID shortening code. The red is the existing and the green is the proposed change? Where would I implement this change? (BTW I'm no coder, but I can sometimes determine the intent of certain lines and make some changes. But I am very green to this.) Looks like it's found in your script file, starting with line 242? Do I simply remove that red line and add the green in it's place? (then reboot steam)

Running that just launches the game, without mods enabled.

Yes, that was the intention. This shows that the arguments get passed to steam correctly and that the long command is the culprit here. As you can see, this doesn't include the rest of the generated launch parameters, like the long list of mods, your ingame name, etc.

BTW I'm no coder

Sorry about the confusion. It's a diff, and it means that you should replace the line
    modlink="@${modid}-$(echo "${modname}" | sed -E 's/[^[:alpha:]0-9]+/_/g; s/^_|_$//g')"

with
    modlink="@${modid}"

which essentially removes the name of the mod links. I posted the diff, because I'm interested whether shortening the mods list like this works for you. This comes at the cost of not being able to tell the mods apart (as a human).
Please run the script with the modifications applied, restart steam (just to be sure), and re-run the launcher, so that it generates a shorter mods launch parameter which steam will hopefully accept. If it does not, then my last idea is shortening the mod links further by converting the mod IDs into a string of ascii characters and converting that into a base64 string, which should save a couple more bytes.
Other than that, I guess it's up to steam to fix this. Or you'll have to set the generated launch parameters in the steam launch options manually, which should work.

That worked!!! It's launching straight into the modded server without issues.
Thank you so much for working through this with me. I've been playing dayz since 2014, and have about 2000 hours on it. I've been waiting for this day for so long.

Nice to hear that it's working.
I'll push a change later to the master branch which will reduce the mod names further, so servers can be joined with lots of mods.

0.5.0 has been released.


Feature Request : Okta Oauth2 support / Generic oauth2 support

Hello,
It would be nice if pocketbase would support Okta oauth2 as an authentication provider or a more generic way to add an Oauth provider in the admin pannel.
https://developer.okta.com/docs/reference/api/oidc/

I don't plan working on this, but users contribution for new OAuth2 providers are welcomed. If some one want to contribute, you can use the latest merged Gitea and Authentik integrations:

Gitea #1643: https://github.com/pocketbase/pocketbase/commit/4c73e16f5404383ed73aa13d4643b477f68ff48e
Authentik #1377: https://github.com/pocketbase/pocketbase/commit/6d08a5f36fb92ac00409c9405a7c8d0d5f9f18d5

(the generated ui/dist files can be ignored)
Support for creating external OAuth2 providers from the Admin UI is not planned because each integration requires some manual mapping (and sometimes even more than 1 request to fetch the necessary user data) and this will differ from one provider to another.


docs: schema evolution

Adds a documentation section for schema evolution methods, describing each.
Consolidates methods for schema evolution in Rust, so they have their own header.

Make sure to answer these questions: https://github.com/lancedb/lance/pull/1909#discussion_r1482905944

Codecov Report
Attention: Patch coverage is 68.35443% with 25 lines in your changes missing coverage. Please review.

Project coverage is 79.42%. Comparing base (8c2667d) to head (c391044).

Files
Patch %
Lines

rust/lance/src/dataset.rs
68.35%
21 Missing and 4 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1911      +/-   ##
==========================================
+ Coverage   79.41%   79.42%   +0.01%
==========================================
  Files         223      223
  Lines       65082    65082
  Branches    65082    65082
==========================================
+ Hits        51686    51694       +8
- Misses      10396    10400       +4
+ Partials     3000     2988      -12

Flag
Coverage Δ

unittests
79.42% <68.35%> (+0.01%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[FLINK-14625][table-planner-blink] Add a rule to eliminate cross join as much as possible without statistics

What is the purpose of the change
This PR introduces a rule to eliminate cross join as much as possible (the EliminateCrossJoinRule) without the help of statistics. A detailed explanation of this rule can be seen here.
As the newly introduced rule is in conflict with the cost-based join reorder rule to some extent, the old "table.optimizer.join-reorder-enabled" config key is now deprecated. This PR also introduces a new "table.optimizer.join-reorder-strategy" config key to select which join reorder rule to apply (NONE, ELIMINATE_CROSS_JOIN or COST_BASED).
Brief change log

Introduce the new EliminateCrossJoinRule.
Deprecate "table.optimizer.join-reorder-enabled" and add a new config key "table.optimizer.join-reorder-strategy".

Verifying this change
This change added tests and can be verified as follows: run the newly added EliminateCrossJoinRuleTest
Does this pull request potentially affect one of the following parts:

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

Documentation

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

LGTM,  cc @KurtYoung


Update async-executor to 1.9.0

Objective
I've been sending a few PRs to improve async-executor's performance. This updates Bevy to use the improved implementation.
Most notably, this should reintroduce the local-queue optimization that lets the executor reschedule tasks onto the thread-local queue instead of the global injector queue when possible, which should significantly reduce the amount of contention on the global injector queue.
Solution
Update async-executor to 1.9.0, and update other dependencies to minimize the number of duplicates in the tree.

Shoot, it looks like we introduced yet another deadlock.

I think I found it, the way that we're using ThreadExecutor likely breaks this, since it'll push to a local queue instead of the global queue, which never gets pulled and run.

is that because .tick doesn't pull from the local queue?

is that because .tick doesn't pull from the local queue?

It's probably because tick doesn't work steal, but run does.

We could switch to use .run. I think it was a perf hit, which is why I didn't use it originally.

The more complete solution might be to file a PR to ensure that tick falls back to searching for a task to run from other threads.

version 1.9.0 is semver compatible with the 1.7.2 so it's already selected for new projects / on cargo update https://github.com/bevyengine/bevy/issues/12044

1.9.1 released, but unfortunately reverted the thread-local changes (again). This should just be a version bump now.

What's the current status of this PR? Latest async-executor release is 1.12.0


Prepare for the dataset

Hi, do you know what dataset is used exactly? There are many parts of the KITTI Bird's Eye View dataset. I don't know which should I download. Thank you.
Bird's Eye View Evaluation 2017:
Download left color images of object data set (12 GB)
Download right color images, if you want to use stereo information (12 GB)
Download the 3 temporally preceding frames (left color) (36 GB)
Download the 3 temporally preceding frames (right color) (36 GB)
Download Velodyne point clouds, if you want to use laser information (29 GB)
Download camera calibration matrices of object data set (16 MB)
Download training labels of object data set (5 MB)

@seanxu889 did you know now which should we download?

Download Velodyne point clouds, if you want to use laser information (29 GB)
Download camera calibration matrices of object data set (16 MB)
Download training labels of object data set (5 MB)


don't test "compact on launch" if the Realm is open on another thread

Fixes #5010. Depends on realm/realm-object-store#496.

This is ready for review again, now that https://github.com/realm/realm-object-store/pull/496 has been merged.

Rebased to move the changelog entry to the appropriate section. This should be easy to review, it's just tests /cc @tgoyne


MacOS : ShowModal create an empty windows

When I try to open a modal window with .ShowModal<T>() the contant is not rendered and closing that empty window crash the app.
Some breakpoints still work like in event Closing or Activating.

fixed in avalonia.native available now. http://avaloniaui.net/blog/2018-10-09-avalonia-native-osx


Fix unhandled Redis exception in the /api/server/health/ endpoint

Motivation and context

CustomCacheBackend does not handle RedisError, so if Redis is not responding, the backend will propagate the exception, and the endpoint will crash with a 500 response code.
This problem has been fixed upstream in django-health-check 3.18, so just update to the latest version and remove our custom cache backend.
The upstream version, unlike ours, doesn't handle sqlite3.DatabaseError, but we're not using SQLite for caching anymore, so I don't think it matters.
How has this been tested?

I checked the endpoint with both working and non-working Redis.
Checklist

[x] I submit my changes into the develop branch
[x] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@azhavoro Would you mind reviewing this?


[Internal] Move to Java 8 and AGP 7

Version 8.0 of FirebaseUI can/should require Java 8 to allow us to take on newer dependencies. This also partially unblocks a future move to Kotlin.
cc @rosariopfernandes

Looks like the latest version of AGP is 7.0.0-beta05:
https://maven.google.com/web/index.html?q=com.android.tools.#com.android.tools.build:gradle:7.0.0-beta05
@rosariopfernandes have you heard anything about when 7.0.0 stable will be out?

@samtstern Not really, but I know Jetpack Compose is going stable this month (rc01 is out). I'm guessing AGP7 will be stable alongside Compose and AS Arctic Fox.

This has been implemented and released in version 8.0.0


SAK-46197: Theme tab listed as first of the Preferences tabs makes to…

…ol inaccessible

Thank you so much @hornersa.


Document options of command line

Hello,
I have trouble understanding all the options of the command line, could there be a usage section where it is described?
Cheers!

I've set a description for the CLI options, see https://github.com/alien-tools/roseau?tab=readme-ov-file#as-a-cli-tool

LGTM, except perhaps: --report=<reportPath> Where to write the breaking changes report; defaults to report.json. I think it's misleading since the report seems to be written in CSV?


Notification template config

add notification configuration options for notification_template

I don't think this huge PR is going to get approved, bud.


Bug: Remove a mouse pointer offset from the MOVE-function

URL
https://www.openstreetmap.org/edit?node=3601257040#map=24/40.70716/-74.05495
How to reproduce the issue?
1 Goto to https://www.openstreetmap.org/edit?node=3601257040#map=24/40.70716/-74.05495
2 Right click the tree object
3 From the context menu select MOVE
4 Move the mouse slowly downwards and see the jump of the tree marker from the original mouse position to a bit more down position.
Expected behavior: Start the movement of the tree object exactly at this xy-coordinates from the last position.
Screenshot(s) or anything else?
Movie:

Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
iD 2.25.1
Which browsers are you seeing this problem on?
Firefox

It's still open issue.
At least i found possible current workaround.
By using the keyboard shortcut letter M there is no drawing offset noticed.


split chunks for async chunk doesn't work

Do you want to request a feature or report a bug?
bug
What is the current behavior?
there's no async-vendors chunk.
If the current behavior is a bug, please provide the steps to reproduce.
reproduce repo
What is the expected behavior?
async-vendors chunk should be generated.
Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
Node:  v9.3.0
webpack: v4.1.0
OS: macOS 10.13.1
webpack config
module.exports = {
  mode: 'production',
  output: {
    filename: '[name].[chunkhash].js',
    chunkFilename: '[name].[chunkhash].js'
  },
  optimization: {
    splitChunks: {
      cacheGroups: {
        vendors: {
          test: /[\\/]node_modules[\\/]/,
          chunks: 'initial',
          priority: -10,
          name: 'vendors',
        },
        'async-vendors': {
          test: /[\\/]node_modules[\\/]/,
          minChunks: 2,
          chunks: 'async',
          priority: 0,
          name: 'async-vendors'
        }
      }
    },
    runtimeChunk: true,
    namedModules: true,
    namedChunks: true
  }
}

Thanks for the report!


Give each class its own file in proper module

Cleans up the single-file class/monkeypatches/rake tasks into more digestable pieces.

Moves Motion::Cocoapods out of the Motion::Project namespace, as the gem name implies
Breaks apart Motion::Project nesting to ensure there's never a Motion is undefined error
moves rake tasks into lib/tasks directory
groups all requirements into one location

I can't agree this changing.
Will we really need the changing of class namespace?
If there is user's project to refer Motion::Project::CocoaPods,
this changing causes an error easily at build time.
So, I think we have to change the APIs/name spaces with carefully so much if need it.
Don't you think so? :)

I find that logic very frustrating and in line with "we picked an architecture and we're sticking with it, we know it's bad but whatever". This PR brings the code more in line with established module and file naming conventions, which is important for the accessibility of projects that live outside an organization. I realize that this is a HipByte gem, but reaching into the Motion::Project namespace is a very bad practice as this project shouldn't really be touching anything in there except to monkey-patch in the methods that it needs to. I'd urge you to reconsider, even if it requires a 2.0 release and will be continuing to work on my fork where these changes have been made. cc @MarkVillacampa

@jbender First of all, thank you for taking time to contribute.
I have to agree with @watson1978 here.

This project is feature complete (at least for the foreseeable future).
Having all the code in one file is very convenient in a small footprint library like this.

Releasing a 2.0 version just for this change, without any other feature improvements, does not really make sense and can cause confusion for end users.
We should definitely consider this patch if/when we work on a 2.0 version, possibly containing more features that would benefit from better code organization.

Understood, I felt like I had to do this in order to understand what the gem was even doing in order to diagnose the source two bugs in my build tasks:
The first being a repeated error in my build task:
ld: warning: directory not found for option '-L/AFNetworking'
ld: warning: directory not found for option '-L/Bolts'
ld: warning: directory not found for option '-L/DeviceUtil'
ld: warning: directory not found for option '-L/FBSDKCoreKit'
ld: warning: directory not found for option '-L/GTMNSStringHTMLAdditions'
ld: warning: directory not found for option '-L/Mixpanel'
ld: warning: directory not found for option '-L/RSColorPicker'
ld: warning: directory not found for option '-L/SDWebImage'
ld: warning: directory not found for option '-L/UICKeyChainStore'
ld: warning: directory not found for option '-L/XLForm'

which then gets repeated about a dozen times until (presumably) it fails enough that it just gets skipped.
Secondly, the fact that running rake pod:install will always regenerate the Pods project (even if there are no actual Pod changes), which in turn forces the entire Pods directory to be recompiled every time (very resource inefficient and prevents caching on CI builds).
I think that calling this gem 'feature complete' is a little premature. I don't care to have an argument over it in a closed PR, but hope you can appreciate the frustration.
Cheers!

'Feature complete' does not mean the same as 'bug free' :) I totally understand your frustration and appreciate that instead of filing an issue you tried to read and understand the code. If only everybody did the same! :)
Regarding the first issue, please try and see if you can easily reproduce in a new project. If so please file an issue and we will try to fix it.
Regarding the second issue, it is the intended behaviour of Cocoapods (to reinstall all Pods on pod install) and that's not something we can change in motion cocoapods.
This article about the differences between pod install and pod update may be of interest: https://guides.cocoapods.org/using/pod-install-vs-update.html

Re: the second point, you're suggesting that the following is the expected behavior?
$ rake pod:install
... actually installs pods, generates Pods project ...
$ rake
... see pods compile ...
$ rake pod:install
... nothing changes, including Podfile.lock, but still generates Pods project ...
$ rake
... see pods compile again ...

Sorry I must have misunderstood you. That should definitely not happen (I just double checked locally).
Can you try in a fresh project, and, if you observe the behaviour there as well, open a new issue?


Failing in clean new project on code spaces

.devcontainer
// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/typescript-node
{
"name": "Node.js & TypeScript",
// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
"image": "mcr.microsoft.com/devcontainers/typescript-node:0-18",
"features": {
"ghcr.io/stuartleeks/dev-container-features/shell-history:0": {},
"devwasm.azurecr.io/dev-wasm/dev-wasm-feature/rust-wasi:0": {}
},
// Features to add to the dev container. More info: https://containers.dev/features.
// "features": {},
// Use 'forwardPorts' to make a list of ports inside the container available locally.
// "forwardPorts": [],
// Use 'postCreateCommand' to run commands after the container is created.
// "postCreateCommand": "yarn install",
// Configure tool-specific properties.
"customizations": {
"vscode": {
"settings": {
"[azure-pipelines]": {
"editor.defaultFormatter": "esbenp.prettier-vscode"
}
},
// Add the IDs of extensions you want installed when the container is created.
"extensions": [
"eamodio.gitlens",
"davidanson.vscode-markdownlint",
"hashicorp.terraform",
"ms-azuretools.vscode-docker",
"ms-vscode.azurecli",
"ms-azuretools.vscode-azureterraform",
"ms-azuretools.vscode-azurefunctions",
"ms-azure-devops.azure-pipelines",
"esbenp.prettier-vscode",
"rust-lang.rust",
"bungcip.better-toml",
"vadimcn.vscode-lldb",
"loiane.ts-extension-pack",
"dbaeumer.vscode-eslint"
]
}
}
// Uncomment to connect as root instead.  Node.js v14.21.1. linux 5.4.0-1098-azure x64.
2023-01-23 09:22:01.594Z: {"outcome":"error","message":"Failed to process feature devwasm.azurecr.io/dev-wasm/dev-wasm-feature/rust-wasi:0","description":"An error occurred setting up the container."}
2023-01-23 09:22:01.602Z: Error: Failed to process feature devwasm.azurecr.io/dev-wasm/dev-wasm-feature/rust-wasi:0
2023-01-23 09:22:01.606Z:     at one (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1777:3059)
2023-01-23 09:22:01.619Z:     at processTicksAndRejections (internal/process/task_queues.js:95:5)
2023-01-23 09:22:01.631Z:     at async nm (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1777:2227)
2023-01-23 09:22:01.638Z:     at async Mf (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1779:1383)
2023-01-23 09:22:01.642Z:     at async am (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1779:308)
2023-01-23 09:22:01.647Z:     at async EF (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1865:2001)
2023-01-23 09:22:01.650Z:     at async x7 (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1865:901)
2023-01-23 09:22:01.657Z:     at async oie (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1871:2093)
2023-01-23 09:22:01.664Z:     at async qf (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1871:3239)
2023-01-23 09:22:01.669Z:     at async Mse (/usr/lib/node_modules/@microsoft/vscode-dev-containers-cli/dist/spec-node/devContainersSpecCLI.js:1995:16211)
2023-01-23 09:22:01.676Z: devcontainer process exited with exit code 1
====================================== ERROR ====================================
2023-01-23 09:22:01.685Z: Failed to create container.
2023-01-23 09:22:01.693Z: Error: Failed to process feature devwasm.azurecr.io/dev-wasm/dev-wasm-feature/rust-wasi:0
2023-01-23 09:22:01.700Z: Error Code: 1302

Also fails with the following .devcontainer file
// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/rust
{
"name": "Rust",
// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
"image": "mcr.microsoft.com/devcontainers/rust:0-1-bullseye",
"features": {
"devwasm.azurecr.io/dev-wasm/dev-wasm-feature/rust-wasi:0": {}
}
// Features to add to the dev container. More info: https://containers.dev/features.
// "features": {},

// Use 'forwardPorts' to make a list of ports inside the container available locally.
// "forwardPorts": [],

// Use 'postCreateCommand' to run commands after the container is created.
// "postCreateCommand": "rustc --version",

// Configure tool-specific properties.
// "customizations": {},

// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
// "remoteUser": "root"

}

Ok, looking at this closer, it seems the problem is probably that there are no packages here.  If I compare to, e.g. shell history, they have a package and the link in the .devcontainer file points to it.

The problem is actually that the 0.26.0 devcontainers CLI doesn't support the Azure container registry this is fixed here:
https://github.com/devcontainers/cli/pull/341
We need codespaces to pick up the new build.

I have validated that this is now building in the current codespaces environment. Please let me know if you run into any further issues.


Question: does @ApiOperation annotation work for Spring Data Rest search operations?

I'm using SpringFox 2.6.1.
I'd like to add a summary for a search method defined in a repository interface.
This is my code:
@RepositoryRestResource
public interface ModuleRepository extends MongoRepository<Module,String> {

    @ApiOperation( "Search for some data")
    List<Module> findByCode(@ApiParam(value = "my code description") @Param("code")String code);
}

But this is the swagger output:
"/modules/search/findByCode": {
     "get": {
       "tags": [
         "Module Entity Search"
       ],
       "summary": "/findByCode",
       "operationId": "/findByCodeUsingGET",
       "consumes": [
         "application/json"
       ],
       "produces": [
         "application/*+json;charset=UTF-8",
         "application/json",
         "application/hal+json",
         "application/x-spring-data-compact+json"
       ],
       "parameters": [
         {
           "in": "body",
           "name": "param0",
           "description": "my code description",
           "required": false,
           "schema": {
             "type": "string"
           }
         }
       ],

The annotation @ApiParam works properly, but the annotation @ApiOperation seems to be ignored, in fact the summary field does not contain the value that I defined. Am I using it in a right way?
Thanks in advance.

Thats a regression that will be fixed in 2.7 I believe

Hi @dilipkrish
i think there is still a bug. I've tried the current snapshot from 2.7.0<PHONE_NUMBER>5129) and now the description for the /whatever/search path are the same as the description of the last method in the repository.
Here are an example:

The repository:
@RepositoryRestResource
public interface CustomersRepository extends JpaRepository<Customer, UUID> {
    @ApiOperation("Find customer by their firstname")
    Page<Customer> findByFirstname(
            @Param("firstname")
            @RequestParam(name = "firstname") // For swagger
            String firstname,
            Pageable pageable
    );
);

And here my dependencies:
	<dependencies>
		<dependency>
			<groupId>io.springfox</groupId>
			<artifactId>springfox-swagger2</artifactId>
			<version>2.7.0-SNAPSHOT</version>
		</dependency>
		<dependency>
			<groupId>io.springfox</groupId>
			<artifactId>springfox-swagger-ui</artifactId>
			<version>2.7.0-SNAPSHOT</version>
		</dependency>
		<dependency>
			<groupId>io.springfox</groupId>
			<artifactId>springfox-data-rest</artifactId>
			<version>2.7.0-SNAPSHOT</version>
		</dependency>
	</dependencies>

	<repositories>
		<repository>
			<id>jcenter-snapshots</id>
			<name>jcenter</name>
			<url>http://oss.jfrog.org/artifactory/oss-snapshot-local/</url>
		</repository>
	</repositories>

Interesting.. thanks for reporting back.


add example for Parse and Sign

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 36 (38.89%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 73.597%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

jwt/key_finder.go
13
35
37.14%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5848

Relevant Lines:
7946

💛  - Coveralls


FIX: make_people works with processes scheduler

[x] Closes #8094
[x] Tests added / passed
[x] Passes black dask / flake8 dask / isort dask

Can one of the admins verify this patch?

add to allowlist

This looks good to me! Thanks @DahnJ :)


Make ParsingError public?

I just started migrating over to the latest version of swift-parsing. While doing that, I had some custom parsers that I wanted to update to the new throwing style. One of my parsers has a minCharacters variable and when I can't find that chars, I'd like to throw a ParsingError. But when I do, I get an error because ParsingError seems to be internal to the library. Is there any reason we shouldn't have access to the ParsingError type for our custom parsers? While I could write my own error type, wouldn't it be more convenient if all parsers would throw the same errors?
Here's my custom parser:
/// A parser that consumes all whitespace characters from the beginning of the input. No output.
struct Whitespaces: Parser {
  let minCharacters: Int

  init(
    minCharacters: Int = 0
  ) {
    self.minCharacters = minCharacters
  }

  func parse(_ input: inout Substring) throws {
    let foundWhitespaces = input.prefix { char in
      char == " " || char == "\n" || char == "\r" || char == "\t"
    }

    guard foundWhitespaces.count >= minCharacters else {
      throw ParsingError.expectedInput("\(minCharacters) whitespaces", at: input)
      // => ERROR: Cannot find 'ParsingError' in scope
    }

    input.removeFirst(foundWhitespaces.count)
  }
}

@Jeehut I'm going to convert this to a discussion since it's not a bug but an intentionally internal type while its APIs become more fully baked.


Correctly handle seq_lengths in lstm_ref

Changes

Correctly returns the last valid carry according to seq_lengths
Zero-out padded outputs
Improves tests to check for NaNs in loss and grad of the lstm and lstm_ref functions.

cc @zhangqiaorjc

(The lint failure is preexisting/unrelated)

Thanks @cgarciae !

@cgarciae needs to run linter

Are you able to rebase on main?

GPU tests will probably fail until the gradient for rnn.lstm if fixed.
I can rebase when that is ready

LSTM should be fixed now


AE49_181128_194045.677

Type: Missing
Summary:
License
Details:
Add Apache 2.0
Resolution:
https://github.com/aspnet/HtmlAbstractions/blob/2.1.0/LICENSE.txt
Affected definitions:

Microsoft.AspNetCore.Hosting.Server.Abstractions 2.1.0

Duplicate of #789


[CCI][GUIDE] Added Guide for Snapshot API(snapshot.md)

Description
Added Snapshot Actions Guide (guides/snapshot.md) with code examples
Issues Resolved
issue #406 resolved
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Needs actual content in snapshot.md :)

Ohhh I see, the changes weren't properly saved. It's fixed now!

Maybe we can add a link in USER_GUIDE.md as well as links to other guides

@roma2023 feel free to add those links

So, I am going to update USER_GUIDE.md, should I open a new PR for it to specify the change?

So, I am going to update USER_GUIDE.md, should I open a new PR for it to specify the change?

Do it part of this PR!

Sorry for being late to this, let's finish it? We've done some reorganizing, so rebase this change please. I also added working samples to samples, want to add a working piece of code into this PR?

Yes, let's finish this. I can use working pieces of the 'Hello World' sample.

@roma2023, Could you please make the requested changes when you have a moment? Thank you!

Please check new PR #486 and let's finish this task. I apologize for the delay.


Rename main branch from master to main

What is changing?
Every repository in the Lookyloo org is using main as the main branch, in order to be consistent, we should move the docs to use the same scheme.
How will this impact users?
They will need to rename their branch locally, as described here: https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
To which release does this apply?

[x] Current release

Additional information
We need to update the configuration of the repository on github too, and remove the existing master branch to avoid confusion.

This has been resolved


read only registers look editable

Describe the bug
For example color register on LED (single) looks editable, but it can't be edited.

In which view in particular?

https://microsoft.github.io/jacdac-docs/services/led/playground/

Fixed by https://github.com/microsoft/jacdac-docs/commit/72396c704f931e1778d5c8062998a830b84d2a8f


Remove playwright replay on macOS and Windows

📝 Description
To speed up our CI and minimize usage of our runners we don't want to replay our desktop e2e tests on Windows and MacOS.
New workflow: https://github.com/LedgerHQ/ledger-live/actions/runs/7797832626

❓ Context

JIRA or GitHub link: https://ledgerhq.atlassian.net/browse/LIVE-11137

✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[ ] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

@KVNLS can you remove all screenshots related to mac and windows then? before they become all outdated and so we stop using them as possible reference?

Nice catch thank you! I created the PR here: https://github.com/LedgerHQ/ledger-live/pull/6102


Documentation: Create ADQS vignette

Please select a category the issue is focused on?
User Guides
Let us know where something needs a refresh or put your idea here!
A vignette for creating questionnaires ADaM datasets should be created.
The vignette is different from other ADaM vignettes because it is expected that there is more than one questionnaires dataset within a study. Thus the vignette should provide sections for different sort of parameters and the users can pick those sections they need.
Possible sections could be:

Deriving ADQS Parameters for Original Items
Deriving ADQS Parameters for Scales
Deriving ADQS Parameters for Time to Deterioration/Improvement
Deriving ADQS Parameters for Time to Confirmed/Definitive Deterioration/Improvement
Deriving ADQS Parameters for Worst/Best Answer
Deriving ADQS Parameters for Completion

We should look at the examples from CDISC referenced in this issue - https://github.com/pharmaverse/admiral/issues/1266

I hope we can include a first version in the Q1 release.

@pharmaverse/admiral Any takers?  We got about 3 weeks to make a vignette!

@bundfussr has taken on making this vignette!


Problem with flutter run --profile

When I try to install my App using the flutter_map package with  flutter run --profile I get the following error.

flutter run --profile
Initializing gradle...                                              3.5s
Resolving dependencies...                                           3.4s
Launching lib/main.dart in profile mode...
../../third_party/dart/runtime/vm/compiler/aot/precompiler.cc: 1839: error: Want to drop class Library:'package:latlong/latlong.dart' Class: Vincenty, but it has 1 instances

thread=19414, isolate=isolate(0x1b3d4b0)
  [0x0000000000482f7c] Unknown symbol
  [0x0000000000482f7c] Unknown symbol
-- End of DumpStackTrace
Dart snapshot generator failed with exit code -6
Snapshotting exited with non-zero exit code: -6
Running Gradle task 'assembleProfile'...
Running Gradle task 'assembleProfile'... Done                      28.9s
Gradle task assembleProfile failed with exit code 1

I already tried to remove all packages and reinstall them to see if something would change but I always get the same error.

hmm. This part seems odd:
error: Want to drop class Library:'package:latlong/latlong.dart' Class: Vincenty, but it has 1 instances

Do you know what Vincenty could be referring to? I don't see it anywhere in the latlong package

Ah... It looks like it  could be an issue with the latlong package https://github.com/MikeMitterer/dart-latlong or a bug with the AOT compiler

I tried to install the same project using other computer and it worked fine. It has to had been a bug in the installation maybe or as you say with de compiler.
I would try to reinstall flutter and see if that solves the problem.
Thx for the quick answers

I have the same problem. I redownloaded the flutter SDK but no luck. Does anyone know a workaround?

This seems like an issue with your local setup on windows. Please re-open if I'm misunderstanding


Implementation for CachedMeshContent

This pull request implements the CachedMeshContent and solves issue #97.

I have now added two unit tests to the m3d module.

The first compares the original model to the one after being serialized and deserialized.
The second one compares the original model to the one loaded from the CachedContent.

Merged! Thank you :-)


New attribute value vs. Previous attribute value

[Enter feedback here]
I strongly suspect the values listed in the table concerning "New attribute value and Previous attribute value" for the channel is backwards.  I just built a new deployment, and the channel is listed as Broad, where the configuration.xml I had from a few months ago says SemiAnnual.  Your chart here says the NEW attributes include SemiAnnual etc. and the PREVIOUS lists Broad.  Isn't this backwards?
Bruce

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

ID: 65a95a12-d57e-291b-3042-3012ebd7e4a2
Version Independent ID: 3f096623-9336-3cf5-f6ef-5c63b888e8fc
Content: Changes to update channels for Microsoft 365 Apps - Deploy Office
Content Source: DeployOffice/update-channels-changes.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@brucesp1 -- the values in the table are correct. What tool are using to build your new deployment?

I am using ConfigManager. You know what though I think I made a mistake here, if I compare xml files it looks like the package I made in May says Channel="Broad" and the new one I just made this morning says Channel="SemiAnnual"
so disregard that I guess. My mistake.
From: "Daniel H. Brown"<EMAIL_ADDRESS>To: "MicrosoftDocs/OfficeDocs-DeployOffice"<EMAIL_ADDRESS>Cc: "Bruce_spies"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Sent: Thursday, June 25, 2020 11:10:27 AM
Subject: Re: [MicrosoftDocs/OfficeDocs-DeployOffice] New attribute value vs. Previous attribute value (#817)
[ https://github.com/brucesp1 | @brucesp1 ] -- the values in the table are correct. What tool are using to build your new deployment?
—
You are receiving this because you were mentioned.
Reply to this email directly, [ https://github.com/MicrosoftDocs/OfficeDocs-DeployOffice/issues/817#issuecomment-649708392 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/APHJNO6RPFN45EFHMY327UDRYOAIHANCNFSM4OIR6STQ | unsubscribe ] .

@brucesp1 -- Thanks for double-checking. Keep in mind that the previous values will still work, so you don't have to go back and update older xml files.


FAQ menu overlaps into text

please fix how the menu opens and closes. the faq question is not working seamlessly

faq menu entry 2,3,5,6,7

Done


Specify the environment for Jedi

See https://github.com/Microsoft/vscode-python/pull/1418#issuecomment-382909941 for context.

Closing as this is not necessary, please check here (https://github.com/Microsoft/vscode-python/pull/1418#issuecomment-383395613) for further details.


⚠ Bofrost.be has degraded performance

In e1265e8, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1271 ms

Resolved: Bofrost.be performance has improved in 639b48e.


hdfs under filesystem not support impersonate

Now, alluxio request hdfs is use the user that login from kerberos, it will leads to HDFS permission leak for alluxio aways use super user to access hdfs. So if hdfs under filesystem support impersonate, it seems solve the problem。

duplicate of https://github.com/Alluxio/alluxio/issues/14867


Automatic virtual traversal of the build process to determine all symbols/includes

Yo VSCode guys... When working on a complex project like adding user C modules to micropython, VSCode, even with the AI intellisense plugin enabled, fails to find the definitions and header locations of various symbols within an arbitrary source file, such as in the port/esp32 folder. Moreover, it doesn't always properly detect which macro definitions exist or are defined for a specific source file.
VSCode should be able to be told the entry point to the build process of any project (being given the exact command line argument, so it can deduce macros defined at the prompt, and read those from the environment too, and those in the cmake cache, then virtually execute all the commands step-by-step, and build a database/map of all the relevant includes/definitions for each and every source file anywhere, so that clicking on that file and asking for the definition of an arbitrary symbol, will always know exactly which file (and where) contains the definition of that file, even if there are multiple headers for different configurations (instead of occasionally correctly knowing the filename, but showing several possibilities of the same file for different architectures and asking the user to choose one).
This way VSCode then also knows which macros are defined and with which values in any source file at any moment, and can offer to dynamically replace the macros with their values for any number of substitution levels the user wishes, even completely remove them from the file, showing the user what the source file would virtually look like when all macros are replaced, but warning the user when making changes that would require changes to the original macros in the original source. To work with and use specific macros from a specific level, the user must change to that expansion level first, then modify the source code there.

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


Add methods to start/stop swap-in wallet

For the migraton use case, it is useful to be able to wait for a certain number of UTXOs to be published before doing a swap-in. The reason is that:

we want to make as few on-chain operations as possible to save fees, so it's better to group
migration swap-in have special characteristics that are only implemented for channel creation, not for splices.

The new methods startWatchSwapInWallet/stopWatchSwapInWallet are footgunny and should only be used in the context of the migration, to be removed later. Note that the Peer calls startWatchSwapInWallet at initialization, so the migration process must first stop...(), then later start...().

With the latest commit, the swap-in watcher isn't automatically started by the Peer at initialization.
The goal is to be able to handle the case where something went wrong during the migration, and only a subset of the legacy channels have been closed:

before this change, at the next restart the swap-in watcher would automatically process the closed channels and we would end up in an half-migrated state
after this change, at the next restart the app can check if all legacy channels have been closed and then:

if there are no legacy channels, enable the swap-in watcher and start the app normally
if there are some legacy channels, do the migration again, and only then enable the swap-in watcher

@dpad85 this affects the Android app, peer.startWatchSwapInWallet() must be called after initialization.


Grape.js integration

Research pending

any details on implementation?

@bhanuvrat is doing the RnD on it @nerdyk3


test add NetworkManagerTests

not complete and 1 does not reliably work

StopClientTest() isn't working probably because you're calling manager.StartClient() twice (first time in StartClientTest()). You may consider to call StopClient at the end of your StartClientTest in order to "reset" everything properly.

Such an easy fix. Thank you :)


Added support for prerelease and nightly repos

Closes #17
Summary
This PR adds support to ubuntu-prerelease and ubuntu-nightly Gazebo repositories.
Two additional tests have been added to the workflow to test the installation of harmonic on jammy and noble using the unstable repos.

Thanks for the PR!
Both prelease and nighly can be installed together, both requires to have gazebo-stable but all three can be working perfectly. Let's change the code so we can use that option.
In the PR we also need documenttion in the README about how to use these options.

Updated the function to allow both the nightly and prerelease together. All checks pass. Will be adding tests and updating README!

@j-rivero Added unit tests and updated README with instructions. All checks pass!


Added issue, feature, and documentation templates

Explanation: I have created and added three new templates to the repository, aiming to improve the GitHub issue creation process, feature requests, and documentation contributions. These templates introduce a standardized format for creating issues, requesting features, and documenting project details. By implementing these templates, contributors and maintainers will be able to collaborate more effectively.
here is demo of templates. :

@sazamansari Please Add the Gssoc label and Level label on my Merge PR otherwise it's not calculated in Gssosc Leaderboard


Hard to find when searching GitHub repos

There are a lot of copycat projects on GitHub and finding this project is hard.
For example: https://github.com/search?q=copycat+chrome+extension&ref=opensearch&type=repositories
Perhaps adding chrome extension or browser extension to the project description would help.

It's enough to be able to find it with Google.
No one takes Github's repository search engine seriously.


appimageupdatetool Error checking for changes

When running appimageupdatetool on an AppImage I just created, I get:
motofckr9k@motofckr9k-mint-desktop:~/Vircadia$ ./appimageupdatetool-x86_64.AppImage -j Vircadia-x86_64-release-latest.AppImage
qt5ct: using qt5ct plugin
zsync2:
zsync2: Reading and/or parsing .zsync file failed!
Error checking for changes!motofckr9k@motofckr9k-mint-desktop:~/Vircadia$

There is no clear indication of what the problem is. Personally I don't even know if the update information actually made it into the AppImage properly.

So apparently you can check the update information of an AppImage with ./*.AppImage --appimage-updateinfo
This revealed that the URL was just wrong. We should really be getting a "404 Not Found" back when this happens.


have generated protocol class take fields as arguments to the constructor

Currently, the constructors to the generated protocol class don't take any arguments to initialize the fields.  This makes using them more verbose without improving readability.  Suggest generate optional arguments to protocol class that initialize each field.  Idealy, they would initialize to the default value if not specified, however just defaulting to None would a big improvement.
For example, https://github.com/ga4gh/server/blob/develop/ga4gh/datamodel/variants.py#L72 CallSet.toProtocolElement()  we currently have:

         gaCallSet = protocol.CallSet()
         gaCallSet.created = self._variantSet.getCreationTime()
         gaCallSet.updated = self._variantSet.getUpdatedTime()
         gaCallSet.id = self._id
         gaCallSet.name = self._sampleName
         gaCallSet.sampleId = self._sampleName
         return gaCallSet

If protocol.Callset initialized all the class members from constructor arguments, one could have

         return protocol.CallSet(created = self._variantSet.getCreationTime(),
                                 updated = self._variantSet.getUpdatedTime()
                                 id = self._id,
                                 name = self._sampleName,
                                 sampleId = self._sampleName)

This wouldn't be difficult to do, and I think would increase readability in some situations. +1 on the idea and the changes.

This depends on #369
Once that is done, this will be a pretty easy change to process_schemas.py

Fixed in #518


update for website links

Adds links for the Village websites and modifies index.html so it pulls from the villages yaml file

closes https://github.com/beauwoods/hackervillages.github.io/issues/1

nudge


Suggestion

for server-query.py
should add the method to query usernames using a2s and if possible even steamid's using another library

server_query.py, as the name indicates, is meant to provide the ability to query a server, if I remember correctly it actually does show connected IDs, but steam is not very accurate with it and shows alot more players than are actually connected. With about 90% of the playerbase playing on Epic Games now anyways, I dont really want to spend time on trying to track steam players.

my apologies for my poor suggestion what i was ment to say it that when querying the server it also fetches the usernames connected to it, and session time (both should be possibile with a2s), and if it is possibible adding fetching steamid linked to the users in the server .
Since i couldnt find any api that does it, i might aswell suggest it for ark-api.