Can't select note type

I keep receiving this error after selecting a note type.
Error
An error occurred. Please start Anki while holding down the shift key, which will temporarily disable the add-ons you have installed.
If the issue only occurs when add-ons are enabled, please use the Tools>Add-ons menu item to disable some add-ons and restart Anki, repeat until you discover the add-on that is causing the problem.
When you've discovered the add-on that is causing the problem, please report the issue on the add-ons section of our support site.
Debug info:
Anki 2.1.35 (84dcaa86) Python 3.8.0 Qt 5.14.2 PyQt 5.14.2
Platform: Windows 10
Flags: frz=True ao=True sv=1
Add-ons, last update check: 2020-10-20 21:51:52
Caught exception:
Traceback (most recent call last):
File "C:\Users\Necip\AppData\Roaming\Anki2\addons21\Memrise2Anki\importer.py", line 877, in importCourse
model = self.modelMapper.getModel(thing, deck)
File "C:\Users\Necip\AppData\Roaming\Anki2\addons21\Memrise2Anki\importer.py", line 386, in getModel
self.models[thing.pool.id] = self.__loadModel(thing, deck)
File "C:\Users\Necip\AppData\Roaming\Anki2\addons21\Memrise2Anki\importer.py", line 370, in __loadModel
self.col.models.add(model)
File "anki\models.py", line 220, in add
File "anki\models.py", line 87, in save
File "anki\models.py", line 231, in update
File "anki\rsbackend_gen.py", line 414, in add_or_update_notetype
File "anki\rsbackend.py", line 267, in _run_command
anki.rsbackend.InvalidInput: InvalidInput { info: "1 template required" }
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\Necip\AppData\Roaming\Anki2\addons21\Memrise2Anki\importer.py", line 943, in importCourse
raise exc_info0.with_traceback(exc_info[2])
File "C:\Users\Necip\AppData\Roaming\Anki2\addons21\Memrise2Anki\importer.py", line 877, in importCourse
model = self.modelMapper.getModel(thing, deck)
File "C:\Users\Necip\AppData\Roaming\Anki2\addons21\Memrise2Anki\importer.py", line 386, in getModel
self.models[thing.pool.id] = self.__loadModel(thing, deck)
File "C:\Users\Necip\AppData\Roaming\Anki2\addons21\Memrise2Anki\importer.py", line 370, in __loadModel
self.col.models.add(model)
File "anki\models.py", line 220, in add
File "anki\models.py", line 87, in save
File "anki\models.py", line 231, in update
File "anki\rsbackend_gen.py", line 414, in add_or_update_notetype
File "anki\rsbackend.py", line 267, in _run_command
anki.rsbackend.InvalidInput:

I can't reproduce this error. Could you give some more details what exactly you are doing?

I click on import memrise course select create new deck then put the URL of Japanese no script 2 and click ok. Once it has done downloading I selected new note type and it crashed. However I tried again but selected the basic note type and it worked fine.

Could you post the course url?

https://app.memrise.com/course/5503974/japanese-2-no-script/

Okay, thank you. I tried to fix that already (#84), but it's a difficult one. Obviously there is an inconsitency in the data. I have a fix ready and will post a new release soon.


update(owners): trigger group update automation

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind cleanup

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area docs
What this PR does / why we need it:
As per title. Groups should now be automatically updated via test-infra automation.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

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

LGTM label has been added.  Git tree hash: 672886e2f87053d5595978b1bf9af69a57c22d77

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,LucaGuerra]

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


passwords hashes are utf-8 not ascii

according to API:

Each password is stored as a SHA-1 hash of a UTF-8 encoded password..

    sha1pwd = hashlib.sha1(pwd.encode('utf-8')).hexdigest().upper()

Thanks for the PR on this one - it was an oversight on my part!


Wasm VM failed Wasm module is missing malloc function

Describe the bug / error
2022-03-01T07:12:52.851833Z     error   envoy wasm      Wasm VM failed Wasm module is missing malloc function.
2022-03-01T07:12:52.851878Z     error   envoy wasm      Wasm VM failed Failed to initialize Wasm code
What is your Envoy/Istio version?
1.7.8
What is the SDK version?
wasm-go-sdk
What is your TinyGo version?
URL or snippet of your code including Envoy configuration
Additional context (Optional)

Version is unspecified here and Envoy 1.7.8 ha already reached EOL. Closing.


datepicker does not open

Hello,
I do not want all the directives, so I used "create your own build" to download only datepicker Say ui-bootstrap-datepicker-tpls-0.10.0.min.js. Have been using this directive and everything worked fine.
Recently, I wanted to use progress bar also and hence downloaded respective directive, say ui-bootstrap-progressbar-tpls-0.10.0.min.js. When I included this js file also, datepicker is not shown when clicked on a button. But when I remove progress bar js file, I see datepicker working fine.
I don't understand the relation. Can you please help?

Closing as resolved by support, let us know if this is still an issue.


v3api: detach lease from a key

Is there a way to dissociate a key from its lease without removing it? My use-case is to save temporary data (with a lease) and keep it (i.e. detach the lease) when needed.

Yes. Update the key without empty lease ID.

So with the Go client, that would be done with a Put with the key and its value, without passing a lease ID?
Letting a client remove a lease from a key without sending its value again could be a valuable feature.

@louis-paul Sounds a reasonable feature to add. /cc @heyitsanthony

It's been requested before. Fix would probably be something like a PreserveValue bool in the Put RPC


Switch to using pants in CI

there are still issues w/ the secret for PR builds.
this might need to land first before those can be resolved, at any case, not having a token just means no remote cache or buildsense access and it doesn't actually break the build.

@tdyas fyi


Want to add some html project in your repo

#HACKTOBERFEST2022

yes, add.
Star this repo : https://github.com/DeepanshuGoel1122/CodeEasy
https://github.com/DeepanshuGoel1122 follow, let's build connection strong

please assign this issue to me


[Pages]Custom blocks and Pre-built blocks

Add a custom block option, as well as a few pre-built options

Transitioned to Jira


Add a /ness command with info

Closed in https://github.com/violetwtf/Necessities/commit/23705c5866730f7426324ca3a6c3dd7cd07bb7ba


Is it possible to use the Media (Omnimount) as a functional external storage in NextCloud?

Hi All!
While setting up NextCloud, from the Omni Components, I was able to connect the Media (the Omnimount mount point) as an external storage location. After some time I can see the contents without issue, but I am unable to create files/folders within "Media". NextCloud gives the "Could Note Create Folder.." message. I realize this may be a NextCloud issue, but I wanted to check here first as there are so many "moving pieces" and Omnimount being a developed implementation by @kelinger.
Thanks again for all of the assistance and friendly patience!

@Misterobots - Thank you for trying out OmniStream!  I'm not currently running NextCloud but have run it in the past.  Give me a bit to get it setup again so I can test.
I do remember, though, that getting it to share my Google drive (mounted locally, of course) took a bit of playing around the last time I used NextCloud.  While I'm preparing a test environment, can you confirm that you are mapping the "target" of OmniMount (essentially, the locally cached read-write directory) and not the raw cloud directory?

@kelinger Thanks so much for the assistance! The "target" would be whatever ${MEDIA} is, correct? If that's not the case? Could you point me in the correct direction? I very much appreciate the help.

@Misterobots - The problem is that OmniMount is using a "umask" setting of 002 which makes the mount read/write for the Docker container's main user but other users in the container only have read permission.  NextCloud runs as root, but the web service (www-data) is actually creating/accessing the files.
I changed this and posted a new OmniMount that allows read-write from anywhere.  This really isn't that much of a security hole because it's the basic idea of this project.  I've also tested it and verified that this works.  Just run either omni update or omni down followed by omni up to get the updates and restart your containers.
[ you can end reading here but I'm also putting the setup instructions for NextCloud below for you or anyone else who wants to see how to get a quick NextCloud instance running ]
The assumption is that everything is set up using the defaults.  (@TechPerplexed - possible documentation item since this is a bit beyond the "normal" turnkey setup of most other containers)
To install, I enabled 403-nextcloud.yaml, 422-mariadb.yaml, and 425-redis.yaml
o+ 403-nextcloud.yaml 422-mariadb.yaml 425-redis.yaml
Bring up OmniStream
omni up
I waited a minute for the housekeeping and then I went to https://nextcloud.mydomain.com.
I created an admin account in NextCloud and used the default MariaDB credentials (root / secret123; servername = "mariadb")
Once the system was set up and I was logged in, I went to the profile menu (user icon at the top right) and chose the "+Apps" menu.  There, I added and then enabled "external storage."
I now have a menu item under "administration" on the left called "External Storage."  After clicking that, I'm taken to--go figure--the setup for external storage.
I created a share called "Cloud" with the following settings, left to right:

Folder name = Cloud
External storage = Local
Authentication = None
Configuration = /cloud
Available for = All users

Then I clicked the checkmark on the right to apply it.
I now have my entire cloud mount available, read and write, via the NextCloud file browser.  Since I created this under the admin section, this should now be available for any users on my system.

EUREKA! Read/Write is working successfully after update! Thank you so much @kelinger! Loving OmniStream more and more, especially with the fantastic support!

Glad to hear it!  Let us know if you run into any other issues.


ofnative: support for goto_table instruction

run skydive-functional-hw-tests
run skydive-functional-tests-backend-elasticsearch
run skydive-functional-tests-backend-orientdb
run skydive-k8s-tests


Autogluon Import Error: cannot import name 'IPV6_ADDRZ_RE'

Hi,
Issue Description: Until yesterday I was able to import autogluon, but now if I try to import I get an error stating, cannot import name 'IPV6_ADDRZ_RE'.
Environment/ OS: I am using google colab and below are the details.
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.5 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
Steps to Reproduce:
Step1: Open a new notebook on google colab.
Step2: Install the autogluon.
!pip install --upgrade "mxnet_cu101<2.0.0"
!pip install autogluon
Step3: Restart the environment.

Step4: You'll get the error below.

Thanks for the info!
Seems like botocore or urllib released a new version today which causes the issue. Downgrading the versions of those packages would be your best bet.
Could you try following this: https://github.com/boto/botocore/issues/2187#issuecomment-712819351


Default build task runs user task in random repositories

I got confused after seeing this a few times when running the default build task:

Looking into this I found that I only have a single build task, which is defined in user tasks:

I don't remember adding this, so an extension may have done this without my knowledge, or I just forgot I tested something. Additionally I have seen this build task trigger in folders with actual default build tasks, which is likely that recurring issue coming back where the default build task can't be found until I reload the window.
Regardless, I think we should consider some changes:

How do you unset the default build task?
A user task probably should never be the default, this makes sense to me at least.

This is odd because you haven't specified isDefault here, so i'm not sure why it would run any task at all. It should instead prompt you to configure the default build task.

How do you unset the default build task?

by removing isDefault

A user task probably should never be the default, this makes sense to me at least.

We should allow this, but in your case, this was a bug because you hadn't set it as the default via isDefault and it was falling back to that.

Repro:

have a workspace with no tasks besides a user defined one that has group:build
Use the ctrlCmd+shift+b shortcut to run the default build task
🐛 before, it was running that task
now, there should be a configure default build task quickpick

Make sure to also verify that if you have a defined isDefault task, it gets run automatically.
Also try having several with isDefault and verify that it prompts you to choose which one you mean.


Make errors

When I run make && cd build && sudo make install.I get the following error.
%%%%%%%%%%%%%%%
google::protobuf::internal::ArenaStringPtr)'
collect2: error: ld returned 1 exit status
make[3]: *** [bin/blob_gpu_test] Error 1
make[3]: Leaving directory /home/beans/caffe2/build' make[2]: *** [caffe2/CMakeFiles/blob_gpu_test.dir/all] Error 2 make[2]: Leaving directory /home/beans/caffe2/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/beans/caffe2/build'
make: *** [all] Error 2
So how can I fix these problems. Any help from you will be appreciated. Thank you very much.

Given that the first line of the output you posted had to do with protobuf I'm going to assume this was a protobuf build issue. Can you post your CMake version, CMake summary output, compiler version, operating system, and other relevant details about your environment?
If this is no longer a problem, please feel free to close the issue.

@YangBain are you still having this issue?

The cmake logic for protobuf has changed significantly since this issue was created, so I will close this issue. If you encounter any problems in the future, please open a new issue.


proof of reserve

Reach out on slack if you're interested in the bounty
Proof of reserve is key for the success of bitcoin. To understand why, some useful reading:
https://niccarter.info/wp-content/uploads/Proof-of-Reserves-.pdf
https://github.com/olalonde/proof-of-assets
https://blockstream.com/2019/02/04/en-standardizing-bitcoin-proof-of-reserves/
Some idea of how this could be rolled out progressively:
Step 1 (proof of liabilities):
Proof of reserve with public account listing.
This is what Coinfloor is currently doing.
one hash per user, so that each user can verify that their balance has been included correctly
Step 2 (proof of reserve):
For every UTXO on our onchain wallet, sign a message showing the wallet own the UTXO
For lnd wallet, more research is being needed: https://github.com/lightningnetwork/lnd/issues/5391
(TODO: look at how this should be published?)
Step 3 (better proof of liabilities):
Instead of publishing the whole list of hashed user with amount, use a merkle tree and only published the merkle root.
This would require adding an API so that the user can send his hash, and can receive the merkle path and the balance so that the client can verify that their balance has been included themselves
Step 4 (zero knowledge proof: improve the privacy by not disclosing the total amount):
This is the difficult part. Step 2 and 3 involves that the total amount is published to the world (or the user at least). This would be preferable to have a proof that the total assets is >= than the total liabilities without having to disclose the total balance.

Idea for Proof of Liabilities
Use a Merkle tree to sign in batch the proof for each wallet (like in blockcerts).
Steps to create the proof

Create a hash for each wallet (id of wallet or username, balance, date, time)
Create a Merkle tree
Save the Merkle tree path for each user, it could be and additional field in user schema or just a plain file uploaded to a publicly available storage (in this case we cant make the proof with the username)
Include the Merkle root hash in the same procedure of proof of reserve

Steps to validate

Add an additional setting in mobile app to:

allow the user to download the proof of reserve (for his/her wallet)
view the content of the proof/certificate

Create and publish a validation tool or... just copy or use blockcerts validation tool

https://blog.bitmex.com/addressing-the-privacy-gap-in-proof-of-liability-protocols/

https://blog.bitmex.com/addressing-the-privacy-gap-in-proof-of-liability-protocols/

https://github.com/BitMEX/proof-of-reserves-liabilities

https://blog.bitmex.com/proof-of-reserves-liabilities-bitmex-demonstration/

Should be looked at: https://github.com/jakecraige/provisions

@nicolasburtey can we close this?

I think so but we should copy the documentation/link maybe to the poof of sats repo in a RESEARCH.md (or another better name)

this will be implemented in other layers (bria, cala) so closing this ticket.


Redirect loop when linking to the site with target="_blank"

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

[x]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Important: Please fill in your exact version number above, e.g<EMAIL_ADDRESS>Framework
Angular 9
Description
A link to an angular app using target="_blank" results in an infinite loop since the MSAL library thinks that the real window is a popup.  It uses the following line of code from WindowUtils to check if we're in a popup context:
    static isInPopup(): boolean {
        return !!(window.opener && window.opener !== window);
    }

in Chrome at least, when linking to the app using target="_blank" results in window.opener being non-null and pointing to the old page.  So the MSAL library thinks we're in a popup, neglects to handle the hash and (later down the line) my app thinks the login didn't occur and redirects again;  infinite loop.
Security
No
Regression
Unknown
Configuration
 MsalModule.forRoot({
      auth: {
        clientId: environment.msalConfig.clientId,
        authority: environment.msalConfig.authority,
        redirectUri: window.location.origin,
        validateAuthority: false,
        navigateToLoginRequestUrl: false
      },
      cache: {
        cacheLocation: 'sessionStorage',
        storeAuthStateInCookie: isIE
      },
      system: {
      }
    }
      , {
        protectedResourceMap: environment.msalConfig.resourceMap,
        unprotectedResourc

Reproduction steps

Expected behavior
Links opened in new tabs should function correctly.
Browsers
I bleieve all browsers expose window.opener to pages opened with target="_blank", so they should all have this problem.

@burns47 This is a known issue, we plan to have a fix soon. cc: @sameerag

Status: Working on a POC and will release a beta to get this rolling, potentially later this week or early next week.

<EMAIL_ADDRESS>is available with a fix for this issue, please let us know if it is still a problem. Thanks!

@jasonnutter I am using<EMAIL_ADDRESS>and still having the login issue when coming from a link with target="_blank". I am using login redirect as login method.

@turculaurentiu91 Can you please open a new issue, thanks!


"stable" redirect to latest release page

I want to be able to link to the latest "stable" release for a given page.
e.g

http://docs.projectcalico.org/stable/getting-started/kubernetes/installation/hosted/kubeadm/

should redirect to

http://docs.projectcalico.org/v1.6/getting-started/kubernetes/installation/hosted/kubeadm/

So I don't have to update links in other repos all the time.

Seems possible with jekyll-redirect-from which luckily is on the list of jekyll plugins supported by github

That gem is quite powerful, but would require adjustments to our release process. Let's walk through a quick example of how this works. Let's use v2.0/getting-started/kubernetes/index as an example.
We'd place at the top of that document, in the yaml front matter:
---
redirect_from: /stable/getting-started/kubernetes/
---

When it renders the site, jekyll will create _site/stable/getting-started/kubernetes/index.html, which includes the following:
<title>Redirecting…</title>
<link rel="canonical" href="http://docs.projectcalico.org/v1.6/getting-started/kubernetes/">
<meta http-equiv="refresh" content="0; url=http://docs.projectcalico.org/v1.6/getting-started/kubernetes/">

Redirecting…

Click here if you are not redirected.

Folks who visit docs.projectcalico.org/stable/getting-started/kubernetes/ will see this basic web page briefly before the web browser interprets the html and does the redirect.
This leaves two questions:

How does this affect SEO? This doesn't appear to issue a 300 or 301 redirect, so not sure how google's web crawlers will take this.
How do we work this into our release processes and layouts. Lets say stable changes from v1.6 to v2.0. We now need to remove that from the header of all v1.6 pages, and add it for v2.0 pages. Additionally, any pages that no longer exist or had their URL changed will now 404.

We should look into improving the release scripts (when we tackle #134) so they also remove /latest from all frontmatter of the last release, and add it on the new latest release

This is now fixed


Add a fallback way to determine the home path.

On linux/386 systems Parse (in wego) fails with something like:
"[...]
2016/04/15 12:13:04 Error parsing config: user: Current not implemented on linux/386
You can set the environment variable WEGORC to point to your config file as a workaround
[...]"
Before restorting to WEGORC we should try the HOME env variable first.

The Problem is probably that you are using the gccgo package instead of the golang-go package of your distribution. I don't know why, but gccgo doesn't seem to be able to implement that functionality, while it works perfectly from the golang sources.
I don't want to introduce codepaths which might not work on all architectures (It is not defined for all of them what $HOME and $UserProfile should link to) when we have a whole programming language team dedicated to unify the interface for all supported platforms.

Actually it was cross compile with gc Go 1.6.1. When compiling it natively it works.
os.user depends on cgo.
See https://github.com/golang/go/issues/6376

Ah, thanks for the reference.


(PUP-5604) (WIP) Make systemctl better at bubbling up errors to puppet logs

Error: Could not start Service[corosync]: Execution of '/usr/bin/systemctl start corosync' returned 1:
Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details.

Figure out a way of giving visability in logs when systemctl commands fail. Actually run the journatclt command to get the error, rather than requiring manual intervention.
I'm not sure the best way of doing this, and its been a long time since I've tried doing anything for puppet-core. I'll need some dev guidance on this if possible! :smile:

Note here about the discussion we had online: spelunking through the code, it seems that this is the right thing to do, but at the wrong place. tracing calls through the inheritance, the start/stop/restart methods of the baseclass (service.rb) need to be overridden instead.

CLA signed by all contributors.

Yeah. As DavidS said, the service providers rely largely on their base class(es) to do the work. The rescues you added here will never fire, since those *cmd methods just return the command name to be executed. No execution actually happens there.
Since this has been sitting since February I'm gonna go ahead and close it, but if you have time to poke this again let us know


[Docs] AI overview guidelines

Related https://github.com/carbon-design-system/carbon-website/issues/3997
Added a new page under the guidelines sections for "Carbon for AI." There are a few links and a leadspace image that will need to be added before merging but I wanted to go ahead and get a content review on the rest of the page.
Changelog
New

Guidelines/Carbon-for-AI

Note

Some links will 404 until the Design for AI site is live.
Also still waiting on a leadspace image at the top, it will be a version of the home banner.

Ready for review but do not merge
We are waiting to roll this out at a specific time later in the week. Do not automatically merge it.

@alisonjoseph Also do you know what I need to do to resolve the merge conflict?

@aagonzales I'll push a fix, this file actually doesn't even need to be in github


Vi script that automates compile/synth/upload from editor

@cliffordwolf , maybe this is interesting for some VI users. If not just happily ignore.
 The script has been tested (lightly, not extensively) on a VIM - Vi IMproved 7.3.

This PR removes the top-level makefile!? (see "done merge" commit efd0a26)

Re. the vim script itself: I like that you wrote that. But I think it is something tailored to your personal workflow, not necessarily something that is useful to a general audience. Therefore I'm not going to merge this PR. I hope you are not disappointed.

Makefile removal = commit bug.
All cool, it is indeed a very personal hack, just shared in case you were collecting such things somewhere in the repo. I'll keep it on mine nonetheless.

Once more, thanks @cliffordwolf  for this amazing tool!


MasterDetailRelation, throwing NullReference on ListRequestHandler.Process()

Hoping someone has seen something like this... I have a MasterDetailRelation, exception being thrown in the master's repository.List() method. SQL that's executed right before the exception looks fine, returns results with no empty columns.
Master row has this:
[DisplayName("Audit Result List"), MasterDetailRelation(foreignKey: "ActiveAuditId"), ClientSide]         public List<PolicyTestResultRow> AutomatedTestList         {             get { return Fields.AutomatedTestList[this]; }             set { Fields.AutomatedTestList[this] = value; }         }
Detail row has this:
[DisplayName("Audit"), Expression("jRequest.ActiveAuditId"), ForeignKey("Audit", "Id"), LeftJoin("jAudit"), LookupInclude, MinSelectLevel(SelectLevel.List)]         public Int64? ActiveAuditId         {             get { return Fields.ActiveAuditId[this]; }             set { Fields.ActiveAuditId[this] = value; }         }
And here's the stack trace for the exception:
Serenity.Services.MasterDetailRelationBehavior.<OnReturn>b__24_1(Row x) in P:\Sandbox\Serene\Serenity\Serenity.Services\RequestHandlers\IntegratedFeatures\MasterDetail\MasterDetailRelationBehavior.cs:line 167    at System.Linq.Lookup2.Create[TSource](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer)
at ...`
Anyone seen something like this before?

MasterDetailRelation loads all detail rows in list handler with an IN query, and converts them to lookup by their master ID values, then fills them in response entities by using the lookup. But somehow you get error in lookup creation so your master value should be null in one of details but dont know how.

Ok. I'm no longer using a MDR so this isn't blocking me. Thanks.


Retrieve only a summary of the condor jobs in DrainStatusPoller - wmagent 1.4.5 branch

1.4.5_wmagent branch version of https://github.com/dmwm/WMCore/pull/10458
Otherwise I cannot properly test it in the agents...

testing it on submit3

Still getting stuck after 5 or 10 condor queries. Trying a minor variation of it by creating a schedd object in the method local scope.

Creating the schedd object for every call does not help either. I have removed this patch from submit3.

It does not fix the issue, and I might not try to fix it again for the coming weeks, so closing it.


Update broken profiles.yml link

Issue
Closes https://github.com/fishtown-analytics/dbt/issues/1344
Solution
This MR:

replaces the existing (broken) link to the docs where there is a functional, accurate sample profile. This is a great link to point to because the docs are extremely likely to stay updated as the requirements for the profiles.yml file changes (rather than another thing to be maintained).

Thanks for the contribution @emilieschario! This LGTM - are you ready for me to merge this?

Ready whenever you are!


[FEATURE] Remove x[pattern] and just use shuffle() function instead

The wide::operator[] is massively absued and it leads to strange dependency.
We're going back to a proper shuffle function that do the optimization of patterns.

[ ] Move all specific swizzle to function/
[ ] Move lookup to function
[ ] Add a shuffle function that perform pattern recognition + calls
[ ] Remove the operator[] performing swizzle/lookup from wide/logical


Build time profiling using -Z timings

cargo has -Z timings feature in nightly. It shows how long compile spent times like following:
   Completed espr v0.1.0 lib (test) in 6.1s
   Completed ruststep v0.1.0 lib (test) in 10.1s
   Completed ruststep v0.1.0 in 18.7s
   Completed espr-derive v0.1.0 lib (test) in 0.5s
   Completed ruststep-derive v0.1.0 test "try_build" (test) in 1.4s
   Completed ruststep-derive v0.1.0 lib (test) in 2.3s
   Completed ruststep v0.1.0 test "abc_dataset" (test) in 3.4s
   Completed ruststep v0.1.0 test "enum_deserialize" (test) in 3.5s
   Completed ruststep v0.1.0 test "simple" (test) in 3.5s
   Completed ruststep v0.1.0 test "list" (test) in 3.6s
   Completed ruststep v0.1.0 test "any_deserialize" (test) in 3.7s

https://doc.rust-lang.org/cargo/reference/unstable.html#timings

cargo build --timings

has been stabilized in 1.60.0
https://blog.rust-lang.org/2022/04/07/Rust-1.60.0.html#cargo---timings


Updated the tags creation parameters to reflect current api options.

Removed parameter options not listed in this list.

Coverage decreased (-0.2%) to 97.624% when pulling 88112884fcc8c66c3b0c2ce6d23320c88bdba4c7 on prasadsurase:updated-tags-create-parameters into 2632ae380f01f0827180369e23df4dadb24c6693 on piotrmurach:master.

Coverage decreased (-0.2%) to 97.624% when pulling 88112884fcc8c66c3b0c2ce6d23320c88bdba4c7 on prasadsurase:updated-tags-create-parameters into 2632ae380f01f0827180369e23df4dadb24c6693 on piotrmurach:master.

Thank you.


fix for dubbo source metric destination label unknown

fix for  source  metric destination label is unknown  https://github.com/aeraki-mesh/aeraki/issues/196


Change the hard code to fix test_spdm_common error  and make the test case id correct

Fix: #450
Change the hard code to fix test_spdm_common unit test error.
Because the size of viod* is different on different machine, test_spdm_common unit test error is happen in ia32. Change the hard code to fix it.
Make the test case id correct.
Signed-off-by: Wenxing Hou<EMAIL_ADDRESS>

Looks good to me.


Bump terraform to (tama)go1.22

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@cb61646). Click here to learn what that means.

Additional details and impacted files
@@          Coverage Diff           @@
##             main    #147   +/-   ##
======================================
  Coverage        ?   0.00%
======================================
  Files           ?      20
  Lines           ?    1437
  Branches        ?       0
======================================
  Hits            ?       0
  Misses          ?    1437
  Partials        ?       0

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


20 usd in crypto to whoever can help me solve this getrandom error when i run anchor build

disclaimer im a noob so pls bear with me. anyway, when i run cargo build my program compiles successfully but when i run anchor build i get this error output.
error: target is not supported, for more information see: https://docs.rs/getrandom/#unsupported-targets
   --> src/lib.rs:267:9
    |
267 | /         compile_error!("\
268 | |             target is not supported, for more information see: \
269 | |             https://docs.rs/getrandom/#unsupported-targets\
270 | |         ");
    | |__________^

error[E0433]: failed to resolve: use of undeclared crate or module `imp`
   --> src/lib.rs:291:5
    |
291 |     imp::getrandom_inner(dest)
    |     ^^^ use of undeclared crate or module `imp`

For more information about this error, try `rustc --explain E0433`.
error: could not compile `getrandom` (lib) due to 2 previous errors
warning: build failed, waiting for other jobs to finish...`.

according to the documentation of solana (this section corresponds to my error) https://solana.com/docs/programs/lang-rust#depending-on-rand.    “Programs are constrained to run deterministically, so random numbers are not available. Sometimes a program may depend on a crate that depends itself on rand even if the program does not use any of the random number functionality. If a program depends on rand, the compilation will fail because there is no get-random support for Solana. “
and it said to add this to the program cargo.toml:
getrandom = { version = "0.1.14", features = ["dummy"] }.
and
getrandom = { version = "0.2.2", features = ["custom"] }.
i tried it and it did not work
givens

i dont have getrandom as a direct dependency for my program though i have rand 0.8.5 which doesnt pull in getrandom (but rand 0.7.3 does…which i have as a transitive dependency)
my program seems to be pulling in getrandom 0.1.16 and 0.2.15
i found that getrandom 0.2.15 is a required dependency of ahash 0.7.8. ahash 0.7.8 is an optional dependency for hashbrown 0.11.2. i tried disabling default features for hashbrown 0.11.2. it did not get rid of ahash 0.7.8

if you solve it drop your sol address and ill send you 20 bucks. appreciate the help!

Please provide a detailed reproduction for the error you're encountering. Incentivization won't prioritize your issue if no MCVE provided.

You also mentioned that this problem happens with anchor build but not cargo build.  It might be more helpful to reach out on an anchor support channel in case there is anything unique they are doing to cargo.
And generally, cargo user support questions are better addressed at https://users.rust-lang.org/  while this is more targeted for when behavior seems to be incorrect.

rand v0.7.3

Pulled by:

ed25519-dalek v1.0.1

Used by ed25519-dalek-bip32 v0.2.0

Which is a dependency for solana-sdk v1.18.18 and subsequently anchor-client v0.29.0, orao-solana-vrf v0.4.0, and other Solana-based dependencies.

libsecp256k1 v0.6.0

Used directly in your project's Solana program code (linked via solana-program v1.18.18).

program cargo.toml:
[package]
name = "LD"
version = "0.1.0"
description = "Created with Anchor"
edition = "2021"

[lib]
crate-type = ["cdylib", "lib"]
name = "lucky_dog"

[features]
no-entrypoint = []
no-idl = []
no-log-ix-name = []
cpi = ["no-entrypoint"]
default = []

[dependencies]
anchor-lang = "0.29.0"
orao-solana-vrf = { version = "0.4.0", default-features = false, features = ["cpi", "sdk"] }
spl-token = { version = "4.0.0", features = ["no-entrypoint"] }
solana-program = "1.18.19"
anchor-spl = "0.29.0"
clock = "0.3.3"
scopeguard = "1.2.0"
anchor-client = { version = "0.29.0", optional = true }
solana-account-decoder = "1.18.19"
solana-sdk = { version = "1.18.19", default-features = false }

problem appears when i add anchor client as a dependency. everything else in my program are default. (i did not add any logic to my lib.rs yet) other than that the only other modificaiton i made outside this file was setting the resolver to "2" in my root cargo.toml

@luckydog6969 Without a minimal reproducible example, this is not going to move forward. Check these issues as examples of how to provide an MRE.

https://github.com/rust-lang/cargo/issues/14010
https://github.com/rust-lang/cargo/issues/13720

To provide an MRE, you can either setup a Git repository, or send a zip file of the affected project here.

You also mentioned that this problem happens with anchor build but not cargo build. It might be more helpful to reach out on an anchor support channel in case there is anything unique they are doing to cargo.

Given this. I am going to close the issue now. If later you find it is potentially a Cargo bug, feel free to open a new one.


Update gulp spawn to work with latest jekyll and bundle

I was trying to use this and could not get the build process to spawn. I believe its because the jekyll command required the bundler as well. I updated the build command in the gulp file to use the bundler to call jekyll.

I actually went ahead and expanded the gulp file to handle different levels of work. I added npm scripts to run the browsersync server, build the site with dev settings, or build the site for production.
Dev settings adds sourcemaps for css.
Production settings purges, autoprefixes, and compresses css.
There are a significant amount of changes to the gulpfile, but ultimately it makes for a much faster development experience.

This is so awesome! Thank you so much! I'm going to review this ASAP.

Cheers. I’m still messing with the gulp file some.
I keep having an issue with the Browsersync freezing on Reloading browsers. Seems like a somewhat common issue from what I’ve found so far.   Is that something you run into?
I think it has to do with the timing of which gulp tasks run causing a rebuild before other gulp tasks finish.
Joey Defourneaux

On Nov 9, 2018 at 5:35 PM,  <Taylor Bryant (mailto:notifications@github.com)>  wrote:
This is so awesome! Thank you so much! I'm going to review this ASAP.
—
You are receiving this because you authored the thread.
Reply to this email directly,   view it on GitHub (https://github.com/taylorbryant/tailwind-jekyll/pull/16#issuecomment-437516504), or   mute the thread (https://github.com/notifications/unsubscribe-auth/AOWMW_kuBXO9Mb4lu_PJ9y1nQjXcJ7Dtks5utgMmgaJpZM4YPvO9).

@allcontributors add @jd4no for code


Addition for SAP HANA

Addition for SAP HANA as a database option with SQLPAD

Thanks so much for this @ccmehil! Looks great. I should have this in the next release some time next week.


The list is starting to grow, really fast.

Is your feature request related to a problem? Please describe.
Yes, i believe the apps/features list is starting to grow really fast, and getting kinda messy and tiring to look at the description of each program, if you want to try something new.
Describe the solution you'd like
I'm new to Powershell, so i don't know too much to make a pr for that, but what about, making sub-sections?
Describe alternatives you've considered
Like in the Games section, we could have "launchers", "multi-launchers", "base-games", etc. But for each section, when needed.
What you guys think?

I agree, would make discovering new software a lot easier. And in conjuction with this suggestion the sub-headers should be collapsible

Agreed, it's starting to get a bit overwhelming now. I think collapsible subsections are a necessity at this point.

Agreed, it's starting to get a bit overwhelming now. I think collapsible subsections are a necessity at this point.

I have no experience with ps, but i believe i learned how to implement that, i'm still testing it. Once it's working properly, i'll submit a pr.


Update OAuthController.cs

I think this is a bug.
It takes the realm as the Name, then it always looks for a user named 'default' in the Umbraco members.

Doh! How did I miss that! Nice spot,

@TimPickin have released a 1.0.1 version with your fix in. Thanks again for the PR.

@mattbrailsford  You are welcome, thanks for writing such a great package. It is exactly what I need.


Create it_IT.lang

Thanks for your work :D

You are welcome. If there would be a way to add the keys that don't work, it would be awesome


OTF analysis shows 0% decrease

Overview
The extent area comes in a different format when querying pre-calculated area (as an array) or an OTF query (as a single value). This will will parse it one way or another depending on the type.

@SARodrigues thanks! I guess it's better safe than sound. I edited your suggestion a little bit to not nest tertiary operations (linter doesn't let me :)


Run clippy --fix -- -D clippy::pedantic

CI is unhappy. Also, do you think it's worth having it in CI?

CI is unhappy.

Yeah, I added some #[must_use]s manually, and clippy is unhappy if the return type is already #[must_use]. Fixed.

Also, do you think it's worth having it in CI?

There is still a ton of pedantic warnings. Only the automatically fixable ones are changed by this PR. IMHO many warnings in clippy::pedantic are, well, overly pedantic. :) But I guess we can gradually enable more clippy lints. E.g. from a users' point-of-view missing_errors_doc is very useful, but has to be done manually.

Thanks!


6.3 Standardization of validation and test data

I have 2 concerns:

The training data is standardized using the mean and standard deviation of the training set. Shouldn't the validation and test set be standardized using its respective mean and standard deviation as well? I can't see this done anywhere.
Wouldn't it be better to refer to the procedure as standardizing and not normalizing? If nothing else, this will conform to scikit-learns terminology.

I withdraw the issue as I understand now that it is standard practice to standardize or normalize the validation and test set with the mean and standard deviation of the training set. This is, so that, the same (inverse) transformations can be applied to the validation and test sets with the prediction results. My bad!


Unpin torch

cc @ydshieh

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


App language dropdown content not loading(Profile page)

Autographa 2.0 beta 4
Issue Description:- profile page -> app language (option in dropdown not loading)

Disable the dropdown for now, as only english is available,


[TW#28233] Why ESP-IDF does use old version of submodules?

We are using latest stable version of EDP-IDF but i noticed submodules are not using latest versions.
Esp-Idf version I'm using is v3.1.2 and it's the latest one provided by the espressif at the moment. Release date of v3.1.2 is 02 January 2019.
Here is the list of some submodules still using the old version:
1. AWS IoT SDK:  commit 8bf852d on 08 January 2018. espressif/aws-iot-device-sdk-embedded-C repo has latest AWS version on 06 August 2018 and commit 2991832. I'm testing AWS and using latest version of AWS making my compile dirty.
2. BT lib: sdk included commit 2bf7a0620f on 14 December 2018. Repo latest stable release commit bc66c9d on the same day but inluding more bug fixes.
3. mbedtls: sdk included commit b9ada30675 on 30 July 2018. Repo latest stable release commit 19eb57f7 on 18 September 2018
Other submodules also using old versions but they are not forked into espressif repositories, but all the submodules I mentioned above are forked in espressif repos and that commits are made by espressif employees. They are checked and release on submodule's repos but not included in the esp-idf sdk.
Is there any particular reason for not tracking submodules?
Thanks,
Ibrahim.

Hello @IBeRyUS. v3.1.2 is a bugfix-only release which means that the submodules are updated only if they contain a bugfix for the v3.1 release. It is normal that it has older submodules in comparison with later releases (new submodule features of v3.2 or v3.3 are not required in v3.1).
It is normal even for master to not have the latest submodule versions because new features/bugfixes are firstly added to the submodule and only later to master.

Hi @dobairoland. V3.1.2 is bugifx for release/v3.1 yes it's true. but the submodules i mentioned they are already bug-fixes for v3.1. if you have enough time please check v3.1.1 and v3.1.2 submodule versions.
one example. if you check esp32 lib you will see same versioning with esp-idf. All the new commits i mentioned are either using version number correlation with esp-idf or standalone repo.
or why don't you check aws-iot repo on espressif repos. it's updated months ago by @projectgus but not even master branch including latest version.
I'm manually changing to latest versions of submodules but it's making my compiles dirty and that's annoying. Deploying esp-idf on other machines is another hassle too.

Sorry, maybe I don't get your point or I was not clear with my explanation. Let's take a look at your example:

BT lib: sdk included commit 2bf7a0620f on 14 December 2018. Repo latest stable release commit bc66c9d on the same day but inluding more bug fixes.

You are right. If we take a look at the release/v3.1 branch of the BT library then we see bc66c9d as the newest commit which is not included in v3.1.2 of ESP-IDF (and not even in the release/v3.1 branch of ESP-IDF). The reason is simple. We have an internal PR which hasn't been merged yet. After merge it gets into the release/v3.1 branch of ESP-IDF and after testing it gets into some of the subsequent v3.1.x releases.
If you need a bugfix from a submodule then you have to wait until it gets released with ESP-IDF or you can manually checkout-out the given fixes (as you do). But be advised, that untested combination of IDF and submodules may yield issues.
You are right regarding third-party submodules. Those are not updated automatically. We are updating them on request (or plan). The update also may take a while because it cause incompatibility issues and has to be tested with the other components.

Esp submodules updating regularly. I know you are making stable versioning for v3.1.x. Esp32-lib, bt-lib and esptool-py are followed by esp-idf submodules but third-party submodules are not followed in the esp-idf.
Another thing if documentation says latest and stable version is v3.1.x then I expect all submodules to be updated as well.
I need to change AWS, mbedtls after every pull because old versions not working properly with AWS servers. Doing this manual update makes my compilation with dirty flag and sometimes it's hard to understand is it because of my alterations on the sdk or this updates.
If you update third-party submodules by request, can you check and update aws, json and mbedtls ASAP.
Other third-party submodules also needs checking too.

Hi @IBeRyUS,
There are three different things to discuss here: versioning, internal & external libraries.

Another thing if documentation says latest and stable version is v3.1.x then I expect all submodules to be updated as well.

We have a "master" branch which is the equivalent of the "latest" version in the docs, and stable releases which are older than this. Currently master (new development) is v3.3-dev, we have a prerelease of v3.2-beta1 and the latest stable release ("stable") is v3.1.2. You can read more about the versioning scheme here: https://docs.espressif.com/projects/esp-idf/en/latest/versions.html
For internal (Espressif) libraries (esp32-wifi-lib & esp32-bt-lib), the matching submodule version for a particular commit (version) of ESP-IDF should always be used not any other version or branch from the repo. The very latest esp32-wifi-lib and esp32-bt-lib commits on GitHub usually correspond with the master branch (ie new development, not stable). Sometimes they may even be pushed to github ahead of the corresponding (necessary) source changes in ESP-IDF itself which update the submodule. If these internal library submodules don't match the commits set in the ESP-IDF repo, ESP-IDF will probably not work as expected.
For third party libraries, we try to track upstream versions but there are sometimes delays because we need to test any updates still work with ESP-IDF. For the supported stable (tested) version of ESP-IDF, please use the submodules at the versions provided. If you find something doesn't work (either because the library is out of date or for some other reason), please open an issue with details and we'll fix it (possibly by updating the library submodule or possibly by some other method).
For bugfix releases like v3.1.2, we only update to fix bugs found since the v3.1 release, to avoid unexpected behaviour changes for users. This applies to both ESP-IDF code and upstream libraries.
So currently AWS IoT is based on v2.2.1 in the v3.1.x releases and based on AWS IoT v3.0.1 (the current stable AWS IoT release) in master. If something isn't working in ESP-IDF v3.1.2 with the provided AWS IoT version, please open an issue with the details.
For mbedTLS, ESP-IDF v3.1.x releases are using the v2.12.0 mbedTLS release and ESP-IDF master is using mbedTLS v2.13.1. I notice we're about six weeks behind on mbedTLS minor versions, so we will update the mbedTLS version used in the master branch soon - thanks for the reminder. However we probably won't update mbedTLS to a new minor version in ESP-IDF bugfix releases unless there are known bugs which are fixed by updating - so if you experience problems with the provided mbedTLS version then please open an issue with those details as well.

Closing due to lack of response.
AWS IoT SDK v3.0.1 (latest upstream release) can be found in ESP-IDF master branch and prereleases v3.2-beta3 and v3.3-beta2. This version will be v3.2 & v3.3 final releases once they are available.


Remove charSize. Always use utf8.

Closes #60
(but is still a draft - things to figure out, mainly how breaking this will be)

I've been looking at this a bit myself.
Why would we want plain strings at all for this library? 🤔
Why not always use Uint8Arrays or encoded strings (eg. base64)?

Aside: status of this PR is that it breaks some stuff in webnative and I didn't yet do the work of figuring it out yet.
Yeah I agree with that mostly. I think in some cases you want to be able to encrypt some user input maybe?
Something needs to change though. Encoding seems messy at the moment.


ModuleNotFoundError

gerald@P3530:~/Bureau/CROWDSEC/DEVEL/pycrowdsec/examples/flask$ python3 main.py
Traceback (most recent call last):
  File "/home/gerald/Bureau/CROWDSEC/DEVEL/pycrowdsec/examples/flask/main.py", line 1, in <module>
    from pycrowdsec.client import StreamClient
ModuleNotFoundError: No module named 'pycrowdsec'

Did you run python setup.py install before ?
Also, please note that this module is still in very early development, so no guarantee on whether it will work correctly or not.

Did you run python setup.py install before ?

Yes :
gerald@P3530:~/Bureau/CROWDSEC/DEVEL/pycrowdsec$ pip show pycrowdsec
Name: pycrowdsec
Version: 0.0.2
Summary: Python bouncer and clients for crowdsec
Home-page: https://github.com/sbs2001/pycrowdsec
Author: CrowdSec
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: /usr/local/lib/python3.9/dist-packages/pycrowdsec-0.0.2-py3.9.egg
Requires: requests
Required-by:

Also, please note that this module is still in very early development, so no guarantee on whether it will work correctly or not.

Sure ! ;-)

This is a bug indeed.
@erdoukki  as a workaround you can do
git clone https://github.com/crowdsecurity/pycrowdsec
cd pycrowdsec
python3 -m venv venv
source venv/bin/activate
pip install -e ./
cd examples/flask
python main.py

Stay tuned we will be fixing this quick and add more features very soon.

@erdoukki  could git pull the latest now, just pushed a fix.

Thanks,
Done this, to get it work :
git clone https://github.com/crowdsecurity/pycrowdsec
cd pycrowdsec
python3 -m venv venv
source venv/bin/activate
pip install -e ./
cd examples/flask
pip install -r requirements.txt
python main.py

Then it start :
$ python main.py
 * Serving Flask app 'main' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on all addresses.
   WARNING: This is a development server. Do not use it in a production deployment.
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

But it quickly hang :
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.9/threading.py", line 892, in run
    self._target(*self._args, **self._kwargs)
  File "/home/gerald/Bureau/CROWDSEC/DEVEL/pycrowdsec/src/pycrowdsec/client.py", line 34, in _run
    self.process_response(resp.json())
  File "/home/gerald/Bureau/CROWDSEC/DEVEL/pycrowdsec/src/pycrowdsec/client.py", line 38, in process_response
    if response["new"] is None:
KeyError: 'new'

Stay tuned we will be fixing this quick and add more features very soon.

Thanks !

another attempt from OpenWrt give (partial) success :
root@ultra:~# git clone https://github.com/sbs2001/pycrowdsec/
Cloning into 'pycrowdsec'...
remote: Enumerating objects: 70, done.
remote: Counting objects: 100% (70/70), done.
remote: Compressing objects: 100% (42/42), done.
remote: Total 70 (delta 16), reused 69 (delta 15), pack-reused 0
Receiving objects: 100% (70/70), 14.48 KiB | 411.00 KiB/s, done.
Resolving deltas: 100% (16/16), done.
root@ultra:~# cd pycrowdsec
root@ultra:~/pycrowdsec# git checkout dev
Branch 'dev' set up to track remote branch 'dev' from 'origin'.
Switched to a new branch 'dev'
root@ultra:~/pycrowdsec# pip install -e ./
Looking in indexes: https://pypi.org/simple, https://packagecloud.io/crowdsec/crowdsec/pypi/simple
Obtaining file:///root/pycrowdsec
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
	Preparing wheel metadata ... done
Requirement already satisfied: requests in /usr/lib/python3.9/site-packages (from pycrowdsec==0.0.2) (2.25.1)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3.9/site-packages (from requests->pycrowdsec==0.0.2) (2020.6.20)
Requirement already satisfied: chardet<5,>=3.0.2 in /usr/lib/python3.9/site-packages (from requests->pycrowdsec==0.0.2) (4.0.0)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/lib/python3.9/site-packages (from requests->pycrowdsec==0.0.2) (1.25.11)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3.9/site-packages (from requests->pycrowdsec==0.0.2) (3.2)
Installing collected packages: pycrowdsec
  Attempting uninstall: pycrowdsec
	Found existing installation: pycrowdsec 0.0.1
	Uninstalling pycrowdsec-0.0.1:
	  Successfully uninstalled pycrowdsec-0.0.1
  Running setup.py develop for pycrowdsec
Successfully installed pycrowdsec-0.0.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
WARNING: You are using pip version 21.1.3; however, version 21.2.4 is available.
You should consider upgrading via the '/usr/bin/python -m pip install --upgrade pip' command.
root@ultra:~/pycrowdsec# cd examples/flask/
root@ultra:~/pycrowdsec/examples/flask# pip install -r requirements.txt
Looking in indexes: https://pypi.org/simple, https://packagecloud.io/crowdsec/crowdsec/pypi/simple
Requirement already satisfied: flask in /usr/lib/python3.9/site-packages (from -r requirements.txt (line 1)) (2.0.1)
Requirement already satisfied: pycrowdsec in /root/pycrowdsec/src (from -r requirements.txt (line 2)) (0.0.2)
Requirement already satisfied: requests in /usr/lib/python3.9/site-packages (from -r requirements.txt (line 3)) (2.25.1)
Collecting expiringdict
  Downloading expiringdict-1.2.1.tar.gz (8.1 kB)
Requirement already satisfied: Werkzeug>=2.0 in /usr/lib/python3.9/site-packages (from flask->-r requirements.txt (line 1)) (2.0.1)
Requirement already satisfied: click>=7.1.2 in /usr/lib/python3.9/site-packages (from flask->-r requirements.txt (line 1)) (8.0.1)
Requirement already satisfied: Jinja2>=3.0 in /usr/lib/python3.9/site-packages (from flask->-r requirements.txt (line 1)) (3.0.1)
Requirement already satisfied: itsdangerous>=2.0 in /usr/lib/python3.9/site-packages (from flask->-r requirements.txt (line 1)) (2.0.1)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/lib/python3.9/site-packages (from Jinja2>=3.0->flask->-r requirements.txt (line 1)) (2.0.1)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3.9/site-packages (from requests->-r requirements.txt (line 3)) (2020.6.20)
Requirement already satisfied: chardet<5,>=3.0.2 in /usr/lib/python3.9/site-packages (from requests->-r requirements.txt (line 3)) (4.0.0)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/lib/python3.9/site-packages (from requests->-r requirements.txt (line 3)) (1.25.11)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3.9/site-packages (from requests->-r requirements.txt (line 3)) (3.2)
Building wheels for collected packages: expiringdict
  Building wheel for expiringdict (setup.py) ... done
  Created wheel for expiringdict: filename=expiringdict-1.2.1-py3-none-any.whl size=8440 sha256=436f2d92259cdc8c3c2d060cb68fa39bad24b579cb2f91bf2b8ee9d053e94701
  Stored in directory: /tmp/.cache/wheels/5e/fa/f2/0bd2b5b01f0fca88a9869905463f1ed55cececa3ad979debe5
Successfully built expiringdict
Installing collected packages: expiringdict
Successfully installed expiringdict-1.2.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
WARNING: You are using pip version 21.1.3; however, version 21.2.4 is available.
You should consider upgrading via the '/usr/bin/python -m pip install --upgrade pip' command.
root@ultra:~/pycrowdsec/examples/flask# nano main.py
root@ultra:~/pycrowdsec/examples/flask# cscli bouncers add flask_eg
Api key for 'flask_eg':

   3e20c1ca98f1d9cb2fd21da8a0aae805

Please keep this key since you will not be able to retrieve it!
root@ultra:~/pycrowdsec/examples/flask# export CROWDSEC_LAPI_KEY=3e20c1ca98f1d9cb2fd21da8a0aae805
root@ultra:~/pycrowdsec/examples/flask# python main.py
 * Serving Flask app 'main' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on all addresses.
   WARNING: This is a development server. Do not use it in a production deployment.
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

root@ultra:~/# tail /var/log/crowdsec.log
time="13-08-2021 11:33:47" level=warning msg="bad user agent 'CrowdSec-Python-StreamClient' from '<IP_ADDRESS>'"

Fixed via https://github.com/crowdsecurity/pycrowdsec/pull/3


Install ASO command fails on some tenants

Describe the bug
ASO requires a Service Principal (actually it no longer does, but it still supports deployment using a Service Principal). The Service Principal belongs to an Entra ID tenant. This tenant may have Conditional Access policies configured which prevent "token issuance". That is, they prohibit authentication flows in which a client ID and secret are exchanged for an access token (at least from certain machines - it still seems to work from within AKS clusters, which is why ASO itself is not broken by this).
In these cases (the MSIT tenant is an example), the ASO deployment command fails at the stage of checking the service principal. That is because we attempt to check subscription access using the Service Principal's own credentials (which are a client ID and secret), rather than those of the signed-in user.
This means we probably have to remove the functionality to check which subscriptions the service principal can access. We can use the signed-in user's token to examine role assignments, but it is very possible the user will not have the required permissions to do this, even if the service principal does. We don't want this command to fail in those cases, and so it will be simpler and more robust to remove the check altogether.
Mention the platform you are using
Occurs on all platforms
To Reproduce
Run the ASO command in any cluster on the MSIT tenant, and enter a service principal's client ID and secret.
Expected behavior
The extension checks which subscriptions the service principal can access without error.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Fixed by #724


Added checking for kubeCluster is Openshift to be used by Vault instance

Type of change

Bugfix

Description
To enable some configurations in Vault, we would need to detect whether the cluster used is Openshift or not. For that we have included a method to figure out when the cluster used is Openshift or just kubernetes.
Additional Context
Fixes #999
Checklist

[ ] Write tests
[X] Make sure all tests pass
[ ] Review performance test results. Ensure that any degradations to performance numbers are understood and justified.
[ ] Make sure all Sonarcloud warnings are addressed or are justifiably ignored.
[ ] Update documentation
[ ] Reference relevant issue(s) and close them after merging
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

@strimzi-ci run system tests

:arrow_forward: Build started - check Jenkins for more info. :arrow_forward:

:heavy_check_mark: Test Summary :heavy_check_mark:
BUILD NUMBER: 21
KAFKA VERSION: 3.6.1
TOTAL: 8
PASS: 7
FAIL: 0
SKIP: 1


Allowing passing a list of objects to the rule engine

One of the user come up with this idea along with typical use case: person can sign a contract. Then in fact the input would be the contract, the list of employees to choose from and the output should be a list of employees that can sign.

Hi, any update on this issue?

I think a better way of handling this use-case is to use an additional dummy attribute that contains the result of the condition(s). Then in your microflow you can filter for the attribute value


chore(router) rename atc to expression

Summary
rename 'atc' to 'expression'

The ATC is still mentioned here:
https://github.com/Kong/kong/blob/master/.requirements#L11

The ATC is still mentioned here: https://github.com/Kong/kong/blob/master/.requirements#L11

I think the normal user can not see this file, and we will not change atc-router's repo name now.

What about:
https://github.com/Kong/kong/blob/master/kong/router/atc_compat.lua#L414

What about: https://github.com/Kong/kong/blob/master/kong/router/atc_compat.lua#L414

Good catch. I will fix it.


Update iv and len context pointers manually when reallocating buffers

This PR adds a fix for faulty behaviour when using the library with variable buffer lengths enabled, in a scenario with CID and MFL.
Certain fields in the ssl context might be shifted in ssl_parse_record_header() when receiving a connection with CID, so they require a manual update after calling the generic mbedtls_ssl_reset_in_out_pointers().
This PR also adds a regression test which is run by all.sh.

I have introduced the requested changes. I'll also refactor the code, but in a different PR, if you don't mind, @gilles-peskine-arm.

CI fails due to whitespace checks:
* check_files: Check: file sanity checks (permissions, encodings)

* Tue Jun 16 14:07:38 UTC 2020

******************************************************************

Trailing whitespace:

tests/ssl-opt.sh: 2215, 2228

The other code changes look good, although there's still the misleading reference to all.sh in the commit message (not a gating issue). I agree any refactoring can happen in a subsequent PR.

Fixed formatting, thanks for letting me know. The commit message only mentions all.sh, not a specific configuration, so I think it's fine.

Thanks for the prompt responses!


Add scroll restoration when navigates back

This PR fixes #3277 issue.
I refactor the Home component to make the react-router-dom ScrollRestoration work. There are some useless re-rendering that makes the ScrollRestoration not work.
Here's the demo
https://www.veed.io/view/d774a53a-fcd9-4c9f-afe2-d145e204dcc2?panel=share

Sorry, I've just noticed there's a bug. When we navigate back from memo detail and the Home page already has more than 1 page of memos in the store (I mean the zustand store), the next page token is reset.
We need to move it out to the zustand store so it doesn't reset when navigating back.

I encountered many problems because we reused the same store on multiple pages (the homepage, the explore page, and others).
I think we can do a workaround. By using full page reload when navigating pages between home, explore, timeline, and other pages that show memo lists and use the same store, we can prevent the bug and enable the scroll restoration feature.


Use Confluent platform version 5.3.0

Use the latest Confluent platform version to prevent some security issues

We need this PR to be merged in order to use a newer version of confluentinc/cp-kafka-connect-base that has fewer vulnerabilities.

Switched to openjdk:11-jre-slim


feat: Implement release functionality

Description
This Pull Request introduces the release functionality to the project. It encompasses all changes and improvements developed in the feat/release branch.
Changes

Implementation of release logic
Update of versioning mechanisms
Addition of release-related tests
Documentation of new release processes

Review
Please check the following points:

[ ] Code quality and adherence to coding standards
[ ] Functionality of release features
[ ] Completeness of tests
[ ] Accuracy of documentation

Additional Information
This PR prepares the project for future release cycles and enhances the overall release process.

Will add contents to readme and then set up for merge


bmenu in manjaro i3 openrc 686 liveCD

Hi. Couldn't find an e-mail for you or the project, so here's an initial dump of my bmenu experience notes when evaluating the liveCD for manjaro i3 686. I really did not want to initially post any of this as a bug report before emailing you because I'm brand new to i3, and maybe some of what I'm experience may plausibly be an i3 or other issue; however, some clearly seem to be bmenu-specific
bmenu

says it corrects the system time and timezone, but it doesn't
update the time displayed on the panel
selecting 1 for hardware, or 2 for display, surprisingly goes to the network to  synchronize the package database, and then asks me whether I want to install, and all that without telling me what it wants to install
selecting 6 for network gets response "wrong option" in red,
followed by "wait and try again later"
selecting 4 for appearance, and then 5 for toggle dark theme, gets
response "unknown option" in red, followed by "wait and try again
later"
for choosing the shell or the display manager, it would be helpful
were there some indication of the current state.

Best to respond to me at: boruch_baum @@@at@@@ gmx ...com...

Hi!
Please open separate issues for different cases.

time management is actually done by different package. You can open up issue there. Does tge time update on i3panel after you relogin?

this installs the necessary packages for the task ( mhwd-tui and brandr respectively). They are very small. Notification about it is a good idea. I thought pacman would give you the names, but appearantly it does not.

sounds like a bug. I'll look into it.  Cause this option uses a systemd command to determine network manager first.

4&5) should not happen, sounds like a bug. I'll look into it.

good idea.

That was quick! Thanks for the quick reply.
On 01/03/2016 08:24 PM, Chrysostomus wrote:

Hi!
Please open separate issues for different cases.
Sure thing.

time management is actually done by different package. You can open up issue there. Does tge time update on i3panel after you relogin?
I'm still busy with the eval, but when I get to a point where I do
logout and re login. I'll make note. Do you know offhand the name of
that other package?

Wait. I just tried "restarting i3 in place" using mod+shift+r, and the
time is now displaying correctly.
Are you sure I should file this with the time management package? I have
no idea of the internals, but if your package is updating stuff, should
it be doing a config reload/restart, or does the environment depend upon
each package getting notified when a config file is modified?

this installs the necessary packages for the task ( mhwd-tui and brandr respectively). They are very small. Notification about it is a good idea. I thought pacman would give you the names, but appearantly it does not.
My security consciousness gets me concerned that I'm not clearly warned
in advance when a program attempts to go to the network. The current
setup doesn't ask my permission before going out over the network to
sync packages.

sounds like a bug. I'll look into it.  Cause this option uses a systemd command to determine network manager first.
Yes, I'm running the openrc version. In fact, that's the reason I
switched to manjaro from debian. When debian adopted systemd, I was one
of those who bailed. I've been using manjaro-openrc with xfce for the
past few months, and have been reasonably happy; when I saw the i3
release announcement, I thought I would check out your spin.

4&5) should not happen, sounds like a bug. I'll look into it.

good idea.
Glad to be of some help.

So, in summary: I'll file 2-5 as separate bugs, 6 as an enhancement
request, and for 1, you'll update me if you know the other package name,
or if you want to do something like have bmenu "restart i3 in place".

Reply to this email directly or view it on GitHub:
https://github.com/Chrysostomus/bmenu/issues/6#issuecomment-168562708

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0

If it works after reloadong i3, it is feature, not a bug. It is a small bash script and cannot support live reloadong on every enviroment. Name of the package is timeset.

Thanks. I'll drop the issue, then.
On 01/03/2016 09:32 PM, Chrysostomus wrote:

If it works after reloadong i3, it is feature, not a bug. It is a small bash script and cannot support live reloadong on every enviroment. Name of the package is timeset.

Reply to this email directly or view it on GitHub:
https://github.com/Chrysostomus/bmenu/issues/6#issuecomment-168567741

--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0


Azure AD Integration Not Working - HTTP 400 Bad Request

System Information
Rancher versions:
rancher/server: Replicated on both v1.5.5 and v1.5.10
Infrastructure Stack versions:
N/A
Docker version: (docker version,docker info preferred)
rancher@rancher-controller:~$ docker --version
Docker version 17.05.0-ce, build 89658be
rancher@rancher-controller:~$ docker info
Containers: 6
 Running: 1
 Paused: 0
 Stopped: 5
Images: 5
Server Version: 17.05.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 51
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-78-generic
Operating System: Ubuntu 16.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 6.804GiB
Name: rancher-controller
ID: 7J64:JVNR:BX43:4AFB:HMDW:ZW3X:2O6N:I7FN:MBE4:3CLF:SVI6:2N2W
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

WARNING: No swap limit support

Operating system and kernel: (cat /etc/os-release, uname -r preferred)
rancher@rancher-controller:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.2 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
rancher@rancher-controller:~$ uname -r
4.4.0-78-generic

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Azure
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node, no hosts.
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
N/A
The Error
Steps to Reproduce:
1) Create Application Registration in Azure
-Navigate: Azure Active Directory -> App Registrations -> New Application Registration
-Application Type: Native
-Sign-on URL: rancher.domain.io
2) Configure Application Registration:
-Navigate: Azure Active Directory -> App Registrations -> Your App -> Required Permissions -> Windows Azure Active Directory API
-Select all Delegated Permissions
-Save your changes & Grant Permissions to the API
3) Create Active Directory Service Account
-Navigate: Azure Active Directory -> Users and Groups -> All Users -> New User
-User name<EMAIL_ADDRESS>-Groups: Domain Group
-Directory Role: Service administrator & User Administrator
-Save
-Navigate: portal.azure.com -> Sign in as new user and set a new password
4) Configure Rancher Server
-docker run -d --restart=unless-stopped -p 8080:8080 rancher/server:v1.5.10
-Navigate: https://ip.add.re.ss:8080/v1/settings/logback.root.level
-Click Edit and replace INFO with TRACE
-Show Request -> Send Request
-Restart Rancher Server: docker restart >containerid<
-Connect to the Rancher Server container: docker exec -it >containerid< bash
-Tail the debug log: tail -F /var/lib/cattle/logs/cattle-debug.log
5) Configure Azure AD
-Wait 1 minute and Navigate: https://ip.add.re.ss:8080/
-Navigate: Admin -> Access Control -> Azure AD
(Sidenote: The next two fields should be renamed in your application/documentation. It is very confusing since Application ID appears above Object ID on Azure, but Tenant ID appears above Client ID in Rancher. And they're named differently too...)
-Copy Object ID from Azure Application Registration to Tenant ID in the first field.
-Copy Application ID from Azure Application Registration to Client ID in the second field.
-Insert domain into third field.
-Provide<EMAIL_ADDRESS>credentials to fields four and five.
-Provide personal user account credentials to fields six and seven.
-Click Authenticate with Azure
6) Experience Login Failure
-Navigate: http://ip.add.re.ss:8080/login
-Open Developer Console in your browser to view HTTP errors
-Try and sign in as any user in the domain, or even your service account
-Rancher verifies credentials are correct, appears to login, and loops back to the login page. Invalid credentials are always rejected. Valid AD credentials are always accepted for lack of a better word.
Results:
Login is accepted by Rancher and then immediately jumps back to the login prompt. Rancher must be able to perform an identify lookup in Azure AD because it can tell if credentials are correct or not. Incorrect credentials won't be accepted by the form and it will simply say Username or Password Incorrect
Several HTTP error occur at different times. 400, 401, and 500.
Several 400 errors in trace logs. Predominantly Failed to get Azure user account info by Id. io.github.ibuildthecloud.gdapi.exception.ClientVisibleException: Error from Azure: 400 and
Response from Azure API: HTTP/1.1 400 Bad Request
Error received from Azure: null
Error Description received from Azure: null
Got error from Azure. io.github.ibuildthecloud.gdapi.exception.ClientVisibleException: Error from Azure: 400

Log Files and Screenshots

Developer Console post login attempt: http://i.imgur.com/WMJjStl.png
Debug Trace while Enabling Azure AD Access Control: https://goo.gl/RpCPDs
Debug Trace during Login Attempt: https://goo.gl/6bJF9q

Possible issues

Azure might be rejecting requests from servers without valid SSL certificates?
Possible misconfiguration on the Azure AD side? I have tried this as both the service account I created here and as an AD user that is an owner in the subscription

Attempted Troubleshooting steps

Have tried using a user account that is an Owner of the Azure subscription instead of a service account. Still receive 400 errors.
Have tried all of this using SSL termination behind an NGINX reverse proxy as well. This issue was made with an example running over HTTP. However, I first experienced this issue on my Rancher Server that was using SSL Termination behind an NGINX reverse proxy though. SSL Labs gave it a A- grade as I was using the full chain and everything.
Reached out in Public slack channel for support.
Read countless Google Search results via variations of this query: https://goo.gl/hBrqZs

Please help. :(

I've noticed at least two other similar issues to this one on the Issue Tracker. Although I believe that both of them are unique in that they are using Multi-Factor Authentication and we are not. So I thought it would be better to create a new issue rather than commenting on theirs.
https://github.com/rancher/rancher/issues/5772

Is it possible that the underlying Linux host that the Rancher Server container is running on must be joined to the domain it's trying to authenticate against?

@tfiduccia Is this something you can check/verify?

@zimmertr can you try few requests to Azure AD using a REST tool (like Advanced Rest Client tool for Chrome)? We would know if the issue is outside of Rancher or not, depending on if these requests error out/work.

Login to Azure login using Advance rest client tool and check what response you get from Azure.
Here is a screenshot of what the request should look like, you would need to provide the clientId, username and password and URL encode the special characters if any.

If the login works, copy the access token you get back from Azure and use it to search for your user and group details as below (This is the request that is seen to be failing in Rancher logs):

a. To search your user:

Do a HTTP GET request to
https://graph.windows.net/(tenantId)/users/feb4e488-6faa-4852-91c2-3a80f13ecbda?api-version=1.6
Set the following request headers:
Accept: application/json
Authorization: Bearer <access_token received in login above>

b. To look for your group

Do  a HTTP GET request to
https://graph.windows.net/(tenantId)/groups/321cf82a-e6fa-4349-87b1-c8fce7298e47?api-version=1.6
Set the following request headers:
Accept: application/json
Authorization: Bearer <access_token received in login above>

And Check what response you get for the user/group search.

Hi @prachidamle , thank you very much for your reply. I performed the POST and I did receive an error invalid_grant. What exactly is graph.windows.net? I noticed it was passed as a string during the POST. Was I supposed to edit this to something specific on my end? Sorry, I'm still relatively amateur at working with REST APIs.
{
"error": "invalid_grant",
"error_description": "AADSTS50034: To sign into this application the account must be added to the graph.windows.net directory. Trace ID: 00a2b0b8-f9c5-46d4-b53f-e57da11e1700 Correlation ID: af255cde-08ae-4418-85c6-454af127efbf Timestamp: 2017-05-31 14:46:08Z",
"error_codes": [
  50034
],
"timestamp": "2017-05-31 14:46:08Z",
"trace_id": "00a2b0b8-f9c5-46d4-b53f-e57da11e1700",
"correlation_id": "af255cde-08ae-4418-85c6-454af127efbf"
}

Hi @prachidamle, thank you very much for your response. It has been incredibly valuable to me. It appears that the error is that the service account that I have created has not been added to the graph.windows.net directory. I've done some research on the Graph API and I understand that it provides access to AD via Odata endpoints.
{
"error": "invalid_grant",
"error_description": "AADSTS50034: To sign into this application the account must be added to the graph.windows.net directory. Trace ID: 00a2b0b8-f9c5-46d4-b53f-e57da11e1700 Correlation ID: af255cde-08ae-4418-85c6-454af127efbf Timestamp: 2017-05-31 14:46:08Z",
"error_codes": [
  50034
],

Perhaps there is still an issue with fully understanding how this all fits together, but isn't the Graph API a tool used to perform lookups against AD? Is the error misleading me into thinking that I have to add some sort of Graph role to my service user account? Google isn't helping a whole lot with this unfortunately, so I'm sorry for my naivety.

Hi @prachidamle, thank you very much for your response. It has been incredibly valuable to me. It appears that the error is that the service account that I have created has not been added to the graph.windows.net directory. I've done some research on the Graph API and I understand that it provides access to AD via Odata endpoints.
{
"error": "invalid_grant",
"error_description": "AADSTS50034: To sign into this application the account must be added to the graph.windows.net directory. Trace ID: 00a2b0b8-f9c5-46d4-b53f-e57da11e1700 Correlation ID: af255cde-08ae-4418-85c6-454af127efbf Timestamp: 2017-05-31 14:46:08Z",
"error_codes": [
  50034
],

Perhaps there is still an issue with fully understanding how this all fits together, but isn't the Graph API a tool used to perform lookups against AD? Is the error misleading me into thinking that I have to add some sort of Graph role to my service user account? Google isn't helping a whole lot with this unfortunately, so I'm sorry for my naivety. My service user has the Directory Role Limited Administrator with the subroles Service Administrator and User Administrator. Beyond this, I'm not sure what needs to be done.
Thank you again for your help, I really appreciate it. Rancher is a very awesome organization.

@prachidamle
Hi, okay so I've managed to obtain an Access Token via Step 1) from your instructions. However, when I try and perform a GET via Step 2A) or Step 2B), it bombs out with Invalid domain name in the request url.
I've replaced the tenantid portion of the URL. Nothing else should be mandatory, correct? Where do we go from here?

@zimmertr I'm experiencing the same problem. Have you been able to fix this?

I'm fairly certain this was user error pertaining to the application not having requisite permissions to perform read actions against the directory. Closing this ticket as it is no long relevant and appeared to be my fault to begin with.


unpin docplex

Summary
docplex 2.24.231 issue #445 is fixed by 2.24.232.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4332

Relevant Lines:
4699

💛  - Coveralls


WIP: Adding initial Vaxrank (detailed) docs for ReadTheDocs integration.

Coverage decreased (-1.7%) to 86.486% when pulling afd8aa98293dd374a640e23a561ea4da33a57bb5 on add-docs-for-rtd into 3331def003eebfaf50ceb39116eb645d48cab5eb on master.

Coverage decreased (-1.5%) to 86.637% when pulling afd8aa98293dd374a640e23a561ea4da33a57bb5 on add-docs-for-rtd into 3331def003eebfaf50ceb39116eb645d48cab5eb on master.


usbtmc error on Raspberry Pi 3

I am trying to install the usbtmc package on a Raspberry Pi 3. I extracted the package and used sudo python3 setup.py install in the terminal window to install, and it was successful. Now I am trying to run this bit of code:
import usbtmc
instr = usbtmc.Instrument(0x2a8d, 0x5c18)
print(instr.ask("*IDN?"))
I am receiving the error:
AttributeError: 'Endpoint' object has no attribute 'clear_halt'
So I think something might be wrong in the way I installed it? Any help is appreciated.

What version of pyusb do you have installed?

Here are the links from where I downloaded pyusb and libusb:
http://sourceforge.net/projects/pyusb/
http://www.libusb.org/wiki/libusb-win32
So I have pyusb 1.0.0

Are you sure that you have 1.0.0 installed?  What's the output of pip show pyusb?


PrimeNumbers.cs does not work

PrimeNumbers.get(8) returns 4, which is obviously incorrect.
Caused by int n = 8*sizeof(ulong)/sizeof(ulong);

Besides some other minor errors, the major error was actually in the loop logic.


Run bdb v0.9.1 as a pod in k8s

This PR include the config file to run BDB+RDB (as in v 0.9.1) in a single pod. It uses statefulsets to expose them as services to the external world.
Further plan of action is to split this pod to contain two images: bdb + rdb/mdb.
That will come after this is merged so that we can keep track of the evolution in case we need to refer to it.

Codecov Report

Merging #1240 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1240   +/-   ##
=======================================
  Coverage   96.73%   96.73%
=======================================
  Files          49       49
  Lines        2300     2300
=======================================
  Hits         2225     2225
  Misses         75       75

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 6702ad1...64f4afb. Read the comment docs.

Thanks @krish7919, I'll test this out with the PersistentVolumeClaim I created earlier and add some docs about how to do all that: I'll add those changes & docs as commits on this branch/PR.

@krish7919 - We're exposing some sensitive ports here, e.g. MongoDB's port 27017 and RethinkDB's ports 29015 & 8080. We need to be careful to safeguard them somehow.


Complete Material UI on main page (SWOT Cards)

Checkout https://react-md.mlaursen.com/. Source: https://www.reddit.com/r/reactjs/comments/5p1rin/whats_the_best_way_to_use_material_design_with/

See also:

https://ant.design/docs/react/introduce
https://hackernoon.com/the-coolest-react-ui-frameworks-for-your-new-react-app-ad699fffd651


Feature: More granular pay offer endpoints

Feature Description
In addition to pay-offer, which completes the full offer flow when sending a BOLT12 payment, we should have two other endpoints that offer a little more granular control when paying an offer.

Get_invoice would, when provided an offer, get an invoice from the offer and return it.
Pay_invoice would pay the invoice it's provided with.

This will require refactoring the pay_offer method on the offer handler. I'm imagining creating two methods of offer handler (get_invoice and pay_invoice) that mirror the above endpoints. Then we'd call these two methods in pay_offer, instead of clumping everything together in pay_offer.

I can take this one!
Is a bit bigger than the others, so i'll do a draft to collect early feedback

I can help you with testing and feedback on this one @mauricepoirrier

@mrfelton cool tx! I'll ping you 🙌🏼

Closed by #131.


reinstall files weren't properly created

[root@io-install ~]# ls -la /var/www/provision/reinstall/
total 8
drwxr-xr-x 2 apache apache 4096 Dec  9 15:55 .
drwxr-xr-x 4 root   root   4096 Nov 26 14:06 ..
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io1,gpu
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io2,gpu
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io3,gpu
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io4,gpu

tested ansible-playbook tools/reinstall_computes.yml, it works like it should
So the cause must be elsewhere

[root@io-install ~]# ls -la /var/www/provision/reinstall/
total 8
drwxr-xr-x 2 apache apache 4096 Dec  9 15:55 .
drwxr-xr-x 4 root   root   4096 Nov 26 14:06 ..
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io1,gpu
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io2,gpu
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io3,gpu
-rw-r--r-- 1 root   root      0 Dec  9 15:55 io4,gpu
Found it
reinstal script needs a fix

I've label it as bug but still it's a minor one

This has been fixed


Reorder JSON RPC calls and delete duplicates

Reorder the JSON RPC calls to make it more intuitive to find them.

Order more consistently for discv5, history and state
Order related calls close to each other
Delete some duplicate calls: portal_*Accept and portal_*Content

I found it sometimes difficult to figure out which call I'm looking at / looking for. Hopefully this improves it a bit.
Aside from that, I'd be fine with removing all the Send versions of the calls. Fluffy does not support them as they are difficult to implement and would require quite some refactor. I don't see a good use case for them either. If other clients have the same view on this, it would make the spec also smaller / easier.

Nice! I'm in favor of removing all send endpoints, to minimize confusion and complexity. Not sure about the use cases either.

Cool, I'll drop that in a separate PR not to hold up this one.


Flappy Bird Game

Project title
Bird Fly Game
Project Description
Bird Fly Game
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript

assign @gurjeetsinghvirdee

Isme aur flappy bird me kitna fark hai?

Isme aur flappy bird me kitna fark hai?

Bhai same hai... Mujhe naam hi nhi yaad aa rha tha , issue banata waqt... Abhi change krta hu naam😂

Already a Flappy Bird is there with HTML,CSS,JS

Already a Flappy Bird is there with HTML,CSS,JS https://github.com/khushi-purwar/WebDev-ProjectKart/tree/master/Flappy Bird Game Using Javascript

Mine is entirely different, atleast look at it once, before closing

Already a Flappy Bird is there with HTML,CSS,JS https://github.com/khushi-purwar/WebDev-ProjectKart/tree/master/Flappy Bird Game Using Javascript

Mine is entirely different, atleast look at it once, before closing

Kindly add some references images...by which I will judge yours ..You haven't added any images or description related Your issue

Already a Flappy Bird is there with HTML,CSS,JS https://github.com/khushi-purwar/WebDev-ProjectKart/tree/master/Flappy Bird Game Using Javascript

Mine is entirely different, atleast look at it once, before closing

Kindly add some references images...by which I will judge yours ..You haven't added any images or description related Your issue

i will send a pr in an hr, kindly check back then.

Already a Flappy Bird is there with HTML,CSS,JS https://github.com/khushi-purwar/WebDev-ProjectKart/tree/master/Flappy Bird Game Using Javascript

Mine is entirely different, atleast look at it once, before closing

Kindly add some references images...by which I will judge yours ..You haven't added any images or description related Your issue

i will send a pr in an hr, kindly check back then.

okayy either you can dm me on discord

Already a Flappy Bird is there with HTML,CSS,JS https://github.com/khushi-purwar/WebDev-ProjectKart/tree/master/Flappy Bird Game Using Javascript

Mine is entirely different, atleast look at it once, before closing

Kindly add some references images...by which I will judge yours ..You haven't added any images or description related Your issue

i will send a pr in an hr, kindly check back then.

okayy either you can dm me on discord

sure


build: upgrade to bazel 3.0.0

Signed-off-by: Lizan Zhou<EMAIL_ADDRESS>

Just for my own knowledge, how come https://github.com/fweikert/bugs/issues/628 doesn't actually break Envoy? eg https://github.com/envoyproxy/envoy/blob/4e1f9f95618ca354b255fb207a5a6e3097d687d0/bazel/BUILD#L238

FWIW, I've been compiling Envoy on Bazel 3.0 since it was released including test runs without issues apart from warnings (x86_64 Linux and MacOS and aarch64).

@asraa Looking at bazel issue https://github.com/bazelbuild/bazel/issues/8622 seems the flag isn't flipped in 3.0 but delayed to 4.0.
@mattklein123 I believe some of them are still valid issue but just delayed to a later version. I'll go over them to see whether it is fixed or not.


fix: sync file list expected by cache with Lake changes

The .c.trace files no longer exist, see https://github.com/leanprover/lake/commit/6499494befc24e388d12f3d9411f99aae0769491#diff-43ead6410f2dcb31276401eb765b8ada18c8e288626dfa8d6123cfab46961e7aL81-L83.

Let's see if it uploads something now

@arthurpaulino Is there any conceivable scenario where allExist failing should not result in a fatal error?

I assume the idea is to allow uploading a cache for an incomplete build that has successfully built some files? Either way, that behavior sounds like it should be hidden behind a flag.

I assume the idea is to allow uploading a cache for an incomplete build that has successfully built some files? Either way, that behavior sounds like it should be hidden behind a flag.

This is really important if you need to edit a low-level file while porting a new file, for example.

Ah good point; in CI you want a partial cache to be uploaded when a PR build fails, so that you don't have to start from scratch.

bors d+
Feel free to merge if you don't want to wait for further feedback. No need to wait for the remaining CI, since the cache upload is already done.

Since there is no hurry, I'll leave taking a final look to @gebner

in CI you want a partial cache to be uploaded when a PR build fails, so that you don't have to start from scratch

For that purpose, I believe it would be better to say "upload a module's files iff the .olean file exists". This logic would be compatible with producing optional output files such as with #3575 or #3404 (/cc @semorrison).

Well, I guess we're preventing new files from being uploaded, so let's get this merged. My first bors command, yay.
bors r+


Major redesign

These are the collective changes we did for getting a working collection of metrics from multiple servers.
Sorry for the patchbomb, but it had to go fast.

Implement multiple new collectors for ethernet port statistics. RX/TX/port stats
All data collection is now done in a seperate thread and only the last results are reported back on request.
We are already over 3.3 mb of metrics and run into multiple timeouts from telegraf and very unstable behaviour.
Now the socket pushes out over 1.1 gb/s in metrics.
The current design could be done a bit better with job queues but this can be done later
Better handling of failures through wrapping of query methods
Generic query class for gauge metrics
Proper fix for illegal password characters
setup.py for installation
logging framework with debug levels instead of printing

@poelzi I liked it 👍 I will test.

I also changed the way metrics are reported in accordance with our discussion of the server monitoring team.
Metrics are only reported once after collection.

@mithunmgore ping

@viennaa Please check the PR https://github.com/sapcc/ucs-exporter/pull/9/ for addressed comments and new collectors


Support encoded checkout

Note: opted to only pass key- and valueEncoding rather than passing through the ...opts to the Hyperbee constructor because I'm not sure if it makes sense to support (all) other options. Can adapt

makes a lot of sense


fix: remove FF edge_functions_invalid_config_throw

Is at 100%

FYI: The only functions that do throw now are nextjs API routes, see https://netlify.slack.com/archives/C01TKAEBP3Q/p1683277444878149