how to upgrade a single rancher node to ha mode

Rancher Version:
rancher v1.1.0-dev2-rc3
Docker Version:
Docker version 1.10.3, build 20f81dd
OS and where are the hosts located? (cloud, bare metal, etc):
ubuntu 14.04
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
We have a single node with some service ,and need to be ha
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
1.Run  a single master with extend database
docker run -d --restart=always -p 8080:8080     -e CATTLE_DB_CATTLE_MYSQL_HOST=<IP_ADDRESS>   rancher/server:latest
2.add some host and service to that rancher server

enable ha, update "Host Registration URL"
Waiting for host and service back...

Results:
we found all the host be come Reconnection.....
and service become unhealthy
Expected:
all host back and service recovery

Per the directions, it doesn't seem like you've actually turned on HA.
After you've launched your script generating Rancher server, you need to generate the script and save it. Then you need to stop the first rancher/server instance and then re-launch rancher/server with the script.
Did you do those steps? These should be done BEFORE adding any hosts into Rancher.

Done as your say?but before enable ha?we already have losts of host and service in a single rancher server?
We want to upgrade that rancher server?Let all old service and docker host ?connect to a ha rancher cluster without service downtime?
? 2016?5?27??08:08?Denise <notifications<EMAIL_ADDRESS>???
Per the directionshttp://docs.rancher.com/rancher/latest/en/installing-rancher/installing-server/multi-nodes/, it doesn't seem like you've actually turned on HA.
After you've launched your script generating Rancher server, you need to generate the script and save it. Then you need to stop the first rancher/server instance and then re-launch rancher/server with the script.
Did you do those steps? These should be done BEFORE adding any hosts into Rancher.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rancher/rancher/issues/4893#issuecomment-222028577, or mute the threadhttps://github.com/notifications/unsubscribe/AQcWuDlPWxkoR2LUpTG6KCjWo4FxLWkVks5qFjXggaJpZM4IlFEv.

Done as your say.But before enable ha,we already have losts of host and service in a single rancher server.
We want to upgrade that rancher server.Let all old service and docker host ,connect to a ha rancher cluster without service downtime.
So I create a testing environment,and make sure we can do the same steps in our production environment.

Let me re-confirm with our engineering team, but I believe in order to upgrade an existing Rancher instance to a HA enabled instance, there will be some service downtime as you need to spin up a new Rancher server that will HA enabled.
But it also sounds like you only have 1 single Rancher master, so I'm not clear on how you are trying to make this setup HA without more than 1 Rancher server.

I have 1 rancher server with some services and try to enable ha,with other two new rancher server.

any updates？

Yes, you should be able to take an existin Rancher instance and convert it to HA.
Have you confirmed that when you try to convert to HA, you stop the currently running old rancher server (That generated the script) and used the script on that machine?

@rmops Please re-open if you have further questions.


Passing non-existant selector to Backbone.View

This is more of a question really...
Given this fiddle: https://jsfiddle.net/oowrs2gh/ (copied below also)
var MyView = Backbone.View.extend({
});

var view = new MyView({
	el: '#foo-bar-bat'
});

console.log(view.el);

The el is undefined. And I wonder if perhaps _ensureElement should fallback to creating an element if the selector fails?

This issue was recent raised with Marionette as well as currently what happens is nothing.  The view appears to work and if you adhere to jQuery for rendering and appending, there may not be any error given, you'll just end up with a blank view where you were expecting it to be prefilled with DOM.  I don't really think that creating an element is the ideal solution as it doesn't really follow what I imagine the intention is of setting the el as a selector.  Honestly I'd prefer that el didn't take a selector at all.. it's easy enough to give the view an el... but since it does take a selector, I think it'd be better to error if it doesn't find it.

That's working as intended. If you pass a selector to view.el, it needs to exist. Otherwise, why pass it at all?


Unable to load to T-Beam AXP2101-V1.2

I'm unable to load the config file to T-Beam APX2101-V1.2.   The firmware loads OK.
I've been able to load alternative APRS Tracker software using the same method - VSCode - Upload firmware - upload config and works fine.   :-(  The alternative does list the T-Beam APX2101-V1.2. as a specific environment.  I would have thought that the T-Beam V1.2 would have worked for this application, but doesn't seem to.
Also of note, I have been able to upload your APRS Gateway using the web installer to the same T-Beam APX2101-V1.2 without any issues.

how does it fail to upload the filesystem?
error on vscode output? or problem in editing the tracker_conf.json file?

No change in tracker display and not beaconing (or doesn't seem to be).  I had expected the display to show my callsign/ssid.

but you see LORA APRS welcome message in display and nothing else?

Yes, nothing on the display changes - stays the same as the photo (not my photo, not my screen, but this is what is displayed).

ok, does you /data/Tracker_conf.json file has any small red waves in it ? (anywhere?)

Not that I can see..
{
"beacons": [
{
"callsign": "MM0NBW-15",
"gpsEcoMode": false,
"symbol": "[",
"overlay": "/",
"micE": "",
"comment": "LoRa Tracker",
"smartBeacon": {
"active": true,
"slowRate": 120,
"slowSpeed": 3,
"fastRate": 60,
"fastSpeed": 15,
"minTxDist": 50,
"minDeltaBeacon": 20,
"turnMinDeg": 12,
"turnSlope": 60
}
},
{
"callsign": "MM0NBW-15",
"gpsEcoMode": false,
"symbol": ">",
"overlay": "/",
"micE": "",
"comment": "LoRa Tracker",
"smartBeacon": {
"active": true,
"slowRate": 120,
"slowSpeed": 10,
"fastRate": 60,
"fastSpeed": 70,
"minTxDist": 100,
"minDeltaBeacon": 12,
"turnMinDeg": 10,
"turnSlope": 80
}
},
{
"callsign": "MM0NBW-15",
"gpsEcoMode": false,
"symbol": "b",
"overlay": "/",
"micE": "",
"comment": "LoRa Tracker",
"smartBeacon": {
"active": true,
"slowRate": 120,
"slowSpeed": 5,
"fastRate": 60,
"fastSpeed": 40,
"minTxDist": 100,
"minDeltaBeacon": 12,
"turnMinDeg": 12,
"turnSlope": 60
}
}
],
"display": {
"showSymbol": true,
"ecoMode": false,
"timeout": 4,
"turn180" : false
},
"other": {
"simplifiedTrackerMode": false,
"sendCommentAfterXBeacons": 10,
"path": "WIDE1-1",
"nonSmartBeaconRate": 15,
"rememberStationTime": 30,
"maxDistanceToTracker": 30,
"standingUpdateTime": 15,
"sendAltitude": true,
"sendBatteryInfo": false,
"bluetoothType": 1,
"bluetoothActive": true,
"disableGPS": false
},
"winlink": {
"password": "ABCDEF"
},
"bme": {
"active": false,
"temperatureCorrection": 0.0,
"sendTelemetry": false
},
"notification": {
"ledTx": false,
"ledTxPin": 13,
"ledMessage": false,
"ledMessagePin": 2,
"ledFlashlight": false,
"ledFlashlightPin": 14,
"buzzerActive": false,
"buzzerPinTone": 33,
"buzzerPinVcc": 25,
"bootUpBeep": false,
"txBeep": false,
"messageRxBeep": false,
"stationBeep": false,
"lowBatteryBeep": false,
"shutDownBeep": false
},
"lora": [
{
"frequency": 43912500,
"spreadingFactor": 12,
"signalBandwidth": 125000,
"codingRate4": 5,
"power": 20
},
{
"frequency": 43912500,
"spreadingFactor": 9,
"signalBandwidth": 125000,
"codingRate4": 7,
"power": 20
},
{
"frequency": 439912500,
"spreadingFactor": 12,
"signalBandwidth": 125000,
"codingRate4": 5,
"power": 20
}
],
"pttTrigger": {
"active": false,
"io_pin": 4,
"preDelay": 0,
"postDelay": 0,
"reverse": false
}
}

I pasted the code here to check and all looks good:
now into the (once again) upload filesystem part
so :

turn off VSCODE
disconnect Tracker from usb from PC

turn on VSCODE again
connect Tbeam with usb cable to PC
and just then , try to "UPLOAD FILESYSTEM IMAGE" and return with comments ;)

Thanks - uploaded filesystem image only and no change.  Here is a paste of the output from VSCODE:
Verbose mode can be enabled via -v, --verbose option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/ttgo-t-beam.html
PLATFORM: Espressif 32 (6.7.0) > TTGO T-Beam
HARDWARE: ESP32 240MHz, 1.25MB RAM, 4MB Flash
DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES:

framework-arduinoespressif32 @ 3.20016.0 (2.0.16)
tool-esptoolpy @ 1.40501.0 (4.5.1)
tool-mkfatfs @ 2.0.1
tool-mklittlefs @ 1.203.210628 (2.3)
tool-mkspiffs @ 2.230.0 (2.30)
toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ deep+, Compatibility ~ soft
Found 53 compatible libraries
Scanning dependencies...

Auto-detected: COM7
Uploading .pio\build\ttgo-t-beam-v1_2\spiffs.bin
esptool.py v4.5.1
Serial port COM7
Connecting.........
Chip is ESP32-D0WDQ6-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 08:f9:e0:f7:50:6c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00310000 to 0x003effff...
Compressed 917504 bytes to 2925...
Writing at 0x00310000... (100 %)
Wrote 917504 bytes (2925 compressed) at 0x00310000 in 4.9 seconds (effective 1512.8 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
========================================================= [SUCCESS] Took 23.02 seconds =========================================================
Environment       Status    Duration

ttgo-t-beam-v1_2  SUCCESS   00:00:23.020
========================================================== 1 succeeded in 00:00:23.020 ==========================================================

Terminal will be reused by tasks, press any key to close it.

now,  with the board connected (and VSCODE open) press on the bottom the "plug" symbol
the energy plug connector (this will open the serial port info)
wait till this new window is ready in viscose and press RST button on the tbeam
this should give us info on the booting process

OK, not sure what exactly fixed it, but here is what I did;
Downloaded the source files again.
Edited the config json file.
Uploaded firmware
Uploaded config
**At this stage nothing happened.
Then I saw your message about pressing the "plug" button on VSCode - which I did and now the tracker seems to be working ok...
Strange behaviour, but we got there!  Thank you for your help with this!  It's very much appreciated!
Best,
Craig

OK, not sure what exactly fixed it, but here is what I did; Downloaded the source files again. Edited the config json file. Uploaded firmware Uploaded config
**At this stage nothing happened.
Then I saw your message about pressing the "plug" button on VSCode - which I did and now the tracker seems to be working ok...
Strange behaviour, but we got there! Thank you for your help with this! It's very much appreciated!
Best, Craig

FINALLY WE SUCCEED!!!!!   great!!
now enjoy! :)


Wider dependency requirements

The package as of now to be installed requires  tensorflow ~= 2.4.0 and keras ~= 2.4.0. It turns out that this is sometimes problematic for folks who have custom installations of TensorFlow and a winder requirement could be set up.

Fixed via commits 770de711290d230f96feed5a2e5d073ebedfa23a and 4ee65d670dbcf8b0475c8bf417edaedc3663fec8 .


xdf importer unit tests

@arnodelorme @chkothe @dmedine @tstenner @cll008 @dojeda @aojeda
Based on our meeting, the next steps forward for XDF are to create unit tests. Don't worry about the platform (Win/Mac/Linux x Matlab/Python) yet. For now, we need sample files and a list of desired unit tests.
Please provide your desired unit tests and offer up problematic data files. We need tests to verify healthy & perfectly formatted files, as well as tests for problematic files (unusual jitter, missing nominal_rate, poorly formatted XML headers, etc.).

I don't have GitHub usernames for everyone. Please feel free to tag other users.

This issue seems to be a bit of a stub, but I recently implemented some XDF unit tests for a consulting job and checked that the following cases were correct for each combination of HandleClockSynchronization and HandleJitterRemoval:
-standard xdf with eeg and markers
-data with gaps
-data with clock resets
-data with each possible format type represented as both data and marker stream
Any unit test should also, of course, trigger any and all exceptions/error handling in one way or another.
I'd be happy to share the XDF sample files I used.

If they are small they can go here: https://github.com/xdf-modules/example-files
There's an outstanding PR to add that as a xdf submodule: https://github.com/sccn/xdf/pull/47
I have no idea if that particular submodule is currently being used by any unit tests that are part of any CI.


Error with printcoinage debug arg

Use of the printcoinage arg for extra debugging causes random and silent daemon crashes.

Fix merged, closing

Mixed up commits, this was not merged yet...

Fix merged, closing issue


SVGs blocking buttons - not calling function when expected

More info here: https://github.com/Lorem-Ipsum-Spot/spot/commit/c41b3e482188f98578cbd6136c040bafab61df88#r141566417

Fixed in commit db3bec3e2b6700b37379a5e40ea253cc7c2539aa good job


chore/debug lerna

fix: make graphql a peer dependency
ci: run tests against v16
feat: support graphql v16
Remove overlapping version ranges
feat: use latest version of graphql internally
chore: add debug info with lerna

Codecov Report

Merging #65 (143499c) into main (e265723) will increase coverage by 0.16%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #65      +/-   ##
==========================================
+ Coverage   95.91%   96.07%   +0.16%
==========================================
  Files          13       14       +1
  Lines         856      892      +36
  Branches      178      191      +13
==========================================
+ Hits          821      857      +36
  Misses         35       35

Impacted Files
Coverage Δ

...emetry-propagator-instana/src/InstanaPropagator.ts
100.00% <100.00%> (ø)

...metry-propagator-ot-trace/src/OTTracePropagator.ts
95.91% <100.00%> (+0.08%)
:arrow_up:


Update Angular readme

Update readme for the Angular example, primarily to include information on how to configure the client required to run the sample. Also ran prettify on the markdown file and removed code that was copied from the source into the markdown file.

@derekendres I've removed the references to specific Angular versions.


Add Double ImageList, better code, better modularity

Description by Korbit AI
What change is being made?
Implement enhanced modularity for TSIMG by introducing the Double ImageList capability, refining the build process with autogenerated build info, and introducing multiple new utilities and code structure improvements in various source files.
Why are these changes being made?
These changes enhance code modularity, facilitates the dynamic generation of configuration information, and introduces functionalities to accommodate handling of multiple image lists, particularly for improving the user interaction with time-series image data. This restructuring ensures more maintainable code and lays the groundwork for further enhancements while supporting a richer user interface and command-line interactions. The use of a generated build info file assures the integration of consistent metadata across builds, aiding in traceability and debugging.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

/korbit-review


[gl] fix the WASM target and enable on CI

I believe the target was broken for a while, possibly since we moved to Github actions.
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:

bors r+


tokenize:dropdown:fill pulls in empty dropdown after ajax response

Following code pulls in empty dropdown after ajax success response
object.trigger('tokenize:dropdown:fill', [$items]);
whats the solution?

object.trigger('tokenize:dropdown:clear');
https://zellerda.github.io/Tokenize2/events.html

now it says Cannot read property 'find' of undefined ?

use object.trigger('tokenize:dropdown:show') first

The same situation happens to me.
The drop-down does not fill with the received data and when clicking adds undefined.
This is my code.
I need help. Thanks.
    $('.tokenize-search').tokenize2({
        tokensMaxItems: 1,
        searchMinLength: 3,
        tokensAllowCustom: true,
        dataSource: function (term, object) {
            $.ajax('/Articulo/SearchArticulo', {
                type: 'POST',
                data: { search: term, idcarta: idcarta },
                dataType: 'json',
                success: function (data) {
                    var $items = [];
                    var i = 0;
                    object.trigger('tokenize:dropdown:clear');
                    $.each(data, function (k, v) {
                        $items.push(v);
                        i++;
                    });
                    object.trigger('tokenize:dropdown:show');
                    object.trigger('tokenize:dropdown:fill', [$items]);
                }
            });
        }
    });

    $('.tokenize-search').on('tokenize:tokens:add', function (e, value, text, force) {
        console.log(value);
    });

Hi @flopez2904 ,
Can you please post the solution for this problem.
I too got the similar issue and unable to find the solution so far.
Thanks for your help.
Thanks,
Anand Kumar P.


BUG: navbar not working

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
https://github.com/anuragverma108/SwapReads/assets/169196836/23da0e7d-d22d-4c0a-9f24-5b547b09d8d2
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign me this issue


Run on client-side only, and remove unused code

Also removes some unused code.

What is the advantage of doing this? Can the mod still be included in a server's mod files and be ignored if this is done, like it can currently?

With this change, the mod will no longer be loaded if ran on a dedicated server (even if its in the mods folder), reducing startup time

I believe this is quite a useless change.

Can this just be changed? My server is causing errors when using a modpack
that has this mod
On Fri, Dec 29, 2023 at 12:10 PM Caoimhe Ní Bhroin @.***>
wrote:

I believe this is quite a useless change.
—
Reply to this email directly, view it on GitHub
https://github.com/hamarb123/MCMacOSInputFixes/pull/19#issuecomment-1872315520,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5A2HSM37OBJJK7NI46NOHDYL4PURAVCNFSM6AAAAABAYAT3R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGMYTKNJSGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can this just be changed? My server is causing errors when using a modpack that has this mod

You only just indicated that this was potentially causing issues. Please try the following before we consider this change: 1. try removing just this mod alone from the modpack files, and seeing if it launches, 2. if that makes it not fail: please open a new issue with the error log.


Sandbox API keys are expired

I tried all the keys in https://developers.paymaya.com/blog/entry/checkout-api-test-credit-card-account-numbers but they all returns key is expired

resolved in #14


Docker hub image for arm64 architecture fails when initializing it

Describe the bug
When running the docker image for arm64 version 8.128.22, it constantly outputs the following error. After that, it tries to restart but after all, it shows the same error.
To Reproduce

Download docker image for arm64 with version 8.128.22 and run it

Expected behavior
It should start correctly.
Environment (please complete the following information):

OS: MacOS
Infrastructure:self-hosted
Versions 8.128.22

Vespa version
8.128.22

Yes, this is an error, I have reproduced it and we treat it as an incident - thanks for reporting!
Please use vespaengine/vespa:8.128.22 until we have released a new image - sorry for the inconvenience

This is now fixed and vespaengine/vespa:latest resolves to a working 8.128.22


dragEnabled=true does not work with material-ui TextField in grid item component

I am using material-ui along with AbsoluteGrid. When I have the TextField component in my grid item component, I cannot click on the TextField to select it and start editing text. Only with dragEnabled=false does this work. I believe this is because the AbsoluteGrid is eating the touch events in the onDrag function.

@muuhoffman curious whether you ever solved this, if not or for anyone else running into this, I've done the following. It's not pretty, but it works by wrapping createAbsoluteGrid like this:
import createAbsoluteGrid from 'react-absolute-grid';

export default (...args) => {
  const AbsoluteGridBase = createAbsoluteGrid(...args);
  class AbsoluteGrid extends AbsoluteGridBase {
    constructor(props, context) {
      super(props, context);
      const originalStartDrag = this.dragManager.startDrag.bind(this.dragManager);
      this.dragManager.startDrag = (e, domNode, item, fnUpdate) => {
        // Prevent preventDefault to allow focus on input
        if (e.target.nodeName === 'INPUT') {
          e.preventDefault = () => {};
        }
        originalStartDrag(e, domNode, item, fnUpdate);
      };
    }
  }
  return AbsoluteGrid;
};

it would be nice if one could define exceptions to the preventDefault behavior in the props instead


[context] Context as an interface

Issue: #1579

Summary:

Context implementation has been moved mostly to ServletContext. The core implementation has only 160 lines, the rest is provided as default methods in Context interface and are more likely an API sugar.
Quite a lot of internal codebase used Context's internals to apply some changes. If it was possible, all those methods use now standard API methods from Context.
ctx.req & ctx.res fields are replaced with methods ctx.req() & ctx.res() - I think it looks more consistent with the rest of Context API now.

Might be called ctx.request() & ctx.response() as well

Lack of @JvmOverloads for interfaces in Kotlin

(-) Overloaded methods have to be defined explicitly just like in Java, so a little bit more boilerplate
(-) We cannot use @see in Javadocs to refer other overloaded methods (dokka bug)

(+) We're kinda forced to prepare dedicated signatures for each scenario, so might be useful in reducing signatures that doesn't make sense

(+) We're also forced to provide standalone javadocs for each method, we may need to write a little bit more, but user will see more descriptive content I guess

I need a feedback on that, as I think there's no point to make further cleanups etc. if you don't like the direction of those changes at all.
In case of general approval, I'd like to also:

Add missing javadocs
Review more sources were context is used to simplify usages and reduce calls to internals
Remove utility methods that helps to construct stub Context for mocking etc., there's no point to support them anymore

I appreciate the effort to clean things up, but it would be easier to evaluate if this change just contained the "Context as an interface" change.
About ctx.req and ctx.res, they were left "inconsistent" to show that you are stepping away from the Javalin API and over to the Servlet API.

The problem with "Context as an interface" change is that context is present in half of the sources, so it naturally just affected some related features, but I did not change behavior any of them. Also, a lot of utilities just doesn't make sense since Context is an interface as those methods were mostly about to "hack" it a little bit for non standard usages (like mocking).
Speaking of the ctx.req & ctx.res, despite of the difference between methods & fields, those properties were exposed anyway. Ideally, would be great if Context cover missing features and we could hide it in a proper way (under implementation or in dedicated wrapper), but that's change for another topic I guess. I can turn those methods into Kotlin properties for now, so it'll contain less changes in this PR and we could talk about it in standalone issue.

I've slightly reduced changes you see in diff caused by this PR, we can discuss those ideas in standalone PRs to simplify and extract each topic.
I've kept the method with current handle type tho, in theory it could be also moved to standalone PR but I don't think it makes much sense. Previous impl explicitly affected HandleType with Context:
https://github.com/javalin/javalin/blob/5076467ad145f70e08c7d2d78c1bc9e56b0a4478/javalin/src/main/java/io/javalin/http/HandlerType.kt#L20-L26
And usages were inconsistent, it's now just method() that returns HandlerType.

In theory I can move those cached properties to interface as it could be possible to store it in private val, but not sure if that's the right call 🤔

In theory I can move those cached properties to interface as it could be possible to store it in private val, but not sure if that's the right call 🤔

They can't be lazy then though?

With this change we split the implementation into two places, and we lose reified methods for Kotlin users (but can be imported). I'd argue that these are not unimportant downsides.
So what do we gain? How does this improve the life of our maintaners and end users? It's easier to mock using mockito, but no change from mockk (?). Is there any other benefit?
We get some cleanup of the @JvmSynthetic tags, but we could also group these properties into a single property and provide access to them.
Would it be better if the interface actually had 0 default methods, so we could keep the implementation in one place?

Oops, I thought I can define property initializers in interfaces, you're right!

With this change we split the implementation into two places, and we lose reified methods for Kotlin users (but can be imported). I'd argue that these are not unimportant downsides.

Yes, but those implementations are different. The first one (ServletContext) is internal implementation of context handling by Javalin and exposing core functionalities from Context and the second one is just a sugar, implementation of utility methods on top of that. Even the fact we're able to implement most of them in interface shows which features are dependent on Javalin's core and which on request/response.
We don't lose reified methods for Kotlin users, half of Kotlin std is implemented on top of extension functions. Despite of extra import, there's no difference for user:

So what do we gain? How does this improve the life of our maintaners and end users? It's easier to mock using mockito, but no change from mockk (?). Is there any other benefit?

In my opinion it provides healthier separation between internal implementation in general. For me it's easier to read and I think it's easier to see what Context really does. If we'd like to for instance make Context less mutable etc., all we need is to work on ServletContext that is currently relatively small class now.
Speaking of mocking, well... most of Javalin users are Java developers (surveys), so I'd say that Mockito is leading library, so that's definitely a difference. It also removes need to support those tricky Context init methods -> may lead to possibility to encapsulate even more internals in ServletContext.

We get some cleanup of the @JvmSynthetic tags, but we could also group these properties into a single property and provide access to them (I like these "private" APIs which let developers do unsafe things at their own risk).

As long as removing @JvmSynthetic  is a good change, this PR is not really against exposing unsafe api. We can still do this and I think it's ok.
Also, a personal note about "private api": As user I never seen e.g. req & res as unsafe api because it was implemented as fields, but by assuming how it works in general. I don't think that people that are newbies see much difference between methods and fields, in the end it's available directly in Context.

Would it be better if the interface actually had 0 default methods, so we could keep the implementation in one place?

At first I through about it, but I don't quite see a benefit of that. We'd just increase amount of signatures etc. and we'd get literally nothing out of this, especially that like I said, most methods are only utilities implemented on top of the core methods, so in general it's healthier for implementation to keep only important things, especially in our case where we don't quite expect people to implement Context on their own and even if they would, it also might be a better solution. For instance, user in Mockito/custom impl can implement only the root method, and he has a guarantee that all related methods will use it by default. Without default methods they'd need to implement each one of them.

A better approach would be probably wrapping those unsafe properties in dedicated wrapper ctx.getOrigin().req/res/other with proper javadocs that describe how it works than relying on implementation detail such as field vs method 🤔

Yeah, I think something like that might be a good idea, regardless of interface or no interface.

In my opinion it provides healthier separation between internal implementation in general. For me it's easier to read and I think it's easier to see what Context really does. If we'd like to for instance make Context less mutable etc., all we need is to work on ServletContext that is currently relatively small class now.

 Adding this layer does introduce some complexity and muddies the water a bit. I'm afraid we'll end up in a situation where we have to ask ourselves "should this go in the interface or in the implementation" when we add new features to Context/ServletContext, without really having a good answer. If we are doing this, we should at least add some documentation describing our thoughts.
If Java mocking is a big benefit from this, we should probably include some Java mocking tests.
Also, sorry for being a pain, but it would be nice if you could pull out the ctx.method() change as a separate PR - I can merge it right away if you do ☺

You say that, but then you had a commit titled Remove unnecessarily duplicated methods.

That's mostly because I've duplicated whole Context class (that was slightly big) and had to go through all of those methods + like I said: I need a feedback on that, as I think there's no point to make further cleanups etc. if you don't like the direction of those changes at all. - we're moving forward so I'm just cleaning it up.

"should this go in the interface or in the implementation"

If we can implement feature on top of existing Context methods, then it should be in interface. ServletContext should contain only implementation related to internal fields, such as handling (fields from constructor) and caching (utility fields).

If Java mocking is a big benefit from this, we should probably include some Java mocking tests.

Might be a good idea!

Also, sorry for being a pain, but it would be nice if you could pull out the ctx.method() change as a separate PR - I can merge it right away if you do ☺

Sure :)

That's mostly because I've duplicated whole Context class (that was slightly big) and had to go through all of those methods + like I said: I need a feedback on that, as I think there's no point to make further cleanups etc. if you don't like the direction of those changes at all. - we're moving forward so I'm just cleaning it up.

Just to be clear, it wasn't meant as a comment on your work, but the pitfalls that follows with using this approach. This commit message would not be possible if we had a strict interface, or just a single class.

Thanks @dzikoysk, one more item to check in the roadmap 😁


Joda to Java time

Summary:
Joda -> Java8 time
JIRA issues: METRONOME-238

after reading the docs I think that ZoneOffset != ZoneId and what Metronome supports in its API is actually a ZoneId, not ZoneOffset - for that reason I think we should stick with ZoneId (even though there is no enum)


Cannot play music nor see library

What version of Music Assistant has the issue?
2022.7.0
The problem
No music will play when launching either from the media browser or from the side bar and the side bar now wont load my youtube music or spotify it shows as if there is nothing there. The integration used to perform flawlessly then completely stopped.
How to reproduce
Just playing anything will start the google home then nothing comes out and the device shows it was switched to off by maas
Relevant log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2022.7.6
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Windows

I am not a Home Assistant newby I have had my system up and running for about 2 years now but usually if it doesnt work I just move on but love this integration. So if there are any logs etc that could be helpful please lmk what you need and I can use some googlefu to get it over to you!

Hi @bnieves1994
I need some more info to understand your issue.

You indicated that music doesn't play in de media browser. Are you referring to the standard media browser from home assistant? Or the browser in music assistant?

what side bar now wont load your youtube music or spotify? Music assistant doesn't have a side bar?

Some screen shot could help

Forgive my lack of info up front. So both the home assistant media browser and the browser in music assistant. Specifically I am navigating both ways as follows. I will include screen shots

If I navigate as such it still wont play music but shows my saved music in spotify etc. However when clicking music assistant in the side bar like this nothing is shown at all

And again however I chose to try to use it would turn the speaker on which is confirmed by the google home start up sound but then the media never plays.

Please make sure you're using the latest version of Music Assistant which is 2022.7.0 (or 2022.7.1 which has been released just now).

Clear the browser cache because the screenshot above are from a previous/old version. You should see a search bar on top and a "browse" button after radio.

If playback fails, that usually is an issue with the network settings. The players need to be able to reach the HA server directly over the internal network. The IP they connect to is derived from the "internal URL" setting in the HA config. Maybe check there if it's filled with a valid url ?

@erkr and @marcelveldt Thank you both so much for your fast responses and solutions. Everything is working as it should and the new update is incredible. Thank you both again!


Add support for crossing island as way

OSM Tag(s)
footway=traffic_island
How would you like this tag to see supported?
As a Preset
Label
Crosswalk island
Aliases
Crossing island, traffic island, refuge island
Terms
No response
Link to OSM Wiki page
https://wiki.openstreetmap.org/wiki/Tag:footway%3Dtraffic_island
Status of the Tag
In Use
Usage of the tag
4,062
Replaces other Tag?
no
Regional Tag?
No response
Further Information
Often times I see users tagging the island part of the crossing way with footway=crossing, crossing:island=yes(which has different implications. Adding this key will improve detailed tagging of crossing and avoid future mistagging.

I think the name of this preset should be consistent with the name of the crossing:island field, which is currently “Refuge Island”:
https://github.com/openstreetmap/id-tagging-schema/blob/0c8be6bf01c2e5b8e7361da8550e2c22b7768cc1/data/fields/crossing/island.json#L4

I've included this preset in the PR for crossings refactoring: #590


Base64 SVG does not load in new version

Hi using version 0.14.5, my SVG style using base64 can be loaded:
.svg-preview {
  background-image: url('data:image/svg+xml;base64,PD94bWwgdmVyc2lvbjXXX....');
}

However upgrading to version 0.15.1, the browser no longer able to load it :(
Any idea? Don't think is my SVG source file as it can be loaded previously.

My bad ignore it.


Game system integration api doc and extension of the TerrainInfo objects

This PR does two things:
First, it adds the properties environment and obstacle to the TerrainInfo class, as that information might be useful for consumers of the new API. In this PR I assumed that it's not possible for a token to specify an environment or obstacle. For this reason I've made TokenTerrainInfo always return undefined for those properties.
Secondly, the PR adds a short documentation about the new API, so module and system authors know what they are supposed to be doing.

Good catch. I fixed those (and the other two in the measurement templates, that had the exact same issue)


Change position from LTR to RTL

Is there any configuration that change the default position of the tabs from left to write -> change it to from right to left (first tab most right)? Also change the swipe direction to left instead of write?

Duplicate of #66


Make sure mc questions are all locked down when show team interface = false

I did a full pass with show_team_interface = False and allow_advancing = False and could not bypass any of the mc questions, so I think we are good here.


Add AdminConsolePublicURL to webconsole config

/assign @deads2k
@jwforres fyi

Corresponding change to the admin console: https://github.com/openshift/console/pull/270

kicking travis

/lgtm

there is no internal equivalent in openshift/origin, so this shouldn't require any origin changes.  merging


Could not install franklinkim.environment

Failed at following instruction:
ansible-galaxy install franklinkim.environment
- downloading role 'environment', owned by franklinkim
 [WARNING]: - franklinkim.environment was NOT installed successfully: - sorry, franklinkim.environment was not found on https://galaxy.ansible.com.

ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.

https://galaxy.ansible.com/franklinkim/environment is not found currently but https://galaxy.ansible.com/weareinteractive/environment is found.
I tried the following and succeeded:
ansible-galaxy install weareinteractive.environment
- downloading role 'environment', owned by weareinteractive
- downloading role from https://github.com/weareinteractive/ansible-environment/archive/1.3.0.tar.gz
- extracting weareinteractive.environment to /home/taiki/src/github.com/smartoperation/cobit/infra/playbook/galaxy_roles/weareinteractive.environment
- weareinteractive.environment (1.3.0) was installed successfully

Hi, yes, this is due to Ansible Galaxy (see https://github.com/weareinteractive/ansible-ufw/pull/16#issuecomment-427034769)

thanks!


Support query_string function in SQL/PPL query engine

Related design is presented in issue #182
Todo list

[ ] Support the query_string functionality by pushing it down to the search engine
[ ] Enable query_string function in SQL and PPL syntax and parser, including all the available parameters
[ ] Make sure the function in new engine is compatible with the old engine support
[ ] Add unit tests. (Unit tests are mandatory for all code changes.)
[ ] Add integration test cases for query_string
[ ] Update user manual

Function details
The query_string function maps to query string used in the search engine. This query returns documents based on a provided query string, using a parser with a strict syntax.
Syntax:
query_string([**field_expression** | **field_list**, ] **query_string_expression**[, option=<option_value>]*)
Query string expression syntax:
**query_expression** operator **query_expression**, where operator includes AND and OR
Example: "query_1 AND query_2"
Available options:

analyzer
default_field: (string) Default field you wish to search if no field is provided in the query string.
fields: (array) Array of fields you wish to search. Set to "*" if wish to search all fields. Defaults to the index.query.default_field index setting, which has a default value of *.
allow_leading_wildcard: (boolean) If true, the wildcard characters * and ? are allowed as the first character of the query string. Defaults to true.
analyze_wildcard: (boolean) If true, the query attempts to analyze wildcard terms in the query string. Defaults to false.
auto_generate_synonyms_phrase_query
boost
default_operator
enable_position_increments: (boolean) If true, enable position increments in queries constructed from a query_string search. Defaults to true.
fuzziness
fuzzy_max_expansions
fuzzy_prefix_length
fuzzy_transpositions
lenient
max_determinized_states: (integer) Maximum number of automaton states required for the query. Default is 10000.
minimum_should_match
quote_analyzer: (string) Analyzer used to convert quoted text in the query string into tokens. Defaults to the search_quote_analyzer mapped for the default_field.
phrase_slop: (integer) Maximum number of positions allowed between matching tokens for phrases. Defaults to 0. If 0, exact phrase matches are required. Transposed terms have a slop of 2.
quote_field_suffix: (string) Suffix appended to quoted text in the query string.
rewrite: (string) Method used to rewrite the query.
time_zone

Sample query:
# Search query 1
GET my_index/_search
{
  "query": {
    "query_string": {
      "query": "(new york city) OR (big apple)",
      "default_field": "content"
    }
  }
}

# SQL
SELECT * FROM my_index WHERE query_string(content, "(new york city) OR (big apple)")

# PPL
source=my_index | where query_string(content, "(new york city) OR (big apple)")

# Search query 2
GET my_index/_search
{
  "query": {
    "query_string": {
      "fields": [ "content", "name" ],
      "query": "this AND that"
    }
  }
}

# SQL
SELECT * FROM my_index WHERE query_string([content, name], "this AND that")

# PPL
source=my_index | where query_string([content, name], "this AND that")

@joshuali925 Here is a quick demo of the query_string implementation usage in SQL and PPL for PR: 675
https://user-images.githubusercontent.com/36905077/177881003-e866a767-4989-42bd-afdd-aa307d5a9e2a.mp4

fixed by https://github.com/opensearch-project/sql/pull/675 and https://github.com/Bit-Quill/opensearch-project-sql/pull/85

@forestmvey The video is really helpful to user. Do we have our channel for all these video? If not, maybe we can put them into doc in https://github.com/opensearch-project/sql/tree/main/docs/presentations

@forestmvey The video is really helpful to user. Do we have our channel for all these video? If not, maybe we can put them into doc in https://github.com/opensearch-project/sql/tree/main/docs/presentations

Updating the documentation with video links to the github issue may be nice to do alongside saving demo videos in this directory you've suggested. AFAIK demo videos have only been attached to the github issues so far.


Initial Commit

It's a little rough around the edges, but it works for a lot of the basic stuff. This is running the ILI9341 displayio driver example without modifications:

Lots more stuff to add, but it's a good starting point.

Please ignore the fact that it's HUGE. It needs to be split into multiple files really, but I wanted to get something working committed.

Text artifacts fixed.

Much better. This is what the final rendering is supposed to look like:

yay fonts!

@makermelissa Do you think this could work on this older Pi 2.8" TFT: https://www.adafruit.com/product/1601
It does seem to be using ILI9341 driver so I think it maybe it could be used with this. I found the example code in the ILI9341 driver repo and tried it out but I am only getting a blank white screen with no error message.
I think this example has the pins meant to be used on Feather devices. Did you change the pins used to something different for the Raspberry pi?

It should work with that. You’ll need some displayio libraries which aren’t on pypi. Yeah, I forgot I changed pins.

I got the adafruit_display_text and adafruit_ili9341 and I think it's all loaded correctly for the example to use them.
Can you share which pins you used for your setup?

D25 for d/c D24 for reset and CE0 for chip select if I recall.

Thank you!
Got it working successfully with Raspberry Pi 3 B+

Thanks for testing @FoamyGuy

You're welcome.
Thank you for working on it. This is very neat!
adafruit_display_shapes seems to be working as well:

Oh neat! I wasn't even expecting those to work yet.

This PR fixes https://github.com/adafruit/Adafruit_Blinka/issues/109. I will create issues for any missing features so that this library can be improved over time.

i haven't had time to test but others have :) so this is good by me!

Thanks


⚠ Bofrost.lu has degraded performance

In 49ea894, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1373 ms

Resolved: Bofrost.lu performance has improved in 0cf7c72 after 6 minutes.


Add falco-exporter daemonset annontations

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area falco-exporter-chart
What this PR does / why we need it:
Update PR based on https://github.com/falcosecurity/charts/pull/203
/assign @leogr
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [cpanato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 8748f16a0fa1b024f11c68687024dbee4bc12ee1

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [cpanato,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Next page scroll not working if we scroll slowly...

Next page Scroll not working if we scroll slowly...

Any chance you could confirm if this happens in a vanilla / plain Magento 1 install? If not then could you please tell us which Magento version you're running and what browser you're using to test?


?url and ?raw suffix support

Using ?url suffix  to explicit URL Imports,
as well as ?raw suffix to import .svg file as string.
#20  by gawlk

Thanks @Thy3634
I'll look into it next week

@Thy3634 Could you run the linter over your code? npm run lint

Failed. So I add a submit, and the code could be linted over now.

Failed. So I add a submit, and the code could be linted over now.

There are still some lint errors:
index.js:5:36: Missing space before function parentheses.
index.js:12:14: Missing space before function parentheses.
index.js:15:15: Missing space before function parentheses.
index.js:19:38: Strings must use singlequote.
index.js:20:21: Strings must use singlequote.
index.js:22:28: Strings must use singlequote.
index.js:26:20: Missing space before function parentheses.
index.js:30:38: Strings must use singlequote.
index.js:31:21: Strings must use singlequote.
index.js:39:36: Unexpected trailing comma.
index.js:40:11: Extra semicolon.
index.js:41:73: Extra semicolon.

Maybe git ignored something.
I add a commit via github directly. It should work.

Thanks for your changes! I've added 1 comment.

Thanks for your work 👍


MAMP

I cloned the repository into /htdocs using MAMP. If I go through the commands listed in the readme I get the following errors:

Going to _http://localhost:8888/angular-symfony/web/#/login_ or _http://localhost:8888/angular-symfony/web/app_dev.php/#/login_ the js does not find the templates.
Playing around with the paths in app.js I will get /username/salt not defined.
Which symfony2 version do u used? "SecurityContextInterface" is deprecated at me (See WsseListener) UPDATE: version 2.6.x cleares this problem.

Do I missed some setup step?
U.I Symfony2 version 2.7.10

Hi, do you have mod_rewrite enabled? You should access the project using http://localhost:8888/angular-symfony/ (no web).
To install dependencies (with symfony) you should use composer.phar install

I personally use a virtualhost for my testings, let me try with a subfolder to see if I get the problem

Issue should have been resolved with commit 752adc86400fa5e318da4d57d195f7ac04fe3722. Let me know if it's OK now.


Amount field is not shown when doing a subscription or a one-time donation

What: Amount field is not shown when doing a subscription or a one-time donation

Why: Looks like we should have an Amount field in this step.
The other issue is that the form can be submitted when it's invalid, this shouldn't be the case.

Related to #153


Potential regression causing resource exhausted after recent commit

I noticed latest HEAD could not hold in memory anymore a Mistral 7B training on tpu-v3-8, sequence length was set to 2048
Git bisect indicated that the commit below was the first with RESOURCE_EXHAUSTED: XLA:TPU
Author: erfanzar<EMAIL_ADDRESS>Date:   Wed Jan 31 12:02:38 2024 -0800

    Working on `LoRA`

The preceding commit does not exhibit the resource exhausted issue.
Author: Erfan Zare Chavoshi<EMAIL_ADDRESS>Date:   Wed Jan 31 18:33:47 2024 +0330

    Delete python_test/EasyDel-Checkpoints/Lora-Test directory

I instantiate the trainarguments like this (I've incorporated the change from max_length to max_sequence_length) :
tokenizer = AutoTokenizer.from_pretrained(model_id, trust_remote_code=True)
model, params = AutoEasyDelModelForCausalLM.from_pretrained(model_id)
config = model.config
config.freq_max_position_embeddings = config.max_position_embeddings  # 32768
config.max_position_embeddings = 2048  # Let use context length of ... for training
config.c_max_position_embeddings = config.max_position_embeddings

import pprint
pprint.pprint(config.get_partition_rules(True))

max_sequence_length = config.max_position_embeddings

train_args = TrainArguments(
    model_class=EasyDel.FlaxMistralForCausalLM,
    configs_to_initialize_model_class={
        'config': config,
        'dtype': jnp.bfloat16,
        'param_dtype': jnp.bfloat16,
        'input_shape': (1, 1)
    },
    custom_rule=config.get_partition_rules(True),
    model_name='MistralBoreas',
    num_train_epochs=1,
    learning_rate=1e-5,
    learning_rate_end=1e-6,
    optimizer=EasyDelOptimizers.ADAMW,
    scheduler=EasyDelSchedulers.WARM_UP_LINEAR,
    warmup_steps=500,
    weight_decay=0.01,
    total_batch_size=1,
    save_steps=2000,
    do_train=True,
    do_eval=False,
    backend='tpu',
    max_sequence_length=max_sequence_length,
    gradient_checkpointing=EasyDelGradientCheckPointers.NOTHING_SAVEABLE,
    sharding_array=(1, -1, 1, 1),
    use_pjit_attention_force=False,
    use_flash_attention=False,
    gradient_accumulation_steps=8,
    remove_ckpt_after_load=True,
    ids_to_pop_from_dataset=['token_type_ids'],
    loss_remat="",
    dtype=jnp.bfloat16
)

trainer = CausalLanguageModelTrainer(
    train_args,
    dataset_train,
    checkpoint_path=None
)

Hello
Thank for reporting the issue ill fix that asap.

fixed you can try training Mistral Model on kaggle with a batch size of 8 and gradient au of 4.
and thank for reporting the issue

Verified it works, thanks!


Lasercount not working

Hi
i ve changed the value for MaxCount in the laser category (tried 6 and 8) and even after restarting the game (even the computer itself as i tried those changes few days ago) and there is still only 3 laser capturing stuff around.

You'll need to lower CheckIntervalTick too. It can be viewed as laser cool-down time.

oh great thanks it work fine indeed now xD


Copy of tc-java#3893

Describe the bug
The mysql container does not allow the username root for the MYSQL_USER, which makes the current TestContainerConfiguration not useful as the container will fail to start.
https://github.com/testcontainers/testcontainers-dotnet/blob/08e7fa5a6e1d08c02bf249db79ac57e097276ba6/src/Testcontainers/Configurations/Modules/Databases/MySqlTestcontainerConfiguration.cs#L40-L44
To Reproduce
_container = new TestcontainersBuilder<MySqlTestcontainer>()
    .WithDatabase(new MySqlTestcontainerConfiguration { Database = "datadonation", Username = "root", Password = "example" })
    .WithImage("mysql:8.0.29")
    .WithCleanUp(true)
    .Build();

Expected behavior
Should incoporate the possibility to use root user (e.g. for migrations)
Additional context
Basically a copy of https://github.com/testcontainers/testcontainers-java/issues/3893 for dotnet.

You can probably use the MariaDbTestcontainerConfiguration. Nevertheless, it would make sense to support it for the MySQL too. Probably it is better to inherit one configuration and adjust it to the Java behavior? Would you like to create a pull request?

I don't think it would make sense to have the same configuration for two different things.
This is also not about allowing another variable to be passed in, but about abstracting the more complicated container settings to one that works as expected from the current interface.
Basically:
new MySqlTestcontainerConfiguration {
    Username = "standarduser",
    Password = "standardpassword"
}

should set: MYSQL_USER="standarduser" and MYSQL_PASSWORD="standardpassword"
new MySqlTestcontainerConfiguration {
    Username = "root",
    Password = "rootpassword"
}

should set: MYSQL_ROOT_PASSWORD="rootpassword"
While still giving the right connectionString.

I made a draft here #629

I don't think it would make sense to have the same configuration for two different things.

What I meant by that is, MySQL and MariaDB shares the same configuration. Right now, the configuration is copied and pasted. I think we can just inherit from one or the other and get rid of the copy and paste code.


IITB BOP

Moving to portfolio of products as part of IITB's TOM suggests BOP may be starting discussions on that front

Finance
HR

Touched base with Resource Management (IITB Finance).
Now need HR but would most likely be done as part of the buy-in for the business case


aks issue

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks create
Errors:
An RSA key file or key value must be supplied to SSH Key Value. You can use --generate-ssh-keys to let CLI generate one for you

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks create --resource-group {} --name {} --kubernetes-version {} --location {} --node-vm-size {} --load-balancer-sku {} --api-server-authorized-ip-ranges {} --node-count {} --node-osdisk-size {}

Expected Behavior
Environment Summary
Linux-4.15.0-1077-azure-x86_64-with-debian-stretch-sid
Python 3.6.5

azure-cli 2.2.0 *

Additional Context

routing to appropriate team

The error message is accurate, you need an ssh key to exist on create to exist. As mentioned in the error you can pass a flag to have one generated on your behalf.

Closing this for now as the question was answered above.


Accessibility Audit - Carbon Website: What's happening - News & articles

This epic is tied to a larger "release" that is meant to track the progress of the Accessibility Audit for the Carbon Website. We will audit all of the pages of the carbon website based on AVT 1, AVT 2, & AVT3 - which can be found here.

AVT 1: will audit the site against the IBM Accessibility Checker - browser extension

AVT 2: will audit the site against accessible keyboard interactions

AVT 3: will audit the site against screen readers

Legend:

🌶 fully audited - on all three AVT levels

:one: 🔍 AVT 1 audited
:two: 🔍 AVT 2 audited
:three: 🔍 AVT 3 audited

:boom: issues and documentation - on all three AVT levels are complete

:one: 🚨 AVT 1 issues submitted
:two: 🚨 AVT 2 issues submitted
:three: 🚨 AVT 3 issues submitted

:sparkles: tickets are triaged

Current status of this page:

Contributing - What's happening - News & articles - 3 issues - 1 new issue found:

1⃣ 🔍 AVT 1 audited & 🚨 AVT 1 issues submitted

Closing due to inactivity. Will reopen if/when ready to be worked on again.


DEV: UPDATE (U) Fluids Report Object

EPIC:
#491  - Fluid Report Implementation
SIZE:
TBD pending 6/12 LOE review
DEV: UPDATE (U) Fluids Report Object

Update: Theresa has provided access to the object with the WitsmlObjectsLibrary. She will complete Update ETA 7/25

Update: UpdateToStore is now failing in getUUIDFR (throw new ValveException(“No fluids report date found.“);)
Requested a trace from Sukhe.

Update: UpdateToStore is now working. Will complete testing this morning with Shehzad and plan to release for Container 0.17.1 8/7.


Updated camerax

fixed https://github.com/JessYanCoding/InsGallery/issues/15
fixed without access in black layout in cameraview
There is no need to explicitly call CameraX.unbindAll() , since the UseCase is bound to a lifecycle and resources will be automatically freed when the lifecycle reaches the destroyed state. Also, Activity has no onDestroyView method, which is instead owned by Fragments. By the way, for Fragments the proper lifecycle to bind the UseCases to would be the viewLifecycleOwner ‘s lifecycle.

same issue,, not getting clear solution

After changing camerax_version & camerax_view  like this is working ..
        **camerax_view                  : "1.0.0-alpha10",
        camerax_version               : "1.0.0-beta03",**

After changing the camerax_version & camerax_view to @osama-alshanti mentioned versions, I'm having the following errors:

The @osama-alshanti mentioned versions take the File but the original library's versions take ImageCapture.OutputFileOptions. As for the library, I cloned it 2 days ago and using it directly in my existing app. I also added the 'ucrop' & 'picture_library' as modules. I'm updating the versions in the module gradle of 'picture_library'.

try @HaXxanParhar use like this mCameraView.takePicture(imageOutFile, ContextCompat.getMainExecutor(getContext()),


ClientSideInstance.xml missing while upgrading from 1.5.0 with cli 1.19.0

Hello,
While upgrading a solution from SPFX version 1.5.0 to 1.7.1 and finally to 1.8.2, there's no creation of the file sharepoint/assets/ClientSideInstance.xml, and if it's missing the custom action is not activated on the site after the package deployment.
if we're initializing a project in SPFX 1.8.2 the file is created.
Steps To Reproduce:

Create a Extension Project with SPFX 1.5.0
Upgrade it to 1.7.1
Upgrade it to 1.8.2

Thanks for your help.

Thank you for reporting the issue and the details. I'll try to repro it and will get back to you as soon as I know more.

You're right: the CLI doesn't suggest adding the file. The tricky part, and I believe the reason why we haven't added it initially, is that it would change the characteristic of your solution. Where originally it would not support tenant-wide deployment, after adding this file it would, without it being an explicit choice on your part.
I'm open for a discussion and arguments if you think this behavior should be changed 🙂

Hi @waldekmastykarz ( sorry for the delay ),
As per my understanding of the post https://github.com/SharePoint/sp-dev-docs/issues/3690 by @andrewconnell  the tenant-wide deployment is only triggered if we have the ClientSideInstance.xml file & the skipFeatureDeployment setting set to true.
So what about a suggest about adding the file only if the skipFeatureDeployment is set to true, with a warning on the effects on the project?

What if we added is an optional update step? So, the person upgrading the project can choose if they want to apply it or not?

It sounds better than my solution ;) as expected from you haha
Sent from My iPhone

De : Waldek Mastykarz<EMAIL_ADDRESS>Envoyé : Tuesday, May 21, 2019 7:23:51 PM
À : pnp/office365-cli
Cc : Pierre-Yves Bardy; Author
Objet : Re: [pnp/office365-cli] ClientSideInstance.xml missing while upgrading from 1.5.0 with cli 1.19.0 (#972)
What if we added is an optional update step? So, the person upgrading the project can choose if they want to apply it or not?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/pnp/office365-cli/issues/972?email_source=notifications&email_token=AAO35KLNAY77SUAEPLFICCTPWQV2PA5CNFSM4HNCL4WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4TKFI#issuecomment-494482709, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAO35KOCPSD6PONULXBAOK3PWQV2PANCNFSM4HNCL4WA.

It takes two to arrive to it. I would've never given it a thought if it wasn't for your comment 👏

Closing due to lack of activity


[W ParallelNative.cpp:229] Warning: Cannot set number of intraop threads after parallel work has started

When testing the CLI on macOS, it seems like the lungmask might hang yielding this warning:
[W ParallelNative.cpp:229] Warning: Cannot set number of intraop threads after parallel work has started or after set_num_threads call when using native parallel backend (function set_num_threads)

This does not seem to crash the run, but it for sure hangs the process for quite some time.

A simple workaround is basically to just add this before the CLI:
OMP_NUM_THREADS=1 lungtumormask

Only seems to be an issue with macOS on some Python/PyTorch versions:
https://stackoverflow.com/a/64855500/17883656


python code, autopep8 0.9.1 does not support --indent-size option

Description
autopep8 does not support --indent-size option
autopep8 version 0.9.1
Expected Results
Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
ERROR occurs

Debug
Here is a link to the debug.md Gist:
Checklist

[ ] I have tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] I have reloaded (or restarted) Atom to ensure it is not a caching issue
[x] Searched for existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Generated debugging information and added link for debug.md Gist to this issue

Hello, @Alienfeel.
I just had this exact problem too. I also had installed autopep8 0.9.1 from Linux Mint repositories. Then I found this StackOverflow question with the same error report. It simply suggests to remove the autopep8 package (in my case was python-autopep8) and install autopep8 with pip.
pip install autopep8

This installed autopep8 1.2.4 and it works flawlessly with atom-beautify.


FR: Provide unprivileged way of installing

I wish to install this onto a system where I don't have root permissions, and we already have an external PostgreSQL server so there is no need to install one.
I believe this should be manageable eg via systemd user units and default to running the services for zulip as the user which ran the script if it's not root.

While theoretically possible, there are a significant number of places where we assume the user has root permissions -- for instance, even just installing system packages like nginx.  You're correct that nothing would technically prevent Zulip Server from running unprivileged (for example, by downloading and installing our own nginx under ~zulip) -- but we already support that in the form of Docker containers or unprivileged LXC containers.  Supporting it directly on the host would be a significant effort, and most probably not worth it when containerized solutions already offer a reasonable alternative in the space.

containerized solutions already offer a reasonable alternative in the space.

Which unfortunately are not available in most situations where root permissions are not either.

I hear you that in most cases where you are entirely in userspace, you don't have any other options, and that's certainly frustrating.  However, and it would take significant re-architecting of our installation processes, and only affect an incredibly small potential user-base -- I don't want to give false hope by saying "we'll consider it" and leave this issue open.
My best suggestion to you is to ask the sysadmins to allow userspace LXC containers.  Barring that, you're welcome to use the hosted Zulip Cloud service, or you can switch to one of the many cloud server providers that do allow root access.

I hear you that in most cases where you are entirely in userspace, you don't have any other options, and that's certainly frustrating.  However, and it would take significant re-architecting of our installation processes, and only affect an incredibly small potential user-base -- I don't want to give false hope by saying "we'll consider it" and leave this issue open.

Could you please point out the puppet things that I would need to manually do if I cannot use the included installer (as it won't run at all unprivileged)? I think it would be beneficial to also include instructions/docs on how to manually install the app without the installer at all.

My best suggestion to you is to ask the sysadmins to allow userspace LXC containers.  Barring that, you're welcome to use the hosted Zulip Cloud service, or you can switch to one of the many cloud server providers that do allow root access.

LXC and grsecurity patches are more than likely not really compatible.

Could you please point out the puppet things that I would need to manually do if I cannot use the included installer (as it won't run at all unprivileged)?

scripts/lib/install is the place to start -- it installs several system packages, and then applies puppet/zulip/manifests/profile/standalone.pp.  You can follow the includes from there.

I think it would be beneficial to also include instructions/docs on how to manually install the app without the installer at all as currently all of the docs seems to expect that one can use the installer.

The list of steps is long, would become rapidly out of date, and would be difficult to support.  All of the docs expect that one can use the installer because that's the only configuration we support.
I understand the constraints that you're operating under, and why you're asking for what you are -- but the use case is too uncommon for us to support.  It's like looking at a house and asking for documentation on how to make it float -- I can see why it would be a nice feature (and in some cases it might be the only option available!), and it's potentially possible, but it's really not been designed for it, and we don't have the capability to make the required changes.


Notify "when all invoked services are done"

Is there a way to wait till all invoked services have reached their final state before moving on to the next state?
In the example below I'd like all childMachines be in their final state before moving on to the success state. Putting target: "success" into the onDone configuration doesn't do the job as the first response will move to success ignoring all other responses that are still in flight.
states: {
    pending: {
      invoke: [
        {
          id: "topTenProjects",
          src: topTenProjects,
          onDone: {
            // target: "success",
            actions: assign((ctx, event) =>
              produce(ctx, draft => {
                draft.topTenProjects = event.data
              })
            )
          }
        },
        {
          id: "fundingTypes",
          src: fundingTypes,
          onDone: {
            // target: "success",
            actions: assign((ctx, event) =>
              produce(ctx, draft => {
                draft.fundingTypes = event.data
              })
            )
          }
        }
      ]
    },
    success: {}
  }

Originally posted by @RainerAtSpirit in https://github.com/davidkpiano/xstate/issues/321#issuecomment-461802330

Copying the reply here:
I haven't seen anything in SCXML that would notify "when all invoked services are done" although you can accomplish this with "when all parallel states are done" - xstate.js.org/docs/guides/final.html#parallel-states
That might be a bit verbose, but it's for good reason - parallel states can have invoked services on each of them, but they can also be normal states without invoked services.
You can create a helper function that cuts down on the extra config, something like:
states: {
  pending: {
    ...parallelServices(svc1, svc2, svc3),
    onDone: { /* ... */ }
  }
}

I was able to implement that feature in userland by adding an invokeCount and a transient transition.
Would it be possible that xstate support this scenario OOTB?
export const serviceMachine = Machine<
  IServiceMachineContext,
  IServiceMachineSchema,
  EventObject
>({
  id: "serviceMachine",
  initial: "pending",
  context: {
    invokeCount: 0,
    topTenProjects: undefined,
    fundingTypes: undefined
  },
  states: {
    pending: {
      on: {
        "": [
          {
            target: "final",
           cond: (ctx, event) => ctx.invokeCount === 2
          }
        ]
      },
      invoke: [
        {
          id: "topTenProjects",
          src: topTenProjects,
          onDone: {
            actions: assign((ctx, event) =>
              produce(ctx, draft => {
                draft.topTenProjects = event.data
                draft.invokeCount = ctx.invokeCount + 1
              })
            )
          }
        },
        {
          id: "fundingTypes",
          src: fundingTypes,
          onDone: {
            actions: assign((ctx, event) =>
              produce(ctx, draft => {
                draft.fundingTypes = event.data
                draft.invokeCount = ctx.invokeCount + 1
              })
            )
          }
        }
      ]
    },
    final: {}
  }
})

Would it be possible that xstate support this scenario OOTB?

As much as I'd love to, every single API design decision must be fully 1-1 compatible with SCXML: https://www.w3.org/TR/scxml/ . Remember: XState is nothing new invented.
I would tackle this a different way:
pending: {
  invoke: {
    src: (ctx, event) => Promise.all([
      /* all services */
    ]),
    onDone: 'final'
  }
}

Sounds fair. Thanks for sharing a different approach.

After reading up a bit on invoke your suggestion of using parallel machines with a single invoke per state is favorable to any "workarounds" to make invoke arrays  work the way I'd expect them to work.
@davidkpiano Would it make sense to add that limitation the invoke array documentation?
For sake of completeness here's the above refactored example.
export const serviceMachine = Machine<
  IServiceMachineContext,
  IServiceMachineSchema,
  EventObject
>(
  {
    id: "serviceMachine",
    initial: "pending",
    context: {
      topTenProjects: undefined,
      fundingTypes: undefined
    },
    states: {
      pending: {
        type: "parallel",
        states: {
          topTenProjects: {
            initial: "loading",
            states: {
              loading: {
                invoke: {
                  src: "topTenProjects",
                  onDone: {
                    target: "done",
                    actions: assign((ctx: IServiceMachineContext, event) =>
                      produce(ctx, draft => {
                        draft.topTenProjects = event.data
                      })
                    )
                  }
                }
              },
              done: {
                type: "final"
              }
            }
          },
          fundingTypes: {
            initial: "loading",
            states: {
              loading: {
                invoke: {
                  src: "fundingTypes",
                  onDone: {
                    target: "done",
                    actions: assign((ctx: IServiceMachineContext, event) =>
                      produce(ctx, draft => {
                        draft.fundingTypes = event.data
                      })
                    )
                  }
                }
              },
              done: {
                type: "final"
              }
            }
          }
        },
        onDone: {
          target: "final"
        }
      },
      final: {}
    }
  },
  {
    services: {
      topTenProjects,
      fundingTypes
    }
  }
)

Would it be possible that xstate support this scenario OOTB?

As much as I'd love to, every single API design decision must be fully 1-1 compatible with SCXML: https://www.w3.org/TR/scxml/ . Remember: XState is nothing new invented.
I would tackle this a different way:
pending: {
  invoke: {
    src: (ctx, event) => Promise.all([
      /* all services */
    ]),
    onDone: 'final'
  }
}

How would you parameterise those promises? Imagine I have parameterised fetchUser and fetchData e.g.. Now I want to use those in a Promise.all. Is that possible?

Combinators (like Promise.all) are not supported out of the box - you'd need to handle that yourself, for example by just externalizing your promises and calling to them directly.


TextInput rendering two characters per keystroke

Hey I'm having an issue with text inputs where they get two characters printed per key stroke, this is also reproducible on the _examples/demo did some debugging and modifying the textinput.go
func (t *TextInput) doInsert(c []rune) {
	s := string(insertChars([]rune(t.InputText), c, t.cursorPosition))
	time.Sleep(50 * time.Millisecond)
	if t.validationFunc != nil {
		result, replacement := t.validationFunc(s)
		if !result {
			if replacement != nil {
				s = *replacement
			} else {
				return
			}
		}
	}

	t.InputText = s
	t.cursorPosition += len(c)
}

Seems to fix this, although this does not feel like the real fix.

This should be resolved now. Please let me know if you see any other issues!


'docker compose' to 'docker-compose'

fix typo (doesn't typically affect github actions b/c the runner doesn't have any pre-existing containers running)
Signed-off-by: Bob Callaway<EMAIL_ADDRESS>

Codecov Report

Merging #1009 (1cda94c) into main (4923f60) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1009      +/-   ##
==========================================
- Coverage   40.94%   40.90%   -0.05%
==========================================
  Files          69       69
  Lines        6496     6527      +31
==========================================
+ Hits         2660     2670      +10
- Misses       3554     3575      +21
  Partials      282      282

Impacted Files
Coverage Δ

pkg/types/entries.go
5.08% <0.00%> (-1.17%)
:arrow_down:

pkg/api/entries.go
0.00% <0.00%> (ø)

pkg/types/types.go
0.00% <0.00%> (ø)

cmd/rekor-cli/app/pflag_groups.go
89.47% <0.00%> (+2.27%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Updating cacheControl property with Azure CLI is outdated

The Azure CLI command stated to update the cacheControl is outdated and does not work for new CLI
azure storage blob upload -c <connectionstring> -p cacheControl="max-age=3600" .\<blob name> <container name> <blob name>
This is not in the AZ CLI.
The Az CLI equivalent would be
az storage blob upload etc with added parameter --content-cache "max-age=3600"
Using the combination of -p cacheControl="max-age=3600" will generate an error for an unrecognized parameter.

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

ID: e745eb82-ea12-5135-31f8-7f5a88882560
Version Independent ID: 68496c81-5048-fb2b-645f-ead02aa2fbf6
Content: Manage expiration of Azure Blob storage - Azure Content Delivery Network
Content Source: articles/cdn/cdn-manage-expiration-of-blob-content.md
Service: azure-cdn
GitHub Login: @zhangmanling
Microsoft Alias: mazha

Hello @wkoeter
Thank you for your feedback! We will review and update as appropriate.

Hello @wkoeter, Thank you for your feedback. I have made a PR to address this issue which is currently under doc author's review. I have modified the command as follows.
az storage blob upload --connection-string <connection-string> --content-cache max-age=3600 --container-name <container-name> --name <blob-name> --file </path/to/file>
You can go through this documentation for additional details.
We will now proceed to close this issue out. Please tag me in your response if you have any additional questions. Thank you!


Update SQLite ERD to show posture checks table

This reflects changes added in https://github.com/netbirdio/netbird/pull/1540

Should be merged after https://github.com/netbirdio/docs/pull/145


Define ODO user/scope && few questions

I have few questions:

who is odo user ?
does he know openshift in advance ?
does he care about yamls in openshift ?

who is superuser ?
will superuser use odo ?

do we need to consider that user will use both oc and odo ?
for greater user experience, do we need to draw some line between what we will provide and what not ? (just had a fear that, eventually odo should not become oc again )

I was thinking this way:

if you are ops, use oc
if you are noob/dev, use odo
Am I correct here ?

cc @kadel @cmoulliard @sspeiche

Some of the questions also from the discussion in :
https://github.com/redhat-developer/odo/pull/626#discussion_r215315130
may be relevant to this

Here are my answers, which can differ from @sspeiche

who is odo user ?

A developer that is not (nor want/need to be) familiar with OpenShift and kubernetes but needs to create applications using this platform

does he know openshift in advance ?

Don't need to, and the ideal user is the one not really experienced with OpenShift

does he care about yamls in openshift ?

For sure not

who is superuser ?

What is a superuser?

will superuser use odo ?

Since I don't know what you mean by superuser, can't answer

do we need to consider that user will use both oc and odo ?

Ideally, our users would only use `odo, but there will be many users, those familiar with OpenShift that for convenience might use both

for greater user experience, do we need to draw some line between what we will provide and what not ? (just had a fear that, eventually odo should not become oc again )

Hopefully, when oc will be implemented as plugins, we should consider doing same/similar so we can use same plugins or embed/vendor their code into our own plugin. Think that there will be differences in our commands, order, options, etc... for many things, but for others they could be just drop in (or almost). This is one of the reasons I introduced the plugin mechanism the openshift guys are thinking so that we can start trying to align the sooner the better.

I was thinking this way:
if you are ops, use oc
if you are noob/dev, use odo
Am I correct here ?

Basically yes, and there will be some that will use any interchangeably. Again, we need to start R&D about the plugin mechanism in kubectl/openshift and when we will be able to pick it up and how.

@lalatendum, can you please elaborate on superuser ?

Here are my answers, which can differ from @sspeiche

who is odo user ?

A developer that is not (nor want/need to be) familiar with OpenShift and kubernetes but needs to create applications using this platform

Agree. There are many kinds of developers. odo is focused on developers who just want to use typical concepts and flows they would expect from a "PaaS"-like platform. Abstract away some of the complexities of the platform and get out of my way to get my development done.

does he know openshift in advance ?

Don't need to, and the ideal user is the one not really experienced with OpenShift

Another way of saying it, we should not require any knowledge of OpenShift prior to using odo, other than it is a thing, you need connection info and go.

does he care about yamls in openshift ?

For sure not
Agree, should only care for certain advanced use cases.

who is superuser ?

What is a superuser?
I assume you mean "cluster-admin" or someone who really knows OpenShift. This tool isn't designed for them but if they find it useful to do their job, by all means, go for it.

will superuser use odo ?

Since I don't know what you mean by superuser, can't answer

do we need to consider that user will use both oc and odo ?

Ideally, our users would only use odo, but there will be many users, those familiar with OpenShift that for convenience might use both
Another way I look at it, odo will hit a certain number of use cases and when it comes down to some of the advanced or not covered ones, the user may need to drop and do things like oc and YAML.

for greater user experience, do we need to draw some line between what we will provide and what not ? (just had a fear that, eventually odo should not become oc again )

Hopefully, when oc will be implemented as plugins, we should consider doing same/similar so we can use same plugins or embed/vendor their code into our own plugin. Think that there will be differences in our commands, order, options, etc... for many things, but for others they could be just drop in (or almost). This is one of the reasons I introduced the plugin mechanism the openshift guys are thinking so that we can start trying to align the sooner the better.

There will be some overlap but we need to be clear and deliberate. We don't want to invest >1 time in a piece of code for Red Hat and the community to have to maintain. Based on the new plugin work in 1.12, kubectl is providing some libraries for plugins others to make it easier to use in their CLIs since they will need to be go binaries and may need to reimplement many of the same things. oc should follow that same approach and odo should leverage it.
There may become a day where odo could be a plugin to oc and you could do something like oc do or whatever, though odo would need to mature some but it is good to work with this in mind.

I was thinking this way:
if you are ops, use oc
if you are noob/dev, use odo
Am I correct here ?

Basically yes, and there will be some that will use any interchangeably. Again, we need to start R&D about the plugin mechanism in kubectl/openshift and when we will be able to pick it up and how.

I think this is a good way at looking at it. I would say even reword slightly...

if you are a dev, whether noob or just want to focus on dev, use odo

Good set of questions, thanks

thanks @jorgemoralespou  and @sspeiche for answers :smile:

Could we close this @surajnarwade :100:

Closing this issue since I got my answers :tada:


Checkout should have transaction time stored

Right now we do not store the transaction time at the time of writing to checkout database.
This is a important data point and should be added.

add a field created_at for transaction

Already implemented here: https://github.com/bee-travels/bee-travels-node/blob/master/services/checkout-v2/src/services/postgresService.js#L13


Enabling Email Notification in Password Expiry Feature requires IS Analytics

Describe the issue:
In order to enable Sending Email Notification functionality in Password Expiry feature requires to install and run IS Analytics alongside WSO2 IS. This seems like an extra mile taken for users who are only using WSO2 IS as the product. As a result, these users would not be able to make use of the Email Notification functionality if they do not wish to maintain another product as well.
Expected behavior:
Email Sending Notification should be available in the WSO2 IS without the need to install and run another entirely different product.
Environment information:

Product Version:  IS versions 5.6.0 and above

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Support for 4.17?

Is there support for UE4.17?

Nothing that works out of the box as of right now.
I've been neglecting this repository for quite a while now, but I've been trying to find the time to wrap up the modern rewrite (fork found here: https://github.com/getnamo/myo-ue4/compare/hub-packaging-fixes). Whenever that gets done it will get a 4.17 or newer release.
Otherwise you can try to take the current master repository and recompile it for 4.17, there will likely be some compiles fixes due to UE api changes, but they shouldn't be too daunting.

4.18 is now supported in the early modern rewrite release merge here: https://github.com/getnamo/myo-ue4/commit/6d1d87c29c3236ac320060da8ed88180a41c8ff6. Grab the latest release here: https://github.com/getnamo/myo-ue4/releases


Throw exception in function doesn't enterrupt execution

/* @flow */

function throwException() {
	throw new Error('Invalid number passed');
}

function getIdentifier(id: number) {
  if (id === 1) return 'one';
  if (id === 2) return 'two';

  throwException();
}

function getValue(id: number) {
  const str: string = getIdentifier(id);

  // some logic
}

This snippet cause of error in flow, but I expect that exception in function getIdentifier should interrupt execution of function getValue before assignment.
This example in sandbox

Just throw the error in the getIdentifier function instead of in a separate function. Try in the sandbox.

Yes, it's great! Thank you! But why exception in called function doesn't
interrupt execution. This fact is my trouble, but not exactly this snippet.
On Wed, Dec 20, 2017, 21:30 Wyatt Cready<EMAIL_ADDRESS>wrote:

Just throw the error in the getIdentifier function instead of in a
separate function. Try in the sandbox.
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVUCuA7AxgFwEs5swBzAU3wEkATC7IqQigJwApDaAuMbTALYAjNgEowAb1RgwhKGE60wAXlVgAjONZVMrUgHISFfQG5ps+YpVqATFp16w+-Ajinz5-AAtWiPhSQAUVZfDn1qbAA3AEMYLll6bAYmFlYwAAdogGcsilp9UTMAX3QsPCIScioANVjMCkVefmExSXNcEiz8MC7WXl7CbDIVKppElLZFQo8ZYGAeuAEKMHgyQlxUIqA
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/flow/issues/5540#issuecomment-353144860, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACXaUdXOzZKib0yR7G89qtXNJ2MsIv_qks5tCVIxgaJpZM4RIIf9
.

--
С Уважением,
Best regards,
Александр Шоронов
Aleksandr Shoronov
моб. тел / mobile: +7 (967) 596-49-93
skype: alexshoronov
telegram: t.me/underoot

Because flow doesn't keep track of which functions will throw an error. There's no syntax to do so either. The only thing flow really knows is that getIdentifier calls the function throwException, but all it knows about that function is that it takes no parameters and implicitly returns void. With just that amount of information it decides that your getIdentifier function is returning string | void.

@jcready Thanks for explanation.


Nova

[x] Kiosk URL generation (?door=blah&token=asdf)
[x] Some form of visit metrics/reporting

Nova is in a good enough place now to close this.


Remove .DS_Store

Remove unneeded files like .DS_Store. Possibly node_modules as well.

I think this is related to https://github.com/sdras/project-explorer/issues/8
Is there any case in which we need to cover .gitignore files?

Yeah, I think we would read what's in .gitignore and then exclude them. I can probably make a small PR that removes .DS_Store and node_modules very quickly. The .gitignore idea might take a bit longer because if it takes some time to run and has to do error handling we might also need a loader. But it would be much more elegant so I think that's what we should do eventually.

This is now done! See https://github.com/sdras/project-explorer/issues/8 for more info 🎉


Password confirmation does not confirm password

Ignoring the fact that password validation errors (e.g password too short) errors are not shown at all (probably related to https://github.com/keystonejs/keystone-5/issues/433).
The confirm password field does not actually confirm anything.
Reproduction steps:

Enter a password password
Enter a confirmation password foo
Save (and watch it succeed)

Can't reproduce this one either. 🤔


fix(response submit page): remove expired form, encourage pull request

Fixes

Fixes #85 by @nown1ne
Description

I replace the expired Google Form link with the project GitHub link to encourage pull requests, according to the will of the original developer.
Screenshots

The broken response submit page is as below.

The problem is that the original Google Form has expired.

With the help of the Wayback Machine, I get to know that the developer has long suggested not to use the form but to make pull requests instead. The original form isn't useful anymore.

Hence, I remove the link to the Google Form and encourage pull requests from anyone who needs to submit a resource.

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@itsyuxuan This is a good catch and approach, but it is not entirely covered by #85. I think what you've outlined here is certainly broader than that Issue, even if related.
I'd suggest you open an Issue for this with a lot of this information above, and wait for it to go through the Contribution pipeline, outlined in the Contribution Guidelines prior to submitting a PR.
Closing this for now, until it's went through an Issue fully.


Native editor scroll bar too small to use [II]

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
It does not seem possible to resize the scrollbar of the jupyter editor.
I have tried the following settings:
    "editor.scrollbar.horizontalScrollbarSize": 64,
    "editor.scrollbar.verticalScrollbarSize": 64,
    "editor.scrollbar.vertical": "visible",
    "notebook.editorOptionsCustomizations": {
        "editor.scrollbar.horizontalScrollbarSize": 64,
        "editor.scrollbar.verticalScrollbarSize": 64,
    },

And this is the outcome:

regular editor
.ipynb editor

This was reported in #2373, but I do not see the settings being respected in the current version (Version: 1.85.2).
Thanks.
VS Code Version
Version: 1.85.2 (Universal) Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681 Date: 2024-01-18T06:40:32.531Z (2 wks ago) Electron: 25.9.7 ElectronBuildId: 26354273 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: <IP_ADDRESS>-electron.0 OS: Darwin arm64 23.3.0
Jupyter Extension Version
v2023.11.1100101639
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None

i have the same problem
anyone know how to solve this?

I'm also having this issue


cmake: build all executables

My attempt of enabling CMake to build all executables.
I am far from a CMake expert. I tried to make it as explicit and simple as possible to read/follow.
Only tiny_bvh_test is actually run, but this should greatly increase the chance of catching build-breaking changes on CI.

Thanks! Looks good to me, not an expert either. :)


With a large config, the configuration diff when selecting "Mark as Ignored" is blank

We are using a large config.yaml file for Artemis.  It has over 12K lines.  When we view an alert and select "Mark as Ignored" the "Configuration diff (Learn new rule" window that comes up is blank.  See screenshot.

Could you please clarify what type of alert are you using to learn? E.g., 'E|0|...'. Also please check if there are updates associated with it in the underlying table.

Also I assume that this is related to the renderer on the frontend (the backend does not have issues handling such configs), have you tried adding the rule and checking the diff post-change in the config comparison section?

The alert type is E|1|-|-
There are numerous "Related BGP Updates" at the bottom of the page for these alerts.
I do not see the post-change config being updated.

OK. I will try to replicate in current frontend and will notify also when a new react-based frontend that is currently under work and in the integration stage is in for further testing. Will need to find out if it is a renderer or a backend issue or a combination of both.

Replicated locally. Seems to be not a renderer issue but a problem with the configuration microservice timeout due to the size of the config (it takes time to respond and in the meanwhile the JS library times out).  Since this is related to the general way we handle the config file in the on-premise setup, and we will do a total revamping of this for speed and scale, I will add it to the enterprise SaaS requirements we are working on for collecting and managing the BGP data needed to keep ARTEMIS ground truth correct and up-to-date (incl. learning from hijack events and from other sources, like the local network).

leaving open since it also applies to the new frontend. Will be solved in a SaaS version due to the scale of the config file.


Change in 'include' syntax in new ejs

Syntax for include snippet has changed from <% include ./partials/footer.ejs %> to <%- include('partials/footer.ejs') %>
https://stackoverflow.com/questions/59045136/syntaxerror-unexpected-token-while-compiling-ejs-happening-in-include

Hi,
I was about to raise an issue about this myself when i found this issue, after checking out the code i was able to find the right place to make the change and submit it as a pull request.
If someone really needs it, take a look at the pull request (2 lines of code) and make the change in your local extension version, after relaunching vscode it should work.

This was always valid syntax in EJS 2.x.
It's just that the legacy EJS 1.x syntax was removed in EJS 3.0.

Couldn't we sync this ejs-grammer release with ejs release ? What i am suggesting is that, can we release new major version synced with ejs 3.0 ? and mention which ejs-grammer major semver is for which ejs version.
-------------------------
| ejs-grammer     | ejs |
-------------------------
| 1.x.x           | 1.0 |
-------------------------
| 1.x.x           | 2.0 |
-------------------------
| 2.x.x           | 3.0 |
-------------------------