Support minCount in TextArea component

Request for TextArea component minCount prop
Currently there is a maxCount prop on the TextArea component that limits the number of allowed characters to be below a certain number.
https://svelte.carbondesignsystem.com/components/TextArea#maximum-character-count
For different use cases, it would be very useful to be able to specify a minCount, that requires the user to type a minimum number of characters, also showing the character count as maxCount does.
If the length of input is below minCount it should put the component in an invalid state and indicate that more characters are required.
This could be implemented by users of the library if there was a prop showCharacterCount or similar, that didn't put a restriction on maxCount but shows the character count in the top right.

Seeing that the core React library doesn't have a minCount prop, this requires upstream designs. I recommend opening a ticket in https://github.com/carbon-design-system/carbon/issues to kick off this functionality.


Allow blacklisting HTTPS requests without connecting to server first

This is a problem because these sorts of pathological situations are exactly why I started using browsermob-proxy.  Workaround is to use AdvancedHostResolver#remapHost instead, but this is unsightly and might fail in some corner cases.
I think it probably has something to do with the order the HttpFiltersSourceAdapters are applied in BrowerMobProxyServer, but I'm new to this code base.  I think either ResolvedHostnameCacheFilter or HttpsOriginalHostCaptureFilter requires a valid SSL socket to be created before the blacklist is applied in BlacklistFilter.
Using bmp 2.1.1 and selenium 2.53.1.
Test case:
    @Test
    public void bugReport() throws Exception {
        final BrowserMobProxyServer server = new BrowserMobProxyServer();
        server.blacklistRequests(".*google\\.com.*", 204);
        server.blacklistRequests(".*licdn\\.com.*", 204);
        server.start();

        final Proxy proxy = ClientUtil.createSeleniumProxy(server);
        final DesiredCapabilities capabilities = new DesiredCapabilities();
        capabilities.setCapability(PROXY, proxy);
        final FirefoxDriver driver = new FirefoxDriver(capabilities);

        // works fine
        driver.get("https://www.google.com/");

        // java.net.SocketException
        driver.get("https://media-vnsh.licdn.com/");
    }

DEBUG logs:
2016-07-21 17:04:32,868 [:main] DEBUG ImpersonatingMitmManager - Allowed ciphers for proxy connections to upstream servers (some ciphers may not be available): [TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDH_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_MD5, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2016-07-21 17:04:32,869 [:main] DEBUG ImpersonatingMitmManager - Allowed ciphers for client connections to proxy (some ciphers may not be available): [TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA, TLS_ECDHE_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_SHA, TLS_ECDH_ECDSA_WITH_RC4_128_SHA, TLS_ECDH_RSA_WITH_RC4_128_SHA, SSL_RSA_WITH_RC4_128_MD5, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
2016-07-21 17:04:32,990 [:main] INFO  DefaultHttpProxyServer - Starting proxy at address: <IP_ADDRESS>/<IP_ADDRESS>:0
2016-07-21 17:04:33,049 [:main] INFO  DefaultHttpProxyServer - Proxy listening with TCP transport
2016-07-21 17:04:33,454 [:main] INFO  DefaultHttpProxyServer - Proxy started at address: /0:0:0:0:0:0:0:0:37211
2016-07-21 17:04:36,264 [:LittleProxy-0-ClientToProxyWorker-1] DEBUG ImpersonatingMitmManager - Impersonated certificate for tiles-cloudfront.cdn.mozilla.net in 462ms
2016-07-21 17:04:36,349 [:LittleProxy-0-ClientToProxyWorker-0] DEBUG ImpersonatingMitmManager - Impersonated certificate for www.google.com in 547ms
2016-07-21 17:04:57,382 [:LittleProxy-0-ProxyToServerWorker-2] INFO  ProxyToServerConnection - (CONNECTING) [id: 0x6af86dfa]: Connection to upstream server failed
java.net.SocketException: Socket is not connected: no further information: media-vnsh.licdn.com/<IP_ADDRESS>:443
    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
    at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:224)
    at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:289)
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:545)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:485)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:399)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:371)
    at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
    at java.lang.Thread.run(Thread.java:745)
2016-07-21 17:04:57,444 [:LittleProxy-JVM-shutdown-hook] INFO  DefaultHttpProxyServer - Shutting down proxy server immediately (non-graceful)
2016-07-21 17:04:57,444 [:LittleProxy-JVM-shutdown-hook] INFO  DefaultHttpProxyServer - Closing all channels (non-graceful)
2016-07-21 17:04:57,450 [:LittleProxy-JVM-shutdown-hook] INFO  ServerGroup - Shutting down server group event loops (non-graceful)
2016-07-21 17:04:57,452 [:LittleProxy-JVM-shutdown-hook] INFO  DefaultHttpProxyServer - Done shutting down proxy server

Yes, you've found an unfortunate limitation of BMP that stems from LittleProxy's ConnectionFlow. There's a refactor of CF in the works that will solve this problem, but it won't be released until later this year. Actual HTTP requests (other than the CONNECT) are blacklisted, but the initial CONNECT still must be successful.
As you note, it's possible to work around it by using the AdvancedHostResolver to remap the host. That is less than an ideal solution, and will be addressed after the ConnectionFlow refactor.

@jekh, is there any progress on that CF rewrite?

Not yet, unfortunately. I'm on the verge of releasing the next version of the REST API for comment. ConnectionFlow refactor is the next big thing on my list though.

No updates on this issue? I'm having problems with a page that takes so long to load and I want to blacklist it, but the page is under HTTPS and is still being loaded.
And AdvancedHostResolver is not an option, since I still need to open the HTTPS website.

Any updates, guys? Having problems with blacklisting that doesn't work for https is really upset thing..

@lightbody  perhaps you can give any update on it? Is it  possible to implement this feature?

Hi all. Any updates?

Hello! Does anyone managed to resolve this problem independently from the browsermob-proxy ? Thank you!

Hi all. Any updates?


Update PWA app description

The referenced PWA sample app, while owned by the Polymer project, doesn't actually use Polymer.

Polymer isn't a framework... it's a state of mind

Thanks @krumware!

Lmao


Add source map

Please add source map on the demo site to ease the learning process as people going around the site.

Done in b887fd2427b285ec2dbdedaaa7ba19ee1c4be3f1


How to show JS confirm alert with TD elements ?

I make listing of data/table with TD elements for data cells and I have a question if there is a way
to make delete button with JS confirm alert and javascript code/axios request if user selected “Yes”
to run request on server side?
Please examples.
    "laravel/framework": "^9.19",
    "orchid/crud": "^3.8",
    "orchid/platform": "^13.6",

Thanks!

I have used a simple button:
Button::make(__('Delete'))                 ->icon('trash')                 ->confirm(__('Are you sure?'))                 ->method('remove')


bug: Unable to install after upgrade to capacitor v4

Platform(s):

"@capacitor/core": "^4.0.1",

Current behavior:

ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ****
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@capacitor/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@capacitor-community/text-to-speech
npm ERR!   @capacitor-community/text-to-speech@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

I will release the update over the next week.

@samizarraa You can already give it a try:
npm i<EMAIL_ADDRESS>

Same problem!

Did you try the dev build? What is the error message?

Did you try the dev build? What is the error message?

npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@capacitor/core
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@capacitor-community/text-to-speech
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

@samizarraa You need to do a clean install:

Remove node_modules folder
Remove package-lock.json
Update the version number of this package manually in your package.json
Run npm i

@samizarraa You need to do a clean install:
1. Remove `node_modules` folder

2. Remove `package-lock.json`

3. Update the version number of this package manually in your `package.json`

4. Run `npm i`

It works fine when I installed first time,but got the same error when I tried "npm update"

@samizarraa You need to do a clean install:

1. Remove `node_modules` folder

2. Remove `package-lock.json`

3. Update the version number of this package manually in your `package.json`

4. Run `npm i`

It works fine when I installed first time,but got the same error when I tried "npm update"

Sure, because 'npm update' updates the dependency to the latest version. This is just a dev version. It is not yet the latest release. I will release the dev version as soon as it is tested. Just install the dev version and give it a try.

Ok, Thanks


Log NNPACK profile to std::cout instead of LOG(INFO)

Similar to #2333, but for NNPACK bindings

Wait, for core libraries we never want to do std::cout because this will print stuff during execution time, so I thin we should keep LOG(INFO) in this case.

@Yangqing It will log only if you run the binary with --caffe2_profile_nnpack, which is off by default, and practically only used for performance analysis & tuning.

Ah got it, makes sense.


Fix demo application, if no knn dict was provided and over 100 docs are indexed

Description
If you index over 100 documents with the demo application without providing a KnnVector dictionary via the -knn-dict parameter you'll run always into this code path, which throws an exception. This PR extends the condition to only be executed, if an actual KnnVector dictionary was provided.
Note: As test-files/docs only contains 16 documents I hesitated to introduce additional 85 docs just for testing this specific functionality of the demo application. Happy to add it anyway, if needed. We could also parameterise the thresholds via an additional constructor, but again don't know, how extensively this should be tested.
Closes https://github.com/apache/lucene/issues/12330

I also cherry-picked to branch_9x: 3d109bdc493b451f967a7ad3102267c9d177ade0


3.7.11 release failed to push packaging artifacts

3.7.11 tag was pushed, but the artifacts are not showing on https://docs.flutter.dev/release/archive?tab=macos for any platform.

Issue was the tool proxy command did not indicate the packaging builds were scheduled. We'll send workflow updates to paste the packaging console at the end.
Larger issue uncovered here is the engine tag was incorrect.

Should we open a new bug to track the incorrect engine tag. The issue in this bug is working as intended proxy tool just tags and pushes and luci scheduler is the one triggering the packaging builds as post-submit to stable | beta branches.

Marking this as closed. We resolved the incorrect engine tag in https://flutter-review.googlesource.com/c/recipes/+/41665


Test Writing

Need to create more tests for better coverage so we can improve their code coverage!

We added some e-mail addresses to the tests, so we got better coverage.


Chipper

I updated today, and ran "sudo ./chipper/start.sh"
This happened:
"# github.com/kercre123/chipper/pkg/wirepod/config-ws
pkg/wirepod/config-ws/webserver.go:328:2: syntax error: unexpected else, expecting }"
It won't run.

Same here

I fixed the issue. In webserver.go the DownloadVoskModel function should look like the following:
func DownloadVoskModel(language string) {
	filename := "vosk-model-small-"
	if language == "en-US" {
		filename = filename + "en-us-0.15.zip"
	} else if language == "it-IT" {
		filename = filename + "it-0.22.zip"
	} else if language == "es-ES" {
		filename = filename + "es-0.42.zip"
	} else if language == "fr-FR" {
		filename = filename + "fr-0.22.zip"
	} else if language == "de-DE" {
		filename = filename + "de-0.15.zip"
	} else if language == "pt-BR" {
		filename = filename + "pt-0.3.zip"
	} else {
		logger.Println("Language not valid? " + language)
		return
	}
	os.MkdirAll("../vosk", 0755)
	url := "https://alphacephei.com/vosk/models/" + filename
	filepath := os.TempDir() + "/" + filename
	destpath := "../vosk/models/" + language + "/"
	DownloadFile(url, filepath)
	UnzipFile(filepath, destpath)
	os.Rename(destpath+strings.TrimSuffix(filename, ".zip"), destpath+"model")
	vars.DownloadedVoskModels = append(vars.DownloadedVoskModels, language)
	DownloadStatus = "Reloading voice processor"
	vars.APIConfig.STT.Language = language
	vars.APIConfig.PastInitialSetup = true
	vars.WriteConfigToDisk()
	processreqs.ReloadVosk()
	logger.Println("Reloaded voice processor successfully")
	DownloadStatus = "success"
}

Was simply the else statement for if the "Language not valid?" not being formatted properly

Unfortunately, I can only open webserver.go as "read only".

May someone open up a pull request? I won't be at a computer for a while.

I never did a pull request. Wish I could help. Instead, I'll wait.

I got it

Thank you.

@mdinolfo123 the repo has just been updated. If the error goes away could you close the issue?

@SummerSigh When it gets to "wire-pod started successfully!" it's frozen, I think. No voice commands. I can access localhost:8080 and play with that just fine.
Do you have voice commands?

I haven't gotten bluetooth working 100% just yet

@SummerSigh When it gets to "wire-pod started successfully!" it's frozen, I think. No voice commands. I can access localhost:8080 and play with that just fine.
Do you have voice commands?

Could you close this and make a new issue then?


Color ESC sequences should be filtered out

The ESC sequences that set colors are recognized by the extension but these sequences are still displayed as characters, therefore making the output unreadable.
Example:
foobar

Is this intended? I'm inclined to classify this as a bug as I'd expect those sequences to not be shown any more in the editor.
Without these sequences been displayed this would be a fantastic extension!

There is currently no known way to hide the escape characters in the editor. Use the preview feature to see the colorized text without the escape characters.

:-(
Thank you for your response!


ProcessorError: Unsubstitutable key in template found: 'NAME'

Hi, I'm having an issue uploading a script using the jamf_upload.sh method. Any help is appreciated.
Thank you!
./jamf-upload.sh script -vvvv --url  --clientid --clientsecret  --name super-5.0.0 --script /Users/richard.adams/Downloads/super-5.0.0/super.sh
File Doesn't Exist, Will Create: /private/tmp/processor.plist
Initializing Plist...
[jamf-upload] Wrote RECIPE_DIR='.' into /tmp/processor.plist
[jamf-upload] Wrote verbose='4' into /tmp/processor.plist
[jamf-upload] Wrote JSS_URL=into /tmp/processor.plist
[jamf-upload] Wrote CLIENT_ID= into /tmp/processor.plist
[jamf-upload] Wrote CLIENT_SECRET= into /tmp/processor.plist
[jamf-upload] Wrote script_name='super-5.0.0' into /tmp/processor.plist
[jamf-upload] Wrote script_path='/Users/richard.adams/Downloads/super-5.0.0/super.sh' into /tmp/processor.plist
JamfScriptUploader: No value supplied for script_category, setting default value of:
JamfScriptUploader: No value supplied for script_priority, setting default value of: AFTER
JamfScriptUploader: No value supplied for osrequirements, setting default value of:
JamfScriptUploader: No value supplied for script_info, setting default value of:
JamfScriptUploader: No value supplied for script_notes, setting default value of:
JamfScriptUploader: No value supplied for script_parameter4, setting default value of:
JamfScriptUploader: No value supplied for script_parameter5, setting default value of:
JamfScriptUploader: No value supplied for script_parameter6, setting default value of:
JamfScriptUploader: No value supplied for script_parameter7, setting default value of:
JamfScriptUploader: No value supplied for script_parameter8, setting default value of:
JamfScriptUploader: No value supplied for script_parameter9, setting default value of:
JamfScriptUploader: No value supplied for script_parameter10, setting default value of:
JamfScriptUploader: No value supplied for script_parameter11, setting default value of:
JamfScriptUploader: No value supplied for skip_script_key_substitution, setting default value of: False
JamfScriptUploader: No value supplied for replace_script, setting default value of: False
JamfScriptUploader: No value supplied for sleep, setting default value of: 0
JamfScriptUploader: Checking for existing authentication token
JamfScriptUploader: No existing valid token found
JamfScriptUploader: Getting an authentication token using OAuth
JamfScriptUploader: Output file is:  /tmp/jamf_upload_8qcs13vi/jamf_upload_4j4t3d4v.txt
JamfScriptUploader: No existing cookie found - starting new session
JamfScriptUploader: curl command: /usr/bin/curl --location --dump-header /tmp/jamf_upload_8qcs13vi/curl_headers_from_jamf_upload.txt  --header User-Agent: JamfUploader/2<IP_ADDRESS> --request POST --silent --show-error --header Content-Type: application/x-www-form-urlencoded --output /tmp/jamf_upload_8qcs13vi/jamf_upload_4j4t3d4v.txt --cookie-jar /tmp/jamf_upload_8qcs13vi/curl_cookies_from_jamf_upload.txt --data-urlencode client_id= --data-urlencode grant_type=client_credentials --data-urlencode client_secret=
JamfScriptUploader: Session token received
JamfScriptUploader: Token:
JamfScriptUploader: Expires: 2024-10-25T00:20:10.246211Z
JamfScriptUploader: Checking for existing 'super-5.0.0' on
JamfScriptUploader: Full path: /Users/richard.adams/Downloads/super-5.0.0/super.sh
JamfScriptUploader: Output file is:  /tmp/jamf_upload_8qcs13vi/jamf_upload_8fcu7861.txt
JamfScriptUploader: curl command: /usr/bin/curl --location --dump-header /tmp/jamf_upload_8qcs13vi/curl_headers_from_jamf_upload.txt uapi/v1/scripts?page=0&page-size=1000&sort=id&filter=name%3D%3D%22super-5.0.0%22 --header User-Agent: JamfUploader/2<IP_ADDRESS> --request GET --silent --show-error --header authorization: Bearer '' --header Accept: application/json --output /tmp/jamf_upload_8qcs13vi/jamf_upload_8fcu7861.txt --cookie-jar /tmp/jamf_upload_8qcs13vi/curl_cookies_from_jamf_upload.txt --cookie /tmp/jamf_upload_8qcs13vi/curl_cookies_from_jamf_upload.txt
JamfScriptUploader: WARNING: 'NAME' has no replacement object!
ProcessorError: Unsubstitutable key in template found: 'NAME'

Without looking at the "super" script, I'm going to take a guess that it includes some lines with ampersands in them, specifically %NAME%. This is special syntax in JamfUploader that allows you to substitute values within scripts.
However, for scripts that don't need any substitutions, you can add the the option skip_script_key_substitution.

See https://github.com/grahampugh/jamf-upload/wiki/JamfUploader-Tips,-Tricks,-FAQs#how-do-i-handle-importing-a-script-that-genuinely-has-percent-signs-in-it for more details.


Logout Bug

If a player don't disconnect normaly, but disconnects by closing the window, the player don't leave the server, and others on the server and even the console are not able to kick this ghost player. Other players see the lefted player as a normal one who is not moving.
Also, the ghost player don't disconnects after an amount of time, he is forever online.
Video:
https://youtu.be/h88mpbLLYTw

Duplicate of #1895


UI scaling + Text color issues for layouts 2011-2008

This issue is easily reproducible, as it happens on both firefox-based and chromium-based browsers. It also happens from layouts 2011-2008 and all aspect ratios and resolutions.
On channel pages, the about section is offcenter and the dark blue borders do not line up with the grey border.

On the history page, the history settings will be hidden behind the sidebar.

Some text in other pages will blend in with the background and be unreadable.
I don't know how this hasn't been reported as an issue, or even fixed, as this literally can't be fixed just by uninstalling, resetting, or re-enabling the extension. This makes these layouts nearly unusable.

First issue is caused by your screen resolution being too small. CustomTube is mainly tested at a screen resolution of 1920x1080, but anything above 1366x768 should work. If your screen is smaller than that, you'll need to zoom out (I need to zoom in to 170% to get this to happen).
Second issue is also caused by your screen resolution, though the history page has issues no matter what resolution you use currently. I'm not sure when this will be fixed.

My resolution is 2160x1440, so I don't understand what you mean.

Well that is very strange, because when I zoom out to 67% (around 2560x1440), I get this:


Docker 1.12.0-rc3 - can't pull an image from ECR when creating a service.

Our nodes are on AWS EC2.
Steps to reproduce the issue:

$(aws ecr get-login --region us-east-1)
( I don't need to authenticate because I'm using an IAM profile on the node)
docker pull account_id.dkr.ecr.us-east-1.amazonaws.com/repo:version
When i try these 2 steps, it works and pulls the image from the relevant registry.
The problem appears when i try to create a service:
docker service create --name application --replicas 2 -p 31500:3000 account_id.dkr.ecr.us-east-1.amazonaws.com/repo:version

As you can see, i'm trying to create a service from the same image that "docker pull" command worked with. This doesn't work. The tasks constantly fail, and docker logs show the following errors:
msg="pulling image failed" error="unauthorized: authentication required" module=taskmanager task.id=blabla...
msg="fatal task error" error="No such image: account_id.dkr.ecr.us-east-1.amazonaws.com/repo:tag" module=taskmanager task.id=blabla...
msg="Attempting next endpoint for pull after error: Get https://account_id.dkr.ecr.us-east-1.amazonaws.com/v2/repo/manifests/tag: no basic auth credentials"
msg="Not continuing with pull after error: unauthorized: authentication required"

Describe the results you received:
The new service fails to pull the image from our private registry.
Describe the results you expected:
The new service would pull the image from our private registry and initialise properly.
Additional information you deem important (e.g. issue happens only occasionally):

I'm not sure how authentication is handled in ECR; we did merge a PR that is included in RC3 to pass authorization tokens when creating services (see https://github.com/docker/docker/pull/23584)
ping @samuelkarp @stevvooe perhaps you have ideas?

You need to include the --registry-auth flag when creating the service. That will grab the credentials from your client and propagate it with the service.

Oh, thanks, forgot we added a flag for that. I'll close this issue, but let us know if you're still running into this

@thaJeztah thanks for tagging me again!
Amazon ECR vends an authorization token to be used for pulls/pushes that is valid for up to 12 hours.  When you invoke aws ecr get-login it calls GetAuthorizationToken and returns a docker login command that can be run to provide the credentials to the Docker CLI.
I think @stevvooe's suggestion of using --registry-auth is fine, but if the image needs to be pulled again after the token expires it'll need to get new credentials.
@stevvooe, can the swarm use a credential helper?  I wrote one for ECR that could help here.  If that's not possible, Docker could directly call GetAuthorizationToken; both Amazon ECS and Kubernetes take this approach (see here and here respectively).

@samuelkarp thanks for looking; I think the feature implemented in https://github.com/docker/docker/pull/23584 is a first implementation to address the direct issue of deploying private images, but may need to be improved on in future iterations.

think @stevvooe's suggestion of using --registry-auth is fine, but if the image needs to be pulled again after the token expires it'll need to get new credentials.

Yes, that should probably work fine if the image is pulled triggered by a docker service update, but I see that may be an issue if images are pulled due to (e.g.) a node being down, and Swarm automatically starting new replicas.
Could you open a new issue with the information you provided above, so that we can use that for tracking? I don't think we have a tracking issue for those points yet.

@samuelkarp I had originally suggested we use the credential helper approach, across the board. Unfortunately, for most users, that would require running docker login on every single cluster node. There is also the problem that credential helpers are really a client-side feature, rather than something used from the server. We'd need to make sure that it works in that scenario.
AWS login implementation sounds a little unfortunate.
In the meantime, you'll have to update the auth token on the service whenever it expires. Something like this:
docker login <args from aws ecr get-login>
docker service update --registry-auth <the service>

Mind that this will trigger a rolling update, so its not ideal but it does ensure that new tasks will always have a valid token. Having that valid token will be critical if there are node failures that move replicas to nodes that have not yet pulled an image.
We will be looking deeper into this in 1.13, so please make sure to file an issue detailing this use case.

Can someone explain what the fix is for this issue when using ECR? Followed the AWS ECR tutorial to the letter, but blocked on the last step of uploading the image to the ECR registry because of:
error parsing HTTP 403 response body: invalid character 'Y' looking for beginning of value:  "Your Authorization Token has expired. Please run 'aws ecr get-login' to fetch a new one."

@jm3 the --registry-auth flag was renamed to --with-registry-auth in the actual release (it was named --registry-auth in the beta's

@thaJeztah i clearly don't understand docker at all:
docker service update --with-registry-auth https://123deadbeef.dkr.ecr.us-west-1.amazonaws.com
Error response from daemon: This node is not a swarm manager.
Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.

> docker --version
Docker version 1.12.1, build 6f9534c

@jm3 if you're not running in Swarm mode, then docker service commands don't apply to you. If you just want to "run" a container from an image (docker run foobar), then you don't need Swarm mode, and don't need the docker service commands.
"Swarm mode", and the docker service commands are for multi-host docker setups; read about it here: https://docs.docker.com/engine/swarm/, and https://docs.docker.com/engine/swarm/swarm-tutorial/

@thaJeztah ah, ok. i'm not really trying to use swarm mode, it just happened to be the error i get when i try to use the --with-registry-auth flag. I want to complete the 4 step AWS ECR tutorial, but docker throws that error above as shown in my comment.

@jm3 sorry, can't help you with that, I'm familiar enough with the AWS  ECR tools (possibly @samuelkarp has some hints)

@jm3 You can't use services without enabling swarm mode, so --with-registry-auth wouldn't be usable either. Once you've setup swarm mode, this should integrate with the AWS tutorial using docker login.

cool. i have no knowledge of swarm mode whatsoever, just trying to push
image to ECR :)
On Fri, Sep 16, 2016 at 2:28 PM, Stephen Day<EMAIL_ADDRESS>wrote:

@jm3 https://github.com/jm3 You can't use services without enabling
swarm mode, so --with-registry-auth wouldn't be usable either. Once
you've setup swarm mode, this should integrate with the AWS tutorial using docker
login.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/24372#issuecomment-247713138,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAvtQYluKd53RB3Y6j7TwPHGHFaRDn4ks5qqwnpgaJpZM4JGNjv
.

--
jm3 :: CTO + co-founder, 140 Proof
code.140proof.com

@jm3 Above, you said you were trying to use services. Rather than hijack this issue, I'd recommend opening on focused on your particular problem. Make sure to be clear about what you are trying to do.


MemGPT integration

does it make sense to have support for MemGPT, I was following a langchain (python) issue about adding this feature, but I didn't understand if it would be used with llms or memory

I was actually looking into this a few weeks ago, I think it makes sense... I need it for a project I'm working on. Will take a deeper look ;)


generate index.html for dev/build instead of separate files

using gulp

look into:
https://www.npmjs.com/package/gulp-replace
https://www.npmjs.com/package/gulp-inject


fixes filter pills no longer wrapping correctly #2155

Simple fix for #2155, which IMO is a fairly bad layout regression. Trivial review, hopefully we can get it in soon. FYI @ericpgreen2 @hamilton @djbarnwal

This seems to have messed up the grid layout. I'm seeing this big gap between line charts and leaderboards on each of my dashboards:

Hey @ericpgreen2 , I think that is the expected behavior
Here is what I see on main:

and on this branch:

same gap in both cases.


update packages

pin NUnit to ~> 2
fix generate.fsx

I have no time to fight with all these half backed packages issues.


/volvoAAOS2mqtt/mqtt.py:56: SyntaxWarning: invalid escape sequence '\d'

Describe the bug
Since version 1.9.0 or 1.9.1 (unsure which version), the new "create_otp_input()" contains a syntax error for new pattern argument.
At load time, log contain the following error message:
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/volvoAAOS2mqtt/mqtt.py:56: SyntaxWarning: invalid escape sequence '\d'
"pattern": "\d{6}",
May 27 20:33:21 volvo2mqtt [106] - INFO: Starting volvo2mqtt version v1.9.1
May 27 20:33:21 volvo2mqtt [106] - INFO: Starting login with OTP
It seems this also prevents to enter the OTP code after email with OTP code has been received from Volvo.
Version info:
Core                          2024.5.5
Supervisor                2024.05.1
Operating System    12.3
Frontend                   20240501.1
volvo2mqtt               1.9.1
Logs:
Enable the debug option and upload your logfile here.
May 27 20:36:48 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 7/24
May 27 20:36:53 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 8/24
May 27 20:36:58 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 9/24
May 27 20:37:03 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 10/24
May 27 20:37:08 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 11/24
May 27 20:37:13 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 12/24
May 27 20:37:18 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 13/24
May 27 20:37:23 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 14/24
May 27 20:37:28 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 15/24
May 27 20:37:33 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 16/24
May 27 20:37:38 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 17/24
May 27 20:37:43 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 18/24
May 27 20:37:48 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 19/24
May 27 20:37:53 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 20/24
May 27 20:37:58 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 21/24
May 27 20:38:03 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 22/24
May 27 20:38:08 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 23/24
Traceback (most recent call last):
File "/volvoAAOS2mqtt/main.py", line 15, in
authorize()
File "/volvoAAOS2mqtt/volvo.py", line 73, in authorize
response = send_otp(auth_session, response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/volvoAAOS2mqtt/volvo.py", line 157, in send_otp
raise Exception ("No OTP found, exting...")
Exception: No OTP found, exting...
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/volvoAAOS2mqtt/mqtt.py:56: SyntaxWarning: invalid escape sequence '\d'
"pattern": "\d{6}",
May 27 20:38:19 volvo2mqtt [106] - INFO: Starting volvo2mqtt version v1.9.1
May 27 20:38:19 volvo2mqtt [106] - INFO: Starting login with OTP
May 27 20:38:19 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 0/24
May 27 20:38:24 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 1/24
May 27 20:38:29 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 2/24
May 27 20:38:34 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 3/24
May 27 20:38:39 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 4/24
May 27 20:38:44 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 5/24
May 27 20:38:49 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 6/24
May 27 20:38:54 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 7/24
May 27 20:38:59 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 8/24
May 27 20:39:04 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 9/24
May 27 20:39:09 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 10/24
May 27 20:39:14 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 11/24
May 27 20:39:19 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 12/24
May 27 20:39:24 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 13/24
May 27 20:39:29 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 14/24
May 27 20:39:34 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 15/24
May 27 20:39:39 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 16/24
May 27 20:39:44 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 17/24
May 27 20:39:49 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 18/24
May 27 20:39:54 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 19/24
May 27 20:39:59 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 20/24
May 27 20:40:04 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 21/24
May 27 20:40:09 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 22/24
May 27 20:40:14 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 23/24
Traceback (most recent call last):
File "/volvoAAOS2mqtt/main.py", line 15, in
authorize()
File "/volvoAAOS2mqtt/volvo.py", line 73, in authorize
response = send_otp(auth_session, response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/volvoAAOS2mqtt/volvo.py", line 157, in send_otp
raise Exception ("No OTP found, exting...")
Exception: No OTP found, exting...
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
/volvoAAOS2mqtt/mqtt.py:56: SyntaxWarning: invalid escape sequence '\d'
"pattern": "\d{6}",
May 27 20:40:24 volvo2mqtt [106] - INFO: Starting volvo2mqtt version v1.9.1
May 27 20:40:24 volvo2mqtt [106] - INFO: Starting login with OTP
May 27 20:40:25 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 0/24
May 27 20:40:30 volvo2mqtt [106] - INFO: Waiting for otp code... Please check your mailbox and post your otp code to the following mqtt topic "volvoAAOS2mqtt/otp_code". Retry 1/24

This is only a warning.. should not be a problem.

Fixed with v1.9.2


Upgrade to Electron 7.0

Electron has shipped version 7.0, and support for Version 4.0 has ended. That means EOL for 5.0 is just around the corner.
Would be great if we could get the perf improvements of Microsoft's involvement with the Chromium project into our apps ASAP. Thanks!

Thank you for your donation!
At the moment I am sick. If I am well again on the weekend, I will take care of your wishes as soon as possible .. at the latest next week ..

No worries, please get some rest and feel better soon! :)

Implemented! Available in Electron.NET version 7.30.2.


Update Get-DtcClusterTMMapping.md

Issue - "fill in the blank" assignments - Description has been updated now.

Docs Build status updates of commit 53c9e14:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/msdtc/Get-DtcClusterTMMapping.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@dariomws306  @tseward
Peer review needed for this PR. Thanks.

Agree with @dariomws306, otherwise looks good.

Docs Build status updates of commit dc04d01:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012r2-ps/msdtc/Get-DtcClusterTMMapping.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@sowjanya365 @e0i Closing this PR; please PR against Master


There is no "install" command

There is no "install" command. The only commands are modify, update, repair, uninstall, and export. It appears that the "(blank)" command is for both "install" and "layout maintenance."
Please make install an alias of the (blank) command in both code and documentation. It might also be helpful to have an explicit "layout" command for cache layout maintenance.
Explicit is better than implicit.
(blank)     The default command both installs the product, and it is used for all layout maintenance operations.
modify      Modifies an installed product.
update      Updates an installed product.
repair      Repairs an installed product.
uninstall   Uninstalls an installed product.
export      Exports installation selection to an installation configuration file. Note: Can only be used with vs_installer.exe.
Bootstrapper commands and command-line parameters
Parameters Description
--installPath      For the default install command, this parameter is Optional and describes where the instance will be installed on the client machine. For other commands like update or modify, this parameter is Required and denotes the installation directory for the instance to act upon.

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

ID: 5e97b834-fa82-6aa0-5913-4d5a8ed23366
Version Independent ID: e988e3ea-8565-ca88-6ade-ab67425a51ae
Content: Use command-line parameters to install Visual Studio
Content Source: docs/install/use-command-line-parameters-to-install-visual-studio.md
Product: visual-studio-windows
Technology: vs-installation
GitHub Login: @j-martens
Microsoft Alias: jmartens

@Liturgist -- Paul, thank you for your considered feedback.  Please add this issue here:

Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.

@j-martens -- Josée, please look into this potential documentation issue.

We are happy to document once it has been added to the product.
@Liturgist, please share your product enhancement idea here:
Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.
#please-close as not a documentation issue.


Add platform detection crate

make hardware feature detection complete and use it instead of the config flags

Implemented in https://github.com/cryspen/libcrux/pull/51


AttributeError: 'MMDataParallel' object has no attribute 'reducer'

Thanks for your error report and we appreciate it a lot.
Checklist

I have searched related issues but cannot get the expected help.
I have read the FAQ documentation but cannot get the expected help.
The bug has not been fixed in the latest version.

Describe the bug
A clear and concise description of what the bug is.
Reproduction

What command or script did you run?

A placeholder for the command.

Did you make any modifications on the code or config? Did you understand what you have modified?
What dataset did you use?

Environment

Please run python mmgen/utils/collect_env.py to collect necessary environment information and paste it here.
You may add addition that may be helpful for locating the problem, such as

How you installed PyTorch [e.g., pip, conda, source]
Other environment variables that may be related (such as $PATH, $LD_LIBRARY_PATH, $PYTHONPATH, etc.)

Error traceback
If applicable, paste the error trackback here.
A placeholder for trackback.

Bug fix
If you have already identified the reason, you can provide the information here. If you are willing to create a PR to fix it, please also leave a comment here and that would be much appreciated!

Closing due to inactivity, please reopen if there are any further problems.


Fixed postProcessHtml option

Current usage of postProcessHtml option incorrectly assigns renderedRoutes.html to the output of this._options.postProcessHtml(). However, renderedRoutes is an array of route objects with both route and html properties, so the assignment of renderedRoutes.html doesn't make sense here. This proposed change allows users to pass a function as the postProcessHtml option in the webpack plugin. This function is responsible for processing the array of route objects and returning it as a similar array, processedRoutes, to be used in the next .then() statement on line 47.
As an afterthought, it may be better to use "processedRoutes" for the variable assignment inside the if statement on line 42 and return that variable on line 45 instead of mutating the "renderedRoutes" variable.

Good catch. I know postProcessHtml was working at one point, but I must've switched things around and made that mess. Thanks a ton!
I'm not available to test it at the moment, but I'll merge it in for now since I plan to do some major overhaul work before the next release.


Invariant Violation: requireNativeComponent: "RCTGCanvasView" was not found in the UIManager.

Do you follow the README.md as also described below?
Add below into /ios/Podfile
  pod "GCanvas", :path =><EMAIL_ADDRESS>
cd YOUR_PROJECT/ios
pod install

i have done this

and it is the same on android, i am testing it on both android and ios

I have fix it in https://github.com/flyskywhy/react-native-particles-bg/issues/2 with the related commit https://github.com/flyskywhy/react-native-particles-bg/commit/9eebd9100b1bccb0924a2dc420d4e262d6047588 said:
npm install @flyskywhy/react-native-gcanvas

And follow the steps to install @flyskywhy/react-native-gcanvas

i have this in my package and i have done it
i will do it again or can i share my package.js
i am using expo 41, with "react-native": "~0.63.4"

Bare react-native project can use this
npx react-native config

If @flyskywhy/react-native-gcanvas exist in packge.json, then in the output, if you can see @flyskywhy/react-native-gcanvas, then RCTGCanvasView will be auto linked in react-native building.
I don't know if expo project can do this. And why yours is package.js not package.json?

sorry that was a mistake, it is package.json

thank you, it is working fine now


Godepchecker

Added a checker to ensure s2i's godeps match origin's.  Currently, warnings are printed but do not cause make verify to bomb out.
Bumped two vendorings to match origin as well.
@soltysh

I was rather thinking about verifying the godeps if the are valid, and not if they are the same as in origin. Iow. if godep restore works cleanly without any errors.

lgtm
[merge]


Consider splitting 'Haplotype' into two subtypes

This is a proposal to consider splitting 'Haplotype' into two subtypes - one to represent the unlocated haplotype (which is a discontinuous set of alleles), and the other to represent the located version (which is a continuous extent of sequence that contains some variation as part).
This idea that a Haplotype can be these two very different things depending on whether a Location is provided seems to be a point of confusion for many. In my opinion explicitly separating these in different classes makes this distinction easier to explain and understand, and would allow more precise specification supporting haplotype creation in the schema.
We already do polymorphism so it can be implemented with no technical barriers.
Another proposed benefit is that this would make mapping to classes in variation-related ontologies possible (e.g. SO, GENO MSO).  Each of these ontologies make high level distinctions between sequences that are continuous features and things that are discontinuous sets, and thus they hold no classes that could map to the current VMC haplotype definition.  But if haplotype is split as proposed, then mappings could be made.   For example, the unlocated vmc haplotype would map directly to a GENO:haplotype (which it defines as a set of discontinuous alterations in cis), and the located vmc haplotype would map to a GENO:complex allele . . . as GENO, like the ClinVar allele model, distinguishes 'simple' alleles that vary along their entire extent, from 'complex' alleles that are defined extent's of sequence that contain variation(s) as a proper part).
The ability to map to ontology terms would let us point to an ontological-based, high-level, biologically-rooted, conceptual model of the VMC domain of discourse.  And perhaps more importantly,  it would make it easy for people to understand how vmc concepts are related to variation concepts in other models that are also mapped in GENO - as GENO would act as a Roseetta Stone allowing this translation. This would be a big win w.r.t. interoperability with models in other communities (e.g. model organism/AGR) who are at this time also working to define variation models to support their data, and considering use/alignment with GENO concepts.
@reece @larrybabb @ahwagner curious as to your thoughts here.

This is the correct conceptual design and the rationale is well stated and crystal clear. I like the approach.
I am still not super clear on how to weight the value proposition being made regarding the requirement to have a one to one mapping of classes to ontological concepts?
Here’s why the decision is challenging when it seems like a no brainer...
Finding the proper balance between adding new concepts/classes to a messaging model to more accurately reflect the reality of the data versus the trade off of denormalizing parts of the schema in order to simplify the learning curve of adoption is the key.
I’m very confident that we would produce a less adoptable schema if it directly  represented the real world nature of the data being shared and we must first be diligent to not model aspects and concerns that are far beyond the needs of the the community. I feel like we do pretty good here. Second, I think there is utility in demoralizing (i.e.rolling up subclasses or embedding a dependent but optional class).
In this specific case I see the merit in simplifying a set of subclasses into a single concept with one optional location attribute.
If one wanted to store the shared data from this schema into an RDF based repo to perform reasoning then it seems reasonable to think that consumer could split out and associate the natural representation quite easily. But for those that simply want to share haplotyp data. They will not want to necessarily learn about why there are multiple types as it will be likely that they will be dealing with either one or the other type for a given service. I’m sure I can think of several other small but notable reasons for how and why implementors might be burdened by the additional subclass game for merely a single attribute (location) including initial perception.
I recognize that implementors will still need to understand and deal with the 2 different concepts or uses of the Haplotype schema but I do think the flatter the schema is the simpler it will be perceived and the more likely we will gain interest from engineers looking to investigate and try low threshold alternatives and solutions.
I do think this reveals an important point that has been hanging over us since day 1. I think it is vital that we maintain an information model that does deviate from these type of denormalizations. We need this for several reasons least of which may be keeping us from not loosing track of the core info model from which we denormalize. All the way to helping with providing documentation to show where the message schema originates from and how that maps to the correct semantic terms.
We need to add this tool to our approach for building and sustaining our ability to continue to extend and modify the schema for the foreseeable future.
Allowing a place to demonstrate the proper semantic mappings to our schema for those tat need and want this is important and providing a simplified and reasonably denormalized schema will buy is much more users than otherwise.

Totally agree with Larry's comments, which I would summarize this way: Splitting might be a fine idea, but we should keep it simple for now. Let's defer this question to the next version.
IMO, we're missing several prerequisites for a meaningful discussion:

Motivation. Real-world use cases that demonstrate shortcomings of the current model to motivate the problem. By real-world, I mean a user story or similar that is missed or significantly impaired by the current Haplotype model.
Proposal. What should we do instead? What exactly is proposed?
Analysis. We need an analysis of implementing diverse haplotype use cases using the current and proposed models. Our goal is to solve many uses cases well and simply, and that might make particular uses harder. We must make the system better overall, not just better for a specific concern.

Let's pick this topic up again after we've executed our current plan and when we have sufficient motivation to address it.

Sounds like a plan guys, and thanks @larrybabb for the thoughtful analysis.  @rrfreimuth and I chatted the proposal at dinner the other night and will have some thoughts relevant to 'Analysis' when we revisit this question after the v1 release.

I agree with @mbrush re: the need for this change, and it is my opinion that our schema should reflect these two different concepts as separate types. In addition, I think we should construct formal representations of these concepts in our implementation to match the schema, but keep the documentation low-barrier (with an emphasis on ease of adoption for common variation types).
Also, I would like to add my voice to the above consensus on tabling this discussion until we get the v1.0 schema out the door.


GitLab's CI and --onefile option

I have a pipeline set at GitLab to build Linux and Windows binaries.
My .gitlab-ci.yml looks like this:
    image: docker:stable

    variables:
    BASE_IMAGE: cdrx/pyinstaller
    IMAGE_TAG: python3

    services:
    - docker:dind

    .build: &build
    script:
        - docker run --rm -v "$(pwd):/src/" ${BASE_IMAGE}-${TARGET_OS}:${IMAGE_TAG} "pyinstaller --onefile myScript.py"
    artifacts:
        paths:
        - dist/myScript.py/

    build-windows:
    <<: *build
    variables:
        TARGET_OS: windows

    build-linux:
    <<: *build
    variables:
        TARGET_OS: linux

However, after finishing the job it says that there are no files to upload:
 [....]
 6674 INFO: checking PYZ
 6675 INFO: Building PYZ because PYZ-00.toc is non existent
 6675 INFO: Building PYZ (ZlibArchive) /src/build/myScript/PYZ-00.pyz
 7185 INFO: Building PYZ (ZlibArchive) /src/build/myScript/PYZ-00.pyz completed successfully.
 7194 INFO: checking PKG
 7195 INFO: Building PKG because PKG-00.toc is non existent
 7195 INFO: Building PKG (CArchive) PKG-00.pkg
 17274 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
 17305 INFO: Bootloader /root/.pyenv/versions/3.7.5/lib/python3.7/site-packages/PyInstaller/bootloader/Linux-64bit/run
 17306 INFO: checking EXE
 17307 INFO: Building EXE because EXE-00.toc is non existent
 17307 INFO: Building EXE from EXE-00.toc
 17308 INFO: Appending archive to ELF section in EXE /src/dist/myScript
 17502 INFO: Building EXE from EXE-00.toc completed successfully.
Uploading artifacts...
 WARNING: dist/myScript.py/: no matching files
 ERROR: No files to upload
 Job succeeded

And if I simply remove that --onefile option, then everything works just fine, a whole bundle uploads (and works) OK.
What am I missing?


fix: Fix kubeletConfiguration.cpuCFSQuota and its defaulting

Fixes #
Description

Fix kubeletConfiguration.cpuFSQuota and its defaulting

How was this change tested?

make presubmit
Manual Testing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
71 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.1%) to 81.081%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/deprovisioning/helpers.go
2
83.04%

pkg/controllers/node/controller.go
7
73.53%

pkg/apis/v1alpha5/zz_generated.deepcopy.go
62
63.38%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
6660

Relevant Lines:
8214

💛  - Coveralls

This one is blocked while I'm still figuring out how to properly model a boolean with a default. Some ongoing discussion in the controller-runtime Slack


add taxon restrictions  L-dopa & orcinol  O-methyltransferase activity

To
Scizosaccharomyces
and
Saccharomyces (I think) @srengel ?
We are picking up a couple of mappings .
thanks
Val

I don't think L-dopa is part of normal biology of any fungi, as far as I can tell?

no we don't have this
http://amigo.geneontology.org/amigo/term/GO:0004510
and orcinol appears to be associated with lichens

Agreed.  It's not a normal part of fungal biology.  We don't have any annotations to any l-dopa terms.  The few papers about it in yeast discuss it as an externally-applied experimental insult, or using yeast as a factory to produce it: https://www.yeastgenome.org/search?q=L-dopa&category=reference
Totally fine with me to taxon-restrict these terms for fungi.

Oh yes I see only pombe has the mappings for a gene product conserved in human but absent from S. c.
http://preview.pombase.org/gene/SPBC119.03
http://preview.pombase.org/gene/SPBPB21E7.04c
So good to restrict, thanks

L-dopa O-methyltransferase and orcinol O-methyltransferase activities already have never_in Ascomycota restrictions. That should suffice shouldn't it?

Weird, I wonder why we are getting terms mapped via EC to GO, they should be blocked?

@cmungall could this be a problem with the taxon import? I don't see the full tree under Ascomycota when I load the editors' GO into Protege.

@cmungall and @ValWood , I don't think there is anything more to do here with respect to ontology development. Is this pipeline working now? It seems the restrictions are in place in the ontology.

Looking in the ontology, I see pombe is imported, so I am closing this one.

Actually, some Ascomyvota have enzymes that convert L-dopa into melanin. Cryptococcus, a Basidiomycetes, does this quite well. This taxon restriction would be best used for Sac and S. Pombe.
Diane


Map scale and virtualradar distance range [not a issue]

It is possible to add dependence between:
fDstU inside virtualradarserver query
and
scale (MAP_SCALE) inside mapquestapi query  ?
In this moment, when I extend range inside virtualradar query for eg. to 25km
map is still in smaller scale and do not show extended area.

Very good point. I actually have it almost working: everything should be dependent from the scale. The problem is that mapquest doesnt give me boundaries of the map and my calculations seem to be off...
Any idea how to calculate the boundaries?
Sent from my iPhone

On 5 Jan 2017, at 12:17, reaper7<EMAIL_ADDRESS>wrote:
It is possible to add dependence between:
fDstU inside virtualradarserver query
and
scale (MAP_SCALE) inside mapquestapi query ?
In this moment, when I extend range inside virtualradar query for eg. to 25km
map is still in smaller scale and do not show extended area.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


add support to structurizr

Add support to render Structurizr.
https://kroki.io/examples.html#structurizr-container

@b-bittner @oniboni @janLo

Hello @jairhenrique ,
thanks for your PR, I appreciate every help I can get, seems I've missed adding structurizr last year.


Fixes model kwargs argument passing

Fixes #1 where parameters have been passed via packing assigned.
Passing arguments via the model_kwargs works now.

If you want to do SemVer, patching bugs +0.0.1, adding features +0.1.0, and introducing breaking changes +1.0.0. So in theory, we could merge with the branch v0.0.2 and later merge that branch with main.


fix: isSameNodeType between Component and real DOM

This might be an solution of #260 fixing rendering Component with merge.
isSameNodeType in innerDiffNode (src/vdom/diff.js line 170) return false in this use case:

Before

Cmp

After

class Cmp extends Component {
  render() {
    return
Cmp
;
  }
}

class App extends Component {
  render() {
    return (

Before

      <Cmp />

After

);
  }
}
render(
  <App />,
  document.body,
  document.getElementById('my-app')
);

isSameNodeType between p#cmp and <Cmp> SHOULD be TRUE.

Or maybe we can generate a key to each Component automatically like react-id.

@csbun Hmm - it seems like this is already returning true for that case?
//
._componentConstructor === Cmp
// vnode.nodeName === Cmp
node._componentConstructor===vnode.nodeName

Pre-resolving during diff would be nice, but that would trigger mount events and all sorts of shenanigans.

It won't be true cause
 is rendered from server-side and
._componentConstructor should be undefined.

@csbun Let me know if this is solved in 6.0.0 - I've marked the other issue as closed, but want to make sure I've covered your usecase before closing this out.  Thanks for your hard work!!

Thanks! I'll try it in my new project these days.

Going to close this out since I'm fairly confident 6.0.1 being released fixes the issue. Let me know if I'm crazy!


Restructure the About section

The about section of the website hasn't been touched/updated in a very long time, it is now very outdated, I propose we keep it, but make the following changes.
I propose we REMOVE the following pages under about:

Community

I propose we REPLACE the Community page by CREATING the following new pages under about:

Kubeflow Slack: a page which describes (and provides an invite to) the official Kubeflow Slack
Kubeflow Mailing List: a page which describes (and links to) the kubeflow-dicsuss mailing list
Kubeflow Blog: a page which describes (and links to) the offical Kubeflow blog
Kubeflow Working Groups: a page which lists and describes the Kubeflow Working Groups

possibly links to the kubeflow/community pages
possibly include links to calendars for meetings

Google Summer of Code

this event has finished, and its confusing to keep this page, we should REMOVE it

Docs

this page does not provide useful information, we should REMOVE it

Style Guide for the Kubeflow Docs

the content of this file can be moved to the README of this repo (only docs contributors need to see it), then we can REMOVE it

Events Calendar

this page has not been updated in over a year, and therefore, I think we can REMOVE it

This would leave the following structure under about:
About:
- Introduction to Kubeflow
- Use Cases
- Contributing to Kubeflow
- Kubeflow Slack
- Kubeflow Mailing List
- Kubeflow Blog
- Kubeflow Working Groups

/priority p1

@RFMVasconcelos what are your thoughts?

Thank you for this @thesuperzapper! All the changes sound reasonable to me. If you are able to create a PR, I am more than happy to review :)


image_url support for vision models

What is the issue?
curl:
curl http://localhost:11434/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer OPENAI_API_KEY" \
  -d '{
    "model": "minicpm-v:8b-2.6-fp16",
    "messages": [
      {
        "role": "user",
        "content": [
          {
            "type": "text",
            "text": "What’s in this image?"
          },
          {
            "type": "image_url",
            "image_url": {
              "url": "http://images.cocodataset.org/val2017/000000039769.jpg"
            }
          }
        ]
      }
    ],
    "max_tokens": 300
  }'

response:
{
	"error": {
		"message": "invalid image input",
		"type": "invalid_request_error",
		"param": null,
		"code": null
	}
}

OS
macOS
GPU
Apple
CPU
Apple
Ollama version
0.3.10

You had just to read the docs about the openai compatibility click here to see it
The docs tell that for now that the openai compatibility doesn't handle the url image format. So until the ollama team had it, you will need to convert your image in base64 by yourself.Also, i recommend to use the regular api of ollama (the openai compatibility is experimenatl) if you can avoid the openai compatibility. This compatibility is make more for application that already exist with openai api and don't want to deal with ollama api. In the case of example an app that make able to use openai before Ollama exist, well now customer can use ollama even if the "team" who build the app change nothing.
Classic Ollama api here
There is a screenshot to you see what i mean quickly:

What is the issue?
curl:
curl http://localhost:11434/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer OPENAI_API_KEY" \
  -d '{
    "model": "minicpm-v:8b-2.6-fp16",
    "messages": [
      {
        "role": "user",
        "content": [
          {
            "type": "text",
            "text": "What’s in this image?"
          },
          {
            "type": "image_url",
            "image_url": {
              "url": "http://images.cocodataset.org/val2017/000000039769.jpg"
            }
          }
        ]
      }
    ],
    "max_tokens": 300
  }'

response:
{
	"error": {
		"message": "invalid image input",
		"type": "invalid_request_error",
		"param": null,
		"code": null
	}
}

OS
macOS
GPU
Apple
CPU
Apple
Ollama version
0.3.10

I admit that it would be great to be able to simply pipe URLs to the LLMs with any API.

I admit that it would be great to be able to simply pipe URLs to the LLMs with any API.

Technically, you can fetch the image from any API, transform it to the base64 and send it to Ollama. All you need to add to your app is a column in you DB that indicate if the source is an url or a machine image. I mean transforming an image to base64 doesn't change between the two type, juste indicating if it's an url to search the image from the web instead of local machine. If i succeed to transform uploaded user image on Electron with Ollama's API and that was not easy because of Electron, you can technically do that from scratch in your side.


Segfault when adding a module to itself

#[pymodule]
fn othermod(_py: Python<'_>, m: &PyModule) -> PyResult<()> {
    m.add_wrapped(pyo3::wrap_pymodule!(othermod))?;
}

>>> import othermod
[1]    15567 segmentation fault (core dumped)  ipython

Problem is not fixed through #1143 either

Importing the module causes recursion because PyInit for the module calls the function returning the module wrapper which in turn calls PyInit for its submodules.

Interesting find. If we wanted to fix this, I guess we could add a check for recursion in the module initialisation?
OTOH, this is a classic infinite recursion caused by malformed user code, there's probably endless ways users can write these and I don't believe any of them are unsound?

This could be fixed by changing add_submodule to take &PyModule instead of the wrapper. The recursion only happens because we're doing the full initialization dance for each submodule with the PyInit call.

impossible to accidentally add #[pyfunctions] with add_submodule (currently possible)
add_submodule becomes a lot more transparent.
If both submodule and toplevel should be instantiable, #[pymodule] can be placed on the submodule fn, otherwise it can just be a method modifying the passed module.

fn submodule(module: &PyModule) -> PyResult<()> {
    module.add("foo", "bar")
}

#[pymodule]
fn submodule_can_be_instantiated(_py: Python, module: &PyModule) -> PyResult<()> {
    module.add("foo", "bar")
}

#[pymodule]
fn module_with_functions(_py: Python<'_>, _mod: &PyModule) -> PyResult<()> {
    let submod = PyModule::new(_py, "submod")?;
    submodule(submod)?;
    _mod.add_submodule(&|py| submod.into_py(py))?;
    let submod = PyModule::new(_py, "another_module")?;
    submodule_can_be_instantiated(_py,submod)?;
    _mod.add_submodule(&|py| submod.into_py(py))?;
    Ok(())
}

Maybe we can take it a step further and provide PyModule::create to initialize a PyModule but I haven't figured out how to keep the PyModuleDef alive long enough.

Maybe as an alternative, we could work on the #[pymodule] syntax suggested in #694 ? I think that syntax would be awesome as it makes python modules more like Rust modules. And I guess we could design that syntax / implementation to make the infinite recursion impossible :)

Do you see any advantage of having add_module take a wrapper over taking &PyModule? That could be changed independently of the full module rework discussed in #694 and changed for #1143 since that introduces the add_module in the first place.

I guess the downside of add_module taking a module instead of a wrapper is that we have to teach a slightly different pattern in our documentation versus what currently exists. And it might be confusing to users whether they should put #[pymodule] on everything or not.
Also, it creates more work for users to migrate from add_wrapped to add_submodule if it's more than just a trivial rename.
But I don't feel too strongly. I'm just not sure whether it's worth fixing this edge case right now when maybe we can just keep it in mind for an upcoming (bigger) redesign?

Although it changes existing patterns, I think dumping the wrap_pymodule makes the API as a whole more transparent. Right now there is such a large amount of magic going on around #[pyfunction] wrap_pyfunction, add_wrapped, etc. that it's really hard to grasp.
I think it's pretty straight forward to say, if you want a submodule in your module:

Create your module: PyModule::new()
Add your members to the module
Add your module to the top level module.

Done!
It's clear where the module is created, it's straight forward what you're adding to it and it enables adding already existing modules, thus making the API more flexible. E.g. imagine this fn:
#[pyfunction(pass_module)]
fn add_some_module_to_slf(slf: &PyModule, other: &PyModule) {
    slf.add_submodule(other)
}

Of course it's also possible to go through slf.add(other.name()?, other), but that argument can be brought up against all add_X functions.

Also, it creates more work for users to migrate from add_wrapped to add_submodule if it's more than just a trivial rename.

I was hoping to get a stronger typed API, it's possible to add any PyObject to a module through add_submodule as long as it's generated from a &impl Fn(Python<'a>) -> PyObject.
The same holds for add_function but here we don't have a definition of a Rust type to rely on. That'd entail larger changes, which I'd also be in favour of. Have add_function take &PyFunction (iirc doesn't exist) and add_module take &PyModule.

👍 ok, you've convinced me 😅
One final question: should add_submodule take a &str and return the new &PyModule? That would mean no need to call PyModule::create first.

Maybe while what I propose is nice, it means submodules can't be imported directly? Not sure if that's an issue.

From my tests they all behave the same, but I haven't implemented the changes to add_submodule, I just faked it by using a closure &|py| submod.into_py(py) in place of wrap_pymodule!(). I'll implement the changes later and run unit tests to verify that everything still works the same.

Is this now to be closed with #1143 merged?

Yup, should be done!


Installation from repo head

May I ask you the reasons for 54ceb1290408b78b89f56b9812496f0b6cdfb81c ?

For me it's very important, because for example an issue of mine was fixed here https://github.com/makeworld-the-better-one/amfora/commit/5cb629f4c32c79b5544c572caf5796487bf03cf8 at the beginning of August but the next release came out almost a month after that. In the meantime I had to use the head build of my formula to be able to properly use the tabs feat.

It definitely is important. I removed it because I couldn't get the makefile to work correctly. The commit and version info in the binary would be completely blank:
$ amfora -v
Amfora
Commit:
Built by: official-brew-tap

I believe this is related to how homebrew clones git repos, but I'm not sure. Maybe it doesn't make the .git folder available to the script? I'd be happy to have solutions for this.

I have managed to create a formula that behave the way you want: having amfora -v to return
Amfora v1.5.0
Commit: 922e7981a92cb7bf0d7b3baf1694d0fffe90d448
Built by: official-brew-tap

when built normally and
Amfora v1.5.0-29-gfe0fd78
Commit: fe0fd784bb47ffe885c64baa91f18e50f3a54b96
Built by: official-brew-tap

when built from head. You can find the final formula here:
https://gist.github.com/Jackymancs4/83730fd42b96c9715ce1a09958a6d5f4
I honestly fail to get why make works the way it does, but I've very little experience about it.

Fixed by #6.


Test failure: CheckStdoutWithLargeWrites_LogFile

This issue was made automatically. If there is a problem contact ryanbrandenburg.
This test failed with the following error:
Assert.Equal() Failure
Expected: InternalServerError
Actual:   OK
   at Microsoft.AspNetCore.Server.IISIntegration.FunctionalTests.StartupExceptionTests.AssertFailsToStart(IISDeploymentResult deploymentResult) in /_/test/Common.FunctionalTests/Inprocess/StartupExceptionTests.cs:line 81
   at Microsoft.AspNetCore.Server.IISIntegration.FunctionalTests.StartupExceptionTests.CheckStdoutWithLargeWrites_LogFile(String mode) in /_/test/Common.FunctionalTests/Inprocess/StartupExceptionTests.cs:line 53
--- End of stack trace from previous location where exception was thrown ---
------- Stdout: -------
| [0.002s] TestLifetime Information: Starting test CheckStdoutWithLargeWrites_LogFile-CheckLargeStdErrWrites at 2018-11-06T10:08:55
| [0.002s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Information: Deploying [Variation] :: ServerType=IISExpress, Runtime=CoreClr, Arch=x64, BaseUrlHint=, Publish=True
| [0.003s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\runtimes\unix\lib\netcoreapp2.0
| [0.004s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying System.Security.Principal.Windows.dll
| [0.005s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\runtimes\unix\lib
| [0.005s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\runtimes\unix
| [0.006s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\runtimes\win\lib\netcoreapp2.0
| [0.006s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying System.Security.Principal.Windows.dll
| [0.008s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\runtimes\win\lib
| [0.008s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\runtimes\win
| [0.008s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\runtimes
| [0.008s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b\wwwroot
| [0.008s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying static.txt
| [0.009s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug: Processing C:\BuildAgent\temp\buildTmp\0d948f5887a144419108a381e1553b2b
| [0.009s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying aspnetcorev2_inprocess.dll
| [0.010s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying aspnetcorev2_inprocess.pdb
| [0.021s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying InProcessWebSite.deps.json
| [0.023s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying InProcessWebSite.dll
| [0.024s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying InProcessWebSite.exe
| [0.025s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying InProcessWebSite.pdb
| [0.027s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying InProcessWebSite.runtimeconfig.json
| [0.028s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Authentication.Abstractions.dll
| [0.029s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Authentication.Core.dll
| [0.030s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Connections.Abstractions.dll
| [0.033s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Hosting.Abstractions.dll
| [0.034s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Hosting.dll
| [0.034s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Hosting.Server.Abstractions.dll
| [0.036s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Http.Abstractions.dll
| [0.037s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Http.dll
| [0.041s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Http.Extensions.dll
| [0.044s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Http.Features.dll
| [0.045s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.ResponseCompression.dll
| [0.046s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Server.IIS.dll
| [0.047s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Server.IIS.pdb
| [0.048s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.Server.IIS.xml
| [0.049s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsoft.AspNetCore.WebUtilities.dll
| [0.050s] Microsoft.AspNetCore.Server.IntegrationTesting.IIS.IISExpressDeployer Debug:   Copying Microsof
...

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on master.
CC muratg

This comment was made automatically. If there is a problem contact ryanbrandenburg.
Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

Is this actually a flaky test?

No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
Yes, proceed below...

Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

[ ] File a bug against the product (TODO: Link to other bug)
Is it possible to change the test to avoid the flakiness?

Yes? Go to the "Change the test!" section.
No?

[ ] Disable the test (TODO: Link to PR/commit)
[ ] Wait for other bug to be resolved
[ ] Wait for us to get build that has the fix
[ ] Re-enable our test (TODO: Link to PR/commit)
[ ] Close this bug

Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

Is there is a way to change our test to avoid this flakiness?

Yes? Change the test!

[ ] Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
[ ] Run the test 100 times locally as a sanity check.
[ ] Close this bug

No?

Is there any logging or extra information that we could add to make this more diagnosable when it happens again?

Yes?

[ ] Add the logging (TODO: Link to PR/commit)

No?

[ ] Delete the test because flaky tests are not useful (TODO: Link to PR/commit)


Slurm migration

I've simplified the _wait_for_jobs function, fixed an issue with the for loop and removed some unnecessary sleeps.

You need to update ppc_cluster_submit


Development Fund Contract and Testing

Includes:

[x] Development Fund Contract
[x] Development Fund Testing

The code is good.
There are minor possibilities for gas optimization.
However, the contract's security depends heavily on the Governance. If the Governance becomes compromised, the developers' funds are gone.

governance decision are always scheduled on the timelock contract before execution. this gives the team multisig the chance to transfer the tokens to a previously defined safe vault before. because this vault is belonging to the governance as well, it's not completely rescuing the funds, but gives more time for solving the issue.


Can we have yaml marshalling directives as well as xml

All of the API related structs have excellent XML marshalling metadata directives attached, such as the following example:
type CreateServerRequest struct {
...
	AvoidHost  string `xml:"avoid_host,omitempty"`
	BootOrder  string `xml:"boot_order,omitempty"`
	CoreNumber int    `xml:"core_number,omitempty"`
...
}

Alternative encoding and decoding would be much simpler if the same metadata was provided for other marshalling/unmarshalling libraries such as json and yaml.
An example would be:
type CreateServerRequest struct {
...
	AvoidHost  string `xml:"avoid_host,omitempty" yaml:"AvoidHost,omitempty" json:"avoid_host,omitempty"`
	BootOrder  string `xml:"boot_order,omitempty" yaml:"BootOrder,omitempty" json:"boot_order,omitempty"`
	CoreNumber int    `xml:"core_number,omitempty" yaml:"CoreNumber,omitempty"  json:"core_number,omitempty"`
...
}

@Jalle19 mainly created this issue as a pointer for some colleagues, who told me that they were interested in contributing some effort.

@james-nesbitt I started out developing this SDK with the JSON API exclusively in mind. I had to start using XML instead though because the API returns a very weird JSON structure which is hard to serialize/deserialize nicely. Here's an example:
{
  "account": {
    "credits": "10000",
    "username": "username"
  }
}

This means you can't have an Account object, because that would be serialized to this:
{
  "credits": "10000",
  "username": "username"
}

I asked UpCloud about this and they said it was due to the API using XML behind the scenes, and the JSON serializer doesn't really cope with that. They said they would potentially improve the situation in the next major API version (no release date whatsoever for that though).
I'm assuming the same situation would apply to YAML.

Yeah there are a lot of artifacts of xml usage inside their API.
While I am not suggesting that we use XML for the API->UpCloud processes, I would like the metadata added so that the structs used for creating requests can come from YAML.
Currently I am using your API, but feeding in data from YAML files.   In order to get the yml to populate structs I have to duplicate your structs with metadata, and then use the duplicates to create your structs.  Adding the metadata wouldn't break any existing functionality.

BTW the example that you gave can have an ugly solution by using the JSON UnMarshaller interface, but it would require a lot of silly mapping.

Yes that's what I realized too while working on this. Do you think a YAML representation of structs will map correctly without custom marshaling logic? If so feel free to make a PR.
Generally I'm not very keen on adding YAML support since the API itself doesn't support it at all, but I guess it wouldn't hurt as long as it doesn't complicate things.

Right now I have servers starting and stopping using this approach:
https://github.com/james-nesbitt/kraut-project-template/blob/master/.kraut/upcloud.yml#L28
But I have to admit that I am having problems with the firewall rules (I keep getting response back saying that IPs and Ports are required.)
I think that the conversion code that I am using is not up to date in branch, but I will show you the effort that I have to go through to get YML converted to your structs.

You should add some debug print statements to the service class so you can see the XML that is generated for the request. You can also try the Postman collection that the SDK ships with too do further debugging if you're unsure what a request should look like.

sorry for delays here.  Holidays got in the way.  I will look at this again.

Thanks!

Hello again from 2020. One of the new updates to this API/SDK is using the JSON over XML. No yaml plans now nor in the future, so closing this issue. Please raise this issue again if there is still need for the support, so we can review the feature request again! :)


Add support for function instead of string in name/description field …

Description
Add support for function instead of string in schema object.
You can now use
let schema = {
        type: "object",
        properties: {
                name: {
                    type: "string",
                    minLength: 2,
                    title: () => $filter('translate')("Name"),
                    description: () => $filter('translate')("Description")
                },
                title: {
                    type: "string",
                    enum: ['dr','jr','sir','mrs','mr','NaN','dj']
                }
            };

Fixes Related issues
#754
Checklist

[x] I have read and understand the CONTRIBUTIONS.md file
[x] I have searched for and linked related issues
[ ] I have created test cases to ensure quick resolution of the PR is easier
[x] I am NOT targeting main branch
[x] I did NOT include the dist folder in my PR

@fookoo thanks for the PR, can you see a way we could apply the solution to the form instead of the schema? schema-form is a standard we do not control and can't really make changes to while remaining compliant.
I love the approach and can see the need for it, but to be accepted it needs to be applied via the form javascript instead which is optional also.

Closing due to lack of response, i18n has alternative suggestions for handling such as #865


Test issue

:tada: This issue has been resolved in version 5.2.1 :tada:
The release is available on:

GitHub Release
Chocolatey Package
.Net Global Tool

Your GitReleaseManager bot :package::rocket:


Add rudimentary CI

#2
#1  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aschepis and the rest of your teammates on  Graphite


Minimum height is too large in recent mobile browsers

When viewing the site with a recent mobile browser that has a retractable navigation bar, the minimum page height is too large and requires scrolling. This is because recent mobile browsers compute the CSS length 100vh as if their navigation bar would be hidden even though the bar is visible by default. This can be fixed by using a relative length unit based on viewport such as 100svh.

Fixed in v1.0.2.


VideoPlayerController / ChewieController called on Dispose ()

Hi there!
FluTube did a really good job where other plugins fails to do but I am having a strange issue and that is when ever I tries to change video URL Programmatically It shows error "VideoPlayer Controller called disposed".
Note: Error Disappears when I call setState on onVideoStart.
But this red error screen till video is loading is really annoying!

I will take a look on this. Thanks!

I will take a look on this. Thanks!

I fix it by modifying the source of FluTube!
Normally Example work perfectly but when we fetch youtube links from API then this error appears.
Moreover, sometimes this error got triggered due to Problem in VideoPlayer library so I have to write more code in FLuTube to handle these exceptions!

I think i'm not fully understanding you.
Which API are you talking about? This plugin does not use any APIs.
Also, what code did you add/modify to fix this problem?

I think i'm not fully understanding you.
Which API are you talking about? This plugin does not use any APIs.
Also, what code did you add/modify to fix this problem?
If you solved this issue yourself and you think your fix could help others, you can make a pull request and it will be welcome.

The problem is in videoPlayerController so in onWidgetUpdate you are disposing videoController and chewieController. so I just added:
if(videoPlayerController !=null || chewieController !=null)
{
videoPlayerController .dispose();
chewieController .dispose();
}
Moreover there are more issues in VideoPlayer library that is used by chewieController so to handle this add this code.
videoController.addListener(() {
if (videoController.value.hasError) {
//handle by yourself
}
});
OR
videoController.addListener(() {
if (videoController.value.hasError) widget.onVideoError();
//let User to handle by creating onVideoError Callback
});
Sometimes performing these fixes also through Red Screen so handle this:
chewieController.addListener(() {
if (chewieController.videoPlayerController.value.hasError)
widget.onVideoError();
});
I hope you get it!

Thanks for your contribution!
You could send a pull request to add those changes as i don't have much time to do it. I will try thought.
I like the idea of letting the user handle errors via a callback!

Hello,
In the last commit i tried to apply what you said but i think it is not working.
Could you please review the changes and tell me what is wrong? Or better just send a pull request?
Thank you

Yeah, that's correct I review it and that's the same way I am doing!

Youtube does not allow to access copyright videos so as for your permission can I do changes in your plugin so it can fetch those videos and play in player!

So did your issue got fixed?
Did you try the example app? I added a button to change video url but it is showing red screen when video gets changed, and also the onVideoError callback doesn't seem to be working for me.
Sure you can!

Roll back your commit as Error is in videoPlayer controller, and will be fixed soon according to them.

I have reviewed the example code, unfortunately, onVideoError is not working there. You should do roll back as it is not working.

Rollback done. Thanks!


Implement cache for types of 'load'ed identifiers

DataObject.load() requests the rdf:type triples for each identifier from GraphObjectQuerier(). We should be able to get better performance by skipping the disk accesses entailed by getting those triples.

Did this in the pow-store-zodb (formerly rdflib-zodb). Actually, the rdf:type triples are indexed differently from other triples rather than being cached, but the effect is improved response time for BaseDataObject::load.


use is-number-object

use is-number-object for more robustness

Why are you closing this PR?

It's clear these are all bad faith trolling PRs, and "TODO" isn't an invitation for a contribution anyways - it's not time to make these changes yet.

oh, i misunderstood