Attempting to Refuel on Non-Scoopable Class T Star

So essentially EDAutoPilot parks on this star at Col 285 Sector JX-T d3-76 even though it is Class:T.  In the Python debugger the ship() method returns 'star_class': 'M' so is mistaken on the star class. It looks as if the Star Class of the FSDTarget (the next star) is being populated too early for the fuel scoop decision. I need to understand how EDAutoPilot determines star_class in ship() to work on a fix.
ED Log:
{ "timestamp":"2021-01-04T04:39:59Z", "event":"StartJump", "JumpType":"Hyperspace", "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "StarClass":"TTS" }
{ "timestamp":"2021-01-04T04:40:04Z", "event":"Music", "MusicTrack":"NoTrack" }
{ "timestamp":"2021-01-04T04:40:07Z", "event":"FSDTarget", "Name":"Col 285 Sector NZ-C b14-1", "SystemAddress":2868904273297, "StarClass":"M", "RemainingJumpsInRoute":3 }
{ "timestamp":"2021-01-04T04:40:17Z", "event":"ReceiveText", "From":"", "Message":"$COMMS_entered:#name=Col 285 Sector JX-T d3-76;", "Message_Localised":"Entered Channel: Col 285 Sector JX-T d3-76", "Channel":"npc" }
{ "timestamp":"2021-01-04T04:40:17Z", "event":"FSDJump", "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "StarPos":[-78.25000,77.12500,-54.15625], "SystemAllegiance":"", "SystemEconomy":"$economy_None;", "SystemEconomy_Localised":"None", "SystemSecondEconomy":"$economy_None;", "SystemSecondEconomy_Localised":"None", "SystemGovernment":"$government_None;", "SystemGovernment_Localised":"None", "SystemSecurity":"$GAlAXY_MAP_INFO_state_anarchy;", "SystemSecurity_Localised":"Anarchy", "Population":0, "Body":"Col 285 Sector JX-T d3-76 A", "BodyID":1, "BodyType":"Star", "JumpDist":19.221, "FuelUsed":4.620865, "FuelLevel":5.408135 }
{ "timestamp":"2021-01-04T04:40:17Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2021-01-04T04:40:24Z", "event":"Scan", "ScanType":"AutoScan", "BodyName":"Col 285 Sector JX-T d3-76 A A Belt Cluster 5", "BodyID":10, "Parents":[ {"Ring":5}, {"Star":1}, {"Null":0} ], "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "DistanceFromArrivalLS":5.226392, "WasDiscovered":true, "WasMapped":false }
{ "timestamp":"2021-01-04T04:40:24Z", "event":"Scan", "ScanType":"AutoScan", "BodyName":"Col 285 Sector JX-T d3-76 A", "BodyID":1, "Parents":[ {"Null":0} ], "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "DistanceFromArrivalLS":0.000000, "StarType":"TTS", "Subclass":2, "StellarMass":0.964844, "Radius":718677632.000000, "AbsoluteMagnitude":5.582504, "Age_MY":48, "SurfaceTemperature":4780.000000, "Luminosity":"Va", "SemiMajorAxis":471539974212.646484, "Eccentricity":0.120456, "OrbitalInclination":23.009228, "Periapsis":213.535804, "OrbitalPeriod":644373738.765717, "RotationPeriod":309500.146263, "AxialTilt":0.000000, "Rings":[ { "Name":"Col 285 Sector JX-T d3-76 A A Belt", "RingClass":"eRingClass_MetalRich", "MassMT":1.4533e+14, "InnerRad":1.1858e+09, "OuterRad":2.6044e+09 } ], "WasDiscovered":true, "WasMapped":false }
{ "timestamp":"2021-01-04T04:40:24Z", "event":"Scan", "ScanType":"AutoScan", "BodyName":"Col 285 Sector JX-T d3-76 A A Belt Cluster 3", "BodyID":8, "Parents":[ {"Ring":5}, {"Star":1}, {"Null":0} ], "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "DistanceFromArrivalLS":8.481720, "WasDiscovered":true, "WasMapped":false }
{ "timestamp":"2021-01-04T04:40:24Z", "event":"Scan", "ScanType":"AutoScan", "BodyName":"Col 285 Sector JX-T d3-76 A A Belt Cluster 4", "BodyID":9, "Parents":[ {"Ring":5}, {"Star":1}, {"Null":0} ], "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "DistanceFromArrivalLS":5.205257, "WasDiscovered":true, "WasMapped":false }
{ "timestamp":"2021-01-04T04:40:24Z", "event":"Scan", "ScanType":"AutoScan", "BodyName":"Col 285 Sector JX-T d3-76 A A Belt Cluster 1", "BodyID":6, "Parents":[ {"Ring":5}, {"Star":1}, {"Null":0} ], "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "DistanceFromArrivalLS":7.940810, "WasDiscovered":true, "WasMapped":false }
{ "timestamp":"2021-01-04T04:40:24Z", "event":"Scan", "ScanType":"AutoScan", "BodyName":"Col 285 Sector JX-T d3-76 A A Belt Cluster 2", "BodyID":7, "Parents":[ {"Ring":5}, {"Star":1}, {"Null":0} ], "StarSystem":"Col 285 Sector JX-T d3-76", "SystemAddress":2621800728931, "DistanceFromArrivalLS":3.995406, "WasDiscovered":true, "WasMapped":false }
{ "timestamp":"2021-01-04T04:43:37Z", "event":"ReservoirReplenished", "FuelMain":4.778135, "FuelReservoir":0.630000 }
{ "timestamp":"2021-01-04T04:49:54Z", "event":"Music", "MusicTrack":"SystemMap" }
{ "timestamp":"2021-01-04T04:50:39Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2021-01-04T04:51:09Z", "event":"ModuleInfo" }
{ "timestamp":"2021-01-04T04:51:14Z", "event":"Music", "MusicTrack":"SystemMap" }
{ "timestamp":"2021-01-04T04:51:16Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2021-01-04T04:51:17Z", "event":"Music", "MusicTrack":"GalaxyMap" }
{ "timestamp":"2021-01-04T04:51:51Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2021-01-04T04:57:54Z", "event":"ReservoirReplenished", "FuelMain":4.148135, "FuelReservoir":0.630000 }

EDAutoPilot Log:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---- AUTOPILOT JUMP ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
DEBUG:root:jump
DEBUG:root:jump= try:0
DEBUG:root:jump= start fsd
DEBUG:root:send=key:{'pre_key': 'DIK_J', 'key': 36},hold:1,repeat:1,repeat_delay:None,state:None
DEBUG:root:jump= in jump
DEBUG:root:jump= speed 0
DEBUG:root:send=key:{'pre_key': 'DIK_X', 'key': 45},hold:None,repeat:1,repeat_delay:None,state:None
DEBUG:root:jump=complete
INFO:root:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---- AUTOPILOT REFUEL ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
DEBUG:root:refuel
DEBUG:root:refuel= start refuel
DEBUG:root:send=key:{'pre_key': 'DIK_R', 'key': 19},hold:None,repeat:1,repeat_delay:None,state:None
DEBUG:root:refuel= wait for refuel
DEBUG:root:send=key:{'pre_key': 'DIK_X', 'key': 45},hold:None,repeat:3,repeat_delay:None,state:None

Debug Console:
ship()
{'fuel_capacity': 32.0, 'fuel_level': 5.408135, 'fuel_percent': 17, 'is_scooping': False, 'location': 'Col 285 Sector JX-T d3-76', 'star_class': 'M', 'status': 'in_supercruise', 'target': 'Col 285 Sector NZ-C b14-1', 'time': 663, 'type': 'krait_mkii'}

i think the problem is here: https://github.com/skai2/EDAutopilot/blob/master/dev_autopilot.py#L229
i think it is taking the first instance of StarClass it finds and in this case that is infact the class of the target system not the curent one. it should be easy to add some more conditions to prevent this. i think this has been fixed in one of the forks but need to confirm that.

i think the problem is here: https://github.com/skai2/EDAutopilot/blob/master/dev_autopilot.py#L229
i think it is taking the first instance of StarClass it finds and in this case that is infact the class of the target system not the curent one. it should be easy to add some more conditions to prevent this. i think this has been fixed in one of the forks but need to confirm that.

Yes @TomW1605 it appears the reliable message in the ED Journal for StarClass of the current system would be the current "event":"StartJump" event and the current "event":"FSDTarget" event should be ignored for StarCLass of the current system.

Yes @TomW1605 it appears the reliable message in the ED Journal for StarClass of the current system would be the current "event":"StartJump" event and the current "event":"FSDTarget" event should be ignored for StarCLass of the current system.

Yes @TomW1605 it appears the reliable message in the ED Journal for StarClass of the current system would be the current "event":"StartJump" event and the current "event":"FSDTarget" event should be ignored for StarClass of the current system.

Should I submit a pull request?

Yes @TomW1605 it appears the reliable message in the ED Journal for StarClass of the current system would be the current "event":"StartJump" event and the current "event":"FSDTarget" event should be ignored for StarClass of the current system.

Should I submit a pull request?

go for it but please test it first

go for it but please test it first

This is working for non-scoopable stars now. Simple fix really. I didn't see any testing files in the repo but I did test on a 300LY route through scoopable and non-scoopable stars with no issues. I had the threshold turned up to a fairly high percentage to see plenty of refuel activity. Pull request is inbound.

This is working for non-scoopable stars now. Simple fix really. I didn't see any testing files in the repo but I did test on a 300LY route through scoopable and non-scoopable stars with no issues. I had the threshold turned up to a fairly high percentage to see plenty of refuel activity. Pull request is inbound.


Issue #982 A UX improvement on skipping rotation while pinching on mobile devices

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Does your submission pass tests?

Note: please do NOT include build files (those generate by the build-xxx commands) with your PR,

Thank you for your help in advance, much appreciated !

My apologies if I missed this in the contribution guide. Could you please let me know if it was on purpose all the semicolons are omitted? Is it documented somewhere?

there is standardx tool that you need to run after changing files. it is almost the same as https://standardjs.com/ but allows few customizations. The tool will let you know if file is not formated to that style and also has --fix option to fix automatically those that can be fixed reliably

Thanks very much.
On Wed, Jan 26, 2022 at 02:34 Davor Hrg @.***> wrote:

there is standardx tool that you need to run after changing files. it is
almost the same as https://standardjs.com/ but allows few customizations.
The tool will let you know if file is not formated to that style and also
has --fix option to fix automatically those that can be fixed reliably
—
Reply to this email directly, view it on GitHub
https://github.com/jscad/OpenJSCAD.org/pull/983#issuecomment-1021938238,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFVCX7QE72PSOUPSAXY7Z3TUX6PXLANCNFSM5M2HUBJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Thanks
Sam

Also if you use discord feel free to join the jscad channel https://discord.com/channels/412182089279209474/758341118177050634/935275349586116648

Also if you use discord feel free to join the jscad channel https://discord.com/channels/412182089279209474/758341118177050634/935275349586116648

Looks like the channel is not accessible to me. Will check it later.

Thanks to @hrgdavor 's tips on formatting the code.
I had ran the below commands to fix the format. Amended the commit and now ready for review.
standard --fix %filenames%

Code looks good to me, but I do not have any ios device to test. Maybe @z3dev has something to test and approve this PR.

@samuelwang48 Thanks for the changes. These look fine but must work across all browsers, both PC and mobile browsers.
I’ll do some testing this weekend across browsers.
What browsers did you test with?

I tested on MacOS (Firefox, Safari, and Chrome) with track pad, and wheel mouse.
I also tested with iPad with Firefox, Safari, Edge, and Chrome.
Everything worked just fine, @samuelwang48
Thanks for these changes!

@samuelwang48 nice to see new committers, hope to see even more PRs in the future :)
if u are chatty like I am, you can also join jscad channel on CadHub discord server https://discord.gg/AaqGskur93

@z3dev Hi thanks for taking time to test it.
@hrgdavor Thanks for the info. I've joined.
Really glad to be here. Filed a few new issues while scanning through all the documentation. Will be looking into it.


Move Release checklist to Eng hub

See section: https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release
This applies to both management and data plane

Hi @czubair Any updates for this item?

@ccbarragan Hi Crystal! Sorry I don't quite understand what I should be updating/reviewing here. Feel free to ping me or set up a meeting. Since I am transitioning off the release, this might be better for others to decide.

Link to ADO PR to get checking list in Docs: https://dev.azure.com/azure-sdk/internal/_git/azure-sdk-docs-eng.ms/pullrequest/947


fix e2e producer

I've noticed that when working with clusters having several controller and broker nodes, retrieving cluster metadata may occasionally return stale data. This issue is evident when, for example, an end-to-end test topic is created, and the topic metadata is retrieved immediately afterward. In this case, the metadata request may return error code 3, which corresponds to the UNKNOWN_TOPIC_OR_PARTITION error. This error likely occurs when a client connects to a broker that is not yet aware of the new topic because it hasn't consumed the latest data from the __cluster_metadata topic.
In summary, when the end-to-end code attempts to populate the value of s.partitionCount, it might encounter the UNKNOWN_TOPIC_OR_PARTITION error, even if the topic actually exists. This results in a partition count of zero, preventing the producer from sending any data.

Hi @weeco. Can you please have a look?

@weeco just a kind reminder.

@andrewhsu can you have a look?

@bachmanity1 I'll try to look at your PR soon, but I'm currently very busy with other things that have higher priority. Even though this change is just a few lines, I'll have to dig deeper to see if this could cause other sort of issues before approving & merging the PR.

Hi @weeco,
I wanted to let you know that I've updated this PR. I realized that my previous approach didn't account for scenarios where the broker count is updated.
I also wanted to discuss the partitionsPerBroker config. I believe it should clarified that this configuration is only applied when a topic is created and does not take effect when the broker count changes. If the original intent was for this setting to apply even when the broker count changes, we’d need to adjust the topic reconciliation logic accordingly. However, handling cases where the broker count decreases could be quite tricky.
By the way, it seems there’s a bug preventing new partitions from being created when new brokers are added, as reported in #257. Could you take a look at that PR too? Thanks!

@weeco kind reminder

Hi @weeco, is there any chance to get this reviewed anytime soon?

Thanks for your PR @bachmanity1 and sorry for the long waiting time. I added some minor things but generally LGTM


[Autoplay policy changes] Update ETA and add WebAudio

This CL adds a WebAudio best practises section so that Web Developers know how to deal with upcoming Autoplay policy changes.
It also updates ETA to April as in https://sites.google.com/a/chromium.org/dev/audio-video/autoplay
WDYT @mounirlamouri
Preview: https://pr-5760-dot-web-central.appspot.com/web/updates/2017/09/autoplay-policy-changes

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2017/09/autoplay-policy-changes.md#L164 - '

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2017/09/autoplay-policy-changes.md#L164 - '

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2017/09/autoplay-policy-changes.md#L164 - '

lgtm! :)

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2017/09/autoplay-policy-changes.md#L171 - '

@petele Can you merge?

:tada: This has been pushed live to https://developers.google.com/web/


Intellij passing --mode=OFF

I'm on lubuntu trying to run RuneLite through Intellij, I can't seem to figure out how to make the game show up, all I get is a RuneLite window that I can see through.
Jdk 8 is set to the project, I have it running in --debug and dev mode. I tried adding --mode=OFF here, but it just through's errors.
Exception in thread "main" joptsimple.UnrecognizedOptionException: mode is not a recognized option

mode is an argument to the launcher, it is not a valid client argument.

How would I be able to do it with Intellij, I need the dev mode. I've done it on windows before like that.


[Feature]: Allow setting of SANDBOX_ENV variables from config.toml

What problem or use case are you trying to solve?
It is possible to set environmental variables in the sandbox through environmental variables in the environment, pre-pended with SANDBOX_ENV: https://github.com/OpenDevin/OpenDevin/blob/beb74a19f607e7fa2d1c2581373fc7ec1409ffeb/opendevin/runtime/sandbox.py#L12-L16
I expected that I would also be able to set the same variables through config.toml, but apparently this does not work.
Describe the UX of the solution you'd like
It would be good if we could set the variables through config.toml as well. This can be done by modifying the code above, or possibly modifying the file opendevin/core/config.py

There's a PR that reworks sandbox config https://github.com/OpenDevin/OpenDevin/pull/2336. It doesn't address this currently, but I'll include this.

Oh interesting. I didn't know this is a thing. Meaning if we append "SANDBOX_ENV" to any environment variable and use it in the docker command, it will set it in the sandbox?

Hey @mamoodi , yes it's a thing. It could definitely be documented better.

Loading the .env file in the workspace folder is not suitable for this?


fixed issue for 64b BOOL as string in ipod 5

Was facing an issue with ipod 5 where bool value gets stringified. Last commit has removed this check I guess it is still needed for backward compatibility

Yep, looks like this conflicts with #569

Relevant Apple docs: https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ObjCRuntimeGuide/Articles/ocrtPropertyIntrospection.html

I think the issue may be that the BOOL type essentially is a char - https://opensource.apple.com/source/objc4/objc4-493.9/runtime/objc.h.auto.html

@billinghamj this check was there before #569 integration. #569 removed it which breaks my conversion. ipod 6 doesn't have any issue with #569 adding this check back will not affect #569 I have tried and tested it myself on both ipod 5 and 6.

@faizan-carameltech As you can see, the tests on Travis are failing with the change - so it is quite non-trivial and does seem to affect #569.
https://travis-ci.org/jsonmodel/jsonmodel/builds/225915686#L467-L468

Is this a 32 bit thing perhaps?

Closing due to inactivity for now. As this does seem to be a 32-bit issue, and no devices have been 32-bit only for many years, I'm not too concerned about this.
If anyone can adapt this to push it through safely though, would be very happy to get it merged.

This might be the root cause for crashe #601 and missbehaviour #585

@mstarke If you’re able to make this PR safe to merge, happy to review and get it merged

I can give it a try bot do not count on me :)


Unable to start container with repository-gcs setting added to keystore

Hi there,
I am building an image using the following Dockerfile:
FROM docker.elastic.co/elasticsearch/elasticsearch:5.4.2

USER root
ENV JQ_VERSION=1.5 \
    JQ_SHA256=c6b3a7d7d3e7b70c6f51b706a3b90bd01833846c54d32ca32f0027f00226ff6d
RUN cd /tmp \
    && curl -o /usr/bin/jq -SL "https://github.com/stedolan/jq/releases/download/jq-$JQ_VERSION/jq-linux64" \
    && echo "$JQ_SHA256  /usr/bin/jq" | sha256sum -c - \
    && chmod +x /usr/bin/jq

# https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#_c_customized_image

COPY elasticsearch.yml /usr/share/elasticsearch/config/
COPY encoded /tmp/.

RUN chown elasticsearch:elasticsearch config/elasticsearch.yml \
    && chown elasticsearch:elasticsearch /tmp/encoded \
    && bin/elasticsearch-plugin install io.fabric8:elasticsearch-cloud-kubernetes:5.4.2 \
    && bin/elasticsearch-plugin install repository-gcs

COPY docker-entrypoint.sh /usr/local/bin/
RUN chmod +x /usr/local/bin/docker-entrypoint.sh

USER elasticsearch

ENTRYPOINT [ "/usr/local/bin/docker-entrypoint.sh" ]
CMD ["elasticsearch", "-v"]

Here is the elasticsearch.yml config file:
network.host: <IP_ADDRESS>

processors: ${PROCESSORS:}

# minimum_master_nodes need to be explicitly set when bound on a public IP
# set to 1 to allow single node clusters
# Details: https://github.com/elastic/elasticsearch/pull/17288
discovery.zen.minimum_master_nodes: 1

plugin.mandatory: repository-gcs

And the entrypoint script:
#!/bin/bash
set -e

if [ "$1" = 'elasticsearch' ]; then
    echo "Decoding credentials"
    cat /tmp/encoded | base64 -d > /tmp/elasticsearch-backup-service-account.json
    chown elasticsearch:elasticsearch /tmp/elasticsearch-backup-service-account.json
    mv /tmp/elasticsearch-backup-service-account.json bin/creds.json

    echo "Creating keystore"
    bin/elasticsearch-keystore create

    echo "Adding credentials to keystore"
    cat bin/creds.json | bin/elasticsearch-keystore add-file --stdin gcs.client.gcs1.credentials_file

    echo "Deleting secure files"
    rm -f /tmp/encoded
fi

exec "$@"

When running the container, I get this error:
[2018-10-16T10:57:51,605][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [aggs-matrix-stats]
[2018-10-16T10:57:51,605][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [ingest-common]
[2018-10-16T10:57:51,605][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [lang-expression]
[2018-10-16T10:57:51,605][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [lang-groovy]
[2018-10-16T10:57:51,606][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [lang-mustache]
[2018-10-16T10:57:51,606][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [lang-painless]
[2018-10-16T10:57:51,606][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [percolator]
[2018-10-16T10:57:51,606][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [reindex]
[2018-10-16T10:57:51,606][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [transport-netty3]
[2018-10-16T10:57:51,606][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded module [transport-netty4]
[2018-10-16T10:57:51,607][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded plugin [discovery-kubernetes]
[2018-10-16T10:57:51,607][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded plugin [ingest-geoip]
[2018-10-16T10:57:51,607][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded plugin [ingest-user-agent]
[2018-10-16T10:57:51,607][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded plugin [repository-gcs]
[2018-10-16T10:57:51,608][INFO ][o.e.p.PluginsService     ] [w7B4izN] loaded plugin [x-pack]
[2018-10-16T10:57:53,665][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown secure setting [gcs.client.default.credentials_file] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:127) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:114) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:67) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.cli.Command.main(Command.java:88) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) ~[elasticsearch-5.4.2.jar:5.4.2]
Caused by: java.lang.IllegalArgumentException: unknown secure setting [gcs.client.default.credentials_file] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:293) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:256) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.common.settings.SettingsModule.<init>(SettingsModule.java:139) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.node.Node.<init>(Node.java:343) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.node.Node.<init>(Node.java:242) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:232) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:232) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:350) ~[elasticsearch-5.4.2.jar:5.4.2]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) ~[elasticsearch-5.4.2.jar:5.4.2]
	... 6 more

Can anyone direct me in what I am doing wrong please? I have a feeling that the plugin isn't registering the setting correctly or something I can't quite work out

This way of configuring the repository-gcs plugin was not added until 6.3.0 yet you're on 5.4.2. You need to refer to the 5.4.2 documentation for how to configure repository-gcs for that version.


Duo hardware tokens user not get authenticate

We running this scripts for Meraki VPN  integrated with Duo authentication, When user use Duo app on cell phone it authenticate the user . When user use Duo   Hardware Token it did not works, i check  RADIUS server logs even user not hitting the RADIUS server for authenticate .

change the UseRasCredentionals=0 to 1 issue resolved


packages should match without flavour

Some packages matches only with given architecture:
{:package [{ :name "openjdk-8-jdk:amd64" }]}
Enhance parsing to have archinfo avail in extra field.

added failing test:
https://github.com/DomainDrivenArchitecture/dda-serverspec-crate/commit/9d118dc5d4945923fa1043edb8527c0b8ecc8828

Fixed: https://github.com/DomainDrivenArchitecture/dda-serverspec-crate/releases/tag/1.1.3


fix(trajectory_follower): accommodate the parameters of the controllers to the dynamics in the simulator.

Description
Without specific reasons, the parameters of the controllers should correspond to the parameters of the dynamics.
However, the current version of autoware has a mismatch in these parameters, the detail of which is visualized below:

Therefore, this PR corrects these two parameters in the controller.
vehicle_model_steer_tau in mpc.param.yaml and delay_compensation_time in pid.param.yaml, in specific.
The corrected controllers will match the dynamics of the vehicle in the simulator.
Related links

Tests performed

Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@HansOersted Please add the link of the sample_vehicle_description in the description.


Allow PDCClient to be configured with arguments.

Looks good to me.

Looks good.

looks good

Merged as https://github.com/product-definition-center/pdc-client/commit/e6d62040479d3c94a1c2aaafafed7835ddb8205a


Update dc68e38e-dfa1-45b8-b204-89c8ba121f96.png

Made changes to the wordings in the Screenshot it was misspelt as "patter"

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8006

@tiburd Please merge this PR. Thanks


can't be installed since not a package, no setup.py

add a setup.py so this can be installed as a package and uploaded to PyPI, etc.

setup.py added in d0e0b4d83ba10f901e4e6ade9e753ebbae0ee789


Sensors disabled in Hassio

With the new Frigate 0.13.1 all the sensors have disappeared in Hassio. I only have sensors for the camera, but all the switches and the rest of the sensors are invalid now.
Could you please check?

No one else has reported this, you'll need to provide more info

У меня также

you are running frigate 0.12 which is not compatible with the integration, this is covered in the release notes

aaa sorry, as always I didn’t read the small description

Solved from my side. It was a problem with the mqtt server. I have changed it and not updated the ip in Frigate.


Error breaking popup : null is not an object

I implemented the popup by following the Wizard and copy/pasting the result.
I get this error on Chrome:
cookieconsent.min.js:1:4274
TypeError: null is not an object (evaluating 's.firstChild')
I get this error on FireFox:
cookieconsent.min.js:1:4257
TypeError: s is null[Learn More]
Is this something at my end or is this the code provided?
Apologies if this is my bad somehow.
Link to the Wizard I used: https://cookieconsent.insites.com/download/

For some reason document.body returns null.
You could try:

Moving the scripts to footer, just before the </body> tag.
Wrapping the initialise code in window.onload:
window.onload = function() { window.cookieconsent.initialise( //your_options ) }

Moving the scripts to the bottom has helped. Thank you :).


WIP: inline small content into manifest

If merged will close #1742

@vdice FYI

Seems to work fine based on some local testing.


[BUG] Migration from BIG-IP HA to BIG-IP Standalone leave HA config in migrated config

Describe the bug
Opening this bug on behalf of Chris. Tried in his lab to migrate a BIG-IP from vCMP to VELOS, and we noticed the restored BIG-IP was containing artifacts of the secondary BIG-IP part of the cluster in the source. I believe the problem is the same as SOLUTIONS-6481.
Workaround is to execute the following command on the target device:
tmsh delete /cm trust-domain all
To Reproduce
Steps to reproduce the behavior:

Get UCS from SR 1-6993580048\INCOMING\jun_10\lab02.ucs
Restore the UCS on a vCMP guest <IP_ADDRESS>
Use Journeys 3.3.2 to migrate the config to a VELOS tenant <IP_ADDRESS> after resolving all the errors in the tool (including DeviceGroup)

Context

Please specify, app version: 3.3.2
And Platform version of the system you want to migrate: vCMP guest to VELOS tenant <IP_ADDRESS>

The bug was fixed in release 3.3.5


Player data is lost (v3.2.7)

The problem I have had with this version and with previous versions, is that the progress of the players is lost, in addition to the costs involved in each mission.
At any time the plugin starts to fail, does not count the killed mobs, or other errors and from one moment to another the user loses the progress in the mission.
Quests version: 3.2.7
[Quests] Loading Quests v3.2.7-b284
Console errors:
Line x: [15:55:00] [Server thread/ERROR]: [Quests] currentStage was null for 97a0169f-d9ee-384f-8314-7d7395efa638 on command Line z:[15:56:12] [Async Chat Thread - #43/ERROR]: [Quests] currentStage was null for 97a0169f-d9ee-384f-8314-7d7395efa638 on chat Some errors:[15:57:21] [Server thread/ERROR]: [Quests] currentStage was null for 97a0169f-d9ee-384f-8314-7d7395efa638 on command [15:57:25] [Server thread/INFO]: resdicam0909 issued server command: /t [15:57:25] [Server thread/INFO]: [PLAYER_COMMAND] resdicam0909: /t  [15:57:25] [Server thread/INFO]: o_Xo issued server command: /quests journal [15:57:25] [Server thread/ERROR]: [Quests] currentStage was null for 97a0169f-d9ee-384f-8314-7d7395efa638 on command [15:57:26] [Server thread/INFO]: o_Xo issued server command: /quests journal [15:57:26] [Server thread/ERROR]: [Quests] currentStage was null for 97a0169f-d9ee-384f-8314-7d7395efa638 on command [15:57:27] [Server thread/ERROR]: null org.bukkit.command.CommandException: Unhandled exception executing command 'quests' in plugin Quests v3.2.7-b284 	at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46) ~[spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:141) ~[spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at org.bukkit.craftbukkit.v1_12_R1.CraftServer.dispatchCommand(CraftServer.java:649) ~[spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.PlayerConnection.handleCommand(PlayerConnection.java:1397) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.PlayerConnection.a(PlayerConnection.java:1232) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.PacketPlayInChat.a(PacketPlayInChat.java:45) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.PacketPlayInChat.a(PacketPlayInChat.java:1) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.PlayerConnectionUtils$1.run(SourceFile:13) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_131] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_131] 	at net.minecraft.server.v1_12_R1.SystemUtils.a(SourceFile:46) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.MinecraftServer.D(MinecraftServer.java:748) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.DedicatedServer.D(DedicatedServer.java:406) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.MinecraftServer.C(MinecraftServer.java:679) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:577) [spigot-1.12.2.jar:git-Spigot-3d850ec-809c399] 	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] Caused by: java.lang.NullPointerException 	at me.blackvein.quests.Quester.getObjectivesReal(Quester.java:374) ~[?:?] 	at me.blackvein.quests.Quester.updateJournal(Quester.java:268) ~[?:?] 	at me.blackvein.quests.Quests.questsJournal(Quests.java:1555) ~[?:?] 	at me.blackvein.quests.Quests.questActionsCommandHandler(Quests.java:1351) ~[?:?] 	at me.blackvein.quests.Quests.onCommand(Quests.java:710) ~[?:?] 	at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44) ~[spigot-1.12.2.jar:git-Spigot-3d850ec-809c399]
... 15 more
Config.yml - PasteBin
Thanks.

on my end the data is not lost only the stages are bugged for players here is an example:
currentQuests:

Clean the statue of the Hokage's nose
Helping the villagers in the small village
Team in Need!
Talk to my friend
Orochimaru
Stolen Sunagakure Intel
Find Missing Cat
Speedy Kitty
Finding the LostKid
currentStages:
0
0
null
0
null
2
0
null
0

The user data is fine, they are missions that disappear from one moment to another in the middle of the mission.
`currentQuests: none
currentStages: none
quest-points: 60
completed-Quests:

Atraco 1
ModernWar Mision
Atraco 2
hasJournal: false
lastKnownName: o_Xo
`
This user, had an active mission called "Modern War 2", and as you can see he does not have it in his configuration.

Since the developer doesn't do anything. Meanwhile I found out why this happens. /quests journal is breaking players and all their permissions they cant do anything and it's duplicating the quests book instead of removing them

@RubenStryker The error you've posted means that a quester with a UUID of 97a0169f-d9ee-384f-8314-7d7395efa638 does not have any current stages even though Quests expects that they should. Looking up that UUID online, it doesn't appear to match with any known Minecraft player...

It could be that an NPC has been mistaken for a quester somehow or perhaps you're running in offline mode? Hard to suggest a fix when there's no obvious way to replicate the problem. You could try blacklisting the UUID and see if that resolves the issue (believe the command is /questadmin purge 97a0169f-d9ee-384f-8314-7d7395efa638).
@andinis That journal issue sounds unrelated and is more likely a duplicate of #332

That uuid that does not find, on my server is the user "O_xo" that if you look for your username on that website gives a different uuid.
I do not know why, maybe it's because the server is non-premium, if I do what you tell me this user will not be able to perform any mission.
I have warned the users of my server not to do missions until this is solved, since they lose the money and the items that are required to start some missions.
My users are waiting for you to solve it, if you want to provide more information about the error I can provide all you need.
A greeting.

If by "non-premium" you mean the server is running in offline mode, chances are that is part of the issue. In your config.yml, there is a note that says:
#The server is no-premium, and as previously the user data was also lost I have tried to modify these last two options.
convert-data-on-startup: false
generate-files-on-join: false
Quests needs to know a player's UUID to save and load their data. Here's what I think happened: since your server is offline, it saved whatever the player's client claimed its UUID to be when they joined, in this case the unofficial 97a0169f-d9ee-384f-8314-7d7395efa638. However, when you enabled convert-data-on-startup, Quests tried to get their official UUID from Mojang's servers, which is 29ba6c34-a53c-4a8b-8d55-306526a8822a. It stands to reason that, since the two are obviously different, Quests is having trouble figuring out which UUID to use.
Unfortunately, the only way to fix this would be to stop the server, wipe all traces of either UUID from the Quests/data/ folder and start the server with convert-data-on-startup: false. You could try replacing every instance of the official UUID with the unofficial one, but frankly that may or may not work. In the future, do not enable settings you're unfamiliar with.


flag for ollama executable path

Hi!
Nice work! Could you add a flag like --ollama-bin ~/code/ollama/ollama to explicitly give the path to the ollama executable?
when building and testing ollama from source, i'd like to just be able to supply it the path, without having to do a full install on the system.
Cheers

--ollamabin flag is added in v0.3.12
Please checkout the latest code


UBL support

As far as I understand, python-drafthorse supports only CII flavor. Is UBL support planned?

Currently not

Just a little note about this topic: As far as i found out while searching for CII and UBL, the "ZUGFeRD" (-> drafthorse) type only supports CII flavor. UBL is only used with X-Rechnung(xinvoice), so i think that's the reason why it is not supported by this library.

@RitchiS99 that's a good point. Do I understand correctly that an XRechnung-conform ZUGFeRD invoice provides only an XML file without the PDF? See this site for details.


New version: ElijahLopez.MusicCaster version 5.13.9

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

That has never happened before, must be because of the new winget releaser not solving the edge case of last major version? I'm surprised I even caught your comment in my emails since I usually auto-delete them.


Automating colors from current colorscheme

I'd like to automatically theme galaxyline using the colors from the colorscheme I'm using at any given time. I thought about doing this by setting up the galaxyline config for each component's highlight using some n/vim variable which holds the highlight groups and their color, but I can't find such a variable (I'm looking for something like e.g.: "vim.g.theme.colors.bg").
Is there any such way of doing this?
Thanks :)

I'm not sure if this is what you mean, but you can pass highlight groups to a component as a string, like:
highlight = 'StatusLine'

I'm not sure if this is what you mean, but you can pass highlight groups to a component as a string, like:

This is indeed possible, thanks! However, ideally it would be nice to have some sort of themes like lualine has. At the moment, I think the best option unfortunately is to manually define the colors for the colorscheme you are using (and script it somehow to change dynamically along with your colorscheme).
Would automatic themes taken from your colorscheme be possible, as in lualine?

Hey, I forked galaxyline very recently and added this feature (I'm hoping to PR upstream when glepnir is free), you can use my fork in the meanwhile if you want.
There's also documentation about themes if you want to take a look and create your own colors.


can't download json

Hello, split_ zhou_ Caltech101.json，split_ zhou_ OxfordFlowers. JSON, and split_ zhou_ DescribableTextures. JSON page link can't be opened. Is there any other download link?

The links work fine. Maybe use a VPN if you're in an internet-restricted area?


2.0 Release

Given the addition of reactive interfaces for all the exposed APIs, and the internal change to a reactive backend for everything,  I'm thinking we should bump to 2.0; if not at the very lease we're looking at 1.2

@vsevel The ball is in your court for this currently as I'm not knowledgable about the release process.


Copy templates from pluto

These templates will be pushed to our data library image so that the pluto publishing action can reference them by name. This page on the docker website has direction how to push these changes

Max all your questions are good and they all have the same answer, which is that I'm just taking the templates from pluto and putting them in data library. I assumed that the differences were due to the data library ones being out of date and this PR as updating them

Ok cool yea that's a good question. You can see that it's using today's date to construct the url, but the only working url's are those where the version is an actual version of pluto (22v1, 22v2, etc). You can see where the publishing version gets the workflow

After figuring out the proper versioning for the files (22v2 and 20v7 for the dcp_mappluto_historical), everything worked except for the pluto_corrections.yml template. digging into this now but getting error:feilds are not valid. please review your file

I got the pluto_corrections template to work, do you want me to push the changes? @SashaWeinstein. @td928 would then have to approve the PR

can you start a new branch and open a PR pointing to 256-Templates-From-PLUTO?

Hey I want to flag that this action successfully used these templates via the ubuntu-pluto_templates version of the image. I would appreciate a quick confirmation that the 5 datasets we publish have been successfully added to the 22v2 folder.
Once that's confirmed I will merge this work in, and replace the ubunutu-latest version with the version from this code. Then I'll work to clean up the action-library-archive repo, and make an enhancement to this repo to make this upgrade easier in the future.
Since no actual changes were made to the action-library-archive process we won't need to merge any PR's

@SashaWeinstein I see all 5 outputs in edm-recipes each with a 22v2 folder that was updated earlier today. FYI The latest folders are still using the 22v1 versions - let me know if you want me to look at these closer

That's the expected behavior here


Add test workflow

Currently, there is no workflow to check the quality of code when it is pushed to the repository. However, by setting up this, we can prevent code quality degradation and achieve safer development.
First, I incorporated eslint into the workflow, which requires minimal modification of existing code. I plan to add typescript compiler checks, etc. later.

LGTM, good idea to add some automated tests!


HTML escaping

Changes:

include bleach dependency
escaping for form and model field
updated readme
simple test cases

@lqez Can you release latest version to pypi 🙇 ?

@Surgo Oh my! I will do it today. Thanks.

☺

Any chance of a release with this PR fix?  Thanks!


CheckHealth Reports "Cody Auth Failed: nil"

sg.nvim report ~
- Machine: x86_64, sysname: Darwin
- OK Valid nvim version: table: 0x010900ba98
- WARNING Unable to find valid cargo executable. Trying to build sg.nvim locally will fail. Instead use `:SourcegraphDownloadBinaries`
- OK Found `sg-nvim-agent`: "/Users/[REDACTED/.local/share/nvim/lazy/sg.nvim/dist/sg-nvim-agent"
- OK Found `node` (config.node_executable) is executable.
  Version: '18.19.0'
- OK Found `cody-agent`: /Users/REDACTED/.local/share/nvim/lazy/sg.nvim/dist/cody-agent.js
- OK   Authentication setup correctly
- OK     endpoint set to: https://REDACTED.sourcegraph.com
- OK Found correct binary versions: "1.0.5" = "1.0.5"
- OK   Sourcegraph Connection info: {
  access_token_set = true,
  endpoint = "https://REDACTED.sourcegraph.com",
  sg_nvim_version = "1.0.5",
  sourcegraph_version = {
  build = "5.2.5",
  product = "5.2.5"
  }
  }
- ERROR Cody Auth Failed: nil
- ERROR sg.nvim has issues that need to be resolved

This issue persists even though Cody is running and available. This state has occurred after the following issue resolved.

Running into a similar issue running Neovim v0.9.5
sg.nvim report ~
- Machine: x86_64, sysname: Linux
- OK Valid nvim version: table: 0x7f8658360ea8
- OK Found `cargo` (cargo 1.46.0) is executable
-     Use `:SourcegraphDownloadBinaries` to avoid building locally.
- OK Found `sg-nvim-agent`: "/home/username/.local/share/nvim/site/pack/packer/start/sg.nvim/dist/sg-nvim-agent"
- OK Found `node` (config.node_executable) is executable.
  Version: '18.18.2'
- OK Found `cody-agent`: /home/username/.local/share/nvim/site/pack/packer/start/sg.nvim/dist/cody-agent.js
- OK   Authentication setup correctly
- OK     endpoint set to: https://codyendpoint.sourcegraph.com
- OK Found correct binary versions: "1.0.5" = "1.0.5"
- OK   Sourcegraph Connection info: {
  access_token_set = true,
  endpoint = "https://codyendpoint.sourcegraph.com",
  sg_nvim_version = "1.0.5",
  sourcegraph_version = {
  build = "5.2.5",
  product = "5.2.5"
  }
  }
- ERROR Cody Auth Failed: nil
- ERROR sg.nvim has issues that need to be resolved

I am getting the same error on sg 1.0.6 as well.
sg: require("sg.health").check()

sg.nvim report ~
- Machine: arm64, sysname: Darwin
- OK Valid nvim version: table: 0x0100e00840
- OK Found `cargo` (cargo 1.68.2 (6feb7c9cf 2023-03-26)) is executable
-     Use `:SourcegraphDownloadBinaries` to avoid building locally.
- OK Found `sg-nvim-agent`: "/Users/jmaxwell/.local/share/nvim/site/pack/packer/start/sg.nvim/dist/sg-nvim-agent"
- OK Found `node` (config.node_executable) is executable.
  Version: '20.11.0'
- OK Found `cody-agent`: /Users/jmaxwell/.local/share/nvim/site/pack/packer/start/sg.nvim/dist/cody-agent.js
- OK   Authentication setup correctly
- OK     endpoint set to: https://sourcegraph.internal.url.net
- OK Found correct binary versions: "1.0.6" = "1.0.6"
- OK   Sourcegraph Connection info: {
  access_token_set = true,
  endpoint = "https://sourcegraph.internal.url.net",
  sg_nvim_version = "1.0.6",
  sourcegraph_version = {
  build = "5.1.9",
  product = "5.1.9"
  }
  }
- ERROR Cody Auth Failed: nil
- ERROR sg.nvim has issues that need to be resolved

The report above seems to have all the relevant info, but please let me know if there is additional information that would be helpful.

Latest version I think will have a fix for this (checked with other server and solved the problem). Not all of the graphql query params I was using were live on all other servers (non-dotcom) which caused an error. Hopefully works now!

Unfortunately, I'm still seeing the same error log on sg.nvim 1.0.7

Same, still seeing the error. Will this require a server update if we're self-hosting our Sourcegraph instance?

Let me check when we added the Cody flag, perhaps it's more recent than I thought.

Do you have access to the API Console on your instance? Usually it's at https://sourcegraph.com/api/console I think.
Could you run this query:
query EnterpriseUserQuery {
  currentUser {
    id
    username
    codyProEnabled
  }
}

Maybe I just need to remove the codyProEnabled -- I'll test that right now

Ah, makes sense. Sorry about that. The new release is building right now and should be available in the next ~10 minutes or so. I removed that and hopefully the rest should work for you.

OK, I think you can try now -- hopefully this should work now! Thanks for the patience

That did the trick. Thanks TJ!
sg: require("sg.health").check()

sg.nvim report ~
- Machine: arm64, sysname: Darwin
- OK Valid nvim version: table: 0x0103d5b3b8
- OK Found `cargo` (cargo 1.68.2 (6feb7c9cf 2023-03-26)) is executable
-     Use `:SourcegraphDownloadBinaries` to avoid building locally.
- OK Found `sg-nvim-agent`: "/Users/jmaxwell/.local/share/nvim/site/pack/packer/start/sg.nvim/dist/sg-nvim-agent"
- OK Found `node` (config.node_executable) is executable.
  Version: '20.11.0'
- OK Found `cody-agent`: /Users/jmaxwell/.local/share/nvim/site/pack/packer/start/sg.nvim/dist/cody-agent.js
- OK   Authentication setup correctly
- OK     endpoint set to: https://sourcegraph.eng.qops.net
- OK Found correct binary versions: "1.0.8" = "1.0.8"
- OK   Sourcegraph Connection info: {
  access_token_set = true,
  endpoint = "https://sourcegraph.eng.qops.net",
  sg_nvim_version = "1.0.8",
  sourcegraph_version = {
  build = "5.1.9",
  product = "5.1.9"
  }
  }
- To manage your Cody Account, navigate to: https://sourcegraph.com/cody/manage
- OK Cody Account Information: {
  cody_pro_enabled = false,
  username = "jmaxwell"
  }
- OK sg.nvim is ready to run

Great!! Thanks for your patience, let me know if anything else comes up!


Treat cygwin as a Windows

To be more specific, I had errors with os.path.realpath. As it turned out, cygwin wasn't recognized as a Windows and thas was causing the errors.
This commit should fix most of other undiscovered issues with cygwin.
Also, it's better to keep the critical logic of recognizing the system in a single place.

Within fake_filesystem.py, how about makint it a private variable _is_windows?
Of course that means that the definition would have to be repeated in fake_filesystem_test.py, but I think that is acceptable in a test file.  How about adding is_windows to class fake_filesystem_test.TestCase?
Also, could you verify that all those tests really must be skipped in Cygwin?  Do some of the tests skipped for Windows actually pass on Cygwin?  I think you already know the answer to this.
Thanks for your help on this.

All tests pass, with the exception of testExpandUser (the "~root" bit fails).
After some tinkering with my original problem, it turned out that the issue with os.path.realpath is even bigger, and possibly not related to cygwin
The exception I'm getting is AttributeError: 'NoneType' object has no attribute 'error'
Pytest traceback is useless, even though I've added py and inspect modules to Stubber.SKIPMODULES set.
/home/Filip/renamer/renamer.py:30: in common_dir
    paths = [os.path.realpath(p) for p in paths]
/home/Filip/pyfakefs/fake_filesystem.py:1142: in foo
    ???
/home/Filip/.virtualenvs/renamer/lib/python2.7/posixpath.py:382: in realpath
    ???
/home/Filip/.virtualenvs/renamer/lib/python2.7/posixpath.py:407: in _joinrealpath
    ???

I've modified FakePathModule.__getattr__ function to wrap result in a exception-catching, traceback-printing decorator:
   def __getattr__(self, name):
     """Forwards any non-faked calls to os.path."""
     print name
     attr = self._os_path.__dict__[name]
     def foo(*a):
         print name, a
         try:
             result = attr(*a)
         except Exception as e:
             print "TRACEBACK"
             formatted_lines = traceback.format_exc().splitlines()
             print '\n'.join(formatted_lines)
             raise
         return result
     return foo

Here's the traceback:
realpath (u'bar',)
TRACEBACK
Traceback (most recent call last):
  File "/home/Filip/pyfakefs/fake_filesystem.py", line 1142, in foo
  File "/home/Filip/.virtualenvs/renamer/lib/python2.7/posixpath.py", line 382, in realpath
  File "/home/Filip/.virtualenvs/renamer/lib/python2.7/posixpath.py", line 407, in _joinrealpath
  File "/home/Filip/.virtualenvs/renamer/lib/python2.7/posixpath.py", line 143, in islink
AttributeError: 'NoneType' object has no attribute 'error'

Here's standard lib's posixpath.islink code:
def islink(path):
    """Test whether a path is a symbolic link"""
    try:
        st = os.lstat(path)
    except (os.error, AttributeError):
        return False
    return stat.S_ISLNK(st.st_mode)

I've then checked and confirmed that in this scope os is actually a None. At this point I'm totally clueless. What could be causing this?

I've fixed that issue and created a separate PR. See #41

I've added the changes you requested. Is everything okay now?

Nice job.  Pushed.


Update icons and location for the namespace icon

Wait until #9427 is done so that we don't have to port this over.

These changes are still in progress.

Pass verified in rancher v2.8-head commit ID 5cffa89

nav groups highlighted - done
sidenav - done
sidenav decoupled as standalone element - done


GoPlatform: Use libapp.so to preprocess the host

The go example has to use zig to create a prebuilt-platform. I have no idea how to install zig on the test-distributions. If you think, this is a useful change, could you help me to make the changes to install zig?

Not sure what the problem is on Ubuntu 20.04. I do have a machine with that OS, I'll try it on there tomorrow.


Improve performance of bidichk

We noticed of all the analyzers we have enabled in golangci-lint, the bidichk one was consuming the most time. This was a bit surprising, but I believe I've identified the reason for the performance issue.
The analyzer is iterating over analysis.Pass.Fset (which contains all imports including the go stdlib and module dependencies) in addition to the files found in the specified packages. It appears it should be updated to only run on analysis.Pass.Files instead.
Additionally, using Fset will mean that for files imported by multiple packages, the analyzer will process the same files multiple times.
After enabling a fix for this locally, the runtime of the analyzer dropped from 76.29s to 4.71s in our moderately sized project.

@pkwarren Thanks for opening this issue and already providing a PR. I am currently AFK. I will have a look at this next week.


Rework how we handle seed phrases in the examples

Currently, when multiple people run examples at the same time, they are likely to get sequence mismatch errors on the registration transaction. This will become more and more prevalent as we get more users.
One solution would be to force the users to enter their own seed phrase for these examples, but feel free to suggest other options.

+1 for forcing of the seed to be put in manually and also for enforcing a seed structure like 12 word mnemonic phrases or something similar

First part is handled in #260
enforcing seed structure will be handled separately.

Reopening because the examples PR is not yet merged.


provide an replicateWithTranslations function

Hi Dimitris
I've tried to implement a replicate function to the asgard cms. my main problem is now, that the 'locale' column is not a fillable column so it does not allow me to make the replication. i know i could allow this in the config, but that's a security risk and i will provide the duplicate function to all modules for asgard cms so everyone has it. i think it would be anyway helpfull if the the translatable module would provide this.
Or do you have any advice?
Cheers

Hey!
What do you mean by replication? Show some code.

well, i already tried many ways but here the probably most closest:
for example, $mymodel->replicate() doesn't replicate the translations.
so one way looked like that:
        $duplicatedEntity = $this->infobox->find($infoboxId)->replicate();
        //it replicates also the relation, but the id's and foreign key ids are already set to the origin so no change applied
        $translations = [];
        foreach($duplicatedEntity->translations as $translation)
        {

            $except = [
                $translation->getKeyName(),
                $translation->getCreatedAtColumn(),
                $translation->getUpdatedAtColumn(),
            ];

            $attributes = array_except($translation->getAttributes(), $except);

            $translations = [
                $InfoboxTranslation(attributes);
            ];
            with($duplicatedEntity)->setRawAttributes($attributes);

        }
        $duplicatedEntity->name = $request->get('code');
        $duplicatedEntity->code = $request->get('name');
        $duplicatedEntity->save();

The problem now here is, that the local column is not fillable.

Have you googled for this?
This is a generic laravel question. I didn't even notice there was a replicate() method :P
Are you eager-loading the translations first? (No idea if this will solve the issue)

Yeah of course ;)

You see, all already read articles.
As i wrote i tried several things, as well eager-loading. Loading is not the problem, the problem i can not save it from my controller, cause then i get a constrain because "locale" can not be empty and is not permitted cause it's not fillable. so it would makes sense that the translatable package provides it ;)

Thanks to @Propaganistas, a solution will come soon.

ah ok, so i'm looking forward to it :)

so, i've done it and made a PR for it ;)
https://github.com/dimsav/laravel-translatable/pull/199


Transfocator: Convert to ophyd-async

We should convert the i04 transfocator to ophyd-async. As discussed at https://github.com/DiamondLightSource/dodal/issues/399 the transfocator and f-switch are basically the same device. However, the i22 one does not have some of the features that the i04 one has. In doing this conversion we should try and make sure the two share as much code as reasonable. This may involve a bit of discussion with controls/scientists to get the features on i04's added to i22's IOC as well.
Acceptance Criteria

I04's transfocator no longer uses ophyd but instead uses ophyd-async

Discussed with @shihab-dls , as part of this issue, we will also document any changes required in EPICS in order to share code between i22's f-switch and the i04 transfocator


1195 extend temporalgraph api snapshot

fixes #1195

Good review! I realized your suggested changes.

The test is currently checking the functionality of subgraph again, I don't think this is necessary, as there is a snapshot test already. Other opinions on that?

The concept of unit test is to check every method and possibility. Since you do not know which change will be done in the future in these convenience API methods, we have to check, that a call of TemporalGraph#deletedId(a,b) returns a equal result to snapshot(new DeletedIn(a, b)) which in turn returns a equal result to callForGraph(new Snapshot(new DeletedIn(a, b)))


Unable to get the checksum due to errors in the Ansible

https://github.com/cloudalchemy/ansible-alertmanager/blob/e42e7ef1f551fe3ae018f0b8400a62e733189206/tasks/preflight.yml#L44
Mac OS 10.14.6 ssh into Linux CentOS Linux release 7.9.2009
Ansible Version
ansible [core 2.11.4]
  config file = None
  configured module search path = ['/Users/yoakum/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/yoakum/venv/ansible/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/yoakum/.ansible/collections:/usr/share/ansible/collections
  executable location = /Users/yoakum/venv/ansible/bin/ansible
  python version = 3.9.6 (default, Jun 29 2021, 04:45:03) [Clang 11.0.0 (clang-1<IP_ADDRESS>)]
  jinja version = 2.11.2
  libyaml = True

Errors:
TASK [alertmanager : Get checksum for amd64 architecture] **********************************************************************************************************************************************************************************************************************
fatal: [<IP_ADDRESS>]: FAILED! => {"msg": "template error while templating string: expected token 'end of print statement', got 'select'. String: {{ lookup('url', 'https://github.com/prometheus/alertmanager/releases/download/v' + alertmanager_version + '/sha256sums.txt',
 wantlist=True) | list select('contains', 'linux-' + go_arch + '.tar.gz') | list | first).split(' ')[0] }}"}
...ignoring

TASK [alertmanager : Checksum lookup error message] ****************************************************************************************************************************************************************************************************************************
fatal: [<IP_ADDRESS>]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'alertmanager_checksum_url' is undefined\n\nThe error appears to be in '/Users/yoakum/git/analytics-techops/analytics-bakery/ansible/roles/alertmanager/tasks
/preflight.yml': line 51, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Checksum lookup error message\n  ^ here\n"}

PLAY RECAP *********************************************************************************************************************************************************************************************************************************************************************
<IP_ADDRESS>              : ok=5    changed=0    unreachable=0    failed=1    skipped=2    rescued=0    ignored=1

I was able to get passed part of this issue by adding a '(' before the lookup and then adding a '|' after list. I also had to add the checksum url to the main ansible because it was not being set.
"{{ (lookup('url', 'https://github.com/prometheus/alertmanager/releases/download/v' + alertmanager_version + '/sha256sums.txt', wantlist=True) | list | select('contains', 'linux-' + go_arch + '.tar.gz') | list | first).split(' ')[0] }}"

Actually... there is a lot broken in that section (latest tag didn't work either). Here's what I had to have to get it to work with latest or a specified version
- block:
    - name: Get latest release
      uri:
        url: "https://api.github.com/repos/prometheus/alertmanager/releases/latest"
        method: GET
        return_content: true
        status_code: 200
        body_format: json
        user: "{{ lookup('env', 'GH_USER') | default(omit) }}"
        password: "{{ lookup('env', 'GH_TOKEN') | default(omit) }}"
      no_log: "{{ not lookup('env', 'MOLECULE_DEBUG') | bool }}"
      register: _latest_release
      until: _latest_release.status == 200
      retries: 5

    - name: "Set alertmanager version to {{ _latest_release.json.tag_name[1:] }}"
      set_fact:
        alertmanager_version: "{{ _latest_release.json.tag_name[1:] }}"
        alertmanager_checksum_url: "https://github.com/prometheus/alertmanager/releases/download/v{{ _latest_release.json.tag_name[1:] }}/sha256sums.txt"
  when:
    - alertmanager_version == "latest"
    - alertmanager_binary_local_dir | length == 0

- name: "Get checksum for {{ go_arch }} architecture"
  set_fact:
    alertmanager_checksum_url: "https://github.com/prometheus/alertmanager/releases/download/v{{ alertmanager_version }}/sha256sums.txt"
    alertmanager_checksum: "{{ (lookup('url', 'https://github.com/prometheus/alertmanager/releases/download/v' + alertmanager_version + '/sha256sums.txt', wantlist=True) | list | select('contains', 'linux-' + go_arch + '.tar.gz') | list | first).split(' ')[0] }}"
  when:
    - alertmanager_binary_local_dir | length == 0
  ignore_errors: true
  register: alertmanager_checksum_lookup


An example?

This really is not an issue, more of a question and hopefully a little help if it makes sense...
I am trying to figure out how to perform a cloud function and saw this in my search.  I assume this lib was built to make cloud code easier...?  or more functional..?
Here is what I am trying to do ~

For new user registration only save email, username and password in Users table
Any other information provided in the registration request (for example firstName, lastName, phone, sex, dateOfBirth, etc) stored in a UserProfile Collection
The new User will have a 1:1 relation with the new UserProfile as user_profile_object
The UserProfile will have a 1:1 relation with the new User as user_object

I can get 50% there creating profile and adding the profile to the User on beforeSave - but everything I try to get the User saved to the UserProfile fails.  Here is what I have currently
Parse.Cloud.beforeSave(Parse.User, function (request) {
  var Profile = Parse.Object.extend('UserProfile')
  var profile = new Profile()
  profile.set('first_name', request.object.get('first_name'))
  profile.set('last_name', request.object.get('last_name'))
  profile.set('full_name', request.object.get('first_name') + ' ' + request.object.get('last_name'))
  profile.set('email', request.object.get('email'))

  return profile.save(null, {
    useMasterKey: true
  }).then(function (userProfile) {
    request.object.set('user_profile_object', userProfile)
    request.object.unset('first_name')
    request.object.unset('last_name')
  })
})

which returns to the client...
{
	"objectId": "V3DPPRR1MGtC",
	"username": "test1",
	"email"<EMAIL_ADDRESS>	"user_profile_object": {
		"__type": "Pointer",
		"className": "UserProfile",
		"objectId": "NmlaleRPgC4N"
	},
	"emailVerified": true,
	"createdAt": "2018-09-11T16:55:38.387Z",
	"updatedAt": "2018-09-11T16:57:26.186Z",
	"ACL": {
		"*": {
			"read": true
		},
		"V3DPPRR1MGtC": {
			"read": true,
			"write": true
		}
	},
	"sessionToken": "r:bc33da9a4dce66c6a2b4659a5083504d"
}

what I would like returned is:
{
	"objectId": "V3DPPRR1MGtC",
	"user_profile_object": "NmlaleRPgC4N"
	"emailVerified": false,
	"createdAt": "2018-09-11T16:55:38.387Z",
	"updatedAt": "2018-09-11T16:57:26.186Z",
	"sessionToken": "r:bc33da9a4dce66c6a2b4659a5083504d"
}

I am putting time in trying to reason cloud code and would very much welcome something a little more organized and clearer.  Does your lib facilitate what I am looking for above?

Hello!
Well, this library helps you organize a little bit more the Cloud Code on your Parse Server, defining your beforeSave, afterSave, beforeDelete and afterDelete functions in a class that can be extended and use addons.
That said, this class definitely could help you do what you are trying to do, however your question has to do more with the way you program with parse-server and not with parse-server-addon-cloud-class
Regarding your code, I see that every time you save your user you create a new UserProfile object, which will end up in you having lots of UserProfile records only for one user and I don't think that is exactly what you want.
You could avoid creating new UserProfile objects every time by doing the following change in your code:
var profile = request.object.get('user_profile_object') || new Profile();

In your case, I understand that you want to also have an user_object key in the user profile as a 1:1 relation. Please consider that the objects that hit the beforeSave function on your Parse Server don't always have an id, because some of them might not be already in the database at that point, so if you create a relation in the way you are trying to do, then you can expect to have Parse errors telling you that You cannot create a pointer to an unsaved Parse.Object.
What I would to is to split this functionality between beforeSave and afterSave, wich is accomplishable by doing the following and using this library (untested code):
const { ParseCloudClass } = require('parse-server-addon-cloud-class');

class MyCustomUserClass extends ParseCloudClass {
  async processBeforeSave(request) {
    const user = request.object;
    const profile = user.get('user_profile_object') || new Parse.Object('Profile');

    profile.set('first_name', user.get('first_name'));
    profile.set('last_name', user.get('last_name'));
    profile.set('full_name', user.get('first_name') + ' ' + user.get('last_name'));
    profile.set('email', user.get('email'));

    return profile.save(null, {
      useMasterKey: true,
    }).then((userProfile) => {
      user.set('user_profile_object', userProfile);
      user.unset('first_name');
      user.unset('last_name');

      return user;
    });
  }

  async afterSave(request) {
    const user = request.object;
    const profile = user.get('user_profile_object');

    profile.set('user_object', user);
    return profile.save(null, { useMasterKey: true })
      .then(() => {
        return user;
      });
  }
}

An async version of it would be:

class MyCustomUserClass extends ParseCloudClass {
  async processBeforeSave(request) {
    const user = request.object;
    const profile = user.get('user_profile_object') || new Parse.Object('Profile');

    profile.set('first_name', user.get('first_name'));
    profile.set('last_name', user.get('last_name'));
    profile.set('full_name', user.get('first_name') + ' ' + user.get('last_name'));
    profile.set('email', user.get('email'));

    // Save the profile (async version)
    await profile.save(null, { useMasterKey: true });

    user.set('user_profile_object', profile);
    user.unset('first_name');
    user.unset('last_name');

    return user;
  }

  async afterSave(request) {
    const user = request.object;
    const profile = user.get('user_profile_object');

    profile.set('user_object', user);
    await profile.save(null, { useMasterKey: true });

    return user;
  }
}

Please take into account that as parse-server-addon-cloud-class lets you create addons, you can create this functionality as an addon and publish it on npm for sharing it with others or using it on your own projects later. You would do this:
class MyCustomUserClass extends ParseCloudClass {
  async processBeforeSave(request) {
    const user = await super.processBeforeSave(request);
    const profile = user.get('user_profile_object') || new Parse.Object('Profile');

    profile.set('first_name', user.get('first_name'));
    profile.set('last_name', user.get('last_name'));
    profile.set('full_name', user.get('first_name') + ' ' + user.get('last_name'));
    profile.set('email', user.get('email'));

    // Save the profile (async version)
    await profile.save(null, { useMasterKey: true });

    user.set('user_profile_object', profile);
    user.unset('first_name');
    user.unset('last_name');

    return user;
  }

  async afterSave(request) {
    const user = await super.afterSave(request);
    const profile = user.get('user_profile_object');

    profile.set('user_object', user);
    await profile.save(null, { useMasterKey: true });

    return user;
  }
}

and then publish it on npm as parse-server-addon-cloud-<something>

You rock!
So here is the cloud code I tried to implement...
const {
  ParseCloudClass
} = require('parse-server-addon-cloud-class')

class UserProfile extends ParseCloudClass {
  async processBeforeSave (request) {
    const user = request.object
    const profile = user.get('user_profile') || new Parse.Object('Profile')

    profile.set('first_name', user.get('first_name'))
    profile.set('last_name', user.get('last_name'))
    profile.set('full_name', user.get('first_name') + ' ' + user.get('last_name'))
    profile.set('email', user.get('email'))

    return profile.save(null, {
      useMasterKey: true
    }).then((userProfile) => {
      user.set('user_profile', userProfile)
      user.unset('first_name')
      user.unset('last_name')

      return user
    })
  }

  async afterSave (request) {
    const user = request.object
    const profile = user.get('user_profile')

    profile.set('user_object', user)
    return profile.save(null, {
      useMasterKey: true
    })
      .then(() => {
        return user
      })
  }
}

The response:
{
	"objectId": "SWSURrZJQ6wD",
	"createdAt": "2018-09-12T17:40:04.060Z"
}

But when I check the data browser (after reload) there is no associated UserProfile class row created and the first_name and last_name were inserted into the new User record.
  We should connect.  Also, a very good friend and wizard developer lives in Bogata.  Check out https://github.com/kevoj and if you are in same location you should think about contacting him...

PS I changed only MyCustomClass to UserProfile and param user_profile_id to user_profile otherwise everything is the same.  I also tried the async version with same results

What I don't see is how Parse knows that it is supposed to call this service when a new User is created.  The "old" way was Parse.Cloud.beforeSave(Parse.User, function (request)

Helloo!
Well I will definetely contact kevoj, thank you!
I will have to create a new Parse server and test your code. Maybe you have your code as a public repo to share?
To call the service when a new User is created you should write this in the Cloud Code's main.js file:
// Import the library
import { ParseCloudClass } from 'parse-server-addon-cloud-class';

// Import the class you created
import { UserProfile } from './<path-to-the-class>';

// Create an instance of it
const userProfile = new UserProfile();

// Connect it to the Parse _User class
ParseCloudClass.configureClass(Parse, '_User', userProfile);

Now, you could be willing to have extra functionalities on your _User class, so you could create another class that does some extra processing and connect both of them via addons. Let's see:
// Import the library
import { ParseCloudClass } from 'parse-server-addon-cloud-class';

// Import the classes you created
import { UserProfile } from './<path-to-the-class>';

// Imaginary class created by you that connects any user
// to a mailchimp list on afterSave
import { UserToMailchimp } from './<path-to-the-class>';

// Create the instances
const userProfile = new UserProfile();
const userToMailchimp = new UserToMailchimp();

// Connect both classes through addons
userProfile.useAddon(userToMailchimp);

// Connect to the Parse _User class
ParseCloudClass.configureClass(Parse, '_User', userProfile);

In this case, you would have both functionalities working. You could create the UserProfile you are needing, and then send the user to mailchimp. This means that you can grow in functionalities creating new classes that extend ParseCloudClass and test them separately.

A complete working example can be found here!! 😄
https://github.com/owsas/parse-cloud-class-example

AWESOME!
I was fiddling around with it yesterday, get the gist of it but then got sidetracked on another requirement I have that Parse seems to be lacking that if I cannot solve may have to go another direction.  I am quite surprised no one has addressed this outside a few references in the git issue.   Maybe another lib you can evaluate, this will facilitate multi-tenant and boost Parse security?
Basically, In Class Level Permissions (CLPs) you can fine-grain control access to create, get, find, update, delete, add field.  ACLs are basically read/write setup to users (pointers) or roles.  I need to have CRUD level permission controls - a blanket WRITE and READ is not sufficient so the way I could do it is through CLPs.  I also want to close off any PUBLIC access to my classes for increased security.
My example use case is when a new company (tenant) is created in Parse I can setup default Roles - 1) ADMIN (full CRUD) 2) Create Only 3) Read Only 4)Update Only 5) Delete only.  Now when the Admin logs in he can create a User and assign them to Admin ROLE for full CRUD or can assign lets say…Update only.  Another user can be assigned to READ role.  Then the admin can assign the ROLES to the available classes and the Users assigned to those roles will have the restricted permissions for that Class.  For example a User can be assigned to the READ role for Accounts Class and also assigned to the Create and the Update Roles for Products Class (but not delete which is what the current WRITE ACL will give them).
Anyway, throwing this out there if you are the type that like solving these issues…I will go through your new example and report back results hopefully today.  I appreciate you Juan!

On Sep 14, 2018, at 11:38 AM, Juan Camilo Guarin Peñaranda<EMAIL_ADDRESS>wrote:
A complete working example can be found here!! 😄
https://github.com/owsas/parse-cloud-class-example https://github.com/owsas/parse-cloud-class-example
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/owsas/parse-cloud-class/issues/2#issuecomment-421398228, or mute the thread https://github.com/notifications/unsubscribe-auth/AjVHtbZsmya-r9tMCVH2diDGcDbPD-_Kks5ua82NgaJpZM4WjzCW.

Helloo I'm back!
Well, I have had a lot of work to do and I am coming back to this issue. Well, in your case you may want to create new Parse.Roles with those CREATE, READ, UPDATE, and DELETE names when you create a new company. For instance, on afterSave on Company, you create the roles for that object, with names like Company-${company.id}.
Then, you could write a new addon using parse-server-addon-cloud-class that checks if the request.user is linked in the users relation and throw errors on processBeforeSave, processBeforeDelete, beforeFind, and others.
Hope this helps,
Juan


drone: update fetch operation before build

Update the build flow of drone

@mergifyio backport v0.5.x


Formatting of zero duration returns empty string

Steps to reproduce
Default formatter returns just "P":
iex> Timex.Duration.zero |> Timex.Format.Duration.Formatters.Default.format
"P"

Humanized formatter returns just empty string:
iex> Timex.Duration.zero |> Timex.Format.Duration.Formatters.Humanized.format
""

Description of issue
This probably should be more informative. I also took a look at specification and ISO-8601 mandates at least one element for a zero duration (see <IP_ADDRESS>.c - page 21):

If the number of years, months, days, hours, minutes or seconds in any of these expressions equals zero, the number and the corresponding designator may be absent; however, at least one number and its designator shall be present.

Hi here! I've been looking around for a chance to contribute to the project, so if it's fine with you guys I'll open PR taking care of this issue.
Thanks! :)


2966 before response hook

Implement before_response and before_serve_file EPI hooks.
These hooks are useful in following cases:

to inject vendor specific headers
to inject vendor keys into json objects returned to client
to override return code

This is a replacement PR for #133

+1, but I think we can live without respond_.

+1

+1


New package: Migrations v1.0.0

Registering package: Migrations
Repository: https://github.com/JuliaServices/Migrations.jl
Created by: @quinnj
Version: v1.0.0
Commit: 4d1d9fe86d50db7bbe749af34284985354c85c33
Reviewed by: @quinnj
Reference: https://github.com/JuliaServices/Migrations.jl/commit/4d1d9fe86d50db7bbe749af34284985354c85c33#commitcomment-137310063

Migrations might be little bit too general as a package name. Can I suggest DatabaseMigrations?

Replaced by https://github.com/JuliaRegistries/General/pull/99127


Unexpected '__typename not found on object'

Hi, possibly related to https://github.com/morpheusgraphql/morpheus-graphql/issues/493
I got around to using the changes for this feature. They are compiling as expected, however now I am getting a runtime error.
My query looks like:
defineByDocumentFile
  "../resource/minimal-github.graphql"
  [gql|
    query FetchRepoFile ($repoOwner: String!, $repoName: String!, $expression: String!) {
      repository(name: $repoName, owner: $repoOwner) {
        object(expression: $expression) {
          ... on Blob {
            isTruncated
            text
          }
        }
      }
    }
  |]

You can see the schema I am using here https://github.com/AlistairB/morpheus-repro/blob/master/minimal-github.graphql .
The error I am getting: Error in $.data.repository.object: key \"__typename\" not found on object
Running this in the github graphql explorer, eg. this query:
query {
  repository(name: "react", owner: "facebook") {
    object(expression: "af219cc6e6c514099a667ffab4e2d80c5c0c1bcc:.nvmrc") {
      ... on Blob {
        isTruncated
        text
      }
    }
  }
}

produces this response:
{
  "data": {
    "repository": {
      "object": {
        "isTruncated": false,
        "text": "v12.16.2\n"
      }
    }
  }
}

I can include __typename in the query and will get back in the response "__typename": "Blob" (via the github graphql explorer).
Adding __typename to the query that morpheus is using causes compile time errors eg. Error: \"cant find field DataInterface.
Is this enough info? If not I can set up a repro in https://github.com/AlistairB/morpheus-repro

hi @AlistairB. please checkout #511

Thanks! This works if I change the query to:
defineByDocumentFile
  "../resource/minimal-github.graphql"
  [gql|
    query FetchRepoFile ($repoOwner: String!, $repoName: String!, $expression: String!) {
      repository(name: $repoName, owner: $repoOwner) {
        object(expression: $expression) {
          __typename
          ... on Blob {
            isTruncated
            text
          }
        }
      }
    }
  |]

This works for me as a solution.
However, if I don't add __typename to the query it still fails with the same error. This is a bit unintuitive since I don't need __typename for my purposes, but morpheus seems to require it. I think ideally morpheus would request __typename itself if it needs it even if it isn't in the query.
I could be wrong though. Happy to close if you think this is the right solution.

@AlistairB you are right, i fixed that too. please checkout #512

Unfortunately this is still producing the same error unless I manually include __typename.
I have updated master on https://github.com/AlistairB/morpheus-repro to reproduce the issue.
As per https://github.com/AlistairB/morpheus-repro/blob/master/src/Lib.hs#L50-L52 , you will need to create a github personal access token. Then you can reproduce the issue with stack run.

Hi, I've been playing with this a little bit more and noticed another minor issue. In the morpheus-repro example, the master version of morpheus will generate the following type:
data RepositoryObjectGitObject
  = RepositoryObjectGitObject {__typename :: Text} |
    RepositoryObjectBlob {__typename :: Text,
                          isTruncated :: Bool,
                          text :: (Maybe Text)}
  deriving Generic
  deriving Show
  deriving Eq

A sum type with record accessors is considered a bit of an anti-pattern. This is because isTruncated is now a partial function. ie. isTruncated (RepositoryObjectGitObject "blah") will compile, but will error at runtime. The data type will cause a ghc warning if compiled with -Wpartial-fields.
I pushed a new commit to https://github.com/AlistairB/morpheus-repro with the warning enabled to demonstrate the issue.
One solution is just to exclude the accessors, but this would get ugly if you had a lot of fields returned. I think the ideal solution would be something like:
data RepositoryObjectGitObject
  = RepositoryObjectGitObject RepositoryObjectGitObjectValues
  | RepositoryObjectBlob RepositoryObjectBlobValues
  deriving (Generic)
  deriving (Show)
  deriving (Eq)

data RepositoryObjectGitObjectValues = RepositoryObjectGitObjectValues {repositoryObjectGitObjectValues__typename :: Text}

data RepositoryObjectBlobValues = RepositoryObjectBlobValues
  { repositoryObjectBlobValues__typename :: Text, -- actually we need to prefix this now as there can't be overlapping `__typename`. Unless DuplicateRecordFields is enabled.
    isTruncated :: Bool,
    text :: (Maybe Text)
  }

Anyway, as mentioned I think this is minor. It could be a separate issue (I can create if you want), or not worried about. Just thought I'd mention it.

hi @AlistairB ,

Hi, I've been playing with this a little bit more and noticed another minor issue. In the morpheus-repro example, the master version of morpheus will generate the following type:

please address it in different issue :)

Unfortunately this is still producing the same error unless I manually include __typename.

i checked this out. i will address this problem later, as long as it is not as trivial as i thought

finally fixed it. see #773


JSON in Narrate/Chat Feature

It would be good to be able to embed json into a narrate command - like done with the /tellraw command (Add tooltips to text and add click events)
This would allow for a clickable menu in chat - with the click event being able to execute a server or denizen command (zap around an interact script simply by clicking for example)
Currently we need to use execute as_server to do this and default json click event runs the command as the player who clicked it - which isnt the most efficient - and doesn't allow for easy integration of denizen commands into the json data
With Denizen JSON could add an option to execute the command when the player clicks the item in chat, as the server, or the player.
/tellraw @p ["",{"text":"Test","clickEvent":{"action":"run_command","value":"Hello"},"hoverEvent":{"action":"show_text","value":{"text":"Clicking this makes you say Hello"}}}]

We have plans to support this in a significantly less stupid way that frippin JSON support.

Honestly MCL is so solid we're realistically just going to use that as the official supported option for D1 stuff at the moment https://github.com/AnthonyAMC/Public-Denizen-Scripts/blob/master/MessageConstructors.yml


[Error Report] there is an unexpected error for ubuntu build test

I got an error at the CI test and want to share it.
You can check what it is at below PR.
https://github.com/nnsuite/nnstreamer-example/pull/85
The main point is the path of nnstreamer package for ubuntu-xenial.
...

Err http://ppa.launchpad.net/nnstreamer/ppa/ubuntu xenial/main amd64 nnstreamer amd64 <IP_ADDRESS>-0~201911070953~ubuntu16.04.1
  404  Not Found [IP: <IP_ADDRESS> 80]
Err http://ppa.launchpad.net/nnstreamer/ppa/ubuntu xenial/main amd64 nnstreamer-dev amd64 <IP_ADDRESS>-0~201911070953~ubuntu16.04.1
  404  Not Found [IP: <IP_ADDRESS> 80]
E: Failed to fetch http://ppa.launchpad.net/nnstreamer/ppa/ubuntu/pool/main/n/nnstreamer/nnstreamer_<IP_ADDRESS>-0~201911070953~ubuntu16.04.1_amd64.deb: 404  Not Found [IP: <IP_ADDRESS> 80]
E: Unable to correct for unavailable packages

...

:octocat: cibot: Thank you for posting issue #578. The person in charge will reply soon.

Do $ sudo apt update

@myungjoo
It works :)


FileIO, BufferedWriter left unflushed when ipy exits

Running the following code with ipy, will get an empty file test.txt, while with CPython, the file will have one byte 'a'

import io
out = io.FileIO('test.txt', 'w')
out.write(b'a')

Similar case but using BufferedWriter:

import io
out = io.TextIOWrapper(io.BufferedWriter(io.FileIO('test.txt', 'w')))
out.write('a')

Case involving stdio:

The following powershell command output nothing,
PS C:\Users\james\proj\ironpython3> .\bin\Debug\netcoreapp3.1\ipy.exe -c "import sys;sys.stdout.write('text')"
PS C:\Users\james\proj\ironpython3>

and the following powershell command could output the "text"
PS C:\Users\james\proj\ironpython3> .\bin\Debug\netcoreapp3.1\ipy.exe -c "import sys;sys.stdout.write('text\n')"
text
PS C:\Users\james\proj\ironpython3>

For the TextIOWrapper it seems like flush is called by __del__:
import io
class Test(io.TextIOWrapper):
    def __del__(self):
        pass
out = Test(io.BufferedWriter(io.FileIO('test.txt', 'w')))
out.write('a')

Probably similar for io.FileIO.  For writing to standard streams it looks like CPython calls flush on sys.stdout and sys.stderr during Py_FinalizeEx. See https://github.com/python/cpython/blob/6c065594c720fdd4783a4284cb9f2eebcb2c10bd/Python/pylifecycle.c#L480-L502

sys.stdout is TextIOWrapper(BufferedWriter(FileIO(Console.OpenStandardOutput()))) and sys.stderr is TextIOWrapper(BufferedWriter(FileIO(Console.OpenStandardError())))
So I think if TextIOWrapper or BufferedWriter could flush at exit, sys.stdout and sys.stderr should be good.
stdio are created here
https://github.com/IronLanguages/ironpython3/blob/f32bf73f364c176db5cbbb6cefc6ec5f9fc92934/Src/IronPython/Runtime/PythonContext.cs#L1830-L1834
and
https://github.com/IronLanguages/ironpython3/blob/f32bf73f364c176db5cbbb6cefc6ec5f9fc92934/Src/IronPython/Modules/_io.cs#L2847-L2859


Connector silently fails to generate messages when schema is too long

Hi,
When setting a large json schema either in schema.string or in schema.filename file, connector does not send any message.
No errors are raised, just messages are  not generated.
Is there a known size limit in schemas that can be handled by datagen connector?
It used to work with 0.3.3 and does not work anymore from 0.4.x onward
Kind regards,
Olivier

I can reproduce this issue, but it's not related to schema size, it is happening when "regex": "[a-zA-Z0-9]{x}": where x>15:
        {
            "name": "MY_STRING",
            "type": {
                "type": "string",
                "arg.properties": {
                    "regex": "[a-zA-Z0-9]{16}"
                }
            },
            "default": ""
        }

@vdesabou any workaround for this?

@guitcastro This was fixed by https://github.com/confluentinc/kafka-connect-datagen/pull/99 and available in 0.5.3 release.
This issue can be closed


[SILOpt] Reject existentials in AnyObject specialization application

Also allow this feature to be enabled in non-assert compilers

@swift-ci smoke test


Can't disable taggable option

Reproduction Link
https://jsfiddle.net/oaue3y2r/
Steps to reproduce
Set taggable option to "false"
Expected behaviour
The documentation states that taggable option default value is false, and i expect that they will dispaly by setting taggable option to true.
Actual behaviour
The documentation states that taggable option default value is false, but when i initalise vue multiselct without this option tags is apear. I can't disable tags appearance by setting taggable option to false.

Having the same issue here. I've been banging my head against a wall for a week trying to figure this out.

Did anyone figure this out?

same here

@sergeyzlobin taggable prop is not for tag appearance. It is for allow user to create their own tags if not available in option.
If you looking for changing appearance of selected tags than look into https://github.com/shentao/vue-multiselect/issues/1343


Update to 3.08

Checklist

[X] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Updates to latest version, bringing some more plugins so it's in sync with defaults. Future work on constructor will require this version for EXE signing.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

makensis -VERSION does not error on Linux, but doesn't print the version either.
Running it locally with the downloaded artifact does print something:
$ makensis -VERSION
v07-Jul-2022.cvs(nsis)

It's using the build date I guess?

The issue was already present in 3.06.1, btw:
$ makensis -VERSION
v22-Sep-2020.cvs(nsis)

Explicitly passing VERSION=${PKG_VERSION} works!
$ makensis -VERSION
v3.08

Ready for review @conda-forge/nsis!

Is this still blocking on: https://github.com/conda/constructor/issues/526

I issued repodata patches for constructor, but they were not merged yet. See https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/300

@conda-forge-admin, please rerender

@jakirkham @mbargull - this is ready for review whenever you have time :D

Gentle ping @conda-forge/nsis :D

@conda-forge-admin, please rerender

Looks like everything is in order. I'll merge to unblock the constructor release. The previous builds of constructor are pinned to not use 3.08 so this shouldn't break anything in the unlikely event something is off.