Detect that component has not been build yet

[kind/Feature]
In the situation when a component is newly created and it doesn't have any source yet, supervisorD is restarting application over and over again. This creates a lot of ugly error messages.
It doesn't make sense to keep trying to start it if there is no application has been build yet.
odo should detect that the component has not been deployed, and prevent supevisorD from trying to restart it, until there is something.

This is one of the things that our own supervisor process, instead of a generic one, could potentially manage easily. We need to keep in mind that sooner or later, we'll need our own supervisor with a proper API to manage all these specific lifecycle events.

So, this involves

setting autostart=false in the section https://github.com/redhat-developer/odo-supervisord-image/blob/master/supervisor.conf#L1-L8
setting autostart=true via an sed command in supervisor.conf before https://github.com/redhat-developer/odo-supervisord-image/blob/master/assemble-and-restart#L83 which is triggered on first push

/remove-priority medium
/priority high

I'm assuming that this issue is affecting the cases where SourceType is local and the directory is most likely empty. It could also affect to binary type when user does something like odo create java --binary . and do odo push - and, in fact, odo push is happy to push this without errors. :wink:
Besides the popular opinion of configuring supervisorD, would does it make sense to add some checks to odo itself? I can think of two places where we can add some checks:

odo create could have a function isValidGitRepo that would check for the existence of a .git/ directory. If it's not a valid git directory, odo would raise a warning that component doesn't seem to be a valid git repo. It could also go a step further and ask the user if they're sure to create a component in such a case.
This might seem annoying at first but it will also lead to user developing a habit of cloning the git repo before doing odo create.

odo push could have a function that would interrupt the user and ask for confirmation if

it's not  a valid git repo
there's no server.js file (for nodejs component). We could make odo smart to check this for supported components.

If user says that they know what they are doing, then we go ahead and create the component for them on OpenShift cluster.

This approach adds some checks which would slow down the odo create and odo push for valid components which we have worked so hard to make as fast as we could. So I'm not suggesting that we go with this approach but I'm trying to gather feedback if it's plausible to do this.
But if we go with this approach, we would be able to give quick feedback to the user they "Hey you're missing things that make a component valid and if you choose to push this anyway, things might not work" instead of they coming back to us (technical support) with "Why is this thing not working?"
@kadel @jorgemoralespou @girishramnani wdyt?

@dharmit A git repo is not mandatory and in many cases will not be there. The essence of inner-loop is that is the workflow before you check into git, so you might not have even initialized the directory as a git repository, so not an option IMHO.
What we need to make sure is that the supervisorD starts up with stopped runtime, to prevent an overflow of error messages trying to run a non existing application, binary or source code, and that push/sync will start it up, by any possible mechanism like changing the supervisorD configuration.
My initial thought was on a dedicated supervisor that could understand this fact, but to make things easier, maybe just having the supervisor calling a wrapper script that will do this detection should do the trick for now.
The component now, will most likely not be created empty, as it used to happen before the new workflow, so this issue's relevance has decreased, as odo create will not create the component anymore in the cluster, and push will be pushing the component creation and the code itself. Still, there's some chance due to missconfiguration that should be prevented/checked, but that's it.

The component now, will most likely not be created empty, as it used to happen before the new workflow, so this issue's relevance has decreased, as odo create will not create the component anymore in the cluster, and push will be pushing the component creation and the code itself. Still, there's some chance due to missconfiguration that should be prevented/checked, but that's it.

Yes, this is not a big problem as it used to be, but It still creates some problems. First-time push can still take a long time (copying files, and downloading all dependencies from maven or npm). For this time SupervisorD is constantly restarting the run script and sometimes it can sometimes lead to unexpected situations like https://github.com/openshift/odo/issues/2224#issuecomment-539543375
I think that without big re-architecturing there is probably only one way how to achieve this.

disable autostart in a default supervisor.conf
when the main container starts, before starting supervisord, copy the supervisor.conf (from /opt/odo/conf/supervisor.conf) into the directory that is on volume, for example  ${ODO_S2I_WORKING_DIR}/odo/conf (ODO_S2I_WORKING_DIR is usually /opt/app-root)
use ${ODO_S2I_WORKING_DIR}/odo/conf/supervisor.conf as config for supervisord (instead of current /opt/odo/conf/supervisor.conf
After the sucessfull assemble execution (inside assemble-and-restart script) modify ${ODO_S2I_WORKING_DIR}/odo/conf/supervisor.conf and set autostart=true

The second step is necessary as the /opt/odo/ directory is on emptyDir volume. Each time the container is started the directory is empty and it gets populated by default files from odo-init-image


Idea for crawler upgrade

So, while manually changing all the URL's to missing files that crawler missed during the export I got an idea how to make the export process more bulletproof.
Would it be possible to crawl the exported site (assuming it is saved in a local folder within the same server) and automatically gather a list of missing files and retry the export process? Kinda like verification of the export? After the export, it should be quite easy to crawl all exported pages through and see if any 400 errors are returned.
Does this make sense for anyone else?

That. Makes. Sense!
I love it.

moving this to a Trello board for upcoming features, ideas, etc. Will make this public after cleaning it up a bit / taking out any non-public items


Guideline to Add APIKey and APISecret for App is missing

There is no guideline for where to add APIkey and APISecret on the specific machine, it should be added in the Getting Started Section

Hi @mayankagwl , Thanks for raising the issue.
As this CLI is meant for the LoginRadius Dashboard Users, we don't need to add any configuration for using this CLI.
After installing the CLI, Once you run the command lr login and successfully authenticate. The .lrcli folder will be automatically created with all required information that is needed for further dashboard related actions.
You are facing the above issue because there was some bug in the login command, which will be fixed in the next release.


ReadRequest unable to retreive payload

Question
I am using lesan 2.0.0-M11
My client has this
sendService.sendData(serverIdentity, ContentFormat.SENML_JSON, List.of("3443/0/3/"), 1000, responseCallback, errorCallback);

on the server side
 @Override
    public void dataReceived(final Registration registration, final TimestampedLwM2mNodes data, final SendRequest request) {
        CommunicationProtocolThreadLocal.setCommunicationProtocol(CommunicationProtocolEnum.LWM2M);
        final LwM2mPath lwM2mPath = new LwM2mPath(3443, 0, 3);
        final String prettyString = data.getNodes().values().stream().findFirst().get().toPrettyString(lwM2mPath);
        //TODO how to get the data from here
        //final LwM2mNodeOpaqueEncoder lwM2mNodeVisitor = new LwM2mNodeOpaqueEncoder();
        // data.getNodes().values().stream().findFirst().get().accept((LwM2mNodeVisitor) lwM2mNodeVisitor);
     }

I do have the data, I can see it when debugging but I can't find a way to get it out

There is no .getValue function or anything similar. I also tried the LwM2mNode functions like the toPrettyString which tells me the correct size and path but not the payload. I can't make the accept() work, but I don't know if that would help either.
I could not find any examples or detailed documentation about this anywhere, other than reading the code, the Javadocs, and the forum, if you know anywhere else I could read about this, it would also be helpful.
Thanks!

getNodes() could return object, object instance, single resource, multiple resource or resource instance.
So it's up to you to cast the node to the expected type .
LwM2mResource resource = (LwM2mResource) data.getNodes().get(new LwM2mPath("3443/0/3/"));
resource.getValue();

Yup that was it.. thanks! ^^


About gradient penalty

Hi, I see that in your paper, the discriminator is updated with

I think the D appeared here means a "discriminator with sigmoid",
But in the implementation, we always use "tf.nn.sigmoid_cross_entropy_with_logits" instead of explicit calculation of the sigmoid function.
In your paper, I think the gradient penalty is based on "discriminator with sigmoid"
But in your codes,
gradients = tf.gradients(discriminator(interpolates), [interpolates])[0]
this is the gradient term w.r.t "discriminator without sigmoid"

And limit the gradient term w.r.t "discriminator with sigmoid" would cause numerical problem.

We can just use just D(x) since sigmoid is monotonic


What is port 3033 used for?

I've self hosted this only exposing port 3000 and everything seems to work. Is port 3033 supposed to be for websocket communication between Interval server and the client SDK? Or between Interval server and Interval's frontend? Both the client and server seem to work fine without it being exposed. Am I missing out on anything?

Based on https://github.com/interval/server/pull/20/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L65 which removed it from the readme, I'm assuming it's not used? Or used to be used for something?


[Card] Inverted arrows in expandable cards

Problem description
Arrows in expandable cards seem inverted.

Card Status
material-ui
material design

Expanded
:arrow_up:
:arrow_down:

Closed
:arrow_down:
:arrow_up:

Here is a simple card component (expanded):

And here is a picture from Material Design Cards guidelines:

I have also checked paper-card component in polymer.
Steps to reproduce
No particular steps required to reproduce this issue, simply instantiate a card that can be expanded.
Versions

Material-UI: 0.15.0
React: 15.1.0
Browser: All

@mbasso I'm going to go out on a limb here, and see you've found a mistake in the spec. (Not much of a limb, as the spec has more than a few mistakes and inconsistencies).
If you look at Expansion panels, you'll see the opposite design / behaviour.
In general, the icon should indicate the intent of the button, in this case, down to expand downwards, and vice versa. Nested List follows a similar pattern.

@mbrookes you're right. I have just checked your link and seems to be an error in the spec. Thanks a lot for the clarification.

NP, thanks for the detailed report and for following through with a PR. 👍


Why keybinder works in Wayland using gtk2 but doesn't work using gtk3 gir bindings?

Hi there,
I've been using keybinder3 with gir bindings for a while. Now I'm looking for a way to make it work in Wayland session. After doing some research I found this:
GTK3 + gir bindings - works in X session, doesn't work in Wayland
GTK2 + python-keybinder lib - works in X and Wayland session
Can someone explain this behavior please?
Thanks.

Because Gtk2 applications are ran in XWayland. env GDK_BACKEND=x11 would make a Gtk3 application run under XWayland too.

Awesome. Now my app runs in Wayland
Thanks a lot @TingPing

Just to state the obvious, forcing using X11 is of course not ideal.

Yeah, you are right.
However there is no way to programmatically bind a hotkey in Wayland, is there?

No. One one of doing it is exposing an action in your application and then the user can configure their compositor to call that action by keypress.

Like a dbus method?
Could you please share a link where I can read more about how to do that the right way?
After discovering that there is no way of binding a hotkey using API I thought of making an executable that would call a dbus method of my app. But I think binding a hotkey to run a program may result in a noticeable delay :thinking:

@gornostal

Use GApplication: https://wiki.gnome.org/HowDoI/GtkApplication
Add your GAction: https://wiki.gnome.org/HowDoI/GAction
Call it over dbus

Thanks :)


AMA-29 added json schemas for underlying business objects

Ready for merge

Please review components against the XSD items

Bracket Blindness (bb)
noticed some errors in some of the schemas so will amend


Off-by-one issue in the DataFrame - Last line is not shown in dataframe component

I noticed that the last line in a dataframe is missing when you try to scroll down...
import streamsync as ss
import pandas as pd

initial_state = ss.init_state({
    "df": pd.DataFrame(
        {
            "col_a": list(range(11)),
            "col_b": list(range(11,0,-1))
        }
    )
})

This is the dataframe showing scrolled down to the bottom...Only row 10 is shown (index 9), not 11 (index 10)

I tracked it down to this statement in CoreDataframe.vue
const rowOffset = computed(() => {
	let maxOffset: number;
	if (fields.wrapText.value == "yes") {
		maxOffset = rowCount.value - 1;
	} else {
		maxOffset = rowCount.value - displayRowCount.value;
	}
	const newOffset = Math.min(
		Math.floor(relativePosition.value * maxOffset),
		maxOffset,
	);
	return newOffset;
});

Math.floor should be Math.ceil.
This works:
const rowOffset = computed(() => {
	let maxOffset: number;
	if (fields.wrapText.value == "yes") {
		maxOffset = rowCount.value - 1;
	} else {
		maxOffset = rowCount.value - displayRowCount.value;
	}
	const newOffset = Math.min(
		Math.ceil(relativePosition.value * maxOffset),
		maxOffset,
	);
	return newOffset;
});

relativePostion.value never reaches 1, so always maxOffset -1

Thanks for the test case and the fix. It was a great help. I have reproduced the bug on firefox. I was confused first because the component was working fine on chrome / chromium.
I will open the PR.

Fixed in v0.3.0


"Last Updated At" is wrong for tap-salesforce (on GitLab)

https://hub.meltano.com/taps/salesforce says “Last Updated At 02 Nov 2018”, while the last commit on https://gitlab.com/meltano/tap-salesforce is from 7 months ago. Not sure if this is related to it being on GitLab not GitHub.

cc @tayloramurphy @pnadolny13

@DouweM ah I think I know whats going on. Those repo metrics should only come through for github repos. It looks like its referencing https://github.com/meltano/tap-salesforce instead of the gitlab repo. Right now we send repo metrics without the github prefix i.e. meltano/tap-salesforce with the understanding that we only pull from github. In the next metrics iteration we're sending the full repo url so https://github.com/meltano/tap-salesforce.
This is a bug with the way that we're rendering the repo data. I don't think were checking to make sure the variant repo is a github repo before matching (line https://github.com/meltano/hub/blob/79819ea04601ebde833fd781764403f88481972c/_plugins/plugin_enricher.rb#L78) on namespace so in this case we have an accidental match. We should probably check that the variant repo matches the namespace AND is a github repo until the new metrics are in use. Potentially needing to update https://github.com/meltano/hub/blob/79819ea04601ebde833fd781764403f88481972c/_layouts/meltano_plugin.html#L67 as well.

@pnadolny13 Ah, makes sense! If you think you can fix this in a few minutes, feel free to submit a PR -- that'll be faster than waiting for this to make it onto the engineering board :)

@DouweM I opened https://github.com/meltano/hub/pull/719 that fixes it!


[WIP] Support for hidden columns in reports and views

Columns, including headers, with MiqReport#col_options[<column_name>][:hidden] == true should not
are included in html, pdf, text output formats and only be included in csv
UI changes in https://github.com/ManageIQ/manageiq-ui-classic/pull/3564
/cc @dclarizio

@miq-bot add_label transformation

I was able to validate this PR by added the following changes in the ui-classic repo.
--- a/product/views/VmOrTemplate.yaml
+++ b/product/views/VmOrTemplate.yaml
@@ -27,6 +27,12 @@ cols:
 - allocated_disk_storage
 - last_scan_on
 - region_description
+- uid_ems
+
+col_options:
+  uid_ems:
+    :hidden: true
+

 # Included tables (joined, has_one, has_many) and columns
 include:
@@ -75,6 +81,7 @@ headers:
 - Allocated Size
 - Last Analysis Time
 - Region
+- uid_ems

@gmcculloug This should be good to go

@gtanzillo Please add BZ link.

Gaprindashvili backport details:
$ git log -1
commit 0a950abc0a2fefadf4b52aa7e09b9e1a2ab7ea56
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Tue Mar 20 10:35:36 2018 -0400

    Merge pull request #17133 from gtanzillo/report-hidden-cols

    Support for hidden columns in reports and views
    (cherry picked from commit 220677511a07ad56f4587133269c62a3ecde3c98)


Change SftpClient structure so that SFTP keys don't hang around in memory

Idea from @kevinrobinson:

Something like it just reads [SFTP keys] from disk when it needs it but doesn't hang around in memory except for in ENV (which will always have sensitive bits).

Fixed by @kevinrobinson in #1066.


WebDriver server randomly times out

Hi there!
So I have been having there a weird error in which my build would fail after 100 - 200 builds but it happens very randomly after it goes back to normal like nothing had happened, it's an odd behavior. my test does not get marked as fail but the web driver times out which is very odd, I have the build run every two minutes and also autorotate the build after 20 days.
Bug report

Node Version: 8.5.0
Protractor Version: 5.3.2
Browser(s): chrome
Operating System and Version Amazon Linux
Chromedriver Version 2.40
Webdriver Manager 12.0.6

Conf File
exports.config = {
  seleniumServerJar: 'selenium-server.jar',
  specs: ['tests/**/*.js'],
  capabilities: {
    browserName: 'chrome',
    chromeOptions: {
      args: ["--headless", "--disable-gpu", "--window-size=800,600"]
    }
  },
  params: {

  },

  onPrepare: function () {
    let jasmineReporters = require('jasmine-reporters');
    jasmine.getEnv().addReporter(new jasmineReporters.JUnitXmlReporter({
      consolidateAll: false,
      savePath: 'results',
      filePrefix: ''
    }));
  },
  jasmineNodeOpts: {
    print: function () {}
  }
};

Error Output
[00:20:00] I/launcher - Running 1 instances of WebDriver
[00:20:00] I/local - Starting selenium standalone server...
[00:20:30] E/launcher - Error: Error: Timed out waiting for the WebDriver server at http://<IP_ADDRESS>:35816/wd/hub
    at Error (native)
    at onError (/usr/lib/node_modules/protractor/node_modules/selenium-webdriver/http/util.js:102:16)
    at process._tickCallback (internal/process/next_tick.js:109:7)
[00:20:30] E/launcher - Process exited with error code 100
Build step 'Execute shell' marked build as failure

Having the same issue.

@bdbrown4  and @tiagocpeixoto no luck on this issue yet. sorry!

I also have this issue randomly. Please fix, it's very annoying!


add discord reference

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation addition

Checklist

[ ] I tested my contribution locally and it seems to work fine.
[ ] I locally ran pytest inside the repository and no unexpected problems came up.
[x] I have adjusted the docstrings in the code appropriately.
[x] I have documented the effects of my code changes in the documentation doc/.
[x] I have added a note to release notes doc/release_notes.rst.
[x] I have used pre-commit run --all to lint/format/check my contribution

ready to review/merge


Start Error

Hello I have another problem.. :)
After successful build I installed: way-cooler-bg  wc-grab  wc-lock
via some part of this script:  https://way-cooler.github.io/way-cooler-release-i3-default.sh
and run way-cooler.
It was started, but I got this output:
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:191 Lua: awaiting request
thread 'main' panicked at 'Could not talk to Way Cooler -- is Way Cooler running?: D-Bus error: The name org.way-cooler was not provided by any .service files (org.freedesktop.DBus.Error.ServiceUnknown)', /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/result.rs:868
stack backtrace:
   1:     0x561f71073dcc - std::sys::imp::backtrace::tracing::imp::write::hf33ae72d0baa11ed
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:511
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:495
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:471
   8: core::panicking::panic_fmt
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:42
   2:     0x561f71076cbe - std::panicking::default_hook::{{closure}}::h59672b733cc6a455
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:351
   3:     0x561f710768c4 - std::panicking::default_hook::h1670459d2f3f8843
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:367
   4:     0x561f7107715b - std::panicking::rust_panic_with_hook::hcf0ddb069e7beee7
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:555
   5:     0x561f71076ff4 - std::panicking::begin_panic::hd6eb68e27bdf6140
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:517
   6:     0x561f71076f19 - std::panicking::begin_panic_fmt::hfea5965948b877f8
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:501
   7:     0x561f71076ea7 - rust_begin_unwind
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:477
   8:     0x561f7109efdd - core::panicking::panic_fmt::hc0f6d7b2c300cdd9
             at /checkout/src/libcore/panicking.rs:69
   9: core::result::unwrap_failed
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/panicking.rs:69
   9:     0x561f70f27e28 - core::result::unwrap_failed::h2ed6b20536231858
  10:     0x561f70f2ea44 - way_cooler_bg::get_screen_resolution::h0c36067ed0415487
  11:     0x561f70f2b08b - way_cooler_bg::main::h16eae7f9bfaedf81
  12:     0x561f7107e01a - __rust_maybe_catch_panic
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libpanic_unwind/lib.rs:98
  13:     0x561f710778c6 - std::rt::lang_start::hd7c880a37a646e81
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panicking.rs:436
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/panic.rs:361
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/rt.rs:57
  14:     0x7f7b457eb82f - __libc_start_main
  15:     0x561f70f272b9 - _start
  16:                0x0 - <unknown>
             at /checkout/src/libcore/macros.rs:29
  10: way_cooler::ipc::session::DBusSession::create
             at /checkout/src/libcore/result.rs:761
             at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/ipc/session.rs:26
  11: std::panicking::try::do_call
             at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/ipc/mod.rs:34
             at /checkout/src/libstd/panic.rs:296
             at /checkout/src/libstd/panicking.rs:454
  12: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  13: <F as alloc::boxed::FnBox<A>>::call_box
             at /checkout/src/libstd/panicking.rs:433
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/thread/mod.rs:360
             at /checkout/src/liballoc/boxed.rs:640
  14: std::sys::imp::thread::Thread::new::thread_start
             at /checkout/src/liballoc/boxed.rs:650
             at /checkout/src/libstd/sys_common/thread.rs:21
             at /checkout/src/libstd/sys/unix/thread.rs:84
  15: start_thread
  16: clone

Try dbus-launch --exit-with-session way-cooler when launching Way Cooler

@Timidger ok now I have this:
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:348 Updating programs:x11_bar = String(
    "lemonbar"
)
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:348 Updating programs:lock_screen = String(
    "wc-lock"
)
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:348 Updating mouse:lock_to_corner_on_resize = Boolean(
    false
)
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:191 Lua: awaiting request
 TRACE [callbacks] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/callbacks.rs:67 view_props_changed for view WlcView { handle: 2, title: "", class: "Background" }: PROPERTY_APP_ID
 ERROR [modes::default] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/modes/default.rs:179 Could not update title for view WlcView { handle: 2, title: "", class: "Background" } because ViewNotFound(
    WlcView {
        handle: 2,
        title: "",
        class: "Background"
    }
)
 TRACE [callbacks] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/callbacks.rs:67 view_props_changed for view WlcView { handle: 2, title: "Background Color: 102197331", class: "Background" }: PROPRETY_CLASS
 ERROR [modes::default] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/modes/default.rs:179 Could not update title for view WlcView { handle: 2, title: "Background Color: 102197331", class: "Background" } because ViewNotFound(
    WlcView {
        handle: 2,
        title: "Background Color: 102197331",
        class: "Background"
    }
)
 TRACE [callbacks] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/callbacks.rs:49 view_created: WlcView { handle: 2, title: "Background Color: 102197331", class: "Background" }: "Background Color: 102197331"
 TRACE [modes::default] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/modes/default.rs:105 Setting background: Background Color: 102197331

Ok it looks like it's authenticating properly, and the background is attaching to it. If you didn't modify the default configuration, you should have a purple background on your main output.
The error about updating the title is a misnomer.
The lock screen program and screen capture are programs that should be spawned be the user (either via a keybinding you bind to spawn it, or manually using dmenu or a terminal). Is there some issue with the that I'm not seeing?

@Timidger No there is only problem with the Background error
Do you know how can I fix it??

Is it only an error in the log? Eg does the background display or not? If it does display you can happily ignore the "error". It shouldn't be causing Way Cooler to panic (ie crash). If it does, let me know and include a full log.

@Timidger No way-cooler doesn't work.
I am trying it in virtual box and when I run command: dbus-launch --exit-with-session way-cooler
And I see this:

Only black background and arrow. (I can't to do anything..)
Here is the full log: https://pastebin.com/JgHhwR0C

If you're running in virtual box, please ensure that it's allowing your key presses to go through. Looking at the logs, it's defaulting to the pre-compiled init file (since you don't have one in your virtualbox session). By default, we use "alt" as the meta key to do an action, e.g "alt+enter" will spawn a terminal (defaults to weston-terminal, which will obviously fail if you don't have that installed) and "alt+d" will spawn dmenu (again, assuming you have it installed).
By googling around, it looks like virtualbox doesn't pass through the alt key. Try allowing it to pass through, or download the init.lua file from the repo and change the meta key to something that will pass through (e.g "Ctrl"). If you go with the second option, put the configuration file in ~/.config/way-cooler/init.lua.

@Timidger ok I tryed run: Alt+Enter
and I got:
 INFO [modes::default] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/modes/default.rs:251 [key] Found an action for Keypress(MOD_ALT, Some("Return")), blocking event
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:202 Handling a request
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:287 Lua: handling keypress Keypress(MOD_ALT, Some("Return"))
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:297 Handled keypress okay.
 TRACE [lua::thread] /root/.cargo/registry/src/github.com-1ecc6299db9ec823/way-cooler-0.6.0/src/lua/thread.rs:191 Lua: awaiting request
weston-terminal: clients/window.c:5077: window_create_internal: Assertion `custom || display->xdg_shell || display->ivi_application' failed.

and weston-terminal I have installed.
Shortcut for exit way-cooler: Alt+Shift+Escape works fine.
And I am also trying move mouse in vitrualbox, but doesn't work..

Sounds like the xdg shell versions don't line up properly. Can you post the output of ls -l /usr/share/wayland-protocols/unstable/xdg-shell/? We (half) support v6, and you'll need that to use Way Cooler properly. Older versions of Way Cooler supported v5. It's potentially possible to run the current version with an old version of xdg_shell, but you'd have to downgrade your wlc version to before they changed it (and I'm pretty sure that version would be ABI-incompatible, since there have been quite a few changes since then). If you don't have v6, I suggest using your package manager + google to find out how to get v6 on your machine.
Assuming you have xwayland installed, you can launch other applications with dmenu ("alt+d") and see if those work. You can also change your default terminal emulator if you follow the steps I outlined in my previous comment and add a custom init.lua to ~/.config/way-cooler/.

@Timidger  Hello so I installed Way-cooler on my pc with your fixed installation script: https://github.com/way-cooler/way-cooler/issues/326#issuecomment-318848444
And now it starts fine. :)
Xdg-shell I would like replace by gnome-terminal if is it possible..
For another problems with applications in way-cooler I opened new issue: https://github.com/way-cooler/way-cooler/issues/357 ;)


Readme clarifications

Had to do some searching to figure out what was meant by "open up coverage/index.html in your browser", so I changed that verbiage around a little to make it crystal clear for anyone looking that up in the future.
Also modified the line lengths throughout the readme for consistency (and maybe mild neuroticism, too).
Hope that this is helpful, rather than pedantic. I usually assume that if I have an issue, might be something that another person experiences, too!

Please let me know if this needs any further modifications!

All great thank you for your contribution! :tada:


MudTable Can only insert a new line

Bug type
Component
Component name
MudTable
What happened?
Only one new line can be inserted.
Expected behavior
It should be possible to add several new rows to the table
Reproduction link
https://try.mudblazor.com/snippet/QOmGYRPTTlJKCTGi
Reproduction steps

click on the Button New Row
2.Enter a row and click on end edit.
3.Click again on New Row nothing happens.
...

Relevant log output
No response
Version (bug)
6.0.7
Version (working)
5.1.5
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

haha, me too.

Seems like a duplicate of
https://github.com/MudBlazor/MudBlazor/issues/4153


Fix JavaEE related dependencies

#12760 Upgraded jakarta libraries to the latest Jakarta EE (read more here), but all the libraries in Pinot are still following Java EE.
This PR downgraded the library versions to be Java EE compatible:
    <jakarta.servlet-api.version>4.0.4</jakarta.servlet-api.version>
    <javax.servlet-api.version>4.0.1</javax.servlet-api.version>
    <jakarta.annotation-api.version>1.3.5</jakarta.annotation-api.version>
    <javax.annotation-api.version>1.3.2</javax.annotation-api.version>
    <jakarta.validation-api.version>2.0.2</jakarta.validation-api.version>
    <javax.validation-api.version>2.0.1.Final</javax.validation-api.version>
    <jakarta.xml.bind-api.version>2.3.3</jakarta.xml.bind-api.version>
    <javax.jaxb-api.version>2.3.1</javax.jaxb-api.version>
    <jakarta.ws.rs-api.version>2.1.6</jakarta.ws.rs-api.version>
    <javax.ws.rs-api.version>2.1.1</javax.ws.rs-api.version>
    <jakarta.activation-api.version>1.2.2</jakarta.activation-api.version>

Also downgrade libthrift from 0.20.0 to 0.18.1 which is the last version using Java EE

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (59551e4) to head (a17eee0).
Report is 396 commits behind head on master.

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13058       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2427        -9
  Lines        133233   133012      -221
  Branches      20636    20628        -8
=============================================
- Hits          82274        0    -82274
- Misses        44911   133012    +88101
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
0.00% <ø> (-61.75%)
:arrow_down:

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


relation graph

Project Abstract

Rlation Graph is a substrate pallet that allows anyone to use GraphDB in Substrate platform.
Rlation Graph provides organizations with ready-to-use GraphDB service for successfully running Dapps on the Substrate.  using Rlation Graph Dapps builders can focus on bussiness logic by removing the complexities of Substrate.

For which grant level are you applying?

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $50,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for > $100k Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI/USDT) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the terms and conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted.

How Did You Hear About our grants program?

[x] Social Media
[ ] Hackathon
[ ] Personal Recommendation
[ ] Substrate Builders Program
[ ] Investor/VC
[ ] Online Search
[ ] Other: _______

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Btw. only committee members can approve applications.


Build GlobalHeader component

Global Header
Figma: https://www.figma.com/file/Lo1ZcBOO9t4QRbX2I0PwBQ/RBB?node-id=427%3A670
The GlobalHeader component should consist of a SVG version of the RBB logo that when clicked, navigates to the home page.
Pages in the navigation should follow this structure:
Home (slug: "/")
About (slug: "/about")
Businesses (slug: "/businesses")
Allies (slug: "/allies")
Resources (slug: "/resources")
Desktop

Small Screens

As screen size is reduced, the navigation within the GlobalHeader should become hidden behind a hotdog menu. Upon click of the hotdog, the navigation will appear in a row layout.

Ticket has been claimed in Trello.

Merged with #54


Installing cport on local computer or request of running 5-6 protein files on your local computer

Hi can you guide me how can I go about installing cport locally or If you can run my left protein files. on your computer, We will give you requied credit.

Read the installation instructions :-)
https://github.com/haddocking/cport/blob/main/INSTALL.md


Update gems for April 25, 2020

Major

[x] Updates rack-mini-profiler from 1.1.4 to 2.0.1 (Changelog) (Upgrade info)
[x] Updates rspec-rails from 3.9.0 to 4.0.0 (Changelog)

Minor

[x] Updates aws-sdk-s3 from 1.55.0 to 1.63.0 (Changelog)
[x] Updates aws-sdk-ses from 1.27.0 to 1.28.0 (Changelog)
[x] Updates bootstrap from 4.3.1 to 4.4.1 (Diff)
[x] Updates byebug from 11.0.1 to 11.1.3 (Changelog)
[ ] Updates capybara from 3.29.0 to 3.32.1 (Changelog)
[ ] Updates database_cleaner from 1.7.0 to 1.8.4 (Changelog)
[ ] Updates httparty from 0.17.1 to 0.18.0 (Changelog)
[ ] Updates newrelic_rpm from <IP_ADDRESS>9 to <IP_ADDRESS>4 (Changelog)
[ ] Updates nilify_blanks from 1.3.0 to 1.4.0 (Changelog) (broke user-spec tests)
[ ] Updates rack-cors from 1.0.6 to 1.1.1 (Changelog)
[ ] Updates simplecov from 0.17.1 to 0.18.5 (Changelog)
[ ] Updates tinymce-rails from 5.1.4 to 5.2.2 (Changelog)
[ ] Updates webdrivers from 4.1.3 to 4.3.0 (Changelog)
[ ] Updates webmock from 3.7.6 to 3.8.3 (Changelog)

Patch

[ ] Updates apipie-rails from 0.5.16 to 0.5.17 (Changelog)
[ ] Updates html-proofer from 3.15.0 to 3.15.3 (Diff)
[ ] Updates pg_search from 2.3.0 to 2.3.2 (Changelog)
[ ] Updates selenium-webdriver from 3.142.6 to 3.142.7 (Changelog)
[ ] Updates test-unit from 3.3.4 to 3.3.5 (Diff)

Superseded by #1489
I'll copy these links over!


feat: Replace nginx snippet annotation with custom header annotation

Our cluster does not allow snippet annotations by default and changing the configuration would be complicated.
But the snippet is not actually needed, since the same thing can be achieve using a config map and the custom-headers annotation.

Does this functionality hold harmless users that do not require this functionality?
If so, LGTM. Can you increment the version in Chart.yaml?

Overall, looks good. I would just worry about breaking functionality for other users that are using Nginx Ingress with your changes.
Also, since this is a feature release, could you update the Chart.yaml to increment the minor version of the release?

Changed the version :)
I'm not sure if it would interfere with other users. There was no way before to set any custom headers before, so I'm not overriding anything. Also, the Request-Id header is still only added if the nginxIngressAnnotations are activated, which is the same behavior as before.

Hallo @HerrSpeck, danke für die PR
I am adding some review points.

Thanks for the response! :)
You're totally right, I moved the config map to the configmap.yaml file :) and I also fixed the typo, not sure how that happened 😅
I did some digging into the global-allowed-response-headers flag and from what I can tell this is not actually a key in the custom-headers config map, but is instead defined in the nginx-configuration config map. As far as I can tell, it controls which headers are allowed in general and as soon as you would like to set custom headers, you also have to specify this value and "whitelist" the custom headers.
So I added another config map for the nginx-configuration and I put it in the same namespace as the ingress configuration. Kind of lost at this point though, because I'm not sure if that's enough for the value to be applied or if we still have to add a reference to this config map somewhere. My current understanding is that this should suffice, but maybe you can help me out if I do in fact have to reference it somewhere else :)

Hi there @guerzon !
I had a colleague take a look at the problem as well and we found some more information that I would like to share:
It looks like this is a flag/setting on the ingress-controller and I couldn't find any way to configure this using these charts at all. Instead, as the name suggests, this is a global configuration (like the allow-snippet-annotations flag that caused this whole issue on our side) that has to be applied directly to the ingress-controller. Therefore, I reverted the changes where I introduced an additional config map that I tried to use to allow the correct headers.
BUT: I also found out that the allow-snippet-annotations configuration is deprecated and should not be used, because of security issues.
Therefore, I still think this is the correct way to solve this issue and I would suggest that we add a notice/warning to the README, that tells readers to configure the global-allowed-response-headers field of their ingress-controller to allow the Request-Id header. What do you think?

Thanks for the feedback @HerrSpeck. I had more time to test this and I can see no issue with not adding global-allowed-response-headers.
PR looks good and ready to merge, but please rebase and fix the merge conflict. Thanks.

@guerzon Alright, sounds great :) I rebased the pr and fixed the merge conflicts. Setting 0.25.0 as the new version is alright? Or should I just increase the patch version instead?

This broke my Setup. Not exactly sure why yet. Gives me 503 now, but other then in the nginx log I can not see any errors. Need to investigate after work.

This broke my Setup. Not exactly sure why yet. Gives me 503 now, but other then in the nginx log I can not see any errors. Need to investigate after work.

Hi @RealKelsar, please submit a new issue and include your config and logs. Thanks.


Custom props

What this PR does
This PR brings int the custom props demo.
Requirements
Narrator handles SVG pretty poorly overall. I will add aria-hidden to it all when I get home. But want to get the PR in for @molant and @melanierichards to review.

[X] My PR follows all applicable accessibility requirements (See .github/ACCESSIBILITY_REQS.md).

@melanierichards can you take a look at this demo?

We will need an image for the tile of this demo. Have you talked with @ststimac about it?

@molant Nope haven't spoken with @ststimac about the tile. Stephanie do you mind creating one?

@gregwhitworth yes I can make a tile for this.

Here's a tile for EdgePortal.

@melanierichards this should be good for review from you

Can confirm the changed code text color should be black. I think I mentioned that last week that the white on light brown doesn't meet accessibility requirements.

@melanierichards @dstorey Regarding this statement:

For a11y reasons I think we need to have some kind of control that will allow the person to pause all the animations in the SVG.

I don't think the dogs tail moves far enough or is large enough to cause reactions to vestibular disorder, I assume that's what you're referring to when saying "for a11y reason." That said, we could potentially mix up the animation of the tail a bit so that it isn't as constant. Like, wag->wag, delay, wag->wag->wag etc. If we feel we must have a control to turn off animations, does this cover all animations including transitions? Finally, if we go that route where would you like it placed?

@molant I haven't had a chance to test this on an internal build since I got the feedback after leaving work. Just in the off chance it's signed off on before tomorrow (21) please don't merge this until I get a chance to ensure it works well.

@gregwhitworth regarding the question about wagging animations: I think the best route is probably a control to pause all animations (including the clouds and such). I'm thinking a text only, minimal <button> below the bottom right corner of the demo art that says "Pause animations". If making this update would cause us not to get the demo out in a timely fashion I'm fine with us merging this PR now and submitting another PR with that update, just let me know :]

@melanierichards @molant all feedback has been addressed. The code for the animation button could easily be pulled out and made into a component since this is something that we're wanting on all demos according to the guidelines listed above.

@melanierichards alrighty - we should be good to go

@molant we can haz merge if you're satisfied (cc @gregwhitworth)

As soon as @gregwhitworth is OK I'll merge. I think he wanted to wait for something.

@molant I checked it out this morning - we're good to go!


fix compare slider component

Trello - The slider component was missing the aria-label attribute and the text version for the selected value. I also added the getValueLabel property which gives values its corresponding name.
Tested with VoiceOver, works well
Learn more

https://material-ui.com/components/slider/#accessibility
https://material-ui.com/api/slider/

 Accessibility: Add aria-labels to slider values


Implement core

[x] Versionage
[x] Serialage
[x] versify
[x] deversify
[x] B64ChrByIdx
[x] intToB64
[x] readInt

core.ts

Looks like these are done.


Use workspaces for name prefixes

Nice to have a clear mapping of terraform workspace name to resource names (or at least resource group name) in the azure portal.
Should use this setup in other subfolders:
https://github.com/Denolle-Lab/azure/blob/f1f43b5d993cc9d0f412ffd986800244ffd33e4f/azure_file_share_data/main.tf#L33-L34

Same for other resources that live within a resource group. Even if things are in separate resources groups they can't have the same name
https://github.com/Denolle-Lab/azure/blob/a938a925cdacb637bb4630d443ba432c8286ecc8/aci_plus_volume/main.tf#L37

switched all the configurations to use "workspace" instead of "prefix" in https://github.com/Denolle-Lab/azure/commit/5d408be63cabd168fd9a586160d458deb385daf3


C# class wasn't updated

The C# class of 1.3 doesn't work anymore!!!

It seems toot scream at me if I comment out lines 50-53 in DialogicSharp:
    // public static Node Start(String timeline, bool resetSaves = true, bool debugMode = false, bool useCanvasInstead = true)
    // {
    //   return Start<Node>(timeline, DEFAULT_DIALOG_RESOURCE, resetSaves, debugMode, useCanvasInstead);
    // }

I have yet to test whether this actually works or not.

I can see about adding a PR when I have some time (I'm not sure what my schedule for this week is yet, and I might have more to add - Someone else can add this if they want), but a fix is to change would be:
  public static T Start<T>(String timeline, String defaultTimeline = "", bool debugMode = false, bool useCanvasInstead = true)
  {
    return (T)_dialogic.Call("start", timeline, defaultTimeline, DEFAULT_DIALOG_RESOURCE, debugMode, useCanvasInstead);
  }


Feature/add arm to build pipeline

Description

Please include a summary of the changes and the related issue.
Fixes # (issue)

Type of change

[ ] New features (non-breaking change).
[ ] Bug fix (non-breaking change).
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected).

Checklist

[ ] I have performed a self-review of my code.
[ ] I have added thorough tests if it is a core feature.
[ ] There is a reference to the original bug report and related work.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] The feature is well documented.

My bad, did some bad stuff on my fork lol


Explore: Voting: Referendums Missing

Is your feature request related to a problem? Please describe.
We're currently not displaying Referendums as an option for users to be able to vote on.
Fix to include Referendums.

This is ugly.

This is ugly.

fixed.

@n13 I thought that this type of proposal would have a separate section from (as in v1).
If they are included together with the proposals in the same section, would it be to request both lists and then merge them into one?

Hmm... I think it's a little messy to merge them into 1 list, since these objects are actually different objects.
The referendum data is different from proposals data.


Color of a styled(Paragraph) is different in dev and prod build

Current Behavior
The issue is that the color of a styled Paragraph variant is different when running the dev server (with extraction disabled) and prod build (extraction enabled).
Using on web with next-expo-solito starter.
Expected Behavior
The text in the first box in the demo below should be white in step #5 instead of purple.
Tamagui Version
1.39.6

Reproduction
Minimal repro: https://github.com/la55u/tama-color-bug
Steps:

clone the repo
run yarn
run yarn web and confirm the text in the first box is white (OK)
kill the terminal
run yarn web:prod && yarn web:prod:serve and the first text becomes purple (NOT OK)

System Info
System:
    OS: Linux 6.3 Fedora Linux 38 (Workstation Edition)
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1260P
    Memory: 19.14 GB / 31.04 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 3.5.0 - ~/.nvm/versions/node/v18.12.1/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
    pnpm: 7.26.3 - ~/.local/share/pnpm/pnpm
  Browsers:
    Chrome: 114.0.5735.198
  npmPackages:
    @babel/runtime: ^7.21.0 => 7.22.5
    @commitlint/cli: ^17.6.1 => 17.6.6
    @commitlint/config-conventional: ^17.6.1 => 17.6.6
    @types/react: ^18.0.38 => 18.2.14
    check-dependency-version-consistency: ^3.0.3 => 3.3.0
    eslint: ^8.36.0 => 8.44.0
    husky: ^8.0.3 => 8.0.3
    node-gyp: ^9.3.1 => 9.4.0
    prettier: ^2.8.8 => 2.8.8
    turbo: 1.10.7 => 1.10.7
    typescript: 5.1.6 => 5.1.6

set TAMAGUI_TARGET for dev as well

@TheEhsanSarshar it's set in apps/next/.env which should be picked up in both dev and prod builds

can you check on latest? multiple fixes have landed

It was fixed some versions ago just forgot to close it. Verified it's working with 1.45.2 too, thank you.


Streamline "Getting Started" documentation

Remove the "Running an example.." section from the Installing VE page and clarify the Using the Virtual Ecosystem page.
Other typos / corrections

Hi @sallymatson I was about to tackle the same issue and glad to have checked here. I agree that re: point 1 because it duplicates with the Example page.
Before I mess it up, are you working on this already in a branch / fork?

Hi @hrlai yes, I have started working on it! I hope to have a PR in the next few days for review. Would you like me to add you as a reviewer, so you can see what I was thinking and offer further input?

Sure @sallymatson :) Happy to review. I am approaching this as someone who has near-zero experience with running Python scripts (and have no streamlined way to run bash / shell simultaneously) so will add some thoughts on how to make the tutorial accessible.


D2.2 Update Documentation

Update documentation to reflect changes in release 1.7.x:

correct install instructions in System Administrator Guide
description of changed functionality in User Manual
updated Data Dictionary

Currently converting original word doc versions of the documentation to the reStructuredText format (.rst), for use on readthedocs.
test https://test-wct.readthedocs.io/en/latest/


Manage a single window resize event instead of one per component

I am looking into improving the performance of react-waypoint. We can be
a little more mindful of how many event listeners we end up creating by
only managing a single event listener. Using Chrome's timeline tool, I
have verified that this type of optimization is significant when there
are a lot of event listeners on the page.
Since we always set up a window resize event, this seemed like a good
place to start for this optimization. I chose a Set, since that seemed
like the easy and nice way to go, but it will require that older
browsers have a polyfill.
If we like this approach, I plan to do something similar for the scroll
event listeners. These are a little more complicated since they could be
attached to any scrollable container, instead of just the window. One
option would be to use a Map to manage a Set of event listeners for each
scrollable container. It might also be worth exploring using a single
top-level event listener instead of one per scrollable container, which
should be accomplishable via the Map/Set approach.

This is a good start! Was your plan for polyfilling to bundle it with react-waypoint? It wouldn't be too hard to use splice and indexOf too, which would have more broad support. Also, how do you feel about making addResizeEventListener return a "subscription" of sorts, that you can use to remove it?
componentDidMount() {
  this._resizeSubscription = addResizeEventListener(this._someFunc);
}

componentWillUnmount() {
  this._resizeSubscription.remove();
}

My plan was to not polyfill it, but to list it in the readme as a dependency. I want to avoid the indexOf route because that requires a full scan of the array every time. Maybe I'll use an object with your subscription suggestion instead. That should be both fast and well supported.

@trotzig I've updated this PR with an object-based approach. PTAL

Cool, thanks for addressing! Merge at will.

Merged. This afternoon, I plan to expand this approach to the scroll event listeners.

👌nice


qutebrowser qute-keepassxc doesn't work when launch from .desktop

Describe the bug
When using an userscript called qute-keepassxc gpg throws an error code 2 when trying to get passwords when run from kde application mene with .desktop, but when run from the shell in terminal gpg work's with no issues.
Expected behavior
gpg doesn't throw an error and the script works with no issues
Additional context
home.nix
  home.packages = [
    ...
    pkgs.qutebrowser
    ...
  ];

  ...

  programs.gpg = {
     enable = true;
     homedir = "${config.xdg.dataHome}/gnupg";
   };

   ...

  services.gpg-agent = {
     enable = true;
     pinentryFlavor = "qt";
   };

Qutebrowser message error
19:37:13 ERROR message message:error:63 Command '['gpg', '--decrypt', '/home/crony/.local/share/qutebrowser/keepassxc.key.gpg']' returned non-zero exit status 2.

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.77, NixOS, 24.05 (Uakari), 24.05.20240207.f8e2ebd`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

Fixed the issues, problem was sddm didn't load my custom gpg path variable.
Fixed by adding xsession.enable = true; to home.nix


Remove set_cluster_name.

We may need to add this back within cluster.save(). If we do, we should add a breaking test case. It seems to work fine for the cases I'm looking at.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#703  👈
#702
main

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

Join @rohinb2 and the rest of your teammates on  Graphite


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-24-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2246

Questions ?
Please refer to the Backport tool documentation


Visit OperatorService methods in interceptor

What changed?

Visit OperatorService methods in interceptor
Reenable generatorcheck Makefile target

Why?
There are payloads in the Nexus EndpointSpec description that need to be visited for completeness.

We want to allow encryption in Cloud too. There's a planned breaking change to switch the description field to a payload once we figure out how cloud / and OSS protos are going to be combined.


Use viewport size for css dimensions

Make use of vw / vh / vmin / vmax units for better rendering on any device and screen size

Themes and core css updated, but some widgets are not yet responsive.


i'am unable even to run the flutter test app

hello everyone
i'm facing this error and still can't solve this issue

Hi @AzilMahdi
This isn't related to Futter itself, looks like you're missing the required SDK.
Please follow this possible solution
Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Failed to load class PlantCasingCondition when registrying the chemical plant recipes

the chemical plant casing condition need to load this class, but it failed in kubejs

now you can


Unable to deploy project to Vercel (mono repo setup on Vercel with yarn workspaces)

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[x] Read the docs.
[x] Use Vite >=2.0. (1.x is no longer supported)
[x] If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug
I am currently enable to run vite build on Vercel infrastructure when in a monorepo setup (yarn workspaces
Reproduction

Clone this repo: https://github.com/sync/mono
Use your Vercel account and import project following those instructions (https://vercel.com/blog/monorepos), the vite project is located under docs. So select docs
yarn build will fail to build vite project on Vercel

I can run build the project on my local computer MacOSX or Linux (GitHub Actions) without issue.
System Info

vite version: (latest)
Operating System: Linux
Node version: 12.x
Package manager (npm/yarn/pnpm) and version: yarn
Vercel setup:

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

error:
Error: Failed to resolve entry for package "@dblechoc/mono-components". The package may have incorrect main/module/exports specified in its package.json.

14:04:33.699 | $ vite build --debug
-- | --
14:04:33.939 | 2021-01-24T03:04:33.938Z vite:config no config file found.
14:04:33.946 | 2021-01-24T03:04:33.946Z vite:config using resolved config: {
14:04:33.946 | root: '/vercel/workpath0/docs',
14:04:33.946 | base: '/',
14:04:33.947 | mode: 'production',
14:04:33.947 | configFile: undefined,
14:04:33.947 | logLevel: undefined,
14:04:33.947 | clearScreen: undefined,
14:04:33.947 | build: {
14:04:33.947 | target: [ 'es2019', 'edge16', 'firefox60', 'chrome61', 'safari11' ],
14:04:33.947 | polyfillDynamicImport: true,
14:04:33.947 | outDir: 'dist',
14:04:33.947 | assetsDir: 'assets',
14:04:33.947 | assetsInlineLimit: 4096,
14:04:33.947 | cssCodeSplit: true,
14:04:33.948 | sourcemap: false,
14:04:33.948 | rollupOptions: {},
14:04:33.948 | commonjsOptions: { include: [Array], extensions: [Array] },
14:04:33.948 | minify: 'terser',
14:04:33.948 | terserOptions: {},
14:04:33.948 | cleanCssOptions: {},
14:04:33.948 | write: true,
14:04:33.948 | emptyOutDir: null,
14:04:33.948 | manifest: false,
14:04:33.948 | lib: false,
14:04:33.949 | ssr: false,
14:04:33.949 | ssrManifest: false
14:04:33.949 | },
14:04:33.949 | inlineConfig: {
14:04:33.949 | root: undefined,
14:04:33.949 | base: undefined,
14:04:33.949 | mode: undefined,
14:04:33.949 | configFile: undefined,
14:04:33.949 | logLevel: undefined,
14:04:33.949 | clearScreen: undefined,
14:04:33.950 | build: {}
14:04:33.950 | },
14:04:33.950 | command: 'build',
14:04:33.950 | isProduction: true,
14:04:33.950 | optimizeCacheDir: '/vercel/workpath0/docs/node_modules/.vite',
14:04:33.950 | alias: [
14:04:33.950 | {
14:04:33.950 | find: /^\/@vite\//,
14:04:33.950 | replacement: '/vercel/workpath0/node_modules/vite/dist/client/'
14:04:33.950 | }
14:04:33.950 | ],
14:04:33.950 | plugins: [
14:04:33.951 | 'alias',
14:04:33.951 | 'vite:dynamic-import-polyfill',
14:04:33.951 | 'vite:resolve',
14:04:33.951 | 'vite:html',
14:04:33.951 | 'vite:css',
14:04:33.951 | 'vite:esbuild',
14:04:33.951 | 'vite:json',
14:04:33.951 | 'vite:wasm',
14:04:33.951 | 'vite:worker',
14:04:33.951 | 'vite:asset',
14:04:33.951 | 'vite:css-post',
14:04:33.951 | 'vite:build-html',
14:04:33.951 | 'commonjs',
14:04:33.951 | 'vite:data-uri',
14:04:33.952 | 'vite:define',
14:04:33.952 | 'rollup-plugin-dynamic-import-variables',
14:04:33.952 | 'vite:import-analysis',
14:04:33.952 | 'vite:esbuild-transpile',
14:04:33.952 | 'vite:terser',
14:04:33.952 | 'vite:size'
14:04:33.952 | ],
14:04:33.952 | server: { hmr: { path: undefined } },
14:04:33.952 | env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
14:04:33.952 | assetsInclude: [Function: assetsInclude],
14:04:33.952 | logger: {
14:04:33.952 | hasWarned: false,
14:04:33.952 | info: [Function: info],
14:04:33.953 | warn: [Function: warn],
14:04:33.953 | error: [Function: error],
14:04:33.953 | clearScreen: [Function: clearScreen]
14:04:33.953 | }
14:04:33.953 | }

building for production...
--
14:04:34.148 | [vite:resolve] Failed to resolve entry for package "@dblechoc/mono-components". The package may have incorrect main/module/exports specified in its package.json.
14:04:34.153 | error during build:
14:04:34.154 | Error: Failed to resolve entry for package "@dblechoc/mono-components". The package may have incorrect main/module/exports specified in its package.json.
14:04:34.154 | at resolvePackageEntry (/vercel/workpath0/node_modules/vite/dist/node/chunks/dep-3174cbb5.js:39897:15)
14:04:34.154 | at tryNodeResolve (/vercel/workpath0/node_modules/vite/dist/node/chunks/dep-3174cbb5.js:39753:11)
14:04:34.154 | at Object.resolveId (/vercel/workpath0/node_modules/vite/dist/node/chunks/dep-3174cbb5.js:39640:28)
14:04:34.154 | at /vercel/workpath0/node_modules/rollup/dist/shared/rollup.js:18953:25
14:04:34.154 | at processTicksAndRejections (internal/process/task_queues.js:97:5)
14:04:34.171 | error Command failed with exit code 1.
14:04:34.171 | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
14:04:34.182 | Error: Command "yarn build --debug" exited with 1
14:04:38.698 | Done with "package.json"

I don't think this is Vite issue. When you build a Vite project that links to other packages in the same monorepo, Vite expects those packages to be properly linked. The special Vercel monorepo setup you linked to seems to be designed for monorepos that contains packages that don't actually depend on one another. You should simply build using the whole project instead of using that setup.

I don't think this is Vite issue. When you build a Vite project that links to other packages in the same monorepo, Vite expects those packages to be properly linked. The special Vercel monorepo setup you linked to seems to be designed for monorepos that contains packages that don't actually depend on one another. You should simply build using the whole project instead of using that setup.

Makes sense thanks for having a look

Makes sense thanks for having a look

@yyx990803
hi, I also encountered this problem in development mode.
I want to ignore this feature in development mode, what should I do?

@yyx990803
hi, I also encountered this problem in development mode.
I want to ignore this feature in development mode, what should I do?


Bump terser from 4.8.0 to 4.8.1

Bumps terser from 4.8.0 to 4.8.1.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: terser dependency-type: indirect ...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

Already merged this from dependabot


[ON HOLD] Add starboard

Description of Changes
Add a starboard to contrib_extensions for an example on how to handle user data which needs to persist for some amount of time but not indefinitely
Related Discussions/Issues
This is on hold for now, even what's here isn't necessarily going to be used when continuing.

Closing this. May reopen or create a parallel repository for things which may not be worth inclusion in the core


New reindex-all script feature with dedicated logging

This PUT /reindex-all was added at the early phase of search-api. As we have a lot more data now, it no longer serves the desired purpose using a REST API call to handle the reindex that may take a few hours to complete. The lack of dedicated logging is another major reason we should deprecate it.
Add new reindex-all scripting feature and generate dedicated logging to a separate file. The scripting feature should also handle the following use cases:

Full Reindex: Delete all the old entities and portal indices (which also deletes all the documents in each index) first, then recreate them and index documents to the new indices. This ensures a clean "reset", which is what we have now with running the hubmap_translator.py as a script in command line.
Live Reindex All: Without deleting the indices, just reindex the documents one by one (concurrently). This is currently achieved by the PUT /reindex-all call, we'll convert it to a scripting feature to generate dedicated logging similar to the above.

For both cases, we'll want to have a statistic feature that tracks the failed entity uuids.
Eventually we'll be able to deprecate the PUT /reindex-all endpoint.

8/1/2024, @kburke proposed this blue/green deployment procedure which would accommodate all the requirements with dedicated logging and it'll also minimize the downtime and incomplete data state that the current "Full Reindex" poses.

8/15/2024, branched off @kburke's branch with mounting scripts to container and tested on DEV with create command.
[2024-08-15 22:06:16] INFO in hubmap_translator:286: ############# Finished executing translate_full() at 22:06:16. #############
[2024-08-15 22:06:16] INFO in hubmap_translator:290: ############# Executing translate_full() took 07:24:56. #############
[2024-08-15 22:06:16] INFO in fresh_indices:231: ############# Full index via script complete at 22:06:16 #############
[2024-08-15 22:06:16] INFO in fresh_indices:234: ############# Full index via script took 07:24:57. #############

I created a new Sample HBM985.PKTG.328 on DEV to be used to verify the "catch up" output, it generated an error though:
Command to execute: 'catch-up'
Output will be in ./exec_info

[2024-08-16 12:03:20] INFO in fresh_indices:55: logger initialized with effective logging level 20.
[2024-08-16 12:03:20] INFO in fresh_indices:59: The fill strategy to be executed is create_fill.
[2024-08-16 12:03:20] INFO in fresh_indices:363: ESWriter initialized with URL https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com
[2024-08-16 12:03:20] INFO in fresh_indices:365: ESManager initialized with URL https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /fill20240815_fresh_index_hm_dev_public_entities HTTP/1.1" 200 0
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /hm_dev_public_entities HTTP/1.1" 200 0
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /fill20240815_fresh_index_hm_dev_consortium_entities HTTP/1.1" 200 0
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /hm_dev_consortium_entities HTTP/1.1" 200 0
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /fill20240815_fresh_index_hm_dev_public_portal HTTP/1.1" 200 0
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /hm_dev_public_portal HTTP/1.1" 200 0
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /fill20240815_fresh_index_hm_dev_consortium_portal HTTP/1.1" 200 0
[2024-08-16 12:03:20] DEBUG in connectionpool:1021: Starting new HTTPS connection (1): search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443
[2024-08-16 12:03:20] DEBUG in connectionpool:474: https://search-hubmap-dev-test-hfnqv4ylo5ywvc42vwnyptbup4.us-east-1.es.amazonaws.com:443 "HEAD /hm_dev_consortium_portal HTTP/1.1" 200 0
Not ready to catch-up activity which took place in the Production indices during or after creation of the new indices
But if we will be once we:
*** reindex these uuids for documents which failed while creating the new indices:
Traceback (most recent call last):
  File "/usr/src/app/scripts/fresh_indices/fresh_indices.py", line 392, in <module>
    catch_up_new_index()
  File "/usr/src/app/scripts/fresh_indices/fresh_indices.py", line 318, in catch_up_new_index
    print(f"****** {op_data['translator_failed_entity_ids']}", file=sys.stderr)
KeyError: 'translator_failed_entity_ids'

The actual output file exec_info/op_data_20240815.json
{
 "index": {
   "hm_dev_public_entities": {
     "destination": "fill20240815_fresh_index_hm_dev_public_entities",
     "max": {
       "last_modified_timestamp":<PHONE_NUMBER>224.0,
       "created_timestamp":<PHONE_NUMBER>616.0
     },
     "initial_doc_count": 4619
   },
   "hm_dev_consortium_entities": {
     "destination": "fill20240815_fresh_index_hm_dev_consortium_entities",
     "max": {
       "last_modified_timestamp":<PHONE_NUMBER>568.0,
       "created_timestamp":<PHONE_NUMBER>568.0
     },
     "initial_doc_count": 53505
   },
   "hm_dev_public_portal": {
     "destination": "fill20240815_fresh_index_hm_dev_public_portal",
     "max": {
       "last_modified_timestamp":<PHONE_NUMBER>224.0,
       "created_timestamp":<PHONE_NUMBER>616.0
     },
     "initial_doc_count": 4618
   },
   "hm_dev_consortium_portal": {
     "destination": "fill20240815_fresh_index_hm_dev_consortium_portal",
     "max": {
       "last_modified_timestamp":<PHONE_NUMBER>568.0,
       "created_timestamp":<PHONE_NUMBER>568.0
     },
     "initial_doc_count": 53285
   }
 },
 "file_time_prefix": "20240815"
}


Issue while building the sdk

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

Building the SDK Always giving me this error
/build/Integration/tmp_AlexaClientSDKConfig.json
awk: newline in string  {
    "gstreamerMed... at source line 1
awk: newline in string  {
    "gstreamerMed... at source line 1
awk: newline in string  {
    "gstreamerMed... at source line 1

What is the expected behavior?

build the sdk
What behavior are you observing?

Provide the steps to reproduce the issue, if applicable:

followed the steps but getting this error after i run
bash setup.sh config.json -a androidConfig.txt
/build/Integration/tmp_AlexaClientSDKConfig.json
awk: newline in string  {
"gstreamerMed... at source line 1
awk: newline in string  {
"gstreamerMed... at source line 1
awk: newline in string  {
"gstreamerMed... at source line 1
Tell us about your environment:

What version of the AVS Device SDK are you using?
1.23.0
OS -> MAC
Building for Android
Tell us what hardware you're using:
Laptop MAC
Tell us about your OS (Type & version):
MacOS

Hi @JordanTaylo,
Can you please confirm if androidConfig.txt contains valid JSON? Ie, there are no missing or invalid characters?

Hi @kjkh
that is my androidConfig.txt
PLATFORM="android"
API_LEVEL="23"
TARGET_SYSTEM="arm"
DEVICE_INSTALL_PATH="/new/data"
BUILD_TYPE="debug"

Hi @JordanTaylo, could you try commenting out or deleting this line here in setup.sh file in your workspace?

Hi, I have the same error and we did comment that line. Once we did, the process continued but since that line copy the content of the temp config file to the output config file, the output file on my device was empty.
I logged what $GSTREAMER_CONFIG was and copied it manually into the temp file and I copied it on my device but this didn't help at all since once the StartSample ran, all we had was a bunch of garbage character that made no sense.

I have the same error.If i comment that line.Build success, but the file "AlexaClientSDKConfig.json" is empty.
How to solve this problem?

Hello @JordanTaylo, @HelloYuGi, @krustache,
Are you still experiencing this issue? Are you able to reproduce this on the latest version of the SDK?

Closing due to inactivity. If there are additional requests for support, please create a new ticket linking to this one.


Investigate inability to read non-public-read objects from the CN index

It looks like objects without public-read permission aren't being returned by the CN index when requests are made with a token that (1) is valid and (2) should have read permission. It's not clear how long this has been the case.
The package below is an example. We can see it fine on arctica but not on the CN:

Metadata PID: urn:uuid:ebcb68d6-45c1-4440-b214-bb5b8eca1d6c
Resource map PID: resource_map_urn:uuid:5aff3115-ff3d-446a-90ed-94057bbb9348

Note: The metadata does not have public read permission but the resource map does. This is actually what led us to discover things weren't working.
Since discovering, we haven't seen a case here we are able to see a non-public-read object. We know this used to work. We've confirmed the Solr document is in the index by querying Solr directly so it's something to do with the interaction of the API and Solr.

When I query the private object through DataONE api with the CN certificate, it works. This morning we used tokens and it didn't work.
I am thinking that after we switched to tokens, we haven't touched the cn query part yet.


DOM will eventually need CSS parsing

to implement the CSSOM, e.g. CSSStyle* IDL types

This issue has been moved to dart-lang/html#28.


Allow fulfill relay fix

The Problem

allowFulfillRelay: false was still broken.
The Solution

Checklist

[ ] Test manually on test-ui using remote chains.
[ ] Run load tests.
[ ] Update documentation if needed.
[ ] Update CHANGELOG.md.

No questions

Can you approve if it looks okay :)?


support IndexedSlices in add_n

Fixes #15943

ound a whitelisted error:
  tensorflow/contrib/eager/python/evaluator.py:209: [E0202(method-hidden), Evaluator.call] An attribute defined in evaluator line 61 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/evaluator.py:361: [E0202(method-hidden), SparseSoftmaxEvaluator.call] An attribute defined in evaluator line 61 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:179: [E0202(method-hidden), Metric.build] An attribute defined in metrics_impl line 121 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:192: [E0202(method-hidden), Metric.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:301: [E0202(method-hidden), Mean.build] An attribute defined in metrics_impl line 121 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:312: [E0202(method-hidden), Mean.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:356: [E0202(method-hidden), Accuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:401: [E0202(method-hidden), CategoricalAccuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:454: [E0202(method-hidden), BinaryAccuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
  tensorflow/contrib/eager/python/metrics_impl.py:498: [E0202(method-hidden), SparseAccuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
  tensorflow/python/kernel_tests/constant_op_eager_test.py:250: [E0303(invalid-length-returned), ConstantTest.testInvalidLength.BadList.__len__] __len__ does not return non-negative integer
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3125: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_invalid_type] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3132: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_one_feature_column] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3142: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_two_feature_columns] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3143: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_two_feature_columns] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3155: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_different_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3156: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_different_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3163: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_equal_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3164: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_equal_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3177: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_multiple_features_dict] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
  tensorflow/python/feature_column/feature_column_test.py:3178: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_multiple_features_dict] Abstract class '_TestFeatureColumn' with abstract methods instantiated
FAIL: Found 2 non-whitelited pylint errors:
tensorflow/python/ops/math_ops.py:2120: [C0301(line-too-long), ] Line too long (81/80)
tensorflow/python/ops/math_ops.py:2124: [C0301(line-too-long), ] Line too long (81/80)

The relevant lines:
FAIL: Found 2 non-whitelited pylint errors:
tensorflow/python/ops/math_ops.py:2120: [C0301(line-too-long), ] Line
too long (81/80)
tensorflow/python/ops/math_ops.py:2124: [C0301(line-too-long), ] Line
too long (81/80)
On Thu, Aug 9, 2018, 6:31 PM drpngx<EMAIL_ADDRESS>wrote:

ound a whitelisted error:
tensorflow/contrib/eager/python/evaluator.py:209: [E0202(method-hidden), Evaluator.call] An attribute defined in evaluator line 61 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/evaluator.py:361: [E0202(method-hidden), SparseSoftmaxEvaluator.call] An attribute defined in evaluator line 61 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:179: [E0202(method-hidden), Metric.build] An attribute defined in metrics_impl line 121 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:192: [E0202(method-hidden), Metric.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:301: [E0202(method-hidden), Mean.build] An attribute defined in metrics_impl line 121 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:312: [E0202(method-hidden), Mean.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:356: [E0202(method-hidden), Accuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:401: [E0202(method-hidden), CategoricalAccuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:454: [E0202(method-hidden), BinaryAccuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
tensorflow/contrib/eager/python/metrics_impl.py:498: [E0202(method-hidden), SparseAccuracy.call] An attribute defined in metrics_impl line 131 hides this method
Found a whitelisted error:
tensorflow/python/kernel_tests/constant_op_eager_test.py:250: [E0303(invalid-length-returned), ConstantTest.testInvalidLength.BadList.len] len does not return non-negative integer
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3125: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_invalid_type] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3132: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_one_feature_column] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3142: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_two_feature_columns] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3143: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_two_feature_columns] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3155: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_different_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3156: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_different_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3163: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_equal_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3164: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_equal_keys_equal_parse_spec] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3177: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_multiple_features_dict] Abstract class '_TestFeatureColumn' with abstract methods instantiated
Found a whitelisted error:
tensorflow/python/feature_column/feature_column_test.py:3178: [E0110(abstract-class-instantiated), MakeParseExampleSpecTest.test_multiple_features_dict] Abstract class '_TestFeatureColumn' with abstract methods instantiated
FAIL: Found 2 non-whitelited pylint errors:
tensorflow/python/ops/math_ops.py:2120: [C0301(line-too-long), ] Line too long (81/80)
tensorflow/python/ops/math_ops.py:2124: [C0301(line-too-long), ] Line too long (81/80)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/21494#issuecomment-411947880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim8Ir36TqUhaugNNH5Er8fdenBXIHks5uPOJ7gaJpZM4V0uZh
.

Hi @drpngx, just curious what release this will make it into? I saw version 1.10.1 was released 5 days ago but this commit isn't in there.

1.10.1 was a patch release and by definition will not necessarily contain all latest commits. @drpngx is correct it will be in 1.11 which will be cut tomorrow at 5pm.


Waited 7 days, bot still not accepting offers

Waited 7 days because of the steam guard but still bot doesn't accept the trade offers, same as before https://github.com/ztizzlegaming/CSGOWinBig-SteamBot/issues/37

Add me on steam

@TheAnthonyNL helped me :)
The password in password.txt didn't match.


invalid feature names

I'm not sure how many of these there will be, but I'll log them here. I guess crates.io is being a bit more picky.
   Uploading azure_svc_confidentialledger v0.1.0 (C:\Users\cataggar\io\azure-sdk-for-rust\services\svc\confidentialledger)
error: failed to publish to registry at https://crates.io

Caused by:
  the remote server responded with an error: invalid upload request: invalid value: string "package-0.1-preview-ledger", expected a valid feature name at line 1 column 1378

   Uploading azure_svc_graphrbac v0.1.0 (C:\Users\cataggar\io\azure-sdk-for-rust\services\svc\graphrbac)
error: failed to publish to registry at https://crates.io

Caused by:
  the remote server responded with an error: invalid upload request: invalid value: string "1.6", expected a valid feature name containing only letters, numbers, '-', '+', or '_' at line 1 column 1334

   Uploading azure_svc_batch v0.1.0 (C:\Users\cataggar\io\azure-sdk-for-rust\services\svc\batch)
error: failed to publish to registry at https://crates.io

Caused by:
  the remote server responded with an error: invalid upload request: invalid value: string "package-2022-01.15.0", expected a valid feature name at line 1 column 1359

   Uploading azure_svc_servicefabric v0.1.0 (C:\Users\cataggar\io\azure-sdk-for-rust\services\svc\servicefabric)
error: failed to publish to registry at https://crates.io

Caused by:
  the remote server responded with an error: invalid upload request: invalid value: string "6.5", expected a valid feature name containing only letters, numbers, '-', '+', or '_' at line 1 column 1338

Note: crates.io imposes additional constraints on feature name syntax that they must only be ASCII alphanumeric characters or _, -, or +.
https://doc.rust-lang.org/cargo/reference/features.html

The . are invalid.


Manufacturer of Swing Shutter | Build Enterprises

Build Enterprises India’s biggest Rolling Shutters, motorized swing shutter, interior designing services and office furniture manufacturer/exporter in Delhi India.
http://buildenterprisesindia.com/listing.html?category_id=88

Thanks @gariantoye! Your service looks good.


E/FMAuthPlugin(21695): The redirect URI in the configuration file doesn't match with the one generated with package name and signature hash. Please verify the uri in the config file and your app registration in Azure portal.

I made changes from example it's fine but when I try to recreate new flutter app it doesn't work
How do i debug or fix this

You should rester your app hear.
And submit the package name and signature hash of your app.
https://docs.microsoft.com/en-us/onedrive/developer/rest-api/getting-started/app-registration?view=odsp-graph-online


Refactor trovilo job design

Currently trovilo supports multiple jobs (e.g. to gather information for Prometheus and for Grafana) since trovilo is designed to run inside Kubernetes environments I don't actaully see a benefit in supporting multiple jobs (and adding the complexity). From my perspective trovilo should always be used as a sidecar to the according service like in the Prometheus example: https://github.com/inovex/trovilo/blob/master/examples/k8s/deployment.yaml#L60
Are there any reasons why we should keep to support multiple jobs?

I see some use cases, but before writing some of them down I would be interested in the motivation (next to making the code more simple) behind your question. :)

From my perspective at-least the namespace selection should be moved inside the job section since I wouldn't assume that all configmaps are in the same namespace if I actually want to use multiple job (and currently I don't see any use case that couldn't be solved using multiple sidecars e.g. for Prometheus/Grafana etc.). Also the additional sidecars have a really low compute footprint since they only do stuff if a specific configmap was changed/added/deleted. Also I would trade code simplicity (and robustness) over a functionality that can be solved by starting multiple instances/sidecars of trovilo.

Regarding namespace: 👍  Can you show an updated version of the config example (see README) please so we all have the same picture about the resulting configuration file/DSL?

I would go with something like this (one job per instance):
name: alert-rules
selector:
  type: prometheus-alerts
verify:
  - name: verify alert rule validity
    cmd: ["promtool", "check", "rules", "%s"]
target-dir: /etc/prometheus-alerts/
flatten: true
post-deploy:
  - name: reload prometheus
    cmd: ["curl", "-s", "-X", "POST", "http://localhost:9090/-/reload"]

We already have cmd line flags but I'd like to keep other (global, non-redundant) options possible. Just thinking about stuff with newlines or more complex options..
What do you think?
job:
  selector:
    type: prometheus-alerts
  verify:
    - name: verify alert rule validity
      cmd: ["promtool", "check", "rules", "%s"]
  target-dir: /etc/prometheus-alerts/
  flatten: true
  post-deploy:
    - name: reload prometheus
      cmd: ["curl", "-s", "-X", "POST", "http://localhost:9090/-/reload"]


What is the purpose of the separate global and per-channel backlogs?

The architecture of message_bus is unclear on some points, and this is one of them.

Per channel backlog is critical so we can efficiently grab backlogs for a channel when clients are catching up.
Global backlog is critical for firehose consumers that re-distribute events


API Restructure

Adds a bit more structure to wallets and wallet addresses with the goal of making usage between implementations more consistent.

Wallets now have a unique ID, friendly name, and description for easier updating.
Addresses (optionally) support storing their spend policy

Splits the SC and SF utxo endpoints
Adds pagination to the SC and SF utxo endpoints
Returns 404 errors on all the wallet endpoints if the wallet does not exist

Good stuff. What's the motivation for names->IDs, especially int64? Is it a sqlite thing?

Good stuff. What's the motivation for names->IDs, especially int64? Is it a sqlite thing?

name -> ID makes it possible to later change the name and keep the other wallet data consistent. The UI currently generates a UUID as the name and adds an additional friendlyName to metadata. This enforces that flow for all consumers.
I don’t really have a preference on the type. Int64 is easy and supported by every db engine I’m aware of. We could also use UUID or frand.Entry128().String. As long as it’s unique and set by walletd

Ok. Let's at least define a distinct WalletID type for it.


FIX: typo: 'defalut' instead of 'default'

Thank you for your PR

You are wlcome :)
Thanks for the plugin


what is ndvi_stack ?

In the function f_img_collyou use a ndvi_stack variable that is never referenced in your code.
I assume that it was the ndvi_1y_coll but I'm not convinced, please take a look and change the code according to your development

You right! it was the ndvi_1y_coll. I have revised the variable name accordingly.


renamed stroke apis family.

@Issue: https://github.com/thorvg/thorvg/issues/1372

@JSUYA @SergeyLebedkin @RuiwenTang @mgrudzinska Hellow, please let me know if you have any opinion on this. Otherwise I will push this soon.


DotNetCoreCLI restore command does not support Azure artifacts views

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Feature
Enter Task Name: DotNetCoreCLIV2
Issue Description
vstsFeed format is projectID/feedID
If you want to select a view in Azure Artifacts you'd need projectID/feedID@viewID
but this results in invalid XML in Nuget.config, eventually resulting in dotnet restore returning
The '@' character, hexadecimal value 0x40, cannot be included in a name
reason is that the task puts anything after the "/" into Feed.Name, because it expects only a GUID.
As far as I can see there is no possibility (currently) to use feedsToUse: 'select' and select a view in Azure Artifacts. You can only select the complete feed.

Hi @bishal-pdMSFT  Any response to this?

Just an update:
If you use feed: config this will also fail if you use the nuget.config XML as provided by azure artifacts web interface.
you need to remove the '@' from 'key' to make it work properly.

Adding @shubham90 as this is related to nuget feeds

Thanks @bishal-pdMSFT, Adding @phil-hodgson as he is the owner of this task


vocab-sensitive tag filtering

This introduces a feature that allows public users to filter source sets by tags on the source_sets#index view.
There are two ways to filter - dropdown menus, and clicking on a linked tag listed under a set.
Changes to the code include:

In the source_sets#index controller, the instance variable @tags used to be an Array of tag slugs, taken from params[:tags].  However, the view need access to the entire Tag model, not just the slugs.  So, the value of @tags is now an Array of Tags.

There is a new boolean data field for vocabularies called filter.  This field allows the admin to determine whether or not a vocabulary will be filterable on public UI. It will help admin workflows, b/c they can ensure that all necessary data is in the database before “turning on” the filter.  Note that views only display data from “filterterable” vocabularies (i.e. vocabularies where filter-true).

There is a helper method, filters_for_sets, which returns filterable vocabularies and their associated tags for a given group of sets (for public users, the group of sets will be published sets; for admins, it will be all sets).  By collecting all of this data into a Hash that is available to the view, I was able to significantly reduce calls to the database.

There is an edge case in which a user keys in a URI that contains multiple tags from the same vocabulary.  This doesn’t happen naturally on the site, but could happen.  In that case, the select element appears as an HTML multi-select, ie. an expanded select menu with multiple terms hilighted.  Because the multi-select menu takes up so much space on the screen, it is not the default.

This PR may benefit from some refactoring, and there is one rspec test that is not yet working; however, in the interest of getting it out the door on time, I’m submitting it as in with the intention to iterate later.

@markbreedlove I streamlined and sanitized the query: https://github.com/dpla/primary-source-sets/commit/e317be1f35e293b208e093f1e16a1d00b2a2b4ec

OK, looks good!

rebased - should be ready to :merge: if @markbreedlove is ready

On second thought @markbreedlove I have some style changes to the UI I can merge in before we :merge:.  I'll do that now...

Okay @markbreedlove I changed the UI display based on feedback from Franky.  It required adding a new helper method, for which there is also a test.  I've tested my local instance in browser, and everything is working as expected.