az aks get-credentials should not point to privatelink dns zone

Describe the bug
az aks get-credentials generate an entry on ~/.kube/config pointing to privatelink via private zone.
Example:
https://my-aks-cluster-my-aks-cluster-a12345-a1234567.privatelink.<region>.azmk8s.io:443
name: my-aks-cluster

The correct address should be:
https://my-aks-cluster-my-aks-cluster-a12345-a1234567.hcp.<region>azmk8s.io

If I'm understanding this wrongly, maybe the documentation on https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-dns#on-premises-workloads-using-a-dns-forwarder should be updated.
Environment Summary
macOS-11.6.3-x86_64-i386-64bit, Darwin 20.6.0
Python 3.10.2
Installer: HOMEBREW

azure-cli 2.32.0 *

Extensions:
azure-devops 0.23.0
ssh 1.0.0

Dependencies:
msal 1.16.0
azure-mgmt-resource 20.0.0

Additional Context

route to CXP team

That’s the case, it’s a private cluster.
But shouldn’t private clusters get the public dns zone name? If I change the server url entry in kubeconfig to the public dns, I get a private IP, as expected.
At the portal, API endpoint is shown as cluster_name-resource_group-XXXXXX-XXXXXXXX.hcp.brazilsouth.azmk8s.io:
A DNS query for that address at <IP_ADDRESS> results (surprisingly) in its private IP (!) .
At the internal (on-premises) DNS server, the query returns the same result, NOT the privatelink zone address. The privatelink address for that cluster is cluster_name-resource_group-XXXXXX-XXXXXXXX.privatelink.brazilsouth.azmk8s.io.
In other Azure products we have private links for, when we query the public zone at the internal server, we got a CNAME to the private zone, but with a A entry on the same response. If we query an external server like <IP_ADDRESS> we got an Azure IP (not ours).
To wrap up:

External (public) DNS resolution for private clusters seems strange (unlike other azure products), leaking our private IP in a public query.
The get-credentials command give me the private zone address, which we don’t (as per the azure documentation) have no forwarder on-premises to.
Nonetheless, the api endpoint responds on the public zone address, which allows us to use it as long as kubeconfig is changed.

Thanks for your response.

Em 11 de mar. de 2022, à(s) 21:17, SaurabhSharma-MSFT @.***> escreveu:
@weltonrodrigo https://github.com/weltonrodrigo I could see the correct server entry in config file. Please check below.
https://user-images.githubusercontent.com/38112130/157994558-8c94c58c-3178-4560-8740-8d5339bb5363.png
You may be getting the private link entry if your cluster is a Private AKS https://docs.microsoft.com/en-us/azure/aks/private-clusters. Please verify and let us know if that's not the case.
—
Reply to this email directly, view it on GitHub https://github.com/Azure/azure-cli/issues/21584#issuecomment-1065706850, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMRQZBARIOKHEE4IEFBEJ3U7PPB7ANCNFSM5QNDTBHQ.
You are receiving this because you were mentioned.

@weltonrodrigo I am checking internally on this and get back to you. Thanks

@weltonrodrigo Can you please try using az aks get-credentials -n <cluster> -g <rg>  --public-fqdn ?

—public-fqdn gives me the public zone. Thank you.

Em 22 de mar. de 2022, à(s) 21:59, SaurabhSharma-MSFT @.***> escreveu:
@weltonrodrigo https://github.com/weltonrodrigo Can you please try using az aks get-credentials -n  -g  --public-fqdn ?
—
Reply to this email directly, view it on GitHub https://github.com/Azure/azure-cli/issues/21584#issuecomment-1075799164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMRQZE7BCR753LHRFK3NU3VBJUH3ANCNFSM5QNDTBHQ.
You are receiving this because you were mentioned.


Update to 0.4.1

Also re-render and modernize the recipe.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Parameter to verify certificate chain when use Mojo::IOLoop::Client (Mojo::UserAgent)

In current version of Mojo to check certificate chain need to set tls_ca param (ca param in Mojo::UserAgent) to true value or specify file which not exist.
I believe that this unpredictable behavior.
I think that need to add additional param (something like tls_verify) to implicit verify certificate chain.

Don't think this issue contains enough information to consider it a feature request. Perhaps you should try discussing it on IRC or the mailing-list first.

I think the question was that there is no way to explicitly set SSL_verify_mode to SSL_VERIFY_PEER without specifying the SSL_ca_file.
@Logioniz you can set ca attribute to \undef for this (check docs https://metacpan.org/pod/distribution/IO-Socket-SSL/lib/IO/Socket/SSL.pod#SSL_ca-SSL_ca_file-SSL_ca_path)
May be this use case should be described in ca docs.

@avkhozov, thanks, i think it should be documented.


KeyError: 'ゖ'

Here's another KeyError I found:
% cutlet
齋藤タヶオ
Traceback (most recent call last):
  File "/Users/ykim/.local/share/virtualenvs/sandbox-nIHPi2Hu/bin/cutlet", line 8, in <module>
    sys.exit(main())
  File "/Users/ykim/.local/share/virtualenvs/sandbox-nIHPi2Hu/lib/python3.8/site-packages/cutlet/cli.py", line 16, in main
    print(katsu.romaji(line.strip()))
  File "/Users/ykim/.local/share/virtualenvs/sandbox-nIHPi2Hu/lib/python3.8/site-packages/cutlet/cutlet.py", line 133, in romaji
    roma = self.romaji_word(word)
  File "/Users/ykim/.local/share/virtualenvs/sandbox-nIHPi2Hu/lib/python3.8/site-packages/cutlet/cutlet.py", line 198, in romaji_word
    return self.map_kana(kana)
  File "/Users/ykim/.local/share/virtualenvs/sandbox-nIHPi2Hu/lib/python3.8/site-packages/cutlet/cutlet.py", line 238, in map_kana
    out += self.get_single_mapping(pk, char, nk)
  File "/Users/ykim/.local/share/virtualenvs/sandbox-nIHPi2Hu/lib/python3.8/site-packages/cutlet/cutlet.py", line 271, in get_single_mapping
    return self.table[kk]
KeyError: 'ゖ'

It feels like we're slowly inching toward bullet proofing cutlet xD

Gah, I thought I caught all these. Should be fixed in master now.
I'll look at testing a whole Unicode block or fuzzing cutlet so this doesn't happen any more.

OK, I have gone over the relevant Unicode blocks and I think I have it all now. I will try fuzzing though.

Ended up not trying fuzzing, but I went ahead and released the fix for this.


Desktop: Lets give a subtle golden lustre animation to the Keeper logo

If we are going for animation direction then We have an animation option here placed in file:
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=484-8461&t=jSTMtkWC16JG36dV-1


Next

FIX generate matches "saveSchema".

Peto what's this? it does not compile see travis marks. where is problem?
You should create separeate branch for each pull request, please. For now i do not know what i should merge.


Unexpected properties in tauri.conf.json

I was trying to compile the orga gui example.
Got the following error:
❯ make example-Orga-gui
(cd -P examples/Orga && tar -cf /home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/Orga.ayapack --exclude=plugins -- *)
cd plugins && make plugins
make[1]: Entering directory '/home/rot/pr/rustpr/ln/zirka-game/Ayaka/plugins'
cargo build --target wasm32-unknown-unknown --release
    Finished `release` profile [optimized] target(s) in 0.10s
mkdir -p ../examples/plugins
cp target/wasm32-unknown-unknown/release/*.wasm ../examples/plugins/
make[1]: Leaving directory '/home/rot/pr/rustpr/ln/zirka-game/Ayaka/plugins'
(cd -P examples && tar -cf /home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/plugins.ayapack -- plugins)
cd bins && make run-gui FILE='/home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/Orga.ayapack /home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/plugins.ayapack'
make[1]: Entering directory '/home/rot/pr/rustpr/ln/zirka-game/Ayaka/bins'
cd ayaka-gui && make run FILE='/home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/Orga.ayapack /home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/plugins.ayapack'
make[2]: Entering directory '/home/rot/pr/rustpr/ln/zirka-game/Ayaka/bins/ayaka-gui'
cargo tauri dev -- -- /home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/Orga.ayapack /home/rot/pr/rustpr/ln/zirka-game/Ayaka/examples/plugins.ayapack
       Error `tauri.conf.json` error on `build`: Additional properties are not allowed ('devUrl', 'frontendDist' were unexpected)
       Error `tauri.conf.json` error: Additional properties are not allowed ('app', 'bundle', 'identifier', 'productName', 'version' were unexpected)
make[2]: *** [Makefile:11: run] Error 1
make[2]: Leaving directory '/home/rot/pr/rustpr/ln/zirka-game/Ayaka/bins/ayaka-gui'
make[1]: *** [Makefile:24: run-gui] Error 2
make[1]: Leaving directory '/home/rot/pr/rustpr/ln/zirka-game/Ayaka/bins'
make: *** [Makefile:53: example-Orga-gui] Error 2

Fibonacci2 example works with no issues
I was following the docs so, tell me if I'm doing something wrong.
I'm open to any questions.

If one example works, the other should work. What's your tauri-cli version?

If one example works, the other should work. What's your tauri-cli version?

❯ cargo tauri --version
tauri-cli 1.5.14

Should be the latest version from nixpkgs-unstable

You need a beta version, e.g., 2.0.0-beta.18

That fixed the issue :+1:
The example now runs without issues.
I recommend to add this mention to the docs.

I recommend to add this mention to the docs.

Would you like to open a PR for that?

Just in quick_start is OK, I think. And by the way, this command is simpler:
cargo install tauri-cli --version 2.0.0-beta.18

Got it!
Just wanted to ask if we should use any latest beta version or just specifically 2.0.0-beta.18 for now?
I currently have version 2.0.0-beta.20 working without issues.

Currently there's only beta.18 on crates.io

I opened a PR to change the docs #344


[BUG] ...Could not retrieve an AuthToken from the B2C Commerce Account Manager instance

Attempting to run npm run crm-sync:sf:b2cinstance:setup and getting the following error...
Error: Could not retrieve an AuthToken from the B2C Commerce Account Manager instance.  Please enable auditing on the B2C Client ID for additional details.
at Command. (/Users/rory.wickham/Workspaces/crmsync/b2c-crm-sync/lib/cli-interface/_sfB2CInstanceSetup.js:246:27)
at processTicksAndRejections (node:internal/process/task_queues:93:5)
Node version: 15.2.1
NPM version: 7.0.8
SFDX version: 7.140.0
B2C version: 24.2

Getting the same error while executing the command: npm run crm-sync:sf:b2cclientid:setup
Anyone found the root cause for this issue?


[VS Code] Unable to connect to the host. Verify both you and the host are online.

Error:
Unable to connect to the host. Verify both you and the host are online.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.735

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.27.2

platformName
Linux

platformVersion
4.15.0-34-generic

Closing as a dupe of 327.


Issue 46

Hey there!
Please review my changes.
Thank you very much.

Hey @badgersow,
This looks like a great effort. I like the names of classes you've used, and the test coverage is great.
I have a few issues though, which means I can't merge right away:

by default, this approach will always load classes to get the line numbers. This can cause errors when running from the CLI, and the classes are not available from the classpath, or they fail to load, etc. There are two options: A) convert the existing code (LineNumbers), in it's current form, to not load classes. B) only call LineNumbers when creating the error for a unit test, and only do it for unit tests, where the class is likely to be loaded anyway. I much prefer option A, and the good news is, if LineNumbers can get the information via reflection, then it can get it via bytecode too. I'll describe this in more detail in a moment.
I don't mind copying in code if the license permits, but if it's copied in, I don't think we can't strip the original copyright, according to the Redistribution section here. Of course, IANAL, so please correct if wrong. Let's see if the previous issue makes it a moot point or not.

It's very close though!
So, reflection. I'm going by the principle that in order for reflection to work at all, the bytecode must contain all the information necessary -- I don't see how it could possibly work otherwise. I think that the reflection classes (Class, Method, Field) used in LineNumbers are only used as a convenience.
For example, getDeclaringClass is called, but it's only needed to check that an instance of LineNumbers contains the same class as that which the Member belongs to when getLineNumber is called. We can either enforce this further up the call stack, or throw an exception later when we don't find the member, because this can only be a programmer error on our part, not the users. For example, in LineNumbersUtil, we take a fieldName string, and if you trace back all the code paths that end up invoking that method, the field name comes from ASM. So as long as we're careful, we can ensure all callers only pass a valid class and field name combination. That way we don't need an instance of Class to call getDeclaredField on, and we don't need to do Class.forName in LineNumbersUtil.
Later uses of the Member type are to construct a key, for later lookup in a map, and that seems to be it. Actual storing of that key against a line number is done with "vanilla" ASM code that doesn't need to load classes. The key for the field is simple, it's just the name. The key for the method is a bit more tricky, for example it calls ASM's Type.getMethodDescriptor(Method), but there's another method on that class that does the equivalent, but takes a Type instead, which doesn't require reflection. It's possible to supply an equivalent instance of Type, in fact we could probably pass it all the way from the visitor that raised the error. For example, where we detect setter methods, it's in the setter method itself, so the method descriptor can't be that far away. Constructor is the trickiest, but I believe it's doable (not sure how off the top of my head though).
Once we don't need to do Class.forName, the ASM visitor that retrieves line numbers can reuse the code within Mutability Detector that attempts various ways of visiting classes and adds some custom error handling (check out the class InformationRetrievalRunner).
To conclude, the bad news is I can't accept the PR as it is, but the good news is all the structure is there and looking good, and I see no reason the implementation can't be tweaked to avoid loading classes.
Are you happy to pursue the changes I've described?

Hi.
Thank you for your comment. I am really didn't think about the problem of loading classes.
You are completely correct: there is no need to load classes when we can avoid it.
Thanks again for your suggestion about the way code can be changed.
I really like the format of working with MutabilityDetector: I am learning a lot from every issue and comment.
I will proceed with fixing the problem in the next few days.
About the licensing issue: Let's discuss this after code will be accepted by you.
Thanks again, I'll continue my work.

Hi, @Grundlefleck !
Could you please advice about possible better way to implement the problem I ran into?
First, I rewrote LineNumbers class not to use Class.forName and it works OK, you was completely right about this.
Now I try to use common analysis functionality (InformationRetrievalRunner) for line numbers info (see class LineNumbersInformation).
As before, I want CodeLocation class to be able to print itself via prettyPrint method with line numbers info.
But now I can't simply use LineNumbersUtil in CodeLocation.prettyPrint, I need to obtain LineNumbersInformation from AnalysisDatabase.
I investigated how analysis information is processed now: it is obtained in MutabilityCheckerFactory and passed as parameter to some checkers.
The only difference is this: old analysis information (PrivateMethodInvocationInformation, etc.) was required only for some checkers, but line numbers info will be required for ALL checkers (it is necessary for CodeLocation to print itself).
As one of the possible ways I can do the following:

Create CodeLocationFactory with line numbers info and pass it to all checkers in MutabilityCheckersFactory. You can see I do it for ArrayFieldMutabilityChecker and CollectionWithMutableElementTypeToFieldChecker in latest commit. This will allow for all checkers to create CodeLocation instances via CodeLoca tionFactory and that CodeLocation instances will be aware about line numbers.

Rewrite all checkers and tests to create CodeLocation instances only via CodeLocationFactory.

But before I refactor checkers and tests I want to ask you, what do you think about this approach?
Maybe I overcomplicate things and you know how it can be solved easier?
Thanks very much for your time!

Hi Efim,
Sounds like you're definitely making progress in the right direction, good
stuff.
I haven't looked at the diffs, but the way you suggested sounds fine, but
just to complicate things, let me throw a few other thoughts into the mix:

did you intend to keep CodeLocation as an immutable value type? I would
like that, and wasn't sure if you were proposing that CodeLocation could
call LineNumbersInformation or if the checkers would do that and just pass
source file and line number to a CodeLocation constructor.

I wonder if perhaps the checker superclass that is inherited by all could
help keep track of line numbers as the class was being analysed. Meaning,
if the superclass had a lineNumber() and sourceFile() method that returned
the right value when calling addReason(), it would save having to have a
LineNumbersInformation class at all. At the expense of having a more
complicated super class, and probably having some way of making sure a
subclass didn't accidentally break the methods. This would save on
complexity of looking up the location separately, which can be complicated
if trying to specify completely unambiguous parts of the class to look up.
It would also imply there would be only one pass over the bytecode, which
would be a little bonus. I've not thought through exactly how this would
work, do you think it's worth trying? Since it's all implementation detail
we can do as you are proposing now and revisit later.

If you don't want to consider these points just now, and continue with your
suggested approach, I am fine with that too. I like that the parts being
worked on are internal, gives a lot of freedom to just get it working and
change later if we feel the need.
Is that helpful?
On 2 Apr 2016 5:54 pm, "Efim Pyshnograev"<EMAIL_ADDRESS>wrote:

Hi, @Grundlefleck https://github.com/Grundlefleck !
Could you please advice about possible better way to implement the problem
I ran into?
First, I rewrote LineNumbers class not to use Class.forName and it works
OK, you was completely right about this.
Now I try to use common analysis functionality (InformationRetrievalRunner)
for line numbers info (see class LineNumbersInformation).
As before, I want CodeLocation class to be able to print itself via
prettyPrint method with line numbers info.
But now I can't simply use LineNumbersUtil in CodeLocation.prettyPrint, I
need to obtain LineNumbersInformation from AnalysisDatabase.
I investigated how analysis information is processed now: it is obtained
in MutabilityCheckerFactory and passed as parameter to some checkers.
The only difference is this: old analysis information (
PrivateMethodInvocationInformation, etc.) was required only for some
checkers, but line numbers info will be required for ALL checkers (it is
necessary for CodeLocation to print itself).
As one of the possible ways I can do the following:

Create CodeLocationFactory with line numbers info and pass it to all
checkers in MutabilityCheckersFactory. You can see I do it for
ArrayFieldMutabilityChecker and
CollectionWithMutableElementTypeToFieldChecker in latest commit. This
will allow for all checkers to create CodeLocation instances via
CodeLoca
tionFactory and that CodeLocation instances will be aware about line
numbers.
Rewrite all checkers and tests to create CodeLocation instances only
via CodeLocationFactory.
But before I refactor checkers and tests I want to ask you, what do you
think about this approach?
Maybe I overcomplicate things and you know how it can be solved easier?
Thanks very much for your time!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/MutabilityDetector/MutabilityDetector/pull/73#issuecomment-204756670

Thanks for reply!
Your observations are helpful,
I'll consider them during my investigation.


Update dist and qunit process

QUnit should run on the compiled dist code, which should be generated when QUnit task is kicked off.
Everyone should be checking in their dist --OR maybe not(!).

Update Grunt tasks to make qunit task generate the dist and then run qunit
Update QUnit to test the dist files instead of the dev files
Update documentation to tell people to always commit their dist files
Update documentation to tell people how to deal with the now more frequent merge conflicts that this will result in

Maybe also keep the current way to run unit tests around so you can test your files while you develop on them for speed. Like a qunit-dev task or something, idk...

I don't think we should have dist files in Pull Requests, so we would need a way to delete them at the end of the unit tests, too.
If we truly need to test the fuelux.js and fuelux.min.js, it should be a part of the release task and probably be a URL variable set in test/fuelux.htmlthat conditionally loads the dist JS instead of the individual controls.

Dist should not be committed on every PR

OK, closed the pull request because I've been thinking about the dist directory stuff and trying to make sure we are making the change intelligently. The problems as I saw them were:

People weren't actually testing their changes (which included making sure it would compile to dist and testing dist, which means testing everything together whereas previously we were only testing everything separate, as separate modules)
dist was often completely out of date

One way to "fix" this is just have everyone compile and check in dist. However, there are some specific problems with this:
A) Muddies the PRs (there are strategies to get around this, but, we are still "getting around" it)
B) (and this is the key one for me) It complicates automation. If we want to do automated merges of more than just one branch and master, we have to do extra work to compensate for the merge conflicts
C) It complicates merges. If you branched off of an older version of master and then you want to merge in the newer version of master, you'll have very easily fixable (but annoying) merge conflicts (edited)
I'm going to be thinking about this over the weekend, and hope to get a chance to look at the links that the Stephens provided, but, I just wanted to let you know why I killed the PR and that I don't consider the topic "closed" in my mind and may actually end up arguing for keeping it the way we have it. I think we can solve the stated problems in different ways than the "obvious" way of having everyone commit their dists

http://githooks.com/
Another approach to consider (as if we don't have enough) is a git hook on post commit. This could keep the build step separate from development work but reinforce the dist folder staying up-to-date.

For now, address dist dir confusion with a pre-commit (or pre-pr???) hook that blocks PRs with dist changes from being submitted so the user knows immediately. #1104

Abandoned

To provide a bit more clarity, a lot of work was done around this, but, no more work will be done for this particular issue (any more work around this topic will be done under a new issue. This one is now closed).


Logo sometimes does not load

Example: http://localhost:4200/grants/1
Directly entering this URL into the browser, the app will try to load the logo from localhost:4200/grants/logo.png.
Logo image appears as <img src='logo.png' ... > in the browser, though in template (application.hbs), it is written as src='{{rootURL}}logo.png'. rootURL issue?

But works from http://localhost:4200/grants/. Perhaps some issue with dynamic segments?


Failed installation

I installed V extension, and then tried to install VLS (from V extension setting Vls: Enable).
At first try:
builder error: cannot write to folder C:\Users\Максим\.vls\bin: No such file or directory

At second:
Error: Command failed: git pull --rebase origin master
From https://github.com/vlang/vls
 * branch            master     -> FETCH_HEAD
Rebasing (1/210)
Rebasing (2/210)
Rebasing (3/210)
error: could not apply 12c9646... vls, lsp: make tree sitter work on vls
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 12c9646... vls, lsp: make tree sitter work on vls

Also, I tried to compile VLS by myself. I use commands from main branch at last commit with gcc instead of clang.
C:\vls>v run build.vsh gcc
> Building VLS...
V panic: chmod failed: No such file or directory
v hash: 227d12f
C:/Temp/v/v2.17047977922843096392.tmp.c:16895: at _v_panic: Backtrace
C:/Temp/v/v2.17047977922843096392.tmp.c:29543: by v__vcache__CacheManager_key2cpath
C:/Temp/v/v2.17047977922843096392.tmp.c:29561: by v__vcache__CacheManager_postfix_with_key2cpath
C:/Temp/v/v2.17047977922843096392.tmp.c:17903: by v__builder__Builder_get_os_cflags
C:/Temp/v/v2.17047977922843096392.tmp.c:17262: by v__builder__Builder_setup_ccompiler_options
C:/Temp/v/v2.17047977922843096392.tmp.c:17448: by v__builder__Builder_cc
C:/Temp/v/v2.17047977922843096392.tmp.c:16988: by v__builder__Builder_compile_c
C:/Temp/v/v2.17047977922843096392.tmp.c:17964: by v__builder__compile
C:/Temp/v/v2.17047977922843096392.tmp.c:18859: by main__main
C:/Temp/v/v2.17047977922843096392.tmp.c:19601: by wmain
0077f227 : by ???
0077f2ec : by ???
767bef3c : by ???
76e8360c : by ???
76e835df : by ???
Failed building VLS

Commands below was executed on Windows 7/32bit

PS C:\> git clone https://github.com/vlang/vls
Cloning into 'vls'...
remote: Enumerating objects: 3312, done.
remote: Counting objects: 100% (1482/1482), done.
remote: Compressing objects: 100% (725/725), done.
remote: Total 3312 (delta 967), reused 1149 (delta 709), pack-reused 1830Receiving objects:  95% (3147/3312), 1.79 MiB |Receiving objects:  98% (3213/3312), 1.79 MiB | 425.00 KiB/s
Receiving objects: 100% (3312/3312), 1.83 MiB | 435.00 KiB/s, done.
Resolving deltas: 100% (2043/2043), done.
PS C:\> cd vls
PS C:\vls> v run build.vsh gcc
> Building VLS...
C:\vls\tree_sitter\lib\lib.o not found, building it in C:\Users\yuyi9\.vmodules\cache\e1\e15f4274238f2cf6e0bb743bc9461dd4.o ...
C:\vls\tree_sitter_v\src\parser.o not found, building it in C:\Users\yuyi9\.vmodules\cache\2e\2e3b85b7c489bf4f7e5f422c8b602edd.o ...
> VLS built successfully!

Maybe it is a compilation cache error, you can clean the cache and try again.

How can I do it?

delete .vmodules/cache.

delete .vmodules/cache.

Same error, even with deleting the whole .vmodules folder

v doctor if it can help:
C:\vls>v doctor
OS: windows, Microsoft Windows 7 Home Basic v7601 32-bit
Processor: 2 cpus, 32bit, little endian, AMD Turion(tm) II Dual-Core Mobile M520
CC version: cc (Rev4, Built by MSYS2 project) 10.3.0

getwd: C:\vls
vmodules: C:\Users\Максим\.vmodules
dules
vroot: C:\v
vexe: C:\v\v.exe
vexe mtime: 2021-09-02 15:30:42
is vroot writable: true
is vmodules writable: false
V full version: V 0.2.4 bd33eaa.227d12f

Git version: git version 2.31.1.windows.1
Git vroot status: 0.2.4-13-g227d12f1 (6 commit(s) behind V master)
.git/config present: true
thirdparty/tcc status: thirdparty-windows-i386 a59d4f9c

@Masynchin try executing v wipe-cache then recompile once again.

@Masynchin try executing v wipe-cache then try compile it again.

C:\vls>v wipe-cache
V cache folder C:\Users\Максим\.vmodules\cache was wiped.
iped.

C:\vls>v run build.vsh gcc
> Building VLS...
V panic: chmod failed: No such file or directory
v hash: 227d12f
C:/Temp/v/v2.17047977922843096392.tmp.c:16895: at _v_panic: Backtrace
C:/Temp/v/v2.17047977922843096392.tmp.c:29543: by v__vcache__CacheManager_key2cpath
C:/Temp/v/v2.17047977922843096392.tmp.c:29561: by v__vcache__CacheManager_postfix_with_key2cpath
C:/Temp/v/v2.17047977922843096392.tmp.c:17903: by v__builder__Builder_get_os_cflags
C:/Temp/v/v2.17047977922843096392.tmp.c:17262: by v__builder__Builder_setup_ccompiler_options
C:/Temp/v/v2.17047977922843096392.tmp.c:17448: by v__builder__Builder_cc
C:/Temp/v/v2.17047977922843096392.tmp.c:16988: by v__builder__Builder_compile_c
C:/Temp/v/v2.17047977922843096392.tmp.c:17964: by v__builder__compile
C:/Temp/v/v2.17047977922843096392.tmp.c:18859: by main__main
C:/Temp/v/v2.17047977922843096392.tmp.c:19601: by wmain
0077f227 : by ???
0077f2ec : by ???
75bfef3c : by ???
77ab360c : by ???
77ab35df : by ???
Failed building VLS

C:\vls>


fix typos in readme

thanks, but will need a quick rebase post https://github.com/stefanpenner/ember-improved-cp/pull/4/files

@stefanpenner looks like rebased


Added travis ci support

@amilajack Huge thanks for that. If it's OK with you, gonna check it tomorrow.

Sure thing

👍


Do you have the function of URL jump

Do you want to request a feature or report a bug?
bug

Bug

What did you do?

What did you expect to see?
What did you see instead?
Output of traefik version: (What version of Traefik are you using?)
v2.2.0

(paste your output here)

I just want to pass traefik2.2 To enable user browser access test.com If you do, automatically jump to www.test.com 。 At present, our domain name is www.test.com , configured HTTP to jump to HTTPS through tracefik, that is, user access www.test.com It can automatically jump to https://www.test.com , using the middleware function, has been implemented. But now I want to implement user access test.com And then automatically jump to http://www.test.com It is similar to the urlwrite function of nginx, traefik2.2 Can it be realized;
What is your environment & configuration (arguments, toml, provider, platform, ...)?
apiVersion: apps/v1
kind: Deployment
metadata:
  name: portal
  namespace: testprd
  labels:
    k8s-app: portal

spec:
  replicas: 3
  revisionHistoryLimit: 3
  #滚动升级时70s后认为该pod就绪
  minReadySeconds: 70
  strategy:
    ##由于repliportal为3,则整个升级,pod个数在2-4个之间
    rollingUpdate:
      #滚动升级时会先启动1个pod
      maxSurge: 1
      #滚动升级时允许的最大Unavailable的pod个数
      maxUnavailable: 1
  selector:
    matchLabels:
      k8s-app: portal
  template:
    metadata:
      labels:
        k8s-app: portal
    spec:
      containers:
      - name: portal
        image: <IP_ADDRESS>:31000/test1024/portal:build-<BUILD_TAG>
        #env:
        #- name: portal_PROFILES_ACTIVE
        #  value: "prod"
        resources:
          # need more cpu upon initialization, therefore burstable class
          limits:
            memory: 4096Mi
            cpu:  2000m
          requests:
            cpu: 1000m
            memory:  2048Mi
        ports:
        #容器的端口
        - containerPort: 80
          name: portal
          protocol: TCP
        readinessProbe:
          tcpSocket:
            port: 80
          initialDelaySeconds: 120
          periodSeconds: 10
        livenessProbe:
          tcpSocket:
            port: 80
          initialDelaySeconds: 240
          periodSeconds: 20
        #volumeMounts:
        #- mountPath: "/download"
        #  name: data
      imagePullSecrets:
      - name: myregistrykey
      #volumes:
      #- name: data
      #  persistentVolumeClaim:
      #    claimName: download-pvc

apiVersion: v1
kind: Service
metadata:
  name: portal
  namespace: testprd
  labels:
    k8s-app: portal
spec:
  ports:
  #集群IP的端口
  - port: 80
    name: portal
    protocol: TCP
    #容器的端口
    targetPort: 80
  selector:
    k8s-app: portal

apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: redirect-https
  namespace: testprd
spec:
  redirectScheme:
    scheme: https

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: portal-https
  namespace: testprd
spec:
  entryPoints:
    - websecure
  routes:
  - match: Host(`www.test.com`,`test.com`) && PathPrefix(`/`)
    kind: Rule
    services:
    - name: portal
      port: 80
  tls:
    secretName: 1024prodportal

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: portal-http
  namespace: testprd
spec:
  entryPoints:
    - web
  routes:
  - match: Host(`www.test.com`,`test.com`) && PathPrefix(`/`)
    kind: Rule
    services:
    - name: portal
      port: 80
    middlewares:
    - name: redirect-https

# (paste your configuration here)

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
(paste your output here)

Hello @gaoyang02,
thanks for your interest in the project.
You're issue seems to be a question and / or a miss-configuration and thus, our community forum is a better place to have that discussion.
Just a hint: It can be done through the https://docs.traefik.io/middlewares/redirectregex/ middleware.
Forum: https://community.containo.us/c/traefik/traefik-v2/10


Can't enable Probe in build.gradle

I've added this to my build.gradle file; but when I try running assembleProbeDebug in the gradle logs I see that probe is disabled; when I run my code it is in fact disabled.
productFlavors {
probe {
buildVariants {
debug {
enabled true
}
}
}
}

you should add buildscript dependency like this:
buildscript {
repositories {
// mavenCentral()
// ...
}
dependencies {
// classpath 'com.android.tools.build:gradle:1.0.0'
//  ...
classpath 'org.lucasr.probe:gradle-plugin:0.1.3'
}
}


The RetryGatewayFilterFactory should regenerate body Flux

Describe the bug
Using RetryGatewayFilterFactory as a global filter, retry POST with body. The body was sent for the first request, but the body was empty if there was a retry.
Here is the retry GlobalFilter:
@Component
public class RetryGetGatewayFilter extends RetryGatewayFilterFactory implements GlobalFilter, Ordered {

    private final GatewayFilter gatewayFilter;

    public RetryGetGatewayFilter() {
        RetryConfig retryConfig = new RetryConfig();
        retryConfig.setMethods(HttpMethod.POST);
        retryConfig.setRetries(2);
        retryConfig.setSeries(
                HttpStatus.Series.SERVER_ERROR
        );
        retryConfig.setExceptions(IOException.class, TimeoutException.class,
                CallNotPermittedException.class);
        BackoffConfig backoffConfig = new BackoffConfig();
        backoffConfig.setBasedOnPreviousValue(true);
        backoffConfig.setFactor(2);
        backoffConfig.setFirstBackoff(Duration.of(100, ChronoUnit.MILLIS));
        backoffConfig.setFirstBackoff(Duration.of(500, ChronoUnit.MILLIS));
//        retryConfig.setBackoff(backoffConfig);

        gatewayFilter = this.apply(retryConfig);
    }

    @Override
    public Mono<Void> filter(ServerWebExchange exchange, GatewayFilterChain chain) {
        return gatewayFilter.filter(exchange, chain);
    }

    @Override
    public int getOrder() {
        return RouteToRequestUrlFilter.ROUTE_TO_URL_FILTER_ORDER - 1;
    }
}

I think the reason is that the body is a Flux all over the filterchain, and subscribed only when routing and sending to the downstream backends. The Body Flux is an one-time thing. Therefore, I think the retry factory should regenerate the body from the last filter when there is a retry

We have tests that work retrying a body. https://github.com/spring-cloud/spring-cloud-gateway/blob/master/spring-cloud-gateway-core/src/test/java/org/springframework/cloud/gateway/filter/factory/RetryGatewayFilterFactoryIntegrationTests.java#L115
You're doing custom code that changes things to a global filter. Not sure we want to change for that case or why it doesn't work in this case.

I figure it out that I should put this retry after AdaptCachedBodyGlobalFilter, thanks


Request to release pretrained models for training

Hi @alexandrosstergiou ,
Since I was not able to reproduce the results from the checkpoint model you have shared, I would like to train the model myself.
For that I am lacking the pretrained model used by you. It would be really helpful if you could release the same.
Thank you so much.

Closing as this was primarily related to using UCF101 subsets (which have different class indices). There was also an offline discussion by email which hopefully helped resolve the issues.
For anyone else interested, the pretrained encoders are part of the publically available models, so to drain from scratch only load the encoder weights (and not TemPr)


extend Trade and SecurityInfo types with new fields

Added 2 new fields that are presented in flex report by default.

Alexey,
from my experience - Christopher usually ask to add test cases for new fields in the same way as already done for any other.
So, I would propose you not to wait his feedback but add test cases for these 2 fields (I may assist if required)

Yeah the new fields are fine.  I'd just like to have a test case incorporating real data (sanitized of any sensitive information).  This is important for long-term maintainability of the library code.
Thanks!

@csingley @titov-vv thanks guys, totally make sense. I'd ask before adding tests if somebody can check real values for these files before, because in my reports the are both emtpy (settlementPolicyMethod="" and accruedInt="").
I assume accruedInt is safe, because it exists in other Types, but I don't have any idea what settlementPolicyMethod would be.

Well, if we simply don't have data, then it will be difficult to write good tests.  Unfortunately I don't have any myself.  Vlad I don't suppose you have anything non-NULL for these fields anywhere?
Trade.accruedInt should have decimal values for bond trades.
I guess SecurityInfo.settlementPolicyInfo should be something like T+2, T+3, etc.  Maybe?
If we can't get any data, I'll just merge the patch anyway.  The library will be improved by having these, even without proper tests.  It would just be better to have the tests, to ensure that any later changes to the parser don't break data that is currently parsed correctly.

I've checked my recent reports - there are no such fields. I expected to find settlementPolicyInfo in  but it isn't there... I may assume it is because my flex report was created some time ago and it haven't been updated with recently added fields.
Thus, nothing tangible from my side. But I'll try to create new report in spare time and notify you if I'll have something interesting there.

In the meantime, might as well merge this improvement!


this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script

We just upgraded to the last version of dehydrated (prior version was: 4.0.X). After that, when running the script I see:

[2018-03-07 11:03:01] Unknown command: this_hookscript_is_broken__dehydrated_is_working_fine__please_ignore_unknown_hooks_in_your_script

In the CHANGELOG I could find this:

Calling random hook on startup to make it clear to hook script authors that unknown hooks should just be ignored...

The function that throws this message just checks whether the HOOK variable has any content and then it shows the message. I also understand that this is done on purpose, but I just can't understand the reason?
Will it be wrong to specify a hook from now on? In our case this hook does a lot of work in terms of integration with our DNS server so it is unthinkable to remove it. If this is the wrong way to go, is there any other recommended way to do this?

Dehydrated is constantly extended with new hook calls and existing hook scripts constantly break and I get tons of bug reports that dehydrated is broken.
Hook scripts should just ignore unknown hooks, that's why this hook breaker has been implemented.
It should make it clear to hook script authors to simply please_ignore_unknown_hooks to be compatible with future dehydrated versions.
If you are using somebody else's hook script please contact them to ignore all unknown hooks. If this is your script please make sure that you ignore unknown hooks.

@nkovacne The example hook script in the repo illustrates how to whitelist particular functions in a hook script. All others will be ignored.
If you implement something like that, and whitelist only the functions implemented by your hook script, the error will go away.

@txr13 Yep, in fact it was my fault. My hook file actually caught any undefined hook and sent to stdout the error message that I wrote in my first message (which I thought was sent by the dehydrated script). I simply removed the "echo" statement and it stopped showing up. Thanks.


Don't crash the server when there's a listen error

This change is an attempt to address #577, and also seems like correct behavior for a server. Regardless of what goes wrong with any individual request, we attempt to continue to respond to subsequent requests. Previously, the use of ? was returning from the listen function scope, which shut down the server.
Extracting the inner functions was mostly for clarity and will be further refactored/extracted in future PRs
closes #577

I think we should merge this; though the more structural fix seems to be https://github.com/http-rs/tide/pull/386 by @tailhook which allows setting more fine-grained limits. Happy to merge this in the interim though!

As far as I can see this will hang single CPU with 100% usage in case ENFILE or EMFILE is encountered (depending on one's use case it may be worse than just crashing, because in case of crashing supervisor would restart the process). I've tried to explain that in the book: https://book.async.rs/patterns/accept-loop.html#handling-errors Let me know if book is not clear enough on this issue.
Sorry, for not having enough time for finishing #386

Merging this based on @yoshuawuyts' comment above, especially since this is a short-term fix for multiple reasons:

When/if async-listen is Clone (tailhook/async-listen#3), tide will be able to use that instead of this code
When tide supports multiple simultaneous listeners (a near-term goal), we'll need a totally different approach that pools open fds across multiple listeners of different types, and that will require rewriting this yet again


Modal cluster sets empty table fix

Prop to stop Table render after submit and during submission in-progress.
Signed-off-by: randybrunopiverger<EMAIL_ADDRESS>regarding: https://github.com/open-cluster-management/backlog/issues/12997
https://user-images.githubusercontent.com/21374229/132753849-6d3d124d-edf2-4a31-9c47-a4bfd5ac9f4c.mov

/cc @KevinFCormier @jamestalton

/hold
Were we going to bring back the delay so that the user sees the progress bar?
https://github.com/open-cluster-management/console/pull/674/files#diff-694c0a04c5c4105651ef6949df025774ed3413248620c5e3eedcc0a57a01ceaf

@KevinFCormier Thanks, forgot to pull that over to the new branch I made.

/unhold
/lgtm


Suggested edit to Unit Tests Walkthrough Page

This is a very clear page. One issue I have come across, and it is fairly minor, is the section starting :-
Fix your code and rerun your tests
The test result contains a message that describes the failure.
The wording suggests that a message will be displayed describing the failure, but when I tried this in VS 2019 and VS 2022, the user in fact needs to click on the red circle and white cross three times before the Error Message column shows a message.
It would be good if the documentation could be amended to say :-
The test result contains a message that describes the failure. You may need to drill down to see this message.
This would help users new to unit testing, like myself.

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

ID: b98c1d2a-1393-21d2-58c1-ff01d9aec0be
Version Independent ID: e109ff12-0172-f3ee-c10d-2e2e8a7aa699
Content: C# unit test tutorial - Visual Studio (Windows)
Content Source: docs/test/walkthrough-creating-and-running-unit-tests-for-managed-code.md
Product: visual-studio-windows
Technology: vs-ide-test
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@s52, thank you for your feedback.  I have updated the documentation and it should be live by tomorrow.


#[serde_as(as = Option<...>)] does not allow field to be missing

I'm trying to deserialize one optional field from comma-separated string:
#[serde_as]
#[derive(Deserialize, Debug)]
struct Query {
    search: Option<String>,
    #[serde_as(as = "Option<StringWithSeparator::<CommaSeparator, u32>>")]
    priority: Option<Vec<u32>>,
}

#[test]
fn test_queries() {
    let query1 = "priority=2,3";
    let q1: Result<Query, _> = serde_urlencoded::from_str(query1);
    println!("ok: {:?}", q1);
    let query2 = "search=ttt";
    let q2: Result<Query, _> = serde_urlencoded::from_str(query2);
    println!("fail: {:?}", q2);
}

But it doesn't allow that field to be missing:
ok: Ok(Query { search: None, priority: Some([2, 3]) })
fail: Err(Error { err: "missing field `priority`" })

This unfortunately a side effect of using deserialize_with. I see how I can better document the pitfall.
If you provide serde's default attribute, then it behaves as expected. It will deserialize a None in this case:
#[serde_as]
#[derive(Deserialize, Debug)]
struct Query {
    search: Option<String>,
    #[serde_as(as = "Option<StringWithSeparator::<CommaSeparator, u32>>")]
    #[serde(default)]
    priority: Option<Vec<u32>>,
}

If you do not care about the distinction between priority was provided but the list is empty and priority is missing, you can also remove the Option from priority:
#[serde_as(as = "StringWithSeparator::<CommaSeparator, u32>")]
#[serde(default, skip_serializing_if = "Vec::is_empty")]
priority: Vec<u32>,

The skip_serializing_if is only necessary if you also want to use Serialize.
I hope this helps you :)

Thanks! First solution works for me.
It would be nice if that was the default behavior (without extra attribute), if possible.

Thanks for the feedback, I will consider that as an option.


Adding Brandon as CODEOWNER

Codecov Report

Merging #182 (fac5998) into master (9bf452b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #182   +/-   ##
=======================================
  Coverage   79.24%   79.24%
=======================================
  Files          19       19
  Lines        1436     1436
=======================================
  Hits         1138     1138
  Misses        172      172
  Partials      126      126

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 9bf452b...fac5998. Read the comment docs.


Fix issue with fixture generation

Resolves #138 by ensuring that encoded data are converted to bytes before being written to a file.
TODO:

[x] tox -e py37 passes locally
[x] tox -e py27 passes locally
[x] Changes documented in docs/release.rst
[x] tox -e docs passes locally
[x] AppVeyor and Travis CI passes
[x] Test coverage to 100% (Coveralls passes)

Thanks for tackling this so quickly, @alimanfoo.


Deploy .NET 9 Project to Azure with Aspire

Output from azd version

Describe the issue
I am currently looking into the new Aspire Project that aims to make deployment to Azure easier. So far it worked great for me, but I am facing a big issue that I can't find any information about. When pushing zu Azure it automatically builds docker containers for my Applications. This would be great but since I am using the .NET 9 preview version the container just fails because it has the wrong version of .NET! Is there a way to fix this or is deploying the preview version simply not possible?

To Reproduce
This repository
i ran the following 2 command wich successfully created the resources on azure
azd init
azd up
Expected behavior
Seeing my application working on Azure
Environment
.NET 9 Preview

This would be great but since I am using the .NET 9 preview version the container just fails because it has the wrong version of .NET! Is there a way to fix this or is deploying the preview version simply not possible?

We use the standard dotnet publish command to produce the container image that is pushed to ACR.  I think there is some friction in some of these cases with pre-release builds. It's possible that the base image that is used doesn't have the correct pre-release version of .NET installed.  You can control this by setting ContainerBaseImage on your individual projects: https://learn.microsoft.com/en-us/dotnet/core/docker/publish-as-container?pivots=dotnet-8-0#containerbaseimage.
Configuring you application to publish standalone may also be a work around, since you'll burn in the runtime.

I added the <ContainterBaseImage>mcr.microsoft.com/dotnet/aspnet:9.0-preview</ContainterBaseImage> to my csproj files but noting changed

I managed to fix the issue by using <PublishSingleFile>true</PublishSingleFile>, thanks a lot for your comment to point me in the right direction. Have a great day!


Element type is invalid

I am trying to use the component search-bar https://github.com/umhan35/react-native-search-bar
I have followed the instructions and installed it correctly what I am confused about is how to use it as everything I am trying is throwing errors.
To test it I am using it on a program called testingReact which is just the starting react program.
I added the searchBar so the imports look like this.
'use strict'; import React, { AppRegistry, Component, StyleSheet, Text, View, SearchBar } from 'react-native';
Now if I run it still does not throw an error
Now I add the following code (taken straight from the example
<View>
  <SearchBar
    placeholder='Search'
    textFieldBackgroundColor='blue'
    />
</View>

When I run I get the following error "Element type is invalid : expected string(for built in components) or a class/function (for composite components) but got: undefined. Check the render method of 'testingReact'.

Sorry worked out the problem I was just installing incorrectly


fix: Brand typo, Github to GitHub

@sonyarianto Closing this one in favor of https://github.com/shadcn-ui/ui/pull/2158


Add REGION to .env

Release Note

Add REGION to .env

I'm gonna merge this and take a look at why tests are suddenly sad.


Add proposer_slashing and attester_slashing to SSE

Add proposer_slashing and attester_slashing to SSE. There's a non-zero delay between slashable messages seen on gossip, and them being included on-chain. These new events allows consumers to learn about slashable events faster than just tracking blocks, specially in the case of large amounts of slashable messages.
One relevant use-case
The total cost of a slashing event for large operators is highly dependant on their response time. If many keys are involved in an operational error it can take some time for those slashable messages to be included on chain.
There are monitoring tools available that stop your setup in response to slashable messages seen on-chain. For example https://github.com/attestantio/esd. Their response time could be minimized to zero slots by watching gossip directly.

I think it would be better and simpler to consolidate the two events into a simple one:

Event: slashed_validator
Data: {"pubkey": "0x...."}

That would be sufficient for this purpose. I don't see the point of having all the current attester and proposer slashing messages payload, plus it's more usefull for the VC to have the public keys instead of the index (let the BN do the translation) as mentioned by @rolfyone here

I would have thought it'd be less work all round if there was just a stream of pubkeys or pubkeys and indices, rather than publishing the whole event for the 1 field... This would satisfy what's been asked for, just wondering if we're ever going to use the rest of that data... It's admittedly nice to just publish standard spec events, I do see that side of things...

Right the intent of this specification was to expose this data in the most generic way possible, instead of satisfy a very specific demand. However if we are confident that the full events will always be useless, just emitting pubkeys is more succint. Validators should already have a internal cached map of index -> pubkey, plus dealing with a few extra kB of data over the wire isn't that bad.
Do you see a big downside in complexity for having to parse the full events? Sending the full event also opens the possibility for trustless verification on the validator client side

I'd be inclined to send the full spec struct, probably simpler in codebases to do this than creating a new struct with a subset of the data, and also sets us up if we ever move towards sending events as SSZ.

+1
also its better to have it as separate events

Lets add these to the change doc:)

Biggest concern we have that still needs investigating is if this would clog up our event notifier based on its current design. may be a bigger task to add if its the case.

Biggest concern we have (prysm side) that still needs investigating is if this would clog up our event notifier based on its current design. may be a bigger task to add if its the case.

if we have that many slashings that this becomes an issue, that would be a concern in itself...


Applying multiple variants to a single box

I thought I saw somewhere that I should be able to apply multiple variants to a single box by listing them like so? Currently I only get the rounded border and if I flip them I only get the cursor change.
export const Box = styled.div(
	background,
	space,
	color,
	layout,
	flexbox,
	border,
	fontSize,
	fontWeight,
	lineHeight,
	shadow,
	variant({
		variants: {
			rounded: {
				borderRadius: '10px',
			},
			clickable: {
				cursor: 'pointer',
			},
		},
	}),
);

<Box variants={['rounded', 'clickable']}>

I'm currently working around this by using custom prop variants but that will get lengthy and doing it this way seems like it would be useful and succinct.

@TerrellLinnell what would be your proposed api for something like this as currently using an array for a prop is a media query.
I feel like "rounded, clickable" would work better?

With the code above, you can render either <Box variant='rounded' /> or <Box variant='clickable' /> -- hope that makes sense

@The-Code-Monkey Oh yeah I forgot that the array pattern is for media queries, that makes sense. I hadn't thought of an api for it but the way you show would work just fine and would also be useable with the current media query api.

@TerrellLinnell I was thinking about this and I think rather than delimit by , but use && instead so it follows js conventions a bit more.
so it would be "rounded&&clickable"

@The-Code-Monkey as long as we are able to have spaces this makes sense, I was worried about readability if someone has 6 variants to apply (likely a very small use case) but if the spaces get stripped out along with the && when it gets read by styled system I dont see an issue with code readability.
"rounded && clickable && borderLarge && lorem && ipsum" looks fine to me and does follow js better so it'll be an easier syntax to remember, good idea!

Yeah that makes sense as we can just regex for && with or without spaces.

Alright, I suppose someone needs to change the label to a feature request because I cant edit it or do I need to open a new issue?

@TerrellLinnell one question how would it handle multiple variants would the second variant overwrite css keys for the first one if it was this && that

Ideally you wouldn't do that, but realistically someone will, so yes. Also possibly throw a warning about overwriting css keys? I work with @medelman17 who also had some ideas on this and shared this with me
https://github.com/system-ui/theme-ui/pull/586#issuecomment-591206221
I'm thinking this may be a  better solution and where this may actually end up.
    <Text variant="h1" modifiers={['bigger', 'bold', 'orange']}>
        Hello!
      </Text>

where the variant can be used for the brunt of the styling but then the modifiers (similar to styled-component-modifiers https://github.com/Decisiv/styled-components-modifiers) can be used to fine tune it.

<Text variant="bigger orange h1">This would be awesome</Text>

Any work on this? Multiple variants seems like a really straightforward UX use-case for a library like this.

I can take a look into this today see if I can come up with a
valid solution that will work well.
On Tue, 22 Dec 2020, 20:01 Daniel Saewitz<EMAIL_ADDRESS>wrote:

Any work on this? Multiple variants seems like a really straightforward UX
use-case for a library like this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/styled-system/styled-system/issues/1146#issuecomment-749749065,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHOFWX637627SQEJKLOJNALSWD3JZANCNFSM4KXONB5A
.

Hi, is there an update on this?
I'm trying to apply multiple variants, but I'm having a hard time figuring out how.

My use case for multiple variants is:
<Button color="primary" mode="solid" />
<Button color="primary" mode="ghost" />

The first would have a solid blue background, with white text.
The second would have a transparent background, with blue text.

Check out this on my component. https://github.com/The-Code-Monkey/TechStack/blob/dev/packages/components/src/atoms/button/styled.ts you cannot combine them within compose is the only thing I have found

This is using my version of styled system which has a few changes. Dunno if it will work in normal styled system

this is probably very messy but.. here's what I came up with to enable multiple variants.. in this case the variant props which the component takes are variant and centered

import {variant as _variant} from 'styled-system'

const APressable = styled(Pressable)<{
  variant: 'primary' | 'secondary';
  centered: boolean;
}>`
  color: white;
  padding: 10px 20px;
  min-height: 50px;

  ${({theme}: {theme: ITheme}) =>
    _variant({
      variants: {
        primary: {
          color: theme.primary,
          backgroundColor: theme.secondary,
        },
        secondary: {
          color: theme.secondary,
          backgroundColor: theme.primary,
        },
      },
    })};

  ${() =>
    _variant({
      prop: 'centered',
      variants: {
        true: {
          display: 'flex',
          alignItems: 'center',
          justifyContent: 'center',
        },
      },
    })}
`;


For optimize, allow the signal/background arguments to be lists of filenames

Is this resolved? Or did you want to pass in a file containing the list of names?


Update User Stories and Glossary sections in DG

Add in user stories and more details in the glossary section of the DeveloperGuide.md.

LGTM

LGTM

LGTM

LGTM

LGTM


Update "Timeline and milestones" status

Move from "Eth2 deposit contract launch" to "Phase 0 launch" 🚀
Add phase 1.5, consider renaming to "docking"?
Rename phase 1 to sharding?
Rename phase 2 to state execution model?

/cc @flamingYawn

closed via #308


Python call of Stub results an interpreter crash

Hi,
I used grpc in python to do my work, finding some problems. To simplify the problem, I tested on the examples of route_guide with my same usage of grpc in my project.
I created a new client which is similar to line 117-130 of route_guide_client.py. The new client is as below:
import route_guide_client as rgc
import route_guide_pb2
import time

def run(stub):
    with stub:
        rgc.guide_route_chat(stub)

if __name__ == '__main__':
    count = 0
    stub = route_guide_pb2.early_adopter_create_RouteGuide_stub('localhost', 50051)
    while True:
        count += 1
        print "run start on count:", count
        run(stub)
        time.sleep(1)

All the other codes and environment configure are as the example shows. Finally, the python interpreter which runs the above client crashes! (run in python2.7.9 virtualenv on win10 build 10074, crash is uncertain to occur, but very likely to happen)
I think the problem is the frequent run of code with stub, which actually runs stub.__enter__() and stub.__exit__() frequently, and that's the only difference between the above codes and the origin. But I think it's a normal usage. Can anybody help to check if it's a bug?

Something that makes the interpreter crash is definitely a bug.
Thank you for including your code; what does the crash look like? What gets printed?

I run the script on windows' console by using python myclient.py, there are no any prints get except for a crash notification window as below, it just tells me something is wrong but no extra messages...

python.exe has stopped working
An error occurred, causing the program to stop working normally. If there is any solution, WIndows is going to close the program and notify you.

Thanks, @yang-g, for the translation!

There seem to be no problems any more on new release 0.10.0. It should be fixed by some unkown commits. :+1:  The original test is carried on release 0.9.1.


ImportError: No module named 'tensorflow.models'

The version of TF that I installed is 1.0. I met the error when I ran run_dbn.py. Maybe there is something different in the 1.0 TF?
Traceback (most recent call last):
  File "run_dbn.py", line 5, in <module>
    from yadlt.utils import datasets, utilities
  File "/usr/local/lib/python3.5/site-packages/yadlt/utils/datasets.py", line 8, in <module>
    from tensorflow.models.rnn.ptb import reader
ImportError: No module named 'tensorflow.models'

Yes, tf 1.0 changed a lot of things, I still have to update the code to the latest tf version. I hope to do it in the following days.

It should work now.

It still doesn't work now,I get the same ErrInfo.


[FEATURE]: Vuex state-based routing

Feature Motivation
Enable the app to reactively work with the login state. If the state is loggedIn display the main application page if not display the login page.
Solution Description
Use the watch API to monitor the loggedIn state for change and route accordingly.
feature_acceptance_criteria

[x] routing based on vuex login state is implemented

Further Information
No response
Related Issues
No response

implemented in d5dae6168f39eca9ce70090e2f807ae293193302.


native-or-bluebird is deprecated. please switch to any-promise

https://github.com/kevinbeaty/any-promise
this implementation supports more promise implementations and allows the end-user to configure the promise implementation.

Released v3.1.1 with any-promise :+1: Any word when https://github.com/thenables/thenify will be updated to match?

done :)

Awesome, cheers! I have to narrow it down, but this set of changes actually broke caching of HTTP requests since it's using promises to resolve internally (no idea how, I can only assume a Promise.resolve was imploding with this mix and match).


Switch to "new Mongo.Collection(...)"

This uses the "new Mongo.Collection(...)" call when its available. Maintains backward compatibility and eliminates the following warning on newer versions of meteor:
Consider migrating from `new Meteor.Collection` to `new Mongo.Collection`

Thanks @pward123!


fix: Reduce client log levels

Signed-off-by: Nitesh Balusu<EMAIL_ADDRESS>debug!("find by prefix");
debug!("No state transitions available, waiting before re-trying");
These two logs are creating a lot of noise on the client side, lowering them to trace.

Successfully created backport PR for releases/v0.1:

#3503


horizontal's dropdown generate javascript code

Expected Behavior
horizontal's dropdown generate javascript code
Actual Behavior

when generate javascript code, console show:

Steps to Reproduce
XML:

Json:
Blockly.Blocks['light_new'] = {   init: function() {     this.jsonInit({       "id": "light_new",       "message0": "%1 %2",       "args0": [         {           "type": "field_image",           "src": Blockly.mainWorkspace.options.pathToMedia + "icons/set-led_mystery.svg",           "width": 40,           "height": 40,           "alt": ""         },         {           "type": "input_value",           "name": "CHOICE"         }       ],       "inputsInline": true,       "previousStatement": null,       "nextStatement": null,       "category": Blockly.Categories.looks,       "colour": Blockly.Colours.more.primary,       "colourSecondary": Blockly.Colours.more.secondary,       "colourTertiary": Blockly.Colours.more.tertiary     });   } };

Javascript code :

Operating System and Browser
windows 7 & chrome 56.0.2924.87

Make sure the compressed_javascript.js file is included in your website and if you are running this in node see #856

Closing this for now: we're planning to work on horizontal blocks some time next year.


update wasmtime

Update to latest version of wasmtime and fix the code that was broken by the API changes.

Note: the burrego changes are tested via the integration tests


Switch to active page for Next.js

Issue Type: Feature Request
As I am running my react/next/vue runtime, it would be great if Live Preview could sprinkle in its magic to switch to the right page in preview as I move between pages/routes.
Extension version: 0.2.6
VS Code version: Code - Insiders 1.59.0-insider (e437d424c5e6de97632f5513229c7ebc2cf27a32, 2021-07-28T05:12:37.003Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No
Remote OS version: Linux x64 5.10.25-linuxkit
Remote OS version: Linux x64 5.10.25-linuxkit

Upon reading https://nextjs.org/docs/advanced-features/custom-server, this seems possible. However, it seems that we'd need to have next.js as an npm dependency since we would need to require('next') in the server. I would rather not ship live preview with a dependency on nextjs, so I'll close the issue for now. I'm open for feedback on this, though.


Add Web Support

Changes

Added Web support with Pbxproj.parse constructor to parse the String Pbxproj content
Fixed index out of bounds error

Thank you for your contribution

Glad to help, also thank you for responding so quickly.


No ACK from the Server since 0.17.1 (End device has a RN2483)

Since the update to 0.17.1 I have a problem with the ACK from the Server. If I turn on the relax mode, the enddevice receive no ACK from the Server. If I turn off the relax mode, everthing work fine, as long as the counter is correct. The enddevice has a RN2483 as LoRa modem. The distance between the gateway and the end device is around 4km. We work with the ABP mode.
The whole system was working with the older Loraserver version.
Has anybody an enddevice with RN 2483 and 0.17.1 installed?
I have no idea how I can debug the issue.
Thanks for your help.

Additional Info: I have no problem if I send a short payload (~4byte) But if the payload is around 30byte, I receive no ACK from the server. It works only for 3-7 payload.

What happens is that your node is probably sending a retransmit sometimes. The first uplink that was received by LoRa Server was processed and the counter was incremented at the side of LoRa Server. However, the ACK was not received by the node. Because of this, the node performed a re-transmit.
As LoRa Server notices that the counters are out-of-sync it will reset both the uplink and downlink counters on the server (as the counter mismatch could be because of a node-reset). However, the counter mismatch was not due to a node reset but because of packet-loss. Note that this only happens with the relax frame-counter mode turned on.
I’ll change the behaviour so that the uplink counter gets a reset (sync with what was received), but that it will not reset the downlink counter. Again please note that the relax frame-counter does not offer any security and that it is very likely that you are going to receive duplicated frames, as LoRa Server will not filter out the re-transmits!


Awesome updates :)

As a user I want to see list of awesome project updates (which has been selected by Admin) with a related project card in the admin page.
Related to : https://github.com/Giveth/giveth-dapps-v2/issues/1996

@CarlosQ96  Can you take this?
I think @MohammadPCh  has comments on it

ill take it!

Thanks, @mohammadranjbarz
Yes, this is how I build that section:

get N projects that have been updated/added their featured updates without that featured Update.
create the page.
when the user scrolls to that part of the page I fetch the featured update of that project and show it to the user.
so I want 2 queries:
fetch the latest projects with featured updates.
get a project's featured update by project id.
Thanks @CarlosQ96

I started on this, talked to Cherik on how will be implemented. Working on a issue in adminbro I have but I will push it today for Cherik to start testing it.

UX isnt that great for selecting the project update in the Adminbro but will push it for review

The awesome updates isn't shown on this branch https://giveth-dapps-v2-git-add-awsome-projects-update-givethio.vercel.app/
and the latest update is not work correctly and my last update is not shown in list

@maryjaf Thanks for reporting. we don't show the updates since they haven't the position and the backend doesn't return them to front-end, I fixed them and added the position and now you can see them.
and about the latest updates did you stay for 10 minutes?

Thanks @mohammadranjbarz @MohammadPCh , Now the awesome updates are shown on stg based on  their's position on admin bro
But when I add a update on project update list from admin bro as featured update, it is'n shown in  featured update list on admin, plz check this

@maryjaf thats because the update was a default Update (all projects have an empty update)
You have to filter by isMain = false (No)
To get the non-default updates, you can add those.
Also there is a restriction you cannot add twice the same project as featured.
So make sure its not an update from the same one and its not the isMain=true update.

@maryjaf Thanks for reporting. we don't show the updates since they haven't the position and the backend doesn't return them to front-end, I fixed them and added the position and now you can see them. and about the latest updates did you stay for 10 minutes?

and about the latest updates did you stay for 10 minutes?

the latest update also shown in stg but we have 3 problem related that @MohammadPCh
1- the updates of  deactivate or unlisted project is shown
2- the color for projects is dark Blue even if the cover set for the project is a different color
3- if I edited my project update this isn't shown in latest update

@maryjaf thats because the update was a default Update (all projects have an empty update) You have to filter by isMain = false (No) To get the non-default updates, you can add those. Also there is a restriction you cannot add twice the same project as featured. So make sure its not an update from the same one and its not the isMain=true update.

Thanks @CarlosQ96 I'll check it

@maryjaf thats because the update was a default Update (all projects have an empty update) You have to filter by isMain = false (No) To get the non-default updates, you can add those. Also there is a restriction you cannot add twice the same project as featured. So make sure its not an update from the same one and its not the isMain=true update.

Yeah, that's right
Thanks @CarlosQ96 Now we don't have any problems with the awesome updates and it's ok
Just one question, if I click "see more " on an update as a project owner, I see the update page as below

isn't it better to scroll and display the section related to this update? @MoeNick @MohammadPCh
according to the picture

@maryjaf Latest update issue: https://github.com/Giveth/giveth-dapps-v2/issues/2053

@maryjaf Thanks for reporting. we don't show the updates since they haven't the position and the backend doesn't return them to front-end, I fixed them and added the position and now you can see them. and about the latest updates did you stay for 10 minutes?

and about the latest updates did you stay for 10 minutes?

The latest update also shown in stg but we have 3 problem related that Do we have a separate issue for latest update or should I register? To raise these problem there @MohammadPCh 1- the updates of deactivate or unlisted project is shown 2- the color for projects is dark Blue even if the cover set for the project is a different color 3- if I edited my project update this isn't shown in latest update

@mohammadranjbarz Plz check 1 & 3 ,seems these related to backend

@maryjaf Thanks for reporting. we don't show the updates since they haven't the position and the backend doesn't return them to front-end, I fixed them and added the position and now you can see them. and about the latest updates did you stay for 10 minutes?

and about the latest updates did you stay for 10 minutes?

The latest update also shown in stg but we have 3 problem related that
Do we have a separate issue for latest update or should I register? To raise these problem there @MohammadPCh
1- the updates of  deactivate or unlisted project is shown
2- the color for projects is dark Blue even if the cover set for the project is a different color

@CarlosQ96 Plz check # 1 ,seems these related to backend

@aminlatifi fixed it, it's deploying on Staging now


add index for the deleted_at columns

Ref: https://issues.redhat.com/browse/ACM-6441

/test test-unit

/lgtm


Evidence playbook update

Evidence playbook update for tendrl, gluster and ceph.

@ltrilety is this ready? If yes, I'm going to review it and merge it.

@ltrilety is this ready? If yes, I'm going to review it and merge it.
It should be. I used that once already.


Problem with password reset flow

Bug report

[ ] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
I am trying to set up password reset flow in Next13 with app router. I get the following error in my Vercel logs:
[AuthApiError]: invalid request: both auth code and code verifier should be non-empty

To Reproduce

User enters their email and triggers the flow using:

export const authRouter = router({
    sendPwdResetEmail: publicProcedure
        .input(z.string().email())
        .mutation(async ({ input }) => {
            const sp = spServerClient();
            const { error } = await sp.auth.resetPasswordForEmail(
                input,
                {redirectTo: 'http://my-domain.io/api/auth/callback'}
            );
            if (error) throw Error(error.message);
        }),
    resetPwd: publicProcedure
        .input(z.string().min(8).max(25))
        .mutation(async ({ input }) => {
            const sp = spServerClient();
            const { error } = await sp.auth.updateUser({password: input});
            if (error) throw Error(error.message);
        }),
});

User receives an email where they click on the button. They are redirected to the following callback url (api). This comes directly from the Supabase+Next13 template

export async function GET(request: NextRequest) {
  const requestUrl = new URL(request.url)
  const code = requestUrl.searchParams.get('code')
  if (code) {
    const supabase = createRouteHandlerClient({ cookies })
    await supabase.auth.exchangeCodeForSession(code)
  }
  return NextResponse.redirect(`${requestUrl.origin}/reset-password`)
}

Browser shows an error that it has been redirected too many times and the vercel logs say the error I mentioned above.
If I click on the button in the email again, it takes me to the reset password url but the url has some search params that mention that the auth code has expired or is invalid.

Expected behavior
I expect the callback url to redirect the user to the password reset page.
System information

OS: macOS
Browser: Arc (Chromium)
Version of supabase-js: latest

Additional context
If I am doing anything wrong or if you require more info, please let me know.

This is an ongoing issue but they seem to just move on here is another thread that was closed. https://github.com/supabase/auth-helpers/issues/545
I have been scratching my head for days. following the guide provided in that thread creates the session correctly in the confirm/route.ts but once the next redirect happens it has no session sounds like there are a few open bugs about it.


Allow usage of pc

Allow usage of pc instead of only parsec, so to be consistent with Gpc/Mpc/kpc

seems ok to me..


Bump version 3.8.0

Coverage decreased (-0.6%) to 90.761% when pulling e7af210b1a4979a63aed5d263f1a76eea2003cb8 on bump-version into 44e2c65bb2030a0d1b57775dfe8182bb24aba2ff on master.


Context-specific Metabase Lab Training

To avoid downloading Metabase data in spreadsheets, training needs to be provided to show users how to create dashboards and use Metabase according to their specific use cases/needs.
First we will need to find out what they are downloading and what they are using it for. Then we can tailor training to show them how to do those tasks within Metabase.
There needs to be emphases on data security from an authority. Since permissions are setup in Metabase, those go out the window when tables are downloaded and saved on a LAN for example (anyone with that access can then see the data). We need a data custodian to be present to share the need to put data privacy FIRST and use Metabase as it was intended.
AC Related to setting up Metabase for training:

[x] Set up team meeting to discuss approach
[x] Reach out to Hanna and John and Matt in discussion to determine what is of most value to their teams in terms of training
[x] Create training objectives on Miro board
[x] Setup metabase data....
[x] Start new Miro board for the lab

Notes:

UX/Service Design support on creative miro board design
Additional tickets may stem from this one

Last item to do: take in account the feedback from the trial run with the team and update the miro board with that information

Great work to everyone who designed the training! I'm looking forward to when we can deliver the training to staff :)


Signature of enter is not sound

Neat, another self-referencing structs crate I hadn’t known of before (but now I do because of your recent-ish blog post). :tada:
You might have seen me before on the issue trackers of many other self-referencing structs crates.

Anyways, here’s the issue: The signature of enter says
G: for<'a> FnOnce(&'a mut <T as Family<'a>>::Family) -> Output,

which features a &'a mut Foo<'a>-style type, an infamous anti-pattern in Rust generally. These types are almost impossible to produce in safe code since they promise that Foo<'a> is borrowed mutably for its entire existence, essentially. So unsafe code producing them results in unsoundness really easily, more on that below.
The full signature in question is
pub fn enter<'borrow, Output: 'borrow, G>(&'borrow mut self, f: G) -> Output
where
    G: for<'a> FnOnce(&'a mut <T as Family<'a>>::Family) -> Output,

If you want to follow the precedent of ouroboros or self_cell, e.g. documented here:[^1]
fn with_dependent_mut<'outer_fn, Ret>(
   &'outer_fn mut self,
   func: impl for<'a> ::core::ops::FnOnce(&'a $Owner, &'outer_fn mut $Dependent<'a>) -> Ret
) -> Ret

then your correct signature must be the following instead:
pub fn enter<'borrow, Output: 'borrow, G>(&'borrow mut self, f: G) -> Output
where
    G: for<'a> FnOnce(&'borrow mut <T as Family<'a>>::Family) -> Output,
//                     ^^^^^^^

also, Output: 'borrow is unnecessarily restrictive, as far as I can tell, so you could consider
pub fn enter<'borrow, Output, G>(&'borrow mut self, f: G) -> Output
where
    G: for<'a> FnOnce(&'borrow mut <T as Family<'a>>::Family) -> Output,

[^1]: for comparison, yoke has a bit of a weird, different signature, that also appeared sound last time I looked at it, but I should consider opening an issue there, too, because the ouroboros/self_cell one is just a lot better (less restrictive) for the user.

So how is this unsound? Two ways, really. For one, producing &'a mut Foo<'a> at all is impossible to do soundly if Foo is a custom type that does implement Drop. On the other hand, for types without drop glue, producing more than one &'a mut Foo<'a> reference to the same target ever is also unsound. (This explains the Drop situation, too, as Drop receives &mut Self.)
Exploiting this is as easy as storing the &'a mut Foo<'a> (or some projection of it) inside of Foo<'a> itself:
use nolife::{BoxScope, Family, TimeCapsule};

struct Foo<'a> {
   s: String,
   r: Option<&'a mut String>,
}

struct FooFamily;

impl<'a> Family<'a> for FooFamily {
   type Family = Foo<'a>;
}

fn main() {
   {
       let mut scope = BoxScope::new(|mut time_capsule: TimeCapsule<FooFamily>| async move {
           let mut f = Foo {
               s: String::from("Hello World!"),
               r: None,
           };
           time_capsule.freeze_forever(&mut f).await
       });

       scope.enter(|foo| {
           foo.r = Some(&mut foo.s);
       });
       scope.enter(|foo| {
           let alias1: &mut String = &mut foo.s;
           let alias2: &mut String = foo.r.as_deref_mut().unwrap(); // miri will complain here already
           // two aliasing mutable references!!

           let s: &str = alias1;
           let owner: String = std::mem::take(alias2);

           println!("Now it exists: {s}");
           drop(owner);
           println!("Now it's gone: {s}");
       })
   }
}

example output
Now it exists: Hello World!
Now it's gone: b%�E[

miri output
error: Undefined Behavior: trying to retag from <2342> for Unique permission at alloc763[0x10], but that tag does not exist in the borrow stack for this location
   --> /home/frank/.rustup/toolchains/nightly-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/deref.rs:274:9
    |
274 |         *self
    |         ^^^^^
    |         |
    |         trying to retag from <2342> for Unique permission at alloc763[0x10], but that tag does not exist in the borrow stack for this location
    |         this error occurs as part of retag at alloc763[0x10..0x28]
    |
    = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
    = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
help: <2342> was created by a Unique retag at offsets [0x10..0x28]
   --> src/main.rs:25:21
    |
25  |             foo.r = Some(&mut foo.s);
    |                     ^^^^^^^^^^^^^^^^
help: <2342> was later invalidated at offsets [0x10..0x30] by a Unique function-entry retag inside this call
   --> src/main.rs:21:49
    |
21  |             time_capsule.freeze_forever(&mut f).await
    |                                                 ^^^^^
    = note: BACKTRACE (of the first span):
    = note: inside `<&mut std::string::String as std::ops::DerefMut>::deref_mut` at /home/frank/.rustup/toolchains/nightly-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ops/deref.rs:274:9: 274:14
    = note: inside `std::option::Option::<&mut std::string::String>::as_deref_mut` at /home/frank/.rustup/toolchains/nightly-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/option.rs:1288:29: 1288:42
note: inside closure
   --> src/main.rs:29:39
    |
29  |             let alias2: &mut String = foo.r.as_deref_mut().unwrap();
    |                                       ^^^^^^^^^^^^^^^^^^^^
    = note: inside `nolife::scope::Scope::<FooFamily, {async block@src/main.rs:16:82: 22:10}>::enter::<'_, (), {closure@src/main.rs:27:21: 27:26}>` at /home/frank/.cargo/registry/src/index.crates.io-6f17d22bba15001f/nolife-0.3.3/src/scope.rs:166:22: 166:30
    = note: inside `nolife::BoxScope::<FooFamily, {async block@src/main.rs:16:82: 22:10}>::enter::<'_, (), {closure@src/main.rs:27:21: 27:26}>` at /home/frank/.cargo/registry/src/index.crates.io-6f17d22bba15001f/nolife-0.3.3/src/box_scope.rs:117:18: 117:41
note: inside `main`
   --> src/main.rs:27:9
    |
27  | /         scope.enter(|foo| {
28  | |             let alias1: &mut String = &mut foo.s;
29  | |             let alias2: &mut String = foo.r.as_deref_mut().unwrap();
30  | |             // two aliasing mutable references!!
...   |
37  | |             println!("Now it's gone: {s}");
38  | |         })
    | |__________^

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

error: aborting due to 1 previous error

As far as I can tell, this soundness issue is present in all existing versions of nolife.

Thank you, I opened #9 to apply the suggested enter signature.

also, Output: 'borrow is unnecessarily restrictive, as far as I can tell, so you could consider

I can't remember off the top of my head why I added the restriction. I spent a lot of time fiddling the signature of enter, so I'm not too keen on relinquishing the restriction without giving it more thoughts.
I'll keep the suggestion on my TODO to reevaluate someday where my head is fresher.

I can't remember off the top of my head why I added the restriction. I spent a lot of time fiddling the signature of enter, so I'm not too keen on relinquishing the restriction without giving it more thoughts.

Possibly the thought process was that Output: 'borrow would prevent the FnOnce here to return anything that involves the lifetime 'a. However, this is already sufficiently prevented by the mere fact that it’s a HRTB, and Output is a single type that’s the same for all choices of 'a.
AFAICT, the only thing that Output: 'borrow now prevents is that Output contains any lifetimes from stuff that the FnOnce captured; unless such lifetimes are longer than (or equal to) 'borrow. Which is often not a problem, in case you don’t want to keep 'borrow all that long. But I suppose, this could prevent niche – but sound – use-cases where it’d return … say … Result<&'borrow Foo, &'x Bar>, where the &'x Bar is some captured reference, and then in the Ok case, you’d keep the &'borrow Foo around for longer while already dropping the Bar early.
Also… I’m just realizing that even with Output = (), you can “simulate” output by capturing a &mut Option<Output> in the closure, and populating it inside. This approach results in no limitation of Output either. Which is quite a strong argument against keeping Output: 'borrow: because it’s trivial to write a wrapper that lifts this bound, anyways. (Feel free to double-check whether or not one really can wrap the API like this, of if I’m missing something.)

Alright that's pretty convincing, I might consider doing this soon :-).
If that's OK with you, I'm adding you as a co-author of the commits in #9. Given I applied your suggested fix this looks only fair to me.
I'll do the same once I'm done ironing out the quirks of #11.

If that's OK with you, I'm adding you as a co-author of the commits in #9. Given I applied your suggested fix this seems only fair to me.

Sure, that's okay ^^


refactor(saas): Improved Promotion Section

Description
I didn't really like the promotion section on the homepage, with the strong contrast between backgrounds. Therefore I refactored this section to make it look better...
If you don't like it just close it :)
Changes

fixed padding on footer on desktop
updated promotion section

Images

@alifarooq9 You should probably still fix the footer... I did that in the first commit

Okay, I will do it. Thanks!


Document version mismatch error when saving any modified notebook

Applies To

[x] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

Disable auto-save
Create a new notebook
Add a cell
Save the notebook
:bug: Document version mismatch

VS Code Version
1.94.0-insider
Jupyter Extension Version
2024.9.2024092401
Jupyter logs
No response
Coding Language and Runtime Version
N/A
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

This should be fixed in next Insiders.

seems fixed now


Didn't install...

martincleaver@MartinCleaversMBP-2.local:~/SoftwareDevelopment 18:42:14 499$ git clone git@github.com:andreaskoch/dee-cli.git && cd dee-cli
Cloning into 'dee-cli'...
remote: Counting objects: 374, done.
remote: Total 374 (delta 0), reused 0 (delta 0), pack-reused 373
Receiving objects: 100% (374/374), 376.58 KiB | 333.00 KiB/s, done.
Resolving deltas: 100% (149/149), done.
Checking connectivity... done.
martincleaver@MartinCleaversMBP-2.local:~/SoftwareDevelopment/dee-cli 18:42:21 500$ go run make.go -install
actioncreate.go:11:2: cannot find package "github.com/andreaskoch/dee-ns" in any of:
/usr/local/go/src/github.com/andreaskoch/dee-ns (from $GOROOT)
($GOPATH not set)
cli.go:11:2: cannot find package "github.com/mitchellh/go-homedir" in any of:
/usr/local/go/src/github.com/mitchellh/go-homedir (from $GOROOT)
($GOPATH not set)
actionlist.go:12:2: cannot find package "github.com/pearkes/dnsimple" in any of:
/usr/local/go/src/github.com/pearkes/dnsimple (from $GOROOT)
($GOPATH not set)
cli.go:12:2: cannot find package "github.com/spf13/afero" in any of:
/usr/local/go/src/github.com/spf13/afero (from $GOROOT)
($GOPATH not set)
Error running go install --ldflags=-X main.GitInfo=v0.7.0-2016-05-23-af8087e: exit status 1exit status 1
I'm new to Go...
Thx. M.

Thanks for pointing that out. The installation instructions did not work.
The easiest way to install dee-cli is using go get:
go get -u github.com/andreaskoch/dee-cli

Please let me know if this resolves your problem.


Upgrade to solana 1.16.2

I think this change is relevant -- https://github.com/solana-labs/solana-program-library/pull/4703
I'm not sure if sticking with particular version of hashbrown is better than adding getrandom or not. If this getrandom custom doesn't break anything, than I would argue that sooner or later we will have to upgrage hashbrown and, hence, getrandom. Maybe there is something else I'm not aware of


tslint support in add-missing-lint/fix-script

Support tslint projects in add-missing-lint/fix-script update tasks.

yarn-recursive is a suitable test project for this work.


ARROW-9090: [C++] Bump versions of bundled libraries

@github-actions crossbow submit -g linux

(I'm waiting for s390x CI that detects OpenSSL link error.)

I don't know what is happening with the s390x build. I downloaded the libssl1.1_1.1.1f-1ubuntu2_s390x.deb package locally and checked that d2i_SSL_SESSION is indeed exposed by /usr/lib/s390x-linux-gnu/libssl.so.

The command line that causes this link error has the following arguments in this order:

...
/usr/lib/s390x-linux-gnu/libssl.so
...
/usr/lib/s390x-linux-gnu/libssl.so
...
grpc_ep-install/lib/libgrpc++.a
....
/usr/lib/s390x-linux-gnu/libssl.so
...
/usr/lib/s390x-linux-gnu/libssl.so
...
grpc_ep-install/lib/libgrpc.a
...

It seems that we need libssl.so after libgrpc.a because libgrpc.a uses d2i_SSL_SESSION:
$ nm grpc_ep-install/lib/libgrpc.a | grep d2i_SSL_SESSION
                 U d2i_SSL_SESSION

@kou @pitrou seems like it has affected the osx wheels, there are symbol collisions between grpc and openssl https://travis-ci.org/github/ursa-labs/crossbow/builds/697504702#L7247

Oh, sorry. I'll fix it.


Labels in the help card and the person card have wrapText set to true

Codecov Report

Merging #73 (7b12ea3) into master (95ca74a) will increase coverage by 0.13%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #73      +/-   ##
============================================
+ Coverage     71.70%   71.83%   +0.13%
- Complexity      473      474       +1
============================================
  Files            80       80
  Lines          1495     1495
  Branches        159      159
============================================
+ Hits           1072     1074       +2
  Misses          375      375
+ Partials         48       46       -2

Impacted Files
Coverage Δ
Complexity Δ

...main/java/seedu/address/commons/core/Messages.java
66.66% <0.00%> (ø)
1.00% <0.00%> (ø%)

...java/seedu/address/logic/commands/EditCommand.java
97.59% <0.00%> (+1.20%)
12.00% <0.00%> (ø%)

.../java/seedu/address/model/person/DeliveryDate.java
86.36% <0.00%> (+4.54%)
10.00% <0.00%> (+1.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 95ca74a...7b12ea3. Read the comment docs.


amplify import auth does not add an OAuth entry to the amplifyconfiguration.json

Describe the bug
When going through the process using amplify import auth to import an existing Cognito pool, the section OAuth with the WebDomain is missing and  Amplify.Auth.signInWithWebUI fails (because WebDomain is nil).
Steps To Reproduce
Steps to reproduce the behavior:

use amplify import auth to import an existing Cognito pool to Amplify
look at the amplifyconfiguration.json:

{
    "UserAgent": "aws-amplify-cli/2.0",
    "Version": "1.0",
    "auth": {
        "plugins": {
            "awsCognitoAuthPlugin": {
                "UserAgent": "aws-amplify/cli",
                "Version": "0.1.0",
                "IdentityManager": {
                    "Default": {}
                },
                "CredentialsProvider": {
                    "CognitoIdentity": {
                        "Default": {
                            "PoolId": "***",
                            "Region": "***"
                        }
                    }
                },
                "CognitoUserPool": {
                    "Default": {
                        "PoolId": "***",
                        "AppClientId": "***",
                        "Region": "***"
                    }
                },
                "Auth": {
                    "Default": {
                        "authenticationFlowType": "USER_SRP_AUTH"
                    }
                }
            }
        }
    }

Expected behavior
According to https://github.com/aws-amplify/amplify-ios/issues/1058#issuecomment-776105649 it should look like this:
{
    "UserAgent": "aws-amplify-cli/2.0",
    "Version": "1.0",
    "auth": {
        "plugins": {
            "awsCognitoAuthPlugin": {
                "UserAgent": "aws-amplify/cli",
                "Version": "0.1.0",
                "IdentityManager": {
                    "Default": {}
                },
                "CredentialsProvider": {
                    "CognitoIdentity": {
                        "Default": {
                            "PoolId": "xxx",
                            "Region": "xxx"
                        }
                    }
                },
                "CognitoUserPool": {
                    "Default": {
                        "PoolId": "xxx",
                        "AppClientId": "xxx",
                        "AppClientSecret": "xxx",
                        "Region": "xxx"
                    }
                },
                "Auth": {
                    "Default": {
                        "OAuth": {
                            "WebDomain": "xxxx.amazoncognito.com",
                            "AppClientId": "xxx",
                            "AppClientSecret": "xxx",
                            "SignInRedirectURI": "xxx",
                            "SignOutRedirectURI": "xxx",
                            "Scopes": [
                                "phone",
                                "email",
                                "openid",
                                "profile",
                                "aws.cognito.signin.user.admin"
                            ]
                        },
                        "authenticationFlowType": "USER_SRP_AUTH"
                    }
                }
            }
        }
    }
}

Amplify Framework Version
1.13.3
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5
CLI version
5.3.0
Xcode version
13.0
Relevant log output
No response
Is this a regression? (i.e. was this working before a version upgrade)
No response
Device
iPhone 12
iOS Version
iOS 14.1
Specific to simulators
No response
Additional context
No response

I managed to get a UI to show by manually filling all the missing values above, but it took me while to figure out the correct values.
(Also sorry for the above bad formatting, I had posted this during a GitHub service outage so I couldn't edit it anymore)

good to hear you were able to get the UI to show, for reference there's https://docs.amplify.aws/lib/auth/existing-resources/q/platform/ios
I'm not aware of the questions that amplify import auth will ask, but i think if it asked for something and you had provided some values, but it was not translated over to the configuration then there is an issue.

Could you open an issue over there if there is an issue in the amplify import auth workflow? https://github.com/aws-amplify/amplify-cli/issues I don't have access to transfer this one

Mhmm, I don't think the command line ever asked me to put any web-domainr elated info in, thats why I was wondering/
I can run amplify remove auth and import it again tomorrow.
I also created a ticket over in the amplify-cli issues under https://github.com/aws-amplify/amplify-cli/issues/7947

@Bersaelor I'm closing this in favor of https://github.com/aws-amplify/amplify-cli/issues/7947, but feel free to reopen if you need more help.