[Select] Touch Issue with select component (Firefox)

Bug report
Current Behavior
When using mobile touch emulator on Firefox the select menu does switch to the new option on first touch.
I would assume that this could cause a problem in some mobile browser. But I am not sure that it does. At the very least it is annoying .
Expected behavior
Select the option when selecting and option in the select menu
Reproducible example
The example on the radix ui exhibits this behavior. You must be in mobile view on Firefox with touch simulation turned on.
CodeSandbox Template
Your environment

Software
Name(s)
Version

Radix Package(s)

React
n/a

Browser
Firefox
<EMAIL_ADDRESS>

Assistive tech

Node
n/a

npm/yarn

Operating System

happens on Windows and Linux Ubuntu

I'm not sure what you mean, this is what I see:
https://user-images.githubusercontent.com/1539897/160611256-1912d5ed-0140-4241-8ad8-4b773277546e.mov

@benoitgrelard On chrome you do not have to click the option twice. It selects the option on first touch. Notice in your screen capture you have to click on pineapple / courgette twice. on the first click it focuses it and then on the second click it selects it.

Have you tested on firefox on a real device? Could it potentially be a quirk of the emulation?

I can confirm that this is an issue on my phone (Pixel 2, Firefox 100.2).
It appears just as @benoitgrelard 's screengrab shows; two presseses need to select the option, with the first highlighting the option you've selected.

@equal-matt Thanks for confirming, I totally forgot to do it.

Hi @equal-matt, @DanielBailey-web, we have recently made some fixes to some underlying logic which I suspect may be related to this Select issue. Would either of you be able to test the latest Select rc on a mobile device with Firefox?
The easiest way will be to:

go to this page: https://www.radix-ui.com/docs/primitives/components/select
click on the codesandbox icon in the bottom right corner of the demo at the top of the page
update the version of Select to the latest rc (0.1.2-rc.28 at the time I'm writing this, so needs to be this or higher)

Let me know what you observe,
Thanks 🙏

@benoitgrelard Just tested it and it's back to normal on 0.1.2-rc.28. 🎉
FYI if things like this come up again it's actually quite hard to edit CodeSandbox on mobile - it would be really helpful to fork and send a link to an environment that's set up already.

Thanks for confirming! I will close the issue.

FYI if things like this come up again it's actually quite hard to edit CodeSandbox on mobile - it would be really helpful to fork and send a link to an environment that's set up already.

Thanks also for noting this, I didn't think about it but will definitely consider it for next time.

Closed via #1401


rqt_joint_trajectory_controller: Use urdf_parser

Maybe we can use the upstream urdf_parser_py? The mentioned issue got fixed years ago..
https://github.com/ros-controls/ros2_controllers/blob/925a690fcb469cb705ec67185cd67c6f1481dd61/rqt_joint_trajectory_controller/rqt_joint_trajectory_controller/joint_limits_urdf.py#L17-L20

Hello @christophfroehlich , are we going to do this work? If yes, I can give it a try.

no one is working on that afaik. Thanks for picking this.
I just had the idea when we were fixing a bug. Please check if it really makes sense/supports all we need before you start coding!


[CH] Unsupported spark function list [please leave a comment if you plan to pick some]

Description
Here listed spark functions still not supported by Gluten CH backend. Please leave a comment if you'd like to pick some. In the below list, [√] means someone is working in progress for the corresponding function.

[ ] https://github.com/apache/incubator-gluten/issues/6816
[ ] https://github.com/apache/incubator-gluten/issues/6815
[ ] https://github.com/apache/incubator-gluten/issues/6814
[ ] https://github.com/apache/incubator-gluten/issues/6813
[ ] https://github.com/apache/incubator-gluten/issues/6812
[ ] https://github.com/apache/incubator-gluten/issues/6811
[ ] https://github.com/apache/incubator-gluten/issues/6810
[ ] https://github.com/apache/incubator-gluten/issues/6809
[ ] https://github.com/apache/incubator-gluten/issues/6808
[ ] https://github.com/apache/incubator-gluten/issues/6807
[x] https://github.com/apache/incubator-gluten/issues/6806
[x] https://github.com/apache/incubator-gluten/issues/6805
[ ] https://github.com/apache/incubator-gluten/issues/4945
[ ] https://github.com/apache/incubator-gluten/issues/4730
[ ] Kurtosis
[ ] UnixMillis
[ ] UnixMicros
[ ] MillisToTimestamp
[ ] MicrosToTimestamp
[ ] Stack
[ ] TransformKeys
[ ] TransformValues

@taiyang-li let's discuss this

can you merge this issue into #4039? Github allow only 3 pinned issue.


Add get_allies and get_enemies to basegroup.py

note I don't do python often, check for bugs and optimizations before adding

Just tested your code out the paginator is not compatible with group Relationships endpoints
aka if we want this we would need to make a new Iterator for this endpoint

I know, thats why I moved this to draft. Needs a new paginator.


Documentation issue: wrong file name in TLS instructions

Expected behavior
Following the instructions for generating a server certificate at https://pulsar.incubator.apache.org/docs/latest/security/tls-transport/#Servercertificate-av2fql should provide me with a server certificate.
Actual behavior
The step labelled "… and sign it with the certificate authority." fails with:
proxy.csr.pem: No such file or directory

Steps to reproduce
Follow the instructions on the page.
System configuration
Pulsar version: n/a
Solution
The step labelled "Generate the certificate request…" needs to be adjusted to use the "broker.csr.pem" file name as last argument, not "broker.cert.pem" - it's generating the CSR after all. It should read:
openssl req -config openssl.cnf \
      -key broker.key.pem -new -sha256 -out broker.csr.pem

@peterbecker I think you are using an old website link, can you try using the instructions here: https://pulsar.incubator.apache.org/docs/en/security-tls-authentication/ ?

The page you link is the TLS auth page. Mine is the encryption one. You can follow the link on the page you linked, which takes you to https://pulsar.incubator.apache.org/docs/en/security-tls-transport/ which still has the issue.

@peterbecker you're right. Will update.

This is fixed by #2531


Object metadata is not retrieved if field metadata is already retrieved (custom settings)

Summary
Running the command "sfdx force:source:retrieve --loglevel fatal -m CustomObject:xyz" fails to retrieve xyz.object-meta.xml if a field on the object has already been retrieved.
Steps To Reproduce:

Create a new custom setting "AMLAlarmConfiguration" (AMLAlarmConfiguration__c).
Create a new field "CreateAlarmCase" (CreateAlarmCase__c) on AMLAlarmConfiguration__c
Execute "sfdx force:source:retrieve --loglevel fatal -m CustomField:AMLAlarmConfiguration__c.CreateAlarmCase__c" to retrieve the field.
Execute "sfdx force:source:retrieve --loglevel fatal -m CustomObject:AMLAlarmConfiguration__c" to retrieve the object.
Verify that "AMLAlarmConfiguration__c.object-meta.xml" has not been rtetrieved.

Expected result
The object metadata "AMLAlarmConfiguration__c.object-meta.xml" should have been retrieved from the org.
Actual result
"AMLAlarmConfiguration__c.object-meta.xml" is not present.
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.112.1 win32-x64 node-v14.17.4
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core):
@oclif/plugin-autocomplete 0.3.0 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.2 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.10.1 (core)
@oclif/plugin-update 1.4.0-3 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-diff 0.0.6
@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.10 (core)
apex 0.2.3 (core)
auth 1.7.1 (core)
config 1.2.14 (core)
custom-metadata 1.0.12 (core)
data 0.6.0 (core)
generator 1.1.7 (core)
limits 1.2.1 (core)
org 1.6.7 (core)
salesforce-alm 52.2.3 (core)
schema 1.0.8 (core)
sfdx-cli 7.112.1 (core)
sfdx-git-delta 4.8.1
source 1.0.6 (core)
telemetry 1.2.3 (core)
templates 52.1.0 (core)
user 1.4.0 (core)
OS and version:
Windows 10

Hey @pfrandsen, I am unable to replicate this issue. I've tried with CLI versions 7.112.1 and 7.119.2 (latest) on a Mac and 7.119.2 on Windows. Try updating your CLI and try again. If that doesn't work, it's possible it depends on the specific settings of the Custom Setting you are using, you could share more details on how it's configured.


Included CVE-2019-0686 and CVE-2019-0724

Added the security vunerabilites to the script.

@lusassl-msft please review. I believe I placed everything back in correctly. I reverted one of the commits, but then I realized why you moved it out of the current CU if statement like we were previously doing.


Adds notification when saving and publishing a resource.

closes #1032

@justinlittman when testing this locally, the message shows up for about 3 seconds, then clears. Is that expected?

Yes. I should have made that clear in PR.


SQL compound statement awareness in ScriptUtils

This came out of #570. In brief, for DB init script handling, ScriptUtils is not capable of handling scripts that contain compound statements in stored procedures (BEGIN...END sections). It will simply split the script on semicolons, mid-procedure, thus breaking the script.
An example would be:
CREATE PROCEDURE count_foo()
    BEGIN
      SELECT *
        FROM bar;   -- <-- ScriptUtils will split here, which is wrong
      SELECT 1
        FROM dual;
    END; -- <-- statement should end here

This prevents users from having stored procedures in their init scripts, which feels like an unpleasant limitation.
The Spring developers behind ScriptUtils chose not to go down the path of parsing the SQL, and I can see why they would do this. For arbitrary scripts and many SQL dialects, this could be quite open ended.
However, I wonder if we can still improve on this just enough to be useful with a small change, so have created this WIP PR. I'm not intending for this to be the solution to all possible problems, but hope it unlocks us in some ways.
As-is, this:

won't split statements in between BEGIN/END tokens
can deal with nested blocks
seems to be OK with BEGIN/END appearing in string literals or comments

I don't believe this could create any regressions in its current form, and I believe BEGIN/END support is all we need to improve things greatly.

I don't think this fixes the problem, see my comment here:
https://github.com/testcontainers/testcontainers-java/issues/608#issuecomment-373326735

@bsideup @kiview I'd like to resurrect this PR, as it is a quick win to enable better SQL init scripts for JDBC containers. Issues such as #946 and #570 will continue to catch people out, which is silly when we have a solution that works well enough for typical usage.
Please could you review?
For reference init_mysql.sql shows the kinds of syntax that this PR enables, and is included in this PR for testing.

Released in 1.10.4!

Released in 1.10.4!

Thanks @rnorth, we ran into this issue with postgres a few weeks back.

Hi guys, I'm having some issues when using IF statement, it seems that it is assuming the word END in the "END IF" as the END of the BEGIN statement.
CREATE OR REPLACE PROCEDURE updatealladvertisers() LANGUAGE plpgsql AS $$ BEGIN     IF (SELECT count(1) FROM information_schema.tables WHERE table_schema = 'public' AND table_name='all_advertisers') = 0 THEN         CREATE TABLE IF NOT EXISTS public.all_advertisers         (             partnerid   BIGINT,             partnername VARCHAR(255),             partner     VARCHAR(255),             gsm_id      BIGINT         );     END IF; END $$;


Auth pages

Styled up login/register pages

"Sign out" link on current user indicator now works without redirecting user
Minor ui tweaks (removed outline, since input fields have border color for focus state)

before:

after:

Thanks a lot, this looks great to me!


Ensure all <a class='button'> are <button class="button"> so disabled click is actually preveneted

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1602
Originally created by @derek-knox on 2020-01-24 13:40:36

We most commonly use two different elements with class button for buttons. Those that are not using <button> but have a disabled attr still allow a click.
Resolve this (likely by converting to <button>, but there may be another good solution)

View 2 previous comments from the original issue on GitLab


Correct the type of the configuration.

Fixes:
PHP Fatal error:  Uncaught Symfony\Component\OptionsResolver\Exception\InvalidOptionsException:
 The option "comment_types" with value "hash" is expected to be of type "array", but is of type "string".
 in /path/to/project/vendor/symfony/options-resolver/OptionsResolver.php:1017

Thank you :+1:


Core,Controls(Gtk): implement tap/click gestures

Implement tap/click gestures for Gtk.
Note that due to the way Gtk works only certain widgets can respond to click events.
I changed ContentView to inherit from EventBox, so many elements have this capability, including all layouts. Still many widgets such as label for which adding tap gesture recognizer will have no effect.
See
https://discourse.gnome.org/t/gtk-widget-mouse-down-event-does-not-seem-to-work/1699.

@webwarrior-ws nit: please avoid 1-letter vars, e.g. o

Renamed 1-letter variables

Made PreventGestureBubbling private


https://sage-licorice-6da44d.netlify.app/doc/users-guide/getting-started/

Apologies for not putting this issue in the right place.
There is an issue in the section within the getting started page on using cilkscale
python3 /opt/opencilk/share/Cilkscale_vis/cilkscale.py
-c qsort -b qsort-bench --args 10000000
This command should be
python3 /opt/opencilk/share/Cilkscale_vis/cilkscale.py
-c ./qsort -b ./qsort-bench --args 10000000
or else you get an error
/bin/sh: 1: qsort: not found
(An alternate fix is to have "." in your path, but this is deprecated due to security issues.)

Thank you @dcurtisatmit. I will merge this with #59, which is about "Getting started."


green flame icon still in use

if I link to contribute.freecodecamp.org in the forum, the embed that appears has still the old green icon that was substituted with the one with the new color scheme:

Thanks for letting us know.
We have a dedicated issue for the older icons. It would be great if you could update https://github.com/freeCodeCamp/freeCodeCamp/issues/38540 with instances of the green logo.
I am closing this issue in favor of https://github.com/freeCodeCamp/freeCodeCamp/issues/38540
let me know if this issue has been closed by mistake.


go get version mismatch

What is the issue?
i try go get ... and such , just testing go cmds
esecially for newest versions
then well this appeared
go<EMAIL_ADDRESS>(matching ...@upgrade) requires<EMAIL_ADDRESS>not<EMAIL_ADDRESS>(matching ...@upgrade)
OS
Linux
GPU
Other
CPU
Other
Ollama version
from git today

seemfully it got fixed . thank you . ++ !


Add the automatic mount script

Boot automatic mount steps are tedious, we should use scripts to help users make the setup easier.

might not be an actual script (and relevant docs), instead I'll try to integrate --update-fstab functionality into mount.go


Update faircookbook_rdmkit_mapping.yml

New links between the RDMkit and the FAIRCookBook

It seems that the RDMkit task pages "Documentation and metadata" and "Data brokering" share 5 out of 7 FCB recipes. I wonder if that is ok or not. There should be other topics (maybe future recipes) that characterise "Data brokering", distinguishing it from "Documentation and metadata".

@tabbassidaloii You will regret that we met haha, now I dare to tag you 😉 Do you want to give your opinion on this for the FAIRCookbook side?

Not at all :)
I understand the logistics, but let's hear from other members.
The problem is that it is not possible to include the links only in one resource (each link would appear on both resources)
@daniwelter and @proccaserra what do you think?

The comments here reflect a few of the discussions we had at the BioHackathon Europe

only domain-specific recipes to domain pages
generic recipes only to task pages

We should formalize some of these rules to avoid future attempts at multiple linking. It was also raised that at some point, if many links are stablished, a revision on the way the links are presented should be done.

@elixir-europe/fair-cookbook-editors I think The problems got resolved (including merge conflicts). If one of you approve, I think this can be a Christmas holiday achievement!

Wohoow, lets goo!


Recover from parser errors

Currently we use Swift error handling for parser errors. While this is convenient, it has a number of drawbacks:

Any AST parsed gets thrown away as soon as we encounter an error. This prevents clients from being able to get any useful information from invalid AST (rdar://93677069).

Multiple diagnostics cannot be issued, meaning that e.g a basic syntactic error could obscure a more useful semantic error.

It doesn't extend nicely to e.g warning diagnostics, meaning that we'd eventually end up with 2 ways of emitting diagnostics.

The thrown errors relied on recordLoc blocks to annotate them with source location info, which could lead to errors without location info if we forgot to add the appropriate recordLoc calls. Additionally, in some cases we want a more fine grained location info than the block would give us.

Therefore this PR removes the use of Swift error handling throughout the parser. The parser is now a total function that always returns an AST. If errors are encountered while parsing, they are recorded, and are attached to the resulting AST by the parser. The parser attempts to recover as much of the AST it can when encountering an error. As such, there is now are now .invalid atom and character property kinds. Sema then runs and can attach more diagnostics onto the AST.
For now, the compiler interface remains the same, and we pick a single error to throw, but this will be changed in a later PR to allow multiple errors and warnings, as well as AST recovery. This also means we can better preserve the capture type in the presence of parser errors.
Fortunately, in most cases, this is quite a mechanical transformation. It entails:

Moving the lexical analysis methods onto the Parser. We were already passing ParsingContext parameters for most of them, so it's not clear they were benefitting from the isolation that Source offered. Effectively this means that all parsing has access to the context and diagnostics.

Converting error throwing statements into calls to the parser's error method (or unreachable method for unreachables).

This PR also updates the parser tests to be able to be able to match against multiple diagnostics.
Part of the fix for rdar://93677069
Resolves #449

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

We'll want to figure out if we want to land this in a feature branch in the short term or if we'll try to get this into 5.7

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test


Reland "Fix CheckExchangeMessages crashes when malicious packet is sent"

Problem
This is reland of https://github.com/project-chip/connectedhomeip/pull/6120 which was reverted because of regression in PASE.
The root cause of the regression is PASE is moved from transport layer to exchange, and packets exchanged during PASE do not have Source Node ID, so the following check in MatchExchange is no more valid.
// AND The message must come with a source Node ID.
&& (packetHeader.GetSourceNodeId().HasValue())

Summary of Changes
Fix CheckExchangeMessages crashes when malicious packet is sent

Fixes ##4635
Test
I don't have ESP32, so I used python device controller and lighting example to verify this change. I expect the PASE logic is same cross different platforms.
chip-device-ctrl > connect -ip <IP_ADDRESS> 20202021 12344321
Device is assigned with nodeid = 12344321
CHIP:BLE: Assigned local session key ID 0
CHIP:BLE: Sent PBKDF param request
CHIP:BLE: Received PBKDF param response
CHIP:BLE: Sent spake2p msg1
CHIP:BLE: Received spake2p msg2
CHIP:BLE: Peer assigned session key ID 0
CHIP:BLE: Sent spake2p msg3
CHIP:IN: New pairing for device 0x0000000000bc5c01, key 0!!
CHIP:CTL: Remote device completed SPAKE2+ handshake
CHIP:CTL: AsyncSetKeyValue: PairedDevicebc5c01=EAABEbyplB3xp6cuEWz2SFVrAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAFcvAAAAAAAMTkyLjE2OC44Ni4xNTcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFkrAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAA
CHIP:CTL: AsyncSetKeyValue: ListPairedDevices0=AVy8AAAAAAA=
CHIP:CTL: AsyncSetKeyValue: StartKeyID=1
Secure Session to Device Established
Device temporary node id (this does not match spec): 12344321
chip-device-ctrl >

@woody-apple ?


Make buildinfo not depend on scalajslib and scalanativelib

This uses structural types and catching NoSuchMethodException to check if a module is a ScalaJSModule or a ScalaNativeModule.
This way, users of buildinfo don't have to depend no scalajslib and scalanativelib mitigating the transitive dependencies problem.

Yeah, I think trying to solve this using structural types isn't worth the complexity. A bit of awkwardness around transitive plugin dependencies is ok for now, especially since it's the status quo. We can take our time to resolve it properly later, via coursier exclude configuration or something else


Flyout: use the new integration point

Use the documented integration point for our theme.
Read the official documentation at https://docs.readthedocs.io/en/stable/flyout-menu.html
I'm thinking about simplifying how all these integrations work and use only the ones that are documented. The idea is to inject the documented HTML tag that will be replaced by our integration at serve time.
Besides, I'm populating the template context with all the READTHEDOCS environment variables, so we can stop passing them from the Read the Docs application at build time by injecting them into the conf.py file.
Related: https://github.com/readthedocs/readthedocs.org/pull/10127

Besides, I'm populating the template context with all the READTHEDOCS environment variables, so we can stop passing them from the Read the Docs application at build time by injecting them into the conf.py file.

Most of these "context" variables should be converted into environment variables that all the doctool/theme authors can benefit from to integrate properly with their doctool/theme. Note this is something risen at https://github.com/readthedocs/readthedocs.org/issues/9423 as well.

I'm closing this PR because this integrates "the old flyout" and we are moving forward with the "new flyout out" now, see https://github.com/readthedocs/sphinx_rtd_theme/issues/1523


Close window ?

Is there any way to programmatically close the window ?
I'm evaluating the possibility to write a daemon that pops a window asking a question, then when the question is answered, the window must disappear without the user clicking the close button.

There is currently no way to do this.
It should be easily implementable (maybe as part of Mode?), but we need to keep in mind that Application::run will never return. Therefore, closing the main window will exit the whole process.
Opening and closing windows from the same process is something that we should explore when tackling #27.

While not being the best solution, i think it might be possible to currently do this by taking control of the event loop yourself. The integration example might be a good starting point, you would just need to remove the scene code from the example. You would then just call Window::set_visible to show and hide your dialog.

While not being the best solution, i think it might be possible to currently do this by taking control of the event loop yourself. The integration example might be a good starting point, you would just need to remove the scene code from the example. You would then just call Window::set_visible to show and hide your dialog.

Thank you. Yes, this seems to be a good way to do it by now. Or to *set control_flow to ControlFlow::Exit, to end the application on certain user interactions.

There is currently no way to do this.
It should be easily implementable (maybe as part of Mode?), but we need to keep in mind that Application::run will never return. Therefore, closing the main window will exit the whole process.

Do you mean that Mode should have a variant like Unmapped or Invisible ? And we can just set this mode from the running code?

Opening and closing windows from the same process is something that we should explore when tackling #27.

This issue is somewhat related to #170. Maybe we should tackle both of them together.

Do you mean that Mode should have a variant like Unmapped or Invisible ?

Yes, I think an Invisible variant could work nicely.

And we can just set this mode from the running code?

The mode can be currently set in Application::mode.

Currently this works, for killing the entire process. But looks your asking for something to close a spawned window, idk if those are spawned as their own process.
std::process::exit()

Currently this works, for killing the entire process. But looks your asking for something to close a spawned window, idk if those are spawned as their own process.
std::process::exit()


Fresh clone does not -O2-build under Windows

Could you please verify or refute?
Error is
[translation:ERROR] FlowingError:
[translation:ERROR]
[translation:ERROR] getattr(<module 'os' from 'C:\\Users\\j4yk\\Documents\\d
ev\\HPI\\rsqueakvm\\.build\\pypy-win32\\lib-python\\2.7\\os.pyc'>, uname) always
 raises <type 'exceptions.AttributeError'>: 'module' object has no attribute 'un
ame'
[translation:ERROR]
[translation:ERROR] In <FunctionGraph of (platform:1166)uname at 0x57069d0>:
[translation:ERROR] Happened at file C:\Users\j4yk\Documents\dev\HPI\rsqueak
vm\.build\pypy-win32\lib-python\2.7\platform.py line 1188
[translation:ERROR]
[translation:ERROR]             system,node,release,version,machine = os.uname()

[translation:ERROR]
[translation:ERROR] Processing block:
[translation:ERROR]  block@3 is a <class 'rpython.flowspace.flowcontext.SpamBloc
k'>
[translation:ERROR]  in (platform:1303)system
[translation:ERROR]  containing the following operations:
[translation:ERROR]        v33 = simple_call((function uname))
[translation:ERROR]        v34 = getitem(v33, (0))
[translation:ERROR]  --end--

This was done in a Git Bash session but it does not work with cmd either:
https://gist.github.com/j4yk/1f38525e08a31189678e
Works in the vagrant Linux box (although the Vagrantfile seems to need an update).
However, when compiling with JIT, i. e. leaving out the -O2 flag for the build script, it works. But I want to avoid that for frequent smoke-check builds because it takes so long.

Hm, this seems strange. Maybe this should be replaced with
system,node,release,version,machine =
platform.system(),platform.node(),platform.release(),platform.version(),platform.machine()

On 15 September 2015 at 17:21, j4yk<EMAIL_ADDRESS>wrote:

Could you please verify or refute?
Error is
[translation:ERROR] FlowingError:
[translation:ERROR]
[translation:ERROR] getattr(<module 'os' from 'C:\Users\j4yk\Documents\d
ev\HPI\rsqueakvm\.build\pypy-win32\lib-python\2.7\os.pyc'>, uname) always
raises <type 'exceptions.AttributeError'>: 'module' object has no attribute 'un
ame'
[translation:ERROR]
[translation:ERROR] In <FunctionGraph of (platform:1166)uname at 0x57069d0>:
[translation:ERROR] Happened at file C:\Users\j4yk\Documents\dev\HPI\rsqueak
vm.build\pypy-win32\lib-python\2.7\platform.py line 1188
[translation:ERROR]
[translation:ERROR]             system,node,release,version,machine = os.uname()
[translation:ERROR]
[translation:ERROR] Processing block:
[translation:ERROR]  block@3 is a <class 'rpython.flowspace.flowcontext.SpamBloc
k'>
[translation:ERROR]  in (platform:1303)system
[translation:ERROR]  containing the following operations:
[translation:ERROR]        v33 = simple_call((function uname))
[translation:ERROR]        v34 = getitem(v33, (0))
[translation:ERROR]  --end--
This was done in a Git Bash session but it does not work with cmd either:
https://gist.github.com/j4yk/1f38525e08a31189678e
Works in the vagrant Linux box (although the Vagrantfile seems to need an
update).
However, when compiling with JIT, i. e. leaving out the -O2 flag for the
build script, it works. But I want to avoid that for frequent smoke-check
builds because it takes so long.
—
Reply to this email directly or view it on GitHub
https://github.com/HPI-SWA-Lab/RSqueak/issues/108.

That code is in the Python standard library. But unfortunately the error message does not seem to tell me, what called there.

Oops. That's strange. And shouldn't happen

It works without the platform lines introduced in 158c6c402394920c7151aa15e89c243f141d6af1.

We could calculate that stuff at translation time, right?
On 12.10.2015, at 18:26, Jakob Reschke<EMAIL_ADDRESS>wrote:

It works without the platform lines introduced in 158c6c4.
�
Reply to this email directly or view it on GitHub.

--
Tobias Pape
Research School on Service-Oriented Systems Engineering
Software Architecture Group | http://www.hpi.uni-potsdam.de/swa/
Hasso-Plattner-Institut f�r Softwaresystemtechnik GmbH | Universit�t Potsdam
Prof.-Dr.-Helmert-Str. 2-3, D-14482 Potsdam, Germany
Amtsgericht Potsdam, HRB 12184 | Gesch�ftsf�hrung: Prof. Dr. Christoph Meinel

platform.system() probably so, but I think platform.version() or platform.processor() not.

Looking at the pypy/lib-python implementation of platform, it seems to be expected, that os.uname sometimes does not work, however, they do not resort to the host platform but implement their own:
https://bitbucket.org/pypy/pypy/src/c9976e50bbb80cab189ff525b2c6d2643d48ee50/lib-python/2.7/platform.py?at=default&fileviewer=file-view-default#platform.py-1166

That is user-level Python code, right? Maybe copying the uname implementation and changing the try-catch to something that causes the translation to skip uname if it is not available might work... but I do not particularly like that path.

Fixed this!


Add support to tag existing node as g/w node

Add support to tag an existing node as g/w node
Open the required ports to enable g/w traffic
Removes the security groups and removes the tag in cleanup.

Fixes : submariner-io/cloud-prepare#289
Signed-off-by: Aswin Suryanarayanan<EMAIL_ADDRESS>

@sridhargaddam Can you review?


[feature request] Add docker images to public ECR

To the Ops team of the project
Firstly this is not a bug report but request.
I would like to propose that we should also mirror container images in AWS ECR. Why?

Public ECR does have more lenient the rate limit policy than that of free tier DockerHub membership -> higher availability
Fast image fetch for AWS users (ECS, EKS, Docker on EC2 for example)
Better security for users with strict firewall policy that block non-AWS traffic
Encourage calico adoption in AWS ecosystem

I am more than happy to be the guinea pig should the team decides to give it a go.
Thanks much for your consideration

We can consider this if it gets enough interest.
In general, we expect that most production users will want to host their own images in their own registry anyway. We should definitely move off of DockerHub as our default as the rate limit is very annoying, but quay is likely our go-to there since we're already publishing images there.


squelch c compiler warnings

remove unused variables (-Wunused-variable)
make isLeap static (-Wmissing-prototypes)
replace strncpy with memcpy (-Wstringop-truncation)

Thank you for your efforts to improve the compiler warnings but I unfortunately will not be merging pull requests.  I've added the below text to the README to clarify the issue.
Feel free to fork the project and change the license.  You can also see if the original C code from the original authors is a better fit for you.
https://www.agi.com/cssi
https://www.centerforspace.com
The new README says:
Sorry, but the license for this project is the "Unlicense" and it does not provide any protection for contributors. You deserve credit and protection for the work you do, but this license won't provide that. I chose this license because I do not own the original code. The original authors who published it did so by fixing several problems in a US Government standard. They also provided amazing test cases to demonstrate their fixes. My unique contributions are porting the code to multiple languages including support for running their test cases. If you want to make changes, feel free to fork the project and put your own license on it. However, this project is not setup for collaboration.


[JTC] Non-0 velocity commanded after closed-loop execution

Describe the bug
PR #565 sets traj_point_active_ptr_ to nullptr after trajectory execution to avoid a race condition.
This changes the behavior of closed-loop execution from (a) continuously commanding the last trajectory waypoint, to (b) leaving the last interface command in place after the goal tolerance has been reached.
This leads to behavior where, if the goal tolerance has been reached with a non-0 velocity (likely in a closed-loop velocity-only command setting), we continue to command that velocity after reporting a successful execution.
If we with to maintain (b), we should explicitly command the final desired velocity when traj_point_active_ptr_ becomes null, I'll submit a PR to this effect.
To Reproduce
Steps to reproduce the behavior:

Command a trajectory to any robot with only a velocity interface and closed-loop control and non-0 goal tolerance
Execute the trajectory
Observe non-0 velocity after the Execution has been reported a success.

Expected behavior
Comment out L339.
Repeat previous steps. Observe 0 velocity after execution has been reported a success.
Screenshots
N/A
But I can provide video of our physical robot (a modified Kinova JACO2) if necessary.
Environment (please complete the following information):

OS: Ubuntu 22.04 Jammy
ROS Version Humble
With current package ros-humble-joint-trajectory-controller v2.20.0-1jammy.20230522.072811

I can confirm that this is also an issue for effort command interfaces. The expected behavior was replicated on a Franka Panda by commenting out L339 as proposed by @egordon.

That's a good point, (b) is almost certainly not the desired behavior for closed loop effort control.
So unless we have more info about how to prevent the race condition, we may just need to revert to 2.17.3 for the time being.

Isn't the real source of the problem that set_hold_position does not really set the commands to zero? see #558 et al.
After the call of set_hold_position, in the next run of the update() method we have again a non-null traj_point_active_ptr_ and the control loop is active again.
After the PR you proposed, the action tests fail with a segmentation fault -> see #688, but I haven't found the explanation for that yet.

@christophfroehlich you are right. Should we revert this merge? @bmagyar and I were probably too optimistic when agreeing to merge this.

See https://github.com/ros-controls/ros2_controllers/issues/688#issuecomment-1613128488
I'm not sure about the change introduced with #682 makes sense for itself, but tending to revert and bring #558

@egordon @tingelst Isn't this issue a duplicate of #514? At least the same behavior causing both issues IMHO.

@christophfroehlich Apologies, I was out the past couple of weeks.
I believe the PR that fixes #514 can fix this as well, but this issue specifically highlights successful execution (where set_hold_position() isn't called), while #514 covers unsuccessful execution (where set_hold_position() is called but doesn't do anything).
#565 exposes successful executions to 514's issue by removing the previous behavior where the final trajectory waypoint was continuously commanded.
So a PR that both fixes set_hold_position and makes it so that the previous behavior is effectively restored (i.e. final waypoint is commanded continuously, perhaps by calling set_hold_position on successful trajectory execution) should address this as well.
We'll continue to use our fork until said fix is back-ported to humble, and happy to help in any way to expedite that.

fyi: #558 got merged, but first will be released to rolling/iron before an eventual backport to humble.
If by chance you have a test environment with rolling, we're happy for feedback if this solves your issue.

While we're not on rolling, I did base our internal force gate controller off of the Rolling JTC, and it appears to solve the issue.
Thanks! I think this can either be closed now or after a humble backport.

It'll be backport only after some feedback on the changes from the rolling branch..


Issues with bash-script counterpart in ammonite shell

Hi Ammonite team
I'm running into errors regarding the usage of ammonite repl in a non-interactive i.e. purely in a script oriented way.
For example, here's a minimal test script I
#!/usr/bin/env amm

import ammonite.ops._

println(wd)

mkdir! pwd/"analysis"

cp.into(wd/"test.sc", wd/"analysis")

cd! pwd/"analysis"

ls!

This script works perfectly fine when used from the ammonite repl, however when I tried running it using
> chmod +x test.sc
> ./test.sc

It raises the following errors
test.sc:7: not found: value wd
val res_1 = println(wd)
                    ^
test.sc:11: not found: value wd
val res_3 = cp.into(wd/"test.sc", wd/"analysis")
                    ^
test.sc:11: not found: value wd
val res_3 = cp.into(wd/"test.sc", wd/"analysis")
                                  ^
test.sc:13: not found: value cd
val res_4 = cd! pwd/"analysis"
            ^
test.sc:15: could not find implicit value for parameter arg: ammonite.ops.Path
val res_5 = ls!
              ^
Compilation Failed

I also tried using amm --no-default-predef test.sc  in case there's something wrong in my predef.sc
Here's the content of my predef.sc
interp.load.ivy(
  "com.lihaoyi" %
  s"ammonite-shell_${scala.util.Properties.versionNumberString}" %
  ammonite.Constants.version
)
@
val shellSession = ammonite.shell.ShellSession()
import shellSession._
import ammonite.ops._
import ammonite.shell._
ammonite.shell.Configure(interp, repl, wd)

But the issue remains the same. I'm using this wonderful shell in a Genomic analysis pipeline - could you please guide me here :)

@abhi18av check: https://github.com/lihaoyi/Ammonite/issues/447#issuecomment-242858449
Ammonite in scripts doesn't expose wd.
In addition if you check docs there is note:
pwd: The current working directory of the process. This can't be changed in Java, so if you need another path to work with the convention is to define a wd variable.

In ammonite scripts you don't navigate through path the same was as in bash. So there are 2 ways to go about it. One is to use pwd everywhere if you just do stuff in sub directories:
#!/usr/bin/env amm

import ammonite.ops._
mkdir! pwd/"analysis"
cp.into(pwd/"test.sc", pwd/"analysis")
ls! pwd/"analysis"

Or you can declare wd by yourself:
#!/usr/bin/env amm
import ammonite.ops._

val wd = pwd
mkdir! pwd/"analysis"
cp.into(wd/"test.sc", wd/"analysis")
ls! pwd/"analysis"

Thanks @piotrkwiecinski and sorry for replying late.
You suggestion effectively solved the issues I was facing.


Toybox being enabled prevents ability resource usage regardless of settings.

On ability activation no rounds are consumed from Bard or Azata songs. This is also true of subsequent rounds. This was observed with no flags enabled, and when I disabled Toybox and Restarted the game did not occur. Enabling Toy box immediately breaks the expected behavior. This was tested with 1.1.2

Fixed in 1.1.3


How I keep null type but not null string

json:"country_code" example:"null" extensions:"x-nullable"
it will be null string, but I need null type

This sounds funny, I don't think you should add the example definition for empty values ("null")


Flop Counting Example Notebook

This PR creates a notebook walking through how to use the flop counter introduced in #5, both for simple use cases and in cases where one needs to add custom operator support.

Oh one more thing: could you modify the README to link to this notebook in addition to the hyperprior and DVC examples? You can ping me if you want me to look it over.


WEBP is preferred over JPEG  by top e-commerce giant due to its superior compression at equivalent quality - When can we expect it in bagisto?

Dear Team,
WebP is a modern image format that provides smaller, richer images that make the web faster.
WebP images are 26-34% smaller in size compared to PNG & JPEG.
When can we expect it in Bagisto?

Hi @parasbhadauria,
We already enable the webp extension. It's up to the admin.


gen_random helper: move ptr argument to front

This matches, for example, the getrandom syscall.

@bors r+

:pushpin: Commit 0096a0df2a34b5818976ff40b6ec5b1a54ebf92f has been approved by RalfJung

:hourglass: Testing commit 0096a0df2a34b5818976ff40b6ec5b1a54ebf92f with merge d82b24422d3778f595731981065873e015bb297b...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing d82b24422d3778f595731981065873e015bb297b to master...


Deliver EPUB versions of plays in Download tab

We could do that using the official TEI stylesheets.

Maybe use TEI Garage to generate: https://teigarage.tei-c.org/#
API Documentation of the RestAPI:
https://raw.githubusercontent.com/TEIC/TEIGarage/refs/heads/main/src/main/webapp/openapi.json


:align: center does not work for images

Describe the bug
When using :align: center with images (SVG) from a jupyter-book document (myst source file), the image remains aligned to the left.
I am able to overcome this by adding the following to my custom.css:
img.align-center {
   margin-left: auto;
   margin-right: auto;
   text-align:center;
   display:block;
}

I don't fully understand why this solution works, so I'm reluctant to submit it as a PR.
Environment
jupyter-book                   0.7.3
Sphinx                         2.4.4
sphinx-book-theme              0.0.33
sphinx-bootstrap-theme         0.7.1
sphinx-copybutton              0.2.11
sphinx-rtd-theme               0.4.3
sphinx-thebe                   0.0.7
sphinx-togglebutton            0.2.0

hmmm I wonder if this is an SVG vs PNG thing. Do PNGs work for you?

@choldgraf I now have a minimal working example, and it shows the problem for png files:

Create a template jupyter-book project with jupyter-book create template
Add the following lines to markdown.md

```{image} logo.png
:align: center
```

Resulting output below shows that image is not centered

Possibly also related, I am having similar problems with alignment of figures too. I'll report here when I get the time to create a clear minimum example.

Hmmm - it seems like align works for figures but may not apply to {image} directives. @najuzilu did you run into this at all?

According to the Sphinx documentation align should also work for image directives. It looks like the option is set through css under their basic theme here. I think one way forward would be to include these options under sphinx-book-theme.scss (similarly to how the align option for figure is handled).
However, I wonder if it makes sense to add the align option for figure and image directives under a JB basic theme. The align options are a no-brainer and it doesn't make sense to incorporate them in every theme. What do you think @choldgraf?

oops, just realized I didn't get back on this - I think for now we should just add the right CSS classes to the sphinx-book-theme to make sure that this works, and we can think about how to generalize for other themes later. Does that make sense?

This seems to be related: https://github.com/executablebooks/jupyter-book/issues/1204

Hi @choldgraf! I've added the CSS for now https://github.com/executablebooks/sphinx-book-theme/pull/292.
If you'd prefer a default unstyled img and explicit use of align-center please let me know!

Hey guys, this new CSS change makes my small images look really wonky when they appear between paragraphs, so I was wondering if we could change back to left aligning by default? That way, for those who want to center images, they can add a directive to do so?

Please remember that changing the CSS impacts lots of different users. Thanks.

@leneym - sorry for the confusion there, I believe that this was the intended behavior since that's how the figure directive was working. If you add align: left then they should snap back to the left
(closing since this one is fixed up)


Disable plugin for project

Hi,
Is it possible to disable the plugin for given project ? I would like to enable the plugin only for particular projects, not for all projects in android studio.
For example, I created a flutter package and I don't want the class S to be generated ..
Thanks a lot !

This is a good suggestion indeed, thanks.
Do you want to submit a pr for this, @benoitverstraete?

Thanks @noordawod !
I didn't work on a solution so I can't submit a new PR.

This will be fixed once #98 is merged.

This is now resolved in v1.1.0. Please upgrade through the Plugins page in your IDE and read the new README.


Trivial update: add missing closing quote on --resource-group

@lsundaralingam -
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


embark spec fails on demo project

with embark 0.4.3 and the embark demo project:
$ embark spec
Started
FF

Failures:
1) SimpleStorage should set constructor value
  Message:
    Expected '' to equal '150'.
  Stack:
    Error: Expected '' to equal '150'.
        at Object.<anonymous> (/Users/mids/Projects/embark_demo/spec/contracts/simple_storage_spec.js:9:40)

2) SimpleStorage set storage value
  Message:
    Expected '' to equal '100'.
  Stack:
    Error: Expected '' to equal '100'.
        at Object.<anonymous> (/Users/mids/Projects/embark_demo/spec/contracts/simple_storage_spec.js:14:33)

2 specs, 2 failures
Finished in 0.016 seconds

pyethereum and EtherTDD.py are installed in the active virtualenv:
$ pip freeze
bitcoin==1.1.29
ethereum==0.9.66
pyethash==23.1
pysha3==0.3
PyYAML==3.11
repoze.lru==0.6
rlp==0.3.8
structlog==15.2.0

This might be due to the latest geth (0.9.36) to which compatibility is being worked on

@jorisbontje should be fixed in 0.5.0. works for me. could you confirm plz?

Same with 0.5.0

result with that logging added https://gist.github.com/jorisbontje/bad27c26f4ae6fc0dc3c
looks like EtherTDD.py requires serpent, after installing Serpent I am getting a bit more output: https://gist.github.com/jorisbontje/765bf7c75b03d1895607
tests still fail though.

Fixed with serpent (silly user mistake in previous comment):
$ embark spec
address is : 0x616a4800acb771ec573faa577a32be074b8dbe59
compiling app/contracts/simple_storage.sol
Started
..

2 specs, 0 failures
Finished in 0.301 seconds


demo not working on ios

I cloned this repo to run the demo. On the android simulator i see the picker. Unfortunately i do not see the picker on the ios simulator(iOS 10.2).
suggestion:
Make a gif showing how the picker works.

Hi @elvismercado,
I stated on the READ.ME this hasn't been tested on ios, but it should work fine.
I'll give this a try as soon as i get a mac. Sorry about this.
You could give this a shot if you're familiar with  NS. The implementation is similar to that of android.
Could you debug this ?

@Robophil
I understand what you said in the readme. That is why i am now confirming that it is not working. I am not familiar with NS. But i will try to see if i can fix it myself. If i do i'll let you know.

Thanks @elvismercado ,
Feel free to ask me anything.


Unlock All Items error

When I got them all item hack when I used it after I set how much items I wanted. After a minute or so there was an error that popped up and said something went wrong please log back in. And it just keeps happening every time I try to use them.

then dont use alot


Adopt new configuration resolver service in tasks

Due to the multi root work now the configuration resolver service needs to take in the workspace root uri when resolving variables.
This is needed for reolving variables like ${workspaceRoot}
The tasks frameworks needs to adpot this, I have left TODO in the following places:
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/tasks/node/processRunnerDetector.ts#L176
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/tasks/node/processRunnerDetector.ts#L219
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/tasks/electron-browser/terminalTaskSystem.ts#L636
https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/tasks/node/processTaskSystem.ts#L380

Will tackle this is September with the user tasks related multi root work.

Done.


Chromium Browser crashing on launch

I followed the instructions and managed to download Chromium, but everytime I open it I hangs for a bit then throws me back to EmulationStation.
Here's the runcommand.log:
Parameters:
Executing: xinit /opt/retropie/ports/chromium/chromium.sh
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
Build Operating System: Linux 5.10.17-v8+ aarch64 Raspbian
Current Operating System: Linux retropie 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l
Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 smsc95xx.macaddr=E4:5F:01:09:40:FB vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyAMA0,115200 console=tty1 root=PARTUUID=fb041c1c-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait loglevel=3 consoleblank=0 plymouth.enable=0
Build Date: 19 April 2021  03:23:36PM
xorg-server 2:1.20.4-1+rpt3+deb10u3 (https://www.debian.org/support)
Current version of pixman: 0.36.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/pi/.local/share/xorg/Xorg.0.log", Time: Sun Jul 18 14:45:11 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/home/pi/.local/share/xorg/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Nevermind. I found this from last year and it solved it. Closing issue and posting with revised instructions

Just bumped into this issue
After running
$ sudo apt-get install xserver-xorg-legacy
$ sudo dpkg-reconfigure xserver-xorg-legacy

select "anybody"

Solves the issue for me
Originally posted by @yulrizka in https://github.com/zerojay/RetroPie-Extra/issues/196#issuecomment-727616350


Will allow us to use extends in our tslint.json

This will allow us to use
"extends": "tslint-microsoft-contrib"

in our project's tslint.json.

Hi @gaurav21r, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

This is a very small change and https://github.com/rcorp/standard-project-structure/issues/15 is blocked because of it. Request for feedback / merge quickly ? :)

Ah, I always wondered how this worked. I can merge this in the next few hours.
Do you need a release? Or can you configure your npm dependency like this:
"tslint-microsoft-contrib": "git@github.com:Microsoft/tslint-microsoft-contrib.git@releases"

We are making a release over the next day or two regardless.

If you ever have ideas for new rules then please don't hesitate to file an issue here!

@HamletDRC Thanks a lot for your quick response. Well a release would be great (even minor version number) but we can do without one as well. Incase that doesn't fit with your release strategy, It'll be great, if by the time we go live with https://github.com/rcorp/standard-project-structure (Maybe October 2nd week) we can get a release!

@iclanton This pull request changes main to tslint.json instead of package.json. Your last commit changed it to package.json with the comment "Pointing main in package.json to a real path." #8ab3195
If we change this to tslint.json then will it break something on your side? tslint.json is a real file in our npm package, so I think you will be OK:

@HamletDRC Thanks for the merge :smiley: ! I didn't understand

This pull request changes main to tslint.json instead of package.json. Your last commit changed it to package.json with the comment "Pointing main in package.json to a real path." #8ab3195

I  changed package.json in this PR. Are you saying we need to change tslint.json? But in the final commit you seemed to have changed package.json only? I'd love to learn the use case here for future ref.

@gaurav21r I think it was done correctly... but let me clarify my comment:

We changed package.json
within that file we previously had "main": "package.json"
now that file has: "main": "tslint.json"

I think it is all correct. I merged your PR as-is.

@HamletDRC Oh ok now I got it! Thanks for the quick release! Much appreciated :smile:
Btw, it seems the latest release hasn't been updated on npm. Requesting you to please see that as well? Thanks!

@gaurav21r the npm package is there now. Our npm admin is in California so sometimes we have to wait a few hours :)


Commonjs resolver plugin error since Waku 0.20.1

When building my project with Waku 0.20.1 I get the following error, which I didn't get in Waku 0.20.0. This specifically occurs because of this single line change. When reverting this line to the original implementation, everything builds fine again.
// vite-plugin-rsc-analyze.js
syntax: ext === '.ts' || ext === '.tsx' ? 'typescript' : 'ecmascript',

I am not entirely sure why this change was necessary, but I assume there's some good reasoning behind it. Do you have some information on this? I'd love to help figure out a solution.
Build failed in 1.42s
/Users/daan/Documents/GIT/project/node_modules/@swc/core/index.js:141
            return JSON.parse(bindings.parseSync(src, toBuffer(options), filename));
                                       ^

Error: [commonjs--resolver]
  × Expected a semicolon
    ╭─[4:1]
  4 │   return new Promise(async(resolve, reject) => {
  5 │     await sql.begin(async sql => {
  6 │       let finish
  7 │       !oid && ([{ oid }] = await sql`select lo_creat(-1) as oid`)
    ·        ───
  8 │       const [{ fd }] = await sql`select lo_open(${ oid }, ${ mode }) as fd`
  9 │
 10 │       const lo = {
    ╰────

Caused by:
    Syntax Error
file: /Users/daan/Documents/GIT/project/node_modules/postgres/src/large.js
    at Compiler.parseSync (/Users/daan/Documents/GIT/project/node_modules/@swc/core/index.js:141:40)
    at Module.parseSync (/Users/daan/Documents/GIT/project/node_modules/@swc/core/index.js:327:21)
    at Object.transform (file:///Users/daan/Documents/GIT/project/node_modules/waku/dist/lib/plugins/vite-plugin-rsc-analyze.js:24:33)
    at Object.handler (file:///Users/daan/Documents/GIT/project/node_modules/waku/node_modules/vite/dist/node/chunks/dep-whKeNLxG.js:67689:19)
    at file:///Users/daan/Documents/GIT/project/node_modules/rollup/dist/es/shared/node-entry.js:19611:40 {
  code: 'PLUGIN_ERROR',
  pluginCode: 'GenericFailure',
  plugin: 'commonjs--resolver',
  hook: 'resolveId',
  id: '/Users/daan/Documents/GIT/project/node_modules/postgres/src/large.js',
  watchFiles: [
...

Thanks for reporting!
Oh, this is interesting and unexpected. I thought typescript parser can parse any JS code.
I wonder exactly what code causes the parse error.

I would expect the same, but apparently not.
This is part of the postgres module, which I was trying out in combination with Drizzle ORM. This is the code for which the error occurs: https://github.com/porsager/postgres/blob/master/src/large.js
I don't see anything special though. Do you?
Would it be an option to revert back to the following, or do you have any arguments against it?
// vite-plugin-rsc-analyze.js
syntax: ext === '.ts' || ext === '.tsx' ? 'typescript' : 'ecmascript',

I'm fine to revert, but we need to understand the exact problem and the reason why typescript doesn't work.

we could experiment with swc cli.

Totally agree! I have done a quick test by compiling postgres/src/large.js with the swc cli. It works fine when using the ecmascript syntax, but the same error surfaces when using the typescript syntax.
I'm not really sure yet what the reason might be.
➜  waku-test npx swc ./node_modules/postgres/src/large.js

  × Expected a semicolon
    ╭─[node_modules/postgres/src/large.js:4:1]
  4 │   return new Promise(async(resolve, reject) => {
  5 │     await sql.begin(async sql => {
  6 │       let finish
  7 │       !oid && ([{ oid }] = await sql`select lo_creat(-1) as oid`)
    ·        ───
  8 │       const [{ fd }] = await sql`select lo_open(${ oid }, ${ mode }) as fd`
  9 │
 10 │       const lo = {
    ╰────

Caused by:
    Syntax Error
Error: Failed to compile 1 file with swc.
    at Object.assertCompilationResult (/Users/daan/Downloads/waku-test/node_modules/@swc/cli/lib/swc/util.js:164:15)
    at files (/Users/daan/Downloads/waku-test/node_modules/@swc/cli/lib/swc/file.js:205:19)
    at async _default (/Users/daan/Downloads/waku-test/node_modules/@swc/cli/lib/swc/file.js:224:9)

Thanks for trying! Can you try with tsc too? Then, we will know if it's swc issue or TS issue.

I extracted the large.js file and ran tsc as follows:
npx tsc ./large.js --allowJs --outDir ./dist

This seems to work fine, no errors reported. When I run npx swc ./large.js, again with the typescript syntax, the same error as earlier occurs.
So to me it seems like an issue with swc, although I don't fully understand why it happens.

I've also gone over the SWC docs on using swc instead of tsc, but haven't really found anything that makes a difference there.

Thanks for your investigation.
Let's assume that it's a bug in SWC.
I'll open a PR for the workaround.


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Current coverage is 37.41% (diff: 100%)

Merging #38 into master will not change coverage

@@             master        #38   diff @@
==========================================
  Files             1          1
  Lines           155        155
  Methods          31         31
  Messages          0          0
  Branches         25         25
==========================================
  Hits             58         58
  Misses           97         97
  Partials          0          0

Powered by Codecov. Last update a26f42e...ddb8061


chore: remove tmuxinator

At this point mprocs has fully replaced tmuxinator as our local dev environment of choice. The last remaining problem was that multi-line text selection wasn't working very well but AFAIK that's fixed now.
Closes https://github.com/fedimint/fedimint/issues/2426

The last remaining problem was that multi-line text selection wasn't working very well but AFAIK that's fixed now.

Are we already running the newest mprocs with that fix?

BTW. How do I copy&paste in mprocs now? :D

BTW. How do I copy&paste in mprocs now? :D

Selecting the text then "c" worked for me

I will re-work this PR to keep tmuxinator but recommend mprocs as the default in dev-running.md tutorial

Selecting the text then "c" worked for me

Oh, I get it. I have to use the mouse to select the text. A bit ew, but I guess it works.

Updated. Doesn't remove tmuxinator, but recommends mprocs in the docs. Also remove some old tmuxinator cruft like unused shell scripts and docs.


Multiple injections if instance is bound in child injector

Hi everyone,
I came across a pretty weird behaviour when I integrated dependency injection with Guice in our Java project.
We instantiate objects with Guice that derive from a common base class, let's call this base class Block. Later on we create other objects that depend on the formerly created block. To be able to create those objects, a child injector is used. The child injector features an additional module that binds Block.class to the instance that was created earlier. So, we do something like this:
public class Block {
	@Inject
	public void setBlockDependency(BlockDependency bp)
	{
		System.out.println("Block::setBlockDependency " + (System.identityHashCode(this)) + " - BlockDependency with HashCode " + System.identityHashCode(bp));
	}
}

public class BlockAccessModule extends AbstractModule {

    private Block block;

    public BlockAccessModule(Block block) {
        this.block = block;
    }

    @Override
    protected void configure() {
        bind(Block.class).toInstance(block);
    }
}

public static void main(String[] args) {
    Injector baseInjector = Guice.createInjector();
    Block block = baseInjector.getInstance(DerivedBlock.class); // class DerivedBlock extends Block

    baseInjector.createChildInjector(new BlockAccessModule(block));
}

The weird thing is, that when createChildInjector() is called, the set-Methods of the already instantiated Block gets called again. So, its dependencies are getting injected again, with different instances of these dependencies.
Running the piece of code would output something like this:
Block::setBlockDependency<PHONE_NUMBER> - BlockDependency with HashCode 836514715
Block::setBlockDependency<PHONE_NUMBER> - BlockDependency with HashCode 459857341

From my point of view, the second call to Block::setBlockDependency should not occur. Is there a way to prevent it? Currently, we put the block into a wrapper object and bind this in the BlockAccessModule. Objects that depend on the created block then have to obtain the block from the wrapper. But this seems like a pretty hacky workaound.
Attached you will find a runnable eclipse project that contains all classes used in this example.
GuiceDoubleInject.zip

See https://github.com/google/guice/wiki/Injections#automatic-injection:

Guice automatically injects all of the following:

instances passed to toInstance() in a bind statement

So your Block instance will be injected once when you retrieve it in main and again when you bind it using toInstance in BlockAccessModule.
To avoid this change the binding in BlockAccessModule to be:
import com.google.inject.util.Providers;
...
bind(Block.class).toProvider(Providers.of(block));

This works. Thanks a lot for the fast reply. :)


Removed Ch. 1 error message in Transacting Challenge

Fixes #574

Hello @harshita130602! Thank you so much for this PR. 🙏
I tested it and there is no longer the "almost" message so it's a tACK for me! Let's get a code review on this and then we can merge.


pdf viewer

check https://github.com/lazypanda10117/docsify-pdf-embed
if not try google pdf viewer

The docsify plugin didn't work with external links (needed local files).
Google pdf viewer worked https://github.com/crystaluniverse/publishingtools/pull/160


Alerts for VPN issues now silence other shoot alerts

If an alert is already present for VPN service, then silence all other alerts of type=shoot.
Fixes #170
/cc @plkokanov

Why would we silence all other alerts? And when looking into it, we didn't see VPN failing. You can't be serious to "just silence everything now"?


Switch to a date-based catalog versioning system, and related updates

Closes #191 .
This PR significantly alters the way the catalog generated by access-nri-intake-catalog is handled, stored, and versioned.
Catalog storage location
The live catalog will now be stored on gdata/xp65 (access_nri_intake.CATALOG_LOCATION), rather than being shipped with the package. This is because all of the catalog data lives on Gadi anyway, so there doesn't seem to be much point to being able to see the catalog definition YAML, but not be able to access any data.
However, to support power users and local developers, there is the option to place a catalog.yaml file at a defined location in the user's home directory (access_nri_intake.USER_CATALOG_LOCATION). This catalog will automatically take precedence over the 'live' catalog on Gadi, if it exists. I thought about adding utility functions that would allow users to create this directory, put a catalog.yaml in it, etc.; however, given that it's a power user move, I decided it's easier and safer to have the user do that themselves manually.
Versioning
Catalog versions will now be date-based, e.g., a catalog built today will be, by default, v2024-11-07. Attempts to set a version number that doesn't conform to this pattern will raise an exception.
catalog.yaml will now contain a min and max version. This is to cover the possibility that the catalog structure may change, and a particular version of catalog.yaml may not be compatible with certain catalog versions. I've confirmed that doing the usual < and > operations on our version strings has the expected output.
Under this versioning schema, there isn't really a need to have a symlinked latest version of the catalog (and also because we can update the live catalog on xp65 at will, without doing a code release).
Building the catalog
Because catalog.yaml will be placed on xp65 now, there is no need to make a new code release for every catalog build.
As mentioned above, a catalog built today will take today's date as the default version, although the user can override it.
The build process is now intelligent to the presence of older versions of catalog.yaml, and to directories that look like older catalogs:

If no catalog.yaml exists, one will be created. If the data directory contains folders that look like catalog versions (i.e. vYYYY-MM-DD), then the code will use those to construct the min and max version boundaries (i.e., it will assume that the new catalog.yaml is good for describing those existing sources).
If a catalog.yaml exists, and there is no structural change to the catalog, then the existing catalog.yaml will be updated with:

A new default (and probably max) version; and,
Updated storage metadata that is the union of the old and new storage metadata (i.e., we deliberately don't remove any storage metadata that is redundant with the new catalog version, as it will still be required for the older versions under this catalog.yaml).

If the new catalog is structurally different to the old catalog, then a new catalog.yaml will be created, with min version = max version = current/new version. The old catalog.yaml will be moved aside to catalog-<old min version>-<old max version>.yaml. These catalogs are nominally not accessible, unless the user hacks the access_nri_intake.CATALOG_LOCATION variable. For now, given how infrequently we'll be making the sort of changes that will trigger this scenario, I'm fine with that.

Documentation
To be updated once we're happy with the core structure of this update. The updates required will be:

Alter the catalog build process instructions;
Document the ability to have a local 'override' catalog.yaml.

Testing
All of the above should have at least one unit test.

OK. What's the best way for us to test this on GADI?

OK. What's the best way for us to test this on GADI?

The way I've done this in the past (e.g. to test #175 updates):

Check out the code onto Gadi, and do a local install of the package (non-destructive override of the environment version)
Copy the build_all.sh script, and modify it to point to a dummy directory, a subset of the data sources, etc.
Run the copied build process as per the documentation
Scream incoherently when it fails (optional), work out why it fails, run it again
Repeat 3-4

The main thing to check would be to copy the existing catalog folders (e.g. v0.1.3) to the dummt directory, create symlinks to them using the date catalog format, and make sure the build process picks those up as previous versions and sets the catalog min version correctly.

I have just tried with only one source in cmip6.yml same pb

Do you have an existing catalog.yaml in the build directory? If so, it's going to look for a min value in that, and it appears to be bombing out because it can't find one. The assumption I made is that the first catalog build in the 'live' directory on xp65 (and, therefore, the first build in your dummy area) will be the first catalog.yaml to appear there, so it will inspect the present directories to compute a min and max version instead.

I have tried with an empty folder and I still get the issue...

OK I'll take a look and see what's happening...

Found the problem - the code is building the catalog in one place, but it's looking for the existing catalog (and, it seems, building the catalog.yaml back out to) the live location referred to by the CATALOG_LOCATION variable. I need to have a quick think about how to rectify that.

@rbeucher OK, check out the latest code version and try again. You'll need to update your test version of the build_all.sh script to include the new --catalog_base_path option (see the canonical build_all.sh in the repo).
The issue was that, while changing the build_base_path option in the build script lets you stick the catalog data in a different place, the catalog yaml was always being forced into either live location on xp65, or into your home area if you have a local catalog.yaml set up. I've now added an extra option to the build() function call, as well as some additional supporting changes, that let you set where the catalog.yaml lives. In production, this will be the same place as the catalog data, hence why the canonical build_all.sh script sets --build_base_path and --catalog_base_path to be the same.

Running a build test right now - will comment if I have any issues

@rbeucher It looks like you might have overwritten a default catalog location or similar on Friday? I'm currently getting the following error - are you able to take a look & let me know if the file in the error message is one you recognise?
>>> import intake
>>> intake.cat.access_nri
/g/data/hh5/public/apps/miniconda3/envs/analysis3-24.07/lib/python3.10/importlib/__init__.py:126](https://are.nci.org.au/g/data/hh5/public/apps/miniconda3/envs/analysis3-24.07/lib/python3.10/importlib/__init__.py#line=125): RuntimeWarning: Unable to access a default catalog location. Calling intake.cat.access_nri will not work.
  return _bootstrap._gcd_import(name[level:], package, level)
access_nri:
  args: {}
  description: ''
  driver: intake.catalog.base.Catalog
  metadata: {}

>>> from access_nri_intake.utils import get_catalog_fp
>>> get_catalog_fp()
'/g/data/xp65/public/apps/access-nri-intake-catalog/catalog.yaml'
>>> intake.open_catalog('/g/data/xp65/public/apps/access-nri-intake-catalog/catalog.yaml').access_nri
---------------------------------------------------------------------------
FileNotFoundError                         Traceback (most recent call last)
Cell In[9], line 1
----> 1 intake.open_catalog('[/g/data/xp65/public/apps/access-nri-intake-catalog/catalog.yaml](https://are.nci.org.au/g/data/xp65/public/apps/access-nri-intake-catalog/catalog.yaml)').access_nri
...
FileNotFoundError: [Errno 2] No such file or directory: '[/g/data/tm70/rb5533/intake_tests/v0.1.4](https://are.nci.org.au/g/data/tm70/rb5533/intake_tests/v0.1.4)+13.g869f576.dirty[/metacatalog.csv](https://are.nci.org.au/metacatalog.csv)'

I've run a catalog build with just CMIP5 enabled which built without any issues - I'm just running into this slightly weird error trying to import it.

Yes. Sorry, my bad. It looks like I have mess up with the file

No worries. I'm looking into it more closely now - probably something we're going to want to have some guard rails against.

I've restored the file to default to v0.1.3 for now.

@charles-turner-1 I think you might have to hack the code to open your existing catalog (or, better yet, put it into ~/.access_nri_intake_catalog/) - the code only knows to look for a catalog to open at either CATALOG_LOCATION = "/g/data/xp65/public/apps/access-nri-intake-catalog/catalog.yaml" or USER_CATALOG_LOCATION = Path.home() / ".access_nri_intake_catalog/catalog.yaml".
We should probably look at adding a path option to intake.cat.access_nri to see if we can make that more flexible.

Sorry @marc-white, just saw your comment - the default catalog was pointing at a nonexistent file. My catalog in .access_nri_intake_catalog/catalog.yaml worked just fine.
I've approved but I think before merging we want to update docs?

Yes, a docs update is definitely required. I can get started on that today.

I've added the necessary documentation, take a peek...

Other than the two minor typos, documentation changes look correct to me.
I updated cli.py::build if update: ... clause on my local machine to make it a bit more readable to check the docs - are you happy for me to push the changes to the branch?

Yep push the changes

@marc-white Can you confirm the shorthand variable names I used in 5c80be3 aren't misleading? Other than that I think this is good to go.

@marc-white Can you confirm the shorthand variable names I used in 5c80be3 aren't misleading? Specifically driver_new, etc..

Looks reasonable to me!

I'm going to get onto Gadi now and create symlinks for the existing catalog versions, so they get picked up the first time we generate a 'new-style' catalog.


fix: return normal results for lock queries

When using forUpdate or forShareLock now sqlite and postgres will both use normal root queries. While for HANA it will first execute the lock SQL and then execute the query with the lock removed. As HANA does not allow locks when using sub queries.
Example:
SELECT ID FROM (SELECT * FROM Books) FOR UDPATE ID NO WAIT -- cannot identify Books as the lock target table

When using expands in lock queries only the lock on the root table is guaranteed.

Should we rename the PR title as it's a fix for an unreleased feature.


Wallpaper - with alpha, and the usual settings (center, stretch, tile etc.)

)(Was closed accidentally by a mistyped commit message.)_

OK, it's there now, part of the theme config: .bg in ThemeCfg can be sf::Color or Theme::WallpaperCfg (which is {string filename, Wallpaper::Placement placement}`


Give some information about RHEL ELS

RedHat provides some Extended life support add-on which provides updates for a subset of packages for some extra duration after EOL. Ref : https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates
Is there any chance to provide information about this (especially in api/json file) ? Not sure what would be the best between having an extra cycle like "RHEL 6 ELS", or just some extra fields in the default cycle ?

@BiNZGi @captn3m0

As I saw the ELS is an additional service which must be paid via subscription. We are having a similar discussion in the Java topic. But  in this case it is a bit different because only Red Hat provides this service.
The RHEL page is not that crowded and from my side it would be a good addition for the users of our page. If we agree to support the ELS details I would add an extra cycle as proposed.

Related to discussion #535

The only (minor) concern I have is that every RHEL release is currently supported with ELS, so it's not very meaningful (could be covered in the text as well for now - "All RHEL releases are currently supported with a paid ELS subscription").

Mhh, I don't understand it that way. As per https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates , only RHEL  6,7,8 are still covered by an active ELS support. RHEL 5 ELS ended in 202 and 4 in 2017 (but the Extended life phase ends column is a bit strange)

Yeah, was confused with that, looks like we shouldn't be tracking Extended Life Phase, since it doesn't cover any fixes, just technical support.
So +1 to adding ELS as a separate row for the supported releases.

For versions of products in the Extended Life Phase, Red Hat will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only.

Yeah, just an extra repeated row with ELS in the releaseCycle field.

Yeah, just an extra repeated row with ELS in the releaseCycle field.

Can you clarify? Would it be like this:
  - releaseCycle: "RHEL 8"
    release: 2019-05-01
    support: 2024-05-31
    eol: 2029-05-31
    ELS: 2029-12-31 # Example
    latest: "8.5"

Looking at further, I believe you meant having a completely different releaseCycle with ELS in the name? Personally believe that is not ideal. Just by looking at the Windows entry it can result in a mess to put it mildly.
Unfortunately I'm not familiar with HTML, Rudy or netlify to see how easy it would be to have an additional column for dates, but this would be highly useful especially for entries such as Ubuntu, RHEL, Windows, and potentially others that have more than just two support structures.

Looking at further, I believe you meant having a completely different releaseCycle with ELS in the name

Yes, that was the idea. As it stands, the code does a lot of templating logic, along with calculations to render the tables and it's not easy to easily add more columns. Let's go for the new release cycle row for now?
Can you provide a table that you think will work for our site? (With ELS as a column?). Will track it in a separate issue on how we can do more columns more easily (we only have discontinued right now, and it's not very easy to add more).

Should be covered now by the "Extended Life Cycle Support" on https://endoflife.date/rhel.
Will be available from the API once #2080 is completed and merged.

Closing this issue because it should be OK now. Do not hesitate to reopen if necessary.


NIFI-10802 Apply bundle updates before properties in component synchr…

…onizer

Summary
NIFI-00000
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[ ] Apache NiFi Jira issue created

Pull Request Tracking

[ ] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[ ] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[ ] Build completed using mvn clean install -P contrib-check

[ ] JDK 8
[ ] JDK 11
[ ] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Will reivew...


Advanced uses of relationship matchers?

Hi there.
Firstly: Thanks for a really nice gem!
I was wondering how I would go about testing that a particular relationship has a particular set of links or meta?
E.g. In my serializer, I have:
class User
  include JSONAPI::Serializer
  blog_posts_meta = lambda do |contest|
    {
      count: contest.candidates_count,
    }
  end
  blog_posts_links = {
    self: ->(u) { "/link/to/#{u.id}" },
  }
  has_many :blog_posts,
           meta: blog_posts_meta,
           links: blog_posts_links
end

Is there an in-built way that I can test that the association has the right links and the right meta block?
Thanks in advance.
Emil

Hi @ekampp!
That's currently not possible. Each association option needs a specific submatcher, currently we have only 2 (id_method_name and serializer).

Hi, @mateuscruz.
Thanks for the response!
After some deliberation with my colleagues, we have decided on validating the resulting JSON instead.
I will close this PR.


Gray Code Calculator

Enter calculator name -
Gray Code Calculator
Describe calculator functionality -
The Gray Code Calculator takes either input in binary format and converts it into the Gray Code or vice-versa.
Under which category you wish to place it -

[ ] Computer Science
[ ] Mathematics
[ ] Physics
[ ] Chemistry
[ ] Biology
[ ] Art
[ ] Finance
[ ] Scientific
[ ] Health
[ ] Sports
[x] Let project owner decide
[x] Microprocessors & Microcontrollers
[x] Digital Systems Design
[ ] Suggest a new category - (Answer here)

@SarthakKeshari kindly assign me this issue

kindly assign to me @SarthakKeshari @Vedansh-Keshari

@Satvik-Garg,
Abiding by the contribution policy, not more than 2 issues can be assigned at a time.
Kindly comment once the previous issues are merged.

Hey @PrachiDev11,
Assigned.
You may contribute your code under the folder path -
calc_for_everything\calculators\src\computer_science\grayCodeCalc
Issue completion deadline - 22nd Oct 8:00:00 am IST
NOTE - In case the issue completion deadline is not met, the issue will be assigned to a new participant


branch for last index fix

Here we just fixed line in index.html
changed to have correct links
also changed linter code to see if all is well

hi @shella12
please see the changes I made

Hi @bobb-Rob
please check it again

Hi @mckent05
Can you please check again and be more descriptive about whats missing?

H1 @kayjeee , I see that you have not compared the Microverse README template with your own. Please see the image below for the difference. I marked the missing section in red. You included the Tech stack but it is positioned in the wrong section.
Microverse Template

Your README

Hi @bobb-Rob
thank you for the response, I have made changes please check again
and review

Hi @bobb-Rob
thank you for the response, I have made changes please check again and review

@kayjeee, I claimed your pull request for review and you haven't updated your README file. Kindly check this portfolio readme file for inspiration.

Hi @topeogunleye please be more specific as you can see this thread is long and I have been making changes to this readme file
be clear about what is missing this time.

@kayjeee Please ensure that you push your code to GitHub after you make changes because I do not see any commit from you ever since your pull request has been invalidated many times. Also, ensure it is the correct branch.

Hi @topeogunleye please be more specific as you can see this thread is long and I have been making changes to this readme file be clear about what is missing this time.

@kayjeee, as stated by @bobb-Rob, it seems like you didn't push your changes to GitHub

Hi @topeogunleye and @bobb-Rob
I opened another pull request by mistake, please check if my changes are visible now.

Hi @topeogunleye and @bobb-Rob
I opened another pull request by mistake, please check if my changes are visible now.

@kayjeee, No, your changes are no visible. Kindly ensure that you're on the right branch which is addcssline when you are pushing

Hi Hi @topeogunleye
Thank you for being clear I can clearly see my mistakes, Apologies for my mistakes
I think now I was able to make changes,

@kayjeee, Great 👍 , Kindly add some future feature and optionally you can remove these instructions telling you what to add:
Describe between 1-3 key features of the application.

Hi @topeogunleye
okay i believe I did the changes you asked

Hi @topeogunleye
okay i believe I did the changes you asked

Hi @topeogunleye okay i believe I did the changes you asked

Okay then

hi @franclobo
please check again, I managed to fix the hamburger button

Hi @Olamarx
can you be specific on what I should do next?


[New game]: Flappy Bird Game

🎮 Game Request
Game logic and basic description
adding flappy bird game

Point down the features
Game points
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @dhairyagothi !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @dhairyagothi!
We are already having a similar game request in #4607 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.

/assign


Installation of @ngx-translate/core also installs “semantic-release” (since version 12.1.0)

Current behavior
The @ngx-translate/core package seems to depend on semantic-release since v12.1.0:

https://www.npmjs.com/package/@ngx-translate/core/v/12.1.0?activeTab=dependencies
https://www.npmjs.com/package/@ngx-translate/core/v/12.0.0?activeTab=dependencies

Expected behavior
No installation of semantic-release since it’s a devDependency.
Minimal reproduction of the problem with instructions
npm install @ngx-translate/core
less package-lock.json

Thanks, good catch! It'll be fixed in the next version (I won't release a new version just for that)

Shouldn't it be a dependency on the root package.json?

or install wirhout adding to package.json at all?
btw: latest semantic-release is v17.0.3 and you are using v8.2.3

As long as it works, I'm reluctant to change the setup since it does
releases automatically and it works fine 😁

@ocombe Is it released? I still have it installed with @ngx-translate/core 12.1.1 :

Same issue here. The latest version still installs<EMAIL_ADDRESS>and generates warnings in Angular 9 when the latter tries to compile all npm dependencies as esm2015. Please remove it from the dependencies, since it's not a requirement to run your app code.

Can you try 12.1.2 please? Hopefully it should be fixed for good now

Seems fixed, thanks!

Yep, it's fixed. Thank you @ocombe 🙏


Add shelljs (v0.7.0) declarations

This PR adds flow declarations for shelljs. It covers the complete API but in some cases I have restricted the interfaces for certain functions to the part that can be reasonably typed. However, this should not limit functionality.
I've added tests following some of the others as examples but I had some trouble getting the flow-typed CLI tool to run them.

I love how complete and extensively tested this libdef is! Awesome :D

Okay, I cleaned up some of the exports and moved most of the stuff that's probably not needed in other libdefs into the module declaration. Think it's good to go on my end.


[CHANGE ME] Re-generated apis/Google.Cloud.Debugger.V2 to pick up changes in the API or client library generator.

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/91e2c74b-447a-4195-b8ad-25a3508fd86e/targets

[ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)

Deleting - ordering only.


When youtube-dl requires authentication when download YouTube video

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

Seem like youtube-dl always does "login" in init phase with all videos if user specify "username" and "password" parameter.
    def _real_initialize(self):
        if self._downloader is None:
            return
        self._set_language()
        if not self._login():
            return

Usually it is not necessary with public youtube video and no age restriction.
My question is which YouTube video requires authentication? Could "youtube-dl" only login when in forced situation?
Login many times can move us into bad situation like: blocking or "security notice" requires sms verify.
I integrated youtube-dl to my system which makes ~ 100.000 requests per day, so login 100.000 times is impossible.
youtube-dl is awesome project, thanks your team!

Use --cookies instead of providing credentials.


No entities in the enties card after upgrading to 2024.12.0

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
v1.00
Last working release (if known):
Browser and Operating System:
Chrome and Edge, on Windows 11
Core 2024.12.0
Supervisor 2024.11.4
Operating system 14.0
Frontend 20241127.4

Description of problem:
After installing Core 2024.12.0, the entities cards are empty, (I can still see the entities in edit mode)

Javascript errors shown in the web inspector (if applicable):
Uncaught TypeError: Cannot read properties of undefined (reading 'styleSheet')
    at energy-entity-row.js?hacstag=640556013100:11:2978
    at Array.map (<anonymous>)
    at energy-entity-row.js?hacstag=640556013100:11:2939
    at kt.createRenderRoot (energy-entity-row.js?hacstag=640556013100:11:3142)
    at kt.createRenderRoot (energy-entity-row.js?hacstag=640556013100:23:151)
    at kt.connectedCallback (energy-entity-row.js?hacstag=640556013100:11:3253)
    at kt.connectedCallback (energy-entity-row.js?hacstag=640556013100:23:737)
    at kt.connectedCallback (energy-entity-row.js?hacstag=640556013100:39:4762)
    at t.connectedCallback (scoped-custom-element-registry.js:248:42)
    at $.k (lit-html.ts:1411:53)

Additional information:
After returning back to Core 2024.11.3, it worked again!

Here's what it looks like for me: none of the entities are shown anymore. I would love to get this back in operation, as this screen gave me great insights on energy used, produced and the costs and income over a selected period

Thanks a lot. To confirm it works again:


Fragment's menu not localized on rotation

Steps to reproduce:

Create fragment
Add menu to fragment
Rotate device

If you add something like this:
override fun onPrepareOptionsMenu(menu: Menu) {
        super.onPrepareOptionsMenu(menu)
         menu.clear()
         MenuInflater(activity?.applicationContext).let {
             it.inflate(R.menu.main_menu, menu)
             super.onPrepareOptionsMenu(menu)
         }
     }
it solves problem, but adds new one - app:showAsAction="always" is ignored
I've created fork to test this out and maybe add some fixes if have any, but no luck.
If you want sample, please check https://github.com/RumataEstorish/lingver/tree/fragment_menu_test

Unfortunately, I can't reproduce it across different android versions on emulator and my Pixel2 using your sample project.
Are you using some specific device?

Ok, lets add more steps to reproduce :)
Environment:

Emulator API 28 (Pixel 2 XL skin my case)
Languages: English primary, Russian secondary
Auto rotation is turned ON

Steps:

Open app. Language is English
Switch to Russian
Press "Screen 1"
Open 3 dots menu. Observe "второй пункт меню"
Without closing menu rotate emulator.

Expected result:

We still see "второй пункт меню"

Actual result:

We can see "second menu item"

Note:
Fragment stays in Russian as expected and we can see "произовольный текст 1"

Okay, just reproduced it. It's important to keep the menu open before rotating the device to replicate the issue.
Will dive deeper and see what I can do. Thank you for reporting!

Well, there are more cases when this can happen. Not only when menu is kept opened, but when you open/close navigation drawer and some other. But they require much more code for resting.

This is androidx.appcompat:appcompat bug. Downgrade from1.3.0-alpha01 to 1.2.0-rc01 fixed this problem.


Add globbing to inputs.path

resolves https://github.com/actions/upload-pages-artifact/issues/28

https://github.com/actions/upload-pages-artifact/pull/27#issuecomment-1279826816


[WIP] Adding OpenShift e2e test for existing vnet.

Adding a test for deploying an openshift cluster with an existing vnet.

looks good so far, I guess you need to get that vnet created and values substituted into the json file before acs-engine reads it?

@CecileRobertMichon, I believe this is ready to merge.  Please review.   Thanks!


Abide by flesh roots’ suggestion.

Now the developer only checklist is commented out and only shows to the pull creator

Also could I be added to the org? Apparently it’s impossible to request a review unless you are in the org.

Only team members are added to the org.

Not necessarily needing admin privileges however it is common practice to add contributors to the org even if they are not maintainers.

Could this get reviewed?

Also apparently when the github actions was merged it removed the initial commit for this template.

@nmcain reviee?

yes its good

Resolve git conflicts tho

Git trickery, commence!


Architecture zoo

Adding a library for model architectures initialized with a simple 1D resnet implementation. Implementation is largely lifted from torchvision's implementation, with a few changes for supporting 1D convolutions as well as arbitrary kernel sizes and depths given the difference of our problem from the usual CV ones this arch was built for.

Right now wrapper tests are failing because pinto can't install extras (ml4gw/pinto#7). This should be a reasonably quick fix on the pinto side, so I'll implement this this afternoon and then update the workflow here to use this feature.


feat: compare timestamp partition values as timestamps instead of strings

Description
Delta protocol specifies 2 possible formats for timestamp partitions: {year}-{month}-{day} {hour}:{minute}:{second} or {year}-{month}-{day} {hour}:{minute}:{second}.{microsecond}
However, string comparison of partition filter value and partition values was performed, which rendered timestamps like 2020-12-31 23:59:59.000000 and 2020-12-31 23:59:59 as different.
This change uses timestamp comparison instead of string comparison.
Documentation
https://github.com/delta-io/delta/blob/master/PROTOCOL.md#partition-value-serialization

@rtyler, @roeap, @wjones127 - guys, could you please review?


Node.js  Outreach Meeting 2020-12-22

Time
UTC Tue 22-Dec-2020 17:00 (05:00 PM):

Timezone
Date/Time

US / Pacific
Tue 22-Dec-2020 09:00 (09:00 AM)

US / Mountain
Tue 22-Dec-2020 10:00 (10:00 AM)

US / Central
Tue 22-Dec-2020 11:00 (11:00 AM)

US / Eastern
Tue 22-Dec-2020 12:00 (12:00 PM)

EU / Western
Tue 22-Dec-2020 17:00 (05:00 PM)

EU / Central
Tue 22-Dec-2020 18:00 (06:00 PM)

EU / Eastern
Tue 22-Dec-2020 19:00 (07:00 PM)

Moscow
Tue 22-Dec-2020 20:00 (08:00 PM)

Chennai
Tue 22-Dec-2020 22:30 (10:30 PM)

Hangzhou
Wed 23-Dec-2020 01:00 (01:00 AM)

Tokyo
Wed 23-Dec-2020 02:00 (02:00 AM)

Sydney
Wed 23-Dec-2020 04:00 (04:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Outreach+Meeting+2020-12-22&iso=20201222T1700
or https://www.wolframalpha.com/input/?i=05PM+UTC%2C+Dec+22%2C+2020+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1tmV4FvUloJVlDpD2Vm6mPNpLr_Jz-x2rUvH0DnhaNzg/edit

Agenda
Extracted from outreach-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Invited

Outreach Members: @nodejs/outreach

Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
Notes
The agenda comes from issues labelled with outreach-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

Link for participants: https://zoom.us/j/526318636
For those who just want to watch: https://www.youtube.com/nodejs-foundation

Because of light agenda and holidays, I suggest skipping this meeting.


#2222 k8s, and cluster partial refactor

Description
Refactor k8s and cluster packages to consolidate GetImagesWithNodes and GetAllImages into one function GetAvailableImagesFromNodes.
Move utility functions from images.go to prepare.go where they are used.
Delete images.go
Related Issue
Fixes #2222
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

Should GetImagesFromAvailableNodes and ImageNodeMap be public?


Doc build warning lvgl/README.rst

Describe the bug
When building the doc, there is a build warning in lvgl/README.rst
To Reproduce
Steps to reproduce the behavior:

make htmldocs

Expected behavior
No warning
Impact
Yet another doc warning, maybe some broken links
Screenshots or console output
doc/_build/rst/doc/samples/display/lvgl/README.rst:4: WARNING: duplicate label lvgl-sample, other instance in doc/_build/rt

Environment (please complete the following information):

OS: Ubuntu
Toolchain N/A
Commit SHA or Version today's master: e12757e9e91ebc9dbe2a4ff13631e7a3b6536580

Seems this was a glitch due to something else(?) closing as can't reproduce


RFC, WIP: Refactor Text into platform-specific files

Do not review yet.
React Native for Windows is going to be released as a separate npm module. Since the Windows versions of components will have platform-specific prop types and logic, we (Eric Rozell, Nick Lockwood, Konstantin Raev, David Aurelio) decided to split the cross-platform components into:

a file with code shared by all platforms
one file per platform with platform-specific code

Test plan

propTypes validation works - <Text style={'foo'} /> produces a warning both on iOS and Android:

Mixins work, tried adding TimerMixin to TextBaseMixin's mixins, Text.ios.js can use this.setTimeout and componentWillUnmount fires correctly when <Text> is unmounted.

onPress handlers work - tried <Text onPress={() => alert('press')} />

TODO: The code that renders propTypes on the website will need changes. It can't see the propTypes inherited from the mixin.

Ran the UIExplorer:

By analyzing the blame information on this pull request, we identified @sahrens and @grabbou to be potential reviewers.

@mkonicek updated the pull request.

@mkonicek updated the pull request.

It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @sahrens as a potential reviewer. Could you take a look please or cc someone with more context?

This was just an RFC to demo how we can share parts of components with RN for Windows. We can close it and keep for reference.
cc @rozele


Foxy devel

Stacked behind https://github.com/ipa-hsd/ros_model_parser/pull/1. Need to fix the issues mentioned in the comments

@ipa-nhg