file_put_contents(.../storage/framework/cache/data/): failed to open stream: No such file or directory

Laravel Version: 5.6
PHP Version: 7.1
Database Driver & Version: MySQL 5.7.23

Description:
I got an error

file_put_contents(.../storage/framework/cache/data///<some_cache_index>): failed to open stream: No such file or directory

<some_cache_index> is always the same.
I have CACHE_DRIVER=file  inside .env.
Error occurs on certain cross-domain request which fetches some data from database.
What I tried so far: php artisan cache:clear, didn't helped. storage/framework/cache/data/ is empty, but why framework ask that file each time? How can I make framework to forgot that file?

If you take a look at your cache.php config file you'll see that for the file driver the storage/framework/cache/data folder is set for writing:
'file' => [
    'driver' => 'file',
    'path' => storage_path('framework/cache/data'),
],

That means that your permissions for that folder should be properly set so that the web server user can successfully write to that folder.

@X-Coder264 Thank you! I've also tried
sudo chown -R $USER:www-data storage/*, sudo chown -R $USER storage/* - no success.

I guess, chmod -R 775 storage solved my problem.

php artisan config:cache solved my issue.

in my case it worked to delete the bootstrap/cache/config.php file.

php artisan config:cache

php artisan config:cache solved my issue.

It's work for me. Thank's

@mxl @hosamalzagh @jackgoh @yazansalhi @YNathaly @nadhifhayazee @Pezadilla still waiting for your feedback

in my case it worked to delete the bootstrap/cache/config.php file.

Perfect solution

In my case i do php artisan config:cache but now my app is totally down with this error  Fatal error: Uncaught Error: Call to a member function connection() on null in /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php:1201 Stack trace: #0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1167): Illuminate\Database\Eloquent\Model::resolveConnection(NULL) #1 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(997): Illuminate\Database\Eloquent\Model->getConnection() #2 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(912): Illuminate\Database\Eloquent\Model->newBaseQueryBuilder() #3 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(950): Illuminate\Database\Eloquent\Model->newModelQuery() #4 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(901): Illuminate\Database\Eloquent\Model->newQueryWithoutScopes() #5 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1570): Illuminate\Database\Eloquent in /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php on line 1201
can anyone help me?

In my case the problem was that he data folder inside storage/framework belonged to root instead of the correct user. chown -R < user: group > data did the trick.

go to /bootstrap/app.php
edit your app.php file and see that the storage directory is not hardcoded to the path /storage/framework/cache/data/
mine looked something like this: $app->useStoragePath('../../../logs/Reports' );

I tried everything written above, but I still get this error.
ErrorException : file_put_contents(/var/www/storage/framework/cache/data/5e/3c/5e3cbbed47195384f39edf30b47d8cd8245cdff8): failed to open stream: No such file or directory
I am using Laradock in project. it is working normally but in phpunit is not working.

Hey everyone,
I'm locking this issue because it either has gone off-topic, become a dumping ground for things which shouldn't be in an issue tracker or is just too old. Please try to discuss things further on one of the below channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC


BarChart can be modified by swipes with proper implementation.

Possible reference:
https://www.jianshu.com/p/8bce70785b2f

The arthur provided its source code as a whole at https://github.com/xiaoniu/SingleTapLineChart

Too little space for the interaction. Abandoned the solution.


The plugin deletes all gitolite mirroring attributes

Hi Nicolas,
We are using the gitolite mirroring feature (http://gitolite.com/gitolite/mirroring.html), which requires to add attributes to the repository description in gitolite.conf such as:
repo foo
...access rules...
option mirror.master        =   mars
option mirror.slaves        =   phobos deimos
option mirror.redirectOK    =   all

We have setup such mirroring for some of our redmine managed repos and it works fine, until someone makes changes through redmine, e.g. adding new project members.
At this point, the repo configuration is rewritten and the mirroring attributes are lost.
Do you think it would be possible that all attributes that the plugin does not manage be kept as they are found?
If you agree with that design and are willing to head me to the code where the rewrite operation is done, I'd fork and suggest a pull request with pleasure.
Please let me know and thank you for this great plugin!
Cheers,
Paolo

Hi Paolo!
Why not using the provided mirroring feature?

Hi Nicolas,
We need a two way mirroring between a private (intranet) gitolite and a public (internet acces but restricted to authorised users) gitolite, both of them being administrated by us.
Does the provided feature support two way mirroring ?
Does it support mirroring to another gitolite managed server ?
Thank you in advance.
Cheers,
Paolo

Does the provided feature support two way mirroring ?

No.

Does it support mirroring to another gitolite managed server ?

Yes. (actually it supports mirroring to any Git repository)
But I'm not sure this will fit your needs...

Hi,
Thank you for your answers.
Well we do need the two way mirroring.
So do you think my suggestion that mirroring attributes (and perhaps any gitolite attribute not managed by the plugin) should be kept as is makes sense?
If yes, as I was telling you, I could do the job, provided that you give me a few hints on where to start.
Thank you in advance.
Paolo

Hi Nicolas,
Any news on this topic?
Thank you in advance.
Paolo

Hi Paolo,
Unfortunately no. If you want to work on this you can take a look a these classes :

RepositoryHandler
RepositoryUpdater

RepositoryUpdater inherits from RepositoryHandler which defines most of the instance methods needed to update a repository config.
The real things happen here https://github.com/jbox-web/redmine_git_hosting/blob/devel/lib/redmine_git_hosting/gitolite_handlers/repository_handler.rb#L61

Thank you very much, I'll do my best!
Cheers,
Paolo

Hi Paolo! Any news?

Hi Nicolas,
No, sorry. May is not the most productive month nearby :-)
I don't see that I'll be able to work on the topic in the close future, I'll publish a proposal to work on this to my colleagues.
Wait and see...

Hello @n-rodriguez
I've talked with @paolosystemx, and I will work on this issue.
All best.

@alessandroleite Great! May the force be with you!

Hi! I've added support for Gitolite option in commit : https://github.com/jbox-web/redmine_git_hosting/commit/7b7e4586afb98305c1934055e7b55001aa19ab03.
Next to 'Git config keys' you'll be able to add 'Gitolite options' such as your mirroring options :)

Example :
repo    blibl
  RW+                            = redmine_admin
  -     master                   = redmine_developer1 redmine_developer2 redmine_developer3
  -     refs/tags/v[0-9]         = redmine_developer1 redmine_developer2
  RW+   dev/                     = redmine_developer1 redmine_developer2 redmine_developer3
  RW                             = redmine_developer1 redmine_developer2 redmine_developer3
  R                              = redmine_reporter1
  config redminegitolite.projectid = blibl
  config redminegitolite.repositoryid =
  config redminegitolite.repositorykey = bMs2qj6sPl1ttTZJH5vWJOClIQ2V8ZhwK2d7Szy1CnSDX0EYzE7SuTgAnyrVS7b
  config http.uploadpack = true
  config http.receivepack = true
  config multimailhook.enabled = false
  option mirror.master = mars
  option mirror.slaves = phobos deimos
  option mirror.redirectOK = all

Thank you @n-rodriguez , we'll try this ASAP!

Hi,
I have a similar requirement. Did this work for you?

@timoc , yes, it works fine for us.
Our config:

redmine 3.3.0
redmine-git-hosting 1.2.0
gitolite3 v3.6.4-0-g93e6524 on git 1.9.1


Explicit control over Nested SDFG codegen

To allow more control over Nester SDFG code generation, the user can now:

use a "hash" based approach (implicit): nested SDFGs with the same hash are code generated only once
or, use the "unique_name" of SDFG (explicit): SDFGs with the same unique_name are generated only once
or "none" of the above: a separate function is produced for each Nested SDFG

This is controlled by a property in dace.conf.
Solves #697

To be honest this approach is a bit dubious to me -- what happens if two SDFGs have the same unique_name, but are different?
I was hoping for an approach where we can guarantee programmatically that two nested SDFG nodes have the same SDFG reference, and therefore are identical.
This is not a good API, but an example of how you could guarantee this:
sdfg = dace.SDFG("top_level")
nested_sdfg = dace.SDFG("nested")
sdfg.register_nested_sdfg(nested_sdfg)
state = sdfg.add_state("foo")
nested_sdfg_node = state.add_nested_sdfg("nested")

If the unique_name is the same, but the SDFGs are different, it will result in undefined behavior.
It's up to the programmer to deal properly with this if he wants more control over NSDFG code generation.
Regarding your proposed API @definelicht , what will happen with the graphical representation of the SDFG?
If in the SDFG I have a Nested SDFG which is "registered", it becomes a sort of placeholder (like Access Nodes)

If the unique_name is the same, but the SDFGs are different, it will result in undefined behavior.
It's up to the programmer to deal properly with this if he wants more control over NSDFG code generation.

This is what I'm worried about, apart from being dirty, it's also not a nice workflow and has potential for bugs. For example, if you load the SDFG from JSON, and the nested SDFGs exist as two separate entities in memory. Then, you apply a transformation to one of the nested SDFG. But if you are unlucky and the other is found first, the transformation has no effect. It would be much nicer if this was guaranteed to work by design, so you could never get two copies of the same SDFG.

Regarding your proposed API @definelicht , what will happen with the graphical representation of the SDFG?
If in the SDFG I have a Nested SDFG which is "registered", it becomes a sort of placeholder (like Access Nodes)

Nothing would happen with the graphical representation: There is a unique mapping from each nested SDFG node to which SDFG it represents, so it's easy to retrieve this and draw the same way as we do now.

@TizianoDeMatteis @definelicht
Another much simpler option is to prepend the hash (in a way that is invisible to the user) to the unique_name.

@TizianoDeMatteis @definelicht
Another much simpler option is to prepend the hash (in a way that is invisible to the user) to the unique_name.

That doesn't address my primary concern, which is to expose an explicit way for the programmer to instantiate nested SDFGs


trigger build of all images for openssl fix

Signed-off-by: Subbarao Meduri<EMAIL_ADDRESS>

/approve
/lgtm

/retest-required

/retest


[WIP] php5 compatibility

Why this downgrade?

@malukenho I built this component mainly as a PoC, but @maglnet is taking over (I just got it kickstarted)

@maglnet actually, indeed, here's a question: since this tool will not be part of production environments, but only dev environments, is there a reason not to simply use PHP7?
Consider that nobody should really require this package in any app...
Basically, any environment can run /path/to/php7 composer-require-checker/check.php path/to/composer.json

@Ocramius, @malukenho
the main problem is our build environment, which doesn't provide php7 for now.
regarding the massive use of generators and the complexity to rewrite these, I'll think about a different approach to run it within our companies environment.

@maglnet the release date of php7 isn't too far away, is it? I'll probably make the final available than.

Then I should stop working on this. ;)

That's what I was suggesting - for a build environment, you could even just compile 7 (takes 10 minutes) and then use that just for this task :-)

So, I'll close this one, we'll try to get php7 running on our build server, as soon as it's released.


CSP-879: Knox proxy errors while uploading jar files

Changes the user facing Nginx conf to accept "Expect" header. This is helpful in uploading in large files. Currently it does not allow the header to pass through and Knox fails the request.

Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry request with a non-repeatable request entity.
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:226)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)

@doktoric Please assign to this relevant person to get this merged into master and relevant branches. This is required for CSP-3.0.0 release.

@biharitomi please review this change


ImageJ ROI Converter

Hello
I am trying to run the imageJ ROI converter.py file but am getting this error when I choose an the text file to display:
Traceback (most recent call last):
File string, line 10, in module
UnicodeEncodeError: 'ascii' codec can't encode character u'\xb5' in position 94: ordinal not in range(128)
Note string and module are flanked by quotes and arrows but the words don't appear if they are present so I deleted them.
Can any one help me? I have a working understanding of python but this one is confusing me.
Thanks

Ah solved my own problem. I didn't realised that you had to have the image open when running the file. Works well now.


Fix crash in 3D Tiles Feature Styling for ModelExperimental

When ExperimentalFeaturses.enableModelExperimental is enabled in the 3D Tiles Feature Styling sandcastle, the "Color By Distance To Selected Location" style causes a crash. This PR mimics what Batched3DTileContent does to avoid this crash.

Thanks for the pull request @j9liu!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

@ptrgags updated!

Thanks @j9liu!


librealsense: 0.9.2-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository librealsense to 0.9.2-0:

upstream repository: https://github.com/IntelRealSense/librealsense.git
release repository: https://github.com/intel-ros/librealsense-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.21
previous version for package: 0.9.2-0

Correcting the release repo.


HOTFIX 1.05? Good or Bad? Heads up!!!

HOTFIX 1.05
https://www.cyberpunk.net/en/news/37166/hotfix-1-05
PC-specific
Allot of fixes already fixed by you guys!! But this one caught my eye! Maybe nothing to worry about but thought I would mention it.
"Removed debug console to prevent functions that could lead to crashes or blocked quests. This doesn't mean we don't want to support the modding community. Stay tuned for more info on that."

When is this getting released? Is it Steam-only? Checked GOG and nothing yet. Hellooo???

the script isnt nessesary with the new patch:
"Removed the memory_pool_budgets.csv file. which was not connected with the final version of the game and had no influence on it (it was a leftover file used during the development to estimate memory usage. It had no effect on how much memory was actually allocated). Perceived performance increase after editing the file may have been related to restarting the game."
"[AMD SMT] Optimized default core/thread utilization for 4-core and 6-core AMD Ryzen(tm) processors. 8-core, 12-core and 16-core processors remain unchanged and behaving as intended. This change was implemented in cooperation with AMD and based on tests on both sides indicating that performance improvement occurs only on CPUs with 6 cores and less."
"Removed the use of AVX instruction set thus fixing crashes occurring at the end of the Prologue on processors not supporting AVX."

They say that 8+ core AMD CPUs are already "working as intended". So for my 5800X I'll still need this mod. I hope it gets updated to support 1.05!

the script isnt nessesary with the new patch:

That's not true. AMD SMT improvements clearly bring huge performance increase and more consisten frame times even on 8 core cpu's. I saw up to 20% increase in 1% low performance on the R7 3800X

Don't know how they can oversee this, but I too clearly had quite a huge performance increase with this mod and I'n on an 8 core 3700x. So yes, I think its still needed, but we'll see.

"Removed the memory_pool_budgets.csv file. which was not connected with the final version of the game and had no influence on it (it was a leftover file used during the development to estimate memory usage. It had no effect on how much memory was actually allocated). Perceived performance increase after editing the file may have been related to restarting the game."

This is an obvious lie. I tested this on a freshly restarted game both Before and After the file was edited.
I will be holding off on updating. They seem hellbend to destroy again what the modders fixed about this game.

Don't know how they can oversee this, but I too clearly had quite a huge performance increase with this mod and I'n on an 8 core 3700x. So yes, I think its still needed, but we'll see.

I have a 3700x and  a 5700xt and have no performance increase. use capeframe and test it  and show it.

On top of removing an obvious fix and removing debug console permanently this time, I think I'll stick with 1.0.4.

Don't know how they can oversee this, but I too clearly had quite a huge performance increase with this mod and I'n on an 8 core 3700x. So yes, I think its still needed, but we'll see.

I have a 3700x and a 5700xt and have no performance increase. use capeframe and test it and show it.

The game was unplayable for me before the fix. Microstuttering and FPS drops. After applying the fix (I did it manually on day one), no more problems, I have 80+ hours of buttery smooth playtime now. If I put the original exe back, stuttery mess again. 3700x and 2070S. Without the fix, core utilization is very low, around 35-45%, with the fix, it's 75-85%.
I really don't understand what CDPR is doing right now, but it sure looks like their main goal is to destroy the reputation, as fast as possible.

Don't know how they can oversee this, but I too clearly had quite a huge performance increase with this mod and I'n on an 8 core 3700x. So yes, I think its still needed, but we'll see.

I have a 3700x and a 5700xt and have no performance increase. use capeframe and test it and show it.

The game was unplayable for me before the fix. Microstuttering and FPS drops. After applying the fix (I did it manually on day one), no more problems, I have 80+ hours of buttery smooth playtime now. If I put the original exe back, stuttery mess again. 3700x and 2070S. Without the fix, core utilization is very low, around 35-45%, with the fix, it's 75-85%.
I really don't understand what CDPR is doing right now, but it sure looks like their main goal is to destroy the reputation, as fast as possible.

show it. use https://www.capframex.com/

@spenderniere: Dont need to test it to be honest, I see it via the fps monitor in game.

Process monitor does show that memory_pool_budgets.csv is being read by the game at least:

The values are actually parsed and handled too, this project even has code that hooks into that and increases the numbers it reads.
What isn't known is what happens with those numbers, people reported changing them to 0 and other crazy values with no bad effect, there could have always been a minimum/maximum set for them though, and a default for invalid values.

I'm hard gpu bottlenecked (ryzen 7 3700x, gtx 1060 6gb)
And all that smt thing didn't even increased my fps by one.
I benchamerked in the same spot, while moving, and checking npc count.
It might be doing smth for cpu bound people, hard to say


If there's a sourcemap for a file, mention the original line that causes the error

Currently if I run es-check for a bundled/minified filed, it's a bit hard to tell which exact line of code (and which related library/file) causes the error. See screen below.

Instead, we could consume sourcemap (if there's one located in the file or next to it, e.g. a.js and a.js.map) with https://www.npmjs.com/package/source-map#new-sourcemapconsumerrawsourcemap , and then improve the es-check error message, by saying what's the original line that causes the error.
What do you think? Would you be open to such a code contribution?

@jtomaszewski I'm open to it! Thanks for this consideration!


Enable memory debugging while testing

Checklist

[x] CLA is signed

Description of change

Pre 1.1.0, 'make test' would set the environment variable
OPENSSL_DEBUG_MEMORY to "on".  This got lost when translating the old
build files to the new templates.  This changes reintroduces that
variable.

Merged


test: rename all sim test files to camelCase

Motivation
Consistent codebase.
Description
Keep the file name pattern consistently every where.
Steps to test or reproduce

Run all tests

:tada: This PR is included in v1.18.0 :tada:


Draw temperature and winds

Both should be rendered and saved (and correspondily steps should be added)

Precipitations are drawn while winds are not but it should be addressed as part of #13


The docs for the security rules must have a section or page for examples

Currently, we are just explaining the options users have to write the security rules. While this is great it, it isn't clear on how flexible the rules really are.
Maybe we could some common usage patterns in the docs? It would help users to get started with writing security rules and ensure all apps built with space cloud are secure.

Resolved


error in yaml causes frontend to freak out

in feature branch frotnend, using the files from issue #121 , if I uncomment the line defining bottom while not yet erasing another line defining bottom (so that bottom is defined twice, an illegal yaml)
      bottom: =value[B:D, 7+$n] == ""
      bottom: =$end

I don't get the chance to erase the second bottom because the frontend immediately errors out into a big red page
edit: actually this appears to be caused by making any changes in the yaml editor whatsoever.

fixed in a28b946be3e3


types of useGLTF missing in 3.9.0

Describe the bug
3.8.0:

3.9.0:

It's still exported in .js file and is usable, but the types missing makes IDE yelling error.

Reproduction
https://www.npmjs.com/package/@tresjs/cientos?activeTab=code
Steps to reproduce
N/A
System Info
N/A

Used Package Manager
pnpm
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

 REMOVE AFTER TRESJS FIXES TYPES
declare module "@tresjs/cientos" {
  export function useGLTF(any, any);
  export function CameraControls(any);
// Necessary to declare any other cientos packages you are importing here
}

Currently I just simlpy remove opt out of TS (remove lang="ts") on model components :D,
Should be a quick fix but the team is preparing for 4.0 I guess.

 REMOVE AFTER TRESJS FIXES TYPES
declare module "@tresjs/cientos" {
  export function useGLTF(any, any);
  export function CameraControls(any);
// Necessary to declare any other cientos packages you are importing here
}

that worked brilliantly for me
but I am also getting a number of other type errors
error TS2322: Type 'number[]' is not assignable to type 'Vector3 | Readonly<Vector3 | undefined>'
error TS2322: Type 'string' is not assignable to type 'Color | Readonly<Color | undefined>'
which are not resolved.
did anyone else get those?

@BenoitBotton I have to use the classes from THREE in those places.
:position="new THREE.Vector3(0, 0, 0)"
:color="new THREE.Color('orange')"

thanks @NamesMT and @wcheek
I went with using the THREE classes

actually that does not fully work. one of my components is called several times in a v-for loop. it's template is
<template>
    <TresGroup :rotation-z="cutter.theta * toRad" :key="cutter.spiral">
        <TresGroup :position-z="cutter.ztip">
            <TresGroup :position-x="cutter.radius">
                <TresGroup :rotation-y="cutter.yrot * toRad">
                    <TresGroup :rotation-z="-cutter.siderake * toRad">
                        <TresGroup :rotation-x="cutter.backrake * toRad">
                            <TresMesh :position="cutter.spiral < 500 ? [0, 0, -r] : [0, 0, 0]"
                                :rotation="[90 * toRad, 0, 0]">
                                <Suspense fallback={null}>
                                    <Comp :color="color" />
                                </Suspense>
                            </TresMesh>
                            <TresAxesHelper :visible="showTipHelper" :args="[10]" />
                        </TresGroup>
                    </TresGroup>
                </TresGroup>
            </TresGroup>
        </TresGroup>
    </TresGroup>
</template>

only  :position="cutter.spiral < 500 ? [0, 0, -r] : [0, 0, 0]" is called out by the type error, not any of the other position or rotation props on the groups.  issue is r is a reactive prop and, when I replace it with
<TresMesh :position="cutter.spiral < 500 ? new THREE.Vector3(0, 0, -r) : new THREE.Vector3(0, 0, 0)"
I end up with only one component showing (or maybe all of them on top of each other? tresjs scene is blank in the dev tools! )
and if I revert back but remove lang=ts from the component, I get nothing at all!
I guess I will revert to cientos 3.8 for now

Should be fixed by 4.0 https://github.com/Tresjs/cientos/releases/tag/4.0.0 . If not feel free to reopen


Fr/range select

Updated
Page testing
This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Fixed range select issues with selectedItems increasing with duplicates
Simplified itemComparator to just itemKey: string

Some bugs I noticed.
First bug:
itemComparator was getting errors out due to it was receiving null anchor points.
Solution:
don't use null and use empty ember objects and just check if they are empty. This removes .get being used on null items.
Second bug:
When using pagination, switching pages does not reset anchors and trying to find the anchor item from a previous array of items does not work. Use shift click on page 1, switch to page 2 and try to use shift click again. It was not working.
Solution:
When a anchor is -1, it should be safe to assume we are working on a new array of 'items'. That means we should reset the anchors. Anchors from an old array are not useful.
Third bug:
The logic for the range base clicks may not have been correct in the first place (or I broke it) due to 'selectedItems' kept growing.
Why was it growing?:
shift select on item1, pushes item1 in selectedItems (1 item), selectItems.length = 1
shift select on item3, pushes item1-3 in selectedItems (3 item), selectedItems.length = 4
shift select on item5, pushes item1-5 in selectedItems (5 item), selectedItems.length = 9
Fourth bug(I introduced after resetting pagination):
If you switch pages and reset anchor,  new behaviors need to be addressed.
Scenario 1, two pages, 10 items each page:
page 1, shift click item1, item1 selected
switch to page 2, reset anchors, shift click item 9-10, item 9-10 selected.
switch to page 1, reset anchors, shift click on item 1, ERROR.
Item 1 was already selected on page 1 but now it was throw in selectedItems again due to anchor reset.
Solution:
Be aware of pagination and reset anchors, verify first shift clicked items before sending them into 'selecteditems'
Scenario 2, two pages, 10 items each page:
page 1, shift click item 3-5
switch to page 2, reset anchors, shift click item 9-10
switch to page 1, reset anchors, shift click item 1-6, ERROR
Your shift click now encompassed item 3-5 that was already selected on page one, dupes were thrown into 'selectedItems'.
Solution:
just wipe out dupes that way no crazy logic is needed.
My general opinion is selectedItems should be a map but I was looking to just keep things as they were with out doing major rewrites.

Ok, so if I boil down the issues:

Guard against null during comparison
Support selection reset in pagination
Items added to the selection array aren't being compared correctly, which results in duplicates

Is that a reasonable summary?

Yep that is what I noticed

Changes Unknown when pulling 030d36cb33950d4f02909a412b6fdf8e1e0e4906 on frosetti:fr/range_select into ** on ciena-frost:master**.

Changes Unknown when pulling<PHONE_NUMBER>2f9c31dc9a9f539986a668312d0b96 on frosetti:fr/range_select into ** on ciena-frost:master**.

Changes Unknown when pulling<PHONE_NUMBER>2f9c31dc9a9f539986a668312d0b96 on frosetti:fr/range_select into ** on ciena-frost:master**.

Approved

Changes Unknown when pulling d71a5003e7621e8204627640d498feaed4e81709 on frosetti:fr/range_select into ** on ciena-frost:master**.


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.12.9 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Timeseries: Notebook about CrateDB SQL, paired with pandas and Plotly

About
This Notebook is a canonical example demonstrating how to use CrateDB SQL for timeseries data exploration together with pandas and Plotly.
It builds upon the CrateDB Cloud tutorial about Time-Series: Analyzing Weather Data, aiming to explore a few features more deeply.

@amotl Could you please have a final review on the changes?

I expected already that this would become large ;].

Well. Those few klocs are definitively the space hog here.

NB: I don't know why that floating point value changed ;].

@amotl Could you please have a final review on the changes?

I've reviewed the notebook, and I absolutely love it 💯. In order to sand a few spots, I've submitted a corresponding proposal.

GH-180

Well. Those few klocs are definitively the space hog here.

A simple solution could be to render the "full dataset" graph as a bitmap image. It will be way smaller than the raw data.

I just added PNG vs. live rendering of the images. File size is now down to 540kB. Nice spot and thanks for the suggestion - we now always see the output as well.

I just added PNG vs. live rendering of the images. File size is now down to 540kB.

Excellent! I will continue squashing your commits and bring it in.

@amotl - Just retested on Google Colab - works :) I would be fine to merge back to main.


Feature/logo as wagtail conf setting

@miltontony @saeedmb8 ready for quick review

:+1: :cake:

holdup! Don't merge yet

:cake: thanks for fixing the {% trans %} blocks.

slack plus one from @miltontony


Skip hook/command when commit message matches a pattern

:zap: Summary
Allow to skip a hook (or individual command) if the commit message matches a certain pattern.
Value
I like using cog verify (cf. cocogitto/cocogitto) as part of a commit-msg hook. I also like creating fixup commits (in IDEA, if that matters) which end up vanishing after rebasing with autosquash.
Sadly, the two do not mix well: cocogitto forbids the ephemeral commit messages of such commits, as they don't conform to conventional commits.
What I would like is to configure lefthook to ignore fixup commits:
commit-msg:
  skip:
    - ref: "wip/*"
    - msg: "^fixup! "
  commands:
    cog:
      run: cog verify --file {1}

Behavior and configuration changes
The change seems additive to me.

FWIW: cocogitto/cocogitto#403
Either feature fixes my use case, but I do think that this proposal has merit in its own right for lefthook.

Workaround:
commit-msg:
  skip:
    - ref: "wip/*"
  commands:
    cog:
      run: sh -c "if grep -qv '^fixup!' {1}; then cog verify --file {1}; fi"


Cross-build docker image

Here's a feature branch that switch the base image to multi-architecture docker image:

https://github.com/liuqun/rpi-docker-tensorflow/tree/crossbuild-armhf-stretch-py27

The docker contains:

Docker base image multiarch/debian-debootstrap:armhf-stretch
Python 2.7
tensorflow-1.9.0-cp27-none-linux_armv7l.whl built by Google .
numpy 1.14.5 built from original source package.
Lots of pre-built python wheel packages from Raspbian's extra pip index repo https://www.piwheels.org/ .

It enables image cross-building from any 64-bit PC.
And I have uploaded another none-official docker image for raspberry pi 2/3 at:

https://hub.docker.com/r/liuqun/rpi-docker-tensorflow

Welcome to test (I have only one Raspberry Pi 2 at hand. And I don't know whether my docker image works on other device or not.)
docker pull liuqun/rpi-docker-tensorflow:1.9.0

Known bugs:

Not compatible with numpy-1.15.0rc2 ~ numpy-1.15.0: numpy.dtype size changed, may indicate binary incompatibility. Expected 56, got 52
I tried to upgrade to python-3.5, but got warnings that in tensorflow-1.9.0 or earlier version module 'tensorflow.python.framework.fast_tensor_util' is compiled with python-3.4. The following warning messages would be fixed in tensorflow-1.10.x release. See issues  tensorflow/tensorflow#18202 and bennuttall/piwheels#41

Python 3.5.3 (default, Jan 19 2017, 14:11:04)
[GCC 6.3.0 20170118] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412

and for tensorflow 1.12 ?

This project was originally an experiment to explore the practicality of
running Sam Abrahams' Tensorflow port in a docker container on the Pi.
These days there is an up-to-date official Tensorflow wheel, and I no
longer see value in running Tensorflow inside a container on the Pi.
Therefore I do not plan to develop or support this project further.
If anyone wants to do so there should be enough information here to enable
then to build their own docker image.
On Wed, 5 Dec 2018 at 10:44, antoniosap<EMAIL_ADDRESS>wrote:

and for tensorflow 1.12 ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/romilly/rpi-docker-tensorflow/issues/9#issuecomment-444441353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJHPt2yfS5p4mRaCL7PZb3kDs6SBzD4ks5u16OQgaJpZM4VfbaF
.

--
personal:@romillyc work:@rareblog skype:romilly.cocking web:
http://blog.rareschool.com/

The project has risen from the dead, as it's now realistic to run TensorFlow on a Pi 4 with 4 GB of RAM. I do not intenb to create cross-builds for X86, as the current build takes a reasonable me on Rasbia/Pi 4.


IBC Rate Limits: RBAC Permissions

Overview
Adds RBAC styled permissions which allow delegating control over various rate limit management functions to different addresses. Changes made to rate limits (such as reseting quotas, adding/removing paths, etc...) can optional have timelocks enforced for additional security.
This is largely intended to be used with protocols like DaoDao to allow for dao based management of rate limits.
Changes

The state.rs file was moved into a state module, and broken up into multiple different files.
RBAC permissions for each of the various management capabilities (add/remove rate limits, etc..)
Optional address specific timelock enforcement for any changes made to rate limits
Contract migration added to handle new storage variables
RBAC access control added to the ExecuteMsg handler
All functions in query.rs were changed to accept &dyn Storage trait instead of a full Deps object, as only the storage trait is needed
Most functions which used DepsMut as input have been changed to use &mut DepsMut due to the need to chain multiple function invocations and to work around the borrow checker as DepsMut is not cloneable

Thanks so much for the PR, honestly so beneficial, just cause the CI is complaining alot and we need the e2e tests to run on each commit to make sure we're ok, closing in favour of this PR :arrow_double_down:
https://github.com/osmosis-labs/osmosis/pull/8570

That PR will still give them commit credits right? Want to ensure that happens


Purs012

I've got this working with my current project. I had to do a FromJSON dance because I needed to use  generic types mixed with primitive types and non-generic types.

I'm closing this because we have a pure-0.13 PR coming


Characters Strings Example Missing in Processing.js

Actual Behaviour
Characters Strings Example is Missing in Processing.js
Expected Behaviour
Adding Characters Strings Example From Processing to Processing.js
Steps to reproduce it

Go to Examples
Check Data

Screenshots of the issue

Would you like to work on the issue?
Yes

hey @Himanshu664 ! yes i would like to work on the issue

Hi @Himanshu664, do you have in mind the example for string in this case? Could be a sketch on the editor and some descriptions.

@rinkydevi you can solve this issue and do changes as suggested by limzykenneth.


Added empty result set check to nextRowset()

This is a fix for the bug discussed in issue #507.

Coverage decreased (-0.003%) to 74.249% when pulling 83631cdabcaf34a1ac8edc21ead4ccfd2c84433b on david-puglielli:nextrowset-fix into 9e695d2d573f774fc5d30773f7c3525c537cbdf3 on Microsoft:dev.

Coverage increased (+0.08%) to 74.332% when pulling f4117a88d47071afaceb35be68138c2b82505385 on david-puglielli:nextrowset-fix into 9e695d2d573f774fc5d30773f7c3525c537cbdf3 on Microsoft:dev.

Moved the error check to core_sqlsrv_next_result in core_stmt.cpp.

Coverage decreased (-1.3%) to 72.967% when pulling 8666ea63c71dfc16a178baef5e9500c6575b31b9 on david-puglielli:nextrowset-fix into 9e695d2d573f774fc5d30773f7c3525c537cbdf3 on Microsoft:dev.

Coverage decreased (-0.8%) to 73.406% when pulling 2c28d0bf312fc856258c1aaaf23d44c8c4e83059 on david-puglielli:nextrowset-fix into 9e695d2d573f774fc5d30773f7c3525c537cbdf3 on Microsoft:dev.

Coverage decreased (-0.8%) to 73.406% when pulling f11c2084f28054674585f6c80534af5ec1f69a99 on david-puglielli:nextrowset-fix into 9e695d2d573f774fc5d30773f7c3525c537cbdf3 on Microsoft:dev.

Coverage increased (+0.09%) to 73.366% when pulling 66a12d33303cee7413c8272dbe59538e60c79edc on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.05%) to 73.321% when pulling d56446c41c581f2632a816a004f73fe70ebe7aa2 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling 3acab1ae0c0e69cd966cc228e53ea0a34976a6d7 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling 257b1cd6717355e97c3f474b83efa47a6ae938c6 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling 7315d4426aa279c939153042ffe4693547b90452 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage decreased (-0.04%) to 73.23% when pulling 494527d465fa7d1497448d24963e2b128bf9efd1 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling dc6e2a34fa67d844158cdd9483bef13c7e383916 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling dc6e2a34fa67d844158cdd9483bef13c7e383916 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling 4674f58a15007e6527fb4ff3deff7e4252fd4b16 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling 4674f58a15007e6527fb4ff3deff7e4252fd4b16 on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

I'm not sure how useful testing with a regular SELECT statement would be, because I don't think the result set could ever be null in that case. At most you can have an empty result set with no rows but at least one column, or you select from a nonexistent column, which yields a different error message. These are not the same as a null result set, in which there are no rows and no columns, and it's why I needed to use the stored procedure in the tests to trigger a null result.

Coverage increased (+0.003%) to 73.276% when pulling 4349a3c029808a5efdf8ae27db4860baba9b33cd on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.

Coverage increased (+0.003%) to 73.276% when pulling 70b20a2bb968b50770c8e647fae2ca93bfae3bba on david-puglielli:nextrowset-fix into ca9ba63672f41ab87a2a6adc3191880e449c21e1 on Microsoft:dev.


Release v7.19.0

Time for a new release:

[x] Gem pushed to RubyGems & GitHub Package Registry
[x] Deployed to GitHub.com
[x] Grammars deployed to Syntax highlighting service - highlighting won't be 💯 up-to-date until this happens

This release is now live on GitHub.com 🎉


Fixes html5-detection:

Brief explanation: $locationProvider.html5Mode() returns an object:
{enabled: true|false,...}.
Guess it's happening since 1.3.X.

Hi @emgee, please take a look at this small fix.
thankss!

Thanks & sorry for slow response.


Installer fails on raspberry pi 4

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | sudo bash -s -- -m raspberrypi4 -p /opt
[Warning] No NetworkManager support on host.
[Warning] No AppArmor support on host.
[Info] Install supervisor Docker container
[Info] Install supervisor startup scripts
bash: line 142: /opt/sbin/hassio-supervisor: No such file or directory

The curl command on this line (142) tries to download to /opt/sbin/ on your raspian-filesystem, wich not exist.
Try to let the -p and -s flag untouched and only provide the -d flag for data-mountpoint for correct raspian integration

Plus, the machine name is wrong on the installer. If -m is left alone, it suggests you armv7l (which will fail) - while the correct is raspberrypi4

I had a problem using the installer because I specified -m armv7l because of a misunderstanding of the error message when no -m option is given:
see: https://community.home-assistant.io/t/145697
Error message was:
[ERROR] Please set machine for armv7l

I erroneously used -m armv7l   instead of  -m raspberrypi3
And that created a difficult to recover problem... (basically needed to cleanup all docker).
My suggestion if to make this request in the script:
DOCKER_REPO=homeassistant
curl -s https://hub.docker.com/v2/repositories/$DOCKER_REPO/?page_size=1000| jq -r '.results|.[]|.name'|sed -ne 's/-homeassistant$//p'|sort

This lists all currently supported architectures for homeassistant in hassio
Based on that:
1- check that image exists if user specifies -m
2- if no -m, propose the list after the error message


Support for sparse node features

❓ Questions & Help
Hi there,
I am looking at GCNs for visual question answering, a problem which requires efficient embedding of up to thousands of different object classes. I have experimented with torch.nn.functional.one_hot encodings of objects, however such large node feature dimensions cause a large slowdown when compared to lower-dimensional dense features such as those retrieved from CNNs. My question is two-fold:

Is there support for sparse node features in PyG?
What kind of alternatives to one-hot vectors would be worth trying? My background is mainly in DL and NLP, where we mainly deal with dense feature representations.

Cheers,
Alex.

There is some kind of sparse node feature matrix support in PyG, for example, GCNConv should work fine when inputting a torch.sparse_coo_tensor as node feature matrix x, but that's not the case for all GNN operators.
To fix, one could also make use of an initial simple Linear layer to reduce the dimensions of your high-dimensional sparse features.

Thanks so much, that's good to know about the GCNConv layers, I'll make sure to check the source on a case-by-case basis. As a side note, thank you so much for all the hard work put into this library, I look forward to being able to contribute to it in the near future!


Add a dropdown as SOCIETIES

Purpose

The purpose of this PR is to fix #352
Goals

Adding a dropdown as Societies and put Computer Fraternity inside it
Approach

I added a dropdown as Societies and put Computer Fraternity inside it
Screenshots

https://user-images.githubusercontent.com/97069900/152082819-197af499-8ac2-4ffc-b7b2-40ab6a4222f6.mp4
Preview Link
https://yoshitharathnayake.github.io/sack-site/
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[ ] I have read and understood the development best practices guidelines
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Related PRs

Test environment

Learning

@Piumal1999, @Hasthikagirihagama told "we want a hover dropdown and material kit has outdated so updating material kit is a hard work, put the dropdown in custom css". I created the hover dropdown look like material kit from custom css

And the current problem is contact us link is divided into two lines. how to solve that @Piumal1999 , @Hasthikagirihagama


[feature request] download each block respectively when hex is not sequential

When a firmware is merged from bootloader and app, the hex file will be not sequential. However, using wlink flash seems to download the empty part in the middle, which would cause the download time be longer.

Good point. This is very useful for customized second-stage apps.

I was going to ask, and found this ticket. :)
The request would be when using elf files as well.
Apart from the typical bootloader/app situation, another use case is putting constant data into the non-zero-wait Flash area, something I'm trying right now.


(false error code, no apps are working)

Aware of duplicate of certain issue but this really needs attention. The game IS compatible with IPhone 3GS, i'm using 6.1.6

Please explain what is the issue because no apps are working for me

are you jailbroken with appsync installed?

yeah i used p0sixspwn to jailbreak and i have appsync unified from karen's repo

late update but it works.
if anyone else has this problem just reinstall appsync unified and it should work, if not, reinstall it again


Segment record TTL not work.

Please answer these questions before submitting pull request

Why submit this pull request?

[X] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues
#1942

Bug fix
Fixed a bug which the segment record index does not delete the history data because of the saving time bucket is a second format date, but the query delete is minute format date.

Coverage remained the same at 13.24% when pulling 20acce207dcfd6bb875358133ad9adbd136dfedf on peng-yongsheng:fixed/1942 into da734ac8fe0e298bce5019ea0e3c3c157a5e7a07 on apache:master.


[Document] Remove development snapshot toolchain requirement in "Get Started" document

Description
The "Get Started" document says "A recent development snapshot toolchain is required to use the testing library". Is that still relevant after Swift 5.9 is released? This confused me when I first tried the library, but my experiment shows the library works fine with Xcode 15.0 on macOS.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
No response
Swift & OS version (output of swift --version ; uname -a)
No response

Yes, this is still relevant. As this package remains experimental, we expect to need to rely on language features and enhancements that are not available in 5.9.


Textbook Quiz: Section 12.2: Question 2 Answer Validation Confusion

In the Textbook Quiz for Section 12.2, Question 2 marks only the answer "distance between the two group proportions", which is corrected based on how the reading presents the test statistic, but technically it is a "distance between the two group means". Also, one might expect the reading and lecture content to parallel each other, so from the lecture the test statistic we explored was the "difference between the group means."

Thanks for bringing this up, @asheynis. I'll consult with @amclanahan about this next week. I can definitely see how the wording/answer choices can be confusing if you are literally answering the quizzes based on the textbook content.

The answer for the question asked (in 2) is 'the distance between the group proportions', which is correct (and that statement is taken right out of the textbook). We DO calculate proportions and find the absolute value of the difference between the two groups. We do it using np.mean (which adds up all the 1s and divides by the number in the set), but this process IS calculating a proportion (the proportion of people who said yes, there was an effect). So maybe I could amend this answer to be 'the distance between the group proportions (which are calculated using np.mean applied to the 1s and 0s)', but I am not sure that would not confuse the readers more. So I am not certain, we should change it.
And maybe we should do a better job of showing that we are actually calculating proportions here in our lecture.
Thanks for the thought provoking question!


libgpiod and the future of gpio in Python

First off, it's abundantly clear to me that - despite its deprecation - Linux sysfs GPIO (the way this library currently works) is going to stick around for quite some time, and still has uses on embedded platforms with behind-the-curve kernels. I don't want to take any functionality away from people.
However, Linux's new libgpiod is the clear path forward, and the current state of libgpio for Python users is absolutely heinous.
We have:

The excellent but confusingly named python3-gpiod, which is a pure-python re-implementation of python3-libgpiod. It works, but is severely lacking in documentation and does not in any way attempt to be "pythonic" in its implementation- being a 1:1 mapping of the reference design. It's available via pypi but not (afaik) in any Linux package managers.
The, effectively a reference design, python3-libgpio, this is a C library that is available via - for example - the python3-libgpiod Debian package. It does not have a pypi counterpart, so it cannot be specified as a dependency or installed in a virtual env.
A mystery-meat libgpiod package which has been uploaded to pypi with no details or indication as to which of the above it resembles
Third-party libraries such as RPi.GPIO (RPi only), wiringpi (defunct), and lgpio (too broad)
Libraries like blinka or gpiozero which attempt to solve the problem of the GPIO ecosystem by sweeping it all under a more Pythonic, user-friendly API. These are inevitably too broad in scope to be a reasonable dependency for- for example- handling an interrupt pin in a simple sensor driver.
Libraries like this one, which - in my humble opinion - represent a reasonable, Pythonic answer to the problem of GPIO, but rely on a deprecated interface.

To confound this issue, in the case of the low-level libraries (gpiod and libgpio) documentation is scant.
To confound it further, as of Debian Bookworm (the underpinnings for the new Raspberry Pi OS) it is not possible for a user to install pypi packages system-wide, or casually maintain a mix of system/user packages. All pypi packages must be installed into a virtual environment. This effectively makes python3-libgpiod impossible to specify as a dependency, since you'll end up with the user's pip pulling libgpiod (the mystery meat package mentioned above) from pypi. This is the case unless they have initialized their venv with --system-site-packages so that the system python3-libgpiod can satisfy this dependency.
I first picked up gpio (this library) because I wanted to solve this problem, and had (ha ha) mistaken this library for a libgpiod based library.
I still want to solve this problem, and - given how complicated, cryptic and confusing the various gpio package names are (lgpio, libgpio and libgpio etc) - making gpio (this library) the canonical library for Linux GPIO in Python seems like the prudent move. That means adding support for libgpiod based GPIO access into this library, and doing it right.
And, thus, this is an open call for feedback and input on this idea, how to approach it and what GPIO should look like in Python.

https://stackoverflow.com/questions/74352978 looks like a good reference

Okay, plot twist- it's the author of libgpiod who uploaded libgpiod to Pypi. The package appears to be irreconcilably broken on Raspberry Pi OS (Debian Bookworm) due to a mismatch in assumed libgpiod versions.
The big problem with no 2 this is that gpiod cannot be imported from system packages while in a virtual context, unless the user specifies --system-site-packages. I'm trying to figure out how that can be fixed, since depending upon the python3-libgpiod (whether it comes via apt or pypi) seems to be most reasonable solution.
I suspect we could probably probe for the existence of /sys/class/gpio/gpiochipX and, if the library is available, prefer it.
I was broadly hoping that a widely available, widely compatible python3-libgpiod library would let us simply specify it as a dependency but it seems to be repeating the same mistakes made by smbus (that prompted the pure-python smbus2).
We might have to depend upon or largely re-implement the pure-Python alternative: https://github.com/hhk7734/python3-gpiod

Note: the linked stackoverflow is, afaik, already out of date.

Okay I've got a prototype libgpiod package that I can install (via pip) on a Raspberry Pi.  It - with any luck - works elsewhere too, but I'll admit I'm probing in the dark a little here.
https://github.com/Gadgetoid/libgpiod-python/releases/tag/2.0.0
I'm in the process of working out how this package could become the canonical libgpiod Python distribution, but I realize "works for me" is a very long way from clearing the bar for such an important package.

If you can get a gpiod installed from pip, then couldn't users simply use that?

If you can get a gpiod installed from pip, then couldn't users simply use that?

In theory, yes, but in practise it's another API to learn and understand to accomplish the same task. And not a terribly user-friendly one at that.
Perhaps it's hubris thinking it could be better. But it's had multiple years to make a dent in the Python ecosystem and all we've got is a bunch of stackoverflow posts with various snapshots of out of date code.
In all cases, though, it would be faster to use the library directly and that's always an option, but I very much believe there's a neat little gap between libgpiod and gpiozero where a very concise GPIO library can sit for the benefit of people who aren't either engineers or kids/beginners respectively.
Also gives a migration path for those using this library to transition painlessly over to libgpiod if/when they get rugged by their distro 😆

This does sound concerning, but I don't think that making this library more complicated is going to help anyone. In fact, folks are better helped by this library being stable and constant IMO.
PyPi's fragmented ecosystem is outside the scope of this package :smile:


KIP-368: Allow SASL Connections to Periodically Re-Authenticate

The adoption of KIP-255: OAuth Authentication via
SASL/OAUTHBEARER in release 2.0.0 creates the possibility of
using information in the bearer token to make authorization
decisions. Unfortunately, however, Kafka connections are
long-lived, so there is no ability to change the bearer token
associated with a particular connection. Allowing SASL
connections to periodically re-authenticate would resolve this.
In addition to this motivation there are two others that are
security-related. First, to eliminate access to Kafka for
connected clients, the current requirement is to remove all
authorizations (i.e. remove all ACLs). This is necessary because
of the long-lived nature of the connections. It is operationally
simpler to shut off access at the point of authentication, and
with the release of KIP-86: Configurable SASL Callback Handlers
it is going to become more and more likely that installations
will authenticate users against external directories (e.g. via
LDAP). The ability to stop Kafka access by simply disabling an
account in an LDAP directory (for example) is desirable. The
second motivating factor for re-authentication related to
security is that the use of short-lived tokens is a common OAuth
security recommendation, but issuing a short-lived token to a
Kafka client (or a broker when OAUTHBEARER is the inter-broker
protocol) currently has no benefit because once a client is
connected to a broker the client is never challenged again and
the connection may remain intact beyond the token expiration time
(and may remain intact indefinitely under perfect circumstances).
This KIP proposes adding the ability for clients (and brokers
when OAUTHBEARER is the inter-broker protocol) to re-authenticate
their connections to brokers and for brokers to close connections
that continue to use expired sessions.
Signed-off-by: Ron Dagostino<EMAIL_ADDRESS>

Beginning to add tests, and I need to rebase to get KAFKA-7324: NPE due to lack of SASLExtensions in SASL/OAUTHBEARER (#5552)

Rebasing again to resolve conflicts with KAFKA-6950: Delay response to failed client authentication to prevent potential DoS issues (KIP-306)

@rajinisivaram This PR now has everything except:

implementation and tests for client-side latency metrics
implementation and tests for server-side connection kill metrics
a test to see if server-side kill works

I added re-authentication to the NioEchoServer and I test for it with bearer tokens and delegation tokens within SaslAuthenticatorTest.  I added re-authentication every 50 ms for all end-to-end scala authorization integration tests as well.
I will work on the remaining 3 items on Wednesday.  Can you review what is here already, or would you prefer to wait?
Ron

@rondagostino I will review the PR tonight or tomorrow. There is a failing test iin the PR builds (org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testTokenReauthenticationOverSaslScram[reauthenticate=true]) - can you check if that is a test issue or a code issue? I will start a system test run once you get a chance to look at that.

@rajinisivaram It is a test issue.  I cannot reproduce the error locally -- it passes on my laptop.  I pushed a commit to sleep a bit longer in the hope that it will fix the issue during the build.

@rondagostino Thanks, I have started a system test run on your branch: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1979/. Will review the PR later tonight.

@rajinisivaram Pushed a commit that I think fixes/resolves most of the issues you raised.  It's getting late here so I couldn't get to all of them, but I think we are in a better place at this point.

@rajinisivaram The test failures are due to the tests being flaky rather than a coding problem in the feature implementation.  I may have been able to solve the delegation token-related test that was failing (it didn't fail in these runs) by increasing the session lifetime in that test (from 50 ms to 500 ms).
I will try to fix these flaky tests by increasing the associated session lifetimes as well.  I think what may be going on is the tests are taking a long time to run and by the time they send data the session expiration time has arrived and the connection is being killed.  It has also occurred to me that setting the session lifetime to something less than 1000 ms is probably not a good idea in general -- it may invite this type of flakiness due to unexpected delays, for example -- and maybe we should change the units of the configuration value to seconds instead of milliseconds to make sure it is never less than 1000 ms.  Thoughts?  Commit pushed with larger lifetimes, it was clean on my laptop.

@rajinisivaram I just pushed a commit to add an ExpiredSessionsKilledCount metric.  The KIP called for expired-connections-killed-total as the metric name but ExpiredSessionsKilledCount is consistent with the existing metric RequestHandlerAvgIdlePercent.  Thoughts?

@rondagostino Sorry, I haven't had any time today to look into this PR. Given the complexity of the PR and how close it is to feature freeze, it would be very helpful if we could get another reviewer. I will try and take another look tomorrow, but not sure if we will have enough time to get this merged without help from one more reviewer. If it didn't meet feature freeze deadline, would it work for you if it was committed only to trunk and not the 2.1.0 branch?

@rajinisivaram We would really like this in 2.1.0 if at all possible.  Is there anything I can do to help?  Maybe find another reviewer, perhaps someone else who has voted for the KIP?

@rondagostino Yes, getting another reviewer would definitely speed up the process.

@rajinisivaram There are a couple of changes that are not necessary as part of this PR -- more like cleanup of things I discovered while working on the alternate implementations that we considered and rejected.  I could remove those changes and submit them as minor tickets post-2.1.0 if it helps to minimize the surface area requiring review.  ExpiringCredentialRefreshingLogin is one, for example, and OAuthBearerSaslClientTest is another.

@rajinisivaram Both builds passed.  I'm going to work on adding the last metrics, and if I get that done tonight then I believe this will be complete.

@rajinisivaram I was able to add the additional metrics.  This PR now has all functionality, but I could not figure out how to test server-side expired connection kill or its metric since I have no way of running an older client.  I know it works because it was the cause of the test failures in SaslGssapiSslEndToEndAuthorizationTest -- I just don't have a way to test it in an automated fashion because there is no way to disable re-authentication at the client side.  I probably have to add metric documentation as well.  But I think that's it.  I asked someone to review, but this section of the product is pretty difficult to understand without experience, so I'm not optimistic about it.  Any chance you can review this on Friday?  Al tests passed last run, and I hope the same will be true of this one.

@rondagostino In terms of testing, I think system test may be the way to go for testing with older clients since we already have other system tests for testing with older clients. If this goes in by Monday, you have until code freeze two weeks later to add the system test to 2.1.0.

@rajinisivaram Ok.  Last set of builds was clean again.  I'm confident this is working as expected and is able to be merged assuming a review cycle can be completed.

@rajinisivaram Metric documentation is added, this is now done except for any additional PR review required.  All conversations from above are resolved/fixed.  I've contacted 5 people (4 of whom up-voted the KIP) in the hope that at least one will be able to review.

@rajinisivaram I reverted 9 files and eliminated 500 changed lines from this PR.  I will submit minor tickets for these changes separately.  These changes perform cleanup of code that was discovered while implementing rejected alternatives.  These changes are minor and can be submitted separately at a later date.  They have no impact on functionality or performance and are simply reducing technical debt. Keeping these separate reduces the surface area of this PR.

@rajinisivaram I added functionality to prevent changing the principal or the SASL mechanism during re-authentication and added tests for both cases.  I defined a 1-second minimum before you can re-authenticate a second time (see comment above) to prevent the rogue/buggy client from re-authenticating over and over again (the connection will be closed if the 1-second timeframe is violated, and then there will be the new DDoS delay as well, so I think this covers it).  I will address client interoperability with system tests (I assume it will be easier as you stated, though I am unfamiliar with the system test suite at the moment).  Assuming everything looks good, any chance of this being merged and included in 2.1.0 even though it is the morning after?

@rondagostino I can do another review today to make sure it is ready to merge. Can you check with the 2.1.0 release manager @lindong28 on whether it can still go into 2.1.0? The alternative is to merge to trunk only after the branch is cut.

@lindong28 See comment from @rajinisivaram above -- any chance this can get into the 2.1.0 release if it is merged today?

@rondagostino @rajinisivaram Do you think we can merge this PR by end of Wednesday? Since this PR is almost ready to be merged, it is reasonable to wait for a day or two to include it in 2.1.0 release.

@rondagostino @lindong28 I will do another review today and see where we are. We also need a good system test run on this branch. Unfortunately the last one I started didn't work, so started another one: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1985/.
@rondagostino Since we don't have any interop tests yet, it will be good if you can run some manual tests with different versions of broker/clients.

@rondagostino Sorry, not sure about access since it is a Confluent Jenkins. I will update with the system test results when the test run completes.

@rajinisivaram Agreed.  The tests failures in the JDK 8 build appeared when I "fixed" the ExpiredConnectionsKilledCount metric.  I'm going to comment out that metric to see if the failures go away.  Unfortunately this is a long turnaround cycle -- a couple of hours -- but it's the best I can do given that I can't reproduce the issue locally under JDK 1.8.

@rajinisivaram Still seeing this error on JDK 8 build:

kafka.api.GroupEndToEndAuthorizationTest > testNoConsumeWithoutDescribeAclViaSubscribe FAILED
java.lang.Exception: Unexpected exception, expected<org.apache.kafka.common.errors.TopicAuthorizationException> but was<org.apache.kafka.common.errors.SaslAuthenticationException>
Caused by:
org.apache.kafka.common.errors.SaslAuthenticationException: Authentication failed due to invalid credentials with SASL mechanism SCRAM-SHA-256

This is the same type of problem that occurred before.  It isn't happening as frequently without the metric there, but it is still happening.  I pushed a commit to add more debug information to the error message.  Will have to wait for these builds to finish and then wait another 1.5 hours for a failure to occur in the next build.

@rajinisivaram @lindong28 I agree it would be unwise to include this in the 2.1.0 release.  Thank you both for your willingness to entertain the possibility over the past days.  The point that convinces me is this one:

we have to ensure that there are no paths where existing authentication has changed in any way. Since we dont have tests that cover every possible scenario, I am not sure how we can verify that.

I am actively working on the AuthenticationException issue, and while it is difficult to run experiments where the turnaround time is on the order of hours, I am hopeful that I can figure out what is going on there.
Let's shoot for merging this to trunk when the above two issues are resolved.  I don't expect to be able to write exhaustive tests to guarantee that authentication is not impacted by re-authentication, but I will try to re-organize the code so that the diff makes it much easier to confirm by inspection that there is no impact.  I did not keep this in mind as I worked, so I think I can accomplish the same things with more clearly fenced-in changes.  I think that -- at a minimum -- will be helpful.
Thanks again for your willingness to give the PR a chance for 2.1.0, and Rajini thank you especially for the technical advice on the implementation and the reviews.  Hopefully I can get this into a trunk-mergeable state soon.

The system test run from this branch from yesterday passed all tests except the nine variations of QuotaTest which are also failing from trunk.

@rajinisivaram I am now unable to reproduce the errors.  I've run 3 separate builds -- some were clean, and while others had errors they seem to be unrelated.  I can't fix something that doesn't show up!

  One of them is bound to exhibit the problem at some point, and then maybe I'll get useful information from the additional detail I put in the error message.

@rajinisivaram Still unable to reproduce the problem, both JDK 8 and 10 builds are totally clean at this point.  Today I'm going to try to re-work the SaslClientAuthenticator and SaslServerAuthenticator code so that we can more easily say via inspection that the existing authentication flow is unchanged.  Hopefully that will be useful and then the builds will either remain clean or the AuthenticationException problem will arise (and I will get additional information via the exception message, which I augmented).  Then we can decide whether to commit this to trunk or not.

@rondagostino Thanks for making the updates. FYI if you want to rerun tests without a commit, you can just add a comment retest this please.

retest this please

@rajinisivaram I reorganized SaslClientAuthenticator and SaslServerAuthenticator to make it much easier to tell by inspection that authentication is unaffected by the re-authentication code.  I am unable to reproduce the AuthenticationException problem we were seeing the other day -- the issue has not reappeared across several builds.  The reorganized code and a successful system test should give us high confidence that authentication is unaffected and the issue is likely something that happens rarely -- maybe due to some kind of race condition that is possible only during specific re-authentication states.  That's conjecture on my part, but I don't know what else I can do if the issue doesn't reappear.  I spent the entire day staring at the code and reorganizing it, and nothing jumped out at me.
Please review the latest code and let me know your thoughts on how you wish to proceed with respect to potentially merging this to trunk.

@rondagostino Thanks for the updates. I will do another round of review early next week. Since there have been no more failures, I think we can commit to trunk. Since we are early in the release cycle for the next release, we will have plenty of builds before that and if we do run into that exception again, hopefully the additional debug you added will pinpoint the cause.

@rajinisivaram Thanks.  I'll look forward to addressing any review comments.  FYI, I just updated the KIP to refer to 2.2.0 instead of 2.1.0 and the current metric names (some of which changed over the course of this PR).  I also just pushed a commit updating the ops.html document to refer to 2.2.0 instead of 2.1.0.

@rajinisivaram Everything is finished except re-doing SaslAuthenticatorTest to make it less wasteful (i.e. don't just blindly re-run all tests in "re-authenticate" mode) and performing a rebase.  I found rebase without squash to be difficult given that I had a bunch of OAuth technical debt cleanup changes in here along the way that I backed out.  I have a squash rebase ready to push that runs the test suite cleanly; I'll push that sometime Monday EDT, then assuming that runs well on the build farm all that will remain will be SaslAuthenticatorTest.

@rajinisivaram I believe this is all set, all review comments are addressed.  Note that there were lots of errors on the previous JDK 11 build (https://builds.apache.org/job/kafka-pr-jdk11-scala2.12/97/) but I looked at some of the other PR builds and the same thing happens elsewhere at times (e.g. https://builds.apache.org/job/kafka-pr-jdk11-scala2.12/99/).  The JDK 8 build was clean.  So I suspect this is fine.  I have yet to see a recurrence of the AuthenticationException problem.

@rondagostino Thanks for the updates. Agree that the test failures are unrelated to this PR. I will do another review tomorrow and hopefully we can merge this week.

Rebasing to resolve conflict with clients/src/test/java/org/apache/kafka/common/network/NetworkTestUtils.java

@mjsax Looks like trunk build is broken due to https://github.com/apache/kafka/commit/2646781d3265c8269f35d39c199dfddf14d3c2a8.  When I rebased onto trunk for this PR I am getting this compile error locally and I assume it will also happen here:
streams/src/main/java/org/apache/kafka/streams/kstream/internals/TimeWindowedKStreamImpl.java:198: error: cannot find symbol
                    windows.segmentInterval()
                           ^
  symbol:   method segmentInterval()
  location: variable windows of type Windows<W>
  where W is a type-variable:
    W extends Window declared in class TimeWindowedKStreamImpl

I think org.apache.kafka.streams.kstream.WindowsTest has a similar compile error.

Ok, I see https://github.com/apache/kafka/pull/5806 is where this will be fixed.

@rajinisivaram Any progress on another review?  Would like to merge ASAP so it gets as many builds and test runs as possible prior to the next release.

@rondagostino Sorry, haven't had time to review yet, will try and do it today or tomorrow.

@rajinisivaram Latest comments are addressed/pushed.  The one issue that might need more attention is the REAUTH_BAD_MECHANISM state in SaslServerAuthenticator.  See my comment above.

@rondagostino my recent merge #5684 created some conflicts with this PR. Please rebase the PR.

@rajinisivaram Made two suggested changes, both builds were clean.  Rebasing onto latest trunk now to resolve conflicts.

@rajinisivaram After rebase JDK8 build was clean, JDK 11 build has 2 failures but they seem unrelated/transient issues.

@rondagostino Thanks for the updates. I think we are good to go. I will take a look later today and merge to trunk (if there are any other changes required, we can do them in follow-on PRs).


RAND() is CPU-bound

Introduced in https://github.com/odan/benchmark-php/commit/f88a374a37a1b6797bbfa3f46ad6369558ff683e the mysql query now uses RAND.
Doing that many calls to RAND is heavily CPU bound and generates at least 7 seconds on the benchmark test, which dwarfs the other metrics by far.
I feel that this i skewing the result quite a bit.

That's the idea behind a benchmark :-) If you don't want to test the database, just comment out the  database settings.
//$options['db.host'] = '<IP_ADDRESS>';


Not detecting .njk file extensions

I am not entirely sure if this is related to this plugin or a Atom specific setting, but If I rename files to use the .njk (instead of the .nunjucks) file extension, then Atom is not able to detect that the file is a nunjucks template file.

@ArmanNisch that issue is long pending in pull request #11. Meanwhile i can suggest you use this instead.

@puranjayjain Why didn't you fork this repository to add your changes? I see that you added autocomplete and some additional snippets, which looks great. However, much of the code shows you copied this repository to add the features, instead of forking it. And then you replaced Olivia's name with your own in the copyright, and removed @alohaas as a contributor while retaining the rest of the us?! This goes against the spirit of open source software, not to mention it blatantly violates the attribution requirement of the MIT license.

@joelbschwartz thanks for alerting me to this. It's true that I have been quite busy and have not noticed many of these Issues. I can attend to them now, however.
@puranjayjain in the future I would suggest being more proactive about reaching out to me directly via an @ mention if you are looking for an immediate response, which I usually respond to right away.

@joelbschwartz I am pulling my repo right now and totally agree with you

@ArmanNisch I've merged in PR #11 which will autodetect .nk file extensions.


CplexSolver doesn't work after using workspace() code

I have a problem with using CplexSolver in Atom. The first time I run the code, the code work fine. However, when I run it for the second time, an error shows up solver argument (CPLEX.CplexSolver(Any[])) must be an AbstractMathProgSolver. I found out when I use workspace() to clear the console, the same error shows up. This error appears when I updated julia-client, ink, uber-juno, and language-julia packages. This error will also show up when using CbcSolver.

Could you please help me with this issue? To avoid this issue, I keep reopening Atom each time I want to run the program again.
First part of the code:
for powershell issue
# Pkg.build("MbedTLS")
# Pkg.build("Atom")
# Pkg.update()

Installing solver packages
# Pkg.add("GLPKMathProgInterface")
# Pkg.add("JuMP")
# Pkg.add("CPLEX")
# Pkg.add("Cbc")

workspace()

using JuMP
using CPLEX

obj = JuMP.Model(solver=CPLEX.CplexSolver());

Packages installed:
5 required packages:

Atom 0.5.2
CPLEX 0.1.6
Cbc 0.2.4
GLPKMathProgInterface 0.2.3
JuMP 0.14.1

55 additional packages:

ASTInterpreter 0.0.4
AbstractTrees 0.0.4
ArgParse 0.3.1
BinDeps 0.4.5
Blink 0.4.1
BufferedStreams 0.2.0
COFF 0.0.2
CRC 1.1.1
Calculus 0.1.15
CodeTools 0.4.1
Codecs 0.2.0
ColorTypes 0.2.8
Colors 0.6.8
Compat 0.9.2
DWARF 0.1.0
DataStructures 0.4.6
ELF 0.1.0
FileIO 0.1.2
FixedPointNumbers 0.1.8
ForwardDiff 0.2.5
GLPK 0.3.0
Gallium 0.0.4
Hiccup 0.0.3
HttpCommon 0.2.6
HttpParser 0.2.0
HttpServer 0.1.6
JSON 0.7.1
JuliaParser 0.7.4
Juno 0.2.2
LNR 0.0.2
Lazy 0.11.2
LegacyStrings 0.1.1
LibExpat 0.2.1
Libz 0.2.0
MachO 0.0.4
MacroTools 0.3.2
MathProgBase 0.5.6
MbedTLS 0.3.0
Media 0.2.2
Mustache 0.1.2
Mux 0.2.1
NaNMath 0.2.1
ObjFileBase 0.0.4
Reactive 0.3.5
Reexport 0.0.3
Requires 0.3.0
ReverseDiffSparse 0.5.8
SHA 0.2.1
StructIO 0.0.2
TerminalUI 0.0.2
TextWrap 0.1.6
URIParser 0.1.6
VT100 0.0.2
WebSockets 0.2.1
WinRPM 0.2.1

probably related to https://github.com/JuliaLang/julia/issues/18646 / https://github.com/JuliaLang/julia/issues/16467

Closing since workspace() has been removed from Julia.


Cache the CompileResult produced by the compiler.

We should modify the sway-core API so we have an option to not re-compile std, core, and any dependencies more than once. Instead, once these have been produced, we should be able to pass these cached results into forc-pkg so the compiler only needs to create the AST’s for the user's program. We would only need to detect changes in the Forc.toml which would then trigger a full recompilation.
Without doing this, the compiler is needing to compile all of the standard library and any dependencies on every keystroke in LSP. Obviously, this is highly inefficient so making this change would be a big optimization for the language server.

Just ran time profiling using Xcode instruments on the did_open callback. Nearly all of the time is spent doing semantic analysis in the compiler. If we can somehow only do that once and cache the result, and then only compile the users workspace we would get a pretty large speed up. The problem is the type_id and decl_ids might change in between each compilation so these could get invalidated. Maybe @emilyaherbert has an opinion on how this could work?

Ideally, we would get this down from 600ms per keystroke to something sub 50ms. Anything longer just seems too sluggish.

So the server callbacks are already async already so it's probably fine the way it currently is working. Other LSP capabilities are still able to run asynchronously while we wait for compilation to finish.


PR 20200619 master test run

Latest test run data including AD Instruments data

Will merge once pre-commits pass.


useData() - Error with new vike project

pages/+data.ts
async function data() {
  const result = await fetch('https://pokeapi.co/api/v2/pokemon/pikachu');
  const data = await result.json();

  return data;
}

export { data };

pages/+Page.tsx
import { useData } from 'vike-react/useData';

function Page() {
  const data = useData<unknown>();
  return <>{JSON.stringify(data)}</>;
}

export default Page;

+renderer/config.ts
import type { Config } from 'vike/types';
import vikeReact from 'vike-react/config';

export default {
  clientRouting: true,

  meta: {
    title: {
      env: { server: true, client: true },
    },

    description: {
      env: { server: true, client: false },
    },
  },

  hydrationCanBeAborted: true,

  extends: vikeReact,
} satisfies Config;

localhost-1716830984490.log

I'll need a reproduction, with reproduction steps.

:+1: Let me have a look.

The issue is that you're using your own onRenderClient()/onRenderHtml() hooks.
What is it you're trying to achieve?

Oh that makes sense.
I want to use SSR only for OpenGraph tags, but the rest of the application should be CSR.

Set ssr: false while using the Head setting.

Thank you! This can be closed.


Create Tag unit test #5

Moved model tests to Tests/Unit/Models
Methods available for taggable models: attachTag($tag), attachTagByName($name, ?$type), detachTag($tag), detachTagByName($name, ?$type, syncTags($tags)
Sanitize tag name before saving

Let's add those back. That function is in the Helpers of https://github.com/tipoff/support

@gurgentil Take a look at some of the features I want to add to this opinionated way of doing tags:

https://github.com/drewroberts/media/issues/5#issuecomment-758730027

What is your opinion about these macros in MediaServiceProvider? @drewroberts

@gurgentil Can you add some tests here to make sure it is saving correctly?

add tag "Drew Roberts" should be tested to have name: #DrewRoberts & slug drewroberts

add tag "Gustavo's new-creation Thing!" should be tested to have name: #GustavosnewcreationThing & slug gustavosnewcreationthing

Another test would be to try to add a tag with multiple hashtags. It should strip all hashtags and just add one at the beginning in the name field. Example:

add tag "#Drew #DrewRoberts##" should be tested to have name: #DrewDrewRoberts & slug drewdrewroberts


export async;

Input Code

export async;

https://astexplorer.net/#/gist/08a46bcd5b3c2260a3e470a774c20cce/latest
Expected Behavior
Is should throw "Unexpected token, expected function (1:12)"
Current Behavior
It is parsed as an export declaration with an expression statement
Your Environment

software
version

Babylon
7.0.0-beta.16

Hey @nicolo-ribaudo! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.


Better windows compatibility.

Setup to help address #14.
Changes (copied from issue):

Replaced all icons with twitter emoji: https://github.com/twitter/twemoji
On windows, using ctrl + shift in place of command only for the preferences window (,) and quitting (q) and using Windows version of DevTools keyboard shortcut (Control+Shift+I).
On Win10, the system tray background can be dark, so removed transparency in the center of the icon (using white).
Added yarn.lock lock file, 'cause: shit's fast, yo! 🐱
New: Tooltips providing keyword hints. Now you know What keywords to use moving forward if you want to find other emojis (or exactly what portion of what you typed triggered a particular emoji).
New: Ability to customize window position. I really like it in the center, not all the way in the corner. The default is still topRight, however!

Here is a demo before/after for the icon (you'll see why I changed it):
Before:

After:

Demo:

NOTE: Had an issue with the dashed versions not working. Turns out those are ones without any sort of actual unicode but still have an alias, so I'm fixing this too 👍😎

Friend tested on Mac and noticed a bug with the icons, will need an OS-level check to only add the non-transparent version on Windows.

Thanks for putting in all these work!

Friend tested on Mac and noticed a bug with the icons, will need an OS-level check to only add the non-transparent version on Windows.

This is probably related to #8. The -Template file name has a purpose.

Replaced all icons with twitter emoji: https://github.com/twitter/twemoji

I'd prefer if this is either an option or flagged for Windows only.

New: Tooltips providing keyword hints. Now you know What keywords to use moving forward if you want to find other emojis (or exactly what portion of what you typed triggered a particular emoji).

Nice touch! :heart:

@muan Nope, actually I believe it works fine without the -Template suffix in OSX from what I could tell. Maybe you should check yourself to confirm just in case? I tested this with my aforementioned friend as well and he confirmed it working fine once I put int he OS level check. The reason why that OS level check is necessary is because while it looks fine on Mac with transparency, it doesn't look good on Windows since the background can still be dark (see screenshots above).
I'm registering a level of discomfort with standardizing the icons across both OS's, is that correct? If so I can understand since it seems like a drastic change due to the level of native support in the mighty OSX. I like the idea of the app having a consistent appearance across all OS's using standardized icons, as it is already understood that even in Windows why the app itself may not display an emoji, it may still display just fine in Twitter (due to their shims) or in Github (due to Chrome/Chromium/Electron/Webkit still supporting it or via more shims) and it is known that it will also display differently depending on OS.
At least the screen shots/demos displayed would be consistent with user experience regardless of OS, and I think that is a plus. But that's just me and that's my [albeit potentially weak] argument for it.

Also just resolved some merge conflicts and rebased against master. Some notes on that:

The transition to CommandOrControl for Linux compatibility was a good one and I've revised my code to instead check to see if the current platform is OSX instead of if it's Windows. This is because Linux and Windows share most of their keyboard shortcuts and Mac is the only one with the "Command" key.
Based on above, now only the icon is checking to see if we're on Windows, so maybe that could be switched as well since again I think only OSX is performing the icon colorization selectively based strictly on transparency so in Linux we could have similar issues as Windows if the OS is styled to have a dark background like on Windows.
Quit shortcut: The code click: function () { app.quit() } was still retained because on Windows, the code selector: 'terminate:' does nothing (doesn't work at all). Please let me know if this doesn't work on OSX. It should, though since I assume this is a standard API for quitting the app 😁

Let me take a look at your focus related question in #85 while I'm still in here.

@muan I can rebase & resolve conflicts... would you be willing to merge this soon? Any comment? It has sat for a while 😔

What is blocking the merge (except the conflicts)?

That was my main aprehension with resolving the conflicts (which should be easy, haven't checked yet). I didn't want to resolve and have it continue to rot again.
SIDE NOTE: I still use this daily 🎉

Also using it daily for nearly one year 🎉


x/blog:Tutorial not working

What version of Go are you using (go version)?

$ go version
go version go1.13 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\DELL\AppData\Local\go-build
set GOENV=C:\Users\DELL\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\go-work
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=c:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\DELL\AppData\Local\Temp\go-build164497938=/tmp/go-build -gno-record-gcc-switches

What did you do?
I think the example on the tutorial is wrong

https://blog.golang.org/gos-declaration-syntax
At the end sector 'Pointer':
they declare a variable that i think it a integer nil pointer like this: []int("hi")
but i think the author is mistook with the : []int(nil)
What did you expect to see?
It run, cause it's a tutorial
What did you see instead?
the compiler throw back with the error:
command-line-arguments
.\test.go:10:14: cannot convert "hi" (type string) to type []int

Back in 2010, when that article was written, there was no rune, and unicode strings were made of ints.
So in pre-1 Go releases, []int("hi") was perfectly valid. Then in Go1 rune was introduced as an alias for int32, so today you would write []rune("hi") (which works), and now []int("hi")  is a compilation error.

A (very old) blog post is not really a tutorial, so I'm not sure we want to go back and retroactively change posts that were correct at the time but are not now. Labelling this as "NeedsDecision".
cc @robpike

A (very old) blog post is not really a tutorial, so I'm not sure we want to go back and retroactively change posts that were correct at the time but are not now. Labelling this as "NeedsDecision".
cc @robpike

I think if those post are still used as "valid and formal documentation" they should be updated. When  I say "Formal" I mean that is given by a reliable source as google, not just a dev that works with the language. If is that not the case, I give a +1 to close the issue.

I'd leave it alone for historical reasons and also because that whole section is built around int and introducing rune might be distracting. But I'm not certain about that decision, so other opinions welcome.

How about adding a note box for all old blog articles before Go 1 to address such problems?


Update maintainers list

Link to GitHub repository

https://github.com/jenkinsci/ease-plugin
When modifying release permission
If you are modifying the release permission of your plugin or component, fill out the following checklist:

Release permission checklist (for submitters)

[x] The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to accounts.jenkins.io.
[x] All users added have logged in to Artifactory and Jira once.
[ ] I have mentioned an existing team member of the plugin or component team to approve this request.

The user proposed to be added needs to log in to Jira first, and artifactory too.


Update content list styles

Closes #4425

Adds the author avatar (with default fallback)
Shows author name when hovering the avatar (falls back to email address)
Slightly adjusts type, colour, and spacing

Wow, that is beautiful! :+1:

@jaswilli Thanks for the tips! Updated with all of them. :)

This looks good to me :+1:, nice work Paul.

Stunning!


Create K.c

adding file to repo

@all-contributors please add @Shanmuk-palnati   for code

As discussed it is not a valid Pull request. So closing it...


[Feature]: Improve navigation menu on top right

New design see figma
Add organizations and events to navigation menu on top right


Add a method to GET standalone attachments

What
Add a method to GET standalone attachments.
How
Reads an attachment from the database, returning an InputStream.
Testing
Updates unit tests.
Issues
Fixes #331.

oh also needs an update to CHANGES.md before merging.


[TE] frontend harleyjj/rca - double encode filter value to protect ag…

…ainst special characters
Depends on separate backend change to double decode the filter value

@vincentchenjl @jihaozh The PR is passing tests after the rebase


move_and_collide can Clip RigidBody2Ds

Godot version
3.4.2-stable_win64
System information
Windows 10 x64
Issue description
KinematicBody2D's move_and_collide can clip through RigidBody2Ds when moving at high speed, even if the RigidBody2Ds are barely moving. This does not happen if they're StaticBody2Ds and I don't think it's supposed to happen at all.
https://user-images.githubusercontent.com/10686700/154850075-58648da6-f54e-45f5-8906-90bc7720efe0.mp4
Steps to reproduce
Create a RigidBody2D and a KinematicBody2D that you can move quickly via move_and_collide. Move it quickly enough and it'll clip through the RigidBody2D. Move it less quickly and it won't.
Minimal reproduction project
Clipping.zip

This is absolutely expected. At these "Speeds" the body is basically no longer "moving" but teleporting. The only way to prevent that is with continuous collision detection, which can be costly to compute.

Is it expected to behave differently with StaticBody2Ds? Or should it teleport past those as well?

If you are moving faster that: Size of Object + Size of Obstacle. Collision detection will fail.

This is absolutely expected. At these "Speeds" the body is basically no longer "moving" but teleporting. The only way to prevent that is with continuous collision detection, which can be costly to compute.

I am not suggesting that RigidBody2Ds should not be expected to teleport at high speeds. The common solutions to that are to enable Continuous Collision Detection for them or switch them to KinematicBody2Ds.
I don't believe it is expected that KinematicBody2Ds should teleport when using move_and_collide. For one, they lack the option of Continuous Collision Detection (or rather I believe move_and_collide is supposed to function similarly to CCD). For another, it's very suspicious that they will clip through an essentially-unmoving RigidBody2D at high speeds but will not clip through a StaticBody2D at such speeds or even higher. This implies that move_and_collide does not teleport, else how would it have detected the collision with the StaticBody2D?

If you are moving faster than: Size of Object + Size of Obstacle. Collision detection will fail.

That is demonstrably untrue in the case of move_and_collide. Try changing the RigidBody2D in the example project's mode from Rigid to Static -- you won't be able to clip through it at any speed.

RigidBody implements CCD if you enable it, like I mentioned before. Static bodies are static, and can be optimized for. What's your point? At certain speeds, phasing is expected. That is how kinematic physics work. I can't see the body actually translating in your examples, so it is evidently too fast.

Enabling CCD has no impact on the clipping demonstrated; it's actually on and set to Cast Shape in the example project. At the very least if the solution to the problem is "enable CCD" then CCD is not working correctly.
But he expectation that KinematicBody2Ds should clip while using either test_move or move_and_collide is not well-set by the engine, its documentation, nor Internet Q&A, and I'm not convinced it should be an expectation. The expectation of fast-moving RigidBody2Ds is consistently well-set.

At certain speeds, phasing is expected. That is how kinematic physics work.

What do you mean? move_and_collide() doesn't just "teleport" the body and then check for a collision at the end. A KinematicBody2D will never, as far as I've tested, phase through another KinematicBody2D that is not moving, no matter the speed. Though it can potentially happen if both are moving - see https://github.com/godotengine/godot-proposals/issues/2332

Should it be expected that KinematicBody2Ds can phase through unmoving RigidBody2Ds?
Given that they won't clip through StaticBody2Ds or as you say other unmoving KinematicBody2Ds it feels like there's at least an opportunity for improvement if this isn't an outright bug. After all, the engine has demonstrated the potential to not clip through unmoving objects via these other types, so the collision can't be impossible to detect.
That's why I've raised the issue -- it does not feel to me like this is expected behavior, though it's easily conflated with a similar behavior that is expected: RigidBody2Ds clipping while moving at high speeds (or via the above issue, two moving objects missing each other).
If someone who works on the physics engine says this behavior is expected then I'll merely suggest it might be worth updating the documentation, but I've a suspicion people's first tendency will be to confuse this specific observation with the much more common one where the RigidBody2D is what's moving quickly.

this is essentially a duplicate of #9071 and should be closed
to the guy telling him this is expected: it is not, at least not with CCD enabled, this issue has been known for almost 4 years now.

That issue is about RigidBody2Ds moving too quickly and clipping through things. This issue is about KinematicBody2Ds moving too quickly and clipping through things.
That issue states that a RigidBody2D with CCD enabled can still clip through StaticBody2Ds. I have demonstrated that a KineticBody2D will not clip through StaticBody2Ds. This strongly suggests that they do not share the same internal movement implementation, and therefore fixing the bug in RigidBody2D's movement code will not affect the KinematicBody2D movement code.

This is absolutely expected. At these "Speeds" the body is basically no longer "moving" but teleporting. The only way to prevent that is with continuous collision detection, which can be costly to compute.

Fun fact: CCD is not even working at all :DDD