Icon and splash screen use Cordova default when app is built with PhoneGap Build

When app is built with the PhoneGap CLI, the splash screen looks like this (as defined in config.xml):

However, when the app is built with PhoneGap Build, the default Cordova splash (and icon) are used instead:

Can you describe where the app source for both came from?

Hi @chrisgriffith, sorry for the terse issue description, I had a solution in mind but wanted an issue to link it to.
The app source for both is this repository, and every app that is created by running phonegap create <path>.

This template is used by the CLI and the PhoneGap Desktop app, so adjust the asset and folder structure is not something that can easily be done. Use of either of those tools is not recommended for use with PhoneGap Build at this time.

Do I understand it correctly that this template won't work 'out of the box' when using PhoneGap Build?
This GitHub project is referenced in the PhoneGap Build Getting Started Guide.

That template is PhoneGap Build friendly. I suspect since the CLI was used, an older template might have been initially referenced somewhere along the process. I just tested creating an app with this template and it rendered correctly.

@mxro in my testing, the splash screen and icon defined in config.xml are not used when the app is built with PhoneGap Build. The app itself will work, but debugging icon and splash issues can be frustrating and time consuming.

This GitHub project is referenced in the PhoneGap Build Getting Started Guide.

This repository is indeed linked to from the guide, suggesting to me that it is intended to work with Build.

Icons and splash screens issues are usually due to incorrect paths being defined in the config.xml or not being included in the zip file.

Icons and splash screens issues are usually due to incorrect paths being defined in the config.xml or not being included in the zip file.

That is a good place to start, thank you. So is this template supposed to work 'out of the box' with PhoneGap Build (including a correct rendering of the splash screen) or changes have to be made manually?
I've tested it on an Android phone (Version 6.0) and I would get a black screen instead of a splash screen. I tried adjusting the paths in the config.xml and use slightly different tags as suggested in the PhoneGap Build Icon and Splash documentation but without success so far.
I do agree with @blefebvre that this is a bit frustrating ...

I'm experiencing just the opposite: Phonegap build set the right icons and phonegap set the default icons, also using this template.
In either case, I haven't got any of them with the splashscreen working.
I've tried what I've read here: http://stackoverflow.com/questions/25385308/phonegap-build-not-showing-splashscreen but it only works If I use the default <splash> element.

I finally fixed it! It had to do with my config.xml file.
If you're having some troubles with setting your splashscreens, see this post). Maybe It can help you as so it did to me...

@Akronix - can you be more specific?  I looked through that post, but the best I could ever get working was if I removed the density from one of the <splash> entries or had a default splash entry.  Did you actually get it to load the appropriate splash screen based on the resolution?

@tisdall siimply.... Edit your config xml via github  change preferences as your directory file. That it.next you verified your app file or use real device.


wrapped name package methods in react i18n

Description
Closes https://github.com/Shopify/quilt/issues/2681
Adds abbreviate business name method to react-i18n, removes all name related method source code from react-i18n and instead wraps imported methods from the name repo.

/snapit


chore: bump superset-ui 0.18.19

SUMMARY

bump superset-ui 0.18.19

https://github.com/apache-superset/superset-ui/pull/1406

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

closed first, we will open in the future.


[PE-D][Tester A] Adding meeting is too complex

Due to the complexity of the command the user may forget to add }} between names, in which case a more appropriate error can be thrown to remind the user to add }} between names.
I have also noticed that } or }}} both work as well so it should be mentioned in the UG.

Labels: type.FunctionalityBug severity.Medium
original: JordanChua/ped#9

Not sure why }}} and } both work? Haven't tested.

Not sure why }}} and } both work? Haven't tested.

Just tested a bit, by right "[name 1] } [name 2]" won't work as "[name 1] } [name 2]" will be considered as one entire name, which leads to ambiguity in the query and an error throwb
the input "[name 1] }}} [name 2]" (with triple } )  probably still leads to the two names being split into [name 1] and [name 2] respectively for the query, shouldn't impact the functionality of the code.

Maybe we should just add it into the UG then? Like it must be "}}}" and "}}" will not work properly? Or will be taken as a person?


delete generated Go files

I dropped a table and removed the corresponding db/query/<table>.go file. However, src/internal/db/<table>.sql.go file was not deleted. I expected it to be deleted.

Does protoc do this? I'm tempted to close this out as wontfix.

Good question, I'm not sure.

I've tested the behavior of protoc. The generated files are not deleted. I'm content to do the same.

I've tested the behavior of protoc. The generated files are not deleted. I'm content to do the same.

I just renamed a table and discovered this behavior of sqlc, could we add a note somewhere in the docs that the out folder contents are not cleared upon calling sqlc generate? (although having an optional flag to do so would be a wonderful addition)


feat(slice): add duration option

Description

add --duration option for slice verb, which make rosbag split into multiple files
add rosbag2_py_wrapper package to realize its function

Test performed
start and end time option
ros2 bag slice rosbag.db3 -o output --start-time 0 --end-time 123455678

After that
duration option
ros2 bag slice rosbag.db3 -o output --duration 10

After that, I confirmed multiple files which has 10secs data
Remarks
I made rosbag_py_wrapper based on https://github.com/ros2/rosbag2/tree/rolling/rosbag2_py.
Please check License too.

@hayato-m126 I fixed build error in humble. Could you confirm again?


Citric Acid and Stearic Acid and Sodium Stearates subscript format is incorrect

GregTech CEu Version
v2.4.0
Gregicality Multiblocks Version
v1.1.4
Gregicality Science Version
v0.0.1
Modpack Used
GregTech Expert 2
Addons Installed
No response
Environment
SP
New Worlds
Yes
Cross-Mod Interaction
No
Expected Behavior
they have subscript as a small character
Actual Behavior

Steps to Reproduce
install GCYS
Additional Information
No response

These are not GCYS materials, these are GTFO materials. This is also now fixed on GTFO's master.


Debugging is broken on latest master

Hi,
As a result of commit: baf5b7b4d55e88bad232f57adb899b03028fb3fe - De-batch native->js calls and react updates - debugging no longer works as expected when using the iOS sim with Chrome debugging enabled. Our system is getting the red box socket closed error.
Using Xcode 7.01 plus El Cap with latest node.
M

Same here. Works without Chrome attached. As soon as I Command+D > Enable Chrome Debugging I get the "socket closed" red box error.

@admmasters, @marcshilling have you guys bisected the problem to @tadeuzagallo's rev?

@martinbigio It was indeed my diff, I already shipped the fix, should be on github soon.

Fixed by https://github.com/facebook/react-native/commit/529687f9234ae9730a2660a1fee10ce45319c3fb

Was just about to close this as well, thanks!


Issue #162 - CODEOWENERS

This pull request updates the CODEOWNERS file to reflect the changes in GhostBSD GitHub Members levels.

Related to https://github.com/ghostbsd/issues/issues/162


Rename operation on methods or say record fields result in full replace of dot syntax path with renamed symbol

Rename operation on methods or say record fields result in full replace of dot syntax path with renamed symbol.
Renaming currently replaces symbols like this:
type Foo = { BeforeRename: int }

let usage (x: Foo) =
   x.BeforeRename

Renaming BeforeRename to AfterRename breaks every location that uses it through dot syntax.
See example:
type Foo = { AfterRename: int }

let usage (x: Foo) =
   AfterRename // Error here

This basically happens with every symbol that could be accessed through dot syntax and has been happening for quite some months, surprised I couldn't find an open issue already.

Same thing occurs with modules
module Oof =
    let dooter () =
        "asdf"

module Foo =
    let doTheFoo() =
        printfn "%s" (Oof.dooter())

Renaming to dewter
module Oof =
    let dewter () =
        "asdf"

module Foo =
    let doTheFoo() =
        printfn "%s" (dewter())

This also happens with any functions in modules where you are accessing them with a prefix.
module Common =
    let myCommonFunction param =
        ...

// Somewhere else
let result = Common.myCommonFunction param

// After rename refactoring myCommonFunction to commonFunction
let result = commonFunction // <- Should be Common.commonFunction

Definitely very frustrating.

I haven't really taken a look at Ionide's code before, but if anyone is familiar, is this the entry point I'd be looking at to fix this?
https://github.com/ionide/ionide-vscode-fsharp/blob/master/src/Components/Rename.fs

@weebs The file you linked if the one responsible to edit the file indeed. However, it calling LanguageService.symbolUseProject in order to get all the symbols locations to rename.
And so the logic to find the symbols and their location is implements in FSAC.
I think the entry point for FSAC is here

Symbol finding logic seems fine - the whole qualified name is a symbol. So I think it should be fixed on the Ionide side - rename implementation should handle symbols containing .

That's probably my fault.
https://github.com/ionide/ionide-vscode-fsharp/pull/890/files
I tried to fix renaming with ``, but also broke the symbols with .

Fixed by c6fa8e5dea4f8e2171aaa897956dd99513dd7697


Add support for image composition

Allow to create OCI layers on top of an existing OCI KIWI based image description
layers can be used in two ways:

natively via the docker/podman build and a Dockerfile. As users can do this already there is nothing we need to add
via kiwi from so called derived images. This feature already exists in kiwi and can be utilized via the oci-build implementation #18

Delta and Layering has been added to kiwi (https://github.com/OSInside/kiwi/pull/2252) and oci-pilot (provision)


Syft SBOMs support dependency hierarchies.

What would you like to be added:
When I generate SBOMs from Syft (in either CycloneDX or SPDX), the resulting SBOM files don't show the dependency hierarchies (i.e. the tree relationships between libraries) that other generators do (like the open-sbom-generator).
I want/need to be able to see, for a given vulnerable library, how it was introduced into an asset.
Ex:

Dependency 1 (has a CVE)

introduced by dep 2

introduced by dep 3

introduced by dep 4, which is a top-level library / root node.

Why is this needed:
This allows me to tell developers what libraries they specifically need to upgrade/replace in order to remediate vulns or other issues introduced.
Additional context:

This is a duplicate of #572.

Indeed it's a dup -- I'll close this one. Shout out if there is extra context that is not capture in the original issue.


JDK_JAVA_OPTIONS picked up twice

When using the JDK_JAVA_OPTIONS environment variable it's picked up twice.
$ echo 'public class Test { public static void main(String[] args) { System.out.println("Should pick once"); } }' > Test.java
$ docker run --rm -it -v $(pwd)/Test.java:/Test.java:Z -e JDK_JAVA_OPTIONS="-Dsomehow=duplicated" eclipse-temurin:17.0.1_12-jdk-alpine java Test.java
NOTE: Picked up JDK_JAVA_OPTIONS: -Dsomehow=duplicated
NOTE: Picked up JDK_JAVA_OPTIONS: -Dsomehow=duplicated
Should pick once

Visible also by running an app in the background and doing
$ jps -lvm
6 jdk.compiler/com.sun.tools.javac.launcher.Main Test.java -Dsomehow=duplicated -Dsomehow=duplicated --add-modules=ALL-DEFAULT

Also visible from JMX.

duplicated as in https://github.com/adoptium/adoptium-support/issues/303 ?

i think this is because we set JAVA_TOOL_OPTIONS in our entrypoint.sh:
https://github.com/adoptium/containers/blob/e78d85595512fba851c6d9e1eab37e1743557d56/17/jdk/alpine/entrypoint.sh#L48
Running your test with JAVA_TOOL_OPTIONS instead of JDK_JAVA_OPTIONS seems to prevent this from happening:
docker run --rm -it -v $(pwd)/Test.java:/Test.java:Z -e JAVA_TOOL_OPTIONS="-Dsomehow=duplicated" eclipse-temurin:17-jdk-alpine java Test.java

Picked up JAVA_TOOL_OPTIONS: -Dsomehow=duplicated
Should pick once


Reimplement lines

This addresses both trailing newline and DOS endings issues.
I also added a couple of tests. I haven't tested the performance, though.

I just noticed that there's a .travis.yml. If you decide to merge the tests, they should be probably be added to travis, too.


Expose Node.js function for running dev build in watch mode

Just an idea, feel free to discard if you disagree.
If goldpage exposed a Node.js function that ran the dev build in watch mode, it would mean users of the library wouldn't have to run goldpage dev on the command line. I prefer having control of starting the server myself instead of having goldpage start the server.
Here's what that could look like:
import { ssr, dev } from "goldpage";
import express from "express";

const app = express();
app.use(ssr.express);

// dev build with hot-reloading
if (process.env.NODE_ENV !== "production") {
  dev();
}

app.listen(3000);

Thoughts?

Would love this but it's problematic when you want to auto-restart your server. E.g. when doing nodemon ./path/to/server.js — whenever the server is auto-reloaded it will terminate require('goldpage').dev().

Would love this but it's problematic when you want to auto-restart your server. E.g. when doing nodemon ./path/to/server.js — whenever the server is auto-reloaded it will terminate require('goldpage').dev().

Now that I know that I can just run goldpage dev, I’ll probably create a separate npm script for the build and run it in parallel with my server.


AWS::Serverless::Api deployment resource is not generated on Sub'ed Ref change

Deploy the attached Cloudformation template, see that visiting the API GW address shows the text in the RandomParameter CF parameter.
Update the stack and change the RandomParameter value, see that a new Deployment resource is not created by the Serverless transform and see that visiting the API GW address shows the previous value of RandomParameter rather than the expected current one.

Thinking about this in the context of my own custom transform I get why detecting the change in the ref is difficult in a transform, with it being a layer removed, but the UX confused me, my VTL changed so why didn't it deploy was my initial reaction.
I suspect this suggestion won't fly but I'm making it anyway: could you generate a new Deployment on every transform regardless of if the Api resource has changed or not? It feels like a safe choice, worst case it's a noop deployment, best case it means !Refs and !Subs and !Ifs within the transformed resource work intuitively.
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31

Parameters:
  RandomParameter:
    Type: String

Resources:
  Api:
    Type: AWS::Serverless::Api
    Properties:
      StageName: Prod
      DefinitionBody:
        swagger: '2.0'
        schemes:
        - https
        paths:
          "/":
            get:
              consumes:
              - application/json
              produces:
              - text/html
              responses:
                '200':
                  description: Successful operation
                  headers:
                    Content-Type:
                      type: string
              x-amazon-apigateway-integration:
                responses:
                  default:
                    statusCode: '200'
                    responseParameters:
                      method.response.header.Content-Type: "'text/html'"
                    responseTemplates:
                      text/html: !Sub |-
                        <html>
                            <body>
                                <h1>${RandomParameter}</h1>
                            </body>
                        </html>
                passthroughBehavior: when_no_match
                requestTemplates:
                  application/json: '{"statusCode": 200}'
                type: mock

Outputs:
  Url:
    Value: !Sub https://${Api}.execute-api.${AWS::Region}.amazonaws.com/Prod

This is similar to issue #479. SAM only generates a new API Gateway Deployment if the swagger definition changes. If SAM uses an intrinsic function inside the swagger definition, the definition is not seen as changed, even if the value returned by the intrinsic function changes.
One way to workaround this (and force redeployment) is to make a change in the swagger.
This isn't ideal, and we are aware of this issue. Please +1 on #479 to help prioritize this issue. Thanks!


Implemented "readOnly" property (mobile friendly feature)

Added the property "readOnly", this is used to block user input and prevent keyboard opening on mobile phones.
Ofcourse default value is false and the input is enabled on readOnly true.
This feature was requested some time ago, by other guys https://github.com/brianreavis/selectize.js/issues/110 today i've implemented this feature because I want to use this (fantastic) library for my project and this feature is essential.

Coverage decreased (-0.06%) to 83.13% when pulling<PHONE_NUMBER>363bf63968eb837fb3de0c6c939318 on AndreaCatania:master into 3dc07d40047cd98de8a8f8beacca06a73970139d on brianreavis:master.

What's wrong?

Coverage decreased (-0.13%) to 83.05% when pulling dfb3174325a0c1c3060c42e2ef9ac95d162300c3 on AndreaCatania:master into 3dc07d40047cd98de8a8f8beacca06a73970139d on brianreavis:master.

Why coverage fails? What's wrong in the code? I've tried in local and works fine.

Coverage increased (+0.03%) to 83.22% when pulling 2d56b4cb7718d33eeb35e1b9dc1ee04775d8a6d7 on AndreaCatania:master into 3dc07d40047cd98de8a8f8beacca06a73970139d on brianreavis:master.

With this coverage i'm forced to write a bad code instead of one "IF" I had to write two "IF"... absolutely useless

Coverage increased (+0.03%) to 83.22% when pulling ddecefed6399fcc87cb0d50e754544977f3072f5 on AndreaCatania:master into 3dc07d40047cd98de8a8f8beacca06a73970139d on brianreavis:master.

:+1:

+1

:+1:

+1 This really fixes undesired behaviour on touch devices where keyboard widget shows up when user touches 'selectized select. Thank you.

:+1:

This PR probably can't be accepted as is.
README:

When issuing a pull request, please exclude changes in the "dist" folder to avoid merge conflicts.

Would you please remove changes in dist, as stated?
Can you tell me why we're not using attr 'required' instead of adding an option?
Can you add tests?


chore(package): update npm-pkgbuild to version 6.6.2

Coverage decreased (-56.5%) to 33.78% when pulling 6d221763cd4f08413c9ed6501d60c54c37d4c87a on greenkeeper/npm-pkgbuild-6.6.2 into 51549d37e66e6502111ae39a58679d055b76ada6 on master.


feat: making not found better

changed not found to use params instead of env vars to test that out
added temperature to the open ai call
run two separate open ai calls, one for url selection, one for content gen
moved init method to init file
updated notfound control to support array of returned links

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


Handle a state created due to race condition between RetentionManager and segment commit, resulting in no consuming segments for the partition

Segment commit takes place in 3 steps:

mark committing segment metadata to DONE
create new segment metadata to IN_PROGRESS
update ideal state with segment state to ONLINE and new segment state to CONSUMING

The RetentionManager checks for segments which have metadata present but no entry in ideal state. If the RetentionManager happens to check between steps 2 and 3 above, it will mark the newly created segment for deletion.
The fix for this is to make retrntion manager not pick segments that are new (provided 5 days buffer: https://github.com/linkedin/pinot/pull/2890)
Additionally, the ValidationManager should be able to detect and recover from sucha a scenario
In this PR, a check is put in place to look for all segments ONLINE in ideal state for latest segment, and metadata being DONE. In such a scenario, a new metadata is created IN_PROGRESS and new segment is created in ideal state CONSUMING. We make sure that we don't correct segments that are too soon to correct

Codecov Report

Merging #2891 into master will increase coverage by 23.46%.
The diff coverage is 77.41%.

@@             Coverage Diff             @@
##           master    #2891       +/-   ##
===========================================
+ Coverage   45.73%   69.19%   +23.46%
===========================================
  Files         912      912
  Lines       43651    43658        +7
  Branches     5931     5932        +1
===========================================
+ Hits        19962    30211    +10249
+ Misses      22008    11418    -10590
- Partials     1681     2029      +348

Impacted Files
Coverage Δ

.../core/realtime/PinotLLCRealtimeSegmentManager.java
73.63% <77.41%> (+17.01%)
:arrow_up:

.../impl/dictionary/FloatOnHeapMutableDictionary.java
86.66% <0%> (-6.67%)
:arrow_down:

...impl/dictionary/FloatOffHeapMutableDictionary.java
85.45% <0%> (-5.46%)
:arrow_down:

...mpl/dictionary/DoubleOffHeapMutableDictionary.java
67.27% <0%> (-1.82%)
:arrow_down:

...ata/manager/realtime/RealtimeTableDataManager.java
39.55% <0%> (-1.5%)
:arrow_down:

...lix/core/realtime/PinotRealtimeSegmentManager.java
73.54% <0%> (-1.06%)
:arrow_down:

.../broker/routing/HelixExternalViewBasedRouting.java
90.33% <0%> (-0.67%)
:arrow_down:

...e/operator/dociditerators/BitmapDocIdIterator.java
60.71% <0%> (ø)
:arrow_up:

...e/operator/dociditerators/SortedDocIdIterator.java
59.45% <0%> (ø)
:arrow_up:

...ore/realtime/impl/kafka/SimpleConsumerWrapper.java
62.64% <0%> (+0.38%)
:arrow_up:

... and 480 more

Continue to review full report at Codecov.

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

should we revisit the purpose of validateLLCSegments and the scenarios it is trying to handle. Do we know the reason a segment gets into an invalid state? validateLLCSegments has become too complicated.
Another orthogonal question. This bug seems to have existed for a long time, what is the change that surfaced this issue.

Yes the bug existed for a long time. No change in particular surfaced the issue. It's just a very rare scenario I think, where the commitSegment steps and retentionManager steps exactly align

The following sequence of events can cause the bug:

server A sent a request to complete Segment S1 (realtime) to Controller.
Controller marked metadata for S1 as Done
Controller created new metadata for S2 and marked IN-PROGRESS
Retntion manager came along and looked at IS and decided S2 needs to be deleted since it has metadata but not in idealstate.
Controller changed Idealstate to mark S1 ONLINE and S2 CONSUMING (single change)
Retention manager deleted S2.

steps 1 thorugh 5 has to have happened in the same ms in that order
or probably a few ms
The correction logic in the controller worked for this case until PR #2721 , when the bug was introduced to NOT handle the case when there are no consuming segments.
Until then the race condition probably existed, but things auto-corrected, so we did not see it.


important Bug report

welcome and leave work only in first server you set doesn't work on multi discord server And (LeaveDm doesn't  work)

Same

Same Here

Idk why
But i will check that once i got the time for fixing all issues.

i'm  personally using it in few servers, all working

It was working, while bot was on less than 10 guilds, when it start have more (now 22) it stop working

My notebook, so it isn't problem in host, at least my fork

not host problems beacuse my bot host is vps

when the last activity is guild leave, not join, all works fine

when the last activity is guild leave, not join, all works fine

but welcome 2 Work fine
idk know why channel 1 DOSEN't work

same
but if bot leave guild, after that it works, idk how long it will be, but...

same but if bot leave guild, after that it works, idk how long it will be, but...

you find any solution ?

nope

Now if my bot join guild, i adding to 1 server and kick from, and it works, but i still waiting for Tomato

same

guys there is any sol ?

nope)

BTW This correctly works on mongo version

nope same prob with mongo version just work only in the first server but others servers dosent work

hmm, all works in my


Speed improvement suggestion: array resizing

Example:
◌ ⍥(⊂⚂)1e5 []

Obviously that is not how you would write code for the same result. But sometimes, a join in a do/repeat is the simplest way to accomplish something (such as generating all permutations of a list that satisfy a certain condition). When I run the above with uiua run 'file.ua' --time-instrs | grep ⊂, the time taken seems to increase proportionally to the current length of the array on every single call.
# first few lines
  ⏲    0.01ms - ⊂
  ⏲    0.00ms - ⊂
  ⏲    0.00ms - ⊂
# last few lines
  ⏲    0.36ms - ⊂
  ⏲    0.36ms - ⊂
  ⏲    0.40ms - ⊂

How do you feel about having the backing Rust array pre-allocate higher amounts (e.g. instead of "exact fit", leave some head-room up to the next power of two? Ruby does something similar.) when an array is too small to fit its next element?

I agree this should be fixed.
If you join to the end instead of the front, does the extra time go away?

If you join to the end instead of the front, does the extra time go away?

I did some testing and yes, joining to the end has no extra cost.
I'm going to push a change that fixes joining to the front.
It will still technically be O(n), since all the existing elements have to get shifted over. But in my testing, it's 1 or 2 orders of magnitude faster since there is no longer an allocator call on ever join.

Fixed in 67634f73ca02bd5470.
This fix only applies to join, but there may be opportunities for other similar optimizations.

Super cool, thanks!! And I'll take care to join flip when in a loop.
BTW, if there is still a known performance cost for prepending instead of appending, I'd also recommend the docs call that out.
Thanks again for the lightning fix.


Debezium server is failing to create a table because of an invalid table identifier.

hi @ismailsimsek ,
we move further actually from that last error(https://github.com/memiiso/debezium-server-iceberg/issues/341), now we have done all the practice we Chris Cranford (Naros)'s blog and debezium blog has said all the privileges from oracle database but without kafka now we are getting issue like this (please check the attachment) where the error message in the log indicates that the Debezium server is failing to create a table due to an invalid table identifier: apacheiceberg.debeziumcdc_aws_DNT_TEST. This error occurs while processing change data capture (CDC) events using the Iceberg sink connector.
we hope that we'll finds solution for this time.
Thank you,
Dhruv Mevada

duplicate of #369
@mevadadhruv please don't open duplicate ttickets


Update Method Observer to 1.0.1

Changelog:
add checks to connection testing variables
add debug check to handleResponse
add valid url check to onItemContainerChanged before sending http request
add test response null check
add internal server error check
remove unused onActorDeath event
remove unused overlayManager
remove logging of json body
let ::test reset badResponse count

You'll need to rebase/merge plugin-hub's master branch into this branch to resolve the conflict here


GoTestCompile

vim-go offers nice command GoTestCompile to only compile current file and check if it builds. Implemented as:
https://github.com/fatih/vim-go/blob/c1fc27a5ad95589558f3083b0ece9d4d8f74ab18/ftplugin/go/commands.vim#L50
which calls go test with -c flag. It is very useful.
I've tried same thing with go.nvim by calling GoTest -c but got error cannot use -c flag with multiple packages
Is there any other way that I can only check if my files compile?

Added -c option to GoTest

Looks like the command works, thanks for quick fix, it also opens quickfix window on errors, but output is messed up.
On every line it prepends || so jumping to file:line error location is not working as expected.
Also for a simple case when only main.go exists command should finish without reporting that no test files exist (if no compile errors).

I updated efm and it should work now.

Its working.
Just two minor things.

Is there a way to jump to first error if compilation fails?
How can I avoid opening quickfix if there are no errors?


CI/CD to push Scrapers Docker Image to AWS

As a...
member of the development team
Wants to...
automatically push changes to the Scrapers Image to AWS
So that...
save time and focus on other aspects of development
Acceptance Criteria

[ ] Create a GitHub action that automatically pushes the Docker Image to AWS ECR

Resources
No response

Found an action on Github Marketplace


missing package attribute on intent

when sending an intent its possible to add a package to specify which intentReceiver should handle it to circumvent the chooser at the bottom im not entirely certain if ios has a similar feature but i feel they should

I made a pull request for the android and dart part of this


Create OSMigrator

OSMigrator is a tool for openstack migration, with a more flushed out CLI.

+1 after it passes testing.


Remove External Table Backwards Compatibility Options

Which issue does this PR close?
Closes #8547 .
Rationale for this change
See issue for details
What changes are included in this PR?
Options single_file, append_new_files  and create_local_path  are removed already. This is to remove the Backwards Compatibility so that providing these options will not work now.
Are these changes tested?
Yes
Are there any user-facing changes?
No

Thanks again @yyy1000


Add a self contained fpm layer

The FPM layer needs a lambda function which has a installed composer autoloader. It's not possible to just write a small function inside the AWS console itself. A self contained FPM layer can be bootstrapped without any autoloading mechanism inside the function itself.
I opened this PR as a discussion base as it's not yet complete. It doesn't have the functionality to publish the layer. It's maybe also better to move this in the FPM layer itself.

Thank you for the pull request, this is something that we need to consider indeed.
I don't think however that we need to create a separate FPM layer for this. We could update the existing php-fpm layer directly.

I checked and we have the same problem/need in the console layer.
One disadvantage of this approach as well is that it will increase the size of the layer (in short Bref and its dependencies will be installed twice on the Lambda).
Another solution could be to introduce an environment variable, e.g. BREF_AUTOLOAD_FILE, that users could define and point it to their custom vendor/autoload.php file. By default it would look in /var/task, but if you put your dependencies in a custom directory it could be customized with this variable.
The related issue is #226 (ping @faizanakram99 who reported it)

The size is increased at least for the fpm layer by about 2mb. As it was before above 30mb this adds not that much.
Will change the PR to directly use the FPM layer

I checked and we have the same problem/need in the console layer.
One disadvantage of this approach as well is that it will increase the size of the layer (in short Bref and its dependencies will be installed twice on the Lambda).
Another solution could be to introduce an environment variable, e.g. BREF_AUTOLOAD_FILE, that users could define and point it to their custom vendor/autoload.php file. By default it would look in /var/task, but if you put your dependencies in a custom directory it could be customized with this variable.
The related issue is #226 (ping @faizanakram99 who reported it)

See #232 as a possible solution to this which avoids completely the autoloading issue


minithumbnail size

I've noticed that width/height values for minithumbnail (at least for photos) are mixed up, consider logs from TDLib:
[ 3][t 4][1572600137.539397240][Td.cpp:4646][#1][!Td][&td_requests]	Sending update: updateChatLastMessage {
  chat_id = xxxx
  last_message = message {
    id =<PHONE_NUMBER>12
    sender_user_id = xxxx
    chat_id = xxxx
    sending_state = null
    is_outgoing = true
    can_be_edited = true
    can_be_forwarded = true
    can_be_deleted_only_for_self = true
    can_be_deleted_for_all_users = false
    is_channel_post = false
    contains_unread_mention = false
    date =<PHONE_NUMBER>
    edit_date = 0
    forward_info = null
    reply_to_message_id = 0
    ttl = 0
    ttl_expires_in = 0.000000
    via_bot_user_id = 0
    author_signature = ""
    views = 0
    media_album_id = 0
    content = messagePhoto {
      photo = photo {
        has_stickers = false
        minithumbnail = minithumbnail {
          width = 20
          height = 40
          data = bytes [659] { FF D8 FF E0 00 10 4A 46 49 46 00 01 01 00 00 01 00 01 00 00 FF DB 00 43 00 28 1C 1E 23 1E 19 28 23 21 23 2D 2B 28 30 3C 64 41 3C 37 37 3C 7B 58 5D 49 64 91 80 99 96 8F 80 8C 8A A0 B4 E6 C3 A0 ...}
        }
        sizes = vector[2] {
          photoSize {
            type = "m"
            photo = file {
              id = 10960
              size = 2050
              expected_size = 2050
              local = localFile {
                path = ""
                can_be_downloaded = true
                can_be_deleted = false
                is_downloading_active = false
                is_downloading_completed = false
                download_offset = 0
                downloaded_prefix_size = 0
                downloaded_size = 0
              }
              remote = remoteFile {
                id = "AgADAgADZ6wxG6X84Elf__H5t4xE_MPcug8ABAEAAwIAA20AA0W4BAABFgQ"
                is_uploading_active = false
                is_uploading_completed = true
                uploaded_size = 2050
              }
            }
            width = 200
            height = 100
          }
          photoSize {
            type = "i"
            photo = file {
              id = 10961
              size = 2293
              expected_size = 2293
              local = localFile {
                path = "/home/user/Pictures/200x100.png"
                can_be_downloaded = false
                can_be_deleted = false
                is_downloading_active = false
                is_downloading_completed = true
                download_offset = 0
                downloaded_prefix_size = 2293
                downloaded_size = 2293
              }
              remote = remoteFile {
                id = "AgAD_v___2esMRul_OBJX__x-beMRPwACAEAAwIAA2kABxYE"
                is_uploading_active = false
                is_uploading_completed = true
                uploaded_size = 2293
              }
            }
            width = 200
            height = 100
          }
        }
      }
      caption = formattedText {
        text = ""
        entities = vector[0] {
        }
      }
      is_secret = false
    }
    reply_markup = null
  }
  order =<PHONE_NUMBER>512000002
}

image's size is 200x100, but size of the minithumbnail is 20x40, looks invalid
Thanks

actual image stored in minithumbnail.data has 40x20 size

Thanks, @zevlg! Fixed in https://github.com/tdlib/td/commit/afca63a4f43531058a079e91eb5c81f54ad744b5.


Support references to foreign types

This was breaking eurydice

I integrated that into https://github.com/AeneasVerif/charon/pull/308 to save me one all-projects update.


 does not work for nested routes

Environment
- Operating System: Darwin
- Node Version:     v21.2.0
- Nuxt Version:     3.10.1
- CLI Version:      3.10.0
- Nitro Version:    2.8.1
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      devtools, css, modules, runtimeConfig, image, build, i18n, ignore, nitro, routeRules, security, vite
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-5pbsy2?file=pages%2Findex.vue,layouts%2Fdefault.vue
Describe the bug
<NuxtLinkLocale> does not seem to work with a nested custom path.
For example:
Works:
<NuxtLinkLocale to="/about">about</NuxtLinkLocale>

Does not work:
<NuxtLinkLocale to="/services/advanced">advanced</NuxtLinkLocale>

Additional context
Maybe it is actually not a bug but  is missing the name prop
Logs
No response

Added a PR that should support using name

Since you're translating the routes /services/advanced (and other routes) don't exist, you can view the paths using devtools to confirm this.
You can pass the route name to the to prop instead of a path, same for localePath:
<NuxtLinkLocale to="services-advanced">Link</NuxtLinkLocale>

or
localePath('services-advanced')

Wow this actually works. So my PR is not needed. I didnt know it is workign because it is documented to use localePath({ name: 'about' })

I understand it's a bit unclear, feel free to open a PR to expand the docs instead! 😄

Made a PR to update the docs :)

Thanks!

@BobbieGoede How do named routes work with dynamic routes?
E.g. from you website:
pages/
├── blog/
├──── [date]/
├────── [slug].vue

How can I use this with localePath() or <NuxtLinkLocale>? I will update the docs when I know how it works :D

@BobbieGoede


Fix for local development.

Prevent the following issue, e.g. locally:
SSL certificate problem: unable to get local issuer certificate

which is a curl issue with SSL
Also fixed wrong doc blocks.

Done :)

@nkt All good?

ping


Fix StringInterpolationProtocol validation crasher

Some old circularity-breaking code caused an unexpected null type, which led to crashes in the decl checker when trying to check that an appendInterpolation method in a different file would satisfy the informal requirement for one in a StringInterpolationProtocol conformer. This code appears to now be unnecessary, so this commit removes it. Fixes rdar://problem/55864759.

@swift-ci please smoke test


Skipping regular workflows in PR created for testing

#974  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


too much recursion when calling a custom transition

An example is worth a thousand words so I put together a reproduction:
https://codesandbox.io/s/microstates-jgdhu
I sum up the issue in the comments there but basically calling a custom transition on a microstate is causing an infinite recursion error. I think because the action in question is still pointing to a previous revision of the microstate. But I'm not sure how to avoid this happening or if Glimmer should have known to re-compute the action when the state was updated?

To be more explicit in case the code sandbox is unavailable, given the following setup:
https://gist.github.com/vitch/d8edb1b5d4895daf944cf5f086454d28
Where tabManager is {{#let (state (type "tab-manager") this.model) as |tabManager|}} the following code works once:
onclick={{action tabManager.activateTab tab}}
But running it a second time fails - I think because tabManager in the action is still pointing to the original instance of the microstate while it should have been updated to the new microstate...


[v0.13.x] Utilizing the parameterized drain timeout value

In a previous PR (#1722) I had attempted to stop node drainer scheduling on cordoned nodes once the timeout had elapsed (300s/5m). This is beneficial to me as otherwise nodeDrainer tries to redeploy itself onto the node after the 5 minutes have elapsed, and goes into a restart loop as kubelet is preventing things from being scheduled. When this happens our alerts go off.
This proved more difficult than planned, and I can not think of any other way to do so than placing a taint on all nodes that the daemonset does not have a toleration for. This is IMO not feasible and way too heavyweight.
We already have drainTimeout specified here in cluster.yml so it makes sense to use this value in the drain command also. This way I can increase the timeout allowing the node to drain and terminate within the allotted time.

Codecov Report

Merging #1732 into v0.13.x will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           v0.13.x    #1732   +/-   ##
========================================
  Coverage    25.28%   25.28%
========================================
  Files           98       98
  Lines         5087     5087
========================================
  Hits          1286     1286
  Misses        3659     3659
  Partials       142      142

Continue to review full report at Codecov.

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


Fix copyright year from 2016ff to 2016 - 2023 since there were recent changes

Happy to merge this. If you agree, @jspaaks, please feel free to push the button.

OK, will do, although I think legally speaking it's not needed to do either 2016ff or 2016-2023, just 2016 would suffice (for copyright, for license the year doesn't matter anyway)


Clarify markup details in the documentation

This makes explicit the fact that:

A markup-defined list is tight iff its items are separated using a blank line.
Markup-defined text is a block iff three backticks are used.

Thanks!


Add arianv and learvnoverpass

As I see it, https://github.com/Secretmapper/arianv isn't a link to the Hugo source (it is a link to the generated HTML). It's fine if you do not want to show off the source, but then the source link should be removed.

Looks like I accidentally linked it to the gh-pages branch! Fixed now!

Merged and live soon.


Multi GPU

Hi how to use multi gpu for inference. Thanks

just turn cache_examples = False, then you can run this on a single gpu


Old eslint version referenced in npm-published v1.5.0

Version 1.5.0, which is published in the global npm-repository (https://www.npmjs.com/package/plato), has an old eslint version referenced (^0.7.4). This makes plato unpossible to use with current versions of eslint. Is there a way to publish a new version of plato, with a new eslint version referenced (like in master)?
Thx!

Ran into this as well, looks like more dependancies are out of date: https://www.versioneye.com/nodejs/plato/1.5.0
The version of fs-extra is so old, that is it incompatible with newer versions of Node.
I also wonder about Plato version 1.5.0 being availabel on NPM, while if I look under Releases in this repository on gitHub, the latest release is v1.2.1, with 3 newer tags going up to v1.4.0. No mention of a v1.5.0 in this repo at all. Wondering what is actually published on NPM

Hi Guys, (The Maintainers)
Could you please drop a comment here with an ETA on proposed resolution?
It's getting a quite important on some projects as ESLint is at v2.11.1
Thanks a lot!

Hi Guys,
are there any plans for that task?
Thanks!

Sorry all, haven't been on top of github issues for some time. This project is (obviously) pretty much unmaintained right now and could use both someone to keep v1 alive (with PRs like this) and someone to advance it to modern best practices in a v2.
Any takers?


Ringing event does not trigger

I updated a bunch of stuff on my raspberry yesterday, so not totally sure if it was the update of this adapter.
But since yesterday, the ringing sensor event does not trigger anymore (as it seems). My scripts are still there, but when I ring the bell, the scripts do not trigger.
Any idea? Is it tested that the ringing event should work with the latest version?
Thanks for this amazing adapter

Set the adapter in debug mode and check that the push notifications arrive. If they do not arrive, check in the Eufy app that you have enabled them for ringing.

stale


[Feat] Enable dynamic filter

Description
This PR introduces dynamic filters for the following selectors (so, all Vizro selectors except vm.DatePicker):
vm.Dropdown, vm.RadioItems, vm.Checklist, vm.Slider and vm.RangeSlider
You can test the feature by altering values in the scratch_dev/data.yaml (in the way that's described in the comment) and running the scratch_dev/app.py.
TODOs:
This PR TODOs:

[x] - Improve the UI of the dynamic placeholder -> https://github.com/mckinsey/vizro/pull/879/commits/86171e0f4799a412c8c1d8818d237f3b938b2eea
[x] - Unit tests -> db017a2acc606a6691419f86f300578777cd6d5a
[x] - Documentation -> https://github.com/mckinsey/vizro/pull/891

This or next PR TODOs (we should decide it):

[ ] - Support dynamic for the vm.DatePicker. (Maybe it's better to wait for the dash persistence bugfix as persistence doesn't work for the vm.DatePicker even on the main branch)

Next PRs:

[ ] - Enhance the default selector.value handling for new users. There are a few cases marked with 🟠 in this Issue -> https://github.com/McK-Internal/vizro-internal/issues/1356. There are two inconsistencies listed at the bottom of the Issue description. This TODO points to the second inconsistency.
[ ] - Introduce "Universal Vizro placeholder component" -> https://github.com/McK-Internal/vizro-internal/issues/1307
[ ] - Fix the multi=False vm.Dropdown dynamic selector bug when the value is cleared. This will be solved when Vizro universal placeholder component become introduced.
[ ] - Enable dynamic filter to work with the empty data_frame.
[ ] - Propagate data_frame Parameter default values from the model_manager into the DM._multi_load() that's called from the vm.Filter.pre_build(). -> PoC can be found in the comment.
[ ] - Implement "Select ALL" for the multi=True categorical selectors.
[ ] - Implement "Select the entire range" for the multi=True numerical selectors.
[ ] - Enhance filter.build UI for the returned object. -> https://github.com/mckinsey/vizro/pull/879#discussion_r1846283227,   https://github.com/mckinsey/vizro/pull/879#discussion_r1846289738

References:

Miro board link
poc branch for testing dash persistence mechanism -> https://github.com/mckinsey/vizro/tree/poc/dynamic-filter
poc branch where the default selector value for a the new user is aligned with new dynamic min/max https://github.com/mckinsey/vizro/tree/feat/dynamic-filter-slider-support-for-new-user - This improvement can wait until dash persistence bug is fixed.

Open questions:

How to enable dynamic Parameters? Should we allow, for example, the "options" property of a categorical parameter selector to be a function that dynamically calculates and returns new options?
How to enable a dynamic filter to be targeted by any predefined action? For example the parameter_action target. Or like this: update_figures(targets=[”filter_1_id”])
What exactly is a new way of dash persistence handling we expect (this fix will be implemented by us)?
If we introduce the data_frame property for the vm.Filter component, and if the data_frame Parameters change the targeting form to data_manager_key.function_argument, does is mean that our dynamic Filters could be handled in a same way as any other dynamic figure components?

Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
I have not referenced individuals, products or companies in any commits, directly or indirectly.
I have not added data or restricted code in any commits, directly or indirectly.

This or next PR TODOs (we should decide it):

[ ]  - Support dynamic for the vm.DatePicker. (Maybe it's better to wait for the dash persistence bugfix as persistence doesn't work for the vm.DatePicker even on the main branch)

Definitely not urgent. Let's wait for this and fix https://github.com/plotly/dash/issues/2678 first.

Next PRs:

[ ]  - Enhance the default selector.value handling for new users. There are a few cases marked with 🟠 in this Issue -> Fix default value for dynamic controls McK-Internal/vizro-internal#1356. There are two inconsistencies listed at the bottom of the Issue description. This TODO points to the second inconsistency.
[ ]  - Introduce "Universal Vizro placeholder component" -> Add universal Vizro placeholder component to all dynamic components McK-Internal/vizro-internal#1307
[ ]  - Fix the multi=False vm.Dropdown dynamic selector bug when the value is cleared. This will be solved when Vizro universal placeholder component become introduced.

How many of these will still be problems once we fix https://github.com/plotly/dash/issues/2678?

[ ]  - Enable dynamic filter to work with the empty data_frame.

Good idea - let's discuss how this works now and how it should work.

[ ]  - Propagate data_frame Parameter default values from the model_manager into the DM._multi_load() that's called from the vm.Filter.pre_build(). -> PoC can be found in the comment.

Added to the comment there but basically let's leave as a TODO and open a ticket. Not urgent.

[ ]  - Implement "Select ALL" for the multi=True categorical selectors.

Would love to do this soon (like by end of year if possible).

[ ]  - Implement "Select the entire range" for the multi=True numerical selectors.

Not as high priority - let's make a ticket and forget for now.

Open questions:

How to enable dynamic Parameters? Should we allow, for example, the "options" property of a categorical parameter selector to be a function that dynamically calculates and returns new options?

Good question but I think not super high priority unless we have an immediate use for it.

How to enable a dynamic filter to be targeted by any predefined action? For example the parameter_action target. Or like this: update_figures(targets=[”filter_1_id”])

Very good question and presumably required for us to get DFPs to update filters without reloading the page? So this one needs to be worked out soon.

What exactly is a new way of dash persistence handling we expect (this fix will be implemented by us)?

Let's discuss but I think basically the "common sense" way that we initially expected things to work.

If we introduce the data_frame property for the vm.Filter component, and if the data_frame Parameters change the targeting form to data_manager_key.function_argument, does is mean that our dynamic Filters could be handled in a same way as any other dynamic figure components?

Not sure I understand this, please could you explain?

Basically I think roughly ordered priorities are:

Finish this PR
Fix https://github.com/plotly/dash/issues/2678
Tidy our code, see what remaining cases remain to fix
DFP to update filters without reloading page
@antonymilne completes some current work coming from #363 on class-based action and refactoring
Possibly https://github.com/mckinsey/vizro/pull/880, not sure whether I want to do it yet though
Implement "Select ALL" for the multi=True categorical selectors.
wdyt?

@petar-qb still working on the review, but let me update this post as I proceed so you know where things stand.
985ec4c: very small code changes that should be uncontroversial. Things with AM comment are for your information now and can be deleted once you looked at them. AM questions would be good to answer.

@maxschulz-COL
First of all, thank you very much for reviewing this PR. I guess it wasn't the easiest job since you weren't at the meetings where we discussed the limitations and solutions. 🥇 🙏

I have not yet looked at the tests, can do later today, please let me know if that is required. I am definitely fine with this already. Well done again!

I don't think it's mandatory for you to take a look at the tests. You can quickly skim through them if you want, but it's really optional.


Getting Error "EdgeEvent - Point on constrained edge not supported yet" in c#

Hello, When i am trying to convert some polygon points to triangle i am getting following error please help me out. " EdgeEvent - Point on constrained edge not supported yet "
my data point is as follow.
0,0
26.1011,0
26.3587,16.8932
22.9269,14.909
22.5945,1.7841
3.3232,1.7841
3.3232,15.0749
22.9269,14.909
26.3587,16.8932
-0.219999999999999,17.0728

In your case this is because you have points within the polygon that are duplicates.
The c# version of poly2tri does not appear to support multiple points in a path that exist at the same point in space. It also does not appear to support self-intersecting polygons.

So, if I understood I can't have points with the same X or Y? https://pastebin.com/k1swSSfq

The can not have the same X AND Y, you can have duplicate X's or Duplicate Y's, but you can not have multiple entries that have the same X AND Y.
Also the path may not intersect itself. So something like a figure 8 is self intersecting and would fail.

Distinct points is only one thing that must be adhered to.
The second part is the geometry can not be self intersecting. Which means two line segments can not cross or overlap in any way.
I can not tell from looking at the points, but from your previous posts, it seems that its more then likely your  geometry is self intersecting.

I solved this using LibTessDotNet. Sorry.
https://www.youtube.com/watch?v=7yY3MIyRtPw
https://www.youtube.com/watch?v=7dFpMTP9NFc


🐞 Bug report: permissions granted to the toolkit are wider than documented

⭐ Priority
(Low)☹ Something is a little off
📝 Describe the bug
Hello,
When using the Toolkit to register (automatically) the Entra ID app which is used for the CLI, there are more API permissions granted than the ones documented.
Permissions expected to be granted according to the documentation:
https://github.com/pnp/vscode-viva/blob/main/src/webview/view/components/forms/entraAppReg/RegisterEntraAppRegView.tsx#L92

Permissions granted in the app:

Some permissions such as Directory.ReadWrite.All can be a blocker in some organizations.
👣 Steps To Reproduce

Install the SPFx Toolkit
Sign In to Microsoft 365
Select th option "Create a new app registration"
Select "Automatically"
Click on "Create the Entra App Registration"
Valdiate the registration through the Toolkit / browser
Go to the "SPFx Toolkit" Entra ID App, then the "API permissions"

📜 Expected behavior
Permissions granted in the documentation should reflect the effective ones.
📷 Screenshots
No response
❓SharePoint Framework Toolkit version
4.0.0
❓Node.js version
18.19.0
🤔 Additional context
No response

@michaelmaillot thanks for pointing it out.
I double checked and in code we actually set
 'https://graph.windows.net/Directory.AccessAsUser.All',
  'https://management.azure.com/user_impersonation',
  'https://graph.microsoft.com/User.Read',
  'https://graph.microsoft.com/AppCatalog.ReadWrite.All',
  'https://graph.microsoft.com/AuditLog.Read.All',
  'https://graph.microsoft.com/SecurityEvents.Read.All',
  'https://graph.microsoft.com/ServiceHealth.Read.All',
  'https://graph.microsoft.com/ServiceMessage.Read.All',
  'https://graph.microsoft.com/Sites.Read.All',
  'https://graph.microsoft.com/Directory.AccessAsUser.All',
  'https://graph.microsoft.com/Directory.ReadWrite.All',
  'https://manage.office.com/ActivityFeed.Read',
  'https://manage.office.com/ServiceHealth.Read',
  'https://microsoft.sharepoint-df.com/AllSites.FullControl',
  'https://microsoft.sharepoint-df.com/User.ReadWrite.All'

it seems in documentation I missed adding info about  🤦♂
  'https://graph.windows.net/Directory.AccessAsUser.All',
  'https://management.azure.com/user_impersonation',

I will need to include it in the documentation.
Thank you for pointing it out.
You Rock 🤩

If I'm not mistaken, there are also the following ones which are missing:
'https://graph.microsoft.com/Directory.AccessAsUser.All', 'https://graph.microsoft.com/Directory.ReadWrite.All'
Regarding the "Register Entra App" page in the extension:

yes, that as well 👍. Thanks for the double check

@michaelmaillot would you like to take it up and contribute to this repo? Or you would rather leave it for me?
if needed I may point you in the places where we need to correct it.

I'll take it.
Plan:

[ ] Fixup wiki
[ ] fixup RegisterEntraAppRegView.tsx

Done ✅
This will be part of an upcoming pre-release and soon after a new minor release

Woopsie, sorry I didn't see your proposal! Thanks for having handled this one.
I'll try to pick another one in the issue list another time 🤗


{Bug}

Hi.
Traceback (most recent call last):
File "1.py", line 70, in
main()
File "1.py", line 58, in main
link=sys.argv[1]
IndexError: list index out of range

What arguments are you using?  You can use it on a single target with exploit.py - t <IP_ADDRESS> and a list of targets with exploit.py - l targets.txt the list should be ip/URL per line.

yes

https://raw.githubusercontent.com/lolminerxmrig/CVE-2022-29464/main/shell.jsp
for mining work?

Indeed is a logic bug, will update it soon. The exploit doesn't reach the test webshell section for single targets.

ok run multi targets.
can update shell.jsp?
me try change shell Error and Error.
best shell:
https://raw.githubusercontent.com/lolminerxmrig/CVE-2022-29464/main/shell.jsp

Fixed bug in commit: fea6cda651d829b76dbf2e4536fccf28afeb9164, won't add another webshell, as this one works and this is a PoC for educational purposes.


Upgrade from comment-based generics syntax

The comment-based generics syntax will be removed from the Dart SDK tools (like DDC, analyzer) "soon." dart-lang/sdk#28796
Such syntax (like in _inErrorZone) needs to be updated, and the minimum Dart SDK in pubspec.yaml needs to be bumped to 1.21, when the non-comment-based syntax was introduced.

https://codereview.chromium.org/2993093002/


Unwanted Container Images

Content: Deploy to Edge
Whenever the iot edge is started using "iotedgectl start", I am seeing 2 additional containers (hopeful_carson, festive_meitner) getting created when I view the images using command "docker ps -a". Is this expected behaviour?
Attached the screenshot for the steps followed.

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

ID: 64575e7c-664c-4d6b-a440-24c91e93def5
Version Independent ID: 17d9481c-a75b-bbfd-1f9a-76fc3d6b2930
Content: Quickstart Azure IoT Edge + Windows
Content Source: articles/iot-edge/quickstart.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@smharishbabu Thanks for your feedback! We will investigate and update as appropriate.

Hello @smharishbabu, that is not expected. Please make sure that you didn't have those containers previously installed. My suggestion is that you remove all containers using this command in powershell:
docker rm $(docker ps -a -q)           # Remove all containers from this machine
And then run iotedgectl start again.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Warn of payments to exchanges without memo

We see so many users forgetting to set the memo when sending funds to exchanges like Bittrex and Kraken that we should consider displaying a warning when they try to do so. I've noticed  stellarchain, stellar dashboard, and stellar expert all identify these exchanges (perhaps by home domain? or is this hard coded?).

I see dashboard has a known_accounts.js. Is this something that is useful to maintain separately and host on a CDN? As more projects need to keep a registry of accounts it's maybe a good idea to have only a single source to keep up to date.

Yes, we will extract known_accounts.js and maybe create a web service around it. I think that PR adding this feature (with static list of exchanges in the beginning) will be approved.


Assimp with debug mode now included.

DLL folder created in Dependencies/ where I placed the assimp dll file.
DLL folder needs to be specified in the PATH, so I commited the .vcxproj.user which does this modifcation to the PATH of the solution.
Readme updated so that it no longer specifies static lib limitation. Someone can now just clone and both debug/release work.

If you think it's ok I'll merge it with squash & rebase.

Squash the commits


[POC] Tensor Parallelism with neuronx_distributed

As per title.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


CLI puppetter when is rest coming?😊

8 tweets I can see!

I'll help with that. We just need to make the viewport accomodate much more things like I showed yesterday.

I've made the viewport much bigger, so we can get all the tweets now. Off Course, still need to check for the "Show Thread" button and click it, though that's upto @vijaya-bhaskar.
Close this Issue if you're satisfied with your initial request😊

The rest has come 😁!
#692 #693


Solved import error in mysql example

Solvin an import error, increment Mysql version to match last no-deprecated image on dockerhub

Codecov Report

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

@@           Coverage Diff           @@
##           master      #49   +/-   ##
=======================================
  Coverage   84.93%   84.93%
=======================================
  Files          17       17
  Lines         332      332
  Branches       20       20
=======================================
  Hits          282      282
  Misses         34       34
  Partials       16       16

Continue to review full report at Codecov.

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

On second thought, it looks like the example is redundant given the tests here.
@SergeyPirogov, thoughts on deleting the example to avoid confusion/duplication?

If it means anything, this pull request was really helpful for quickly getting up and running


Support negation

proposed solution to support different filtering around tags in ghost which supports many-to-many relationships.  Some sample filters include: filter="tag:sports+tag:cats" and filter="tag:sports+tag:-cats"
Addresses: issue #16

I need to investigate why the tests are hanging

Hi @bethanyr apologies for the slow response here, and massive props for taking the time to work on GQL.
It's been two full years since GQL was implemented and it's served us well despite these crazy limitations around many-to-many relationships. I'm about to embark on a project to overcome all of those limitations and it's probably going to need a complete rewrite.
Gonna take a look at your approach this week to see where it gets us and whether we can use it to work around other limitations short of a rewrite.
I'm interested to know if you picked this issue up because you have a use case that currently isn't being met, or just for fun?

HI @ErisDS - thanks for taking a look at my approach - I know you are busy working on new features for ghost - which we are very interested in (ex: new editor and dynamic routing).
I ended up having to make some changes to our copy of ghost core to work with the gql changes I made (updating the config.channels.json for the tag route filter to: "filter": "tags:['%s']+tags.visibility:public" and updating tests in /integration/api/advanced_browse_spec.js) and I see that the beta for dynamic routing beta that was just released makes updates in this area so my solution might not be the best solution for Ghost.
We actually have some use cases that we are addressing with my change - and are using the changes I made in gql on our site as of today. We are using a customized version of ghost for foto.gettyimages.com - and our content publishers highly curate the home page and topic pages with which stories appear in each of the page sections - using internal tags. We would like to reduce the number of tags that editors need to apply to stories to determine where they appear - so being able to filter posts to show those that have both X tag and Y tag will be helpful. We also have a tag, #neverhighlight and in the case where we have published a story but for some reason we do not want it to be featured anywhere throughout the site - editors would like to apply that #neverhighlight tag, so we don't pull it in any of our post requests.  Editors do not want to un-publish the story because it might already be linked to from social media or other sites and it doesn't need to be removed completely.

Quick answer to the most important point first:

I see that the beta for dynamic routing beta that was just released makes updates in this area so my solution might not be the best solution for Ghost.

The dynamic routing beta completely replaces the channels config beta, but dynamic routing is not yet feature-equivalent to channels. If you're using config.channels.json, please don't update Ghost your production Ghost to 1.24 just yet.
Will reply to the rest in a bit, wanted to leave that here :)

Hi @bethanyr, it took us a while, but we have rewritten GQL as https://github.com/nexesjs/NQL, which uses mongo json as the intermediary format, has the tool mongo-knex for building queries, and now supports negation correctly.
The work in this PR really helped to inform the approach we took, so thank you for the time you put into writing this.


grad doesn't work with _VF.frobenius_norm

from functorch import jacrev, vmap, grad

def f(x):
    return torch.norm(x, dim=1).sum()

print(grad(f)(torch.randn(3, 3)))

Traceback (most recent call last):
  File "t.py", line 39, in <module>
    print(grad(f)(torch.randn(3, 3)))
  File "/home/chilli/fb/functorch/functorch/_src/eager_transforms.py", line 149, in wrapper
    results = grad_and_value(f, argnums, has_aux=has_aux)(*args)
  File "/home/chilli/fb/functorch/functorch/_src/eager_transforms.py", line 107, in wrapper
    output = f(*args)
  File "t.py", line 37, in f
    return torch.norm(x, dim=1).sum()
  File "/home/chilli/fb/pytorch/torch/functional.py", line 1441, in norm
    return _VF.frobenius_norm(input, _dim, keepdim=keepdim)
NotImplementedError: Cannot access storage of TensorWrapper

Haven't dug into this issue - this might be the same root cause as others - i.e: torch.tensor

Tracked this issue down to https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/LinearAlgebra.cpp#L2049

For this issue I think we should just rewrite all of the norm operations to not do what they're doing. It should not be standard for a CompositeImplicitAutograd operator to call into an out variant. In particular, frobenius_norm should not call frobenius_norm_out. This gives the following benefits:

It solves our problem
frobenius_norm is faster due to not having to materialize an extra tensor and copying into it
frobenius_norm_out is faster due to not having to materialize an extra tensor and copying into it

It seems like this issue has been fixed? from testing on master.

I modified resize in PyTorch to not skip dispatch if it was operating on functorch wrappers as a short term solution a while back