Roll Plugins from ace9e78bd3c3 to 8a95012fb037 (1 revision)

https://github.com/flutter/plugins/compare/ace9e78bd3c3...8a95012fb037
2021-11-13<EMAIL_ADDRESS>[path_provider] Publish fully federated version (flutter/plugins#4497)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-plugins-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Never-ending tasks stop showing up after a while: Message too big

What crate(s) in this repo are involved in the problem?
tokio-console, console-subscriber
What is the issue?
My application has some tasks that are always running, so they never get completed. I'm using tokio-console so I can debug my process at any time, but I'm facing a huge issue here. After a while, these tasks stop showing up on tokio-console, and I get the following error in my log file: ERROR Message too big. Start with smaller retention. min_retention=1s.
As far as I know, retention should only affect how long completed tasks are held in memory, at least that's what the documentation says. Also, I'm using a custom retention of 60 seconds, but these tasks keep showing up in tokio-console for much longer (about 1 hour or maybe a bit less), so there doesn't seem to be a correlation.
Am I missing something here? Is this a limitation of the crate or am I doing something wrong?
Thank you!
How can the bug be reproduced?

Setup tokio-console in your project.
Spawn some never-ending tasks using tokio::spawn.
Launch the process and wait for about 1h.
Connect to the tokio-console server, the tasks won't show up and an error will be logged.

Logs, error output, etc
ERROR Message too big. Start with smaller retention. min_retention=1s
Versions
│   ├── console-subscriber v0.4.0
│   │   ├── console-api v0.8.0
│   ├── console-subscriber v0.4.0 (*)
tokio-console 0.1.12
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
yes

Looking at the code, it seems like the console-subscriber starts reducing the retention when the message it has to send to tokio-console is too big. Since retention doesn't affect uncompleted tasks, which in this case are the ones responsible for exceeding the maximum message size, so the retention gets reduced to its minimum and the message with the task's information is never sent.
I don't think reducing the retention forcefully is the right way to reduce message sizes, especially since it isn't communicated to the user at any point, so you might end up with a lower retention that you set up without knowing it.
Could message size be reduced in any other way? Splitting it up and making multiple sends sounds like the most straightforward solution, but I'm not an expert on this crate so I have no idea of its limitations and whether that's feasible to implement within the current codebase.

@sergioabreu-g Thanks for you report!
Given the error message you've received, I think that you're hitting the second case where nothing will be sent at all because console-subscriber has already tried to reduce the retention below the minimum (which is the publishing interval).
I actually wonder whether any of this works properly at all, since cleaning up closed items depends on them not being dirty, but if those objects haven't been sent to any client then they're all dirty and so maybe nothing is being cleaned up at all...
Certainly, a mechanism that chunks the initial state so that it can be sent bit by bit to the client would be a more robust and generally better solution.
I'd be more than happy to provide guidance.
We would have to create a better message builder. One that somehow takes the maximum size into account. The current message construction happens here (for the initial state update):
https://github.com/tokio-rs/console/blob/main/console-subscriber/src/aggregator/mod.rs#L288-L296
It adds everything.
I see 2 possible strategies:

Fill up with objects of a specific type until the limit and send that (including some new flag that this is a partial update). The order in the code would likely make sense: tasks, resources, async ops.
Send all object tyoes up to a certain point in time, then send the next chunk of time, and so on. Again, with some partial update flag.

In either case, we would need to modify tokio console to understand that it doesn't yet have a full state and so it should probably not display anything yet.
Finally, we'd want to try and detect a pathelogical case where updates are coming in faster than they can be sent, and so the client (tokio console) will never get a full state update. In this case, sending some signal to tokio console that it may never get up to date might provide a better user experience than we currently have.


Update tapir-core, tapir-http4s-server, ... to 0.19.0-M8

Updates

com.softwaremill.sttp.tapir:tapir-core
com.softwaremill.sttp.tapir:tapir-http4s-server
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-openapi-circe-yaml
com.softwaremill.sttp.tapir:tapir-openapi-docs
com.softwaremill.sttp.tapir:tapir-refined
com.softwaremill.sttp.tapir:tapir-swagger-ui

from 0.19.0-M7 to 0.19.0-M8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

labels: library-update, semver-pre-release

Codecov Report

Merging #177 (716ac0d) into develop (dba66e3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #177   +/-   ##
========================================
  Coverage    50.58%   50.58%
========================================
  Files            5        5
  Lines           85       85
========================================
  Hits            43       43
  Misses          42       42

Continue to review full report at Codecov.

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


Steam Account Log in for OSRS?

Hi Everyone,
I haven't played OSRS for sometime and just wanted a fresh start, so as of them putting OSRS on steam directly. I just have been logging in through my steam account to play OSRS. And today I made runelite the primary client for when I launch the game through steam but every time I do that it won't just log in through my steam it asks me for an email and password. If I try using my steam email and password it doesn't recognize it. I was wondering if there is a way to connect my new steam account to a new runescape one under the same email. Or what the best course of action is for logging into runelite as I am very eager to using runelite.
Thank You

https://support.runescape.com/hc/en-gb/articles/360013472137-Add-a-login-email-to-a-Steam-created-account


fix broken images

hidden images for now. TODO: find out package that has broken it and roll back to stable release + change dependabot schedule to every 2 weejs

Rolled back prod to release from 12 days ago until issue is fixed


dropdown_widget: Show disabled if value not in options.

It is possible that the current value of a dropdown widget is valid but not present in options since the current user doesn't have access it. So, we show [disabled] as value in that case.
This can be reproduced by setting a private stream for notifications in org settings and then opening org settings as a user which doesn't have access to the private stream.
discussion: https://chat.zulip.org/#narrow/stream/9-issues/topic/organisation.20settings.20dropdown.20widgets.20not.20initializing

This is great, merged, thanks @amanagr!


ideviceInstaller error on Mac with Genium-Framework Api usage

Using methods as:
          ServerArguments serverArguments = new ServerArguments();
    serverArguments.setArgument("--address", "<IP_ADDRESS>");
    serverArguments.setArgument("--no-reset", true);
    serverArguments.setArgument("--local-timezone", true);
    serverArguments.setArgument("--port", "4723");
    serverArguments.setArgument("--session-override", true);
    serverArguments.setArgument("--log", properties.get("appiumLogs"));
    AppiumServer _appiumServer = new AppiumServer(serverArguments);
    _appiumServer.startServer();

Works fine for Windows machine, but for Mac, its giving error as below. Howerver if Appium GUI
is started manually i.e. without API usage than tests run fine.
Appium v: 1.4.13
Mac: 0.10.5
2016-01-20 10:39:21:571 - info: Welcome to Appium v1.4.13 (REV c75d8adcb66a75818a542fe1891a34260c21f76a)
2016-01-20 10:39:21:574 - info: Appium REST http interface listener started on <IP_ADDRESS>:4723
2016-01-20 10:39:21:577 - info: [debug] Non-default server args: {"address":"<IP_ADDRESS>","sessionOverride":true,"noReset":true,"log":"/Users/intelligrape/appiumLogs.log","localTimezone":true}
2016-01-20 10:39:21:577 - info: Console LogLevel: debug
2016-01-20 10:39:21:577 - info: File LogLevel: debug
2016-01-20 10:39:22:338 - info: --> GET /wd/hub/status {}
2016-01-20 10:39:22:340 - info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.13","revision":"c75d8adcb66a75818a542fe1891a34260c21f76a"}}}
2016-01-20 10:39:22:350 - info: <-- GET /wd/hub/status 200 6.830 ms - 105 {"status":0,"value":{"build":{"version":"1.4.13","revision":"c75d8adcb66a75818a542fe1891a34260c21f76a"}}}
2016-01-20 10:39:23:185 - info: --> POST /wd/hub/session {"desiredCapabilities":{"platformVersion":"8.1.3","app":"/Users/intelligrape/Mobility_QA/app/American-Swan.ipa","platformName":"iOS","deviceName":"TTND iPhone5c 1","browserName":"iOS","--log":"/Users/intelligrape/appiumLogs.log","udid":"adff85c69b6404975219f5518d32571545c7b421","takesScreenshot":"true","noReset":true}}
2016-01-20 10:39:23:185 - info: Client User-Agent string: Apache-HttpClient/4.3.3 (java 1.5)
2016-01-20 10:39:23:186 - warn: Converting cap takesScreenshot from string to boolean. This might cause unexpected behavior.
2016-01-20 10:39:23:187 - info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : --log, takesScreenshot
2016-01-20 10:39:23:189 - info: [debug] Using local .ipa from desired caps: /Users/intelligrape/Mobility_QA/app/American-Swan.ipa
2016-01-20 10:39:23:189 - info: [debug] Copying local zip to tmp dir
2016-01-20 10:39:23:402 - info: [debug] /Users/intelligrape/Mobility_QA/app/American-Swan.ipa copied to /var/folders/x0/sdy7g6b57pqf9pwll9zmq7vr0000gn/T/116020-1962-1cnj9tj/appium-app.zip
2016-01-20 10:39:23:535 - info: [debug] Unzipping /var/folders/x0/sdy7g6b57pqf9pwll9zmq7vr0000gn/T/116020-1962-1cnj9tj/appium-app.zip
2016-01-20 10:39:23:535 - info: [debug] Testing zip archive: /var/folders/x0/sdy7g6b57pqf9pwll9zmq7vr0000gn/T/116020-1962-1cnj9tj/appium-app.zip
2016-01-20 10:39:23:945 - info: [debug] Zip archive tested clean
2016-01-20 10:39:24:482 - info: [debug] Unzip successful
2016-01-20 10:39:24:483 - info: [debug] Using locally extracted app: /var/folders/x0/sdy7g6b57pqf9pwll9zmq7vr0000gn/T/116020-1962-1cnj9tj/Payload/American-Swan.app
2016-01-20 10:39:24:483 - info: [debug] Creating new appium session 6708fa84-72ec-41c2-955d-e3f22ebd77b9
2016-01-20 10:39:24:485 - info: [debug] Removing any remaining instruments sockets
2016-01-20 10:39:24:486 - info: [debug] Cleaned up instruments socket /tmp/instruments_sock
2016-01-20 10:39:24:486 - info: [debug] Auto-detecting iOS udid...
2016-01-20 10:39:24:486 - info: [debug] Not auto-detecting udid, running on sim
2016-01-20 10:39:24:487 - info: [debug] Could not parse plist file (as binary) at /var/folders/x0/sdy7g6b57pqf9pwll9zmq7vr0000gn/T/116020-1962-1cnj9tj/Payload/American-Swan.app/en.lproj/Localizable.strings
2016-01-20 10:39:24:487 - info: Will try to parse the plist file as XML
2016-01-20 10:39:24:488 - info: [debug] Could not parse plist file (as XML) at /var/folders/x0/sdy7g6b57pqf9pwll9zmq7vr0000gn/T/116020-1962-1cnj9tj/Payload/American-Swan.app/en.lproj/Localizable.strings
2016-01-20 10:39:24:488 - warn: Could not parse app Localizable.strings assuming it doesn't exist
2016-01-20 10:39:24:488 - info: [debug] Getting bundle ID from app
2016-01-20 10:39:24:492 - info: [debug] Parsed app Info.plist (as binary)
2016-01-20 10:39:24:492 - info: [debug] Creating instruments
2016-01-20 10:39:24:493 - info: [debug] Preparing uiauto bootstrap
2016-01-20 10:39:24:493 - info: [debug] Dynamic bootstrap dir: /Users/intelligrape/Library/Application Support/appium/bootstrap
2016-01-20 10:39:24:493 - info: [debug] Dynamic env: {"nodePath":"/Applications/Appium.app/Contents/Resources/node/bin/node","commandProxyClientPath":"/Applications/Appium.app/Contents/Resources/node_modules/appium/submodules/appium-uiauto/bin/command-proxy-client.js","instrumentsSock":"/tmp/instruments_sock","interKeyDelay":null,"justLoopInfinitely":false,"autoAcceptAlerts":false,"autoDismissAlerts":false,"sendKeyStrategy":"grouped"}
2016-01-20 10:39:24:501 - info: [debug] Dynamic bootstrap code: // This file is automatically generated. Do not manually modify!
...
2016-01-20 10:39:24:501 - info: [debug] Dynamic bootstrap path: /Users/intelligrape/Library/Application Support/appium/bootstrap/bootstrap-5923cadea0343e3f.js
2016-01-20 10:39:24:504 - info: [debug] Reusing dynamic bootstrap: /Users/intelligrape/Library/Application Support/appium/bootstrap/bootstrap-5923cadea0343e3f.js
2016-01-20 10:39:24:507 - info: [debug] Attempting iOS device log capture via libimobiledevice idevicesyslog
2016-01-20 10:39:24:508 - warn: Could not capture device log using libimobiledevice idevicesyslog. Libimobiledevice probably isn't installed
2016-01-20 10:39:24:508 - info: [debug] Attempting iOS device log capture via deviceconsole
2016-01-20 10:39:34:513 - error: Log capture did not start in a reasonable amount of time
2016-01-20 10:39:34:514 - warn: Could not capture logs from device. Continuing without capturing logs.
2016-01-20 10:39:34:514 - info: [debug] Creating iDevice object with udid adff85c69b6404975219f5518d32571545c7b421
2016-01-20 10:39:34:515 - info: [debug] Couldn't find ideviceinstaller, trying built-in at /Applications/Appium.app/Contents/Resources/node_modules/appium/build/libimobiledevice-macosx/ideviceinstaller
2016-01-20 10:39:34:515 - error: Could not initialize ideviceinstaller; make sure it is installed and works on your system
2016-01-20 10:39:34:516 - info: [debug] Cleaning up appium session
2016-01-20 10:39:34:516 - error: Failed to start an Appium session, err was: Error: Could not initialize ideviceinstaller; make sure it is installed and works on your system
2016-01-20 10:39:34:520 - info: [debug] Error: Could not initialize ideviceinstaller; make sure it is installed and works on your system
at [object Object].IOS.getIDeviceObj (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/ios.js:909:13)
at [object Object].IOS.installToRealDevice (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/ios.js:856:32)
at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:607:21
at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:246:17
at iterate (/Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:146:13)
at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:157:25
at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:248:21
at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/async/lib/async.js:612:34
at [object Object]. (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/ios.js:1552:14)
at /Applications/Appium.app/Contents/Resources/node_modules/appium/node_modules/underscore/underscore.js:890:21
at [object Object]._onTimeout (/Applications/Appium.app/Contents/Resources/node_modules/appium/lib/devices/ios/ios-log.js:166:7)
at Timer.listOnTimeout (timers.js:119:15)
2016-01-20 10:39:34:521 - info: [debug] Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Could not initialize ideviceinstaller; make sure it is installed and works on your system)","origValue":"Could not initialize ideviceinstaller; make sure it is installed and works on your system"},"sessionId":null}
2016-01-20 10:39:34:523 - info: <-- POST /wd/hub/session 500 11338.296 ms - 300
2016-01-20 10:39:43:332 - info: --> GET /wd/hub/status {}
2016-01-20 10:39:43:333 - info: [debug] Responding to client with success: {"status":0,"value":{"build":{"version":"1.4.13","revision":"c75d8adcb66a75818a542fe1891a34260c21f76a"}}}

This is an old defect report, I am gonna close it. Please update to the latest version of Appium server and let me know if the problem still persists.


"ValueError: numpy.dtype has the wrong size, try recompiling"

The full stack trace:
  File "run_algo.py", line 17, in <module>
    from zipline.utils import parse_args, run_pipeline
  File "/Library/Python/2.7/site-packages/zipline/__init__.py", line 25, in <module>
    from . import data
  File "/Library/Python/2.7/site-packages/zipline/data/__init__.py", line 1, in <module>
    from . import loader
  File "/Library/Python/2.7/site-packages/zipline/data/loader.py", line 25, in <module>
    import pandas as pd
  File "/Library/Python/2.7/site-packages/pandas/__init__.py", line 7, in <module>
    from pandas import hashtable, tslib, lib
  File "pandas/src/numpy.pxd", line 157, in init pandas.hashtable (pandas/hashtable.c:23654)
ValueError: numpy.dtype has the wrong size, try recompiling

I uninstalled and reinstalled numpy(through pip), but it didn't help.
Is there anything else I am missing ?
The tutorial also doesn't mention that before running "python run_algo.py -f dual_moving_average.py --symbols AAPL --start 2011-1-1 --end 2012-1-1 -o dma.pickle" I should move to a directory where run_algo.py and dual_moving_average.py are present

Hi Ishan,
That error is telling you that you need to recompile pandas, not numpy.  Pandas uses numpy's headers to access their C API, so if you install numpy, then install pandas (using the currently-installed numpy headers), then upgrade numpy, pandas may no longer function properly.  Can you try running pip install --upgrade pandas?

Didn't make much difference . Tried the following
sudo pip uninstall numpy
sudo pip uninstall pandas
sudo pip install --upgrade pandas
sudo python run_algo.py -f dual_moving_average.py --symbols AAPL --start 2011-1-1 --end 2012-1-1 -o dma.pickle

If you just open a Python shell and do import pandas, what happens?  Also, it looks like you're running from the system Python on OSX?  You might want to consider running from inside a virtualenv.

In [3]: import pandas
ValueError                                Traceback (most recent call last)
 in ()
----> 1 import pandas
/Library/Python/2.7/site-packages/pandas/init.py in ()
5
6 try:
----> 7     from pandas import hashtable, tslib, lib
8 except ImportError as e:  # pragma: no cover
9     module = str(e).lstrip('cannot import name ')  # hack but overkill to use re
pandas/src/numpy.pxd in init pandas.tslib (pandas/tslib.c:73721)()
ValueError: numpy.dtype has the wrong size, try recompiling

This worked (ref: http://stackoverflow.com/questions/17709641/valueerror-numpy-dtype-has-the-wrong-size-try-recompiling):
sudo pip uninstall pandas
sudo pip uninstall numpy
sudo easy_install --upgrade numpy
sudo pip install pandas

ok.  For what it's worth, using sudo with pip and working in the system python is generally considered bad practice (largely for reasons like what you're experiencing).  I'd highly recommend using virtualenv or something like it (e.g. conda envs).

@ishandutta2007 after 30 minutes of trying everything else on OSX Yosemite for Python 2.7, your solution worked! Thanks!

Also this error happened for me when I was trying to import nltk package!

Uanble to uninstall the numpy. But upgrading the numpy  worked for me 👍
sudo easy_install --upgrade numpy


Add ability to get ITestContext from ITestResult

I needed to have the ability to get the test context from a test result in one of my ITestListener listeners. There didn't seem to be a reliable way to do that so I added the ability to get the test context from the test result. Would love to see this added, for now I will have to use my own build.

Note that I renamed getContext() to getTestContext() for consistency.
Thanks for the patch!


Move getSdkIdentifiers handling in Core

Currently in 1.0.0 the event for getSdkIdentifiers is handled by AEPIdentity, we would need this API to be handled at the Core level so that the Identity implementation can be detached from the other solution extensions.
The discussed solution is to have a simple core extension that retrieves the various shared states as needed and return them back to the getSdkIdentifiers API.

@shalehaha this is no longer a requirement for the Edge implementation, but you may still want to move it to core as not all identifiers are owned by the Identity extension.


Arguments passed to script aren't ignored anymore

I see this, it looks good ... let me test it and think about it; just to be conservative here.
Thanks for your work!

Seems to be ok, but it just "looks" dangerous ... but if all hell breaks loose we'll fix it. So be it. Here you go.


[Bug] Votes scraper not pulling in most recent vote, until I cleared cache

Hi!
I had an up-to-date cache of 116th congress 2020 session votes as of Sunday June 7. 2020.
ran
./run votes --congress=116 --session=2020
this morning (Tuesday June 9) and it was missing a senate vote on June 8th.
The vote was present in the xml file when I called the script.
Once I cleared the votes cache, it pulled correctly.
If this is a bug, I'll go ahead and try to fix this.
Thanks!

I haven't had a problem. It could be a bug, but it might have just been some sort of fluke.

I just experienced the same issue for the current congress and year (117, 2022)


change language to python 3.6 only

Coverage remained the same at 85.519% when pulling d498a3e0a90511a10f9df2a03543a460b5607394 on reset_password into 13b1be81324dacd30a43111208570f0cdcedc7c0 on master.


Feat: streaming functions

This adds the initial implementation of streaming responses of functions aka the stream pseudo-type.
It's a pseudo to type because while it looks like any regular type: stream<t> the only valid position where it may appear is as the sole return type of a function like so
interface streams {
   func streaming_bytes() -> stream<list<u8>>
}

(This restriction might be gradually lifted at some point)
The primary motivation for this new addition is to model sequences of asynchronously produced data such as events, log streams, or just streaming bytes from e.g. the disk.
With this addition the tauri-bindgen system can finally replace the current IPC system as this allows us to model events (in an IMO type-safer and more ergonomically way)
Details
The generated guest rust code look like this:
pub async fn streaming_bytes() -> ::tauri_bindgen_guest_rust::Streaming<Vec<u8>>;

where ::tauri_bindgen_guest_rust::Streaming<T> takes care of the underlying raw http stream and deserialisation of the incoming data. It in turn implements Stream<Item = T>.
It's worth noting that currently the implementation relies on ReadableStreams returned by fetch, and so performs no additional buffering (everything follows the rust pull-based model here which is nice).
Streaming<T> doesn't implement framing yet though it probably should.
The generated host code looks like this:
pub trait Streams: Sized {
    type StreamingBytesStream: ::tauri_bindgen_host::Stream<Item = Vec<u8>>
        + Send
        + 'static;
    ///A function that returns a stream of strings
    fn streaming_bytes(&self) -> Self::StreamingBytesStream;
}

So an implementation would need to give a specific type for StreamingBytesStream (most likely some wrapper type)
struct Ctx {
   // a list of handles so we can send events to all open channels
   // this emulates a broadcast channel
   txs: Arc<Mutex<Vec<mpsc::Sender<Bytes>>>>
}

impl Streams for Ctx {
   type StreamingBytesStream = tokio_stream::wrappers::ReceiverStream<Bytes>;

   fn streaming_bytes(&self) -> Self::StreamingBytesStream {
      let (tx, rx) = mpsc::channel(250);

      // this can of course be refactored to not require locking
      let txs = self.txs.lock().unwrap();
      txs.push(tx);

      Self::StreamingBytesStream::new(rx)
   }
}

The above example also showcases how a similar DX to the classical tauri events can be achieved, by essentially passing around mpsc::Sender handles.

Note
This PR is currently blocked by the fact that wry's event handler doesn't allow for streaming responses back to the webview tauri-apps/wry#1022

TODO list

[ ] Host implementation
[ ] Guest JS implementation
[ ] Guest TS implementation
[x] Guest Rust implementation
[ ] Markdown implementation

This closes #180

I love this!
Since stream can only appear in the output of the function, how is the guest supposed to mimic the event emitter pattern the host has?


[INFRA] Set ctest env vars

Artifacts available for download:

Artifact Name
Download Link

clang.versions
https://github.com/seqan/actions/actions/runs/11721508320/artifacts/2157099119

gcc.versions
https://github.com/seqan/actions/actions/runs/11721508320/artifacts/2157095741

intel.versions
https://github.com/seqan/actions/actions/runs/11721508320/artifacts/2157095300


Scrub Sandcastle examples

Current examples:

[x] Remove Animations?
[x] Improve UI for Billboards, Labels, and Camera?
[x] Remove Black Marble.
[x] Cesium Inspector shouldn’t have a Tutorials tag.
[x] Remove jQuery UI Demo?
[ ] Keep Materials since they are covered elsewhere?
[x] Remove Minimalist.
[x] Picking: Remove Fade Sensor on Click and Layer Primitives.
[ ] What to do with Polygons, Polylines, and Volumes?
[x] Use viewer widget for Two Canvases or remove it.
[x] Resnap all out of date gallery images.

Need new examples for:

[x] GeoJSON/TopoJSON
[x] More CZML examples? CC #1649
[ ] Customizing the standard widgets?
[ ] More advanced ones as time allows: custom geometry, appearances, data sources, widgets, etc.
[x] Camera - ICRF

Other

[x] #1747 - implicitly define Cesium in all examples

Example improvements are ongoing.


Roadmap: add file upload feature to 1.0

Hi all,
As suggested here:

Shouldn't the file upload features be considered part of the 1.0 Apollo Client release? I think the method proposed by @HriBB is a great starting point.

The proposed "method" is exemplified in these packages: graphql-server-express-upload and apollo-upload-network-interface.
Handling the data flow with the Apollo stack feels very natural. Most apps will require some form of file uploading on top of Apollo's data flow handling.
For my projects, it was the first and foremost reason to apply a custom redux implementation aside Apollo's. All other project requirements could be handled with Apollo - which is great! Because file uploading is flowing data as well, it however feels very unnatural to have to handle the upload "manually", outside Apollo. When integrating with the UI, things get complicated fast.
So I think there's a clear use case for file uploading with Apollo. Besides that, @HriBB has showed it can be done with the Apollo stack.
Therefore i.m.h.o., the Apollo stack 1.0 release cannot not be complete without file uploading functionality.
Kind regards,
Sander van Hooft

Can you elaborate on your use case? Is it that you want to fetch data about the new file after upload?

Good morning @stubailo ,
Ofcourse. I hope the following use case clarifies how much simpler Apollo could make file uploading.
User wants to add an offer to a market place using a form:

User enters title, price, availability, description
User adds pictures
User saves the offer
User sees offer detail page, including images

If using Apollo as primary transport, after some client-side validation multiple calls need to be made to the backend:

Image upload to REST endpoint, returns image urls
Graphql mutation with offer title, price, availability, description, image urls
Some way to roll back if one of the above fails
Due to the multi-request nature of this solution, it is over-complex, fragile and error-prone.

If using a REST endpoint as primary transport for uploads, and use Apollo for the other transports:

Single POST request to REST endpoint with formdata including all info and the images
Retrieve the details page info with Apollo & Update the Apollo store's offer list query
It seems inconsistent to bypass Apollo like this for such a common task in an app architected around Apollo. It also requires a specific REST endpoint for this task alone.

Preferably, the offer creation including images can be done with a single Apollo-roundtrip:

Graphql mutation with offer title, price, availability, description, image files.

This way, there's only a single request to validate and respond to. Plus a lot of code/complexity can be factored out from the client. Both the front-end team and back-end team will be happy with this simplicity.
Kind regards,
Sander

I think that file upload should be handled using external modules/packages. Many apps might use CDN for storing files, and in that case, GraphQL server should have no awareness of file uploading whatsoever.

@HriBB I agree that Apollo should be storage agnostic. It should focus on what it does best: simple data transport using Graphql.
My plea is to include file uploads in these transport features.

Addendum: the storage specifics (CDN etc) can then be handled at either the client or the server, depending on the project requirements.

Having file uploads would be lovely! I was just wondering how to upload form data with a picture through a mutation.

@savovs file upload is already possible. Take a look at https://github.com/HriBB/apollo-upload-network-interface and https://github.com/HriBB/graphql-server-express-upload

@stubailo do you guys have a concrete plan for how this should work. We are about to implement mutation based file upload for graph.cool and want to align closely with Apollo.

I have the same problem.

@sorenbs We haven't really had to deal with file upload, so we haven't thought about it too much. It looks like there is enough interest in this topic that we might pick it up soon, though.

@helfer That's excellent news! Anything we can do to help move this forward? It seems like @HriBB has done an excellent job exploring a concrete implementation already.

The method proposed by @HriBB is great, however you are missing some features like Multer validation rules. In this example made by @HriBB, Multer is used one time like Express middleware before calling GraphQL.
IMO, is better use Multer inside each GraphQL resolve function. If you use this way, you will be able to setup different validation rules for each resource.
I am trying to figure out this, but I need some help. See this issue for more information.

That's a great point @jferrettiboke Do you think this is something that it would make sense to tackle during the Apollo Contributor Week? https://dev-blog.apollodata.com/save-the-date-apollo-contributor-week-eef66d09f0e6#.pj0yj67qu

Hi @sorenbs.
Yes. I think so. There are different use cases where developers have to validate the files before upload them (extension and size) depending of the resource (user photos, user videos, etc).
If developers use only one endpoint which accepts any file, they could not write specific validation rules for each files as I said.
Anyone could help on the issue I mentioned to bring another approach to the table?

@thebigredgeek I think you should tune in here with the file upload solution you were working on!

Well, I am not working on it yet haha.  Was waiting until we had a spec for the network interface we were discussing on slack.  I figured we were going to bundle file upload handling into the new interface?

Closing this for now. We can continue the discussion on apollographql/apollo.


feat(sqsLambda): make functionResponseTypes configurable

Goal
Make functionResponseTypes configurable. Can use it to report individual failures when processing batches from e.g. SQS.
Reference
Documentation here:

Terraform docs
AWS Docs

:tada: This PR is included in version 3.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Discuss API Design

Problem description
Potentially Device Swap API could provided 2 distinct information:

Request last Device Swap date (When was the last device swap for the mobile line identified by the phone number +123456799?)
Check last Device swap by providing a delay (Does we had a device swap for the last 240 hours for the mobile line identified by the phone number +123456799?)

In order to move forward on the API design we should discuss on following questions

Are we sharing same expectations of the API?
Are we considering this information as independent one from the other ? We can have different privacy requirement, different way to commercialize it. Technical implementation feasibility should be considered.
How multi-SIM can affect this design?

Possible evolution

Alternative solution

Additional context

Are we sharing same expectations of the API?

Totally aligned on this perspective.

Are we considering this information as independent one from the other ? We can have different privacy requirement, different way to commercialize it. Technical implementation feasibility should be considered.

For aligning as much as posible with Sim Swap, I'd tend to think that same kind of information is shared (date) and only difference may appear based on the age of the info that can be provided. If both endpoints consider the same kind of data age limitation (maxAge maximum value equal to the retrieve date maximum age), both endpoints should be considered as common and it will mostly be up to the developer to choose the best mechanism for retrieving the information.

How multi-SIM can affect this design?

When a multi-SIM subscription is in place, more than one IMEI is associated to the same MSISDN. It is, depending on which device is active/connected, the record of IMEI associated tot he MSISDN will change time to time, sometimes more than one time per day/hour. Therefore, the device swap events will be triggered continuously and no valid information will be provided, since the event only represents that the user is activating one of his already existing devices.
Proposal is to only consider new devices as a valid device swap event, e.g. establishing a margin of 1 or several months in which a device can be used in the same MSISDN without considering it a device Swap event, as no valuable information for the API consumers.

For Multi-SIM please provide comment on the discussion #10

Hello @krishvenkatachalam
May I ask you to provide feedback on the topic from MTN.
We should close on the topic of one or 2 yaml.
Thanks
cc: @wwAMRA

Hello @krishvenkatachalam , @wwAMRA
Any update?


Legion: Expose task provenance in mapper

It would be useful if we could access provenance for task launches in the mapper. It does not appear to available here: https://gitlab.com/StanfordLegion/legion/-/blob/master/runtime/legion.h#L4138

Isn't this what you want?
https://gitlab.com/StanfordLegion/legion/-/blob/master/runtime/legion.h#L4081-4085


extend documentation to mention '{recursive_cmds, []}' as config option

Commands like 'eunit' or 'clean' don't act recursive anymore since the built-in recursive_cmds doesn't include these. Please mention the '-r' option somewhere and also how to readd those commands to rebar.config by using the recursive_cmds option in order to retain the old behaviour for example.

Fixed in #432.


Unable to subscribe app to heroku page

My issue is with setting up the app page.
When I try to setup the webhook url, it doesn't work.
More specifically, when I used create heroku to create my heroku app the following text appeared
"Creating app... done, ancient-lake-88699
https://ancient-lake-88699.herokuapp.com/ | https://git.heroku.com/ancient-lake-88699.git"
So I assume that my CallBack URL should be "https://ancient-lake-88699.herokuapp.com/" or "https://ancient-lake-88699.herokuapp.com/webhook/"
I tried both but I kept getting the error message "The URL couldn't be validated. Callback verification failed with the following errors: HTTP Status Code = 503; HTTP Message = Service Unavailable"
It's bizarre because I went to my heroku dashboard and I can see a tab for "ancient-lake-88699" so I don't understand why this error is happening.
HELP ME! please...
I attached images of my command prompt and heroku dashboard.

When I try to load up the heroku link it shows the app is broken. Can you paste in what the heroku logs say?

Sure no problem. I tried to open my application and it said the same thing. so I went to view logs on heroku and copyed the text. I hope this help cause im still lost :(

I'm having the same issue... was any conclusion made on how to solve this problem?

Remove all app.get and app.post except root path
app.get('/', function (req, res) {
	res.send('hello world i am a secret bot')
})

it should be ok, if not pls check on heroku

I did this but its still not working for me

@shurm and @Marisha-Sahay I faced this same issue and here is what I did to solve it.
When I tried to run it locally using node index.js it gave me an error saying:
const express = require('express');
SyntaxError: Use of const in strict mode.

So I replaced all const in the code with var
After tha,t I ran it again locally and it gave an error saying: Cannot find module 'request', so I did
npm install request --save
After this, I ran it locally and it gave the message "Hello world, I am a chat bot". I deployed it to Heroku and ran it from there again and it gave the same message. So now the app is working on Heroku. I did the Facebook webhook setup again and it worked.

Hi what URL are you using? You should add /webhook/ to your FB URL

@neeraj87 I am getting the same problem. my code is running good and I am getting output in local port but when deployed to heroku, I am getting the error message(check the image). Is there something we need to change in the script before deploying it to Heroku? I have no prior knowledge to Heroku cloud.

@codename-47 few ways to debug.

Have you included the procfile?
install heroku toolbelt on your machine and print out logs: heroku logs --app appname

@neeraj87 Thanks. yes, I have included the procfile. However when I am using heroku logs --app appname, heroku is not recognising the app. (chatbot is my app name). Any comments on that?

On your app's dashboard in heroku, there is a More button near Open App which has View Logs option. Open your app, when it shows the application error then go back and View logs, it will show you the logs on heroku.
Regarding the screenshot above, have you first logged in heroku toolbelt from terminal? Also, are you the primary owner of the app or a collaborator?

@neeraj87 What connection string are you providing in the code? I have hardcoded it to my local machine port 5000. That might be the problem?

@neeraj87 @Marisha-Sahay  @shurm  it worked!!! We need to provide start script to "start": "node index.js" in package.json file. Thanks for all the help.

@codename-47 glad you got it figured out.

Okay so, since I am having the exact same problem, here is what I have to show for now:
Error Received:
The URL couldn't be validated. Callback verification failed with the following errors: HTTP Status Code = 503; HTTP Message = Service Unavailable
Did definitely use:
.../webhook/
The package.json is also configured:


Caddyfile not loaded in one of latest updates

After the (for me) last update I couldn´t reach my Home Assistant sitting behind the reverse proxy of this proxy addon anymore. Took me quite some time to realise what was going on and then how to resolve it.
Behore I had my Caddyfile /config/caddy/Caddyfile and it worked like a charm. I gather it know has to be in /addon_configs/c80c7555_caddy-2 . Did I miss some warning about this change? And might it be possible to move the config automatically?
Hopefully this issue at least helps some people who are searching why their Caddy setup broke out of nowhere. :)
And to be clear, I am still very happy and thankful that you package Caddy for us as an addon, it is a great tool to use!

This change was listed in the release notes with instructions to move custom caddyfiles to the new directory.

It’s not so celar how to access to the new folder. Could someone explain how to do it?
thanks

@trickinit Ok so it is a issue of HA OS installing major versions automatically. I have to find out how to prevent that, without getting bothered by all the minor updates.
@Lukeslowly you can access it via ssh or smb sharing (the last one depending how it is setup). It is one level up from the config directory, which is a little inconvenient as the standard file browser and vscode add-on by default restricted to the config folder.

I have exactly the same problem.
Where exactly should the new folder "/addon_configs/c80c7555_caddy-2" be created, under or above the /config folder?
If I revert to version 1.5.3 everything works fine.
The Caddy2 log still gives me this:
s6-rc: info: service legacy-services successfully started
INFO: Prepare Caddy...
INFO: Checking path: /config/caddy
INFO: Use built-in Caddy v2.8.4 h1:q3pe0wpBj1OcHFZ3n/1nl4V4bxBrYoSoab7rL9BMYNk=
INFO: Prepare Caddyfile...
**INFO: No Caddyfile found**
INFO: Use non_caddyfile_config
INFO: Run Caddy...
{"level":"info","ts":1727343226.047366,"msg":"using config from file","file":"/etc/caddy/Caddyfile"}.

This is my Caddy2 configuration:
non_caddyfile_config:
  email<EMAIL_ADDRESS>  domain: xxxx.duckdns.org:9000
  destination: localhost
  port: 8123
args:
  - "--watch"
env_vars: []
log_level: info
config_path: /addon_configs/c80c7555_caddy-2/Caddyfile.

Thanks for any response.

@cmussoni I don't believe you have to create the folder. Updating Caddy2 should have already done so. The /addon_configs folder should be in the root of your Home Assistant installation, so up a level from the /config folder you've been using.

@cmussoni You have to modify the setting of the file editor adding installed in your HA.
Go in file editor configuration page then disabling enforce basepath.
Restart the addon, then you were able to go up one level in file editor addon and finally you will be able to access to the caddy 2 folder where you can place the config file.
Honestly speaking the installation instruction of caddy 2 addon it’s not so clear….

@trickinit @Lukeslowly
Perfect, so I finally solved it.
It wasn't that clear to me.
Thank you very much.

🤙😎


Nova services adoption (no extra cell, no ffu)

Extracted nova services adoption w/o FFU being done from https://github.com/openstack-k8s-operators/data-plane-adoption/pull/176
Note about remapping cell DB names from OSP cells naming scheme
to the NG scheme with the superconductor layout.
Add a step to rename default cell as cell1, and to delete stale
Nova services records from cell1 DB during initial databases import,
to properly transition it into a superconductor layout later on.
Adjust minor gaps in the Placement adoption docs
Address the switch for service overrides spec instead of
externalEndpoints, where it is missing on the path to Nova adotpion.
Remove Nova Metadata secret creation workarounds from the EDPM
adotopion docs and test suits.
Provide workaround for renaming 'default' cell's DB during adoption.
Add test suits for Nova CP services adoption.
Add missing nova and libvirt services for the edpm adoption tests.
Add nova extra config custom service to complete pre-FFU deployment.
Use nova-extra-config service instead of the nova service,
because by today design choices, each config change requires a new
service deployed with ansible EDPM framework.
Document/automate creating a Nova migration key-pair requiremed
for EDPM deploy.
Stop Nova services in stop_openstack_services instead of edpm_adoption
(that was too late to do that).
Jira: OSPRH-338

@jistr @gibi it fails as there is no https://github.com/openstack-k8s-operators/nova-operator/pull/566 in the CI builds. I'm hitting on my dev env this for the same reason. How could we improve the delivery of fixes into builds?..

this passes testing on my dev env, if I manually patch CSVs of nova and openstack operators to latest tags. We really need to fix CI...

The CI job failed as the cell0 conductor was not able to talk to keystone.
2023-11-08 18:26:12.128 1 ERROR nova keystoneauth1.exceptions.http.Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-af061dbb-93a9-41e6-b5ca-4f3aaf248003)

https://review.rdoproject.org/zuul/build/c1d1eed1ce8b411e9a3975de4b6c4dd0/log/controller/pod/nova-cell0-conductor-0-logs.txt

The CI job failed as the cell0 conductor was not able to talk to keystone.
2023-11-08 18:26:12.128 1 ERROR nova keystoneauth1.exceptions.http.Unauthorized: The request you have made requires authentication. (HTTP 401) (Request-ID: req-af061dbb-93a9-41e6-b5ca-4f3aaf248003)

https://review.rdoproject.org/zuul/build/c1d1eed1ce8b411e9a3975de4b6c4dd0/log/controller/pod/nova-cell0-conductor-0-logs.txt

this is really weird, I was hitting exactly the same issue on my env, until I retried it from scratch, after make crc_storage_cleanup crc_storate.

recheck

recheck

@gibizer @jistr this passes now. Although on my env I'm hitting ovn adoption problems with
"ovsdb-client: failed to connect to \"tcp:<IP_ADDRESS>:6641\" (Connection refused)"]

if it works for you, please consider merging

TASK [osp.edpm.edpm_nova : Copy the migration ssh public key as authorized_keys to the nova user] ***
Wednesday 15 November 2023  14:48:56 +0000 (0:00:00.750)       0:00:24.214 ****
fatal: [standalone]: FAILED! => {"changed": false, "msg": "Source /var/lib/openstack/config/nova/ssh-publickey not found"}

https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/f64c83e/controller/pod/nova.compute.extraconfig-openstack-8vq6r-logs.txt

TASK [osp.edpm.edpm_nova : Copy the migration ssh public key as authorized_keys to the nova user] ***
Wednesday 15 November 2023  14:48:56 +0000 (0:00:00.750)       0:00:24.214 ****
�[0;31mfatal: [standalone]: FAILED! => {"changed": false, "msg": "Source /var/lib/openstack/config/nova/ssh-publickey not found"}�[0m

https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/f64c83e/controller/pod/nova.compute.extraconfig-openstack-8vq6r-logs.txt

Strange. We have the secret generated at https://github.com/openstack-k8s-operators/data-plane-adoption/pull/191/files#diff-0d721d5c31018c7d1dff0df6f5732b2d29a0cd1e814a5af5ce80d2d6c23c80d3R118 and that is included in the DataPlaneService at https://github.com/openstack-k8s-operators/data-plane-adoption/pull/191/files#diff-0d721d5c31018c7d1dff0df6f5732b2d29a0cd1e814a5af5ce80d2d6c23c80d3R153 and we using that server at https://github.com/openstack-k8s-operators/data-plane-adoption/pull/191/files#diff-0d721d5c31018c7d1dff0df6f5732b2d29a0cd1e814a5af5ce80d2d6c23c80d3R178

recheck

it will fail again, see @gibizer comments above

recheck

@jistr I couldn't get the CI failure cause https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/cc30154/controller/pod/dataplane-operator-controller-manager-569f9b45d-5qt4d-describe.txt
shall we just increase timeout? it takes more than 40m it seems?

@jistr I couldn't get the CI failure cause https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/cc30154/controller/pod/dataplane-operator-controller-manager-569f9b45d-5qt4d-describe.txt
shall we just increase timeout? it takes more than 40m it seems?

it is not a timeout issue,
it is a failure with the secret:
TASK [osp.edpm.edpm_nova : Copy the migration ssh public key as authorized_keys to the nova user] ***
Thursday 16 November 2023  18:56:20 +0000 (0:00:00.842)       0:00:25.837 *****
fatal: [standalone]: FAILED! => {"changed": false, "msg": "Source /var/lib/openstack/config/nova/ssh-publickey not found"}

https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/cc30154/controller/pod/nova.compute.extraconfig-openstack-tj68g-logs.txt
see: https://github.com/openstack-k8s-operators/data-plane-adoption/pull/191#discussion_r1394453454

@jistr I couldn't get the CI failure cause https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/cc30154/controller/pod/dataplane-operator-controller-manager-569f9b45d-5qt4d-describe.txt
shall we just increase timeout? it takes more than 40m it seems?

it is not a timeout issue,
it is a failure with the secret:
TASK [osp.edpm.edpm_nova : Copy the migration ssh public key as authorized_keys to the nova user] ***
Thursday 16 November 2023  18:56:20 +0000 (0:00:00.842)       0:00:25.837 *****
fatal: [standalone]: FAILED! => {"changed": false, "msg": "Source /var/lib/openstack/config/nova/ssh-publickey not found"}

https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/cc30154/controller/pod/nova.compute.extraconfig-openstack-tj68g-logs.txt
see: https://github.com/openstack-k8s-operators/data-plane-adoption/pull/191#discussion_r1394453454

@jistr I couldn't get the CI failure cause https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/cc30154/controller/pod/dataplane-operator-controller-manager-569f9b45d-5qt4d-describe.txt
shall we just increase timeout? it takes more than 40m it seems?

it is not a timeout issue, it is a failure with the secret:
TASK [osp.edpm.edpm_nova : Copy the migration ssh public key as authorized_keys to the nova user] ***
Thursday 16 November 2023  18:56:20 +0000 (0:00:00.842)       0:00:25.837 *****
�[0;31mfatal: [standalone]: FAILED! => {"changed": false, "msg": "Source /var/lib/openstack/config/nova/ssh-publickey not found"}�[0m

https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/cc30154/controller/pod/nova.compute.extraconfig-openstack-tj68g-logs.txt
see: #191 (comment)

thanks, I've read it back now :)
related question do you  think that deployment should fail, not timeout in such cases? looks like another related bug discovered (aside of my typo)

good point, we should make the deployment fail on these cases

I notice the ansible gets stuck on the task error:
https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/f64c83e/controller/pod/nova.compute.extraconfig-openstack-8vq6r-logs.txt
as the playbook doesn't finish to run, the AEE job keeps JobStatus as Running:
https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/f64c83e/controller/crs/openstackansibleees.yaml
and that's why the deployment doesn't get updated:
https://logserver.rdoproject.org/91/191/a5672bf71cfdb47b751a8752410fa0d0b5fe38b6/github-check/data-plane-adoption-github-rdo-centos-9-extracted-crc/f64c83e/controller/crs/openstackdataplanedeployments.yaml
So I'm trying: https://github.com/openstack-k8s-operators/data-plane-adoption/pull/201
to see if it unstucks ansible


Error message on unqualified blocks

Here is the message:
EdgeQLSyntaxError: only fully-qualified name is allowed in top-level declaration
### CREATE MIGRATION main TO {
###     type User {
###          ^

It's quite unclear. Especially when upgrading an app. Should probably suggest adding a module block instead of kinda subtly hinting about adding a namespace prefix.

Keeping this one open to make sure the new flow addresses this error better.


Cranelift: Failure to write PLT bytes when creating many modules

Minimal example
https://gist.github.com/PROMETHIA-27/7ac3d63e82610a220048442886cbebe5
Steps to Reproduce
Run this example (with dependencies cranelift_codegen, cranelift_jit, cranelift_module) and after ~30,000 iterations it should crash.
Expected Results
The example completes after 50,000 iterations and nothing notable happens.
Actual Results
it fails with the following error:
`thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: TryFromIntError(())', C:\Users\elect\.cargo\registry\src\index.crates.io-6f17d22bba15001f\cranelift-jit-0.97.1\src\backend.rs:299:82`

Versions and Environment
Cranelift version or commit: Latest commit as of now as well as 0.97.1
Operating system: Windows x64
Architecture: x86_64
Extra Info
I encountered this while attempting to exclude the cost of dropping modules from a benchmark that runs roughly 50,000 times. I hope it doesn't affect anything more important but I suspect that it's UB. When I insert a print statement into the panicking function to print what - at every call, it consistently reports values around -2^16 and does not panic. When I insert a print statement that only activates when the try_into fails, it reports something closer to +/-4 billion and panics at roughly ~30,000 iterations.

Duplicate of https://github.com/bytecodealliance/wasmtime/issues/4000


"Error: EMFILE: too many open files... " when deploying Nuxt 3 app with Phosphor Icons to Netlify

🐛 The bug
When I deploy my Nuxt 3 app which uses the @phosphor-icons/vue package to Netlify, the deployment is successful but when I visit the site, initially, I get an error:

After some time, when I revisit the site, I get this error:

It works okay in development and I've also tried building the app locally, Nuxt uses the "node-server" option and that works fine.
🛠 To reproduce
https://stackblitz.com/edit/nuxt-starter-tfqdxc?file=app.vue
🌈 Expected behaviour
The Icons should be displayed in production when deployed to Netlify and not crash the entire app.
ℹ Additional context
No response

Sorry for getting back to you so late, aparrently I wasn't automatically set as an assignee.
This error is interesting, I wouldn't know why netlify runs out of file descriptors. After all this library is really just a accumulation of pre-compiled components.
Does your repro represent your project exactly or is it just a placeholder-repro for us to test against?
Seems that you haven't really installed any packages in your repro, could you please provide the nuxt config as well as your package.json of your actual project where this issue occurs so I can better check what's going on?

Hey @dnlsndr, thanks so much for responding to this issue.
Yes, it's a placeholder reproduction you can test against but the issue only appears during deployment.
Here's a repository with the code from the StackBlitz reproduction.
I deployed it on Netlify and you can visit the site to see the error.
package.json
{
  "private": true,
  "scripts": {
    "build": "nuxt build",
    "dev": "HOST=<IP_ADDRESS> nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "devDependencies": {
    "nuxt": "^3.3.3"
  },
  "dependencies": {
    "@phosphor-icons/vue": "^2.0.1"
  }
}

nuxt.config.ts
// https://v3.nuxtjs.org/api/configuration/nuxt.config
export default defineNuxtConfig({

})

I believe the error can be addressed using this simple Nuxt project since the error occurs here. I hope that's okay.
Thanks @dnlsndr

I've implemented a compact build that's only a single file. This should help with your building issues. Check the release notes: https://github.com/phosphor-icons/vue/releases/tag/v2.1.4

Hey @dnlsndr, I'm using 2.2.1 and also getting this error? Has something accidentally been reverted?

@dnlsndr I have changed all my imports to be import { PhBed, PhMapPin } from "@phosphor-icons/vue/compact" and it worked for one build, but now it is erroring again. I deleted packages and reinstalled, but same issue. I'm running  "@phosphor-icons/vue": "^2.2.1", and deploying on vercel, which is just returning a 500 error:
[nuxt] [request error] [unhandled] [500] EMFILE: too many open files, open '/var/task/chunks/build/styles.mjs'
  at async open (node:internal/fs/promises:636:25)
  at async readFile (node:internal/fs/promises:1246:14)
  at async getSource (node:internal/modules/esm/load:46:14)
  at async defaultLoad (node:internal/modules/esm/load:137:34)
  at async ModuleLoader.load (node:internal/modules/esm/loader:396:7)
  at async ModuleLoader.moduleProvider (node:internal/modules/esm/loader:278:45)
  at async link (node:internal/modules/esm/module_job:78:21)


chore(release): fix typo in CHANGELOG.md

Description
seperate -> separate
seperately -> separately

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (no code change)
[x] Refactor (refactoring production code)
[ ] Other

Checklist:

[x] My code follows the code style of this project.
[ ] I have updated the documentation accordingly.
[ ] I have formatted the code with rustfmt.
[ ] I checked the lints with clippy.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Codecov Report
All modified lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:loudspeaker: Thoughts on this report? Let us know!.

Given that

the changelog is auto-generated and
this project is the auto-generator, so not auto-generating it doesn't make much sense, and
git history is immutable (at least in the context of a publicly released code base)

how will manually fixing typos in the changelog that stem from Git commit messages stick?
I presume one could only re-generate future bits, but in my own projects I find it handy to be able to regenerate the whole change log (to update formatting, etc.)

Yeah, this won't have an effect since the changelog is being auto-generated every time. You can probably use preprocessors to edit the commit message or postprocessors to tweak the changelog after generation.

Hmm, a preprocessor that fixes up egregious spelling mistakes that are cemented in Git history for all developers to see but you'd rather not have turn up in the more public facing changelog does sound like a reasonable approach.

Fixed in #316


graphql errors?

1.0 branch.
Didn't modify anything :(
running queries for 1 paths for /Users/Breezewish/Development/about-vijos/node_modules/gatsby-plugin-offline/app-shell.js
graphql errors from file: /Users/Breezewish/Development/about-vijos/node_modules/gatsby-plugin-offline/app-shell.js [ { GraphQLError: Syntax Error GraphQL request (1:1) Unexpected <EOF>

  1:
     ^

      at syntaxError (/Users/Breezewish/Development/about-vijos/node_modules/graphql/error/syntaxError.js:28:15)
      at unexpected (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:989:33)
      at parseDefinition (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:152:9)
      at parseDocument (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:106:22)
      at parse (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:43:10)
      at Promise.then.error.errors (/Users/Breezewish/Development/about-vijos/node_modules/graphql/graphql.js:53:41)
      at graphql (/Users/Breezewish/Development/about-vijos/node_modules/graphql/graphql.js:51:10)
      at graphqlRunner (/Users/Breezewish/Development/about-vijos/node_modules/gatsby/dist/bootstrap/index.js:371:43)
      at /Users/Breezewish/Development/about-vijos/node_modules/gatsby/dist/utils/query-runner.js:378:12
      at Array.map (native)
      at /Users/Breezewish/Development/about-vijos/node_modules/gatsby/dist/utils/query-runner.js:367:21
      at /Users/Breezewish/Development/about-vijos/node_modules/async/queue.js:9:5
      at process (/Users/Breezewish/Development/about-vijos/node_modules/async/internal/queue.js:158:17)
      at Immediate.<anonymous> (/Users/Breezewish/Development/about-vijos/node_modules/async/internal/setImmediate.js:26:16)
      at runCallback (timers.js:649:20)
      at tryOnImmediate (timers.js:622:5)
    message: 'Syntax Error GraphQL request (1:1) Unexpected <EOF>\n\n1: \n   ^\n',
    locations: [ [Object] ],
    path: undefined } ]
rewrote JSON for queries for /Users/Breezewish/Development/about-vijos/node_modules/gatsby-plugin-offline/app-shell.js
graphql query time: 3.751ms
running queries for 3 paths for /Users/Breezewish/Development/about-vijos/templates/template-blog-post.js
rewrote JSON for queries for /Users/Breezewish/Development/about-vijos/templates/template-blog-post.js
graphql query time: 153.079ms
running queries for 1 paths for /Users/Breezewish/Development/about-vijos/pages/index.js
rewrote JSON for queries for /Users/Breezewish/Development/about-vijos/pages/index.js
graphql query time: 3.968ms
running queries for 1 paths for /Users/Breezewish/Development/about-vijos/node_modules/gatsby-plugin-offline/app-shell.js
graphql errors from file: /Users/Breezewish/Development/about-vijos/node_modules/gatsby-plugin-offline/app-shell.js [ { GraphQLError: Syntax Error GraphQL request (1:1) Unexpected <EOF>

  1:
     ^

      at syntaxError (/Users/Breezewish/Development/about-vijos/node_modules/graphql/error/syntaxError.js:28:15)
      at unexpected (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:989:33)
      at parseDefinition (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:152:9)
      at parseDocument (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:106:22)
      at parse (/Users/Breezewish/Development/about-vijos/node_modules/graphql/language/parser.js:43:10)
      at Promise.then.error.errors (/Users/Breezewish/Development/about-vijos/node_modules/graphql/graphql.js:53:41)
      at graphql (/Users/Breezewish/Development/about-vijos/node_modules/graphql/graphql.js:51:10)
      at graphqlRunner (/Users/Breezewish/Development/about-vijos/node_modules/gatsby/dist/bootstrap/index.js:371:43)
      at /Users/Breezewish/Development/about-vijos/node_modules/gatsby/dist/utils/query-runner.js:378:12
      at Array.map (native)
      at /Users/Breezewish/Development/about-vijos/node_modules/gatsby/dist/utils/query-runner.js:367:21
      at /Users/Breezewish/Development/about-vijos/node_modules/async/queue.js:9:5
      at Object.process (/Users/Breezewish/Development/about-vijos/node_modules/async/internal/queue.js:158:17)
      at /Users/Breezewish/Development/about-vijos/node_modules/async/internal/queue.js:100:15
      at apply (/Users/Breezewish/Development/about-vijos/node_modules/lodash/_apply.js:14:25)
      at /Users/Breezewish/Development/about-vijos/node_modules/lodash/_overRest.js:32:12
    message: 'Syntax Error GraphQL request (1:1) Unexpected <EOF>\n\n1: \n   ^\n',
    locations: [ [Object] ],
    path: undefined } ]
rewrote JSON for queries for /Users/Breezewish/Development/about-vijos/node_modules/gatsby-plugin-offline/app-shell.js

I have same error

To reproduce:
git clone git@github.com:gatsbyjs/gatsby-starter-blog.git
git checkout 1.0
npm install
npm run dev

Updated the 1.0 branch to the latest canary which removes these not-actually-errors errors.

Thanks for the reports!


Do all the remaining TODOs

Closes: https://github.com/alphagov/rubocop-govuk/issues/42
Please see the commits for more details.

@richardTowers thanks for reviewing - I hesitated with the Blacklist, but it seemed a bit extreme to avoid using the Cop because of the terminology it uses.


FEATURE REQUEST: please add a wildcard/catchall to data-errors-when

I just need to display a single error message when there is any error without creating all the possibile DIVs with the exact error class.
Is that possibile?

Thanks for the suggestion! 👍
Could you expand a bit on your use case? I cannot think of a situation where not being specific about an error would improve the user experience. I know properly handling form errors can become tedious but I'd like GentleForm to encourage developers to provide a better user experience.
You can also use the includes to declare the error messages once and reuse them as much as needed (see reusing messages).

Il 11/12/2017 16:25, Gabin Aureche ha scritto:

Thanks for the suggestion! 👍
Could you expand a bit on your use case? I cannot think of a situation
where not being specific about an error would improve the user
experience. I know properly handling form errors can become tedious
but I'd like GentleForm to encourage developers to provide a better
user experience.

The use case is when you use a single full error message like this: "The
password is mandatory and must be at least 8 chars with 1 uppercase and
1 number". So this cover any case.
Also in multilingual application, having multiple error message with
different text for the same field is a pain :-)


Ignore filters in Custom Query

Problem:
When a filter (e.g. Time Filter) is in use, this affects Custom
Queries as well.
Root cause:
When executing a Query, entries is used, which contains the
entries after filters have been applied.
Solution:
Use all_entries instead.

Good catch! Thanks!


Process - grooming, assigning issues etc

We write it on readme, so it would be clear.

https://github.com/okestonia/jkan/wiki We will create a wiki and maintain discussion there.


Fix LayerGroup PM property TypeScript

The pm property is now added to L.Path instead of L.Layer. Now we can have different pm handlers for LayerGroup and Layers.
Fix: #912
@ryan-morris please take a look if there is a reason, why this should not work.

@Falke-Design so only problem is pm is not available on just a plain Layer reference now. This PR worked fine with my code, do you know how common a use case on pm for a simple layer is? example

Ok, this is perfect solution then, and way it should have been originally.

Im facing the same issue here.  Im going to use geoman for the first time production and a got this error on ng build.
Glad it is fixed already.


identify remaining open-sourcing issues w/suggested dates

We've already open-sourced Wattile, so this issue is kind of moot. Still, we should check off anything that is done and create new issues to track anything that is not done (if issues don't already exist).


Compatibility issue with node v5.8

node-db-migrate installed globally under nvm and node v5.8.0.
db-migrate up returns:
[2016-03-16 15:21:56.263] [INFO] console - Exit with status code 0
Output is the same if I manually specify my config file (database.json in project root) and environment ("dev").
If I switch to node v5.7.1 db-migrate up works as expected.

Whoops, created this in the wrong project.


Prettification customization is broken

The section on prettifying in the README.md mentions being able to add one's own prettifications.
While really cool in theory, in practice I cannot get that to work at all.
Meanwhile, the built-in prettifications work without issue.
When I go and check the rust-prettify-symbols-alist var after loading a Rust project, it just contains the built-in prettifications (<=, >=, -> etc).
While I haven't checked the code, this leads me to believe that rust-mode bluntly setqs the prettify-symbols-alist or rust-prettify-symbols-alist var rather than adding or pushing to it, as it should.
The problem here is that if I alter the value of prettify-symbols-alist, I need to turn prettify-symbols-mode off and on again in order to use them, and that process erases any modifications I (or my elisp code) makes to prettify-symbols-alist.
So this means I can't update prettify-symbols-alist before loading prettify-symbols-mode (because it will get overwritten), and I cannot do it after (because prettify-symbols-mode will not pick it up until it is reloaded, at which point it will overwrite prettify-symbols-alist).
While it shouldn't be a problem (again in theory), one last thing worth mentioning is that I'm using Prelude.el. EDIT: at this point I'm 99.9% confident that this isn't the issue.
EDIT: Suspicion confirmed, see rust-prog-mode.el in this GitHub search result.

Strange. I had a commit all ready to go, and when I went to test it, my definitions just started working with upstream (i.e. I wasn't loading my fork).
It seems like the behavior I observed is the result of a strange interaction between rust-mode and desktop-save-dir/desktop-change-dir.
The weird part is that in one library file I can see the behavior I observed earlier, and in a sibling library file (i.e. in the same repo, and both files live in $PROJECT_DIR/src) I observe the correct behavior.
What's more is that if I close and reopen the file in which the erroneous behavior is observed, after reopening the correct behavior is observed.
I'm not sure what should and could be done to fix this TBH.
In any case it is apparent that the patch I had ready is not useful in its current form.

I haven't come up with a proper solution to this, so for now I'm closing the issue.
If that changes, I'll reopen it.


Refs #373 - Fixed tuple lookups coding style issues.

Trac ticket number
ticket-373
Branch description
Fixed coding style issues based on @felixxm 's feedback (https://github.com/django/django/pull/18404).
Checklist

[X] This PR targets the main branch.
[X] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[X] I have checked the "Has patch" ticket flag in the Trac system.
[X] I have added or updated relevant tests.
[X] I have added or updated relevant docs, including release notes if applicable.
[X] I have attached screenshots in both light and dark modes for any UI changes.

hyy everyone i am interested in contributing to this project can someone walk me through how to do it

hyy everyone i am interested in contributing to this project can someone walk me through how to do it

@harshisageek please don't ask for help on unrelated pull requests - instead use one of our support channels such as the Django forum, see the FAQ docs for details
You can read through our contributing docs and go through the tutorial to get an idea of how it all works

@sarahboyce , I think this could be merged as it is? It has been a month... if more changes are required we can make that in a follow-up PR. What do you think?


Use configuration to create new atom types

The main part of this PR is e1edd74, where I added the ability to define new atom types in the configuration file:
[atoms.Zn]
charge = 1.8

[atoms]
CH4 = {mass = 16.043, charge = 0, full_name = "methane"}
Ph = {mass = 77.106, full_name = "phenyl"}

Additionally, I renamed the configuration file from .chemfilesrc to .chemfiles.toml, which should be clearer and give syntactic coloration.
Fix #75.

Updated, thanks!


🐛 Bug Report: 'Transaction' is only available in iOS 13.0 or newer

👟 Reproduction steps
Appwrite 2.0.0
Xcode 14.3
import appwrite and build it
👍 Expected behavior
Should be working without any errors.
👎 Actual Behavior
Build failing due to 'Transaction' is only available in iOS 13.0 or newer

🎲 Appwrite version
Different version (specify in environment)
💻 Operating system
MacOS
🧱 Your Environment
sdk-for-apple: 2.0.0
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@truongphamit, thanks for creating this issue! 🙏🏼 The SDK may not be compatible with older versions of iOS. Maybe you can try an older SDK? In the meantime, I'll check with the team to see if there are any other workarounds.

@truongphamit, I've checked with the team, and unfortunately, there isn't any workaround for using the latest version of the SDK on older devices.


Cannot see actual date of package

In the new gallery, you can no longer easily see the publish date of a package. It shows the "friendly" version, but that hides the details. Both on the list of versions and on the package view itself, you see this:

Please bring back the actual publish date.

As a tooltip or do you prefer to see the actual date everytime (which would also work for mobile / screenreader (?))

Friendly version helps to understand 'quickly' the updated timeframe. This gives an idea of how updated the given package is without doing any mental calculation.
In the list view though, the actual publish date can make sense because someone looking at the versions is now doing a deeper dive than while looking at the info.

I'd be okay with it just in the list view since that shows the details.

The current approach is to show the absolute date via a tooltip. Try mousing over any relative date to see the ISO timestamp. This however is not a great situation for phones, as mentioned above.
Also, for dates that would show "x years ago", we show the absolute date (e.g. 8/18/2017) instead since having a bunch of versions next to each other with "1 year ago" is not very helpful (thanks @NickCraver, https://github.com/NuGet/NuGetGallery/issues/4424).
Consider the case where a version is released every couple of months. Is it more helpful to show relative dates or absolute dates? I'm not sure one way or another! My gut says that relative dates make it easier to quickly assess roughly how frequently the package author releases new versions.
Perhaps we can leave this issue open and allow the community to voice their opinions one way or another?

We had no upvotes on this issue over the last year. Seems like the current UI is good enough.
Will reopen if you disagree.


Form-Builder Json not readable

This is  a bug.
Prerequisites

[/ ] Are you running the latest version?
[ /] Are you reporting to the correct repository?
(enso is made of many specialized packages: https://github.com/laravel-enso)
[/ ] Did you check the documentation?
[ /] Did you perform a cursory search?

Description
cannot render create component, json not readable, using homestead/vagrant
Steps to Reproduce

cloned and set up current repo
created structure using php artisan enso:cli (php artisan enso:make:structure does not work)
completed setup of structure, migrated
edited App/Tables/Builders files and showed table properly.
edit App/Forms/Builders but error occurred during render

" Json file is not readable /home/vagrant/code/enso/app/Forms/Builders/Administration/../../Templates/Administration/Sales.json"

Expected behavior
Actual behavior

This looks like a path issue or permission issue.
Can you show your templatePath? It looks like you have an extra parent directory ../.
/home/vagrant/code/enso/app/Forms/Builders/Administration/../../Templates/Administration/Sales.json
Example path
namespace App\Tables\Builders;

use LaravelEnso\Tables\app\Services\Table;
use App\Models\ExampleModel;

class ExampleTable extends Table
{
    protected $templatePath = __DIR__.'/../Templates/ExampleTable.json';

this is the one with a problem
`namespace App\Forms\Builders\Administration;
use App\Sales;
use LaravelEnso\Forms\app\Services\Form;
class SalesForm
{
private const TemplatePath = DIR.'/.. /.. /Templates/Administration/Sales.json';
private $form;

public function __construct()
{
    $this->form = new Form(self::TemplatePath);
}

`
but this table builder works fine
`namespace App\Tables\Builders\Administration;
use App\Sales;
use LaravelEnso\Tables\app\Services\Table;
class SalesTable extends Table
{
protected $templatePath = DIR.'/../../Templates/Administration/Sales.json';
public function query()
{
   `

@carlosiv,
if the error is 'Specified json file was not found :filename' you have a problem with the template path.
if the error is 'Json file is not readable :filename' then the json file is not valid. Use a json validator to fix your file.

@aocneanu This solve my problem. I missed a , in my json file. Thanks a lot.


go-micro/web  too many colons in address

when I run code, at one comput not work and have this word (too many colons in address)
even i run with --server_address <IP_ADDRESS>:5678

Can you provide a code sample you're trying to run?

not need special code i just use temple code

micro new --type web micro_test/user
remove needless code, just print now time
go build -i -o user main.go

but not any comput have this problem

What version of micro and go-micro are you using? I can't reproduce this with the latest versions.

<EMAIL_ADDRESS><EMAIL_ADDRESS>

Interesting. I have not been able to reproduce this, but I'll try few more things and get back to you. Unless someone else beats me to it

I am facing this issue too. Looks like it can be reproduced in an ipv6 network environment. Our team has two guys facing this issue.

I am facing this issue too. Looks like it can be reproduced in an ipv6 network environment. Our team has two guys facing this issue.

I believe I was wrong, the ipv6 issue has been resolved a couple of weeks ago: https://github.com/micro/go-micro/pull/594.
I just found that there is a : at the end of the address and port. Maybe this is the issue.

Ah I see. Not having used ipv6 with micro explains why I could not reproduce it. Thanks for the heads up @kid7st

I just found that there is a : at the end of the address and port. Maybe this is the issue.

Yes, this seems like a plausible cause. Could you pinpoint this to the source code?

What's printing the address here? I can imagine there's some sort of parsing issue here https://github.com/micro/go-micro/blob/master/web/service.go#L50
But what's strange is you're binding to a standard loopback while someting else is specifying ipv6.

can you provide minimal repro code? also say what ipv6 addresses do you have when fail

this is fixed in latest go-micro release


Redis as a caching backend

Are there any plans to support redis as a caching backend?

yes, it's already acknowledged as an accepted feature request here https://github.com/pagespeed/mod_pagespeed/wiki/Accepted-Feature-Requests
closing as a duplicate of https://github.com/pagespeed/ngx_pagespeed/issues/777


Fixes nginx conf file if using http (port 80) only

The options server_name and root were missing in the nginx config file if one wants to install an instance only using port 80 (and let another remote reverse proxy deal with the ssl part for instance)

To merge that, you need to sign off your commit and made DCO check passed.
To do that you have to rebase your commit for further details, please visit this link: https://github.com/nextcloud/ansible-collection-nextcloud-admin/pull/300/checks?check_run_id=15846042861
or click "Details" near DCO check icon.

@aalaesar @staticdev could you take a look?
@YohannLYD I'm not 100% sure if fastcgi_param HTTPS $https if_not_empty; will work without setting it first. Have you tested that for https?

I'm not 100% sure if fastcgi_param HTTPS $https if_not_empty; will work without setting it first. Have you tested that for https?

Yes, the server properly works in both cases (http and https) with this setting.

I've already tested and verified this config. I'm merging it.
Thanks again @YohannLYD for your contribution! :)


Closes: #1

Fixed the code, if the username start with '.' or '_' returns False,
Corresponding of the print statements.
Fixes #<issue_number_goes_here>

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

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

Nice, Thank You! :)


add your favourite mini Javascript games

Good day! Please take a look to added game and let me know if everything is right. Thanks

@rohitbakoliya I want to add one game .

@rohitbakoliya please review my PR and merge into your repo and my PR id is #6 .Thanks!!


Pacifism CB restrictions

It's strange that with pacifist government you can't start a war for democracy in another country, but can conquer/sphere/make puppet it. Feels like it should be to the contrary.
Also, peacekeeping mission failure should probably give free CB.

I would recommend a part of the cb of PDM or HPM. I pack an example in the attachment
(I do not know what it looks like with the permission if parts thereof are used)
cb_types.txt

Point taken on incorporating cb functionality from PDM... but that makes it from a bug into an enhancement.

Victor, please reopen if you feel like correcting.


Error while adding JQuery public methods

If jquery is loaded at page footer and some trick is done make ready function to work before jquery is loaded, like described in here http://writing.colin-gourlay.com/safely-using-ready-before-including-jquery iFrameResizer thorws an exception and stops execution.
Uncaught TypeError: Cannot set property 'iFrameResize' of undefined.
Probably can be fixed if use it like,
if (window.jQuery) {$(document).ready(function () {createJQueryPublicMethod(jQuery);});}
Plunker link

Did you try that? Surely if $.fn isn't available, then surely ready won't be either.

Having just read the article, that trick would break just about every jQuery plugin. If you want to do that I'd suggest using requireJS to late load libraries and plugins. Or just load this after jQuery at the foot of your page.
You could also avoid the jQuery 'tax' completely, I've not used it on my last couple of work projects.
http://youmightnotneedjquery.com/

That said this patch will stop it crashing.


Update how-to-connect-sync-staging-server.md

removed misleading information for delta and full import run profiles, where the suffix: "(stage only)" should refer to staging mode of the server, what is basically not true.

@billmath
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

#sign-off

@akosre @billmath - this article has changed since this PR was created and there are now merge conflicts that prevent merging. Can you you resolve them and sign off again? thanks.
#hold-off

This is no longer in the doc.  I tried to add it on my end.  We can just close it and @akosre se can re-submit it if needed.
#please-close


PLUMED Collective Variables in OPS

This adds a PLUMED wrapper to the OPS collective variables, along with tests and examples. The wrapper requires a PLUMED and py-PLUMED (available via conda-forge) and OpenMM (available from conda/omnia). Tests are skipped in these requirements are not met.
Unsure about if/how to change OPS conda-recipe/meta.yaml

Thank you for the very clear pointers! All changes are implemented as requested.
subprocess did not work for me to source PLUMED. I opted to add the built-in wrapper to the current PYTHONPATH. Please let me know if this is fine.

@apdealbao : Right now it seems that the PLUMED RMSD and MDTraj's RMSD are not looking at the same trajectory, probably a result of the last set of changes. That's the only error in unit testing. (Once it passes tests without errors, I can check things like test coverage, etc.)

Hi @dwhswenson. I am unable to track the error. In the last commit, I updated the tests/test_data/plumed_wrapper/AD_plumed_rmsd.pdb file  to be the same as the first frame of tests/test_data/ala_small_traj.pdb, and in my local branch test_rmsd_vs_mdtraj is passed. Maybe there's something I'm missing.

I reran tests, and that didn't fix. Looking at the error, it's clear that MDTraj has it right and PLUMED has it wrong: with t=0 as the reference frame, the RMSD should be 0 at t=0. It is for MDTraj; is not for PLUMED. The numbers look like the wrong thing is being used as reference, but I don't see that in the code.
Is it possible that PLUMED is reordering equivalent hydrogens or something? It seems like some value entering the RMSD is off by 0.101, but I couldn't find an obvious culprit. Let's take closer looks tomorrow, and if we can't figure it out there, I'll ping Gareth and Giovanni to see if they can help.
It's possible that something is going wrong because one has waters and one does not? That's another guess. In any case, I probably won't look into it until tomorrow afternoon.

Alright. I think it should be easy to fix. I also had that 0.101 error before, and I corrected it by updating the tests/test_data/plumed_wrapper/AD_plumed_rmsd.pdb, so that it was the same as the first frame of the new trajectory. Now it's clear that I probably didn't update that properly in my commit and push. I'll try again early tomorrow.

Hi @dwhswenson. Strangely, in my previous commit (70c899c ) I can already see the corrected tests/test_data/plumed_wrapper/AD_plumed_rmsd.pdb. Not sure what is going wrong.

It runs fine for me locally, as well. I'm on a Mac; I think that you are, too, @apdealbao. It is possible that this is something specific to the Linux version of PLUMED.
I suspect we're going to need to ask the PLUMED team for help here. Could you add a pure-(py-)PLUMED version to the test (i.e., manually include the commands your wrapper classes automate), and compare that your wrapper version? Showing an implementation only based on PLUMED will make it easier for them to debug.
Note that you should do git pull before starting on this -- I added some changes to really ensure that that both are using the same reference frame. (Before MDTraj was technically using frame 0 of the trajectory, not the separate PDB file, which contains the same information. Now it uses the separate PDB file.)

I've been trying this on a Linux box. I can sometimes reproduce the error.
The little bash script I'm using:

#!/bin/bash

COUNT=0

for i in `seq 10`
do
    py.test --pyargs openpathsampling.tests.test_plumed_wrapper > /dev/null
    result_code=$?
    if [ $result_code -eq 1 ]
    then
        echo -n "X"
        COUNT=$((COUNT+1))
    elif [ $result_code -eq 0 ]
    then
        echo -n "."
    else
        echo -n "?"
    fi
done
echo " : $COUNT failures"

Output gives . if all the plumed wrapper tests pass; X if a test fails; ? if something weird happens. Here's what I got from three runs on a Linux box:
X...X.X..X : 4 failures
......X.X. : 2 failures
X......XX. : 3 failures

Whether it fails seems to be random, with about 30% probability. And on my Mac:
.......... : 0 failures
.......... : 0 failures
.......... : 0 failures

Now, what's really weird is that (on Linux) I get a serious mistake on the first frame if I only run the RMSD test. There are two ways of doing this:

ensure that I'm using local data: cd openpathsampling/tests; then py.test test_plumed_wrapper.py::TestPLUMEDCV::test_rmsd_vs_mdtraj
use installed data: from anywhere py.test -k rmsd --pyargs openpathsampling.tests.test_plumed_wrapper

Both give me no error on Mac, same error on Linux:
_______________________ TestPLUMEDCV.test_rmsd_vs_mdtraj _______________________

self = <openpathsampling.tests.test_plumed_wrapper.TestPLUMEDCV object at 0x147787734a10>

    def test_rmsd_vs_mdtraj(self):
        plmd = PLUMEDInterface(self.topology)
        rmsd_ref_file = data_filename(os.path.join("plumed_wrapper",
                                                   "AD_plumed_rmsd.pdb"))
        md_ref = md.load(rmsd_ref_file)
        rmsd_md = paths.MDTrajFunctionCV("rmsd_md", md.rmsd, self.topology,
                                         reference=md_ref, frame=0,
                                         atom_indices=range(22))
        rmsd_pl = PLUMEDCV("rmsd_pl", plmd, "RMSD REFERENCE="
                           + rmsd_ref_file + " TYPE=OPTIMAL")

        np.testing.assert_almost_equal(rmsd_md(self.trajectory),
>                                      rmsd_pl(self.trajectory), decimal=3)
E       AssertionError:
E       Arrays are not almost equal to 3 decimals
E
E       Mismatched elements: 1 / 10 (10%)
E       Max absolute difference: 0.2579862
E       Max relative difference: 1.
E        x: array([0.   , 0.003, 0.006, 0.008, 0.012, 0.018, 0.024, 0.03 , 0.036,
E              0.042], dtype=float32)
E        y: array([0.258, 0.003, 0.006, 0.008, 0.012, 0.018, 0.024, 0.03 , 0.036,
E              0.042])

The first frame is way off, and everything else is fine. When I only run the RMSD test, I always get an error on Linux. This looks kind of like an uninitialized variable error in C: for example, it could be that the Mac conda-forge compiler automatically initializes things to 0 and the Linux compiler doesn't, and that might be why we see a difference.
Is there anywhere you might need to initialize something for PLUMED?

Hi @dwhswenson. I'm currently trying to make a test using the plumed module directly. It will take me some time, but I'll let you know what comes out. Indeed that are many things that are initialized in the interface and perhaps one is responsible for the error.

hi @dwhswenson. I added a new test that uses the plumed module directly. The tests is successfully passed in my Mac, but it might show an error in Linux.

@apdealbao : Thanks for assembling that extra test. I can confirm that it does reproduce the errors I'd seen previously. However, when I used it as the basis of a simple script (with no OPS at all; only MDTraj and PLUMED), I couldn't reproduce the errors. I'll be going through the test bit by bit to make your new test more like my MDTraj-based script, and we'll see if that makes anything clearer.

ok, @dwhswenson. Let me know if I can help with anything else.

Hi @dwhswenson. Just saw the fix :) Any idea why this didn't work in Linux? Just as a take-home message for me.

No idea at all. I'm going to post an issue on PLUMED; maybe they'll have an idea. Since it is only a problem for RMSD, I'm wondering if it is a detail there. My best guess is that first binding it to a name somehow prevents garbage collection? Anyway, I'll CC you on that issue when I post it.
I figured it out because I had rewritten something based on your test_direct, but it didn't reproduce the error. So I slowly changed test_direct to be more like my working version. I had to triple check to be sure that change actually fixed it, because I see no reason that it would.

Hi @dwhswenson. Busy day. I just squashed the commits. I'll take a look at the other comments and try to address them by tomorrow. Thanks for the guidance!

Sorry for the delay on getting this merged. It has been ready to go in for a while. Merging now!

Great news! Thanks a lot @dwhswenson!


Fixed "componentstatuses" API object JSON descriptions.

Also renamed "componentstatus" to "componentstatuses" in kubectl.

Updated with the changes. PTAL.

LGTM. Thanks.

Shippable passed. Merging.


InteractivePopGestureRecognizer Gesture issue

How can I disable interactivePopGestureRecognizer gesture for one page of the application?

Currently not supported, if this is important to you, I recommend using HBDNavigationBar


fix: modal not opening if no options provided

Description
Please include a brief summary of the change.
Type of change

[ ] Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Associated Issues
For Linear issues: Closes APKT-908
Checklist

[ ] Code in this PR is covered by automated tests (Unit tests, E2E tests)
[X] My changes generate no new warnings
[X] I have reviewed my own code
[X] I have filled out all required sections

@tomiir Made few updates to hook comps


win32: Reimplementation of VIMDLL

The VIMDLL support was removed at 8.1.1066.
I reimplemented it on MSVC and MinGW.
The differences from the old implementation are:

Supports MSVC and MinGW. (Don't support Borland C++.)
Supports gvim.exe and vim.exe.
If you build with nmake -f Make_mvc.mak VIMDLL=yes, vim{32,64}.dll
will be built and also stub gvim.exe and vim.exe will be built.
The shared codes between GUI and CUI are all built into the DLL.
So the total size of the distribution files can be reduced.
Supports vim -g and the :gui commands.
If the commands are executed with the -f option, vim.exe will open a GUI
window directly. Otherwise, vim.exe will execute gvim.exe. :gui will
use :mksession to inherit the session to gvim.exe.

Related: https://github.com/vim/vim/pull/4171#issuecomment-477512999

Codecov Report

Merging #4287 into master will decrease coverage by <.01%.
The diff coverage is 31.14%.

@@            Coverage Diff             @@
##           master    #4287      +/-   ##
==========================================
- Coverage   79.86%   79.85%   -0.01%
==========================================
  Files         107      107
  Lines      141589   141621      +32
==========================================
+ Hits       113077   113095      +18
- Misses      28512    28526      +14

Impacted Files
Coverage Δ

src/ui.c
53.8% <ø> (ø)
:arrow_up:

src/option.c
85.98% <ø> (ø)
:arrow_up:

src/gui_gtk_x11.c
48.42% <ø> (-0.35%)
:arrow_down:

src/normal.c
79.14% <ø> (ø)
:arrow_up:

src/ex_docmd.c
80.65% <ø> (ø)
:arrow_up:

src/terminal.c
80.62% <ø> (ø)
:arrow_up:

src/mbyte.c
65.29% <ø> (ø)
:arrow_up:

src/getchar.c
75.54% <ø> (ø)
:arrow_up:

src/channel.c
83.54% <ø> (ø)
:arrow_up:

src/syntax.c
79.61% <ø> (ø)
:arrow_up:

... and 21 more

Continue to review full report at Codecov.

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

Example file sizes:

VIMDLL=no
VIMDLL=yes

gvim.exe
2,841,088
85,504

vim.exe
2,679,296
88,064

vim32.dll
-
2,867,712

Total
5,520,384
3,041,280

Total file size is reduced about 2.4 MB.

@brammool

Supports vim -g and the :gui commands.
If the commands are executed with the -f option, vim.exe will open a GUI
window directly. Otherwise, vim.exe will execute gvim.exe. :gui will
use :mksession to inherit the session to gvim.exe.

Does this really work?  Any variable values would be lost.

:gui with :mksession works almost fine. It inherits global status. But It is not perfect as you pointed out.
(On the other hand, :gui -f works perfect, because vim.exe itself opens the window in the same process.)
If there are any unsaved files, :gui automatically falls back to :gui -f.

@brammool

Supports vim -g and the :gui commands.
If the commands are executed with the -f option, vim.exe will open a GUI
window directly. Otherwise, vim.exe will execute gvim.exe. :gui will
use :mksession to inherit the session to gvim.exe.

Does this really work?  Any variable values would be lost.

:gui with :mksession works almost fine. It inherits global status. But It is not perfect as you pointed out.
(On the other hand, :gui -f works perfect, because vim.exe itself opens the window in the same process.)
If there are any unsaved files, :gui automatically falls back to :gui -f.

I rather not implement this, unless it works perfectly.  Otherwise we
will keep getting bug reports around this.
Ideally this works the same way as it does on Unix.  But I suppose
bringing back the command prompt won't be possible, since Windows
doesn't have a way to detach, other than starting a GUI program.
--
Apologies for taking up the bandwidth with the apology.  Anything else I
can apologise for ...... er no can't think of anything, sorry about that.
Andy Hunt (Member of British Olympic Apology Squad)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

But I suppose bringing back the command prompt won't be possible, since Windows doesn't have a way to detach, other than starting a GUI program.

Yes, unix shell can use Ctrl-Z and bg to move the process to the background, but Windows doesn't support it. Opening a GUI from vim.exe and stay in foreground is useless. So, :gui -f is not useful.
And :gui -b doesn't work perfectly as it uses :mksession. So it might be better to disable :gui.
I think that vim -g is still useful. It works perfectly.

I disabled the :gui command in the latest commit.

Thanks.  So now we mainly save space and the installer will get a lot smaller.
If someone sees a drawback, please let us know.
Otherwise I'll include it soon.

I had a report that "gvim --serverlist" didn't work, so I fixed it.
I also revised the makefiles, update nsis script for VIMDLL.
I think this is ready to be included. If there are still some problems, they can be fixed one by one.


Fonts installation is hardcoded to jcampbell

Hi Jim, thanks for working on this, I"m hoping to adapt this playbook to my needs. Fonts role doesn't complete unless you're jcampbell. Modifying it to my username completes successfully.
Also should the homedir be: /var/home/$USER?
user: jcampbell
homedir: /home/jcampbell

This should be resolved in the main branch now. I use ansible's 'gather_facts' to get the user and home directory information now.