A11y_SQLAzureDataStudioMAC_Add Database reference_Project_VoiceOver: Voiceover does not announce the radio button grouping when the VO focus lands on 'Project', 'System Database', 'Data tier application' radio button. VO announces 'Project, selected, radio button, 1 of 3'.

GitHubTags: #A11yMAS;#A11yTCS;#A11ySev2;#BM_SQLAzureDataStudioMAC_June2022;#SQL Azure Data Studio;#MAC;#FTP;#DesktopApp;#VoiceOver;#AINotInScope;#WCAG1.3.1;
Environment Details:
Application Name: SQL Azure Data Studio
Application Version: Version 1.37.0
Mac Version: macOS Monterey 12.4
Screen Reader: Voice-Over
Repro Steps:

Please do not close this bug. This bug should only be closed by TCS, C+AI Accessibility tester after verification of the fix.
Launch SQL Azure data studio.
Connect to a server.
Install the extension 'SQL database Projects'.
Tab till 'Connected server'.
Right click and select 'Create project from database'.
New database will get created.
Right click on data base and select "Add Database references".
'Add database reference' dialog will open.
Tab till 'Project' radio button.
Turn on voiceover and observe.

Actual:
Voiceover does not announce the radio button grouping when the VO focus lands on 'Project', 'System Database', 'Data tier application' radio button. VO announces 'Project, selected, radio button, 1 of 3'.
The same issue can be observed throughout the application.
Expected:
Voiceover should announce the radio button grouping when the VO focus lands on 'Project', 'System Database', 'Data tier application' radio button. VO should announce 'Type, Project, selected, radio button, 1 of 3'. When the user leaves the last radio button VO should announce 'Group ended' and when we hit shift+ tab to the last radio button it should read the group name.
User Impact:
Screen readers users will face inconvenience if complete information of the radio buttons is not passed to the users, and the users will not know the group that the radio buttons are part off.
Attachment:

@bbarik06 this is now fixed in the latest ADS release 1.38.0.

near SLA, so closing, please let us know if this still reproes.

GithubTags:#Closed;Version 1.41.2


What about MCA

In the FAQ section https://docs.microsoft.com/en-us/azure/virtual-machines/linux/spot-vms#limitations under supported billing models, MCA is excluded.

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

ID: 5fc1cf2b-efba-fd67-2111-45a96fb9e407
Version Independent ID: 7178f530-8b62-19f2-dcfc-2be2df9d6a52
Content: Use Azure Spot VMs (Preview) - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/spot-vms.md
Service: virtual-machines-linux
GitHub Login: @cynthn
Microsoft Alias: cynthn

@cynthn Do you know if we have any guidance for Microsoft Customer Agreement (MCA) for Spot VMs? Thanks :)

@Karishma-Tiwari-MSFT That's outside of my knowledge. Adding @JagVeerappan, but he is out. Can you pull in Varun Shandilya?
@mimckitt Anyone else that might be able to answer?

Can someone elaborate on what MCA is? I am not familiar with that term.

@mimckitt I think it is Microsoft Customer Agreement (MCA).
@jabbera Can you confirm?

If that is the case, MCA is not a stand alone offering type. So not sure why it would be included in the list
https://azure.microsoft.com/en-us/support/legal/offer-details/

Essentially only those three are eligible at the moment to use SPOT. We include the others as they are also highly used subscription types and want to make it easily visible.
As availability changes, we will continue to update the document.
#please-close

@mimckitt the Microsoft Customer Agreement is not an offering type but a contract type, the same way the Enterprise Agreement is. Cf https://azure.microsoft.com/en-us/pricing/purchase-options/microsoft-customer-agreement
By the way, Enterprise Agreement is not in the /legal/offer-details/ list neither but it is in the FAQ in this documentation page.
As Azure sellers are selling to customer through this contract type nowadays, I think that a line should be included in this document, hopefully to confirm that MCA is supported.
Can you please reconsider your decision?

Updated the table. Once the PR merges the changes should go live later tonight or early tomorrow morning.
Let me know if you have any other questions.


Promoting Idempotency Through Metadata

Currently, implementing idempotent jobs over Iceberg is done via data-based predicates. For instance, if a job run is presumed to have written the data for 2018-08-05, you will write something like:
df.write(t).overwrite($"day" === "2018-08-05")

However, this may be:

Slow - Need to push down filter for partitions on rewrite and to calculate the boundary values for each write (might be slow if it's on-demand)
Incomplete (false negatives) - the predicate doesn't cover it. e.g. late arriving data included in the previous output
Overzealous (false positives) - the predicate covers it, but it's not data we want to overwrite. e.g. data that has arrived before or after this job's run for the same day
Mix domain knowledge into the operations - each job needs to understand which field determines what it wrote and what value it wrote and preserve that value somewhere

To promote more complete idempotency, we can use the metadata Iceberg provides to revert previous snapshots based on their metadata. If, for instance, Partition P1 writes file F1, and we want to re-run the job that wrote it, we can write P2 which deletes F1 and writes F2 with the new data, effectively reverting P1.
The benefits from this would be:

Snapshot isolation is preserved
No duplicate data can be read (F1+F2)
No incomplete data can be read (neither F1 nor F2)
We can revert a snapshot, regardless of how far back it happened

Note: This would only be usable in cases where we are only appending new data in snapshots, so cases where we also regularly compact or coalesce files may not be supported.
To achieve this, we could:

Use the com.netflix.iceberg.RewriteFiles operation, but this would keep us at a very low-level, close to Iceberg, and force us to manually manage the files ourselves.
Use the com.netflix.iceberg.Rollback operation, but this only rolls back the previous snapshot, which is something we don't want to be tied to.
Use the com.netflix.iceberg.DeleteFiles operation, but this would create a new snapshot, causing us to either read duplicate or incomplete data.

What could be great is an API that lets us have some sort of transaction over both high-level (Spark) and low-level (Iceberg) APIs, so that we could delete the files written in a snapshot and write data using Spark, only then committing the transaction and creating a new snapshot.
@rdblue I would love to hear what you think this kind of API would look like.

I think we're talking about different use cases that are both idempotent:

Incremental processing - I wouldn't want to build incremental processing on top of the overwrite you're referring to for the reasons you cite here. If I have a job that processes all data as it comes in, then to make it idempotent and able to re-run (e.g. after fixing a bug) then I would agree that we don't want to require filtering on the data values.
Aggregation processing - Likewise, if I have a job that aggregates another table to produce a daily summary, I would not want to revert snapshots for nearly the same reasons: What if 2 days of summaries were written in 1 snapshot? In this case, because the job knows what output data it creates, it also knows what output it should replace.

I think the right choice depends on the job and how it is written. Our data engineers write jobs all the time that overwrite specific partitions and are idempotent, but we also have a separate system for them to run incremental processing.
Also, the point about overwrite being slow doesn't really apply unless what you're trying to delete is mixed with other data you're not trying to delete. This isn't intended to support that case.
I think there is a use case for incremental processing, so I'd like to see support for writes that also revert a previous commit. I'm skeptical about an API that bridges both Spark and Iceberg, though. To do this, I'd just pass the snapshot to revert through Spark's API as a DataFrameWriter option to Iceberg. Then let Iceberg handle the revert and commit.
I think this requires:

A RevertCommit action
Support for an atomic RevertCommit with some other operation, like a ReplaceCommit. For revert + append, it could validate that the replacement commit has the same type as the reverted commit.

@omervk, you might want to have a look at #52, which adds single-table transactions. That would enable you to revert a commit and replace its data in the same commit.
Also, I've updated the Snapshots section of the spec with a set of operations to help identify what changed in a snapshot. It would be great to hear your take on the update and whether revert should be one of those actions. If so, maybe the operation info should be an object instead of a string that can encode more information, like what previous snapshot was reverted or how many data files were added/removed.


mtime set to 0 in .ninja_log for outputs of rule with restat = 1 whose sole dependency is a phony target

This was found when making a change in gn to use phony targets (https://gn-review.git.corp.google.com/c/gn/+/16920) for Chromium.
If a target use a custom rule, has restat = 1, does not modify its output, and only has phony target as outputs, then ninja will record a mtime of 0 for that target if it decides to rebuild it as part of an incremental build. From that point, the build will always be considered as dirty because the recorded mtime (0) will always be older than the mtime of the phony target.
Sample reproduction:
$ mkdir repro && cd repro
$ touch a
$ cat > build.ninja <<EOF
rule create_b
  command = test -f b || touch b
  restat = 1

build s: phony a
build b: create_b | s
EOF
$ ninja b -d explain
ninja explain: output b doesn't exist
[1/1] test -f b || touch b
$ ninja b -d explain
ninja: no work to do.
$ touch a
$ ninja b -d explain
ninja explain: restat of output b older than most recent input s<PHONE_NUMBER>851462338 vs<PHONE_NUMBER>788860000)
[1/1] test -f b || touch b
$ ninja b -d explain
ninja explain: restat of output b older than most recent input s (0 vs<PHONE_NUMBER>788860000)
[1/1] test -f b || touch b
$ cat .ninja_log
# ninja log v5
0	10<PHONE_NUMBER>851462338	b	142acf958f60ee36
1	7	0	b	142acf958f60ee36
1	7	0	b	142acf958f60ee36

As can be seen, the mtime for b is stored as 0 after the target is rebuild due to the modification of a.
I think this is because the following code in Builder::FinishCommand(...):
  // Restat the edge outputs
  TimeStamp output_mtime = 0;
  bool restat = edge->GetBindingBool("restat");
  if (!config_.dry_run) {
    bool node_cleaned = false;
    ...

    if (node_cleaned) {
      TimeStamp restat_mtime = 0;
      // If any output was cleaned, find the most recent mtime of any
      // (existing) non-order-only input or the depfile.
      for (vector<Node*>::iterator i = edge->inputs_.begin();
           i != edge->inputs_.end() - edge->order_only_deps_; ++i) {
        // here (*i)->path() is "s" which does not exist, so
        // Stat() returns 0.
        TimeStamp input_mtime = disk_interface_->Stat((*i)->path(), err);
        ...
      }

      ...

      output_mtime = restat_mtime;
    }
  }

So it looks like it reproduce with origin/release but not with origin/master.
After looking at the changes between those two branches, it looks like this was fixed by a2b5e6deff1545f5ca1947930fa59fa3ff236db7.


翻译#134

翻译的文档的 Issue 编号是：https://github.com/servicemesher/trans/issues/134
NOTE：
文章标题shaping with 意为“塑造、加工”，修饰“流量”并不合适，故翻译为“控制”；
文章中TCP ECHO Server，server在此处翻译为服务端、服务器都不贴切，故翻译为服务。

GitHub has finally published these changes to my blog: https://venilnoronha.io/raw-tcp-traffic-shaping-with-istio-1.1.0

GitHub has finally published these changes to my blog: https://venilnoronha.io/raw-tcp-traffic-shaping-with-istio-1.1.0

OK，I will follow your latest post to translate.


As an internship applicant, I can note the potential internship opportunities that I haven’t started applying

... so that I can apply for them when I finish crafting my resume specifically for them

Closes #127


Could not resolve all dependencies for configuration

Hi!
Can me help with problem?

Could not resolve all dependencies for configuration ':app:_x1DebugCompile'.
Could not find org.scala-lang:scala-library:2.11.6.
Searched in the following locations:
file:/home/alexander/sdk/android/extras/android/m2repository/org/scala-lang/scala-library/2.11.6/scala-library-2.11.6.pom
file:/home/alexander/sdk/android/extras/android/m2repository/org/scala-lang/scala-library/2.11.6/scala-library-2.11.6.jar
file:/home/alexander/sdk/android/extras/google/m2repository/org/scala-lang/scala-library/2.11.6/scala-library-2.11.6.pom
file:/home/alexander/sdk/android/extras/google/m2repository/org/scala-lang/scala-library/2.11.6/scala-library-2.11.6.jar

I make project with command "gradle build"

@ulx which repos are you using?

I using config
buildscript {
repositories {
mavenCentral()
}
dependencies {
    classpath "com.android.tools.build:gradle:1.2.3"
    classpath "jp.leafytree.gradle:gradle-android-scala-plugin:1.4"
}

}
repositories {
jcenter()
}

The error says dependency is not found in your local google repository, and should search the dependency in maven/jcenter.
If you define the repository in the root build.gradle you have to add:
allprojects {
    repositories {
        jcenter()
    }
}

Thanks!!


updated genome resources for dbSNP, clinvar

Updates for clinvar/dbSNP
This makes sure the versions in the VEP cache and the resources are more aligned
ref:https://github.com/chapmanb/cloudbiolinux/pull/273
Cheers
M

Thanks again for keeping these in sync. Much appreciated.


js - flattenObject: throws on null values and omits date objects

flattenObject omits date objects in the flattened result
flattenObject({ a: { b: new Date() } }) // result: {}
flattenObject throws when nested properties are null
flattenObject({ a: { b: null }, d: 1 }) // TypeError: Cannot convert undefined or null to object
See https://runkit.com/tbasse/5f2aaca10f979f00194eb236 for test cases

If noone is not working on this, I would like to take a stab at it.

@Sparkadelic177 Sure, go ahead. Make sure to write Resolves #1176 in the PR description and follow the guidelines. Happy coding! :smiley:


Fix mutation of input in CBC

Previously the input buffer passed into the CBC encrypt method was encrypted at the same time as the output buffer. This fix ensures that only the output buffer is encrypted, and the input buffer is not changed.
Note: complete use of "const" inputs could have made this bug more obvious.

Fixed in https://github.com/kokke/tiny-AES-c/commit/1cd676c262797c97228254072e88f8019e72f91a


Cannot modify this site because another operation is in progress. OperationName: StopContainerAppOperation

Which trigger/binding are you using?
HTTP
Which language are you using?
Python 3.11
Expected behavior
Success in restart/delete/modify config
Actual behavior
Cannot modify this site because another operation is in progress. Details: Id: 472ad74a-12b4-4686-8ac2-3132a46411d9, OperationName: StopContainerAppOperation, CreatedTime: 10/27/2024 9:27:40 PM, RequestId: 5506e854-5cac-4e18-810e-aac558bfcc5d, EntityType: 3
To Reproduce
Steps to reproduce the behavior:

Stop function app in Az portal
Attempt to restart/delete/modify config

Additional context
I created this function app today, so earlier runtime versions shouldn't be an issue in this case.
Now I can't even delete it.

We have pushed the mitigation for now for this issue, we will be deploying the long-term fix soon. Thanks.

Thanks! Delete succeeded.


undefined symbol error when loading plugin (Nuke 11.2v3)

First of all, thanks for this plugin! I managed to build and install it (I think), but when I try to drop the node into Nuke I get the following error:
/usr/local/home/fcole/.nuke/MLClient.so: undefined symbol: _ZNK2DD5Image2Op15input_longlabelB5cxx11Ei
I checked the build paths and it does seem like it is built against the Nuke version I am running (11.2v3). I've had a couple other Nuke installs on this machine, though, so wondering if this error could be caused by finding a stale library somewhere.

Hello! Glad you're enjoying it.
I think you're correct that it's linked against the wrong library. Running 'ldd' on the MLClient.so might give you a hint at the library it linked against during compilation. You could also try running 'make' in verbose mode (i.e. 'make VERBOSE=1') to print out the linker command to see what paths are being included. Hope that helps!

Hmm, after further inspection it seems to be loading the right library, but the library indeed does not seem to have the symbol it's looking for. If I do
nm -D /usr/local/Nuke11.2v3/libDDImage.so
I get output that looks like:
00000000001f88b0 T _ZN2DD5Image2Op14set_unlicensedEv
0000000000344d20 T _ZN2DD5Image2Op15add_draw_handleEPNS0_13ViewerContextE
00000000003455a0 T _ZN2DD5Image2Op15add_knob_handleEPNS0_4KnobEPNS0_13ViewerContextE
000000000024b630 T _ZN2DD5Image2Op15anyInputHandlesEPNS0_13ViewerContextE
000000000024d230 T _ZN2DD5Image2Op15disallowNoTreesEv
000000000024d240 T _ZN2DD5Image2Op15isTimingEnabledEv
000000000011e8d0 W _ZN2DD5Image2Op15pre_write_knobsEv
000000000024c7c0 T _ZN2DD5Image2Op15progressDismissEv
000000000024c570 T _ZN2DD5Image2Op15progressMessageEPKcz
0000000000a10770 D _ZN2DD5Image2Op15status_callbackE
000000000024a5b0 T _ZN2DD5Image2Op16add_input_handleEiPNS0_13ViewerContextE
So similar symbols are there, but
nm -D /usr/local/Nuke11.2v3/libDDImage.so | grep _ZNK2DD5Image2Op15input_longlabelB5cxx11Ei
returns nothing.
Can you confirm the plugin should work with Nuke 11.2v3?

Ok, I figured out the issue. I guess Nuke 11.2v3 was compiled with the old, non-cxx11 ABI. To fix this error, I had to recompile both protobuf and the client with '-D_GLIBCXX_USE_CXX11_ABI=0'.

Ah interesting, thanks for persevering, that makes more sense now!
So it seems you shouldn't be able to build plugins without that macro,
which is likely because you aren't building on CentOS or RHEL 6/7? The
compilers on these platforms by default define this macro, so we don't do
it explicitly. This is a libstdc++ thing, which the vfx platform still
keeps for backward compatibility. A new ABI was introduced in gcc 5.x but
the VFX platform explicitly wants us to keep the old ABI, which is the
default on the supported linux platforms. See
https://vfxplatform.com/#footnote-gcc6 for more info.
On Wed, Jul 17, 2019 at 9:23 PM fcole<EMAIL_ADDRESS>wrote:

Ok, I figured out the issue. I guess Nuke 11.2v3 was compiled with the
old, non-cxx11 ABI. To fix this error, I had to recompile both protobuf and
the client with '-D_GLIBCXX_USE_CXX11_ABI=0'.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TheFoundryVisionmongers/nuke-ML-server/issues/15?email_source=notifications&email_token=AAIH2BYPNN26RRG74ZIN6O3P755UFA5CNFSM4IDYBRC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2GPIIQ#issuecomment-512554018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIH2B4F633XZYLC7SNIO6TP755UFANCNFSM4IDYBRCQ
.

Hi,
I also ran into the same issue using ubuntu 18.04 LTS. Where exactly do I need to paste that line of code to fix that gcc problem?

Ok, I figured out the issue. I guess Nuke 11.2v3 was compiled with the old, non-cxx11 ABI. To fix this error, I had to recompile both protobuf and the client with '-D_GLIBCXX_USE_CXX11_ABI=0'.

Hi @UweMajer ,
I haven't tested it, but you can add the definition in the 'nuke-ML-server/CMakeLists.txt':
add_definitions(-D_GLIBCXX_USE_CXX11_ABI=0)
(from: https://stackoverflow.com/questions/50867365/what-is-difference-between-add-definitions-and-set-in-cmake-file, more info here: https://blog.conan.io/2016/03/22/From-CMake-syntax-to-libstdc++-ABI-incompatibiliy-migrations-are-always-hard.html)

for me it did not work to add the codeline provided by @ringdk , but i managed to get it running anyway on Ubuntu 18.04.3 LTS.
i installed gcc-4.8.5 and used it instead of the newer gcc which was preinstalled. recompiled protobuf and the mlserver.so, and it worked fine. (remove protobuf before installing protobuf compiled with older gcc)
my post might be useless for experienced users, but for me as a noob this would have helped so I thought I just post it.
best regards,
felix

fwiw- builds ok in 12.0 but not in 12.2, so it's a roller coaster ride of versions!

So I did a recompile ala @fcole under 12.2 and continue to see the same problem. One thing I didn't check is if the definitions 'survived' the configure since I notice that it also goes in and does some ABI related foolishness.
Next I suppose would be to build a docker / roll back my gcc ala @sprnglf ... ugh.


update dropwizard to 1.1.0 and CXF to 3.1.11

Thanks. I will merge this as soon as I fix the example application. It needs a minor update due to Hibernate upgrade in Drowpizard 1.1.0.


Bug fixed (SocksPort) and add the DataDirectory command

Fixed a bug in ClientCreateParam.cs (SocksPort hardcodded which prevented the user to specify its socks port)
Add the DataDirectory command option (ConfigurationNames.cs & Configuration.cs)

@PsykotropyK is this lib work for you?
`ClientRemoteParams remoteParams = new ClientRemoteParams();
        remoteParams.Address = "<IP_ADDRESS>";
        remoteParams.ControlPassword = "";
        remoteParams.ControlPort = 9051;

        Client client = Client.CreateForRemote(remoteParams);

        client.Proxy.Port = 8182;

        using (WebClient webClient = new WebClient())
        {
            if (client.Proxy.IsRunning)
                webClient.Proxy = client.Proxy.WebProxy;

            Console.WriteLine(webClient.DownloadString("http://bot.whatismyipaddress.com/"));
        }`

running the above code will give you a IP address of Tor node actually conected to?

Hi Tomasz,
I did not try your specific piece of code, but when I start usting the library I realized that I could not use webClient.Proxy = client.Proxy.WebProxy;. I had to recreate the proxy for the http client.
Something like this should work :
webClient.Proxy = new Webproxy() { Address = new Uri(client.Proxy.Address) };
Then It showed a Tor exit node ip instead of my ip.
Hope it will help you.
Ciao

@PsykotropyK by WebProxy class you mean this or some custom?

Yes, System.Net


cctools-llvm: init at 11.1.0-973.0.1

Note: This is targeting staging because it will be needed by Darwin stdenv changes that will need to go through staging.
Description of changes
cctools-llvm is a replacement for cctools that replaces as much of cctools with equivalents from LLVM that it can reasonably do. This was motivated by wanting to reduce dependencies on cctools, which are updated infrequently by upstream.
To provide a motivating example, the version of strip included in cctools cannot properly strip the archives in compiler-rt in LLVM 15. Paths are left to bootstrap tools, resulting in failed requisites checks in the final stdenv build. Since strip needs replaced, the opportunity was taken to replace other provided they are functional replacements.
Note: This has to be done in cctools (or some equivalent) because some derivations (noteably LLVM) use the bintools of the stdenv directly instead of going through the wrapper.
The following tools from LLVM are not used in this derivation:

LLD - not fully compatible with ld64 yet and potentially too big of a change;
libtool - not a drop-in replacement yet because it does not support linker passthrough, which is needed by xcbuild;
lipo - crashes when running the LLVM test suite;
install_name_tool - fails when trying to build swift-corefoundation; and.
randlib - not completely a drop-in replacement, so leaving it out for now.

If other incompatabilities are found, the tools can be reverted or made conditional. For example, cctools strip is preferred on older versions of LLVM (which lack the compiler-rt issue) or when cctools itself is a new enough version because llvm-strip on LLVM 11 produces files that older verions of codesign_allocate cannot process correctly.
One final caveat/note: Some tools are not duplicated or linked from cctools-port. The names of the tools and which ones were linked was determined based on what is provided upstream in Xcode and is installed on macOS system.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I’m doing a rebuild to make sure it works, but I’ll be pushing an update to this PR later tonight that incorporates your feedback @toonn. I’ve also made a few additional changes:

I dropped useLLD because it’s untested and complicates things; and
Reverted back to ranlib from cctools because llvm-ranlib is not a drop-in replacement.

IIUC this won't actually be used until a later PR, right?

Correct. Once the prerequisite PRs are merged, I’ll open a PR with the stdenv rework that decouples it from the bootstrap tools. It will still target LLVM 11, but that will set things up to do a separate PR that only bumps LLVM.

The latest push fixes the issue with darwin.cctools not being the same thing as darwin.cctools-port.

Looks like case-insensitive HFS strikes again for cctools-apple

I’m using case-sensitive APFS, and I get the same error. I think the hashes changed when Apple started redirecting downloads to GitHub.

And cctools-llvm seems to be missing machocheck, I don't think that was intentional?

I only linked binaries that correspond to what Apple ships (as part of macOS or Xcode), so an omission may be intentional. However, I don’t see macrocheck in cctools-port, and grepping the source (and nixpkgs) turns up nothing. I’m not sure what that is.

@reckenrode, not macrocheck, machocheck.

I created #235975 to fix the hashes on cctools-apple. I’ll also be opening a separate PR to fix cctools-port on x86_64-darwin when built with clang 16.

@reckenrode, not macrocheck, machocheck.

Replying here to document since this was discussed on Matrix: Apple doesn’t appear to ship machocheck, so it’s not included. It looks like it’s used by ld64 for some tests.

I think I fixed the cctool ≠ cctools-port issue. I’m not sure using rec was the right approach, but neither self.cctools-port nor pkgs.targetPackages.darwin.cctools-port is the same as the cctools-port that’s created directly by callPackage.

@toonn I figured out the problem. The stdenv defines an overlay that sets darwin.cctools to the one built during the stdenv build. That results in darwin.cctools having a different value from darwin.cctools-port. I didn’t catch that during development because my stdenv rework branch was already including the additional attributes. When I cherry-picked the commit onto master, I didn’t update the stdenv to include cctools-port. I pushed an update that does.

$ nix-build --pure --no-out-link -A darwin.cctools -A darwin.cctools-port
/nix/store/3p2xdd5xmrc0qyi10lf95nbydcyprqy9-cctools-port-973.0.1
/nix/store/3p2xdd5xmrc0qyi10lf95nbydcyprqy9-cctools-port-973.0.1

The latest push fixed a typo. Even with man pages enabled, it wasn’t installing any of them because the check for $sourcePath was missing the leading $.

Hmm, am I wrong in expecting this to give me the man pages?

No, you’re not wrong. Are you using the latest commits? I pushed some fixes last night when I found that enabling the man pages in my rework branch wasn’t working as expected.

I see what’s happening with the man pages. The man page for otool just includes llvm-otool.1, which does not exist in the cctools-llvm man output. I can special case it. However, it still won’t load because the man page is compressed. You can see an example of that below for cctools-port. It seems like that should be addressed in cctools. I’ve pushed an updated branch that special cases otool and ld64.
/usr/bin/man -d  /nix/store/6q78w47d2y74p97x52ps5xg7f9d6c9g1-cctools-port-973.0.1-man/share/man/man1/otool.1.gz
-- Using pager: less -R
-- Using manual sections: 1:8:2:3:3lua:n:4:5:6:7:9:l
-- Searching PATH for man directories
--   Adding /etc/profiles/per-user/reckenrode/share/man to manpath
--   Adding /run/current-system/sw/share/man to manpath
--   Adding /usr/share/man to manpath
--   Adding /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/share/man to manpath
--   Adding /Applications/Xcode.app/Contents/Developer/usr/share/man to manpath
--   Adding /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/man to manpath
-- Adding default manpath entries
-- Parsing config file: /etc/man.conf
-- Using manual path: /etc/profiles/per-user/reckenrode/share/man:/run/current-system/sw/share/man:/usr/share/man:/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/share/man:/Applications/Xcode.app/Contents/Developer/usr/share/man:/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/man
-- Using locale paths: en_US.UTF-8:en.UTF-8:.
-- Using non-standard page width: 185
-- Searching for /nix/store/6q78w47d2y74p97x52ps5xg7f9d6c9g1-cctools-port-973.0.1-man/share/man/man1/otool.1.gz
-- Found a usable page, displaying that
-- /nix/store/6q78w47d2y74p97x52ps5xg7f9d6c9g1-cctools-port-973.0.1-man/share/man/man1/otool.1.gz includes man1/llvm-otool.1
--   Unable to find man1/llvm-otool.1


Remove version 2<IP_ADDRESS> of RemoteDesktopManagerFree

This PR removes version 2<IP_ADDRESS> of Remote Desktop Manager Free by Devolutions. RDM Free has been discontinued since October 2022, it should not be used anymore since it will require a free license which cannot be generated anymore. Please see the official blog regarding this: https://blog.devolutions.net/2022/10/news-remote-desktop-manager-is-changing-for-the-better/
Microsoft Reviewers: Open in CodeFlow

URL: https://cdn.devolutions.net/download/Setup.RemoteDesktopManagerFree.2<IP_ADDRESS>.msi
Status Code: 200
(Automated message - build 737)

URL: https://cdn.devolutions.net/download/Setup.RemoteDesktopManagerFree.2<IP_ADDRESS>.msi Status Code: 200
(Automated message - build 737)

The file stills exists on our CDN, but it should not be used anymore

URL: https://cdn.devolutions.net/download/Setup.RemoteDesktopManagerFree.2<IP_ADDRESS>.msi
Status Code: 200
(Automated message - build 738)


"Cocorăștii Colț" is listed in the drop-down menu

Description:
When user writes "Cocorăștii Colț" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Cocorăștii Colț"
Expected results
The location appears in the drop-down menu as "Comuna Cocorăștii Colț, PRAHOVA"


Test "test repeat write 2" failed

Mode : NATIVE
branch : master_1327
commit : 5fa2c64
Logs:
6p - https://gist.github.com/evabishchevich/d468157c95c85ff0a63936c44c62b6ef
6p - https://gist.github.com/evabishchevich/ce6217b13201546cbb7be62115b0783c
s7 - https://gist.github.com/evabishchevich/0f20b28cba6de4fb93b3808ea8cb5750
server - https://gist.github.com/evabishchevich/91d5c6ac1a973751e356dea3c811d655

s7 - https://gist.github.com/evabishchevich/37f27605b2c9027307b327e94cca73ad
6p - https://gist.github.com/evabishchevich/3aea60040d6e52db4a5a7cc41cfb8b0a
6p - https://gist.github.com/evabishchevich/868373dc1a341db34a270a2bc1170155
server - https://gist.github.com/evabishchevich/a1070d42c3573fd7c5ddd805539bb0fe

6p - https://gist.github.com/evabishchevich/b67dd9e3c8e81cc535d3e2595aca6bae
6p - https://gist.github.com/evabishchevich/0667876207e9931caf60fcee01168954
server - https://gist.github.com/evabishchevich/a8d0183e27db1d26527bcdb233e3628e

With thaliPeerPoolOneAtATime
6p - https://gist.github.com/evabishchevich/782a346ecc8219e5c7666d8a1baea5b9
6p -  https://gist.github.com/evabishchevich/6c65ca2d8e1c74608cdee44bf7cda218
server - https://gist.github.com/evabishchevich/f8d0d9204ee9025d8b00723193b77961

6p - https://gist.github.com/evabishchevich/49a454de063496eb160b860fa98c5aaf
6p - https://gist.github.com/evabishchevich/dce5334742179b9f2c79c8956d72b207
server - https://gist.github.com/evabishchevich/feadb428d6cd191556342f51188dd877

Need to fix thaliproject/Thali_CordovaPlugin#1377 because different generations cause problems in this test


[ffmpeg] build failure: configure script is not executable

While compiling ffmpeg for x64-linux, the configure file (part of ffmpeg source) called by build_linux.sh is not executable, and the build fails.
See workaround indicated under "Additional Context" - I explicitly enable the executable permission of the configure file before it is invoked from build_linux.sh
Host Environment

OS: Linux x64 Ubuntu 18.04
Compiler: gcc

To Reproduce
Add Triplet: x64-linux-dynamic.cmake
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE dynamic)

set(VCPKG_CMAKE_SYSTEM_NAME Linux)

Install:
./vcpkg install ffmpeg:x64-linux-dynamic

Failure logs
Replaced local path with XXXXX for privacy:
Command failed: /bin/bash --noprofile --norc XXXXX/vcpkg/ports/ffmpeg/build_linux.sh XXXXX/vcpkg/buildtrees/ffmpeg/x64-linux-dynamic-rel XXXXX/vcpkg/buildtrees/ffmpeg/src/n4.2-02d8c63f80 XXXXX/vcpkg/packages/ffmpeg_x64-linux-dynamic "--enable-asm --enable-yasm --disable-doc --enable-debug --enable-runtime-cpudetect --disable-openssl --disable-ffmpeg --disable-ffplay --disable-ffprobe --disable-libvpx --disable-libx264 --disable-opencl --disable-lzma --disable-bzlib --enable-avresample --enable-cuda --enable-nvenc --enable-cuvid --disable-libnpp  --disable-static --enable-shared "
    Working Directory: XXXXX/vcpkg/buildtrees/ffmpeg/x64-linux-dynamic-rel
    Error code: 126
    See logs for more information:
      XXXXX/vcpkg/buildtrees/ffmpeg/build-x64-linux-dynamic-rel-out.log
      XXXXX/vcpkg/buildtrees/ffmpeg/build-x64-linux-dynamic-rel-err.log

Contents of XXXXX/vcpkg/buildtrees/ffmpeg/build-x64-linux-dynamic-rel-err.log
/home/mbertola/code/clean/vcpkg-suosdk/ports/ffmpeg/build_linux.sh: line 20: /home/mbertola/code/clean/vcpkg-suosdk/buildtrees/ffmpeg/src/n4.2-02d8c63f80/configure: Permission denied

Additional context
Adding chmod a+x "$PATH_TO_SRC_DIR/configure" to build_linux.sh works.
echo "=== CONFIGURING ==="
chmod a+x "$PATH_TO_SRC_DIR/configure"
"$PATH_TO_SRC_DIR/configure" "--prefix=$PATH_TO_PACKAGE_DIR" $4

I added the chmod as part of pull request 9165. Feel free to comment and/or propose better ways to move forward.
https://github.com/microsoft/vcpkg/pull/9165

Does this issue still exist?

Thanks for posting this issue, please reopen this issue if it still be a problem for you.


[Bug]: The Select component's right arrow is too much on the right

Contact Details
No response
What happened?
According to Figma, the right arrow is supposed to be a little bit more on the left:

Current Select's right arrow:

Component
Select
Component Version
1.3.13
Which browsers are you seeing the problem on?
No response
Mobile Device
No response
Relevant log output
No response

We should probably update the icon while we're at it, too.


[Feature Request]: Colab notebooks automated Integration Tests

What would you like to happen?
Colab Notebook tutorials are now being added into the Apache Beam Repo to provide for additional training materials. (example)
We should have an automated integration test that makes sure that the code in these notebooks run fine, and without errors as future versions of Beam are released.
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[X] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

.take-issue

Yes, lets keep this open.

This added to 2.49.0 milestone because #26690 closed this before. iiuc it's not a blocker and I am removing it from milestone


[BUG] Fix website title icon and text

Describe the bug
Currently, the title of the website is default "React App" and "ReactJs" icon.
To Reproduce

Go to the website
Observe the title of the website

Expected behavior

The title should be "React Flashcard App"
The title icon should be same as the navbar

Screenshots

@rezwan2525
Hey! Can I work on this issue.

@trishitchar Yes sure, please go ahead.🤩

This issue resolved in this PR  https://github.com/rezwan2525/flashcard-react/pull/5


Add New JWT Issuer for Migration

Purpose

$Subject
Related PRs: https://github.com/wso2-enterprise/apim-migration-resources/pull/425

put this into migration docs

Codecov Report
Patch coverage has no change and project coverage change: +55.00 :tada:

Comparison is base (b9d836b) 25.10% compared to head (4b94506) 80.10%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1375       +/-   ##
===========================================
+ Coverage   25.10%   80.10%   +55.00%
===========================================
  Files         234        9      -225
  Lines       30762      548    -30214
  Branches     6150      246     -5904
===========================================
- Hits         7722      439     -7283
+ Misses      22774      109    -22665
+ Partials      266        0      -266

Flag
Coverage Δ

adapter
?

config-deployer-service
?

idp-domain-service
80.10% <ø> (ø)

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 225 files with indirect coverage changes

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


fix the outdated URL of NIN logo

Replace the outdated URL of NIN logo with a valid one from Wikipedia(https://en.wikipedia.org/wiki/Nine_Inch_Nails).

🤘
Thanks!


[Relay] Support resize in the ONNX conversion

Added support for resize2d op
Added unit test

Can we also support resize in other dimensions?

Sure, I will look into it.

@comaniac @trevor-m
I have made the changes (catch error using else and updating the test for coord trans and rounding method). I see that it the conversion fails (as in not identical) for certain cases.
I had to add the following:
if (i == "nearest_neighbor" and j == "align_corners") or (i == "cubic" and j in ["half_pixel", "align_corners"]):
Should I use the discussion forum to debug this?

@mbrookhart could you help take a look if you got a chance?

This looks fine to me. I am curious what the use case for this pass is :)

@mbrookhart Here is the PR for this: https://discuss.tvm.apache.org/t/rfc-relay-to-onnx/6101
The issue I am facing is relay operator resize2d doesn't faithfully convert to onnx operator Resize when method = nearest_neighbor and coordinate_transformation_mode = half_pixel

Interesting. We run this onnx file in CI and make sure it imports correctly: https://github.com/onnx/onnx/blob/v1.6.0/onnx/backend/test/data/node/test_resize_upsample_sizes_nearest_ceil_half_pixel/model.onnx
Maybe you could import it, and then re-export the relay, and compare the protobuf you get with the original?

Interesting. We run this onnx file in CI and make sure it imports correctly: https://github.com/onnx/onnx/blob/v1.6.0/onnx/backend/test/data/node/test_resize_upsample_sizes_nearest_ceil_half_pixel/model.onnx
Maybe you could import it, and then re-export the relay, and compare the protobuf you get with the original?

Thanks. Let me give it a try.

Thanks @trevor-m @comaniac


Enable golangci-lint deadcode linter, fix errors

Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

We shouldn't merge this until https://github.com/openshift/release/pull/22322/ goes in.

The plugin is tested in https://github.com/open-cluster-management/submariner-addon/pull/162

Depends on https://github.com/openshift/release/pull/21461 to add the golangci-lint job.

/approve


Switch api and contracts

Known Problems
1.) Ecosystem endpoint failing with 500
https://dev.api.deuro.com/#/Ecosystem Controller/EcosystemStablecoinController_getStablecoinInfo
2.) Savings core info failling with 500
https://dev.api.deuro.com/#/Savings Controller/SavingsCoreController_getInfo
3.) Governance module failing with a weird error


Performance improvement: Added/Removed buildings are saved on close and game save.

Old behaviour: Adding/Removing a building to a district by clicking on the checkbox writes the changes to disk. This takes several seconds.
New behaviour: District styles are written to disk if they are created, deleted, the contained buildings are changed and a) the DS panel is closed or b) the game is saved.
Tested and styles seems to work like before with a lot of other mods running too.
PackageManager.ForcePackagesChanged() is removed to allow async saving, but I personally don't understand what it does and if it is needed. So far no problems though...

@AndreasMayer1  i am trying to test your changes atm, and I am getting error in output log

@jk2l Didn't notice that. I can look into it too. Maybe using the games save functionality wasn't a good idea after all :D
Should we revert the PR?

@jk2l Didn't notice that. I can look into it too. Maybe using the games save functionality wasn't a good idea after all :D Should we revert the PR?

i am trying to understand the error but haven't got much luck yet, if i can't figure how it cause error then i think it is best to revert it


A few simplifications to Paxel

List:

Removes ObjectLiteralExpression - it's not needed anymore
Removes CurrentScopeExpression - can be signified with null on FieldExpression
Fixes the first type argument of FieldExpression to be Scope, as we always look up on scopes and subclasses don't need to be used in typing of expressions.
Changes the NewExpression builder to avoid extra listOf()

/gcbrun

/gcbrun


[RHCLOUD-18864] fixed logic in SubCollectionList() methods in mock dao

RHCLOUD-18864
Logic in SubCollectionList() methods needed to be fixed.
I found out in mock daos for SubCollectionList() for sources that there is not good logic for route application_types/id/sources ... before we returned sources where source id = application type id (and it was working because our test data was not so perfect)
line 88 from mock_daos.go
// Application type exists = return sources subcollection
for index, source := range src.Sources {
    if source.ID == object.Id {
        sources = append(sources, src.Sources[index]
    )

but it is simply wrong ... first we need to find out if application type exists (if not, we return not found error) and then we need to find all applications with given app type, get source ids from these apps and then return list of these sources
similar situation was for SubCollectionList() for app type (sources/id/application_types) ... first we need to find out if source exists and if so, then find all applications with given source id and create list of app types and then return the list with app types objects
then I updated our fixtures to have there 2 apps with different app type for 1 source id and because this, I needed to update test data for status listener too

maybe it could be good if you can add few words about what is issue and how are you fixing it, it helps in review ;) thanks!

maybe it could be good if you can add few words about what is issue and how are you fixing it, it helps in review ;) thanks!

yes, that's a good point ... I'll get better next time ... I added description at the top

I changed my help function to check that 1 source can have only 1 app with specific app type. Now the GetSourcesWithAppType() in helpers returns not count of sources but list with sources so it can be reuse on more places. Now we can add "invalid" application test data into fixtures and this option will be considered in the test.

rebased and conflicts solved


Backlog 16051 Add structured view for pages/contents

JIRA

https://jira.jahia.org/browse/BACKLOG-16051
Description
Add structured view for pages and contents, fix selection navigation etc.

Just trying to get context: for ContentListHeader, I see there's two versions: ContentListHeader and ContentListHeaderMoon and seems to be using former. I'm guessing we can't use moonstone version yet?

Just trying to get context: for ContentListHeader, I see there's two versions: ContentListHeader and ContentListHeaderMoon and seems to be using former. I'm guessing we can't use moonstone version yet?

We are using moonstone version already, the other one needs to be removed.


Can't install it via panda install DBIish: Cannot invoke null object

Hi,
I get following error when I try to install DBIish:
Cannot invoke null object
in sub strip-pod at lib/Panda/Builder.pm:15
in sub builder-order at lib/Panda/Builder.pm:56
in method build at lib/Panda/Builder.pm92
in method install at lib/Panda.pm:127
in method iresolve at lib/Panda.pm:214
in sub MAIN at panda:20
in block at panda:87
I guess I am missing a module, because installation works on my desktop but not on my fresh Fedora 22 installation.
Is what missing?
What is missing?
THX

Seems to have started happening with recent rakudo builds. The current rakudo ac720edaf6b0abe40d4c8bc922e83a507f78e1b7 give me the same error with panda install DBIsh.
But a rakudo build from about a week ago works fine 27499bbdbf9bbc1163f9afb2397ce1af8c8493c4.

I've golfed this a little and raised a rakudobug https://rt.perl.org/Ticket/Display.html?id=125342

Good job @dwarring, much appreciated.
Meanwhile we can try looking for a workaround of some sort.

I was having the same problem with Linenoise, and I think I found a workaround in the meantime: installing other modules before the broken one in a single command (e.g. panda install p6doc Linenoise) seems to make it work.

Wow, the fact that it worked sounds quite scary :o I'll try to get a solid look at it tomorrow.

Hey, the workaround worked for me as well ^^ "panda install p6doc DBIish" ran wihtout errors, yeah.

@dwarring @tadzik I fixed the "Cannot invoke null object" bug a few days ago; please retry!

DBIish now installs for me.

I just now saw that it should be fixed.
To test whether it works now I did a

rakudobrew self-upgrade
rakudobrew build-panda
During the build-panda command the DBIish is successfully updated:
==> Successfully installed DBIish
Done, built panda for moar-nom
Updating shims
But following command failes:
[wolf@localhost ~]$ panda install DBIish
==> Fetching DBIish
==> Building DBIish
Cannot invoke null object
in sub strip-pod at lib/Panda/Builder.pm:15
in sub build-order at lib/Panda/Builder.pm:56
in method build at lib/Panda/Builder.pm:92
in method install at lib/Panda.pm:127
in method resolve at lib/Panda.pm:214
in sub MAIN at /home/wolf/.rakudobrew/bin/../moar-nom/install/share/perl6/site/bin/panda:20
in block  at /home/wolf/.rakudobrew/bin/../moar-nom/install/share/perl6/site/bin/panda:87

The code causing that is now gone from panda, so the issue doesn't exist anymore. Please reopen if for some reason it still doesn't work :)

Hmm, thx tadzik
I just updated rakudobrew here and tried to update panda. Unfortunately, it still fails:
rakudobrew build-panda
Cloning into 'panda'...
remote: Counting objects: 4226, done.
remote: Compressing objects: 100% (164/164), done.
remote: Total 4226 (delta 78), reused 0 (delta 0), pack-reused 4046
Receiving objects: 100% (4226/4226), 717.94 KiB | 1.25 MiB/s, done.
Resolving deltas: 100% (1879/1879), done.
Checking connectivity... done.
No need to rebootstrap, running normal bootstrap
==> Bootstrapping Panda
==> Installing panda from a local directory '/home/wolf/.rakudobrew/moar-nom/panda'
Could not download module metadata: Too many positionals passed; expected 1 argument but got 2
in method update at /home/wolf/.rakudobrew/moar-nom/panda/lib/Panda/Ecosystem.pm:110
in method init-projects at /home/wolf/.rakudobrew/moar-nom/panda/lib/Panda/Ecosystem.pm:48
in method get-project at /home/wolf/.rakudobrew/moar-nom/panda/lib/Panda/Ecosystem.pm:119
in method get-deps at /home/wolf/.rakudobrew/moar-nom/panda/lib/Panda.pm:166
in method resolve at /home/wolf/.rakudobrew/moar-nom/panda/lib/Panda.pm:209
in sub MAIN at bin/panda:18
in block  at bin/panda:95
==> Please make sure that /home/wolf/.rakudobrew/moar-nom/install/share/perl6/site/bin is in your PATH
Done, built panda for moar-nom
Anything I can do?

Wow, that's very weird. Looking at it now...

This really shouldn't be happening: bootstrap isn't even supposed to access the network at all.
Can I ask you to clear/move your ~/.rakudobrew/moar-nom/install/share/perl6/site so that it's empty and try again? It seems to me that for some reason your bootstrap.pl loaded some old Panda installation that's lying around.

I removed .rakudobrew at all and checked it out again. Now it is working. Obviously, the old installation was in a mess.
Thanks for your help anyway!

You're welcome, I'm glad all is fine after all :)


Long class names in IdP branch

This is purely a style related issue.
Are we ok with having class names such as EmailPasswordResetPasswordRenderHandler and BasicIssuerReferenceWebIdOwnershipValidator? While there is nothing inherently wrong with such names, in my opinion it does make it sometimes more difficult to parse which class I'm looking at. Of course we do need to be more descriptive if we have more classes so it's not always easy to find shorter names that accurately reflect the class.

I also think that such long names are confusing.
I would adopt the rule of thumb to use the minimum length for class names, they just need to be unique and descriptive enough. Probably for those two:

EmailPasswordResetPasswordRenderHandler -> ResetPasswordRenderHandler
BasicIssuerReferenceWebIdOwnershipValidator -> WebIdOwnershipValidator (and directly extend the AsyncHandler)

* `BasicIssuerReferenceWebIdOwnershipValidator` -> `WebIdOwnershipValidator` (and directly extend the AsyncHandler)

I do like still having the WebIdOwnershipValidator abstract class, since in the future we might want to have multiple validators (we could for example have one that only works for webids stored in the server itself). But the abstract name itself could probably be shortened. Does anyone have a synonym for OwnershipValidator? 😄

Maybe WebIdOwnershipValidator doesn't need to be shortened, but one could call this implementation BasicWebIdOwnershipValidator and have a SameServerWebIdOwnershipValidator later on?
I don't have a shorter good name for now :sweat_smile:

Yes to shorter names.


using branch deploy, c++ version on xavier become worse

I am using branch deploy, I get the .so of the unsupport ops, and the python scripts work fine. Nearly the same.
I moved to xaiver(aarch64), and generate the onnx file and .so file, and then use trtexec plugin to get the engine file.
The result become worse.
There are two difference, first, the trt version on xaiver is 7.1 while in deploy it is 7.2.
Second, I am doubting the preprocess but have no progress.
The process is about crop->resize->np.float32-> /255.0 -> add a dim and dims to 3201
maybe there is a little difference between the different method(cv transform imgaug) and the step order, I check the input find the difference is really small.
Really need some help!

the performance show difference on the image, there are one or two lanes missed. And lanes on the left are worse than lanes on the right. The distal side has a trend close to the middle.

@mengxia1994
Trt 8.5.x works fine for me, the preprocess is same as yours
CROP --> RESIZE --> 1/255 --> NCHW. None other transforms is applied.
i recommend you check the model output first, they should be the same or atleast 99% the same (ONNX and TRT sometime produce difference results if you mis-choose the type (float, double,..).

Thank you~ Yes, the model output are at least 99% the same between pth, onnx and trt on a x86_64 training machine. But I have to run it on xavier and consider the total system stability it will take months to upgrade jetpack. The model output are quite different on xavier.
According to current clues, this should because of some ops difference between trt7.1 and newer versions

I am using branch deploy, I get the .so of the unsupport ops, and the python scripts work fine. Nearly the same. I moved to xaiver(aarch64), and generate the onnx file and .so file, and then use trtexec plugin to get the engine file. The result become worse. There are two difference, first, the trt version on xaiver is 7.1 while in deploy it is 7.2. Second, I am doubting the preprocess but have no progress. The process is about crop->resize->np.float32-> /255.0 -> add a dim and dims to 3201 maybe there is a little difference between the different method(cv transform imgaug) and the step order, I check the input find the difference is really small. Really need some help!

hi , i  have a xavier too , but when i use the branch deploy , cmake error happened , which show me
CMake Error at tensorrt/CMakeLists.txt:32 (target_link_libraries):
so i want to know how can i change the script of CMakeLists.txt to get the  correct  .so file , thanks

您好，我已收到您的邮件，我将尽快查阅并给予回复，谢谢！（孟夏的自动回复）

您好，我已收到您的邮件，我将尽快查阅并给予回复，谢谢！（孟夏的自动回复）

我已经生成了ibmmdeploy_tensorrt_ops.so，但是我用trtexec转换模型的时候，依然失败了，提示No importer registered for op: GridSample，请问你是怎么转换成engine的，谢谢

did you make it work with trt 7.1.x? im trying to implement it on xavier or nano. if it didnt work in the end, prolly ill need to make it work on trt 7.1.x so please let me know

您好，我已收到您的邮件，我将尽快查阅并给予回复，谢谢！（孟夏的自动回复）


Add support for new "inline visits" feature

See: https://github.com/inertiajs/inertia/pull/315
This PR adds support for the new "inline visits" feature coming to Inertia. For the most part, this is a client-side feature. However, there are two situations that need to be handled server-side:
First (full) page visits
Consider a /users/create endpoint, which displays a create user modal on top of the current page. If you visit this endpoint directly (the the first page visit), you have two choices:

Show a full page version of the create user page, which uses the app layout.
Show the create user modal again, but with another page loaded in the background.

The first option here is easy, since you can conditionally render the modal version of full page version of your page component based on the new $inline global property (literally no server-side changes required at all).
However, the second option is more complicated, since you need to get the component and data for two pages: the create user modal, in this example, and the page you want to load in the background.
Inertia.js supports "double page visits" like this by allowing you to provide a page object that includes an inline key. When you do this, the main page is treated as the background, and the inline page as the inlined page (naturally).
{
  "component": "Users/Index",
  "props": {
    "users": [],
  },
  "url": "/users",
  "inline": {
    "component": "Users/Create",
    "props": {},
    "url": "/users/create",
  },
  "version": "c32b8e4965f418ad16eaebba1d4e960f",
}

To make a response like this, you can use the new Inertia::inline() option, which takes the inline page as the first argument, the base page as the second argument, and any props for the inline page as the third argument. I am totally not sold on this API yet, this is a WIP.
return Inertia::inline('Users/Create', function () {
    return Inertia::render('Users/Index', [
        'users' => User::all(),
    ]);
}, ['foo' => 'bar']);

// Shorthand (by using existing controller method)
return Inertia::inline('Users/Create', fn () => $this->index(), ['foo' => 'bar']);

Note how thee base page is lazily evaluated. This is because we don't want to load the base page on inline visits.
Non-inline Inertia modal visits
The second situation is similar to the full page visits, but this time for standard non-inline Inertia modal visits. For example, imagine you click on the /users/create link to create a new user, but your session has expired, and you get logged out. You log back in, and then Laravel redirects you (in an Inertia request) back to the intended URL, /users/create.
In these situations, you don't want the create modal page to appear on the login page, nor do you necessary want to have to create a full page version of the create user page. What you probably want here is show the create user modal with a logical base page in the background.
By using the new Inertia::inline() helper, this adapter will check to see if the request is an inline visit, and if it's not, will automatically return a "double page" response instead.

Closed, as https://github.com/inertiajs/inertia/pull/315 was closed as well.
See https://github.com/inertiajs/inertia/pull/642


Don't display missing symbol warning for jailbroken devices

Right I get the yellow warning for the current version of my app saying "Symbols are missing for app version..." even though I've uploaded the symbols. This warning comes most probably from the following crash which happens on jailbroken devices:
CoreFoundation
__exceptionPreprocess
libobjc.A.dylib
objc_exception_throw
Foundation
+[NSJSONSerialization JSONObjectWithData:options:error:]
SY.dylib
0x0000000102c30000 + 2510832
SY.dylib
0x0000000102c30000 + 2508980
SY.dylib
0x0000000102c30000 + 2485920
libdispatch.dylib
_dispatch_client_callout
libdispatch.dylib
_dispatch_continuation_pop
libdispatch.dylib
_dispatch_source_invoke2
libdispatch.dylib
_dispatch_source_invoke
libdispatch.dylib
_dispatch_main_queue_callback_4CF
CoreFoundation
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
CoreFoundation
__CFRunLoopRun
CoreFoundation
CFRunLoopRunSpecific
GraphicsServices
GSEventRunModal
UIKitCore
UIApplicationMain

Notice that for SY.dylib there are no function names. This seems to be some library specific for jailbroken devices and there will probably be never any symbols for it.
I think that the warning regarding missing symbols shouldn't be displayed if it's because of a crash on a jailbroken device.

Hey thanks for filing an issue. We'll look into improving this scenario. In the meantime, you can ignore the missing symbols from the Unsymbolicated tab to remove the notification:


Inconsistent spaces vs tabs

Overview
Several files are inconsistent with spaces vs tabs. Per the coding guidelines (incoming to master per #2038), spaces should be used instead of tabs.
Expected Behavior
No tabs
Actual Behavior
Tabs

This was released in the 2<IP_ADDRESS> release candidate


Calculate md5 signature only once per point

This PR contains optimisation of creating the ring for ketama algorithm. MD5 hash calculates only once per point instead of calculation in all iterations.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@manjuraj, @idning

Up @idning @manjuraj


Update Jenkins to 2.32.3

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed


When add/edit row can`t modify those rows real-time, only after reload data

can modify/delete, but when edit rows are not set to the corresponding fields


TypeError: Not a buffer

So, after getting past the previous error I get this. I tested my config of secret key endpoint etc with the plain ddb package that this depends on. And it works as expected.
TypeError: Not a buffer
    at new Hmac (crypto.js:257:17)
    at Object.Hmac (crypto.js:255:12)
    at auth (/Users/emris/htqkly/AppTrackerRefactor/node_modules/seneca-dynamo-store/node_modules/dynamodb/lib/ddb.js:1010:23)
    at execute (/Users/emris/htqkly/AppTrackerRefactor/node_modules/seneca-dynamo-store/node_modules/dynamodb/lib/ddb.js:849:5)
    at EventEmitter.scan (/Users/emris/htqkly/AppTrackerRefactor/node_modules/seneca-dynamo-store/node_modules/dynamodb/lib/ddb.js:706:5)
    at Seneca.store.load (/Users/emris/htqkly/AppTrackerRefactor/node_modules/seneca-dynamo-store/lib/dynamodb-store.js:192:20)
    at Object.execspec.fn (/Users/emris/htqkly/AppTrackerRefactor/node_modules/seneca/seneca.js:1497:24)
    at Object._onImmediate (/Users/emris/htqkly/AppTrackerRefactor/node_modules/seneca/node_modules/gate-executor/gate-executor.js:108:14)
    at processImmediate [as _immediateCallback] (timers.js:354:15)

Also, is there a reason endpoint is being ignored in your package? the line is commented out.

so found error was related to a disparity between documentation and implementation:
      accessKeyId: 'ACCESSKEYID',
      secretAccessKey: 'SECRETACCESSKEY',
      endpoint: 'ENDPOINT'

when I changed config to match
    var conf = 'string' == typeof(spec) ? null : spec;
    connection = dynamodb.ddb({accessKeyId: conf.keyid,
                               secretAccessKey: conf.secret,
                              endpoint: conf.endpoint});
    seneca.log.debug('init', 'db open', spec);
    cb(null);

everything worked, also required uncommenting out endpoint from the connection config.

pretty frustrating the owner doesn't seem to take care of this repo. It's time to fork and make an active version.

Hi @jreeter - I understand your frustration and you're right, I have been neglecting this. I have two young children so I don't have much time for open source these days... Maybe @vtardia knows someone who could take a look?

Hi @jreeter  - I've updated the master branch with our latest work. A lot has changed and it works with latest versions of seneca. Give it a try and let me know if you still have errors.


[Audit v2] id_tree_index is never updated

Although as the new audit version is released, this might no longer an issue. But some of the projects, including semaphore_auth, that still using the legacy audit v2 version, might have this issue. So I'm leaving this issue here for people who come here from the search engine.
What's wrong
Only the first inserted identity can broadcast a signal.
To broadcast a signal, the  Semaphore.sol checks if the identity tree root is in the  root_history in the isValidSignalAndProof check. The root_history is supposed to be updated when an identity is inserted.
 function insertIdentity(uint256 identity_commitment) public onlyOwner {
        insert(id_tree_index, identity_commitment);
        uint256 root = tree_roots[id_tree_index];
        root_history[root] = true;
    }

The root is determined by the tree_roots[id_tree_index], however, the variable id_tree_index is never updated. This means the root_history only recognizes tree_roots[0], which means the root history check for the future identities will all return false. No one can broadcast signal anymore.
Version
https://github.com/appliedzkp/semaphore/tree/audit_v2
How can it be fixed
The new version doesn't seem to have this issue. The new rootHistory is native to the Merkle tree library and is updated correctly when a new leaf is inserted.

Sorry, I got this wrong. id_tree_index is always 0, and tree_roots are roots from different trees. The root of tree 0 should be updated when running insert of the MerkleTreeLib.sol .


Public fields and getters / setter attributes that have the same name generate duplicate JS methods

Describe the Bug
Public fields and getters / setter attributes that have the same name generate duplicate JS definitions.
Steps to Reproduce
#[wasm_bindgen]
pub struct Struct {
    pub field: i32,
}

#[wasm_bindgen]
impl Struct {
    #[wasm_bindgen(getter)]
    pub fn field(&self) -> i32 {
        self.field
    }

    #[wasm_bindgen(setter)]
    pub fn set_field(&mut self, field: i32) {
        self.field = field;
    }
}

Expected Behavior
An error forbidden the duplicated behavior
Actual Behavior
Duplicated getters and setters.
get field() {
    ...
}
set field(arg0) {
    ...
}

get field() {
    ...
}
set field(field) {
    ...
}

Closed by #1605


environmentSupportsReuse() method in TestcontainersConfiguration class not looking at the classpathProperties

environmentSupportsReuse() method in TestcontainersConfiguration class is not looking at the classpathProperties but only env variables and userProperties. (getEnvVarOrUserProperty method is used inside, instead of getEnvVarOrProperty method)
There is a comment like "specifically not supported as an environment variable or classpath property" but i am curious on why we cannot use the classpath properties for reusing the container.
Is it a bug? If it is not, i'd be glad to hear the rationale behind it.

By design. See https://github.com/testcontainers/testcontainers-java/pull/1781#discussion_r369160221


Lower/Uppercase inconsistencies in dropdown data type names vs in script

Azure Data Studio Version: Insiders
OS Version: Windows Enterprise

Steps to Reproduce:

Open Table Designer in Azure Data Studio
Open data type drown. Observe case settings in data type drop down
Make changes to the table and select "Publish"
Select "Generate Script" to view T-SQL script of table

Expected:
Case-sensitivity should be consistent in data type drop down and script
Actual:
Script contains upper case data types and Designer drop down is lower case

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

no impact to the functionality


Add support for Decimal type

Similar to rust postgres, it will be great if this lib add support for the Decimal type.
My case is that I'm building my own mini-orm, and differently to rust postgres, I can't implement ToSql/FromSql for it:
impl FromSql for Decimal {
    fn column_result(value: ValueRef<'_>) -> FromSqlResult<Self> {
        unimplemented!()
    }
}

error[E0117]: only traits defined in the current crate can be implemented for arbitrary types
   --> db/src/sqlite.rs:220:1
    |
220 | impl FromSql for Decimal {
    | ^^^^^^^^^^^^^^^^^-------
    | |                |
    | |                `rust_decimal::Decimal` is not defined in the current crate
    | impl doesn't use only types from inside the current crate
    |
    = note: define and implement a trait or new type instead

The orphan rule means that only rust_decimal or rusqlite crates can implement FromSql/ToSql for Decimal directly.

Oh, I see. I ask there. Thanks.

Ok, so can I put a pull request for this here?

Yep, something like https://github.com/rusqlite/rusqlite/pull/506

Making the test I found is not possible to round-trip Decimal::Max, and it fails with InvalidColumnType instead of report is an overflow.
In [get<I: RowIndex, T: FromSql>(https://github.com/rusqlite/rusqlite/blob/master/src/row.rs#L280)  it returns this error.
Can I return the overflow instead or let it be as-is and you look at it later?

You should be able to use FromSqlError::Other, no ?

Yeah, but is still returned as InvalidType, no matter the original error...

Ok, I send the pull request, tell me if I need to improve it anyway!


Clashes with reverse query name (related_query_name in Models)

When you have a field with a related_query_name set, doing migrations (once you have added django simple history) will fail, telling you that reverse query name for 'HistoricalName.field' clashes with reverse query name for 'ModelName.field'.
I have the next models:
class CommonModel(models.Model):
    created_at = models.DateTimeField(auto_now_add=True)
    modified_at = models.DateTimeField(auto_now=True)
    deleted_at = models.DateTimeField(blank=True, null=True)
    is_deleted = models.BooleanField(default=False)
    history = HistoricalRecords(
        inherit=True
    )

    class Meta:
        abstract = True

class Worker(CommonModel):
    name = models.CharField(max_length=25, help_text="Nombre del trabajador")
    surname = models.CharField(max_length=70, help_text="Apellidos del trabajador")
    entry_date = models.DateField(blank=True, null=True, help_text="Fecha de entrada en la empresa")
    check_in_hour = models.TimeField(blank=True, null=True, help_text="Hora de entrada del trabajador (Opcional)")
    check_out_hour = models.TimeField(blank=True, null=True, help_text="Hora de salida del trabajador (Opcional)")
    social_security_number = models.CharField(max_length=12, blank=True,
                                              help_text="Número de la seguridad social (Opcional)")
    user = models.OneToOneField(
        User,
        related_name="worker",
        related_query_name="worker",
        null=True,
        blank=True,
        on_delete=models.PROTECT,
        help_text="Usuario de la plataforma asociado al trabajador (Opcional)"
    )

    def __str__(self):
        return "{}, {}".format(self.surname, self.name)

When I try to run python manage.py makemigrations I get the next error:

workers.HistoricalWorker.user: (fields.E305) Reverse query name for 'HistoricalWorker.user' clashes with reverse query name for 'Worker.user'.
HINT: Add or change a related_name argument to the definition for 'HistoricalWorker.user' or 'Worker.user'.

I've been doing some research in google but I didnt find anything until inspecting the 'simple_history/models.py' code I found this in copy_fields function line 278 (at the time of writing this issue):
# Override certain arguments passed when creating the field
# so that they work for the historical field.
field_args.update(
    db_constraint=False,
    related_name="+",
    null=True,
    blank=True,
    primary_key=False,
    db_index=True,
    serialize=True,
    unique=False,
    on_delete=models.DO_NOTHING,
)

Here I realized that no new related_query_name was given to field_args.update() so, in the moment of creating the Historical model, the two models will have in the field the same related_query_name.
A possible solution (works for me) is to delete all related_query_name added to fields of your model.
I don't know if this is really a bug, but the fact that I did not find anything it's come to my attention.
Environment (please complete the following information):

OS: Zorin OS 15.2
Django Simple History Version: 2.10.0
Django Version: 2.2
Database Version: PostgreSQL 10.12

Hey @Yorchly! Why are you specifying both related_name and related_query_name? You should get the same result if you just specify related_name, and you'll no longer run into this bug.

Hey @Yorchly! Why are you specifying both related_name and related_query_name? You should get the same result if you just specify related_name, and you'll no longer run into this bug.

Indeed, but I didn't know! Thanks for the reply :+1:

Have same issue


Xamarin IOS Unified support

Package current doesn't work on IOS unified projects :(
MTOUCHTASK: error MT2002: Failed to resolve assembly: 'Nito.AsyncEx.Enlightenment, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'
Any change for a quick fix?

iOS actually optimizes away that supporting library by default, so you have to add a line of code to your app to ensure it doesn't get dropped during compilation:
EnlightenmentVerification.EnsureLoaded();

Sorry for the confusion; this detail used to be on the main library page but I neglected to copy it over to GitHub... I'll put this in the docs right away!

Where do I get this reference from?  I've included Nito.AsyncEx package which adds references to Nito,Async and Nito.AsyncEx.Concurrent.  I'm not seeing the EnlightenmentVerification class.

If you're installing into a PCL, then you only have the AsyncEx and AsyncEx.Concurrent references. The AsyncEx.Enlightenment reference is only added for platform-specific assemblies (i.e., an iOS application).

I'm thinking it's picking up the PCL version because "lib\Xamarin.iOS10" target does not exist in the nuspec.  I'm only seeing lib\MonoTouch which is the old system.
http://blog.xamarin.com/how-to-update-nuget-packages-for-64-bit/

Boy, that's annoying. I'll have to fix this, then.

Is there any update on the status of this? This is a blocking issue for a project I am working on. Referencing Nito.AsyncEx causes conflicting libraries to be brought into the solution because it brings in the Xamarin iOS Classic libraries.

I'll see if I can get to it this weekend. No promises, though.

Thanks, just wanted to make sure it was on your radar.
And thanks for a great library.

Can both of you try the 3.0.1 prerelease and let me know if that worked? The Xamarin docs don't actually say exactly how to do this, so I had to guess a bit. https://www.nuget.org/packages/Nito.AsyncEx/3.0.1-pre
Let me know if there's still a problem, thanks!

Looking good so far.  Compiles, links and runs!  Thank you.

Thanks so much for following up - for various reasons, it's difficult for me to currently test with Xamarin.
FYI, I've already started adding a new feature to AsyncEx, so the released version will probably be 3.1.0 rather than 3.0.1.

Worked fine for me, too.

Thanks.

Hi Stephen... the fixed 3.0.1 pre-release package seems to be working properly on iOS Unified... what about pushing it to stable channel? ;)

OK, I pushed the 3.0.1-pre as 3.0.1. It's actually the same package, just with a non-prerelease version.


Disable OSX testing

OSX tests have been failing on slow machines lately.
However they do not fail for the developers.
Disable them to not block progress while we work on a fix.

💚


Add a "gallery" view to configuration -> job types and Recipes

Instead of just a drop-down chooser, add (or replace) the drop-down picker with a "grid-gallery" view for all job types and recipes...
So the user can see all the jobs, on one page.  Maybe we can "stack" multiple versions?
Recipes work the same way, but need to be slightly different look.  (Maybe even a thumbnail of the recipe tree inside the grid?) Not sure the performance, but it might work...

For recipes, instead of the recipe tree thumbnail, look into showing the job types/recipe types that comprise the recipe. This would be an indicator of the recipe type's complexity.

If we want to change the recipe-type list api to support this, we would have to make 4 additional database calls for each recipe type.  This could have a major hit on performance when we are just trying to get a list of recipe types.

Another option would be to have a parameter passed in to the recipe-type list api to optionally populate these fields.

Do it.

On Mar 18, 2019, at 1:38 PM, John Tobe<EMAIL_ADDRESS>wrote:
Another option would be to have a parameter passed in to the recipe-type list api to optionally populate these fields.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Eric, what fields from job types and sub recipes do we need for this? If we just need things like name and revision we might be able to pull it from the definition rather than make a db call.

We could even possibly just do a count?

Talking to shamis, we could maybe just have a set of tags for all the nodes in the recipe.  I could put the definition in the response or a list of job types, recipe types and condition nodes.  Ideally it would be the recipe graph which could also be built from the definition.


ingressroute: Support enforcing mode

Defined in the specification here: https://github.com/heptio/contour/blob/master/design/ingressroute-design.md#enforcing-mode
This will allow for more secure multi-team functionality where Root IngressRoute objects are only read from trusted namespaces

I thought this would be actionable but I think this is blocked on #448 as we don't have delegation yet.

In terms of feature yes, I think that is correct. However, given that delegation has not been fully fleshed out yet, I am not sure where this feature would fit in terms of code/architecture. I'll add an item to our sync agenda.

I propose that we do this as a first cut of this feature for beta.1
diff --git a/cmd/contour/contour.go b/cmd/contour/contour.go
index 1f00a62..f07d36d 100644
--- a/cmd/contour/contour.go
+++ b/cmd/contour/contour.go
@@ -97,6 +97,11 @@ func main() {
        serve.Flag("use-proxy-protocol", "Use PROXY protocol for all listeners").BoolVar(&t.UseProxyProto)
        serve.Flag("ingress-class-name", "Contour IngressClass name").StringVar(&t.IngressClass)

+       var roots []string
+
+       // restricted mode
+       serve.Flag("ingressroute-roots", "Restrict contour to searching for ingress route roots to these namespaces").StringVars(&roots)
+
        args := os.Args[1:]
        switch kingpin.MustParse(app.Parse(args)) {
        case bootstrap.FullCommand():

Then plumb roots down the dag watcher.
We can iterate on the UX of setting this field and redeploying contour in a later iteration.


OSX. Run as a daemon failed with 401

When agent start interactively it work fine.
But when I try to start it as daemon it fails with 401.
stdout.log shows that env vars set right.
How to set authentification for deamon correctly?
I'm could not find anything in docs.

Can you add details on how you ran it as a daemon.  Do you mean a launch daemon?  Can you provide other details?  Are you connecting to an on-prem server?

Sorry for a long silence.
Yes, it's a on-premise server.
Today update agent to 0.3.13 but it does not helps.

Any ideas?

check out the read me for updated instructions for on-premise (use preview version).
However that's not what you're hitting.  401 means bad creds.
So, first, let's interactive (not daemon).  Does that work?
Second, look in the plist that's referenced.  What creds are in it?

/So, first, let's interactive (not daemon). Does that work?/
Yes, I've said it in my previous message.

Second, look in the plist that's referenced. What creds are in it?

I wonder if it's a quoting/escaping issue in that file?? Also, you will need to append the flag to force basic (let me look that up).  Just realized that will be needed.

So I've updated agent to "0.4" version, node to 4.2.3
Removes old agent, reconfigure, set force-basic, and now got 403 at interactive mode:

this user in "Agent Pool Service Account" and "Agent Pool Administrators"

Got it! Added user to "Project Collection Service" group.

Daemon still fails

adding scott
Just to confirm, you got it to work interactively by adding to the Project Collection Service group (we should figure out why - wasn't expecting).
But, you're still having an issue with the service?  (note the plist is just telling it to run what you did interactively).  Try interactively with -u and -p args (what the plist does)

I've got a minus character in my password

Ha!

I wonder if it's a quoting/escaping issue in that file??

:) Looks like we need to fix that.
Does quoting it work?

I've tried -u "user.name" -p "password", but it does not helps.

I updated the README.md to have specific on-prem instructions link.  There were additional permissions needed (now doc'd) and a couple of fixes.
I would recommend getting a new agent via the latest instructions


Include headers explicitly and add constructors to comply C++20

The constructor update is necessary for the project to compile in C++20 due to struct initialization rules made more strict in C++20. The header update is to reduce the implementations details (ic header includes) leak.

After thinking about this I would probably change the pattern used in constructors to the following:
class X {
  some_type _a;
  some_type _b;

  X(some_type a, some_type b)
    _a(std::move(a)),
    _b(std::move(b)) {}
};

The reason is that with this design the user can actually decide which argument to move and which to copy. The copy is guaranteed to only happen once, so there is only the extra move per value, which seems okay to me.

After thinking about this I would probably change the pattern used in constructors to the following:

I concur with this recommendation as being the least intrusive.


Update authors (and separate roles into groups for clarity).

Built with updated ghizmo https://github.com/jlevy/ghizmo/pull/3

👍 lgtm. Thanks for doing this, @jlevy - the authors list is much more readable now.

Looks good. There’s an SSL error that’s making Travis sad, but not relevant to this PR.


add proxy, packageRepository and certificate injection

add proxyInjection, packageRepositoriesInjection, CustomAuthorityCertificationInjection that had been added in the onyxia-api by https://github.com/InseeFrLab/onyxia-api/pull/163 in the OnyxiaValues.
That will allow the injection of this values in the helm charts launcher for compatible catalogs.

Je marge dès que c'est OK. Je reste attentif

sorry i will check this today or tomorrow

Ok i have accepted your suggestion commit

I have rerun this in local to make another check it's ok for me

Thank you for your contribution.
It's being released as I type theses words


Add test against fsl_con_f_multiple

Test data  fsl_con_f_multiple is currently excluded from the test suite (in coming edits to #124). In a future PR, we should add this test back and check that the tests run without error.

Fixed by #121


update agdc-v2/examples/band_stats.py in response to #67

Refactor to remove dependency on filename convention

Doesn't rely on filenames anymore.
Still a lot of boilerplate and fudge


How to get it running without using a specific Inventory file?

Hi,
I've found your module very useful. However, the one thing that is troubling me right now is how can I run this without using the inventory file ? I tried something like : role : rolename , ansible_python_interpreter="PATH=/home/core/bin:$PATH python" but it fails in the step where its trying to setup pip. Have you run it without an inventory file ? How do I do that?
Thanks.

@madhurranjan
Same problem here.
I tried using set_fact module to set ansible_python_interapter in ansible-coreos-bootstrap/task/main.yml.
Like this
- name: set ansible fact
  set_fact: ansible_python_interpreter="PATH=/home/core/bin:$PATH python"

then bootstrap properly worked without using inventory.

Thanks @shufo. I'll keep that in mind. I got over it by using dynamic inventory and having the ansible_python_interpreter set as part of that.


Rewrite: useReducer based implementation

https://twitter.com/dai_shi/status/1185849112895225856

In react-hooks-async, I tried useReducer but it was too ugly, the current code with forceUpdate is pretty readable. So, I gave up. I could try further. There could be a better implementation with only immutable states. I wish somebody would try.

https://twitter.com/dai_shi/status/1191518644389335040

react-hooks-async implementation is not very declarative.

I actually agree. Used to useReducer, but changed assuming mutations are easier to read. I'll try again. It should be technically possible

So, it should be technically possible to code without forceUpdate.
It would be better because forceUpdate is not a good pattern unless there's an avoidable reason.
Now, I hope it's not too ugly now. I don't preserve the exact same behavior(no abort in this hook), but the public API should be able to be used the same as before.
There might be room for improvements. a) dispatchRef doesn't seem nice, b) do we really need two symbols? c) Is the use of useLayoutEffect correct?
I found implementing this is pretty tricky, and I'm not sure how readable it it.

@dagda1 You wanna have a look?

HI @dai-shi,
I feel really awful.  I was not meaning to criticise.  I was just saying that somebody in the comments reminded me of react's declarative nature.  I learned a lot looking at this library and I think it is excellent.
I will have a look at the PR

I was not meaning to criticise.

@dagda1 Please don't get it wrong. I never felt this as criticism. It's a suggestive feedback. I mean I thought the use of forceUpdate wasn't nice. It should be a last resort. I had wanted to rewrite this.
My implementation was originally useReducer based, but when I supported the "callback" pattern, I changed it to forceUpdate+memoization. Now, I got to know useReducer better, I'm using lazy initialization this time.

I think this is much better but the one thing I don't see is a state change for an Error.
I like the reducer in the codesandbox I referenced in the article.

      let result = null;
      let error = null;
      try {
        result = await func(abortController, ...args);
        dispatchRef.current({
          type: 'RESULT',
          taskId,
          runId,
          result,
        });
      } catch (e) {
        if (e.name !== 'AbortError') {
          error = e;
        }
        dispatchRef.current({
          type: 'ERROR',
          taskId,
          runId,
          error,
        });
      }
      if (error) throw error;
      return result;

You mean you prefer this?

yes,an error is a state change IMO
On Tue, 5 Nov 2019 at 21:53, Daishi Kato<EMAIL_ADDRESS>wrote:

  let result = null;
  let error = null;
  try {
    result = await func(abortController, ...args);
    dispatchRef.current({
      type: 'RESULT',
      taskId,
      runId,
      result,
    });
  } catch (e) {
    if (e.name !== 'AbortError') {
      error = e;
    }
    dispatchRef.current({
      type: 'ERROR',
      taskId,
      runId,
      error,
    });
  }
  if (error) throw error;
  return result;

You mean you prefer this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dai-shi/react-hooks-async/pull/33?email_source=notifications&email_token=AAA44ODRSFIABLUESQCTC4DQSHTM7A5CNFSM4JJDRXVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDEO3GI#issuecomment-550038937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA44OFZK65RUW4XESWGVFDQSHTM7ANCNFSM4JJDRXVA
.

--
Cheers
Paul Cowan
Cutting-Edge Solutions (Scotland)
blog:      http://thesoftwaresimpleton.com/
website: https://cutting.scot/

@dagda1

yes,an error is a state change IMO

But, it was already a state change. I think it's just coding style preference.

should abort be a state changed also?

Hm, currently, we have no aborting nor aborted state, because abort() is usually called on unmount or on starting a new task and no component read the state. If we had a use case to use aborting state, we would consider that. How does that sound?

i did have a use case recently but it was for uploading large  files into azure in chunks. are you saying abort is only called on unmount

No, I only meant "usually". Let's open a new issue about it. I think it's a good use case to dig in.

Let me merge this.
@dagda1 Would you open a new issue for aborting state with a use case?

should abort be a state changed also?

Actually, I ran into an issue because of no aborted state. There is a bug in the current typings after #30.

 That's a really undesired behavior of React.
Fair enough. Let's see how useIsomorphicLayoutEffect hack works.


EmrEtlRunner: replace hadoop_shred in config.yml.sample with rdb_shredder

Should we move the config to the storage part as well, instead of enrich?

Hmm, good question - I think we should...

We're calling the component RDB Shredder, so the config file property should be rdb_shredder - updated the ticket title...

Should we rename the tags as well: https://github.com/snowplow/snowplow/pull/3203/files#diff-354f30a63fb0907d4ad57269548329e3R75 ?

same goes for https://github.com/snowplow/snowplow/blob/78676a1e2497f0169260986f606b89535a08dff5/.travis/release_relational_database_shredder.yml

Let's do it, please rename the tags, commits, tickets etc...


Line items in cart rule not working if "is none of" and parent product is selected

Description:
When creating a rule for a promotion with the "line items in cart "rule, then selecting "At least one", "is none of" and a parent product, the rule always returns true.
Environment:
dev
Steps to reproduce:

Create a promotion with the above mentioned rule.
Use it as the "apply to specific products only" rule in a promotion
Add a variant of the parent product to the cart
Add the promotion to the cart

Expected result:
The promotion won't be applied
Actual result:
The promotion will be applied
Note:
I don't know if this can be fixed that easily since the rule would need to know if the selected identifier is a parent product or a variant.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-31325.
[created from NEXT-31325, comment 485519]

[public] Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know. Thank you again for your valuable feedback.
[created from NEXT-31325, comment 492298]


docker run error, how to set "--device" ?

when I follow this sample: DirectX Container Sample
There is an error:
docker run --isolation process --device class/5B45201D-F2F2-4F3B-85BB-30FF1F953599 winml-runner
invalid argument "class/5B45201D-F2F2-4F3B-85BB-30FF1F953599" for "--device" flag: class/5B45201D-F2F2-4F3B-85BB-30FF1F953599 is not an absolute path
How to set the "--device"?

Did you ever solve this issue? Currently having the same error

Did you ever solve this issue? Currently having the same error
This error occurs if you're not running a Docker client/engine that supports '--device' arg for Windows containers. This functionality is not yet available in non-edge editions of Docker Desktop for Windows.
You should install the Edge version, not the stable version.
https://docs.docker.com/docker-for-windows/edge-release-notes/

I have the edge version still having this issue. I also changed the docker.exe and dockerd.exe from master.docker.com

Can you list your environment?
You must meet the requirements below strictly :
For this feature to work, your environment must meet the following requirements:
The container host must be running Windows Server 2019 or Windows 10, version 1809 or newer.
The container base image must be mcr.microsoft.com/windows:1809 or newer. Windows Server Core and Nano Server container images are not currently supported.
The container must be run in process isolation mode. Hyper-V isolation mode is not currently supported.
The container host must be running Docker Engine 19.03 or newer.
The container host must have a GPU running display drivers version WDDM 2.5 or newer.

And some third-party anti-virus software affects process isolation, like Symantec and so on.

@cwilhit FYI
@adityasingh1 @SoldierProgrammer Hi there, and thanks for reporting this issue. Are either of you still encountering this? If so, can you please reply with:

the exact version of Windows you're using as your container host;
the output of the docker version command; and
confirmation that you're running Docker in "Windows containers" mode (not "Linux containers" mode).

Thanks!

hello, rick-man,
i've tried both the stable and edge version, neither could do device assignemnet. and local env exactly meets the requriements.
the trial cmd is to assign/share COM device:
docker run -it --isolation=process --device="class/86E0D1E0-8089-11D0-9CE4-08003E301F73" mcr.microsoft.com/windows/servercore:1809 cmd
from the log file, it seems like a timeout syscall:
[14:08:59.008][WindowsDaemon     ][Warning] Syscall did not complete within operation timeout. This may indicate a platform issue. If it appears to be making no forward progress, obtain the stacks and see if there is a syscall stuck in the platform API for a significant length of time. [timeout=4m0s cid=5c02254fc569ad67146a293f77da5e4f75056c8affba67268150ee754413566f]
log.txt
     the env:
      docker info

Server:
Server Version: 19.03.1
Default Isolation: hyperv
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows 10 Enterprise Version 1809 (OS Build 17763.107)
the output of docker version:
Client: Docker Engine - Community
Version:           19.03.1
API version:       1.40
Go version:        go1.12.5
Git commit:        74b1e89
Built:             Thu Jul 25 21:17:08 2019
OS/Arch:           windows/amd64
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          19.03.1
API version:      1.40 (minimum version 1.24)
Go version:       go1.12.5
Git commit:       74b1e89
Built:            Thu Jul 25 21:25:07 2019
OS/Arch:          windows/amd64
Experimental:     true
 looking forward to your comment.

@lobbyzhu can you confirm the container runs without the --device argument? Also, are you running any antivirus software?

hello, cwilhit,
the container could run without the "--device" argument. and it also could run with volume mount like below：
“docker run -it --rm --name test -v "$(pwd):c:/repo"  mcr.microsoft.com/windows/nanoserver:1809 cmd”
yes, there is antivirus, i'll have a try and update. thanks for the hint.

after disabling the antivirus, still fails. :(
need further advice.

I had the same problem, switching to windows containers worked for me (with the latest stable of docker desktop)

Is there a solution that doesn't include switching to windows containers?

@teunbruijnen: --device class/5B45201D-F2F2-4F3B-85BB-30FF1F953599 is the syntax for exposing devices to Windows Containers, so there isn't really a solution that doesn't involve using Windows Containers to use that command-line.

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Updated/simplified streaming tutorial

Made it ok to execute cells out of order by making variables unique
Simplified code and made it clearer which bits were about setting up a stream, and which bits are about streaming viz

Not sure why the 0.9.8 commits are showing up here, but presumably they won't hurt?


feat: api docs catchup part 2

Like #3257, each commit is tied to an issue.
Issues that will be closed:
fixes #3020
fixes #3036
fixes #3078
fixes #3105
fixes #3216
fixes #3219
fixes #3222
fixes #3228
fixes #3230
fixes #3231
fixes #3233
fixes #3234
fixes #3235
fixes #3236
fixes #3238
fixes #3242
fixes #3249
fixes #3251
fixes #3252
fixes #3253
fixes #3265

Someone should still test that the types for the gateway events for the ENTITLEMENTS_CREATE _UPDATE and _DELETE are correct, but the rest should be ok


Address spelling and grammar issues in specification

Fixes some small grammar/spelling issues.
"heterogenous" seems to be a medical/biological term. I think this is what was intended: "heterogeneous"

Thanks for these corrections. As noted inline, my only concern is regarding "can not" vs. "cannot", and my preference to avoid making unnecessary changes.

For reference re: heterogenous vs heterogeneous
https://grammarist.com/usage/heterogeneous-heterogenous/


Does envoy get the Public IP or Private IP of the client in the x-forwarded-for header ?

If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
<EMAIL_ADDRESS>where the issue will be triaged appropriately.
Title: want to understand if envoy get private IP of the client (downstream application) by default
Description:
we have a set up where there is a downstream application (client) sending a request to upstream application via envoy and we want to capture the public IP of the client. in the envoy x-forwarded-for header we are seeing only private ip. Our requirement is to get public IP. Is this possible ? or does envoy by default reads private IP ?
[optional Relevant Links:]

Any extra documentation required to understand the issue.

How Envoy handles XFF is for better or worse extremely complicated. Start by reading this: https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/headers#x-forwarded-for.
If Envoy is sitting behind additional proxy hops, you may have to configure other things to make this work as as proxy proto, etc.


cypress: 8.3.1 -> 9.0.0

Motivation for this change
Update Cypress to next major version
Things done
Run Cypress tests from a code base at work on my NixOS machine.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 145609 run on x86_64-linux 1

1 package built:

cypress

Should there be not a symlink in bin to $out/cypress/opt/cypress/Cypress?

Superseded by #148826


Support for hash.random

Add Support for hash.random
hash.random: Randomly distribute events if no hash or key value can be computed.
https://www.elastic.co/guide/en/beats/filebeat/master/kafka-output.html
@pcfens when do you think you're going to build a new version with this change ?

I'm going to try and tag a new release today that also incorporates #141.