React app compiles with errors if we use absolute imports after adding jsconfig.json

Describe the bug
Created using create react app, compiles with errors if we use absolute imports after adding jsconfig.json
Module not found: Error: Can't resolve '@/components'
{
  "compilerOptions": {
    "baseUrl": "./",
    "paths": {
      "@/src/*": ["src/*"],
      "@/components/*": ["src/components/*"],
    }
  },
  "exclude": ["node_modules"]
}

Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

Environment Info:
current version of create-react-app: 5.0.0
running from /node_modules/create-react-app
System:
OS: Linux 5.13 Ubuntu 20.04.3 LTS (Focal Fossa)
CPU: (4) x64 Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
Binaries:
Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
Yarn: 1.22.17 - ~/.npm-global/bin/yarn
npm: 8.5.3 - ~/.nvm/versions/node/v16.13.2/bin/npm
Browsers:
Chrome: Not Found
Firefox: 96.0
npmPackages:
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
react-scripts: 5.0.0 => 5.0.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

Generate a react app using npx create-react-app my-app
Add jsconfig.json
Create component with some absolute imports.
Run it, error.

Expected behavior

All absolute imports for defined paths must work.
Actual behavior

All absolute imports for defined paths fail/errored.
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

+1 same but in TS


Missing information on the documentation

I had to check the source code to find out that if you pass false to the layout parameter, you can render the template without using the layout. I would suggest to put it on the README.md as well.
Usage Example:
// Not Found (404)
app.use(function(req, res) {
  res.status(404).render('error-404', { layout: false }); // Don't use any layouts for 404 error pages
});

Sounds good to me. Care to open a PR?


remove no longer supported ambassador test code

Changes

🗑  Remove ambassador test code as ambassador is no longer supported

/kind cleanup
/kind removal
/kind deprecation

/cc @maximilien


[docs] additional code examples for 12 rules

PR checklist

[x] Addresses an existing issue: #3601
[x] New feature, bugfix, or enhancement

[ ] Includes tests

[x] Documentation update

Overview of change:
Added code examples to rules:

noAny
noEmptyInterface
noSparseArrays
noUnnecessaryCallbackWrapper
objectLiteralSortKeys
oneVariablePerDeclaration
onlyArrowFunctions
preferTemplate
radix
switchDefault
typedef
useIsnan

CHANGELOG.md entry:
See: "Overview of change"

Thanks for your interest in palantir/tslint, @Shinigami92! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

@palantitrech Sorry, but currently I am not allowed to sign the CLA.
I want to and will do this in the next few days / weeks.
Currently, the organization I work for joins an OSB alliance and I have to wait :/

@Shinigami92 is the CLA signed? would love to merge this!

@suchanlee sorry but I want this too and also work on tslint
But I have to wait at my business :(
My chef said that it is in final stage and i'm hoping and praying that it's next week
This week i'm in holiday

ah okay sounds good, just let us know!

Finally I could accept the CLA

AFAICT everything is now ready for review and merge.
Shall I change the dates in each src/rules/code-examples/* on line 3 or are they good as is?

Hi! Sorry that this has been left for a while. Please update the dates of the copyrights, and then we can merge this in.

I think in src/rules/classNameRule.ts an import line was added
that caused the conflict

@johnwiseheart anything needed before review?

Looks good to me. Can you confirm whether you have signed the CLA? The cla bot seems to be a little funky right now.

yes I have

Sweet, let me look into why its not reporting properly and I'll merge it in once it passes.

yay it passed

Thanks for your contribution!

I will look into some more code examples in the next few days
and then do this in a new pr


copy --background-op stuck in "Scanning..."

Which version of the AzCopy was used?
Note: The version is visible when running AzCopy without any argument
azcopy version 10.0.8-Preview
Which platform are you using? (ex: Windows, Mac, Linux)
Windows 2016 Server
Windows 10
What command did you run?
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
AzCopy.exe cp "$srcPath" "$targetPath" --overwrite --background-op
What problem was encountered?
The downloaded test file is about 1.5MB in size. Stdout would be stuck with the message "Scanning..." and never recover control until the script is manually stopped. Note that download is actually performed in the background.
How can we reproduce the problem in the simplest way?

Create a blob storage container
Create a test file in the container
On a computer, create a script to download the test file including --background-op=true in the copy syntax
run the script from powershell/powershell ISE

Have you found a mitigation/solution?
Removing the --background-op=true bit from the script restores full functionality. Interrupting the script recovers immediate response from the console.

Hi @gmassari-88, thank you for reaching out!
I apologize for the inconvenience. It looks like I mistakenly revealed the background-op flag which is not supported anymore. I'll fix it right away, thank you for bringing this to our attention!

Fixed in 10.0.9.


Param Editor and Specimen Cards do not deal well with overflow

To reproduce: Select an OEIS sequence, and make the modulus have 30 digits or so. Then open the sequence switcher. The text for the card representing the current sequence runs off the card and overlaps the text of the neighboring card. It's a bit better in the Param Editor -- it is just cut off at the edge of the card, but it does still overlap the scroll bar. These need to be laid out better.
This was Bug (2) in #510.

If you want to be able to see an entire very long number (and I think you do), it will need to split lines. Reading a bit on the 'net, it seems the typical way to split lines is like so:
My very long book had nearly 10,123,
456,789,876 pages.

i.e. to use thousands separators and then split right after one. But I don't know that it would look right to include commas in the descriptions of a sequence, like
This is some OEIS sequence. (mod 20,000,000,
000,000,000,000,000)

Would it be better to use spaces (or maybe thin spaces), like
This is some OEIS sequence (mod 20 000 000
000 000 000 000 000 000)

? Or some other suggestion about how to linebreak long numbers?


NaN values in images

Adding changes to allow nan calculations (i.e. nanmean, nanmin, nanmax)

Is there any chance we can get this merged in?


Fix missing switch text

Switch text is hidden by default, so I added the showText="true" attribute which fixes the issue.
And, I took the opportunity to consolidate the style being used in 3 places.
(Fixes an issue from https://openedx.atlassian.net/browse/MA-1002)

@miankhalid Please review?

Great work with the consolidation :star2: lets standardise the styles as well :+1:

Updated to address all comments. Also removed the ripple background which doesn't really fit our design.


CRUD update pattern is broken with fastapi 0.61

The first line of the CRUDBase update method is:
obj_data = jsonable_encoder(db_obj)
This now stack overflows when using fastapi 0.61. We need an updated base CRUD pattern in this project, along with updating the various dependencies. I'll additionally be filing an issue to the fastapi project itself with the need for CRUD update examples.
From what I've figured out so far, we may need a reference to the ModelInDB or Model pydantic models, and then:
obj_data = ModelInDB.from_orm(db_obj)
and change the iteration to:
for field in obj_data.dict():

I fixed this issue by adding as_dict() to base_class.py in db:
@as_declarative()
class Base:
    id: Any
    __name__: str

    # Generate __tablename__ automatically
    @declared_attr
    def __tablename__(cls) -> str:
        return cls.__name__.lower()

    def as_dict(self) -> dict:
        return {c.key: getattr(self, c.key) for c in inspect(self).mapper.column_attrs}

Then adding as_dict() to the db_obj in update in base.py in crud:
obj_data = jsonable_encoder(db_obj.as_dict())

Quick fix for this is in backend > app > app > crud > crud_user.py replace the line
if update_data["password"]:

with
if update_data.get("password", False):

until this has been fixed in a future release.


Adding a loading gif using Wookmark before images was loaded

How can I add a loader before images was loaded? Is there callbacks like start/end?

Hi,
the imagesLoaded plugin supports events.
You can see an example in the example-load-images.

Hi,
To achieve this you can include a div element that contains the loading gif. After the images have loaded I hide this div.
imagesLoaded('#container', function () {
jQuery('#loadingDiv').hide();
.....


division by zero error

Hi,
in the query shown in the article:
SELECT relname, n_dead_tup, n_live_tup, (n_dead_tup/ n_live_tup) AS DeadTuplesRatio, last_vacuum, last_autovacuum FROM pg_catalog.pg_stat_all_tables WHERE relname = 'XYZ' order by n_dead_tup DESC;
there is no protection against division by zero, so if live tuples will be zero it will throw an error
[Enter feedback here]

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

ID: a1103bde-c05b-23f9-93bd-b1350c3abb0f
Version Independent ID: 11cae63b-7bd5-e3be-602f-cd4fba8871e0
Content: Optimize autovacuum - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/howto-optimize-autovacuum.md
Service: postgresql
GitHub Login: @DianaPutnam
Microsoft Alias: dianas

@AwdotiaRomanowna Thank you for the feedback. We are actively investigating and will get back to you soon.

@AwdotiaRomanowna This is being assigned to the content author to evaluate and update as appropriate.

We sincerely apologize for the delayed response to this issue. I collaborate with the owners of the GitHub Issues related to PostgreSQL/MySQL/MariaDB to help either get them resolved or determine how to update our documentation.
Due to the age of this issue, we will continue to close this issue.
Please visit https://docs.microsoft.com/en-us/answers/support/ for more information on asking questions about the product or service.
Thank you.

#please-close


bit.io support

While using bit.io
Getting this error
pq: inet_client_addr is not supported

I havent used bit.io so dont know much about how its configured. Could you provide some context on what you're doing and how you're connecting to their endpoints?

I am able to connect through psql this using url scheme
<EMAIL_ADDRESS>
the databasename contains a slash
databasename=abcd/efgh

Not sure what the problem is then. Im going to close unless you have anything else to share

@anaschaudhary33 try url encoding the database name

@anaschaudhary33 try url encoding the database name

Tried url encoding database%2Fname but getting same error


Listener widget used in package doesn't work only on iPhone X and earlier iPhones

I used package of "gesture_x_detector".
https://pub.dev/packages/gesture_x_detector
But I discovered that its callback of onTap in the package doesn't work only on iPhone X and earlier iPhones.
Upon investigating, I found that it was created by the Listener widget.
https://github.com/taodo2291/xgesture_flutter/blob/c9dfedfcee294a5281fed55e8b7523b65ced4f98/lib/gesture_x_detector.dart#L119
For further investigation, I put "gesture_x_detector" as a local file in my project.
Just doing so, onTap worked on the iPhones.
In other words, just doing so, Listener widget works on the iPhones.
I would like you to teach me about the cause.
Also, the solution when using "gesture_x_detector" only as package.

For reference, followings is the repository created in the investigate.

I used "gesture_x_detector" as package (Doesn't Work only on iPhone X and earlier iPhones.)
https://github.com/taku-kw/x_gesture/tree/main
I used "gesture_x_detector" as local file (Works including iPhone X and earlier iPhones.)
https://github.com/taku-kw/x_gesture/tree/x-gesture

@taku-kw
Can you provide a minimal complete code sample without the said package, that shows the behavior ?

@darshankawar

Can you provide a minimal complete code sample without the said package, that shows the behavior ?

Here you are.
https://github.com/taku-kw/x_gesture/tree/x-gesture

@taku-kw
What's the expected result you are looking for upon running the code ?

@darshankawar

What's the expected result you are looking for upon running the code ?
I expect that when I tap on display, tapped position change color of red.

Is it only happening on iphone X and earlier simulators or on devices too ?
I confirmed only simulators, didn't device.

@taku-kw
I verified on iOS simulator (12 Pro max) and observed that sometimes it recognizes the tap on single tap and sometimes on double tap, ie, you have to double tap to see the red dot. Have you notices this already ?

@darshankawar
Yes, I recognize that is also a problem.
However, I haven't been able to investigate whether it is caused by the Listener widget.

@taku-kw
I do see the same behavior upon running your code sample on iPhone 8 and 8 plus simulators, wherein, tapping or double tapping isn't recognized, but the same action is being recognized on iPhone 12 Prox max simulator.
I guess you are hitting this, but exactly not similar case, but opposite of what's mentioned in the linked issue. Can you try this solution and see if it helps ?

@darshankawar
As written there, I added SafeArea widget and tried.
https://github.com/taku-kw/x_gesture/tree/add_SafeArea
But unfortunately I confirmed that it doesn't work on iPhone 8 by simulator.

@taku-kw
Can you try by framework's core GestureDetector instead of XGestureDetector from the package and see if it gives you same behavior ?

@darshankawar
I created a branch that use GestureDetector instead of XGestureDetector.
https://github.com/taku-kw/x_gesture/tree/GestureDetector_instead
As a result, I confirmed that it works expectedly on iPhone 8 by simulator.
(I used onTapUp in GestureDetector to get tapped position.)

Thanks for verifying. Is it now safe to close as resolved ?, because the issue doesn't seem to occur using core framework widget, but using the third party plugin.

@darshankawar
I'd like to have known cause that  the behavior of Listener widget is different between the package and the local file,
but it's okay to close.

Closing based on above comment and unable to replicate using GestureDetector.


Is there a solved method of synchronizing zooming while panning between two instances of viewports?

(I'm not sure how to add the question label, but this is a question about functionality rather than an issue)
I'm attempting to create dynamic OpenSeadragon Instances that are opened and closed, each with their own individual viewports and viewers. However, I'm now trying to link them together so that any movement on one is reflected on the other. There's a big problem with this, though. The images are not a standard size, and need to be locked together from different viewport/zoom locations. Therefore, I can't just use zoomTo and panTo with hard values that are self-correcting, I need to use dynamic delta based values for zoomBy and panBy
If I capture pan events, and just rebroadcast a new panBy with the difference between the last viewport target and the current viewport target, I can easily synchronize panning between them. The same goes for zooming. However, there's a major issue when panning while zooming, and that's what I'm trying to solve.
If you try to pan while zooming, the rebroadcast zoom event will cycle through almost invariably at a different rate than the zoom event from the original viewport. Therefore, when the pan event occurs, the two viewports are at different stages of the zoom, so the image either moves farther or less far than it should in a true synchronization.
The current solution that I'm working on for this, after wracking my brain and trying several failed ideas (such as converting to dx dy image coordinates, then reconverting those dx dy image coordinates back to viewport coordinates using the other viewer's viewport conversion, but this doesn't actually fix the discrepancy with zoom because these conversions still happen from asynchronous zoom levels with viewports) is to calculate image distance vectors based on the first pan event's target position in image pixel coordinates in each synchronized viewport system and the new target position points (both done as delta from the initial point rather than hard coordinates), then subtracting the normalized vectors to get the delta target image coordinate vector between them at each point that a pan event fires. That vector is converted to viewport coordinates and fed into a panBy.
However, in doing this, even though it solves my major problem of the different zoom levels not resulting in the real expected viewport dx dy shift at any given firing of the pan event, I no longer allow simple viewport level synchronized movement between different sized images. If I have a high resolution triangle and a low resolution triangle, the low resolution triangle will jet off of the screen with a flicker of movement of the high resolution triangle that's synchronized with it. So, while that fixes the big problem, it has an unsavory side effect of requiring everything to be the exact same size in order to be able to be linked. A viewport coordinate based solution would let me keep them interacting in a more expected manner.
Is there a known way to solve this discrepancy between viewport pans during zooms that, due to zoom animation asynchronicity even on images of the same size, end up with different real movements of the viewports?

Are these images different sizes but the same aspect ratio? That's no problem... You just need to align their viewport coordinates. If image A is 400x300 and image B is 4000x3000, they can still both be presented with viewport coordinates of 4x3 or whatever.
If they are different aspect ratios, (e.g. 4x3 vs. 3x4) that gets more challenging... you basically need to decide which part of the image to align.
At any rate, here's our basic synchronous viewer example:
https://codepen.io/iangilman/pen/BpwBJe
Let me know if that helps, or if there are specific cases that it doesn't cover, or if you need help aligning your viewport coordinates as mentioned above.


Allow compilation with xcode 13 and 12

Currently SwiftyCam will not compile when using xcode 13 due to the return type of cgImageRepresentation changing in iOS15, reference https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-15-release-notes
Fixes the issue reported here: https://github.com/nstudio/nativescript-camera-plus/issues/166

You’re the best @Logikgate i was just looking at this earlier today - looks perfect thank you!


Android devices should have system animations disabled

What App Center service does this affect?
Espresso Test runs
Describe the bug
Device animations are not disabled
To Reproduce
Steps to reproduce the behavior:
Run espresso tests
Expected behavior
Tests that pass locally should pass on App Center
Additional context
As per Espresso setup instructions all device system animations should be disabled. App Center support has confirmed that they are not disabled on App Center. We believe this is the cause of our test flakiness when running on App Center and this renders App Center UI testing useless to us. Please disable system animations on Android devices.

Can I ask you to reach out to our support in App Center, it's the blue chat icon the right corner?

Thanks for reporting it, I have converted it to feature request. Were you able to get any help from our support?

Support basically just said "Sorry, we currently don't support disabling animations".

Same issue, about 20 tests are failing because of this, I also believe that this slowdown test execution

Is there a place where I can track the feature internally? Was it evaluated?

Hello everybody,
We're actively looking into options here.
Sorry for the slow response.

Hey guys.
@Oddj0b have you any news?
I tried to add this option in build.gradle, but no success.
testOptions {
    animationsDisabled = true
}

@douglascarvalho Does that work for all devices?
In the meanwhile, we're running an experiment where we have disabled animations on Motorola Nexus 6 running Android 5.0.1.

@Oddj0b I believe so, we tested on a Pixel 2 device. I think it is more related to Gradle version than device setup to work. It should work on Gradle 3.0+>

Has anyone else had success with this? My appcenter device is still enabling animations with
testOptions {
    animationsDisabled = true
}

and gradle v3.5.3
Currently using a Nexus 5x, android 8.1.0

@rfogar2 Thank you for the feedback, we'll check the devices settings.

@rfogar2 The Nexus 5x running Android 8.1.0 have had their animation disabled. This is until we get a broader solution implemented that disables animation on Android devices.

@Oddj0b do you have a timeline for that? We are moving our tests to appcenter from Firebase and this is causing some tests to fail.
Thanks

@Oddj0b  same here. UI tests with espresso are usually not robust at all if animations are turned on. Espresso usually delays searching for UI elements until the application is in some sort of idle state. Unlike other UI testing frameworks which mostly provide some sort of waitForElementX functionality. System animations seem to confuse espresso in determining this idle state.

@Oddj0b It doesn't seem like animations were disabled for the Nexus 5x on Android 8.1.0. I'm still having the same issues as before.

Hey guys, still facing same problem here. Do we have any updates?
I think I will move to another device farm. My code has a lot of animations and it has no sense to test on devices that cannot disable their animations. All my tests fails at AppCenter device farm.

@Oddj0b  any update about this feature request?

We use this custom test rule to disable animations on App Center:
class AnimationsRule : TestRule {

    private companion object {
        const val PREFIX = "settings put global"
        const val TRANSITION_ANIMATION = "transition_animation_scale"
        const val WINDOW_ANIMATION = "window_animation_scale"
        const val ANIMATOR_DURATION = "animator_duration_scale"
    }

    private val animations = listOf(TRANSITION_ANIMATION, WINDOW_ANIMATION, ANIMATOR_DURATION)

    override fun apply(base: Statement, description: Description) =
            object : Statement() {
                override fun evaluate() {
                    disableAnimations()
                    try {
                        base.evaluate()
                    } finally {
                        enableAnimations()
                    }
                }
            }

    private fun disableAnimations() = animations.forEach {
        val command = "$PREFIX $it 0"
        UiDevice.getInstance(InstrumentationRegistry.getInstrumentation())
                .executeShellCommand(command)
    }

    private fun enableAnimations() = animations.forEach {
        val command = "$PREFIX $it 1"
        UiDevice.getInstance(InstrumentationRegistry.getInstrumentation())
                .executeShellCommand(command)
    }
}

System Animations are disabled on Android devices now.
Closed.

Thanks for the speedy resolution.

@peter-iglaev because of the disabled animations we started getting crashes on our Xamarin UI Tests when using Lottie animations in our app, is there anyway to force enable animations ?
thank you in advance

@Sergiu-Cosmin hello.
We are working on the feature to add customers' opportunities to enable system animations.
Follow the current issue for updates.

@Sergiu-Cosmin hello.
We are working on the feature to add customers' opportunities to enable system animations.
Follow the current issue for updates.

Push

@peter-iglaev any news on this ?

it's already September, is anyone still working on this ?


Getting Started doc should tie in better with the examples scenes

I hadn't read getting started for a while so I just went through it and found it curious that it got me to a point that differed considerably from 001_CameraRig_VRPlayArea
Ideally "Getting Started" should take the user down the same road and use the same conventions as the demo scene - or another doc should go through the simplest demo scene piece by piece, explaining the structure.

The example scenes are examples, not documentation, therefore they differ (for example in the number of added SDK Setups, we are very careful with not including the SDKSetups prefab in the "core" of VRTK, they are in the example folder for a reason).

I'm not sure I follow.
I'm thinking about how best to bridge the gap between "Getting started" and understanding how to construct a fully working VRTK scene. The way I've learned is via examining the examples. The main docs are useful afterwards but they are too high level to provide much help to someone who's just come to VRTK.
If my experience is common then the examples are the most realistic way currently to learn how to use VRTK.

Let's reduce the confusion. 😄
The Getting Started document is explaining how to set up the SDK Setups. The resulting scene differs from the included first example scene because all the example scenes are set up to allow using any of SDKs VRTK supports.
To update the Getting Started document to explain how to list all of the SDK Setups would be a waste: People should only have the SDK Setups in their scene for which they also import the needed vendor SDKs for, otherwise Unity will tons of script not found warnings whenever the scene is run.
The only other difference is probably the names of the game objects, but the Getting Started document doesn't give names at all. We previously had multiple instances of people thinking there were some kind of name lookups going on there, so it's good to make sure people understand VRTK doesn't care what you're naming your things like, nor does it care for a specific hierarchy of game objects (except for the SDK Setups with respective camera rig, which the Getting Started document states).

Excellent. Everything you just said should be in Getting Started ;-)
More seriously - a few things in response:

I agree about the SDK setups. Leave them out
The confusion around naming is easily solved by phrasing it as a suggestion not as a requirement
There are other differences too - I'm currently picking through to understand what matters and what doesn't. I'll update here or do a documentation PR when I've got something more constructive to add.

Gonna close this and roll it into this new issue:
https://github.com/thestonefox/VRTK/issues/1422


Fix FixedPointNumber: zero is not positive.

is_positive fn of FixedPointNumber returns true for zero value. It's against the usual positive definition in math, and not consistent with the API in Rust std lib.
This PR includes:

is_positive fix.
Updated docstring of is_positive and is_negative to be the same with rust std lib(which I think is a bit more accurate).
Added a unit test for is_positive and is_negative fn.

The CI failure is the same with the one in latest master branch commit, not related to this PR.
https://gitlab.parity.io/parity/substrate/-/jobs/558297
https://gitlab.parity.io/parity/substrate/-/jobs/557655


update chmod user permissions.

update chmod user permissions.

Why are these changes needed?

Related issue number

Checks

[ ] I'm working against the latest source on the experimental branch.
[ ] I've run scripts/format.sh to lint the changes in this PR.
[ ] I've included any doc changes needed.
[ ] I've made sure the tests are passing. Note that there might be a few flaky tests.
Testing Strategy

[ ] Unit tests
[ ] Release tests
[ ] This PR is not tested :(

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

closing, mistake. change not needed.


ValueError: empty range for randrange()

Hi,
I've tried long but I can't get the script running. I am now getting below error. Could you help me further with this? Thanks in advance!
pi@raspi:~/gekkoJaponicus $ python3 japonicus.py -g
Traceback (most recent call last):
File "japonicus.py", line 66, in
gekko_generations(settings_, GenerationMethod)
File "/home/pi/gekkoJaponicus/evolution_generations.py", line 34, in gekko_generations
World = promoterz.world.World(GlobalTools, loops, genconf, TargetParameters, NB_LOCALE, EnvironmentParameters=availableDataRange)
File "/home/pi/gekkoJaponicus/promoterz/world.py", line 24, in init
self.generateLocale()
File "/home/pi/gekkoJaponicus/promoterz/world.py", line 34, in generateLocale
L = promoterz.locale.Locale(self, name, position, random.choice(self.loops))
File "/home/pi/gekkoJaponicus/promoterz/locale.py", line 38, in init
World.EnvironmentParameters, World.genconf.deltaDays)
File "/home/pi/gekkoJaponicus/promoterz/evaluation/gekko.py", line 259, in getRandomDateRange
Starting= random.randint(FLms,TLms-deltams-testms)
File "/usr/lib/python3.5/random.py", line 227, in randint
return self.randrange(a, b+1)
File "/usr/lib/python3.5/random.py", line 205, in randrange
raise ValueError("empty range for randrange() (%d,%d, %d)" % (istart, istop, width))
ValueError: empty range for randrange()<PHONE_NUMBER>,1500657061, -5219)

Hey @jwijmans, it seems you got no available candlestick dataset available for backtesting, or timespan of your CS sets is too narrow...
If this is true, run $node gekko --import to get your gekko loaded.
If not, let me know
Thanks.


WIP Extended documentation regarding INFORMATION_SCHEMA.COLUMNS

Codecov Report

Merging #5623 into sql99-information-schema will decrease coverage by 0.12%.
The diff coverage is n/a.

@@                      Coverage Diff                       @@
##             sql99-information-schema    #5623      +/-   ##
==============================================================
- Coverage                       82.87%   82.75%   -0.13%
+ Complexity                      11806    11784      -22
==============================================================
  Files                            1392     1392
  Lines                           45323    45323
  Branches                         5626     5626
==============================================================
- Hits                            37562    37507      -55
- Misses                           5154     5200      +46
- Partials                         2607     2616       +9

Impacted Files
Coverage Δ
Complexity Δ

...r/transport/executionphases/SetBucketCallback.java
66.66% <0%> (-33.34%)
2% <0%> (-1%)

...exceptions/GroupByOnArrayUnsupportedException.java
66.66% <0%> (-33.34%)
1% <0%> (-1%)

...in/java/io/crate/lucene/match/CrateRegexQuery.java
43.47% <0%> (-30.44%)
4% <0%> (-4%)

...a/io/crate/exceptions/ContextMissingException.java
81.81% <0%> (-18.19%)
1% <0%> (-1%)

...o/crate/analyze/SafeExpressionToStringVisitor.java
83.33% <0%> (-16.67%)
7% <0%> (-1%)

.../distributed/TransportDistributedResultAction.java
66.15% <0%> (-15.39%)
8% <0%> (-1%)

...in/java/io/crate/data/CollectingBatchConsumer.java
69.23% <0%> (-15.39%)
4% <0%> (-1%)

...a/io/crate/operation/join/NestedLoopOperation.java
82.85% <0%> (-11.43%)
14% <0%> (-1%)

...ration/collect/collectors/OrderedDocCollector.java
90% <0%> (-10%)
5% <0%> (-1%)

...rc/main/java/io/crate/analyze/UnboundAnalyzer.java
85% <0%> (-10%)
2% <0%> (ø)

... and 28 more

Continue to review full report at Codecov.

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


Terminal tab still black if started from the terminal (bash)

I found a temporary fix,
Is to start Atom from the app launcher, then i can get the terminal tab working

Thanks in advance, cheers,
F0x

Still relevant ?


Return 500 error by cURL

Hi @ije. First of all, thank you so much. We are developing with esm.sh because it is very useful.
Now, we tried using esm.sh by curl. However, the response is 500 error:
❯ curl -I<EMAIL_ADDRESS>
HTTP/2 500
date: Wed, 04 Jan 2023 14:31:13 GMT
content-type: text/html; charset=UTF-8
x-frame-options: SAMEORIGIN
referrer-policy: same-origin
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
cf-ray: 7844ad33be79df5c-NRT
server: cloudflare

But, when target query or User-Agent header is added, the response returns 200 status:
❯ curl -I 'https://esm.sh/svelte@3.53.1?target=esnext'

HTTP/2 200
date: Wed, 04 Jan 2023 14:31:46 GMT
content-type: application/javascript; charset=utf-8
content-length: 97
cf-ray: 7844adfeeb92af2b-NRT
cache-control: public, max-age=86400
vary: Origin
cf-cache-status: DYNAMIC
x-typescript-types<EMAIL_ADDRESS>report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=HMCXn3lE4GGmvCWNUK5tONV2aa7H04rom4qQYqktyhLTSjnT7mv3WYttPYmcNmq2nfVbsgfbu4h5v86lqOY0HpAM675ycyG7E%2FZqbyAkZm43dOKepMViqyM%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

❯ curl -I<EMAIL_ADDRESS>\
-H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36'

HTTP/2 200
date: Wed, 04 Jan 2023 14:31:06 GMT
content-type: application/javascript; charset=utf-8
content-length: 97
cf-ray: 7844ad0a084cafe5-NRT
accept-ranges: bytes
age: 14
cache-control: public, max-age=86400
last-modified: Wed, 04 Jan 2023 14:30:52 GMT
vary: Origin, User-Agent
cf-cache-status: HIT
x-typescript-types<EMAIL_ADDRESS>report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=XxwHXDS8Z%2BcmFNS3TZsvPrhloISqm5UbkFN9N3sSEBQv%2FY5N1H9dbs5C%2BLlle7jSrEEHdrnckCWwmJcdHq6QO%2BxWVpyNdQFh0V6OxcffaXeIfT4tq%2BcR9NE%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

I’d recommend that esm.sh does not return 500 error. Could you check the happening?

I'm encountering a similar issue.

fixed the user-agent checking


Remove VSCode (User) Settings

All of them ( the forced files by ! notation ) are user-settings and should not be a part of a repository.
### VisualStudioCode ###
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json

Please submit your changes to this template to GitHub and we'll sync them down once they are approved.
https://github.com/github/gitignore/blob/master/Global/VisualStudioCode.gitignore
Thanks.


Jenkins remove dry run

Description
This is on top of #1233, so only review the last commit.
I was trying to use the Build_Jenkinsfile job that includes a bunch of dryRun: true to test incremental build and gave up. It's a faster build, but it's confusing because we constantly have to fake input and output. Instead, I ended up creating a real build job that doesn't have notifications or cron settings, and run that in Jenkins. That also seems to be what everybody else is doing or trying to do.
Unit tests already do a good job covering actual execution, too.
This removes dryRun altogether.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1236 (5e70250) into main (67381d3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #1236   +/-   ##
=========================================
  Coverage     93.26%   93.26%
  Complexity       11       11
=========================================
  Files           116      116
  Lines          2761     2761
  Branches         10       10
=========================================
  Hits           2575     2575
  Misses          176      176
  Partials         10       10

Impacted Files
Coverage Δ

...sts/jenkins/jobs/ArchiveAssembleUpload_Jenkinsfile
100.00% <ø> (ø)

tests/jenkins/jobs/BuildAssembleUpload_Jenkinsfile
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Add the ability to create custom metrics in an Ansible Operator

Feature Request
Describe the problem you need a feature to resolve.
When running an Ansible Operator, there is no easy way to provide metrics based on the operation of the operator. Operator SDK provides various metrics, but there is no ability to create custom metrics.
Describe the solution you'd like.
I would like to have an Ansible module/task that provides some syntactic sugar for the creation and updating of custom metrics.
There were a couple of implementation approaches proposed by @fabianvf . I'm  quoting him below to capture the ideas.
From a discussion I had with @joelanford and @fabianvf in Slack.

a generic metrics server that allows posting of metrics could be pretty useful, and integration from Ansible definitely wouldn't be hard. For the Ansible-based Operators we can also pass information back to the Golang process as it is watching the Ansible event stream, so we could also do something like create a dummy metrics module that doesn't do anything but accept/validate metrics information, and intercept the event from the Golang binary to handle the updates. The generic server seems cleaner and more useful though, just mentioning that as another possibility

< /language ansible >

This was done in https://github.com/operator-framework/operator-sdk-ansible-util/pull/40
To be used with operator_sdk.util.osdk_metric


secondary_y plot shows in separate figure

Hi, don't know if this is my Python/some module version.. but when I try to do the following, I end up with two figures popping up, instead of the expected one:
df[[0, 1]].plot(kind='bar', stacked=True, ylim=(0, 100))
df[[2]].plot(secondary_y=True, color='orange', linewidth=2.0)

The data in both plots looks right, the left/right y axes are correct etc.. but they're not on the same figure :(
Also if this is of any help, if I do fig = plt.figure() before running the commands above, I end up with another completely empty figure shown to me first..

Hmm, it works if I do fig, ax = plt.subplots(1, 1) and then add ax=ax to both df.plot() calls above.. Might be worth documenting?
However, there are two bugs now:

the secondary legend is on top of the first one
the plot width is scaled down to the line points, i.e. the first and last bars are cut off by 50%

Erm, executing the secondary_y line plot command first and the bar plot second solves issue 2. Now the plot has enough space for the bars.

Another possibility is doing ax = df[[0,1]].plot(...) and then providing this ax to the second df[[2]].plot(..), or by doing df[2].plot(..) (this is then plotting a series -> added to the existing figure). But, I think your solution of fig, ax = plt.subplots(1, 1) is the cleanest and clearest one.
Providing the ax is documented (see the docstring and http://pandas.pydata.org/pandas-docs/stable/visualization.html), but maybe not explicitly enough (see also #8776). If you have any suggestions on how to improve it, certainly welcome!
For the other questions, can you provide a small reproducible example? (some runnable code with some dummy data that shows the issue)

Hmm, the two options you mention work indeed, though somehow I'm now missing the first plot's y axis ticks/labels and the second plot's legend altogether.. Here's the snippet with the shortened version (I was doing df[2] before and it didn't work because my columns had titles, but otherwise that way works indeed, like the doc says!)
from pandas import DataFrame
import matplotlib.pyplot as plt

points = [[50.69922925478467, 23.857641645143786, 2247], [51.11691211658459, 23.30982697233231, 80], [55.37656430470213, 23.25234081849125, 12]]
keys = ['one', 'two', 'three']
df = DataFrame(points, index=keys, columns=['OK', 'OK too', 'Where am I'])

df[[0, 1]].plot(
    kind='bar',
    stacked=True,
    ylim=(0, 100),
)
df['Where am I'].plot(
    color='orange',
    linewidth=2.0,
    mark_right=False,
    secondary_y=True,
)
plt.show()

On the other hand, using the following makes the second plot's legend overlap:
from pandas import DataFrame
import matplotlib.pyplot as plt

points = [[50.69922925478467, 23.857641645143786, 2247], [51.11691211658459, 23.30982697233231, 80], [55.37656430470213, 23.25234081849125, 12]]
keys = ['one', 'two', 'three']
df = DataFrame(points, index=keys, columns=['Cant see this', 'This OK', 'Move me please'])

fig, ax = plt.subplots(1, 1)
fig = df[[0, 1]].plot(
    kind='bar',
    stacked=True,
    ylim=(0, 100),
    ax=ax
)
fig2 = df[[2]].plot(
    color='orange',
    linewidth=2.0,
    mark_right=False,
    ax=ax,
    secondary_y=True,
)
plt.show()

PS. This issue has now gone almost completely off-topic.. but still some issues I think :)

On first one, you should pass legend=True explicitly because it is disabled for Series by default. Then you will get the same result as latter one (overlapped legend).
The overlapped legend seems to be caused by a bug which is the same as #9610. Expected to be fixed by #9812 as below:

@arski should be fixed now if you're comfortable running off master. Thanks for the report.

Maybe make a separate issue for that bug, if we don't have one already. You can work around it with the ax.get_xlim() methos.

@arski Because xlim is adjusted by last plot kind, another option is draw fig2 first, then fig. Note that it should affect to legend order.
fig, ax = plt.subplots(1, 1)
fig2 = df[[2]].plot(
    color='orange',
    linewidth=2.0,
    mark_right=False,
    ax=ax,
    secondary_y=True,
)
fig = df[[0, 1]].plot(
    kind='bar',
    stacked=True,
    ylim=(0, 100),
    ax=ax
)

ah, fair enough I guess, if only the legend order could be adjusted ;)


updating the chef client to incorporate semantic changes

Description

Related Issue

Types of changes

[ ] 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)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

@johnmccrae Can you sign off this commit with the DCO so we can accept it? Also can you tell us why this change is being made in the PR description?
@stuartpreston @mwrock care to take a peak at this?

This looks mostly to be PSScriptAnalyser reccomendations for changes, e.g. using verbs from the Approved Verb List, adjusting the fallthrough from if { } statements across the module and fixing the spacing in line with typical PS standards (though these are not strictly necessary), am I right @johnmccrae? Have we done a sweep across the codebase to ensure we don't call into these functions as an entrypoint from any other modules (e.g. in Chef Workstation?).
Also needs DCO signoff to proceed.

Stuart, yes. That's pretty much it. I figured if we're going to publish modules, we should be following the standards.

@johnmccrae I'm with Stuart on this. Make sure we're not using any of the old method calls anywhere and then we can merge this.

Ping @johnmccrae can this get updated please?

@johnmccrae We haven't heard back from you so I'm going to close this out now. Feel free to open this up with the suggestions I left earlier.


Cannot compile on windows (nightly channel)

This is the output:
$ cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling gcc v0.3.8
   Compiling libc v0.1.8
   Compiling time v0.1.26 (file:///C:/Users/Nicolas/dev/time)
failed to run custom build command for `time v0.1.26 (file:///C:/Users/Nicolas/d
ev/time)`
Process didn't exit successfully: `c:\Users\Nicolas\dev\time\target\debug\build\
time-73371842c1eccfc4\build-script-build` (exit code: 101)
--- stdout
TARGET = Some("x86_64-pc-windows-gnu")
TARGET = Some("x86_64-pc-windows-gnu")
CARGO_MANIFEST_DIR = Some("c:\\Users\\Nicolas\\dev\\time")
OUT_DIR = Some("c:\\Users\\Nicolas\\dev\\time\\target\\debug\\build\\time-733718
42c1eccfc4\\out")
OPT_LEVEL = Some("0")
PROFILE = Some("debug")
debug 0
TARGET = Some("x86_64-pc-windows-gnu")
HOST = Some("x86_64-pc-windows-gnu")
CC_x86_64-pc-windows-gnu = None
CC_x86_64_pc_windows_gnu = None
HOST_CC = None
CC = None
TARGET = Some("x86_64-pc-windows-gnu")
HOST = Some("x86_64-pc-windows-gnu")
CFLAGS_x86_64-pc-windows-gnu = None
CFLAGS_x86_64_pc_windows_gnu = None
HOST_CFLAGS = None
CFLAGS = None
TARGET = Some("x86_64-pc-windows-gnu")
HOST = Some("x86_64-pc-windows-gnu")
CC_x86_64-pc-windows-gnu = None
CC_x86_64_pc_windows_gnu = None
HOST_CC = None
CC = None
running: "gcc" "-O0" "-c" "-ffunction-sections" "-fdata-sections" "-mwin32" "-m6
4" "-fPIC" "c:\Users\Nicolas\dev\time\src/time_helpers.c" "-o" "c:\Users\Nicolas
\dev\time\target\debug\build\time-73371842c1eccfc4\out\src\time_helpers.o"

command did not execute successfully, got: exit code: 1

--- stderr
gcc: error: CreateProcess: No such file or directory
thread '<main>' panicked at 'explicit panic', c:/Users/Nicolas\.cargo\registry\s
rc\github.com-0a35038f75765ae4\gcc-0.3.8\src\lib.rs:497

Thanks for the report! Currently this repository needs MinGW installed to build as it has some native C code, so you'll need to make sure that's installed locally. The issue for removing this dependency is tracked in https://github.com/rust-lang/time/issues/78, so I'm going to close this in favor of that.


SXP loader

PR for drafting an SXP loader

This should more or less work now, needs to be tested with a full run. For test data upload, I am waiting for David's approval.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

239 of 333 (71.77%)  changed or added relevant lines in 5 files are covered.
83 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.4%) to 88.98%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tests/loader/test_loaders.py
22
26
84.62%

sed/loader/utils.py
16
21
76.19%

sed/loader/sxp/metadata.py
11
40
27.5%

sed/loader/sxp/loader.py
189
245
77.14%

Files with Coverage Reduction
New Missed Lines
%

sed/calibrator/delay.py
19
86.52%

sed/core/processor.py
64
83.88%

Totals

Change from base Build<PHONE_NUMBER>:
-1.4%

Covered Lines:
5216

Relevant Lines:
5862

💛  - Coveralls

This works for now. It has only a few modifications to the flash loader, but probably too many to become a single loader.
The metadata stuff is untouched as of now, this needs to be updated once it's known how it works. Also, the additions from the flash consistency check can be ported once completed, but this I would do in separate PRs.

Generally I have seen the git blame so I got the idea where you made changes. Is this going to be a permenant loader or it's just for your beamtime? Because adapting flash loaders structure makes this confusing and likely unmaintainable. We should later definitely think of a solution to this.

Well, In gerneral the requirements for FLASH and SXP are very similar, i.e. the train /micro/macrobunch structure etc., so it does not make sense to me to deviate too much from what we have. But I agree we need to find a way to maintain this. Either we outsource the common code into utils files, or build an intermedate FEL loader, where FLASH and SXP loader inherit from.

Generally I have seen the git blame so I got the idea where you made changes. Is this going to be a permenant loader or it's just for your beamtime? Because adapting flash loaders structure makes this confusing and likely unmaintainable. We should later definitely think of a solution to this.

Well, In gerneral the requirements for FLASH and SXP are very similar, i.e. the train /micro/macrobunch structure etc., so it does not make sense to me to deviate too much from what we have. But I agree we need to find a way to maintain this. Either we outsource the common code into utils files, or build an intermedate FEL loader, where FLASH and SXP loader inherit from.

I think best solution is to define different classes for these different aspects and create the actual loaders to instantiate these classes


Update connection status

Notes for Reviewers
This PR fixes #

Update connection status

https://github.com/meshery/meshery/assets/52546856/e5475f90-7ac4-4862-86ff-6c6763823bcc
Signed commits

[x] Yes, I signed my commits.

@Aritra8438 @Freedisch, there is a bug here that you can assist with: when a connection's status is changed, and a POST request is sent with the new status value, the request is accepted and new status saved, however, the value of the Connection's name is nullified.

@Aritra8438 @Freedisch, there is a bug here that you can assist with: when a connection's status is changed, and a PUT request is sent with the new status value, the request is accepted and new status saved, however, the value of the Connection's name is nullified.

Looking into it

@Aritra8438 @Freedisch, there is a bug here that you can assist with: when a connection's status is changed, and a PUT request is sent with the new status value, the request is accepted and new status saved, however, the value of the Connection's name is nullified.

Sure! I think @Freedisch is working already?

hey @senali-d
Let's discuss this on Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

Still on-hold, right?

Still on-hold, right?

Because connection name nullified on update. That's the reason for hold.

Still on-hold, right?

Because connection name nullified on update. That's the reason for hold.

@Aritra8438 are you aware of this?

No, @leecalcote. Will look into it. @Freedisch, any suggestions or insights?

No, @leecalcote. Will look into it. @Freedisch, any suggestions or insights?

@Aritra8438, @Freedisch isn't contributing here actively any longer. Please proceed without him.

@senali-d, Can you let us know if you are still facing any issues related to the previous comments?

@senali-d, Can you let us know if you are still facing any issues related to the previous comment?

@Aritra8438 It's fixed now. 👍

Merged to PR #8902


NullPointerException in CirceSerialization

Kafka Deserializers need to handle null data, as outlined in this comment: https://github.com/apache/kafka/blob/1.0/clients/src/main/java/org/apache/kafka/common/serialization/Deserializer.java#L43.
Right now my streams app is crashing because data is null and is being passed to the string constructor

https://github.com/ovotech/kafka-serialization/blob/master/circe/src/main/scala/com/ovoenergy/kafka/serialization/circe/CirceSerialization.scala#L36
Is the line that can throw an NPE

Thanks for reporting the issue. The best approach, in my opinion, is to provide another general deserializer that returns Option[T] so that we can wrap a Deserializer[T].


Update environment variable format to be standard on all

Closes: N/A
What's Changed
Minor change to docs to ensure that they all followed the same format for environment variables.

Resolving open comments, as my preference would be to leave as is. Feel free to re-open them, but don't want to get lost in presuming there is unresolved comments.


[ENHANCEMENT]- Enhance navigation on Files section when file name is too big

Description
Currently the Files section actives the horizontal scrolling when a file name is too big

Reproduction URL
https://storz.pages.dev/app/myFiles
Reproduction steps
1. Go to the Storz app https://storz.pages.dev/
2. Login
3. Add a new file with a large name
4. See behavior

Screenshots
![image](https://user-images.githubusercontent.com/48018975/193726016-74c69263-7c1f-4f13-8045-83a1b36d005f.png)

Logs
No response
Browsers
Chrome
OS
Windows

If applicable assign it to me

Hi @nujovich, great job finding this bug!
Do you want to truncate the filename or wrap the remaining word in the next line?

Great! Np

@anomic30 I think truncating the filename is a better choice than wrapping it, this is causing issues here also:

What's the fixed max length you suggest need to set up for a filename?


corrupt jpeg files

I have a Shield_V2 VF with a OV5642 camera connected to a Arduino UNO, I am using the example sketch ArduCAM_Digital_Camera.ino
Everything works ok, but when I try to open the .jpg files I get a message "File damaged, or not doesn’t recognize".
I have "#define ARDUCAM_SHIELD_V2", and "#define OV5642_CAM" in the memorysaver.h file.
I am not sure what I am doing wrong.
I am also seeing error messages with the Arducam Library that I just downloaded.
/Arduino/libraries/ArduCAM/ArduCAM.h:104:0: warning: "pulse_high" redefined
#define pulse_high(reg, bitmask) sbi(reg, bitmask); cbi(reg, bitmask);
/Arduino/libraries/UTFT4ArduCAM_SPI/HW_AVR_SPI_defines.h:5:0: note: this is the location of the previous definition
#define pulse_high(reg, bitmask) sbi(reg, bitmask); UTFT_cbi(reg, bitmask);
^
/Arduino/libraries/ArduCAM/ArduCAM.h:105:0: warning: "pulse_low" redefined
#define pulse_low(reg, bitmask) cbi(reg, bitmask); sbi(reg, bitmask);
/Arduino/libraries/UTFT4ArduCAM_SPI/HW_AVR_SPI_defines.h:6:0: note: this is the location of the previous definition
#define pulse_low(reg, bitmask) UTFT_cbi(reg, bitmask); sbi(reg, bitmask);
^

I did notice the old post #104 that had the same issue, and was able to fix it by
"uncomment the following line from the example: //myCAM.read_fifo(); and placed a second line of the exact code"
But I did not have the same luck with the OV5642 camera.

@msach281, would you please upload your corrupt JPEG files? we will examine what's the problem and get back to you.

This is was created from the sketch example ArduCAM_Digital_Camera.ino.

@msach281, BTW: did you download the latest library?

There are two dummy bytes at the beginning of  your JPEG file, I have removed these, and you can see you photo below

Yes, I downloaded the library and installed it again this morning.
How do I see the dummy bytes on the JPEG files.
How do I prevent the dummy bytes from being saved at the beginning.

@msach281, You can use hex editor like UltraEdit.
In order to prevent the dummy bytes, you can use myCAM.read_fifo(); to remove one byte dummy at a time.

It is working now.
I did try adding myCAM.read_fifo() twice to the sketch yesterday and it didn't work, but today it did.
I must have done something else wrong.
Thanks for your help.


DFTD3 Method error for incorrect atom distances

Describe the bug
This is more of a hunch than a hard error. In several cases where jobs were inputted into QCArchive in Angstrom rather than Bohr DFTD3's error return was "Unsuccessful run. Possibly -D variant not available in dftd3 version.".
Additional context
It would be good to run this and see if we can break out "atom too close" errors from variant errors.

uggh. For dftd3 alone, do you consider using their internal b2a conversion in qcng as a potential fix or an anathema?

This is a user input error due to a lack of clarity of units. I don't consider this a DFTD3 issue beyond our parser incorrectly pinning a cause to the issue.

closed by #194
If anyone has an input that can trigger this error, please post, and I can try to classify errors further.


DragAndDrop Calendar doesn't update resourceHeader properly

Do you want to request a feature or report a bug?
bug
What's the current behavior?
resourceHeader doesn't update properly in DragAndDrop Calendar. I have extracted simplified snipped from my code:
function useResourceToggle<TResource>(
  resources: TResource[],
): [TResource[], (resource: TResource) => void] {
  const [selected, setSelected] = useState<TResource | null>(null);
  const selector = (resource: TResource) => {
    setSelected(selected ? null : resource);
  };

  return [selected ? [selected] : resources, selector];
}

export const Component = ({ assignments, users }: Props) => {
  const [resources, resourceToggle] = useResourceToggle(users);

  return (
    <BigCalendarDnD<Assignment, User>
      events={assignments}
      resources={resources}
      components={{
        resourceHeader: (props: any) => {
          return (

 resourceToggle(props.resource)}>{props.resource.displayName}

          );
        },
      }}
    />
  );
};

resourceToggle function inside resourceHeader doesn't update. This results in inability to reset selected. In other words selected will always by null when resourceToggle is called from within resourceHeader.
This happens only with DragAndDrop plugin. Without it everything works fine.
What's the expected behavior?
resourceHeader should be updated properly.

Do you want to request a feature or report a bug? ...

@Bielik20
Sent with GitHawk

Do you have a CodeSandbox with what you're trying to do here? I'm trying to visualize it, but just not seeing it.

I don't have CodeSandbox at hand but I can show it on pictures.
All resources:

Only one toggled resource:

So, when selecting a resource (header) you want it to only show that resource's items, right? Clicking again should show the other resources. Does that sound right? Just trying to fully understand your use case.

Yes, that is exactly the use case. I did it with very dirty workaround and I hope to remove it. It is clearly something with DragAndDrop, because it works fine without it.

I've written a few different component overrides, but never messed with the resource header before. As far as I can tell though, reading through the code I'm not seeing where the hoc does anything specific with that component.
I also use the DnD hoc, and will be doing some stuff with resources in a future iteration of my work. Can't give you any clues now, but if I find something I'll post back (but, unfortunately, it won't be any time soon)

Thank you, in the mean time I will post my workaround for anyone who stumbles opon this issue:
export function useResourceToggle<TResource>(
  resources: TResource[],
): [TResource[], (resource: TResource) => void] {
  const [selected, setSelected] = useState<TResource | null>(null);
  const selector = (resource: TResource) => {
    setSelected(selected ? null : resource);
  };

  return [
    (selected ? [selected] : resources).map((res) => {
      // @ts-ignore
      res.__toggle = () => selector(res);
      return res;
    }),
    selector,
  ];
}

It is dirty and ugly but it works. You must use __toggle method on a resource to toggle, not the returned selector callback.


Menu doesn't close after clicking on a menu item.

How to close the menu if an item is clicked?

Hello, that behavior is not and default behavior of dropdown.
However, if you'd like to achieve that you can check out this #6 issue, it has been described there. Thanks ! :)


1640 recruitment cycle not null

Context
Rollover 🎉
Changes proposed in this pull request
recruitment_cycle cannot be null on courses
Guidance to review
Try and create a course without a recruitment cycle
Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 [M] Backend - Add recruitment cycles to courses


Decouple actor from implementation of transaction signer

Current implementation of rpc client's actor has direct dependency on struct transaction.Signer. Actor implements logic to sign transactions and generate witnesses based on contract's attributes in transaction.Signer.
This covers basic scenarios when signers are wallets or proxy contracts without parameters. However, if we need a more complex scenario that requires us to pass extra parameters to proxy contract (that is, to Verify method of proxy contract) we are required to build transaction from scratch similarly to what neofs-node does in notary for signers and witnesses.
We have to build transaction ourselves, because we need to build scripts for witness that includes parameters for Verify method call. Current implementation of actor does not allow us to inject such logic in the transaction processing flow. However, it would be much more convenient if we could control behavior of signers and logic of witnesses outside actor.
So, the proposal is:
Step 1. In actor replace struct SignerAccount with an interface that goes something like this:
type Signer interface {
	SignTx(net netmode.Magic, tx *transaction.Transaction) error
	TxSigner() transaction.Signer
	TxWitness() transaction.Witness
}

Step 2. Provide implementations of the interface Signer for wallet and contract, something like:
type WalletSigner struct {
	Account *wallet.Account
	Scopes  transaction.WitnessScope // and AllowedContracts,AllowedGroups,Rules
}

func (s *WalletSigner) SignTx(net netmode.Magic, tx *transaction.Transaction) error {
	return s.Account.SignTx(net, tx)
}

func (s *WalletSigner) TxSigner() transaction.Signer {
	return transaction.Signer{
		Account: s.Account.Contract.ScriptHash(),
		Scopes:  s.Scopes,
	}
}

func (s *WalletSigner) TxWitness(tx *transaction.Transaction) transaction.Witness {
	return transaction.Witness{
		VerificationScript: s.Account.Contract.Script,
	}
}

type ContractSigner struct {
	Hash   util.Uint160
	Scopes transaction.WitnessScope `json:"scopes"`
}

func (s *ContractSigner) SignTx(net netmode.Magic, tx *transaction.Transaction) error {
	// Ideally we want FakeContractAccount and others to be encapsulated in these ready-to-use signers
	account := wallet.Account{
		Address:  address.Uint160ToString(s.Hash),
		Contract: &wallet.Contract{Deployed: true},
	}
	return account.SignTx(net, tx)
}

func (s *ContractSigner) TxSigner() transaction.Signer {
	return transaction.Signer{
		Account: s.Hash,
		Scopes:  s.Scopes,
	}
}

func (s *ContractSigner) TxWitness(tx *transaction.Transaction) transaction.Witness {
	return transaction.Witness{
		// Here we can have some convenience logic to convert parameters (if any) into byte-code...
		// Parameter values can be stored in instance of ContractSigner
	}
}

Step 3. Remove logic that produces scripts and witnesses in actor itself. Instead, call signer interface methods.

I don't think transaction.Signer is a problem, you have to have this data anyway to build a transaction, it's basically copy-pasted into it and to have all the features transaction signers have it has to be a complete transaction.Signer. The problem is more in *wallet.Account. It already can have arbitrary contracts inside and they can deployed and they can have any parameters at the same time. So primitive cases like zero parameters are even already handled by the SignTx method:
https://github.com/nspcc-dev/neo-go/blob/7306beca4ddc013157027ca0de35686c2dd0c538/pkg/wallet/account.go#L111-L113
But most likely you've already seen that.
I'd say this should be solved either by replacing the Account part of SignerAccount by some interface or expansion of wallet.Account to handle more complex scenarios. But the problem itself is very much valid and in some ways already known, it's just that we hadn't had any practical scenarios like that before, even though Notary contract takes a signature in its verify:
https://github.com/nspcc-dev/neo-go/blob/abf3ef5af73c85267714d7cc1118a33a4475bd20/pkg/core/native/notary.go#L361-L365

I totally concur that interface in place of *wallet.Account would provide sufficient flexibility to address the issue. Thank you, @roman-khimov!


Unable to debug go tests (MacM1) - Skipped breakpoint

Currently, using MacM1, Goland, dlv and go.
Unable to set a breakpoint. When running test, debug build is generated, i am able to run test in debug mode but not breakpoint is ever hit (they are skipped).
So far I've isolated the issue to bazel since build generated with bazel (from Goland or cmd line) cannot be debugged with break point. On the same host, builds created directly with go can be debug with dlv.
Bazel:
Build label: 4.2.2
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Dec 2 18:28:52 2021<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

Dlv :
Delve Debugger
Version: 1.8.2
Build: $Id: dbb493ec14d1e7753504d016b1e1ef1665b75b16

OS :
ProductName:	macOS
ProductVersion:	12.2.1
BuildVersion:	21D62

Go:
go version go1.18 darwin/arm64

Goland :
Version: 2021.3.4 ([Release notes](https://youtrack.jetbrains.com/articles/GO-A-35))

Build: 213.7172.22

Released: 15 March 2022

Same issue

Same issue

This unfortunately continues to be an issue for me


Replace multiple == checks with in

Replace multiple == checks with in

@harishsg993010 Thanks for this patch :+1: however we try to avoid trivial code reformatting unless it's a big problem as it creates extra noise in the history. Also, this change is incorrect in some places.


Running riverpod migrate suggests added "WidgetRef ref" to initState

Describe the bug
When running riverpod migrate on my project, riverpod recommended passing WidgetRef ref into a stateful widget's initState method.
To Reproduce
Run riverpod migrate
<Please add a small sample to that can be executed to reproduce the problem. As a general rule, 100 lines is the maximum>
Expected behavior
Shouldn't recommend this. I think it only happens when I am calling a method in initState that also uses the old context.read so riverpod suggests passing the WidgetRef into that method.

This is potentially fixable, but it is hard, because if one function needs the parameter (_initDataAndStartRoutine) then all functions that call that function also need to get the WidgetRef so it can pass it down. To fix this we would need to identify methods in StatefulWidgets as different than other methods / functions, and not needing the parameter forwarding. It is possible, but will take some time.

@TimWhiting If it's that big of investment I would vote it just gets put in the documentation that this might happen. It took very little time to correct, and it was pretty easy to understand what it was trying to do.
The migration tool handled 98% of the code migration which is amazing.
Not sure if you were the main developer that worked on this or not but thank you for this tool!

@TimWhiting What exactly is the difficulty? I'm not certain I see the issue here
To begin with, State methods should not need to receive the ref as parameter since it's available as a State property.

I'll close this. I have no plan to fix the remaining bugs for the migration tool as it's been quite a while now since the breaking change happened.


Whether the from attribute of the AuthorizationPolicy resource can support filtering and allowing traffic based on the label.

Whether the from attribute of the AuthorizationPolicy resource can support filtering and allowing traffic based on the label.
Because the ip of the pod will change after restarting, the only certainty is that the label has been.

Why do you use ip auth, if the allowed clients are in the mesh,  Source.Principals can be used instead.


[Bug] After deploying Docker, the API address was not entered into the address bar.

#!/bin/bash
docker run -d
--net=host
-e PROXY_URL=http://<IP_ADDRESS>:1314
-e OPENAI_API_KEY="sk-hb3z222222222222"
-e CODE="xxxxx"
yidadaa/chatgpt-next-we
The above is my startup script.

@lobmoo  Your image is broken, plz try upload again

@lobmoo I didn't understand your question too much, "the API address was not entered into the address bar." What exactly is the problem?

test


Metadata change in ES 2.x

In ES 2.x, metadata can no longer be specified per document but rather per call. This makes things somewhat tricky in terms of bulk indexing since it means different calls need to be made per call

We have around 40 storm nodes feeding to a 30-shard, 1-replica-each Elastic-Search cluster.
Without routing, each indexing request from storm is being further divided into 30 shards by the receiving shard.
That means even if we send 30 MB per request, it ends being 1 MB / shard / request.
This is really a performance killer for us.
If we can get routing back, there will be 29 lesser network requests per call and each shard will index 30 MB / request without distributing.
So getting routing to work is really important for us.
Will appreciate if there is some hint on when it is planned to be put back.
I can offer a patch if someone is ready to help me review the same.


Add a recommand a pub form  to contact us

What have been done:
Pushed to: add-a-recommand-a-pub-form
Tag somebody: @Shane-Walsh
Issue: #211
Asking for validation:

Check on mobile and on desktop if the issue have been correctly fixed.
If everything is correct, move the card to accepted column.
If the issue isn't fixed, re-open the comment clearly what the problem is and what is the desired result.
Move the card to have issues column.
Merge (or express approval in) the corresponding PR if needed. Move the card to the launch column.

This branch has conflicts that must be resolved
Conflicting files

package.json
yarn.lock

@Shane-Walsh fixed and rebased


same file with different compile command in one compile_commands.json

seems clangd uses first entry it encounters, what about popup a window and let user to choose which compile command to interpret for the current open file.

You already filed this as https://github.com/clangd/clangd/discussions/1288 :)

See also #681.


Default open when there is only one app available

It would be cool if the picker would automatically open the location if there is only one app in the list. Also the case of no app installed should be handled in some way.
But nice work and great naming of the library ;-)

Good idea and thanks! 😊
What do you think would be a good way to handle the case in which no supported app is installed?

That definitely sounds pretty cool, but it does feel a bit too much at this point at least 🙈 For the time being I'd rather try and keep this as simple as possible ideally without any custom UI.


Visualization import/export design

We're providing a new import/export feature, including all visualization metadata and optionally the data.
Details and full discussion at feature doc.
cc @xavijam

cc @urbanphes

Closing, designed by @urbanphes . cc @gfiorav


Enable reuse of the constituent primitive key shares of hybrid KEM

As a follow-up feature to be considered after #25884 has been implemented:
draft-ietf-tls-hybrid-design-11 explicitly allows reuse of the constituent primitive key shares of hybrid KEM in the ClientHello.
I.e. sending the exact same encapsulation key for ML-KEM-768 when sending key shares for both X25519MLKEM768 and SecP256r1MLKEM768 is explicitly allowed. Same for the X25519 or P-256 key share.
This behaviour is actually already implemented in NSS.
Originally posted by @tomato42 in https://github.com/openssl/openssl/issues/25884#issuecomment-2459767477

Basically it requires special handling in libssl and exporting/importing the individual part keys of the hybrid composite from/to the provider.
I.e., in scenario with 4 key shares (X25519MLKEM768, SecP256r1MLKEM768, X25519, P-256) 1. libssl generates a key for X25519, creates a key share and exports the private key, 2. same for P-256, 3. libssl generates a key for MLKEM768, doesn't create a key share but exports the private key, 4. libssl imports the X25519 and MLKEM768 private key components into the hybrid X25519MLKEM768 EVP_PKEY and creates a key share 5. libssl imports the P-256 and MLKEM768 private key components into the hybrid SecP256r1MLKEM768 EVP_PKEY and creates a key share. There is not much to be changed in suggested APIs for the generic hybrid KEM support. The import of the private key components can be done with a single EVP_PKEY_fromdata() if the exported OSSL_PARAM arrays are merged by libssl (we have helper functions for that). I do not think we want to add another provider key management import function allowing import from multiple OSSL_PARAM arrays.
As you can see all the special handling is done on the libssl side and there is no need for any extra provider functions. Of course in case the provider does not allow exporting the private key this optimization will not work and such failure needs to be handled gracefully by libssl.
In my opinion this optimization is really low priority and not worth it. We still do not even support sending multiple key shares from the client at all which is a much bigger deficiency.


Cannot chain .post() and .promise()

This code:
var api = 'http://localhost:3007/';
var promise = request.post(api + '/endpoint')
              .send({
                name: ' some data'
              })
              .promise();
return promise;

throws this error:
(intermediate value).cancellable is not a function

Ah, never mind. I was using an old version of 'bluebird'...


simplejson.errors.JSONDecodeError in FrappeClient.login(user, password)

Since maybe an update on a private site, I get this when trying to login with user and password (which works on the web login):
  File "export_timesheets.py", line 90, in main
    client.login(data["usr"], data["pwd"])
  File "/home/ubuntu/.local/lib/python3.8/site-packages/frappeclient/frappeclient.py", line 58, in login
    if r.json().get('message') == "Logged In":
  File "/usr/lib/python3/dist-packages/requests/models.py", line 897, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/lib/python3/dist-packages/simplejson/__init__.py", line 518, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 370, in decode
    obj, end = self.raw_decode(s)
  File "/usr/lib/python3/dist-packages/simplejson/decoder.py", line 400, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

When printing the http response, I get: <Response [403]>

Fixed by this branch of devittest's fork (you need to pull all 8 commits on his fork as well): https://github.com/devittest/frappe-client/pull/1


Employee Password

No place to add Employee password.

employee phone number set for the password.after login employee can change the password. Thanks


updated value is not displayed with custom Edit component

material-react-table version
v1.14.0
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it
Following the pattern from this discussion on custom edit components, I've created a simple example with a custom Select widget here. Here's the relevant part:
{
  accessorKey: "state",
  header: "State",
  Edit: ({ row, cell }) => (
    <Select
      value={cell.getValue<string>()}
      onChange={(e) => (row._valuesCache["state"] = e.target.value)}
    >
    <MenuItem key="Alabama" value="Alabama">
      Alabama
    </MenuItem>
    <MenuItem key="Zanzibar" value="Zanzibar">
         Zanzibar
       </MenuItem>
     </Select>
  ),
}

Selecting a value does actually set the new value, which I can see after hitting the Save button -- but it does not update the temporary value displayed while editing, so there's no visual indication that a new item was selected. (This is complicated to explain but trivial to see -- just try the demo.)
I thought that this change might fix it:
<Select
  value={row._valuesCache["state"]}
  onChange={(e) => (row._valuesCache["state"] = e.target.value)}
>

But surprisingly that had no effect.
In general the row._valuesCache thing seems problematic ... seems like we need a more principled way of accessing and setting the row state in a custom editor. For reference, here's how MUI does it -- though I don't particularly like their solution. Seems to me the cleanest and most elegant solution is for Edit params to just give me what I need:
{
  accessorKey: "state",
  header: "State",
  Edit: ({ value, setValue }) => (  // <-- notional new props here
    <Select
      value={value}
      onChange={e => setValue(e.target.value)}
    >
    <MenuItem key="Alabama" value="Alabama">
      Alabama
    </MenuItem>
    <MenuItem key="Zanzibar" value="Zanzibar">
         Zanzibar
       </MenuItem>
     </Select>
  )
}

(If setValue just calls row._valuesCache[accessorKey] = value under the hood, great, but as the MRT user I'd rather not know about it.)
Minimal, Reproducible Example - (Optional, but Recommended)
See CodeSandbox demo.
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
No, because I do not know how
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

@githorse  did you able to solve this issue? I'm also facing this issue

@mbmohib Unfortunately not. At the moment I'm just using the built-in select functionality, like this:
{
  ...
  muiTableBodyCellEditTextFieldProps: {
    select: true,
    options: myOptions.map(({value, label}) => (
      <MenuItem key={value} value={value}>{label}</MenuItem>
    )
}

But it's not what I want -- my actual custom Select widget has other functionality (styling) that I'm missing here.

After hours of digging: <table.options.data>

@Drecula could you elaborate? What do I do with table.options.data?

@githorse If you check the TextField component, whenever you change the table gets re-rendered. But with the custom component when we update the cache value, it does not re-render. So if we make the parent component force to rerender, you will see this value will be populated.

for those who are suffering from the same issue us the function row.toggleSelected this will update the component after value is changed>
  {
    type: "autoComplete",
    autoCompleteOptions: roles.data,
    header: "الدور",
    accessorKey: "role",
    enableHiding: false,
    Edit: ({ row }) => {
      return (
        <Autocomplete
          disablePortal
          id={"autoComplete"}
          key={"autoComplete"}
          value={row._valuesCache["role"] || null}
          onChange={(_, value) => {
            row._valuesCache["role"] = value;
            row.toggleSelected(row._valuesCache["role"]);
          }}
          isOptionEqualToValue={(option, value) => option._id === value._id}
          getOptionLabel={(option) => option.title}
          fullWidth
          options={roles.data || []}
          renderInput={(params) => (
            <TextField
              key={"autoCompleteText"}
              {...params}
              label={"الدور"}
            />
          )}
        />
      );
    },
  },


Accordion animation in Native JS

I am trying to get auto-animate working with an accordion and pure JS, yet it isn't working, but with a list it is. My code is the following:

        Title of the question

Nice stuff here

How can I set this up to work?

Your situation needs to conform to one of these:

Adding/removing the "hidden" attribute does not satisfy those. You could re-write yoru code to use .remove() and .appendChild() (or similar) to get it working.


Map Edits

Changelog:
Arena/Hammurabi:

Adds material reclaimer
Adds station maps
Adds bar rags
Adds soiled mattresses
Adds s&p

Hammurabi:

Reconfigures escape shuttles

Sorry, I should have tested first before pushing.. Seems it's still spitting the failed to fill error on map start

Ok, it's in a state now where it no longer triggers the error. I will have to play some more to figure out exactly what the limitations are. But, it's good to go for now.

Very good. If you ever figure out what exactly caused it in the first place, that would be great info. I thought it was because the evac pods were too close together (technically they could still fit, but would spawn 0 tiles apart).
It's strange because this fails for Hammurabi during tests, but not for Shoukou. It errors out on Shoukou during actual gameplay.


HIVE-24460: Refactor Get Next Event ID for DbNotificationListener

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

@pvary @nrg4878 Can you please take a look at this one too?  I am doing quite a bit of work within this class.


Change seconds()*1000 to milliseconds()

Signed-off-by: arthursens<EMAIL_ADDRESS>Addresses a small TODO. The previous fuzzit_regression test was complaining about the Milliseconds() function. Now that the test was removed, changing it back to milliseconds makes things a little bit easier to understand :)

Thanks!


False positive for insecure dependencies

https://deps.rs/repo/github/IMI-eRnD-Be/twine
This project is a library and does not have a Cargo.lock. The crate regex is marked as insecure but in this case it should be considered secure since cargo will take the latest available version.

Oh wait it's "maybe insecure". Maybe it won't show up after I update heck...

The badge now says "maybe insecure"... I guess that's okay


move install commands around a bit

npm/less notes are only relevant for dev installs

@minrk Thanks for making the changes. Happy to merge.


Problem when mouse is clicked while dragging outside the window

When you got out of the window (using Chrome) while draging and don't keep the mouse clicked outside the window until you go again into it, the drag function did not stop from that point on. After this fix you can stop it by clicking once more into the window.

Can you let me know if this is still a problem - maybe this has been fixed in Chrome?  I'm not seeing the problem you describe when I start a drag, move the mouse outside the window, release the mouse, then move back into the window.  When I do that it acts like I'd expect (dragging stops).


Endpoints are undocumented

The API endpoints do not appear to be documented anywhere. This makes the shootout a bit harder. :-)

While not ideal, the tests provide decent documentation of the desired behavior, IMO.
Maybe I should give up my goal of having a dependency-free test suite and use something like cucumber so that we can have fully executable documentation/tests. I dunno.


Hive 1.1.x support

Migrates to hive 1.1.0.
Needed to adapt ViewSerde since Hive now serializes Maps using : as separator. The proper solution would be to use a JSON deserializer in ViewSerde since the current implementation will fail if either a colon, an equals sign or double quotes appears in keys or values.
Closes #6

Ok, we actually have tests with ":" inside a map. Probably will need to integrate a JSONParser then. Or adapt the tutorial not use ":" as a seperator in tests.
Moreover the missing HCatLoader problem does not occur locally for me. I will investigate amend the PR tomorrow.

Can't we go for good old \001 \002 \003 separators? We control serialization and the textformat parameterization.

merged with master

Took it over in my fork for some final validations and changes and will merge from there.
Good job!!


Add a --with-dyncall option to configure instead of having to specify LDFLAGS and CFLAGS

Rejected.


Lost file metadata in artifacts and images

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Jun 12, 2017, 12:39
Problem
Currently, assuming a linux sandbox (we dont have others currently) everything is committed to the artifacts as:

UID/GID 0
No extended file attributes

When files are created with setuid/setgid in the sandbox, those should be recorded in the artifacts, but; when we checkout from ostree in user mode, the setuid/setgid bits are stripped.
This means that in addition to the above, when we create a bootable image, we pack in files that the sandbox sees without setuid/setgid bits.
Solution
Since recently, we now have a fuse subsystem in BuildStream which the sandbox uses, currently we only have one fuse layer which provides a copy-on-write hardlink experience (to solve issue #19).
To solve this I would like to take an approach similar to yocto's pseudo tool, but instead of doing any LD_PRELOAD, we would implement it with a fuse layer.
This will mean essentially the following:

The local artifact cache will have to be able to tell us about the real UID/GID, file attributes and extended attributes for any file, for the ostree artifact cache this can be done by following the ostree source code of ostree ls
The sandbox will use a fuse layer for the sake of spoofing the sandbox environment with the real attributes; this will be a separate fuse layer as the existing one we have for copy-on-write hardlinks.
The fuse layer will need to store the real attributes introspected from the artifact cache in a temporary local store, an in memory sqlite database could be a good choice if this is too intense for simple python data structures.
The fuse layer will handle filesystem callbacks in such a way that:

Calls to chown and redirected to the local store and not applied to the underlying filesystem
Setting extended attributes always succeeds, but is stored in the temporary store and not applied to the underlying filesystem
Reading the attributes and ownership is always read from the store and not from the underlying filesystem

When the fuse layer is unmounted, we need to persist the attributes (real UID/GID and xattrs etc) recorded by the fuse layer, or obtain that data somehow
When committing the artifact, the artifact cache API needs to have some interface for accepting the ownership and attributes separately from the files being committed, for the ostree artifact cache implementation this can be applied with the commit modifier callbacks, for other stores such as tarballs its just as easy.
The sandbox will have to orchestrate the fuse layer; it will be required on the root filesystem at all times, it is not required in /buildstream/build (it will slow things down significantly if we use it there, too), and it is also required in the read-write /buildstream/install directory. The sandbox mark_directory() API should be enhanced to communicate some of the requirements that an element has on the marked directories so that the sandbox can make a sane choice about this.

In GitLab by [Gitlab user @tristanvb] on Oct 12, 2017, 09:56
mentioned in merge request !100

In GitLab by [Gitlab user @tristanvb] on Oct 28, 2017, 07:56
mentioned in merge request !128

In GitLab by [Gitlab user @tristanvb] on Oct 28, 2017, 08:11
Marking this critical because it prevents important things from being possible.
It's also a mild security concern because currently suid binaries are created on the real backing filesys, instead of suid-ness being virtualized inside the sandbox root (allowing others to gain access to the builder user's rights via a plausible build of sudo in an active sandbox).

In GitLab by [Gitlab user @tristanvb] on Nov 8, 2017, 09:10
Some notes:

It seems that it will become interesting to store at least a list of attributes in artifact metadata so that an artifact can be properly reasoned about and standalone, regardless of it's storage backend (currently ostree or tar).
This is important for things such as standalone GPG signing features.
We can also potentially use this to store a virtual inode number in order to record and the state of hardlinks which is lost by ostree. If you commit a directory containing hardlinks, that information cannot be retrieved via ostree at checkout time, related upstream bug report here.

In GitLab by [Gitlab user @juergbi] on Feb 13, 2018, 16:52
We need to consider #232 before expanding the use of FUSE to regular build jobs. I'm also worried about the impact on (parallel) build performance, especially with Pyfuse but potentially even with a FUSE layer in C. I expect that most builds do not need additional metadata and I wouldn't want to accept a noticeable slowdown (assuming tracking that metadata will be enabled by default).
We should consider possible alternatives to FUSE. Some aspects could likely be handled when analyzing the file metadata after the build (before/while committing it to the artifact cache), e.g., hardlinks, permission bits, and extended attributes. owner/group would be more problematic, however, static uid/gid numbers are anyway an issue and we might want to recommend a different solution to this.
Another possible alternative is to use seccomp together with ptrace to intercept certain syscalls. I expect this to be faster than FUSE as file operations such as read/write/mmap would not have to be intercepted at all, however, I don't have any numbers. It would definitely avoid #232. On the other hand it would be Linux-specific and likely require more effort to implement. We would also first need a proof of concept to check whether it's even feasible.

In GitLab by [Gitlab user @juergbi] on Feb 15, 2018, 18:12
FUSE running outside the sandbox can only ever handle UIDs from outside the sandbox. I.e., it cannot be used to record chown() calls from a sandboxed process for UIDs that have no mapping. According to my current understanding on Linux, supporting arbitrary UIDs either requires the use of subuids or a solution within the sandbox environment.

In GitLab by [Gitlab user @samthursfield] on Feb 16, 2018, 16:47
mentioned in merge request !279

In GitLab by [Gitlab user @juergbi] on Feb 26, 2018, 11:17
As some projects will likely use Squashfs, I'll mention here that mksquashfs supports pseudo files as possible workaround.

In GitLab by [Gitlab user @juergbi] on Mar 27, 2018, 09:40
A few weeks ago I performed a few test builds of GTK+ 3 as a simple benchmark for the FUSE overhead. Adding results here for future reference.

Filesystem
parallel build -j32
notparallel build

ext4 without FUSE
2:37 (100%)
13:30 (100%)

SafeHardlinks (pyfuse)
13:45 (525%)
32:42 (242%)

bindfs (C libfuse)
6:42 (256%)
22:57 (170%)

In GitLab by [Gitlab user @juergbi] on Mar 27, 2018, 13:52
I've moved the aspect of preserving hardlink information to #324. The focus of this issue #38 is the permission metadata: UID, GID, lost permission bits such as setuid/setgid, and extended security attributes such as file capabilities and possibly ACL.

In GitLab by [Gitlab user @juergbi] on Apr 4, 2018, 15:55
Looking further into FUSE I've discovered that the tested FUSE filesystems don't make use of various optimization possibilities that FUSE supports. I then wrote my own minimal read-only FUSE filesystem to determine whether FUSE may be fast enough for regular builds despite the earlier disappointing tests.
That's now working and with this enabled, building GTK+ 3 on the same system takes 2:46, i.e., just 6% longer than without FUSE.

In GitLab by [Gitlab user @toscalix] on May 15, 2018, 14:14
marked this issue as related to #324

In GitLab by [Gitlab user @juergbi] on Jul 11, 2018, 12:28
The merge of the CAS artifact cache !337 will result in a small step backwards with regards to permissions. The only permission bit CAS supports is the executable bit for files. I.e., CAS will not store read/write permission bits for user/group/other, they are always 0644 or 0755. I don't expect major issues in practice given that we don't currently support setting UID/GID and thus the permission bits are of limited use. Non-world readable files and directories in /etc may be affected, though.
We will need to support all permission bits when addressing this issue, however, when we have a solution for UID/GID, setuid, and extended attributes, it should be trivial to also cover the missing permission bits.

In GitLab by [Gitlab user @tristanvb] on Jul 27, 2018, 07:39
mentioned in merge request !570

In GitLab by [Gitlab user @tristanvb] on Jul 29, 2018, 19:10
mentioned in merge request !581

In GitLab by [Gitlab user @nanonyme] on Jan 20, 2019, 21:16
[Gitlab user @juergbi] wow, so is that the root cause for why currently in Flatpak any application can write to /etc files that are not shipped by runtime allowing arbitrary configurations unless we ship defaults under /etc?

In GitLab by [Gitlab user @juergbi] on Jan 21, 2019, 09:15
Is there a Flatpak issue open for this with more information?

In GitLab by [Gitlab user @nanonyme] on Jan 21, 2019, 10:03
I was told on IRC this is most likely implementation detail of bubblewrap, not CAS. I'll create a bug into Flatpak anyway so this can be properly audited.

In GitLab by [Gitlab user @abderrahimk] on Feb 1, 2019, 16:47
mentioned in merge request bst-external!69

In GitLab by [Gitlab user @tristanvb] on Jul 17, 2019, 10:10
marked this issue as related to #910

In GitLab by [Gitlab user @juergbi] on Mar 16, 2020, 10:30
mentioned in merge request celduin/crash/jetbot-system-bst!36

In GitLab by [Gitlab user @abderrahimk] on Mar 23, 2020, 15:10
I think this doesn't necessarily need to be implemented all in one go. If the the UID/GID information is hard, we can start by implementing permissions, and possibly xattrs.
So what does this need exactly? Do we need to define an extension for CAS to store this information?

In GitLab by [Gitlab user @juergbi] on Mar 23, 2020, 15:30

I think this doesn't necessarily need to be implemented all in one go. If the the UID/GID information is hard, we can start by implementing permissions, and possibly xattrs.

A question is whether it's useful to store permission bits without UID/GID. There may be some cases where it would be useful but it could also be misleading in other cases.

So what does this need exactly? Do we need to define an extension for CAS to store this information?

The UnixMode node property can be used to store permission bits. No protocol extension is required (some details are expected to change, though: https://github.com/bazelbuild/remote-apis/pull/128), however, support needs to be added to BuildBox components and BuildStream.
It should most likely be optional given that it may have a performance impact (when hardlinking) and especially as it's incomplete for now (no UID/GID). An option for this would probably best fit into the sandbox config.

In GitLab by [Gitlab user @willsalmon] on Mar 24, 2020, 08:43
The way I understand it is that we need a mechanism to deal with meta data, this should be very similar to how we already deal with mtimes. And then we need some configuration options, as like [Gitlab user @juergbi] say we already store some meta so this is very important for some tasks that need extra but not at all for others were we already store enough meta, so if it can be behind configuration then that would be great.

In GitLab by [Gitlab user @tristanvb] on May 28, 2020, 12:58
This is not a blocker item for BuildStream 2.0, removing from the milestone.
As discussed in the BuildStream 2.0 planning announcement (See the "Sandboxing" section), it is intended to work as follows:

BuildStream projects make assertions about guarantees which it needs to have provided, which can be

Setting of the uid/gid of the build process during a build (already supported in BuildStream format, and supported in some execution environments)
Storing the uids/gids or specific attributes which need to go into artifacts (not currently supported)

BuildStream will then proceed to build your project and support your feature if the guarantee you asked for is supported

If it's not supported on that host OS or for whatever reason, BuildStream will abort with an error informing you why

If you do not require anything specific, then nothing specific will be guaranteed

E.g. on some execution environments, the build process is whatever uid/gid was used to launch a worker in an execution environment, if that buildbox did not support user namespacing etc

These extensions can be added over time without breaking API, as such BuildStream 2.0 does not block on this.

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 10:49
marked this issue as related to #429

In GitLab by [Gitlab user @BenjaminSchubert] on Dec 4, 2020, 12:46
marked this issue as related to #1413


[Inline LU] Create user inputs with utterance in form when creating inputs

Describe the solution you'd like

similar editing experience for intent with utterance when creating triggers
dialog/bot level setting for merging sections
Inputs includes Text, Number, Confirm, DateTime and MultiChoice.

Hi @hibrenda
I was discussing the issues remaining in managed-lu with @cwhitten . That a proper split up of tasks in the hoisting experience of Lg  is two tasks

let @alanlong9278 to work on the data flow (using shell api of LU) of hoisting Lu in Form, the deliverable of this one is a working version of hoisted lu editors in Form. But without any intelligence.
then @tdurnford can take from there to make LU LSP working in a inline mode.  This will involve updating the payload in the LSP protocol and add handlers and some mechanism similar to LG inline mode.

@cwhitten Do I need to file another issue to track LU LSP working in a inline mode for TJ ? So this one will only cover the form inline data flow.

hi, @hibrenda  @tdurnford, how is the lu inline editor going? And @cwhitten Do I still need to wait lu inline editor on this PR https://github.com/microsoft/BotFramework-Composer/issues/1848