CommonCrypto Error

How to solve this error
SendBird-iOS-master/sample-swift/SendBird-iOS/Common/Utils.swift:11:8: Could not build Objective-C module 'CommonCrypto'

I've never seen this error when I build this project. Did you change any configurations in this project?

I've changed signing account, bundle identifier and updated pods

I had the same error and right above it another error that was the real issue so maybe the following information will help. There is a modulemap file that is set to point to the XCode directory under the Applications folder but if you are using XCode installed in a different location that won't work. I changed the directory name in the modulemap files to match where I have XCode installed and that fixed this issue for me.

I have tried many times to get resolve my CommonCrypto problem.
Can you please let me know how to solve that. If possible then please send me some quick step to use CommonCrypto framework as updated version of CommonCrypto. I am in trouble and need some quick solution for that.
Please let me know what kind of configuration need to set there. Because your provided demo is working fine.

@ayazrafai90  Have you ever referred to this link? I referred to the answer, but I hope that other answers can help you, too.

Thanks for replied.
Yes, I reviewed that but can’t getting solutions. I just want to know the configuration of framework in build setting or info.
I have added Cocoa Touch Framework with name “CommonCrypto” now can you please let me know how to configure that wothout bridging header.

Thank you @sf-jed-kyung I have fixed that issue. But now another little problem is that I can't build my app with simulator. Do we have to set anything else?

@ayazrafai90 Let me know the error that you see.

Thanks for the instant reply. It's working perfect in real device but not running in simulator.
I have reviewed every path in Build Setting and modulemap files which absolutely perfect.
But still getting an error in simulator : fatal error: lipo: -remove's specified would result in an empty fat file.

What is the version of CocoaPods that you are using?

I am using 1.4.0.beta.2

Someone says the beta version has the problem.
https://github.com/Instabug/Instabug-iOS/issues/208
Could you try to downgrade to 1.3.1?

Do I have to update pod in my source code?

After downgrading, I think you'd better update pod.

👍 Thank you very much! Everything going smoother now.
Really happy to meet you.
Thanks once again.

Thanks you  too @aly-irshad Your issue's fixed one of mine :)

My pleasure. :-)


New url

https://github.com/asppsa/archlinux-nix/blob/126df06ec9c1d0cb59af71e5242d610c4787c91b/archlinux-nix#L59
has to be https://releases.nixos.org/... now or else the sha256 match fails hash1 being "Redirected ..."

Is duplicate of #8.


Marriage abroad: Outcome per path British Indian Ocean Territory

Trello card
Motivation
Updating Marriage abroad questions and outcomes can be quite a complex process.
Marriage abroad is also one of the most frequently updated Smart Answer.
Here we have converted the flow and flattened all outcomes belonging to British Indian Ocean Territory, to enable content designers make updates quicker.
By providing one template per outcome for marriage abroad British Indian Ocean Territory content, content editing barriers are greatly reduced.
Factcheck
Preview link
GOV.UK
Expected changes

None

As this is a refactor of British Indian Ocean Territory flow, and not a change to the content or flow of the smart-answer, users should not experience any changes. The changes that have occurred to the code are:

Templates for British Indian Ocean Territory
British Indian Ocean flow to use outcome per path
Remove British Indian Ocean Territory entries

@ikennaokpala I think I found a difference in outputs.
Heroku preview:
https://smart-answers-preview-pr-3155.herokuapp.com/marriage-abroad/y/british-indian-ocean-territory/uk

GOV UK:
https://www.gov.uk/marriage-abroad/y/british-indian-ocean-territory/uk

@mgrassotti that is a very good spot.. this has occurred because in b34a61f the country in question was revmoved from the BRITISH_OVERSEAS_TERRITORIES list.. I going to have a chat with the content design team to seek guidiance as this is a content issue.  Also see [1]
[1] https://github.com/alphagov/smart-answers/blob/master/lib/smart_answer/calculators/marriage_abroad_calculator.rb#L128-L140


GameStream Patcher is not working on Azure with Windows 10 20H2 and newest drivers

Hello,
for some reason your GameStream Patcher is not working on Azure Instances running Windows 10, version 20H2 + newest NVIDIA drivers. For some reason, Server 2019 with newest driver works and Windows 10, version 20H2 works too when you get old driver.
I think you should look into this

Try spoofing your gpu device id to a supported one. This script only patches geforce experience dll, it does not touch the driver. My guess is that there is a cross check between geforce experience and the driver installed/device id's

But the weird thing is...on Windows Server 2019, it's actually working. Same drivers, same geforce experience version.
On older Windows 10 version, it's working too, just on Windows 10 20H2 the patch is not working

Unfortunately I can't find the root cause of this issue as I currently don't have any cloud service subscriptions to test it on. I hope someone out there can do some investigation as to what is causing this.

Unfortunately I can't find the root cause of this issue as I currently don't have any cloud service subscriptions to test it on. I hope someone out there can do some investigation as to what is causing this.

I can set you up on a user account with some privs on aws.

i have the same issue when i want to use game stream  the option isnt there i need to use the old graphics driver but the problem with that is that i stuck in 1024x768 resolution pls fix this

why my shield option is not showing in geforce experience.....


Access directly warehouse Docker DB from pypi-legacy ?

Hi there,
I'm trying to get legacy-pypi to work locally, to implement pep-503 (the data-python-requires attributes).
The information to run pypi-legacy are quite out of date, but IIUC current deployed warehouse and PyPI are sharing a DB; so I guess it is possible to start a legacy-pypi and set-it up to use the docker-db...
So far I think I understood that the db ip is the docker one, usename is warehouse so config.ini should be something like... :
``
[database]
;Postgres Database
host = <IP_ADDRESS>; ? db ?
;port = 5432 ; ?? is that the right port
name = warehouse
user = postgres
password = ??;

I've commented / wrapped in try/except all the boto connexions in pypi-legacy that are trying to connect ... and end ran `python pypi.wsgi` which ends up showing this on the main page :

Database connection failed
Please try again later.

Now I'm stuck.

I'm happy to improve the documentation to tell people how to do that, which I've [started with a PR](https://github.com/pypa/pypi-legacy/pull/497), so would gladely get some help/pointers !

Thanks !

I can't help with the Docker part, but wouldn't be easier to download example.xz in https://github.com/pypa/warehouse/tree/master/dev and then use it to create the database for pypi-legacy? I haven't tried the idea but, it should be doable in theory :)

Generally when working on legacy PyPI is just use example.sql.xz like @berkerpeksag to restore to a new database. Sometimes I have to run the migrations on it and such but genreally that's what I Do.
You could adjust docker-compose.yml so that it exposes the PostgreSQL port though.

Thanks @berkerpeksag and @dstufft ! I'll try that, and if it works update the PyPI-legacy instructions !

it should be doable in theory

You know the difference between theory and practice ? In theory it's the same.  :-)

You could adjust docker-compose.yml so that it exposes the PostgreSQL port though.

Hum... my docker experience is only copy-pasting instructions, but I can try...

Good ! Moving forward, a bit, I can now connect to the database !
# url : localhost:port/simple/flit
Error...

Internal Server Error

Traceback (most recent call last):
  File "webui.py", line 489, in run
    self.inner_run()
  File "webui.py", line 744, in inner_run
    return self.run_simple()
  File "webui.py", line 1144, in run_simple
    serial = self.store.last_serial_for_package(path)
  File "store.py", line 1213, in last_serial_for_package
    (package,),
  File "store.py", line 265, in safe_execute
    return cursor.execute(sql, safe_params)
ProgrammingError: column "last_serial" does not exist
LINE 1: SELECT last_serial FROM packages WHERE name = 'flit'
               ^

last_serial can be found in commit fc6a6fa5393beec9a351604ae3794c10cc2730d4 of warehouse, from https://github.com/pypa/warehouse/pull/1166 ... anything obvious I would have missed ?
(note a few other errors, but details I can work around like having to connect through TLS)...
I'm guessing it has to do with docker-compose run web python -m warehouse db upgrade head that's likely to trigger alembic.command.upgrade(config.alembic_config(), revision, **kwargs) but then it becomes too magic for me.  Thanks !

Yea, you need to run docker-compose run web python -m warehouse db upgrade head.

Yea, you need to run docker-compose run web python -m warehouse db upgrade head.

Yeah, that's possible if you are running the docker-version, I went with @berkerpeksag advice and imported example.sql in a local version of postgres and had no clue how to run the above command on my local version.
I now have a local pypi-legacy that connects to the warehouse db container, and things seem to work !
So closing here I'll document the step on PyPI-legacy !
Thanks  for your help !


[BUG] spark350 shim build failed in mvn-verify github checks and nightly due to dependencies not released

Describe the bug
spark 3.5.0 RC is still under voting. maven repo does not have required libs for building corresponding shims for now
Let's disable 350 build in nightly to unblock mvn-verify github checks and nightly artifact build,
we can re-enable when available in the future
Steps/Code to reproduce bug
Please provide a list of steps or a code sample to reproduce the issue.
Avoid posting private or sensitive data.

@pxLi It could be a while before 3.5.0 is released, and we are already finding that PRs can be merged that break the current 3.5.0 build. Could we build the 3.5.0-rc3 artifacts ourselves and publish them to urm so that we can enable pre-merge against 3.5.0-rc3? We can then increment the version if there are future rc releases.

@pxLi It could be a while before 3.5.0 is released, and we are already finding that PRs can be merged that break the current 3.5.0 build. Could we build the 3.5.0-rc3 artifacts ourselves and publish them to urm so that we can enable pre-merge against 3.5.0-rc3? We can then increment the version if there are future rc releases.

yes, we could if needed. cc @NvTimLiu can you help deploy a pkgs and bin based on https://github.com/apache/spark/releases/tag/v3.5.0-rc3? So developers could start test against internal maven repo.
As 3.5 RC is still under voting, we will not enable https://github.com/NVIDIA/spark-rapids/blob/branch-23.10/pom.xml#L681-L682 but add a separate pipeline for 3.5 build and testing before the official release
@andygrove please also notify use whenever there is a new RC need to be built, we will need to update all corresponding CICD setups that are targeting RC-old to RC-new, thanks!

Thanks @pxLi. I will keep you posted about new rc releases.


Semi-Hard Example Sampling implementation

Hello,
I would like to ask if there is available the implementation of sampling hard positive/negatives pixel for the computation of the contrastive loss, because I only found the implementation of hard anchors sampling.
Thanks

I also have this question, have you solved it?

No, in this repo the implementation of sampling hard positives/negatives does not exist

s

Thanks a lot for quick reply! Have you try to implement it by yourself?


FS-4355: Dynamically set file url on open method

Description
The component was designed to handle both single and multiple files but wasn’t properly tested with multiple files until HSRA. We found that the accept method was setting a global URL for every individual file upload, leading to race conditions where multiple files sometimes shared the same pre-signed URL.
The fix now assigns a unique upload URL directly to each file instead of using a global URL, solving this issue. We’ve also customized the XMLHttpRequest to use the unique URL for each file's upload if available, falling back to the default URL otherwise. This approach prevents the race conditions and ensures each file has its own upload URL.

Need to bump the version on this once all the other pending PRs are merged.


Merging the branch 0.9.0 back into Master

Hi @kylemcdonald ,
Could we merge the 0.9.0 branch into Master?
Thanks

try this one:ofxDeckLink

I've merged it. But my guess is that the ofxDeckLink by @hanasaan and @satoruhiga is better :)


[feature request] call afterAll() on ctrl+c

Do you want to request a feature or report a bug?
What is the current behavior?
When I launch a test taking way too long to run, I hit ctrl+c to stop it. But... then afterAll method is not called (to clean what I have done in beforeAll).
If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can yarn install and yarn test.
What is the expected behavior?
I wish afterAll was called when typing ctrl+c
Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.

I had the same problem when run Docker or other services in beforeAll hook so I thinks is good idea to do that.
I would like to do this 💪 🤓

It would be nice if globalTeardown would also be run.

For now i have to leave this issue because I do not have so much time to do it .. 😞

Can you use timeouts instead of ctrl+c?

Any workaround or hack so far?

This may work depending on where you put it:
function exitHandler(options, err) {
    if (options.cleanup) console.log('clean');
    if (err) console.log(err.stack);
    if (options.exit) process.exit();
}

//catches ctrl+c event
process.on('SIGINT', exitHandler.bind(null, {exit:true}));

@rickhanlonii, not sure if it plays nicely with Jest workers. Does it broadcast SIGINT to workers when it gets one?

@noomorph @rickhanlonii I'm also curious about this. Not having luck putting it in the config or in the tests themselves. I have access to process, but not the .on method

any update on this?

No update, the issue with running these functions is that users could add code that hangs in the afterAll, breaking the semantics of existing the process and resulting in environment specific "cmd+c doesn't kill the process" issues.
It would be better to handle this in a more specific way as a opt-in than always running afterAll code on cmd+c, but I'm not sure what that would be.

Hey folks, I thought I'd share a quick minimal reproduction for handling SIGINT. The Jest extension for VS Code is also having issues about stopping Jest and manage the process tree. I hope this helps. 😀

@rickhanlonii, not sure if it plays nicely with Jest workers. Does it broadcast SIGINT to workers when it gets one?

Yes and no.
Yes: When you press Ctrl-c from the macOS terminal it will propagate. I don't know if that is a SIGINT though or another mechanism. Here's the process tree (using pstree) while I run and interrupt the tests for jest-community/vscode-jest.

No: When you send a SIGINT from Node.js, there is a process that is left dangling.
const child_process = require('child_process');
const process = require('process');
const delay = ms => new Promise(resolve => setTimeout(() => resolve(), ms));

(async () => {
  const { pid } = child_process.spawn('yarn', ['jest', '--watch-all'], { stdio: ['ignore', 'inherit', 'inherit'] });

  await delay(5500);
  process.kill(pid, 'SIGINT');

  try {
    process.kill(pid);
  } catch (err) {
    console.error(err);
  }
})();

I'm not sure how it will behave on Windows.
--
Good luck and keep up the great work! 👋

Oh, also this might help from the docs:

'SIGTERM' and 'SIGINT' have default handlers on non-Windows platforms that reset the terminal mode before exiting with code 128 + signal number. If one of these signals has a listener installed, its default behavior will be removed (Node.js will no longer exit).

Thanks @seanpoulter  - it sounds like crtl+c has hooks into the subprocesses so they're killed but when you only kill the parent jest process we don't forward the kill to children. I would have expected Node to handle that but I guess they don't. That's a bug we should fix.

Is there really no way to reliably clean up resources created in beforeAll?


Fix bug in LangaugeSettings.ps1

$projectPaths could be an array or string depending on how PowerShell resolves the number of .csproj files in the directory.
Fix logic to take care of both array and string cases.

Bug fix from this PR added to https://github.com/Azure/azure-sdk-for-net/pull/19651


App has a Docker image that can run in production/staging

[ ] - 👆

Bumping this to a 2 because there's question in how staging will be set up, in terms of instances for the databases(mysql, redis, memcached, elasticsearch).

Gonna touch upon this periodically.

It's done.


Edge detection ignored in flutter/dart popup tooltips

I am using VS Code 1.25.1 on Windows 7 SP1.
The tooltips that appears when the cursor hovers over a documented object do not display their content in the most readable manner. For example, the current CustomPaint tooltip appears as:
CustomPaint({Key key, CustomPainter painter, Cust
omPainter foregroundPainter, Size size: Size.zer
o, bool isComplex: false, bool willChange: false,
 Widget child}) → CustomPaint

package:flutter

Creates a widget that delegates its painting.

I argue that for greater readability, the CustomPaint tooltip should appear as:
CustomPaint({Key           key,
             CustomPainter painter,
             CustomPainter foregroundPainter,
             Size          size: Size.zero,
             bool          isComplex: false,
             bool          willChange: false,
             Widget        child}) → CustomPaint

package:flutter

Creates a widget that delegates its painting.

An argument for edges is found in http://coding-guidelines.com/cbook/sent766.pdf, Section 1.3 Edge detection, beginning on page 207.
Realizing that this modification is a significant effort, I offer my services.

@DanTup ?

@bwilkerson This text is from elementDescription so if we think this can be improved it may be better done in the server (though we would need to ensure editors can handle newlines or add as another property, either formatted, or a collection of properties). I do agree the original is a bit hard to read:

I'm not sure lining things up is perfect, though I do think it's easier to read when there's more than a few arguments:

Another possible may be to use the formatting as it appears in the source (in this case, the ButtonBar source does have them split across lines).
WDYT?

I would suggest that "more than a few" in "I'm not sure lining things up is perfect, though I do think it's easier to read when there's more than a few arguments:" read "more more than one". This makes reading the tooltip much easier. Please read the reference in the original post.

Sure, I didn't mean to suggest we shouldn't do it for smaller numbers, just that (in my head) the gain seemed smaller. For example:
clamp(int min, int max);

I don't think that's bad too bad, and is one line instead of four. However, I'm not sure changing formatting at some magic number is a good idea; I was just thinking out loud.

I am using VS Code 1.25.1 on Windows 7 SP1.

BTW, the latest version of the Dart plugin requires Code 1.27 so you're probably not seeing the updates. Doesn't affect this, but it does mean you won't have all the latest bug fixes in the plugins.

Thanks for pointing that out. I have "update_channel":"default" so it should have upgraded automatically. How do I get the upgrade? When I downloaded the zip for windows and executed it, I receive a warning that the current vs code was installed for everyone and that I should remove it. But I'm not sure I want to do that. Any thoughts?

@gggustafson There are two ways of installing VS Code - at the machine level (which will require elevation to install updates) or at the user level (each user gets their own copy in their %AppData%, which can be their own versions and upgraded by the user themselves).
I can't advise on which is best for you (though I switched to the user installs and uninstalled the main one - the less things that require elevation the better IMO, even if it's only updates), but if you're using the machine-level install you may need to approve elevation to install updates (and if you have both, that may confuse things a little, especially if you update extensions in one, then open the other and it's an older version).
You can force an update check within Code, but I'm not on Windows atm so can't confirm that the menu entry is (probably File/Help menu?). I'm not sure why it didn't auto-update though - maybe there's a VS Code bug worth filing there.

FYI, I went to Microsoft/vscode on GitHub and entered an issue. In response, a thingy name vscodebot intervened and advised me that my issue had already been raised. It pointed me to five existing answers. Unfortunately, all of them were vscodebot  responses to other users stating that the issue was already raised. Whoever built vscodebot needs to reconsider its implementation.
Latest VS Code is now 1.28 and I cannot get it down.

@gggustafson That note from vscodebot is just trying to be helpful; it hasn't closed your issue so it'll still be looked at by someone. It's useful in that sometimes it finds a real dupe and you can close your issue; though in my experience it tends to miss a lot. I tend to put 👍/👎's on the vscodebot comment in the hope that maybe it gets retrained based on that; but who knows :D

Removing tool designation since this has nothing to do with package/flutter_tools

Hi @gggustafson
following the indication of VS Code Flutter Extension
the correct way to address the problem
is to open an issue on the dedicated github
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it.
Thank you


0.1.0 SkiaSharp Update has been released! 0.1.1 and 0.1.2 too.

Coinciding with the 1st birthday of CSharpMath (October 6), the 0.1.0 SkiaSharp Update has been released. 🎉🎉🎉🎂🍰🎂🍰🎂🎉🎉🎉🎉🎉🎉🎂🍰🎂🍰🎂🎉🎉🎉🎉🎉🍰🎂🍰🎉
Edit: 0.1.1 has been released, which fixes issues mentioned below.
This supersedes #17.
Features

SkiaSharp and Xamarin.Forms platform support
CSharpMath.Forms.Example (an actual application that you would want to use)
Partial support for global-level LaTeX (only available for SkiaSharp and Xamarin.Forms)
Easier porting to other platforms with CSharpMath.Rendering, CSharpMath.Settings static class in CSharpMath.Rendering package for easier settings
Arbitrary TTF and OTF font support via Typography (SkiaSharp and Xamarin.Forms only) (Thanks @prepare)
Accents
Overlines and underlines
Colors
Raise boxes
\TeX
Proper support for primes
Beautiful \mathbb capital latters (SkiaSharp and Xamarin.Forms only)
Bugfix for nested \sqrt
LaTeX brace groups now stored in a new Group atom so that they are preserved when converting back to LaTeX strings
Fixed limits in text style, \sin, \cos etc are now non-limitable
The CSharpMath core package now targets .NET Standard 1.1!
CSharpMath now buildable in .NET Native (Thanks @FoggyFinder)
CSharpMath now has an icon
Major internal restructuring
Optimizations all over the place
Plus a lot more...

What's next?

#11 MathEditor port
#4 Merge with wpf-math

Refactor TextAtoms and MathAtoms to have common atoms
Refactor MathAtoms to get rid of MathAtomType and AtomCloner
Unit tests (and picture comparisons)
Tavis CI integration

After that...

Subpixel rendering
Getting started
Documentation of MathPainter on both NuGet and GitHub wiki
Extra docs on Measure
2 new wiki pages
Document release procedure
Promotion of the merged project
Also native support for all popular platforms
Implement \middle
Fix 1 \\ { 2 \\ 3 }'s spacing between 1 and 2

A way to limit scrolling to horizontal only or vertical only
Improve loading times of CSharpMath.Forms.Android.Example in Release mode
However, it is also not yet complete as in not being able to SeparateThisReallyLongWordWhichIsSoLongThatItSpansAcrossTheEntirePageAndWontStopEvenWhenPartOfItIsOutOfBounds.

ˢᵗᵘᶠᶠ ᶠᵒʳ ᵗʰᵉ ᶠᵃʳ ᶠᵘᵗᵘʳᵉ

@Happypig375  \textbf command doesn't work

Also for 0.1.1: Remove the two experimental buttons in Forms.Example. Previous discussion

I remember having fixed this but the fix did not appear in the codebase. Maybe I forgot to commit it. Anyways, a re-fix is on track for 0.1.1.

Nice. Do you know already approximate release date?

@Happypig375 \textbf command doesn't work

Italics stopped working too.

Nice. Do you know already approximate release date?

Today.

Italics stopped working too.

Should be also fixed.

Usable line length is not adjusted when there is "\par". This leads to incorrect wrapping. E.g. "give" is not fully displayed in the line "This is..." which starts with "\par":

@charlesroddie Somehow the notification for your comment was identified as spam. Anyways, 0.1.2 is now available to fix this.

Great. Any chance of a CSharpMath.SkiaSharp 0.1.2 which depends on the other 0.1.2 update (to keep packagereferences clean)? Thanks!

NuGet just needs a while for validating the packages. Each takes different time, independent of the order I uploaded them. In this case, SkiaSharp and Ios were successful first, and the others just needed a few more minutes.

Sorry for misinformation.
Upload time 19:56
CSharpMath 19:57
CSharpMath.Forms 19:58
CSharpMath.Ios 19:58
CSharpMath.Rendering 20:01
CSharpMath.SkiaSharp 20:18

Hi @Happypig375. The lower limits of integration are getting cut off.

@angelklim
Can you please paste the LaTeX source, TextPainter settings and the NuGet version? The displayed content does not seem right to me.

TextPainter settings are default, NuGet v0.1.2
This uses \int \limits_3^7. It looks ok with just \int_3^7 albeit a little cramped. Just \int \limits_n still cuts off the lower limit though.

@angelklim Fixed in 0.1.3

Surds in fractions are getting cut off, is it possible to move the number for the root - maybe lower and further left?

The number in the degree of the surd should have been smaller. I'll check the code.


Feature/package cores

Merges branches feat/esm-hop-node-core, feature/v2-sdk-core and feature/v2-explorer
Fixes esm builds for stats-worker and api
Adds scripts to fix core typechain contract exports for esm
pnpm clean && pnpm install && pnpm build should build all packages successfully:

packages:
  - 'packages/api'
  - 'packages/core'
  - 'packages/explorer-backend'
  - 'packages/explorer-frontend'
  - 'packages/frontend'
  - 'packages/hop-node'
  - 'packages/hop-node-core'
  - 'packages/sdk'
  - 'packages/sdk-core'
  - 'packages/sdk-demo'
  - 'packages/stats-worker'
  - 'packages/v2-explorer-backend'
  - 'packages/v2-explorer-frontend'

Packages hop-node, api, stats-worker, explorer-backend, frontend  should run without issue.

PR is up-to-date with latest develop.
All packages should build/run.
@shanefontaine


Officially support a 5Hz wifi dongle

@curcuz Already tested this on rpi3:
https://www.amazon.co.uk/high-performance-technology-Frequency-adjustable-Raspberry/dp/B01C2N2O8S/ref=sr_1_4?ie=UTF8&qid=1470089333&sr=8-4&keywords=csl+wifi
The internal wifi device can be disabled with a simple iwconfig.

I suspect the title here should be "5GHz" rather than "5Hz"? :laughing:

Correct. Fixed.


DCOS-42157: truncate FrameworkConfigurationForm labels instead of overflowing

Long labels were allowed to flow outside of s because most browsers set a useragent style on  like  min-width: min-content
Closes DCOS-42157
Testing

Go to "Catalog"
Add the Elastics services
Go to the "Elasticsearch" tab
Toggle the JSON editor open
Resize your viewport width to somewhere between 991px and 1050px

Any labels in the form should be truncated with an ellipsis, not overflowing out of the width
Trade-offs
It doesn't feel quite right to truncate a form label, but we at least provide a title attribute, and labels long enough to be truncated are an edge case
Dependencies
This issue will be more easier to reproduce once #3293 merges and makes the JSON editor wider
Screenshots
Before:

After:

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

I was surprised to see that's what happens today (truncation) as I would expect form labels to wrap. I think this is a fine fix for now but something to look at when we move our form components to the UI Kit.


Why not estimate gravity value directly

In DLIO, local gravity value is a fixed parameter and can be used to estimate the initial orientation/bias of the robot.
However, most IMU sensors do measure and report gravity, for example something like this:  acc={x=0.1, y=0.2, z=9.76}. Thus the gravity value can be calibrated automatically like so: gravity = (avg_acc - initial_bias).norm()), and it is not necessary to set the gravity value anymore
What do you think?

If anyone is interested, this is how I have implemented here:
      Eigen::Vector3f grav_vec (0., 0., this->gravity_);

      if (this->gravity_estimate_) {
        // Estimate gravity magnitude
        this->gravity_ = (accel_avg - this->state.b.accel).norm();
        grav_vec = Eigen::Vector3f (0., 0., this->gravity_);
      }


Please add support for Nova 4

Hi,
Please add support for Nova 4.
Regards

I'm not sure what's stopping this from being compliant with Nova 4.. If @milewski can point me at the issue, I'll write a PR.

Support added: v1.0.0


Changed default shortcuts to SHIFT + INSERT / CTRL + INSERT

Not sure what keys I pressed, but for some reason the extension shortcuts changed from the default Ctrl + C/ Ctrl + V to  to SHIFT + INSERT / CTRL + INSERT. Restarting VS Code, disabling/re-enabling the extension does not fix the issue.

Shift+Insert / Ctrl+Insert are other ways to copy/paste in Windows.
The extension only override Ctrl+X, Ctrl+C and Ctrl+V (see package.json)
You can override yourself by going to Preferences: Open Keyboard Shortcuts (Ctrl+K, Ctrl+S)

The problem is that Ctr+C/Ctr+V no longer works. These shortcuts are disabled by the extension. I understand that there are other shortcuts for copy/paste, but the extension should not prevent you from using the default Ctr+C/Ctr+V. It should not disable them.


feat(Renderable) Add a new Value variant: Renderable

This is a method of representing a value only though its Display or Debug implementation.
There is some discussion in #43 about making 2 different variants for Display and Debug, but that presented a problem because Valuable needs to implement Debug, but & dyn Display doesn’t. Adding a new trait like Displayable to wrap & dyn Display seems a little wasteful 😜
This method wraps both would-be variants Display and Debug in an enum Renderable and adds a new variant of the same name. The next step is to add #[display] and #[debug] derive annotations to allow struct fields to be included as their Display or Debug implementations instead of actual values (as discussed in #131)

is there any progress here? this would be incredibly helpful for custom domain specific types


Package request: Lem Editor

Re-opening #250777 because there's still interest in doing this.
Project description
Lem is an Emacs-like editor written in Common Lisp.
Metadata

homepage URL: https://lem-project.github.io/
source URL: https://github.com/lem-project/lem
license: MIT
platforms: linux, darwin

In-progress attempts:

https://github.com/NixOS/nixpkgs/issues/250777#issuecomment-2155875518
https://github.com/NixOS/nixpkgs/issues/250777#issuecomment-2172513977

And a WIP package definition for guix:

https://github.com/arthur-dog/lem-guix-packaging/blob/main/package.scm

Add a :+1: reaction to issues you find important.

Status?

Nothing yet, as far as I know...

There's now a nix flake in the repository!

Damn, that's awesome! Thanks for keeping us updated! :)

Should work now: nix run github:lem-project/lem#lem-sdl2 for the GUI variant. There's still a couple remaining issues, namely how to package/load things in contrib.


fix(tools): get docstrings from module file

FROM_COMPILER=true ./analysis/rescript-editor-analysis.exe extractDocs ~/Desktop/projects/rescript-compiler/jscomp/others/belt.res | jq '{items}[] | map(select(.id == "Belt.Array")) | .[0] | .docstrings'

Before:
[
  "[`Belt.Array`]()\n\n  **mutable array**: Utilities functions"
]

After:
[
  "Utililites for `Array` functions.\n\n### Note about index syntax\n\nCode like `arr[0]` does *not* compile to JavaScript `arr[0]`. Reason transforms\nthe `[]` index synta
x into a function: `Array.get(arr, 0)`. By default, this\nuses the default standard library's `Array.get` function, which may raise an\nexception if the index isn't found.
If you `open Belt`, it will use the\n`Belt.Array.get` function which returns options instead of raising exceptions. \n[See this for more information](../belt.mdx#array-acce
ss-runtime-safety)."
]

Should we get both rather than dropping one of them?

of course, it's an array


use default instead of active for everything color tables

Description
Resolves #3533
Replaces "active" with "discrete" for everything related to the color tables.

TODO need to regen python docstrings? maybe not...

Type of change

[x] Bug fix~~
[ ] New feature
[x] Documentation update~~
[ ] Other

How Has This Been Tested?

In the GUI this looks good. It also looks good on the CLI. None of our tests use either of the functions I changed the names for. Is any additional testing required?
Checklist:

[x] I have followed the style guidelines of this project.~~
[ ] I have performed a self-review of my own code.~~
[ ] I have commented my code where applicable.
[ ] I have updated the release notes.~~
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have confirmed new and existing unit tests pass locally with my changes.~~
[ ] I have added new baselines for any new tests to the repo.
[ ] I have NOT made any changes to protocol or public interfaces in an RC branch.~~
[ ] I have assigned reviewers (see VisIt's PR procedures for more information).~~

I may have gone too far in a few places.

Should this go on the RC at all? It does modify a user-facing cli function

This should only go on develop.

This PR is being closed; the changes are being added to develop in #17666


[install] Docker amd64 unable to build with ruby 3.3.0 - nokogiri 1.16.0 fails to install with libjemalloc2 libjemalloc-dev debian deps installed

Have you read and followed the installation tutorial at http://www.nokogiri.org/tutorials/installing_nokogiri.html?

[ x] Yes!

What is the complete output of gem install or bundle install?

when building with the jemalloc deps it throws
662.0 --- End jemalloc statistics ---
662.0
662.0 make failed, exit code 2
662.0
662.0 Gem files will remain installed in /bundle/ruby/3.3.0/gems/nokogiri-1.16.0 for
662.0 inspection.
662.0 Results logged to
662.0 /bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/nokogiri-1.16.0/gem_make.out
662.0
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:125:in `run'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:51:in `block in make'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:43:in `each'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:43:in `make'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/ext_conf_builder.rb:42:in `build'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:193:in `build_extension'
662.0 /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:227:in `block in
662.0 build_extensions'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:224:in `each'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/ext/builder.rb:224:in `build_extensions'
662.0   /usr/local/lib/ruby/3.3.0/rubygems/installer.rb:852:in `build_extensions'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/rubygems_gem_installer.rb:76:in
662.0 `build_extensions'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/rubygems_gem_installer.rb:28:in
662.0 `install'
662.0   /bundle/gems/bundler-2.5.4/lib/bundler/source/rubygems.rb:205:in `install'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/installer/gem_installer.rb:54:in
662.0 `install'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/installer/gem_installer.rb:16:in
662.0 `install_from_spec'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/installer/parallel_installer.rb:132:in
662.0 `do_install'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/installer/parallel_installer.rb:123:in
662.0 `block in worker_pool'
662.0   /bundle/gems/bundler-2.5.4/lib/bundler/worker.rb:62:in `apply_func'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/worker.rb:57:in `block in
662.0 process_queue'
662.0   <internal:kernel>:187:in `loop'
662.0   /bundle/gems/bundler-2.5.4/lib/bundler/worker.rb:54:in `process_queue'
662.0 /bundle/gems/bundler-2.5.4/lib/bundler/worker.rb:90:in `block (2 levels) in
662.0 create_threads'
662.0
662.0 An error occurred while installing nokogiri (1.16.0), and Bundler cannot
662.0 continue.
662.0
662.0 In Gemfile:
662.0   rails was resolved to 7.1.3, which depends on
662.0     actioncable was resolved to 7.1.3, which depends on
662.0       actionpack was resolved to 7.1.3, which depends on
662.0         actionview was resolved to 7.1.3, which depends on
662.0           rails-dom-testing was resolved to 2.2.0, which depends on
662.0             nokogiri
662.5 ___ Begin jemalloc statistics ___
662.5 Version: "5.3.0-0-g54eaed1d8b56b1aa528be3bdd1877e59c56fa90c"

664.7 Fetching gem metadata from https://rubygems.org/.........
666.2 Installing nokogiri 1.16.0 with native extensions
1322.8 Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
1322.8
1322.8     current directory: /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ext/nokogiri
1322.8 /usr/local/bin/ruby extconf.rb
1322.8 checking for whether -std=c99 is accepted as CFLAGS... no
1322.8 checking for whether -Wno-declaration-after-statement is accepted as CFLAGS...
1322.8 no
1322.8 checking for whether -O2 is accepted as CFLAGS... no
1322.8 checking for whether -g is accepted as CFLAGS... no
1322.8 checking for whether -Winline is accepted as CFLAGS... no
1322.8 checking for whether -Wmissing-noreturn is accepted as CFLAGS... no
1322.8 checking for whether -Wconversion -Wno-sign-conversion is accepted as CFLAGS...
1322.8 no
1322.8 Building nokogiri using packaged libraries.
1322.8 Static linking is enabled.
1322.8 Cross build is disabled.
1322.8 Using mini_portile version 2.8.5
1322.8 checking for iconv... yes
1322.8 ---------- IMPORTANT NOTICE ----------
1322.8 Building Nokogiri with a packaged version of libxml2-2.12.3.
1322.8 Configuration options: --host\=x86_64-pc-linux --enable-static --disable-shared
1322.8 --libdir\=/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxml2/2.12.3/lib
1322.8 --with-iconv\=yes --disable-dependency-tracking --without-python
1322.8 --without-readline --with-c14n --with-debug --with-threads --without-tls
1322.8 --disable-shared --enable-static CPPFLAGS\= CFLAGS\=-O2\ -U_FORTIFY_SOURCE\ -g\
1322.8 -fPIC
1322.8 The following patches are being applied:
1322.8   - 0001-Remove-script-macro-support.patch
1322.8   - 0002-Update-entities-to-remove-handling-of-ssi.patch
1322.8   - 0003-libxml2.la-is-in-top_builddir.patch
1322.8   - 0009-allow-wildcard-namespaces.patch
1322.8   - 0010-update-config.guess-and-config.sub-for-libxml2.patch
1322.8   - 0011-rip-out-libxml2-s-libc_single_threaded-support.patch
1322.8
1322.8 The Nokogiri maintainers intend to provide timely security updates, but if
1322.8 this is a concern for you and want to use your OS/distro system library
1322.8 instead, then abort this installation process and install nokogiri as
1322.8 instructed at:
1322.8
1322.8 https://nokogiri.org/tutorials/installing_nokogiri.html#installing-using-standard-system-libraries
1322.8
1322.8 Note, however, that nokogiri cannot guarantee compatibility with every
1322.8 version of libxml2 that may be provided by OS/package vendors.
1322.8
1322.8 Extracting libxml2-2.12.3.tar.xz into
1322.8 tmp/x86_64-pc-linux/ports/libxml2/2.12.3... OK
1322.8 Running git apply with
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/patches/libxml2/0001-Remove-script-macro-support.patch...
1322.8 OK
1322.8 Running git apply with
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/patches/libxml2/0002-Update-entities-to-remove-handling-of-ssi.patch...
1322.8 OK
1322.8 Running git apply with
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/patches/libxml2/0003-libxml2.la-is-in-top_builddir.patch...
1322.8 OK
1322.8 Running git apply with
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/patches/libxml2/0009-allow-wildcard-namespaces.patch...
1322.8 OK
1322.8 Running git apply with
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/patches/libxml2/0010-update-config.guess-and-config.sub-for-libxml2.patch...
1322.8 OK
1322.8 Running git apply with
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/patches/libxml2/0011-rip-out-libxml2-s-libc_single_threaded-support.patch...
1322.8 OK
1322.8 Running 'configure' for libxml2 2.12.3... OK
1322.8 Running 'compile' for libxml2 2.12.3... OK
1322.8 Running 'install' for libxml2 2.12.3... OK
1322.8 Activating libxml2 2.12.3 (from
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxml2/2.12.3)...
1322.8 Using mini_portile version 2.8.5
1322.8 ---------- IMPORTANT NOTICE ----------
1322.8 Building Nokogiri with a packaged version of libxslt-1.1.39.
1322.8 Configuration options: --host\=x86_64-pc-linux --enable-static --disable-shared
1322.8 --libdir\=/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxslt/1.1.39/lib
1322.8 --disable-dependency-tracking --without-python --without-crypto --with-debug
1322.8 --with-libxml-prefix\=/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxml2/2.12.3
1322.8 --disable-shared --enable-static CFLAGS\=-O2\ -U_FORTIFY_SOURCE\ -g\ -fPIC
1322.8 The following patches are being applied:
1322.8   - 0001-update-config.guess-and-config.sub-for-libxslt.patch
1322.8
1322.8 The Nokogiri maintainers intend to provide timely security updates, but if
1322.8 this is a concern for you and want to use your OS/distro system library
1322.8 instead, then abort this installation process and install nokogiri as
1322.8 instructed at:
1322.8
1322.8 https://nokogiri.org/tutorials/installing_nokogiri.html#installing-using-standard-system-libraries
1322.8
1322.8 Extracting libxslt-1.1.39.tar.xz into
1322.8 tmp/x86_64-pc-linux/ports/libxslt/1.1.39... OK
1322.8 Running git apply with
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/patches/libxslt/0001-update-config.guess-and-config.sub-for-libxslt.patch...
1322.8 OK
1322.8 Running 'configure' for libxslt 1.1.39... OK
1322.8 Running 'compile' for libxslt 1.1.39... OK
1322.8 Running 'install' for libxslt 1.1.39... OK
1322.8 Activating libxslt 1.1.39 (from
1322.8 /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxslt/1.1.39)...
1322.8 checking for whether -DNOKOGIRI_PACKAGED_LIBRARIES is accepted as CPPFLAGS... no
1322.8 xml2-config cflags:
1322.8 -I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxml2/2.12.3/include/libxml2
1322.8 checking for whether
1322.8 -DNOKOGIRI_LIBXML2_PATCHES="\"0001-Remove-script-macro-support.patch
1322.8 0002-Update-entities-to-remove-handling-of-ssi.patch
1322.8 0003-libxml2.la-is-in-top_builddir.patch 0009-allow-wildcard-namespaces.patch
1322.8 0010-update-config.guess-and-config.sub-for-libxml2.patch
1322.8 0011-rip-out-libxml2-s-libc_single_threaded-support.patch\"" is accepted as
1322.8 CPPFLAGS... no
1322.8 checking for -llzma... yes
1322.8 xslt-config cflags:
1322.8 -I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxml2/2.12.3/include/libxml2
1322.8 -I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ports/x86_64-linux/libxslt/1.1.39/include
1322.8 checking for whether
1322.8 -DNOKOGIRI_LIBXSLT_PATCHES="\"0001-update-config.guess-and-config.sub-for-libxslt.patch\""
1322.8 is accepted as CPPFLAGS... no
1322.8 checking for xmlParseDoc() in libxml/parser.h... yes
1322.8 checking for xsltParseStylesheetDoc() in libxslt/xslt.h... yes
1322.8 checking for exsltFuncRegister() in libexslt/exslt.h... yes
1322.8 Using mini_portile version 2.8.5
1322.8 ---------- IMPORTANT NOTICE ----------
1322.8 Building Nokogiri with a packaged version of libgumbo-1.0.0-nokogiri.
1322.8 Configuration options: --disable-shared --enable-static CFLAGS\=-fPIC
1322.8 Copying gumbo-parser files into
1322.8 tmp/x86_64-pc-linux/ports/libgumbo/1.0.0-nokogiri/gumbo-parser...
1322.8 Running 'compile' for libgumbo 1.0.0-nokogiri... OK
1322.8 Activating libgumbo 1.0.0-nokogiri (from
1322.8 ports/x86_64-linux/libgumbo/1.0.0-nokogiri)...
1322.8 checking for whether
1322.8 -I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ext/nokogiri/ports/x86_64-linux/libgumbo/1.0.0-nokogiri/include
1322.8 is accepted as CPPFLAGS... no
1322.8 checking for gumbo_parse_with_options() in nokogiri_gumbo.h... yes
1322.8 checking for xmlHasFeature()... yes
1322.8 checking for xmlFirstElementChild()... yes
1322.8 checking for xmlRelaxNGSetParserStructuredErrors()... yes
1322.8 checking for xmlRelaxNGSetValidStructuredErrors()... yes
1322.8 checking for xmlSchemaSetValidStructuredErrors()... yes
1322.8 checking for xmlSchemaSetParserStructuredErrors()... yes
1322.8 checking for rb_category_warning()... yes
1322.8 checking for whether
1322.8 -DNOKOGIRI_OTHER_LIBRARY_VERSIONS="\"libgumbo:1.0.0-nokogiri\"" is accepted as
1322.8 CPPFLAGS... no
1322.8 creating Makefile

1322.8
1322.8 current directory: /bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ext/nokogiri
1322.8 make DESTDIR\= sitearchdir\=./.gem.20240117-40744-1974oq
1322.8 sitelibdir\=./.gem.20240117-40744-1974oq
1322.8 compiling gumbo.c
1322.8 gumbo.c:32:10: fatal error: nokogiri_gumbo.h: No such file or directory
1322.8    32 | #include "nokogiri_gumbo.h"
1322.8       |          ^~~~~~~~~~~~~~~~~~
1322.8 compilation terminated.

1322.8 --- End jemalloc statistics ---
1322.8 make: *** [Makefile:472: gumbo.o] Error 1
1322.8 ___ Begin jemalloc statistics ___

If installation completed but is broken, what is the complete output from nokogiri -v?

When build as is the nokogiri inside the image is
root@c830f01b9add:/app# bundle exec nokogiri --version
# Nokogiri (1.16.0)
    ---
    warnings: []
    nokogiri:
      version: 1.16.0
      cppflags:
      - "-I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ext/nokogiri"
      - "-I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ext/nokogiri/include"
      - "-I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ext/nokogiri/include/libxml2"
      ldflags: []
    ruby:
      version: 3.3.0
      platform: x86_64-linux
      gem_platform: x86_64-linux
      description: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) +YJIT [x86_64-linux]
      engine: ruby
    libxml:
      source: packaged
      precompiled: false
      patches:
      - 0001-Remove-script-macro-support.patch
      - 0002-Update-entities-to-remove-handling-of-ssi.patch
      - 0003-libxml2.la-is-in-top_builddir.patch
      - '0009-allow-wildcard-namespaces.patch'
      - 0010-update-config.guess-and-config.sub-for-libxml2.patch
      - 0011-rip-out-libxml2-s-libc_single_threaded-support.patch
      memory_management: ruby
      iconv_enabled: true
      compiled: 2.12.3
      loaded: 2.12.3
    libxslt:
      source: packaged
      precompiled: false
      patches:
      - 0001-update-config.guess-and-config.sub-for-libxslt.patch
      datetime_enabled: true
      compiled: 1.1.39
      loaded: 1.1.39
    other_libraries:
      libgumbo: 1.0.0-nokogiri

If installation failed during compilation, what are the complete contents of the mkmf.log file generated during the failed installation?

failing durring docker build process

Tell us about your system!
docker / docker compose
compose
version: "3.9"
services:
  app:
    platform: linux/x86_64
    build:
      context: .

      ... TLDR

Docker file
FROM ruby:3.3.0-bookworm

ENV APP_HOME=/app \
#    LD_PRELOAD="libjemalloc.so.2" \
#    MALLOC_CONF="dirty_decay_ms:1000,narenas:2,background_thread:true,stats_print:true" \
    RUBY_YJIT_ENABLE="1" \
    LANG=C.UTF-8 \
    RUBY_VERSION=3.3.0 \
    BUNDLER_VERSION=2.5.4 \
    CHAMBER_VERSION=2.13.6 \
    NODE_VERSION=20 \
    BUNDLE_PATH=/bundle \
    BUNDLE_BIN=/bundle/bin \
    GEM_HOME=/bundle \
    RAILS_ENV=development \
    BUNDLE_GITLAB__COM=change_me \
    BUNDLE_GITHUB__COM=change_me
#libjemalloc2 libjemalloc-dev
# dose not work with jemalloc deps - had to remove it for now TODO: fix it

RUN apt-get update -qq \
    && DEBIAN_FRONTEND=noninteractive apt-get install -y wget nano zlib1g-dev liblzma-dev patch pkg-config

RUN wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | apt-key add -
RUN echo "deb http://apt.postgresql.org/pub/repos/apt bookworm-pgdg main" |tee  /etc/apt/sources.list.d/pgdg.list

RUN apt-get update -qq \
    && curl -fsSL https://deb.nodesource.com/setup_$NODE_VERSION.x | bash - \
    && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends nodejs

RUN apt-get update -qq \
    && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends libxml2-dev nano libxslt-dev git tzdata unzip openssl postgresql-client libjpeg62 libpng-dev libxrender1 libxext-dev wkhtmltopdf libfontconfig1 libssl-dev

RUN wget -q -O /bin/chamber https://github.com/segmentio/chamber/releases/download/v$CHAMBER_VERSION/chamber-v${CHAMBER_VERSION}-linux-amd64
RUN chmod +x /bin/chamber \
    && rm -rf /var/lib/apt/lists/* \
    && sed -i 's,^\(MinProtocol[ ]*=\).*,\1'TLSv1.0',g' /etc/ssl/openssl.cnf \
    && sed -i 's,^\(CipherString[ ]*=\).*,\1'DEFAULT@SECLEVEL=1',g' /etc/ssl/openssl.cnf

# install latest chrome for testing purposes
RUN wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
    && echo 'deb http://dl.google.com/linux/chrome/deb/ stable main' >> /etc/apt/sources.list.d/google.list
RUN apt-get update && apt-get -y install google-chrome-stable

#RUN wget -q http://archive.ubuntu.com/ubuntu/pool/main/o/openssl/openssl_1.1.1f-1ubuntu2.20_amd64.deb \
#    && yes | dpkg -i ./openssl_1.1.1f-1ubuntu2.20_amd64.deb
# old deps - left fpr refference

RUN mkdir ${APP_HOME}
WORKDIR ${APP_HOME}
RUN gem install bundler:$BUNDLER_VERSION
RUN bundle config set --global force_ruby_platform true
COPY Gemfile $APP_HOME/
COPY Gemfile.lock $APP_HOME/
RUN bundle install -j40 --retry 30 \
    && bundle check || bundle install
COPY . ${APP_HOME}

Hi, sorry you're having problems, I'll try to help.
Is there a reason you're compiling Nokogiri from source? If not, I'd recommend just using a precompiled native gem by removing this line from the dockerfile:
RUN bundle config set --global force_ruby_platform true

If you really want to compile from source, then I'll need more information from you. This line from the build indicates a problem:
1322.8 checking for whether
1322.8 -I/bundle/ruby/3.3.0/gems/nokogiri-1.16.0/ext/nokogiri/ports/x86_64-linux/libgumbo/1.0.0-nokogiri/include
1322.8 is accepted as CPPFLAGS... no

and I need to see the contents of the mkmf.log file to know for sure why this is failing.

There's definitely something wrong with the build toolchain, because lots of things I would expect to be fine are failing during build:
1322.8 checking for whether -std=c99 is accepted as CFLAGS... no
1322.8 checking for whether -Wno-declaration-after-statement is accepted as CFLAGS...
1322.8 no
1322.8 checking for whether -O2 is accepted as CFLAGS... no
1322.8 checking for whether -g is accepted as CFLAGS... no
1322.8 checking for whether -Winline is accepted as CFLAGS... no
1322.8 checking for whether -Wmissing-noreturn is accepted as CFLAGS... no
1322.8 checking for whether -Wconversion -Wno-sign-conversion is accepted as CFLAGS...
1322.8 no
...
1322.8 checking for whether -DNOKOGIRI_PACKAGED_LIBRARIES is accepted as CPPFLAGS... no

The mkmf.log will tell us more.

Thank You for a quick reply - I will deliver the info asap :)

As it turns out, a simple upgrade to rails 7.1.3 from 7.1.2 was enough to make it work flawlessly ...
Also removed redundant nokogiri arch variants from gemfile.lock - left only the x86_64 (had multiple)
Even with the native bundler platform set for ruby, it worked now ...

I have the same issue, when I try to build docker image on Macbook M1. On Mackbooks with Intel chip it builds without any problems.

@EvgeniyRRU This issue is closed. Even if it wasn't closed, the original issue was for an intel system. If you need help, please open a new issue and fill out the template.


Statement R vs SAS - Survival Analysis

Hello guys, I was looking at your repo https://psiaims.github.io/CAMIS/ recently, and in Survival Analysis I found some statement that for me is not perfectly clear. You say, talking about the quantiles, that for R "the median is the smallest time which survival estimate is <= 0.5", whether SAS "... searches the smallest time which survival estimate is < 0.5, which does not exist in this dataset ...", and the example works perfectly. But if we try to make the last observation not censored (put 1 instead of 0), the result for R doesn't change, but if it is true what you said about SAS (smallest time < 0.5) I would expect the quantile to return 118 (smallest time which survival estimate is < 0.5). Instead, the same result as R, so 102.5, is returned, which is the mean point of the segment.
What do you say about it? I think your statement is not perfectly clear and correct.
Let me know!

Hi @chrisoraruf , Thanks so much for raising this.   I will go in and add some more detail.   Could you then have another read through and if still not clear let me know.  SAS actually returns a result of NE, because the survival estimate does not go <0.5 (it is exactly = 0.5).   Many Thanks for helping us to ensure our content is clear & understandable :)   Please do come back to  us if it's still unclear once my additional content goes in.  May take a few days as i'll need pull request to be accepted by @statasaurus

@chrisoraruf those changes are now live on the website so I'll close this issue, but please have a read through and raise another issue if it's still not clear.  Thanks!


New Lotus dependencies (ffi) require OpenCL

This seems to be the normal approach in Lotus. Closing as we cannot change this


Updated template with the new design proposals link

Before the Issue Template will be globally reimplemented, the quick fix.

cc @michelleN @bgrant0607

LGTM
On Dec 19, 2016 8:13 AM, "Ihor Dvoretskyi"<EMAIL_ADDRESS>wrote:
cc @michelleN https://github.com/michelleN @bgrant0607
https://github.com/bgrant0607
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/pull/161#issuecomment-268005055,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHXi0URhGlJWptB1GmgMoXXTbhCpdu1Hks5rJq0zgaJpZM4LQ5Tc
.


UX updates for content and behavior in event log modal for a starting workbench

JIRA: https://issues.redhat.com/browse/RHOAIENG-14737
Description

Update several places:

Update the waiting message from "Waiting for notebook to start..." to "Waiting for workbench to start..." and the popover title from "Notebook status" to "Workbench status"

Update the event modal title from "Starting server" to "Starting workbench" and Update the cancel button text from "Cancel" to "Stop workbench"

When stop workbench from the event modal, it will also prompt a confirmation modal now

How Has This Been Tested?

Create a workbench
Start and stop it, check the event modal
Make sure all the content and behavior are as described

Test Impact

Updated some cypress tests to adapt to the change
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

FYI, data test IDs were updated as a result of this PR
@manosnoam

Tested in the live cluster
all the content and behaviors works as expected

Just a small comment:
https://github.com/opendatahub-io/odh-dashboard/pull/3401/files#diff-ed8131a3c29c559bbe0d910b599e583b4589517174c05d0bc13a7d48a014dec8L49-R58 this
We do have another location to change, but this isn't displayed in the UI because the modal only opens when the workbench is starting. Can we consider removing this piece of code?

Thanks for making these updates, @DaoDaoNoCode! These look good to me.

@DaoDaoNoCode thanks for the changes
/lgtm


Pinning poetry version

The recently released 1.4.1 version of poetry exposes an issue with some dependencies where package hashes/sizes are marked as invalid and installation fails with WheelFileValidationError, e.g. torch==1.12.0 - https://github.com/pytorch/pytorch/issues/97153
While this behavior can be disabled by setting installer.modern-installation to false (https://github.com/python-poetry/poetry/issues/7686) or downgrading from 1.4.1 to 1.4.0, pinning pip install poetry in Dockerfiles seems like a good idea in case of other breaking changes in the future.

closed by #82


[Bug]: String literals in MLIR are not as permissive as those in C

VAST version
master
LLVM version
17
Operating system
All
Description
String literals are more permissive in C. Especially those found in things like __attribute__((section("..."))), which are "unevaluated" string literals. C string literals support more escape formats than those supported by MLIR's string literals. Unevaluated C string literals can contain arbitrary / made up escape strings/formats.
VAST should introduce additional escape characters into the string literals where necessary.
Steps to Reproduce
const char * x = "\r"; should probably do it. Unfortunately MLIR's verifier doesn't catch this, so you need to round-trip and parse it.

This should be fixed in LLVM 18. @Jezurko can you check this?

This should only happen where a StringRefParameterl(e.g.: in the type created by typeof) is used. And it happens because this hasn't been merged into an llvm release yet.
But right now both of the cases you mentioned should be handled by our own core::StringLiteralAttr*  and should work properly (and at least for me it did on current master branch).
I think it's preferable to wait until the fix gets into a release, as we would be duplicating logic while bringing more complexity to our TableGen code.
*soon to be replace by mlir::StringAttr that also handles it and we don't need our own String attribute anymore.

"Should probably do it" is not exactly a step to reproduce, please next time provide proper steps.

Just in case I didn't understand you properly - try it with #467 which is removing the core::StringLiteralAttr

Just in case I didn't understand you properly - try it with #467 which is removing the core::StringLiteralAttr

I will test this branch once it is merge to master. The issue I observed is in this MLIR function:
/// Lex a string literal.
///
///   string-literal ::= '"' [^"\n\f\v\r]* '"'
///
/// TODO: define escaping rules.
Token Lexer::lexString(const char *tokStart) {

Found [here](https://mlir.llvm.org/doxygen/AsmParser_2Lexer_8cpp_source.html#:~:text=405 Token-,Lexer%3A%3AlexString,-(const char). I figured the issue was actually in the pretty printers, i.e. that when pretty printing string literals, an extra add slashes step would be needed, so that MLIR's string literal lexer would not complain.

const char * x = "\r"; should probably do it. Unfortunately MLIR's verifier doesn't catch this, so you need to round-trip and parse it.

@lkorenc, @Jezurko  I've now confirmed that my suggested example is indeed enough to reproduce this issue. Again, the key is that the relevant error message (shown below) only manifests when parsing the human-readable MLIR, and is not caught by the MLIR verifier.
Example error:
loc("-":66:33): error: unknown escape in string literal

@pgoodman sorry, my fault. I now reproduced the issue on master and can also confirm that it is fixed with the PR (because the LLVM/MLIR printer uses the hex codes instead of the "special" characters - and therefore it can also parse it)


Serve content from memory

What was wrong?
May not always want to offer content from database, sometimes want to offer it from memory. See #368
LRU cache is a hacky solution, this is ... a little less hacky.
How was it fixed?
Added a new PopulatedOffer which is just like an Offer but with the data included.
This is a special-cased out-bound only offer that allows us to skip all the database lookups. Even more importantly, we can offer data that never gets stored locally, like in the bridge nodes.
There are a couple of commits added at the end, related to the peertest failure in CI. The commits are pretty tidy, for reviewing one at a time.
To-Do

[ ] Add entry to the release notes (may forgo for trivial changes)
[ ] Clean up commit history
[x] Add commit that reverts LRU cache

Not able to reproduce the peertest failure locally. I assume this is the same thing that everyone else is running into.

So it looks like we have a little more info with the peertest failure, when the exit(1) is removed:
Jul 28 16:17:00.840  INFO ethportal_peertest::jsonrpc: Testing IPC method: "portal_historyStore"
Jul 28 16:17:01.026 DEBUG trin_core::jsonrpc::service: New IPC client: (unnamed)
Jul 28 16:17:01.028 DEBUG trin_core::jsonrpc::service: Got new IPC request: Ok(JsonRequest { jsonrpc: "2.0", params: Array([String("0x000300720704f3aa11c53cf344ea069db95cecb81ad7453c8f276b2a1062979611f09c"), String("0xf90222a02c58e3212c085178dbb1277e2f3c24b3f451267a75a234945c1581af639f4a7aa058a694212e0416353a4d3865ccf475496b55af3a3d3b002057000741af9731919400192fb10df37c9fb26829eb2cc623cd1bf599e8a067a9fb631f4579f9015ef3c6f1f3830dfa2dc08afe156f750e90022134b9ebf6a018a2978fc62cd1a23e90de920af68c0c3af3330327927cda4c005faccefb5ce7a0168a3827607627e781941dc777737fc4b6beb69a8b139240b881992b35b854eab9010000200000400000001000400080080000000000010004010001000008000000002000110000000000000090020001110402008000080208040010000000a8000000000000000000210822000900205020000000000160020020000400800040000000000042080000000400004008084020001000001004004000001000000000000001000000110000040000010200844040048101000008002000404810082002800000108020000200408008000100000000000000002020000b00010080600902000200000050000400000000000000400000002002101000000a00002000003420000800400000020100002000000000000000c00040000001000000100187327bd7ad3116ce83e147ed8401c9c36483140db184627d9afa9a457468657265756d50504c4e532f326d696e6572735f55534133a0f1a32e24eb62f01ec3f2b3b5893f7be9062fbf5482bc0d490a54352240350e26882087fbb243327696851aae1651b6")]), method: "portal_historyStore", id: 11 })
Jul 28 16:17:01.028 DEBUG trin_core::jsonrpc::handlers: Processing Portal JSON-RPC request: HistoryEndpoint(Store)
Jul 28 16:17:01.352 DEBUG discv5::discv5: Discv5 service already shutdown
Jul 28 16:17:01.353 DEBUG discv5::discv5: Discv5 service already shutdown
Jul 28 16:17:01.353 DEBUG trin_core::jsonrpc::service: Panic hook: Skipped removing /tmp/trin-jsonrpc.ipc because: No such file or directory (os error 2)
Jul 28 16:17:01.353 DEBUG trin_core::jsonrpc::service: Panic hook: Skipped removing /tmp/ethportal-peertest-buddy-2.ipc because: No such file or directory (os error 2)
Jul 28 16:17:01.353 DEBUG trin_core::jsonrpc::service: Panic hook: Skipped removing /tmp/ethportal-peertest-buddy-1.ipc because: No such file or directory (os error 2)
Jul 28 16:17:01.561 DEBUG discv5::discv5: Discv5 service already shutdown
test test::test_launches has been running for over 60 seconds

There was a panic, but no information printed about the panic :/

... and now it looks like it's hanging, which is presumably why the exit(1) was there in the first place. We just need to find a better solution for a clean rpc exit I suppose.

Failure on Windows build with:
Aug 03 01:36:54.028 DEBUG trin_core::jsonrpc::service: New IPC client: (unnamed)
Aug 03 01:36:54.031 DEBUG trin_core::jsonrpc::service: Got new IPC request: Ok(JsonRequest { jsonrpc: "2.0", params: Array([String("0x000300720704f3aa11c53cf344ea069db95cecb81ad7453c8f276b2a1062979611f09c"), String("0xf90222a02c58e3212c085178dbb1277e2f3c24b3f451267a75a234945c1581af639f4a7aa058a694212e0416353a4d3865ccf475496b55af3a3d3b002057000741af9731919400192fb10df37c9fb26829eb2cc623cd1bf599e8a067a9fb631f4579f9015ef3c6f1f3830dfa2dc08afe156f750e90022134b9ebf6a018a2978fc62cd1a23e90de920af68c0c3af3330327927cda4c005faccefb5ce7a0168a3827607627e781941dc777737fc4b6beb69a8b139240b881992b35b854eab9010000200000400000001000400080080000000000010004010001000008000000002000110000000000000090020001110402008000080208040010000000a8000000000000000000210822000900205020000000000160020020000400800040000000000042080000000400004008084020001000001004004000001000000000000001000000110000040000010200844040048101000008002000404810082002800000108020000200408008000100000000000000002020000b00010080600902000200000050000400000000000000400000002002101000000a00002000003420000800400000020100002000000000000000c00040000001000000100187327bd7ad3116ce83e147ed8401c9c36483140db184627d9afa9a457468657265756d50504c4e532f326d696e6572735f55534133a0f1a32e24eb62f01ec3f2b3b5893f7be9062fbf5482bc0d490a54352240350e26882087fbb243327696851aae1651b6")]), method: "portal_historyStore", id: 11 })
Aug 03 01:36:54.031 DEBUG trin_core::jsonrpc::handlers: Processing Portal JSON-RPC request: HistoryEndpoint(Store)
Aug 03 01:36:54.231 DEBUG trin_core::jsonrpc::service: New IPC client: (unnamed)
Aug 03 01:36:54.232 DEBUG trin_core::jsonrpc::service: Got new IPC request: Ok(JsonRequest { jsonrpc: "2.0", params: Array([String("enr:-IS4QKjoo7Ks3ghrWSROc6UzZ0jD3ENsVwEKyz6Um1yT8sgKQGP97-jzZod-HTdDtUTKu96_n2nR-VtWR1E7O35oRU4BgmlkgnY0gmlwhH8AAAGJc2VjcDI1NmsxoQLNT3JLMGY9ao9J0CPP6tlcGXyEtLpESGp-UV4La22VAYN1ZHCCIyk"), Array([String("0x000300720704f3aa11c53cf344ea069db95cecb81ad7453c8f276b2a1062979611f09c")])]), method: "portal_historyOffer", id: 11 })
Aug 03 01:36:54.232 DEBUG trin_core::jsonrpc::handlers: Processing Portal JSON-RPC request: HistoryEndpoint(Offer)
Aug 03 01:36:54.241 DEBUG discv5::service: Sending RPC Request: id: f90e8d775e2935e2: TALK: protocol: 500b, request:<PHONE_NUMBER>04000000000300720704f3aa11c53cf344ea069db95cecb81ad7453c8f276b2a1062979611f09c to node: Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.243 DEBUG trin_core::portalnet::overlay_service: [History] Node set to Connected. Node: 0xb871..66a9
Aug 03 01:36:54.244 DEBUG trin_core::portalnet::overlay_service: [History] Handling request f90e8d775e2935e2
Aug 03 01:36:54.244 DEBUG trin_history::events: Sending reply: Accept(Accept { connection_id: 40728, content_keys: Bitfield { bytes: [1], len: 1, _phantom: PhantomData } })
Aug 03 01:36:54.245 DEBUG discv5::service: Sending TALK response to Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.246 DEBUG discv5::service: Received RPC response: Response: Response 07189f0600000003 to request: TALK: protocol: 500b, request:<PHONE_NUMBER>04000000000300720704f3aa11c53cf344ea069db95cecb81ad7453c8f276b2a1062979611f09c from: Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.247 DEBUG trin_core::portalnet::overlay_service: [History] Node set to Connected. Node: 0x8a27..1b0f
Aug 03 01:36:54.248 DEBUG trin_core::utp::stream: sent Packet { type: Syn, version: 1, extension: None, connection_id: 6303, timestamp: Timestamp(1150419510), timestamp_difference: Delay(0), wnd_size: 0, seq_nr: 1, ack_nr: 0 }
Aug 03 01:36:54.249 DEBUG discv5::service: Sending RPC Request: id: 4d0540d6e6430252: TALK: protocol: 757470, request: 4100189f44920236000000000000000000010000 to node: Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.250 DEBUG trin_core::utp::stream: received Packet { type: Syn, version: 1, extension: None, connection_id: 6303, timestamp: Timestamp(1150419510), timestamp_difference: Delay(0), wnd_size: 0, seq_nr: 1, ack_nr: 0 }
Aug 03 01:36:54.251 DEBUG trin_core::utp::stream: Handle packet: Syn. Conn state: Uninitialized
Aug 03 01:36:54.251 DEBUG discv5::service: Sending RPC Request: id: 427d8ab1e56bf044: TALK: protocol: 757470, request: 2100189f44920e6100000c2b00100000d3360001 to node: Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.253 DEBUG discv5::service: Sending empty TALK response to Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.254 DEBUG trin_core::utp::stream: received Packet { type: State, version: 1, extension: None, connection_id: 6303, timestamp: Timestamp(1150422625), timestamp_difference: Delay(3115), wnd_size: 1048576, seq_nr: 54070, ack_nr: 1 }
Aug 03 01:36:54.254 DEBUG trin_core::utp::stream: Handle packet: State. Conn state: SynSent
Aug 03 01:36:54.255 DEBUG trin_core::utp::stream: sent Packet { type: Data, version: 1, extension: None, connection_id: 6304, timestamp: Timestamp(1150426547), timestamp_difference: Delay(3388), wnd_size: 0, seq_nr: 2, ack_nr: 54069 }
Aug 03 01:36:54.254 DEBUG discv5::service: Received RPC response: Response: Response  to request: TALK: protocol: 757470, request: 2100189f44920e6100000c2b00100000d3360001 from: Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.255 DEBUG trin_core::utp::stream: sent Packet { type: State, version: 1, extension: None, connection_id: 6303, timestamp: Timestamp(1150422625), timestamp_difference: Delay(3115), wnd_size: 1048576, seq_nr: 54070, ack_nr: 1 }
Aug 03 01:36:54.255 DEBUG discv5::service: Sending empty TALK response to Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.255 DEBUG discv5::service: Sending RPC Request: id: f8f5aedd8d84ee9a: TALK: protocol: 757470, request: 010018a044921db300000d3c000000000002d33504000000f90222a02c58e3212c085178dbb1277e2f3c24b3f451267a75a234945c1581af639f4a7aa058a694212e0416353a4d3865ccf475496b55af3a3d3b002057000741af9731919400192fb10df37c9fb26829eb2cc623cd1bf599e8a067a9fb631f4579f9015ef3c6f1f3830dfa2dc08afe156f750e90022134b9ebf6a018a2978fc62cd1a23e90de920af68c0c3af3330327927cda4c005faccefb5ce7a0168a3827607627e781941dc777737fc4b6beb69a8b139240b881992b35b854eab9010000200000400000001000400080080000000000010004010001000008000000002000110000000000000090020001110402008000080208040010000000a8000000000000000000210822000900205020000000000160020020000400800040000000000042080000000400004008084020001000001004004000001000000000000001000000110000040000010200844040048101000008002000404810082002800000108020000200408008000100000000000000002020000b00010080600902000200000050000400000000000000400000002002101000000a00002000003420000800400000020100002000000000000000c00040000001000000100187327bd7ad3116ce83e147ed8401c9c36483140db184627d9afa9a457468657265756d50504c4e532f326d696e6572735f55534133a0f1a32e24eb62f01ec3f2b3b5893f7be9062fbf5482bc0d490a54352240350e26882087fbb243327696851aae1651b6 to node: Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.256 DEBUG discv5::service: Received RPC response: Response: Response  to request: TALK: protocol: 757470, request: 4100189f44920236000000000000000000010000 from: Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.258 DEBUG trin_core::utp::stream: received Packet { type: Data, version: 1, extension: None, connection_id: 6304, timestamp: Timestamp(1150426547), timestamp_difference: Delay(3388), wnd_size: 0, seq_nr: 2, ack_nr: 54069 }
Aug 03 01:36:54.258 DEBUG trin_core::utp::stream: Handle packet: Data. Conn state: Connected
Aug 03 01:36:54.259 DEBUG discv5::service: Sending RPC Request: id: 28b06fe535dc994a: TALK: protocol: 757470, request: 2100189f44922d6f00000fbc00100000d3360002 to node: Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.261 DEBUG discv5::service: Sending empty TALK response to Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.262 DEBUG trin_core::utp::stream: received Packet { type: State, version: 1, extension: None, connection_id: 6303, timestamp: Timestamp(1150430575), timestamp_difference: Delay(4028), wnd_size: 1048576, seq_nr: 54070, ack_nr: 2 }
Aug 03 01:36:54.262 DEBUG trin_core::utp::stream: Handle packet: State. Conn state: Connected
Aug 03 01:36:54.262 DEBUG trin_core::jsonrpc::service: New IPC client: (unnamed)
Aug 03 01:36:54.262 DEBUG discv5::service: Received RPC response: Response: Response  to request: TALK: protocol: 757470, request: 2100189f44922d6f00000fbc00100000d3360002 from: Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.263 DEBUG trin_core::jsonrpc::service: Got new IPC request: Ok(JsonRequest { jsonrpc: "2.0", params: Array([String("0x000300720704f3aa11c53cf344ea069db95cecb81ad7453c8f276b2a1062979611f09c")]), method: "portal_historyLocalContent", id: 16 })
Aug 03 01:36:54.263 DEBUG discv5::service: Sending RPC Request: id: dc9db414e522a67b: TALK: protocol: 757470, request: 110018a044923b9300000000000000000003d335 to node: Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.263 DEBUG trin_core::utp::stream: sent Packet { type: State, version: 1, extension: None, connection_id: 6303, timestamp: Timestamp(1150430575), timestamp_difference: Delay(4028), wnd_size: 1048576, seq_nr: 54070, ack_nr: 2 }
Aug 03 01:36:54.263 DEBUG trin_core::utp::stream: Removed packet from incoming buffer: Packet { type: Data, version: 1, extension: None, connection_id: 6304, timestamp: Timestamp(1150426547), timestamp_difference: Delay(3388), wnd_size: 0, seq_nr: 2, ack_nr: 54069 }
Aug 03 01:36:54.264 DEBUG trin_core::jsonrpc::handlers: Processing Portal JSON-RPC request: HistoryEndpoint(LocalContent)
Aug 03 01:36:54.264 DEBUG discv5::service: Sending empty TALK response to Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.266 DEBUG trin_core::utp::stream: received Packet { type: Fin, version: 1, extension: None, connection_id: 6304, timestamp: Timestamp(1150434195), timestamp_difference: Delay(0), wnd_size: 0, seq_nr: 3, ack_nr: 54069 }
Aug 03 01:36:54.266 DEBUG trin_core::utp::stream: Handle packet: Fin. Conn state: Connected
Aug 03 01:36:54.266 DEBUG trin_core::utp::stream: FIN received but there are missing acknowledgements for sent packets
Aug 03 01:36:54.266 DEBUG discv5::service: Received RPC response: Response: Response  to request: TALK: protocol: 757470, request: 010018a044921db300000d3c000000000002d33504000000f90222a02c58e3212c085178dbb1277e2f3c24b3f451267a75a234945c1581af639f4a7aa058a694212e0416353a4d3865ccf475496b55af3a3d3b002057000741af9731919400192fb10df37c9fb26829eb2cc623cd1bf599e8a067a9fb631f4579f9015ef3c6f1f3830dfa2dc08afe156f750e90022134b9ebf6a018a2978fc62cd1a23e90de920af68c0c3af3330327927cda4c005faccefb5ce7a0168a3827607627e781941dc777737fc4b6beb69a8b139240b881992b35b854eab9010000200000400000001000400080080000000000010004010001000008000000002000110000000000000090020001110402008000080208040010000000a8000000000000000000210822000900205020000000000160020020000400800040000000000042080000000400004008084020001000001004004000001000000000000001000000110000040000010200844040048101000008002000404810082002800000108020000200408008000100000000000000002020000b00010080600902000200000050000400000000000000400000002002101000000a00002000003420000800400000020100002000000000000000c00040000001000000100187327bd7ad3116ce83e147ed8401c9c36483140db184627d9afa9a457468657265756d50504c4e532f326d696e6572735f55534133a0f1a32e24eb62f01ec3f2b3b5893f7be9062fbf5482bc0d490a54352240350e26882087fbb243327696851aae1651b6 from: Node: 0x8a27..1b0f, addr: <IP_ADDRESS>:9001
Aug 03 01:36:54.267 DEBUG trin_core::jsonrpc::service: Panic hook: Skipped removing /tmp/trin-jsonrpc.ipc because: The system cannot find the file specified. (os error 2)
Aug 03 01:36:54.268 DEBUG trin_core::jsonrpc::service: Panic hook: Skipped removing /tmp/ethportal-peertest-buddy-2.ipc because: The system cannot find the file specified. (os error 2)
Aug 03 01:36:54.268 DEBUG trin_core::jsonrpc::service: Panic hook: Skipped removing /tmp/ethportal-peertest-buddy-1.ipc because: The system cannot find the file specified. (os error 2)
Aug 03 01:36:54.268 DEBUG discv5::service: Sending empty TALK response to Node: 0xb871..66a9, addr: <IP_ADDRESS>:9000
Aug 03 01:36:54.268  WARN discv5::service: Failed to send empty talk response channel closed
Aug 03 01:36:54.269 DEBUG discv5::discv5: Discv5 service already shutdown
Aug 03 01:36:54.270 DEBUG discv5::discv5: Discv5 service already shutdown
Aug 03 01:36:54.332 DEBUG discv5::discv5: Discv5 service already shutdown
test test::test_launches has been running for over 60 seconds

Too long with no output (exceeded 10m0s): context deadline exceeded


ES Inverter - New Sensor Update: Warning Code is actually the battery level

sensor.goodwe_warning is the current battery level
sensor.goodwe_battery_status is definately not my battery level or status

Please elaborate bit more.
Why do you think warning is level ? You mean SoC ?
What are the values of battery_soc and battery_soh then ?
Why battery_status is not status and what is it ?

I have an EM invertor and I see the same behavior the warning code sensor is an exact copy of the battery charge level. (SoC)


Prioritise the Documentation Team's work - mark as MVP

@richpomfret and @richpomfret do you agree with my prirotisation?

Bumping for my inbox

@DeniseColbert

Should #170 be labelled MVP? It's in a MVP epic.

Yes - I've given #170 the MVP phase.

Hi Pat and Denise,
It’s on my list of “jobs to do” and has been for some months, but (off topic) I have been working on the basis that “Help” pages were a bit higher on my list of “to-do-jobs” than “About” pages. I had always been working on the basis that it was MVP, but when is that?
This task (of page writing) also seems to have several #-numbers associated with it.
I can certainly write an outline of the page, but it will be somewhat different to its FreeBMD(1) predecessor, which used a number of html and Perl pages. Its a bit more complicated than that, because I have no knowledge of what the format of the output or outputs from the FreeBMD2 App or Apps will “look like”.
Most of the html pages that can be moved across are there in either mostly complete or skeletal form. So, I know what with be “hanging off” that Tab-page.
Is there a date for MVP (I believe at one time it was this Summer), or is it still a bit “fuzzy” still?
Sent from Mail for Windows 10
From: PatReynolds
Sent: 27 October 2020 12:24
To: FreeUKGen/FreeBMD2
Cc: Subscribed
Subject: Re: [FreeUKGen/FreeBMD2] Prioritise the Documentation Team's work -mark as MVP (#247)
Yes - I've given #170 the MVP phase.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think the pages are now all marked appropriately, so suggest review at next scrum with a view to closing.

Appears complete now so closing.


Clicking "Top" and then "Recent"

Clicking "Top" and then "Recent" quickly results in top rants showing but the buttons on the top indicates "Recent".

Were currently working on this, check #104. Should be fixed tomorrow.

👍

This is actually a bit different than #104. Need to have a look.

This seems to be the network requests arriving at different times. @tahnik, suggestion for fix: don't dispatch send event unless last one is finished.


Robustness: Heathchecks and restarts for analyzer

If analyzer gets stuck, let's restart it for our users.
Might need something like a health check and heuristics for "analyzer is dead, jim" and restart.
Users shouldn't have to diagnose why their editor is slow or broken. :)

Might fix issues like https://github.com/dart-atom/dartlang/issues/72

We have some diagnostics plumbed in.


Contents overflows when using the highlight shortcode with the "linenos=table" option.

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.100.2-d25cb2943fd94ecf781412aeff9682d5dc62e284 windows/amd64 BuildDate=2022-06-08T10:25:57Z VendorInfo=gohugoio

This bug is reproduced in v0.93.0 and later.
Does this issue reproduce with the latest release?
Yes.
Problem
After v0.93.0 and later, contents overflows when using highlight shortcode with the "linenos=table" option.
{{< highlight react "linenos=table" >}}
// some code
{{< / highlight >}}

This result is rendered with the browser default style sheet only. There is no my custom style.
Woking fine with v0.92.2. A horizontal scroll bar appears when the browser width is reduced.

This is the smallest sample that the bug reproduces.
https://github.com/k1350/hugo_sample


StormwindDies

Recreate the following GUI trigger in C#.

The Construction Site stuff is getting simplified so we can't do this without the new map.


Unpopulated Volumes Dropdown in Templates in Portainer 2.21.4

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
The selection of named volumes is not available using templates.
When trying to deploy many (maybe a problem with all, only checked Caddy, Gitlab, Ghost and Solr) applications via the Templates -> Application feature, under Advanced Options, the Volume mapping "Volume" option should allow selection of a named volume from a drop down, in a similar manner to the "Containers" Advanced Volume option. The dropdown is unpopulated and there seems to be no way to edit it. Therefore named volumes cannot be accessed in an obvious manner.
Expected Behavior
In an analogous manner to the behaviour shown by Containers -> "Add Container", Advanced Container Settings -> Volumes tab -> "map additional volume" - the dropdown Volume selector shows all available volumes.
So I would expect, for example:

On the left, under "Local" environment selecting "Templates", "Application"
Select "GitLab CE" from the list of templates on the right
In the details form expand "Show advanced options"
to the right of the third container mapping to /var/opt/gitlab click "Volume"
A selection dropdown of available Volumes should appear allowing selection

This image taken from the behaviour of the Container equivalent:

Actual Behavior
When clicking on the Volume dropdown one obtains an unpopulated list (with a gray background) with no way to edit or select anything.

Steps to Reproduce
Using Portainer 2.21.4, with local docker installation as the only environment.
The underlying host is a Debian 6.1.119-1 (2024-11-22) x86_64 a VM running on ProxMox Linux 6.8.12-5-pve (2024-12-03T10:26Z)

On the left, under "Local" environment selecting "Templates", "Application"
Select "GitLab CE" from the list of templates on the right
In the details form, at the top of the page, expand "Show advanced options"
To the right of the third container mapping to /var/opt/gitlab click "Volume"
A selection dropdown of available Volumes should appear allowing selection

Portainer logs or screenshots
Logs not relevant as no action is finalised.
Relevant screenshots are above - reproduced here:

The correct behaviour as expected in the "Add container" context

The incorrect behaviour as experienced in the Template context

Portainer version
2.21.4
Portainer Edition
Community Edition (CE)
Platform and Version
Docker CE 27.4.0
OS and Architecture
Debian 6.1.119-1 (2024-11-22) x86_64 running as VM on ProxMox Linux 6.8.12-5-pve (2024-12-03T10:26Z) running on hardware AMD Ryzen 7 8745HS w/ Radeon 780M Graphics (1 Socket)
Browser
Firefox 133.0 on Windows 11 Pro (up to date)
What command did you use to deploy Portainer?
docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always
-v /var/run/docker.sock:/var/run/docker.sock
-v portainer_app_data:/usr/share/portainer
-v portainer_data:/data
portainer/portainer-ce:2.21.4
Additional Information
No response

Thanks @mcginnie I have tested this on our STS release and confirmed I can add the named volume but under 2.21.4 I cannot. I am raising this internally


septentrio_gnss_driver: 1.4.0-2 in 'jazzy/distribution.yaml' [bloom]

Increasing version of package(s) in repository septentrio_gnss_driver to 1.4.0-2:

upstream repository: https://github.com/septentrio-gnss/septentrio_gnss_driver
release repository: https://github.com/ros2-gbp/septentrio_gnss_driver_ros2-release.git
distro file: jazzy/distribution.yaml
bloom version: 0.11.2
previous version for package: null

septentrio_gnss_driver
* New features
  * Send custom commands via ASCII file on startup
  * Save config to boot after setup
  * NTP and PTP server options (BREAKING: NTP is not setup automatically for use_gnss_time: true anymore)
  * Receiver status on /diagnostics
  * Option to publish only valid SBF block messages
  * Option to auto publish available messages for configure_rx: false
* Changes
  * Change floating point do-not-use-values to NaN (BREAKING in case these values ae used for validity checks downstream)
  * VSM now uses separate TCP device specified IP server
* Improvements
  * Rework some sections of the README
  * Combine ROS 1 and ROS 2 in one branch
  * Change GPSFix publishing policy to allow for high update rates

Holding for Jazzy sync


Failed to access tables on alibaba oss via spark + gluten + velox

Describe the bug
refer to https://github.com/facebookincubator/velox/issues/4615
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

@Yohahaha Is OSS supported added to velox?

@Yohahaha Is OSS supported added to velox?

No, OSS support feature is partially enabled in Alibaba could EMR 5.11.1, we have not push this feature to Velox due to some internal dependency has not been opensourced, but it will done in soon.
@leesf you could contract us offline to get OSS support for test.

thanks, would you please add my wechat: xleesf

@Yohahaha Is OSS supported added to velox?

No, OSS support feature is partially enabled in Alibaba could EMR 5.11.1, we have not push this feature to Velox due to some internal dependency has not been opensourced, but it will done in soon.
@leesf you could contract us offline to get OSS support for test.

hi, i have the same question, how can we contract offline? my wechat: jigezhuanxiang


Enable relocation test

Now that callmemaybe is replaced we can run the test.

Is this ready to be pushed?


'Version Package Manifest' giving error with this sample code

Below is what I was getting from my build pipeline.  Seems like  I fixed this by putting it all on the same line, and maybe removing the semicolon at the end.  Here's what I ended up with that worked.

powershell: |
[Reflection.Assembly]::LoadWithPartialName("System.Xml.Linq")
$path = "PlanomaticPackage/Package.appxmanifest"
$doc = [System.Xml.Linq.XDocument]::Load($path)
$xName = [System.Xml.Linq.XName]"{http://schemas.microsoft.com/appx/manifest/foundation/windows10}Identity"
$doc.Root.Element($xName).Attribute("Version").Value = "$(major).$(minor).$(build).$(revision)"
$doc.Save($path)
displayName: 'Version Package Manifest'

and the error:
Cannot convert argument "name", with value: "System.Xml.Linq.XName", for "Element" to type "System.Xml.Linq.XName":
"Cannot convert the "System.Xml.Linq.XName" value of type "System.RuntimeType" to type "System.Xml.Linq.XName"."
At D:\a_temp\a49d836d-2d06-4c14-ad96-e3cf22881399.ps1:8 char:1

$doc.Root.Element($xName).Attribute("Version").Value =

  + CategoryInfo          : NotSpecified: (:) [], ParentContainsErrorRecordException
  + FullyQualifiedErrorId : MethodArgumentConversionInvalidCastArgument

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

ID: 57e7e624-229c-a7f4-caf7-c09767d5f942
Version Independent ID: 8a980367-fc9c-b208-0246-a436cecf4688
Content: Set up a CI/CD pipeline to automate your MSIX builds and deployments - MSIX
Content Source: msix-src/desktop/azure-dev-ops.md
Product: msix
GitHub Login: @Huios
Microsoft Alias: tajimha

To fix it use that code instead (call static "factory method" Get)
$xName =
[System.Xml.Linq.XName]::Get(
"{http://schemas.microsoft.com/appx/manifest/foundation/windows10}Identity");


Merge pull request #12 from juice-shop/master

merging new juice shop in kiwashop

Description

A clear and concise summary of the change and which issue (if any) it fixes. Should also include relevant motivation and context.
Resolved or fixed issue:
Affirmation

[ ] My code follows the CONTRIBUTING.md guidelines

Sorry, I'll have to decline this (probably accidental) PR. We'll stick to the 🧃 theme... 😉


(powershell) Nested comments are not recognized

Describe the issue

PowerShell supports nested comments, but Highlight.js seems to be unaware of that.
Which language seems to have the issue?

powershell
Are you using highlight or highlightAuto?
This is reproducible with both methods, but I used highlight.
Sample Code to Reproduce

<# Some <# nested #> comment #> Get-ChildItem C:\Windows\Fonts -Recurse |
Where -Match ".*\.fon" | ForEach-Object { Remove-Item $_.name }
# short form
ls \Windows\Fonts -rec | ? -m ".*\.fon" | % { rm $_.name }

https://jsfiddle.net/Keyacom/qvm7p3bx/14/
Expected behavior

The part comment #> should also be highlighted as a comment, but Get-ChildItem C:\Windows\Fonts -Recurse | should not.
Additional context

Even GitHub's syntax highlighter gets this wrong, but another syntax highlighting library that's used in some places on the Web (and written in Python), Pygments, gets this right.

Confirm, would you be interested in working on a PR for this?

I was fooled by the fact #> can both start an inline comment thanks to #, and end a multiline comment, but as it turns out, comments cannot be nested in PowerShell.


chore: release v1.534.0

feat: thorchain LP halted pool tag (#6139)
fix: ensure optimism network fees are included in eip-1559 transactions (#6151)
fix: add tooltips on confirm step of trade (#6150)
chore: remove dead code relating to single hop trade ui (#6117)
feat: hide virtual pools in Thorchain LP "Available Pools" view (#6138)
fix: thorchain LP add liquidity radio shenanigans (#6147)
chore: update app translations (#6145)
fix: force thorchain swapper to wait for outbound tx confirmations on-chain (#6143)
fix: dont nuke trade input state when backing out of a trade preview (#6113)
Merge branch 'main' into develop
feat: thorchain lp fees (#6127)
feat: turn on arbitrum nova production (#6134)
fix: pass tx link instead of tx base url (#6136)

Non blocker:

[ ] fix: force thorchain swapper to wait for outbound tx confirmations on-chain (#6143)--- modal not updating after tx completes

Discord thread: https://discord.com/channels/554694662431178782/1204945189299294250


dashboard/config/linux: run make configs under syz-env

make configs uses host compilers.
This produces constant diffs in the generated configs related to different compiler versions.
Suggest to run make configs under syz-env and check-in configs produced this way.

I would delay this until we really need them for something. By that time it may already be clang 15 :)
We install clang from llvm repos in other docker images, so we could do the same w/o switching to a new Debian.
Not sure about gcc, but I also see fewer reasons to keep gcc very fresh.


Fix failure on missing result files

Added check for existence of result files in buildNetworkPerformanceIndex.
It may happen that release folder exists, but DQD processing wasn't completed, so that dq-result.json wasn't created yet. This led to failure. Now the processing is skipped if required files are missing.

Thanks, this closes #15


 Setting the width to 100% will always scale the svg to fit the whole screen width.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

true, but on small screens width="100%" would make the text unreadable, right?

@pReya thanks for looking into this. I tried out your PR, but it seems like svg has no width... I did another PR which fixes the sizing, by using the figures instead of the svg tag https://github.com/owncloud/ocis/pull/3520

@pReya could you please check https://owncloud.dev again if it works for you now? You also can now use right-click -> open image in new tab. That wasn't possible before

@wkloucek Yes it works very well. Thanks for fixing this.


Strategy doesn't find running blotter

Hello, I'm trying to run simple dumb strategy and getting:
[CRITICAL] qtpylib.broker: Cannot connect to running Blotter [None]
I commented out system exit though after "[ERROR] qtpylib.blotter: Cannot create database schema", as I executed schema.sql manually

resolved already


Is there an escape hatch for the wrapping transaction?

Question: Is it possible to run a step (or await on a job) that is not run inside the "acidic" transaction.
Use case: Let's say we want to fetch a collection of items from an API, process each item, then persist the processed items. The collection feature in AcidicJob can do this, but let's say an additional requirement is that we don't want to persist the collection to a database record.
Let's also assume that processing is expensive, so while we don't mind fetching from the API on retry, we don't want to reprocess items on retry.
One way we could handle this is with an idempotent job that: 1) fetches the collection; 2) checks the db to see which processed items exist; 3) only processes the unprocessed items from the collection (persisting immediately as each item is processed). If there is a failure during the processing iteration, we can retry the job, and it should start from where we left off, but that only works if we are outside of the "acidic" transaction (because otherwise all the persisted processed items are rolled back in the event of an error). Hope this makes sense.
Maybe there is another way of thinking about it within the AcidicJob frame of mind that I'm not seeing?

Nice! Thanks for your response.


Add parent path to know the real path of change

This PR adds the extra field to params, onChange and onAdd to know what property of path has changed.

I wonder what is the progress of this PR

@YYsuni I wonder what is the progress of this PR

https://github.com/YYsuni/react18-json-view/pull/65
0.2.9-canary.9
Sory.🙌


Allow multiple finders to run in parallel

Right now, finders keep a track of their own jobId, which is then set on the nodes.
If you want to alternately use finders on a graph it could generate incorrect paths (or not find them at all) due to skipping some nodes, assuming they were already evaluated.
Node's job should be store per type / category, meaning each node should be able to have more than one jobId at the same time.

solved by [this commit] (https://github.com/xaguzman/pathfinding/commit/acf5187ef672af97de8528a8142f3d79fd20f693)


[Fixes #19] Correctly handle package renaming

Problem: tl;dr—Previously the generation approach was just to ignore all import statements and let goimports generate the correct import block. This mostly worked but broke down in the case of an import being renamed.
Described more thoroughly in #19.
Solution: The naive approach was to just pull out the imports on the first pass then reinsert them in an import ( ... ) block at the top but that fails in the case that imports were done as a series of import "..." statements. This change collects all imports for each pass through the file (meaning duplicates will be found in the case of multiple type assignments) then reconstructs the file before passing to imports.Process.
I added a test for the broken case this change resolves and updated the test where this changes output.

The failing test is unrelated to this PR and was fixed in #22.

Hey @falun , can you please rebase it? We are seeing the same problem and would love this MR to be merged.


Newsletters: add 121 (2020-10-28)

[ ] Update RCs/releases on Tuesday @harding
[x] Add topic entries @harding
[x] Bitcoin StackExchange section @bitschmidty
[x] Bitcoin Core #20198 Show name, format and if uses descriptors in bitcoin-wallet tool @dongcarl
[x] C-Lightning #4046 libplugin: support for sending notifications @moneyball

Pushed edit for @jonatack feedback (thanks!) and removed final FIXMEs.  Contributions by @dongcarl, @bitschmidty, and @moneyball look good to me (thanks!).

Had a quick skim this morning and it looks good to me. Thanks everyone!

@harding @dongcarl @moneyball with the 🖊
@adamjonas @jonatack @jnewbery with the 👍 / 👎
thank you team!