Docs release fails for IAM (alpha05)

Filing as process as it isn't a bug that will affect customers, beyond our ability to release.
The release build for #8423 is failing in the docs build with:

[22-04-29 01:57:02.625]Warning:ExtractMetadataWorkspace failed with: [Failure] Msbuild failed when processing the file 'T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Iam.V1\Google.Cloud.Iam.V1\Google.Cloud.Iam.V1.csproj' with message: The SDK 'Microsoft.NET.Sdk' specified could not be found.  T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Iam.V1\Google.Cloud.Iam.V1\Google.Cloud.Iam.V1.csproj

This is odd given that alpha02 released with no problems.

Oddly, this works locally when running "builddocs.sh Google.Cloud.Iam.V1" directly in the docs directory, but fails in a subtly different way when running via buildrelease.sh:

[22-04-29 02:45:20.175]Warning:ExtractMetadataWorkspace failed with: [Failure] Msbuild failed when processing the file 'C:\users\jonskeet\GitHub\googleapis\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Iam.V1\Google.Cloud.Iam.V1\Google.Cloud.Iam.V1.csproj' with message: SDK Resolver Failure: "The SDK resolver "Microsoft.DotNet.MSBuildSdkResolver" failed while attempting to resolve the SDK "Microsoft.NET.Sdk". Exception: "System.IO.FileNotFoundException: Could not load file or assembly 'System.Collections.Immutable, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Collections.Immutable, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at Microsoft.NET.Sdk.WorkloadMSBuildSdkResolver.CachingWorkloadResolver.Resolve(String sdkReferenceName, String dotnetRootPath, String sdkVersion, String userProfileDir)
at Microsoft.DotNet.MSBuildSdkResolver.DotNetMSBuildSdkResolver.Resolve(SdkReference sdkReference, SdkResolverContext context, SdkResultFactory factory)
at Microsoft.Build.BackEnd.SdkResolution.SdkResolverService.ResolveSdk(Int32 submissionId, SdkReference sdk, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath, Boolean interactive, Boolean isRunningInVisualStudio)

I suspect the two have the same cause though...

Still failing now that we're targeting netstandard2.1 in the generated docfx JSON files. The nature of the error ("The SDK 'Microsoft.NET.Sdk' specified could not be found.") suggests it's an environmental issue, but I'm surprised that it all builds fine if that's the case - and that alpha02 was okay.

We fixed this in the end by updating the CI machine.


Revert "Update the vulnerable dependency"

Reverts idosinchuk/security-strategy-essentials#1

Revert for pass the next step.


pipe.fit() freezes and don't return anything

Hi many times while running this model in pycharm the model just freezes and don;t return the output.
It works sometimes after restarting the kernel twice or thrice.
Sometimes doesn't work at all.
Please look into this

On further investigation it seems intiliazing the model pipeline can happen only once per kernel as it opens the llm_response session.
If we want to run this api again with different key ,different config(domain and labels), we need to restart the kernel.

Yes, because changing key and domain etc would initiate the prompter, model etc again. for a single model you can initialize the things once and then call the pipe.fit() multiple times on any number of samples.

Was facing the same issue, setting structured_output=False and parsing the output myself seems to bypass the issue.

@roperi  Hi, did you solve this problem?
I have neither the structured_output=False attribute nor the global Pipeline pipeline working

@roperi Yes, same for me, so i parsed received JSON by myself. BUT, for some reason we received JSON with extra brackets, so i had to remove them


Fixed #21936 -- Refactored DeleteView to be compatible with SuccessMessa...

Refactored DeleteView to use the form related base classes and mixins, like the
other class-based generic editing views.  Added tests for the handling the
DELETE http method and ensuring the SuccessMessageMixin works. Updated DeleteView
documentation to reflect the new base classes.
The majority of the code changes were provided by Simon Charette.

I've gotten my branch into a state where I can't figure out how to rebase properly to get rid of the merge commits.  Anyone have any ideas how I can get this back into a good state?

Does https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/#after-upstream-has-changed help?

Those were the instructions I was following.  I think I managed to get the merge commit back out now. So I think I'm getting closer.  Thanks.

I'm not sure about the isort failure that I'm getting when it runs the build, either.  I've run isort -rc . in the root folder and commit all modified import statements.  Is there a way to tell what the error is?

Select the "default" build and click "Console Output" in the left menu: http://djangoci.com/job/isort/31/label=trusty-pr/console
ERROR: /home/jenkins/workspace/isort/label/trusty-pr/django/db/backends/sqlite3/schema.py Imports are incorrectly sorted.

_sqlite3 getting moved might be a Python version difference or something. Maybe we need to add it to "known_third_party" or something...

That does seem to be the import statement that was causing the issue.  I've reverted my change to that file.  Is marking the import statement somehow something I should do in this pull request, or is it best handled separately?

Separate change will be fine. What is your system/Python version? Latest version of isort?
Ubuntu 14.04/Python 2.7/3.4/isort 3.9.6 here and on CI.

OS X (10.10.2), Python 2.7.9, isort 3.9.6

buildbot, add to whitelist.

Sorry, this has gone stale again as messages tests have been moved out of contrib to tests/messages_tests.

@timgraham opened a new pull #4256

Close as per request


Default Provided Unbound Config Does Not Work With DnsCrypt

Operating System
Raspberry Pi
Architecture
64-bit
Platform
Windows, Linux, Android
Project
Aduard Home, Wireguard, Unbound, DNScrypt
Browser
Chrome
Issue
Not working
Issue Description
Using the default configurations of Unbound  <-> DNSCrypt causes an issue where Unbound will consistantly return a SERVFAIL.
Increasing the verbosity from 0 to 3 in the unbound.conf file results in these visible errors.
debug: validator[module 1] operate: extstate:module_wait_module event:module_event_moddone
debug: return error response SERVFAIL
debug: configured stub or forward servers failed -- returning SERVFAIL

debug: iterator[module 2] operate: extstate:module_wait_reply event:module_event_noreply
debug: tcp error for address <IP_ADDRESS> port 5353
debug: outnettcp got tcp error -1
debug: outnettcp got tcp error -1
debug: cache memory msg=66072 rrset=66072 infra=8402 val=66368 subnet=74504
debug: sending to target: <.> <IP_ADDRESS>#5353

Using dig to check dnscrypt, it shows NOERROR on the responses. When I toggle forward-ssl-upstream: yes to no, this issue is resolved however the first request results in an over 300ms request time. Basic dns query results in 23msec.
Using Raspi 4B.
Unbound: Version 1.13.1

@Kashalls  hi
This issue does not reproduce for me
https://user-images.githubusercontent.com/18756975/196043963-018e4f25-a0ac-4cad-aca9-296d1b9245dc.mp4
Not sure why this is happening but can you try another port other than 5353 and see if same error occurs.

@Kashalls  hi
This issue does not reproduce for me
Version 1.13.1
https://user-images.githubusercontent.com/18756975/196043963-018e4f25-a0ac-4cad-aca9-296d1b9245dc.mp4
Not sure why this is happening but can you try another port other than 5353 and see if same error occurs.

I eventually got the latest build of unbound done and working but the same issue. I tried 6565 and 4200 and got the same result. I have a feeling it's certificate related but I lack the knowledge to debug this.

@Kashalls hi
This issue does not reproduce for me
Version 1.13.1
powershell_Lg0xo2PHvk.mp4
Not sure why this is happening but can you try another port other than 5353 and see if same error occurs.

I have been able to reproduce this issue quite considerably. Debating whether or not to try getting a public instance up to test my theory.

@Kashalls you said

When I toggle forward-ssl-upstream: yes to no

apart from in default config which is forward-tls-upstream: yes which means tls security is not being used(which is better)
it baffles me to see DNScrypt to cause this issue. Forgive me for asking what was understood by you already, I would like to know if this happens with Stubby or cloudflared or unbound by itself.

@Kashalls you said

When I toggle forward-ssl-upstream: yes to no

apart from in default config which is forward-tls-upstream: yes which means tls security is not being used(which is better)
it baffles me to see DNScrypt to cause this issue. Forgive me for asking what was understood by you already, I would like to know if this happens with Stubby or cloudflared or unbound by itself.

I'd be willing to get in a call with you on something like Discord if you want to take a look at the instance. I had to switch to no in order for unbound to query dnscrypt.

If it does happen only with dnscrypt I suggest trying it on a vps if you can to rule out that it do not have anything to do with your network.. this "SERVFAIL" error in unbound upstreams according in forums sounds like a DNS server side issue

If it does happen only with dnscrypt I suggest trying it on a vps if you can to rule out that it has nothing to do with your network.. this "SERVFAIL" error in unbound upstreams according in forums sounds like a DNS server side issue

In a weird turn of events, on a seperate machine I installed ubuntu server (64bit) in a minimal configuration on a desktop pc of mine I use for testing. It setup immediately and did not have the issues I was presented on the Raspberry Pi 4B.

Used vultr to deploy a $5/mnth with Ubuntu 22.04.1.
Process of Installation Taken:

Follow the entirety of this section: https://github.com/trinib/AdGuard-WireGuard-Unbound-DNScrypt#install-adguard-home-
follow the entirety of this https://github.com/trinib/AdGuard-WireGuard-Unbound-DNScrypt#install-adguard-home- and disabling DNSStubListener
Download unbound configuration from repo.
Follow https://github.com/trinib/AdGuard-WireGuard-Unbound-Cloudflare/wiki/Install-DNScrypt-proxy-(DoH)(oDoH)(Anonymized-DNS) as per document
Configure adguard with <IP_ADDRESS>:53 and <IP_ADDRESS>:5353 parallel requests
Reboot
dig @<IP_ADDRESS> -p 53 google.com -> SERVFAIL

@Kashalls i rebooted a couple times(fyi, my date is not set) i do not get SERVFAIL.
on your raspberry pi , check nano /etc/resolvconf.conf  to see what is your nameservers

![image)(https://owo.whats-th.is/3RycW8w.png)
Seems to be wrong, what should they be set to?

@Kashalls hmmm you should have nameserver <IP_ADDRESS> in /etc/resolvconf. it should be added automatically after installing unbound
when you ping google.com you should be reachable to internet right ?
Do you have cloudflare dns on your router or somewhere else before installing unbound?  My config shows:
# Generated by resolvconf

forward-zone:
        name: "."
        forward-addr: <IP_ADDRESS>
        forward-addr: fe80::1%eth0

<IP_ADDRESS> is my default gateway/ address
can you add nameserver  <IP_ADDRESS> using this guide https://github.com/trinib/AdGuard-WireGuard-Unbound-DNScrypt/wiki/Set-permanent-DNS-nameservers. Ping google and check if internet access if not try adding other nameserver

Followed instructions to the T.
As soon as I turn forward-tls-upstream from no to yes, SERVFAIL's begin showing up at the unbound side.

add nameserver <IP_ADDRESS> in /etc/resolvconf and check unbound again

Local DNS is now being resolved by the router.
Just the same output from unbound:
[1149:0] debug: outnettcp got tcp error -1
Oct 20 07:00:46 adguardhome unbound[1149]: [1149:0] debug: outnettcp got tcp error -1
Oct 20 07:00:46 adguardhome unbound[1149]: [1149:0] debug: outnettcp got tcp error -1

@Kashalls Nice i see now you get no answer section with dig google.com @<IP_ADDRESS> which really means confirms nameserver <IP_ADDRESS>  is not configured properly. I do not know why it do not set for you when unbound is installed🤷♂ use this this guide https://github.com/trinib/AdGuard-WireGuard-Unbound-DNScrypt/wiki/Set-permanent-DNS-nameservers and set it from there and see if it works
and btw is <IP_ADDRESS> your home network default dns and gateway address ??

What is the expected contents of /etc/unbound/unbound.conf.d/resolvconf_resolvers.conf

i have
# Generated by resolvconf

forward-zone:
        name: "."
        forward-addr: <IP_ADDRESS>
        forward-addr: fe80::1%eth0

<IP_ADDRESS> is my default gateway/dns address
when you ping google is it reachable to internet ?
and what do you have when you run ifconfig ?

@Kashalls hmm i rule out its a issue with UniFi cause you mention earlier you used vultr vps and have the same issue ?? my account is currently closed on vultur lol.  can you create a new machine on vultr and send me login details at<EMAIL_ADDRESS>and let me install it and see if issue still occurs

Sure, I will have it done later today.

@Kashalls everything seems to be working fine on vps, test it out for yourself. It looks like you did not follow this guide.
When i installed unbound on this machine it do not set nameserver <IP_ADDRESS> in  /etc/resolv.conf. So resolv package needs to install to set it but when it does you lose internet to host and setting permanent nameserver is needed to regain internet. Before unbound nameserver was set the machine default nameserver was <IP_ADDRESS> which can be added to fix, or the IPv4 address can be used as well👍

if you still get server error, something is wrong on you network side with router or something.

@Kashalls everything seems to be working fine on vps, test it out for yourself. It looks like you did not follow this guide.
When i installed unbound on this machine it do not set nameserver <IP_ADDRESS> in /etc/resolv.conf. So resolv package needs to install to set it but when it does you lose internet to host and setting permanent nameserver is needed to regain internet. Before unbound nameserver was set the machine default nameserver was <IP_ADDRESS> which can be added to fix, or the IPv4 address can be used as well👍

Hmm 🤔 I was confused when you got to the unbound part. Were you able to get it setup to forward to dnscrypt?

First thing I notice is that there is no /etc/unbound/unbound.conf.d/ resolvconf_resolvers.conf is not present as it is on rpi.

You absolutely need to add in forward zone, a dns server that uses port 853 in unbound config for DoT to work .
Forwarding to DNScrypt(<IP_ADDRESS>:5353) uses DoH from dnscrpyt servers
although its same cloudflared. it is using different servers and security protocol👍

You absolutely need to add in forward zone, a dns server that uses port 853 in unbound config for DoT to work .
Forwarding to DNScrypt(<IP_ADDRESS>:5353) uses DoH from dnscrpyt servers
although its same cloudflare. it is using different servers and security protocol👍

So you have to enable BOTH DoT and DoH on Unbound, otherwise you can't use DNSCrypt?
I was under the impression you could only use just oDoH by forwarding to just dnscrypt.

So you have to enable BOTH DoT and DoH on Unbound, otherwise you can't use DNSCrypt?

using dnscrypt(port 5353) in unbound(port 53) forward queries from dnscrypt listen interface - <IP_ADDRESS>:5353. yes dnscrypt can work without unbound,  If you want to use it only replace port 5353 with 53 in dnscrypt config so <IP_ADDRESS>:53 which was unbound is now dnscrypt

I was under the impression you could only use just oDoH by forwarding to just dnscrypt.

dnscypt only allows oDoH or DoH at a time cause its irrelevant, oDoH is like DoH with more advanced security

I still want to use Unbound as a cache, the way I understood it was that it was: Adguard Home -> Unbound -> DNSCrypt-Proxy.
On the server, you had both forwarding addr's for dnscrypt doh and cloudflare dot like so:
The thing I am trying to understand is that in this configuration, nothing is ever resolved by dnscrypt. No traffic, no logs nothing. Whenever unbound queries this, it gets the tcperror interally.

The thing I am trying to understand is that in this configuration, nothing is ever resolved by dnscrypt. No traffic, no logs nothing. Whenever unbound queries this, it gets the tcperror interally, results in a SERVFAIL if dnscyrpt is the only forwarding-addr.

you can use logs and get queries from unbound but im am not sure if there is a way  to show queries of dnscrpyt in unbound  logs itself.  if you are using unbound from package manager you need to create log file in /var/log/unbound.log using touch command and set permission sudo chown unbound:unbound /var/log/unbound.log and restart unbound.
ps : You can use tail -f /var/log/unbound.log to see logs read in realtime
you can get dnscrypt query logs in  /var/log/dnscrypt-proxy/query.log and you will see queries. Here is wiki for more test https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Checking
not sure you can see what dnsscypt is querying from unbound to know it works but I see in logs it selects server ip4 <IP_ADDRESS> port 5353  that has rtt(round-trip time) which mean it is receiving a response
[1666447115] unbound[2443:0] debug: iter_handle processing q with state QUERY TARGETS STATE
[1666447115] unbound[2443:0] info: processQueryTargets: . DNSKEY IN
[1666447115] unbound[2443:0] debug: processQueryTargets: targetqueries 0, currentqueries 0 sentcount 1
[1666447115] unbound[2443:0] info: DelegationPoint<.>: 0 names (0 missing), 6 addrs (6 result, 0 avail) parentNS
[1666447115] unbound[2443:0] debug:   [cloudflare-dns.com] ip6 2606:4700:4700::1001 port 853 (len 28)
[1666447115] unbound[2443:0] debug:   [cloudflare-dns.com] ip6 2606:4700:4700::1111 port 853 (len 28)
[1666447115] unbound[2443:0] debug:   [cloudflare-dns.com] ip4 <IP_ADDRESS> port 853 (len 16)
[1666447115] unbound[2443:0] debug:   [cloudflare-dns.com] ip4 <IP_ADDRESS> port 853 (len 16)
[1666447115] unbound[2443:0] debug:    ip6 ::1 port 5353 (len 28)
[1666447115] unbound[2443:0] debug:    ip4 <IP_ADDRESS> port 5353 (len 16)
[1666447115] unbound[2443:0] debug: attempt to get extra 3 targets
[1666447115] unbound[2443:0] debug: servselect ip6 2606:4700:4700::1111 port 853 (len 28)
[1666447115] unbound[2443:0] debug:    rtt=518
[1666447115] unbound[2443:0] debug: servselect ip4 <IP_ADDRESS> port 853 (len 16)
[1666447115] unbound[2443:0] debug:    rtt=376
[1666447115] unbound[2443:0] debug: servselect ip4 <IP_ADDRESS> port 5353 (len 16)
[1666447115] unbound[2443:0] debug:    rtt=752
[1666447115] unbound[2443:0] debug: selrtt 376
[1666447115] unbound[2443:0] info: sending query: . DNSKEY IN
[1666447115] unbound[2443:0] debug: sending to target: <.> <IP_ADDRESS>#5353

@Kashalls

results in a SERVFAIL if dnscyrpt is the only forwarding-addr.

i tried using dnscrypt only and i still do not get SERVFAIL.

@Kashalls  i get SERVFAIL with dig @<IP_ADDRESS> google.com  cause like what is said is https://github.com/trinib/AdGuard-WireGuard-Unbound-DNScrypt/issues/59#issuecomment-1287770704

Oh okay it makes more sense to me now. Thanks for helping out I appreciate it.


fix(upgrade): source "upgrade to" version from repoinfo

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

A user may manually create a version CR with custom naming to trigger an upgrade. For instance:
cat > ./version.yaml << EOF
apiVersion: harvesterhci.io/v1beta1
kind: Version
metadata:
  name: local-upgrade
  namespace: harvester-system
spec:
  isoChecksum: 2b99b0870d3363b393bb7900c53b8a1f529e150519558cea672e9ff8eab19ba0dac3f35688e49cdc2ac3ba0d253017fd3d8790cb229856735e30c524f56f22a7
  isoURL: http://<IP_ADDRESS>/harvester-amd64.iso
EOF

The name of the Version CR is then used to create the corresponding Upgrade CR. It will be in the .spec.version field. The upgrade eligibility check currently relies on that field to determine what version it will upgrade to. Apparently, it's not so reliable. We need to fix this.
Solution:

The .spec.version field in the Upgrade CR is not reliable. Instead of relying on that field to determine the "upgrade to" version, we read from the release version of the .status.repoInfo field. Those information is populated from the content in the ISO image.
Related Issue:
#5494
Test plan:

Prepare a single-node Harvester cluster containing this fix
Fake the version to v1.4.0 by adding HARVESTER_SERVER_VERSION=v1.4.0 environment variable to the harvester Deployment
Trigger an upgrade to v1.3.2 (simulating a downgrade)

Create a Version CR with a custom name, e.g., local-upgrade
Apply the Version CR
Choose the version and click the upgrade button from the dashboard

The upgrade should end in the "downgrading is prohibited" error after the upgrade repo VM is up and running.

@mergify backport v1.4


jmol: 14.29.17 -> 14.29.19

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from jmol.
meta.description for jmol is: '"A Java 3D viewer for chemical structures"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19/bin/jmol had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 14.29.19 with grep in /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19
directory tree listing: https://gist.github.com/9c4c532329b432d0239f400830497ea4
du listing: https://gist.github.com/4bab9a7318775aeb59b144a7f79e1cb9

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/baf51804f0e616ffd2b56d78b9767377a7940406.tar.gz -p jmol
ls -la /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19

cc @timokau @mounium for testing.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: jmol
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-darwin (full log)
Attempted: jmol
Partial log (click to expand)
  inflating: /nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19/share/jsmol/testjsv_predict.htm
  inflating: /nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19/share/jsmol/testsave.htm
  inflating: /nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19/share/jsmol/validation.htm
  inflating: /nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19/share/jsmol/vibrate.htm
post-installation fixup
strip is /nix/store/df6k4mgdjxciy0f637lryp7c9ln7n1m3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19/bin
patching script interpreter paths in /nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19
/nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19/bin/jmol: interpreter directive changed from "/bin/sh" to "/nix/store/cblfnvb5rmhd2z231mqasn0brzh1hhv4-bash-4.4-p23/bin/sh"
/nix/store/wk9f1qixirpwx9d50a2763rwnr7bj7k2-jmol-14.29.19/share/jmol/jmol.sh: interpreter directive changed from "/bin/sh" to "/nix/store/cblfnvb5rmhd2z231mqasn0brzh1hhv4-bash-4.4-p23/bin/sh"

Success on x86_64-linux (full log)
Attempted: jmol
Partial log (click to expand)
  inflating: /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19/share/jsmol/validation.htm
  inflating: /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19/share/jsmol/vibrate.htm
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19/bin
patching script interpreter paths in /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19
/nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19/share/jmol/jmol.sh: interpreter directive changed from "/bin/sh" to "/nix/store/czx8vkrb9jdgjyz8qfksh10vrnqa723l-bash-4.4-p23/bin/sh"
/nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19/bin/jmol: interpreter directive changed from "/bin/sh" to "/nix/store/czx8vkrb9jdgjyz8qfksh10vrnqa723l-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/yax7yc2krh7cxcnhvvgr6fsn176r67wa-jmol-14.29.19...


About the GPU usage and training time of several methods in registration.

Hello,
I tried to test the code for point cloud registration in Benchmark, but I found that the GPU utilization for these methods is very low (jumping between 0% and 20%, and the training process is also very slow), I used multiple GPUs, do you use a single one for the training process or?
Can you provide us with your hardware environment and the approximate time required for a full training or an epoch?
I'm not sure if it's my environment or code problem, I'd like to get your help.

Two test environments: a). cuda10.2, GPU 2080Ti, pytorch1.5.0; b). cuda11.1, GPU 3090, pytorch1.7.0.

Hi, your observation can be all right.  I think it is not a bug or a problem, just because of the following reasons:

Those methods either have many non-trainable oprations (e.g. knn, gathering. grouping, surface normal estimation, and etc.) 2. They are using complicated backbones (e.g. DGCNN with a large knn).
The input are two point clouds, and each of them has the size (BatchSize, 2048, 3)
I use 2 V100 to train the DCP, and 1 V100 for the rest.  Hope my answer helps you.

Thank you for your reply, which allowed me to confirm that the code was officially tested and certified on multiple cards.

As far as I remember, the official DCP code training speed and GPU occupancy will be much higher than 20% (the exact value is somewhat forgotten due to too long time).  Indeed I also agree with you that calling it a bug or a problem is not quite appropriate.
If possible, could you provide the approximate time it takes to fully train the DCP, under your experimental conditions.
My gpu server is recently doing high io operations, later I will test it in my environment and share it with you.

Hi, @paul007pl. I tested the official dcp code on 4*2080Ti with batch_size=32 and pytorch1.5.0, it takes about 9.5h to run 100 epochs

As a comparison, I tested the dcp code in benchmark repo on 4*2080Ti with batch_size=16 (due to memory overflow), and it takes about 1h to run 1 epoch. I think the difference between the two is huge and the difference in dataset shouldn't cause such a big difference?
I am eager to share the results with you, so I only ran it for a while. But I think it's enough to extrapolate the entire training phase consumption time. (The time required for each iteration is not stable, the shortest time is ~1h to complete an epoch.)

Thanks for your report, and I have imporved its training efficiency now.  Please try again~
For DeepGMR, you can further improve its efficiency by using this file: https://github.com/wentaoyuan/deepgmr/blob/master/rri.cu.
Once I have time, I will further improve.

Wow, your improvements are very effective, now the DCP training process can reach an approximate speed to the official one in my environment, thanks a lot!
But after comparing the dcp.py file, I found that it seems to be just a change in the code structure?
Can you briefly describe the reason for the problem, to help me better understand the reason for the efficiency improvement.
Thanks again.

Haha… If I know the exact reason, the bug won't appear...

🤔 Philosophy of life, hahaha.
Anyway, thanks again! 🎉


Add support for excluding packages

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
Almost all Linux package managers support excluding packages so that they can never be installed. For example in YUM you can set in /etc/yum.conf you can set exclude=package1 package2 so those two packages cannot be installed via YUM.
What is the motivation for the feature?
My use case is that we install dotnet packages from a custom tap, which are in conflict with the official dotnet packages so I would like to disallow the official dotnet packages to be ever installed especially as a dependency of some other packages.
How will the feature be relevant to at least 90% of Homebrew users?
I can't be the only user that has this use case because all other packages managers I used (YUM, APT, Pacman, DNF,...) have this feature.
What alternatives to the feature have been considered?
I didn't find a solution to this.

HOMEBREW_FORBIDDEN_FORMULAE and HOMEBREW_FORBIDDEN_CASKS is how you can do this.

Have you tried setting the HOMEBREW_FORBIDDEN_FORMULAE environment variable?
https://docs.brew.sh/Manpage#environment

I didn't try it. I couldn't find it and none of the AI chat bots suggested this solution. It's very hidden and hard to find, probably because of the strange name compared to other package managers.

I couldn't find it and none of the AI chat bots suggested this solution.
It's very hidden and hard to find

Don't use AI chat bots to for this, use Google/DuckDuckGo/whatever instead.
AI chat bots only work when their training data includes our documentation and it's up-to-date (which it rarely is). Even then, they will often spit out completely wrong answers.
It's not at all hidden and is clearly documented. Next time, please read the docs before asking for help and please consider saying "thank you" when someone answers your question.


Support setting custom kubernetes context

Is your feature request related to a problem? Please describe.
Having the kubernetes context hardcoded to orbstack defeats using OrbStack as a true drop-in replacement for docker-desktop, as configuration files needs updating to point at the OrbStack cluster.
Describe the solution you'd like
It would be great if one could set a custom context for the kubernetes cluster instead of it being hardcoded to orbstack.

You can make a copy of the context with any name you want in ~/.kube/config.

Also: kubectl config rename-context

Ah, thanks! :-)


Management cluster should not use CNRM in namespaced mode

We are currently recommending installing CNRM in namespaced mode.
I'm not sure thats what we should recommend.

Namespace mode is inconvenient when managing multiple projects as we end up having to create
multiple deployments of the CNRM system

Using ACM to install CNRM doesn't appear to install it in namespaced mode.

We should cherry pick the fixes onto the 1.1 branch and then we can close this.


Adjust milvus interface

Signed-off-by: junjiejiangjjj<EMAIL_ADDRESS>

Codecov Report

Merging #1224 (8555fb3) into main (25d34e0) will decrease coverage by 0.00%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##             main    #1224      +/-   ##
==========================================
- Coverage   68.64%   68.63%   -0.01%
==========================================
  Files         249      252       +3
  Lines       12128    12227      +99
  Branches     2006     2029      +23
==========================================
+ Hits         8325     8392      +67
- Misses       3279     3301      +22
- Partials      524      534      +10

Impacted Files
Coverage Δ

towhee/functional/mixins/milvus_mixin.py
100.00% <ø> (ø)

towhee/hub/builtin/operators/milvus_search.py
13.15% <20.00%> (+0.33%)
:arrow_up:

towhee/models/clip4clip/clip4clip.py
65.00% <0.00%> (-11.09%)
:arrow_down:

towhee/models/clip4clip/until_module.py
58.82% <0.00%> (-2.29%)
:arrow_down:

towhee/models/clip/clip.py
90.64% <0.00%> (-0.02%)
:arrow_down:

towhee/models/action_clip/__init__.py
100.00% <0.00%> (ø)

towhee/models/action_clip/action_clip.py
62.50% <0.00%> (ø)

towhee/models/clip4clip/utils.py
92.30% <0.00%> (ø)

towhee/models/clip4clip/__init__.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[Bug]: default alert is set to null with each apply even after applying change

What versions are you using?
2.0.8
What did you expect to happen?
once I apply a resource it should NOT show that an alert is getting set from a value to null
What actually happened?
once you apply the following code and your run terraform apply or plan you will see that alert is getting set from default to null.
terraform plan
thousandeyes_agent_to_server.TE_TEST will be updated in-place
  ~ resource "thousandeyes_agent_to_server" "TE_TEST" {
      ~ alerts_enabled         = false -> true
        id                     = "4634087"
        # (24 unchanged attributes hidden)

      - alert_rules {
          - rule_id = 448256 -> null
        }

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

---  Actual resource
resource "thousandeyes_agent_to_server" "TE_TEST" {
  test_name              = "NO ACTION NEEDD TEST ONLY"
  interval               = 120
  alerts_enabled         = true
  description            = "test"
  server                 = "<IP_ADDRESS>"
  protocol               = "ICMP"
  enabled                = false
#  mtu_measurements       = false
 # bandwidth_measurements = false
  agents {
    agent_id = 3
  }
}

Terraform code to reproduce the bug
resource "thousandeyes_agent_to_server" "TE_TEST" {
  test_name              = "NO ACTION NEEDD TEST ONLY"
  interval               = 120
  alerts_enabled         = true
  description            = "test"
  server                 = "<IP_ADDRESS>"
  protocol               = "ICMP"
  enabled                = false
#  mtu_measurements       = false
 # bandwidth_measurements = false
  agents {
    agent_id = 3
  }
}

Any additional comments or code?
without fixing this issue I can not move from 2.0.5 to 2.0.8 version.  and I need the functionality of 2.0.8 version
Steps to reproduce the bug
apply the resource and re run the plan you will see the bug
resource "thousandeyes_agent_to_server" "TE_TEST" {
  test_name              = "NO ACTION NEEDD TEST ONLY"
  interval               = 120
  alerts_enabled         = true
  description            = "test"
  server                 = "<IP_ADDRESS>"
  protocol               = "ICMP"
  enabled                = false
 mtu_measurements       = false
 bandwidth_measurements = false
  agents {
    agent_id = 3
  }
}

Hey @Sraza11, thanks for reporting. Can you confirm that this happens in 2.0.8 only but not in 2.0.5?

@Sraza11 after looking a bit more into this, it looks like this was introduced by the fix in https://github.com/thousandeyes/terraform-provider-thousandeyes/pull/151.
However, we can't do much about it at this point, since it's the way Terraform works as this is a resource created outside of Terraform  - and in this case, since these are default Alert Rules which we don't want to have managed from Terraform.
Also, there's a super easy workaround for this, which is to simply add the default alert_rule id to the test:
 resource "thousandeyes_agent_to_server" "TE_TEST" {
  test_name              = "NO ACTION NEEDD TEST ONLY"
  interval               = 120
  alerts_enabled         = true
  description            = "test"
  server                 = "<IP_ADDRESS>"
  protocol               = "ICMP"
  enabled                = true

  alert_rules {
          rule_id = 921610
        }

  agents {
    agent_id = 3
   }
 }

Is this an acceptable solution for you?

Hey @Sraza11, thanks for reporting. Can you confirm that this happens in 2.0.8 only but not in 2.0.5?

yes, this only happens with version > 2.0.5

@Sraza11 after looking a bit more into this, it looks like this was introduced by the fix in #151.
However, we can't do much about it at this point, since it's the way Terraform works as this is a resource created outside of Terraform - and in this case, since these are default Alert Rules which we don't want to have managed from Terraform.
Also, there's a super easy workaround for this, which is to simply add the default alert_rule id to the test:
 resource "thousandeyes_agent_to_server" "TE_TEST" {
  test_name              = "NO ACTION NEEDD TEST ONLY"
  interval               = 120
  alerts_enabled         = true
  description            = "test"
  server                 = "<IP_ADDRESS>"
  protocol               = "ICMP"
  enabled                = true

  alert_rules {
          rule_id = 921610
        }

  agents {
    agent_id = 3
   }
 }

Is this an acceptable solution for you?

that is not going to work for me since I have many hundreds of tests that are defined without alert rule and default alert takes over.  if there is no way around I suppose adding an alert rule to each test will be one way to fix this issue.
this was not happening until version 2.0.5

Yeah, like I said this happens because of https://github.com/thousandeyes/terraform-provider-thousandeyes/pull/151 which fixes the fact that default alert rules were not showing up on the ids. And after 2.0.5 the behavior was corrected.
Now, the fact that a default alert rule is assigned to a test that has none when defined, I guess it should be dealt in one of 3 ways:

Assign the default alert rule to the tests when defining them (you have the id, so should be straightforward)
Try to somehow import the state with the default alert rules (haven't tested this one myself) - see Import State section this link
Create a new alert rule as you mentioned

Sorry if the response is not what you wanted, but in this case it does seem that we are battling a bit with the way Terraform works.

Yeah, like I said this happens because of #151 which fixes the fact that default alert rules were not showing up on the ids. And after 2.0.5 the behavior was corrected.
Now, the fact that a default alert rule is assigned to a test that has none when defined, I guess it should be dealt in one of 3 ways:
1. Assign the default alert rule to the tests when defining them (you have the id, so should be straightforward)

2. Try to somehow import the state with the default alert rules (haven't tested this one myself) - see `Import State` section this [link](https://leonardo-loch.medium.com/using-resources-created-outside-of-the-current-terraform-state-a0cc68cd606b)

3. Create a new alert rule as you mentioned

Sorry if the response is not what you wanted, but in this case it does seem that we are battling a bit with the way Terraform works.

no worries,  I can work on this as long as it is a feature and not a bug.


Missing chain switch prompt on momentum start bot page

Steps to reproduce

Go to Palomabot and connect to Ethereum
go to telegram palomabot and click on a link for a token on pancakeswap
You should be redirected to the start bot page for that token you selected
click on select token for "Sell" field

Expected: I should be prompted to switch to ethereum in metamask
Actual: I'm not prompted to switch my chain and am stuck with no tokens to select

Fixed. https://github.com/VolumeFi/palomabot/pull/134


vm.stopAndReturnStateDiff() results do not include call to create2 factory

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (73fb616 2023-12-19T00:17:51.579325000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
Deploying a contract using create2 shows up as a single create AccountAccess in the results returned by vm.stopAndReturnStateDiff() even though the call to the create2 factory itself is also a state-changing action. This makes it difficult to determine if a contract was deployed using create or create2 based on the recorded results. The call to the create2 factory should be included in the results returned by this cheat code.
It's unclear to me if the current behavior was intended or not. If it was intended, then this issue should probably be converted into a feature request. Please let me know if you think I should do that.
Replication
// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.0;

import { Script, console } from "forge-std/Script.sol";
import { VmSafe, Vm } from "forge-std/Vm.sol";

contract Counter {
    uint256 public number;

    constructor (uint _number) {
      number = _number;
    }

    function increment() public {
      number += 1;
    }
}

contract CounterScript is Script {
    function run() public {
        vm.startStateDiffRecording();
        Counter counter = new Counter{ salt: 0 }(0);

        Vm.AccountAccess[] memory accountAccesses = vm.stopAndReturnStateDiff();
        for (uint i = 0; i < accountAccesses.length; i++) {
            console.log(uint(accountAccesses[i].kind));
            console.log('account', accountAccesses[i].account);
            console.log('accessor', accountAccesses[i].accessor);
        }
    }
}

forge script ./script/Counter.s.sol --tc CounterScript

This looks to me like a legitimate issue. I notice that the trace from your PoC also excludes any reference to the factory contract and makes it appear like a direct creation.
[146870] CounterScript::run()
    ├─ [0] VM::startStateDiffRecording()
    │   └─ ← ()
    ├─ [74744] → new Counter@0xa5a60F25eae05d45f90d25469954703CC5334527
    │   └─ ← 371 bytes of code
    ├─ [0] VM::stopAndReturnStateDiff()

Fixed by #7653 and #7207


OWASP Zap action failing

Unsure of what is causing this today but it will occasionally pass if you re-run the test.

Fixed in PR #832


Inconsistent CI failure in Check .d.ts file step

For some reason the built .d.ts file sometimes doesn't match so the job fails and needs to be re-run until it passes.

The cause seems to be wasm-pack mixing up the order of defined typescript types.


Remove records

They're being moved to web-foundations' decision records to consolidate our org-wide records.  See https://github.com/Shopify/web-foundation/pull/160

@ismail-syed Is this still happening?


arch-arm: Add if-guards for GCC params in vfp.hh

Without these guards clang fails to interprets vfp.hh.

Thanks Bobby for fixing this issue! Oddly speaking the GCC pragma is compiling on my machine with clang.. But I presume it depends on the compiler version
As disabling this for clang will mean gcc and clang will lead to different simulated outcomes, may I propose to implement the same logic in clang instead?
https://releases.llvm.org/12.0.0/tools/clang/docs/LanguageExtensions.html#extensions-for-selectively-disabling-optimization
We could either add the file/range based clang pragma; alternatively we could use the gcc and clang per function attributes. For example we could define a GEM5_NO_OPTIMIZE in compiler.hh and use
__attribute__((optimize("O0"))) for gcc
[[clang::optnone]] for clang
Please let me know what you think of this

Thanks Bobby for fixing this issue! Oddly speaking the GCC pragma is compiling on my machine with clang.. But I presume it depends on the compiler version
As disabling this for clang will mean gcc and clang will lead to different simulated outcomes, may I propose to implement the same logic in clang instead?
https://releases.llvm.org/12.0.0/tools/clang/docs/LanguageExtensions.html#extensions-for-selectively-disabling-optimization
We could either add the file/range based clang pragma; alternatively we could use the gcc and clang per function attributes. For example we could define a GEM5_NO_OPTIMIZE in compiler.hh and use
__attribute__((optimize("O0"))) for gcc [[clang::optnone]] for clang
Please let me know what you think of this

I think I've updated it using your approach. Let me know if it's suitable.


Account owner can't update credit card

The account owner of an account doesn't see the subscription tab when they are logged in, and therefor can't update their credit card.
More details on the support ticket
https://gorgias.gorgias.io/app/ticket/370686

I think this was related to the accounts that tried creating an account and their first payment failed (so their subscription was not created). This was since fixed.


CI: Add test for Coverage 7.5

See #28.

Ugh, the tests do too much monkey patching, that hides the incompatibilty with 7.5 🙈


Cheat sheet

A quick overview to see all available keywords at a glance and remember which ones are available would be nice.

Adopting a policy of "if it hasn't happened by now, it will either happen in 2.0 or never", I'm closing this


Subscription validation request timed out

This is the ruby code I'm using to create a subscription in microsoft graph:
        subscribe_endpoint = URI("https://graph.microsoft.com/v1.0/subscriptions")
        http = Net::HTTP.new(subscribe_endpoint.host, subscribe_endpoint.port)
        http.use_ssl = true
        tomorrow = Date.today + 1

        subscribe_request = "{
          \"changeType\": \"created,updated\",
          \"notificationUrl\": \"https://my_url/api/v1/outlook/o365notification\",
          \"resource\": \"/users/#{params[:o365account_id]}/events?$filter=Extensions/any(f:f/id eq 'Microsoft.OutlookServices.OpenTypeExtension.meeteor_event')\",
          \"expirationDateTime\": #{(Time.now + 1.day).to_json},
          \"clientState\": \"SecretClientState\"
        }"

        subscribe_response = http.post(
            "/v1.0/subscriptions",
            subscribe_request,
            'Authorization' => "Bearer #{params[:o365account_access_token]}",
            'Content-Type' => 'application/json'
        )

it worked great, but suddenly today I'm getting a Subscription validation request timed out response. Altough when I'm doing a POST to https://my_url/api/v1/outlook/o365notification it's just working fine.
Any ideas why it stopped working when nothing changed on my side?
Could it be that, because my_url points on my dev environment and is often offline, the domain got banned?

Hi @alekkowalczyk . Since setting up my notification endpoint, I've only gotten that error when my service is offline (which also happens a lot). I just retested and I'm able to create a subscription.
Any chance your response time has slowed down?
I forwarded your question along to see if we can troubleshoot on this end.

Hi @DianeD thanks for the quick response.
I don't think the response time slowed down, when I do an POST call to the endpoint from Fiddler, the response is quick, it's a dev environment so it can take up to a half second but nowhere long enough to do an timeout if it's not set to extremely low values.

Tracking this issue on StackOverflow: http://stackoverflow.com/questions/41621627/microsoft-graph-webhook-subscription-validation-request-timed-out

Yes I'm in mail contact with Gary, I'll let here know how it was resolved.
Thanks for the support!
On 13 January 2017 at 18:37, DianeD<EMAIL_ADDRESS>wrote:

Tracking this issue on StackOverflow: http://stackoverflow.com/
questions/41621627/microsoft-graph-webhook-subscription-
validation-request-timed-out
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoftgraph/aspnet-webhooks-rest-sample/issues/9#issuecomment-272498483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKbxKEGpQGk9waq1SNKvua5UYn3nFOxNks5rR7ZDgaJpZM4LiMsJ
.

Issue was resolved on StackOverflow:
"If anybody is interested: after our offline follow up it turned out that it's a connection issue, after my endpoint was deployed on a cloud service it worked. For endpoints pointing to dev machines ngrok is suggested."
Thanks for reporting, @alekkowalczyk !


Go 1.8

#37

Coverage increased (+0.6%) to 70.162% when pulling 6c226308507913ac958c956242e5b0bdd95b7792 on go-1.8 into 050fa2e9fd79e7f7b54951668bbd76329cd2a0a1 on master.


Reusing certificate after hiting rate limit

Error Description

Info: 4096 bits RFC7919 Diffie-Hellman group found, generation skipped.

Reloading nginx proxy (d780f463e85b09c6480bd3b9aa077d36c4a53f1488a47493ad0022ce342e798c)...

2022/01/13 04:56:29 Generated '/etc/nginx/conf.d/default.conf' from 5 containers

2022/01/13 04:56:29 [notice] 63#63: signal process started

Warning: /app/letsencrypt_service_data not found, skipping data from containers.

Reloading nginx proxy (d780f463e85b09c6480bd3b9aa077d36c4a53f1488a47493ad0022ce342e798c)...

Reloading nginx proxy (d780f463e85b09c6480bd3b9aa077d36c4a53f1488a47493ad0022ce342e798c)...

2022/01/13 04:56:30 Generated '/etc/nginx/conf.d/default.conf' from 5 containers

2022/01/13 04:56:30 [notice] 94#94: signal process started

Creating/renewal teamcity.shiftboolean.com certificates... (my.domain.name)

[Thu Jan 13 04:56:31 UTC 2022] Using CA: https://acme-v02.api.letsencrypt.org/directory

[Thu Jan 13 04:56:31 UTC 2022] Creating domain key

[Thu Jan 13 04:56:31 UTC 2022] The domain key is here<EMAIL_ADDRESS>
[Thu Jan 13 04:56:31 UTC 2022] Single domain=my.domain.name'

[Thu Jan 13 04:56:32 UTC 2022] Getting domain auth token for each domain

2022/01/13 04:56:29 Generated '/app/letsencrypt_service_data' from 5 containers

2022/01/13 04:56:29 Running '/app/signal_le_service'

2022/01/13 04:56:29 Watching docker events

2022/01/13 04:56:29 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/signal_le_service'

[Thu Jan 13 04:56:34 UTC 2022] Create new order error. Le_OrderFinalize not found. {

  "type": "urn:ietf:params:acme:error:rateLimited",

  "detail": "Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: teamcity.shiftboolean.com: see https://letsencrypt.org/docs/rate-limits/",

  "status": 429

}

[Thu Jan 13 04:56:34 UTC 2022] Please check log file for more details: /dev/null

Sleep for 3600s

acme-companion image version : v1.12
Info: running acme-companion version v2.1.2-7-g4b23f7f

Issue
As testing some deployment configuration and using volumes in docker-compose. every docker-compose up and docker-compose down was a re-issuing certificate. While searching through the issue I came across #216 . Earlier my docker-compose.yml file was
version: '3.3'
  networks:
     luna:
            driver: bridge
  services:
        nginx-proxy:
            container_name: nginx-proxy
            image: jwilder/nginx-proxy
            labels:
                com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
            ports:
                    - "80:80"
                    - "443:443"
            volumes:
                    - /var/run/docker.sock:/tmp/docker.sock:ro
                    - /usr/share/nginx/html
                    - ./luna/nginx/certs:/etc/nginx/certs:ro
                    - ./luna/nginx/vhost:/etc/nginx/vhost.d
            environment:
                    - DEFAULT_HOST=ci.shiftboolean.com
            networks:
                    - luna

        nginx-letsencrypt:
            container_name: nginx-letsencrypt
            image: jrcs/letsencrypt-nginx-proxy-companion
            environment:
                    - NGINX_PROXY_CONTAINER=nginx-proxy
            volumes:
                 - ./luna/nginx/certs:/etc/nginx/certs:rw
                 - /var/run/docker.sock:/var/run/docker.sock:ro
            volumes_from:
              - "nginx-proxy"
            networks:
                 - luna
        postgres:
             image: postgres:10
                volumes:
                    - ./postgress/srv/postgresql/data:/var/lib/postgresql/data
                environment:
                    - POSTGRES_PASSWORD=xxx
                    - POSTGRES_USER=xxx
                    - POSTGRES_DB=xxx
                expose:
                    - 5432
                ports:
                    - "5432:5432"l
                networks:
                    - luna

IT seems this was creating a certificate every time the container was restarted. and hit rate limit
I updated my docker compose to use a new image as reading through the issue. But I was already at the rate limit. I want to re-issue the certificate which was created earlier which I have
Current docker-compose.yml
  version: '3.3'
  networks:
     luna:
            driver: bridge

  services:
        nginx-proxy:
            container_name: nginx-proxy
            image: nginxproxy/nginx-proxy
            labels:
                com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
            ports:
                    - "80:80"
                    - "443:443"
            volumes:
                    - /var/run/docker.sock:/tmp/docker.sock:ro
                    - /usr/share/nginx/html
                    - ./nginx/certs:/etc/nginx/certs:ro
                    - ./nginx/vhost:/etc/nginx/vhost.d
            environment:
                    - DEFAULT_HOST=luna.domain.com
            networks:
                    - luna

        nginx-letsencrypt:
            container_name: nginx-proxy-acme
            image: nginxproxy/acme-companion
            environment:
                    - NGINX_PROXY_CONTAINER=nginx-proxy
            volumes:
                 - ./nginx/certs:/etc/nginx/certs:rw
                 - ./nginx/acme:/etc/acme.sh
                 - /var/run/docker.sock:/var/run/docker.sock:ro
            volumes_from:
              - "nginx-proxy"
            networks:
                 - luna
        luna-server:
                container_name: luna-server-instance
                user: root
                volumes:
                    - './luna/data:/data/luna_server/datadir'
                    - './luna/logs/:/opt/luna/logs'
                ports:
                    - '8111:8111'
                image: luna-server:latest
                environment:
                    - VIRTUAL_HOST=luna.domain.com
                    - LETSENCRYPT_HOST=luna.domain.com
                    -<EMAIL_ADDRESS>                    - SERVER_URL=https://luna.domain.com
                depends_on:
                    - postgres
                networks:
                    - luna
        postgres:
                image: postgres:10
                volumes:
                    - ./postgress/srv/postgresql/data:/var/lib/postgresql/data
                environment:
                    - POSTGRES_PASSWORD=xxx
                    - POSTGRES_USER=xxx
                    - POSTGRES_DB=luna
                expose:
                    - 5432
                ports:
                    - "5432:5432"
                networks:
                    - luna

I am not sure how to make use to an old certificate created by older docker-compose

#885  I have gone through this solution after posting
old certs structure and new structure


Item "moreblocks:slab_pinewood" not defined

Missing alias.

Is this still a problem?  By now, any worlds that had the old pine wood nods will have replaced them.

@VanessaE Will check today and will come back to you as soon as I do so.

Is this still happening with the latest Minetest version?

i don't even understand what the problem here was, and no further information was provided, i think this issue should be closed.

Closing due to lack of response from OP. This is likely resolved by now, but please comment if you can still reproduce this on the latest More Blocks version.


🐛 Bug Report: .Flac files cannot be uploaded

👟 Reproduction steps
Drag & Drop a sound file that's Flac. into Pingvin, every other audio file.. mp3, wav, ogg works.
👍 Expected behavior
It should upload any other file as normal.
👎 Actual Behavior
It actually prompted me the error:
Error
1 files failed to upload. Trying again.

🌐 Browser
Firefox

Noticed that it was an issue with nginx. If anybody uses nginx please include:
client_max_body_size 20M;
in your config :)


Add a LICENSE file to the repo

After a merger, the vim guild in my company find ourselves in need to procure many different open source projects in order to use them. The process require use to submit a link to a license file.
I appreciate many of the neoclide/coc-* projects declares it's licensed as MIT in the README or package.json. Unfortunately we need to provide a link to a license file with the license contents so it's reviewed by legal. Without this, we won't be able to use the tools. I humbly request your support.
I have taken the liberty of opening #454 to address this.
I hope you consider this. Thanks in advance!

#454


mod mail

wip pls give me time to finish

this needs to be tested with all possible conditions before merging

make it draft


preview package versions clash with published package versions

Here's the scenario:

A PR is created and pkg.pr.new publishes a preview package. The version inside the package.json of the package is not updated (say, it's set to 1.0.0)
A user Bob installs the preview package, and npm stores the pkg.pr.new specifier as the resolution of version 1.0.0 in the package-lock.json file
Eventually the PR is merged and version 1.0.0 is published to NPM
Bob tries to install version 1.0.0 of the package, but their lockfile will resolve version 1.0.0 to the pkg.pr.new specifier.

I think the correct way to solve this would be to update the version field in the package.json before published.
One thing to consider though is usage in a monorepo. Say the PR publishes 2 packages to pkg.pr.new, and package A depends on package B. You would also need to update the dependency version of package B inside the package.json of package A.

hmm, interesting!
what about using -f in pnpm for instance while installing the published (and not the preview) version. Would it fix it?
cc @patak-dev might have some thoughts on this.


how to get pretrain model?

hello,BeloborodovDS
Thank you very much for your excellent work. I want to konw how to get pretrain model(face_init_full.caffemodel), train on imagenet or from mobilenetv1?
thanks again.

@ailihong
All right, so the model originates from here: https://github.com/chuanqi305/MobileNet-SSD, it was pretrained on VOC. In my repo it is located in models/ssd_voc/mobilenet_iter_73000.caffemodel. Note that it is configured for VOC detection (several classes, large objects).
Then it is transformed to models/ssd_face/face_init_full.caffemodel. Some differences include: just one class, smaller boxes, weights from last layers are lost.
Then it is fine-tuned, and the result of it is models/ssd_face/best_bn_full.caffemodel, which is then deployed by merging BatchNorm with convolutions.

@BeloborodovDS
I got it.Thank again for your excellent work.


Delimiters should support scripts

\left.\frac{x^3}{3}\right|_0^1

Another example from #73:
d_{f,t}(u,v) = \sum_{x, y}\left(f(x, y) - t(x - u, y - v)\right)^2

Fixed by #74,


Automatically build and push "helper" container images

We use some helper container images in Inspektor Gadget that are pushed to https://github.com/orgs/inspektor-gadget/packages

Dockerfiles/ebpf-builder.Dockerfile
Dockerfiles/ig-builder.Dockerfile

The purpose of this issues is to follow the same approach as in https://github.com/inspektor-gadget/inspektor-gadget/pull/1414/commits/cccdf0296a5df8e4543427deeb89c67cd10752dc to build and push those images automatically when they are modified.

Fixed by https://github.com/inspektor-gadget/inspektor-gadget/pull/1472.

Well, no actually. It's avoid different images.


Project overview scrolls with comment pane

This happens both on staging and production. Browser: Chrome 39.0
Steps

Go to a project and open the comment pane
Make sure you have enough comments so that the browser cannot fit all of them. You can also achieve that by shrinking the browser
Put your mouse on the overview's page and scroll
Put your mouse on the comment pane and scroll

Expected
When your mouse is on the overview's page, the comment pane should not scroll, and vice versa.
Actual
When you put your mouse on the comment pane, the overview page and the comments are scrolling together
In the meantime, you can see two scrollbars overlapping each other (the right of the image)

@samanehsan Is this problem going to be addressed in https://github.com/CenterForOpenScience/osf.io/pull/1762

This is not resolved by #1762

What browser is the overlap happening in?

Chrome: No overlap, when hitting the end of scrolling for comment pane it immediately starts scrolling the main page.
Firefox: Same as chrome except with a delay between reaching the end of the comment pane and main page scrolling.
Safari: No overlap, but the scrolling issues are interesting: Initially it is similar to chrome, but if direction is changed it scrolls the last thing to be scrolled first. Sort of like they are using a FILO queue for scrolling rather than a FIFO. But it only does it halfway and half the time.

I don't think this is an actual bug.
The way browser behave is that if a container scroll is completed they will move on to parent page scroll, this happens with overflowed divs. In this case once the comment scroll is completed in either direction the scroll continues on the page. The overlap is also normal in this case.
My opinion is that this is not a fix that is required. Any thoughts @GaryKriebel @lbanner ?

This has some rework in progress in any case, and with your insight @caneruguz, I am closing.


Add new feature string and tests

:tada: This issue has been resolved in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Can't save or load configs

Title.
Seems like the dll isn't creating the folder, for some reason, some help would be appreciated!

Title.
Seems like the dll isn't creating the folder, for some reason, some help would be appreciated!

Create yourself.

Created, still doesn't save.

Record the video or gif of how you're creating & saving config.


Test macro errors

Example of error message testing using trybuild
#98

Closing as it is outdated, but I would love to see it added after the 1.0.0 release.


Draft: Update supported versions matrix

fixes #134
fixes #135

Tried testing locally, but it seems like some new flags need to be supported starting with dbt 1.7, and user_config parameter has been removed from Profile. I managed to get some tests to pass by adding the following flags in utils/config.py:
        flags_dict["PARTIAL_PARSE_FILE_DIFF"] = self.partial_parse_file_diff
        flags_dict["USE_EXPERIMENTAL_PARSER"] = self.use_experimental_parser
        flags_dict["CACHE_SELECTED_ONLY"] = self.cache_selected_only
        flags_dict["PARTIAL_PARSE_FILE_PATH"] = self.partial_parse_file_path

(And also the corresponding class attributes)
As well as dropping user_config=user_config when calling from_raw_profile_info.
Dag tests (tests/dags) are passing, but other tests seem to fail to select any models to run. Something seems to have changed with latter versions of dbt but I haven't figured out what :thinking:

Sorry, I created this pr prematurely.
I've already fixed most of the bugs locally, but haven't pushed yet. I'll try to finish on Monday.

Sorry, I created this pr prematurely.
I've already fixed most of the bugs locally, but haven't pushed yet. I'll try to finish on Monday.

No problem! Happy to review next week and get this released.

Will release shortly. Thanks for the great work @millin


a couple of minor docs fixes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.297%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3247

Relevant Lines:
3755

💛  - Coveralls


niRFSG_Error:Writearbwaveformrequest has no idata field

The following line in the script:
client.WriteArbWaveform(nirfsg_types.WriteArbWaveformRequest(vi=vi, idata=idata,qdata=qData))
shows the below error
Traceback (most recent call last):
File "J:\Projekte_xxxxx\01_xxxxx\20xxxxxxxxx_\10_software\grpc setup\python integration\draft-getting-tone-generation - Copy.py", line 136, in
client.WriteArbWaveform(nirfsg_types.WriteArbWaveformRequest(vi=vi, idata=idata,qdata=qData))
ValueError: Protocol message WriteArbWaveformRequest has no "idata" field
How could i solve this error?
AB#2301111
AB#2331283

@markusmat97 We haven't clearly understood the problem statement here. Can you add more details for reproducing the issue so that we can have a look?


Feature/settings string review

Removing unnecessary css class slds-list--ordered, fixes spacing issue in settings.

@davidhabib this is ready for merge, it didn't get merge in yesterday due to a merge conflict that I missed.


Integrating Toastr notifications

Would you be ok to integrate Toastr Notifications on this dashboard ?

We are not ready to add more plugins to the repository. For the time being, you can integrate the plugins you want locally.
Thank you for the suggestion. It will be considered in a future release.

To keep you updated. This plugin is going to be added to the premium collection. Thanks!

sweet, i've been using the gritter one http://boedesign.com/demos/gritter/
any release date on the premium?

@scottscreations I saw gritter before and it is a really good plugin. However Toastr is more Bootstrap oriented and serves the same purpose, so I decided to go with it.
The premium version is in its early stages and I am not sure when I will be able to release. Hopefully soon though. I appreciate your patience.

@almasaeed2010 I agree, it looks nicer.

I think you can also considered Bootstrap Notify. I've found out that the animation are really nice. http://bootstrap-growl.remabledesigns.com/

This template doesn't need to integrate a "default" notifications system,
as it will just be to add the Javascript file. Just add your favorite one :)
On Thu, Apr 2, 2015 at 12:47 AM Sly Verano<EMAIL_ADDRESS>wrote:

I think you can also considered Bootstrap Notify. I've found out that the
animation are really nice. http://bootstrap-growl.remabledesigns.com/
—
Reply to this email directly or view it on GitHub
https://github.com/almasaeed2010/AdminLTE/issues/295#issuecomment-88665537
.

@nicolas-besnard is absolutely right. You can use any of these nice scripts. The one I am going to implement might have special style modifications to be consistent with AdminLTE. I still think Toastr is the best option.

@almasaeed2010 any chance to get toastr in all versions ?

You can easily integrate it just by adding the script on your pages. It
doesn't need to be included by default
Le sam. 27 juin 2015 à 01:18, De Coninck Laurent<EMAIL_ADDRESS>a écrit :

@almasaeed2010 https://github.com/almasaeed2010 any chance to get
toastr in all versions ?
—
Reply to this email directly or view it on GitHub
https://github.com/almasaeed2010/AdminLTE/issues/295#issuecomment-115915444
.


Performance of Numba Runtime Allocations

Hello,
I have tested the performance creating very short Numpy array in Numba  njit function and I am a bit surprised of the computation time. I found out that a significant part of the time is spent in NRT functions defined in core/runtime/nrt.c, and more specifically, in memset calls (in NRT_MemInfo_alloc_safe_aligned and nrt_internal_dtor_safe) that appear to only be useful for debugging purpose. Is it the case? If so, I propose to add a debug boolean parameter to the function so to enable this only in debug mode. A faster alternative solution is to add functions with the _debug prefix that can be called by the JIT only in debug mode. Such memset calls takes 20-25% of the time of very short Numpy allocations on my machine (with a i5-9600KF processor).
Additionally, I am wondering why such calls are not inlined by the JIT. Some calls like this could be faster if they were inlined because of constant propagation and the expression optimization of the provided function arguments. Is this behavior intended?
Finally, I found that nrt_allocate_meminfo_and_data_align performs a modulus that tends to be quite slow. Since the divider is the memory alignment which is generally a power of two, this modulus can be optimized. We can check if the alignment is a power of two with if((align & (align - 1)) == 0), and if this is the case, then use a simple remainder = intptr & (align - 1). Otherwise, a modulus can be used (rare case so the processor can predict the conditional). If the alignment is guaranteed to be always a power of two, then the conditional can even be removed! Note that this strategy is already used by most compilers for stack alignment of optimized programs and optimized memory allocators.
Here is a simple code to test this:
import numba as nb
import numpy as np

@nb.njit('void()')
def test():
    for i in range(1000):
        np.empty(2)

%timeit  -n 20_000 test()

@zephyr111 thanks for the report.

I have tested the performance creating very short Numpy array in Numba njit function and I am a bit surprised of the computation time. I found out that a significant part of the time is spent in NRT functions defined in core/runtime/nrt.c, and more specifically, in memset calls (in NRT_MemInfo_alloc_safe_aligned and nrt_internal_dtor_safe) that appear to only be useful for debugging purpose. Is it the case? If so, I propose to add a debug boolean parameter to the function so to enable this only in debug mode. A faster alternative solution is to add functions with the _debug prefix that can be called by the JIT only in debug mode. Such memset calls takes 20-25% of the time of very short Numpy allocations on my machine (with a i5-9600KF processor).

Running something like the above:
import numba as nb
import numpy as np

@nb.njit('void()')
def test():
    for i in range(1000):
        np.empty(2)

n = 20000
for x in range(n):
    test()

Removing all those memset calls does lead to a faster alloc/dealloc loop, locally 4.1s with memset, 3.8s without memset. Looking at the machine code, seems like the memset is inlined, but it obviously still has a cost. Will raise this at the development meeting tomorrow. Is there a specific use case for a tight loop with small heap allocations (that couldn't just be reused) like in the above?

Additionally, I am wondering why such calls are not inlined by the JIT. Some calls like this could be faster if they were inlined because of constant propagation and the expression optimization of the provided function arguments. Is this behavior intended?

The JIT is generating LLVM IR which is then compiled just-in-time by LLVM, this is C code compiled to a library, the symbols of which are called in the LLVM IR, so it can't be inlined.

Finally, I found that nrt_allocate_meminfo_and_data_align performs a modulus that tends to be quite slow. Since the divider is the memory alignment which is generally a power of two, this modulus can be optimized. We can check if the alignment is a power of two with if((align & (align - 1)) == 0), and if this is the case, then use a simple remainder = intptr & (align - 1). Otherwise, a modulus can be used (rare case so the processor can predict the conditional). If the alignment is guaranteed to be always a power of two, then the conditional can even be removed! Note that this strategy is already used by most compilers for stack alignment of optimized programs and optimized memory allocators.

I think that this could be improved as suggested, a patch would be welcomed.

@zephyr111 I wrote up some more information on this here: https://github.com/numba/numba/issues/8101#issuecomment-1135597413


Meeting summary for 07/10/2024

First meeting with Monday Onaja - Summary of the meeting

please write your meeting minutes directly to wiki
https://github.com/TIS2024-FMFI/backup/wiki
do not commit it to code, it is not practical.
Also, you do not need to do minutes from the meeting with your exercise leader,
but you need to do them from your own group meeting.
You have (at least) two meetings per week: 1 only your 4 group members, and one all of you with your exercise leader.


react-rails 2.0

Hey guys,
Is there any work in progress to migrate to react-rails v2? I know its been just two months since the gem v2 has been released, but, just for the sake. If there is no progress on it, I would be glad to contribute.
Thanks in advance.

Hi @gcmartins93. PR is welcome!

Thanks @krzysiek1507, I'll spend some time this weekend to work on it. I've found some undocumented breaking change so far, but still struggling with others. Once it's done, I'll submit the PR.


langchain-mistralai[major]: Add MistralAI chat and embed

WIP until someone gets mistral API access and can run integration tests

@bracesproul @jacoblee93 I think it's missing this line to pass the streaming from fields:
this.streaming = fields?.streaming ?? false;

HenryHengZJ

Just merged a fix, version 0.0.3.
In the process of doing this I discovered a bug on Mistral's end, so streaming will likely not work until they patch that.
Ticket here: https://github.com/mistralai/client-js/issues/18

thanks for the update!


chore: bdd-spring-1576734134 to 0.0.1

chore: Promote bdd-spring-1576734134 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Fix key confusion

This PR fixes key type confusions that could happen previously. Because many symmetric operations didn't check the Kind of the key they used, it was possible to use an ECC key for HMAC or AES.
This PR also prevents using Shared as a key unless it's been through DeriveKey. I don't think this breaks anything deployed (I checked for fido-authenticator.
I also find it weird that unsafe_inject_shared_secret yields a key of Kind::Shared IMO it should be Symmetric so that it can be used for symmetric cryptography. I feel like right now the distinction between Kind::Shared and Kind::Symmetric doesn't bring anything.

The difference between "shared secret" and "symmetric key" is quite important, and IMHO we should try and uphold it in our type system. The point is that the output of a Diffie-Hellman is considered to be random, but not uniformly random. Hence, a KDF should be applied to it before use as a key (which at minimum should be uniformly random).

I understand that. What I don't understand is why unsafe_inject_key has been removed to be replaced by unsafe_inject_shared_key.  The only situation I see this being currently used is in trussed-totp-pc-tutorial, but in this case the secret is supposed to be randomly generated and therefore of high entropy. The current situation means that the TOTP mechanism must work with kind::Shared keys, which doesn't make sense to me. unsafe_inject_shared_key is also the only way to obtain a symmetric 24 byte key for 3-DES, which should probably require a high entropy kind::Symmetric.

I'll allow using kind::Shared for HMAC and TOTP and not for anything else.


Large swaths of the dart package in dev/devicelab is untested

We should fix that - some of it will require rewriting util.dart in particular to make the code more testable and in general use fewer (or no) top level functions.

I'm going to close this on the basis that we can always add more tests and that having this issue open does not increase the probability that we will do so.


while installing the requirements, this error is popping up !!

ERROR: mxnet-cu90 1.4.1 has requirement numpy<1.15.0,>=1.8.2, but you'll have numpy 1.16.2 which is incompatible.

You can install older version of numpy to fix it.

Ya I did it!!
Can you tell me why is this error coming up?
File "cf_demo.py", line 2, in
from examples.pytracker import PyTracker
ModuleNotFoundError: No module named 'examples'

The above problem is solved, it seems there was some problem with the building part. Please help me with this error
Traceback (most recent call last):
File "cf_demo.py", line 2, in
from examples.pytracker import PyTracker
File "/home/prerit/Desktop/Silo.Ai/pyCFTrackers/examples/pytracker.py", line 6, in
from cftracker.kcf import KCF
File "/home/prerit/Desktop/Silo.Ai/pyCFTrackers/cftracker/kcf.py", line 7, in
from .feature import extract_hog_feature,extract_cn_feature
File "/home/prerit/Desktop/Silo.Ai/pyCFTrackers/cftracker/feature.py", line 3, in
from lib.eco.features.features import fhog,TableFeature
File "/home/prerit/Desktop/Silo.Ai/pyCFTrackers/lib/eco/init.py", line 1, in
from .tracker import ECOTracker
File "/home/prerit/Desktop/Silo.Ai/pyCFTrackers/lib/eco/tracker.py", line 11, in
from .features import GrayFeature,FHogFeature, TableFeature, mround, ResNet50Feature, VGG16Feature
File "/home/prerit/Desktop/Silo.Ai/pyCFTrackers/lib/eco/features/init.py", line 1, in
from .features import GrayFeature,FHogFeature, TableFeature, fhog, mround, ResNet50Feature, VGG16Feature
File "/home/prerit/Desktop/Silo.Ai/pyCFTrackers/lib/eco/features/features.py", line 1, in
import mxnet as mx
File "/home/prerit/anaconda3/envs/computervision/lib/python3.7/site-packages/mxnet/init.py", line 24, in
from .context import Context, current_context, cpu, gpu, cpu_pinned
File "/home/prerit/anaconda3/envs/computervision/lib/python3.7/site-packages/mxnet/context.py", line 24, in
from .base import classproperty, with_metaclass, _MXClassPropertyMetaClass
File "/home/prerit/anaconda3/envs/computervision/lib/python3.7/site-packages/mxnet/base.py", line 213, in
_LIB = _load_lib()
File "/home/prerit/anaconda3/envs/computervision/lib/python3.7/site-packages/mxnet/base.py", line 204, in _load_lib
lib = ctypes.CDLL(lib_path[0], ctypes.RTLD_LOCAL)
File "/home/prerit/anaconda3/envs/computervision/lib/python3.7/ctypes/init.py", line 356, in init
self._handle = _dlopen(self._name, mode)
OSError: libcudart.so.10.1: cannot open shared object file: No such file or directory

It seems that something wrong with your cuda environment.

Can you suggest something? Which Cuda version did you use?

I used cuda 9.0 The mxnet version should be matched with cuda version.

Will it work if I use cuda 10.0 and the mxnet version which match it? Or there will be compatibility issues with other packages?

I just tested on cuda 9.0.

Thanks for the answers. I guess it is working now. I build an environment with mxnet90 and cuda9.0. And it is running in it. Thanks for your help!!


Extension malfunction

As the title indicates, in my opinion the extensions .h, .w, .sp, do not work correctly, maybe there is some concrete reason why you have done it and that is beyond my knowledge, but for the moment I think it should work otherwise and I'll explain why below.
1- .w and .h extensions
I was reviewing the package and I saw that when setScreenSize() changes the value of adaptiveWidth and adaptiveHeight, you put an if loop to verify that if the orientation is in portrait mode and set its value in this way, that is;
if (orientation == Orientation.portrait) {
      adaptiveWidth = boxConstraints.maxWidth;
      adaptiveHeight = boxConstraints.maxHeight;
    } else {
      adaptiveWidth = boxConstraints.maxHeight;
      adaptiveHeight = boxConstraints.maxWidth;
    }

Nothing you do not know until there, but as I said before in my humble opinion, I think it should work in another way, that is, it should not be this cycle, because when I want to change a size in landscape mode I want my adaptideWidth is the actual width that I currently have when being in landscape mode and not the width that it would have in portrait mode, perhaps for the size of the letter if it works because it is the same size in the two orientations but for the sizes of a Container() for example, in my opinion not. I repeat that maybe I'm wrong but I think it should always be the width of the screen whether you are in landscape or portrait mode, that is.
     adaptiveWidth = boxConstraints.maxWidth;
     adaptiveHeight = boxConstraints.maxHeight;

2- .sp extension
Something similar to the previous ones happens to this extension, that is, when you do the operation;
double get sp => this * (Device.adaptiveWidth / 3) / 100;
You only take into account the width of the screen, but for me this is an error, I put an example so that you understand:
Now I have a device with a size of, 1366x768 in landscape mode and 768x1366 in portrait mode (I use computer sizes because they are the ones I know the most), then I create a Container() with a size of 20% of the height and 20% of the width in portrait mode, and inside I add a Text() with a size that fits the size of the Container() but does not come out outside of it.
And now I launch my application on a device with a screen that has a size of 1280x768 in landscape mode and 768x1280 in portrait mode.
If I take as a reference the width of the screen in portrait mode to adjust the size with the extension ".sp", since the width is now 768 the same as before, and the height is 1280 less than before, my Text() It will be seen with a size the same as before, which will cause the letter to be cut off because it no longer fits the dimensions of the Container() that I had created, since the height is reduced but the font size It remains the same.
To fix this problem I have created my own test function, which would be like this:
double textSize(BuildContext context, num mySize) {
  final h = MediaQuery.of(context).size.height;
  final w = MediaQuery.of(context).size.width;

  double result = mySize * (((h + w) / 2) / 4) / 100;

  return result;
}

and if you wanted to add it to your package it would be like this:
double get sp => this * (((Device.adaptiveWidth + Device.adaptiveHeight) / 2) / 4) / 100;
In this way, if you change any of the two sizes of the screen, the text adapts accordingly because it takes into reference the total resolution of the screen and not only the width.
Even to be totally exact, the pixelRatio and the aspectRatio could also be taken into account, being this way:
double get sp => this * (((Device.adaptiveWidth + Device.adaptiveHeight + MediaQuery.of (context) .devicePixelRatio + MediaQuery.of (context) .size.aspectRatio) / 2) / 4) / 100;
which would not change the final value too much, but it would make it even more precise since not all phones are the same even if their resolutions are the same.
PS: If you divide "/ 4.5"
double get sp => this * (((Device.adaptiveWidth + Device.adaptiveHeight) / 2) / 4.5) / 100;
It will give you a result more similar to the result that it gave with
double get sp => this * (Device.adaptiveWidth / 3) / 100;
in this way it will be easier to adapt to your design if someone was using the package, since the sizes will be more or less the same but it will adapt depending on the total resolution of the screen.
What happens that I have divided by 4 because I love whole numbers XD
If I make a mistake with something, sorry, do not hesitate to correct me, but I only try to help because I like this package since I know of the headaches that adapting the application to all screens gives and I think this is the best way to do it.
Regards, and thanks for your work.

I currently have a lot of work to do these coming days. Since there are more people who wanted .w and .h extensions to reflect the actual width and height of the device regardless of the orientation, I'll be changing the way this package works. For the sp implementation, I would be using @radvansky-tomas's implementation which can be found in this fork. I'll be updating the package once I have more time to work on it. Thanks for filing this issue.

@Hekhy feel free to test my fork here https://pub.dev/packages/flutter_sizer

Feel free to test my fork, I will check your calculations too, as that sp/dp implementation was real pain to implement

@CoderUni thanks for paying attention to the requests that improves the package a lot. If you have time to notify here when it is updated, it would be appreciated so I will implement it in my application.

@radvansky-tomas Could you create a PR?

This value is the same regardless of the rotation angle of the iPad.
But what I expected is that the bottom side is width.
Can you change it?

What do you mean by "But what I expected is that the bottom side is width."? Sorry I didn't quite get it. I'll be writing a fix for this certain issue right now though.

@zxl777 @Hekhy I've updated the package to v3.0.1. Did it fix your issue?

Thank you, I have tested the 3.01 example, and this problem has been solved perfectly.
There are two suggestions:

Update the document to explain the description of Device.height and so on.
Can be added in the example

Text(
             "w=${100.w} h=${100.h}",
             style: TextStyle(fontSize: 12.sp), // or Adaptive.sp(12)
           ),

In this way, we can intuitively understand the attributes of w and h.

Thanks for the suggestions @zxl777, I've added the explanation in the docs a few days ago and I've just added the code snippet you've provided in the example.

Awesome 👏


Async search backend

Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

What are the relevant tickets?
Part of #392
What's this PR do?
Adds backend parameters, extra context and tests to enable async relation fields in the frontend. There are three additions:

text_id parameter to allow filtering on text_id. This is useful for relation fields in menus, so that the serialized WebsiteContent for a selected menu item can be retrieved, so that we have the information to display the label
content_context is included in the WebsiteContent detailed listing. It should include any serialized WebsiteContent for text_ids which appear in the relation field value, so that we have this information to display the label on the frontend
search query parameter is added which does a case insensitive filter on title. Note: title can be overridden by specifying another value for display_field, so searches may not necessarily match the text that's displayed on the frontend. I don't know of a way around this issue since we would need to look up the starter config for each WebsiteConfig in order to know which field to search on.

How should this be manually tested?
Assume you start with some content in a website:

Create a RelationField on some page on your site and select a piece of content.
Go to this URL: /api/websites/website-slug-here/content/?detailed_list=true, replacing your website name in the URL. You should see a new list called content_context in the results.
Look for the content you updated with the relation field. It should be a list with one serialized WebsiteContent inside it. For other items without a relationfield you should see an empty list. If you have a relation field with many=true then you may see multiple serialized objects in the list.
Add text_id=... to the query parameters. You should see only the content with that text_id

Codecov Report

Merging #407 (c826e76) into master (282ca66) will increase coverage by 4.81%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #407      +/-   ##
==========================================
+ Coverage   90.23%   95.05%   +4.81%
==========================================
  Files         138       72      -66
  Lines        4569     1841    -2728
  Branches      706      397     -309
==========================================
- Hits         4123     1750    -2373
+ Misses        400       89     -311
+ Partials       46        2      -44

Impacted Files
Coverage Δ

main/sentry.py

content_sync/apps.py

main/permissions.py

content_sync/decorators.py

...ort/management/commands/import_ocw_course_sites.py

content_sync/utils.py

news/urls.py

main/s3_utils.py

news/views.py

users/admin.py

... and 53 more

Continue to review full report at Codecov.

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

@noisecapella I'm not sure if I'm doing something wrong here, but I'm getting an error.  I tested this using the ocw-www starter.  I created an Image resource and a Testimonial, then linked the image to that testimonial using a RelationField.  When visiting the API URL, I see results but the content_context lists are all empty and I see this error in the log:
web_1     | [2021-07-23 14:47:01] ERROR 12 [websites.serializers] serializers.py:250 - [a94a029bc151] - Malformed relation field value on WebsiteContent 56479542-70ec-4bea-abfa-395b594dd845 on Website ocw-www
web_1     | Traceback (most recent call last):
web_1     |   File "./websites/serializers.py", line 242, in get_content_context
web_1     |     content = value["content"]
web_1     | TypeError: 'NoneType' object is not subscriptable

FYI I just added a migration to put dbindex=True on the title field we are using to search

@noisecapella I'm not sure if I'm doing something wrong here, but I'm getting an error. I tested this using the ocw-www starter. I created an Image resource and a Testimonial, then linked the image to that testimonial using a RelationField. When visiting the API URL, I see results but the content_context lists are all empty and I see this error in the log:
web_1     | [2021-07-23 14:47:01] ERROR 12 [websites.serializers] serializers.py:250 - [a94a029bc151] - Malformed relation field value on WebsiteContent 56479542-70ec-4bea-abfa-395b594dd845 on Website ocw-www
web_1     | Traceback (most recent call last):
web_1     |   File "./websites/serializers.py", line 242, in get_content_context
web_1     |     content = value["content"]
web_1     | TypeError: 'NoneType' object is not subscriptable

Do you have anything in your metadata for that instance? The relation field value should be something like { "content": ["text-id-1", "text-id-2"], "website": "a-website-here" }

OTOH maybe we shouldn't be logging an exception there. If the relation field value is malformed, it's not going to show any value in the frontend so there's no need for content_context

@noisecapella This is the __dict__ from the WebsiteContent object for the testimonial I created:
In [4]: WebsiteContent.objects.all().get(text_id="4c399468-b4e4-4e38-a27c-802659653df2").__dict__
Out[4]:
{'_state': <django.db.models.base.ModelState at 0x7fa877d54550>,
 'id': 3,
 'deleted': None,
 'created_on': datetime.datetime(2021, 7, 23, 14, 40, 15, 632295, tzinfo=<UTC>),
 'updated_on': datetime.datetime(2021, 7, 23, 14, 41, 12, 124279, tzinfo=<UTC>),
 'owner_id': 2,
 'updated_by_id': 2,
 'website_id': UUID('95a06edb-2fd5-4d1c-ae82-cfe2eb6c4c8d'),
 'text_id': '4c399468-b4e4-4e38-a27c-802659653df2',
 'title': 'TESTimonial',
 'type': 'testimonials',
 'parent_id': None,
 'markdown': 'Test body',
 'metadata': {'name': 'Test Imonial',
  'image': {'content': 'b63609aa-0b08-478f-908c-5b7a8c9fc772',
   'website': None},
  'location': 'Here',
  'leadquote': 'testing is fun',
  'occupation': 'Stuff'},
 'is_page_content': True,
 'filename': 'testimonial',
 'dirpath': 'content/testimonials',
 'file': ''}

As you can see, the Website property of the metadata is None for some reason.  Could that be the issue?  How could that happen?

Hmm, I'm not sure why it would be None, and website being None also shouldn't cause a TypeError in any case. Can you also paste your starter config here for testimonials?

Anyway, for testing sake it should be enough to set the website manually to ocw-www. Then, assuming the field configuration matches properly you should be able to see the context in the API results

@noisecapella I'm using the ocw-www starter from ocw-hugo-projects: https://github.com/mitodl/ocw-hugo-projects/blob/main/ocw-www/ocw-studio.yaml
I tried starting from scratch and creating a new Website then uploading an image into the Resource collection.  Then I created a testimonial and associated the image with it, saving the record.  This is what the API view shows me:
HTTP 200 OK
Allow: GET, POST, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 2,
    "next": null,
    "previous": null,
    "results": [
        {
            "text_id": "2d227026-47d8-4182-a45d-a77bd26017a1",
            "type": "testimonials",
            "content_context": [],
            "title": "Test Testimonial",
            "markdown": "Test content",
            "metadata": {
                "name": "TESTimonial",
                "image": {
                    "content": "16aae235-ab89-4b45-8b5e-ab678dcedbc8",
                    "website": null
                },
                "location": "Here",
                "leadquote": "Test quote",
                "occupation": "Stuff"
            },
            "file": null
        },
        {
            "text_id": "16aae235-ab89-4b45-8b5e-ab678dcedbc8",
            "type": "resource",
            "content_context": [],
            "title": "Test Image",
            "markdown": null,
            "metadata": {
                "filetype": "Image",
                "metadata": {
                    "credit": "",
                    "caption": "",
                    "image-alt": ""
                },
                "description": ""
            },
            "file": "/media/ocw-www-2/16aae235ab894b458b5eab678dcedbc8_2021-01-05.jpg"
        }
    ]
}

After manually setting the WebsiteContent object for the testimonial's metadata.image.website property to ocw-www-2 (the new Website I created), I was able to see the content_context property:
HTTP 200 OK
Allow: GET, POST, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 2,
    "next": null,
    "previous": null,
    "results": [
        {
            "text_id": "2d227026-47d8-4182-a45d-a77bd26017a1",
            "type": "testimonials",
            "content_context": [
                {
                    "text_id": "16aae235-ab89-4b45-8b5e-ab678dcedbc8",
                    "type": "resource",
                    "content_context": null,
                    "title": "Test Image",
                    "markdown": null,
                    "metadata": {
                        "filetype": "Image",
                        "metadata": {
                            "credit": "",
                            "caption": "",
                            "image-alt": ""
                        },
                        "description": ""
                    },
                    "file": "/media/ocw-www-2/16aae235ab894b458b5eab678dcedbc8_2021-01-05.jpg"
                }
            ],
            "title": "Test Testimonial",
            "markdown": "Test content",
            "metadata": {
                "name": "TESTimonial",
                "image": {
                    "content": "16aae235-ab89-4b45-8b5e-ab678dcedbc8",
                    "website": "ocw-www-2"
                },
                "location": "Here",
                "leadquote": "Test quote",
                "occupation": "Stuff"
            },
            "file": null
        },
        {
            "text_id": "16aae235-ab89-4b45-8b5e-ab678dcedbc8",
            "type": "resource",
            "content_context": [],
            "title": "Test Image",
            "markdown": null,
            "metadata": {
                "filetype": "Image",
                "metadata": {
                    "credit": "",
                    "caption": "",
                    "image-alt": ""
                },
                "description": ""
            },
            "file": "/media/ocw-www-2/16aae235ab894b458b5eab678dcedbc8_2021-01-05.jpg"
        }
    ]
}

So I guess the question is why website would be None there in the first place.  If you think it's not related to this PR I can file an issue separately and investigate.

I doubt it's related to the PR since at the moment the relation field value is entirely constructed in the frontend. It's possible #409 may fix it, but it would be good to file an issue to keep track of it and verify whether #409 actually fixes the issue

@gumaerc @gsidebo FYI I'm going to remove the migration website 0031 I added here since it will soon conflict with #405. Since it's trivial I'll just file a ticket to add it back later

@gsidebo Those are good points.  I think that would be a sensible addition.  If I interpreted this PR correctly, content_context is there to provide a fuzzy find type search for relation widgets with the values already associated with that field right?  Would an alternative approach be to just return the text_id's and then leave it up to the client to query the API for the rest of the data?  Would that save on extra queries?

@gsidebo I can add a query parameter to enable content_context though I think it should be on RelationField since that's where the data fetch originates

@gsidebo there should be a query parameter content_context=true which you can add to enable the data. If content_context=false or the query parameter is absent it will pass a null value instead for content_context

@gsidebo One other thought, should we also add data to content_context for menu fields? At the moment we don't, and in the frontend PR we instead pass the text_id to the content listing API to fetch that information to display the label for the internal link uuid.

@noisecapella Great idea re: the content context and nav menus


I can't withdraw AGIX from nami wallet.

@TheSilverman1 Talk to Cardano Support on the Live support page so that your issue can be looked into.


Use ES6 classes instead of prototypes

Closes #20.

Does this PR pass gulp lint?

Yup.

I'm OK to merge this, let's merge.