Using Volto in Brazilian Portuguese crash when access "Page not found 404"

Describe the bug
Error when accessing a non-existent URL in the browser, when the language code is pt-br, the "404 Not Found page" is not displayed and crash frontend.
When select  language code en, the "404 Not Found page" is displayed.
To Reproduce
Steps to reproduce the behavior:

Create a Volto project:

cookiecutter gh:collective/cookiecutter-plone-starter

project_title [Project Title]:
project_slug [project-title]:
description [A new project using Plone 6.]:
author [Plone Foundation]:
email<EMAIL_ADDRESS>
python_package_name [project_title]:
plone_version [6.0.3]:
volto_version [16.18.0]:
volto_generator_version [6.3.0]:
Select language_code:
1 - en
2 - de
3 - es
4 - pt-br
Choose from 1, 2, 3, 4 [1]: 4
github_organization [collective]:
...

Start backend and volto.

Proxying API requests from http://localhost:3000/++api++ to http://localhost:8080/Plone
🎭 Volto started at <IP_ADDRESS>:3000 🚀
[React Intl] Missing message: "skiplink-main-content" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "skiplink-navigation" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "skiplink-footer" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Site" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Plone Site" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Plone Site" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Open menu" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Open menu" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Search" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Search Site" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Search" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Search" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Breadcrumbs" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Home" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Copyright" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "The {plonecms} is {copyright} 2000-{current_year} by the {plonefoundation} and friends." for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Plone{reg} Open Source CMS/WCM" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Plone Foundation" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Distributed under the {license}." for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "GNU GPL license" for locale: "pt-BR", using default message as fallback.
[React Intl] Missing message: "Powered by Plone & Python" for locale: "pt-BR", using default message as fallback.

Access for example http://localhost:3000/abc in the browser
See error

RangeError: Incorrect locale information provided
    at Function.supportedLocalesOf (<anonymous>)
    at /home/user/project-title/frontend/node_modules/intl-locales-supported/src/index.ts:45:23
    at Array.every (<anonymous>)
    at Object.areIntlLocalesSupported [as default] (/home/user/project-title/frontend/node_modules/intl-locales-supported/src/index.ts:43:27)
    at createIntl (/home/user/project-title/frontend/node_modules/react-intl/dist/components/provider.js:65:42)
    at new IntlProvider (/home/user/project-title/frontend/node_modules/react-intl/dist/components/provider.js:88:19)
    at processChild (/home/user/project-title/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3305:14)
    at resolve (/home/user/project-title/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3270:5)
    at ReactDOMServerRenderer.render (/home/user/project-title/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3753:22)
    at ReactDOMServerRenderer.read (/home/user/project-title/frontend/node_modules/react-dom/cjs/react-dom-server.node.development.js:3690:29)
sswp> !!! Script exited with code 1

Expected behavior
I hope the "display a 404 Not Found page" is displayed.
Software (please complete the following information):

OS: Ubuntu 22.04
Browser chrome
Volto Version 16.18.0
Plone Version 6.0.3
Plone REST API Version 8.35.3

Work with the following changes:

copy volto/constants/Laguages.js to folder customizations and alter pt_BR to 'pt-BR':

/**
 * Languages.
 * @module constants/Languages
 */

module.exports = {
  en: 'English',
  de: 'Deutsch',
  nl: 'Nederlands',
  ro: 'Română',
  ja: '日本語',
  pt: 'Português',
  'pt-BR': 'Português (Brasil)',
  es: 'Spanish',
  it: 'Italian',
  eu: 'Euskara',
};

change pt-br to pt-BR in frontend/config.js file

  config.settings = {
    ...config.settings,
    isMultilingual: false,
    supportedLanguages: ['pt-BR'],
    defaultLanguage: 'pt-BR',
  };

This is related to https://github.com/plone/volto/issues/3786

This is related to #3786

Two problems, both related to the pt_BR language:
1 - causes duplicate API requests - reported by you;
2 - crash when accessing "Page not found 404" - reported by me;
But the second problem is more serious where it leaves the site unavailable.

@claytonc @wesleybl @ericof
I tried to reproduce it in vanilla Volto:
1.- config:
config.settings.supportedLanguages = ['pt-BR'];
config.settings.defaultLanguage = 'pt-BR';
2.- Go to the control panel, set Brasilian Portuguese as default and supported in Languages.
3.- Check Volto:

Tried also with the cookiecutter, and I saw that the wizard is generating pt-br (in lowercase), which @ericof we would have to address. The rest, all is good, no duplicated requests. @claytonc why are you changing the constants? You should not.

@sneridagh yes. Using pt-BR instead of pt-br in the Volto configuration solves the problem of duplicate requests. See my comments on #3786. But I have two questions:

The documentation gives the example of pt-br. This needs to be fixed as it is misleading.
The I18N_LANGUAGE cookie is recorded as pt_BR. After reading, it is converted back to pt-BR. I wonder if we couldn't record the cookei already with pt-BR, to avoid so many conversions.

@sneridagh
Changing the constants from "pt_BR" to "pt-BR" was necessary to solve the problem of a Volto site stopping working after a page not found ( 404 error). This problem did not occur in previous versions of the Volto.
Also, changing "supportedLanguages" and "defaultLanguage" to "pt-BR" was necessary for the translations to work correctly. Translations made in our addons were not working in pt_BR on Volto.

Changing:
1.- configuration:
config.settings.supportedLanguages = ['pt-BR'];
config.settings.defaultLanguage = 'pt-BR';
2.- go to the control panel, set Brasilian Portuguese as default and supported in Languages.
3.- and access the url for example http://localhost:3000/abc, the following error occurs and it is not displayed on the page not found, but this time the site is not down.
"RangeError: Incorrect locale information provided"
4.- adding 'pt-BR': 'Português (Brasil)' to the constants (Laguages.js), access http://localhost:3000/abc,  page not found is displayed.

5.- changing a setting and the constants:
config.settings.supportedLanguages = ['pt-br'];
config.settings.defaultLanguage = 'pt-br';
6.- access http://localhost:3000/abc, page not found in English displayed.

I've attempted to fix this in https://github.com/plone/volto/pull/4741 -- note that pt-br is the format expected in volto config.


Error: Cannot load nvEncodeAPI64.dll

When I tried to convert the file, I get the following error.
Cannot load nvEncodeAPI64.dll
[hevc_nvenc @ 000001e5ca609280] The minimum required Nvidia driver for nvenc is 436.15 or newer
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

Try updating your nvidia drivers.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Ajay<EMAIL_ADDRESS>Sent: Saturday, September 26, 2020 5:49:59 AM
To: carykh/jumpcutter<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [carykh/jumpcutter] Error: Cannot load nvEncodeAPI64.dll (#188)
When I tried to convert the file, I get the following error.
Cannot load nvEncodeAPI64.dll
[hevc_nvenc @ 000001e5ca609280] The minimum required Nvidia driver for nvenc is 436.15 or newer
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/carykh/jumpcutter/issues/188, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADLRUDAKPEK5NIU6GGFQZ4TSHWTLPANCNFSM4R2YVRXQ.


EPUB text selection sometime breaks in paginated mode

Bug Report
What happened?
On recent Android versions, the viewport sometime shifts when attempting to move the text selection handle.
https://user-images.githubusercontent.com/58686775/212370877-7b95063b-84b0-465b-b652-8fb518adea7a.mov
How to reproduce?

Open an EPUB on a recent version of Android (tested with API 33).
Enable paginated mode.
Increase the font size.
Go to the second page of a chapter.
Long press a word at the top of the page.
Drag down the right text selection handle.
The selection will shift to the previous page.

This is not very reliable and can be hard to reproduce.
Environment

Readium version: 2.3.0

Testing device

Android version: API 33
Model: Pixel 5
Is it an emulator? Yes

Additional context
I believe it's a bug related to the CSS columns in the Chrome Web View. I reproduced the bug in a sample project with a chapter modified to use CSS columns:
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, shrink-to-fit=no"/>
<style>
html {
    column-width: 20em;
    height: 100vh;
}
</style>

Result is the same:
https://user-images.githubusercontent.com/58686775/212371969-af2252c0-a8c8-4cfc-bad8-3df5aa1430de.mov
Here's the test project: TestWebView.zip

Android bug report opened: https://issuetracker.google.com/issues/265334518

It happens on Google Chrome as well. Can be tested with this URL:
https://htmlpreview.github.io/?https://gist.githubusercontent.com/mickael-menu/7db9620b40444f62219abd08a8f22bf3/raw/6494178590b2e54c3b08c6428545970f61b83e51/android-columns.xhtml
https://user-images.githubusercontent.com/58686775/213383488-1a566a50-d12e-4b5d-ba9f-a0c1dd473670.mov

The Android issue was transferred to the Chromium bug tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=1410341

A potential workaround here: https://github.com/futurepress/epub.js/issues/1366#issuecomment-2026512757

It was a dead-end, but it inspired me a different solution: https://github.com/readium/kotlin-toolkit/pull/502


possibility of a version 1.20.1?

Would be really nice, there's no other tameable fox mods out there. A tameable spider mod for fabric would be fun too lol, green eyed spider army :<)

Hi, there's Vulpine on 1.20.1, it has a different taming system, but also new types of foxes. I don't know if I need to port this mod, and I still think how to fix already existing critical bugs, so even if I port it, that will happen after I fix them.


Proposal: make run starts "taggable"

The db[] interface borrows some ideas from git. For example, you can use partial uids. What if we pushed this analogy further, introducing the analog of "git tag" but for scan IDs. We could namespace them a little ('csx.my-tag') to contain the clutter.
@tacaswell is going to hate this.... :imp:

Why am I going to hate this?  It does not make as much sense as git tagging as there is no natural 'parent' or 'child' runs.  We had always talked about keeping another collection of scanid <-> text mappings.

I was half-kidding. I'm glad you don't hate it. I had forgotten any earlier conversation about this. Would you be +1 on a PR implementing this in the near future? Would be nice for demos:
db['xpcs-example-data']

I would expect db['some-tag-name'] to return many headers.

Why don't you add the tags to run_start docs then? I think the first iteration of mds had tags but I was advised to get rid off them :hand:

@arkilic Because we want to keep the core collections an write-once, tags need to be more dynamic.

I know they are write-once, I fought besides you for them to stay that way. You can have a tags collection with docs that hold uid to headers. Make this collection update-able which gives you the dynamic nature. For this kind of stuff, updates work well in mongo

I think that's what Tom proposed. Same page?
On Fri, Aug 7, 2015 at 4:24 PM Arman Arkilic<EMAIL_ADDRESS>wrote:

I know they are write-once, I fought besides you for them to stay that
way. You can have a tags collection with docs that hold uid to headers.
Make this collection update-able which gives you the dynamic nature. For
this kind of stuff, updates work well in mongo
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/dataportal/issues/194#issuecomment-128826229.

Yup, I just saw his comment, have not seen that one. My only concern is this is another query that is added to the header retrieval so I am not sure if this will cause performance issues for many headers. Having mentioned my concern, I say it is up to you since performance requirement is driven by the analysis side.

The performance bottle necks we have seen are all from hitting the db once-per-event, hitting a few times per run start is noise :wink: .
If we are really getting bit by that we can always do a de-normalized cache layer.

I'm worried about the kind of beam line that will have as many headers as hxn events. Yup, but I sure hopen adding more indexing doesn't hurt the header write speed too much :)

moved to https://github.com/NSLS-II/metadatastore/issues/234


How to get more fontawesome icons as a choice

Hi there,
This is probably an easy answer but I am having problems figuring this out.
I want to use the toolbox icon but it isn't available.  How do I use fontawesome icons that aren't available in the default build?
https://github.com/oblador/react-native-vector-icons#custom-fonts

Not sure what you mean, I have the toolbox icon? It was added in v5.0.13 of FA5 so it should be there... Are you sure you are importing FontAwesome 5 and not FontAwesesome 4 (both are bundled)?
The import should be:
import Icon from 'react-native-vector-icons/FontAwesome5';


Build out Google Cloud

Build out google cloud provider (replacement potentially for Azure)

GCE gives $300 in credits free so I went ahead and signed up with my company card. Spinning up a couple test VMs now.

Phew. It's live :) http://www.ardentmc18f.com/


Updated response receiver.

https://forums.solar2d.com/t/update-needed-to-amazon-iap-plugin/352563

Deploy is there. Can anyone check if it still works?

Was able to test it. No issues with my test device. Purchased something and no error. Have not submitted the app to the amazon store.
Adrian

On Oct 22, 2020, at 4:27 PM, Adrian Gomez<EMAIL_ADDRESS>wrote:

On Oct 22, 2020, at 3:57 PM, Vlad Svoka<EMAIL_ADDRESS>wrote:
Deploy is there. Can anyone check if it still works?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/coronalabs/com.coronalabs-plugin.amazon.iap/pull/1#issuecomment-714726672, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYU6SVLHMEWKSEDATD4EOLSMCFBXANCNFSM4S3UWACA.


Grafana Incident unable to display datasource query results

Hey,
When using this data source in Grafana Incident, I get an error Data is missing a number field, see screenshot below:

I double checked the permissions are correct for this datasource as I can use it in a dashboard.
Using Grafana v9.4.3 (cloud) with latest plugin v1.1.1
If there's any other info I can provide, please let me know! Thanks

Hey @xiangshen-dk I just double checked this but unfortunately the problem still remains.

Hi @ramaro , I think the root cause is that alerting is not currently supported (#28).

After some digging, it appears alerting can't be implemented (see #28). Closing this one for now.


TS-4976: Regularize plugins - query_remap

Incremental work on #1114. This also include updates to the documentation about query_remap.

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/112/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/126/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/109/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/238/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1808/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1699/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/370/


Plugin system

Here it is. Believe it or not...
I've merged in Etienne's things, and added a few changes of my own.
What I suggest we do now is
a) Check over all the commits. Etienne's and mine included (@tiennou - you might like to look over mine, esp. the qs-push-plugin script ones)
b) Merge and build this
c) Play around with it to make sure you can pull the list of plugins from qsapp.com, you don't get any errors when you have no internet etc., can download new plugins, can update existing plugins (I suggest you download some old ones from http://qsapp.com/plugins/archived then try to update them), anything else you can think of
d) Play around with this on a clean install (I have not done this yet)
e) check plugin installing from the setup wizard (not tested)
A few things of note:

The qs-push-plugin isn't very clever when you upload an updated plugin. i.e. it just uploads the new one and leaves the old one on the server (it should check to see if the requirements are the same and if it should delete it)
The web interface at http://qsapp.com/plugins.php screws up when there's more than one plugin uploaded with the same ID (direct result of the point above)
I have not tested any version requirements things, but this will not be required for perhaps a few versions

Good luck everyone with testing. It feels so strange to actually send out a pull request on this... should it ever happen?!

I've just been playing about with a few things, and updating from QS, I get this URL for plugins: http://qs0.qsapp.com/plugins/info.php?asOfDate=20111007190043&qsversion=14416&sids=com.blacktree.Quicksilver.QSEventTriggersPlugIn
which returns an empty .plist.
Also, we need to remember to update qs0.qsapp.com/download.php to point to the right stuff. This is what the QSApp download page uses, and more importantly the blacktree.com page (which we cannot change easily)

returns an empty .plist.

because asOfDate is set, so the update system only show modifications from that point (2011-10-07 19:00:43), and there are none. This list is combined with the one available locally with the one in App Support/Plugins.plist.

Also, we need to remember to update qs0.qsapp.com/download.php to point to the right stuff.

Then it should point to qs0.qsapp.com/plugins/download.php?id=com.blacktree.Quicksilver. But don't do it yet, I want to check some more before switching everyone to this...
I've fixed stuff in the update.php & add.php pages (re. different versions of plugins, missing fields). Haven't tested qs-push-plugin yet, it should be adapted to the changes in add.php for QS Applications updates (sending the dmg from the fix_build_dmg branch to qsapp.com).
What things are still missing now ? I just want to get the merge consensus of this ;-).

OK a couple more tests.
One thing that is confusing me is minHostVersion and maxHost...
QS seems to give in the URL qsversion=14416, whereas surely it should be 3850 (that's the version I'm currently on)
Secondly, I've manually edited the SQL table to give my 1Password plugin (com.robertson.onepassword) a min version of 100 and max of 14420, but it doesn't show up for this URL:
http://qs0.qsapp.com/plugins/info.php?qsversion=14416&sids=com.blacktree.Quicksilver.QSEventTriggersPlugIn
What's interesting is that 144200 DOES make the plugin show up with the above URL
Feel free to play with the versions etc. of this 1Password plugin, it's up there for testing purposes.
Secondly, which format have we gone for with the OSVersion bit? Is this working?

Then it should point to qs0.qsapp.com/plugins/download.php?id=com.blacktree.Quicksilver. But don't do it yet, I want to check some more before switching everyone to this...

Then that will always point to the latest? Great!
I guess we can upload ß54 and ß36 to this system, then just update the URLs for qsapp.com/download.php as well

(sorry again)
Also, is there a way to add a download stats count. At the moment, qs0/download.php increments the dl_stats table which gives some info on how many QS .dmgs have been downloaded. Can we do this with the new system?
Warning - something I've just realised. This new system downloads from qsapp.com NOT GitHub, so we will most likely have bandwidth problems. We have 100GB and have been using ~20GB on normal site running (not inc. the plugins system we will now have on top of this)
Perhaps we could point to GitHub - upload a mirror copy?

something I've just realised. This new system downloads from qsapp.com NOT GitHub, so we will most likely have bandwidth problems.

I thought that was an intentional change some time back. (I can’t find the e-mail.) Plug-ins are pretty small. Seems like most traffic will come from periodic checks (completely guessing), but that’s already happening, isn’t it?

Perhaps we could point to GitHub - upload a mirror copy?

Ugh. Not that again. :)

One thing that is confusing me is minHostVersion and maxHost...

That's the QS host version. Min is for "first version that can run this plugin correctly", max is for "last version known to handle this correctly". Same goes for system, but that's not implemented yet...

QS seems to give in the URL qsversion=14416, whereas surely it should be 3850 (that's the version I'm currently on)

That is the same version in fact. One thing that has been bothering me is the format of Blacktree's CFBundleVersion : it is in fact a hexstring-ified version of the "real" base-10 number (14416 in base 10 <=> 3850 in base 16). Since the notes below
say that it should be "comprised of one or more period-separated integers", I don't like them ;-).
CFBundleVersion notes - http://developer.apple.com/library/mac/#documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/20001431-102364

it doesn't show up for this URL:

That's weird... I've fixed that, seems to work now. Putting anything between 100 and 14419 will cause the plugin to appear. Anything higher, the plugin gets hidden.

Then that will always point to the latest? Great!

It's also possible to guess what the user OS X is and provide ß36 and ß54 (or ß61) depending on that. But TODO ;-)

Also, is there a way to add a download stats count.

There's a count in the table, but it is not yet displayed anywhere... Now it is, on the index, and under a plugins' update page ;-).

Warning - something I've just realised.  This new system downloads from qsapp.com NOT GitHub

True, but if we can have a good naming convention, the system could build urls to the plugin on GitHub, but atm it needs to be packaged somewhere (as a ditto archive, but I think dmg can be done easily enough...)

... but yes, I believe plugin size is not really a problem, and QS already alleviates the info.php part by adding the asOfDate parameter.

... but yes, I believe plugin size is not really a problem, and QS already alleviates the info.php part by adding the asOfDate parameter.

Sorry... I meant the .dmg itself. Plugins are fine, and we should have enough bandwidth for that. But I don't think we'd have enough for 20,000 x 5MB = 100GB

That is the same version in fact. One thing that has been bothering me is the format of Blacktree's CFBundleVersion...

OK I thought there was something iffy with QS's display. Can we change one or the other to make things look nicer? I'm easy with whatever though ideas you come up with :)
AAALMOST there! :D

Right, so I'd be happy to merge this if we can just alter the system to download APP (Quicksilver xx.dmg) updates from GitHub.
@tiennou - would this be possible?
Once it's done I say a bit more testing then we merge and release :)

It's doable, yes. I'll try to tackle that before the weekend then.
Also, I have found some weird things going on when you upgrade plugins via the "Plugin updates available" dialog. There are some times where the updatable plugin is not deleted (but the newest one is), so the next time you run QS, you'll see the Plugin update available", for the old plugin. Can someone else confirm this (It happened with the Mail Module here, but I guess you could use any other plugin, provided it's in the update system, and you have an old version somewhere).
That issue is definitely within QS. I'll try to reproduce again and fix, before the weekend I hope.

I think I see the problem. It seems that on startup, QS must be getting mixed up with which plugin it should delete.
Previously, the old and new plugins would have the same name, but @ddl_smurf altered this to give the plugins the format: PluginID.Version.qsplugin, which I guess means that the old plugins are staying.
There must be a problem with the bit that sniffs for old plugins and deletes them. I have just run through the steps with my 1Password plugin, and QS did in fact delete the old plugin when QS relaunched, and kept the new one. Perhaps QS is deleting the wrong one with the Mail plugin.
I am not sure as to where this takes place (probably in QSPluginManager.m somewhere). I will hopefully be able to assess a bit more this evening.

suggestOldPluginRemoval?
QSPluginManager.m:565

Fixed the application download stuff. That's the part of the code that's the most messy, because I got distracted by the fact that QS supported various distribution formats (ditto/qspkg, dmg, zip). Right now it's fixed to qspkg for plugins, and dmg for app updates. Does that fit everybody ?
I'm on IRC btw

Pushed a commit to my branch that fixes the duplicate plugin problem. The system was failing to register duplicates if their dependencies weren't met, and loaded the first one unconditionally when the dependency would get resolved. Since the first one is usually the one with the lower version number, it would always end up loading the older version...
Example with Apple Mail Module (since I think my explanation is sketchy ;-)) :

QS starts, (I'm looking at -loadPlugInsAtLaunch) builds the list of local plugins, check each of them for their requirements, etc. Apple Mail Module vX gets discarded at that point because it depends on Email Support, but the dependency is registered. Same for the subsequent Apple Mail Module vY.

Then, QS loads Email Support (-plugInDidLoad:). It sees there are two plugins waiting on the dependency, it loads (-liveLoadPlugIn:) the first, but since it doesn't know anymore that there is another version (the argument to - plugInIsMostRecent:inGroup: is nil at this point), then fails to load the second one since there's already a loaded plugin with this identifier.

Since it never saw duplicates, they are never added to oldPlugins, and they never get deleted in -suggestOldPluginRemoval.

Hope that makes more sense ;-). Now, it has a few shortcomings : -suggestOldPluginRemoval removes stuff unconditionally (doesn't suggest anything at all, hmm ;-)). I can see a few issues with that, since plugins can come from a lot of difference places (see -allBundles for the search path), it could delete eg. the Core Module included in QS if it finds one with a higher version number somewhere else... Opinions ?

Once again, bd81fb3 is Etienne's work and not mine. I have not checked over it... yet :)

I can see a few issues with that, since plugins can come from a lot of difference places (see -allBundles for the search path), it could delete eg. the Core Module included in QS if it finds one with a higher version number somewhere else

I don’t have a complete picture here, so I don’t know how complicated what I’m suggesting is, but perhaps the decision to delete should require both bundle ID and path to match?
I was going to say maybe we should never delete from /Library/Application Support/Quicksilver at all but I suppose if an admin user manually drops a new plug-in there, it makes sense to remove the old one.
I do think we should never delete from /Applications/Quicksilver.app, but if we check the path, the only way that could happen is if someone manually puts things there. In that case, they either know what they’re doing or deserve what they get (or both). :)

I don’t have a complete picture here, so I don’t know how complicated what I’m suggesting is, but perhaps the decision to delete should require both bundle ID and path to match?

At this moment the plugin is deleted, we have a complete plugin object with version et al. Adding a whitelist at this point would be easy enough. My opinion was a dialog asking the user with a "Always delete silently" checkbox, but I guess it would require a nib blah blah. I think QS handles translations on the fly, so maybe...
I discussed it a little on IRC with Patrick, and we agreed that deleting wasn't really appropriate in some places, like /Applications/Quicksilver.app. It also poses problems if someone use Dropbox to sync its QS configuration with different QS versions, but that is highly doubtful.
Handling that correctly would require adding min/max checking to QS (which I thought was, but it only checks for min).

I think a dialogue would be too far and require too much user input. Plus, as you've said – QS seems to handle things pretty well at the moment already :)
I think the business with different QS versions requiring different plugin versions is also far-fetched (now I've thought about it) so I don't think we have too much to worry about on that front.
I will test the 'two mail plugins installed' bug that Etienne says he's now fixed, then I'm happy with all of this :D

OK a few notes/bugs:

Fresh install works great. No problems downloading plugins. Nor with concurrent downloading - great!
asOfDate in the info.php? URL doesn't seem to work 100%. If I change something in qs0.qsapp.com/plugins/admin it doesn't show it changed for an URL such as: http://qs0.qsapp.com/plugins/info.php?asOfDate=20111017184255&qsversion=14416&sids=com.blacktree.Quicksilver.QSEventTriggersPlugIn
Not sure how to upload new QS.dmg - and then what URL they will point to on GitHub. Using the qs-push-script? Has it been modified?
Can we disable all the verbose logging - when this system goes live that's going to get crazy!
The version business is still confusing me. Looking in the SQL. It says the mail module has a version no. of 280, whereas the plugin itself (in QS and the Info.plist) says 118 :/
/plugins/admin/index.php only shows the latest plugin (if there are multiple versions in the system) - surely it should show all of them?
Downloading an app update gives me "Downloading 1000k of -0k" (i.e. the filesize should display)
File wasn't being downloaded from GitHub
The install of a newer Apple Mail module works fine - the older version is deleted.

Other than that, it all looks good! :D
I'm on IRC now if you'd like to talk!

OK I have fixed:

Clicking 'delete' in the /admin/index.php page doesn't seem to work (at least, for when there are multiple plugins)
asOfDate in the info.php? URL doesn't seem to work 100%

Problems I can't sold (perhaps @tiennou ?!)

Not sure how to upload a new QS.dmg file, and how to mirror it on GitHub. Has the qs-push-plugin script been updated?
Can we disable verbose logging
version business still confuses me
Downloading an app update gives me "Downloading 1000k of -0k" (i.e. the filesize should display)

Final push! :D

Seems like the functions.php (send_file function) is sending the right file size with the content-length header, but for some reason it isn't getting through to QS

OK so after much testing it seems like it's QS's fault (B60 works fine). I'm currently running a git bisect to see where the problem lies.
As for the other two problems:

I recall Etienne explaining the version business
I see I can upload .dmg from the online admin interface. The GitHub URL I see is just as defined in /lib/plugin.class.php (see global defined) with a filename "Quicksilver Bxx.dmg"

Almost done the git bisect now... :)

OK.... so the bad commit IS the `Application update paths' commit.
This means it's a problem with the remote PHP end and NOT Quicksilver.
@tiennou - would you be able to shed any light on this? I've checked to see that the Content-Length is getting set correctly, but where could it be going wrong?
I've even tried a <meta redirect> but that didn't work :(

...OK finally!
So it's no show stopped. It seems to be a problem with just QSApp.com not giving out the data. If I manually change the location to point to GitHub it works beautifully. this'll be the case for all end-users, so we don't have to worry.
I've submitted a support ticket to the hosts none-the-less.
Right:
@skurfer and @tiennou (sorry for all the emails)
ARE WE READY TO GO!? XD

I have to say I’ve only tested this briefly. There’s a merge conflict with the featureLevel branch, and I’d rather keep that merged in so I can make sure it’s stable. (It appears to be.) The conflict is in a XIB, so it’s nearly impossible to resolve in a text editor.
Anyway, I’ll try to test it out over the weekend, but really, my priority now is getting repos set up for the new plug-ins. (I’m currently running an iTunes plug-in that I built. Unbelievable.)

my priority now is getting repos set up for the new plug-ins.

...could you make testing this and giving it the 'ok' the priority for one
day...? :)
Once we've got this merged and the next version the world is absolutely 100%
our oyster!
If not, then I'd say that I could merge it, seeing as 99% of the work is
@tiennou's, and I've just issued the pull request.
I can't wait to get this out!
On 21 October 2011 20:44, Rob McBroom <
<EMAIL_ADDRESS>
I have to say Ive only tested this briefly. Theres a merge conflict with
the featureLevel branch, and Id rather keep that merged in so I can make
sure its stable. (It appears to be.) The conflict is in a XIB, so its
nearly impossible to resolve in a text editor.
Anyway, Ill try to test it out over the weekend, but really, my priority
now is getting repos set up for the new plug-ins. (Im currently running an
iTunes plug-in that I built. Unbelievable.)
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/491#issuecomment-2485422

The whole point of my last message (which I forgot to include) was “don’t wait for me” because you guys have more knowledge of what’s going on than I do and my testing would just be icing on the cake. If you feel good about it, go for it.

Sorry, didn't realise that's what you meant! Sounds good though :)
I'll have a final play on it today. (I actually found another bug yesterday)
but it would be good if you could

Build from plugins-system, run it from wherever you usually run your QS
app from, and click 'now' to check for updates. You should get a download
from GH (from a private repo I've set up) that is just a bumped version of
'master' with 'plugins-system' merged in.
Run with this version (it's near identical to what we'll be releasing) for
a teeny bit
Have a quick look through the 'changelog' pull request and see if there's
anything I've forgotten :) If not - merge it!

If you're too busy/don't feel like it, I'll merge and go ahead with it all!
:)
On 22 October 2011 05:26, Rob McBroom <
<EMAIL_ADDRESS>
The whole point of my last message (which I forgot to include) was dont
wait for me because you guys have more knowledge of whats going on than I
do and my testing would just be icing on the cake. If you feel good about
it, go for it.
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/491#issuecomment-2488384

Gah, more and more questions ! Here are a few answers (from a little while ago, sorry). (IRC time if you want, too ;-)). :
@pjrobertson :

asOfDate in the info.php? URL doesn't seem to work 100%. If I change something in qs0.qsapp.com/plugins/admin it doesn't show it changed for an URL such as: http://qs0.qsapp.com/plugins/info.php?asOfDate=20111017184255&qsversion=14416&sids=com.blacktree.Quicksilver.QSEventTriggersPlugIn

Hmm... I'll double-check that, but saving a plugin through the admin pages ought to update its timestamp. Will check that...

Not sure how to upload new QS.dmg - and then what URL they will point to on GitHub. Using the qs-push-script? Has it been modified?

qs-push-plugin hasn't been updated yet, but it works through the add page if you check Application Update and provide the dmg and Info.plist.

Can we disable all the verbose logging - when this system goes live that's going to get crazy!

Yes, there's a logging level for that. Right now it defaults to DEBUG, but I plan on changing it to ERROR before publicizing this.

The version business is still confusing me. Looking in the SQL. It says the mail module has a version no. of 280, whereas the plugin itself (in QS and the Info.plist) says 118 :/

The Info.plist are wrong. The REAL, integer base 10 number is the one in the database. Everything else lies ;-).

/plugins/admin/index.php only shows the latest plugin (if there are multiple versions in the system) - surely it should show all of them?

Right now you can access older versions by using the links on a plugin's update page. But a direct link ought to be nicer...

Downloading an app update gives me "Downloading 1000k of -0k" (i.e. the filesize should display)

I'm checking... Okay, this one is hard ;-). It seems the qsapp.com host gz-compress the downloaded plugin on the file. I'm sending the Content-Length with the correct file size set, but the host deletes it afterwards, since it recompress the qspkg file... That explains why I don't get the same filesize value from PHP and at download time.
And then IIRC, a long time ago I disabled the thing that gets the Content-Length header inside QS because it used private stuff that broke. It seemed better to keep the plugin system working at the expense of that number. (Hint, look around QSURLDownload for that part).

File wasn't being downloaded from GitHub

Plugins are quite small. I'm not sure about how to handle it on GitHub without a binary git repository...

The install of a newer Apple Mail module works fine - the older version is deleted.

Cool :p

Clicking 'delete' in the /admin/index.php page doesn't seem to work (at least, for when there are multiple plugins)

It works, but you won't get a direct confirmation that the deletion had taken place. Note also that an older version of the plugin will be shown if available, so it could look like nothing was deleted.

Not sure if 'delete' is also deleting the files or just the database reference.

It also delete uploaded files (both qspkg/dmg and qsinfo).
Note, this looks broken at the moment. I can't download a plugin from the qsapp.com/plugins.php page (the download.php page sends me the QS dmg everytime...).

OK, got it built, it saw the update. I removed a plug-in and redownloaded it. I got the correct (newer) version. The interface still showed old versions for plug-ins that weren’t installed, but a refresh fixed that. All seems to work so far. Won’t be able to check much else until later tonight (EST).

Great - all sounds good :)
I've just upgraded to Lion (finally - had to delete my bootcamp partition),
so will fiddle with XCode 4.
Once I'm happy, I'll try and build it and away we go!
On 22 October 2011 21:34, Rob McBroom <
<EMAIL_ADDRESS>
OK, got it built, it saw the update. I removed a plug-in and redownloaded
it. I got the correct (newer) version. The interface still showed old
versions for plug-ins that werent installed, but a refresh fixed that. All
seems to work so far. Wont be able to check much else until later tonight
(EST).
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/491#issuecomment-2492581

For those whom it may concern:
I've moved the 'delete' button from the main index.php admin page to within
the 'edit' page.
I inadvertently clicked and deleted one of the plugins yesterday, so
thought this'd be a good safety measure. It also means you can delete any
version of any plugin.
On 22 October 2011 21:43, Patrick Robertson<EMAIL_ADDRESS>
Great - all sounds good :)
I've just upgraded to Lion (finally - had to delete my bootcamp
partition), so will fiddle with XCode 4.
Once I'm happy, I'll try and build it and away we go!
On 22 October 2011 21:34, Rob McBroom <
<EMAIL_ADDRESS>
OK, got it built, it saw the update. I removed a plug-in and redownloaded
it. I got the correct (newer) version. The interface still showed old
versions for plug-ins that werent installed, but a refresh fixed that. All
seems to work so far. Wont be able to check much else until later tonight
(EST).
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/491#issuecomment-2492581


Update custom images to new ASU api

The new ASU API responses with the very same JSON format as proposed upstream. This simplifies the wizard as it can use the same code to show vanilla (aka official) images as well as custom images created by ASU.

Currently the custom image request fails anyway, instead of using chef.libremesh.org please use https://aparcar.stephen304.com/ as a backend.


LexicalMarkdownPlugin: say hello to markdown exports

This is a first pass at implementing Markdown support for lexical.
It depends on Apple's swift-markdown package.
It needs tests and covering more edges cases (embedded lists, indentations, etc) - but is enough to get started with.
I am also working on a markdown import for our use case, which I will add to this plugin in the next day or so.

Swift markdown supports a whole set of formatting options which make it easy to customise the output:
https://apple.github.io/swift-markdown/documentation/markdown/markupformatter/options/
If it doesn't support your exact variant, it should be relatively straight forward to have a fork.
One of my current challenges is having support for underline & italics - which are mutually exclusive (combined under Emphasis node) in swift markdown.

@amyworrall im yet to fix the indentation issues. Everything else is addressed.
for my project, I went another route. The javascript library has markdown import/export support and we can rely on the fact that JSON internals exported from JS are compatible with swift library (besides this fix https://github.com/facebook/lexical-ios/pull/51).
So i packed the javascript library along with 2 utility functions (convert markdown -> JSON and JSON -> markdown), and using the Javascript headless lexical editor, over a JSContext - i can do the format conversions. This turned out to be quicker than implementing the markdown import reliably.
If you're interested, i can create a branch for that too.

So i packed the javascript library along with 2 utility functions (convert markdown -> JSON and JSON -> markdown), and using the Javascript headless lexical editor, over a JSContext - i can do the format conversions. This turned out to be quicker than implementing the markdown import reliably.
If you're interested, i can create a branch for that too.

That sounds interesting from a tech perspective! For a long term Lexical iOS perspective, we probably do want to do things natively.
Did you make an attempt at the native Markdown import? If so, would you mind sharing what issues you ran into? That may save me some time when I attempt to look at it :)

I added a live markdown view in the playground and started work on imports on a branch here:
https://github.com/mansimransingh/lexical-ios/tree/markdown-importing
Just have to go through each [MarkupVisitor](https://github.com/mansimransingh/lexical-ios/blob/ca2fce9b38cb987713154c0c7371aae27b3c5f6d/Plugins/LexicalMarkdown/LexicalMarkdown/MarkdownImporter.swift#L14) function and implement correctly / map it to a lexical node.
It stacks on top of this PR.

I added a live markdown view in the playground and started work on imports on a branch here:

Awesome, will check it out.
BTW sorry for the churn on the "imported this pull request" messages -- having some trouble wiht our internal tooling.

hi! Have merged. Had to change the name of the SwiftMarkdown library, we call it SwiftMarkdown internally not just Markdown. Haven't checked that still works with the playground, will check tomorrow.


Update Terraform digitalocean to v2.28.1

This PR contains the following updates:

Package
Type
Update
Change

digitalocean (source)
required_provider
minor
2.23.0 -> 2.28.1

⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

digitalocean/terraform-provider-digitalocean
v2.28.1
Compare Source
BUG FIXES:

digitalocean_database_cluster: Fix custom create timeouts (#987). - @andrewsomething
digitalocean_droplet: Prevent inconsistent plan when enabling IPv6 (#982). - @andrewsomething
digitalocean_custom_image: use custom create timeout (#985). - @andrewsomething

v2.28.0
Compare Source
IMPROVEMENTS:

provider: Add godo's rate limiter configuration & retryable http client (#967). - @DanielHLelis
digitalocean_kubernetes_cluster: Support container registry integration (#963). - @mohsenSy
digitalocean_database_replica: Add support for resizing replicas (#977). - @andrewsomething
digitalocean_database_cluster: Add backup-restore functionality to db create (#970). - @danaelhe

BUG FIXES:

digitalocean_record: Handle pagination in data source (#979). - @andrewsomething
digitalocean_kubernetes_cluster: Require importing additional node pools manually (#976). - @andrewsomething
digitalocean_database_replica: Add uuid to data source schema (#969). - @andrewsomething

MISC:

docs: Fix inconsistencies in digitalocean_uptime_alert documentation #972 - @nicwortel
docs: Use correct links in uptime docs. #973 - @andrewsomething
provider: Update Terraform SDK to v2.26.1. #975 - @andrewsomething

v2.27.1
Compare Source
BUG FIXES:

digitalocean_database_replica: Set UUID on read to resolve import issue (#964). - @andrewsomething

MISC:

dependencies: bump golang.org/x/net (#957). - @dependabot
dependencies: bump golang.org/x/crypto (#960). - @dependabot

v2.27.0
Compare Source
IMPROVEMENTS:

digitalocean_database_cluster: Support project assignment (#955). - @andrewsomething

BUG FIXES:

digitalocean_custom_image: use correct pending statuses for custom images (#931). - @rsmitty

DOCS:

digitalocean_app: Fix typo in resource digitalocean_app (#961). - @tobiasehlert

MISC:

provider: Package reorganization (#927). - @andrewsomething
testing: Use comment trigger to run acceptance tests for PRs. (#929). - @andrewsomething
testing: Fix formatting of Terraform configs in tests and enforce in PRs using terrafmt (#932). - @andrewsomething
testing: droplet: Fix acceptance testing (#949). - @andrewsomething
testing: certificates: Add retry on delete (#951). - @andrewsomething
testing: cdn: Add test sweeper and retry with backoff (#947). - @andrewsomething
testing: Add sweeper and use consistent naming for all Spaces buckets in tests (#945). - @andrewsomething
testing: Add sweeper for uptime and monitoring alerts (#944). - @andrewsomething
testing: Add sweeper for projects and add retry for project deletion (#943). - @andrewsomething
testing: Add sweeper for VPCs (#942). - @andrewsomething
testing: Add sweeper for custom images and fix acceptance tests (#941). - @andrewsomething
testing: Use consistent naming for all volumes created in tests (#939). - @andrewsomething
testing: Use consistent naming for all snapshots created in tests (#938). - @andrewsomething
testing: Use consistent naming for all load balancers created in tests (#937). - @andrewsomething
testing: Use consistent naming for all firewalls created in tests (#935). - @andrewsomething
testing: Add sweeper for SSH keys (#940). - @andrewsomething
testing: Use consistent naming for all certs created in tests (#934). - @andrewsomething
testing: Use consistent naming for all Droplets created in tests (#933). - @andrewsomething
testing: Remove unused const to fix linting (#930). - @andrewsomething
testing: Fix flaky database acceptance tests (#953). - @andrewsomething
Remove .go-version and add to .gitignore (#958). - @ChiefMateStarbuck

v2.26.0
Compare Source
IMPROVEMENTS:

database replica: Expose Database Replica ID (#921) - @danaelhe
uptime: Add Uptime Checks and Alerts Support (#919) - @danaelhe
databases: Support upgrading the database version (#918) - @scotchneat
loadbalancers: Add firewall support for Loadbalancers (#911) - @jrolheiser
loadbalancers: Loadbalancers support http alerts metrics (#903) - @StephenVarela

MISC:

docs: routes documentation in app.md matches app_spec.go (#915) - @olaven
testing: Find previous K8s release dynamically. (#916) - @andrewsomething
docs: Fix typo in README (#920) - @mbardelmeijer
docs: Add releasing notes & missing changelog entries (#922) - @scotchneat

v2.25.2
Compare Source
IMPROVEMENTS:

database_replica: add retry on db replica create (#907) - @DMW2151

v2.24.0
Compare Source
IMPROVEMENTS:

spaces: add endpoint attribute to bucket (#886)- @selborsolrac
monitor_alert_resource: Update Monitor Alert resource with new DBAAS public alert types (#893) - @dweinshenker
spaces: Add new DC to spaces (#899) - @mandalae
loadbalancers: load balancers: add HTTP/3 as an entry protocol (#895) - @anitgandhi

MISC:

docs: Fix reference in documentation of project_resources (#890) - @Lavode

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Closing stale automated PR. Reopen if this was done in error


There was an error initializing the YouTubePlayer (INTERNAL_ERROR)

I have an issue every time run with android  'There was an error initializing the YouTubePlayer (INTERNAL_ERROR)'

.
YouTubeStandaloneAndroid.playVideo({
apiKey: 'API_KEY',
videoId: 'lctaXe3s3Ws',
autoplay: true,
startTime: 120,
lightboxMode: false
})
.then(() => console.log('Standalone Player Exited'))
.catch(errorMessage => console.error(errorMessage))
I can play video with iOS very well that have code likes
YouTubeStandaloneIOS.playVideo(youtubeId)
.then(() => console.log('Standalone Player Exited'))
.catch(errorMessage => console.error(errorMessage))
Could you guys help resolve issue with android ?

You might want to remove your API key from your question.

I also see the same error on Kitkat android physical device. If you try start a simulator has higher android ver (ex:  9.0) ,it works


Secure all pod-to-pod network traffic between dsp components

Acceptance criteria:

Catalogue pods/containers that do not use secure tls to communicate
If in scope / simple, enable tls communication for these pods

related: #492

Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1706


How to Test SRGAN?

Hi, thank you for this wonderful repo!
I've trained the network and now I want to test it, but in test_ESRGAN.yml I find that i need to give path for GT images.
How do I test the model with LR images?

have a look at this file
https://github.com/open-mmlab/mmsr/blob/master/codes/options/test/test_ESRGAN_woGT.yml


How to use ncc with Typescript unit tests?

We have a project with production code in the ./src directory and tests written in ./test. All code is written in Typescript.
Our Pre-ncc process is to compile everything to ./dist/{src|test}, then run our tests. When we switched our production code to build with ncc, our tests no longer have anything to compile against.
We are trying to figure out a best practice here. For now I think we need to keep our existing build process, then once the tests pass rebuild with ncc, but that seems sub-optimal.
Other options I've thought of all have other, worse downsides though:

Compile each unit test as its one separate ncc project - this will probably be slow and redundant
Compile test separately but have them import the compiled .js file - we lose all the typing
.... ? other options?

keep our existing build process, then once the tests pass rebuild with ncc, but that seems sub-optimal.

This is what we do for now-builders.
Does ncc take a long time to build for you?

ncc run is a drop-in replacement for node. If you are able to node your tests, then you can ncc run your tests.


[ISSUE] Job run now for a continuous job errors with KeyError: 'run_id'

Description
When executing the jobs.run_now method on a running continuous job, it fails with the following error
File "/opt/conda/envs/venv/lib/python3.11/site-packages/databricks/sdk/service/jobs.py", line 3557, in run_now
run_id=op_response['run_id'])
~~~~~~~~~~~^^^^^^^^^^
KeyError: 'run_id'
When debugging the above, it appears that the 2.1 jobs post API does not return a run_id in this scenario - its simply blank. Therefore the above code fails.
Reproduction

Create a job and set it to be continuous
When the job is running, call the jobs.run_now method

Expected behavior
The same behaviour as in the Databricks UI - an option exists when a continuous job is running in the top right to "restart run". In the chrome debugger, it appears that the run_now API is being called for that button.
Debug Logs
The SDK logs helpful debugging information when debug logging is enabled. Set the log level to debug by adding logging.basicConfig(level=logging.DEBUG) to your program, and include the logs here.
Other Information

OS: [e.g. macOS]
Version: [e.g. 0.9.0]

Facing the same issue. Any updates from Databricks?


DF BE - Polygon Mainnet

This ticket spans all backend projects: dfpy + dfpy-sql-backend
Configure production VM for Polygon Mainnet

[ ] df-py add network + verify queries, dispense are working
[ ] df-py deploy dfrewards.sol
[ ] dfpy-sql-backend configure cron to query chain + update records in DB

Testing:

Request funding in order to test the app
Dispense rewards to test addesses and verify it can be claimed
Verify user can stake on chain
Verify user is linked to pools on chain

[ ] make sure contract is verified on https://polygonscan.com/


Include CAN transport on integration tests

Also added CED middleware to binary creation tests.

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows

Build status:

Linux
Windows


Does this downloader still work?

Just wondering if anyone is having success and if not, have you found alternate programs that do work?

It works.


Allow indexes to be annotated.

Adding annotations to index is now possible.

I've factored out the commit that just cleans up the unused AST nodes. It happens to increase the test_type_coverage_edgeql coverage percentage due to all the deletions in such a way that the next commit decreases the coverage. Although the total still increases for the entire PR.


Post 2.0 docs updates

Working on some changes to improve the documentation and such.
So far:

Updated the goals to align between the site and readme
Added kylejrp's npm instructions to the readme
Added a npm widget to the site as well (thoughts?)

Note to self: make sure CSS files have .min.css suffixes.

Changing base to master, then manually making changes onto the dev branch. Doing this so the merge conflicts don't prevent me from cleanly seeing changes.


Fix panic in getSheetMap

Return early if relationship was not found for the given workbook
PR Details
Fix panic in getSheetMap where we don't check if relationship map is nil
Description
Return early on nil relationship
Related Issue

Motivation and Context
Code panics
How Has This Been Tested
UT + manual against malformed files

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Codecov Report

Merging #1443 (0c16918) into master (14d7acd) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 0c16918 differs from pull request most recent head 7103167. Consider uploading reports for the commit 7103167 to get more accurate results

@@           Coverage Diff           @@
##           master    #1443   +/-   ##
=======================================
  Coverage   98.61%   98.61%
=======================================
  Files          31       31
  Lines       24015    24018    +3
=======================================
+ Hits        23682    23685    +3
  Misses        220      220
  Partials      113      113

Flag
Coverage Δ

unittests
98.61% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sheet.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Thanks @xuri, fixed!


How to merge a project w/ template, the 1st time

Yeah, I don't see why not! Weird that Circle is even running on this repo. I'm going to ignore it...


WIP: podpresets

Will update after seeing how CI does and add tests

I might be stuck on the rebase until kubebuilder updates to 1.11.0.

I'm going to go ahead and close this. The new repository for podpresets for now is https://github.com/jpeeler/podpreset-crd.


Tracking issue: implement the linter

TODOs:

[x] add "too many parameters" warning
[ ] #500
[ ] #502
[ ] #503
[ ] #504

Hey @mtshiba. The child issues seems good for me to tinker around Erg code. I would like to work on this.
If you have any pointers to point me in the right direction, that would be great!

OK, here are the steps for adding rules to the linter.

Define a function to create a warning in erg_linter/warn.rs

For example:
pub(crate) fn true_comparison(expr: &Expr, input: Input, caused_by: String, loc: Location) -> CompileWarning {
    CompileWarning::new(
        ErrorCore::new(
            vec![
                SubMessage::ambiguous_new(loc, vec![], Some(format!("just write: {}", expr.to_string_notype()))),
            ],
            "equality checks against True are redundant".to_string(),
            0,
            ErrorKind::Warning,
            loc,
        ),
        input,
        caused_by,
    )
}

The function can take any arguments, but at least the following arguments are required.

input: file where the warning occurred
caused_by: context in which the warning occurred
loc: location where the warning occurred

The return type is CompileWarning. This is a structure that wraps ErrorCore with additional information. The following information is given to ErrorCore.

sub_messages: sub messages contain hints, etc.
main_message: main message
errno: error number, 0 for now
kind: error type, ErrorKind::Warning
loc: location where the warning occurred

Add lint_* methods to Linter in erg_linter/lint.rs

For example, let's add a rule to warn about redundant expressions such as x == True. This rule can be implemented with a method like this.
impl Linter {
    ...
    fn lint_bool_comparison(&mut self, chunk: &Expr) {
        match chunk {
            Expr::BinOp(binop) => {
                let lhs = <&Literal>::try_from(binop.lhs.as_ref()).map(|lit| &lit.value);
                let rhs = <&Literal>::try_from(binop.rhs.as_ref()).map(|lit| &lit.value);
                let lhs_or_rhs = lhs.or(rhs);
                let func = match (binop.op.kind, lhs_or_rhs) {
                    (TokenKind::DblEq, Ok(ValueObj::Bool(true))) => true_comparison,
                    (TokenKind::DblEq, Ok(ValueObj::Bool(false))) => false_comparison,
                    (TokenKind::NotEq, Ok(ValueObj::Bool(true))) => false_comparison,
                    (TokenKind::NotEq, Ok(ValueObj::Bool(false))) => true_comparison,
                    _ => return,
                };
                let expr = if lhs.is_ok_and(|val| val.is_bool()) {
                    binop.rhs.as_ref()
                } else if rhs.is_ok_and(|val| val.is_bool()) {
                    binop.lhs.as_ref()
                } else {
                    return;
                };
                let warn = func(
                    expr,
                    self.input(),
                    self.caused_by(),
                    binop.loc(),
                );
                self.warns.push(warn);
            }
            _ => self.check_recursively(&Self::lint_bool_comparison, chunk),
        }
    }
    ...
}

I used some conversion functions and helper methods. Please check docs.rs to find out what APIs are available. Or you can implement methods plainly without using helper methods.
Creates a warning and adds it to Linter.warns when expr meets the condition.
You can apply this rule recursively to the expressions in expr with check_recursively.

Add method checks inside Linter.lint's main loop

    pub fn lint(&mut self, src: String) -> Result<CompileWarnings, ErrorArtifact> {
        log!(info "Start linting");
        let art = self.builder.build(src, "exec")?;
        self.warns.extend(art.warns);
        for chunk in art.object.module.iter() {
            self.lint_too_many_params(chunk);
+           self.lint_bool_comparison(chunk);
        }
        log!(info "Finished linting");
        Ok(self.warns.take())
    }

That's all!


Nothing happens when click the play button for both shumway and flash.

SWF: b1270a163a9feebac8f6e8b12b63ebbddcefda0850a63bc6ea2029adc1fd30c3 (Direct Link)

Given that there's no difference between Flash's and Shumway's behavior, there's nothing for us to do here.


Update data structures and constants from latest beacon chain spec

A bunch of the data structures and constants have changed in the beacon chain spec.
This brings the code up to the latest spec in regards to the data structures and constants. Where possible, a variable's name and order is identical to the camel-case-ified name and order of the variables in the spec.
This also minimally fixes existing helper functions and test functions.

Thanks for your contribution! I haven't had a chance to look at the code but the CI is telling me the linter failed.
Could you run npm run lint, if it doesn't make the changes for you can add --fix


About the codes next to AddComponent();

void Start()
{
    UIEffect uiEffect = gameObject.AddComponent<UIEffect>();
    uiEffect.effectMode = EffectMode.Sepia; //Error[0]
    uiEffect.effectFactor = 1f;
    uiEffect.effectColor = Color.white;
    uiEffect.colorMode = ColorMode.Fill; //Error[1]
    uiEffect.colorFactor = 1f;
}

//Error[0]: Assets\AddUiEffect.cs(12,9): error CS0200: Property or indexer 'UIEffect.effectMode' cannot be assigned to -- it is read only
//Error[1]: Assets\AddUiEffect.cs(15,9): error CS0200: Property or indexer 'UIEffect.colorMode' cannot be assigned to -- it is read only
So the effectMode/colorMode can only be changed in the inspector?

Hi @atkdefender
Yes, they are read only properties.
In next release version (v4.0.0), they will be changed with script. :+1:

Got it.
Thank you for answering. And an awesome asset!
I got a UI blur shadow that can use in my game.


Some commands are deprecated

Tried to follow this but got into some errors that are related to the quick evolution of Istio. One example is that istioctl lo longer has the authn command.
This should be updated to work with Istio 1.7/1.8.

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

ID: 04e91998-d53d-5074-5c67-0f9f031bc26c
Version Independent ID: 989fa4fe-e7a8-2003-6a89-73beaade1b80
Content: Use Istio for intelligent routing - Azure Kubernetes Service
Content Source: articles/aks/servicemesh-istio-scenario-routing.md
Service: container-service
GitHub Login: @paulbouwer
Microsoft Alias: pabouwer

@lmqferreira Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate. We will update you accordingly.

@lmqferreira Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate. We will update you accordingly.

@paulbouwer Can you please check and add your comments on this doc update request as applicable

@paulbouwer Can you please check and add your comments on this doc update request as applicable

@lmqferreira - thank you for submitting feedback on this set of content. As you mentioned, it is an ongoing task to keep samples compliant with rapidly iterating Istio releases.
@psmanhas - we have been discussing deprecating this content around canary releases as part of a reworking of this service mesh section. We have discussed directing readers to Flagger which automates all of these steps. Flagger is a Progressive Delivery Operator for Kubernetes which can run automated application analysis, testing, promotion and rollback for the following deployment strategies:

Canary (progressive traffic shifting)
A/B Testing (HTTP headers and cookies traffic routing)
Blue/Green (traffic switching and mirroring)

@lmqferreira - thank you for submitting feedback on this set of content. As you mentioned, it is an ongoing task to keep samples compliant with rapidly iterating Istio releases.
@psmanhas - we have been discussing deprecating this content around canary releases as part of a reworking of this service mesh section. We have discussed directing readers to Flagger which automates all of these steps. Flagger is a Progressive Delivery Operator for Kubernetes which can run automated application analysis, testing, promotion and rollback for the following deployment strategies:

Canary (progressive traffic shifting)
A/B Testing (HTTP headers and cookies traffic routing)
Blue/Green (traffic switching and mirroring)

Thank you for the feedback.
We've added a task to our backlog and will prioritize accordingly.
#please-close


A conditional value was caught referencing a nonexistent breakpoint.

I don't understand how can we replicate the example app in our own code, I am getting this error when trying to do the same. I was previously using 0.2.0 but when I migrated to 1.0.0 I am having these issues. Can anyone help?

This is my debug log:
======== Exception caught by widgets library =======================================================
The following assertion was thrown building Builder(dirty):
A conditional value was caught referencing a nonexistent breakpoint.
ResponsiveValue requires a parent ResponsiveWrapper to reference breakpoints. Add a ResponsiveWrapper or remove breakpoint references.
The relevant error-causing widget was:
MaterialApp MaterialApp:file:///home/lenovo/Aeologic/projects/omgiva/lib/main.dart:141:16
When the exception was thrown, this was the stack:
dart-sdk/lib/internal/js_dev_runtime/private/ddc_runtime/errors.dart 266:49  throw
packages/responsive_framework/responsive_value.dart 34:9                      new
packages/omgiva/main.dart 169:26
packages/flutter_easyloading/src/easy_loading.dart 241:23
packages/flutter/src/material/app.dart 957:33
packages/flutter/src/widgets/basic.dart 7448:48                               build
packages/flutter/src/widgets/framework.dart 5038:22                           build
packages/flutter/src/widgets/framework.dart 4968:15                           performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                            rebuild
packages/flutter/src/widgets/framework.dart 4950:5                            [_firstBuild]
packages/flutter/src/widgets/framework.dart 4944:5                            mount
packages/flutter/src/widgets/framework.dart 3953:15                           inflateWidget
packages/flutter/src/widgets/framework.dart 3682:18                           updateChild
packages/flutter/src/widgets/framework.dart 4993:16                           performRebuild
packages/flutter/src/widgets/framework.dart 4690:5                            rebuild
packages/flutter/src/widgets/binding.dart 1092:16
packages/flutter/src/widgets/framework.dart 2682:19                           buildScope
packages/flutter/src/widgets/binding.dart 1091:12                             attachToRenderTree
packages/flutter/src/widgets/binding.dart 925:24                              attachRootWidget
packages/flutter/src/widgets/binding.dart 906:7
dart-sdk/lib/_internal/js_dev_runtime/private/isolate_helper.dart 48:19       internalCallback
This is my main.dart file:
ResponsiveBreakpoints.builder(
                  breakpoints: [
                    Breakpoint(start: 0, end: 480, name: MOBILE),
                    Breakpoint(start: 481, end: 1200, name: TABLET),
                    Breakpoint(start: 1201, end: 1600, name: DESKTOP),
                  ],
                  child: MaxWidthBox(
                    // A widget that limits the maximum width.
                    // This is used to create a gutter area on either side of the content.
                    maxWidth: 922,
                    background: Container(color: ColorConstants.lightGrey),
                    child: ResponsiveScaledBox(
                      width:
                          ResponsiveValue<double>(context, conditionalValues: [
                        Condition.equals(name: MOBILE, value: 480),
                        Condition.between(start: 0, end: 481),
                        Condition.equals(name: TABLET, value: 1200),
                        Condition.between(start: 481, end: 922),
                        // There are no conditions for width over 922
                        // because the `maxWidth` is set to 922 via the MaxWidthBox.
                      ]).value,
                      child: _streamChatWidget(child),
                    ),
                  ),
                );

Same issue here, I think 1.0.0 needs some more work

Thanks @zhgwu  this seems to have solved the error above.

Thanks


Threading issues

When I run main.py, I get the following error:
RuntimeError:
An attempt has been made to start a new process before the
current process has finished its bootstrapping phase.
    This probably means that you are not using fork to start your
    child processes and you have forgotten to use the proper idiom
    in the main module:

        if __name__ == '__main__':
            freeze_support()
            ...

    The "freeze_support()" line can be omitted if the program
    is not going to be frozen to produce an executable.
w.start()

We did not manually initiate any threads or processes in our original code. And we did not encounter any such issues.
Have you followed the instructions in the readme file and tried executing the following command in your command line: python main.py --gpu 0 --exp office31 --dataset office31 --source amazon --target dslr?


Possibility of using oc rsync

Description:
Checking the way you are doing all the rsync process from Source to Dest cluster seems like it includes different checks, validations, dependencies, etc; which make - specifically the 3rd step - kind of complicated (where configMaps, Services, Routes, Stunnel configs, SSH-keys, etc are involved)
Is the a way to just use oc rsync to do the file copy from the source worker node (where the PVC is mounted) to the Dest pvc-migrate-pod-*. With it we will reduce the dependencies to two, which are:

oc-cli (which majority of our OCP v3.11 worker nodes already have)
rsync (easy to install)
SA token to do the oc login

The command that should be used would look like:
$ oc -n <NS> rsync <PVC-dir-mounted-on-worker> <pvc-migrate-pod-*>:/mnt/<NS>/<PVC-name>/ -c <container-name>

My apologies in advance, if this way was already tested and did not work as I'm exposing here.
Reference: https://docs.openshift.com/container-platform/3.11/dev_guide/copy_files_to_container.html

Hi @lcordero
The main reason we didn't pursue oc rsync was concern of how reliable oc rsync would be at handling long running operations for large PVs (~100GB+).  In past work on Ansible Playbook Bundles for the OpenShift Ansible Service Broker, we ran into several problems when we relied on oc rsync for long lived (several hour+) operations.  Concern was how reliable this mechanism would be for processing large PVs that took multiple hours to transfer.
I'll leave this issue open so we can evaluate if this is worth investigating, it's possible the concerns we saw ~2 years ago have been addressed.

Hello @jwmatthews
I have been working on a PoC of the pvc-migrate code working with oc rsync. Below you'll find the changes I did to your code and also the result of a real test I perform.
Code changes:
https://github.com/lcordero/pvc-migrate/pull/1/files
Test:
PVC-size: 2.2Gb
Time playbooks started: Fri Aug 28 22:30:23 IST 2020
Time playbooks finished: Fri Aug 28 22:33:37 IST 2020
Take into account that the time also includes the pod creation/deletion (and how long it takes to be created/removed)
Next tests:
Migrate a PVC size of 100Gb

@lcordero great, 'oc rsync' as an option would be nice and simple.
Perhaps we could offer both as a choice.
Will defer to @alaypatel07 and @pranavgaikwad to chime in later as this investigation moves along

@jwmatthews;
I did a bigger test; here the details:
PVC1:
sh-4.2$ df -h /lcordero-test
Filesystem                                          Size  Used Avail Use% Mounted on
<IP_ADDRESS>:vol_bac5f06d1fdb6bdd815420be3074ae23   12G  2.2G  9.9G  18% /lcordero-test

PVC2:
sh-4.2$ df -h /lcordero-test-huge/
Filesystem                                          Size  Used Avail Use% Mounted on
<IP_ADDRESS>:vol_8c91095e039184c3e8f9cc3c61b910aa  188G  173G   15G  93% /lcordero-test-huge

MigrationStart time:
Sat Aug 29 03:39:02 IST 2020
MigrationEnd time:
Sat Aug 29 06:47:07 IST 2020
Total Time:
~3h 8m
Average Speed copy data:
~1Gb per minute

+1 on the oc rsync approach to reduce the complexity of stage 3.
@lcordero your last comment said the average speed was 1Gb/min which would correspond to 16,67 Kb/s - that's below modem speed. Any idea why it was that slow?

oc rsync is a wrapper around oc rsh. Underneath the hood, oc rsh uses SPDY Stream Executor. SPDY is a protocol developed by google replaced with HTTP/2 now (I think). The way this works is: oc client creates an HTTP connection to kube apiserver which is upgraded to a bi-directional stream (SPDY protocol) - 1st connection stream. The kube-apiserver recognizes that this is a request to open a shell on a container, it gets the node and opens a separate connection to the kubelet on that node (SPDY): connection 2. The kube-apisever proxies all the information between the kubelet and client. The kubelet in turn makes a gRPC connection to the underlying container-runtime that manages the container on the node, 3rd connection. This three-way tunnel  oc client<->api-server<->kubelet<->CRIO is not a recommended way to migrate data at scale, the major concerns are performance and security. Kubelet by default terminates all ssl connections and leaves some exposure to man-in-the-middle attacks (I am hazy on exact details, but added a source[1] here for more details).

https://erkanerol.github.io/post/how-kubectl-exec-works/


http-01 self check failed for domain "captioned-images.zeeromed.com"

Hi, i read a lot of article on thi error but i can't resolve it.
My Issuer
apiVersion: certmanager.k8s.io/v1alpha1
kind: ClusterIssuer
metadata:
  name: letsencrypt-staging
spec:
  acme:
    server: https://acme-staging-v02.api.letsencrypt.org/directory
    email: 'myemail'
    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt-staging
    # Enable HTTP01 validations
    http01: {}

My ingess
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: captioned-images-ipv4-ingress
  annotations:
    kubernetes.io/ingress.global-static-ip-name: captioned-images-ipv4-address
    certmanager.k8s.io/acme-http01-edit-in-place: "true"
    certmanager.k8s.io/acme-challenge-type: "http01"
    kubernetes.io/ingress.class: nginx
    certmanager.k8s.io/cluster-issuer: letsencrypt-staging
    kubernetes.io/tls-acme: “true”
spec:
  rules:
  - host: captioned-images.zeeromed.com
    http:
      paths:
      - backend:
          serviceName: captioned-images-web
          servicePort: 80
  - host: assets-captioned-images.zeeromed.com
    http:
      paths:
      - backend:
          serviceName: captioned-images-assets
          servicePort: 80
  tls:
  - secretName: tls-staging-cert
    hosts:
    - captioned-images.zeeromed.com

My certificate
Name:         tls-staging-cert
Namespace:    default
Labels:       <none>
Annotations:  <none>
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Certificate
Metadata:
  Cluster Name:
  Creation Timestamp:  2018-10-16T06:47:04Z
  Generation:          0
  Owner References:
    API Version:           extensions/v1beta1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Ingress
    Name:                  captioned-images-ipv4-ingress
    UID:                   6f41cf18-d054-11e8-9c77-42010a8001c3
  Resource Version:        900344
  Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/default/certificates/tls-staging-cert
  UID:                     4ac8afb6-d10f-11e8-9c77-42010a8001c3
Spec:
  Acme:
    Config:
      Domains:
        captioned-images.zeeromed.com
      Http 01:
        Ingress:  captioned-images-ipv4-ingress
  Dns Names:
    captioned-images.zeeromed.com
  Issuer Ref:
    Kind:       ClusterIssuer
    Name:       letsencrypt-staging
  Secret Name:  tls-staging-cert
Status:
  Acme:
    Order:
      Challenges:
        Authz URL:  https://acme-staging-v02.api.letsencrypt.org/acme/authz/MnWGymUGShE7Iqy9vYrVDt2r0LTx_Uq1TkNJ_Ivai14
        Domain:     captioned-images.zeeromed.com
        Http 01:
          Ingress:  captioned-images-ipv4-ingress
        Key:        e8_xH_NoC9j0pQ7oLCuXiincttQ5CVgKbLbReEau5DI.if8ZlzyIfQrOXYheUwV1HmYLLiC-z9Zgkciqn16Y2nc
        Token:      e8_xH_NoC9j0pQ7oLCuXiincttQ5CVgKbLbReEau5DI
        Type:       http-01
        URL:        https://acme-staging-v02.api.letsencrypt.org/acme/challenge/MnWGymUGShE7Iqy9vYrVDt2r0LTx_Uq1TkNJ_Ivai14/183317496
        Wildcard:   false
      URL:          https://acme-staging-v02.api.letsencrypt.org/acme/order/7136397/10574638
  Conditions:
    Last Transition Time:  2018-10-16T07:02:49Z
    Message:               http-01 self check failed for domain "captioned-images.zeeromed.com"
    Reason:                ValidateError
    Status:                False
    Type:                  Ready
Events:
  Type    Reason       Age   From          Message
  ----    ------       ----  ----          -------
  Normal  CreateOrder  15m   cert-manager  Created new ACME order, attempting validation...

My kubectl log
I1016 07:03:49.304321       1 controller.go:171] certificates controller: syncing item 'default/tls-staging-cert'
I1016 07:03:49.305245       1 sync.go:274] Preparing certificate default/tls-staging-cert with issuer
I1016 07:03:49.305601       1 logger.go:43] Calling GetOrder
I1016 07:03:49.451353       1 logger.go:73] Calling GetAuthorization
I1016 07:03:49.511342       1 logger.go:93] Calling HTTP01ChallengeResponse
I1016 07:03:49.511803       1 prepare.go:279] Cleaning up old/expired challenges for Certificate default/tls-staging-cert
I1016 07:03:49.511952       1 logger.go:68] Calling GetChallenge
I1016 07:03:49.721288       1 http.go:134] wrong status code '404'
I1016 07:03:49.721546       1 helpers.go:201] Found status change for Certificate "tls-staging-cert" condition "Ready": "False" -> "False"; setting lastTransitionTime to 2018-10-16 07:03:49.721537176 +0000 UTC m=+84162.893140210
I1016 07:03:49.721589       1 sync.go:276] Error preparing issuer for certificate default/tls-staging-cert: http-01 self check failed for domain "captioned-images.zeeromed.com"
I1016 07:03:49.721979       1 sync.go:206] Certificate default/tls-staging-cert scheduled for renewal in -696 hours
I1016 07:03:49.729879       1 controller.go:168] ingress-shim controller: syncing item 'default/captioned-images-ipv4-ingress'
I1016 07:03:49.730529       1 sync.go:140] Certificate "tls-staging-cert" for ingress "captioned-images-ipv4-ingress" already exists
I1016 07:03:49.730646       1 sync.go:143] Certificate "tls-staging-cert" for ingress "captioned-images-ipv4-ingress" is up to date
I1016 07:03:49.730767       1 controller.go:182] ingress-shim controller: Finished processing work item "default/captioned-images-ipv4-ingress"
E1016 07:03:49.731251       1 controller.go:180] certificates controller: Re-queuing item "default/tls-staging-cert" due to error processing: http-01 self check failed for domain "captioned-images.zeeromed.com"
I1016 07:03:52.170668       1 controller.go:168] ingress-shim controller: syncing item 'default/captioned-images-ipv6-ingress'
I1016 07:03:52.170993       1 sync.go:65] Not syncing ingress default/captioned-images-ipv6-ingress as it does not contain necessary annotations
I1016 07:03:52.171115       1 controller.go:182] ingress-shim controller: Finished processing work item "default/captioned-images-ipv6-ingress"
I1016 07:03:54.914840       1 controller.go:168] ingress-shim controller: syncing item 'default/captioned-images-ipv6-ingress'
I1016 07:03:54.914892       1 sync.go:65] Not syncing ingress default/captioned-images-ipv6-ingress as it does not contain necessary annotations
I1016 07:03:54.914916       1 controller.go:182] ingress-shim controller: Finished processing work item "default/captioned-images-ipv6-ingress"

I'm seeing this a lot

I'm also getting this, as well as
GET /.well-known/acme-challenge/XXXXXXXXXXXXXXXXX-XXXXXXXXXXXXXXXXXX => generated 5016 bytes in 5 msecs (HTTP/1.1 404)

in my pod logs.

I have a set up working for dev. that I merged to master, removed dev. everywhere and now it can't resolve the domains? They're hosted on the same box, DNS looks good, I can get the temporary SSL cert, but it can't see itself 😞 I can hit dev. which works (and it managed to get a proper cert for that).

seeing the same issue; any news on this?

I had not existing cert, so no idea. I close because I don't find solution and help, thx all.

Did someone determine what causes this? Running into this with 0.4.1

Any findings/idea/solution?

I my case acmesolver rightly complained about a 404 as requests to the ACME solver ingress were rewritten, so instead of /.well-known/… the path was something like /foobar/.well-known/…. I solved this by telling cert-manager not to create a separate ingress for ACME validation with the certmanager.k8s.io/acme-http01-edit-in-place: "true" annotation on the ingress whose cert failed to renew.

We have the same problem. Have tried the tips mentioned, but with no luck.
Image: quay.io/jetstack/cert-manager-controller:v0.5.2
Test:
curl -i http://<removed>/.well-known/acme-challenge/<removed>
HTTP/1.1 200 OK
Server: nginx/1.15.8
Date: Tue, 21 May 2019 10:42:36 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 87
Connection: keep-alive

OAKxOVGRzWjZ<removed>

Have been like this for 2 weeks.


[DOCS] Fixed NDCG formula issues

When j is 0, log(j+1) will be 0, and this leads to division by 0 issue.
What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Ping @yueguoguo

@srowen Thanks Sean. Good suggestion and I have pushed new commits.

Test build #4281 has started for PR 22090 at commit f87cf61.

Test build #4281 has finished for PR 22090 at commit f87cf61.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged to master/2.3


Setting simple of ThreadedHole to false does not work

This is the pillow block example from the docs. I changed the ClearanceHole to ThreadedHole, and set simple to False.
# Create the pillow block
with BuildPart() as pillow_block:
    with BuildSketch():
        RectangleRounded(width, height, fillet_radius)
    extrude(amount=thickness)
    with Locations((0, 0, thickness)):  # On the top
        PressFitHole(bearing=skate_bearing, interference=0.025 * MM)
        with GridLocations(width - padding, height - padding, 2, 2):
            ThreadedHole(fastener=cap_screw, simple=False)

But in the ocp_vscode window there were no threads in the result model.

I exported the pillow block into a .step file and opened it with freecad, still no threads, only simple holes.

Thanks for raising the issue.  This is actually a limitation of build123d as this ThreadedHole object does two things:
1- makes a hole by creating the hole object and combining it with the ongoing object with mode=Mode.SUBTRACT
2- make the thread which needs to be added to the ongoing object with mode=Mode.ADD (this operation will commonly result in invalid geometry generated by the OCCT CAD kernel)
but, build123d doesn't currently support chained operations like this.
Thread is very difficult for the OCCT CAD kernel to work with so I've found that the best way to work around this limitation is to create an assembly, in this case of the pillow block and the thread, which isn't something ThreadedHole can do by itself. Unfortunately there is no easy fix for this.

I'm not very familiar with mechanical design, but is it ok to make a threaded hole by subtracting a threaded screw? I find it produces an threaded hole that at least looks good.

Manually making a hole and adding IsoThread works. I'll just take it as a temporary solution.
Cylinder(2 / 2, 3, mode=Mode.SUBTRACT,
         align=(Align.CENTER, Align.CENTER, Align.MAX))
with Locations((0, 0, -3)):
    IsoThread(major_diameter=2, pitch=0.4, length=3, external=False,
              end_finishes=("fade", "fade"))


Bug 1758962: bump(github.com/openshift/library-go): hide secrets in logs

/retest

Is this a backport?

@ashcrow yes


Mouse scroll events with mouse coordinates

Hey, I'd like to improve the VScroll object to only scroll when the mouse is over the control being scrolled. As it is now, if there are multiple vscroll areas, they all respond to all mouse scroll events and scroll in unison.
To implement this I think the scroll event needs to include the mouse coordinates. If the coordinates are included, it should be easy to use them to filter the events for the control.
An alternative may be to use hoverable to decide when to respond to scroll events, but this doesn't work quite right at the moment either, because mouse-move is only received when the window is focused. To feel correct, scroll functionality should work the same regardless of focus. I think this option is less good because it also entails the app receiving a lot more events when the window is not focused.
Thanks!
Darrick

Thanks! I created https://github.com/HumbleUI/JWM/issues/227 to track this. I would appreciate any help.

Hey, I just tried out the 685beef change. It does improve the behaviour but I think it's still not quite right because the scroll now behaves oddly when the window isn't focused because (at least on mac) the hover event doesn't come through.
For example, if the mouse is hovered over a scrollable element, then I Cmd+Tab away from the window, any time I scroll while hovering the window, the previously hovered element scrolls. Even if I click on the window but don't move the mouse, it's still the previously hovered element that scrolls.
I'm sorry if I'm being too finicky, I know this is early software so if this isn't helpful, let me know and I'll stop bothering you!
OTOH, I do like the fact that, if a scrollable area comes under the cursor when scrolling its containing area, the scroll context doesn't change unless the mouse moves. That probably wouldn't be the case of simply using coordinates on every scroll event.

Yes I noticed that too. We’ll fix that eventually :)


Are you still solving issues?

I've had a couple issues I was wanted to solve but I don't know if you were still addressing them or not.

It isn't working on tiktok at all anymore. I have the latest version, but it stopped working today. I just get a message saying they're offline and it's doing to every live I've tried it on.

Also, when I tried upgrading to the newest version, I get this message:
go: downloading github.com/go-olive/olive v0.5.2
go: github.com/go-olive/olive@latest: <EMAIL_ADDRESS>verifying module: checksum mismatch
        downloaded: h1:xlTDXxfmISEUriGC+lANuZHBrGhBCaHK0CpFU4L1+js=
        sum.golang.org: h1:awAjnl3qHcHSQinNrjGiExC9TSPhWS1xEjwU9Wxjjgk=

SECURITY ERROR
This download does NOT match the one reported by the checksum server.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.

I dunno if this has anything to do with it not working on tiktok.

Well now, it doesn't seem to be recording at all now for real. I've waited 20+ minutes and can't get it to work anymore. Even if it does eventually work, it takes way too long to get started and isn't practical to use anymore. I don't know what's going on with it or why it takes forever to work.

It appears TikTok is blocking the requests somehow now. When I use it, it sometimes says my IP or country might be blocked.


Update 'Getting Started' to include non-Node libs

List details of libraries needed on MacOS when installing from scratch.

Please see https://github.com/mozilla/pdf.js/wiki/Squashing-Commits

Moreover, why are these necessary? PDF.js doesn't rely on them, and we have contributors working on Mac as well and never heard about these being required...

I found that, on an almost new Mac system (MacOS 10.15.5), the instructions in the README did not work.  I couldn't npm install successfully until I'd installed canvas & friends manually via brew.  My suspicion would be that other contributors already have these deps installed or, as you said, packages were pre-built at the time they followed the README.
I'm happy to document this elsewhere such as the FAQ or a new Wiki page instead if you'd prefer that.  I can't comment on the need for canvas; I was only focusing on making the README more useful to new contributors.

Related to Automattic/node-canvas/issues/1587. Adding the package request to packages.json solves the issue. Since the instruction is deleted from Automattic/node-canvas/issues/1511, I am not sure it is an appropriate one at present.

OK, so the only reason we need these extra steps here that were not necessary before is because upstream does not provide valid prebuilt canvas packages anymore, at least not without adding a dependency to package.json that we don't even use, or we need to install extra packages to compile canvas.
I think a better solution here would be to do neither or the two, and instead do something like https://github.com/mozilla/pdf.js/pull/11964/files where we mention in the README file of the example that a prerequisite is installing canvas. This way a regular clone of PDF.js will not require this dependency at all anymore. We only need to check if canvas is indeed only used for the example.

We only need to check if canvas is indeed only used for the example.

The canvas package is primarily used for the unit-tests, when running on Node.js/Travis; please see https://github.com/mozilla/pdf.js/blob/ac4a5c3ace85c22880e2fb9ead3cff4fbb12c5c4/test/unit/test_utils.js#L65-L69

Hm, I'm wondering if adding the request package temporarily (until upstream issues are fixed) is the least bad solution here. For me it's better than asking people to install software globally on their workstation. Opinions?

Another solution is executing the following explicitly:
npm install --save-dev canvas

Then, prebuilt binaries and required libraries are installed in node_modules/canvas/build/Release without errors. I do not know why this works well. After the installation, npm install causes no error.
One thing making things complicated is that the package request is deprecated. See https://github.com/request/request#deprecated
The following is my configuration.
OS: macOS Highe Sierra 10.13.6
npm: 6.14.5
node: v12.16.3

I was surprised that the needle issue appeared to be addressed (according to the bug report) and I wanted to try resolving this with request... but since it's deprecated, I thought I'd take a closer look or by re-open the needle bug.  So, I uninstalled the libraries using brew, blew away my node_modules and tried installing again and.... it worked?
Which was a bit odd, until I compared the checkout I made directly from the project 2 days ago (instead of my fork), and found that needle had installed at 2.3.something instead of 2.5.0.  No idea why, since both were new checkouts and 2.5.0 was released last month, but um.... OK then 🤷 .
"But Dylan, get to the point!" you reasonably cry: https://github.com/mozilla/pdf.js/pull/12024 forces needle to 2.5.0 or higher and this issue is obsolete; No need to replace dependencies, bundle packages or update READMEs.


Demo is not working

When I access the demo link in the docs I get the following error:

Maybe it was an issue with sandbox, please try again.


as

Whoops. Not sure how that happened so quickly. Did not intend to open this issue. Some combination of keyboard presses led to: the new issue page, focus on the body input, inserted content, and opened the issue within a second or so...
Sorry!


Reproducer for DROOLS-1470 Match.getObjects() should include acculumates

See
https://issues.jboss.org/browse/DROOLS-1470
Let's discuss. Maybe we need a new method getObjectsDeep() instead if we can't change getObjects() for backwards compatibility reasons.

Replaced by https://github.com/droolsjbpm/drools/pull/1138


Make all button variants use util function for printing source.

Figured while I was there I'd make everything use the same function...

:+1: nice!


⚠ Bofrost.de has degraded performance

In 87b839d, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 5259 ms

Resolved: Bofrost.de performance has improved in 5594351 after 6 minutes.


docker build fails using go v1.16 or above

docker build fails using the golang docker image v1.16 or above. This seems to be due to a different way how the go get command operates.
The go get command is used to download the timezone package to generate the timezone database.
A solution could be to directly depend to the library instead of just using it at build time

hm it is something related to the docker image bases, checkout https://stackoverflow.com/questions/57648290/golang-cannot-find-package-in-docker-image

@tsony-tsonev the new version with memory shapefile support is ready.
At the moment the docker image is at github.com/noandrea/geo2tz:master

Hm im unable to build the dockerfile
 sudo docker build -t noandrea/geo2tz https://raw.githubusercontent.com/noandrea/geo2tz/master/Dockerfile

gives
Step 5/18 : RUN curl -LO https://github.com/evansiroky/timezone-boundary-builder/releases/download/2020d/timezones-with-oceans.geojson.zip
 ---> Using cache
 ---> 4330eddce4c4
Step 6/18 : RUN unzip timezones-with-oceans.geojson.zip
 ---> Using cache
 ---> e2d1ac968633
Step 7/18 : WORKDIR /builder
 ---> Using cache
 ---> c479688ded39
Step 8/18 : COPY . .
 ---> Using cache
 ---> 42e2c529418c
Step 9/18 : RUN go get -d -v
 ---> Running in eff0bebeeeaf
go: go.mod file not found in current directory or any parent directory; see 'go help modules'
The command '/bin/sh -c go get -d -v' returned a non-zero code: 1

thanks for reporting, should be fixed now.
here the latest docker  release https://github.com/noandrea/geo2tz/pkgs/container/geo2tz
if you still have problem, please reopen the issue

I'm still unable to run the image with the memory shapefile:
sudo docker pull ghcr.io/noandrea/geo2tz:latest

latest: Pulling from noandrea/geo2tz
Digest: sha256:fcf44f1b35382f43c265827c10e917e1d00243e867e5660f0dea3ae8134643af
Status: Image is up to date for ghcr.io/noandrea/geo2tz:latest
ghcr.io/noandrea/geo2tz:latest

sudo docker run -it --mount type=bind,source=`pwd`/config.yaml,target=/etc/geo2tz/config.yaml -p 2004:2004 noandrea/geo2tz

 / ____|         |__ \| |
| |  __  ___  ___   ) | |_ ____
| | |_ |/ _ \/ _ \ / /| __|_  /
| |__| |  __/ (_) / /_| |_ / /
 \_____|\___|\___/____|\__/___| version 0.0.0
ERRO[0000] Error starting the server open timezone.snap.json: no such file or directory

with config.yaml
cat config.yaml

tz:
    database_type: memory
    database_name: timezone
    snappy: true

I'm unable to reopen the issue

https://github.com/noandrea/geo2tz/issues/6


Scope the typography shorthand to CSS

Fixes https://github.com/tokens-studio/sd-transforms/issues/17
Also adds a typography shorthand transformer for Jetpack Compose. It uses TextStyle and maps the properties of the typography tokens to the properties in Compose.
I could not find a way to match paragraphSpacing, it therefore is skipped.

Ah also run a npm run format, will usually fix the linting/formatting issues automatically.