Add rune name to decode command

Currently, ord decode --txid <txhash> command returns this:
  "inscriptions": [],
  "runestone": {
    "Runestone": {
      "edicts": [],
      "etching": null,
      "mint": "189685:18",
      "pointer": null
    }
  }
}

Mint param should also give rune name.

yes, that would be good to add. Great first issue ;)

Currently, ord decode --txid <txhash> command returns this:
  "inscriptions": [],
  "runestone": {
    "Runestone": {
      "edicts": [],
      "etching": null,
      "mint": "189685:18",
      "pointer": null
    }
  }
}

Mint param should also give rune name.

@raphjaph does this mean that the mint prop should not only contain the RuneId but also SpacedRune? Just confirming before giving this a go. Something like:
"mint": ["189685:18", "MY•RUNE"]

Just thinking about this again and I think we should not add it. The ord list command runs stateless, meaning you don't need a synced index, only a Bitcoin Core node. We just parse out exactly the information that is contained in a tx, we don't apply state to it. Since only the RuneId is in a mint transaction, getting the rune name would mean making a request to the database.


login race, on password protected server.

Hi,
We have some servers up on premium v1.7.4, with password for race login configured ad server side.
On Content Manager works fine.
On AC game you can join to server with no password configured.
To Reproduce
Steps to reproduce the behavior:

try login to GTRSpain 1,2 or 3 (works "fine") on cm seems to be password protected
No password = no login permited
No correcte password = no login permited

Try to login with AC game (not CM).  You can login race with no password.

Expected behavior
A  expected to have a password protected server on all login cases.
Sounds very crazy, but maybe no one tryes to login directly with Assetto original game.
thanks in advance,
Xavi.

created by error (duplicate)


proxy_set_header X-Forwarded-Host in advance configuration doesn't take effect

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?

Yes

Are you sure you're not using someone else's docker image?

Yes

Have you searched for similar issues (both open and closed)?

Yes

Describe the bug

I found that if I put
proxy_set_header X-Forwarded-Host $http_host
in my advance config it doesn't take effect. After looking at the saved config file I found that the statement is put outside of the location block. If I manually move the statement into location block it works fine.
I also checked Custom Nginx Configurations section in the documentation, it seems that there is no option to let me customize inside location block.

Nginx Proxy Manager Version

2.9.9
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Operating System

Additional context

Yeah, that's how the advanced config works. I think there is some weird behavior in nginx where it doesn't apply any headers from outside the location block if there is even a single header set inside the location block. However you should be able to add a custom location / where you can duplicate the stuff you need and add your custom header.

Yes you are right. I can add custom locate / in the settings and it works fine.

Would you mind letting me know how to do it?
I want to access it at / and putting the lines at with that in mind, forwarded to the same ip and the parent proxy host does not solve the problem for me. Can I see what you did?

Yes you are right. I can add custom locate / in the settings and it works fine.

Would you mind letting me know how to do it?
I want to access it at / and putting the lines at with that in mind, forwarded to the same ip and the parent proxy host does not solve the problem for me. Can I see what you did?

Here is how I did it:

Yes you are right. I can add custom locate / in the settings and it works fine.

Would you mind letting me know how to do it?
I want to access it at / and putting the lines at with that in mind, forwarded to the same ip and the parent proxy host does not solve the problem for me. Can I see what you did?

Here is how I did it:

Thank you, but apparently, my apps worked without needing to insert these but only enabling websocket. Not a professional so don't know the difference except a few lines being added. But if I do need some custom lines I will be sure to add them that way in the future.
Thank you so much!


Use of undeclared type 'PhotoEditorViewController'

let vc = self.storyboard?.instantiateViewController(identifier: "PhotoEditorViewController") as PhotoEditorViewController
given error  Use of undeclared type 'PhotoEditorViewController'

@Ali-Aqdas
This is how you do it
 let photoEditor = PhotoEditorViewController(nibName:"PhotoEditorViewController",bundle: Bundle(for: PhotoEditorViewController.self))
Please check the example provided for more details

i did it but it was not working same issue was showing

given error Use of undeclared type 'PhotoEditorViewController'

Did you import iOSPhotoEditor


Improve c-ares & curl build process

This commit improves the c-ares and curl build process to use cmake instead. This is a much better choice for docker container. We do not require the features GNU Make provides. CMake should also be faster and more stable for testing pull requests.
It also upgrades the c-ares and curl version to receive the latest bug fixes and performance changes. There's been a huge leap forward since the older changes. Put simple, curl 8 is faster.

I will reopen this pull request. Going to attempt to fix the build jobs first.


[CODE] Need multiple CSS in JS formats

Description
With more applications using the design tokens it has become apparent that the CSS in JS format will not be suitable for both web and mobile applications. At the moment the CSS in JS format only caters for the react native implementations.
e.g typography uses static numbers for font size and line height rather than rems or unitless multiplier values.
// Currently

typography.sDisplayMD.fontSize = fontSizes.fontSize7 = 32
typography.sDisplayMd.lineHeight = lineHeights.lineHeight6 = 40

If we were to use the above tokens in a web application we wouldn't have any accessibility benefits and the line height would not be calculated properly

Some additional formatting is needed to make it display as intended

This is not a great developer experience. We should provide formats appropriate for both react native and react web
Maybe we can move the tokes into folders
import { colors } from '@metamask/design-tokens/web';
import { colors } from '@metamask/design-tokens/mobile';
Technical Details

Come up with a way to import CSS in JS format more appropriate for web

Acceptance Criteria

Be able to import CSS in JS tokens specific for web
Be able to import CSS in JS tokens specific for mobile

References

TBC

Maybe @metamask/design-tokens/react-native and @metamask/design-tokens/react? for js tokens 🤷


Adds multi-module example.

For #540
Depends on #735 to replace a TODO.
Preview at https://github.com/GoogleContainerTools/jib/tree/multimodule-example/examples
A lot of the code is just the wrappers, so when reviewing just skip over those.

It seems to me that some people are also having issues with this if they include a maven library from the same project that they don't want containerized?
for example
.
├── pom.xml (parent/root)
├── container1
│   └── pom.xml
├── container2
│   └── pom.xml
└── non-container-shared-lib
    └── pom.xml

We should cover this case as well either in this PR or a followup.

@loosebazooka Would that non-containerized library be just a pom packaging?

@coollog, it would be a jar of some kind, a common library pulled in to both container1 and container2. The more I look at maven multi module stuff though, the less I like how it is done, since it appears you still need to specify dependency (lib) in all other modules that use it, just as you would any other dependency. It kinda feels like it's just doing an mvn install for you but making every else WAY harder. Maybe, just file the library addition to the example low priority and we can deal with it later.

Added the common library example to #540 as low-priority. This should be good to finalize/merge now.

Furthering the non-pom non-jib module point:
.
├── pom.xml (parent/root)
├── container1
│   └── pom.xml
├── container2
│   └── pom.xml
└── non-container-shared-lib
    └── pom.xml

In this case, we don't want to deploy non-container-shared-jib. Now I'm not sure what exactly happens here when we run mvn compile jib:build and jib-maven-plugin isn't applied on non-container-shared-lib, but I think the user has to do something like
$ mvn compile && mvn jib:build -pl container1,container2

to avoid the maven reactor plugin from throwing an error about jib not being found on non-container-shared-lib.
Although if the user is truly sharing this library in container1 or container2, then non-container-shared-lib needs to be installed, so it might even look like
$ mvn compile && mvn install -pl non-container-shared-lib && mvn jib:build -pl container1,container2

but there's also all this -am (also make), I'm not sure what lifecycle goals that runs.
I think I'm rambling a little here, lets just go with the simple example you have and we can update it as we get questions.


rework structure

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


blurry text with translate3d

using translate3d we can see blurry on text whereas there is no problem with translate. See on Chrome

a get around is using property use-css-transforms="false" . it disable the transform:translate3d


I would like to have a map widget with address input

Is your feature request related to a problem? Please describe.
Right now the map input widget is great but it requires the user to zoom into and pick the location based on topographical knowlege. Itwould be great if there was an inputfield with geocoding to translate that address to a point on the map. That way we could use the map still for finetuning the exact position but it would be much easier and faster to input address location. This is how for example ACF does it in wordpress
Describe the solution you'd like
Add an address field to the map widget that uses geocoding to determine the ppin position in the displayed map.
Describe alternatives you've considered
Alternatively you could say just use a text field for the address and parse it in your application, but that makes it vulnerable to errors. Also less precise.
Additional context
I am building a map wth locations in a city and it is very cumbersome to have the client put in an address and a GeoPoint using the map widget.

Maybe you can use this;
https://www.npmjs.com/package/netlify-cms-widget-gmaps

Maybe you can use this;
https://www.npmjs.com/package/netlify-cms-widget-gmaps

Cool! but it does no tseem to work out of the box.
Applicable Versions:

Netlify CMS version<EMAIL_ADDRESS>Git provider: test-repo
Browser version: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

ReferenceError: google is not defined at i.value (https://unpkg.com/netlify-cms-widget-gmaps@%5E1.0.0:2:267771) at Fa (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:69876) at Na (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:69671) at gs (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:105470) at ul (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:96717) at sl (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:96642) at Js (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:93672) at https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:45314 at t.unstable_runWithPriority (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:196:3844) at qi (https://unpkg.com/netlify-cms@%5E2.0.0/dist/netlify-cms.js:188:45023)

@koraysels so because this uses react-google-maps, the docs for that say at step-3:
https://tomchentw.github.io/react-google-maps/

If you don't use withScriptjs, you have to put a  tag for Google Maps JavaScript API v3 in your HTML's  element

example https://codesandbox.io/s/2xyw6n4o9y (probably need to update with your own valid api key)

Closing as stale


⚠ ESPN has degraded performance

In 2b6f43c, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 927 ms

Resolved: ESPN performance has improved in 1021990.


Keyboard overlaps on webview in android

I am using this plugin. In ios it is working fine but in android keyboard overlaps on webview content. Webview contains inputbox at bottom of the screen like chat window. After clicking on input box keyboard coming on webview.

Hi, I m facing the same issue, but not in react native, I m testing my web app on different devices using browserstack, and on android devices, when i use to add comment, keyboard overlaps the text field, How can I fix this issue in react js

Hello @abdurrehmaan
you can add keyboardVerticalOffset={20} prop in KeyboardAvoidingView
That will fix your problem

Getting similar issue

I see different behavior of webview on different devices, for some devices content goes behind the keyboard, and for some content goes on top of the keyboard. so adding KeyboardAvoidingView fix it for some devices but make a problem for other devices that already pushed the content up

I used KeyboardAvoidingView but added a container inside with the following styles:
`<KeyboardAvoidingView
behavior={Platform.OS == "ios" ? "padding" : "height"}
style={{ flex: 1 }}

const styles = StyleSheet.create({ contenedorView: { justifyContent: "flex-start", position: "relative", flex: 1,},

if using expo. put this inside your app.config.ts
android: {
    softwareKeyboardLayoutMode: "pan"
}

not exactly sure if it's "pan" or "resize". you can try them
it's a good practice to always set this value, otherwise, different Android devices will behave differently.
some render content behind the keyboard and some on top


Fixed the validation for a Form Builder Phone Field

The errorText was not propagating to the decoration
The country code is only prepended when a phone number is specified so that the value is empty when there is no phone number specified
Other minor tweaks

@awhitford : I feel like we would need a few additional improvements to really make this PR successful. I didn't implement this FormBuilder widget so I'm just now inspecting the code and testing it. As I understand, _parsePhone is only called during initState and the other critical function, _invokechange, is only called during initState and _openCountryPickerDialog but not as the user types nor when the user commits their input. I think this could be better improved to follow user conventions.
Rather than handle a simple string, I think we need to use a special Phonenumber object that encapsulates, the raw input, the country code used, the parsed E.164 result, and possibly the validated status and the local formatted result if available, basically the full output of Phonenumber.parse. This would give developers added flexibility in handling both the user's raw input and parsed result simultaneously. Also, think we should have this called in such a way to support parsing as we type and accept input, which I think is natural for the user.

@VOIDCRUSHER I agree that there is room for further improvement.  However, this patch simply does the minimum to enable phone validation which is currently completely broken and thus preventing its use.  This PR will at least fix it so that rudimentary validation works.

I understand. Can we have it at least so that it allows for validation/parsing on text input as well? It seems like a big blind spot if that important process only happens when the widget initializes and when the country code is changed.

I appreciate the good work @awhitford.
@VOIDCRUSHER, kindly note that this input was included through a PR by a community member who implemented the field as they saw fit.
Since your suggestions will lead to breaking changes, I'd suggest that we merge this in - since it contains fixes for some valid concerns as it were - and create a separate PR for the suggested improvements.

I understand. Can we have it at least so that it allows for validation/parsing on text input as well? It seems like a big blind spot if that important process only happens when the widget initializes and when the country code is changed.

I see the point for this. However, when I was implementing this, the main aim of using the phone_number package was to parse the initialValue and separate the country code from the phone to fit our input.
I'm not an expert when it comes to validation and formatting of international phone numbers. When I was researching this, I also found that these general validation libraries may be wrong in some instances, and for these reasons I decided to just utilize the parsing functionality and leave validation to the user.

I would prefer to use this Phone Field instead of a Text Field, but the broken validation prevents me.  I'm anxious to see this fix merged.
I'm open to revisiting this with more improvements, but I prefer to work in small incremental changes.  I too would like to see the input parsed while typing so that it is visually separated, consistent with the country, and I really need E164 formats as values.  I will need more time to play around with this, but the current version with the validation fix gives me something that will function well enough.  "Don't let perfect be the enemy of good."

Thank you!


Does not appear in Settings

I'm on Ventura 13.1 (22C65) and I can't seem to enable the accessibility permissions. I restarted both settings and the menu app multiple times, but Squirrel doesn't appear in the list.

Have you tried using the + button to add Squirrel in manually?


Python 3.9.9 released

https://www.python.org/downloads/release/python-399/

The commit's in there https://github.com/docker-library/python/commit/3d43bcf8ddd26ae85fd6a63a7e1d502b445c9cce
Just waiting for a PR to push it to Dockerhub https://github.com/docker-library/python#see-a-change-merged-here-that-doesnt-show-up-on-docker-hub-yet

Awesome! Thanks


Send the stacktrace in the message

Added the option to send the stacktrace in the message that is not an exception.

Thanks but I am not sure this is the best idea to have a stacktrace context changing the mode of operation of the handler. The best is to log exception as  ['exception' => $e] in the context info to get stack traces.


Add support for postgresql.

To be able to test this you need to have build: https://github.com/Islandora-Devops/isle-buildkit/pull/65 locally and set REPOSITORY=local in your .env file.
Changing the following .env variables can to postgresql will change those services to use postgres:
DRUPAL_DATABASE_SERVICE=postgresql
FCREPO_DATABASE_SERVICE=postgresql
GEMINI_DATABASE_SERVICE=postgresql

If you building the local environment be sure that your settings.php file has it's previous database value stripped out of it.
Also this should not be merged until https://github.com/Islandora-Devops/isle-buildkit/pull/65 has been merged since it is a prerequisite.

I got this going from a clean isle-dc by following the "Create a local codebase from demo" instructions.  Works!
Crazy to be running two dbs but :man_shrugging:


Maximizing the impact of Flask-SQLAlchemy

Intro: When I first started coding, I was using psycopg2 a lot. Finding Flask-SQLAlchemy allowed me to make a ton of progress on my projects in a lot less time (for real, it was great). So, it may be quite beneficial to the world if Fsqla is more explicit about being a low-barrier-to-entry for new or inexperienced coders.
Purpose: I started this issue to gauge interest and gather ideas (pain points) for further lowering Fsqla's barrier to entry for inexperienced coders (kudos for how easy it already is). So, particularly, getting rid of often-encountered hurdles in usage or docs. Sometimes, very small changes can have a large impact (see proposal 1). Pain points that get support can get issues.
Conclusion: It may be argued that it is tedious and verbose to cater too much to new users. That is a possibility. Yet, it is possible to be clear and informative while not bloating things up. And secondly, it may be considered a moral obligation to support new coders in such a useful/easy framework as Fsqla.

"Quickstart: A minimal Application" page doesn't speak about the SQLALCHEMY_DATABASE_URI uri 'sqlite:////tmp/test.db'. It undoubtedly sends many people to google for one reason or another (certainly windows users, because copy/paste doesn't work). A link to doc: config/#Connect-Uri-Format would go a long way.
.
From a newbie perspective: [1] //// is not commonly encountered. [2] It is ambiguous whether tmp/test.db is a relative path or absolute path. [3] The nature of test.db is unclear--is it created automatically? [4] Is sqlite something that needs to be installed? Python includes it already, but what do I need to know about that? [5] How can I easily/quickly view my test.db to see what's in it? A recommended tool?
.
#469 mentions amending quickstart.
#462 intends to make the uri relative to cwd by default, but suggested for 3.0. In there, I suggest allowing sqlite alone to be a valid uri.

#163 Document benefits/differences to using Flask-SQLAlchemy over plain SQLAlchemy.

#502 A note/reminder for users exploring their Postgres db from CLI/via queries. It's interesting and informative to people who don't know. https://github.com/mitsuhiko/flask-sqlalchemy/pull/502/commits/4db21106fa6c494a435277f0749e58937de284f1

For the Version subsection in the left-panel of pocoo site, have the current version you're viewing display the entire documentation overview (as it currently is, the Related Topics subsection instead displays the previous and next topic).

?

whoops accidentally submitted. Adding a description now.

will be handled by #462
is not really in scope, but I'll keep it in mind when updating the readme / docs index.
is not really in scope, and I don't think the note belongs where you added it in that commit, but if you want to put it somewhere and submit a PR, go for it
version section will change, but that's not something that can be tracked here
?

Thanks for your feedback. We'll keep it in mind while updating the docs.


Add language-* classname to

Prism themes expect the language-* classname to be present on the <pre> element as well as <code>, and applies background colors to the <pre> element accordingly:
/* example from Okaidia theme css */

:not(pre) > code[class*="language-"],
pre[class*="language-"] {
	background: #272822;
}

Without that language-* classname present on <pre>, theme background colors aren't applied.

Sorry, totally missed this! Thanks!


TF2 suggests adding report_tensor_allocations_upon_oom to RunOptions while the option is not available

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux 4.18.0-193.60.2.el8_2.x86_64
TensorFlow version (use command below): 2.6.0
Python version: 3.8.0
GPU model and memory: Tesla V100-SXM2-32GB

Describe the current behavior
When OOM, the following message is displayed:
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info. This isn't available when running in Eager mode.
However, the suggested option is not available in tf2.
This (only!) works in tf1, e.g. as described in this SO answer.
tf2 doesn't have RunOptions
run_opts = tf.compat.v1.RunOptions(report_tensor_allocations_upon_oom=True)
results in:
TypeError: Invalid keyword argument(s) in 'compile': {'options'}
Describe the expected behavior

Preferably; Implementation of the option report_tensor_allocations_upon_oom in tf2
Removal of the misleading "hint" in tf2

@ManuelPopp
In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. Thanks!


Project status

Hi,
I'm developing an app on asp.net 5 at the moment and would like to give identity server a try. The docs on identity server 3 look like it can save lots of headache. :-)
I've seen there are already many examples for this new version. Is it worth playing arround with it or should I wait?
Are there important features, that are currently missing? Do you expect bigger breaking changes as far as you can say now?
I'm not planning to go live soon and I know things can change during development.
As I don't care about .net core at the moment, some missing support for that would not be a show stopper for me.
Thanks for any input on this
Max

Most of the core from IdentityServer3 is the same in IdentityServer4. The main things that will be changing relate to the user service and how your UI pages are invoked from IdentityServer (login page, error page, etc). Unfortunately these are the places you spend the most of your time coding for IdentityServer. So I'm not sure what to tell you. In a month's time these aspects will be much more stable, but at the same time if you start to try them out now you are in a perfect position to provide feedback on what works and what doesn't work.
What do you think?

Sounds good and I would be happy to provide feedback.
Any tip where i should have a look in the examples for getting an idea of the new ui invoking and user service? I think there is nothing like a documentation yet, correct?

The MVC sample
-Brock

On Jan 14, 2016, at 5:10 PM, Max Beckenbach<EMAIL_ADDRESS>wrote:
Sounds good and I would be happy to provide feedback.
Any tip where i should have a look in the examples for getting an idea of the new ui invoking and user service? I think there is nothing like a documentation yet, correct?
—
Reply to this email directly or view it on GitHub.

OK. If that's all to look at, let's go. :)

First positive feedback, after playing arround for some time:
I really like the usage of ViewLocationExpanders. This helps much to keep the project directories clean and gives the feeling of component driven development while still using mvc.
But the naming of the UI folder in the example feels somehow wrong. Don't know why.


Change features to labels and update README.md.

https://github.com/DrJohnWagner/PDSUtilities/blob/8547b35a0b0b53acae8aab91be3f9cca033ac23f/PDSUtilities/xgboost/plot_importance.py#L17

Something happened with the commit. Need to try again.


services: Add Tahoe-LAFS service.

Hi! This PR adds tentative (but more or less functional) Tahoe-LAFS service functionality to NixOS.
I have tested this PR by using nixos-rebuild build-vm and confirming that the resulting VM has a systemd service which runs Tahoe when started.
I have also tested that a personal machine with NixOS deploys this service as expected using standard nixos-rebuild switch incantations.
Not all Tahoe configuration is exposed, but all of the stuff that I cared about is exposed. This should be more or less enough to get a small grid online.
Things done:

[ ] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[x] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

More
Fixes issue #
cc @

Please note, that points are not mandatory, but rather desired.

LGTM

Seems fine to me.
@MostAwesomeDude Should we merge this now into to master to maybe get some feedback/users or do you want add more stuff before doing so?

I'm pretty sure that I'm the sole user right now.
I could hack on this more, and get the rest of the configuration sorted out, or we could merge it and then I'll put it to the test in my nixops plan. I'm not really picky; I don't have a preference.
I need sleep, but if this is still open next time I have hacking time, I'll do more work on this.

Okay, I'm done for now. This works on a local set of containers (modulo some nixops networking strangeness), so I think that it'll be fine to merge.

Can you please squash commits?

Squashed.


Too many addresses?

I was seeing bizarre behavior where my lone ToF was showing up as multiple devices in qwiic.list_devices (and consequently seeing the class instantiated multiple times for the same sensor). After spelunking the code I discovered a couple of things:

my pi servo phat registers two addresses on the I2C bus that I wasn't aware of.
my ToF sensor registers for 112 (!!) addresses. The qwiic class happily considers the VL53L1X to be the device for any/all of those addresses that are seen active on the bus. In my case, these are the two used by the phat board in addition to the one that the ToF is really using. Hence, I end up with 3 instances of the ToF class. Yuck.

I can't for the life of me figure out why this class should be registering for 112 addresses. Doesn't this make it basically incompatible with the sparkfun python qwiic implementation which is obviously very dependent on there being (at least initially) a deterministic mapping between I2C address and device type? Doesn't this class just stomp on other devices' available_addresses depending on the order the modules are loaded?
Seems like the fix is to just remove this line:
_AVAILABLE_I2C_ADDRESS.extend(_FULL_ADDRESS_LIST)

btw, in case anyone else has run in to this issue, here's the workaround I'm currently using:
       # wipe out the existing available_devices list         qwiic._QwiicInternal.available_devices = {}         # modify the ToF sensor's entry in the device list so it doesn't         # claim all addresses!         for dev_class in qwiic._QwiicInternal.qwiic_devices:             if 41 in dev_class.available_addresses:                 dev_class.available_addresses = [41]         # reload the available_devices list         qwiic._QwiicInternal.get_available_devices()
Then you can call qwiic.list_devices(), etc. and get the results you'd expect.

Hey there, so I believe your issue is in the implementation of qwiic.list_devices and not this Python package specifically.
When we first started developing the the sparkfun-qwiic python package, that method seemed like a useful feature. However, as we expanded on the number of products implemented in it, we ran into some unforeseen issues with that method. Specifically, I2C peripherals with configurable a I2C address, to any address. The private variable _AVAILABLE_I2C_ADDRESS lists all possible I2C addresses that the sensor can be configured for with the initial address being the default.
Unfortunately, while our proposed change would provide a quick fix to your problem, it would break the change I2C address method for this package. We are looking to fix the implementation of qwiic.list_devices; however, due to the complexity of what we would like to happen, it will take some time to work out the implementation. For now, that method will be unusable until we fix it.
(*As this isn't an actual issue with the VL53L1X Python package, I will be closing this issue.)


When doing "kubectl logs", it should show the FE or BE logs for that container

Right now the kubectl logs show very little data.   When a user executes kubectl logs for that container, it would default to show the FE or BE logs for that container.

We have options to turn on the behavior that redirect FE/BE's application logs to pod console. It turns off by default, because we want to provide consistent experience as VM-based deployment, of which, the user get used to find the log from logdir.
Try add "LOG_CONSOLE = 1" environment variable in the CRD or chart values, all the logs will be redirected to console, can be viewed by kubectl logs
Related documents are still in catch-up.

  I don't think people will run half one way and half another.

I agree. However, our log is chatty, and is important for trouble shoot, if user's infra doesn't have log collection service, it will be painful when log is lost.
It is a trade off.


[FEATURE REQUEST] Add arm64 support to 'load_balancer' component

Is your feature request related to a problem? Please describe.
Currently we only support the x86_64 architectures but we need to add support for arm64.
Describe the solution you'd like

We want the ability to install the load_balancer component on arm64 machines running CentOS.
Only the latest versions we support.
Any requirements missing or not added in #2033 will be added for the effected roles.
haproxy-exporter,  node-exporter, filebeat can be skipped at this point.

Effected Ansible roles:

haproxy
haproxy_runc
download
firewall

Skip the following Ansible roles for now by using a custom feature-mapping config:

node-exporter
haproxy-exporter
filebeat

Describe alternatives you've considered
None.
Additional context
No.
Extra info
Design document and resources:
https://github.com/epiphany-platform/epiphany/tree/develop/docs/design-docs/arm
Terraform scripts for ARM hardware on AWS:
https://github.com/mkyc/aws-arm-simple-setup
YAML for testing:
kind: epiphany-cluster
title: Epiphany cluster Config
provider: any
name: default
specification:
  name: test
  admin_user:
    name: operations
    key_path: /user/.ssh/epiphany-operations/id_rsa
  components:
    repository:
      count: 1
      machines:
      - default-repository
    kubernetes_master:
      count: 0
    kubernetes_node:
      count: 0
    logging:
      count: 0
    monitoring:
      count: 0
    kafka:
      count: 0
    postgresql:
      count: 0
    load_balancer:
      count: 1
      machines:
      - default-loadbalancer
    rabbitmq:
      count: 0
version: 0.11.0
---
kind: infrastructure/machine
provider: any
name: default-repository
specification:
  hostname: repository
  ip: ip #<IP_ADDRESS>
version: 0.11.0
---
kind: infrastructure/machine
provider: any
name: default-loadbalancer
specification:
  hostname: loadbalancer
  ip: ip #<IP_ADDRESS>
version: 0.11.0
---
kind: configuration/feature-mapping
title: "Feature mapping to roles"
name: default
provider: any
version: 0.11.0
specification:
  available_roles:
    - name: repository
      enabled: yes
    - name: firewall
      enabled: yes
    - name: image-registry
      enabled: yes
    - name: kubernetes-master
      enabled: yes
    - name: kubernetes-node
      enabled: yes
    - name: helm
      enabled: yes
    - name: logging
      enabled: yes
    - name: opendistro-for-elasticsearch
      enabled: yes
    - name: elasticsearch
      enabled: yes
    - name: elasticsearch-curator
      enabled: yes
    - name: kibana
      enabled: yes
    - name: filebeat
      enabled: yes
    - name: logstash
      enabled: yes
    - name: prometheus
      enabled: yes
    - name: grafana
      enabled: yes
    - name: node-exporter
      enabled: yes
    - name: jmx-exporter
      enabled: yes
    - name: zookeeper
      enabled: yes
    - name: kafka
      enabled: yes
    - name: rabbitmq
      enabled: yes
    - name: kafka-exporter
      enabled: yes
    - name: postgresql
      enabled: yes
    - name: postgres-exporter
      enabled: yes
    - name: haproxy
      enabled: yes
    - name: haproxy-exporter
      enabled: yes
    - name: vault
      enabled: yes
    - name: applications
      enabled: yes
    - name: ignite
      enabled: yes
  roles_mapping:
    kafka:
      - zookeeper
      - jmx-exporter
      - kafka
      - kafka-exporter
      - node-exporter
      - filebeat
      - firewall
    rabbitmq:
      - rabbitmq
      - node-exporter
      - filebeat
      - firewall
    logging:
      - logging
      - kibana
      - node-exporter
      - filebeat
      - firewall
    load_balancer:
      - haproxy
      - haproxy-exporter
      #- node-exporter
      #- filebeat
      - firewall
    monitoring:
      - prometheus
      - grafana
      - node-exporter
      - filebeat
      - firewall
    postgresql:
      - postgresql
      - postgres-exporter
      - node-exporter
      - filebeat
      - firewall
    custom:
      - repository
      - image-registry
      - kubernetes-master
      - node-exporter
      - filebeat
      - rabbitmq
      - postgresql
      - prometheus
      - grafana
      - node-exporter
      - logging
      - firewall
    single_machine:
      - repository
      - image-registry
      - kubernetes-master
      - helm
      - applications
      - rabbitmq
      - postgresql
      - firewall
      - vault
    kubernetes_master:
      - kubernetes-master
      - helm
      - applications
      - node-exporter
      - filebeat
      - firewall
      - vault
    kubernetes_node:
      - kubernetes-node
      - node-exporter
      - filebeat
      - firewall
    ignite:
      - ignite
      - node-exporter
      - filebeat
      - firewall
    opendistro_for_elasticsearch:
      - opendistro-for-elasticsearch
      - node-exporter
      - filebeat
      - firewall
    repository:
      - repository
      - image-registry
      - firewall
      #- filebeat
      #- node-exporter

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

@seriva just one question regarding "Skip the following Ansible roles for now (...)". Do we need additional tasks not to forget about those?

The missing exporter and logging roles will be addressed in the exporter/logging stories (#2116, #2117). AMP just needs K8s, loadbalancer and Kafka to start.

Already implemented with #2033
Pull request here: https://github.com/epiphany-platform/epiphany/pull/2139

✅ Tested, HAProxy works fine, I was able to reach HAProxy on 443 from internet


[Flowbroker] template node: size of the input field is smaller than the field size

Test OK.


For some? machine-dependent character ("機種依存文字"), it doesn't report that when U+xxxxx is typed for the first time.

I noticed that there is slight behavioral difference between first-time and
afterwards, that when we type U+xxxxx to convert a character based on codepoint
it may or may not report the warning that the character is machine-dependent
(機種依存文字).

What steps will reproduce the problem?
1. Enter mozc hiragana mode.
2. Type U+2F81E.

What is the expected output?

- See this screenshot: https://twitter.com/atsushieno/status/552138494982643715

What do you see instead?

- See this screenshot: https://twitter.com/atsushieno/status/552136801335267328

What version of the product are you using? On what operating system?

- Ubuntu 14.04, mozc-server 1.13.1651.102-2, fcitx-mozc 1.13.1651.102-2

Please provide any additional information below.

- Should be cosmetic issue, but this kind of behavioral differences could be a
glitch when reporting bugs :-)

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 5 Jan 2015 at 4:37

Since 473a26ccd17304f6c64eaac8c61090659bcdb936 removed the feature of "機種依存文字", this issue is marked as obsolete.


Voting window resets on push to any branch

Currently the voting window resets when somebody pushes to any branch on their remote repo, and not just the one they're trying to merge in. Obviously this is unnecessary, and even worse, actively discourages active development, because you need to wait hours between PRs.
The tough part is that we can't base the voting window off of the commit time, because those can be abused as well, such as by backdating or just not pushing malicious commits until right before the voting window ends.
I have noticed that PRs track when commits are added to them, is this something that we can use? And do they get the right time when a backdated commit is pushed?

You hit the problem on the head exactly.  @hongaar and I were having a similar conversation here https://github.com/chaosbot/chaos/issues/142#issuecomment-303660362
Here is basically what we currently have available https://developer.github.com/v3/pulls/#get-a-single-pull-request.  To note: the updated_at field at the top level is misleading, because from my early tests, I believe it is updated when anything happens on the PR, including comments, title changes, etc.
We should definitely try to surface a better solution

Maybe we could store a list of commit IDs from each PR as they come in, and then compare them. If they differ, then extend the voting window.
Naturally this doesn't work if the innocent commit and malicious commit have the same SHA1 hash, but I doubt that will be an issue :P

Another possible solution: https://developer.github.com/v3/activity/events/types/#pushevent

This was fixed yesterday by #420 :tada:

/vote close


[Q] AES key pattern analyzers

Not an issue per se, but do you by any chance know any AES key dumper/scanners? I assume it is compiled with the binary

There are decompilation tools available for Godot games. Granted these work only if the binary isn't encrypted, but you can give it a shot.


Parallel test runs on travis

Should be fairly uncontroversial and needs to happen soon so that we catch OpenMP-related bugs before merging them.

Fixed in PR #145.


Build fails with 'Unable to detect OpenSSL version'

Building on Debian, Cargo version is 1.32.0.
error: failed to run custom build command for `openssl v0.9.24`
process didn't exit successfully: `/home/username/Desktop/weechat-discord/target/release/build/openssl-1a53f5853bfeae35/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Unable to detect OpenSSL version', /home/username/.cargo/registry/src/github.com-1ecc6299db9ec823/openssl-0.9.24/build.rs:16:14
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::begin_panic
   6: build_script_build::main
   7: std::rt::lang_start::{{closure}}
   8: std::panicking::try::do_call
   9: __rust_maybe_catch_panic
  10: std::rt::lang_start_internal
  11: main
  12: __libc_start_main
  13: _start

What version of openssl do you have installed?

# dpkg -s openssl
Version: 1.1.1b-1

So, this looks like https://github.com/serenity-rs/serenity/issues/394. Serenity depends on the 0.9 openssl crate which does not support OpenSSL 1.1.1.  I'm not really sure what to do about, but it looks like there is an open pr and issue in serenity to fix it

bf4ed92 bumps serenity to v0.6, which should work with newer versions of OpenSSL, can you see if it works now?

Now it compiles most of it, but still ends up with the following, although different error:
Compiling serenity v0.5.11 (https://github.com/terminal-discord/serenity?branch=v0.6.x#aa35fe90)
error[E0658]: `extern crate self` is unstable (see issue #56409)
   --> /home/username/.cargo/git/checkouts/serenity-11d2723d0b26d0f2/aa35fe9/src/lib.rs:118:1
    |
118 | extern crate self as serenity;
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: Could not compile `serenity`.

To learn more, run the command again with --verbose.

Interesting, it looks like serenity either depends on nightly rust or a newer stable version.  Try compiling on nightly because I know I am now using a few nightly features in weechat-discord.

How would I do that? This is my first time using Cargo.

@VasyaTheWizard Assuming you installed cargo with rustup, just run the following command:
rustup default nightly

Compling on nightly did the trick, still doesn't compile on stable though.

Closing because this should be fixed


Add a length check to fix detached DOM problem

This follows the suggestions on https://www.cypress.io/blog/2020/07/22/do-not-get-too-detached/ and adds a length check which (hopefully) ensures that the whole list of searched-for-items has loaded before we try to iterate over them.

I haven't had a chance to look into your code carefully, but one thing I wonder is whether you have some serious inefficiency somewhere in your filtering. The fact that so many filtering tests fail so consistently due to timing issues really makes me wonder if you're just doing something awkward in your filtering that's slowing things down and which is the ultimate root of the problem.


Why StreamAccessLogsResponse is named with stream

Got a bit of a naive question, but would be happy if you can clear this out for me
based on grpc documentation, the StreamAccessLogs RPC defined for envoy is a Client streaming RPC:
https://grpc.io/docs/what-is-grpc/core-concepts/:
Client streaming RPCs where the client writes a sequence of
messages and sends them to the server,
again using a provided stream. Once the client has
finished writing the messages, it waits for the server to read them
and return its response.
Again gRPC guarantees message ordering within an individual RPC call.

rpc LotsOfGreetings(stream HelloRequest) returns (HelloResponse);

https://github.com/envoyproxy/envoy/blob/main/api/envoy/service/accesslog/v2/als.proto#L27:
rpc StreamAccessLogs(stream StreamAccessLogsMessage) returns (StreamAccessLogsResponse)
Since the response is not a stream but a single response, isn't the name StreamAccessLogsResponse might be a bit misleading?

I think this is more about sticking to naming conventions. Usually the request message is in xRequest and the response is xResponse, but here a 'request' doesn't make much sense, as it's really a naive request being sent here. In this case x = StreamAccessLogs.

Thanks for the detailed answer, it crossed my mind that the reason could be naming convention.
I was counting on the gRPC documentation examples for convention:
rpc LotsOfGreetings(stream HelloRequest) returns (HelloResponse);
but I guess it was just an example.
Again, Thanks for your response.


Svelte package

Would love to have a Svelte library exposed for Lucide icons, would there be interest in this from the package maintainers?

Good idea, I will add it to our roadmap!


Add --always-total option

Closes #1086

@nedbat Let me know what you think. If you like it, I'll add a test or two.

@nedbat Let me know what you think. If you like it, I'll add a test or two.

Per request on the #1086 going to go with a simpler path and always output the TOTAL line no matter what.

Per request on the #1086 going to go with a simpler path and always output the TOTAL line no matter what.


[Bug] Popping/Clear kb shortcuts don't work

Version: 0.5.0
Description: Popping the stack from the shortcut clears it instead. The clear shortcut does nothing. (Swapping works). All tray icon's menu options work as expected.
Note: I wasn't able to use the trace feature you provided, I'm probably using it wrong.

ah, damnit, last minute refactoring gone wrong! I see the problem, testing out the fix

Just posted 0.6.0 with the fix landed (6645569db6e27eb5c0ded67ec95c2f2a44ccfe00). Let me know if this fixes it!

It does.


STM8S103F3 microcontroller

Hi
I found this STM8S103F3 microcontroller , it support V-USB (description here : https://hackaday.com/2014/03/02/software-usb-on-the-stm8/)
Here is specification of STM8S103F3 microcontroller : https://www.st.com/en/microcontrollers-microprocessors/stm8s103f3.html
can we use this cheap micro STM8S103F3 instead of Atmega32u4?

To use STM8S103F3 you need the 3rd party Board definition from https://github.com/tenbaht/sduino but this has some limitations as the author describes:

I adopted the Arduino core functionality for the STM8S to set up a simple programming environment. But unfortunatly there is no free C++ compiler for these CPUs. This makes it impossible to do a full port of the whole enviroment and integrate it 100% in the Arduino world as it has been done for the STM32 and the ESP8266.

So the libraries must be written in C, but this library(Corsair Lighting Protocol) and FastLED are written in C++. V-USB demonstrate that it is possible to do USB, but it does not implement Arduino USB API, so the complete HID stack must be reimplemented.
It could be possible to use STM8S103F3 but it is not a drop-in replacement for the Atmega32u4 and a lot of work has to be done. I will not support STM8S103F3 in Corsair Lighting Protocol, because it's completely out of scope.

On a tangent topic, how hard would it be to support alternative arduino-compatible microcontrollers?
I know you can use some microcontrollers like the ESP8266 and STM32 in the arduino IDE, but would it be possible to create a CLP program running on one?

You can try to compile the CLP for such a board and if it compiles it's like that it will work. For this "test" you don't even need the hardware.


Verify caller type

When the actor is invoked, it should perform a caller type checker so that when the caller is not satisfied, can throw error.
The proposed solution is to build a simple role management on fvm actor. We can follow existing evm role management system with some simplification. We just need two roles: caller and admin. For admin role, it can perform the CRUD of other roles while caller can just call the actor methods.
Role and address are many-to-many relationships and it can be persisted in a HAMT.

Maybe this can be of help? https://github.com/ethereum/EIPs/pull/881

Sounds, good. I can draft some initial implementation, then we can discuss over that.

Please have a look at FIP-0049 and the corresponding discussion.

method num 1 the implementation of a function supportsInterface(cid) bool

The method number 1 is reserved for the constructor, isn't it?

Please have a look at FIP-0049 and https://github.com/filecoin-project/FIPs/discussions/382.

We could jump right away to implement this approach (and even propose it as reference implementation to the FIP). My only concern is that is still on a draft state and I don't know to what extent it may change or when should we expect an implementation to be available. But if we think that this approach is better, let's go for it. It has been more extensively discussed.

The method number 1 is reserved for the constructor, isn't it?

Correct. I wanted to give an example, but the methodNum I chose is already reserved so it could be confusing (my bad). Already edited.

Hey, @cryptoAtwill. Your proposal makes sense. An improved proposal, what about:

We expose a is_interface method in well-defined method number (e.g. 1024 as you suggest) that actors that want to support interface identification need to implement.

This method accepts the list of method numbers that conform the interface the caller wants to identify.
The method computes the interface identifier that results for those method numbers. The identifier can be computed as the XOR of the hash of the concatenation of the varInt for the method number and the serialization of the method params for all the input methods provided in the call: hash(varInt(1) + method1_params) XOR hash(varInt(2) + method2_params) XOR ...
Calling actors can get use this ID to determine if the actor implements the interface.

Is up to the actor to decide how to implement this is_interface method so it is gas efficient, but is could be something as simple as hard-coding the return value if the right input for all the interfaces supported is received, and return zero bytes otherwise. We could also perform this computation on-chain in the constructor to avoid intentional or unintentional forging of interface ids.
I would also suggest offering the convenient methods to implement this interface_id method and computing the interface id as part of fvm_utils for actors to integrate it, and then expose the subnet_actor interface as part of the ipc_gateway or wherever we choose IPC-related types to live (maybe as part of the ipc_sdk?)

Guys, please have a look at this.

I suggest we use FIP-0049 to compute method numbers (here is a reference implementation). Then we could derive the interface ID simply XORing the method numbers (not imposing any particular order in the method set), similar to ERC-165.

I agree, we should use FIP0049 for method numbers, and XORing to detect that the methods are right, but this standard doesn't consider the types of the method params, right? We are trying to go one step further and not only check that the method name (and thus the method num) is correct, but also that it has the right arguments. //cc @cryptoAtwill

Overloading was considered in the FIP:

Overloading
We could overload method names by including a description of their parameter type in the hash payload. This is rejected for simplicity. There is little evidence that method overloading has been of great utility in, e.g., Solidity. Since payloads are expected to be IPLD structures, overloading would require defining a standard serialization of an arbitrary IPLD type schema.
Excluding the parameter type from the method names means that methods may receive dynamically typed parameter payloads. This permits a kind of overloading if some part of the payload is used for dispatch in addition to the method number. A future convention could define a standard for this.

Excluding the parameter type from the method names means that methods may receive dynamically typed parameter payloads. This permits a kind of overloading if some part of the payload is used for dispatch in addition to the method number. A future convention could define a standard for this.

I completely missed this. @cryptoAtwill, re. our sync discussion. You may probably use FIP0042 directly without any macro-related dance.

@cryptoAtwill, have a look at how @sergefdrv uses this here: https://github.com/consensus-shipyard/ipc-atomic-execution/blob/e5d70adfecfd7883382fdb84ece2308027c5617f/examples/fungible-token/src/lib.rs#L1 Consider using it for the interface identification directly.


[#225] Improve Code Coverage Report in Dangerfile

Resolves #225
What happened
Currently, in a pull request, we are showing the code coverage of all files in the project, we need to update Dangerfile to show only code coverage of file changes.
Insight

Filter file changes in pull requests.
Show code coverage of all file changes instead of all files of the project.

Proof Of Work

No code file changes

Have file changes:

@suho Please fix CI error 🙏

@suho Please fix CI error 🙏

@markgravity For pull requests on ios-templates, we don't use Pull Request Review by Danger, I enabled it for testing, then I already disabled it. Please check only about the Test Script workflow only 😁


Remove backward index, use gradient guessing instead

Solves #73
The new solution reuses the FGradient to get the node correspondence information.

This release the user's burden of declare the correspondence via FBackwardOutToInIndex and FBackwardGradInIndex.
User only need to declare TIsBackward to true in the backward node

@piiswrong Tested on tinyflow and mxnet-nnvm

How about check for name instead. FGradient has to give different names to
the two ops right?
On Nov 24, 2016 7:22 PM, "Tianqi Chen"<EMAIL_ADDRESS>wrote:

@tqchen commented on this pull request.
In src/pass/infer_shape_type.cc https://github.com/dmlc/nnvm/pull/85:

   }

 if (backward_in_grad.count(inode.source->op())) {

   std::vector<uint32_t> in_grad =

     backward_in_grad[inode.source->op()](inode.source->attrs);

   CHECK_LE(in_grad.size(), fnode.source->num_outputs());

   for (size_t i = 0; i < in_grad.size(); ++i) {

     uint32_t eid = idx.entry_id(inode.inputs[in_grad[i]]);

 // input gradient list

 auto igrad = fgrad[fwd_ptr->op()](fwd_ptr, ograd);

 const Op* backward_op = inode.source->op();

 const Node* igrad_node = nullptr;

 // Input gradient assignement

 for (size_t i = 0; i < igrad.size(); ++i) {

   if (igrad[i].node->op() == backward_op) {

no, the error occurs in the inference. However, in all our cases they do
not occur
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dmlc/nnvm/pull/85, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiudBobbgsPk-Ty2rjPwN0NEsuBtUp0ks5rBlR-gaJpZM4K8CU7
.

discussed per offline, we concluded that current version is fine. since in all cases usually one backward op charges gradient for all(or there will be two kinds of backward ops). An error will occur to ensure things don't fall apart silently when violation happens


Add SBOM generation and verification to release

Signed-off-by: Juan Antonio Osorio<EMAIL_ADDRESS>

Codecov Report

Merging #20 (0e2f37e) into main (fa60e5e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #20   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          153       153
=========================================
  Hits           153       153

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

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

Continue to review full report at Codecov.

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


Enhanced Redis setup for addok with file support

This PR adds conditional RDB file management to Addok's Redis configuration, allowing for enhanced flexibility in Redis setups. Key features include:

RDB Support: Enables Redis instance launch with a predefined data path via ADDOK_REDIS_DATA_PATH.
Dynamic Configuration: lib/cluster.js now supports both standard and RDB-based Redis configurations.
Updated Tests: New tests validate the RDB feature without affecting existing functionalities.

Replaced by #4


Include parameter names and javadoc descriptions in suggestions

Class descriptions are currently read with javap command and unfortunately it doesn't print out parameter names. But if a java source file exists for a class, we can scan it both for method parameter names and javadoc descriptions during class loading. Some jar files include javadoc also.

Now includes parameter names if classes have been compiled the -parameters switch of Javac. Still missing parameter names for most libraries though.


[madSHaLz] APOC triggers aren't updated after a user deletes a database

Implemented 3rd solution - DatabaseEventListener,
so that we can delete every system node belonging to the database that we delete.
Added a cleanUpSystemNodes() for backward compatibility

Feel free to merge, we can fix the Snyk issues in another PR, as they are related to dependencies that they've just deemed are insecure


Feature request: 'Open with… [Tagger]' option

I would like to be able to open one or several files I want to edit with Tagger directly from Nautilus / my file manager. Currently you have to open Tagger first and then select a directory which is not very intuitive (e.g. Paper Clip - a PDF metadata editor - lets you open files from the file manager, same for Metadata Cleaner…)
Could be related to #259 as opening one /several files in the app without going through the directory chooser dialog seems to go against the current logic of Tagger

Do you use Tagger via flatpak or installed manually/aur? Beside this feature will not work on Flatpak due to its sandboxing nature...but if you use AUR or something like that I can implement this feature for that...

Beside this feature will not work on Flatpak due to its sandboxing nature...but if you use AUR or something like that I can implement this feature for that...

I think it worth clarifying that the problem is not the ability to provide the feature in Flatpak, we could provide mimetype handler for file managers to consume just like we do in Denaro, but the problem is Tagger currently can only access xdg-music and xdg-dowload directories without portal.
So the question arise again: should we expect users to open files outside of xdg-music and xdg-download in Tagger? If not, then I think opening files from file manager brings no harm, in worst - unexpected - case we could show a toast about insufficient permissions. But if it's not enough, I guess we have to add home permission.

Implemented now, and we added home permission, but take note that if you will try to open a folder outside of home using "Open with..." then Tagger will not start. We can't do anything about this, it's flatpak bug. If you have music files outside of home, it's recommended to give Tagger permission for required folder using Flatseal (not only for "Open with..." to work, but also to get better performance).

https://github.com/NickvisionApps/Tagger/releases/tag/2023.9.0-beta1


Use Selective Omissions

Bump doc-warden version
Leverage new feature to ignore some readmes
Stop treating said readmes as exceptions.

Closing pending discussion in Azure/azure-sdk-tools#42.
Need to establish across the board whether or not these service level should be enforced.


Implement --no-version flag

Removes the SHA/revision from directories in vendor/cache.
See https://github.com/bundler/bundler-features/issues/76 for motivation and
explanation.
I suspect I probably need to update documentation (and possibly tests) etc. as well, but I figured I'd ask for feedback on the idea before putting in that work.

The entire point of including the SHA is so that we know what version of the gem is being cached. If we don't know what version of the gem is being cached, Bundler can't tell if the code in vendor/cache is the right code or the wrong code. I don't think this is a workable change, sorry.


CHQ-103 Moved token handling from event-based system to vuex-based system

Story
https://maddonkeysoftware.myjetbrains.com/youtrack/issue/CHQ-103
Summary

Temporarily commented out shared event system as it is not in use. I suspect it will be used in the future so leaving it in for now.
Removed event based system for sharing API token to move it to shared store based in Vuex.

Testing

Start the UI and API projects.
Perform log in operation. Verify that the nav bar updates appropriately.
Perform log out operation. Verify that the nav bar updates appropriately.

Merging as project has single core reviewer.


handle get_channel_auth_cap sent as IPMIv2 request

If the client sends the get_channel_auth_cap command as an IPMIv2 request then it isn't handled correctly by the initiate_session() method due to the different header structure.  Likewise the response needs to be sent in IPMIV2/RMCP+ form.

@CJLove somehow I missed this PR, is it still relevant? Can you merge latest master (py2/3 support), as there are some conflicts on this PR. Thanks.

I'm no longer doing anything IPMI-related and have no means to test it.


Updated to use esptool-js backend

This has no been updated to use esptool-js. Tested locally, using circuitpython-org with the following modifications (locally):

Added a symbolic link in assets/javascript with ln -s ../../../web-firmware-installer-js/ installer
Update _layouts/download.html changing the script tag at the bottom to <script src="/assets/javascript/installer/cpinstaller.js" type="module"></script>
Starting the circuitpython.org site locally per the README
Navigating to http://localhost:4000/ (using localhost is important as it works around the CORS policy allowing reading JSON files on AWS)

cc @ladyada and @dhalbert for review

Hi, just checking in about testing/review of this PR.

I've tested on plain ESP32, but will test on the other boards.

I can't find my C3, but I can test with a C6, which is similar (no native USB).

Ok, decided to test with the ESP32-C6 first and found some issues already (possibly because old installer didn't support it), so I'm going to fix that up.

Ok, ESP32-C6 works now, but ESP32-S3 and ESP32-S2 are timing out (it may be an esptool-js issue, but I need to dive a bit deeper).


RevEng: Support for additional SQL Server data types

Currently we support many SQL Server data types, but not the following: cursor, hierarchyid, sql_variant, table, xml, geography, geometry. If RevEng comes across a column with one of these types it just outputs a warning message that it is ignoring that column.
We should decide which of the above we do plan to support and how we plan to do so.

Table, xml, geography and geometry would be very welcome.

Cursor  and table are not column types, afaik. Do not support sql_variant. And think carefully about how to support the remaining ones. (most likely not in V1)

I'm working off https://msdn.microsoft.com/en-us/library/ms187752.aspx which lists all the data types for SQL Server 2014. That said several of these types have not traditionally been supported - this list is just exhaustive so that we can make a deliberate yes/no support decision for each of them.

EF Team Triage: There is a more general need to support these throughout EF and our SQL Provider. Closing out this issue not because we don't want to support them, but because we will enable support right throughout the stack as we go and don't need a specific item for reverse engineer.

Hey Rowan, just to add my 2 ct, hope you'll support HierarchyId asap because it's really a great way to manage hierarchy and other manual ways demand so much effort in code.
Also, it could be great to support natively the GROUP BY xxxx WITH ROLLUP to allow to calculate par ex. Totals per group/subgroup/etc... witch make a huge save code effort + offcourse performance improvement
Txs
-Vince


#327 enterprise id mismatch, #275 readFile override, #331 init/upgrade errors, #332 skipInteraction always used

PR details
What is the purpose of this pull request?

[x] Other, please explain:

What changes did you make? (Give an overview)

closes #327 enterprise mismatch errors now include type and value of the found EID to make debugging easy.
closes #275
closes #331
closes #332

Is there anything you'd like reviewers to focus on?
...
Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] ESLint & Prettier are not outputting errors or warnings

@DougMidgley - im going to go ahead and merge this but might be good if you gave this a look after the fact anyways


Add URL shortcut to monitor

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
When visiting the monitored service page (e.g. /dashboard/9) it would be useful to display a Visit link button.
✔ Solution
This would be especially useful for monitored websites
❓ Alternatives
No response
📝 Additional Context
No response

What do you mean by the said button. (where should that button link)
Are you refering to this part of the UI

Exactly. I couldn't find a way to add a link

Currently, we don't quite have the information to construct a link to your other docker containers afaik.
We don't know which port on localhost or which URL from the outside maps to each container
⇒ we currently don't display something like this.
If you'd like to contribute a fix for this, here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md
Here is the code for the link-construction
https://github.com/louislam/uptime-kuma/blob/499429858c6c4926dbeb3511bed45744ea98fd74/src/pages/Details.vue#L30

Thank you so much for your reply! I think that the logic behind my reasoning is similar to how is already done with http. I'll let you know once I figure it out


terragrunt iam-role flag throws UnauthorizedOperation error

when i expose the aws credentials (secret key & access key) via env vars and try to run terragrunt with iam-role flag it throws UnauthorizedOperation error.
But same as the above same scenario this time, i didn't expose the aws credentials via env vars instead i put them in .aws folder (aws profile) terragrunt is successful when assuming the role.
Not sure what's the problem with env vars for aws creds, i've read the documentation clearly and it doesn't mention about this use case.
Probably, this is more of a question rather than an issue.

when i expose the aws credentials (secret key & access key) via env vars and try to run terragrunt with iam-role flag it throws UnauthorizedOperation error.

Could you share the actual error? And how you're setting your credentials (but not the credentials themselves!).

I too remember facing the same issue. The env variable worked fine for me
TERRAGRUNT_IAM_ROLE="arn:aws:iam::${account_number}:role/${iam_role}"
@jack-of-AllTrades  Can you pls try to use the environment variable, something like this?
TERRAGRUNT_IAM_ROLE="arn:aws:iam::${account_number}:role/${iam_role}" terragrunt validate-all

Closing as stale. If this is still an issue, please open a new ticket with the updated context. Thanks!


Map output is not sorted by key

Describe the bug
map output not sorted
To Reproduce
do not know. sometimes maps appear randomized
Expected behavior
maps consistently transmitted

to reproduce:
gwhisper <IP_ADDRESS> examples.ComplexTypeRpcs mapNumbersToString numbers=:7, 4, 2, 1, 9, 8:
2019-07-05 00:08:47: Received message:
| number_to_string[1/6] = {NumberToStringEntry}
| | key.. = 9 (0x00000009)
| | value = "9"
| number_to_string[2/6] = {NumberToStringEntry}
| | key.. = 1 (0x00000001)
| | value = "1"
| number_to_string[3/6] = {NumberToStringEntry}
| | key.. = 2 (0x00000002)
| | value = "2"
| number_to_string[4/6] = {NumberToStringEntry}
| | key.. = 4 (0x00000004)
| | value = "4"
| number_to_string[5/6] = {NumberToStringEntry}
| | key.. = 7 (0x00000007)
| | value = "7"
| number_to_string[6/6] = {NumberToStringEntry}
| | key.. = 8 (0x00000008)
| | value = "8"
RPC succeeded :D


DatabaseException in DBForeignKey.php with SQL-SERVER database

Affected Version
guzzlehttp/guzzle                6.3.3  Guzzle is a PHP HTTP client library
phpunit/phpunit                  5.7.27 The PHP Unit Testing framework.
silverstripe/mssql               2.0.2  Adds MSSQL support to SilverStripe
silverstripe/recipe-cms          4.4.1  SilverStripe recipe for fully featured page and asset content editing
silverstripe/recipe-plugin       1.3.0  Helper plugin to install SilverStripe recipes
symbiote/silverstripe-queuedjobs 4.4.0  A framework for defining and running background jobs in a queued manner
Description
After the latest change  in vendor/silverstripe/framework/src/ORM/FieldType/DBForeignKey.php we receive the following error :
Uncaught Exception SilverStripe\ORM\Connect\DatabaseException: "Couldn't run query:  SELECT count(*) > 100 AS "over_threshold"  FROM "Member"  42000, 102, [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Incorrect syntax near '>'."

row number 99 :
$dataQuery->setSelect(['over_threshold' => 'count(*) > ' . (int) $threshold]);

Microsoft SQL Server does not allow comparison in a SELECT statement without using CASE or IIF.  I do know SQL Server is not fully supported, but everything worked fine until this change.
Steps to Reproduce

Configure SQL Server as database
Create dataobject with a has_one to Member::class
Show dataobject in ModelAdmin

PR in progress: https://github.com/silverstripe/silverstripe-framework/pull/9210

Just wanting to follow up on this as I am expericening the same issue.
Uncaught SilverStripe\ORM\Connect\DatabaseException: Couldn't run query: SELECT count(*) > 100 AS "over_threshold" FROM "PersonType" 42000, 102, [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Incorrect syntax near '>'.
"silverstripe/recipe-plugin": "^1.2",
"silverstripe/recipe-cms": "4.5.2@stable",
"silverstripe-themes/simple": "~3.2.0",
"silverstripe/mssql": "^2.0"

Fixed by https://github.com/silverstripe/silverstripe-framework/pull/9678


HMR not propagating correctly with circular imports and re-exports

Bug report
What is the current behavior?
At import time, the dependency will be undefined, and the update cannot be called correctly after the first HMR cycle.
If the current behavior is a bug, please provide the steps to reproduce.
Reproducible Repo:
https://github.com/pmmmwh/refresh-cycle-repro
Run yarn start and then try to edit SurveyOverview.js, like returning 101 instead of 100 in the function.
The module.hot.accept() calls are intentionally placed for only those files - they are recognized as "boundaries" for HMR to happen in React Fast Refresh world.
What is the expected behavior?
The dependency should be the exact exports and thus calls to it should work correctly, even after HMR.
To be honest, I'm not sure if this is too extreme/specific of an edge case which is hitting the boundaries of Webpack's CJS/ESM module system. It involves re-exports and circular dependencies (both need to be related to an unaccepted dependency for this issue to rise) which, in practice, are both very difficult to deal with properly in CJS. To my understanding, Webpack's module system aligns closer to CJS - so I'm also not sure if this can be solved at all.
This might be related to #10870.
Related issue for FR: pmmmwh/react-refresh-webpack-plugin#81
Other relevant information:
Webpack version: 4.43.0
Node.js version: 14.4.0
Operating System: macOS 10.15.5
Additional tools: None

I didn't run the code yet (on mobile), but from reading the code this seem to be a circular depenency issue.
In a circular depenency behavior often depends on the module you execute first. This one will see all it's dependencies completely, but the child modules may see the parent module incompletely. Here routes execute first and can see Dashboard.
But with a module.accept handler re-execution will start at the accepted module, so we enter the cycle at a different module, which causes a behavior change.
I guess we could detect these circular depenendencies in the HMR runtime and try to enter the cycle at the correct module on re-execution. But this could be a bit tricky to implement.

bump

I think still valid

we are running into this as well. some modules become undefined after a fast refresh in a monorepo with re-exports and some circular imports

I think this is a "won't fix". If you accept a module it will start executing there. If you don't want that behavior place your accept somewhere else.

I’m probably missing something — a module originally having exports but later starting to have undefined as exports, seems like a bug either way? Regardless of how accept works I wouldn’t expect exports to “get lost”. Even stale exports would be better imo.

@gaearon Can you open a new issue and describe why do you think it?


No Intro Text in Linux build

Description of Problem or Question
There is no intro text in any of the missions that you can choose.
It's just either black screen or the choosen background image from the author.
The background music and sounds works just fine.
I have only tried a few of the Mansions of Madness missions.
Valkyrie Version
v2.4.00b and v2.3.04

What distribution/version of linux do you have? Can you please provide a screen shot showing the problem?
Thanks.

Im using Manjaro Linux x86_64, i took pictures from the 3 most popular English missions.
A Strain on Reality
https://imgur.com/a/Yc5X98a
Stress and Strain
https://imgur.com/a/LYnvRrP
Chapeldown Manor
https://imgur.com/a/xW0YKgv
https://imgur.com/a/gdYkUBu
I hope these will help

Looks like it is crashing out. Are you able to get the log from here:
~/.config/unity3d/NA/Valkyrie/Player.log
Thanks.

Yep, I made a new Player.log for each mission. Not sure if it will be any different.
A Strain on Reality
https://www.paste.org/99942
Stress and Strain
https://www.paste.org/99943
Chapeldown Manor
https://www.paste.org/99944

Will investigate further

Same here on Ubuntu 19.10.

As of v2.4.09 the intro shows up as it should on the Linux client.
Tested it today on Linux Mint 19.3 (Ubuntu 18.04).
Not sure what could have fixed it, maybe the update to Unity 2018.4.21f1 LTS?
I keep the ticket open for the devs. If they maybe want to have Player.log file to see any different.
EDIT:
I did the some test again with older version of Valkyrie.
valkyrie-linux-2.4.07 (pre Unity 2018.4.21f1 LTS) = Broken intro
valkyrie-linux-2.4.08 (first version with Unity 2018.4.21f1 LTS) = Broken intro
valkyrie-linux-2.4.09 (post Unity 2018.4.21f1 LTS) = Working intro
So i guess it wasn't the new Unity version that fixed it :) not sure what fixed it. Maybe the recommend dlls that was included with the 2.4.09 release.

Just tested valkyrie-linux-2.4.09 on Kubuntu 20.04 and can confirm that it works fine.

Hello, thanks for the update and good to know that it is fixed (I will update release notes).
One possible explanation is that the latest Unity version 2018.4.23f1 may have corrected this.
It was used in release 2.4.09.


[add] config ci .travis.yml

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1ec9f03). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #17   +/-   ##
=========================================
  Coverage          ?   27.27%
=========================================
  Files             ?        5
  Lines             ?       44
  Branches          ?        0
=========================================
  Hits              ?       12
  Misses            ?       32
  Partials          ?        0

Continue to review full report at Codecov.

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


npm install required?

Unless I do run: npm install in a step before running reviewdog/action-remark-lint@v2, I get warnings about missing plugins. I feel that npm install is something the action should do itself, no?

@asbjornu You'r correct. We should apply similar steps like (https://github.com/reviewdog/action-eslint/blob/master/script.sh) and (https://github.com/reviewdog/action-coffeelint/blob/master/entrypoint.sh).

@asbjornu I just run another test, but in my case everything works fine (see here). Can you maybe give me more information on how to reproduce the warning or show the action where you received the warning?
I also checked the base Dockerfile (by using the docker history command, as the repository it is not public) and it looks like remark is installed as a global npm package. I therefore would expect everything to work fine.

Maybe @prologic still has access to the prologic/remark-lint:latest and can share the original Dockerfile, so we can double-check what goes on.

@asbjornu Can you maybe also check the remark-cli that is installed in the action where you got the warning. It might be that in that version a dependency (plugin) was missing in the package.json but in the new version this is solved.

I don't have a repro available, but your test repo does not seem to have any Remark plugins. It's the plugins that fail loading, not Remark itself.

@asbjornu Good point, I missed the fact that you used plugins. I will run some new tests.

@asbjornu I reproduced your issue, I will write a fix now. I will send it to you for review later today.

@asbjornu I created a pull request in #43. Please review it and merge it if you think it is correct.


Don't allow publish with webm

These won't work on IOS devices. If we can't stop them from selecting webm, put a message up that it's not supported on all devices / link to the publishing guide.

These won't work on IOS devices

video.js should allow for playing webm's on all devices. Unless this is a limitation elsewhere

These won't work on IOS devices

video.js should allow for playing webm's on all devices. Unless this is a limitation elsewhere


docs: usage with Vue.component

📚 Is your documentation request related to a problem? Please describe.
Docs explain how to get vuex types in class components (levaraging TS's decorators). I was wandering whether class components are mandatory or is also possible using typed-vuex with component instantiated via Vue.component.
🔍 Where should you find it?
https://typed-vuex.roe.dev/getting-started-vue
ℹ Additional context
Thanks for the amazing job here. I'm considering introducing store types in a legacy project and I'm trying to figure out which supporting library would better fit our codebase.

@toomuchdesign It's definitely possible! Example here: https://typed-vuex.roe.dev/accessor-introduction#components-fetch-and-asyncdata - just ignore the Nuxt-specific bits if you're not using it.

Amazing! Looking forward to try it out. Thank you @danielroe!