Bundler says the bundle is ok but can't actually do anything with it

So, I have a very weird issue here that I can't easily reproduce.
I have an ubuntu 12.04 machine that had ruby 2.2.2 built in a separate path and linked to /opt/default-ruby and it includes the latest bundler (1.10.5). This machine runs an simple program and I use chef to set it up with the deployment bundle and everything, but when I try to actually run the code it fails.
If I ask bundler what's up with the bundle, it says it's all fine:
ubuntu@ip:/opt/bluecopper/current$ /opt/default-ruby/bundle check
fatal: Not a git repository (or any of the parent directories): .git
The Gemfile's dependencies are satisfied

And:
ubuntu@ip:/opt/bluecopper/current$ /opt/default-ruby/bundle list
fatal: Not a git repository (or any of the parent directories): .git
Gems included by the bundle:
  * aws-sdk-v1 (1.64.0)
  * bluecopper (0.1.0)
  * bundler (1.10.5)
  * dotenv (2.0.2)
  * json (1.8.3)
  * mini_portile (0.6.2)
  * multi_json (1.11.1)
  * nokogiri (<IP_ADDRESS>)
  * rollbar (1.5.3)
  * thor (0.19.1)

But when I call exec, the issue shows up:
ubuntu@ip:/opt/bluecopper/current$ /opt/default-ruby/ruby -S bundle exec bluecopper start -c app-config.yml
fatal: Not a git repository (or any of the parent directories): .git
Could not find json-1.8.3 in any of the sources
Run `bundle install` to install missing gems.

Any idea what this could be and how I could troubleshoot or provide more info?
The local .bundle/config file is:
---
BUNDLE_FROZEN: '1'
BUNDLE_PATH: "/opt/bluecopper/shared/bundle"
BUNDLE_WITHOUT: development:test
BUNDLE_DISABLE_SHARED_GEMS: '1'

It sounds like maybe /opt/default-ruby/bundle doesn't actually use /opt/default-ruby/ruby. Is that true?

the shebang seems to indicate it does use it:
#!/usr/local/ruby/2.2.2/bin/ruby
#
# This file was generated by RubyGems.
#
# The application 'bundler' is installed as part of a gem, and
# this file is here to facilitate running it.
#

require 'rubygems'

version = ">= 0"

if ARGV.first
  str = ARGV.first
  str = str.dup.force_encoding("BINARY") if str.respond_to? :force_encoding
  if str =~ /\A_(.*)_\z/ and Gem::Version.correct?($1) then
    version = $1
    ARGV.shift
  end
end

gem 'bundler', version
load Gem.bin_path('bundler', 'bundle', version)

And:
ubuntu@ip:/opt/bluecopper/current$ ls -l /opt/default-ruby
lrwxrwxrwx 1 root root 25 Jun 25 19:39 /opt/default-ruby -> /usr/local/ruby/2.2.2/bin

I've also tried to call it with /opt/default-ruby/ruby -S bundle and it still breaks.

Okay. Try the troubleshooting steps in ISSUES, and if that doesn't help, try bundle show json, and check up on the files in the path that gets printed.

Also could you check the shebang for bluecopper? It could be invoking a different version of Ruby.

@TimMoore right on target!
The shebang for the bluecopper command was using /usr/bin/env ruby and picking up the system ruby, not a bundler issue, thanks everyone!


There's not enough entropy in the output filenames

At the moment only the request URL is used as an input to the filename hash.
It should really be a hash of the entire output to avoid overwriting files from matching URLs where the output might have changed.

Added the 'help wanted' label as it should be a fairly easy fix and a good one for someone new to Go.


⚠ API - Lens has degraded performance

In f3a142c, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 502
Response time: 596 ms

Resolved: API - Lens performance has improved in 80401aa after 8 minutes.


rewrite the intro part

I put * number to a couple of claims. There claims need to have support evidence. Please add them as references and put a link from the * number.

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

Codecov Report

Merging #102 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #102   +/-   ##
=======================================
  Coverage   77.69%   77.69%
=======================================
  Files          10       10
  Lines         269      269
=======================================
  Hits          209      209
  Misses         53       53
  Partials        7        7

Continue to review full report at Codecov.

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


Web rendering issue with AnimatedContainer example

Steps to Reproduce

https://peiffer-innovations.github.io/json_dynamic_widget/web/index.html
Tap "animated_container"
Hit the button.

The animation does not show the square moving, which was the expected outcome.  This appears to only happen on Web.  I was unable to reproduce the issue on Android, iOS, or MacOS.
Screencap showing the issue

This was deployed in RELEASE mode on Flutter version:
Flutter (Channel dev, 1.22.0-9.0.pre, on Mac OS X 10.15.6 19G2021, locale en-US)

This appears to be an issue with Flutter itself.  Switching to the beta channel on version:
Channel beta, 1.21.0-9.2.pre

... works fine.  I updated the example from the beta channel and this can be closed and should be opened as a ticket as a possible regression w/in Flutter from current beta to dev / master.


Start supporting straw person C style Schema syntax

Opening for comment, needs more tests and further review before ready for merge
I am guessing that the following people are likely to be interested in commenting, but feel free to forward
@shans @bgogul @cromwellian @csilvestrini @SHeimlich

This gives us Kotlin-style schemas, not C-style I think (line terminators aren't required unless multiple logical lines are on the same physical line). Looks good at any rate!


Use GitHub Actions, or other CI that runs

Travis CI linked to here, does not run, currently. Perhaps we can configure a GitHub Actions?

Feel free, this project is largely unmaintained

Closed by #50


Improve launch documentation

This patch improves upon existing documentation on launch to make it easier on newcomers to use it. In particular, it:

reworks the About Launch page under Concepts to be a bit more thorough, and
extends the guide on Using Python, XML, and YAML for ROS 2 Launch files with more examples.

Contributed by The AI Institute.

FYI @jbarry-bdai

Thoughts on the overall idea, and of the specifics of what I've laid out above?

I'm a bit fuzzy on what would happen to guides. Guide != tutorial. Otherwise, the layout looks reasonable to me. I agree it doesn't help to have bits of launch documentation all over the place. I would personally build up launch and launch_ros documentation to include conceptual and architectural deep dives, not just an API reference. I even have a proposal for a layout I can share.
That said, I can't stretch the scope of this PR to cover a complete overhaul. I can reorganize this contribution into basic and intermediate concepts. I can relocate the guide.

I'm a bit fuzzy on what would happen to guides. Guide != tutorial IMHO

Yes, completely agreed.  Guides are meant to answer a specific question, while Tutorials walk through step-by-step, showing the user how to do something.
That said, in my taxonomy above there are only two guides:

Launching composable nodes
Launch file different formats

I think both of those could be reasonably incorporated into Tutorials and removed from the Guides.  Though again, I'm willing to hear other opinions and change it up.

I would personally build up launch and launch_ros documentation to include conceptual and architectural deep dives, not just an API reference.  I even have a proposal for a layout I can share.

This is a hard one to gauge for me.  The ability to have detailed documentation in the individual packages is definitely a feature.  But I also think that we've been most successful (in terms of people finding it) with documentation that is here in ros2_documentation.  Can you share your layout proposal as a starting point?

That said, I can't stretch the scope of this PR to cover a complete overhaul.

Yeah, that's totally fair.  I think it is worthwhile for us to figure out what we want the final product to look like, and write it down somewhere (likely an issue in this repository).  Then as people have time to work on it, at least we have a framework to fit it into.

I think both of those could be reasonably incorporated into Tutorials and removed from the Guides.

I see. That's fair.

Can you share your layout proposal as a starting point?

I had something like this in mind for a launch documentation TOC:

Motivation (why launch?)

FAQ (e.g. why not a shell script?)

Concepts (what is launch?)

Context

Configurations
Events
Scope

Statements

Actions

Expressions

Conditions
Substitutions

Control flow

Event handling

Architecture (launch details)

Entities
Descriptions

Frontend (parsers)

Service

User guide (how to launch?)

Cheatsheet (reference on actions, substitutions, etc.)
Extensions

Implementing an action
Implementing a event
Implementing a condition
Implementing a substitution
Implementing an event handler
Adding a new frontend

API Reference (polished)
Glossary

IMHO this is too detailed to be hosted in https://docs.ros.org. For the front page, the launch concepts page in this PR already covers enough of the basics (and internals for CS savvy folks).

I think it is worthwhile for us to figure out what we want the final product to look like, and write it down somewhere (likely an issue in this repository)

Sounds reasonable. I can adapt this PR to cover concepts and a tutorial on writing launch files.

@clalancette friendly ping

@mhidalgo-bdai So sorry for the very delayed response.  I'm finally coming back around to this.
I like the topics covered in your table of contents.  That is exactly the type of thing I think we should cover.
What I'm wondering is whether it is worthwhile to split it up, though.  In particular, I'm kind of thinking we can take your Concepts section and move it into Concepts/Intermediate here on https://docs.ros.org .  And then we can take the User Guide portion and move it into Tutorials/Intermediate here on https://docs.ros.org.  That would leave only "Architecture" and "API" reference in the individual packages, where I think they belong.  Incorporating that idea back into what I mentioned before, we would end up with something like this:

https://github.com/ros2/launch - the sources plus the Architecture documentation and links to the API reference
https://github.com/ros2/launch_ros/ - ditto
https://docs.ros.org/en/rolling/p/launch/launch.html - API documentation
https://github.com/ros2/ros2_documentation/blob/rolling/source/Concepts/Basic/About-Launch.rst - Leave this more-or-less as-is, since it is worth introducing early without too much detail
https://github.com/ros2/ros2_documentation/blob/rolling/source/Concepts/Intermediate/Launch - a series of pages about concepts in launch (this is the "Concepts" from your TOC)
https://github.com/ros2/ros2_documentation/blob/rolling/source/Tutorials/Beginner-CLI-Tools/Launching-Multiple-Nodes/Launching-Multiple-Nodes.rst - beginner introduction to running a launch file (though I think we should remove the discussion of the launch file details from here)
https://github.com/ros2/ros2_documentation/tree/rolling/source/Tutorials/Intermediate/Launch - set of intermediate tutorials on using launch (this is the User Guide from your TOC)

Thoughts on that?

This looks reasonable. I can try to rework this patch into both concepts and user guide pages. It may take me a while though (internal re-prioritization). I'll ping you when I get to circle back.


Symlink error

Hi,
I am getting following error:
The page build failed with the following error:
A file was included in source/index.html that is a symlink or does not exist in your _includes directory. For more information, see https://help.github.com/articles/page-build-failed-file-is-a-symlink.
If you have any questions you can contact us by replying to this email.
Please let me know what is the issue.

Github does not accept custom plugins for Jekyll :flushed:
Use the Rake task to build and send to branch gh-pages...
See this tutorial >> http://ixti.net/software/2013/01/28/using-jekyll-plugins-on-github-pages.html
Thanks!
https://github.com/nandomoreirame/nandomoreira-jekyll-theme/issues/2

Github does not accept custom plugins for Jekyll :flushed:
Use the Rake task to build and send to branch gh-pages...
See this tutorial >> http://ixti.net/software/2013/01/28/using-jekyll-plugins-on-github-pages.html
Thanks!
https://github.com/nandomoreirame/nandomoreira-jekyll-theme/issues/2

Hi,
I have tried using above link. But I am getting 404 error.
This is my repository https://github.com/appgiablog/appgiablog.github.io
Please let me know what is error.
thank you,

Set master to default branch and remove appgia.com at CNAME file.
see resolves..

Still it gives same error:
Your site is having problems building: A file was included in source/index.html that is a symlink or does not exist in your _includes directory. For more information, see https://help.github.com/articles/page-build-failed-file-is-a-symlink.
thank you

Github does not accept custom plugins for Jekyll :flushed:
Use the Rake task to build and send to branch gh-pages...
See this tutorial >> http://ixti.net/software/2013/01/28/using-jekyll-plugins-on-github-pages.html
Thanks!
nandomoreira-jekyll-theme/issues/2


[Feature Request]: Enable Search by Cryptocurrency Name

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Currently, the Crypto Price Predictor only recognizes cryptocurrency symbols (e.g., BTC, ETH) for fetching predictions. However, when a user inputs the full name of the cryptocurrency (e.g., "bitcoin" instead of "BTC"), the search doesn't return results.

Use Case
if the user tries to search with the name also he can see the predicted price
Benefits
"The user does not need to know currency abbreviations."
Priority
Medium
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

Can you assign this to me? It would be great to contribute to your project!! I'm in GSSoC24

Sure , go make an pr and u need to make changes such that while typing the name we can able to see the drop down of currencies they only appear symbols u need to make Bitcoin(BTC) like that

I appreciate your support! I'll start working on it immediately!!


Can't focus city production anymore

I installed version 0.6 and have the updated version of Civ.
Now I can't turn on focus the city for production/food/culture/science.
The buttons for it in the city menu don't work.
When I load a savegame without CQUI the issue isn't there.
CQUI is the only mod I use.
It's really great! Thank you for it.

Fixed in the nightly, so the next "official" release will have this change. You can simply download the current version from here again and be fine.

That's great, thank you!


Could not connect to the server. HTTPS connection failed, verify there are no self-signed certificates or custom cert validation policies blocking Live Share.

Describe what happened:
Able to log in successfully using microsoft but when I close tab to return to vscode I get this error.
Could not connect to the server. HTTPS connection failed, verify there are no self-signed certificates or custom cert validation policies blocking Live Share.
What was your system configuration?
Product and Version [VS/VSCode]: VSCode
OS Version[macOS/Windows]: macOS
Live Share Extension Version: LiveShare
Target Platform or Language [e.g. Node.js]: Python
Steps to Reproduce / Scenario:

Go to liveshare extension and login with microsoft
See successful login in browser and close tab
Return to Vscode and get popup error.

Please attach logs to this issue:
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
20210922_233639_16323537997060_VSCode.log
20210922_233640_Agent.log
Screenshots
If applicable, add screenshots to help explain your problem.

Hi @lsaadeh, sorry for the issue you're having and thanks for reaching out to Live Share. This looks like a duplicate of #4000. Here are the instructions:

This issue is caused by missing certificates. You can test that you have the proper certificates for openssl by running the command openssl s_client -connect download.microsoft.com -port 443. If this is the problem, you will see an output such as "unable to get local issuer certificate".
To fix the problem, run sudo apt-get install wget ca-certificates and run the openssl command above to double check your connection.

Can you please try to run the equivalent commands on your Mac?

Hi @alyssajotice,
I tried to research what the equivalent for sudo apt-get install wget ca-certificates but it doesn't look to exist.
is it possible to have live share ignore ssl errors as I'm in a corporate environment and there are many proxies?

Thanks for specifying that you're using a proxy. If you're using a proxy, you can double check that you have access to the ports and URLs listed here: https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/connectivity#requirements-for-connection-modes. There is not a way to bypass ssl errors.
In addition to the list in the docs above, you also need access to *.online.visualstudio.com. Ensure your corporate or personal network firewall allows you to connect to this domain. Enter https://sts.online.visualstudio.com/api/swagger/index.html in a browser and verify you land at the swagger page.

As is, this issue doesn’t have enough information to be reproduced. If the issue persists, please review the information provided at https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/connectivity#requirements-for-connection-modes or provide any additional details. Thank you.


COM-286: Refactor theming of FeaturesButtonGroup

@juliawegmayr please merge the feature branch and resolve conflicts, thanks!


January 25, 2024 - Content Release

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.

[x] Yes, I've run yarn install
[ ] No, does not apply to me

Purpose of this pull request
This pull request...

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions, .clabot
[ ] Update Content - Revisions, updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

@kimsauce, could you approve this PR so we can publish it?

Thanks, @kimsauce!


fixing "pygments.util.ClassNotFound: no lexer for alias" error

this fixes an error when an unknown language is encountered in the PygmentsRenderer

@derekn, thank you, LGTM. Do you think you could also add unit tests which would cover the fix (no language vs. known language vs. unknown language)? Looks like test_pygments_renderer.py is missing, so it needs to be created from scratch...

coverage: 90.292% (-0.1%) from 90.439% when pulling d1980359f6ce9b9b5337bafa9c6a17ae40bf570d on derekn:master into 9c218172271e4b6d9e13f4e74d7977fca0056383 on miyuchina:master.

Also, I think we should give clients the possibility to still get an error when an unknown language is passed. I.e. introduce a new constructor parameter, say fail_on_unknown_language=True (True for backwards compatibility), and re-throw the ClassNotFound exception if this parameter is True (and token.language is not empty).

Added unit tests for PygmentsRenderer.
Also, added the fail_on_unknown_language option to the renderer, but defaulted it to False. I believe this aligns with the behavior of other markdown packages and is generally more desirable in this situation. I dont think this will be a breaking change for clients.

@derekn, good point, I agree.
Just a small correction of the handling of empty language supplied (I'm not sure if I want to commit into your master branch - it is usually better to create a dedicated branch for PR, e.g. fix-pygments-classnotfound in this case):
diff --git a/mistletoe/contrib/pygments_renderer.py b/mistletoe/contrib/pygments_renderer.py
index c07a39c..0d3bd29 100644
--- a/mistletoe/contrib/pygments_renderer.py
+++ b/mistletoe/contrib/pygments_renderer.py
@@ -18,11 +18,14 @@ class PygmentsRenderer(HTMLRenderer):
     def render_block_code(self, token):
         code = token.content

-        try:
-            lexer = get_lexer(token.language)
-        except ClassNotFound as err:
-            if self.fail_on_unknown_language:
-                raise err
+        lexer = None
+        if token.language:
+            try:
+                lexer = get_lexer(token.language)
+            except ClassNotFound as err:
+                if self.fail_on_unknown_language:
+                    raise err
+        if lexer is None:
             lexer = guess_lexer(code)

         return highlight(code, lexer, self.formatter)
diff --git a/test/test_contrib/test_pygments_renderer.py b/test/test_contrib/test_pygments_renderer.py
index 491c827..839ea55 100644
--- a/test/test_contrib/test_pygments_renderer.py
+++ b/test/test_contrib/test_pygments_renderer.py
@@ -2,12 +2,17 @@ import unittest

 from mistletoe import Document
 from mistletoe.contrib.pygments_renderer import PygmentsRenderer
+from parameterized import parameterized
 from pygments.util import ClassNotFound

 class TestPygmentsRenderer(unittest.TestCase):
-    def test_render_no_language(self):
-        renderer = PygmentsRenderer()
+    @parameterized.expand([
+        (True),
+        (False)
+    ])
+    def test_render_no_language(self, fail_on_unknown_language: bool):
+        renderer = PygmentsRenderer(fail_on_unknown_language=fail_on_unknown_language)
         token = Document(['```\n', 'no language\n', '```\n'])
         output = renderer.render(token)
         actual = (

In relation to this fix, I've realized we should better name the new option fail_on_unsupported_language - can you do the rename and squash the changes to your last commit? Thank you.

@pbodnar added your changes, renamed fail_on_unsupported_language option, and squashed

Added the pygments dependency to the github action for the tests

Damn it, one more thing it seems - older Python build say this:

TypeError: Parameters must be tuples, but True is not (hint: use '(True, )')

Added the pygments dependency to the github action for the tests

Thank you, you are quick. :) I will probably try to introduce requirements.txt in order to avoid duplication, but in a later separate commit.

@derekn, good job, thank you. :)

@pbodnar thanks, happy to help!


audio bar not displaying in chrome when opening a audio file(.wav) through journal

When a user tries to open an audio file in .wav format, no audio bar is displayed in the media viewer activity.

Fixed in https://github.com/llaske/sugarizer/pull/320

Closed in https://github.com/llaske/sugarizer/commit/dd3c58d56981e4dfa6d94601b95d7117a3bc9241


Recent windows update (KB4541335) causes some windows to flicker.

Recent windows update (KB4541335) causes some windows to flicker. The flickering briefly causes the Windows 7 style 'Aero' border to appear on windows. I believe this is a Windows bug as it has only started with that specific update.
A friend of mine said it's caused by the window re-drawing when being captured too frequently, however, this same issue is happening with the capture framerate set to 30 FPS.
Can reproduce using Spotify's desktop app, or I believe Steam.

I have this same issue. @Curtis-VL did you find a solution for this?

Thanks Curtis! 👍

I'll close this issue as the issue was resolved by Windows 10 version 2004 and later. The fix is simply to update Windows. :)


Reading source and region attributes from Source tags

Hi,
In case anyone is interested, I have added support for reading "source" and "region" attributes from <code source="" region=""> tags in my own fork at https://github.com/cesarsouza/NuDoq
Regards,
Cesar

Hey @cesarsouza, I know it's been ages (I'm trying to bring this a little bit up-to-date). But do you happen to recall where the definition of those two attributes comes from? I can't find any docs related to them :(.

Hey @cesarsouza, I know it's been ages (I'm trying to bring this a little bit up-to-date). But do you happen to recall where the definition of those two attributes comes from? I can't find any docs related to them :(.

Ok, I think those are coming from sandcastle. Given that, once #1 is implemented, this shouldn't need a special case. I think you'd just access the extra attributes with something like code.Attributes.TryGetValue("source", out var source), for example.

Ok, I think those are coming from sandcastle. Given that, once #1 is implemented, this shouldn't need a special case. I think you'd just access the extra attributes with something like code.Attributes.TryGetValue("source", out var source), for example.

Yeah, they were from Sandcastle, maybe even something specific to SHFB.

Given that, once #1 is implemented

Just checked that, its an issue from 2013 😅
Good luck on the update and thanks again for having built this library in the first place :-)

Yeah, they were from Sandcastle, maybe even something specific to SHFB.

Given that, once #1 is implemented

Just checked that, its an issue from 2013 😅
Good luck on the update and thanks again for having built this library in the first place :-)

Hehe, yeah, took me a while to get back to this! 😂

Hehe, yeah, took me a while to get back to this! 😂


multiple SOPClassUIDs in the same series

First, thanks @dannyrb, @swederik and team for this open source software. It is AMAZING.
FYI - in version 4.8.1, build 0 (from docker hub image) when viewing multiframe instances with CINE at 24 FPS, playback is very slow. As CINE steps through each frame, console issues warning "More than one SOPClassUID in the same series is not yet supported". This slowness and console warnings are not experienced in OHIF version 1.7 pointed against the exact same DICOMweb server (Orthanc 1.8.2 from docker hub image).

Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?


feat: add local data map & format code

👀 PR includes

✨ Feature

[1 ] New feature
Filter container tab get local data for default checked

🎨 Enhance

[ ] Code style optimization
[ ] Refactoring
[ ] Change the UI
[ ] Improve the performance
[ ] Type optimization

🐛 Bugfix

[ ] Solve the issue and close #0

🔧 Chore

[ ] Test case
[ ] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

📝 Description
🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

@noneAuth  thanks for your contribution！


vfrmap is not opening openstreetmap

Hi,
I've been using vfrmap with msfs for the last 18 months and it has always worked fine until this week. Now after I start msfs and run vfrmap, when I go to localhost:9000 in google chrome, the map is just solid grey. I get the readings across the top showing heading, alt, speed, etc but no map. The other views like Stamen Terrain, Toner, Water all work fine.
How do I get the map back?
thanks
Ian
<EMAIL_ADDRESS>

gleiches Problem mit der aktuellen Version 0.0.7

You can type this in the console as temporary fix
map._layers[24]._url = 'https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png'

Bibou, forgive me for not understanding but what is the console where I should type the temporary fix?

I have the same gray screen problem but also am not sure about 'the console'.

This should work by adding the index.html file in the folder
https://github.com/bibou/msfs2020-go/raw/master/temp fix vfrmap.zip

Thanks Bibou, adding the index file worked perfectly.
On Sun, Mar 20, 2022 at 4:32 AM bibou @.***> wrote:

This should work by adding the index.html file in the folder
https://github.com/bibou/msfs2020-go/raw/master/temp fix vfrmap.zip
—
Reply to this email directly, view it on GitHub
https://github.com/lian/msfs2020-go/issues/80#issuecomment-1073231067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYJQTGDZTJHKSPQUUPLPX2TVA4EFFANCNFSM5RDJYUZQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Not able to change the offset

kt group -group enews -topic actor-news -partitions 0
found 1 groups
found 1 topics
failed to read partition offset for topic=actor-news partition=0 err=EOF
i am using kafka version  2.10-<IP_ADDRESS>.
i don't know why. can you please help me .
In the kafka logs it shows this error
ERROR Closing socket for <IP_ADDRESS>:9092-<IP_ADDRESS>:59373 because of error (kafka.network.Processor)
kafka.network.InvalidRequestException: Error getting request for apiKey: 2 and apiVersion: 1
at kafka.network.RequestChannel$Request.liftedTree2$1(RequestChannel.scala:95)
at kafka.network.RequestChannel$Request.(RequestChannel.scala:87)
at kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:488)
at kafka.network.Processor$$anonfun$processCompletedReceives$1.apply(SocketServer.scala:483)
at scala.collection.Iterator$class.foreach(Iterator.scala:727)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1157)
at scala.collection.IterableLike$class.foreach(IterableLike.scala:72)
at scala.collection.AbstractIterable.foreach(Iterable.scala:54)
at kafka.network.Processor.processCompletedReceives(SocketServer.scala:483)
at kafka.network.Processor.run(SocketServer.scala:413)
If i update my kafka to kafka_2.10-<IP_ADDRESS> the command worked. but if i reset the consumer using
kt group -group enews -topic actor-news -partitions 0 -reset 1 and then i start consumer it doesn't  starting sending me the data from offset 1.  can you please explain how to reset it .

hi @chandradeepak, can you try to pass the version explicitly? e.g.:
kt group -group -enews -topic actor-news -partitions -version v<IP_ADDRESS>

or
kt group -group -enews -topic actor-news -partitions -reset 1 -version v<IP_ADDRESS>

if that doesn't work, can you please tell me which version of kt you're using?

Thanks @fgeller , i was able to make the request using the version you provided but still the reset doesn't work.  when the consumer read some messages i set the offset to 1 . then i see this in consumer offset topic
[enews,actor-news,0]::[OffsetMetadata[1,NO_METADATA],CommitTime<PHONE_NUMBER>060,ExpirationTime<PHONE_NUMBER>060]
now reset to 4. it will work
[enews,actor-news,0]::[OffsetMetadata[4,NO_METADATA],CommitTime<PHONE_NUMBER>879,ExpirationTime<PHONE_NUMBER>879]
now reset to 1 . it will never work.
kt group -group enews -topic actor-news -partitions 0 -reset 1 -version v<IP_ADDRESS>
found 1 groups
found 1 topics
{
"name": "enews",
"topic": "actor-news",
"offsets": {
"0": {
"offset": 1,
"lag": 5
}
}
}
kt group -group enews -topic actor-news -partitions 0 -version v<IP_ADDRESS>
found 1 groups
found 1 topics
{
"name": "enews",
"topic": "actor-news",
"offsets": {
"0": {
"offset": 4,
"lag": 2
}
}
}

Found the problem
in the code of offset_manager.go there is
func (pom *partitionOffsetManager) MarkOffset(offset int64, metadata string) {
pom.lock.Lock()
defer pom.lock.Unlock()
_//if offset > pom.offset {_
pom.offset = offset
pom.metadata = metadata
pom.dirty = true
_//}_

}
i had to comment the if part to make it work. then it reset the offset and working by really resetting the offset . do you think there is a reason why they wont reset to older offsets less than the pom.offset.

nice!
forgot to maintain that patch on master - updated it now. i'm not sure why upstream isn't allow resets to smaller offsets - i think it's a reasonable use case. here's the upstream issue: https://github.com/Shopify/sarama/issues/554
ok to close this issue?

closing the issue for now - @chandradeepak feel free to re-open if you run into any more related issues

@fgeller , thanks for letting me know about the issue opened in sarama. This issue is good to close now .  Thanks for the tool , it is cool.

👍 glad it is of help!


ILAMB Benchmark / ERA5 Example on NCI

ERA5 data are available on NCI https://opus.nci.org.au/display/ERA5/Data+Access
Idea is to build a config file for ILAMB to run BENCHMARK / ERA5 / ACCESS-ESM comparisons.
We could use ERA5-Land for a start.

I think we still need some mapping tool between ERA5 and CMIP variable, cause even if I found some corresponding variable between those two those two naming criteria, there still some difference like data structure and units, it will cost a lot of time on organise those things. and so far I have already  mapped one variable from ERA5 to CMIP format, so things gonna be very smooth if we have a mapping tool.


file_picker package compatibility issue on texture_renderer example

Help please, I can't seem to run the texture_renderer example cause of uncompatibility with the file_picker packgage, I was trying all different file_picker version from 8.1.2 until 8.1.5

/home/fadel/.pub-cache/hosted/pub.dev/file_picker-8.1.5/android/src/main/java/com/mr/flutter/plugin/filepicker/FilePickerPlugin.java:257: error: cannot find symbol
if (registrar != null) {
^
symbol:   variable registrar
location: class FilePickerPlugin
/home/fadel/.pub-cache/hosted/pub.dev/file_picker-8.1.5/android/src/main/java/com/mr/flutter/plugin/filepicker/FilePickerPlugin.java:260: error: cannot find symbol
registrar.addActivityResultListener(this.delegate);
^
symbol:   variable registrar
location: class FilePickerPlugin
2 errors

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':file_picker:compileDebugJavaWithJavac'.

Compilation failed; see the compiler error output for details.

Originally posted by @fadelfffar in https://github.com/rainyl/opencv_dart/discussions/33#discussioncomment-11538059

@fadelfffar I can't reproduce it with Ubuntu 24.04.
➜  texture_renderer git:(main) ✗ flutter build linux --release
Resolving dependencies... (1.0s)
Downloading packages...
+ async 2.11.0 (2.12.0 available)
+ boolean_selector 2.1.1 (2.1.2 available)
+ characters 1.3.0 (1.4.0 available)
+ clock 1.1.1 (1.1.2 available)
+ collection 1.18.0 (1.19.1 available)
+ cross_file 0.3.4+2
+ cupertino_icons 1.0.8
+ dartcv4 1.0.1
+ fake_async 1.3.1 (1.3.2 available)
+ ffi 2.1.3
+ file_picker 8.1.5
+ flutter 0.0.0 from sdk flutter
+ flutter_lints 2.0.3 (5.0.0 available)
+ flutter_plugin_android_lifecycle 2.0.23
+ flutter_test 0.0.0 from sdk flutter
+ flutter_web_plugins 0.0.0 from sdk flutter
+ leak_tracker 10.0.5 (10.0.8 available)
+ leak_tracker_flutter_testing 3.0.5 (3.0.9 available)
+ leak_tracker_testing 3.0.1
+ lints 2.1.1 (5.1.0 available)
+ logging 1.3.0
+ matcher 0.12.16+1 (0.12.17 available)
+ material_color_utilities 0.11.1 (0.12.0 available)
+ meta 1.15.0 (1.16.0 available)
+ opencv_dart 1.3.3
+ path 1.9.0 (1.9.1 available)
+ plugin_platform_interface 2.1.8
+ sky_engine 0.0.99 from sdk flutter
+ source_span 1.10.0 (1.10.1 available)
+ stack_trace 1.11.1 (1.12.0 available)
+ stream_channel 2.1.2
+ string_scanner 1.2.0 (1.4.0 available)
+ term_glyph 1.2.1
+ test_api 0.7.2 (0.7.4 available)
+ texture_rgba_renderer 0.0.16
+ vector_math 2.1.4
+ vm_service 14.2.5 (15.0.0 available)
+ web 1.1.0
+ win32 5.9.0
Changed 39 dependencies!
19 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.

Building Linux application...
✓ Built build/linux/x64/release/bundle/texture_rgba_renderer_example
➜  texture_renderer git:(main) ✗ screenfetch
                          ./+o+-
                  yyyyy- -yyyyyy+      OS: Ubuntu 24.04 noble
               ://+//////-yyyyyyo      Kernel: x86_64 Linux 6.8.0-49-generic
           .++ .:/++++++/-.+sss/`      Uptime: 1d 16h 28m
         .:++o:  /++++++++/:--:/-      Packages: 1900
        o:+o+:++.`..```.-/oo+++++/     Shell: zsh 5.9
       .:+o:+o/.          `+sssoo+/    Disk: 2.6T / 5.2T (51%)
  .++/+:+oo+o:`             /sssooo.   CPU: AMD Ryzen 9 9950X 16-Core @ 32x 7.835GHz
 /+++//+:`oo+o               /::--:.   GPU:
 \+/+o+++`o++o               ++////.   RAM: 64605MiB / 126404MiB
  .++.o+++oo+:`             /dddhhh.
       .+.o+oo:.          `oddhhhh+
        \+.++o+o``-````.:ohdhhhhh+
         `:o+++ `ohhhhhhhhyo++os:
           .o:`.syhhhhhhh/.oo++o`
               /osyyyyyyo++ooo+++/
                   ````` +oo+++o\:
                          `oo++.
➜  texture_renderer git:(main) ✗

Also, It seems not a problem of opencv_dart, why do you open the issue here rather than file_picker.
P.S., You do not need to use both opencv_dart and opencv_core, just choose one of them, depending on whether you need videoio module.

Sorry my bad for posting this as issues, on another note I forgot to mention that using Imageformat as in imencode(cv.Imageformat.png.cv, img, params) is not working on another example (i forgot which)

cv.Imageformat was deprecated a long time ago, you can use ".png" directly. cv.imencode(".png", image)

abdelaziz-mahdy has reported this in file_picker, check this:

https://github.com/miguelpruivo/flutter_file_picker/issues/1643

okidoki thanks for your help, I'm gonna close this issue

Hello, I have use the temporary fix from abdelaziz-mahdy, but get a GNUC_PREFEQ compiler error and a arm64-v8a error from dart cv, any idea why? thanks in advance ;)

I think you can just use 8.1.4, it works fine for me.

hmmm weird, I already tried that earlier. Does this need Nvidia gpu in anyway?

yes i ded, without the ^ on pubspec.yaml, maybe because I run it on android lol, thanks

All right, kind of weird...


Mook Generator Item Weight error

I'm having some issues with items in the mook generator. Whenever I use the weight with a decimal it drops the number before the decimal and makes the number after the decimal point an integer. E.g. 4.2lbs becomes 2lbs.

Good catch!   Yes, we were only scanning for digits.   I've fixed the code to also scan for periods.   It will be in the next release.


Fixing Order of DB Items Returned for Display in List Queries

This simple change just ensures that the result of listing entities as dictionaries will always be in order by ID so that results aren't swapped around when a new list is returned.

This change is

 Will I need to use the db migration tool on the db in my instance?  If so, guess it's a good chance to try the tool out.

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

No, you won't have to migrate anything. The schema actually doesn't change at all since each entity already had an ID field, but I added the ID field to the base abstract class to formalize that relationship. The other change was just in how results are returned.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Make terminal bright colors lighter than regular colors in Light+

Running this in bash:
echo -e '\x1b[44m blue bg \x1b[104m bright blue bg \x1b[0m'

Results in:

It would be best to differentiate these colors, even if just slightly.
Spotted this due to https://github.com/microsoft/vscode/issues/150858#issuecomment-1178667016, which is only an issue as the user disabled minimum contrast ratio. Don't try to ensure the right contrast ratio with the default foreground color as that will make it hard to see when using white backgrounds.

So would the ask be to make "terminal.ansiBlue" a lighter color?

To make all the terminal.ansiBright* ones slightly lighter


Unable to differentiate None and Some(Value::Null)

As the following example shows, I am unable to differentiate between two different cases:

when a null value is explicitly specified
when a value that could be a Value is omitted

use serde::{Deserialize, Serialize};

#[derive(Debug, PartialEq, Serialize, Deserialize)]
struct MyStruct {
    value: Option<serde_json::Value>
}

fn main() {

    let my1: MyStruct =serde_json::from_str("{}").unwrap();
    assert_eq!(my1, MyStruct {value: None}); // OK

    let my2: MyStruct = serde_json::from_str("{\"value\": null}").unwrap();
    assert_eq!(my2, MyStruct {value: Some(serde_json::Value::Null)}); // Error

}

This happens because null is deserialized as None instead of Some(Value::Null)

Any news?

Hi @dariocurr, sorry that no one was able to provide guidance here. You could try taking this question to any of the resources shown in https://www.rust-lang.org/community, and someone will be able to help you get this working in the way you'd like.

IMHO this is a bug. Anyway, thank you, I'll find a solution 😎


Open external App with com.lampa.startapp plugin

Hi,
I need to open an external app from the side menu... for example Telegram or Whatsapp.
In others apps I'm using this plugin:
cordova plugin add https://github.com/lampaa/com.lampa.startapp.git
Any way to do the same with WPHC ?
regards
MaX

That's not a built in feature but with enough knowledge it should be easy to use it within WPHC.


Add optional newline at the end of every message sent

Several systems operate on newline terminated streams to distinguish messages.
To support those, a new optional (and backwards) compatible flag is added: --append-newline | -n.
This ensures that any message, regardless of formatting, will be terminated with a "\n" character.
Tests are added, as well as help/docstrings.
Note, this was the cleanest implementation I could come up with, as the actual formatter is controlled by a class 2 levels away. Alternate implementations are welcome, but the functionality is critical for us in production.

Coverage increased (+0.3%) to 96.753% when pulling 7be2edc05564643cd74bee7868e9c1dfbbbb144c on krux:jib-add-newline into abc2c4742ef9f41257c7faf18bfa94d6cb2b2596 on dohop:master.

The tests on 3.x don't seem to pass although I don't know why. I can't see anything hat would necessarily cause them to timeout as they're doing. There was also an exception under 2.7, but it doesn't seem to have stopped or interfered with the tests. I need to take a look at this and work out what's going on with these tests and this PR.

Also I should mention, i reran the build in Jenkins and had the same timedout behaviour as the first attempt.

Hi @aodj - thanks for looking into this. I ran the tests both on python 2.6 & 2.7 and they came back clear (so no timeouts).
The timeout in 2.7 looks like a race condition where a write() gets interrupted by the sigterm, although I'm not sure where that'd occur exactly.
I'll try to get a python3 install running as well to see if I can reproduce that error.

There's definitely something strange going on - below are 2 gists (with supervisor debug turned on), 1 for python 2.7 and one for 3.4.
2.7 shows that tests run as you'd expect, and thanks to the wait_for=2 parameter, there's never more than 2 test messages shown.
3.4 shows that the test messages just keep coming, and after a while it just look stuck, so I ^C'd out.
Looking at the difference of packages installed, I diffed the output of ```pip --freeze`` for both of them. Note, for python3, we're using the system supervisor (version 3.1.3) rather than one installed in the virutalenv.
 diff -ruN 2.txt 3.txt
--- 2.txt	2016-04-16 12:28:43.000000000 -0700
+++ 3.txt	2016-04-16 12:30:40.000000000 -0700
@@ -1,20 +1,18 @@
 astroid==1.4.5
 colorama==0.3.7
 coverage==4.0.3
-lazy-object-proxy==1.2.1
+lazy-object-proxy==1.2.2
 linecache2==1.0.0
 mccabe==0.4.0
-meld3==1.0.2
 nose==1.3.7
 pep8==1.7.0
 pylint==1.5.5
 pylint-mccabe==0.1.3
 python-logstash==0.4.6
 six==1.10.0
-supervisor==3.2.3
 -e git+git@github.com:krux/supervisor-logstash-notifier.git@7be2edc05564643cd74bee7868e9c1dfbbbb144c#egg=supervisor_logstash_notifier
 testfixtures==4.9.1
 traceback2==1.4.0
 unittest2==1.1.0
-wrapt==1.10.6
+wrapt==1.10.8

@aodj anything I can do to move this along?

Coverage increased (+0.4%) to 96.805% when pulling d742c9e58a7d9b4fd4b83633b49e45cc22d9a59a on krux:jib-add-newline into abc2c4742ef9f41257c7faf18bfa94d6cb2b2596 on dohop:master.

Coverage increased (+0.4%) to 96.805% when pulling e833e2abd362138140e372482a8952e6c0e31026 on krux:jib-add-newline into abc2c4742ef9f41257c7faf18bfa94d6cb2b2596 on dohop:master.

@aodj thanks to my colleague @hanpeter, we figured out the problem was byte vs string in python 3. The above changes make tests pass in python 3, and even make pylint happy.
This should be good to merge from our side.
Let me know if you need anything else :)

Ah nicely found! Commits look fine, only thing I need to mull over is the wrapping of he logger to append newlines, but It's fine as is, and I can just think on what I want to do with it.

@aodj thanks for merging - i poked around to find a cleaner way than wrapping the formatter, but all that code was buried in the logstash plugin :( if you have any suggestions or want to brainstorm, happy to help.


Auto reload isn't working when Cargo.toml or Cargo.lock are changed outside of editor

When switching between master and kjeremy:mark-fixes-as-preferred things are not reloaded (it is enabled in the settings). There are changes to Cargo.toml and Cargo.lock so I would expect it to reload. The status bar does not change from "Ready".

Right, we probably should move the Cargo.toml stuff from OnDidSave to file-system watcher. Maybe we should just add Cargo.toml an Cargo.lock to the VFS, but I am hesitant to do that, admittedly for no real reason.

I'm not sure if this is the right issue for this, but rust-analyzer isn't picking up changes for Cargo.toml from cargo-edit either.
If you add a dependency with cargo-add, it won't be processed until you manually save Cargo.toml.

Another time when rust-analyzer doesn't pickup changes: cargo update
Fixing this would involve watching Cargo.lock for changes, I think.

I think this applies to rust-project.json as well.

This is super annoying is there any way I can help getting this fixed?

Sending a PR would help! I think what we need here is to just treat cargo.tomls and locks exactly as .rs files.
Sadly, this is a bit of code where fast&robust&high assuarance automated tests are hard, so we only test manually.

This is also something I find inconvenient, but I'm not in a position where I can spend the time to fix it. If I get that way in the future, and this isn't done, I'll try to work up a PR. Until then, maybe someone else will be able to :)

I put up a tentative fix in #9426, but I'm not sure it's correct.


[Feature request] Allow RGBLINK to determine the target of a rst

This shouldn't be too problematic: check that the symbol resolves to one of the 8 possible locations, and produce the corresponding opcode.
This would be part of a new object file specification, breaking backwards compatibility, but the new linker has support for reading several versions, so I believe it should be OK.

The motivation, I assume, is to allow things like rst wait_vblank_irq.
For comparison, the macro pack "ca83" for ca65 also allows this. As its rst implementation shows, this instruction doesn't even require specific linker support, just support for link-time expressions and assertions (see #292). Once that lands, RGBASM can assert that (target & $38) == target and emit .db target | $C7.

Well, it seems it'd be easier to add a new patch type instead of bolting on a check. Error reporting would also probably suffer.

Related issue in WLA-DX: https://github.com/vhelin/wla-dx/issues/213


navi command

https://github.com/casaub0n/casaub0n/blob/6efe84b4b77c6c578958b8cab386ca8c16c916a4/packages/dotfiles/profile/Microsoft.PowerShell_profile.ps1#L26

" can not work well on sd command
echo {} evaluates git commit --allow-empty -m \"[WIP] <commit_message>\" with escape sequence.
sd seems like to be not familiar escaped ", I guess

String-literal mode.   Non-regex find & replace. No more backslashes or remembering which characters are special and need to be escaped.
Easy to read, easy to write.   Find & replace expressions are split up, which makes them easy to read and write. No more messing with unclosed and escaped slashes.
Smart, common-sense defaults.   Defaults follow common sense and are tailored for typical daily use.

Extracting stuff out of strings containing slashes:
sd: echo "sample with /path/" | sd '.*(/.*/)' '$1'

 Write-Output 'git_empty`tWIP`tgit commit --allow-empty -m \"[WIP] <commit_message>\"' | sd '"\"(\w+)\t+(.+)\t+(.+)\""' '"\033[0;36m$2 \033[0;32m[$1]\n\033[1;93m> $3\033[0m"'

"" is allowed on Powershell


Only pull ceph image on bootstrap minion

With this PR, ceph image will only be pulled on the bootstrap minion.
All other minions will pull ceph image via cephadm latter when needed.
The main motivation for this PR is to prevent network overload when pulling the image on all hosts in parallel (e.g. > 100 nodes)
Signed-off-by: Ricardo Marques<EMAIL_ADDRESS>

I'm fine with this, though it seems like the "Prepare to bootstrap the Ceph cluster" stage would fit better in ceph-salt-formula/salt/ceph-salt/apply/cephbootstrap.sls now.

I've now remembered why we decided to pull images in ceph-salt before-hand... the idea was to guarantee that commands like cephadm shell don't pull the "wrong" image:
dpscalam15-master:~ # ceph config dump
WHO     MASK  LEVEL     OPTION                                 VALUE                                                                                RO
global        basic     container_image                        registry.suse.de/suse/sle-15-sp2/update/products/ses7/milestones/containers/ses/7/ceph/ceph  *
  mon         advanced  public_network                         <IP_ADDRESS>/23                                                                                *
  mgr         advanced  mgr/cephadm/manage_etc_ceph_ceph_conf  true                                                                                *
  mgr         advanced  mgr/cephadm/migration_current          2                                                                                *
  mgr         advanced  mgr/orchestrator/orchestrator          cephadm

dpscalam15-master:~ # cephadm shell
Trying to pull docker.io/ceph/ceph:v15...
...

In this example, cephadm shell pulled docker.io/ceph/ceph:v15 instead of registry.suse.de/suse/sle-15-sp2/update/products/ses7/milestones/containers/ses/7/ceph/ceph.
I'm afraid this prevents us from merging this PR.

Here is a PR to guarantee we will never have more than 10 minions pulling the ceph image at the same time: https://github.com/ceph/ceph-salt/pull/355

Would https://github.com/SUSE/ceph/pull/404 enable us to merge this?

Would SUSE/ceph#404 enable us to merge this?

If we merge that PR, should we consider removing the /containes/images/ceph config since it will be ignored?
master:~ # ceph-salt config /containers/images ls
o- images .................................................................................................................... [...]
  o- ceph ................................................ [registry.opensuse.org/filesystems/ceph/master/upstream/images/ceph/ceph]

Would SUSE/ceph#404 enable us to merge this?

If we merge that PR, should we consider removing the /containes/images/ceph config since it will be ignored?

Nothing is getting ignored. SUSE/ceph#404 simply provides a default, if /containes/images/ceph

no image is passed to bootstrap, or
there is no existing image to automatically deduce it.

...
Nothing is getting ignored. SUSE/ceph#404 simply provides a default, if

no image is passed to bootstrap, or
there is no existing image to automatically deduce it.

Exactly, if ceph-salt dont pre-pull image on all hosts, when you deploy a service on a host then the default image will be used, not the one specified in ceph-salt config. This is why I think this config will be useless if we merge this PR + https://github.com/SUSE/ceph/pull/404.

@sebastian-philipp I guess there is no harm in merging https://github.com/SUSE/ceph/pull/404 - we have to make our best effort in ceph-salt to ensure that all the cluster nodes get the "correct" image. What the "correct" image path is will vary from site to site, but I agree that in a supported SES7 cluster it will never start with "docker.io". So, let's merge https://github.com/SUSE/ceph/pull/404 by all means, but it doesn't have anything to do with the PR.
Now, regarding this PR: if we merged it, the bootstrap minion would pull the "correct" image path (defined as the one configured by the user), while the rest of the cluster nodes would get the hardcoded default image path, which might well be different. That wouldn't be good. Conclusion: I vote for closing this PR.

...
..., while the rest of the cluster nodes would get the hardcoded default image path, which might well be different. ...

It depends:

If you deploy a service on the host and then run cephadm shell
in this case, you will always pull the image defined in ceph-salt config

If you do it in the oposite order, run cephadm shell and then deploy a service
in this case you will pull both, because cephadm shell will will pull the default hardcoded one, and then service deployment will pull the onde configured in ceph-salt

I agree that merging https://github.com/SUSE/ceph/pull/404 is a good idea anyway.
Note that even if ceph-salt pre-pull the image, it's sill possible that user will remove that image manually and then run cephadm shell... in this case, we don't want to pull the upstream default

Relates to https://github.com/ceph/ceph/pull/33781

Relates to ceph/ceph#33781
We could resurrect #33781, but note that we are trying to avoid adding cephadm config file until really-really needed.

cephadm is on its way to become a proper software. I.e. proper python module structure, proper packaging etc. At that point we should think about having a proper configuration file for cephadm. Having to do downstream patches is a bad idea in general.
But that's pacific and not octopus.

but https://github.com/SUSE/ceph/pull/404 doesn't have anything to do with the PR.

I'd disagree here. It's also about where we want to put our time and energy into.
If we're ok with users maybe downloading the wrong downstream image and thus calling the wrong ceph binary when calling cephadm shell, then https://github.com/SUSE/ceph/pull/404 should suffice.
If we we really cannot do that, then we might want to continue with  #355 .
In general I'm aiming towards a future where we cepahdm should do the right thing in any case. Independent of ceph-salt.

If the following cephadm issue is fixed, then we can merge this PR: https://tracker.ceph.com/issues/47274

If the following cephadm issue is fixed, then we can merge this PR: https://tracker.ceph.com/issues/47274

note that this would just fix a race: As soon as the crash daemon is deployed on that host, cephadm shell is already using the correct image.

I'm fine with this, though it seems like the "Prepare to bootstrap the Ceph cluster" stage would fit better in ceph-salt-formula/salt/ceph-salt/apply/cephbootstrap.sls now.

Sure, done!

If the following cephadm issue is fixed, then we can merge this PR: https://tracker.ceph.com/issues/47274

note that this would just fix a race: As soon as the crash daemon is deployed on that host, cephadm shell is already using the correct image.

This seems to be a good reason to merge this PR.
When a new host is added, cephadm will deploy crash daemon on it, and to do that, cephadm will pull the same image that was used during bootstrap.
For now, as soon as crash daemon is deployed, it's safe do run cephadm shell.
When https://tracker.ceph.com/issues/47274 is fixed, then it will be safe to run cephadm shell at any time.


Camel k 1.12.0: camel:jta not found in Camel catalog

Hello,
We are migrating some services from Camel K 1.10.2 to Camel K 1.12.0, and I have encountered a problem with the camel-jta dependency. I tested it in a minimal example:
# camel-k: language=yaml
# camel-k: dependency=camel-jta

- route:
    id: main
    from:
      uri: timer:tick
      parameters:
        repeatCount: 1
      steps:
        - log: hello world

This integration runs without problem in Camel K 1.10.2. However, in Camel K 1.12.0, the following error shows:
kamel run main.yaml --dev
Modeline options have been loaded from source files
Full command: kamel run main.yaml --dev --dependency=camel-jta
Warning: dependency camel:jta not found in Camel catalog
Integration "main" created
Progress: integration "main" in phase Initialization
Progress: integration "main" in phase Error
Error: integration "main" deployment failed

On the Camel Quarkus website, it shows that this dependency should work in both Camel Quarkus 2.13 (camel-k 1.10.2) and Camel Quarkus 2.16 (camel-k 1.12.0):
https://camel.apache.org/camel-quarkus/2.13.x/reference/extensions/jta.html
Link to zulip post: link

The component is missing from the catalog.
@christophd I think you had a look at some similar problem recently. Probably it depends on Camel Quarkus platform, can you confirm?

Passing info from @christophd :
Problem caused by https://github.com/apache/camel-k/commit/2da65f2681f67904cfc719deb6573286be8ce92c: "Root cause is that camel-jta for some reason is not in the catalog and that we have added the validation check to raise errors if the component could not be found in the catalog in 1.12."
Reproduced:

minimal example integration runs correctly on v1.10.2
fails on v1.12.0 for both camel-jta and camel:jta
runs correctly on v1.12.0 after removing commit ^ https://github.com/apache/camel-k/commit/2da65f2681f67904cfc719deb6573286be8ce92c

also, we found out that camel-jta has never been in the catalog. it has been working with 1.10 because the explicit catalog check from 2da65f2 is missing in 1.10
I think we should also open a new issue in camel-quarkus to find out why camel-jta is missing in the catalog

There must be another mechanism that resolves dependencies besides that one working on the catalog because in 1.10.2 the integration is working ok despite the fact that the camel-jta is also not part of the catalog in this case.
In 1.12 it fails fast due to the check on the missing component in the catalog

Fixed by #4402

Also fixed by https://github.com/apache/camel-k-runtime/issues/1029


running the program

Hi, could you specify how to run these 3 files at windows ?
thanks

I added some generic installation instructions to the readme.
But for Windows (I'm rusty, but this should get you there):
Ensure you have Python installed and all three files are in the same directory.
Then, create a text file called my_env.py, also in the same directory.
Edit that file so its contents include your OpenAI API key as follows:
API_KEY='INSERT_YOUR_API_KEY_HERE'

Then you should be able to use Python to run stratepai.py, which is the main file.
You might also like to like to review and/or edit the code in stratepai_openai.py, which contains the model selection and prompt.


open source work that was expanded by LogRhythm and now incorporated back again.

@vrecan thanks Ben. Adding tests as agreed.


Swarm stack API

Hi
Do you know if there is issue/PR on stack API implementation ?
I can't find it
Today docker cli is doing all work for creating network/services/secrets from a composefile
I imagine a /stack api for listing / updating / remove stacks
It would be awesome for UI tools
Thanx for reading

The stack deploy feature is currently purely implemented in the client, and uses the regular services API. This may change in future (i.e., make "stacks" a daemon-side feature), but no ETA on that.
Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

https://forums.docker.com
the Docker community Slack channel
StackOverflow

I'm going to close this issue because this is not a bug, but feel free to continue the conversation 👍


Passing tokens to a server-side Blazor app

Opening a new issue for this as per @danroth27 request.
This is how you pass and use access tokens and refresh tokens to a server-side Blazor API
https://github.com/javiercn/blazor-server-aad-sample
There's several people asking for this on a regular basis, (AAD or any other provider) so this sample and associated redme covers it.
I'll leave it up to @danroth27 and the docs team from here.

This is up next immediately after 3.2p3 releases. My plan is to create a TOC node for Blazor Server in the Blazor Security TOC node (akin to our Blazor WebAssembly node there). The new node will have an Overview topic to receive our current Blazor Server guidance. The content on this issue will be a new topic in that node. If there's any objection to this plan, I'm :ear::ear::ear:.


Feature request: allow to remove the small bars below the clock

Great project, just sponsored it a little.
What is the purpose of the small bars below the clock ? I would like to see a feature to remove them in both the settings and through the API.

Hi,
the bars are the days of the week.
And if you use the "Big clock font" no weekdays should be displayed anymore.

the bars are the days of the week.

Ah right, makes sense now. I'm aware using the big clock wil remove the bars but I'd still like to see an option to use the small clock without the bars though if it's not too complicated to add.

I will have a look at it the days, I think that it does not need so much effort.

available in version 1.1.0


[android] Support for time zones in Android.

The time zone database in Android sits in a non-standard place, and it
can be overriden by a second location. Besides not sitting in a standard
place, it differs from other Unixes in that the database is bundled into
one binary file, and there are no folders with small files for each time
zone. Luckily the database is generated from Olson, so most of the
CFTimeZone code already handles the details.
The code implements a generic enumeration of the time zones contained in
the database (checking for both the override and the standard location).
The enumeration code is used for both enumerating the known time zones,
as well as creating time zones by name.
At many points there was code blocking the usage of time zones in
Android that has been removed.
This allows the tests in TestDateFormatter, TestCalendar and
TestTimeZone to pass on Android.

@swift-ci test

This might not apply cleanly without #2172. But one can look only at the second commit, if you want the Android specific changes only.

After fighting a little with the removal of __InitTZStrings and the multiple conditional compilation branches it introduces, I don’t think it is a great idea, but that's the code that it is up for review. If we want to back out of that change because it introduces complexity, we are still on time to do it.

@swift-ci please test

@compnerd, @spevans: thanks for all the feedback already. I was wondering if there's more pieces that anyone thinks need improving, or we can plan to merge this into master. Thanks!

Fixed some merge errors for the Android code.
@swift-ci please test

Heh, I had to make almost the same changes to the previous commit to get it to compile, though I didn't spot the fclose fix and it would segfault.
Now, several dozen more timezone tests pass on Android AArch64 with this latest commit, nice work.


Theme slider add label issue.

Theme slider add label issue.

Checked and Found that the issue has been fixed and found working. Please find the screenshot here


Add function(s) to process _RELS_EXT.rdf

This is a bit complicated because, ideally, 'collection_id' would be in all digital item-level base layer CSV, rather than a separate CSV.
In data_layer_config.py:
DIGITAL_ITEM_RDF_MAP = {
      'collection_id': {'bs_exp':['Description > isMemberOfCollection[rdf:resource]',]}
}

For example of RELS_EXT file, see pitt_31735047439256_RELS-EXT.rdf.

Modify if statement block to include 'collection_id' in extract_base_layer.py:
if u == 'copyright_status':
                # looks for attribute value and handles exception if no attribute
                results = bs_object.select(exp)
                try:
                    field_data += results[0]['copyright.status']
                except:
                    field_data += ''


Unicode support

Gogs version (or commit ref): <IP_ADDRESS>9
Git version: 2.8.1
Operating system: Windows 10
Database:

[ ] PostgreSQL
[x] MySQL
[x] SQLite

Can you reproduce the bug at http://try.gogs.io:

[x] Yes (provide example URL see screenshot)
[ ] No
[ ] Not relevant

Log gist:

Description
It is not possible to give the name of the repository in Unicode

A related issue is here: https://github.com/go-macaron/binding/issues/11
I made a small change of the regular expression, and it works well

Thanks your feedback!
Just want to make sure, will then require specific database charset in order to support unicode?
And why PostgreSQL is not chekced?

I dont use PostgreSQL. Well, I can check it out if I can find time :pensive:

No.. you don't need to, I think the validation rule is blocked using non-english letters anyway..

I changed the validation rules and use for three months without any problems :sunglasses:

I think to make progress on this, you can instead, suggest custom validation rule for user name and repo name, so for standard Gogs installation, won't have to deal with any possible strange unicode problem.

Suggest here or in the go-macaron?

Here. Better to file a new issue and reference this thread.


Improve Go to Rust memory ownership transfer

I'm a bit concerned that we are using undefiend behaviour when using Vec::from_raw_parts on memory that was not created in Rust but in Go. Rust documentations says explicitely this is not allowed:

"Creates a Vec directly from the raw components of another vector."
"ptr needs to have been previously allocated via String/Vec (at least, it's highly likely to be incorrect if it wasn't)."
"Violating these may cause problems like corrupting the allocator's internal data structures. For example it is not safe to build a Vec from a pointer to a C char array with length size_t."

On the other hand, this is what people on the internet recommend and it is unclear what the alternative is. Maybe a copy would be required instead of transferring memory ownership.
Acceptence criteria: either find a more stable solution or document why it is safe to ignore the warnings from Rust's Vec documentation.

It might be safer to use std::slice::from_raw_parts, which creates a non owning view into the Go created memory, and then copy this into a Rust vector.

Taken from a conversation in a private channel:
As a general rule:
Passing buffers from Go to Rust should require no copies at all, unless the Go GC is eager an may deallocate buffers before the functions that "own" them return, and until the Rust side needs to create copies of them for its own purposes (mutating, copying, etc).
Passing buffers from Rust to Go should require one copy on the go side, so the go code can use normal go types.
In both cases, the "sending" side should only provide a pointer and length to a buffer it owns. Then the other side can choose to copy it once, if it needs to. Since Go doesn't support borrowed references, it can use C.GoBytes(...) to directly copy the Rust slice passed to it. Similarly, Rust can use unsafe { std::slice::from_raw_parts(...) } to safely use go buffers directly, while they're in scope, and later use .to_vec(), or Vec::from(...) if it needs to copy them to represent a vector. (Because of the rules mentioned here: https://golang.org/cmd/cgo/#hdr-Passing_pointers I think that it has to copy the buffer this way in order to statically prevent confusing the Go GC)
So, concluding from this, i think what needs to be done is to replace the Buffer type with a SliceU8 type which consists of a pointer and  a length. This type will be constructed from raw parts of owned buffers (Vec<u8> and []bytes) on both sides of the FFI when sending data to the other side. The Buffer type should be renamed VecU8 and only returned from the allocate_rust function and functions called from Go directly.
For example, the cGet function should have this signature:
extern "C" fn(*mut db_t, SliceU8, *mut VecU8) -> i32

Was this resolved in #67 or is there something left to do here?

No, the comment above proposes further optimizations to the FFI which would cut down on the copies between Go and Rust

I assume this is still alive?
I will add it to the 0.9 milestone

I'm not going to tackle this for 0.9. Moving it to 1.0 milestone
unless @reuvenpo wants to take it on?

This task is pretty low priority (unfortunately, because i think it's interesting), since it's just an optimization that saves on the amount of copies between the different layers. I won't be free to touch on this until we wrap up all the more critical tasks.
You can move this to the 1.0 milestone, sure. Is the ABI between the Go and Rust sides of go-cosmwasm a versioned guarantee? if not then you can even push this to a later release.

I'm pretty confident this is done in 0.14. See e.g. Unmanaged vector:
/// An optional Vector type that requires explicit creation and destruction
/// and can be sent via FFI.
/// It can be created from `Option<Vec<u8>>` and be converted into `Option<Vec<u8>>`.
///
/// This type is always created in Rust and always dropped in Rust.
/// If Go code want to create it, it must instruct Rust to do so via the
/// [`new_unmanaged_vector`] FFI export. If Go code wants to consume its data,
/// it must create a copy and instruct Rust to destroy it via the
/// [`destroy_unmanaged_vector`] FFI export.
///
/// An UnmanagedVector is immutable.
///
/// ## Ownership
///
/// Ownership is the right and the obligation to destroy an `UnmanagedVector`
/// exactly once. Both Rust and Go can create an `UnmanagedVector`, which gives
/// then ownership. Sometimes it is necessary to transfer ownership.
///
/// ### Transfer ownership from Rust to Go
///
/// When an `UnmanagedVector` was created in Rust using [`UnmanagedVector::new`], [`UnmanagedVector::default`]
/// or [`new_unmanaged_vector`], it can be passted to Go as a return value (see e.g. [load_wasm][crate::load_wasm]).
/// Rust then has no chance to destroy the vector anymore, so ownership is transferred to Go.
/// In Go, the data has to be copied to a garbage collected `[]byte`. Then the vector must be destroyed
/// using [`destroy_unmanaged_vector`].
///
/// ### Transfer ownership from Go to Rust
///
/// When Rust code calls into Go (using the vtable methods), return data or error messages must be created
/// in Go. This is done by calling [`new_unmanaged_vector`] from Go, which copies data into a newly created
/// `UnmanagedVector`. Since Go created it, it owns it. The ownership is then passed to Rust via the
/// mutable return value pointers. On the Rust side, the vector is destroyed using [`UnmanagedVector::consume`].


[Bridge] Run JavaScript Code on background notifications

I'm not sure there's a definitive issue for this topic yet. Is it possible to run JavaScript code in the background, for example in response to background push notifications? For my specific use case I'd like to fetch data from the network and store it in a persistent database. The app will read from the database when becoming active and update its UI.
It would also be feasible to run a different JavaScript entry point module instead of the main app.
For my specific use case I'm relying on iOS libraries that I'd rather not have to rely on and instead use the JavaScript equivalents.

There have been a few issues created about background execution of the JS Runloop. I speak from experience.
From what i've seen. As of current, it's definitely suspended and what i've read, I don't think there's a way to make it wake up unless so-called signals are sent to it, which React Native doesn't do.
The solution most people are finding is creating ObjC extensions to make this possible.
See this thread: https://github.com/facebook/react-native/issues/1282

@jaygarcia I think it is now possible to run arbitrary JS in response to remote push notifications, even when the phone is locked and screen is off: https://github.com/facebook/react-native/issues/1282#issuecomment-173737204
Closing this unless I'm making this up.

Definitely, I am controlling music player while the app is in background - works. What's worth noting is that all intervals and timeouts are stopped by React, but - if you have some handlers registered on NativeAppDeviceEmitter - they will be called and if you setState on that, this will be respected as well (e.g. if you call some native APIs in componentWillReceiveProps).

hi guys, does someone knows - is it react native that postpone http fetch calls or is it happening on native layer?
I have IOS application with background modes Background fetch and Remote notifications. I can receive notification while the application is in background. It triggers HTTP request (via fetch api) but the result comes only after I switch application to foreground (most likely whole http request is only executed in foreground).
Is it RN "fault" (or intention :)) or am I missing some permissions on IOS level?

@grabbou do you have a sample code snippet how you manage to execute a js while the app is in the background?
I'm building a music player too with a module that makes the app runs in the background, even lock screen. But the thing is. I was not able to update the module via JS because it's preventing JS execution for some reason.


Init project with basic DevOps CI flow using pytest and .drone.yml

Changes

add a basic CI flow with .drone.yml
init the project with a source root

Do you have any experience with using drone? Otherwise, I would prefer Travis and it's free for open-source projects : )

Do you have any experience with using drone? Otherwise, I would prefer Travis and it's free for open-source projects : )

Yes, we use Drone at LINE. Since the Drone server has been installed in our NTU Lab's cluster, so I think it's more convenient to use Drone in this project.
Do you have any comments regarding our DevOps flow? e.g. pytest, or dependency management (currently, requirements.txt), We are totally unfamiliar with them ˊˇˋ

Do you have any comments regarding our DevOps flow? e.g. pytest, or dependency management (currently, requirements.txt), We are totally unfamiliar with them ˊˇˋ

I recommend using pipenv.

poetry or pipenv are all fine IMO. Personally, I prefer poetry because with less issues : p
If @Johnny850807 you're gonna change the service to Travis, should we move to a new PR? or you will do it in the same one?

poetry or pipenv are all fine IMO. Personally, I prefer poetry because with less issues : p
If @Johnny850807 you're gonna change the service to Travis, should we move to a new PR? or you will do it in the same one?

#3 and #2  are created


:memo: Initialize Webdriver helper doc

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage     29.87%   29.87%
  Complexity       39       39
=========================================
  Files             2        2
  Lines            77       77
=========================================
  Hits             23       23
  Misses           54       54

Continue to review full report at Codecov.

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


Exit proc_lib gracefully on proxy header mismatch

If the proxy header was not to match (like, the header not being sent),
cowboy libraries were expecting really strict matching and then crashing
the proc_lib with a badmatch, that generates a hard error report. I
believe this error should be expected and termination should be graceful.

Why wouldn't you want this to be logged?

Why wouldn't you want this to be logged?

Put it another way, why would you do so just here? I think that the cause of death should be handled elsewhere and be given a chance to decide what to do with it. For example, I believe ranch already logs this.

You've made it into a shutdown, shutdowns aren't logged: https://github.com/ninenines/ranch/blob/master/src/ranch_conns_sup.erl#L388
The proxy header missing is most likely a configuration error (on the proxy side), it should provide as much information as possible about the problem.

You've made it into a shutdown, shutdowns aren't logged: https://github.com/ninenines/ranch/blob/master/src/ranch_conns_sup.erl#L388
The proxy header missing is most likely a configuration error (on the proxy side), it should provide as much information as possible about the problem.

Ah, that's the ranch line I was looking for. But then the issue is that the same error is logged twice, once as a crash report for proc_lib, another from Ranch's supervisor, isn't it?

I have no idea what broke so much in the CI but wow how red everything is. Nevertheless I'm stuck wondering, how to deal with the crash reported twice (by proc_lib and ranch respectively).

That's just the way it's done, you get a crash report and a supervisor report. Nothing unusual, you get the same for gen_*+supervisor as well.

You've made it into a shutdown, shutdowns aren't logged: https://github.com/ninenines/ranch/blob/master/src/ranch_conns_sup.erl#L388
The proxy header missing is most likely a configuration error (on the proxy side), it should provide as much information as possible about the problem.

What about the case when the port is only being probed, that is, a load-balancer is only doing a tcp handshake and closing the connection, without sending any traffic whatsoever?

Is there a deployment that has the combination of PROXY and such load balancer?

@essen tested in my environments, I do get {error, closed} and logs aren't dirty with crashes.

OK thanks. It looks fine, I will just need to find time to look into it properly. It's either going to be tomorrow or in weeks. Hopefully tomorrow!

Please don't add a new test group and instead make the test against all http/https/h2/h2c instead so we know it's working for both TCP and TLS and all protocols.

Please don't add a new test group and instead make the test against all http/https/h2/h2c instead so we know it's working for both TCP and TLS and all protocols.

Easy to change, just did it locally, but then it seems that some tests are failing randomly I suppose because of some race condition.

Make sure it connects to the right host/port and if you can't figure it out please post the errors you see.

Just pushed the test, it generally fails the https group with a timeout when waiting for the 'DOWN' message.

Right, the Pid that ct_helper:get_remote_pid_tcp/1 is not the same than the socket is listening to, so it doesn't receive the DOWN message. This happens only for the https and h2 groups, seems now deterministic.

There's a separate function for TLS.

There's a separate function for TLS.

Just saw that, but that won't work, because it's doing ssl:sockname, and this socket is not yet a ssl socket, it's a barebones tcp:connect one.

@essen now, I've pushed a new version of the test that does a bit of a hack, hopefully elegant, to correctly find the process we want to track the dead of. Hope you like the code, I await your comments :)

@essen did you have a chance to review the latest changes? :)

No but the tab is still open for whenever this can happen.

No but the tab is still open for whenever this can happen.

Hi there, it's been a while, how's progress on this one? :)

@essen heads up on this, any updates, plans?

@essen it has been a while with no activity here, any updates on when, and if, this could be merged?

When I have some free time. I think the PR is fine as-is by the way but I need to test it.

It's been quite a while since I worked on this and now this test seems to be failing in CI, however I can't even ct running locally. Do you have a guide somewhere on how to run tests? I'd like to fix this issue but I can't find how.

Should be just make ct but otherwise check https://erlang.mk it has plenty of documentation.
It's likely a race condition in the test itself.
I am going through a number of tickets/PRs so if you can work on this, great! If not, also great, I'll just pick it up when I get to it. Cheers.

I've merged with minimal changes to the tests. Closing, thanks!


Chart Editor Crashing

Describe your problem here.
Trying to take a chart from another engine and load it into Psych. I have successfully loaded up the chart editor but when saving it gives me this crash. I have no idea what i'm doing wrong or how to fix it. Just updated to 6.2 recently and it still doesn't work. Loading the song gives me a different error but it still isn't working.
PsychEngine_2022-07-01_21'53'39.txt
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, Ive added A   L O T

I think your chart may be missing some stuff, like arrowSkin and splashSkin ?

I think your chart may be missing some stuff, like arrowSkin and splashSkin ?

I t h i n k I figured it out. I was using a chart from the 'YoshiCrafter' engine and for some reason the events in the JSON file of the chart couldnt be loaded in Psych. All I had to do was go into the JSON and delete all the event data there.


"mailto" does not work - potential bug

I"m using the latest release "v1.0.3" and the email share does not work (nothing happens when you click). After some debugging I believe I found the issue.
The email link has a "return false" function on click, which should not be there:

at line 248 in share-button.js file , You have the following if statement
if (network.className !== 'email')
          a.setAttribute('onclick', 'return false');

Since you always have multiple class names (share type && enabled )  the condition will never return true  and therefore  mailto link will have onclick="return false".
If you replace the above if statement  the following, it should  fix the issue:
 if (!((' ' + network.className + ' ').indexOf(' ' +'email'+ ' ') > -1)){
       a.setAttribute('onclick', 'return false');
  }

+1

+1

+1

+1 is there no fix for this?

1

+1

Sorry for the inactivity, this will be resolved soon!

Just merged the fix! I'll release an update in the morning :sunrise:

Hi @hhsnopek, has this fix been released?
I still see the issue in chrome and safari mobile

Hey @m00s this fix hasn't been released yet - I was hoping to do so... well 22 days ago, I'll get to this soon :smile:

@hhsnopek many thanks :pray:


Error using custom Element with Generics

I'm creating custom tags that do not yet exist in the bridge.html5 namespace like nav aside i.
I have that:
[External]
[Name("HTMLNavElement")]
public sealed class HTMLNavElement : HTMLElement<HTMLNavElement>
{
    [Template("document.createElement('nav')")]
    public HTMLNavElement() { }
}

Then if I want to use a generic class that uses this class:
public class ClassA<T> where T : HTMLElement
{

}

public class ClassB : ClassA<HTMLNavElement>
{

}

I get a browser error:
"Uncaught ReferenceError: HTMLNavElement is not defined".
If I use
public class ClassB : ClassA<HTMLDivElement>
{

}

Everything works correctly.

You are getting this error because HTMLNavElement is defined as [External] so Bridge is expecting the definition of this class to be provided elsewhere (not controlled by Bridge).
The HTMLNavElement class does not exist during runtime. Your ClassA<HTMLDivElement> sample works because HTMLDivElement does exist during runtime.
See Also

Support for Custom Elements #2580

The implementation of HTMLDivElement is the same as I did in HTMLNavElement
https://github.com/bridgedotnet/Bridge/blob/master/Html5/Elements/HTMLDivElement.cs

The implementation of HTMLDivElement is the same as I did in HTMLNavElement

Yes, but HTMLDivElement exists on the client, and HTMLNavElement does not.

ok, I got it!
Thanks!

The issue in the initial sample could be solved by applying [Virtual] attribute instead of [External] (see more details here).


Using a specific branch from git dependency

Problem description
I wanted to finally drop some ugly pip postinstalls and use git dependency.
I wanted to install some hotfixed branch of git repository, but I met some unexpected behavior (at least for me)
ffmpeg-python = {git= "https://github.com/charlienewey/ffmpeg-python.git", branch = "bugfix/782"}

This resulted in using last commit from main branch anyway, even tho I specified the "bugfix/782" branch.
To get exactly what I wanted I had to pass concrete commit sha.
ffmpeg-python = {git= "https://github.com/charlienewey/ffmpeg-python.git", branch = "bugfix/782", rev="37dd98ca210fb8132575bedd719c6f8f9bfd1021"}

My question is whether it is intended behavior? I couldn't find "branch" option for git dependencies described in docs yet.
It would be more convenient if passing branch resulted in using the most recent commit.

The hard problem with this is the decision when we update the lockfile.
If you would always want to check if there is a new commit on that branch it would be slow to run pixi commands as pixi run also updates environments.
An pixi update command would fix it and would make the logic more like cargo.

Right, was just a bit surprised that still installed main head instead of what would happen with git checkout bugfix/782. Probably one more line in docs would've made it clear, but I can expect it is rarely used feature yet.
pixi update would be crazy for sure, good luck and thanks for recent updates :)

I was hit by a simliar issue today when trying to add a dependency on a git branch.
dependencies = ["moviepy@git+https://github.com/blooop/moviepy.git@feature/decorator_update"]

output error:
  × Unsupported pep508 requirement: 'moviepy @ git+https://github.com/blooop/
  │ moviepy.git@feature/decorator_update'
  ╰─▶ Found invalid characters for git revision 'feature/decorator_update', branches and
      tags are not supported yet

@blooop unfortunately for now you can only use rev tag. So it's limited to using only specific commit now.
pixi update command has been added already, but I'm not sure if current implementation is enough to make using branches or tags easy.

We should give this a look again relatively soon, as I think with the latest uv upgrades this has probably become a lot easier as well.

Thanks.  I have found a workaround for the moment, and its good to know its likely to be fixed in the future.

Thanks. I have found a workaround for the moment, and its good to know its likely to be fixed in the future.

@blooop Just wondering about the workaround..
I'm using pixi with pyproject.toml, and facing the similar Unsupported pep508 issue when doing 'pixi install/update'.
While pip install . works fine, I'd prefer not to fall back.
pixi 0.29.0
python 3.11.9
pip 24.2


Testing the SQL snippet

SQL snippet:
select * from dual

Trying to figure out why the image was not generated for the above... Tested locally but did not face any issue. Let's try that again shall we...
select * from dual;

Trying again with debug statements
select * from dual;

another test
select * from dual

@cresmet Was able to determine the issue - Prettier failed.
You can only test code that babel parses since the default configuration for my repo uses babel as the parser. If you have installed the Action in your repo, then you can use the prettier-parser input for the Action to select a different code parser.
Basically, you can only test with javascript based code in this repo. You would need to install the Action in your own repo to test with a different parser - one that is based off the type of code in your project

Alternatively, in your Action, set use-prettier to false - that will disable prettier and proceed to parse your code...
However, I will still take this as a bug. It should not have failed and instead should have skipped using Prettier...

Ok. Fix is in. Testing now:
select * from dual;

Fixed in v1.0.1

Closing due to inactivity


Switch to use CodeStructureService in DocumentSymbolHandler.

This PR will get outline view working in VS Code when using LSP.

Needs https://github.com/OmniSharp/csharp-language-server-protocol/pull/123 (ping @david-driscoll)
Fixes #1407

Works (but still blocked by https://github.com/OmniSharp/csharp-language-server-protocol/pull/129)

@david-driscoll don't know if LSP update broke renamehandler, but at least it's not working. Seems to pick the wrong symbol.

Updated LSP packages to release. Fix rename stuff in separate PR here #1423
Ready for review @david-driscoll @filipw @rchande


Feat: added quest page

added questions in data file
made reducer
option color change based on selection

Deploy preview: https://deploy-preview-2--utopia-project.netlify.app/

Thank You Both, Merging now :)


Device Storage

Changed KnownDevices to use MetricStorage instead of a List of Metrics
Refactored SparkplugNodeBase.PublishMessageForDevice
Fixed an assignment issue where the DeviceIdentifier would represent itself as the EdgeNodeIdentifier in the DeviceDataEventArgs

This should resolve #28

I need to check this, but looks good from the first view.

I need to check this, but looks good from the first view.

Any update?

Sorry for the delay. I have integrated your pull request and need to test it a bit more for now. An update should be available soon :)


Fix configure-nightly script to match new contents of core.ts

Fixes https://github.com/Microsoft/TypeScript/issues/17012#issuecomment-313727516

👍

@yuit Could you review too?

Can you merge this in?


mapper(u0)  not defined for AttractorsViaFeaturizing

In the docstring of AttractorsViaFeaturizing we have:
This `mapper` also allows the syntax `mapper(u0)` but only if the `grouping_config`
is _not_ `GroupViaClustering`.

but the function is not implemented:
   function dumb_map(z, p, n)
        x, y = z
        r = p[1]
        if r < 0.5
            return SVector(0.0, 0.0)
        else
            if x ≥ 0
                return SVector(r, r)
            else
                return SVector(-r, -r)
            end
        end
    end

    r = 1.0
    ds = DeterministicIteratedMap(dumb_map, [0., 0.], [r])
    u0s = [1 => [r, r], 2 => [-r, -r]] # template ics

    xg = yg = range(-2.0, 2.0; length=100)
    grid = (xg, yg)
    expected_fs_raw = Dict(1 => 0.5, 1 => 0.5)
    featurizer(A, t) = SVector(A[1][1])

function features_from_u(u)
    A, t = trajectory(ds, 100, u; Ttr = 1000, Δt = 1)
featurizer(A, t)
end
templates = Dict(k => features_from_u(u) for (k, u) in u0s)
config = GroupViaNearestFeature(templates)
mapper = AttractorsViaFeaturizing(ds, featurizer, config; Ttr=500)
mapper([1., 0.])

returns:
ERROR: MethodError: objects of type AttractorsViaFeaturizing{DeterministicIteratedMap{false, SVector{2, Float64}, 2,
typeof(dumb_map), Vector{Float64}}, GroupViaNearestFeature{1, Float64, NearestNeighbors.KDTree{SVector{1, Float64},
Euclidean, Float64, SVector{1, Float64}}, Vector{Int64}}, typeof(featurizer), Int64, 2, Float64} are not callable
I will propose a PR to solve this. It is not crucial but it a convenience function that is helpful.

Sorry @awage the docstring is wrong. With GroupViaNearestFeature it is not possible to do mapper(u0). There is simply no other nearest feature to map to, so it doesn't make sense. We just need to correct the docstring.

It is possible since you give the templates to GroupViaNearestFeature. :
Then, generated features from initial conditions in AttractorsViaFeaturizing are labelled according to the feature in templates that is closest (the label is the index of the closest template).
So it works in a similar fashion to AttractorsViaProximity but with features. In #138 the mapper is functional.

Ah, sorry, I mistaken this with the other version that Kalel added, the pairwise comparison. good.

Solved in PR #137


Add config option eval.extended-syntax in GraalJS

Currently extended syntax (nested {}) is always enabled in graal.
But it is better to have an option to enable/disable it for compatibility enhancement.
This PR introduces eval.extended-syntax (true|false)  option.
The default is true. So the behavior is same.
This PR also includes unit test for extended syntax and document.

@frsyuki Our highest priority is migrating to GraalJS with Java11 smoothly.
I understand extended syntax is convenient. So I keep enable as default in "graal" mode.
But if it causes critical incompatibility in our service, we cannot enable it right now.
I will do test with false and if no issue happen, I will also do test with true. Then make decision.
Even if we can't enable it as result of test, we can test and improve after migration.
I think nashorn-graal-check is excellent idea and will expand to more general way in the future.
For example if we can set main=graal, check=graal+extended_syntax, we can check compatibility of extended_syntax. If we want to introduce something incompatibility feature, this way will work.
Anyway I would like to divide large things and apply gradually to avoid critical incidents.

OK, I see. So,

(A) You think two smaller migrations with faster deliver of the first migration could be better, while I think one-time migration is better even though the first delivery delays.
(B) You think extended-syntax could have significantly big impact on backward compatibility, while I don't.

(B) needs data to verify but I agree that verifying it using a working code is reasonable.
(A) depends on how we think about customer/user's manual work involved for the migration.


[BUG] Miss aligned mountain image on hero and footer section on different screen sizes.

The mountain image is not centered when the screen size is bigger than 1920x1080. The screenshots are taken from a monitor of 2560x1440.

Duplicate of #63


Move #rit-foss back to latest TeleIRC release once new release is tagged

#rit-foss is currently being used as another testing bed for TeleIRC, running off HEAD for the remainder of these summer days. However, since this channel is used for classroom communications, we should move it back to the latest stable {{ default_version }} once the next release is out.

@jwflory since we don't currently have plans to cut a release soon, should we simply move #rit-foss back to the latest release since the semester has started?
I haven't looked into what changes we've made since the last release, but I think we should either cut a minor release with what we have (html escaping and other fixes), or just revert this channel back.

@Tjzabel I'm in favor of cutting a new release and distributing this version more widely on the services we maintain. Will you be at FOSS Hours this coming Thursday?

@jwflory Yes, I will be at FOSS Hours this Thursday.

@Tjzabel Awesome – if we can grab 30 minutes there, I can run you through the release process I am following and we can push a new TeleIRC release out.

Sounds good :+1:

This was done last night! See FOSSRIT/infrastructure#55. Closing as complete.


feat: make build type

This PR adds the make build type in rockspecs.
This is a draft as I haven't tested it whatsoever on real world rocks :)

Also, there may be aspects that I missed from the original luarocks codebase w.r.t edge cases for this build step. I'll have to do some thorough testing.

This is now stacked on #109.
I think it's ready to be merged.

LGTM


.NET MAUI sample status progress

Issues found during this challenge:

https://github.com/dotnet/maui/issues/9484
https://github.com/dotnet/maui/issues/9485
https://github.com/dotnet/maui/issues/10479
https://github.com/dotnet/maui/issues/10478

More tests using the latest .NET 7 and .NET 8 versions.
.NET 8
Image inside border misaligned on Android.


How to browserify fluentReports?

Hello,
I tried to use browserify to bundle up fluentreports in a js that can run in the browser, however I ran into some problems. Here's what I did: I installed fluentreports, pdfkit, blob-stream into node.js, then in the fluentreports downloaded directory, I ran:
browserify lib/fluentReports.js -o fr-bundle.js
However, here's what I got:
SyntaxError: Line 92: Unexpected token ILLEGAL while parsing /Users/mar/Downloads/fluentreports-master/node_modules/pdfkit/js/font.js
at Stream.end (/usr/local/lib/node_modules/browserify/node_modules/insert-module-globals/index.js:71:21)
at _end (/usr/local/lib/node_modules/browserify/node_modules/insert-module-globals/node_modules/through/index.js:65:9)
at Stream.stream.end (/usr/local/lib/node_modules/browserify/node_modules/insert-module-globals/node_modules/through/index.js:74:5)
at Transform.onend (/usr/local/lib/node_modules/browserify/node_modules/readable-stream/lib/_stream_readable.js:505:10)
at Transform.g (events.js:180:16)
at Transform.emit (events.js:117:20)
at /usr/local/lib/node_modules/browserify/node_modules/readable-stream/lib/_stream_readable.js:942:16
at process._tickCallback (node.js:419:13)
I'm very new at node.js, and am not sure whether all node modules can work with browserify.
Thanks a lot in advance.
Best regards,
M.

Just for those who care; the latest versions do work fully with browserify.   The demo site; http://www.fluentreports.com uses browserify to build the file.


docs(docker): Add ID mapping to docker commands

Without this, the workspace files are created with uid/gid 0 and thus belong to "root". They can then not be edited by the user who invoked the docker command in the first place.

I've just found the hidden feature to USE_SYSTEM_CA_CERTS .
When using the uid:gid mapping as I proposed in this PR, then the USE_SYSTEM_CA_CERTS feature breaks.
I think I'll have to incorporate the uid:gid mapping by passing this as an ENV variable to the container, and changing uid:gid at the last moment (when running exec "$@" in /__cacert_entrypoint.sh )