text:
Libdoc can give misleading message when dealing with library

This problem was initially seen at:
https://github.com/robocorp/robotframework-lsp/issues/608
The language server tried to generate a libspec with a command line such similar to:
python -m robot.libdoc test_lib::path\to\x.txt out.libspec
and the error given was:
Resource file 'test_lib::d:\foo\x.txt' does not exist.
The same could happen if dealing with a library with a module which ends with .resource or .txt or .rest (libdoc tries to guess, but in this particular case, where the language server knows that it's dealing with a library import, the error for the Resource does not exist is always wrong).

Isn't it so that
python -m robot.libdoc test_lib::path\to\x.txt out.libspec

works if test_lib can be imported? If it cannot, then Libdoc thinks the whole test_lib::path\to\x.txt is actually a resource file and reports a misleading error because importing it fails?

Yes, that's correct. The error is just related to the misleading message -- on the happy path things work as intended ;)

Are you @fabioz fine with only fixing the problem that libraries with the last parameter having a valid resource file extension being detected wrong? That's easy and creating a test isn't hard either. I can do all this myself.
PR #4285 contains also a change that if we first try importing something as a library and then as a resource and neither works, we report both errors. That's a bit more complicated change and harder to test. I personally don't think it's worth the effort as long as the detection that is something a library or a resource isn't faulty. I actually think reporting both errors can be confusing and slightly prefer the current behavior. I don't mind changing it, though, but then the PR #4285 should be finished so that I can merge it.

I want to get this issue closed so I decided to fix this myself.

authors: fabioz pekkaklarck


text:
The Parser between a feature files and the corresponding step definition is not working smoothly when the " (double quotation mark) is present

VERSION INFORMATION
Robot framework version: Robot Framework 5.0 (Python 3.10.4 on win32)
Python version: Python 3.10.4
OS: Windows 10
THE PROBLEM
If 2 step definitions that use " character have similar definition the parser take both as identical.
2 steps definitions

The step definition invoked inside a feature file

The message error

CONCLUSION
We are thinking the " character sometimes is causing confusing during the parser about which text is limited by the double quotation marks.
The possible behavior highlighting how the parser might it be taking the steps definitions

No updates. Closing.

source: gharchive/issue

authors: OswaldGitHub pekkaklarck

repo: robotframework/robotframework

license_type: permissive

license_source: github-api


text:
Create appConfig for regional configuration

Overview
Enable regional configuration in the same repo.
The way it works is the developer sets their env var like NEXT_PUBLIC_REGION=sf, and that selects to include a whole bunch of different region-specific configuration values, specified in sf.js. This way non-secret configuration values can be committed to source code. And non-region-specific configuration values can also be shared in the default.js.
The motivation for doing this is to avoid maintaining a large and growing .env file outside of source control. Multiple developers working on the same project (like me and Rob in Tahoe) would need to share this file with each other outside of git, and in some reasonably secure way because it contains secrets. Also it would need to stay in sync with the individual configuration values in the Heroku web UI. Also, as I continue to add more and more region-specific configuration, I can update the values for all regions in one PR, instead of having to ask the maintainers of each instance of Bikesy to update their local environment files.
Suggested environment changes to accompany this PR

Different instantiations of bikesy are expected to set a new environment variable NEXT_PUBLIC_REGION to configure which regional config file it should use. If unset, I set the default value of this to 'sf', so that no changes should be needed to the Bikesy.com heroku environment in order to deploy this change.
But I would still recommend updating the environment, after deploy, to bring it inline with the suggestions in .env.example: setting NEXT_PUBLIC_REGION to sf, and removing all the other environment configurations that are not secrets.
I recommend doing the same thing for your local gitignored .env file too.

Testing:

Searched the repo for process.env and ensured that all remaining instances are expected secrets.
Tried querying for directions. Searching an address within my search bounds "worked" (no error message). Searching an address outside my search bounds yielded an error saying that the address is out of bounds.
Confirmed that with CONFIG=tahoe and NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN=<TahoeBike access token>, the map loads visually correctly.
Confirmed that with CONFIG=sf and NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN=<TahoeBike access token>, the map fails to load with a 404 from Mapbox in the console. Makes sense. I can't load bikesy styles with my access token. (And I don't have the bikesy access token)
Toggled the values of WELCOME_MODAL_TITLE and SHOULD_SHOW_WELCOME_MODAL and confirmed the expected behavior.
Make sure that routing generally works as expected
Remove NEXT_PUBLIC_REGION configuration and confirm things generally look right for SF.

The thing is, I'm planning to add in significantly more configuration options, basically amounting to the entire difference in features between bikesy.com and map.tahoebike.org. I worry that would be too much to store in environment variables. There would be lots of useful (non-secret) content stored outside of source control, and at risk of getting lost. It also seems like a lot to configure via the Heroku web UI, a burden to keep in sync with local local configuration for development.
For now, while there are only two regions using this application, I was envisioning that the configuration files for both Tahoe and SF would live in the bikesy repo. If a handful of other regions want to start using Bikesy, they could open a PR into the Bikesy repo with their local config file, or they could maintain a fork with their local config file. How would you feel about that?

@brendannee, I'm upgrading this from draft status and would like to ask if you're cool with merging it.
I updated the description with some of the rationale for storing configuration in source control. Being able to make easy small changes like this is what I'm really hoping this enables.

Replaced by https://github.com/brendannee/bikesy/pull/31

source: gharchive/pull-request

repo: robotnealan/bikesy-tahoe

license: MIT


text:
dynamic slack sink configuration for channel

Is your feature request related to a problem?
We would like to be able to configure the slack sink to match a label on a Finding so the slack sink can infer what channel to send a finding to.
Describe the solution you'd like
something like:

slack_sink:
name: slack-sink
slack_channel: alerts
api_key: xyz-abc
slack_channel_label_re_match: (team_slack_channel|slack_channel)

Describe alternatives you've considered
specifying a sink for every teams slack channel.  creating a custom sink that can make the api call to slack with a dynamic channel.
Additional context
none.

@mitch-mckenzie  this is now supported , for more info
https://docs.robusta.dev/master/configuration/sinks/slack.html#dynamic-slack-channels

authors: RoiGlinik mitch-mckenzie

repo: robusta-dev/robusta


text:
Revert "feat: replicache transaction"

Reverts rocicorp/repliear#148

LGTM

Why revert?

Why revert?

Repliear has a custom replicache-transaction.ts that included syncOrder that wasn't implemented correctly during the refactor.

authors: aboodman cesara grgbkr

repo: rocicorp/repliear


text:
🐛 plural instead of singular node

Minor typo

Thanks Mentor!

authors: actuallymentor jclapis


text:
Switch to 32-bit CAR algorithm

This PR covers implementation of

Store all Normal_GF values as array-of-32-bit integers, rather than 64-bit.
Covert GF "*" operation to only use 64-bit arithmetic where absolutely necessary
Recode Car.Product_To_Seminormal to take 64-bit GF as parameter but return 32-bit GF as result.
All other Car.* functions can be done in 32-bit arithmetic.

Proof OK.
Regression tests OK
Performance test, WCSU and code size analysis OK

repo: rod-chapman/SPARKNaCl


text:
sprint30

Lead time component and VideoGuide test .

please review

repo: rodekruis/IBF-system


text:
First signal update doesn't usually get listened to

I have this simple signal i've created to act as a flag/guard to do auth navigation
  @override
  Widget build(BuildContext context) {
    routerGuardSignal.listen(context, () {
      final isUserLoggedIn = routerGuardSignal.value;
      log(isUserLoggedIn.toString());
      while (navKey.currentState!.canPop()) {
        navKey.currentState!.pop();
      }
      if (isUserLoggedIn == true) {
        navKey.currentState!.pushNamed(MainScreen.routeName);
      } else if (isUserLoggedIn == false) {
        navKey.currentState!.pushNamed(LoginScreen.routeName);
      }
    });

this is placed under the material app build context
and from the splash screen i do my check and then i do
routerGuardSignal.value = true or false

sometimes this call make the listener cb invoked and sometimes not

It will only be called if the widget is mounted where the listener is created

I would suggest an effect outside of the build method to ensure it calling no matter what

It will only be called if the widget is mounted where the listener is created
But shouldn't the widget be mounted since this is the root widget ?

That should be the case, although I have had weird behavior before with the root widget being mounted.
Can you reproduce a minimal example to test? I'll added it to the widget tests to make sure it's valid.

What is the expected error and what steps do I need to do to reproduce it?
Also is it fixed with an effect or subscribe in initState?

Sorry for missing that
Steps to Reproduce

Run the code
wait for the app to open the splash screen
wait two seconds

Expected behavior: App navigates to main page route
Actual behavior: Gets stuck on splash screen

and i tried adding the effect in a separate function away from the context and it worked

Definitely sounds like a bug or implementation issue, I think I know what is causing it.

Any updates on this ?

Just got back from my honeymoon so will be looking at it soon!

Oh, Sorry man didn't know
Congratulations on your marriage bro!
On Thu, 23 May 2024 at 23:05, Rody Davis @.***> wrote:

Just got back from my honeymoon so will be looking at it soon!
—
Reply to this email directly, view it on GitHub
https://github.com/rodydavis/signals.dart/issues/266#issuecomment-2127932844,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ625GTB3SI7SQCMZMBNHE3ZDZD2NAVCNFSM6AAAAABHYRY3BCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRXHEZTEOBUGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Found a fix, and will include on the next update!

Just got back from my honeymoon so will be looking at it soon!

🎉 Congratulations, sir, on your marriage! 💍 Wishing you a lifetime filled with love, joy, and endless adventures together. May your journey as a married couple be as enchanting as a fairytale and as vibrant as the brightest stars in the sky. Here's to a future overflowing with happiness, laughter, and unforgettable moments! ❤

Thank you so much 🎉

authors: SPiercer iSaqibShafique rodydavis


text:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)

Environment Python 3 within Anaconda running on Mac OS X (v10.12.6)
The code in lesson5.ipynb for Pre-trained vectors, also found in wordvectors.ipynb doesn't work for me.
def load_vectors(loc):
    return (load_array(loc+'.dat'),
        pickle.load(open(loc+'_words.pkl','rb')),
        pickle.load(open(loc+'_idx.pkl','rb')))

vecs, words, wordidx = load_vectors('data/glove/results/6B.50d')

---------------------------------------------------------------------------
UnicodeDecodeError                        Traceback (most recent call last)
<ipython-input-14-f3d9d0357284> in <module>()
----> 1 vecs, words, wordidx = load_glove(res_path+'6B.50d')
      2 vecs.shape

<ipython-input-13-7df1842b2042> in load_glove(loc)
      1 def load_glove(loc):
      2     return (load_array(loc+'.dat'),
----> 3         pickle.load(open(loc+'_words.pkl', 'rb')),
      4         pickle.load(open(loc+'_idx.pkl','rb')))

UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)

I think I have found the solution to the above issue
def load_vectors(loc):
    return (load_array(loc+'.dat'),
        pickle.load(open(loc+'_words.pkl','rb'),encoding='latin1'),
        pickle.load(open(loc+'_idx.pkl','rb'),encoding='latin1'))

Great, let me know in case the issue is not solved.

authors: ihenry roebius

license_source: bigquery


text:
ZeroDivisionError: integer division or modulo by zero

[2021-01-26 13:19:37] [root                    ] [INFO    ] - Initializing...
[2021-01-26 13:19:37] [root                    ] [INFO    ] - Initializing NVR threads
[2021-01-26 13:19:40] [lib.camera.achtertuin   ] [WARNING ] - ffprobe failed to get stream information
[2021-01-26 13:19:40] [root                    ] [INFO    ] - Initialization complete
Exception in thread Thread-7:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/src/viseron/lib/camera.py", line 423, in capture_pipe
    if motion_frame_number % motion_decoder_interval_calculated == 0:
ZeroDivisionError: integer division or modulo by zero

my config:
# See the README for the full list of configuration options.
cameras:
  - name: achtertuin
    host: 192.168.178.113
    port: 554
    username: xxxx
    password: xxxx
    path: /
    stream_format: rtsp

# MQTT is optional
#mqtt:
#  broker: <ip address or hostname of broker>
#  port: <port the broker listens on>
#  username: <if auth is enabled>
#  password: <if auth is enabled>

fixed by adding height and width in the config

fixed by adding height and width in the config

Will take a look at this soon, closing as its a duplicate of #58

Will take a look at this soon, closing as its a duplicate of #58

authors: Sloth-on-meth roflcoopter

repo: roflcoopter/viseron


text:
Support of flexWrap

I can't see flexWrap in the supported properties list.
Is this supported and if not why?
Related https://github.com/callemall/material-ui/pull/2248

@oliviertassinari Now that you mention it.. Seems like I missed that one.
You can see all props here with their referencing caniuse-data keyword as key.
I will add this and update the prefixer today.

Perfect, thanks.

authors: oliviertassinari rofrischmann

repo: rofrischmann/inline-style-prefixer

license: mit


text:
Old version of embedded Chrome

Hi, can you create new version with latest chrome?
webpack: Compiled successfully.
[11:54:01] I/file_manager - creating folder /home/jenkins/workspace/dev-test/node_modules/webdriver-manager/selenium
[11:54:02] I/update - chromedriver: unzipping chromedriver_2.38.zip
[11:54:02] I/update - chromedriver: setting permissions to 0755 for /home/jenkins/workspace/dev-test/node_modules/webdriver-manager/selenium/chromedriver_2.38
[11:54:02] I/launcher - Running 1 instances of WebDriver
[11:54:02] I/direct - Using ChromeDriver directly...
[11:54:04] E/launcher - session not created exception: Chrome version must be >= 65.0.3325.0
  (Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Linux 4.13.0-1011-azure x86_64)
[11:54:04] E/launcher - SessionNotCreatedError: session not created exception: Chrome version must be >= 65.0.3325.0
  (Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Linux 4.13.0-1011-azure x86_64)
    at Object.checkLegacyResponse (/home/jenkins/workspace/dev-test/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/home/jenkins/workspace/dev-test/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/home/jenkins/workspace/dev-test/node_modules/selenium-webdriver/lib/http.js:440:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/home/jenkins/workspace/dev-test/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/home/jenkins/workspace/dev-test/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver (/home/jenkins/workspace/dev-test/node_modules/protractor/lib/driverProviders/direct.ts:90:25)
    at Runner.createBrowser (/home/jenkins/workspace/dev-test/node_modules/protractor/lib/runner.ts:225:39)
    at q.then.then (/home/jenkins/workspace/dev-test/node_modules/protractor/lib/runner.ts:391:27)
    at _fulfilled (/home/jenkins/workspace/dev-test/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/home/jenkins/workspace/dev-test/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/home/jenkins/workspace/dev-test/node_modules/q/q.js:796:13)
    at /home/jenkins/workspace/dev-test/node_modules/q/q.js:556:49
    at runSingle (/home/jenkins/workspace/dev-test/node_modules/q/q.js:137:13)
    at flush (/home/jenkins/workspace/dev-test/node_modules/q/q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)
[11:54:04] E/launcher - Process exited with error code 199
error Command failed with exit code 199.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Rebuild it and now includes Google Chrome 66.0.3359.139. Please, let me know if this solves your issue

Sorry I little forgot to this issue, but yes. Now i don't have to call apt-get install -y google-chrome-stable in my CI/CD test pipeline.
I'm gonna close this issue. Thx for quick response.

authors: jakubjosef rogargon


text:
Rewrite rbx_xml to use quick_xml instead of xml-rs

rbx-xml is slow and has trouble processing unicode, among other issues. This can and is solved by simply swapping to a new XML parser. Given the speed, I've decided to go with quick-xml.
Unfortunately, the current parser (xml-rs) is intertwined rather thoroughly with rbx-xml's implementation and swapping it out for quick-xml would be impossible without refactoring large segments of it. Given there's a few other design choices that I wanted to change, I decided to bite the bullet and go for a full rewrite. Initial testing is good and suggests we're looking at 15x the parsing speed in some cases. I have tried to prioritize not copying data when possible, so overall memory should also be low.
Update: This is mostly done now, I believe. Many many tests need to be written but the bulk of the code will not change. With that in mind, here are my thoughts beyond "reviewing this is a nightmare":

This rewrite fundamentally changes how the crate is laid out. Specifically, it's split serializer and deserializer into dedicated modules and the code for (de)serializing data types now lives under those modules. This differs dramatically from the current system we use that implements XmlType for each type and both deserialization and serialization in one place. In my opinion, this is easier to reason with but it is significantly different and may require us to point contributors in the right direction if they're used to the old system. Also, it means we have the potential for element name mismatches between serializing and deserializing. Testing will absolutely catch that, but it's something we didn't have to deal with before.

The deserializer now requires the referent attribute to be set on Item elements. I was very surprised to learn it was not before, but as a result this is also a breaking change. I don't think we should care though.

For posterity, here's a checklist of what needs to be done:

[x] Visit properties using the ReflectionDatabase
[x] Port data types
[x] Redo the serializer
[x] Run every test like a million times to ensure I didn't break anything

Rather than work out what work I'm missing since I started this rewrite, I'm going to close this and instead focus on a less invasive rewrite. I think it will result in a much faster turn around for the port, and in turn it should end up being easier to review. Sad to see my work go, but it will not die here.

repo: rojo-rbx/rbx-dom


text:
Release 3.3.0

Description
Please provide a summary of the pull request and the issue it fixes. Please add necessary details, context, dependencies, explanation of when review is needed (see next section), etc.
Fixes #(add issue number here and remove parentheses)
Review Time Estimate
Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

[ ] Immediately
[ ] Within a week
[ ] When possible

Type of changes
Please select a relevant option:

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Other (any another change that does not fall in one of the above categories.)

Checklist:
Please select all applicable options:

[ ] I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
[ ] I have updated the CHANGELOG.
[ ] I have read the Contributor Guidelines.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My change requires updating the documentation.
[ ] I have made necessary changes to the documentation.
[ ] I have added tests related to my changes.
[ ] My changes generate no new warnings.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

can you include 3.3.0 in security.md as well?

authors: bingzhang minump

repo: rokwire/events-manager


text:
colOutline should share same COLOR_A as colShape

https://github.com/rollraw/qo0-base/blob/92a3b3aefa220da941c3feee387702c772d1af82/base/utilities/draw.cpp#L612
https://github.com/rollraw/qo0-base/blob/92a3b3aefa220da941c3feee387702c772d1af82/base/utilities/draw.cpp#L622
https://github.com/rollraw/qo0-base/blob/92a3b3aefa220da941c3feee387702c772d1af82/base/utilities/draw.cpp#L627
https://github.com/rollraw/qo0-base/blob/92a3b3aefa220da941c3feee387702c772d1af82/base/utilities/draw.cpp#L632
https://github.com/rollraw/qo0-base/blob/92a3b3aefa220da941c3feee387702c772d1af82/base/utilities/draw.cpp#L637
https://github.com/rollraw/qo0-base/blob/92a3b3aefa220da941c3feee387702c772d1af82/base/utilities/draw.cpp#L648
Isn't colOutline.Set<COLOR_A>(colShape.Get<COLOR_A>()) better? Agree It's ugly to read but why would you want individual alphas?

current rendering system is very dumb at all, do not think we need to do anything with it now. also i had rework it in v2


text:
Improve dist

rename .es.js to .esm.js
removed jsnext:main
simplified rollup config

It seems that the tests are now failing, could you please take a look?
Error: Cannot find module './preflightCheck.js'

I don't have an idea what's wrong with windows :)

Done

authors: TrySound xtuc

repo: rollup/rollup-plugin-babel


text:
Added nicknames and dump-image-init (like dump-image but with an unit function)

Added nicknames and dump-image-init (like dump-image but with an unit function)

Thank you for the pull request.
Sorry I took so long to merged it, I didn't received an email saying that there was a pull request waiting.
If in the future you find that trivial-dump-core is missing some functionality you can also take a look at the UIOP library. This library is usually bundled with the lisp implementation that have ASDF built-in and has some image dumping functionality (see https://github.com/fare/asdf/blob/master/uiop/image.lisp#L325-L342 ) that supports more implementations than trivial-dump-core.

authors: Matceporial rolpereira

repo: rolpereira/trivial-dump-core


text:
Issue with React Router v4

Whenever I put <Link> inside the tooltip I get this error:
You should not use <Link> outside a <Router>
Can you please tell how to fix the this?

Latest react still works with react-portal-tooltip@2.4.0.

I believe it was this change that broke it.

@pocketjoso It's caused because it renders outside of the root, so yes you are correct, the router is not in the parent dom tree according to the tooltip.
using the createPortal api might work. Update here once you've had the chance to experiment with it -- I'll be sure to review the PR.

@Redmega Yeah using the portal api will work, I tested the basic functionality after making this minimal change:
https://github.com/pocketjoso/react-portal-tooltip/commit/0f59dddf41235eafdcfa643a396e121d56725bdf
However I feel hesitant to do a PR for it, as some more code needs to be refactored. This is because the portal rendering now happens in the (react) render function, rather than in your own renderPortal class method. I believe the latter method should be removed completely now, but first the code responsible for only hiding the tooltip after the given tooltipTimeout option would need to be rewritten:
https://github.com/romainberger/react-portal-tooltip/blob/master/src/index.js#L419-L425
it needs to work a bit differently now, probably setting state.
Do you reckon you can push a fix for this instead?

The portal api works but does not produce the same result as the current implementation. Currently a single tooltip is created for all the parents, where the portal api will create multiple tooltip, so it breaks the idea of a single tooltip moving.

True. Is it more important to you to preserve that functionality than to allow the components to stay in the same react dom tree? I'm not sure going forward that these two separate goals will ever be possible for a single component to satisfy at the same time. So would be good to know what the stance is for this library, as this issue is a deal-breaker for us.

I guess potentially it could be an option in the library, so the consumer could chose what is important to them, but it would make the code a bit heavier and more messy.

I initially made this component exactly for this behavior of a single floating tooltip, so I would definitely keep it that way. I understand the lack of context is an issue and there should be a search for a fix if possible.
But if it's not possible and it means the death of this component, than I'd rather see it deprecated than transformed into yet-another tooltip component. I think there are enough of these available to fill every need.
I'm sorry if this means you'd have to migrate to another library, unfortunately I can't for now work on a fix, so I can't say when it will be fixed, if ever.

I initially made this component exactly for this behavior of a single floating tooltip, so I would definitely keep it that way. I understand the lack of context is an issue and there should be a search for a fix if possible.
But if it's not possible and it means the death of this component, than I'd rather see it deprecated than transformed into yet-another tooltip component. I think there are enough of these available to fill every need.
I'm sorry if this means you'd have to migrate to another library, unfortunately I can't for now work on a fix, so I can't say when it will be fixed, if ever.

I can fully understand you vision and you are right, keeping this as a simple tooltip is a good idea, I opened this issue and then asked myself but why it would do that?! 😄
And thank you for this library!

Yeah thanks for explaining your position - it helps. And thanks as well for providing the library! 👍

authors: Ggayane Redmega pocketjoso romainberger

repo: romainberger/react-portal-tooltip


text:
css loaders

Hi, I have a case where in main.js, css is imported. So during the build, the setup looks like this
module: {
  loaders: [{
    test: /\.css$/,
    include: [POSTCSS_SRC_DIR],
    loader: ExtractTextPlugin.extract('style', 'css?root=..!postcss')
  },{
    test: /\.js$/,
    include: [JS_SRC_DIR],
    loader: 'babel-loader'
  }]
},
plugins: [
      new ClosureCompilerPlugin({
      compiler: {
        language_in: 'ECMASCRIPT6',
        language_out: 'ECMASCRIPT5_STRICT',
        compilation_level: 'ADVANCED',
      },
      concurrency: 3,
    })
]

And it gives me error:
ERROR in ./src/css/main.css
Module build failed: TypeError: text.forEach is not a function

seems like the plugin doesn't take any non js files extracted by ExtractTextPlugin. Is there any way to ignore css files or work around this issue?
Thank you!

having the same issue here~~

Fixed and published as v2.0.2. I've added test option where you can specify a pattern for file names which should be processed, default is /\.js($|\?)/i.
        new ClosureCompilerPlugin({
          test: /\.js($|\?)/i,
          compiler: {
            language_in: 'ECMASCRIPT6',
            language_out: 'ECMASCRIPT5',
            compilation_level: 'ADVANCED'
          },
          concurrency: 3,
        })

authors: DekusDenial Maxlufs roman01la


text:
Search won't execute

Hey Roman!
I'm pretty sure I have everything configured properly…but I'm not a developer or ES expert…but when I go to /_plugin/calaca - and the page opens just like your demo - and type a word in the search box, and hit return, nothing happens.
Running on Ubuntu 14.04, mariadb 10.x, php5.9, 73K posts in the index, ElasticSearch is working fine.
I can see the changes I made in the index file when I reload the page - it appears briefly:
results.post_title (is in red)
results.post_id (in black)
And I edited the .yml as instructed and then researched around, thinking I missed something, and put in the following:
http.cors.enabled: true
http.cors.allow-origin: /.*/
http.cors.allow-credentials: true
Any idea what I'm doing wrong?
Thanks for any help!
Rob

Using the keyboard shortcut Command + Option + J (Mac) or Control + Shift + J (Windows/Linux) to open the Console(in Chrome), do you see any errors being displayed?

Very cool - I didn't know about that on the mac - thanks ;)
And yes - connection errors…ah…I had the config.js set to "localhost:9200"!
Changed it to the ip and it works.
But not getting results…not getting any errors! - but no results…like it doesn't see the index.

Okay - leaving that screen up it timed out and I saw it - I had the wrong index listed in the "type" section.

This is very fast Roman - awesome man, thanks!
I have about a million questions on how to configure the results but I'll contain myself and ask just one - how can I make the results a link? For instance the "post_title" that is coming up results - can that be made clickable/hyperlinked to the article?
Thanks again Roman!

Absolutely, you can format results however you like. If you want to display your title as a link, you can do something like below.
If your elasticsearch data looks something like this:
{
  "title":"Gravity",
  "url":"http://mybooks.com/gravity"
}

then you can modify the index.html to display it like this:
{result.title}

Ah - that's easy! So, just to be sure, I can add anything to the results using the {result.sourcename} as long as it's part of the ES document? And it's all easy enough to format…this is slick stuff Roman - thanks again!
Rob

Yup, that's right.

repo: romansanchez/Calaca


text:
Avoid direct call to M.throttled_update_context() from M.setup()

See details in #69

Sorry, after reviewing the PR I felt like this fix wasn't adressing the root issue. I've added a fix to avoid calling .enable() if .setup({ enabled = false }) is called by the user. Let me know if the issue still appears for you.

I see, your fix looks very sound, it works well, thanks!

authors: lyokha romgrk

repo: romgrk/nvim-treesitter-context


text:
🛑 Rompslomp API is down

In 5614cc8, Rompslomp API (https://api.rompslomp.nl/api/v1/me) was down:

HTTP code: 401
Response time: 475 ms

Testing uptime

Resolved: Rompslomp API is back up in 913e3d1 after 3 hours, 21 minutes.

repo: rompslomp/uptime


text:
HDTime 不显示做种体积

PT 助手版本:d1e8200

PT 助手安装方式：zip

浏览器名称及版本：edge

浏览器是否安装了其他插件：

停用其他插件后是否正常工作：

问题描述：
无法获取到hdtime的做种体积

相关截图：

重现步骤：

之前修过 不清楚是界面又有改版还是语言设置之类的问题

https://github.com/ronggang/PT-Plugin-Plus/pull/1089
https://github.com/ronggang/PT-Plugin-Plus/pull/1131
而且都修过两次了..

#1089 #1131 而且都修过两次了..

我感觉应该能获取到的

我想问问这个query是jquery吗query.text()包含html标签吗

query是selecter获取到的jquery结果，.text()就是输出文本

看下这个commit有没有修好
https://github.com/ronggang/PT-Plugin-Plus/commit/522d241c2631805ec2dd6b043abc01e7a3c44321#diff-4ca9589c5d865ed6259c2a36ba0cadcb8352dc0245cf1aac6b6c98a9f3333c72

repo: ronggang/PT-Plugin-Plus


text:
下载所有种子文件/All Torrents只下载到php文件

PT 助手版本: v1.2.2

PT 助手安装方式：Firefox addon 商店

浏览器名称及版本：Firefox 69.0 (64-bit), Arch Linux

浏览器是否安装了其他插件：是

停用其他插件后是否正常工作：否

问题描述：
在种子列表页面（默认种子第一页）使用“所有种子/下载所有种子文件”按钮下载本页种子时，会出现各种问题，如下载到的都是php页面本身，如"download.php"或"torrents.php"。
在尝试的所有网站中，包含NexusPHP/Gazelle/AvistaZ/Unit3D/IPT等站点或者架构，结果如下：

只有IPT是正常下载的，因为IPT的下载链接是种子直链
Unit3D框架的链接是直链，但链接是“种子名.种子ID”，所以下载到的虽然是种子，但是文件名也是“种子名.种子ID”，而不是点击下载按钮（指种子本身的）而下载到的“种子名.torrent"
其他框架和站点如NexusPHP/Gazelle/AvistaZ下载链接是类似"xxx.php?参数"的情况，下载到的就只有php文件本身

相关截图：

重现步骤：

禁用其他所有插件，重启浏览器
打开网站（如UHDBits）种子页
等待网页和插件加载完毕，点击“所有种子”按钮
得到所有文件都是torrents.php

看起来更像是firefox的‘feature’，我们这边无能为力，建议向firefox那边反应。
插件调用下载命令是浏览器默认的下载方法，在chrome上是 chrome.downloads.download()
文档： https://developer.chrome.com/extensions/downloads#method-download
我在Firefox的插件的背景页手动调用 chrome.downloads.download() （ff在插件层面提供chrome对象兼容） 以及 bowser.downloads.download() (ff自带的WebExtension方法， 文档： https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/downloads/download ， 文档最后说This API is based on Chromium's chrome.downloads API. ) 得到的表现均是问题描述现象。
此外，调大 about:config 中broser.download.saveLinkAsFilenameTimeout 无助于解决问题。
只能认为在 chrome.downloads.download() 这个方法上，ff的实现不能从请求响应的Content-Disposition头中自动获取文件名信息。
由于我们无法在options中添加filename键值对（种子文件名在请求响应的Content-Disposition头中），所以只能建议换用chrome内核浏览器。

所以按我的理解，这只是Unit3D框架站点文件名问题的原因，那最有问题的第三种情况，只下载到php文件又是什么原因呢？

不是，ff只是简单的把下载链接中的文件名作为下载保存的文件名，例如：
https://xxxx.com/download.php/xxxx/1.torrent  -> 1.torrent
https://xxxx.com/download.php?id=xxxxx          -> download.php

通过翻阅ff的相关bugtracker，特别是  https://bugzilla.mozilla.org/show_bug.cgi?id=1579456
以及相关
https://bugzilla.mozilla.org/show_bug.cgi?id=1245652
https://bugzilla.mozilla.org/show_bug.cgi?id=1424502

目前只能建议：

更换浏览器为chrome内核浏览器；
使用IDM等类似下载工具 监听/劫持 Firefox的下载动作。

嗯，谢谢详细的调查，这个8天前的bug甚至正好能够针对这个问题。但是看之前的bug report，感觉近期不会解决了。

感谢理解，那这个issue先做close处理了

authors: OliverLew Rhilip


text:
fix: notfound in wrong place #342

Description
path was wrong for the not-found file

Related Issue
closes #342

Motivation and Context

fix the issue in #342
How Has This Been Tested?
ran it locally

Screenshots (if appropriate):

fyi @Savinvadim1312

repo: roninoss/create-expo-stack


text:
Feature/dashboard sdk

Summary
Make sure it works first.
Use tsup instead of vite packaging to solve the problem of not running in node environment.
However, it is worth noting that there may still be some remaining issues. For instance, warnings may be encountered when using certain frameworks, particularly those that do employ Server-Side Rendering (SSR).
Summary about this PR

Closes #issue

I tried vite, esbuild, tsup
Always encounter node environment or browser environment conflict
@yubing744 Do you have any suggestions?

repo: rooch-network/rooch


text:
🛑 TROJAN 🇬🇧 United Kingdom UKO 1 is down

In cda46c9, TROJAN 🇬🇧 United Kingdom UKO 1 (https://ukt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKO 1 is back up in 0068a22.

repo: roosterkid/opentunnel-status-server


text:
🛑 V2RAY 🇺🇸 United States USF 2 is down

In 3f2db68, V2RAY 🇺🇸 United States USF 2 (https://usv-2.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇺🇸 United States USF 2 is back up in 40f0f87.


text:
🛑 TROJAN 🇩🇪 Germany DEH 1 is down

In a4af87c, TROJAN 🇩🇪 Germany DEH 1 (https://det-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇩🇪 Germany DEH 1 is back up in b4e32ca.


text:
🛑 TROJAN 🇭🇰 Hong Kong HKE 1 is down

In b2f8284, TROJAN 🇭🇰 Hong Kong HKE 1 (https://hkt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇭🇰 Hong Kong HKE 1 is back up in b0ff2b3.


text:
🛑 V2RAY 🇸🇬 Singapore SGF 3 is down

In 6735e46, V2RAY 🇸🇬 Singapore SGF 3 (https://sgv-3.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇸🇬 Singapore SGF 3 is back up in 8843baf.


text:
🛑 TROJAN 🇸🇬 Singapore SGV 1 is down

In cf13057, TROJAN 🇸🇬 Singapore SGV 1 (https://sgt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGV 1 is back up in 2dc96cc.


text:
🛑 TROJAN 🇮🇩 Indonesia IDJ 1 is down

In 0095ac5, TROJAN 🇮🇩 Indonesia IDJ 1 (https://idt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇮🇩 Indonesia IDJ 1 is back up in c12c9de.


text:
🛑 TROJAN 🇭🇰 Hong Kong HKE 1 is down

In 621c05d, TROJAN 🇭🇰 Hong Kong HKE 1 (https://hkt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇭🇰 Hong Kong HKE 1 is back up in e740d51.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKO 1 is down

In 5fd0d16, TROJAN 🇬🇧 United Kingdom UKO 1 (https://ukt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKO 1 is back up in 20e1b0e.


text:
update 1.4 to 1.5 without new SD card because pi is more than just a node

hi everybody, is there a way to update 1.4 to 1.5 without writing a fresh SD card with 1.5 because my rpi4 is more than just a RaspiBlitz
i have also wireguard, Homebridge and pi hole on it and don't want to set up everything from scratch.
thank you in advance

There is no clean way  - maybe just update LND and Bitcoind manually with scripts by openoms - but basically you stay at v1.4.
See background on this here: https://github.com/rootzoll/raspiblitz/blob/master/FAQ.md#why-do-i-need-to-re-burn-my-sd-card-for-an-update

Thanks for the answer. Unfortunately I read that already and Still hoped to get a hackY script.
Can I execute the Manual build Script on that 1.4 pi?
Is there an upgrade way from Version 1.5 for the future releases or will it always be like this?

Is there an upgrade way from Version 1.5 for the future releases or will it always be like this?

This is the upgrade way ... its the idea: if you add personal extra apps to it, that you take care of making them update secure: make yourself a small install script and store important data that should survice an update to mnt/hdd/app-data

Can I execute the Manual build Script on that 1.4 pi?

I never tried - if you feel lucky, give it a try and report back.

TODO: Make it possible that the user can set a custom-installs.sh script in the app-data folder that gets called on upadtes with a fresh sd card. This way at least someone can automize to make custom installs in the pi re-done on on a update.

ok, so I did "wget https://raw.githubusercontent.com/rootzoll/raspiblitz/master/build_sdcard.sh && sudo bash build_sdcard.sh" after I stopped bitcoind and lnd and it went through. nice :)
after the reboot I still see version 1.4 on the blue screen. now I wait until bitcoin is fully started

hmm, tor is somehow "broken": 2020-06-15T21:34:15Z connect() to 127.0.0.1:9050 failed after select(): Connection refused (111)
if I untick TOR in services and do a reboot I have a running bitcoind. if I tick/ activate TOR again, I get the above error

ok i figured it out and updated to 1.5.1, will try this again to version 1.6 and further, will report back. its possible, but with a lot of tinkering. still, thus I learn a lot how raspiblitz is made, very handy to support here in the future

@rootzoll Can this be added to the future release collector? I think it is important to update with flashing the sd card.

@nyxnor There is already a way to add custom installs script to run on a new update - see: https://github.com/rootzoll/raspiblitz/blob/v1.7/FAQ.md#why-do-i-need-to-re-burn-my-sd-card-for-an-update is there anyting more you want from this issue?

@rootzoll Can close this.

authors: nyxnor phenomeus rootzoll

repo: rootzoll/raspiblitz


text:
detect c-lightning wallet locked

In the systembackgound scan thats feeding the status cache c-lightning is seen as always unlocked - this needs to be implemented for v1.8

Currently the locked state causes the general error ERROR_TALKING_TO_LIGHTNINGD and exits with error code 2:
https://github.com/ElementsProject/lightning/blob/3d8293dbf40d2d940a89850ecc87b8c6e1fa0772/cli/lightning-cli.c#L26

ich bekomme genau den gleichen fehler
still at 98% sync
autounlock is enabled
can i edit c-lightning/config to point towards 9735 instead of 9736 or is it supposed to be that way,  ..in a node with both it and lnd.
# lightningd configuration for bitcoin mainnet
network=bitcoin
announce-addr=127.0.0.1:9736
log-file=cl.log
log-level=info
plugin-dir=/home/bitcoin/cl-plugins-enabled
# Tor settings
proxy=127.0.0.1:9050
bind-addr=127.0.0.1:9736
addr=statictor:127.0.0.1:9051/torport=9736
always-use-proxy=true
i guess only one of them runs at any one time anyways, so technically i could but that means i'd have to edit all port entries in .lightning/config
and add ufw 9736/tcp allow entry, there isn't one.
i couldn't say it got temp 'fixed' by enabling LND instead.
but still occasionally getting statuscheck error code 124

@maximlomans please open a new issue for this as you question is not related here.
(you can't run LND and c-lightning on the same port,  but can edit the c-lightning port to.9735 if LND is deactivated )

added the detection from logs, but keeping the v1.8 milestone as in the next c-lightning release will be able to support to specific exit code introduced in https://github.com/ElementsProject/lightning/pull/4908

Worked on my testing machine ... closing issue for v1.8.0 release.

authors: maximlomans openoms rootzoll


text:
Smoothly update pose of point cloud on update()

This is the migration of #1652 to the melodic branch. The PR addresses the problem that a point cloud isn't smoothly moving if its frame_id is moving w.r.t. rviz' fixed frame.
The solution was to update the pose of the corresponding scene node in each update() cycle, not only when the message was received.

I had to revert this PR due to issues in normal uses cases: #1666.

repo: ros-visualization/rviz


text:
ROS_PACKAGE_PATH is sometimes backwards

I don't yet know how to reproduce this, but I thought someone might have ideas about what would cause it.
Some of our users complain that sometimes when they build a big catkin project, their ROS_PACKAGE_PATH ends up backwards, like:
/opt/ros/groovy/share:/opt/ros/groovy/stacks:/home/myaccount/myproject/src

This causes lots of trouble, since myproject is now an underlay of ros groovy instead of an overlay.
Looking in the project's devel/_setup_util.py includes this line:
CMAKE_PREFIX_PATH = '/opt/ros/groovy;/home/myaccount/myproject/devel;/home/myaccount/myproject/devel'.split(';')

I did not set up this project dir initially, so I don't know what the circumstances were.  Obviously it is possible that someone explicitly set the CMAKE_PREFIX_PATH to that backwards path and then ran catkin_make, but I doubt it.
Advice appreciated.

I had the same problem and the reason was because I had ros installed on /opt/ros/ and also had the code of ROS (from source) on my ~/catkin_ws/src.
After remove "ros" from ~/catkin_ws/src, run catkin_make again on ~/catkin_ws and open a new terminal, everything went fine.
So, if anyone see this problem again, maybe is because you have two ROS Versions.

authors: hershwg rubenalvesbcn

repo: ros/catkin


text:
Is it possible to build both ros1 melodic and ros2 foxy into the same image?

Is it possible to build both ros1 melodic and ros2 foxy into the same image?

Currently it's not possible, but we had plans to allowit: https://github.com/ros/meta-ros/wiki/Superflore-OE-Recipe-Generation-Scheme/f2123c4043a6b13f9efc4312991144c5e5e4963d#defer-until-ros_superflore_generation_scheme-3 .

authors: herb-kuta-lge yiyibst

repo: ros/meta-ros


text:
Scarthgap mcap zstd

Update revision and delete outdated files.
{jazzy}: update revision and patch for mcap-vendor

ERROR: mcap-vendor-0.26.1-2-r0 do_fetch: Fetcher failure:
Unable to find revision af39b2f386c10c86cd74f4f78c908e46a0b0ae66
in branch release/jazzy/mcap_vendor even from upstream

{jazzy}: rosbag2-compression-zstd: remove outdated patch

'stdout: Applying patch 0001-CMakeLists.txt-drop-dependency-on-zstd_vendor.patch
patching file CMakeLists.txt
Hunk #1 succeeded at 24 with fuzz 2 (offset -1 lines).
Hunk #2 succeeded at 37 with fuzz 2 (offset -2 lines).
Hunk #3 FAILED at 60.
1 out of 3 hunks FAILED -- rejects in file CMakeLists.txt
Patch 0001-CMakeLists.txt-drop-dependency-on-zstd_vendor.patch does
 not apply (enforce with -f)

Merged fix for mcap-vendor
Refreshed integration patch for rosbag2-compression-zstd instead of removing the patch
Both pushed to scarthgap-next

authors: jiaxshi robwoolley


text:
no match for 'operator==' error

I've encountered such an error when compiling ros2 humble. It looks rcputils::fs::path operator error but the operator seems compiled through colcon build.

Starting >>> rcpputils
Starting >>> rosidl_runtime_c
--- stderr: orocos_kdl_vendor
Cloning into 'orocos_kdl-507de66'...
HEAD is now at 507de66 Fix CMake warning on Windows (#392)
Submodule 'python_orocos_kdl/pybind11' (https://github.com/pybind/pybind11.git) registered for path 'python_orocos_kdl/pybind11'
Cloning into '/root/xarm/ros2_humble/build/orocos_kdl_vendor/orocos_kdl-507de66-prefix/src/orocos_kdl-507de66/python_orocos_kdl/pybind11'...

Finished <<< orocos_kdl_vendor [56.3s]
Starting >>> python_orocos_kdl_vendor
Finished <<< python_orocos_kdl_vendor [2.23s]
Finished <<< rosidl_runtime_c [15.1s]
Starting >>> rosidl_runtime_cpp
Starting >>> rosidl_generator_c
Starting >>> rmw
Starting >>> rosidl_typesupport_introspection_c
Finished <<< rcpputils [16.9s]
Starting >>> rcl_logging_interface
Starting >>> libyaml_vendor
Starting >>> class_loader
Finished <<< rosidl_typesupport_introspection_c [6.88s]
Finished <<< rosidl_generator_c [10.9s]
Finished <<< rcl_logging_interface [10.3s]
Starting >>> rcl_logging_noop
Starting >>> rcl_logging_spdlog
Finished <<< rcl_logging_noop [1.88s]
--- stderr: libyaml_vendor
Cloning into 'libyaml-0.2.5'...
HEAD is now at 2c891fc Changes for v0.2.5 release

Finished <<< libyaml_vendor [13.0s]
Finished <<< rosidl_runtime_cpp [15.0s]
Starting >>> rosidl_generator_cpp
Starting >>> rosidl_typesupport_introspection_cpp
Finished <<< class_loader [18.5s]

Starting >>> pluginlib
Finished <<< rosidl_typesupport_introspection_cpp [6.20s]
Finished <<< rcl_logging_spdlog [10.2s]
Finished <<< rmw [27.9s]
Starting >>> rcl_yaml_param_parser
--- stderr: pluginlib
In file included from /root/xarm/ros2_humble/src/ros/pluginlib/pluginlib/include/pluginlib/class_loader.hpp:334,
from /root/xarm/ros2_humble/src/ros/pluginlib/pluginlib/test/utest.cpp:33:
/root/xarm/ros2_humble/src/ros/pluginlib/pluginlib/include/pluginlib/./class_loader_imp.hpp: In member function ‘std::string pluginlib::ClassLoader::getPackageFromPluginXMLFilePath(const string&)’:
/root/xarm/ros2_humble/src/ros/pluginlib/pluginlib/include/pluginlib/./class_loader_imp.hpp:589:39: error: no match for ‘operator==’ (operand types are ‘rcpputils::fs::path’ and ‘rcpputils::fs::path’)
589 |     if (parent.string().empty() || (p == parent)) {
|                                     ~ ^~ ~~~~~~
|                                     |    |
|                                     |    rcpputils::fs::path
|                                     rcpputils::fs::path
make[2]: *** [CMakeFiles/pluginlib_utest.dir/build.make:63: CMakeFiles/pluginlib_utest.dir/test/utest.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:187: CMakeFiles/pluginlib_utest.dir/all] Error 2
make: *** [Makefile:141: all] Error 2

Failed   <<< pluginlib [7.80s, exited with code 2]
Aborted  <<< rcl_yaml_param_parser [2.20s]
Aborted  <<< rosidl_generator_cpp [24.5s]
Aborted  <<< fastrtps [2min 41s]
Aborted  <<< rviz_ogre_vendor [4min 14s]

Summary: 139 packages finished [4min 39s]
1 package failed: pluginlib

Does anyone know how to solve it?
Thank you.

Based on your file paths, I'm guessing you're trying to build Humble in a 20.04 container which I am doing too and I saw the exact same error. It was because I forgot to remove the Foxy versions of packages on the AMENT_PREFIX_PATH. So I believe pluginlib was compiling against the wrong version of rcpputils.

Given the latest comment here, I'm going to close this out.  If you are still having problems, please feel free to reopen.

authors: clalancette jdlangs k-ish0212

repo: ros/pluginlib


text:
Many Xenial entries are being dropped

I just noticed that many Ubuntu Xenial entries are being dropped.  Looking at the ROS metrics: https://metrics.ros.org/packages_linux.html this will impact a significant portion of the community?  Is this intentional as a way to force these users to newer distros or to force them forking rosdep?

this PR https://github.com/ros/rosdistro/pull/31552 is breaking many dependencies...
Our robot is still running in Indigo and Kinetic.
We want to upgrade but we have no time to do it.

Is this intentional as a way to force these users to newer distros or to force them forking rosdep?

There was no nefarious or explicit intent to break things or push people into upgrading. The changes to the rosdep db were made during infrastructure bootstrap of a new platform with a cleaner-than-we-found-it maintenance policy.
The ROS team is preparing for the upcoming release of Ubuntu 22.04 Jammy which is the supported Ubuntu distribution for the upcoming ROS 2 Humble Hawksbill release. In order to work on ROS 2 on Jammy (and Debian Bullseye), we need to update the rosdep database. Keys which are defined for all Debian or Ubuntu distributions should be valid for all currently supported distributions. As Debian and Ubuntu phase out Python 2, many Python 2 packages are no longer being packaged in Ubuntu Focal and Jammy, or Debian Buster and Bullseye. As a result, there were several cases such as #31554 and #31552 where I needed to expand the collapsed key (i.e. ubuntu: [python-lxml]) key to explicitly exclude Jammy.
When doing so, I made sure that expanded entries were present for currently supported distributions that have the package available. Since community support for Ubuntu Xenial ended in April, I did not add entries for it in order to keep the expanded definition in its minimally valid form.
Based on the reports from #31570  #31580  and in this issue I've opened #31613 and will be either holding or updating the currently in-review pull requests which make similar changes to temporarily limit further changes affecting Ubuntu Xenial.
However I do not think it is sustainable for the ROS team to indefinitely maintain an accurate rosdep database that includes unsupported platforms. So I'd like to work with the affected parties to settle on an alternative.
@cottsay's recommendation to use rosdep sources from an earlier commit remains the best option I see for a static Kinetic project and we can add a few release policies to the rosdep db project to tag just before dropping support for a platform so that there is a named target for running rosdep on unsupported platforms using the last set of official sources to support it.
Since rosdep allows multiple sources, this also means that projects which may be actively developing and introducing new dependencies on an unsupported platform may add additional custom sources to expand upon the snapshot of the official rosdep db without requiring any modifications to it. I mentioned in this comment that I think this approach represents the minimum amount of maintenance work required overall even if it shifts some of that maintenance work onto the projects using unsupported distributions.

The python-numpy package is not present in Ubuntu Jammy. You can see the package listed for focal and bionic but it is not present in jammy (link 404s) because the python2 version of the package has been dropped. If we left the key defined for all Ubuntu distributions then attempts to use rosdep for packages defining those platforms would result in package installation failures rather than correctly reporting that the key has no definition for that platform.

python-numpy key is not found in Ubuntu Jammy, rosdep cannot install it in Jammy and raise key errors.
So I think there is no necessity to remove the existing xenial key from ros/rosdistro, but is my understanding incorrect?
Is there difference between the situation rosdep cannot find python-numpy key in ros/rosdistro, and the situation that rosdep cannot install python-numpy resolved from the key python-numpy.
For me, it seems both two are catched as install error by rosdep.
I understand that adding new keys for xenial should not be acceptable.
Tagging is the gread idea, I think.

Dropping Xenial rules at this point is expected and is not something that we should be avoiding. If someone was to take the time to clean up all the xenial rules today and simplify all the rules which xenail requires a special case for I would likely approve such as PR in my role as a reviewer.
We officially supported Xenial until it's EOL date which was well over half a year ago. And the Xenial support window was clearly advertised as being 5 years ending in April 2021. The reason that we have support periods is to scope the amount of work that we have to do. Maintaining the rosdep database is a non-trivial effort that we do to support the entire community.
We no longer support Xenial so that we can spent that effort on current and upcoming distros. In this case as we're making the updates for Jammy we are taking the opportunity to clean up old rules on unsupported platforms that will safe effort in the future. We could do a policy of never removing them, but that would end up with a weird state of things partially work, but can't be expected to work in all cases and so really it would just be a bad experience and people wouldn't really know if it's supported or not.
Along similar lines the packages in the apt-repository are subject to removal at any point now too. We do not want to continue host them on our high bandwidth CDN network and have our data requirements infinitely grow. We've provided continuing facilities because it was easier to not turn them off immediately and gives users a small grace period but if users take advantage of that extra period doesn't mean that we shouldn't turn it off as previously announced.
It does sound a little harsh, but we should not be spending effort to support users who are choosing to use an unsupported OS with an unsupported version of ROS. If the user makes this choice not to migrate forward, it is there responsibility to provide all the necessary infrastructure that was previously provided by the support platform.
We obviously do not want to leave users who cannot upgrade for whatever reason in the lurch. We have the snapshot repositories for people who want to be able to reproduce old package installations. And we make tags of the rosdistros for all syncs now. I'd recommend those working on xenial to consider using the latest kinetic tag. If a user needs new or updated rules for any other reason. The rosdep database can be forked for their own purposes or augmented with additional rules and it won't slow down the preparations for the next supported release and ongoing improvements for the currently supported releases.

@tfoote , @nuclearsandwich  I fully understand and support your arguments to move on.  Before I would like to close the issue I would like to double check if I got the proper resolution correct.
We create a self-maintained rosdep list file (10-ros-kinetic.list) with the following contents (afaiu it needs to start with a number smaller than 20 to make sure that its definitions will overlay on the default definitions) :
yaml https://raw.githubusercontent.com/ros/rosdistro/kinetic/2021-05-11/rosdep/base.yaml
yaml https://raw.githubusercontent.com/ros/rosdistro/kinetic/2021-05-11/rosdep/python.yaml
yaml https://raw.githubusercontent.com/ros/rosdistro/kinetic/2021-05-11/rosdep/ruby.yaml

Can we still rely on https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml to provide the released kinetic packages, or is it safer to add it in the above list file as well?
On top of that we should update our apt sources files to point to snapshots.ros.org instead?
deb http://packages.ros.org/ros/ubuntu/ xenial main --> deb http://snapshots.ros.org/kinetic/2021-05-11/ubuntu/ xenial main

Yeah, the rosdep sources like that look correct. You may end up wanting to have your own lines added too.

Can we still rely on https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml to provide the released kinetic packages, or is it safer to add it in the above list file as well?

I don't think that we've ever talked about a migration path for the rosdistro cache and have at least put in the EOL status so it's probably be best recommendation to keep the production one for now. It's not a large resource sink so it's likely easier to keep it there than officially migrate it.

On top of that we should update our apt sources files to point to snapshots.ros.org instead?
deb http://packages.ros.org/ros/ubuntu/ xenial main --> deb http://snapshots.ros.org/kinetic/2021-05-11/ubuntu/ xenial main

Yes definitely switch over to use the snapshots. This is what we do in the official final docker images too. They will disappear from the main repository at some point in the not too distant future. Note that the snapshot repository also has a different gpg key too when you set it up.

As I don't think that there's anything we're still tracking on this I'm going to close it out. @smits Please let us know if you hit any corner cases that are problematic on using the snapshots.

authors: knorth55 nuclearsandwich smits tfoote

repo: ros/rosdistro


text:
teb_local_planner: 0.4.3-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository teb_local_planner to 0.4.3-0:

upstream repository: https://github.com/rst-tu-dortmund/teb_local_planner.git
release repository: https://github.com/rst-tu-dortmund/teb_local_planner-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.21
previous version for package: 0.4.2-0

teb_local_planner
* Changed the f0 function for calculating the H-Signature.
  The new one seems to be more robust for a much larger number of obstacles
  after some testing.
* HomotopyClassPlanner: vertex collision check removed since collisions will be determined in the edge collision check again
* Fixed distance calculation polygon-to-polygon-obstacle
* Enlarged upper bounds on goal position and orientation tolerances in *dynamic_reconfigure*. Fixes #13.

The failed sourcedeb jobs were due to a recent change on the buildfarm which didn't work on Saucy. The jobs should pass by now. Sorry for the notification emails.

authors: croesmann dirk-thomas


text:
rosbag_pandas: 0.5.3-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rosbag_pandas to 0.5.3-0:

upstream repository: https://github.com/eurogroep/rosbag_pandas.git
release repository: https://github.com/eurogroep/rosbag_pandas-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.7.2
previous version for package: null

rosbag_pandas
* flatdict dep in package
* Contributors: Rein Appeldoorn

Holding for sync

authors: reinzor tfoote


text:
melodic: add doc entry for opw_kinematics_plugin.

As per subject.

@JeroenDM fyi.


text:
replace python3-pep8 by python3-pycodestyle on Fedora 32

The package python3-pep8 doesnt exist on Fedora 32 and has been replaced by python3-pycodestyle
From the looks of it, most of the dependencies on this list could be installed by rosdep, I went with the simplest fix to get it working but the longer term solution would be to prune this list and rely on rosdep to install the dependencies.

I don't know why python3-pep8 was required, but the python3-pycodestyle is not an drop-in replacement, because it does not provide the pep8 command. So anything that depends on pep8 will fail.
As far as I can see there is no dependency on pep8 in the ROS2 installation, I would prefer to remove it to keep the list of dependencies as short as possible (as suggested in #847).

My understanding is that pep8 was needed by ament_pep8 that became ament_pycodestyle
https://github.com/ament/ament_lint/pull/217 (that now needs pycodestyle)
I agree with you than this list of dependency should be narrowed down to only the bits necessary to install by hand (and let rosdep handle the rest).
However (removal or replacement) the fix needs to be applied to ROS2 rolling instructions as well

@clalancette friendly ping, do you think we can merge this as is or would you rather remove the line completely and let rosdep handle its installation ?

@clalancette friendly ping, do you think we can merge this as is or would you rather remove the line completely and let rosdep handle its installation ?

I think we should let rosdep handle the installation of as much as possible, so let's just remove most of this and let rosdep do it.

so let's just remove most of this and let rosdep do it.

done in https://github.com/ros2/ros2_documentation/pull/848/commits/a4a022cd9119c8496e3f46a581bd41e3648d95ca

authors: clalancette mikaelarguedas rleh


text:
fix: format code comment for rand_kv

change
update to English comments.

Thanks

authors: rfyiamcool roseduan

repo: rosedblabs/rosedb


text:
Add temperature limit readings

There are four documented temperature readings starting at 0x9017, Read/Write functions 0x03/0x10:
"Batt Hi temp limit"
"Batt Lo temp limit"
"Device over temp"
"Device recovery temp"
source https://www.img4.cz/i4wifi/attach/StoItem/7069/MODBUS-Protocol-v25.pdf page 16
I haven't tried, but I have a suspicion they need to be written as a block like the battery voltages.
I will experiment...

Functionality to get/set temp limits did not require to be written as a block like the battery voltages.
However, if desired, this functionality can be added (in addition to the individual functions) so users could in set the block.
Test output:
controller.set_battery_upper_temperature_limit(65.1)
controller.set_battery_lower_temperature_limit(-40.1)
controller.set_device_over_temperature(85.1)
controller.set_device_recovery_temperature(75.1)
Created a nice mess:
Battery upper temperature limit: 65.09
Battery lower temperature limit: -40.1
Device over temperature: 85.1
Device recovery temperature: 75.09
I guess the 0.09 may be to do with the device's internal rounding.
FYI Setting the battery temp limit to -65.0 turns off the output and returns why:
Battery temperature: 21.75°C
Battery status: {'wrong_identifaction_for_rated_voltage': False, 'battery_inner_resistence_abnormal': False, 'temperature_warning_status': 'OVER_TEMP', 'battery_status': 'NORMAL'}
Battery upper temperature limit: -66.0

repo: rosswarren/epevermodbus


text:
Specify CheckM2 DB path

Addresses #164 by specifying --database_path in rule run_checkm2.

@LeeBergstrand This fix passes testing -- mind giving this a quick review? Thanks!

@jmtsuji Looks good.

@LeeBergstrand Thanks!

authors: LeeBergstrand jmtsuji

repo: rotary-genomics/rotary


text:
Error XFC0000: Cannot resolve type "shades:Shadows"

Sdk version: iOS 11/Android SDK 21
Xamarin.Forms: 4.8+

I installed the NuGet and added a shadow to a label, but got the next compilation error on build:
Error XFC0000: Cannot resolve type "shades:Shadows"
Steps to reproduce the behavior:

Install nuget
Add shadow namespace inside xaml
Add shadow
Try to build
See error

Source of the page:

<?xml version="1.0" encoding="utf-8"?>
<ContentPage
    xmlns="http://xamarin.com/schemas/2014/forms"
    xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
    xmlns:shades="http://sharpnado.com"
    x:Class="FailsInShadowsNuget.MainPage">
        <shades:Shadows>

                    <FormattedString>
                        <FormattedString.Spans>

                        </FormattedString.Spans>
                    </FormattedString>

        </shades:Shadows>
</ContentPage>

Cannot replicate your issue

@byme8  xmlns:shades="http://sharpnado.com" - change this to xmlns:shades="clr-namespace:Sharpnado.Shades;assembly=Sharpnado.Shadows"

@themronion @byme8  how do you end up with this issue ?
what IDE are you using ?

@roubachof I didn't even try to reproduce this issue, i just recommended the way i declare your plugin in xamls)

it's the new namespace attribute, it should work this way in the latest version

@themronion, with xmlns:shades="clr-namespace:Sharpnado.Shades;assembly=Sharpnado.Shadows" everything works as expected. Thanks!
@roubachof, I am using Microsoft Visual Studio Community 2019 Version 16.7.6. Also tested on VS For Mac 8.8 and got the same compilation error.

@roubachof

how do you end up with this issue?

I just installed the package and VS resolved namespace as xmlns:shades="http://sharpnado.com". That's all.

Which version of XF please ?

Same for me on version XF 4.8.0.1451 the syntax only shows xmlns:shades="http://sharpnado.com" when implementing in XAML

@dansiegel do you have an idea what is causing this. I could replicate it also. If you add as a nuget package and you add a Shadows you it is fine with the intellisense but you end up with a compile error...

I'm not sure what's causing this, I know that you have your preferred prefix as sho but I tried changing the xmlns to sho and got the same result. It seems very similar to xamarin/xamarin.forms#8451 but I believe that has to do with a project not having been compiled yet which wouldn't quite be the same issue when you're working with a nuget...
Perhaps someone on the Forms team can provide some input here... to me it looks like a problem with XamlC
@redth @StephaneDelcroix @pureween

thanks to @pictos here is the deal:

To consume types from the custom namespace schema, the XAML compiler requires that there's a code reference from the assembly that consumes the types, to the assembly that defines the types. This can be accomplished by adding a class containing an Init method to the assembly that defines the types that will be consumed through XAML:

from: https://docs.microsoft.com/en-us/xamarin/xamarin-forms/xaml/custom-namespace-schemas#consuming-a-custom-namespace-schema
So for the namespace schema to work, you need to call initializer from App.xaml.cs like this:
        public App()
        {
            InitializeComponent();

            Sharpnado.Shades.Initializer.Initialize(false);
            Sharpnado.Tabs.Initializer.Initialize(true, true);
        }

Giving the control a name solved it for me, "x:name" to the shadow control

Yup cause it generates a code reference to the assembly.

authors: byme8 conor-codes dansiegel givod roubachof themronion


text:
Dictionary completion?

I normally use Deoplete but I decided to try this out and I'm wondering if there's a way to get dictionary completion in Pandoc files.
Normally I use setlocal dictionary+=/usr/local/share/dict/common-words (my own dictionary) and disable most other sources, but I don't know how to do that in NCM.
In deoplete I set let g:deoplete#sources_pandoc = ['buffer', 'dictionary', 'member'].

Why not setting the  pumheight option?

Dictionary completion is not supported currently.

authors: Alok roxma

repo: roxma/nvim-completion-manager


text:
proc-macro

Is it possible to write a procedural macro, which takes assembly code as input and generates the corresponding pio-rs function calls, like the @rp2.asm_pio micropython decorator?

This repo contains the pio_proc crate, and https://github.com/rp-rs/rp-hal/pull/9 has code which would allow you to do something like:
use pio_proc::pio;
use rp_hal::pio::PIOBuilder;

let program = pio!("
	write your pio program assembly here
");

PIOBuilder::default()
	.with_program(program)
	.build()

Okay nice. Why is this done in rp-hal instead of here?

repo: rp-rs/pio-rs


text:
Better handling of attribute hierarchies

Attribute Hierarchies are not separate citizens in XML/A. But they are to the user. So, we need to add some smarts to detect attribute hierarchies and render them.
Attribute Hierarchies are actually not hierarchies at all - they are simply attributes that we want to use in queries. in XML/A they end up as hierarchies with one single level, or two levels if you count the all level.
We should probably try to figure out if something is an attribute hierarchy as an additional step after discovering hierarchies. If we find attribute hierarchies, we should probably flatten their hierarchy node, thus revealing its level.

Perhaps this item should be more generalized. The point is that different people like different ways to navigate the metadata of the cube and its dimensions, and some modes of navigation are better suited to different styles of cube setup.
Examples of navigation styles:

"flat": user gets only two flavors of "things", measures and attributes. No hierarchies are apparent, but hierarchies may become apparent in the query/visualization

In xavier this could be achieved by flattening hierarchy nodes and hiding members. Attributes are either levels or properties. Maybe xavier should add a "dimensions" node that can act as directory for all non-measure items. This would of course normally be flattened.

"object oriented": user only gets members (or members and measures).

Advantage is that this provides a lot of detail, as well as an initially lean tree. Drawback is that it would be very difficult to use this if you want to only include a set of members at a particular level without showing ancestors. Another drawback are hierarchies that do not have an all level, and that have a large number of members at the top level, since these become unnavigable.

"rich" is what we have now. Fairly detailed tree structure following the structure of the cube (as projected by XML/A)

Part of this is now realized - we can now choose to render hierarchies "flattened", and levels exposed.
Probably should also add an option to hide the "all" level (and member) in case the hierarchy has only one "real" level (i.e., apart from the all level), and at most highCardinality number of members. Because in that case, it seems the all level really doesn't add that much.

Another idea to deal with attribute hierarchies.
Instead of hiding the all level, we could also fold  the all level in with the "real" members, i.e. only the "real" level would be displayed, not the all level, and the "all" member would appear as first member beneath the "real" level.

See previous comment. This is what it would look like in the config.
    //foldAllLevel: if true, then no separate nodes for the all level will be displayed.
    // if present, the all level will be displayed as first member of beneath the first "real" level.
    // this is especially useful if you have many attribute hierarchies, since this will prune the tree considerably.
    foldAllLevels: true,

I think many of these requirements are now satisfied, although some of them need manual integration/ configuration.
I'm going to close it for now, It was already a very generic issue anyway - let's see if we can come up with more concrete and specific enhancement requests in the future.

repo: rpbouman/xavier


text:
🛑 Raj Haraniya - Portfolio is down

In e419547, Raj Haraniya - Portfolio (https://rajharaniya.me) was down:

HTTP code: 403
Response time: 802 ms

Resolved: Raj Haraniya - Portfolio is back up in 2dc225f after 6 minutes.

repo: rpharaniya/websites-uptime-monitor


text:
🛑 Breze Cleaning is down

In 8dfb659, Breze Cleaning (https://brezecleaning.com/) was down:

HTTP code: 504
Response time: 3904 ms

Resolved: Breze Cleaning is back up in ef00d10.


text:
svgo dependency resolves as v0.7.2 with svgo-loader v2.0.0

Hey all,
While svgo-loader v2.0.0 should use at least svgo v1.0.0, it resolved to v0.7.2. Then, library returns an error while promise are only available from v1.0.0.
Could It comes from the fact that svgo is declared as a peer dependency?
Issue reproduced with both yarn and npm. FYI, loader works properly when svgo is installed manually.
Edit: While a peer dependency should be manually installed (as suggested by npm), documentation should be modified to:
$ npm install svgo svgo-loader --save-dev
$ yarn add svgo svgo-loader -D

That's strange. We require the peer dependency to be ^1.0.0: https://github.com/rpominov/svgo-loader/blob/3864ea3104bf53b8037016013e3cb0951439da1c/package.json#L28
The idea behind using peer dependency as opposed to a normal one is to let users install any version of svgo that they want.
Probably similar issue here #21

There was a time when svgo didn't publish a new version to npm, but now the version 1.0.3 is available there, so 0.7.2 resolution is kinda weird.

I've just tried it out in an empty directory:
$ npm i svgo-loader
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN svgo-loader@2.0.0 requires a peer of svgo@^1.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN test1@1.0.0 No description
npm WARN test1@1.0.0 No repository field.

+ svgo-loader@2.0.0
added 5 packages in 3.101s

$ npm list
test1@1.0.0 /private/tmp/test1
├── UNMET PEER DEPENDENCY svgo@^1.0.0
└─┬ svgo-loader@2.0.0
  └─┬ loader-utils@1.1.0
    ├── big.js@3.2.0
    ├── emojis-list@2.1.0
    └── json5@0.5.1

npm ERR! peer dep missing: svgo@^1.0.0, required by svgo-loader@2.0.0

$ npm install svgo
npm WARN test1@1.0.0 No description
npm WARN test1@1.0.0 No repository field.

+ svgo@1.0.3
added 42 packages in 6.701s

Seems like everything works as expected now.

Why you closed that issue? Now svgo-loader downloads old version svgo as dependency. In order to make it work i must manually install fresh svgo in additional and nowhere can read about that.
Best regards.

Hi @koutsenko , I wasn't able to reproduce this as shown in https://github.com/rpominov/svgo-loader/issues/20#issuecomment-343890264
How do you reproduce it?

Just working with my npm & webpack3-bundled js project.

with svo-loader 1.2.1, all works like charm, without any svgo entries
updated the package.json entry: 1.2.1 -> 2.0.0
totally removed npm_modules and package-lock.json
npm install. All modules are installed from scratch.
npm build/watch and a problem appears.
manually add svgo 1.0.3 entry, and all works again.

Maybe its some ^ or ~ versioning-related magic in svgo-loader deps?
п.с. мой английский ужасен :)

My package.json file

@koutsenko Readme file has been updated and now asks to install both svgo along svg-loader. This is following npm recommendations about peer dependencies.

I've investigated a bit more. Here is how it happens:

css-loader has a dependency on svgo;
if you've installed css-loader and svgo-loader it worked, but by accident (svgo-loader used svgo installed with css-loader);
when you update svgo-loader it no longer works.

But, after step 4 you should see a warning like this:

npm WARN svgo-loader@2.0.0 requires a peer of svgo@^1.0.0 but none is installed. You must install peer dependencies yourself.

And yes, our readme asks to install svgo. Although maybe we should state it more explicitly if already three people stumbled upon this independently.

I've added a warning to the readme https://github.com/rpominov/svgo-loader/commit/2f4563bf4fa07ccdfaf82850bf10cead5552879e

I've added a warning to the readme 2f4563b
@rpominov I was thinking about the reason you chose to declare svg-loader as a peer dependency. You wanted the user to be free to install any version of svgo but finally you need at least the version 1.0.0. So maybe you should declare now svgo as a regular dependency?

Hm. Not sure how it will work in this case. For example:

Someone installs svg-loader and gets svgo@1.0.0 as a normal dependency
svgo releases 1.1.0

How do you switch to svgo@1.1.0 in this case?

babel-loader also specifies babel as a peer dependency, btw: https://github.com/babel/babel-loader/blob/8b07d5d7b7e584a28d8c07bde23f342e675c7b9a/package.json#L18
But I honestly don't know what is the best practice for cases like this. Would appreciate if someone could investigate.

How do they switch to svgo@1.1.0 in this case?

While you declare svgo with a caret range as ^1.0.0, user will get latest version lower than 2.0.0.
=> https://github.com/npm/node-semver#caret-ranges-123-025-004b
Finally, declare a dependency as a peer ensures that if any version already installed (as It happened here with css-loader) doesn't match your package definition, the user will get a warning about an unmet version.
You can also keep svgo as a peer dependency, but then in Readme file modify instructions to:
npm install svgo@^1.0.0 svgo-loader --save-dev to ensure that an incompatible version of svgo doesn't get installed.

I encountered the same error as you did. Then I used npm install svgo and npm i svgo -g and added "peerDependencies" to package.json: {
     "svgo": "^1.0.0"
   },then npm i ,at last I solve my problem @Akaryatrh

authors: Akaryatrh jgchenu koutsenko rpominov

repo: rpominov/svgo-loader


text:
[Technical Debt ⚒] Remove workarounds regarding unpack and pack of canvas apps

export-and-unpack-solution / 2nd solution unpack step
set-canvasapps-instrumentation-key / "manual" solution pack

Tests

For the export-and-unpack-solution workflow, the folders with the source code of the canvas apps should be generated with only one solution unpack
For the import-solution-to-validation using the set-canvasapps-instrumentation-key action, the configured Azure Application Insights Instrumentation Key should be considered without the "manual" solution pack step

First, we will do a test in the demonstration repository, removing the workarounds.

Test on export in demonstration repository did not work - without the second unpack step, we lost the src folder for the canvas apps code.

Wait for next release here for a new test.
If this new test is still unsuccessful, we will finalize the v0.4.0 with the workarounds and resolve this issue in a future release.

New test done on the export today and still does not work with only one solution unpack during the export.
The issue will be moved to the next milestone to unblock the finalization of the v0.4.0.


text:
Handle includes in pre- and post-deployment scripts (fixes #23)

I'm expecting there may be a lot of feedback and proposed changes here, as this goes beyond my comfort zone for dotnet development. I've broken this into a few commits in case we want to replace some of the work.

I've added a number of unit tests, but I think I'll look at adding a postdeployment script to one of the pipeline tests as well. I'll work on that while waiting for review.

@jeffrosenberg On reviewing it another time I found a couple of more things. Sorry about that ;).

@jmezach no problem! I'm about to run into a bunch of meetings, so I'll probably get the remaining changes pushed out tomorrow morning.

@ErikEJ Can you take a look at this as well?

I will this evening

@jeffrosenberg Did you manage to add a test project to the CI pipeline so that we can make sure that works as expected on every change?

@jmezach I didn't add a new test project, but I did add two changes to TestProjectWithSDKRef that I think should be satisfactory for CI testing, let me know if you disagree.
https://github.com/rr-wfm/MSBuild.Sdk.SqlProj/pull/61/files#diff-d8d31a2c069adda9b8a4b6d9ca05c661
https://github.com/rr-wfm/MSBuild.Sdk.SqlProj/pull/61/files#diff-65850b3cc354d04c0e4395d2478e7161

@jeffrosenberg Ah, yes, that will work. I was looking for a change to the CI pipeline, but that isn't necessary if we added it to the existing project.
I guess we're good to go here then. Right @jeffrosenberg @ErikEJ?

I think so!

Agree :shipit:

Awesome. I'll get this merged and released as 1.8.0. Thanks again @jeffrosenberg for your work on this. This is probably our most requested feature currently ;).

authors: ErikEJ jeffrosenberg jmezach


text:
Create 0000-01-02-rradulov.md

Commit m.

Add rradulov's file

repo: rradulov/github-slideshow


text:
Better CLI errors

Here's what it looks like when the input has a syntax error:

and here's what it looks like when the syntax is valid, but we can't produce output for some reason:

These errors aren't friendly at all, and need to be cleaned up. A codeframe would be nice for parser errors, and when we can't generate output, a codeframe and a better explanation would be nice, as well as a link to our issue tracker 😄
Spec

For parser error, output a detailed syntax error and codeframe
For compiler errors (we can't generate output), output a codeframe and why we can't generate the code, maybe a link to our issue tracker as well

Implementation details
This should happen at the JS level, not the compiler - somewhere in the CLI code. Something like babel-code-frame would do most of what we want for us as far as output goes. There might be some Reason code necessary to extract better errors from the Flow parser, possibly in retyped_node.re or the main JS interface index.js.
As always, I'm available to help in the ReasonML Discord or on here!

Looking good!

repo: rrdelaney/ReasonablyTyped


text:
Add people search module

/search/people?q='jon'
/search/players?q='jon'
/search/managers?q='jon'
/search/teams?q='Cubs'

SELECT MATCH(nameFirst, nameLast) AGAINST('(lest*)' IN BOOLEAN MODE) score, playerID, nameFirst, nameLast FROM people having score>0 ORDER BY score DESC limit 10;

repo: rrickgauer/mlb-api


text:
Getting issue with file upload

i cloned the repo and ran the container, i can able to message to the clients (used adium) but when i was sharing the file it is not uploading , but the request is reaching to the server.

The issue is exactly the same for me. Also port 5280 for web admin is not working either, connection drops all the time. I didn't inspect it deeply though. Any thoughts on this? Btw, thanks for this docker image @rroemhild

repo: rroemhild/docker-ejabberd


text:
Writeable models

Models should be writable and saved back to the server.

Addresed in PR #9

repo: rroemhild/flask-ldapconn


text:
DHI-NVR410 not working

Hi,
Can't connect with my DHI-NVR410 NVR
When adding this component as Integration i get a "add camera" prompt.
I fill in the IP/port etc... tried 4 different channels but just keeps showing a loader.
Any help?

Did you see any logs?

repo: rroller/dahua


text:
add setup

I guess someone doesn't know how to set up.

Thanks!

authors: rrousselGit shinriyo


text:
EIP 1193 support

Two main features
Add event listeners for persona/account change and for network change. If the wallet allows for it, pass the attribute autoRefreshOnNetworkChange: false to not reload the page.
Second, add a basic error component and return a message to the user when the network is not what the developer expected. This basic error message should be expanded in the future with developer custom strings and i18n support.
Refs:

Event emitters https://eips.ethereum.org/EIPS/eip-1193
autoRefreshOnNetworkChange https://github.com/MetaMask/metamask-extension/pull/6330

@jessgusclark my feedback here:
https://hackmd.io/Uo7GI6ajRYy3nfVEo1Qu8w?view
see only the "Rlogin tests - 30/10/20" section

authors: jessgusclark miltonwg

repo: rsksmart/rLogin


text:
Magic eden floor price ticker returns Bad data error

Describe the bug
Thanks for the amazing tool! I just saw in the codebase that you also included support for collections found on Magic Eden:
https://github.com/rssnyder/discord-stock-ticker/blob/92c6092bfc64ae03516e2069a68bb2140ee647ed/utils/floor.go#L11-L16
Unfortunately, when I try to use this feature, I get the following error:
INFO[0000] Running discord-stock-ticker version development...
WARN[0000] Will not be storing state.
INFO[0000] Starting api server on 0.0.0.0:8080...
DEBU[0003] Got an API request to add a ticker
INFO[0003] Added ticker: floor
INFO[0004] Watching stock price for floor
DEBU[0014] Fetching stock price for lily
ERRO[0014] Yahoo returned bad data for lily

As I couldn't find this feature in the documentation,, I wondered if it is already released.
To Reproduce
Steps to reproduce the behaviour:

Clone the repository or run the docker container.
Save the following bot JSON file as lily_fp.json in the bots folder:

{
  "ticker": "floor",
  "marketplace": "magiceden",
  "name": "lily",
  "nickname": true,
  "frequency": 10,
  "discord_bot_token": "<BOT_TOKEN>"
}

Create a bot, as explained in https://www.youtube.com/watch?v=LhgCdtE8kmc.
Add the bot token to the JSON file.
Start the discord-stock-ticker ./discord-stock-ticker -logLevel 1.
Post the floor price bot curl -X POST -H "Content-type: application/json" -d @bots/lily_fp.json localhost:8080/ticker.
See error.

Expected behaviour
The bot should successfully update according to the collection floor price.
Python (please complete the following information):

Version: 3.8.10
OS: Ubuntu 20.04 and docker

I found the solution the correct place to put the ticker is in the curl command:
curl -X POST -H "Content-type: application/json" -d @bots/lily_fp.json localhost:8080/floor

What confused me was the ticker json object found in the stock price configuration documentation.

Closed by #180.

repo: rssnyder/discord-stock-ticker


text:
rstudio workbench kubernetes object templating

The newest version of workbench suggests that users should use kubernetes object templating instead of the job-json-overrides method. Will this be supported via this helm chart (meaning that you can edit job.tpl and service.tpl in helm values)?

Yes!! I am super excited about this 😄  And really excited to see that you / others are excited haha.
I'm curious to hear your thoughts. It definitely seems reasonable to me that we would have values to edit job.tpl and service.tpl directly in the helm chart.
However, using helm templates inside of helm values can also be kinda irritating sometimes... (i.e. having to escape things, use strings, etc.) Do you have thoughts on the following potential implementation paths:

"common" modifications exposed as more "standard" values (i.e. imagePullSecrets, annotations, etc.) so you do not have to pass the entire job.tpl file
escape hatch where you just pass the entire job.tpl / service.tpl files (they are kinda big)
an escape hatch for important "parts" of the job.tpl (i.e. a string / YAML type of extraObjects that gets dumped into the "defaultContainer" context)
an easy path to referencing an existing configmap that holds a job.tpl / service.tpl file? (i.e. something controlled / maintained outside of this helm release)

My initial thought is that all might be important, with a preference for the first two... and then just setting the appropriate precedence / warnings to make the UX decent. The third one seems the most "flexible without swallowing the ocean," but not sure if that would be a desirable interface or not.

@samssann I realize it has been a while here, but we are on our way to landing template support in the helm chart. The initial pass is intended to make a "values file" type of approach so that users do not have to modify custom templates directly. Would you be able to share what job-json-overrides you are currently using? We would love to be sure that commonly used values are available 😄

Hi @colearendt,
Apologies for the (very) late response. Here is a sample of our job-json-overrides.
launcher.kubernetes.profiles.conf:
  "*":
    allow-unknown-images: 0
    container-images:
     - xxxxx.azurecr.io/r-session-base:latest
     - xxxxx.azurecr.io/r-session-protobuf:latest

  "@group1":
    allow-unknown-images: 0
    container-images:
      - xxxxx.azurecr.io/r-session-base:latest
      - xxxxx.azurecr.io/r-session-ext:latest
      - xxxxx.azurecr.io/r-session-protobuf:latest
    default-container-image: xxxxx.azurecr.io/r-session-base:latest
    job-json-overrides:
      - target: "/spec/template/spec/containers/0/imagePullPolicy"
        json: "Always"
        name: imagePullPolicy
      - target: "/spec/template/metadata/annotations/cluster-autoscaler.kubernetes.io~1safe-to-evict"
        json: "false"
        name: evictAnnotation
      - target: "/spec/template/metadata/labels/aadpodidbinding"
        json: xxxxxxxxxxxx
        name: aadPodBinding
      - target: "/spec/template/spec/containers/0/imagePullPolicy"
        json: "Always"
        name: imagePullPolicy
      - target: "/spec/template/spec/containers/0/volumeMounts/-"
        json:
          name: storage
          mountPath: "/data"
          readOnly: true
        name: volumeMount00
      - target: "/spec/template/spec/containers/0/volumeMounts/-"
        json:
          name: storage-dev
          mountPath: "/data"
          readOnly: true
        name: volumeMount00dev
      - target: "/spec/template/spec/containers/0/volumeMounts/-"
        json:
          name: secret-provider-01
          mountPath: /mnt/secrets-store
          readOnly: true
        name: volumeMount01
      - target: "/spec/template/spec/containers/0/volumeMounts/-"
        json:
          name: secret-provider-02
          mountPath: /mnt/secrets-store-02
          readOnly: true
        name: volumeMount02
      - target: "/spec/template/spec/volumes/-"
        json:
          name: storage
          csi:
            driver: file.csi.azure.com
            readOnly: true
            volumeAttributes:
              resourceGroup: xxxxx
              storageAccount: xxxxxxx
              shareName: xxxxxx
              protocol: smb
              mountOptions: "dir_mode=0777,file_mode=0777,uid=0,gid=0,mfsymlinks,cache=strict,nosharesock"
              secretName: secret
              secretNamespace: xxxxxx
        name: volume00
      - target: "/spec/template/spec/volumes/-"
        json:
          name: storage-dev
          csi:
            driver: file.csi.azure.com
            readOnly: true
            volumeAttributes:
              resourceGroup: xxxxxxxxxx
              storageAccount: xxxxxxxxx
              shareName: xxxxxxxxx
              protocol: smb
              mountOptions: "dir_mode=0777,file_mode=0777,uid=0,gid=0,mfsymlinks,cache=strict,nosharesock"
              secretName: secret-dev
              secretNamespace: xxxxxxxx
        name: volume00dev
      - target: "/spec/template/spec/volumes/-"
        json:
          name: secret-provider-01
          csi:
            driver: secrets-store.csi.k8s.io
            readOnly: true
            volumeAttributes:
              secretProviderClass: secret-provider-01
        name: volume01
      - target: "/spec/template/spec/volumes/-"
        json:
          name: secret-provider-02
          csi:
            driver: secrets-store.csi.k8s.io
            readOnly: true
            volumeAttributes:
              secretProviderClass: secret-provider-02
        name: volume02
      - target: "/spec/template/spec/affinity"
        json:
          nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
              nodeSelectorTerms:
              - matchExpressions:
                - key: beta.kubernetes.io/instance-type
                  operator: In
                  values:
                  - Standard_E4as_v5
        name: nodeAffinity
  "@group2":
    allow-unknown-images: 1

Is there documentation on how to use the templates feature?

I know this is not the correct platform to post this, but i just want your view on this. After using this product for some months now, I feel like there is one aspect missing: The ability to configure different kubernetes configurations for different users/groups. I acknowledge that this feature would also require additional work in the in the workbench itself. The general idea is that a user can choose which kubernetes configurations to apply (from a drop down menu, or even upload yaml file?) to a new session the same way the user can choose which image to use (see illustrative image below). Available kubernetes configurations could be defined in the config file launcher.kubernetes.conf. Each kubernetes configuration has its own unique name. In launcher.kubernetes.profiles.conf using a variable kubernetes-configs, users/groups can be given permissions to use a subset/all of the kubernetes configurations. See example yaml below.

launcher.kubernetes.conf:
  "base":
      - target: "/spec/template/spec/nodeSelector"
        json:
          nodeSelector:
            kubernetes.azure.com/agentpool: default
        name: nodeSelector
  "app1-production":
      - target: "/spec/template/spec/nodeSelector"
        json:
          nodeSelector:
            kubernetes.azure.com/agentpool: prod-pool
        name: nodeSelector
      - target: "/spec/template/spec/containers/0/volumeMounts/-"
        json:
          name: storage-prod
          mountPath: "/data"
          readOnly: true
        name: volumeMount
      - target: "/spec/template/spec/volumes/-"
        json:
          name: storage-prod
          csi:
            driver: file.csi.azure.com
            readOnly: true
            volumeAttributes:
              resourceGroup: xxxxx
              storageAccount: xxxxxxx
              shareName: xxxxxx
              protocol: smb
              mountOptions: "dir_mode=0777,file_mode=0777,uid=0,gid=0,mfsymlinks,cache=strict,nosharesock"
              secretName: secret
              secretNamespace: xxxxxx
        name: volume
  "app1-development":
      - target: "/spec/template/spec/nodeSelector"
        json:
          nodeSelector:
            kubernetes.azure.com/agentpool: dev-pool
        name: nodeSelector
      - target: "/spec/template/spec/containers/0/volumeMounts/-"
        json:
          name: storage-dev
          mountPath: "/data"
          readOnly: true
        name: volumeMount
      - target: "/spec/template/spec/volumes/-"
        json:
          name: storage-dev
          csi:
            driver: file.csi.azure.com
            readOnly: true
            volumeAttributes:
              resourceGroup: xxxxx
              storageAccount: xxxxxxx
              shareName: xxxxxx
              protocol: smb
              mountOptions: "dir_mode=0777,file_mode=0777,uid=0,gid=0,mfsymlinks,cache=strict,nosharesock"
              secretName: secret
              secretNamespace: xxxxxx
        name: volume
launcher.kubernetes.profiles.conf:
  "*":
    allow-unknown-images: 0
    allow-unknown-kubernetes-configs: 0
    container-images:
     - xxxxx.azurecr.io/r-session-base:latest
    default-kubernetes-config: base
    kubernetes-configs:
     - base
  "@group1":
    allow-unknown-images: 1
    allow-unknown-kubernetes-configs: 1
    default-kubernetes-config: app1-development
    container-images:
     - xxxxx.azurecr.io/r-app1:dev
    kubernetes-configs:
     - base
     - app1-development
   "@group2":
     allow-unknown-images: 0
     allow-unknown-kubernetes-configs: 0
    container-images:
     - xxxxx.azurecr.io/r-app1:latest
     kubernetes-configs:
     - app1-production

This would enable users to e.g.:

choose on which node pool to run their computations
doens't force to mount everything (as we are required to do now)
overall gives better control to leverage kubernetes

authors: colearendt samssann

repo: rstudio/helm