Database password ends with special characters like '@' causes incorrectly parsing.

Bug Report

Versions

Driver: r2dbc-mysql
Database: mysql8
Java: openjdk-11
OS: OSX

Current Behavior

When accessing database using password that ends with character '@', which means there are two '@' lies before hostname in database url, I went into a DataAccessResourceFailureException that tells me the parser could not recognize the hostname.

Stack trace
org.springframework.dao.DataAccessResourceFailureException: Failed to obtain R2DBC Connection; nested exception is java.net.UnknownHostException: @localhost:3306: nodename nor servname provided, or not known
	at org.springframework.data.r2dbc.connectionfactory.ConnectionFactoryUtils.lambda$getConnection$0(ConnectionFactoryUtils.java:70) ~[spring-data-r2dbc-1.1.4.RELEASE.jar:1.1.4.RELEASE]
	Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
	|_ checkpoint ⇢ Handler com.spike.roedeercarnival.controller.TestFindController#list() [DispatcherHandler]
	|_ checkpoint ⇢ HTTP GET "/testFind/list" [ExceptionHandlingWebHandler]
Stack trace:
		at org.springframework.data.r2dbc.connectionfactory.ConnectionFactoryUtils.lambda$getConnection$0(ConnectionFactoryUtils.java:70) ~[spring-data-r2dbc-1.1.4.RELEASE.jar:1.1.4.RELEASE]
		at reactor.core.publisher.Mono.lambda$onErrorMap$30(Mono.java:3286) ~[reactor-core-3.3.10.RELEASE.jar:3.3.10.RELEASE]
		at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnErrorResume.java:88) ~[reactor-core-3.3.10.RELEASE.jar:3.3.10.RELEASE]
		at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnErrorResume.java:100) ~[reactor-core-3.3.10.RELEASE.jar:3.3.10.RELEASE]
		at reactor.core.publisher.MonoFlatMap$FlatMapMain.onError(MonoFlatMap.java:165) ~[reactor-core-3.3.10.RELEASE.jar:3.3.10.RELEASE]
		at reactor.core.publisher.MonoFlatMap$FlatMapMain.onError(MonoFlatMap.java:165) ~[reactor-core-3.3.10.RELEASE.jar:3.3.10.RELEASE]
		at reactor.core.publisher.FluxMap$MapSubscriber.onError(FluxMap.java:126) ~[reactor-core-3.3.10.RELEASE.jar:3.3.10.RELEASE]

Table schema

Not necessarily.

Input Code
-- your SQL here;

Steps to reproduce
Just modify the database user's password and make it end up with '@'. Then run a single demo using springbooot to connect mysql with r2dbc.

Input Code
Not necessarily.

Expected behavior/code

org.springframework.dao.DataAccessResourceFailureException: Failed to obtain R2DBC Connection; nested exception is java.net.UnknownHostException: @localhost:3306: nodename nor servname provided, or not known
Possible Solution
Changing the method in line 124 of file ConnectionUrlParser.java to lastIndexOf('@') would be a good solution.

Additional context

Feel free to submit a pull request that uses lastIndexOf(…).

Note: As per RFC 3986, we require percent-encoding of reserved characters (RFC3986 Section 2.2). However, we can be a bit more lenient.

ok i will submit a pr later


docs(website): add Integration Guide

Add "Integrating with Editors" page to website.

The fail of CI is related with Getting things sorted in V8 · V8.
We will fix next PR.

=> #558


Something I made for a semi-common use case

I realize that this exact implementation is a monstrous mashup of two backends AND SHOULDN'T BE PULLED IN ITS EXACT CURRENT STATE(Schema version and a couple things I just ignored), however, I am sure you could use it as a base to make something of a similar functionality as the use case of synced user groups/ user perms  while server specific group perms is not all that uncommon.   If not,  just close this, no skin off my back.

This is interesting. I'll probably have something more abstract make its way into PEX for Sponge (PEX for bukkit is currently in a maintenance-only development state)


[demo] - enable complex service definitions

Fixes #609
Moves serviceType and servicePort parameters to be members of a service parameter as children called type and port. It also adds support for annotations and nodePort under the same parent parameter.
This will be a breaking change for people who overrode either of the component service parameters before.

I did a search on the entire code base for serviceType and servicePort to make sure we aren't referencing the old values anymore and that they are adopted for the new structure.


Lwm2m timeseries update

Read by server update
Normal Read by server only report back latest stored data.
Notification and Send operation update
Added support for handle case when all data is not possible to add in 1 message for Send and Observed Notification. Engine rebuild message by limiting time series cache data length.
Notification continuous pending time series data is triggered by iMIN attribute. Send Operation generate continuous message in multiple lwm2m message.

@SeppoTakalo I dropped first commit away.

Rebased with upstream

@SeppoTakalo I fixed Ring buffer secure. Send operation was not secured correctly.


OpenSSL <IP_ADDRESS>-b1 : entry point "EVP_PKEY_id" is missing in DLL "libcrypto-3.dll"

I have been able to build openSSL
3.0.0-a16
3.0.0-a17

and to link/run cURL.
e.g.
curl 7.77.0 (i386-pc-win32) libcurl/7.77.0 OpenSSL/3.0.0 zlib/1.2.11 WinIDN libssh2/1.9.0
Release-Date: 2021-05-26
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile NTLM SPNEGO SSL SSPI UnixSockets alt-svc libz

With
3.0.0-b1
cURL claims
entry point "EVP_PKEY_id" is missing in DLL "libcrypto-3.dll"

What am I missing ?!
thx for your work
thx for your time

The name was changed to EVP_PKEY_get_id() late in the piece.
There is a #define EVP_PKEY_id EVP_PKEY_get_id in evp.h which seems to have been missed.
Did you do a clean build after updating?

I forgot to mention: OpenSSL was built with
--api=1.1.1 ... for the moment w!thout >no-deprecated<

I use to build new versions in a dedicated, fresh & untouched environment:
e.g .../3.0.0-b1/MSVC-32

Further I use to build with sequence
configure
nmake clean
nmake

In
...\OpenSSL\3.0.0-b1\MSVC-32\include\openssl\evp.h
there is actually a line
# define EVP_PKEY_id EVP_PKEY_get_id

For
..\OpenSSL\3.0.0-b1\MSVC-32\libcrypto-3.dll

Dependency Walker only reveals
EVP_PKEY_get_id

while
...\OpenSSL\3.0.0-a17\MSVC-32\libcrypto-3.dll

only shows
EVP_PKEY_id

thx for your attention

Do not use --api=1.1.1 there is no point in doing that. Did you rebuild the curl against the beta1. It has to be rebuilt against the beta if you built it against an alpha release before. Otherwise it will not work.


NotImplementedError: forward_dummy is not implemented in SOLOv2

NotImplementedError: forward_dummy is not implemented in SOLOv2
NotImplementedError: forward_dummy is not implemented in SOLOv2
Is solov2's parameter volume calculation not implemented yet? Any current ideas on this?
Any other context?
No response

@comingsoon1204 I recommend that you use the mmdet 3.x branch


MB-61719: Windows requires index variable in an OpenMP for to be signed

See: https://learn.microsoft.com/en-us/cpp/error-messages/compiler-errors-2/compiler-error-c3016?view=msvc-170

It seems we can get around this issue by using clang instead of msvc.

We won't be needing this anymore, as we're pivoting to using clang to compile windows builds - which fixes the compilation error called out.


Wink Fan not able to control without work around automation

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
Python release (python3 --version):
Component/platform:
Wink
Description of problem:
Wink Fan doesnt work after adding to config
Expected:
Traceback (if applicable):

Additional info:

@dale3h was able to write a automation that got it to work but fan did not work on default configuration
as you can see here https://github.com/Vasiley/Home-AssistantConfig/blob/master/packages/wink_fan.yaml and after the work around fan stops sending status updates

my fault

Fixed with this https://github.com/python-wink/python-wink/pull/87


⚠ SkipTheCommericals has degraded performance

In d8297ba, SkipTheCommericals ($STC) experienced degraded performance:

HTTP code: 200
Response time: 4707 ms

Resolved: SkipTheCommericals performance has improved in 920b5d3.


Spec requirements on certificate secrets

There are a number of interoperability questions about the use of secrets to store TLS keys and certificates. It may be helpful to have consolidated language to address these.

If it is a TypedLocalReference, what kinds must an implementation support?
Is the secret type required (e.g. v1.SecretTypeTLS)

If so, spec required types for server and client certificates, keys and CA bundles

Can secret data have multiple keys?
Are any specific secret data keys required?
What secret data formats must be supported? Only PEM?
Are multiple items allowed in a single secret data value (i.e multiple PEM blocks)
How items can be combined (e.g. is it OK to have key, cert and CA bundle all in one secret)

There may be existing certificate specs that we can incorporate by reference; we could also choose to punt this issue to implementations.

For sure supported:

Kubernetes Secrets, as used today by Ingress V1; let's take what is the current requirements from that and pull it here. This is easy for users to interoperate with and we have a solid basis to go from.

It's a typed ref for extension to other systems. The easiest thing to do here is to make anything else Support: custom and put this into the backlog.

/assign @youngnick

/reopen
/remove-lifecycle rotten

I believe this is all documented in Go doc comments. Is it safe to close this?

I believe so as well, feel free to reopen if not.


Tensor & PyTorch support

Related Issue: #73
Overview
This PR is to provide initial functionality to allow a successful upload of models built in the PyTorch or TensorFlow flavor.
Example CLI arguments:

garden-ai model register Steves-testTF-model ../garden-flavor-test/savedtf/ tensorflow
garden-ai model register Steves-testPT-model ../garden-flavor-test/pytorchtest1.pt pytorch

Discussion
The methods employed include the usage of the base library (pytorch or tensorflow) to enable loading of the serialized object subsequent to using the matching flavor of ML Flow to then log the model to the garden MLFLow URI.
This PR also has the following changes:

added .vscode/settings.json to .gitignore
garden_ai/app/model.py

added exists check for model_path typer arguments
added dir_okay for model_path typer arguments (needed for tensorflow)
updated help text for model path and extra_pip_requirements
updated the rich text to raise a typer.BadParameter to allow the CLI to exit rather than sit and require manual abort that existed with the rich text alone
added flavor as a parameter

garden_ai/client.py

added flavor parameter to log_model method

garden_ai/mlmodel.py

imported torch and tensorflow needed for loading serialized versions.
added code to ignore a cpu vs gpu informational warning from tensorflow; hence the flake ignore of E402 for the import of tensorflow after a line of code
added the flavor parameter to ModelUploadException class
updated docstring
created conditional upload based on model flavor, could look into switch case potentially in the future.

also checks that the model is in the proper file/dir required for the flavor

updated the model_full_name in the Model method to align with the other references in the code to model name so that all match to full_model_name.

test/integrations/test_mlflow.py

created a fixture for pytorch toy model
created a test that follows the sklearn scaffolding for pytorch but seems to have an issue with downloading the model (to be investigated as noted below in the testing section)
if this testing issue for pytorch is rectified, then it should be easy to continue to add testing support for further flavors, but I most likely need assistance to confirm this PR is properly uploading and that there are no further errors introduced in the changes listed above.

Testing
To test simply apply the same structure above (the CLI args) and have a model saved according to one of the flavors tensorflow via model.save(model_path) (which requires a directory, unless an HDF5 file) or pytorch via torch.save(model_path).
At this time I have reverted the parametrized unit tests which created toy models for the tensorflow and pytorch models; however due to the added complexity and many variables that could go into said models when compared to a serialized toy sklearn model parameterized tests might not be the way to go here. I feel this warrants further discussion on how to best test the full functionality and if models require additional parameters such as signatures and other items identified in the mlflow.flavor.log_model() documentations.
pytorch - log_model() docs & tensorflow - log_model() docs
For now, I have a test for the pytorch model that should work as a template, however there seemed to be issues I could not debug
Exact error: RuntimeError: PytorchStreamReader failed reading zip archive: invalid header or archive is corrupted
(the pytorch model was failing at unzipping, this could be an issue with me attempting to download the Model [via Model(full_model_name)] and should be investigated further - perhaps a new issue created if this failure continues with other models/systems/users to rule out my exact circumstances) Steps to reproduce are to run the pytests for test_mlflow.py sklearn should pass and pytorch should fail.

:books: Documentation preview :books:: https://garden-ai--100.org.readthedocs.build/en/100/

This is fantastic. Thank you for the well-researched and tested contribution. I also appreciate the open questions and next steps in the PR description. Even with some of the snags you've described I'd like to err on the side of getting this merged in quickly to avoid drift and merge conflicts.
Right now I think the only "issue" is the torch and keras imports at module scope in some of the files. (Like this). For now we can just make torch and keras dependencies in pyproject.toml. But before declaring victory on V0 we'll probably want to go back and make them optional and only import them when a user is dealing with that specific library.
(It so happens that scikit-learn is a requirement of the MLFlow client so we've gotten away with assuming that all users have that installed. Hence the top-level sklearn imports. So we didn't have any pattern established for this and I didn't think to mention it when we were scoping the ticket, my bad.)
I know you're traveling for a while so I'll probably try and do the extra fiddly work to get this PR in this week. Thank you @steve-barnard!

I made some little test and import tweaks on #101 and pulled this in. Thanks again Steve!
Yeah, for now just going with conditional imports based on the flavor argument. I think we'll probably want to add them as optional requirements in pyproject.toml for easy dev setup and to be able to run tests in CI that use them. But for now I just pulled in what you had.


Avoid creating intermediate arrays when possible, it hurt performance

Current implementation creates an array from string, filters it (another array) and then joins. My proposal is to avoid creating the array entirely.
Sure, this looks not so Ruby idiomatic, but I think it's OK for general usage library to lean towards performance, since even slightest improvements boost performance of all applications that depend on it.
Interestingly though, that replacing Regexp literal with a constant actually make performance worse (my bad, incorrect benchmark) doesn't change performance, therefore I left this part untouched.

having a benchmark folder with old code is a bit strange, but might inspire future benchmarks ... so kind of like that :)

v1.1.0

Thanks for reviewing this!

having a benchmark folder with old code is a bit strange

I'm also not so sure about that. At least this comparison (as a snapshot) will be valid even with future changes in the library.

better to use frozen string comments then to make sure it actually works :)
On Wed, Nov 23, 2016 at 10:53 AM, Andrii Malyshko<EMAIL_ADDRESS>wrote:

@nashbridges commented on this pull request.
In lib/sort_alphabetical.rb
https://github.com/grosser/sort_alphabetical/pull/18:

@@ -19,8 +19,12 @@ def sort(set)
end

def normalize(string)

UnicodeUtils.compatibility_decomposition(string).split(''.freeze).select do |c|

 UnicodeUtils.general_category(c) =~ /Letter|Separator|Punctuation|Number/

end.join

result = String.new

String literals will be immutable since Ruby 3, therefore it is on purpose
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/grosser/sort_alphabetical/pull/18, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAsZ5FS9x2BvXg3hkTxXaLqRyi1fM2Tks5rBIu-gaJpZM4K6YEC
.

better to use frozen string comments

Good point. https://github.com/grosser/sort_alphabetical/pull/19


"roots" config added in 3.1.0 breaks Jest default behavior of automatically mocking Node modules

Describe the bug
The change introduced in PR #7480, adding roots: ['<rootDir>/src'] to the Jest config, changes Jests default behavior of mocking Node modules, which is a breaking change if you were using the default setup before the roots config was added.
The Jest documentation says:

If the module you are mocking is a Node module (e.g.: lodash), the mock should be placed in the __mocks__ directory adjacent to node_modules (unless you configured roots to point to a folder other than the project root) and will be automatically mocked.

So after updating react-scripts my auto-mocking broke because I keep the mocks in <project root dir>/__mocks__, just as the Jest docs said I should.
This new requirement to use <rootDir>/src/__mocks__ for Node modules is also not documented in the Create React App filename conventions docs, it only mentions that the test files need to be in src, and it doesn't mention that roots has been configured, so together with what the Jest docs says it's confusing.
And the change was also not mentioned in the 3.1.0 release notes. It ought to have been in the breaking changes section since it limits where Jest is looking for tests. Even though the docs already said that the tests should be in src someone might have placed tests outside of it, and Node mocks is documented by Jest that they should be placed outside of src.
And Create React App doesn't allow us to override the roots config so I can't add a new root so the only way to fix this as it is is to move __mocks__ into src/__mocks__, which I don't want to do.
I suggest two changes to improve upon this, whilst still keeping the performance improvements:

Update the default Create React App config for Jest to roots: ['<rootDir>/src', '<rootDir>/__mocks__']
Allow the roots option to be overridden

I can submit a PR for these changes if you agree that they're the way to go.
Did you try recovering your dependencies?
Yes.
$ npm --version
6.9.0

Which terms did you search for in User Guide?

node_modules
mocks

Environment
$ npx create-react-app --info
npx: installed 91 in 4.867s

Environment Info:

  System:
    OS: macOS 10.14.5
    CPU: (8) x64 Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
  Binaries:
    Node: 10.16.0 - ~/.nvm/versions/node/v10.16.0/bin/node
    Yarn: Not Found
    npm: 6.9.0 - ~/.nvm/versions/node/v10.16.0/bin/npm
  Browsers:
    Chrome: 76.0.3809.132
    Firefox: 69.0
    Safari: 12.1.1
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-dom: 16.9.0 => 16.9.0
    react-scripts: 3.1.1 => 3.1.1
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce

Create a mock for a Node module in <project root dir>/__mocks__, as explained in the Jest documentation for mocking Node modules
Use the mock in a test

Expected behavior
The Node module should be mocked.
Actual behavior
The Node module is not mocked.
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Thanks for the report. It is indeed an issue, but it's a dupe of #7539. If anyone has some time it would be awesome if somebody could take that on 😃. There is a potential fix in there that may work.


Ai-Chat bot

an AI-CHAT BOT should be added so that the user can have a conversation with the ai and can explain exactly what he wants...
using python code an AI-Chat bot code can be done in a clean way.
This can get more responsive by adding ai chatbot

It's already an AI bot with autonomous agents allowing users to chat with documents and only with the LLM also. To trigger that behaviour you can use --mode llm as the parameter when running it.

It's already an AI bot with autonomous agents allowing users to chat with documents and only with the LLM also. To trigger that behaviour you can use --mode llm as the parameter when running it.

I'LL LIKE TO WORK ON THIS ISSUE, PLEASE ASSIGN IT


Upgrade dependencies

For whatever reason I'm getting:
go.mod:6:2: require github.com/avast/retry-go: version "v4.5.1" invalid: should be v0 or v1, not v4

(Which makes little sense, since it was already at v3 something.)
I need to dig deeper before accepting this change. But open to ideas.

Ow. Nevermind. Git conflicts I missed. All good : ) Thank you!

Ow… now the CI for linting is failing. And I can reproduce it locally.
Feel free to add a commit, since I'm not able to investigate it these days.

I upgraded the staticcheck version, too. I don't have any issues locally with staticcheck 2023.1.6


[Issue] Invariant Violation: View config getter callback for component div must be a function (received undefined).

Current Behavior
An attempt to use Tamagui in existing React Native project results in following error being thrown:
Invariant Violation: View config getter callback for component `div` must be a function (received `undefined`). Make sure to start component names with a capital letter.

This error is located at:
    in div
    in Unknown (created by App)
    in PortalProviderComponent
    in _Theme (created by _ThemeProvider)
    in _ThemeProvider (created by _TamaguiProvider)
    in _TamaguiProvider
    in Unknown (created by App)
    in App
    in RCTView (created by View)
    in View (created by AppContainer)
    in RCTView (created by View)
    in View (created by AppContainer)
    in AppContainer
    in app(RootComponent), js engine: hermes

Expected Behavior
It would be nice to use at least core Tamagui components.
Tamagui Version
1.28.1

Reproduction
Add Tamagui to the project by following installation steps:
https://tamagui.dev/docs/intro/installation#native
with one exception: skip Expo installation step, as according to this comment it should no longer be mandatory.
https://github.com/tamagui/tamagui/discussions/1125#discussioncomment-5923702
Config file:
import { config } from '@tamagui/config';
import { createTamagui } from 'tamagui'; // or '@tamagui/core'

const appConfig = createTamagui(config);

export type AppConfig = typeof appConfig;

declare module '@tamagui/core' {
    // overrides TamaguiCustomConfig so your custom types
    // work everywhere you import `tamagui`
    interface TamaguiCustomConfig extends AppConfig {}
}

export default appConfig;

App.tsx:
import React from 'react';
import { TamaguiProvider, YStack } from 'tamagui';

import config from './app/common/theme/tamagui.config';

type Props = {};

export const App = (props: Props) => {
    return (
        <TamaguiProvider config={config}>
            <YStack></YStack>
        </TamaguiProvider>
    );
};

System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (8) x64 Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
    Memory: 2.62 GB / 15.92 GB
  Binaries:
    Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.42)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @babel/core: ^7.20.0 => 7.21.0
    @babel/preset-typescript: ^7.15.0 => 7.21.0
    @babel/runtime: ^7.20.0 => 7.21.0
    @react-native-async-storage/async-storage: 1.17.11 => 1.17.11
    @react-native-clipboard/clipboard: 1.11.2 => 1.11.2
    @react-native-community/blur: 4.3.0 => 4.3.0
    @react-native-community/checkbox: 0.5.14 => 0.5.14
    @react-native-community/eslint-config: ^3.2.0 => 3.2.0
    @react-native-community/hooks: 3.0.0 => 3.0.0
    @react-native-community/image-editor: 2.3.0 => 2.3.0
    @react-native-community/netinfo: 9.3.7 => 9.3.7
    @react-native-firebase/analytics: 17.3.2 => 17.3.2
    @react-native-firebase/app: 17.3.2 => 17.3.2
    @react-native-firebase/crashlytics: 17.3.2 => 17.3.2
    @react-native-firebase/in-app-messaging: 17.3.2 => 17.3.2
    @react-native-firebase/messaging: 17.3.2 => 17.3.2
    @react-native-firebase/remote-config: 17.3.2 => 17.3.2
    @svgr/cli: 6.2.1 => 6.2.1
    @tamagui/babel-plugin: 1.28.1 => 1.28.1
    @tamagui/config: 1.28.1 => 1.28.1
    @tanstack/react-query: 4.26.0 => 4.26.0
    @trpc/client: 10.14.0 => 10.14.0
    @trpc/react-query: 10.14.0 => 10.14.0
    @trpc/server: 10.14.0 => 10.14.0
    @types/jest: ^29.2.1 => 29.4.0
    @types/react: ^18.0.24 => 18.0.28
    @types/react-native: ^0.66.16 => 0.66.27
    @types/react-test-renderer: ^18.0.0 => 18.0.0
    axios: 0.21.1 => 0.21.1
    babel-jest: ^29.2.1 => 29.5.0
    babel-plugin-transform-inline-environment-variables: 0.4.4 => 0.4.4
    eslint: 8.19.0 => 8.19.0
    googleapis: 118.0.0 => 118.0.0
    husky: ^7.0.0 => 7.0.4
    jest: ^29.2.1 => 29.5.0
    lodash: 4.17.21 => 4.17.21
    metro-react-native-babel-preset: 0.73.9 => 0.73.9
    native-base: 3.4.6 => 3.4.6
    prettier: ^2.4.1 => 2.8.4
    pretty-quick: ^3.1.1 => 3.1.3
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    react-native: 0.71.5 => 0.71.5
    react-native-animatable: ^1.3.3 => 1.3.3
    react-native-awesome-gallery: 0.3.4 => 0.3.4
    react-native-camera: react-native-camera/react-native-camera#3443/head => 4.2.1
    react-native-clean-project: ^3.6.7 => 3.6.7
    react-native-code-push: 7.1.0 => 7.1.0
    react-native-device-info: 7.3.1 => 7.3.1
    react-native-drag-sort: 2.4.4 => 2.4.4
    react-native-exception-handler: 2.10.10 => 2.10.10
    react-native-gesture-handler: 2.9.0 => 2.9.0
    react-native-iap: ^7.4.1 => 7.5.6
    react-native-image-picker: 5.1.0 => 5.1.0
    react-native-localize: 2.2.5 => 2.2.5
    react-native-rate: 1.2.12 => 1.2.12
    react-native-reanimated: 3.1.0 => 3.1.0
    react-native-safe-area-context: 4.5.0 => 4.5.0
    react-native-sensitive-info: ^5.5.8 => 5.5.8
    react-native-snowflakes: ^1.0.3 => 1.0.3
    react-native-svg: ^12.1.0 => 12.5.1
    react-native-svg-transformer: ^0.14.3 => 0.14.3
    react-native-ux-cam: 5.3.4 => 5.3.4
    react-native-video: 5.2.1 => 5.2.1
    react-redux: 8.0.5 => 8.0.5
    react-test-renderer: 18.2.0 => 18.2.0
    redux: 4.2.1 => 4.2.1
    redux-logger: 3.0.6 => 3.0.6
    redux-thunk: 2.4.2 => 2.4.2
    svgo: 3.0.2 => 3.0.2
    tailwind-rn: ^3.0.1 => 3.0.1
    tamagui: 1.28.1 => 1.28.1
    typescript: ^4.8.4 => 4.9.5
    zustand: 4.0.0-rc.1 => 4.0.0-rc.1

I did a bit of the debugging and for some reason isReactNative ends up set as false here:
https://github.com/tamagui/tamagui/blob/master/packages/web/src/styled.tsx#L87

Thanks @natew. That was my guess to but when I console log process.env.TAMAGUI_TARGET around the line linked in my previous comment it logs native.
And that's the babel.config.js:
// just to ensure TAMAGUI_TARGET is set
process.env.TAMAGUI_TARGET = 'native';

module.exports = {
    presets: ['module:metro-react-native-babel-preset'],
    plugins: [
        [
            'transform-inline-environment-variables',
            {
                include: ['TAMAGUI_TARGET'],
            },
        ],
    ],
};

Thank you for opening this issue. I am trying to use tamagui library for 2 days. I am using it in react native / Expo and after installing it and related dependencies. and wrapping the whole app with its provider I am getting errors when I am using any of the Tamagui assets. I moved my react, and react-dom to version 18, and integrated typescript with the help of Expo doc but it didn't fix my problem.
I have doubts what is causing this failure. Please check my node modules.
Package.json.
"@bugsnag/react-native": "^7.10.3",     "@expo/webpack-config": "^18.0.4",     "@js-joda/core": "^5.2.0",     "@react-native-async-storage/async-storage": "~1.17.3",     "@react-native-community/cli-platform-android": "^6.3.0",     "@react-native-community/datetimepicker": "6.1.2",     "@react-native-community/hooks": "2.4.3",     "@react-native-community/push-notification-ios": "^1.0.6",     "@react-navigation/bottom-tabs": "^6.0.5",     "@react-navigation/native": "^6.0.2",     "@react-navigation/stack": "^6.0.7",     "@tamagui/animations-react-native": "^1.28.1",     "@tamagui/babel-plugin": "^1.28.1",     "@tamagui/config": "^1.28.1",     "@tamagui/font-inter": "^1.28.1",     "@tamagui/theme-base": "^1.28.1",     "@testing-library/react-hooks": "^7.0.2",     "@testing-library/react-native": "^7.2.0",     "@types/react": "^18.2.6",     "cuid": "^2.1.6",     "deep-diff": "^1.0.2",     "deep-object-merge": "^1.0.0",     "deepmerge": "^4.2.2",     "expo": "~45.0.0",     "expo-background-fetch": "~10.2.0",     "expo-build-properties": "^0.3.0",     "expo-device": "~4.2.0",     "expo-font": "^11.1.1",     "expo-image-loader": "~3.2.0",     "expo-linking": "~3.1.0",     "expo-localization": "~13.0.0",     "expo-modules-core": "~0.9.2",     "expo-notifications": "~0.15.2",     "expo-splash-screen": "~0.16.1",     "expo-status-bar": "~1.3.0",     "expo-store-review": "~5.2.0",     "expo-task-manager": "~10.2.1",     "fast-deep-equal": "^2.0.1",     "global": "^4.4.0",     "i18n-js": "^3.8.0",     "just-is-empty": "^2.0.1",     "poly-filter": "^1.0.2",     "poly-find": "^1.0.1",     "poly-map": "2.2.4",     "postinstall-postinstall": "^2.0.0",     "re-reselect": "^3.4.0",     "react": "18.0.0-alpha-5ca4b0433-20211020",     "react-dom": "18.0.0-alpha-5ca4b0433-20211020",     "react-native": "0.68.2",     "react-native-animatable": "^1.3.3",     "react-native-blink-view": "^0.0.6",     "react-native-calendars": "^1.264.0",     "react-native-chooser": "^1.7.0",     "react-native-datepicker": "rikur/react-native-datepicker#upgrade",     "react-native-flipper": "^0.127.0",     "react-native-fs": "2.16.6",     "react-native-gesture-handler": "~2.2.1",     "react-native-highlight-words": "^1.0.1",     "react-native-html-to-pdf": "^0.11.0",     "react-native-iphone-x-helper": "^1.2.1",     "react-native-localize": "^2.1.1",     "react-native-modal": "^13.0.0",     "react-native-modest-checkbox": "^3.3.0",     "react-native-pixel-perfect": "^1.0.2",     "react-native-privacy-snapshot": "darling-apps/react-native-privacy-snapshot",     "react-native-purchases": "^4.2.0",     "react-native-reanimated": "~2.8.0",     "react-native-safe-area-context": "4.2.4",     "react-native-safe-area-view": "^1.0.0",     "react-native-screens": "~3.11.1",     "react-native-share": "^7.3.3",     "react-native-size-matters": "0.3.0",     "react-native-swipe-gestures": "^1.0.4",     "react-native-text-input": "raccoon-technology/react-native-text-input",     "react-native-theme-picker": "^1.0.0",     "react-native-view-shot": "3.1.2",     "react-native-web": "^0.19.4",     "react-redux": "^7.2.0",     "redux": "^4.0.5",     "redux-devtools-extension": "^2.13.8",     "redux-persist": "^5.10.0",     "redux-persist-seamless-immutable": "^2.0.0",     "redux-saga": "^1.1.1",     "redux-saga-rn-alert": "^1.2.7",     "redux-seamless-immutable": "^0.4.0",     "reselect": "^4.0.0",     "seamless-immutable": "^7.1.4",     "tamagui": "^1.28.1",     "thenby": "^1.3.0"
tamagui.config.ts.

`import { createAnimations } from '@tamagui/animations-react-native'

import { createInterFont } from '@tamagui/font-inter'
import { createMedia } from '@tamagui/react-native-media-driver'
import { shorthands } from '@tamagui/shorthands'
import { themes, tokens } from '@tamagui/themes'
import { createTamagui } from 'tamagui'
import * as ReactNative from 'react-native'
import {setupReactNative} from '@tamagui/core'
const animations = createAnimations({
bouncy: {
type: 'spring',
damping: 10,
mass: 0.9,
stiffness: 100,
},
lazy: {
type: 'spring',
damping: 20,
stiffness: 60,
},
quick: {
type: 'spring',
damping: 20,
mass: 1.2,
stiffness: 250,
},
})
const headingFont = createInterFont()
const bodyFont = createInterFont()
setupReactNative(ReactNative)
const config = createTamagui({
animations,
defaultTheme: 'dark',
shouldAddPrefersColorThemes: false,
themeClassNameOnRoot: false,
shorthands,
fonts: {
heading: headingFont,
body: bodyFont,
},
themes,
tokens,
media: createMedia({
xs: { maxWidth: 660 },
sm: { maxWidth: 800 },
md: { maxWidth: 1020 },
lg: { maxWidth: 1280 },
xl: { maxWidth: 1420 },
xxl: { maxWidth: 1600 },
gtXs: { minWidth: 660 + 1 },
gtSm: { minWidth: 800 + 1 },
gtMd: { minWidth: 1020 + 1 },
gtLg: { minWidth: 1280 + 1 },
short: { maxHeight: 820 },
tall: { minHeight: 820 },
hoverNone: { hover: 'none' },
pointerCoarse: { pointer: 'coarse' },
}),
})
export type AppConfig = typeof config
declare module 'tamagui' {
// overrides TamaguiCustomConfig so your custom types
// work everywhere you import tamagui
interface TamaguiCustomConfig extends AppConfig {}
}
export default config`
bable.config.js
`// Don't forget to specify your TAMAGUI_TARGET here or ideally in the command to run / .env files
process.env.TAMAGUI_TARGET = 'native'
module.exports = function(api) {
api.cache(true)
return {
presets: ['module:metro-react-native-babel-preset'],
sourceMaps: 'inline',
retainLines: true,
// presets: ["babel-preset-expo"],
plugins: [
[
'module-resolver',
{
root: ['.'],
extensions: ['.ios.js', '.android.js', '.js', '.json'],
},
],
// NOTE: this is required to pass the right environment
[
'transform-inline-environment-variables',
{
include: 'native',
},
],
// NOTE: this is optional, you don't need the compiler
[
'@tamagui/babel-plugin',
{
components: ['tamagui'],
config: './tamagui.config.ts',
logTimings: true,
},
],
// NOTE: this is only necessary if you are using reanimated for animations
'react-native-reanimated/plugin',
],
}
}`

looks like outdated react actually, thats trying to call useSyncExternalStore and its undefined. double check your lockfile and maybe use resolutions in yarn if youre using it to ensure only one version of react 18 installed.

@natew I am using react version "18.0.0-alpha-5ca4b0433-20211020", which is the version that is not giving undefined errors inside react node module. Please check the attached screenshot which is giving an error inside react in the latest version 18

.2

i need repros in order to not get totally bogged down on issues, if you create one you can re-open and i'll investigate

I'm having a related issue that shows TAMAGUI_TARGET error as the first error.
If I used any Stack component with no child component in it, I got the same invariant violation error as @404-html, then when I added a Text component inside of it, the error changed to Text strings must be rendered within a  component
I also printed TAMAGUI_TARGET at my index file, and the value is native
I really have no idea

Same problem. Really frustrating.

In Expo 49, the usage transform-inline-environment-variables would seems conflicting with the expo support for .env. All of my environment loaded from .env file would be undefined.
If i remove the plugin, tamagui would not work. The only way to make everything work is to manually include all of my env into the plugin's include list.
[
        "transform-inline-environment-variables",
        {
          include: [
            "TAMAGUI_TARGET",
            "EXPO_ROUTER_APP_ROOT",
            "EXPO_ROUTER_PROJECT_ROOT",
            "EXPO_ROUTER_IMPORT_MODE",
            "EXPO_ROUTER_IMPORT_MODE_ANDROID",
            "EXPO_ROUTER_IMPORT_MODE_IOS",
            "EXPO_ROUTER_IMPORT_MODE_WEB",
            "EXPO_PUBLIC_BASE_URL_DEV",
            "EXPO_PUBLIC_APP_KEY_DEV",
            "EXPO_PUBLIC_APP_SECRET_DEV",
          ]
        }
]

Is there anyway you can support both TAMAGUI_TARGET and EXPO_PUBLIC_TAMAGUI_TARGET?

@idrakimuhamad did you get a working solution for Expo 49?

@idrakimuhamad's solution, plus running expo metro with --clear solved the problem for me.

@idrakimuhamad's solution, plus running expo metro with --clear solved the problem for me.

In my recent attempt, what I did is to remove TAMAGUI_TARGET from babel json, add it into .env, but leave the transform inline environment variable without anything else.


Show list of diagrams for constructs in the current file

Purpose
Show list of diagrams for constructs in the current file.
This list is shown when no construct is selected.
Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #18403 into master will increase coverage by 4.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #18403      +/-   ##
==========================================
+ Coverage   14.82%   19.56%   +4.74%
==========================================
  Files          48       53       +5
  Lines        1268     1390     +122
  Branches      201      222      +21
==========================================
+ Hits          188      272      +84
- Misses       1066     1104      +38
  Partials       14       14

Impacted Files
Coverage Δ

composer/packages/tracing/src/ToolBar.tsx
71.05% <0%> (ø)

composer/packages/tracing/src/TraceList.tsx
94.44% <0%> (ø)

composer/packages/tracing/src/DetailView.tsx
79.31% <0%> (ø)

composer/packages/tracing/src/TraceLogs.tsx
70.83% <0%> (ø)

composer/packages/tracing/src/index.ts
0% <0%> (ø)

Continue to review full report at Codecov.

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


Namespaces don't work with pipes

I can't seem to get namespaced functions to work with pipes. This seems like a parser issue, probably an easy fix.

Noted. It is a parser fix...


mutli thread to download a file and get error "Unexpected status line"

How can I solve this problem now? It's still the only way?
Most likely the preceding response was malformed. You should tell the web server’s administrator to fix this.
Work-around by disabling connection pooling on requests to this host. The easiest way is with this request header:
Connection: close

Originally posted by @swankjesse in https://github.com/square/okhttp/issues/3662#issuecomment-338446870

There is a good suggestion by @15characterlimi that it could be related to unsafe use from multiple threads.  You shouldn't consume from a single Response across threads.
But otherwise, this alone isn't reproducible, please post a question to stackoverflow with sample code.
If you can make a clean reproduction, then reopen this issue.  But as is, we can't do much here.  Sorry.


remove callout and add tabs as examples

addressing @joellabes' request to remove old callouts for alias, database, and schema pages. also added example tabs at the beginning to help provide users with more example at the beginning of the doc

hey @joellabes thank you so much for this! I've made changes to it and added items you suggested. i did ask about tests in custom database to confirm, but i also added an example just in case. also i have a question below for you if you can clarify because i see some do and some don't based on the issues you linked above. thank you!

can you also use config block for all 4 resource types?

can you also use config block for all 4 resource types?

Yes:
models:
  - name: first_model
    config:
      alias: second_model
    columns:
      - name: id
        tests:
          - unique:
              config:
                alias: custom_test_name_when_storing_failures

snapshots:
  - name: first_snapshot
    config:
      alias: second_snapshot


Data serialization

Nodes will exchange a lot of operational and metadata over network. We should try to minimize the traffic and reduce the serialization / deserialization footprint as much as possible. The focus of this issue is to design an (close to) optimal message representation, and decide on the serialization format.
In my opinion, some of the strong candidates are Protobuf, Avro, and Thrift, but there are many more available. We should keep an eye on scalaz-schema as it will eventually provide all necessary "tools".

you rang? We'd be happy to work with you all on that. We don't have the implementations for Protobuf, Avro, or Thrift as of now but that is really only a matter of time. Feel free to just @ me about that though

I know there is an open issue for Avro support. Since we spoke about working together on that one (a long time ago), this might be the opportunity to do so :).

@mijicd right now we are serialize our internal protocol messages manually using ByteBuffer from zio-nio. Since we want to keep dependency as small as possible do you thing we should still look into scalaz-schema or other serialization framework?

we decided to use http://www.lihaoyi.com/upickle/#µPickle0.8.0

done by #121


Reasons to use this client instead of WebFaction's newly announced first-party support

Now that WebFaction supports Let's Encrypt certs right in the control panel, is there a reason you have to still use this client? Please answer in comments below, and don't forget to file a support ticket with WebFaction too.

I can imagine that with their 1:1 mapping between website and cert, if you have a domain for which you continually issue new subdomains, you may hit LE API limits which, using this client, you could combine subdomains into a single certificate and reduce renewals.

They require the nameservers / IP to point at their server, so it looks like I'll be continuing to use this client for domains behind CloudFlare!

It would also seem that WebFaction haven't yet provided any LestEncrypt functionality in their API yet, so those who don't use the Control Panel will doubtless till find a use for this until the API is updated.
Another reason, of course, is "if it ain't broke, don't fix it" for those who get everything they need from this project.

Right now I am using this client.
I am right now trying to use the WebFaction control panel one.
It does not work.
It says the following on their site.

"Please note we can only provision a Let's Encrypt certificate for a domain name once it is resolving to your WebFaction machine.
Please disable any HTTP to HTTPS redirects for any .well-known/acme-challenge urls that you might have set up for this domain before enabling Let's Encrypt."

I guess it means we have to delete the the redirects that this client uses?

A reasonable assumption, but I believe it's incorrect. You can make the
redirection conditional.
WebFaction support suggested changing the .htaccess file in the redirect
app (mod_wsgi, PHP) to
RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-SSL} !on
RewriteCond %{REQUEST_URI} !^/(.well-known)(/|$)
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
Steve Holden
On Sat, Oct 20, 2018 at 5:14 PM, Hamun<EMAIL_ADDRESS>wrote:

Right now I am using this client.
I am right now trying to use the WebFaction control panel one.
It does not work.
It says the following on their site.
"Please note we can only provision a Let's Encrypt certificate for a
domain name once it is resolving to your WebFaction machine.
Please disable any HTTP to HTTPS redirects for any
.well-known/acme-challenge urls that you might have set up for this domain
before enabling Let's Encrypt."
I guess it means we have to delete the the redirects that this client uses?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/will-in-wi/letsencrypt-webfaction/issues/160#issuecomment-431595356,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGbYPSpxHVlGLRMBQ88M-r87WMUAn48ks5um0vwgaJpZM4XFEW7
.

Well we are using nginx and using flask python.
But we are already directing to https (but which now leads to errors 502, because both rerunning this client and using the control panel failed).

WebFaction also helpfully pointed out that you can by-pass the "duplicate requests" timeouts by adding redundant domains to the request, so it is seen as a different certificate request.

Ok I got it to work.
What I basically did was the following:

Remove any URI's with ./well-known from the domain.
Set the Encryption to be Let's encrypt
Restart the server (in my case it was through gunicorn).

When I try to use WebFaction's integrated service I get an unknown error message telling me to contact support. Support just says to:

Remove any HTTP to HTTPS redirects (I'm not aware of any)
Make sure you're not using CloudFlare (I don't believe so, and this site heps: http://www.doesitusecloudflare.com/ )
"Try binding a blank static only type app to the root of the domain to see if this solves the issue."

This did no better
I now get a new error about too many duplicate certificate requests per week, so I guess I'll try again next week.
In the meantime I'm going through the steps to renew the perfectly functional (albeit expired) certificate your wonderful tool helped me to set up.

I think that the biggest reason to continue using this tool is the fact that, for *.webfactional.com domains (i.e - non custom domains), WebFaction will force you to use their 'Shared Certificate'. This will show up as insecure for browsers accessing the webapp, since the Shared Certificate is issued for webfactional.com, not subdomain.account.webfactional.com as is the case for non-private domains.
If you don't have a private domain, want to serve over HTTPS and don't want your users to see 'Insecure' in the address bar, this tool seems to be the only option as far as I can see (and not a bad option at that).

Well... since that webfaction is going to godaddy soon(tm) then this might get obsolete.

I used this gem for about 10 site, but I have converted most of them to use the built Webfaction support.  But I did just run across one use case where I have to use this gem.
One site requires that I have more control over settings in the Apache instance, so I have my own instance installed, that of course gets proxied by Webfaction's frontend server.  Because of this, it has no idea how to do the challenge:
Challenges will not work for the following domains: my.example.org. You should ensure the domain exists, is pointed at your webfaction hosting, and nothing is blocking/redirecting requests for http://<eachdomain>/.well-known/acme-challenge/<filename>

@will-in-wi highly appreciate all the work that's gone into this gem!

I'm not sure what other shared hosting providers exist that are like WebFaction used to be.

It looks like some ex-employees are starting up something similar. I first spotted this on webfaction's own support forums :-) More details here: https://forum.kjodle.net/discussion/14/closest-thing-to-webfaction/discussion/comment/62/#Comment_62
Klynton J and Sean F are onboard.
Their site is here: https://opalstack.com/  I'd try it right away, if they had a WordPress one-click install (they say it's coming).
Anyone here tried it yet?

I'm considering OpalStack for some freelance hosted sites I maintain. I started switching my personal sites over to Linode.

They do have a Wordpress stack available now.  I haven't tried it though.  I haven't done much with my account, as I'm waiting for Rails support.
Does Linode have anything that is managed (and a reasonable price) like Webfaction?  I just don't want to have start to managing the OS stack again...

Currently the Webfaction LE control panel tool has been broken since Dec 23. https://statusblog.webfaction.com/2019/12/23/lets-encrypt-trouble/
Unfortunately I've got a number of ticking time bombs because I cannot even use letsencrypt_webfaction due to the acme v1 error.
Maybe its time to completely pull everything...ugh.

I’ve got some cruddy Python code that I used to do the same job before the
control panel worked. If I open source it would you like to engineer it
sensibly in the open?
I don’t have time to adapt it to anyone else’s needs myself just now.
Steve
On Wed, 8 Jan 2020 at 18:13, Nicscott01<EMAIL_ADDRESS>wrote:

Currently the Webfaction LE control panel tool has been broken since Dec
23. https://statusblog.webfaction.com/2019/12/23/lets-encrypt-trouble/
Unfortunately I've got a number of ticking time bombs because I cannot
even use letsencrypt_webfaction due to the acme v1 error.
Maybe its time to completely pull everything...ugh.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/will-in-wi/letsencrypt-webfaction/issues/160?email_source=notifications&email_token=AAAZWYFF22PCBPPXUJXX3YDQ4YJUZA5CNFSM4FYUIW52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEINPAOQ#issuecomment-572190778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAZWYC4UUWRZGTWYHWQG4TQ4YJUZANCNFSM4FYUIW5Q
.

--
Steve Holden

Thanks for the offer. Webfaction support actually just directed me to this: https://github.com/Neilpang/acme.sh
I was able to manually issue a cert over multiple domains/subdomains and copy and paste into the WF control panel. This will get me by for now.

Their control panel stopped issuing certs!? 🤦♂ I hadn't noticed that. I'm migrating my sites off, and plan on migrating any other sites that encounter this issue.
I'd probably suggest https://opalstack.com/ if you are looking for something similar to classic Webfaction. I haven't used them myself, but they are some of the WebFaction old guard.

I'm unsure about Webfaction's commitment to its Let's Encrypt ACME client. When I created a new Wordpress site yesterday, the Let's Encrypt button didn't come up as an option. Since I couldn't exactly remember the process I used to generate LE certificates for my other sites, I tried some weird workarounds that weren't successful. And I submitted a support ticket to Webfaction. They responded with "We've never had the option of generating a LetsEncrypt certificate."
Then, mysteriously, the Let's Encrypt certificate button appeared today and I was able to generate the certificate. Go figure.
I've been hanging on with Webfaction because my needs aren't critical and migrating seems like more hassle than it's worth. But that interaction gives me pause.
And as long as I stick with them, I hope to have letsencrypt-webfaction as a backup to Webfaction's ACME "support."

@bwareham In my experience, the option to use a LE certificate is not there when first creating the website. However, once the website is created, if you go back into it you will see that there is an option to select an LE certificate. Not sure why this is, but it just is.
The software created by @will-in-wi was incredibly useful a few years ago, but the support from Webfaction for LE is now pretty good and I no longer need this.

Yes, I have also abandoned my own scripts now Webfaction seem to have made
it Just Work™.
Kind regards,
Steve
On Wed, Aug 19, 2020 at 5:10 PM vegemite4me<EMAIL_ADDRESS>wrote:

@bwareham https://github.com/bwareham In my experience, the option to
use a LE certificate is not there when first creating the website. However,
once the website is created, if you go back into it you will see that there
is an option to select an LE certificate. Not sure why this is, but it just
is.
The software created by @will-in-wi https://github.com/will-in-wi was
incredibly useful a few years ago, but the support from Webfaction for LE
is now pretty good and I no longer need this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/will-in-wi/letsencrypt-webfaction/issues/160#issuecomment-676519801,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAZWYEYIY63AUQO6JKTYY3SBP2PBANCNFSM4FYUIW5Q
.

Hey folks, at this point I've migrated all of my websites over to Opalstack. I don't have any other way to test WebFaction, and they are shutting down completely. I'm closing down this project.
I want to thank each and every one of you for your usage and support of this tool. You have made this a pleasure to build and maintain. Those of you who asked good questions and pushed back on early usability issues, who improved documentation, and who contributed code, THANK YOU! I've always been impressed at how polite and respectful you all have been. I hope to encounter you in future projects! ❤


The rendering negatively affects the main window container drag operation.

QtDirect3D will drop to around 40 frames per seconds if you drag the main window container. The drag operation will also show visible lag input. This shouldn’t happen. Below are two comparison gifs, note that the conversion to MP4 does not reflect an accurate representation. In real time, the lag input is considerably more pronounced on the QtDirect3D gif whereas non-present on the expected behavior gif.
QtDirect3D:
https://user-images.githubusercontent.com/83611172/130328954-3a4b7a2b-1bc8-43e5-b64d-63f814ed5479.mp4
The expected behavior:
https://user-images.githubusercontent.com/83611172/130329096-3a5694ab-50d2-46a9-b3fa-96038ea7637b.mp4

Interesting. Did you change something that in the second video doesn't happen anymore?
When I tested this on my machine (GTX 1050 Ti), it was only dropping 5 frames at max, so it didn't drop below 55 FPS. I'm suspecting it could possibly be related to QTimer that Qt's dragging event interferes with it.
Even though it's not a major issue, It would be nice to solve it, as the real interaction with the windows takes place within the actual scene/render surface.

Hey sorry about that, the second video is a standalone DirectX rendering with ImGui and not related to Qt and QtDirect3D. The confusion is on me. That aside, I currently run with an Intel® UHD Graphics 750 which explain the disparity between our tests. I’d suggest to try CPU Rendering to get a possibly better reproducibility.

I’d suggest to try CPU Rendering to get a possibly better reproducibility.

Many thanks! I'll try to have a look at this next weekend hopefully. 🍻


Vara's withdrawal amount is displayed incorrectly

Describe the bug
Vara's withdrawal amount is displayed incorrectly
To reproduce the behavior
Steps:

Prepare 2 withdrawal items (Ex: 2 VARA, 2 VARA)
Perform withdraw unstake funds
After transaction successful, then check:

Withdraw amount in the history screen
Withdraw amount in the subscan

Actual:

In the history screen show Withdraw amount = 2 VARA
In the Subscan show Withdraw amount = 4 VARA

Expect: Show correct withdraw amount

Temporarily Do not fix this issue cause logic of the chain.
=> Improve UI on the withdraw screen to fix this issue.


docs: Need ISSUE_TEMPLATE

Is your feature request related to a problem? Please describe.
ISSUE_TEMPLATE is missing in this repository
Describe the solution you'd like
There is a need for an ISSUE_TEMPLATE, so adding such a template helps the user or contributor when they are raising an issue
Describe alternatives you've considered
Adding an ISSUE_TEMPLATE is the best solution for this, So adding an ISSUE_TEMPLATE is needed

@anantakumarghosh please make sure the development branch is merged with main so that people can get the benefit of the pull request.

@anantakumarghosh please make sure the development branch is merged with main so that people can get the benefit of the pull request.

development branch is merged with main.


remove cuda cache after loading vison model

Motivation
remove cuda cache after loading vison model
with llava-v1.6-vicuna-7b/
Before:

After

Motivation
remove cuda cache after loading vison model
with llava-v1.6-vicuna-7b/ Before:
After

Wrong order of pictures?


[FEAT] Create Canvas Facade

General Info

Pivotal Tracker Story
[ ] Breaking?

Note: This is a pretty massive PR, but its really just the addition of a library.  A lot of it is testing and documentation.
Changes

Add base facade.
Add testing for base facade.
Add canvas facade.
Add testing for canvas facade.
Add error handling for canvas facade.
Add necessary gems for canvas facad:

faraday
ostruct
timecop (test only)

Testing

spec/Facades/canvas_facade_spec.rb
spec/Facades/extension_facade_base_spec.rb

Documentation
Doc comments have been added to all methods in the helper library.
Checklist

[x] Name of branch corresponds to story

Note: codeclimate is requesting issues to fix, but they are relatively minor and will require massive amounts of refactoring.  Because of this and the quickly upcoming deadline, I think it makes more sense to ignore these issues for the time being and accrue them as tech debt to be handled later when we do not have a massive deadline.

this makes sense to me. i assume ExtensionFacadeBase is supposed to be the base/abstract class that is overridden for each type of LMS? if so, we discussed methods that would 'link' an assignment/course/user/whatever in Flextensions to its LMS-specific counterpart - would those methods be part of this class too, or a different facade class?

I think that it would be part of a different facade if I were to approach it the way I was thinking.  I like the idea of this facade being "stupid" in that it just makes API calls and does minimal error handling for them.  Likewise, it doesn't seek to understand the rest of the code-base/integration with our app.  The reason why I added these query parameters is because, on some level, every LMS is going to have a concept of these values, and they will all be necessary to provision an extension (canvas is a good example of how/why).  That said, I totally support extending the base class as well as more direct functionality from the API for all of these platforms is extended.  My goal with this PR specifically, though, was just to get the functionality in the canvas api facade set so that it could handle the entire workflow of provisioning an extension to a student (which is essentially what the function in the base class does).

re "not really handling errors": one thing the facade does need to do is rescue any errors on the remote side and wrap them in the generic facade's error type(s).  looks like you have a start on this already.

re "not really handling errors": one thing the facade does need to do is rescue any errors on the remote side and wrap them in the generic facade's error type(s). looks like you have a start on this already.

Oh yeah, I rescue all rails errors thrown.  I just don't have dedicated error handling for if the http response is an error.  Most of these functions in the facade just return the response itself, so I was leaving it up to the next facade / class that uses these to handle it how they see fit for their specific use case.


add translation support for persian/farsi

hi there, thanks for this useful package. I just added translation for persian language too.
best regards.

Coverage increased (+0.5%) to 85.036% when pulling 2917cc56904eb1e9c74243f19968bf132858223d on mh-firouzjaah:master into 3f4a8d284efe1c2d4c8babb4f668e67aa7f4d5df on grantmcconnaughey:master.


Update index.d.ts

Angular won't compile with "not assignable" error

While this resolves the error message, this is not a proper fix.
Cause of the issue seems to be: In leaflet's typedef the interface of L.Evented changed, so that on() does not accept arbitrary events anymore.

superseeded by #46


New version: Microsoft.OneDrive.Insiders version 22.093.0501.0001

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Microsoft OneDrive Insiders
Microsoft OneDrive

Version
22.093.0501.0001
22.093.0501.0001

Publisher
Microsoft Corporation
Microsoft Corporation

ProductCode

OneDriveSetup.exe

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1474
Microsoft Reviewers: Open in CodeFlow

/azp run

@wingetbot waivers Add Validation-Installation-Error

@wingetbot run


fix: migrate build from rollup to vite

Fix #224.

There should be no more macOS build issues and build should be much faster.


--noop mode not working

I noticed this bug where the --noop mode is not working. This bug is present on any branch.
Steps to reproduce:

Edit a file
Add the file to git
Commit(make sure that it bumps the version)
Run semantic-release --noop version
Check logs

In the logs it can be seen that the version was bumped as and a new commit as well a new tag is created.

Nothing was pushed. It just created a new tag and also a new commit bumping the version. It seems to just ignore the option and run it normally.

It is used here: https://github.com/relekang/python-semantic-release/blob/master/semantic_release/cli.py#L52
It has been a while since I have worked with click, might the problem be that only semantic-release version --noop is supported and not semantic-release --noop version?

The output definitely different:
$ semantic-release --noop version
Creating new version..
Current version: 1.0.2
Bumping with a minor version to 1.1.0.

As it does not include should have bumped from phrase at all.

Just tried it semantic-release version --noop and it works as it produces the following:
Creating new version..
Current version: 1.0.2
No operation mode. Should have bumped from 1.0.2 to 1.1.0.

But it's weird since the documentation indicates option should come fist
Usage: semantic-release [OPTIONS] COMMAND

Yeah, options should preferably work on both sides of the command.

I have a hard time reproducing this:
$ python -m semantic_release.cli --noop version --patch                                                                                rolf@snape
Creating new version..
Current version: 3.11.0
No operation mode. Should have bumped from 3.11.0 to 3.11.1.

$ python -m semantic_release.cli version --noop --patch                                                                                rolf@snape
Creating new version..
Current version: 3.11.0
No operation mode. Should have bumped from 3.11.0 to 3.11.1.

I just noticed the bug is still active:
$ cat src/__init__.py
__version__ = '0.7.1'
$ semantic-release version --noop
Creating new version..
Current version: 0.7.1
No operation mode. Should have bumped from 0.7.1 to 0.8.0.
$ semantic-release --noop version
Creating new version..
Current version: 0.7.1
Bumping with a minor version to 0.8.0.
$ cat src/__init__.py
__version__ = '0.8.0'
$ python -m pip freeze | grep semantic
python-semantic-release==3.11.2

I think the bug is still there.
semantic-release --noop version
Creating new version..
Current version: 1.4.0
Bumping with a patch version to 1.4.1.
but
semantic-release  version --noop
Creating new version..
Current version: 1.4.0
No operation mode. Should have bumped from 1.4.0 to 1.4.1.
Currently using version python-semantic-release==4.3.4
Thank you for the tool, btw, very helpful.

This is weird.
python -m semantic_release.cli --noop version # working as expected
python -m semantic_release.cli version --noop # working as expected
semantic_release --noop version # still releasing
semantic_release version --noop # working as expected

It seems like the argument is set correctly:
➤ DEBUG=* semantic-release --noop version
  semantic_release:cli 'main args:' {'noop': True, 'force_level': None, 'post': False, 'retry': False, 'define': ()} +0.0us
  semantic_release:cli 'main env:' 'PYPI_USERNAME="None",PYPI_PASSWORD="None",GH_TOKEN="None",GL_TOKEN="None",' +82.0us
  semantic_release:cli 'main config:' {'check_build_status': 'false', 'commit_message': 'Automatically generated by python-semantic-release', 'commit_parser': 'semantic_release.history.angular_parser', 'patch_without_tag': 'false', 'upload_to_pypi': 'true', 'version_source': 'commit'} +74.75us

The reason you are seeing different behavior for those two cases is because of the argument sorting that is being done in the cli.py
If you print the name variable in the two cases, you will see that it is main when using the python -m syntax and semantic_release.cli when running directly. Changing the if statement to run in both these cases fixes the issue

While that solution did fix the issue, it caused problems with the test runner. Instead, I added an entry method that does the same thing and changed setup.py to use that method as the entry point.
I have added this fix to #166


AWS managed credentials are already disabled

Per https://eksworkshop.com/ee-support/prerequisites/workspaceiam/:
"Turn off AWS managed temporary credentials"
The option was already disabled when I opened preferences:

https://github.com/aws-samples/eks-workshop/pull/301

Perms were disabled out of band, closing out.


Expiration policy guidelines for Check-in

Summary
Expiration policy guidelines for AAI Check-in Registry VO membership lifecycle

The subject of the notification still seems to be defined ("TODO").
Fixed


Error on init

Hi, i'm using your latest 3.1.1 version for Godot 3.3+ (also tried the previous 3.1.0), and i do have an error when calling the init method. GooglePlayServices are installed on the phone and i can use them in other games.
The singleton is found but the error says no init in it.
Any idea?

Hi, I am also getting the same error, did you find the fix for it?

Hi. Yes I did. The init method wasn't the right one. I have changed it. I
don't remember by heart I should look at the code.
On Sat, 10 Jul 2021, 16:43 Vipul Behl, @.***> wrote:

Hi, I am also getting the same error, did you find the fix for it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/oneseedfruit/PGSGP/issues/1#issuecomment-877598353,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANP66YL6M62UQPNBYAEGIKDTXAB2JANCNFSM45QTYZQQ
.

Thanks, I found the solution. If anyone else is looking for the same thing. You need to change the init method. Use the following.
play_games_services.init(true,false,false,"")
play_games_services.initWithSavedGames(true, "SAVE_GAME_NAME",false, false, "") # Use this init if you want saved games feature to be enabled
@oneseedfruit You can close this issue. This is causing confusion because people are following the readme from cgisca/PGSGP. It's probably a better idea to use this repo instead, as it doesn't seem like the parent repo is supported anymore.

Thanks, I found the solution. If anyone else is looking for the same thing. You need to change the init method. Use the following.
play_games_services.init(true,false,false,"")
play_games_services.initWithSavedGames(true, "SAVE_GAME_NAME",false, false, "") # Use this init if you want saved games feature to be enabled

Yo, on your example, you didnt pass the request_token. is it okay not to input it?

Request token isn't required when you are deploying on Android, as it takes the value from Strings.xml for other platforms it is required

@vipulbehl Can you help me with the sign. I am getting a 12501 error. I am passing play_games_services.initWithSavedGames(true, "SAVE_GAME_NAME", false, false, "") this for initializing. I checked the error codes and it shows the message is displayed when user cancels the sign-in request (The sign in was cancelled by the user. i.e. user cancelled some of the sign in resolutions, e.g. account picking or OAuth consent) But, I am 100% sure, there's no request for cancellation in my code. As it was working in 3.3.3 before I updated to 3.3. Can you help, please? I can provide you with additional code .

Whenever I have the init method not commented out the app instantly crashes. Im using the new play_games_services.init(true,false,false,"") with godot 3.2.3 (because I tried newer versions and got the same issue)

Does openjdk version matters ? Do we need to downgrade the jdk to openjdk8 ? Im on version 11 right now.

Does openjdk version matters ? Do we need to downgrade the jdk to openjdk8 ? Im on version 11 right now.

You must use jdk 8.

I tried it but gradle requres Java11 for godot 3.4 https://github.com/godotengine/godot/pull/53610

I would not worry about JDK 11 I am using it in 3.4  for a tutorial and its fine.


#11769: extend support for transposing/permuting bfloat8 tensors on n…

…on-WH swaps by typecasting to bfloat16
Ticket
Link to Github Issue
Problem description

Add bfloat8 tiled support for transpose
Remove some deeply unserious code

What's changed
Describe the approach used to solve the problem.
Summarize the changes made and its impact.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

https://github.com/tenstorrent/tt-metal/actions/runs/11021619550

https://github.com/tenstorrent/tt-metal/actions/runs/11022888618

https://github.com/tenstorrent/tt-metal/actions/runs/11022565086


close #3: follow redirects

This fixes #3

Awesome! Thanks a lot. Just a small remark.
Could you also please use a conventional commits style commit message?

Done


Create Blog “data-mapping-of-the-anthropocene-curriculum”

Automatically generated by Netlify CMS

👷 Deploy Preview for famous-kulfi-ae21db processing.

Name
Link

🔨 Latest commit
2515c669fc2802b0bd9385941623a4e8f9f2c6a2

🔍 Latest deploy log
https://app.netlify.com/sites/famous-kulfi-ae21db/deploys/658417fd0502c20008f3868a


Video

https://user-images.githubusercontent.com/51350490/229265170-401985da-82b5-4864-86c0-be9264e8e2d0.mp4

https://user-images.githubusercontent.com/51350490/229266001-504f7541-f5c1-40b4-b47b-09b59ae968a8.mov

https://user-images.githubusercontent.com/51350490/235204999-fec6d482-c180-41c4-9831-2481162849e6.mov

Uploading i think.mp4…

https://github.com/owochel/DanceOnE-Textbook/assets/51350490/4e764281-4687-443d-b2f2-2b1beadaa263

https://github.com/owochel/DanceOnE-Textbook/assets/51350490/3b55cba4-522c-43cd-8206-909d68b8f605


Document the use of dollar sign and period in a field name

What
This PR adds content to the documentation to explain the use of $ and . in field names.
Why
A user needs to understand the expected behavior of the query and indexing engine when naming fields.
How
Add a "Restrictions" sub-heading under the "Creating Indexes" heading to describe the behaviors of using a dollar sign as the first character in a field name and a period within a field name.
reviewer @mikerhodes
reviewer @gadamc
BugId: 47451

:+1:

+1


d2i_ECPKParameters and i2d_ECPKParameters are not deprecated

So do not document them as such.
Fixes #22068

This pull request is ready to merge

Merged to master, 3.1, and 3.0 branches. Thank you for the reviews.


Add ERC-20 approvals mini-app

Summary
This mini-app will list all ERC-20 approvals, and allow the user to revoke their allowance
Description
This app loads past events in chunks from the latest block to ~ Sept 2015. The approvals will appear as they are loaded. The user can revoke their approval at any time, making the allowance not to be listed. The first sync might take a while, considering the number of blocks.
If the user leaves, the sync process will continue from the last sync blocked. Once the whole history has been reviewed, each time the user visits the page the app will sync from the newest recent block to the previous one (the one that was the most recent in the first sync) and so on.
Related Issue
Closes #33
How Has This Been Tested?
In both mainnet and ropsten. There were some issues while trying to testing this in a local fork: it wouldn't bring the past logs and it would throw an error in the console (we think this is a bug in ganache-cli)
Screenshots (if appropriate):
An example of a listed approval.

Thanks for your comments! Suggestions applied in https://github.com/purefinance/pure.finance/pull/38/commits/6d39f15fbb1025f897a66e77eb291fca36acb594

In addition, it looks like infinite/unlimited approvals need to be handled in a different way. See PF's result:

And Etherscan's:

In addition, it looks like infinite/unlimited approvals need to be handled in a different way. See PF's result:

And Etherscan's:

I was using 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff as the unlimited value because this is the one being used in token-approvals in PF. Perhaps I should use just a large enough number? (which one?)
As for the other issue, I'll review it. Thanks for the testing!

I was using 0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff as the unlimited value because this is the one being used in token-approvals in PF. Perhaps I should use just a large enough number? (which one?)

My guess would be a hueristic such as:  Some multiple of total supply.  Each transaction should decrement the approved amount.  That implies to me that 0xffff...ffff condition would only exist when there are no further transactions.

@jgarzik some ERC-20 contracts have a condition in their transferFrom methods so if the allowance is 0xffff...ffff, it is not decremented. That effectively makes it "infinite". Others do not, which is the case of VSP.
I like the heuristics you mentioned. In fact, any allowance larger than the total supply is in all practical terms, unlimited. We could check against 10-100x the supply to be on the safe side, though.

I fixed the scenario when switching accounts in https://github.com/purefinance/pure.finance/pull/38/commits/2e816b5e9bf127ed76bb7054ea5063a7c7485c72 and I applied the new heuristic for checking unlimited allowance here https://github.com/purefinance/pure.finance/pull/38/commits/98d09864648b6dcddebef6fec7a110d726167dc6

Suggestions applied here https://github.com/purefinance/pure.finance/pull/38/commits/7fa2dadd7b220100b56fa35e6eed8357adcaebe8

screenshot


Implement DoT UPDATE for wellbore

Child of #102
BLOCKED -> waiting for drilltest support for this API endpoint

as of commit 04588b76f23811fcf810bf041def30fd9e7fab36 this is now supported in drilltest


New Ranges Feature

I've started to implement proper ranges for the library. This pull request is not one that is ready to be merged with the main branch. Many functions don't have an implementation yet, and it still lacks some features I would like to add. But I would like some feedback before progressing in the direction I am going.
What is new
Here is a quick summary of what is present:

Extention of the OffsetDateTime struct, adding functions likes floor_seconds(), ceil_seconds() and next_second(). They are necessary to the OffsetDateTimeRangeExt.
Extension of the Range<OffsetDateTime> struct with functions like days(), full_days(), overlapping_days(), intersection(), union(), ...
Extension of &[Range<OffsetDateTime>] slices (no functions implemented yet).

Important notes about ranges:

You need two OffsetDateTime to create one range, so it was decided that the ranges will always work with the offset of the start datetime.
If the ranges are reversed (end < start), most methods on this range will return None or an empty Vec.

Questions I might have
Should ranges implement the Copy trait ? The struct Range<OffsetDateTime> never changes, and doesn't implement the Iterator trait, so there shouldn't be any problem with this. I would like your feedback on the idea.
EDIT: You can't implement the Copy trait, as the Range struct is not defined inside the crate.
Coming improvements

Implementing missing functions
Implementing OffsetDateTimeExt for RangeInclusive
Parsing & Formatting for ranges
More unit tests
Double sided iterators
Range creation macro ?
Similar functions for millis, micros and nanos ?

Just a heads up, it'll probably be a few days before I get to looking at this.

Yeah, when I get around to it (possibly this coming weekend), I'll be looking at the public API, not the implementation.

After a quick review of the public API, I'm honestly impressed that you managed to get this working — it's a complicated thing to manage. With that said, I am (unfortunately) closing this pull request, as I feel it's far too large for me to manage at this point in time. I am quite busy working on language-related matters, so any issues that pop up would require me to spend time that I don't have.
Thank you for your contribution regardless! If/when I come around to having iterator helpers, I will definitely look at this code for guidance.


Bump up to v0.10.36-SNAPSHOT

As filed an Issue in #16, its tests on GitHub Actions stopped working on macOS for some unknown reason. (Hours to finish only on macOS, but still failing.)
2b95eb3f820b6e522fe3e8ae9234c8b9af9408bf is only updating the version number, no any other changes. So, it's something wrong with GitHub Actions.
Through an effort to making the situation better,

Migrated to OpenJDK 8 Eclipse Temurin, instead of Zulu.
Changed to test all plugins in one GitHub Actions job, per OS.

Because downloading Gradle and dependencies looked taking time on macOS. (Still not working though.)

Thanks!


How to use?

I guess I'll be the one to ask this question, since I can't seem to find any explanation:
How do I use this once I've installed it?
Seems like something that would be good to explain in the README, or on the website?

@amundo, would you still like some help?

yes i would how do you use this thing

You have to install it in your browser (for Firefox); then you should have access to the module menu through its icon.
If I remember properly, you have to change the parameters to a Unicode copy instead of the :name: one, and it only works by copy.


Switch to using clasp API maybe?

What do people think of the idea of switching to whatever API it is that clasp is using, instead of the (apparently undocumented and sort of volatile) RPC API we're currently using? I love what this extension does, but it seems like it's prone to flakiness as a sort of unavoidable consequence of going through the RPC API. I feel like it we migrated it to use the clasp API it would be solid and even more lovable.

as far as i know, clasp is for deploying a project to gas, it does nothing about scm. it just give you the possibility to manage code locally with anyway you like.
if you still want to use the online editor, there's no way to escape from the RPC

Sure, I was just adding my vote because I'd been bitten by RPC-caused errors a couple of times (the failure if the name of the file is a function in the file, the RPC change from a couple of days ago)... I more or less switched to a different workflow to avoid having to use the plugin temporarily as a result. I like the plugin and it's extremely convenient, though, so I wanted to put in some advocacy for switching to a method of talking to the server that doesn't involve this occasional brokenness.

switched in 5.0.0

switched in 5.0.0


WIP; beginning integration of the burwell-sources SPA

Beginning integration of the burwell-sources SPA. Currently, it works about as well as the only live version I could find here. I've rearranged the state management in a similar style as the rest of webv4. As well as refactored the IndexMap component.
Still more to do! There is another page in the app, FeatureList that is not accessible, I couldn't find it on the live version either. Before merging to main I think we should enable this feature, as well as the Scale which seems like a way for the user to filter the size of map source they view, but this is again not something that I see implemented. We should also switch components to blueprintjs and fix stylings. This is a much smaller app so I don't think it will take much effort.

Nice. When you're finished, can you see if you can mark the 'sources' repository as archived?

The scale feature (filter displayed sources by their scale) worked recently, so some change must have been made in a recent commit that broke it. I can't remember what the "view" option was supposed to do.

Things are almost done! I updated the Options menu to use blueprint components and was easily able to re-implement changing the view and scale. Both user interactions are responsive. I also parsed some common functionality for Mapbox initializer functions. Outside of styling, there are 2 bugs/issues that persist.

When changing back from List view to Map view, the features don't render until a new scale is chosen.
On the List view, we need a way to generate static maps as the component wants to render one for each burwell-source. The old code appears to be doing this, rendering a png background, however it errors saying it no longer exists. There's a way to do this I believe in Mapbox studio.


(bot) Update Helm release nfs-subdir-external-provisioner to v4.0.11

This PR contains the following updates:

Package
Update
Change

nfs-subdir-external-provisioner
patch
4.0.3 -> 4.0.11

Release Notes

kubernetes-sigs/nfs-subdir-external-provisioner
v4.0.11
Compare Source
nfs-subdir-external-provisioner is an automatic provisioner that used your already configured NFS server, automatically creating Persistent Volumes.
v4.0.10
Compare Source
nfs-subdir-external-provisioner is an automatic provisioner that used your already configured NFS server, automatically creating Persistent Volumes.
v4.0.9
Compare Source
nfs-subdir-external-provisioner is an automatic provisioner that used your already configured NFS server, automatically creating Persistent Volumes.
v4.0.8
Compare Source
nfs-subdir-external-provisioner is an automatic provisioner that used your already configured NFS server, automatically creating Persistent Volumes.
v4.0.6
Compare Source
nfs-subdir-external-provisioner is an automatic provisioner that used your already configured NFS server, automatically creating Persistent Volumes.
v4.0.5
Compare Source
nfs-subdir-external-provisioner is an automatic provisioner that used your already configured NFS server, automatically creating Persistent Volumes.
v4.0.4
Compare Source
nfs-subdir-external-provisioner is an automatic provisioner that used your already configured NFS server, automatically creating Persistent Volumes.

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (4.0.11). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


[Text Analytics] [AAD] TextAnalyticsClient LROs #analyze some documents with errors and multiple actions failing in nightly runs

Text Analytics nightly test runs are failing with:

Error message:
Internal server error
Stack trace:
RestError: Internal server error
at compileError (/Users/runner/work/1/s/sdk/textanalytics/ai-text-analytics/src/util.ts:76:46)
at AnalyzeLro.sendInitialRequest (/Users/runner/work/1/s/sdk/textanalytics/ai-text-analytics/src/analyzeLro.ts:16:55)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at GenericPollOperation.update (/Users/runner/work/1/s/sdk/core/core-lro/src/lroEngine/operation.ts:70:22)
at LroEngine.pollOnce (/Users/runner/work/1/s/sdk/core/core-lro/src/poller.ts:315:26)

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1213880&view=results

This is a service-side issue and I am reluctant to change the SDK-side test for it. /cc @maorleger is there a guidance on what to do for such cases?

Agree that I wouldn't change the SDK-side tests for this. An Internal server error (500) is something that should be investigated on the service side - is this repeatable or inconsistent? If repeatable maybe we can reproduce it with logging enabled and send them the request-id?

@maorleger it is not consistent and the latest run succeeded. I will close this issue then based on our discussion.


Let people customize the tooltip appearance more easily

Hello, I'd like to be able to customize the tooltip appearance easily.
It would be easier if we could use the tooltip without inlined styles through JS and avoid "tooltip color theme" that are not useful most of the time because they don't fit the design.
It would be only about importing the css that makes the tooltip functional.
For the appearance, it would be possible to make our own styles and simply add the class to the tooltip. Without the "important!" rule to override the inlined styles.

You can use the attribute class to import your custom style, but you have to use important! if you want to override some attribute that tooltip has used as default.

I have read the docs about it. I would like to avoid this situation. It is happening because the appearance is set by inlining styles on the element instead of being included in an external stylesheet that could be customised at will. I feel it is ok to have "function styles" inlined. "the stuff" that makes the tooltip positioning correct, etc.
But for appearance, inlining styles this way (high in the css priority mechanism) leads to ultimate "hack" like !important. When I publish components I make sure they can be customised through external stylesheets and limit inlined styles to minimum. Just "my way" of thinking, I'll use important in the meantime. Thank you for the module :)

Actually I was thinking about this for a long time, but react-tooltip is not using inline style, the component will add style to the header when you render the component, see the source code here https://github.com/wwayne/react-tooltip/blob/master/src/index.js#L568
this is react-tooltip style source file(sass) https://github.com/wwayne/react-tooltip/blob/master/src/index.scss, sometimes you have to use !important because for example the backend color is generated by two classes .__react_component_tooltip.type-dark but you only have one class to manipulate the backend-color, so the default has higher priority, then you have to use !important
At the moment, I don't have any idea on how to get rid of !important, if you have interest,  I've written an article to introduce what I did on this<EMAIL_ADDRESS>

I'll read the article for sure (but I am at work xd).
Why not using a single class for the appearance?
like .__react_component_tooltip-default that is set if no other class is passed.
I do this kind of patterns in my components, not just for styling.
<Component skinClass="my-style"/>
// component render

const cssClasses = this.props.skinClass || '__react_component_tooltip-default'

Regarding the css appending, it will still have more priority because it is appended at the bottom of the head, after the app own styles.
With 3rd parties, I can control the priority of their styles if I am the one who decides where / when it is included. (having access to the css / less / scss file)

Sounds good, could a better practice for a component, I will take a try when I'm free, I'm at work too : ) , thanks for your advice.

After some investigation I find it is hard to put all style in a single class, using class group to control the tooltip placement and colour does make sense.
So closing this ticket at the moment until we find a bette solution, more example will be added to the example page.

Too bad that this issue is closed because the styling of the tooltip simply does not work in my setup. I use styled-components to style my components; it is so simple to use and so obvious that it makes any other alternative look convoluted.
I don't even use css loaders nor preprocessors for styling in my webpack config. Which makes it incompatible with the way react-tooltip styles its component.
Would you have any suggestion?

@jeanmichelcote You could make a PR allowing for custom styles.

Also stuck on this, FWIW
Even specifying what classes need to be manipulated would be helpful. I'm trying to just control the border color and its proving really challenging to do so.
Added a custom class .tooltip-border
It changes the border color, aside from the pointer part of the tool-tip.
I looked at the SASS (https://github.com/wwayne/react-tooltip/blob/master/src/index.scss) and tried to overwrite the relevant rules (see below) but still no love
`.tooltip-border {
border: 1px solid $red1 !important;
&.border{
&.place-bottom {
&:before {
border-bottom: 8px solid $red1 !important;
}
}
}
}`

having to add !important is still an issue...

having to add !important is still an issue...

This also has poor compatibility with Tailwind CSS and twin.macro (styled components for Tailwind). One hack is it just use !important globally in Tailwind (there's a setting for it), but I don't want to turn this on just for a single component.

A shame this is still an issue, definitely don't want to use !important, I just want to style css!


Not serializing dynamically added style attribute

First, Awesome project! Thanks
Now on the issue: when we add the styles through DOM manipulation it doesnt serialize:

 var jsdom = require('jsdom');
 jsdom.env("

", [], function(err, window) {
     var doc = window.document
     doc.getElementById('fooStyle').style.width = "200px";
     doc.getElementById('fooStyle').style.height = "200px";
     console.log(doc.outerHTML);
});

Somebody who knows the code cares to have a look? It probably relates to the latest fix of the 2 times serialization of before.
Thanks in advance.

soo.. apparently fgnass did already fix this problem in https://github.com/fgnass/jsdom/commit/11f1db77659d14be4e799b0138a36d5192bf3ec9
by patching cssom with direct property setters/getters instead of setProperty() calls.
The owner of cssom is not going to pull fgnass its solution/upgrade, but it seems like they are
planning on setting up a new cssom repo where changes like that (making it more css conform) can me made.
But until then I don't think its a bad idea to let the cssom dependency in package.json point to fgnass its cssom version.


Add support for python, python3 and update solution stacks

Updated the spring/java, node and rails solution stacks. Additionally, support for python and python3 was added. There are no content changes to the READE file, I just removed unnecessary whitespaces.

Just merged the pull request, thanks for submitting it!


Support for conditional groups

OK I try to re-formulate the problem I mentioned in https://github.com/fsprojects/Paket/pull/1018#issuecomment-135829321.

@forki Nice, thanks!
Ok I did some more tests and was really impressed to get NO error after specifying
Microsoft.AspNet.Razor

group Net40
 Microsoft.AspNet.Razor

group Razor4
 Microsoft.AspNet.Razor

in paket.references. I think what paket does is correct even considering that the resulting >csproj will not compile.
the first two are fine because one is net45-only and the other one is net40-only. But the third >one is net45 only as well.. This means I need some way to specify which one to take at build time >(I don't want to use two references to the same nuget package on a single compilation).
One suggestion would be to allow something like
group Main if NET45
 Microsoft.AspNet.Razor

group Net40
 Microsoft.AspNet.Razor

group Razor4 if RAZOR4
 Microsoft.AspNet.Razor

in paket.reference (or even paket.dependencies, not sure right now) and then add a condition >to the msbuild references like Condition="$(RAZOR4) == 'True':
<When Condition="$(RAZOR4) == 'True' And $(TargetFrameworkIdentifier) == '.NETFramework' >And ($(TargetFrameworkVersion) == 'v4.5' Or $(TargetFrameworkVersion) == 'v4.5.1' Or >$(TargetFrameworkVersion) == 'v4.5.2' Or $(TargetFrameworkVersion) == 'v4.5.3' Or >$(TargetFrameworkVersion) == 'v4.6')">

This is a feature request, but imho one that would make the group feature more useful.
Is this a scenario you want to tackle with the new group feature?

In RazorEngine we use 3 different builds for 3 different Razor versions

Razor2 (last version supporting NET4.0)
Razor3 (current stable)
Razor4 (vnext, currently beta, used by some people for coreclr/ASP.net5 support)

We use conditional compilation to take care about the API differences and provide the same API on all 3 builds. The thing is that if we develop a new RazorEngine feature there is no reason to support only the latest when it will work fine on any Razor version. Handling 3 branches is not really an option either.
Now with the group feature I can compile for Razor2 and Razor3 because they target different frameworks.
Paket will generate a csproj file like this (this is simplified):
<Choose>
  <When Condition="$(TargetFrameworkVersion) == 'v4.5'">
     <ItemGroup>
      <Reference Include="System.Web.Razor">
        <HintPath>..\..\..\packages\Microsoft.AspNet.Razor\lib\net45\System.Web.Razor.dll</HintPath>
      </Reference>
    </ItemGroup>
  </When>
  <When Condition="$(TargetFrameworkVersion) == 'v4.0'">
     <ItemGroup>
      <Reference Include="System.Web.Razor">
        <HintPath>..\..\..\packages\net40\Microsoft.AspNet.Razor\lib\net45\System.Web.Razor.dll</HintPath>
        <Paket>True</Paket>
      </Reference>
    </ItemGroup>
  </When>
</Choose>

Which is perfect!
But I still can't add Razor4 to the mix, because the reference would be enabled the same time as Razor3 (when compiling for net45):
<Choose>
  <When Condition="$(TargetFrameworkVersion) == 'v4.5'">
       <ItemGroup>
        <Reference Include="Microsoft.AspNet.Razor">
          <HintPath>..\..\..\packages\razor4\Microsoft.AspNet.Razor\lib\net45\Microsoft.AspNet.Razor.dll</HintPath>
        </Reference>
      </ItemGroup>
  </When>
  <When Condition="$(TargetFrameworkVersion) == 'v4.5'">
     <ItemGroup>
      <Reference Include="System.Web.Razor">
        <HintPath>..\..\..\packages\Microsoft.AspNet.Razor\lib\net45\System.Web.Razor.dll</HintPath>
      </Reference>
    </ItemGroup>
  </When>
  <When Condition="$(TargetFrameworkVersion) == 'v4.0'">
     <ItemGroup>
      <Reference Include="System.Web.Razor">
        <HintPath>..\..\..\packages\net40\Microsoft.AspNet.Razor\lib\net45\System.Web.Razor.dll</HintPath>
      </Reference>
    </ItemGroup>
  </When>
</Choose>

Notice how TargetFrameworkVersion=v4.5 will now enable two System.Web.Razor.dll versions, which is not what I want, so I need some way to tell paket to generate an additional condition which should be true.
One way to solve this is adding a way to tell paket to add a group with a custom msbuild condition (see example syntax in from my earlier comment).
Just something to note: Groups already improve the situation as we don't need nuget.exe anymore to resolve Razor2 and Razor4 :+1: . I still need to update all csproj files by hand, but at least I now have stable paths and can use paket update (of course I still need to set <paket>false</paket> for the Razor3 and Razor4 dependency).

Ah. You forget to specify different versions in the first dependencies file. I thought: why would someone install the same package version 3 times.

what if we make this feature independent from groups:
group Main
 Microsoft.AspNet.Razor ~>1.0 condition:NET45

group Net40
 Microsoft.AspNet.Razor ~>2.0 condition:NET40

group Razor4
 Microsoft.AspNet.Razor ~> 3.0 condition:RAZOR4

I mean this would the be like all the settings in http://fsprojects.github.io/Paket/nuget-dependencies.html#Framework-restrictions

Yes that would work for me as well.
I kind of like the idea of a per-package setting.
But on the other hand I'm not sure if we need so much power and it would kind of mess with the paket idea of a  "consistent view" of the dependencies.
I think the main usage should be to switch between a consistent set of dependencies instead of single packages.

mhm. good point.

How do normal settings behave on indirect references? If I have
B ~>1.0 condition:NET45
C ~>1.0

where B and C both depend on A. Then A would have the condition:NET45 setting as well, correct?
This would be a problem and a reason why condition shouldn't be a normal setting.

yes. that would be a conflict.

Ok I added (very very basic) support for this. The generated XML is probably completely wrong right now (I need real samples).
BUT: You can now specify conditions for groups and individual packages.
you can see how it works in the tests at https://github.com/fsprojects/Paket/commit/a815b1aa09b51da821ba93bc348028850d81d506#diff-9fd8e28cd8dc7e84109e9d54ddbd8a84R714
Please try it out and tell me where and how it breaks ;-)

Everything seems to be working fine! One thing I noticed is that the condition generates the warning

MSB4130: The condition ... may have been evaluated incorrectly in an earlier version of MSBuild. Please verify that the order of the AND and OR clauses is written as intended. To avoid this warning, add parentheses to make the evaluation order explicit.

I couldn't find a lot of info about this warning, but it seems to disappear when we generate '$(RAZOR4)' == 'True' (notice the additional quotes around the variable) OR when we put the condition at the first place (instead of at the end).

PR against groups branch are very welcome
On Aug 29, 2015 12:04 PM, "Matthias Dittrich"<EMAIL_ADDRESS>wrote:

Everything seems to be working fine! One thing I noticed is that the
condition generates the warning
MSB4130: The condition ... may have been evaluated incorrectly in an
earlier version of MSBuild. Please verify that the order of the AND and OR
clauses is written as intended. To avoid this warning, add parentheses to
make the evaluation order explicit.
I couldn't find a lot of info about this warning, but it seems to
disappear when we generate '$(RAZOR4)' == 'True' (notice the additional
quotes around the variable) OR when we put the condition at the first place
(instead of at the end).
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1026#issuecomment-135968043.

Once released, RazorEngine can finally make the full switch to paket and get rid of nuget.exe :+1:
Thanks @forki.

Wow. Cool to hear.
On Sep 5, 2015 6:28 PM, "Matthias Dittrich"<EMAIL_ADDRESS>wrote:

Once released, RazorEngine can finally make the full switch to paket and
get rid of nuget.exe [image: :+1:]
Thanks @forki https://github.com/forki.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1026#issuecomment-137972702.