Cellery list ingress is not working for web cell

Followed below steps:

Executed cellery-init
Executed cellery build,  cellery run and made sure the application is working.
cellery list instances

 Cell Instances:
      INSTANCE                  IMAGE             STATUS                GATEWAY                 COMPONENTS           AGE
 ------------------- --------------------------- -------- ------------------------------------ ------------ ----------------------
  my-project100euoa   sinthuja/my-project:1.0.0   Ready    my-project100euoa--gateway-service   1            6 minutes 57 seconds

Executed cellery list ingress  my-project100euoa and the result was empty.

Cell Instances:
      INSTANCE                  IMAGE             STATUS                GATEWAY                 COMPONENTS           AGE
 ------------------- --------------------------- -------- ------------------------------------ ------------ ----------------------
  my-project100euoa   sinthuja/my-project:1.0.0   Ready    my-project100euoa--gateway-service   1            6 minutes 57 seconds

Cellery list ingress  worked, and when I pass the instance it doesn't work as mentioned before.
  COMPONENT   INGRESS TYPE   INGRESS CONTEXT   INGRESS VERSION   INGRESS PORT   GLOBALLY EXPOSED
 ----------- -------------- ----------------- ----------------- -------------- ------------------
  hello       web            /                                   80             True

Fixed in https://github.com/wso2-cellery/sdk/pull/793/files


[chakracore] Fix Linux build (/lib, /bin)

Lib goes to bin folder leading to link error on Linux. The PR fixes that.
Inspired by https://github.com/skyrim-multiplayer/skymp/pull/1290

Shared libraries should also be moved into lib.

hope you're right thanks

The file structure should be that both lib and bin are included under the debug folder. Reference port libgta

The file structure should be that both lib and bin are included under the debug folder. Reference port libgta

What? Mind you, this is linux.

@FrankXie05

#28689

There are two of them now. Merge what you like better.

The file structure should be that both lib and bin are included under the debug folder. Reference port libgta

What? Mind you, this is linux.

Sorry, I missed this.

Approve this PR. :)

#28689

closing in favor of https://github.com/microsoft/vcpkg/pull/28689


Update index.rst

Included a note about deployment to Apache/mod_wsgi gotcha.

This caused me some frustration as I'm not a deployment expert by any stretch, so thought this note might save someone googling around.


Handle multiple of the same components when loaded on the same page

Pretty sure this is working. Closing until told otherwise.


Add new recognition models

Add new recognition models

@felixjunghans Sorry, but can you help me update this

@AnNguyen98 give me ~ 1 hour. I will release a new Version on pub.dev soon.

@felixjunghans Thank you so much!


Readme was updated

And I would suggest to start all words "Company" with a capital letter because it is a name of an entity.

I have just realized that ", который был описан выше" is not correct even in the original. So, I think that ", as written above" altogether. It is obvious that if it is an alternative way than a standard way must already have been provided.


make indexing faster (not an issue)

Hello there. I am trying lunr to index ~40.000 documents. It gets 10x slower when cursor is at about 25.000. Any suggestion on how to speed up this process?

Closing. A number of changes have been introduced that should make indexing faster. There is always scope to make it faster still, but I would need some benchmarking/profiling to help identify the specific issues in this case. Please do re-open if you are still having problems though.


Update README.ru.md

Is it ok?

@DoomzD, I'll try to get a review for this. Please gimme some time for that.


Adding images to Cloze Questions

Is there a way to add images to cloze questions with Anki-remote-decks? It wasn't working when I tried. Thanks!

I will have to have a look. I would have thought it would have worked by default
I assume you mean to add the image in as the cloze?

Actually I was hoping to see if there was a way to make an image appear
after you’ve answered the card but not as part of the cloze.
On Tue, Jul 14, 2020 at 11:42 AM c-okelly<EMAIL_ADDRESS>wrote:

I will have to have a look. I would have thought it would have worked by
default
I assume you mean to add the image in as the cloze?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/c-okelly/anki-remote-decks/issues/65#issuecomment-658346993,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQIWMI6RHH5NLKT6NU3XLLTR3SRH5ANCNFSM4OYZPIBA
.

--
Adam C. Kenney

It should be possible. I will look into it this afternoon and give you an update either how to do it or when it will be fixed

Thank you so much!
On Wed, Jul 15, 2020 at 9:19 AM c-okelly<EMAIL_ADDRESS>wrote:

It should be possible. I will look into it this afternoon and give you an
update either how to do it or when it will be fixed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/c-okelly/anki-remote-decks/issues/65#issuecomment-658860460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQIWMI6FRJZ6NWLK4AMZKGTR3XJJLANCNFSM4OYZPIBA
.

--
Adam C. Kenney

Ye there is def a bug here.
It should have worked to add the image to the "Extra" field but did not for some reason. Am looking into it

Thanks!
On Thu, Jul 16, 2020 at 1:50 PM c-okelly<EMAIL_ADDRESS>wrote:

Ye there is def a bug here.
It should have worked to add the image to the "Extra" field but did not
for some reason. Am looking into it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/c-okelly/anki-remote-decks/issues/65#issuecomment-659664676,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQIWMI5QW2Z7T2TZW7TOMSTR35RXPANCNFSM4OYZPIBA
.

--
Adam C. Kenney

So it turns out it is actually pretty difficult to get the bullet points to work as expected in Google sheets.
This format does work:

When was Dublin founded {{c1::1204}}
# type=Cloze

Some extra info
An image

next question

answer

In order to get the # type=Cloze correctly on the next line though you need to avoid breaking the current list. It means you need to do something like this:

When was Dublin founded {{c1::1204}}
# type=Cloze

Some extra info
An image

And then delete the bullet point. Its quite convoluted. I'm going to have a think about a better solution but currently the # type=Cloze does need to be on it's own line due the fact a line break of some type is needed for Cloze card in order to know where they end.
Once I have done a bit of testing for a better solution I will update

Will be fixed by current pull request once it builds.
I'm not really sure about adding such one off usecases but possibly to be revisited when more appear

released in V1.7.0


Migrate from alchemy/zippy to chumper/zipper

Alternative fix for #39 (move to new zip library)

Coverage increased (+0.02%) to 86.762% when pulling 1138715 on aphofstede:new-zip-library into d363405 on frictionlessdata:master.

Fixed.

@OriHoch Is this worth merging or wanna wait for zippy to be fixed?

thanks


C++20: u8string and char8_t literals

Hi, great work.
Are there any plans to adapt the proposed reference implementation to use std::u8string, boost::text::u8string and char8_t literals instead of std::string, boost::text::string and char literals, if u8 defaults to char8_t literals?

Yes, although there needs to be widespread support for those before I add them.  There should probably be conversions from char8_t * and std::u8string to boost::text::text for instance.

Fixed by 79b1a5536e86a8cb3b .

Great to see you are investing further in this long required library. I followed the discussions about review of text lib on boost mailing list and hoped to see getting it accepted. Thanks for your effort.


Download same titled videos

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.09.27. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.09.27

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

I am trying to download all the videos of one of huge channel and converting to mp3. It has more than 3 tousand videos. But there is a problem. There is multiple videos with same title. I want to download all of them.
For example there are more than one videos with title "Brand X Music - Retribution". I want to save them like:

Brand X Music - Retribution
Brand X Music - Retribution(1)
Brand X Music - Retribution(2)

I didn't make it. Which parameter do I have to use. Thank you.

This works out of the box since default filename output template includes video id to provide uniqueness. Don't override default output template.

I have to override because I don't want to see video id in the title. Is there any workaround?

%(playlist_id)s, %(autonumber)s.


Fixes #53: corrected legend_labels to labels to fix kuramoto demo

Renames "legend_labels" in the 4th cell of kuramoto demo to "labels" for kuramoto demo to work.

@sameerashahh please edit your pull request to match the guidelines in CONTRIBUTING.md https://github.com/DynaDojo/dynadojo/blob/main/CONTRIBUTING.md#pull-request-checklist


Flicker after enabling the library

I've just discovered and installed this library and this is what happens for me:
I create two 250px images, one visible and one hidden.

I use the following script to switch them on mouse over:
$('body').on('mouseenter', '.my-link', function() {
    $('.first').addClass('hide');
    $('.second').addClass('show');
});

$('body').on('mouseleave', '.my-link', function() {
    $('.first').removeClass('hide');
    $('.second').removeClass('show');
});

This is the CSS:
.second { opacity: 0; }
.show { opacity: 1; }
.hide { opacity: 0; }

This works perfectly well. However, I wanted to add lazysizes because:

I have many images on that page and I only want to load them as user gets near them.
The grid of images has "large/small thumbnails" toggle and some JavaScript has to update "sizes". This library seems to be what I need.

When I set lazyload and data-sizes="auto" to both images then on every mouseenter:

the first image disappears,
then there is nothing for about 50ms (just white space),
and then the second appears.

The flicker lasts maybe 50-100ms but it's definitely visible and it's permanent. No matter if the second image is already loaded or not the flicker always happens. What can I do?

Can you make a test case? I doubt, that this is the right JS or the right CSS. The JS would change classes on all elements not only the hovered once.
In case you are using additionally display: none on the image that is hidden, this is the explanation for the time you need to wait. You can use position:absolute; visibility: hidden; instead to improve the situation.
But I really need a test case to see what is happening there. You can use codepen, jsfiddle, jsbin...

Please re-open with more details, if this did not help you.


[Bug] Nodes in network crawler mode are slow to accumulate peers

Network crawler nodes are currently slower to accumulate peers than regular nodes or bootnodes, which is the opposite of their desired behavior.

Fixed by https://github.com/AleoHQ/snarkOS/pull/997.


xcode 12 issue

starscream version : 4.03
xcode version : 12.0

I am also facing this issue, is there any solution?

Thank you


USe tok and ettu from TomNomNom

Hey the other day, while watching tomnomnom's stream with nahmsec. Tom introduced to a cool tool tok which can be used to create custom wordlists from the enumerated subdomains and use it for subdomain permutation using something like ettu.
Super awesome tools, I leave a link to both of them can be really handy for subdomain permutaions.
https://github.com/tomnomnom/hacks/tree/master/tok
https://github.com/tomnomnom/hacks/tree/master/ettu

Imho gotator for permutations and puredns for DNS resolving/bruteforcing are much better tools with a lot of useful features


can UTCDateTime be replaced with Instant?

(Spun off from #59)

Ah, so you are using UTCDateTime as a substitute for Instant

The whole discussion on whether to have Instant or not probably belongs in its own issue. The fact that most modern libraries have this, is a strong signal for its usefulness. Having both UTCDateTime and Instant would probably be unnecessary

I can see some value in UTCDateTime, because it captures an  intent of the developer, and it's more ergonomic than OffsetDateTime(offset=0).
Can UTCDateTime be replaced with an Instant class? The Instant class is a wrapper around an "epoch seconds". It provides type-safety and encapsulation. There should be an unambiguous 1-to-1 conversion between an Instant and UTCDateTime.
Here are some examples from other libraries:

java.time has an Instant class that wraps a long (seconds) and an int (nanoseconds)

"the class stores a long representing epoch-seconds and an int representing nanosecond-of-second,"

NodaTime implements an Instant class

(I don't know how to access its implementation source code)
it holds at least an Int64 as "milliseconds from UNIX epoch"

GoLang provides a Time struct

it wraps 3 values: a uint64, an int64, and a pointer to a Location (i.e. TimeZone) object
Go's Time class contains a Location object, which makes it different than the Instant class in java.time and NodaTime
Go does not have a DateTime class hierarchy. Everything is derived from the Time object

C++ has std::chrono::time_point which is implemented as a std::chrono::duration

I have no idea how it is actually implemented under the covers

I don't know, I can see both Instant and UTCDateTime being useful, because they capture slightly different things, and the ergonomics for the end-users are slightly different.

It occurs to me that theInstant class would replace the float type returned by the timestamp() function mentioned in #63 .

My thoughts after some time:
Instant and UTCDateTime are very similar. In the end, if you normalize to UTC, you might as well be dealing with a timestamp/integer: you're usually not interested in the nominal month, day, hour in UTC. You're more likely interested in comparison or adding/subtracting

An update to add here: In the rust extension I'm working on, UTCDateTime is Instant in almost everything but name.
Note that I'm still hanging on to the UTCDateTime name for these reasons:

The name UTCDateTime will be more familiar to most users than Instant
a UTC datetime is more human-friendly representation of an instant in time than an opaque integer class
For some contexts such as airline or militairy, UTC datetime is a meaningful concept over an abstract integer
Having different kinds of XXXXXDateTime in the API is already complex. Making Instant separate from them may confuse users.

It occurs to me that the Instant class would replace the float type returned by the timestamp() function mentioned in https://github.com/ariebovenberg/whenever/issues/63 .

Not necessarily... Instant can be opaque while the timestamp must be a an integer with a specific value 🤔

I've come around to Instant now:

~The name UTCDateTime will be more familiar to most users than Instant~ Most modern datetime libraries have Instant (or similar)
~a UTC datetime is more human-friendly representation of an instant in time than an opaque integer class~ The Instant repr will be a UTC datetime
~For some contexts such as airline or militairy, UTC datetime is a meaningful concept over an abstract integer~ yes, but hardly anybody uses is as a "local" time for calendar operations. In the rare case it is, ZonedDateTime can be used.
~Having different kinds of XXXXXDateTime in the API is already complex. Making Instant separate from them may confuse users.~ Still true, but many people are confused by having a separate class for UTC anyway.

The next release will replace UTCDateTime with Instant

Release 0.6.0 is now out with this change


wrap_comments breaks markdown formatting

Given the following:
//! This is a list:
//!  * Outer
//!  * Outer
//!   * Inner
//!   * Inner with lots of text so that it could be reformatted something something something
fn main() {
}

rustfmt, with wrap_comments set to true, is reformatted as:
//! This is a list:
//!  * Outer
//!  * Outer
//!   * Inner
//! * Inner with lots of text so that it could be reformatted something
//! something something
fn main() {
}

Notice that the inner bullet point is no longer part of either list.

I also encountered similar problems for code blocks within comments - I haven't reported a separate bug - should I?

There is already an issue for broken code blocks in comments. We have a lot of problems with comments right now :-(

Another test case:
//! This example shows how to configure fern to output really nicely colored logs
//! - when the log level is error, the whole line is red
//! - when the log level is warn, the whole line is yellow
//! - when the log level is info, the level name is green and the rest of the line is white
//! - when the log level is debug, the whole line is white
//! - when the log level is trace, the whole line is gray ("bright black")

is reformatted as
//! This example shows how to configure fern to output really nicely colored
//! logs - when the log level is error, the whole line is red
//! - when the log level is warn, the whole line is yellow
//! - when the log level is info, the level name is green and the rest of the
//! line is white - when the log level is debug, the whole line is white
//! - when the log level is trace, the whole line is gray ("bright black")

completely breaking the list (it no longer even resembles a list).
(diff output)
-//! This example shows how to configure fern to output really nicely colored logs⏎
-//! - when the log level is error, the whole line is red⏎
+//! This example shows how to configure fern to output really nicely colored⏎
+//! logs - when the log level is error, the whole line is red⏎
 //! - when the log level is warn, the whole line is yellow⏎
-//! - when the log level is info, the level name is green and the rest of the line is white⏎
-//! - when the log level is debug, the whole line is white⏎
+//! - when the log level is info, the level name is green and the rest of the⏎
+//! line is white - when the log level is debug, the whole line is white⏎
 //! - when the log level is trace, the whole line is gray ("bright black")⏎

With rustfmt 0.99.2-nightly (5c9a2b6 2018-08-07), getting the following diff:
 ///
-/// All the parameters ***except for `from_theater`*** should be inserted as sent by the remote
-/// theater, ie. as passed to [`Theater::send`] on the remote actor:
-///  * `from` is the sending (remote) [`ActorId`], as reported by the remote theater by theater-specific means
-///  * `to` is the receiving (local) [`ActorId`], as requested by the remote theater
-///  * `tag` is a tag that identifies the message type
-///  * `msg` is the (serialized) message
+/// All the parameters ***except for `from_theater`*** should be inserted as
+/// sent by the remote theater, ie. as passed to [`Theater::send`] on the
+/// remote actor:  * `from` is the sending (remote) [`ActorId`], as reported by
+/// the remote theater by theater-specific means  * `to` is the receiving
+/// (local) [`ActorId`], as
+/// requested by the remote theater  * `tag` is a tag that identifies the
+/// message type  * `msg` is the (serialized) message
 ///

Maybe what could be done is to recognise lines with a leading itemization marker (* or -), which indicates that the line indent should be kept. The line can then be wrapped, taking into account the indent of the item.
Below is an example of what that could look like:
-/// All the parameters ***except for `from_theater`*** should be inserted as sent by the remote
-/// theater, ie. as passed to [`Theater::send`] on the remote actor:
-///  * `from` is the sending (remote) [`ActorId`], as reported by the remote theater by theater-specific means
-///  * `to` is the receiving (local) [`ActorId`], as requested by the remote theater
+/// All the parameters ***except for `from_theater`*** should be inserted as
+/// sent by the remote theater, ie. as passed to [`Theater::send`] on the remote
+/// actor:
+///  * `from` is the sending (remote) [`ActorId`], as reported by the remote
+///    theater by theater-specific means
+///  * `to` is the receiving (local) [`ActorId`], as requested by the remote
+///    theater
 ///  * `tag` is a tag that identifies the message type
 ///  * `msg` is the (serialized) message


Add option to pass in ssl_params for the server's SSLContext so we can set any param on the SSLContext

This PR will allow a user to set the ssl_version, ciphers or options used by the server

:+1:

@cheister the most current branch is actually 0.6.0-milestone which is continued in 0.6.5-release ... I have been waiting for Unix socket support before releasing those, but planned to return to them shortly. Could you rebase this against 0.6.0-milestone please?

Sure.  I didn't see a way to update the branches used by this PR so I created a second PR https://github.com/celluloid/reel/pull/206 and will close this one.


Is there anyone who implement the code with keras?

Thank you for your contribution.I have try to read the code,but I use to read code in Keras.Could you provide the code of network in Keras?Thank you !

No, we have only implemented our method in PyTorch.
And we have no plan to move it to Keras in the near future.


Set @epapbak as additional codeowner

Description
Update of CODEOWNERS file
Type of change

Documentation update (does not change source code nor configuration)

Codecov Report

Merging #143 (a8537b9) into master (06b9984) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #143   +/-   ##
=======================================
  Coverage   89.83%   89.83%
=======================================
  Files          18       18
  Lines         610      610
=======================================
  Hits          548      548
  Misses         54       54
  Partials        8        8

Continue to review full report at Codecov.

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

Codecov Report

Merging #143 (a8537b9) into master (06b9984) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #143   +/-   ##
=======================================
  Coverage   89.83%   89.83%
=======================================
  Files          18       18
  Lines         610      610
=======================================
  Hits          548      548
  Misses         54       54
  Partials        8        8

Continue to review full report at Codecov.

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


Closing all the Document tabs causes document area to no longer show content.

not sure but could be related to...
https://github.com/AvaloniaUI/Avalonia/issues/4187

Didn't have time to investigate, maybe also related to https://github.com/AvaloniaUI/Avalonia/issues/4293

@danwalmsley I have tested and it's broken Carousel

Tested the latest version and can not reproduce.

Tested the latest version and can not reproduce.


Cannot map assets folder

In my angular project, all my images are in /src/assets/images and subfolders.
If I type / I get the project root, and can eventually navigate all the way down to something like /client/src/assets/images/mobile/onboarding/gettingstarted1-ios.jpg.
But that is not the image src, I need  /assets/images/mobile/onboarding/gettingstarted1-ios.jpg.  If I try to type asssets or assets/, I get this for some reason:

I have tried variations on this setting to no avail:
  "path-autocomplete.pathMappings": {
    "assets": "${folder}/src/app/assets",
  }

This is VSCode 1.37.0-insider, extension version 1.13.3, Mac 10,14

It seems there's a conflict with Angular Component Extension which is causing this.


libsqlite3-sys build broken for visionos with feature bundled

Build for the recently added Rust target aarch64-apple-visionos with feature bundled enabled:
RUSTFLAGS="-Awarnings" cargo +nightly build --target aarch64-apple-visionos -Zbuild-std --features "bundled"

Expected
Build to succeed
Actual
Build fails, with errors and warnings including "Unsupported architecture"

FYI, was able to get the visionOS build working by:

Adding this around line 142 of build.rs

        if env::var("TARGET").unwrap().contains("visionos") {
            cfg.flag("-D__arm64__");
        }

Setting this before compilng for visionOS on a macOS build machine:

export CC="/usr/bin/clang"

There may be a more 'correct' way to do this, but HTH.


Shorten title length parameter

Following on from the issue #95 , I added a function parameter "shortenTitle".
In case it's not provided, it uses the default shortenTitle function there was in ExRouteRenderer component.
Cheers,

Hi,
Could you merge this request if everything's ok for you guys?
Thanks,

You should reimplement renderTitle in this case. We don't really want to expose niche configuration options like this.

Then how do you solve this issue?


Polyfills being run more than once

I have noticed an issue in IE11 with the InputEvent polyfill, where if shaka.polyfills.installAll() is called multiple times, a stack overflow error occurs when adding a change event handler to an input type="range".
Previously there there didn't seem to be an issue if we have 2 calls to installAll.
Should I be more careful around when and how this is called?

@gscragg, it was never intended that you would call installAll() more than once, but I can't think of any reason it shouldn't still be safe.  I'll see if I can fix it.

We've pushed a fix.  Please let us know how it works for you.

Thanks @joeyparrish, I appreciate your speedy response.

The fix has been cherry-picked for v2.1.6.


Identifying parent cpgrid for a cpgrid_property

I am trying to create metadata for multiple grids / grid properties in roff format. (I.e. Drogon geogrid/simgrid)
Are there any tags that can be used to identify which grid a grid property belongs to? e.g. a parent keyword?

data.grid_model is an existing tag, we could consider making this mandatory when content is cpgrid_property.
But I also think this more naturally belongs in the fmu section, similar to realization and model etc, something like:
data:
  content: cpgrid_property
fmu:
  grid_model: (mandatory if content is "cpgrid_property")
    name: "geogrid"
    (id: <in the future>)
    (uuid: <in the future>)

Primary:

Establish a sustainable link between property and grid_model so that consumers can link them
...with a minimum of config exposed to the end user.

Offline discussion 2023-10-16
@daniel-sol @HansKallekleiv @perolavsvendsen
Discussion isolated to "grid geometries and parameters produced by RMS".
Not discussed: Connecting grids across applications, multi-application grid results
Grids + parameters produced/used in FMU are represented by:

Grid geometry

Represented by one (per grid) binary file on ROFF format.

Grid parameters

Represented by multiple binary files on ROFF format.
Filename today: <gridname>--<parameter_name>--<date>.roff

Proposal

Export grid geometry:
mygridgeometry # <-- My grid geometry
exp = ExportData(
    name = "MyGridName"
    content = "grid_geometry"
exp.export(mygridgeometry)

--> Produces:
mygridname--geometry.roff

metadata:

class: cpgrid
data:
  name: MyGridName
  content: grid_geometry
fmu:
  model:
  realization:

Export parameters
mygridparameter # <-- My grid parameter, exported from the grid "MyGridName"
exp = ExportData(
    name: MyGridPropertyName
    content: {"grid_property": {"parent_name": "MyGridName}} # align with current convention
    )
exp.export(mygrid, parent="MyGridName") # the `parent` argument is currently supported, but only affects the filename.

[ ] Parent currently supported, but only affects the filename (!). Need to include the parent input into metadata.

--> Produces:
mygridpropertyname--mygridname.roff  # NB should not break existing dependencies, may be backwards...

metadata:

class: cpgrid
data:
  name: MyGridPropertyName
  content: grid_property
  grid_property:
    parent:
      name: MyGridName
fmu:
  model:
  realization:

Convention is to have separate grid- and parameter files.
Basic requirements (Webviz)

Grid parameter values are linked to grid geometry so that they can be co-visualized.
An exported grid parameter can be linked to a corresponding grid geometry element

For reference to the requirements above:
Below is an example of current RMS script for exporting grid geometry and parameters.
The parent argument is only used to create the filename. It is not used in the metadata.
"""
Export geogrid and geogrid parameters (roff format)
Used for both visualization and as input to seismic project

Parameters required/used by seismic project is set in PROPS_SEISMIC
Additional paramters can be set with PROPS_OTHER
All parameters can be used for visualization (coviz)
"""
import xtgeo
import fmu.dataio as dataio
from pathlib import Path, PurePath
from fmu.config import utilities as utils

CFG = utils.yaml_load("../../fmuconfig/output/global_variables.yml")

PRJ = project

GNAME = "Geogrid"
PROPS_SEISMIC = ["PHIT", "VSH", "SW", "SG"]
PROPS_OTHER = ["KLOGH", "KV", "FACIES", "Region", "Zone", "Swl"]

def export_geogrid_parameters():
    """Export geogrid and associated parameters based on user defined lists """

    props = PROPS_SEISMIC + PROPS_OTHER

    edata = dataio.ExportData(
        config=CFG,
        content="depth",
        unit="m",
        vertical_domain={"depth": "msl"},
        workflow="rms grid and property model",
    )

    grd = xtgeo.grid_from_roxar(PRJ, GNAME)
    out = edata.export(grd, name=GNAME)
    print(f"Exported grid as {out}")

    # export properties
    for propname in props:
        prop = xtgeo.gridproperty_from_roxar(PRJ, GNAME, propname)
        out = edata.export(prop, name=propname, parent=GNAME)
        print(f"Exported grid property {propname:>13s}:    {out}")

if __name__ == "__main__":
    export_geogrid_parameters()
    print("Done.")

Exported grid as /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid.roff
Exported grid property          PHIT:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--phit--geogrid.roff
Exported grid property           VSH:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--vsh--geogrid.roff
Exported grid property            SW:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--sw--geogrid.roff
Exported grid property            SG:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--sg--geogrid.roff
Exported grid property         KLOGH:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--klogh.roff
Exported grid property            KV:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--kv.roff
Exported grid property        FACIES:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--facies--geogrid.roff
Exported grid property        Region:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--region--geogrid.roff
Exported grid property          Zone:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--zone--geogrid.roff
Exported grid property           Swl:    /project/fmu/tutorial/drogon/resmod/ff/users/hakal/webviz_case_1/share/results/grids/geogrid--swl.roff
Done.

class: cpgrid_property
data:
  name: MyGridPropertyName
  content: inplace
  content_details:
     attribute: STOIIP
  grid_name: MyGridName
fmu:
  model:
  realization:

Slightly zoomed out:
The general pattern in fmu-dataio today is as follows:

Make a Python object that represents the data you want to export
Initialize fmu.dataio.ExportData with some context
Give that Python object to fmu.dataio.ExportData.export()
Recognize and parse the given object, and extract more context directly
Generate metadata and save to disk

Given this pattern, it seems clear (?) that if we can create Python object representing the grid geometry + parameters, and make this a known object to fmu-dataio, we can infer the relationships between them.
e.g.
from fmu.dataio import ExportData, RmsGrid  # <-- assuming part of fmu-dataio
mygrid = RmsGrid(PRJ.get_grid()) # pseudo-code
exp = ExportData()
exp.export(mygrid)

>>> Files on disk + metadata with context

Can this be closed with #677 @jcrivenaes ?

Answering my own question and considering this solved by ☝


Cleanup code of Session and WebContents

Make BrowserWindow and WebContents share same web-preferences, no more duplicate code of dealing options of BrowserWindow and webview pages.
Simplify the management of BrowserContext for different partitions.

Refs #959.

Awesome! :+1:

Make BrowserWindow and WebContents share same web-preferences, no more duplicate code of dealing options of BrowserWindow and webview pages.

:clap:


Make errors in retention config more verbose

It would be nice to see the line and string value that caused an error of configuration parsing
Traceback (most recent call last):
  File "/opt/graphite/bin/carbon-cache.py", line 32, in <module>
    run_twistd_plugin(__file__)
  File "/opt/graphite/lib/carbon/util.py", line 96, in run_twistd_plugin
    runApp(config)
  File "/usr/local/lib/python2.7/site-packages/twisted/scripts/twistd.py", line 23, in runApp
Starting carbon-cache (instance a)
    _SomeApplicationRunner(config).run()
  File "/usr/local/lib/python2.7/site-packages/twisted/application/app.py", line 386, in run
    self.application = self.createOrGetApplication()
  File "/usr/local/lib/python2.7/site-packages/twisted/application/app.py", line 446, in createOrGetApplication
    ser = plg.makeService(self.config.subOptions)
  File "/opt/graphite/lib/twisted/plugins/carbon_cache_plugin.py", line 21, in makeService
    return service.createCacheService(options)
  File "/opt/graphite/lib/carbon/service.py", line 126, in createCacheService
    from carbon.writer import WriterService
  File "/opt/graphite/lib/carbon/writer.py", line 33, in <module>
    SCHEMAS = loadStorageSchemas()
  File "/opt/graphite/lib/carbon/storage.py", line 126, in loadStorageSchemas
    archives = [Archive.fromString(s) for s in retentions]
  File "/opt/graphite/lib/carbon/storage.py", line 110, in fromString
    (secondsPerPoint, points) = whisper.parseRetentionDef(retentionDef)
  File "/usr/local/lib/python2.7/site-packages/whisper.py", line 122, in parseRetentionDef
    (precision, points) = retentionDef.strip().split(':')
ValueError: too many values to unpack

I think this is improved in https://github.com/graphite-project/whisper/pull/200
carbon should handle the exception to print prettier


Automate Install Script Upload

The catch-all install script (documented here) is not part our release process. Uploading the most recent copy to azurecliprod should be added to the release pipeline.

The curl script?

Correct :) I don't think updating it was documented in the old instructions either. Fortunately, it just don't change all that much either.

add to S164.

Added task in ADO.


Run tests on CI

Now that there's a test suite, it would be helpful to add some sort of CI to the project to ensure the tests are passing.

see PR #23 for a Travis YAML config.


Investigate GoLang channels for multithreading

Processing incoming compound operations and dispatching each OP is inherently a multi-threaded use case. Figure out how GoLang channels can be leveraged to do this.

Through GoRoutines?
https://tour.golang.org/concurrency/1
GoRoutines are light weight threads that share the address space of the main thread.
Only thing here, I think, is to leverage GoLang channels and GoRoutines intelligently.


Update YGNodeStyleGetGap to return YGValue

Gap can be styled using both points and percentages, but YGNodeStyleGetGap currently returns a float value.
To maintain alignment with the padding and margin functionalities and allow it to be handled in bridging code, this function has been updated to return YGValue.

@NickGerleman I accidentally closed the PR while rebasing.
I've combined the previous commits into one. Please take a look when you have time. Thank you.

We seem to be crashing with terminating due to uncaught exception of type facebook::yoga::vanillajni::YogaJniException: std::exception
Seems like we still need to update method descriptor for registerNatives? {"jni_YGNodeStyleGetGapJNI", "(JI)F", (void*)jni_YGNodeStyleGetGapJNI}, (it says it's returning a float right now).

Oh, I missed that. I've corrected it properly.


Intermittent test failures on AdminApiTest.partitionedTopics

Failed tests:
com.yahoo.pulsar.broker.admin.AdminApiTest.partitionedTopics(com.yahoo.pulsar.broker.admin.AdminApiTest)
  Run 1: AdminApiTest.partitionedTopics » ServerSideError Some error occourred on the s...
  Run 2: PASS

Close this issue for now. If we see this test fails again, let's create a new GitHub issue.


Update developer certificate

What should we do?

Update developer certificate
Update documentation

Why should we do it?
Ensure we can continue to build the app, and know how updating works.

Moving to ready due to urgency on this matter.

Let's use cert-test branch and build-on-demand for testing.

Documentation improvements:

https://github.com/bpmn-io/internal-docs/commit/d3088312fbe3e1ca560aec9b4277d661c5a13349
https://github.com/bpmn-io/internal-docs/commit/5d357264ce9e31cbac1e3aac1b1b506deaabe90f

:clap:


Workflow doesn't work when the github_token is not specified

Same issue is present for the formatter: https://github.com/chipsalliance/verible-formatter-action/issues/17
In the README, it writes: "If you don't wish to use the automatic PR review, you can omit the github_token".
However, this doesn't seem to work for me, see example output log here: https://github.com/V0XNIHILI/parametrizable-floating-point-verilog/actions/runs/7738827016/job/21100439503?pr=23 (for code: https://github.com/V0XNIHILI/parametrizable-floating-point-verilog/pull/23/commits/0097a9df2cf3c1494c5d5b81f30e3390db6be8e6)

Thank you for the report!
I can confirm the issue, apparently https://api.github.com/repos/chipsalliance/verible/releases/latest is no longer accessible without the token.
I don't think we can do much about it for now, the workarounds I see is providing a specific verible version when used without github_token (to be verified if it works).
We probably need to update the README to reflect this.
Would you be willing to submit a PR with the update?

I don't have any problems accessing https://api.github.com/repos/chipsalliance/verible/releases/latest without an authorization header specified. You can check yourself by just pasting the URL in your browser, or running
curl -fsSL https://api.github.com/repos/chipsalliance/verible/releases/latest

The problem lies in chipsalliance/verible-actions-common in the install-verible/action.yml file:
- name: Download and unpack Verible
  shell: bash
  run: |
    [...]
    VERIBLE_RELEASES_JSON=$(curl --header 'authorization: Bearer ${{ inputs.github_token }}' -fsSL https://api.github.com/repos/chipsalliance/verible/releases/latest)
    [...]

Because the --header 'authorization: Bearer ${{ inputs.github_token }}' argument is always passed -- even if inputs.github_token is empty -- GitHub's API will return a 401 error if the token is incorrect.
I suggest adding something like this:
if [[ ! -z "${{ inputs.github_token }}" ]]; then
    _HEADERS=(--header 'authorization: Bearer ${{ inputs.github_token }}')
else
    _HEADERS=()
fi
VERIBLE_RELEASES_JSON=$(curl ${_HEADERS[@]} -fsSL https://api.github.com/repos/chipsalliance/verible/releases/latest)

The code example uses bash's array syntax (and also the [[ check).
Because the shell is already set to bash in the workflow file, I'd say this is okay. A pure POSIX shell implementation is a bit more difficult without relying on eval.
Alternatively, the authorization header could also be dropped entirely. It seems like it is currently not necessary. But leaving it in there is also no problem.
I'd be happy to create a pull request on chipsalliance/verible-actions-common with my fixes.

If I'm not mistaken, by merging chipsalliance/verible-actions-common#7 this issue (and chipsalliance/verible-formatter-action#17) should now be resolved.
I checked other places where the GitHub token is used and - to my understanding - this was the only instance where a missing token caused a problem.

Yeah, thanks!


rare item message stuck on separate message list after selling to npc

after selling rare item (boot, circlet etc) to npc, item message will stuck on separate message list for ever.

this seems like a bug
currently I use these 3 conditions to check if an item is on the ground:

the item is not belong to Player (onwerId == 0)
the item is not on body (position = 0)
the item is in somebody's inventory/cube/stash(invPtr != nullptr and itemPosition == 0 or 3 or 4)

so this item does not meet all of the three, but is in NPC's selling box
maybe there should some another field to indicate that the item is on the ground, I'd look the memory over later


Neofetch 3.0 shell command broken with /bin/zsh shell

Description
The neofetch output seems to be broken on the shell command. I'm using Neofetch 3.0 installed through homebrew and using the same config file as in master. My current shell script is as folows:
$ echo $SHELL
/bin/zsh

Neofetch version
Neofetch 3.0
Screenshot
The cropped output:

if I comment the shell command on config, the output is not cropped:

Verbose log
The verbose log is found here: http://pastebin.com/sifHL6EJ
Config file
And the config file used here: http://pastebin.com/K2YF33jv

Thanks for opening this. :)

Does the issue still occur with neofetch --shell_version off?
What's the output of this command?: zsh --version

With neofetch --shell_version off the issue is gone.

*note: I'm now at work in a different machine, but I had the same issue as in my personal machine.

What's the output of zsh --version? This is the only command that gets run in the shell function, which makes it the only possible cause of the issue.

zsh 5.3.1 (x86_64-apple-darwin15.6.0)

Weird.
What about this?

"$SHELL" --version

Also what version of bash do you have installed?

bash --version

I have homebrew zsh installed but not used. Thats why zsh --version is different
$ "$SHELL" --version
zsh 5.0.8 (x86_64-apple-darwin15.0)

$ bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)
Copyright (C) 2007 Free Software Foundation, Inc.

The shell function might include something incompatible with bash 3 and that's why it's suddenly exiting. I'll install bash 3 and see if I can reproduce this.

I can reproduce this with bash 3, working on a fix now. :+1:

This was the offending line: shell="${shell/ ${SHELL##*/}}", I'm not sure why this caused bash to crash. The issue should be fixed now, try out the latest master and let me know if it still occurs. :)

Closing this, reopen it if you're still experiencing the issue. :)

Closing this, reopen it if you're still experiencing the issue. :)

I have got the same problem with $SHELL as zsh, it displays properly when  $SHELL is /bin/bash

Im still experiencing this issue after a fresh reinstall of ubuntu 22.10


[NV-TF] Sync NV-TF 2108 commits.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 11 committers have signed the CLA.:white_check_mark: liutongxuan:x: AyanmoI:x: philipphack:x: nouiz:x: mihaimaruseac:x: benbarsdell:x: kaixih:x: trentlo:x: nluehr:x: DEKHTIARJonathan:x: miaout17You have signed the CLA already but the status is still pending? Let us recheck it.


Query error can exceed the maximum message size.

When returning an error message we should protect the value from growing larger than the maximum error size. While the maximum is never reached, we should still protect the code.
The code has some protection but by mistake the code expected snprintf() to return the number of written characters and not the number which should be written.

Fixed by correcting the value of len so it will never be larger then the maximum value.


fix #117: ResultSet instance might be null

@davidsiro
Thanks for reporting the issue and submitting a PR!
I’ve addressed the null issue for ResultSet in a different way, but I appreciate your effort in creating the PR regardless.

Thank you too! Any ETA on release of datasource-proxy and  datasource-micrometer?

@davidsiro datasource-proxy 1.10.1 is released. You can specify this version to override the default version coming from datasource-micrometer.


[BP-1.8][FLINK-12075][yarn] Set RestOptions.BIND_PORT only to 0 if not specified

Backport of #8096 for release-1.8.

Merged.


us-mn-st_louis_county - parcel data

This county has open data for download on their website here: http://www.stlouiscountymn.gov/LANDPROPERTY/Maps/Data.aspx
And this is a service layer with parcels:
http://gis.stlouiscountymn.gov/arcgis/rest/services/Planning/Cadastral/MapServer/33
But unlike other sources in the Parcel Wiki, this layer DOES have a situs address, with "PHYS*" fields. Here is an example: http://gis.stlouiscountymn.gov/arcgis/rest/services/Planning/Cadastral/MapServer/33/8774072
PHYSADDR: 1726 N 7th Ave E
PHYSCITY: Duluth
PHYSZIP: 55805
Should this go in the parcel wiki under a new heading?

@mmdolbow Looks like the link you posted is stale, but a source with a working data link is currently present. https://github.com/openaddresses/openaddresses/blob/master/sources/us/mn/st_louis.json
But in general, any parcel layer with situs addresses is acceptable.


AzureProvisioner output saves connection strings to user secrets even if it did nothing

This is what happens when you use an azure resource and do nothing else:
Building...
info: Aspire.Hosting.Azure.AzureProvisioner[0]
      Using DefaultAzureCredential for provisioning. This may not work in all environments. See https://aka.ms/azsdk/net/identity/default-azure-credential for more information.
info: Aspire.Hosting.Azure.AzureProvisioner[0]
      Azure resource connection strings saved to user secrets.

The first log should only show up if we are going to provision.
The second log should only show up if we have indeed saved connection string to user secrets.

I don't want to open another issue about AzureProvisioner and user secrets. I have a feeling a provisioner api would help with those issues.
The way it's coded, anyone taking the AzureProvisioner as an example to have a custom provisioner could encounter a concurrency issue updating the user secrets. As the provisioner loads the user secrets once and then saves it at the end of the work (which is launched in Task.Run). Another provisioner that would do the same could end up losing / overriding modified user secrets from another provisioner.

Yep, it's problematic. We'd need to expose a first class API. That wouldn't help if modifications were made outside of the app host though.


Fix Aktia test case

Aktia works when manually clicking the Aktia icon in sample application but it doesn't follow the link when casperjs clicks it and this causes the test to fail

This was resolved in #4


Use consistent quotation and comment style

[ ] Use single quotes except in interpolated strings (should at least consider making all strings double quoted, for even more consistency)
[ ] Use the ###* comment style for all doc comments (those intended for both JSDoc and apiDoc)

See #34

Use single quotes except in interpolated strings (should at least consider making all strings double quoted, for even more consistency)

In Perl, which also interpolates double-quoted but not single-quotes strings, I've always used single quotes whenever interpolation was not expected, and double quotes only when it was. Apostrophes in strings were pesky, which is why I preferred more format errors ("Could not read file" vs. "Couldn't read file").

Thanks for your input @dandv! I was definitely leaning in that direction, as it's the convention I was trying to follow (but clearly failed to do so). Java is one of my most familiar languages, so I accidentally drop those double quoted strings in for no apparent reason sometimes. Just an old habit dying hard, I suppose.
I'll adopt the single-quoted-unless-interpolated convention, and probably even add in a super simple style guideline to the contributing doc and include that info there as well.


[FSDE-936] DevOpsGCR triggerTag

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Playpen/job/ChiGCR/job/ChiGCR/job/PR-11/1/. :white_check_mark:


Trivial fix: Fix some typos in comments

This commit intends to fix some typos in comments for reading easily.
Co-Authored-By: Nguyen Phuong An<EMAIL_ADDRESS>Signed-off-by: Kim Bao Long<EMAIL_ADDRESS>

Thanks!


RFC: Support Persisted Queries for Mutations

Summary
Currently the @urql/exchange-persisted-fetch only supports queries. Enabling persisted queries for mutations has a couple of advantages:
Security
One of the challenges of GQL is that an API is exposed for arbitrary requests. The flexibility in the query language allows bad actors to try DDoS attacks by generating big expensive queries. By leveraging persisted queries at build time you can effectively limit the combinations and defend against these types of attacks.
https://leapgraph.com/graphql-api-security#persist-queries
Efficiency
While queries are usually larger than mutations there is still small improvements in not sending that information in the request. Here flexibility is the enabler, in use cases where mutations for business reasons have to be big in size persisted mutations could be a solution to reduce latency.
Apollo-client compatibility
Apollo-client supports persisted queries for mutations and providing the same feature would help developers that are thinking to port projects into URQL.
Proposed Solution
Enable mutations in the Persisted Fetch Exchange. It could be added as an opt in feature to provide backwards compatibility to projects that don’t need mutations to be hashed.

Hey,
I don't think Apollo supports this currently, code. This checks whether or not it contains any mutation reference and if it does it goes to regular querying.

Hey,
I don't think Apollo supports this currently, code. This checks whether or not it contains any mutation reference and if it does it goes to regular querying.

Agree I don't think GET should be a valid case for hashed mutations, but I don't think there is value in allowing mutations to be sent using a hash.
Which Apollo supports currrently.

Agree I don't think GET should be a valid case for hashed mutations, but I don't think there is value in allowing mutations to be sent using a hash.
Which Apollo supports currrently.

Agree I don't think GET should be a valid case for hashed mutations, but I do think there is value in allowing POST mutations to be sent using a hash.
Which Apollo supports currrently.

Agree I don't think GET should be a valid case for hashed mutations, but I do think there is value in allowing POST mutations to be sent using a hash.
Which Apollo supports currrently.

Hiya :wave: I haven't found any code or documentation that details this. I suppose we could send something like persisted queries against a POST request with a body that's similar to persisted queries. However, I haven't found any hints of this being supported by servers like the Apollo Server implementation. Can you point out where you've maybe seen this as being supported? I haven't found any specification from Apollo's end for this yet anyway, so I'm unsure of what the details of the implementation should be.

Closing due to inactivity

I’m using this approach currently with Apollo client and Apollo server using there is built in persisted query mechanism with custom queries cache.
All works like a charm.
But now we are moving to urql and we need this functionality for mutations.

There is no any reason to not implement it because it highly  improves security of graphql api.
Even if it’s not in any spec or standard.
I think this should be reopened and implemented. I can even send a PR

@stalniy It's definitely something we can support and something we should support, however, we do need to have guarantees that we're not implementing a random feature here, but rather a feature / mechanism that a majority of GraphQL APIs that aim to support APQ/PQs will buy into. Hence, we were asking for references to implementations.
This could include references to code, references to this being implemented in more than one GraphQL API, etc. I see this as a little tricky because both file uploads and persisted queries are currently following looser specs that are not comprehensively documented just yet. So, the issue I'm trying to carefully talk about here is that if every implementation of Apollo's APQ/PQ goes by observed effects, loose documents, and some pieces of code, all implementations may arrive at different tiny quirks.
Anyway, what we can do is enable mutations to be sent with the same mechanism as POST-only always. But I'd love to be able to see first whether this is actually expected in all implementations of APQ that exist, e.g. Mercurius: https://mercurius.dev/#/docs/persisted-queries

I also ran into this transitioning from apollo. I'm using Postgraphile with @graphile/persisted-operations. I'm generating a hash for all of my client mutations and queries at built time with graphql-codegen-persisted-query-ids and using that list of hashes as an allowlist on the server. Now I have to disable persisted queries for mutations since urql doesn't support them. So seconding the calls for implementing persisted queries for mutations.

Restarting this conversation. I'm in the same situation as @rriski. Adding an optional filter option to configure when this exchange is used would be perfect. This logic is already used by Apollo client which also apply the persisted operation logic on mutations (https://github.com/apollographql/apollo-client/blob/main/src/link/persisted-queries/index.ts). Apollo client also force using POST for mutations.
It should be noted that in this usecase, persisted operations are used to create an allow-list of operation in the backend from the queries extracted from a frontend app.


Create coding infrastructure

Checklist:

[x] Create central test task
[x] Integrate with travis-ci (also badge via shields.io)
[x] Integrate with appvevyor (also badge via shields.io)
[x] Integrate with lgtm.com
[x] Integrate with code-climate
[x] FIX potential windows execution issues
[ ] Think about output consistency (Add discerning and playful output on concurrent commands)
[ ] Add configuration file infrastructure (crowconfig, read option flags from local json)
[x] Add lint crow-script

[x] Add nsp
[x] Add eslinter
[x] Add flow
[ ] Add discerning and playful output on concurrent commands

[x] Add fmt (code formatter, prettier) crow-script
[ ] Evaluate usage of https://github.com/documentationjs/documentation
[ ] Add doc (documentation) crow-script
[x] Add Greenkeeper https://greenkeeper.io/
[ ] Add build crow-script

Ref: #20


Dom changed position

Vue version
3.2.33
Link to minimal reproduction
https://github.com/LoveofRedMoon/bug-20220608.git
Steps to reproduce

npm install
npm run dev (this only appears in production or 'production' mode with dev)
click '开发工具'
click '用户管理'
click '用户配置'
click '日常办公'

What is expected?
Menu still appears in left
What is actually happening?
Menu appears in right
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1155G7 @ 2.50GHz
    Memory: 5.92 GB / 15.79 GB
  Binaries:
    Node: 16.10.0 - C:\Program Files\nodejs\node.EXE
    npm: 7.24.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (102.0.1245.33)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    vue: ^3.2.33 => 3.2.33

Any additional comments?
The relative view is 'src/views/Home.vue'
In this SFC, Menu always appears in left
This only appears in 'production' mode, or build and server
I found that one vnode already shows in screen but it's el property is null

Please provide a minimal reproduction, thanks!

Please provide a minimal reproduction, thanks!

I could not determine the problem.
https://github.com/LoveofRedMoon/bug-20220608.git
this link is what i can provide minimal reproduction.

This a far beyond minimal. See https://github.com/vuejs/core/blob/main/.github/bug-repro-guidelines.md#a-repro-should-be-minimal. Remove all unnecessary components and dependencies please.

This a far beyond minimal. See https://github.com/vuejs/core/blob/main/.github/bug-repro-guidelines.md#a-repro-should-be-minimal. Remove all unnecessary components and dependencies please.

The triggering method of some bugs is not simple in itself, just like isBlockTreeEnabled, its triggering condition must be a complex component. Is it not thoughtful to close an issue so hastily?

Is all the code you provided necessary to reproduce the problem? Will the problem disappear if you remove any part of it?

Is all the code you provided necessary to reproduce the problem? Will the problem disappear if you remove any part of it?

I try to remove some components that will not trigger this problem.

Is all the code you provided necessary to reproduce the problem? Will the problem disappear if you remove any part of it?

This is a production project and I have removed most of the business code.

Is all the code you provided necessary to reproduce the problem? Will the problem disappear if you remove any part of it?

Thanks, I will fix this manually myself. This issue is already closed.


Dependent parameters?

How to do dependent parameters in maru, ala Grape?
https://github.com/ruby-grape/grape#dependent-parameters
So I can say, if param1 is found then evaluate this sub-group of parameters.

This feature will included in the next version, thank you!


[Antipattern]  Transient form break hook's dependency logic

Please keep in mind the tips below when formulating a question:
use(options.form, { transient: true }) always returns a new reference, which prohibits using it as a react hook dependency, as it returns a new value at every render.
Maybe it'd be better to have it accessed through a useRef ?

@Fen747 what is the use-case for using it as a react dependency?

Hi @theodorDiaconu ,
Well, we have a very clear use case in our situation :
Our form is split into several panels / parts (a antd stepper). We share common state through a context, which includes sharing the  xForminstance in order to be able to callxForm.render("....")` inside the different steps.
The problem is that when a sub-component re-renders (because we change a Ant Form's field value), the context doesn't rerender, and therefore, we get an error because  myField has already been consumed => because the context has not been re-rendered, the xForm.build() has not been triggered again and therefore, we can't re-render sub-components that would depends on the xForm to render some of its fields.


CompositeMessagingScenarioFactory

Prefer "first one wins" over of "there can be only one". By using LINQ's .Single, it ensures that "catch-all" type messaging scenario factories cannot co-exist with regular factories.

PR review and merge


Dist/spa empty

Unable to find the files to copy for UI

Hi. Please supply more information. Did you follow the steps from readme? Did any error messages appear?

Thank you for your reply,
I managed to get the issue resolved. However when running the quasar Dev or quasar build, after following all the steps get an api errors.
New live gekko does not get started, unable to run backtests.
http://prntscr.com/mk8obc
When starting a live gekko get the following errors
http://prntscr.com/mk8pp5

Looks like the pair does not exist on the selected exchange - what exchange and pair are you using?
That might happen since gekkos's pair-infos are not always up to date.

I know the issue has been there on poloniex pairs, I have tried all exchanges and different pairs, This issue should not occur if running in dev mode as it is fetching the data from the running instance of gekko UI.
I have tried new installations, cross installation, even followed the steps to build the new UI and got all the files and made changes as instructed. Do you have it running fine on your end ?

Yes, I got it running on my end. But I could reproduce you problem with for example
Poloniex - BTC-1CR or
Poloniex BTC-AUR - these are not available for trading anymore.
The error also occurs in the original UI.
It seems to be the market files that have to be updated.
Most of the files (except for poloniex) can be updated manually - this is described here:
https://github.com/askmike/gekko/issues/2605
The problem seems not to be related to this repository, may I ask you to open an issue directly in the original repo for the gekko-bot (to update poloniex)?

Hi,
Is it possible if you can upload your complete gekko, with your UI running in your personal repository.
If you do so please make sure to remove the API keys from your source code.
I am not a developer, but am fine with following instructions. If you upload your files in your repository it will fix my issue which I am trying to resolve from past few days.
Thanks in advance.

Here you go - clone this repo:
https://github.com/H256/gekko
After that, run npm install on the root path (e.g. c:\gekko) and on the exchanges path (e.g. c:\gekko\exchange).
Then run node gekko --ui. This should start the server including new UI on localhost.

Great, Thank you for your help and effort.
It is working now.
Have a great day

Hi,
I just sent 0.01 BTC, as a thank you for your help, as earlier I was unable to find your BTC address on the profile. https://www.blockchain.com/btc/tx/52279416fcc149f2463bbaec0ac79bfcfc33f796fe94e219d51f92aefb05d3de
However I do have an ongoing issue, I was never able to run the gekko on server(even normal gui),
The only way I was able to accomplish it was through docker, I wish to run your GUI on server, but when I run docker image only normal GUI works, If I use your repo, It does not.
I have your GUI working on my desktop, and have one instance Gekko running on server, via Docker
Thank you

Hi @ethcar, first of all thanks for you donation. Since the problem is referenced to the "complete repository" - I have opened and referenced an issue there.


AWS - Add AWS sts dependency so web identity tokens work

Summary
Adds aws-java-sdk-sts dependency so the WebIdentityTokenCredentialsProvider works within the DefaultAWSCredentialsProviderChain. Without this dependency I was unable to use web identity token files in AWS EKS, see https://github.com/aws/aws-sdk-java-v2/issues/1470#issuecomment-601131243 for more details

any updates on this PR? this is critical to make the AWS secret provider work for kafka connect clusters deployed to AWS EKS. Can someone review and approve this? Thanks

Completely forgot about this one... Looking at the last merged PRs the reviewers were @stheppi and @andrewstevenson, maybe one of you could take a look? Also have https://github.com/lensesio/secret-provider/pull/24 still waiting for review as well. Thanks!

Facing the same issue for RedHat ROSA Kubernetes cluster. Please take a look at this:
@andrewstevenson, @johnathana and @stheppi

I can confirm that this works as intended. Any chance we can get this merged in? Right now I've built my own jar and am using that, but I'd prefer to point at the official version.

@davidsloan It looks like you merged the https://github.com/lensesio/stream-reactor/pull/853 PR, can you take a look at this one + https://github.com/lensesio/secret-provider/pull/24 + https://github.com/lensesio/secret-provider/pull/23
Thanks!

Hi @adrianisk , happy to merge this one if you're happy to rebase.
We recently updated to V2 of the AWS SDK, so it might be that the dependency has also changed or is no longer required.

++ when can we merge this. It would be great to authenticate in AWS EKS using IRSA

#56 adds STS dependency


Problem when installing - "next not found"

Hi,
I'm trying to install react-three-next
When installation. I'm following the steps:
$ npx create-r3f-app next my-app
$ cd my-app
$ npm run dev

And it returns the next:

><EMAIL_ADDRESS>dev
> next dev
sh: 1: next: not found

So inside of my-app I did:
> npm install

and it returns:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@react-three/fiber
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@react-three/a11y
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/spacecomet/.npm/eresolve-report.txt for a full report.
npm ERR!  I'm not able to use this package...

Related to https://github.com/pmndrs/react-three-next/issues/51
I'm really confused, I mean<EMAIL_ADDRESS>doesn't even exist that's weird. I can't reproduce the issue with npx so I have no idea of how to fix it sorry.
I can only recommend using yarn.
Are you on Linux?

Yes,
Linux scvb 5.11.0-27-generic #29~20.04.1-Ubuntu x86_64 x86_64 x86_64 GNU/Linux

Running into this issue as well.

Was able to npm i  with the addition of --legacy-peer-deps

Yeah... It is the same with react-spring (made by the same people I believe). I'm working in a project were I had to install everything with yarn instead of npm
It might be something related to how the set up the npm packages...
If I know how to fix this I would contribute but I don't.
I guess if someone knows how to package with npm they might fix this issue

NPM v7+ will fail when there's conflicting peer dependencies (see release notes).

@CodyJasonBennett  so in order to fix this we have to update the dependencies? @RenaudRohlinger can we do that?

Hi everybody,
I solved the problem by removing the eslint:'8' from devdependencies and I also removed eslint from dependencies. Because in Nextjs version 12 eslint is mixed in some way.
with npm run dev its working without any error now!
Here is my packages.json file:
{
"name": "react-three-next",
"version": "2.0.0",
"authors": [
"Renaud ROHLINGER https://twitter.com/onirenaud"
],
"license": "MIT",
"private": true,
"engines": {
"node": ">=14"
},
"scripts": {
"lint": "yarn prettier && yarn eslint",
"eslint": "next lint --fix --dir src",
"prettier": "prettier -l "./src/**/*.{js,jsx,md}"",
"dev": "next dev",
"build": "next build",
"export": "EXPORT=true next build && EXPORT=true next export",
"analyze": "ANALYZE=true next build",
"start": "next start"
},
"dependencies": {
"@babel/plugin-transform-runtime": "^7.17.0",
"@react-three/drei": "^9.11.2",
"@react-three/fiber": "^8.0.19",
"babel-plugin-glsl": "^1.0.0",
"glsl-random": "^0.0.5",
"next": "^12.1.6",
"react": "^18.1.0",
"react-dom": "^18.1.0",
"three": "^0.140.2",
"three-stdlib": "^2.10.1",
"zustand": "^4.0.0-rc.1"
},
"devDependencies": {
"@next/bundle-analyzer": "^12.0.10",
"autoprefixer": "^10.4.2",
"eslint-config-next": "^12.0.10",
"eslint-config-prettier": "^8.3.0",
"eslint-plugin-tailwind": "^0.2.1",
"file-loader": "^6.2.0",
"glslify": "^7.1.1",
"glslify-loader": "^2.0.0",
"next-compose-plugins": "^2.2.1",
"next-offline": "^5.0.5",
"postcss": "^8.4.12",
"prettier": "^2.6.2",
"raw-loader": "^4.0.2",
"tailwindcss": "^3.0.23",
"typescript": "^4.7.3",
"url-loader": "^4.1.1"
}
}

Any updates on this? Is there a way to use it along with ESLint? Did perhaps Next 13 fix something?
Still experiencing this issue when using npm to install react-three-next.


A preview of all the colors in the README.md

should fix #31
Let's see if github renders it correctly.
I'm not 100% sure if github works fine with the svg hosted on open-colors github.io domain.
See https://stackoverflow.com/questions/13808020/include-an-svg-hosted-on-github-in-markdown for information.
The layout isn't fixed, if anyone got a better representation idea, I can implement that. The current one is heavily inspired by the current open-color website.
The generated svg looks like this:

Hey @makepanic could you maybe also add the rgb values? It would make it easier to compare if using rgb values.

You mean as rgb(rvalue, gvalue, bvalue)?
Should it display both hex and rgb colors?

@makepanic yes. I am not sure about both, but rgb is easier to understand and compare so many people use rgb to compare how closely related colors are. This is much more complicateds with hex values.

@lukasoppermann like this?

@makepanic perfect! Thanks.

Actually if this is possible, it would be helpful to generate the same picture with a deuteranopia and protanopia filter as well. Some colors are pretty similar if one has this "impairment" so this would be good to know when designing. Otherwise contrast might be a problem.

I've integrated https://www.npmjs.com/package/color-blind which provides many color blindness transformation methods.
Do you only want deuteranopia and protanopia or all, provided by the library?
Should the complete output be transformed? That is including printed rgb values.
Here's an example output using deuteranopia:

Hey @makepanic this is pretty nice. Including all might be a nice idea, however I think deuteranopia and protanopia are by far the most common.
Another idea for a visual would be to combine them in every row like this (just a mockup):

This would make it easier to see the color you want in all forms, however it might also make it a little confusion, I am not really sure. If so, the deuteranopia and protanopia should probably just be somewhere in a legend, where it explains that the first row isdeuteranopia and the second protanopia. Otherwise it would be quite a bit of repetition.

I'm not a designer, so maybe we should wait for input from others?
Alternatively, we could split color-blindness generation into a different issue/PR.
That'll allow us to finish the color grid generation first and iterate on it later.
cc: @Larpon @yeun suggestions?

@makepanic splitting it up into 2 PRs sounds good to me.

Yup - this is cool stuff. Including it somewhere in the README.md would close #31 IMHO. I don't have any designer glasses either. I was just looking for something to showcase what the project was about :)

@makepanic Thanks, nice work! I really love this and also thanks @lukasoppermann for the idea. There's one thing I need to point out; The deuteranopia and protanopia is a bit different with Photoshop preview mode (which I checked). On the Photoshop, deuteranopia and protanopia looks like this:

protanopia

deuteranopia

I need to check why the both outputs are diffenent. Before then, would you please comment out color-blindness preview emition part in this PR?

@yeun i rebased without the color blindness feature.
I still don't know for sure if github allows the svg linking, so we have to redeploy the website assets to see if it works.
The difference between PS and color-blind could be related to https://github.com/skratchdot/color-blind/issues/1

@makepanic Seems good!


vscode: 1.51.1 -> 1.52.1

Motivation for this change
Upgrades vscode from 1.51.1 to 1.52.1
This PR was automatically generated by nixpkgs-upkeep.

CI workflow that created this PR.
Internal tag: be18e71cb4d013e037ddf2b4a3424571.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Works on nixos-unstable for me!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/speeding-up-vs-code-update-merges/10652/1


Notification to NameTracker, and methods to create the relationship

Migration

Rename the table from notifications to name_trackers
Add a record to interests corresponding to each record in name_trackers

App

Rename the class from Notification to NameTracker, update calls to Notification throughout the app
Add NameTracker to Interest.all_type_tags and a validator for Interest.target_type
Have the "Email Tracking" form create, update or delete an Interest at the same time as the NameTracker with an association between the records
Make it that deleting an Interest targeting a NameTracker deletes the NameTracker, and vice versa

Test

Add  Interest fixtures for NameTrackers
Add tests, adjust expectations

Coverage decreased (-0.009%) to 92.611% when pulling c04942c3fb18ed8b78b2568707913187f5c354ef on nimmo-notifications-to-name-trackers into 12c443d70f53e7df72c8425b98a75dd596313d24 on master.

OK, shall I merge this, and the next one? They're not that complicated.
I kept them separate to facilitate review, but i'm not sure anyone actually wants to review them.
Feel free in the future to drop a note that you'll pass on reviewing.
If i'm not confident about the code I'll say so.

Oh man, I'm sorry, I must have forgotten about this PR.  I don't have any
more time to look at PRs now than I have had for the past few days.  And it
doesn't look good for the rest of the week.
On Sun, Dec 18, 2022 at 1:19 PM andrew nimmo @.***>
wrote:

OK, shall I merge this, and the next one? They're not that complicated.
I kept them separate to facilitate review, but i'm not sure anyone
actually wants to review them.
Feel free in the future to drop a note that you'll pass on reviewing.
If i'm not confident about the code I'll say so.
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1239#issuecomment-1356848854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNKF6LSFCU236LLTGMDWN5IULANCNFSM6AAAAAATAKOOU4
.
You are receiving this because your review was requested.Message ID:
@.***>

All good. Thank you for the guidance at the outset!

Nimmo:
Sorry to be so negligent in reviewing your PRs.
If you like, I'll try to find time to review this this afternoon. But I
can't promise to have anything useful to say (and certainly cannot be as
helpful as Jason -- even his cursory reviews.
So I don't have any problem if you don't want to wait on me.
The ones that have been merged and deployed have been AFAIK problem free,
and the code itself is very nice in standardizing things with the bonus of
lots of improvements in readability and metrics.
-- Joe
PS: You beat me to it. That's very helpful as I can now merge this with my
draft PR #1241, and don't have to worry about colliding with you.
On Sun, Dec 18, 2022 at 10:26 AM Jason Hollinger @.***>
wrote:

Oh man, I'm sorry, I must have forgotten about this PR. I don't have any
more time to look at PRs now than I have had for the past few days. And it
doesn't look good for the rest of the week.
On Sun, Dec 18, 2022 at 1:19 PM andrew nimmo @.***>
wrote:

OK, shall I merge this, and the next one? They're not that complicated.
I kept them separate to facilitate review, but i'm not sure anyone
actually wants to review them.
Feel free in the future to drop a note that you'll pass on reviewing.
If i'm not confident about the code I'll say so.
—
Reply to this email directly, view it on GitHub
<
https://github.com/MushroomObserver/mushroom-observer/pull/1239#issuecomment-1356848854
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAYTNNKF6LSFCU236LLTGMDWN5IULANCNFSM6AAAAAATAKOOU4
.
You are receiving this because your review was requested.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1239#issuecomment-1356849748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALDFHL6IOAB3KSNK4P27DWN5JMFANCNFSM6AAAAAATAKOOU4
.
You are receiving this because your review was requested.Message ID:
@.***>

Thanks Joe, there’s another one merging in a minute.

I hope i’m not doing anything that makes you feel they’re unwelcome, they always improve my code and you catch things I don’t!
Anything you have time for is welcome, and if not — please just leave a comment that you’ll pass.
AN

On Dec 18, 2022, at 10:47 AM, Joseph D. Cohen @.***> wrote:
Nimmo:
Sorry to be so negligent in reviewing your PRs.
If you like, I'll try to find time to review this this afternoon. But I
can't promise to have anything useful to say (and certainly cannot be as
helpful as Jason -- even his cursory reviews.
So I don't have any problem if you don't want to wait on me.
The ones that have been merged and deployed have been AFAIK problem free,
and the code itself is very nice in standardizing things with the bonus of
lots of improvements in readability and metrics.
-- Joe
PS: You beat me to it. That's very helpful as I can now merge this with my
draft PR #1241, and don't have to worry about colliding with you.
On Sun, Dec 18, 2022 at 10:26 AM Jason Hollinger @.***>
wrote:

Oh man, I'm sorry, I must have forgotten about this PR. I don't have any
more time to look at PRs now than I have had for the past few days. And it
doesn't look good for the rest of the week.
On Sun, Dec 18, 2022 at 1:19 PM andrew nimmo @.***>
wrote:

OK, shall I merge this, and the next one? They're not that complicated.
I kept them separate to facilitate review, but i'm not sure anyone
actually wants to review them.
Feel free in the future to drop a note that you'll pass on reviewing.
If i'm not confident about the code I'll say so.
—
Reply to this email directly, view it on GitHub
<
https://github.com/MushroomObserver/mushroom-observer/pull/1239#issuecomment-1356848854
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAYTNNKF6LSFCU236LLTGMDWN5IULANCNFSM6AAAAAATAKOOU4
.
You are receiving this because your review was requested.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1239#issuecomment-1356849748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALDFHL6IOAB3KSNK4P27DWN5JMFANCNFSM6AAAAAATAKOOU4
.
You are receiving this because your review was requested.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub https://github.com/MushroomObserver/mushroom-observer/pull/1239#issuecomment-1356852661, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAO3TP6Z2VRL7XFWP2IFEE3WN5L25ANCNFSM6AAAAAATAKOOU4.
You are receiving this because you modified the open/close state.


Can't compile BLE stuff since IDF update

Hi,
I updated IDF (and recursively the BLE submodule, but dunno if there were any changes) some days ago and since then i can't compile anymore.. Has someone encountered similar issues? Here are the error outputs:
https://pastebin.com/ft5CrRLh
Kind regards :)

When did you last refresh the BLE code from this repository?  A few months back, Espressif changed the exposed BLE APIs in their pre-3.0 release.  This necessitated a change in the BLE C++ classes to be compatible.  Is it possible that you were running a relatively old ESP-IDF from master and now that you have pulled the latest master, you haven't also pulled the latest BLE C++ classes?

I like problems that are none in the first place and thus can be solved easily :)
Thank you for your fast and helpful reply

Pleasure my friend ... and keep coming back.  Open as many issues as desired.  When you are completely satisfied with this one, please close it out.  We walk each of the issues regularly to see if work needs done to make progress.


docs: add more examples to include/exclude

also mention skip_render can be used to exclude posts.
Recommend user to enclose value with quotes, as a respond to https://github.com/hexojs/hexo/issues/3306 https://github.com/hexojs/hexo/issues/3516.

[x] Read the theme publishing doc or plugin publishing doc.

@weyusi
Thank you for your contribution :)


[Bug]: Using the @opExample decorator crashes the compiler if the operation return type is a union

Describe the bug
Consider an operation defined like this:
@get op list(param: string): ListResponse | TypicalErrorResponses
where
model GenericOKResponse<T> {
    ...OkResponse;
    @header contentType: "application/json";

    @bodyRoot
    body: T
}

model ListResponse is GenericOKResponse<ListItems>

alias TypicalGetErrorResponses = UnauthorizedResponse | NotFoundResponse | BadRequestResponse

When adding an @opExample decorator to such an operation, the compiler crashes:
Emitter "@typespec/openapi3" crashed! This is a bug.
Please file an issue at https://github.com/microsoft/typespec/issues

TypeError: Cannot read properties of undefined (reading 'get')
    at serializeObjectValueAsJson (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/compiler/src/lib/examples.ts:45:40)
    at serializeValueAsJson (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/compiler/src/lib/examples.ts:32:14)
    at getExampleOrExamples (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:1206:18)
    at getExamplesForBodyContentEntry (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:1183:12)
    at getBodyContentEntry (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:1234:14)
    at emitResponseContent (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:1038:26)
    at emitResponseObject (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:994:5)
    at emitResponses (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:946:9)
    at emitOperation (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:920:5)
    at getOpenApiFromVersion (file:///Users/dmytrol/externalapi.definitions/node_modules/@typespec/openapi3/src/openapi.ts:771:11)

Reproduction
I've launched compilation under the debugger and here're my observations:

The "offending" line (in transpiled JavaScript) is const definition = type.properties.get(propValue.name);
The value of the type parameter in the call to serializeObjectValueAsJson is { kind: 'Union, ... }`
The value of the type parameter does not have the properties property defined (quite expected IMO because "Union" is not a leaf type in a syntax tree)

I would run the risk to assume that getExamplesForBodyContentEntry should probably perform an additional "walk" over the operation's return type if the return type is a union and substitute the return type passed to serializeObjectValueAsJson with the one matching the data structure provided in returnType in the decorator itself.
Alternatively (this could be easier to implement IMO) the decorator could probably allow specifying the exact return type for a specific operation example.
Checklist

[X] Follow our Code of Conduct
[X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

Ouch, sorry about that I meant to implement that and left on leave and forgot I didn't, I'll try to get a hotfix out


Not working with Python 3.4

Hi,
It seems this code is meant for Python 2.7, is that right? Any advice for people using Python 3.4?

You can run the setup.py file by yourself with the Python3.4 interpreter.
Note that there is a typo error in util.py file (see my issue #44) so you have to fix it manually (it's quite easy to do)

Also, inside the util.py there is usage of urllib2, which is split into two packages in Python3, so you have to rewrite it too.

api密钥那个网站打不开了，无法获得，请问可以借用一下你们的api密钥么？谢谢啦大哥

重复的道歉，但这个API不会回来网上我会建议寻找一个替代解决方案


Address deprecation warnings on Release Action

Noticed
The following actions use a deprecated Node.js version and will be forced to run on node20:
softprops/action-gh-release@v1, <EMAIL_ADDRESS>
For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

For softprops/action-gh-release, we can upgrade to v2.
https://github.com/softprops/action-gh-release/blob/v2.0.9/action.yml#L64
For dev-drprasad/delete-older-releases, it looks like it's no longer maintained.
@muety Was there a particular reason for introducing this step?

Apologies to those who are watching the project and receiving an empty email, I fat-fingered the Enter key...

Thanks for bringing this up! For the delete-older-releases action: I included it simply to remove old clutter. It's not super important, but I'd still prefer if we could find a way to keep it in. Options include to (a) find an alternative on the marketplace, (b) create an own fork (:neutral_face:) and, in the worst case, (c) remove it.

Do you wanna give it a go?

I've addressed softprops/action-gh-release.
I'm more in favor of keeping releases, for the history of past release notes and artifacts.
An example where this documentation might help is when performing major version upgrades.

Alright, then let's remove the delete-release task.

FYI, I think the MSSQL tests are intermittently failing due to https://github.com/microsoft/mssql-docker/issues/895.


how to download file

hi! i already figure it out how to upload .db files, my only problem is how can i download it and save it to a specific folder?

i already figure it out thanks


[Bug report] alter mysql table set property using http request did not worked

Version
main branch
Describe what's wrong
curl -X PUT -H "Accept: application/vnd.gravitino.v1+json" \
-H "Content-Type: application/json" -d '{
  "updates": [
    {
      "@type": "removeProperty",
      "property": "key2"
    }, {
      "@type": "setProperty",
      "property": "key3",
      "value": "value3"
    }
  ]
}' http://localhost:8090/api/metalakes/metalake/catalogs/mysql_test1/schemas/test/tables/test_table1

return 200, but something was wrong:

removeProperty is not support in catalog-jdbc-mysql
setProperty did not worked , properties don't contain key3 after request success

Error message and/or stacktrace
N/A
How to reproduce
add a MySQL catalog, database, table
use bash beblow
Additional context
No response

@zhoukangcn
I remember MySQL catalog only supports setting properties with names that are recognized by MySQL engine like engine,charset, and so on, maybe I have mistaken it.

I think Gravitino server return 200, which means request success.
Yes MySQL only support properties like engine charset, so I think Gravitino server should return 4xx for request invalid.

This issue needs to be discussed and then we can reach an agreement about what to do next, so I postponed it to the next version.


Management security for TLS and certs added

Change Summary

Management security update to include tls version and certificates under a SSL Profile
Management API HTTPS update to include SSL Profile
Code modification for proper order in configuration and use of arista.avd.defined

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Code style update (formatting, renaming)
[x] Refactoring (no functional changes)
[x] Documentation content changes
[ ] Other (please describe):

Related Issue(s)

Fixes issue #662
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes

How to test

Checklist:

[ ] My code has been rebased from devel before I start
[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated molecule CI testing accordingly
[ ] All new and existing tests passed (pre-commit, make linting and make sanity-lint).

CI MKDOCS issue is related to a link change and will be fixed in #698

we should add
protocol_https_certificate:
  certificate: < full certificate as multi-line PEM string >
  private_key: < full private key as multi-line PEM string >

Should be rendered as:
management api https-commands
   protocol https certificate
   {{ protocol_https_certificate.certificate }}
   EOF
   {{ protocol_https_certificate.private_key }}
   EOF


Rate Limits documentation out of date

The API for the rate limits documentation examples are out of date.
This line here is out of date:
RateLimit.RateLimitTrackerOption = RateLimitTrackerOptions.TrackAndAwait;
It should be changed to:
Tweetinvi.RateLimit.RateLimitTrackerOption = Tweetinvi.RateLimitTrackerMode.TrackAndAwait;
Also, putting the entire namespaces in the documentation would be more helpful in finding where things are at exactly, as organization seems to change often.

I have just changed the documentation. Thank you for pointing it out.
We are starting to work on a new documentation website that should help the developers in the future.

Also, putting the entire namespaces in the documentation would be more helpful in finding where things are at exactly, as organization seems to change often.

Organization and naming has often changed and I always informed the user that it could be the case before a version 1.0 is released. Version 1.0 had a complete refactor of its namespace and some naming changes (https://github.com/linvi/tweetinvi/releases/tag/1.0 > Accessibility and consistency).
Note that Namespaces are now coherent and have a dedicated documentation pagge : https://github.com/linvi/tweetinvi/wiki/Namespaces.
Please keep reporting any problem in the documentation that you can find. I try my best to keep it up to date but I sometimes miss some of the wiki pages.


[WIP] Fix empty columnar batch in C2R/R2C.

What changes were proposed in this pull request?
java.lang.RuntimeException: Error during calling Java code from native code: java.lang.UnsupportedOperationException: batch is not intermediate Gluten batch
at io.glutenproject.columnarbatch.GlutenColumnarBatches.getNativeHandle(GlutenColumnarBatches.java:48)
at io.glutenproject.vectorized.ArrowInIterator.next(ArrowInIterator.java:37)
at io.glutenproject.vectorized.ArrowOutIterator.nativeHasNext(Native Method)
at io.glutenproject.vectorized.ArrowOutIterator.hasNextInternal(ArrowOutIterator.java:47)
at io.glutenproject.vectorized.GeneralOutIterator.hasNext(GeneralOutIterator.java:36)
at io.glutenproject.backendsapi.glutendata.GlutenIteratorApi$$anon$3.hasNext(GlutenIteratorApi.scala:314)
at io.glutenproject.vectorized.CloseableColumnBatchIterator.hasNext(CloseableColumnBatchIterator.scala:41)
at scala.collection.Iterator$$anon$10.hasNext(Iterator.scala:460)
at org.apache.spark.shuffle.GlutenColumnarShuffleWriter.internalWrite(GlutenColumnarShuffleWriter.scala:95)
at org.apache.spark.shuffle.GlutenColumnarShuffleWriter.write(GlutenColumnarShuffleWriter.scala:206)
at org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:59)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:52)
at org.apache.spark.scheduler.Task.run(Task.scala:131)
at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:506)
at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1491)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:509)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
at io.glutenproject.vectorized.ArrowOutIterator.nativeHasNext(Native Method)
at io.glutenproject.vectorized.ArrowOutIterator.hasNextInternal(ArrowOutIterator.java:47)
at io.glutenproject.vectorized.GeneralOutIterator.hasNext(GeneralOutIterator.java:36)
at io.glutenproject.backendsapi.glutendata.GlutenIteratorApi$$anon$3.hasNext(GlutenIteratorApi.scala:314)
at io.glutenproject.vectorized.CloseableColumnBatchIterator.hasNext(CloseableColumnBatchIterator.scala:41)
at scala.collection.Iterator$$anon$10.hasNext(Iterator.scala:460)
at org.apache.spark.shuffle.GlutenColumnarShuffleWriter.internalWrite(GlutenColumnarShuffleWriter.scala:95)
at org.apache.spark.shuffle.GlutenColumnarShuffleWriter.write(GlutenColumnarShuffleWriter.scala:206)
at org.apache.spark.shuffle.ShuffleWriteProcessor.write(ShuffleWriteProcessor.scala:59)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:99)
at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:52)
at org.apache.spark.scheduler.Task.run(Task.scala:131)
at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:506)
at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1491)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:509)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Is this to fix Spark UT? which UT?

Is this to fix Spark UT? which UT?

There are many Spark UT which has operator with empty schema that caused empty ColumnarBatch, such as test("copy results for sampling with replacement") in GlutenDataFrameSuite.
This change to get children's schema could not fix all cases, but PR#702 which marked the plan with empty schema to fall back, that could fix the above tests. So, I will revert this change in C2R/R2C.
As a long-term plan, we will fix the schema issue after Spark3.3, because this version could process operators with empty schema without any fallback.


Crash during Solve

What version of OR-tools and what language are you using?
Version: 8.0
Language: C#
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
Windows 10
With the attached model I get the following error during solve
batch.zip
Check failed: SolutionIsFeasible( *shared_->model_proto, std::vector(local_response.solution().begin(), local_response.solution().end())) rens_lns_default_lp_incomplete(d=0.81 s=23 t=0.10 p=1.00)
** Check failure stack trace: **
@   00007FFD7D378DDB  SWIGRegisterStringCallback_operations_research_util
@   00007FFD7D377339  SWIGRegisterStringCallback_operations_research_util
@   00007FFD7D4877B9  SWIGRegisterStringCallback_operations_research_util
@   00007FFD7DA05869  SWIGRegisterStringCallback_operations_research_util
@   00007FFD7DE0FB44  SCIPlpiWriteState
@   00007FFD7DE0E96F  SCIPlpiWriteState
@   00007FFE07D50E72  _beginthreadex
@   00007FFE08F87BD4  BaseThreadInitThunk
@   00007FFE0AAECED1  RtlUserThreadStart

I believe it is fixed on master.
The problem solved to optimality in 2 minutes on my machine (using 16 workers).
Thanks.


feat: configurable faucet address for test-validator

Problem
When using the solana-test-validator, it should be possible to run this entirely within the localhost space.
Currently there are a few services which listen on <IP_ADDRESS> by default, and have no option to configure to another address.
Summary of Changes
This PR fixes the faucet config in the test-validator, so that it runs on localhost + port 9900 (FAUCET_PORT constant from the faucet crate).
If additional configuration is required, the flag --rpc-faucet-address can be used, which is the same as the flag used in the main validator crate.
Example usage if it was required to make the faucet available to other hosts on port 9500:
solana-test-validator --rpc-faucet-address=<IP_ADDRESS>:9500
The clap arg validator ensures that any value passed will parse into a SocketAddr, otherwise an error is displayed to the user. If the flag isn't used, then the default value mentioned above is used.

any comments/suggestions?