sfdx force:source:retrieve -m CustomMetadata fails

Summary
sfdx force:source:retrieve -m CustomMetadata fails against non-scratch orgs
Steps To Reproduce:
Create a non-scratch org and auth to it
sfdx force:source:retrieve -m CustomMetadata
I can't reproduce it with a scratch org because the command works against scratch orgs.
Expected result
Source retrieves
Actual result
$ sfdx force:source:retrieve -u platformers -m CustomMetadata
ERROR running force:source:retrieve:  The "path" argument must be of type string. Received type object
Additional information
Fails against both production and full sandbox
Also fails when trying to pull using the OrgBrowser in vscode...same command underneath in the Output
sfdx-cli/7.61.0 darwin-x64 node-v12.14.0
$ sfdx plugins --core
@mshanemc/sfdx-migration-automatic 0.3.1 (link) /Users/shane.mclaughlin/code/sfdx-migration-automatic
@oclif/plugin-autocomplete 0.2.0
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.7.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/analytics 0.17.0 (link) /Users/shane.mclaughlin/code/sfdx-analytics-plugin
@salesforce/lwc-dev-server 2.2.0
├─ @oclif/plugin-help 2.2.1
└─ @oclif/plugin-update 1.3.9
@salesforce/sfdx-diff 0.0.6
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.7.1 (core)
evergreen 0.22.10
└─ evergreen-build 0.11.1
generator 1.1.2 (core)
salesforcedx 48.19.0
├─ @salesforce/sfdx-plugin-lwc-test 0.1.5
├─ custom-metadata 1.0.1
├─ salesforce-alm 48.20.0
└─ salesforcedx-templates 48.18.0
sfdx-cli 7.61.0 (core)
shane-sfdx-plugins 4.37.1 (link) /Users/shane.mclaughlin/code/shane-sfdx-plugins
OSX 10.15.5 (19F101)

I got this to work--it looks like if the cmdt object is in a packageDirectory that isn't the default, and the pull tries to put the CustomMetadata into a different packageDirectory that is the default, you get this error message.

This is no longer reproducible with the latest version of the CLI

How come using this command works sfdx force:source:retrieve -m CustomMetadata but if I specify a wildcard in a package.xml and do sfdx force:source:retrieve -x package.xml I get this error The specified metadata type is unsupported: [Custom?Metadata]

Note CustomMetadata works but not Custommetadata (case sensitive).

In package.xml I add:
<types>    <members>*</members>    <name>CustomMetadata</name> </types>
This is what the Salesforce documentation suggests. Yet I get the error:
ERROR running force:source:retrieve:  The specified metadata type is unsupported: [CustomMetadata]
Using the command sfdx force:source:retrieve -m CustomMetadata as suggested by @banderson5144 here, it works.
This doesn't make much sense...

@alexferrari88 Using:
<types>    <members>*</members>    <name>CustomMetadata</name> </types>
works for me. It exports all metadata.
It would have been better for me to be able to specify the API name of the particular metadata object, or use some sort of filtering, but that doesn't seem possible.
The only other package.xml configuration that worked was to pull out specific metadata records by specifying their unique fullName. e.g.:
<types>    <members>MyCustomMetadataObject.uniqueMetadataRecordName</members>    <name>CustomMetadata</name> </types>


Fix miss spell typo

I have signed it!
On Sun, Jul 10, 2016 at 2:24 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/getting-started-java/pull/98#issuecomment-231611797,
or mute the thread
https://github.com/notifications/unsubscribe/ABJP6M88m4Gpituk5T-uW4O56pwSibF8ks5qUWMbgaJpZM4JI6-Z
.


Changing blobstore password is not possible

The agent writes the file /var/vcap/bosh/etc/blobstore-<TYPE>.json once and never checks if the settings changed afterwards. So rolling blobstore passwords or even changing the blobstore is not possible.

does bosh deploy --recreate not work for you?
Sent from my iPhone

On Mar 4, 2016, at 7:15 AM, Marco Voelz<EMAIL_ADDRESS>wrote:
The agent writes the file /var/vcap/bosh/etc/blobstore-.json once and never checks if the settings changed afterwards. So rolling blobstore passwords or even changing the blobstore is not possible.
—
Reply to this email directly or view it on GitHub.

Sure, but re-creating 150+ VMs when I'm changing the blobstore password seems a bit much.


fix(plugins/plugin-kubectl): don't retry file fetches so many times i…

…n headless mode
Fixes #7225
git cherry-pick 2867ecf8aa1e9069e764827484836caf2953a4a7
[cherrypick10 e0e8fd202] fix(plugins/plugin-kubectl): don't retry file fetches so many times in headless mode

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[x] 🐛 Bug fix
[ ] 💅 Enhancement
[ ] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

This has received extensive testing on the dev branch.
/lgtm


the source r no longer exists

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty-updates/main/source/Sources  Hash Sum mismatch

Are you sure this is a problem with ctf-tools? What are you trying to install?


Typography fixes

Reset typography styles to medium.css, go from there.

Updated fonts
Adjusted some sizing
Polished link hover effect
Fixed mobile link issues
Etc

Etc

Continued to tweak color scheme

Also: addresses #45


"Ambiguous" character highlight

Would it be possible for the extension to disable VSCode's "ambiguous character" highlighting for primitives?
When the "Unicode Highlight: Ambiguous Characters" setting is enabled, VSCode highlights some of the characters used by primitives:

Currently, you can add the following option to your settings.json to disable all of such highlighting in Uiua files:
"[uiua]": {
  "editor.unicodeHighlight.ambiguousCharacters": false
}

However, this is inconvenient and disables highlighting in strings, which might be undesirable for some.

That's funny. In developing Uiua, I didn't notice it highlighting those because I had already told vscode to disable highlighting them when I was picking the glyphs.
Fixed in d9ff6d8. Should be deployed soon.


Ensure transaction safety

See https://github.com/neos/Neos.EventSourcing/issues/141#issuecomment-333316451
Wrap ProcessManager lastAppliedSequenceNumber and state update into a single transaction
Without the two happening within a transaction, we potentially apply state transitions inside the PM multiple times.
Case:
event X comes in
PM updates state
crashes before updating lastAppliedSequenceNumber
-> catch up from the same event and reapply it after restart

I renamed this ticket from "Wrap ProcessManager lastAppliedSequenceNumber and state update into a single transaction" in order to turn it into an umbrella ticket for the transaction-related issues:
EventListener last applied event & state updates

To implement a "safe" EventListener (not only ProcessManager) getHighestAppliedSequenceNumber(), when*(), saveHighestAppliedSequenceNumber() must be wrapped in a transaction (as mentioned above).
Additionally there needs to be some kind of locking so that two processes can't interfere. SELECT ... FOR UPDATE is one option

Prevent multiple events with the same version
Luckily that is already guaranteed because of the unique key constraint in the events table. But we might want to wrap the corresponding exception (if two processes try to publish to the same stream "simultaneously") so that is easier to deal with – even though the risk of that is probably quite low
Exactly-once-delivery
We can't guarantee exactly once delivery (e.g. in ProcessManagers). We might be able to increase the chances that an event is processed exactly once using some kind of queue, but that is out of scope for this ticket

I didn't get as far with this as I planned originally, but I spend some more thoughts on this:
The following activity diagrams are hard to read, but I can use them as memory aid for further discussions:
Note: HSN = Highest Sequence Number
Catchup all events per Handler in one transaction:

(http://yuml.me/edit/f7ce7c6f)
One transaction per event:

(http://yuml.me/edit/694f60cb)
Questions:

Which of the above is better?
How to ensure a transaction-safe HSN if none has been persisted yet? (INSERT ..., SELECT .. FOR UPDATE is not transaction-safe)
Which class is responsible for which task?
Handle catchup and replay differently?
Reverse responsibility of HSN? (in the Framework by default, EL can "opt in" via custom interface)

I'd like to dig into this topic again, and I tried twice already, but it's really deep and I'm a bit out of it. I hope to find some time for deep diving into this sometime in the near future, but for the moment, that won't be possible.

@albe Thanks for your comment! The list above was more of a mental aid in order to be able to discuss this with others. In the meantime I have a working(tm) solution that allows multiple workers to work in parallel without blocking / re-applying the same event twice. But it needs cleanup and a better architecture.. I tend to create a new branch so that I can push my intermediate state more often...
Would be cool to have your input from time to time, it is greatly appreciated!

There are still some related issues (#245 for example), but the "AppliedEventsStorage" mechanism should be safe now!


Use http.ServeFile instead of creating it by hand

In
https://github.com/dcos/dcos-diagnostics/blob/b5f70d473bc00b613729d940dfba98f7d1395182/api/rest/bundle_handler.go#L230
we use http.ServeFile that is handling lots of config specific seetings
for us. We should do the same for cluster handler.

Codecov Report

Merging #140 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #140      +/-   ##
==========================================
+ Coverage   65.67%   65.71%   +0.04%
==========================================
  Files          30       30
  Lines        2884     2879       -5
==========================================
- Hits         1894     1892       -2
+ Misses        793      791       -2
+ Partials      197      196       -1

Impacted Files
Coverage Δ

api/rest/cluster_bundle_handler.go
63.41% <100%> (+0.55%)
:arrow_up:

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 eb3a182...c4a3002. Read the comment docs.


二次元都是辣鸡

二次元都是辣鸡

#已加入 Koishi Meme

圣地巡礼

This issue is worthless and meaningless, it is not recommended to reply in this issue. Thus, i am going to lock it.


How do i dispatch a router action from a component

Hello, i have been strugling to call a route programaticly without Link, but i don't know how to get the global store, in order to dispatch an event for the router like it says in this link:
https://github.com/reactjs/react-router-redux#what-if-i-want-to-issue-navigation-events-via-redux-actions
Sorry to have so many questions, i am loving this boilerplate but because there is no documentation i am triying to figurate a lot of things
Best Regards
Claudio

You can use dispatch of connected component, add push action to mapDispatchToProps :
import { push } from 'react-router-redux';  // import
import { bindActionCreators } from 'redux';
import { connect } from 'react-redux';
import Counter from '../components/Counter';
import * as CounterActions from '../actions/counter';

function mapStateToProps(state) {
  return {
    counter: state.counter
  };
}

function mapDispatchToProps(dispatch) {
  // Add following code
  return {
    counter: bindActionCreators(CounterActions, dispatch),
    push: bindActionCreators(push, dispatch)
  };
}

export default connect(mapStateToProps, mapDispatchToProps)(Counter);

Then use this.props.push in connected component.

Thanks for @jhen0409 's tip!
Nothing different between a web application and a electron application to dispatch a router action here, so please consult documentation at react-redux and react-redux-router repo.

Thanks! @jhen0409


Update windows-certification-portal.md to indicate Win32 desktop app certification is deprecated

@icnocop : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@icnocop : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@QuinnRadich : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Fixing golangci-lint errors across code base

Fixes #34
Proposed Changes

:broom: Clean up code to pass quality gates

As this is "only" about linting and the CI is happy, let's get this merged.
Thanks @cardil for taking care !
/lgtm
/approve


Salesforce Outbound Private Connect  Doesn't gets provisoned with Endpoint Service Name as Described in read.me file

Hello,
Thanks for writing how to in read.me file of this repo. I was trying to follow it and when i try to create Outbound Private Connect in Salesforce using Endpoint service name - "com.amazonaws.us-west-2.execute-api" it fails. Is there any other steps before creating the Outbound Private Connect in Salesforce. I've already created a interface endpoint in AWS.
Thanks,
Vish

Hi @vishwajeetkumar, can you share any more details around the failure?
One thing that does spring to mind is that you need to have Private Connect licensed in your Salesforce instance to be able to provision, is it failing to create or to provision?
Thanks


Improve logging of deployments

Currently inspector, api and INA all log as
"Deployment ironic ... : created", change this to log the actual name of the deployment

/test unit

/test ironic-operator-build-deploy-kuttl


react-native-debugger: 0.7.18 -> 0.7.20

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/react-native-debugger/versions.
meta.description for react-native-debugger is: '"The standalone app based on official debugger of React Native, and includes React Inspector / Redux DevTools"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/bin/React Native Debugger had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.7.20 with grep in /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20
directory tree listing: https://gist.github.com/9ed79b965816527f2a08ff31ee7b65ec
du listing: https://gist.github.com/e9b19263ab44b03e29d1f3534ef192ba

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout a1f77fbf9cbbbcba19b40d46a6bbf917907764d4 && nix-shell --pure -I nixpkgs=. -p react-native-debugger

cc @ma27 for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: react-native-debugger
Partial log (click to expand)

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

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

Success on x86_64-linux (full log)
Attempted: react-native-debugger
Partial log (click to expand)
  inflating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/natives_blob.bin
  inflating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/pdf_viewer_resources.pak
   creating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/resources/
  inflating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/resources/app.asar
  inflating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/resources/electron.asar
  inflating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/snapshot_blob.bin
  inflating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/ui_resources_200_percent.pak
 extracting: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/version
  inflating: /nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20/views_resources_200_percent.pak
/nix/store/m8qbi45nmp0k3kh8a3gbzfhayjq1fjbb-react-native-debugger-0.7.20

Success on aarch64-linux (full log)
Attempted: react-native-debugger
Partial log (click to expand)
  inflating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/natives_blob.bin
  inflating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/pdf_viewer_resources.pak
   creating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/resources/
  inflating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/resources/app.asar
  inflating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/resources/electron.asar
  inflating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/snapshot_blob.bin
  inflating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/ui_resources_200_percent.pak
 extracting: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/version
  inflating: /nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20/views_resources_200_percent.pak
/nix/store/cv3l8pjgj1n5w5blqnbjdfdmqrr12zjb-react-native-debugger-0.7.20


Error with Lucee <IP_ADDRESS> on Commandbox 5

When trying to create a spreadsheet I am seeing the following error:
Could not initialize class org.apache.poi.ooxml.util.DocumentHelper when running the following:
loc.spreadsheet = New spreadsheetLib.Spreadsheet(); loc.workbook = loc.spreadsheet.workbookFromQuery( data=loc.qReportData, xmlFormat=true );
Is there a jar missing in Lucee <IP_ADDRESS> or something in Commandbox?

Hi Dave. I have reported problems running the library on Lucee 5.3.5.x and it's likely this is what you're seeing.
As I put in that ticket's comments though, the issues appear to go away with a fix deployed in <IP_ADDRESS>.
The strange thing is that having just spun up another <IP_ADDRESS> Commandbox (5) server, I'm no longer seeing any issues with that version! The tests all pass.
Sorry, but I'm not sure what to make of it at the moment...

Thanks, I'll try some different versions of Lucee. I'm limited to what I can use at the moment. In the meantime I have dropped down to just using a csv file but will need to come back to an excel format at some point. At this stage I am seeing it when running Lucee on Commandbox. Not sure about when I deploy to the beanstalk.

In production we're currently using Lucee <IP_ADDRESS> (on Tomcat) which has proved very stable despite being a SNAPSHOT. I've not had any problems running the library on it.


Trouble with some pages

Problem:
I can select all the pages around 10... but when I look at the list there are a couple of pages 2 or 3 that do not appear to generate the token... do you know why?
I will send a PR to add the video upload function!

It may happen due to role and permission issue of page. But actually i have no idea what is happening there. I have three pages. When i select all pages, all are there without any hassles.
Your are always welcome to add new feature of this package.


AppService Plan is not a prerequisite

This is not true:
An existing App Service application to which to grant key vault access. You can quickly create one by following the steps in the App Service documentation.

An Azure Function running on a Consumption Plan is enough to create a managed identity.
Recommend you add "...or an Azure Function" in there. Also recommend you change the left nav title of this topic to "Provide Key Vault authentication with a managed identity" (remove the words "App Service") as the URL slug (https://docs.microsoft.com/en-us/azure/key-vault/general/managed-identity) and title at the top of page (Provide Key Vault authentication with a managed identity) do not include (nor require) "App Service".

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

ID: aa0c5bd2-62b8-f0ba-b569-d54fe97c8a68
Version Independent ID: 95da0c67-d4bd-5e33-d1cf-c6ce9a4ff2f5
Content: Use an system-assigned managed identity to access Azure Key Vault
Content Source: articles/key-vault/general/managed-identity.md
Service: key-vault
Sub-service: general
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

@SeaDude
Thanks for your feedback! We will investigate and update as appropriate.

I was under the impression that an "App Service Plan" was a premium-only resource. After deploying an Azure Function using a "Consumption Plan", I now see that a Consumption Plan shows up as an App Service Plan in the portal (they are one in the same).
Disregard.
Thank you


Improve script class display in a create dialog

The idea comes from: https://github.com/godotengine/godot-proposals/issues/11238#issuecomment-2558096697
I tried to implement the feature and it did look better than simply removing the suffix.
Feature
Now each type from a script will get its suffix removed. Instead, a button with script icon will display at the end of the selection.
Hovering the mouse on the button will display the script path.
When you click it, the editor will jump to editing the script linked to the type you selected.

Say goodbye to irritating suffixes!

This looks like a nice improvement.
Looks like you are removing the suffix customization feature. If that's intended, popup_create_dialog() should be adjusted (and the method doesn't need to be experimental anymore I think?).

By adjusting the method I meant that you should remove the type_suffixes argument, because it does nothing after these changes.

Ofc I will remove that parameter from that method, but that is another pr.

Why though if this PR effectively removes the functionality.
You can keep the experimental flag on the method.

No, the compatibility is tracked only between stable releases. You can freely "break" it during dev period.

?

 You need to re-add it and push again.


CB-17746 Make environment's isUpgradeCcmAvailable internal endpoint a…

…vailable from UI
It was annotated with @InternalOnly which makes the call from UI impossible.
See detailed description in the commit message.

This is only request for 2.60 because of API breaking change and it's not required in the release right?


Support validation of profiles extending other profiles

Is your feature request related to a problem? Please describe.
New profile shave to be copied to extend existing profiles. But the DTR allows defining an "extends" attribute, which we could consider (we most likely do not do it yet).
Describe the solution you'd like
Validation should consider the extends attribute and merge the definitions (preferred) or validate accordingly.
Describe alternatives you've considered
Let people copy profiles, as it is currently the case.
Additional context

"Overriding" properties is then possible to some degree (e.g. change repeatability).
Could also be implemented for types, if the DTR supports it.

Check before starting the implementation:

[ ] Does the EOSC DTR allow inheritence?
[ ] Can we somehow use composition instead to avoid handling overriding issues?


Why is there a binary executable a the root of repo?

https://github.com/aspnet/Docs/blob/master/Code
/cc @danroth27

@pakrym Thanks! We fixed it.


FF version detection on AMO broken

Hi guys. My projects are killing me, almost no time for anything else. :(
IDK if someone already mentioned it here, but in case it didn't, here we go:
I have noticed that /* 4501  */ user_pref("privacy.resistFingerprinting", true); prevents AMO to detect Firefox version, at least version 57.
On FF 57 visit, for example, Cookie AutoDelete AMO page.
You will be unable to install that addon with a notice on that page: This add-on requires a newer version of Firefox (at least version 56.0). You are using Firefox 52.0.
Change privacy.resistFingerprinting to false and revisit/reload CAD AMO page.
Now you will be able to install it.
Maybe, this should be mentioned on Wiki.
Cheers

Hi, yes we are aware of it. There are 2 ways around this atm:

temporarily disable privacy.resistFingerprinting to install new addons from AMO
set privacy.resistFingerprinting.block_mozAddonManager to true and use an addon that can modify headers for certain websites, and configure it to send your real User-Agent for addons.mozilla.org.
If you don't set that pref to true WEs won't be able to modify headers on the restricted domain addons.mozilla.org (and they won't be able to inject content-scripts to modify the site either, fe. try to block an element with uBO - it won't work unless you change that pref to true)

You could also save the xpi file and install the addon manually

Damn! I totally forgot about the simplest solution lol. Thanks @2glops

Cannot see the forest for the trees
To say the idiom "cannot see the forest for the trees" means that a person cannot see the big picture because the focus is too much on the details.

I think I need a break. Wake me up when ESR52 is EOL xD

To add to what @2glops said, if you want to install SuperStop, for example:

Click on the "See all versions".
Click on "Download Anyway" next to "Version 0.2".
When prompted, choose to open the file using Firefox instead of saving it to disk.

Thx @fmarier, obviously there is even simplest solution. :)

I simply right click on the greyed-out "+ Add to Firefox" button, then I click on Copy Link Location and paste in the address bar.

All I've been doing is downloading from the version section same as Francois. This AMO needing a whitelisting (or other mechanism to version detect) was brought up over 10 months ago - someone should give that guy a medal, or a job
source

a built-in whitelist should be considered, eg mozilla AMO


continue on error is per step not per job

Copying https://github.com/simeonschaub/OptionalArgChecks.jl/blob/457488ef04ed68a37aff10af1cb3909f47a8230c/.github/workflows/ci.yml#L23-L37

Github knows https://github.com/actions/toolkit/issues/399


.NET: Non SCREAMING_SNAKE_CASE constant names are converted incorrectly

Godot version
4.0.rc4.mono (e0de3573f)
System information
Windows 10
Issue description
Constant names that are not in snake case are converted with an incorrect case in dotnet.
This happens, for example, with the constants in the ECS class in godex.
Example:
Name in gdscript:
ECS.BtApplyForces
Name in dotnet:
public const long Btapplyforces = 11;
Steps to reproduce

Have a non snake case constant in a class (like CamelCase)
Generate the mono glue
Check the name in dotnet

Minimal reproduction project
N/A

The name converter assumes constants follow the Godot naming convention. Changing this would result in breaking compatibility and we're late in the RC phase, so I don't think we'll want to change this until 5.0.

I see, thanks.
I'll work around that in the c# side, then.


Consider supporting base_namespace cmdline option for C# protobuf plugin.

Protobuf C# has recently introduced this: https://github.com/google/protobuf/pull/785.
For now, this is low priority feature.

I can take a look at this. Any pointers on where to start looking?

https://github.com/grpc/grpc/blob/5f5415eae3acb267155a22fa9b612d43c0659676/src/compiler/csharp_plugin.cc#L27

This has fallen below the team’s cutoff, however we welcome contributions from the community. Closing.


added a toggle for adjusting system nodes to be more label centric

A few folks on discord mentioned a similar desire to have an option to change the look of the node labels.   For our usage of wanderer, we really focus on updating labels to match our bookmarking scheme, that allows us to quickly navigate down long chains.   We don't really need to know the J code for a system, and increment numbers to indicate position in chain, and use letters for W space.
Here is an example of how a small chain might look with this setup

to enable/disable i added a checkbox on the map settings

I also made a small update to the readme, to help other people with using the devcontainer setup

I see only new setting was added, any logic to support it?

the logic for using it is in assets/js/hooks/Mapper/components/map/components/SolarSystemNode/SolarSystemNode.tsx -- nothing overly complicated, it just changes how things are displayed a bit

one more commit -- totally understand if you don't like this -- found some of the text hard to read
reorganized the code a little for clarity after my changes, and adjusted the text and spacing a little


Machine name issue (boot2docker vs default)

Thanks for this piece of software, it helped us a lot. I'm chasing an intermittent situation that might originate in this driver.
THE ENVIRONMENT

windows 7 x64, docker is installed and configured using this driver, our machine is called "default" and everything works, running 4 containers inside, using VMware Workstation 10 with default DHCP settings, manually configured some port forwarding rules
there is a startup batch file that calls the start.sh (.sh code copied from the vmwareworkstation driver readme): bash.exe --login -i start.sh docker login -u xx -p xx; docker-compose -f ~/xx/docker-compose.yml up -d

THE PROBLEM

sometimes after a system restart the start.sh gets stuck on docker-machine commands - last one "waiting for SSH"... it took quite some time to notice what's going on - docker cannot SSH to the machine, because VMnet8 network adapter has wrong IP address (169.254.x.x). Addresses from this range are used by Windows in case of network issues e.g. IP address conflict.
digging deeper, the VMware's DHCP table entries show that tere are 2 devices having the same mac address and IP, but different host name: one is called "default" and the other is called "boot2docker"

THE QUESTIONS
Now how did that happen? The start.sh uses $VM variable for setting the machine name. The variable is populated on this line: VM=${DOCKER_MACHINE_NAME-default}, meaning it's either the existing machine name from $DOCKER_MACHINE_NAME or "default".
There are 2 theories:

there is a bug in the stack somewhere that would fill the docker machine name variable with "boot2docker" string - either docker-machine or this driver or the .sh script
the name of the virtual machine is "boot2docker" initially and it gets replaced only later by some script, meaning our issues are based on random timing of the 2 events (setting the name and getting the address from DHCP)

Any ideas??

Given the date of this and that it was on Windows 7, ill close this issue. Sorry for not replying before. If you see this issue again, please open a new one.


terrible lagging on windows

i create a solution on windows with GTX1080-Ti.
when i try to run it, it lags terriblely. how can i make it fluently ?
thank u very much.

but it more fluently when i run the released version. 0.8.4

Hi @jianghe01.
Which client are you using?
Which is your question?
Can you reformulate it, please?
Also take a look at #485, #606


Update README.md with login and docs instructions

Per request to add some info on accessing the installed service ... the info should mention how the user can access the integrated help.

Thanks for your interest in palantir/palantir-cloudpak, @ecaudill! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.


min/max dimensions not bound to content when using "use-content-size" flag

When making a window with the "use-content-size" flag set, the "min-*" and "max-*" are still calculated with the full window size, not the content size. It would make sense for the "min-*" and "max-*" to match "width" and "height" in this case.

On what OS did you notice this?

On second look it appears this is a side effect of my app working around the bug in #1806. Sorry about that.


0.17.5 Changelog

Issue #, if available:
Description of changes:
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest govulncheck

/retest-required

/retest

/lgtm

/approve

/override govulncheck


未经授权披露专有漏洞 - 需要立即采取行动

亲爱的资源库所有者
我是 Linux 系统远程代码执行（RCE）漏洞的原作者和所有者，在未经我同意或不知情的情况下，该漏洞在本资源库中被公开披露，我特此致函给您。
这种未经授权的披露不仅侵犯了我作为原作者的权利，而且对全世界 Linux 系统的安全构成了重大威胁。我要求你立即删除这个版本库和任何相关的分叉。
此外，我坚持要求你就这一严重破坏安全和侵犯知识产权的行为向北京当局自首。不遵守这一要求将导致严重的法律后果。
我希望你立即就此事给予合作。

Title: Unauthorized disclosure of proprietary vulnerability - requires immediate action
Dear repository owner
I am writing to write to you as the original author and owner of a Remote Code Execution (RCE) vulnerability in Linux systems that has been publicly disclosed in this repository without my consent or knowledge.
This unauthorized disclosure not only violates my rights as the original author, but also poses a significant threat to the security of Linux systems around the world. I ask that you immediately delete this repository and any related forks.
Furthermore, I insist that you surrender to the authorities in Beijing for this serious breach of security and infringement of intellectual property rights. Failure to comply with this requirement will result in serious legal consequences.
I request your immediate cooperation in this matter.```


Migrate to most recent version of Weld

THis implies the infamous migration to jakarta.* namespace. Maybe it's a job for openrewrite

In fact, there is an important overlap between this and #299. Indeed, it seems like the remaining blocker for migration is the lack of a Deltaspike version compatible with Java 17. And it begins to be a real blocker, so I guess I'll have to find some radical solution.


Use datapacks for recipes, spells, etc.

Hi. I'd like to add custom recipes to dark touch but it's currently impossible. And a lot of stuff isn't accessible for modpack developers at all. I think that datapack support would open a lot of possibilities for modpack developers c:
These things could probably be in datapacks:

[ ] Custom researches
[ ] Custom altar empowering stuff
[ ] Touch of darkness recipes
[ ] Custom mystical signs
[ ] Custom runes
[ ] Custom chants
[ ] Custom rituals

Having KubeJS support would be nice too

Sounds cool, but the mod itself is barely usable, you can't even chant yet

Would probably be a good idea to migrate runes and research to be data driven once research is a bit more usable.
Rituals are a little harder due to their effects being more complicated than simply crafting (though I think occultism does custom rituals despite this, so could be possible). However, you can still make custom rituals with KubeJS using reflection (though they'd probably have to be registered at startup), if you want help with that just message me on discord.
Custom mystical signs might be kind of hard to make data driven, same with chants. Touch of Darkness doesn't work yet afaik, but that could be made data driven as well probably.

However, you can still make custom rituals with KubeJS using reflection

Yeah, yesterday I've tried to use KubeJS for everything mentioned and it worked. Would be cool to be able to do it without reflection though.

Touch of Darkness doesn't work yet afaik

It's working. There's just no way to get runes in survival and illwood is useless (illwood logs don't even drop)


[Feature request] Shapes: new shapes.py with classes

Describe the feature
Implement plotting of basic shapes:

Circle
Rectangle
Square
Triangle
...

Constructor:

Basic parameters for geometry and location
fill_color (can be None), edge_color, alpha, line_width, line_style (all of these in style files, colors follow color cycle)

Other useful methods:

Area
Perimeter/circumference
Vertices
get curve from edge? How to specify which edge?

Is there currently a (suboptimal?) way to do this?
Not unless you create a ton of different curves, and even then it's not simple

Arrows (single sided and double sided, curved if possible, etc.) would also be useful.


UX: cargo build rage builds each time

What were you trying to do
Install rage via cargo twice.
What happened
The build has happened. The package is recompiling even if there are no new changes.

If you're referring to cargo install rage, I believe this is caused by https://github.com/rust-lang/cargo/issues/8703. The rage package includes the rage-mount binary which is built when the mount feature flag is provided. There's unfortunately nothing I can do about this while retaining the ability for cargo install rage to optionally provide rage-mount.

Closing as nothing-to-do-here.


Unable to retreive cf clearance (connection closed)

Description
Hi! Since today at 4 p.m. my cf clearance is not renewed, the connection is closed, does this only happen to me? Have Cloudflare improved their protection?
Thanks
Full steps to reproduce the issue
Send a request to cf clearance scraper
Issue Type
No response
Operating System
Linux
Do you use Docker?
Docker

Same for me, seems like Clouflare updated something on their end...

yes, did you find a solution?


Possible missing causal masking for WKV kernel

Hi, I have been testing this code on a set of GPUs, and am getting some results that seem a little too good! Much faster training when compared to an equivilent GPT-2 model (please see attached loss plot).
On inspecting the code more closely it seems like the WKV kernel is missing the causal masking that is used in decoding transformers to stop the model from looking ahead in a sequence. I am new to the RWKV arch, so am not sure how to fix this, but could you take a look and see if my hunch is correct?
loss_compare_RWKV.pdf

Hi, thanks for testing this code. I would explain point by point:

good loss curve: actually, i think LR and optimizer have huge impact on the loss curve beside the model architecture. In the current implementation, following official implementation i didn't introduce dropout which may lead to overfitting to training set. For the optimization, the current code uses the same as nanoGPT.
faster training: this is not expected, on my side the training of rwkv is a little bit slower than that of GPT-2. I am using 8*v100 32G.
casual masking: the current code for training and single batch decoding doesn't need casual mask since WKV kernel is essentially an RNN. You could refer to this huggingface implementation which also doesn't use attention mask for now.

Hi, thanks for the quick reply.

I think the loss curves look to be levelling out at around the same loss as my GPT runs, which I suppose is reassuring (if a little disappointing!).
The training time per batch is around the same as my nanoGPT runs, but the loss decrease on RWKV was far faster per data item which is what surprised me. I updated the CUDA stack on my machine in between the GPT and RWKV runs which may have changed things, so will replicate my GPT 700M run when RWKV is done and see if they match up again.

I'll close this issue as it looks like this was me misunderstanding the RWKV arch. I will go read up on the theory for a bit longer!
To answer your question; I'm running this on 8x40G A100 machines. I can also confirm that bfloat16 is working well for me, so that can be ticked off your TODO list.


Use std::set for trait sets

Description
Closes #1339.
C++ has set operation algorithms. However, these only work for sorted containers. std::unordered_set is not a sorted container, and so (ironically) cannot use set operations.
Most of our prototyping has been done in Python, where set operations are a part of the core language, and we have used them extensively to compare and combine trait sets.
The main benefit of unordered_set is the better average-case time complexity. However, for small sets the difference in performance between std::set and std::unordered_set is negligible (and may even favour std::set). In practice, we haven't seen any large 100k+ trait sets in the wild, which is where we'd expect the performance difference to show up (see links in GitHub issue for details).
Clearly this is a breaking change. However, we do at least use a TraitSet alias everywhere, so as long as no downstream project is using std::unordered_set directly, or non-generic APIs, then source compatibility will be maintained.
We use the default pybind11 bindings for trait sets, which means the set is duplicated as a Python native set. So the Python core library (and hence downstream Python projects) are unaffected.

[x] I have updated the release notes.
[x] I have updated all relevant user documentation.

As expected, ABI diff check failed:
===== Checking ABI of libopenassetio.so.1.0.0 =====

Leaf changes summary: 62 artifacts changed
Changed leaf types summary: 1 leaf type changed
Removed/Changed/Added functions summary: 28 Removed, 5 Changed, 28 Added functions
Removed/Changed/Added variables summary: 0 Removed, 0 Changed, 0 Added variable

For reference, the "5 Changed" are methods where just the return type was changed. The  "28 Added"/"Removed" are where the method arguments changed.


fix the problem that offset in limit query for tiflash system tables doesn't take effect

What problem does this PR solve?
Issue Number: close #6747
Problem Summary: When query tiflash system tables from tidb, tidb will send query like select ... limit offset, 1024. And the query only stops when the num of return rows is less than length. However, the offset parameter is not repected by tiflash, and will always return the same result with any offset value. So if the system table has more than 1024 rows, the query will hang forever.
What is changed and how it works?
Port the implementation from https://github.com/ClickHouse/ClickHouse/blob/19.5/dbms/src/DataStreams/LimitBlockInputStream.cpp#L21
Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)

deploy a cluster and import data to make the tiflash system tables dt_segments with more than 1024 rows;
run the query select count(*) from information_schema.tiflash_segments and make sure it succeeds;

[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

Fix the problem that query on tiflash system tables may hang under large amount of data

Does this bug also affect the v5.x versions or only the v6.x versions?

Does this bug also affect the v5.x versions or only the v6.x versions?

It afffects all versions. But it seems there is no more minor version on v5.x.

/merge

/merge

Does this bug also affect the v5.x versions or only the v6.x versions?

After verification, it just affect the master branch.

Does this bug also affect the v5.x versions or only the v6.x versions?

After verification, it just affect the master branch.

OK, I think it is introduced by this PR: https://github.com/pingcap/tiflash/pull/6268


Update table of contents and remove repeated pulumi

Thank you very much @kbelokon, can we enhance by adding some action to automate this lint typos 🤔

Oh, this is interesting! We can use markdownlint. I've written a custom rule for it that catches duplicates within the same section.
I did it within the same section because, for example, Better Stack appears several times in different sections, and I think that's normal behavior and we don't want to count it as duplicates.
We can set up a GitHub action on pull requests that will go through the README.md and fail if something is wrong.
module.exports = {
    "names": ["detect-duplicates-in-section"],
    "description": "Rule that reports duplicate links within the same section",
    "tags": ["links"],
    "function": function rule(params, onError) {
        let linksInSection = new Map();
        let currentHeading = null;

        params.tokens.forEach(token => {
            if (token.type === 'heading_open') {
                currentHeading = token.lineNumber;
                linksInSection.clear();
            } else if (token.type === 'inline' && currentHeading) {
                token.children.filter(child => child.type === 'link_open').forEach(link => {
                    const href = link.attrGet('href');
                    const text = token.content;
                    if (linksInSection.has(href) && linksInSection.get(href) === text) {
                        onError({
                            lineNumber: link.lineNumber,
                            detail: `Duplicate link in section starting at line ${currentHeading}: [${text}](${href})`
                        });
                    } else {
                        linksInSection.set(href, text);
                    }
                });
            }
        });
    }
};

Oh, this is interesting! We can use markdownlint. I've written a custom rule for it that catches duplicates within the same section. I did it within the same section because, for example, Better Stack appears several times in different sections, and I think that's normal behavior and we don't want to count it as duplicates. We can set up a GitHub action on pull requests that will go through the README.md and fail if something is wrong.

Looks very cool idea, can you test it in your branch, if it works we can add it to the repo ?

Easy, I'll do it today or tomorrow

Works for me in PR. I made it so that it only checks in PR and only when .md files are changed. Do you think that's okay, or do we want to see a failed action when you push to the main branch?

Yes ideally, it should block from merging to main if it fails and to see the failed error
What do you think ?

Perfect @kbelokon  💯 🥇


Index expressible-by-literal expressions.

When a value is initialized or coerced for a type that conforms to one of the ExpressibleBy*Literal protocols (or ExpressibleByStringInterpolation), this change records an implicit call to the corresponding init(...Literal:) in the indexstore, located at the beginning of the literal.

@swift-ci please test

Could you add test cases for SE-0213 Literal initialization via coercion?

Also does it make sense to do similar to ExpressibleByArrayLiteral/ExpressibleByDictionaryLiteral too?

Also does it make sense to do similar to ExpressibleByArrayLiteral/ExpressibleByDictionaryLiteral too?

There's actually an open bug for this as well - https://github.com/apple/swift/issues/56165. So @ileitch may be interested in this PR.

Also does it make sense to do similar to ExpressibleByArrayLiteral/ExpressibleByDictionaryLiteral too?

There's actually an open bug for this as well - #56165. So @ileitch may be interested in this PR.

I've added these two conformances as well now—thanks for mentioning them!

@swift-ci please test

Could you add test cases for SE-0213 Literal initialization via coercion? i.e. CustomInteger(42) implicitly calls CustomInteger.init(integerLiteral:)

Forgot to mention, I also added tests for this. An expression like CustomInteger(42) indexes as an implicit call to CustomInteger(integerLiteral:) at the location of the 42 token due to the way the AST transforms the expression. That might seem a little odd since it looks like an explicit call, but since it's an accurate representation of what's happening here at the language level, I don't know if it's worth treating differently.

Forgot to mention, I also added tests for this. An expression like CustomInteger(42) indexes as an implicit call to CustomInteger(integerLiteral:) at the location of the 42 token due to the way the AST transforms the expression. That might seem a little odd since it looks like an explicit call, but since it's an accurate representation of what's happening here at the language level, I don't know if it's worth treating differently.

Seems reasonable for now, we can always change later if necessary.


Over indentation in markdown code blocks.

We are seeing rendered blocks of code over indented only in the message view, when previewing everything appears normal.  This happens with or without language specification.
Here's the sent message:

Preview of the message:

And the raw:

After a quick bisect, it appears that this issue was introduced by 0c565f50bef24dd03c539d47954215a707ee438f in some strange way.

@andersk perhaps you could provide insight into this issue?

Fascinating; I would not have expected this sort of issue to be the result of the partials migration, but it certainly seems possible.
@andersk this is a priority thing to investigate.

Yikes, that’s awful. #12798 fixes the immediate problem, but this needs some more investigation and tests and complaining at upstream.

Okay I found a better solution with the Handlebars preventIndent option. Updated #12798.


Add installation to README

This is a small PR that solves #2. It adds spacing in the README, some anchors, as well as an Installation section.

This only downloades this source code, it doesn't compile it.
If you add another line, go build github.com/goggle/flatten, wouldn't that be better?

Hmm, it actually does, though!
$ go help get
usage: go get [-d] [-f] [-fix] [-insecure] [-t] [-u] [build flags] [packages]

Get downloads the packages named by the import paths, along with their
dependencies. It then installs the named packages, like 'go install'.

[...]

It can easily be tested with a Docker container:
$ docker run -it golang:latest
Unable to find image 'golang:latest' locally
latest: Pulling from library/golang
Digest: sha256:0bc4b605f127ebcda9c96d8b0411780e8dcc03ee695c5f9cdf6298f9977b8ca8
Status: Downloaded newer image for golang:latest
root@95db6b6811fc:/go# go get github.com/goggle/flatten
root@95db6b6811fc:/go# which flatten
/go/bin/flatten
root@95db6b6811fc:/go# flatten
Flatten performs changes on the file system. Do you want to simulate this process first? [y]/n: n

@dotpy3 you were right.
In my installation it wasn't working, probably because $GOPATH/bin was not included in my $PATH


Status Selection Type is Unclear.(Agent Panel)

Describe the bug
Status Selection Type is Unclear. Creating Confusion to know that  whether its active or Paused.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://www.pulseptt.com/agent.html'
Login with valid credential:- 1. User name: john 2. Password: 12345678
Navigate to Company Management.
Click on Modify Company.
See error.

Expected behavior
Selection should Either be in a List Box or Dark Gray Background should be changed to White for not selected status.  On Active (Text Color should be Green), On Paused (Text Color Should be Red).
Desktop (please complete the following information):
OS: Windows 10
Browser :Version 100.0.4896.60 (Official Build) (64-bit)
Version [0.1.1]
Additional context
Same issue Exist on Modify Sub-agent Page.

This bug is not completely resolved. As I had mentioned in above additional context- Same issue Exist on Modify Sub-agent Page.


Trust Registry Protocol #2

implementing

Vitor P: Define the statusDetail field and how it should be used.

comments from v1 draft - closing


WIP - zapdriver for GC logging

Motivation and Context
We need Go to log with the severity levels used by Google Cloud Logging

What has changed
Adding "zapdriver" plugin for Uber Zap logging

How to test?

run acceptance tests in Sandbox
check severity levels in GC Logging

Links

https://trello.com/c/XkpRkVjw

/deploy foxj

/deploy foxj

/deploy foxj

/deploy terryj

Im not getting any output in stackdriver when i test this


Social icons working

Closes #366
Description:
User were not able to redirect to links.
#Type of change:
Added links..

[✅] Bug fix (non-breaking change which fixes an issue)
[✅] New feature (non-breaking change which adds functionality)

How this has been tested:
I have checked the code .
Checklist✅

[✅] My code follows the style guidelines of this project
[✅] I have performed a self-review of my own code
[✅] I have commented my code, particularly in hard-to-understand areas
[✅] I have added demonstration in the form of GIF/video file
[✅] I am an Open Source Contributor

Screenshots/GIF📷

Hey , i created pr under JWOC.

Merged 🥳 @thatguywhocode


Problems installing the repository on Windows

Hi! Juan, data scientist from the Viz team.
1 ERROR:
I'm having difficulties with the installation for being able to use the library:

(coronawhy) C:\Users\juanc>git clone git@github.com:CoronaWhy/task-geo.git
Cloning into 'task-geo'...
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

I thought that for cloning I should use this command:
https://help.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository
UPDATE: 2 ERROR:
Using

"git clone https://github.com/CoronaWhy/task-geo.git"

I have being able to install, but had the next errors:

Originally posted by @JuanCalvoFerrandiz in https://github.com/CoronaWhy/task-geo/issues/14#issuecomment-607194023

Hi @JuanCalvoFerrandiz  and thanks for the feedback, I will upload the github link in the documentation to the https one.
Can you please specify with python version are you using?
Also, please try with just make install, as the current installation in the readme is focused for developers, will change that too.
Also, please, next time, don't send an screenshot of a text screen, copy and paste the code, is easier to work this way.

Hi @ManuelAlvarezC . Thanks for your help. As we spoke:

Python 3.7
Tried with make install. Same error:

ERROR: Command errored out with exit status 1:
 command: 'C:\Users\juanc\Anaconda3\envs\coronawhy\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\juanc\\Desktop\\01 JUAN CALVO\\01 BIG DATA\\01 PROYECTOS\\COVID-19\\CODE\\REPOSITORIES\\task-geo\\setup.py'"'"'; __file__='"'"'C:\\Users\\juanc\\Desktop\\01 JUAN CALVO\\01 BIG DATA\\01 PROYECTOS\\COVID-19\\CODE\\REPOSITORIES\\task-geo\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info
     cwd: C:\Users\juanc\Desktop\01 JUAN CALVO\01 BIG DATA\01 PROYECTOS\COVID-19\CODE\REPOSITORIES\task-geo\
Complete output (7 lines):
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\juanc\Desktop\01 JUAN CALVO\01 BIG DATA\01 PROYECTOS\COVID-19\CODE\REPOSITORIES\task-geo\setup.py", line 9, in <module>
    readme = readme_file.read()
  File "C:\Users\juanc\Anaconda3\envs\coronawhy\lib\encodings\cp1252.py", line 23, in decode
    return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 193: character maps to <undefined>
----------------------------------------

ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

I have tried to track de error and it seems to have something to be with the encoding of readme_file.  Could be? I'm blocked with this issue. Any help is welcome.
https://stackoverflow.com/questions/9233027/unicodedecodeerror-charmap-codec-cant-decode-byte-x-in-position-y-character

Hi.
You could try:

git checkout --track -b stable

Thanks four your interest @normtak.
I have tried with git checkout master and git checkout --track -b stable, and either in the master, or in the new branch I create name "stable" with your command, doesn't work the installation.

The solution is simple:
On lines 9 and 12 of setup.py the open should be:
with open(filename, encoding='utf-8') as file:

Will fix it ASAP

I had some issues with make install on Windows, so I decided to do the installation using Windows Subsystem for Linux.

Hi @normtak!
Can you link the guideline you used to do so, and list any problem you found? This may be helpful for other users having similar problems.
Thanks!


6.6.1 debian 11 repository have no Release File

Hi.
I just jump to opennebula and want to start trying it.
Description
Failed 'apt update'
Err:5 https://downloads.opennebula.io/repo/6.6.1/Debian/11 stable Release
  404  Not Found [IP: <IP_ADDRESS> 443]
Reading package lists... Done
E: The repository 'https://downloads.opennebula.io/repo/6.6.1/Debian/11 stable Release' does not have a Release file.

To Reproduce
Follow step on https://docs.opennebula.io/6.6/installation_and_configuration/frontend_installation/opennebula_repository_configuration.html#id2
Expected behavior
no error
Details

Instalation step
Repository og 6.6.1 debian 11

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

The correct url is with 6.6 not 6.6.1, it should be fixed now.
Thanks for reporting it


Discuss how configuration/settings will work for the white label extension

Use Daniels initial design/definition of what the URL for theming will supply and hold a meeting to present the possibilities to the community.

The following is the description of the requested feature from Provenant's bounty document:

Configuration with a vendor (Keria provider). Upon install, the extension MUST allow a person to provide a configuration URL for a vendor that will provide the Keria agent for the Signify instance that runs in the extension. Without a vendor who hosts Keria, the extension is not functional.
This URL is NOT the URL of the agent, but rather a URL that MUST be browsable by a person. It should point to an onboarding web page hosted by the vendor, that walks the user through a configuration experience and that ultimately redirects the user to a URL that serves a JSON object with the following configuration parameters:

agent_url: where Signify can call the user's Keria agent.
vendor_css: URL where the vendor's CSS can rebrand the UI of the extension.
strings_url: A nullable URL that includes the token "lang=??". This URL returns a JSON object that contains localized strings for the extension; the extension will call this URL, substituting a lang code appropriate to the user's browser settings.
support_url: A URL where the user can get support from the vendor.
docs_url: A URL where the user can browse documentation about the extension as supported by that vendor.
management_url: A URL which allows the vendor to override the basic UI of the extension. It may be null. If it's null, the extension displays a default UI in a popup window, to help users to manage, create, and select identifiers and credentials to authenticate to a web site. If it's NOT null, the extension loads HTML from this URL to perform management tasks.

(Note: need to discuss overall config strategy. There are cybersecurity implications if we get too fancy, but there are problems with overreach in the UI of this extension if we don't give vendors enough freedom.)

Meeting scheduled on Friday 7:30 EST. Google meet link: https://meet.google.com/koi-ntog-hup

I think that describing this as "theming" is misdescribing its purpose a little. It is true that we will derive from this feature the ability to theme the extension. However, its more important purposes are:

Allow the extension to be configured with policies for its associated agent. (Agents are drastically more powerful than just providers of encrypted storage for dumb wallets, but unless this browser extension has a way to configure said agents, it can't access that power.)

Allow the owner of a web (or mobile) wallet to establish a relationship with one or more value-added websites that will deliver powerful features that depend on much more than the simple authentication of an ordinary website, but that require the user and the wallet they control to make accountable choices using their AIDs/keys/credentials.

If we don't give these purposes their proper weight, then we will create feature pressure on the extension. We will be tempted to add more and more sophisticated features to it, so website X and website Y can get more and more sophisticated in their user interactions. But if we think about it properly, then the extension remains simple and pure (a wallet plus a generic, simple authentication mechanism), and all those extra features move into the websites that interact with the wallet. That's where those features belong.

You are correct Daniel. This is about the configuration of a KERIA provider that should also include an onboarding process to simplify the adoption, as well as the setting the relationship policies to value-added websites.

From our meeting today:
@rodolfomiranda will update the information in the comments.

The following is the proposed mechanism to configure the browser extension:

User will onboard with a KERIA provider and obtain a configuration URL
after installing the browser extension  will ask for the configuration URL
the browser extension will use the URL to GET a JSON  with configuration parameters/values
the browser extension will apply configuration values to personalize the UI such as:

logo
colors
fonts
titles
labels

Additionally, the browser extension GitHub repository will contain a file with known keria providers URLs that the browser extension will use to facilitate the configuration. The list of keria providers can be updated with a PR approved by the community


Windows CLI missing extension

Summary
What happened/what you expected to happen?
After unzipping the argo-windows-amd64.gz bundle, there should be a executable binary with the file extension of *.exe
What version of Argo Workflows are you running?
0.9.4
Diagnostics
I manually added the file extension, added to my tools directory in my PATH, then it works.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@argoproj/argo-windows FYI

Is  CI  issue?

I think we need to append .exe to the output name in -o here when creating Windows binary :
https://github.com/argoproj/argo-workflows/blob/b476c4af505b6f24161a3818c358f6f6b012f87e/Makefile#L178


--profile: 1 required TEST missing

Windows Terminal version
Windows Terminal Version: 1.13.11432.0
Windows build number
Microsoft Windows [Version 10.0.22000.708]
Other Software
No response
Steps to reproduce

Create profile named "u"
Run wt -p "u"; nt -p "u"
Error appear.
"--profile: 1 required TEST missing"

Expected Behavior
New windows terminal is created with two tabs
Actual Behavior
The error pops up and Windows Terminal never opens.
Screenshot of the error  https://prnt.sc/y4Hi3Uir5as9
I think profile name is too short(one sign). Profile name with more than one sign works like a charm.

@Andrew1988123123 that's an interesting find! If you add a space between first profile name and semicolon then it works.
Sample output with wt -p "u"; nt -p "u"

and wt -p "u" ; nt -p "u"

@Andrew1988123123 that's an interesting find! If you add a space between first profile name and semicolon then it works.
Sample output with wt -p "u"; nt -p "u"

and wt -p "u" ; nt -p "u"

It works but there is another issue. For some reason it always opened default profile(which is powershell for me). Profile name "u" is an abbreviation of Ubuntu.

Huh. Maybe I'm splitting things poorly on the ;, it's really weird that adding a space would fix this. Command-line parsing is hard 🙃

No big deal. I just have to remember adding space before ; . Even documentation say so.


Fixed #24974 -- Fixed inheritance from modelform_factory forms

When a form created using modelform_factory is inherited, the
initialization of the subclass will be different from the base class.
Consider the case when formfield_callback is passed to modelform_factory.
The formfield_callback information is lost after initialization of the
base class.
This commit throws the formfield_callback into the Meta
class of the base class, so that the subclass can use it instead
of the default.

@mrmachine, as the reporter of the ticket, could you test and/or review this to see if it solves the reported issue for you?

merged in d5f89ff6e873dbb2890ed05ce2aeae628792c8f7, thanks!


Update Mapillary color scheme

This PR includes

Update lime-green to Mapillary green
Add a different layer style for selected and hovered sequences

Before

After

Ahh sorry, I'd rather not do this.. The colors were chosen so that they would contrast the other two streetside imagery providers and all the other stuff that appears on the map.
I think it's more important for mappers to be able to distinguish Bing Streetside, Mapillary, and OpenStreetCam traces, even if that means we don't strictly use the preferred brand colors of each one.


Updating the Validating.py python script

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

Conversation


Any plan to support macOS 11 ?

or even 10.15 ?
Swift concurrency support back-port to macOS 10.15/iOS 13.
And I can even install Xcode 13.3 on macOS 11, with some tweak :)
If you need help, maybe I can have a fork and PR in this weekend.

[ ] Backward-compatibility for macOS 11.0

So, yes please! Thanks! Things preventing me adding support for older macOS versions are mostly just async fetch that are specific to macOS 12+ :(

Hi.
I fork and modify some back-port API to make it work on macOS 11.0
However, I'm not quite expert at i18n. Is this showing correctly ?
Because I just translate the String(:localized) API to the old style one :)
I only test the en-US and zh-Hans locale.

And, I use Kingfisher instead of AsyncImage, which have a better cache (The AsyncImage is never cached, means each time the icon should be loaded from HTTP)

See #12
Since my old MacBook Pro use macOS 11.4 and not ready to upgrad to macOS 12 (waiting for M1 Pro MacBook, in Shanghai...)
I can not test whether it's pixel match with the previous App running on macOS 12. But acutally I found it's OK for me to use now 😴

Closing in favor of #12

The badget in README.md seems not updated :)

The badges in README.md seems not updated :)

Yes, I'm aware - waiting for a future time to sneak this tiny update in a larger commit :)


Fix classifier for .NET/C# PRs

The area prefix regex didn't include the . or # characters so it wasn't matching PRs with the prefix [C#] or [.NET].
Also added a special case for .NET since some PRs use that as the prefix, but the classifier expects the group name C# instead.

Before
After

Thanks!


Encrypt Metadata by a different key than the Photos

This will allow us to not share Metadata into shared threads

done in https://github.com/textileio/textile-go/pull/353


Bump keras_nlp version

Fixes the build because it expects to match the latest release.

This is done -- thank you


Bars Data collection

I'm trying to use zenbot to collect bar data from exchanges. I noticed that the timestamp on each generated bar seems to be dependent on when the bot was started.
For example, when selecting 1M as the period and starting the bot at 4:30:23 PM, the bot will generate its first bar with a timestamp some time around 4:31:23 PM (plus/minus a few seconds).
For bigger timeframe this might not matter as much but for lower timeframes a bar in the middle of the period does not reflect the price accurately.
Is there an easy fix to make bars generate at exact points in time ie 4:30:00, 4:31:00, 4:32:00 (for 1M). Simply rounding is not sufficient
Thanks for this awesome software.

Dear issue reporter,
We have slightly changed our github issue policy and would now kindly request folks that have questions that they ask them in our zenbot subreddit.
You can find it here: https://reddit.com/r/zenbot
This issue will be closed, but if you disagree with your ticket being marked as a question feel free to leave a comment defending your case.
Thanks for contributing time and effort!
Greetings,
🤖


Remove whitespace replaces inline code with code block

This plugin is great, but in one of my code notes it had messed up several parts. I have oversimplified the case to the bare minimum and share this reproducible version.
A line with several inline codes

`1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, `10`

Two code blocks

```js
console.log(1)
```

```js
console.log(2)
```

When I execute the command "Remove whitespace in document", I get this:
A line with several inline codes

`1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, ```js
console.log(2)
```0, `10`

Two code blocks

```js
console.log(1)
```

TRIM_WHITESPACE_REPLACE_1

The inline code `9` gets replaced with the second code block, and instead of the second code block now there is a placeholder TRIM_WHITESPACE_REPLACE_1
The content of inline codes and code blocks do not change the result. It seems that the quantity and the position are what matters here. Adding more instances of inline code and code blocks, more of them get affected.
The "Skip code blocks" option is enabled, in order to avoid changing indentation whitespace inside them.

Noted, thanks for the ticket!
This wasn't caught in my test cases; will explore.

@andrezgz this should be fixed! Sorry about that.

Thanks @zlovatt! It seems to be working right now


Policy Assemlies failed to load

Hello,
I am working with Visual Studio 2019 and in principle git-tfs works as expected.
But as soon as I want to do a rcheckin or checkin I receive the following errors:
[ERROR]: Policy: Internal error in Builds. Error loading the builds policy (The policy assembly 'Microsoft.TeamFoundation.Build.Controls, Version=<IP_ADDRESS>, Culture=neutral, Public KeayToken= // Public Key' is not registered.).
Installation instructions:
Note: If the checkin policy fails because the assemblies failed to load, please run the file 'enable_checkin_policies_support.bat` in the git-tfs directory and try again.
Unfortunately, running the .bat has no effect. The error still occurs. Even if I run the disable_checkin_policies_support.bat the error is still there.
A hacky workaround is to force the checkin with the --force option but then in the TFS commit the upper Policy warning is written down with a override warning. This works but is not really nice because in TFS it sounds like I overrode a TFS policy warning that is not an actual TFS ovverride warning.

We are aware of this problem.
Checkin policies is the only feature where you explicitly have to support the different version of VisualStudio (find where they are installed and load specific dlls).
Currently, the only supported version is 2015 (previous version of git-tfs support 2012 and 2013).
@siprbaum is working on it and already did a PR for VS 2017 support: #1348
It seems he also has support for VS2019: https://github.com/git-tfs/git-tfs/issues/1054#issuecomment-709465852
@siprbaum An idea like that: perhaps you could create a PR with your dirty work on VS2019 and not intended to be merge (created as a draft) so that @pdeiml is able to test it?

I have support for VS2019 ready, which is build on top of #1348 and my not submitted checkin policy support.
As I am little short on time this week, I want to finish the PR #1348 first. I think it would be possible to provide a draft (or a reald PR) then


Debian package installer instructions fail - no valid OpenPGP data found.

Debian package installer fails
When I follow the Debian installation instructions  as linked from the installers section of the Adoptium installation page, the second step fails on Debian 10 ("buster") and Debian 11 ("bullseye") with the message:
$ wget -O - https://packages.adoptium.net/artifactory/api/gpg/key/public | sudo apt-key add -
--2022-02-14 20:25:34--  https://packages.adoptium.net/artifactory/api/gpg/key/public
Resolving packages.adoptium.net (packages.adoptium.net)... <IP_ADDRESS>
Connecting to packages.adoptium.net (packages.adoptium.net)|<IP_ADDRESS>|:443...
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
connected.
ERROR: The certificate of ‘packages.adoptium.net’ is not trusted.
ERROR: The certificate of ‘packages.adoptium.net’ doesn't have a known issuer.
gpg: no valid OpenPGP data found.

I can see this too on an existing installation of Devuan 4 (Debian 11 compatible) that was previously working when I run apt update.
Err:5 https://packages.adoptium.net/artifactory/deb bullseye InRelease
  Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]
...
W: Failed to fetch https://packages.adoptium.net/artifactory/deb/dists/bullseye/InRelease  Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]

The server provides an incomplete certificate chain, the intermediate certificate seems to be missing:
https://www.ssllabs.com/ssltest/analyze.html?d=packages.adoptium.net


Apply NetworkInfo changes introduced in D354 on master

The NetworkInfo is imo cleaner in the fixed version from 1.4. Might be easier/prevent unnecessary rebasing if we pick after landing D201.

https://phabricator.mesosphere.com/D371


weird error with s3 bucket policy / iam policy

Hi,
I have the following code:
        self.uploadBucketAnonUploadPolicy = t.add_resource(BucketPolicy(
            "uploadBucketAnonUploadPolicy",
            Bucket=Ref(self.uploadBucket),
            PolicyDocument={
                "Version": "2012-10-17",
                "Statement": [
                    {
                        "Action": "s3:PutObject",
                        "Effect": "Allow",
                        "Resource": [
                            Join("", ["arn:aws:s3:::", Ref(self.uploadBucket), "/*"]),
                        ],
                        "Principal": "*",
                    },
                    {
                        "Action": "s3:*",
                        "Effect": "Allow",
                        "Resource": [
                            Join("", ["arn:aws:s3:::", Ref(self.uploadBucket), "/*"]),
                        ],
                        "Principal": {
                            "AWS": [ Ref("AWS::AccountId"), ]
                        },
                    },
                ]
            }
        ))

the output of that fragment is:
        "uploadBucketAnonUploadPolicy": {
            "Properties": {
                "Bucket": {
                    "Ref": "uploadbucket"
                },
                "PolicyDocument": {
                    "Statement": [
                        {
                            "Action": "s3:PutObject",
                            "Effect": "Allow",
                            "Principal": "*",
                            "Resource": [
                                {
                                    "Fn::Join": [
                                        "",
                                        [
                                            "arn:aws:s3:::",
                                            {
                                                "Ref": "uploadbucket"
                                            },
                                            "/*"
                                        ]
                                    ]
                                }
                            ]
                        },
                        {
                            "Action": "s3:*",
                            "Effect": "Allow",
                            "Principal": {
                                "AWS": [
                                    {
                                        "Ref": "AWS::AccountId"
                                    }
                                ]
                            },
                            "Resource": [
                                {
                                    "Fn::Join": [
                                        "",
                                        [
                                            "arn:aws:s3:::",
                                            {
                                                "Ref": "uploadbucket"
                                            },
                                            "/*"
                                        ]
                                    ]
                                }
                            ]
                        }
                    ],
                    "Version": "2012-10-17"
                }
            },
            "Type": "AWS::S3::BucketPolicy"
        },

The resulting policy should look like:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:PutObject",
            "Resource": "arn:aws:s3:::uploadbucket-bla/*"
        },
        {
            "Sid": "",
            "Effect": "Allow",
            "Principal": {
                "AWS": [ "arn:aws:iam::accountidnumber:root" ]
            },
            "Action": "s3:*",
            "Resource": "arn:aws:s3:::uploadbucket-bla/*"
        }
    ]
}

however, the resulting policy looks like this:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:PutObject",
            "Resource": "arn:aws:s3:::uploadbucket-bla/*"
        },
        {
            "Sid": "",
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::accountidnumber:root"
            },
            "Action": "s3:*",
            "Resource": "arn:aws:s3:::uploadbucket-bla/*"
        }
    ]
}

Note the missing array in the principal (with the array the policy does what is supposed to)
is this a cloudformation bug? Am I doing something wrong here?

I think this is the same as cloudtools/awacs#15. Just ran into the same issue, using
Resource=[Join('', [awacs.s3.ARN(''), Ref(bucket), '/*'])],

worked for me. Note that awacs.s3.ARN('') produces 'arn:aws:s3:::'. My first idea awacs.s3.ARN(Ref(bucket)) will not work, as the function does not know what to do with a troposhere.Ref object.
Working example:
bucket = t.add_resource(
    s3.Bucket(
        'Bucket',
        BucketName=Join('-', [Ref(AWS_STACK_NAME), Ref(environment)]),
    )
)

# Bucket policy enforcing server-side encryption
bucket_policy = t.add_resource(
    s3.BucketPolicy(
        'BucketPolicy',
        Bucket=Ref(bucket),
        PolicyDocument=PolicyDocument(
            Id='EnforceServersideEncryption',
            Version='2012-10-17',
            Statement=[
                Statement(
                    Action=[awacs.s3.PutObject],
                    Condition=Condition(
                        StringNotEquals(
                            {
                                's3:x-amz-server-side-encryption': 'AES256'
                            }
                        )
                    ),
                    Effect=Deny,
                    Principal=Principal(Everybody),
                    Resource=[Join('', [awacs.s3.ARN(''), Ref(bucket), '/*'])],
                    Sid='DenyIncorrectEncryptionHeader'
                )
            ]
        )
    )
)


Question: Can Emitter get a list of rooms, or count of connections in a room?

I have a backed server that is processing Data and I need to know if anyone is still in a room before I process the data for that room (no point doing work if no one is listening). I don't really want to have the full Socket.io(+redis) service running since the back-end server cannot receive client http requests / websockets.
Thanks.
I'm Running in Node.js on Heroku.

@Raukk no, there is currently no way to do that with the socket.io-emitter.
Related: https://github.com/socketio/socket.io-redis/pull/168

Ok, Thanks.

@darrachequesne Is there better way to check if room exists from emitter process, when using multiple servers with Redis adapter


Drop skip_abstract_def_check flag support

Nine months have passed since 0.30.0 was released. It's about time to drop it.

Thank you!
But what actually needs to be done is turn the warnings into errors. But I think there are still some. bugs with the abstract de checker, so I don't know...

Abstract def checks are solid and the warnings have become errors in #9810. I think we can drop the flag now. It would be a breaking change, though. So we might have to delay that for 2.0. But I don't expect the flag to be used and it was only a dev tool that was never really documented. I think it should be fine to remove.


Add the ability to upload an image to the AI. [FEAT]:

What would you like to see?
I would love to be able to do the basic function of uploading an image and sending it to the AI since so many now have vision.

Moved to #558


Dreamcast: Review Polish Translation

I don't believe we missed anything, and I believe we also followed the rules laid out in Translations.md but if there are any mistakes you recognise where something was translated when it shouldn't have been, do let me know. :3

(if you are happy with it, I can announce it on my twitter)

We found a few small things we wanna fix, haven't gotten through the whole thing re-reading again. I'll let you know when we submit those small fixes and then you're more then welcome to announce it.

I've added you as 'proofreader' for the Polish translations so you don't need my approval any more for changes you need to make in the future.

I presume changes still need to be pushed in from Crowdin to the repo/made public on the website, correct?
Also wondering if this means I should still make an "issue" for the fact the Gameboy one is also finished and ready for deployment? Not sure how the flow of this all works, sorry.

Yes, but the pull request is automatically created by crowdin as soon as you make changes to the translations.
 Not even for the attribution? (the translation_authors.yaml)
Also if you wanted to announce the translation regardless of any further fixes we need to make I think it should be fine, it's mostly really small stuff (declension of English words being weird and the like)

Crowdin won't update translation_authors.yaml but I can do it for you if I see the translation authors are the same.
I think people understand the translations may contain mistakes, just like any writing. That's why I've setup Github and Crowdin.


Periodically update pod status from kubelet.

Every 3 sync loops kubelet updates pod status using new pod/status handler. This PR fixes #4561 (kubelet to POST pod status to apiserver).

Needs gofmt...

Formatting fixed. Sorry about that. Added hooks as described here to prevent it in the future.

We also need to rebase btw

We already introduced "thread-per-pod" logic to kubelet, why not asking that thread to generate podstatus periodically and cache somewhere, and SyncLoop just simply aggregates the status, and propagates the result back?

I agree with Dawn that caching statuses as part of SyncLoop is a good idea (we should integrate it into pod_workers.go). However, the question is how expensive computing the status is - if it can potentially be expensive we should consider having a separate thread for it.
Also, if you decide to moving it to "thread-per-pod" goroutine, please also take a look into #5239, which may affect your work.

I agree with @dchen1107  that a better way to achieve this is through the worker per pod. We should change the podWorkers to handle more arbitrary work items that we can schedule on that thread.
Only downside (as @wojtek-t  noted) is that the worker may fall behind and post it later. That's probably fine though, since the pod worker would be the first to reflect the pod's state and if it is blocked is because a config change is occurring.

Ping @fgrzadkowski, anything I can help with? I think we talked about moving this to periodically scheduled on the podWorker. WDYT of that approach?

Sorry for the delay. I've been in Spotify for the last 3 days and didn't have time to work on this.
I think that having this logic in podWorker makes sense.

@fgrzadkowski no worries, I hadn't heard back so figured I'd ping :)

Ok. I've just pushed new version:

hostname is set as part of the Status generated by kubelet
status is created after syncPod (run using podWorker) and cached
separate go routine to send status to apiserver.

PTAL

I have also tested this with disabled pod_cache and it works.

I'd like us to also push the status in the podWorker, but I'm fine with a separate thread for now so I won't block on that.

Will need a rebase btw, just merges some changes to syncPod()

All comments addressed and rebased to head.
Regarding pushing the status in podWorker, I'm not sure this is a good idea, because AFAIU we want to push status updates in bulks.

Regarding pushing the status in podWorker, I'm not sure this is a good idea, because AFAIU we want to push status updates in bulks.

+1. podWorker should populate related Status periodically, not push directly. Eventually we want to introduce a bulk post on Status including both Pod and Node.

I'm sorry, you'll need to rebase again :( this is done though.

Rebased :)
We have so much churn that it's quite some work to keep it in sync...

Thanks for dealing with the churn @fgrzadkowski :) merging.

This PR broke e2e tests - Filip is looking into it now.


Two many built in functions slow down the creation speed of Engine

It seems the functions registering is during runtime and two many built in functions here https://github.com/jonathandturner/rhai/blob/master/src/builtin.rs makes it slow to create rhai::Engine

 name                                         before ns/iter  after ns/iter  diff ns/iter   diff %  speedup
 b_benchmark_abac_model                       101,664         28,436              -73,228  -72.03%   x 3.58
 b_benchmark_basic_model                      104,649         31,329              -73,320  -70.06%   x 3.34
 b_benchmark_cached_abac_model                196             204                       8    4.08%   x 0.96
 b_benchmark_cached_key_match                 205             203                      -2   -0.98%   x 1.01
 b_benchmark_cached_priority_model            195             200                       5    2.56%   x 0.98
 b_benchmark_cached_rbac_model                195             199                       4    2.05%   x 0.98
 b_benchmark_cached_rbac_model_large          201             202                       1    0.50%   x 1.00
 b_benchmark_cached_rbac_model_medium         195             194                      -1   -0.51%   x 1.01
 b_benchmark_cached_rbac_model_small          199             196                      -3   -1.51%   x 1.02
 b_benchmark_cached_rbac_model_with_domains   217             224                       7    3.23%   x 0.97
 b_benchmark_cached_rbac_with_deny            197             200                       3    1.52%   x 0.99
 b_benchmark_cached_rbac_with_resource_roles  198             203                       5    2.53%   x 0.98
 b_benchmark_key_match                        159,912         78,486              -81,426  -50.92%   x 2.04
 b_benchmark_priority_model                   106,327         32,874              -73,453  -69.08%   x 3.23
 b_benchmark_raw                              5               5                         0    0.00%   x 1.00
 b_benchmark_rbac_model                       117,752         44,258              -73,494  -62.41%   x 2.66
 b_benchmark_rbac_model_large                 43,627,989      39,623,365       -4,004,624   -9.18%   x 1.10
 b_benchmark_rbac_model_medium                3,657,364       3,541,426          -115,938   -3.17%   x 1.03
 b_benchmark_rbac_model_small                 456,862         381,061             -75,801  -16.59%   x 1.20
 b_benchmark_rbac_model_with_domains          126,699         52,971              -73,728  -58.19%   x 2.39
 b_benchmark_rbac_with_deny                   123,041         48,349              -74,692  -60.70%   x 2.54
 b_benchmark_rbac_with_resource_roles         116,549         41,367              -75,182  -64.51%   x 2.82
 b_benmark_cached_basic_model                 217             200                     -17   -7.83%   x 1.08

Is it possible to register those functions during compile time?

seems Engine::new_raw wont register them, strange...why the bench improved...

There are still a number of essential functions registered for the "core" library (things like arithmetic), but I'm quite sure you'll need those to evaluate expressions.
Which versions did you compare these benchmarks on?  0.12.0 from crates.io?


Remove SimilarityOption enum

Closes #3856

One failing test
build.bat seed:3806 test "responses"

Addressed in different PR already


Cannot start projects that their name begins with a number

Run a Diagnostic and Paste Link Here

Describe the bug

When a project starts with a number (ie. 123website), running dev start results in a Mutagen error.
Starting 123website...
Pushed mkcert rootca certs to ddev-global-cache/mkcert
Volume "123website_project_mutagen"  Creating
Volume "123website_project_mutagen"  Created
Container ddev-123website-db  Creating
Container ddev-123website-db  Created
Container ddev-123website-dba  Creating
Container ddev-123website-web  Creating
Container ddev-123website-web  Created
Container ddev-123website-dba  Created
Container ddev-123website-web  Starting
Container ddev-123website-dba  Starting
Container ddev-123website-db  Starting
Container ddev-123website-dba  Started
Container ddev-123website-db  Started
Container ddev-123website-web  Started
Starting mutagen sync process... This can take some time.
Failed to start 123website: Failed to create mutagen sync session 123website. You may be able to resolve this problem with 'ddev stop 123website && docker volume rm 123website_project_mutagen' (err=Failed to mutagen [sync create /Users/shaal/code/ddev/123 docker://8050c5878746aee43ca49b59c45ed519c2ba0edb40e471f50e61f791c2699aca/var/www/html --no-global-configuration --name 123website --configuration-file=/Users/shaal/code/ddev/123/.ddev/mutagen/mutagen.yml] (exit status 1), output=Error: invalid session name: name does not start with Unicode letter
)

To Reproduce

Create .ddev/config.yaml

name: "123website"
type: drupal9
docroot: web
php_version: "7.4"
webserver_type: nginx-fpm
router_http_port: "80"
router_https_port: "443"
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
mariadb_version: "10.3"
mysql_version: ""
nfs_mount_enabled: false
mutagen_enabled: true
use_dns_when_possible: true
composer_version: ""
web_environment: []

Run ddev start

Expected behavior

Expecting the website to work normal, simiilar to a ddev project without mutagen.
Screenshots

Version and configuration information (please complete the following information):

Host computer OS and Version: [e.g. Windows 10, macOS Big Sur, Linux (distro), WSL2 (distro)]
Docker Desktop version if on macOS or Windows (from "About Docker Desktop")
ddev version information (use ddev version)
config.yaml contents for the misbehaving project (the part before the comments)
Do you have any custom configuration (nginx, php, mysql) in the .ddev folder? If so, have you tried without them?

Additional context

The mutagen docs do specify this, https://mutagen.io/documentation/introduction/names-labels-identifiers
The code, with comments, is at https://github.com/mutagen-io/mutagen/blob/42664e12d58888587ed7487e395ddfe8120fe4b8/pkg/selection/names.go#L11-L49
This is fixed in #3266 - thanks so much!

Thank you for fixing this!


Changes CDB_DateToNumber() to accept timestamps with time zones 2202

Fixes #2202
@rafatower
The trick is that this way if a timestamp without a time zone is submitted it will still work.
CR and thoughts please! :smile:

That's a public function, part of the API and we shouldn't simply change it.
Actually you are creating a different function. In a test DB (creating it in public schema):
CREATE OR REPLACE FUNCTION CDB_DateToNumber(input timestamp)
RETURNS double precision AS $$
DECLARE output double precision;
BEGIN
    BEGIN
        SELECT extract (EPOCH FROM input) INTO output;
    EXCEPTION WHEN OTHERS THEN
        RETURN NULL;
    END;
RETURN output;
END;
$$
LANGUAGE 'plpgsql' STABLE STRICT;
CREATE FUNCTION

CREATE OR REPLACE FUNCTION CDB_DateToNumber(input timestamp with time zone)
RETURNS double precision AS $$
DECLARE output double precision;
BEGIN
    BEGIN
        SELECT extract (EPOCH FROM input) INTO output;
    EXCEPTION WHEN OTHERS THEN
        RETURN NULL;
    END;
RETURN output;
END;
$$
LANGUAGE 'plpgsql' STABLE STRICT;
CREATE FUNCTION

\df public.cdb_datetonumber
                                     List of functions
 Schema |       Name       | Result data type |        Argument data types        |  Type
--------+------------------+------------------+-----------------------------------+--------
 public | cdb_datetonumber | double precision | input timestamp with time zone    | normal
 public | cdb_datetonumber | double precision | input timestamp without time zone | normal
(2 rows)

In this particular case, we can take advantage of function overloading.
Please:

split it in two functions
add tests for this change, as naive as they could be.

cc/ @rochoa

@rafatower
Done!

@rafatower my approach was:
tests=# create table test (date timestamp with time zone);
CREATE TABLE
tests=# insert into test values ('1999-01-08');
INSERT 0 1
tests=# select * from test;
          date
------------------------
 1999-01-08 00:00:00+00
(1 row)

(I used 1999-01-08 because it was an example in the PostgreSQL documentation)
So my assumption is that 1999-01-08 00:00:00+00 is the de facto string representation of a TIMESTAMP WITH TIME ZONE type.
In the first line, I cast it to a normal timestamp to test that the old code works (CDB_DateToNumber(timestamp)).
In the second line, I cast to a timestamp with time zone to test that the new code works.
Does it make sense?

For me the first case definitely doesn't make sense even if it works, because as you said you're using the string representation of a timestamp with timezone and then cast down to a timestamp without timezone.
Let your code speak out its intent as clearly as possible.

@rafatower
You're right: the more intuitive the better.
See if you like the new tests better.

Fine by me, but as in the other case, let's wait till tomorrow to see how we'll deal with the release cycle. Thanks!

Great, thank you!