Odd behavior with 'until' vs '&&'

This is on:
# crystal --version
Crystal 0.21.1 (2017-03-18) LLVM 4.0.0
# uname -a
Darwin my.host 14.5.0 Darwin Kernel Version 14.5.0: Sun Sep 25 22:07:15 PDT 2016; root:xnu-2782.50.9~1/RELEASE_X86_64 x86_64
# # aka macOS 10.10.5 (Yosemite)

I don't understand what is happening in the following.  It seems like either until or && is not processed correctly ( and just try to search for issues with &&! ):
  printf "Enter two integer values:\n"

  low_value = nil
  high_value = nil

  until low_value && high_value
    printf "#DBG B: low_value=%s, high_value=%s\n", low_value.inspect, high_value.inspect
    user_ans = STDIN.gets
    if user_ans.nil?
      STDERR.printf "\n <-- EOF! -->\n"
      exit 1
    end

    user_ans = user_ans.strip
    case user_ans
    when /^\d+$/
      if low_value.nil?
        low_value = user_ans.to_i
      else
        high_value = user_ans.to_i
      end
    else
      STDERR.printf "Invalid response:  '%s'\n", user_ans
    end

    printf "#DBG E: low_value=%s, high_value=%s\n", low_value.inspect, high_value.inspect
  end # until

  exit 1  if low_value.nil?
  exit 1  if high_value.nil?

  if low_value > high_value
    tmp = high_value
    high_value = low_value
    low_value = tmp
  end

  printf "%d\n", low_value
  printf "%d\n", high_value

There are two problems I hit with this, and perhaps they are related.  First off, if I do not include:
  exit 1  if low_value.nil?
  exit 1  if high_value.nil?

then crystal fails with a compile-time error on if low_value > high_value, complaining that no overload matches 'Int32#>' with type (Int32 | Nil).  However, I should not exit the until loop unless both low_value and high_value are not-nil, so why do I need those two checks?
The other issue is that I happened to use until low_value && high_value instead of using while low_value.nil? || high_value.nil?.  If I run the above code using the while statement, it works as expected:
Enter two integer values:
#DBG B: low_value=nil, high_value=nil
1
#DBG E: low_value=1, high_value=nil
#DBG B: low_value=1, high_value=nil
2
#DBG E: low_value=1, high_value=2
1
2

But if I run it with the until statement, the result is:
Enter two integer values:
#DBG B: low_value=nil, high_value=nil
1
#DBG E: low_value=1, high_value=nil
#DBG B: low_value=nil, high_value=nil
2
#DBG E: low_value=2, high_value=nil
#DBG B: low_value=nil, high_value=nil
3
#DBG E: low_value=3, high_value=nil
#DBG B: low_value=nil, high_value=nil
4
#DBG E: low_value=4, high_value=nil
#DBG B: low_value=nil, high_value=nil
^C

Why is low_value being reset to nil each time through the until loop?  Given the logic inside the loop, I can change that until to be until high_value, and then it behaves as expected.  Note that if I did use that condition, then I would understand why I need the check for low_value.nil? outside of the loop.

On gitter, @zatherz noticed that the same issue comes up if you use while !(low_value && high_value).

Reduced:
a = nil
until a
  a = 1
end
p typeof(a) # => (Int32 | Nil)

Basically until (or while) don't do type filtering after them. This is probably a good enhancement.

Well, that's the first issue.  But the second one seems more significant to me!

Reduced second issue with no infinite loop:
Using while !(a && b): https://carc.in/#/r/1t8j
Using while !a || !b: https://carc.in/#/r/1t8n

@drosehn Sorry, I didn't see the second issue the first time I read it. I stopped at the first issue. It's probably better to report issues separately, and try to reduce them as much as possible so the bug is super clear.
I split this issue in two which mention the bugs in a reduced way: #4242 and #4243


prepared for packaging

@kashif , can you have a look
can you pls also try pip install --index-url https://test.pypi.org/simple/ vlrnn --user ?

yes works!


[release-1.1] virt-api: skip clone auth check when DataVolume already exists

What this PR does
Before this PR:
After this PR:
manual cherry-pick of #12547

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

virt-api: skip clone auth check when DataVolume already exists

/retest-required

/approve


Update typesAndWaits method and randomReply

for typesAndWaits:
Use of usleep instead of sleep to be able to sleep for fractions of a second.
for randomReply:
array_rand uses the libc generator, which is slower and less-random than Mersenne Twister.

Please remove the wit changes from this commit, as you already have these in a separate PR


Set/Get UEFI Option fails on long option names

Device
MSI z690 dd45
RTE version

OSFV version
develop
Affected component(s) or functionality
None at this moment, found out when implementing keywords.
Get/Set of Serial Redirection
Brief summary
setup menu Set UEFI Option fails when the option name is split into two lines
How reproducible
100%
How to reproduce
Run Get Uefi Option    SerialRedirection
Expected behavior
Should find and return the value
Actual behavior
The keyword fails because the option name Enable Serial Port Console Redirection is so long it's split into two lines. The Option Name To UEFI Path returns the whole name of the option but when reading the menu construction the option is split into two lines which is a behaviour not handled in the keywords used to navigate the setup menu.
Link to screenshots or logs
The log shows that the option is not found, because it is split into two lines
test-reset.robot_log.zip
Additional context
No response
Solutions you've tried
No response

According to the keyword Parse Serial Port Configuration in dasharo-system-features-menus.robotI think the fact that the second part of the split line is read there is also a bug.
"Second line from Enable Serial Port Console Redirection should not be there"
Parse Serial Port Configuration
    [Documentation]    Check if Serial Port Configuration menu can be parsed.
    Skip If    not ${DASHARO_SERIAL_PORT_MENU_SUPPORT}
    ${serial_menu}=    Parsing Dasharo Submenu Verification    Serial Port Configuration
    ${serial_entries}=    Get Length    ${serial_menu}
    Should Be Equal As Integers    ${serial_entries}    2
    Should Match Regexp    ${serial_menu}[0]    ^Enable COM0 Serial \\[.\\].*$
    Should Match Regexp    ${serial_menu}[1]    ^Enable COM1 Serial \\[.\\].*$
    # Second line from Enable Serial Port Console Redirection should not be there
    List Should Not Contain Value    ${serial_menu}    Console Redirection
    Menu Construction Should Not Contain Control Text    ${serial_menu}
    ```


[Bug]: JavaScript heap out of memory

Which Remix packages are impacted?

remix (Remix core)
@remix-run/dev
@remix-run/node
@remix-run/react
@remix-run/serve
@remix-run/vercel

What version of Remix are you using?
v1.1.1
What version of Node are you using? Minimum supported version is 14.
v16.13.1
Steps to Reproduce
It's just a regular remix app and sometimes when saving something in the codebase the server crashes and gives me the error pasted below, relating to JS memory issues. Looks like something to do with esbuild but I'm not really sure, just wondering if anyone else ever has this?

I've also been receiving this issue randomly after working on in my project with the dev server running for a few hours.

@kentcdodds @jacob-ebey sorry for being pushy, but is this on your radar?

Wow, it got so much better with 1.2.0-pre.0!

1.2.0-pre.0 just blew up completely for me, won't run dev server at all.

@JClackett update all remix deps to 1.2.0-pre.0

@JClackett I've just tested it on your remix boilerplate and it used half the memory was using before (I had to remove the sentry imports though).

Sentry might be doing some global initialization that hangs around and is re-called every time the require cache is purged (i.e every request in dev).

@viczam what version of Node you on? and what machine?
I'm using node 16 on an m1 Mac its not working using all latest remix deps.

Node 14 on an M1 Mac as well.

Hmm strange, can't get it to work at all.

I have found I get this issue also occasionally. But only on an old MacBook Pro with low specs. When I work on my later machine with better specs it doesn't happen 🤷🏼♂

1.2.1 now magically works, cool! I do have to remove sentry though.

1.2.2 randomly crashing :/

I am still getting this issue. Is there a way to change the scripts to allow more memory?

I found that the source of this error for me was importing a large (20mb) json file as
import Messages from '../messages.json' - the way I fixed it was making a new messages.server.ts file and doing a node file read instead.
import path from "path";
import fs from "fs/promises";

const messagePath = path.join(__dirname, "..", "messages.json");

export async function getMessages() {
  const file = await fs.readFile(messagePath, "utf8");
  return JSON.parse(file);
}

I guess this is happening because using an import is continually adding the json to memory and the garbage collector either isn't keeping up or isn't freeing up that memory at all. But the node file system read does. Just speculation as I stopped looking in to it once I found my fix.

this still happens on Linux using remix 1.3.3

Still happening on 1.3.4

Part of the issue is that Remix is constantly purging the require cache on every request (in "development"). This results in a lot of garbage and if you make enough requests quickly enough, the process will run out of memory before the GC can do its thing.
I have my own <LiveReload/> component, that calls an endpoint http://localhost:3000/build/__purge__ before it does the refresh. Then in my Express adapter, I simply add a handler for that route to do the purge instead of every request.
// LiveReload.tsx
             if (event.type === "RELOAD") {
               console.log("💿 Reloading window ...");
-              window.location.reload();
+              fetch("/build/__purge__").finally(() => {
+                window.location.reload();
+              });
             }

// server.js (Express adapter)
app.use('/build/__purge__', (req, res) => {
  console.log('💿 Purging require cache')
  purgeRequireCache()
  return res.send('ok')
})

@kiliman Can you share your LiveReload.tsx file?

Getting this constantly on a large app, seems like after a couple save/LiveReload cycles, it blows up. In active development, it's happening every 5-10 minutes.
Setting NODE_OPTIONS="--max-old-space-size=8192" seems to have temporarily fixed this -- working for a couple hours now with no out of memory errors.

@vinceprofeta you’ll want to delete that first reload() call. It should only reload in the finally block.

This is literally the main major point of remix developer experience. Otherwise, remix is so awesome!

Yes I plan on submitting a PR to fix this. I’m flying back today from Remix Conf which was awesome.

@kiliman Using your LiveReload / express server updates definitely helps. One small issue I found is you can get a stale page in development if this happens:

Load a page (so it's in the require cache)
Close the page
Make changes to the page and save, Remix rebuilds.
Re-open the page, you still have the old version since the LiveReload component wasn't active during the update, so the /build/__purge__ handler never ran. At this point you either need to restart the server, or make a change to the cached page to trigger the purge.

In practice this won't happen often, since you usually have the page open during development, but it's an edge case to consider if you're submitting a PR.

Ah, interesting scenario. Perhaps what should happen is that remix watch should send the request to purge to the web server instead of the browser.

Remix watch detects change and rebuilds
Sends purge request to web server
Sends web socket notification to browser to refresh

So even if browser is not active to refresh, the web server was already notified to purge and will serve new content when browser reconnects.

@kiliman do you know if there is some things going on to fix that bug ?
@dmarkow it seems the files are outdated now, could you update the fix you propose to the last updated files ?
hard for me to understand !
that would be really nice...
thanks !

actually I tried something and it looks better, is my patch correct ?
@remix-run+dev+1.7.1.patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 54f2d99..80eb2fa 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -228,6 +228,7 @@ async function watch(remixRootOrConfig, modeArg, callbacks) {
     },

     onRebuildFinish() {
+      purgeAppRequireCache(config$1.serverBuildPath);
       log(`Rebuilt in ${prettyMs__default["default"](Date.now() - start)}`);
       broadcast({
         type: "RELOAD"
@@ -289,7 +290,6 @@ async function dev(remixRoot, modeArg, portArg) {
   let app = express();
   app.disable("x-powered-by");
   app.use((_, __, next) => {
-    purgeAppRequireCache(config$1.serverBuildPath);
     next();
   });
   app.use(createApp(config$1.serverBuildPath, mode, config$1.publicPath, config$1.assetsBuildDirectory));

well I don't have any such problem since my patch, so it might be correct ! I'll open a PR to move things on, and see with the comments if my patch IS correct 😄

Happening on 1.7.5 too, remix is really bad at this. Development experience with this issue is terrible.

On every page load memory usage grows by a few megabytes, consistently. I've been trying to figure it out using Node's heap dumps, but it's just to much in there that I cannot figure it out.
However, I found a lot of identical cases of… I think it's cached code.

Trying to dig down in the cache I can see a lot of cached node_module files in there.
Is there some cache built-in somewhere that isn't flushed or reused on a reload so it just sticks around forever? I don't know, and I don't understand what I'm looking at.
If you want to have a look, run node --inspect ./node_modules/.bin/remix dev and open a Chromium-based browser to chrome://inspect and make memory snapshots. Perhaps someone else can make sense of this.

actually I tried something and it looks better, is my patch correct ?
@remix-run+dev+1.7.1.patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 54f2d99..80eb2fa 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -228,6 +228,7 @@ async function watch(remixRootOrConfig, modeArg, callbacks) {
     },

     onRebuildFinish() {
+      purgeAppRequireCache(config$1.serverBuildPath);
       log(`Rebuilt in ${prettyMs__default["default"](Date.now() - start)}`);
       broadcast({
         type: "RELOAD"
@@ -289,7 +290,6 @@ async function dev(remixRoot, modeArg, portArg) {
   let app = express();
   app.disable("x-powered-by");
   app.use((_, __, next) => {
-    purgeAppRequireCache(config$1.serverBuildPath);
     next();
   });
   app.use(createApp(config$1.serverBuildPath, mode, config$1.publicPath, config$1.assetsBuildDirectory));

I've just tried your solution and it looks very nice ! 🙏🏽
Purging on watch events seems the natural approach to me, I wonder if there is any edge case that require to purge on each request 🤔

I'm constantly still running into this on the latest version of the remix packages.
 Also just wanted to check that everyone else also gets a load of build artefacts in the public/build directory related to old commits, should it not clear the old files?

actually I tried something and it looks better, is my patch correct ?
@remix-run+dev+1.7.1.patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 54f2d99..80eb2fa 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -228,6 +228,7 @@ async function watch(remixRootOrConfig, modeArg, callbacks) {
     },

     onRebuildFinish() {
+      purgeAppRequireCache(config$1.serverBuildPath);
       log(`Rebuilt in ${prettyMs__default["default"](Date.now() - start)}`);
       broadcast({
         type: "RELOAD"
@@ -289,7 +290,6 @@ async function dev(remixRoot, modeArg, portArg) {
   let app = express();
   app.disable("x-powered-by");
   app.use((_, __, next) => {
-    purgeAppRequireCache(config$1.serverBuildPath);
     next();
   });
   app.use(createApp(config$1.serverBuildPath, mode, config$1.publicPath, config$1.assetsBuildDirectory));

I've just tried your solution and it looks very nice ! 🙏🏽 Purging on watch events seems the natural approach to me, I wonder if there is any edge case that require to purge on each request 🤔

well my solution was for v1.7.1 but it's not working anymore for the latest v1.10.1, what did you do ?

By the way, it looks like this discussion try to address the cache issue 🎉

Fixed by #5133, which will make the new dev server available in the next minor release under the unstable_dev future flag.
Note that we needed to rearchitect the dev server as moving the require cache purging to onRebuildFinished in the current dev server caused race conditions


Program Crash while using After effects

For example, use a mapping that redirects a keyboard key like 'A' or a joystick key like 'DPAD Up' to an abscissa DimY
And the program close itself.

This comes from using null values
This will be fixed in a future version
In the meantime it is possible to check before using an After effect that the value is not null, by adding for example a default value to Y in this example
Just add a line, like HALF to Y (possibly excluding the later key that gives the value to Y, but not necessarily if the overcontrol is not activated) at the begining of the mapping


refactor: remove unecessary useEffect, registerStoryblokBridge listen…

I think here the useEffect is not necessary. You already use registerStoryblokBridge that is listening to any new event and set a new story in case.

Should we do the same for the useStoryblok hook?
https://github.com/storyblok/storyblok-react/blob/main/lib/index.ts#L12

No, I don't think you need to do the same for useStoryblok. I made a proposition for refactoring, but I think there is some room for improvement as I don't really know the whole use case of useStoryblok.
In this case, you need to use useEffect because you are fetching. If you are not using it, you will block the thread until the data comes.
The idea is to separate concerns by having a useEffect for fetching and updating the story. Another one is for initializing the bridge when the story changes (I think that was the idea of the code), so you keep your data consistent.


Use commit SHAs for generating CDN-backed URLs of charts, fix #5

Fixes #5

@arkon Could you deploy it whenever you have a moment?

Done!


TestFailure fails

From #889 and @yifan-gu found
The failure is
=== RUN TestFailure
--- FAIL: TestFailure (4.26s)
    rkt_exit_test.go:74: Missing hello

I can't reproduce on my machine. But I think it smells like a race bug in the gexpect library, which if child.Expect runs before the child process actually starts, it will error: read /dev/ptmx: input/output error, since the gexpect uses pty for starting the chile process asynchronously [1] [2]
[1] https://github.com/ThomasRooney/gexpect/blob/master/gexpect.go#L335
[2] https://github.com/kr/pty/blob/67e2db24c831afa6c64fc17b4a143390674365ef/run.go#L22

I think this might not be the case. Anyway we have improved the error message #890 , hope can catch the real error next tiem.

I can successfully reproduce with the current systemd master build: commit a88abde72169ddc2df77df3fa5bed30725022253
sudo ./tests/run-build.sh src master
Looks like this come from systemd upstream


[WIP]Add basic multiple gpu support

This pull request resolves #60.
The pull request is in progress.
The details of the pull request:

Support parallel on multiple GPU
get_device() now only determine GPU or CPU.
Cannot disable multiple GPU training for now, users can only constraint the gpu usage by specifying CUDA_VISIBLE_DEVICES environment variable

Pull Request Test Coverage Report for Build 1172

4 of 5 (80.0%)  changed or added relevant lines in 3 files are covered.
6 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.05%) to 93.851%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

autokeras/nn/model_trainer.py
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

autokeras/nn/layers.py
1
95.0%

autokeras/nn/model_trainer.py
1
91.94%

autokeras/nn/graph.py
1
97.66%

autokeras/nn/layer_transformer.py
3
97.06%

Totals

Change from base Build 1162:
0.05%

Covered Lines:
3266

Relevant Lines:
3480

💛  - Coveralls

@jhfjhfj1 I think this function is ready to merge. Could you please comment on whether you like the idea of using multi_gpu as a default behavior (can be constraint by CUDA_VISIBLE_DEVICE environment variable) or adding one more parameter to the ModelTrainer is more preferable?

@tl-yang I think it is fine to use multi-gpu by default. So does using env variable means we don't use GPUtil anymore? If we still use GPUtil, how and why should we use it?
I think it would be a good idea that we don't use GPUtil, but let the users to use GPUtil to set the env var to constrain the GPU usage of autokeras.

@jhfjhfj1 GPUtil is used in text_preprocessed.py. Not by utils.py. So I think we need to confirm with @boyuangong ?

@tl-yang I will merge this pull request. We can discuss with Boyuan later. Thanks.


Provide a meaningful error message when a user attempts to perform an action after staying idle (after session timeout)

== Environment ==
IS 5.4.0 GA
JDK - 1.8
DB - H2
OS - ubuntu 16.04
Browser - Chrome - Version 59.0.3071.115
== Issue Summary ==
When a logged in user perform an action in management console after being idle for some time (after session timeout happens), there's an error thrown in back end as below.
WARN {org.owasp.csrfguard.log.JavaLogger} -  potential cross-site request forgery (CSRF) attack thwarted (user:<anonymous>, ip:<IP_ADDRESS>, method:POST, uri:/carbon/oauth/add-finish-ajaxprocessor.jsp, error:request token does not match session token)

By looking at the error log, it's difficult identify the reason for the exception since this will implies a CSRF attack at first place.

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


[Feature Request] Separate Apps and Games Tabs

I know you can toggle from All Apps to Games, but an Apps tab (with no games) and a Games tab separated out would be so much more useful.

You can add a Android Platform Page.
Download this file and remove the "deprecated" at the end.
https://github.com/TapiocaFox/Daijishou/blob/main/platforms/Android.json.deprecated
Then import this platform over the Daijishou settings.
This platform will show all as game marked Android apps.

You can add a Android Platform Page. Download this file and remove the "deprecated" at the end. https://github.com/TapiocaFox/Daijishou/blob/main/platforms/Android.json.deprecated
Then import this platform over the Daijishou settings. This platform will show all as game marked Android apps.

thanks, this is actually great! I'm surprised it's deprecated.


SPM defined Build Settings are not properly generated in xcodeproj

When defining build settings in the Package.swift file, it appears that the generated XcodeProject file does not respect the expected (and documented) behavior of BuildSettingCondition.
If you add the following code:
.define("ENABLE_FEATURE_A")

Then, according to Apples's Documentation on BuildSettingCondition, this should apply to all platforms and build configurations.
This does not happen, instead the created xcodeproj only enables the build setting for DEBUG.
swift-create-xcframework version: master branch
Swift version: Apple Swift version 5.4.2 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin20.6.0
Environment: Xcode Version 12.5.1 (12E507), MacOS 11.5 (20G71)
Source Code of test project: TestMacroDefinition.zip
Checklist

[x] If possible, I've reproduced the issue using the master branch of this package
[x] I've searched for existing GitHub issues

Steps to Reproduce
To reproduce, create a new Swift Package, set the following as the Package.swift:
import PackageDescription

let featureFlags: [SwiftSetting] = [
	  .define("ENABLE_FEATURE_A"),
    .define("ENABLE_FEATURE_B", .when(platforms: nil, configuration: .release))
]

let package = Package(
    name: "TestMacroDefinition",
    products: [
        .library(
            name: "TestMacroDefinition",
            targets: ["TestMacroDefinition"]),
    ],
    dependencies: [],
    targets: [
        .target(
            name: "TestMacroDefinition",
            dependencies: [],
            swiftSettings: featureFlags + [.define("RELEASE", .when(platforms: nil, configuration: .release))]
        )
    ]
)

Then, in the one piece of source code in the library, replace it with this:
struct TestMacroDefinition {
    var text = "Hello, World!"

    #if ENABLE_FEATURE_A
    #if RELEASE
    #error("FEATURE A ENABLED")
    #endif
    #endif
}

With this, the library should fail to build if ENABLE_FEATURE_A is set and RELEASE is also set.
In Xcode, if you go to Product -> Archive, this will (correctly) fail to build.
Also, if you add a script to the directory of build.sh and add the following:
# iOS devices
xcodebuild archive \
    -scheme TestMacroDefinition \
    -archivePath "archives/TestMacroDefinition-iOS.xcarchive" \
    -destination "generic/platform=iOS" \
    -sdk iphoneos \
    SKIP_INSTALL=NO \
    BUILD_LIBRARY_FOR_DISTRIBUTION=YES
# iOS simulators
xcodebuild archive \
    -scheme TestMacroDefinition \
    -archivePath "archives/TestMacroDefinition-iOS-simulator.xcarchive" \
    -destination "generic/platform=iOS Simulator" \
    -sdk iphonesimulator \
    SKIP_INSTALL=NO \
    BUILD_LIBRARY_FOR_DISTRIBUTION=YES
xcodebuild -create-xcframework \
    -framework "archives/TestMacroDefinition-iOS.xcarchive/Products/Library/Frameworks/TestMacroDefinition.framework" \
    -framework "archives/TestMacroDefinition-iOS-simulator.xcarchive/Products/Library/Frameworks/TestMacroDefinition.framework" \
    -output "TestMacroDefinition.xcframework"

and run the following in your terminal:
sh build.sh

It also (correctly) fails to build.
When running this with swift-create-xcframework, this however, does build (incorrectly).
I have cloned the main branch of swift-create-xcframework and debugged this. It appears that the created .xcodeproj file for the above has an issue.

If you'll notice, for release, it does not have an $(inherited), I believe this is making it not take the ENABLE_FEATURE_A from common.
This can be seen in the xcodeproject.

This also appears the same if I directly run swift package generate-xcodeproj in my terminal for this swift package.
Expected behavior
swift-create-xcframework should fail to build.
Actual behavior
swift-create-xcframework successfully builds (incorrectly).

This seems to be an issue not with swift-create-xcframework, but with swift package generate-xcodeproj.
Perhaps an $(inherited) should be added for release configs somewhere in the code?
Alternatively, it looks to me like this library may not even need to create xcodeproj files to make the XCFramework. As in the Steps to Reproduce, there are ways of build the project without using xcodeproj. Are there any edge cases where the xcodeproj is required?

Hi @mhays118. As you've noted, xcodebuild has native support for building packages directly now, so we've got a refactor in progress that moves the existing behaviour to a --legacy flag for backwards compatibility. You do lose being able to build your entire package and its dependencies in a single command and building non-.dynamic products, but as SwiftPM will one day drop support for xcodeproj generation this will be the way of the future.


Add tests for getting tokens for XDS

Please provide a description for what this PR is for:
Add tests for getting tokens for XDS

Test case 1: xdsAuthProvider is google.GCPAuthProvider.
Test case 2: xdsAuthProvider is empty.
The tests need to call constructProxyConfig() and setupSecurityOptions() to
configure the options used by the token provider. Thus,
constructProxyConfig() and setupSecurityOptions() are refactored such
that they can be called in tests.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@lei-tang: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
59b5a805a16be33d5d9b448e75446cdb67d12071
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lei-tang: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
59b5a805a16be33d5d9b448e75446cdb67d12071
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio

/test release-notes_istio

In response to a cherrypick label: #30411 failed to apply on top of branch "release-1.9":
Applying: Add tests for getting tokens for XDS
Using index info to reconstruct a base tree...
M	pilot/cmd/pilot-agent/main.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/cmd/pilot-agent/main.go
CONFLICT (content): Merge conflict in pilot/cmd/pilot-agent/main.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add tests for getting tokens for XDS
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: #30411 failed to apply on top of branch "release-1.9":
Applying: Add tests for getting tokens for XDS
Using index info to reconstruct a base tree...
M	pilot/cmd/pilot-agent/main.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/cmd/pilot-agent/main.go
CONFLICT (content): Merge conflict in pilot/cmd/pilot-agent/main.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add tests for getting tokens for XDS
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #30419

In response to a cherrypick label: new issue created for failed cherrypick: #30419


Add Infection Support docs

As we agreed, here is a draft docs for Pest docs site with information about Pest support in Infection.

Related to

https://github.com/pestphp/pest/pull/291
https://github.com/infection/infection/pull/1516

Feel free to suggest any update and/or commit directly.

Cool, looking forward to your feedback so we can fix any outstanding issues if any. Thanks

Let's move forward, and let the community report bugs - if any.

It's ready to use?

@bebetoalves, currently you'll need to use the development branch of Infection, but should be good to use for testing. 👍🏻

I've now run the dev-master branch of Infection with Pest on about 5 projects and it's working great. The one issue I hit was when running it against the Pest repo itself, where it seems to get the following error, however I think this is just an issue with this test case as it looks like the ampersand isn't escaped.

@maks-rafalko Let me know when its released in your side so we can announce it.

@maks-rafalko Let me know when its released in your side so we can announce it.

released https://infection.github.io/2021/05/13/whats-new-in-0.23.0/

Hi,
I just drop a word to say I'm suprised to not find this doc anymore ?
Regards !

Hi, I just drop a word to say I'm suprised to not find this doc anymore ? Regards !

apparently support was dropped in V2.  in pestphp/pest#48 it is mentioned you should use teamcity as a workaround instead, but I haven't figured out how that works.


Add Arizona

We do not have Maricopa vote centers and the logic for selecting vote centers for a few counties in the Partial file...isn't great. This dataset needs review to ensure that we aren't missing any.


glad  to see this project ,thanks very much

i'am very interested in this project,can you offer more demo;

can you offer more document or presentation

Unfortunately I don't have any documentation for kume, it's all in README file. However you can find examples in unit and integration tests in here: https://github.com/buremba/kume/tree/master/src/test/java/org/rakam/kume

how to run in different machine and how to join the cluster,leader election

dear buremba
in NettyChannel code
public CompletableFuture ask(Packet message) {
CompletableFuture future = new CompletableFuture<>();
messageHandlers.put(message.sequence, future);
channel.writeAndFlush(message);
return future;
}
this is correct ?

Cluster.java->voteElection  function   is correct?  and   how to consistent data in different machine

When creating a cluster, you may set the nodes.
Cluster cluster = new ClusterBuilder()
    .services(services)
    .members(members) // here it is
    .serverAddress(serverAddress)
    .start();

Once the cluster is running, when a new node is started it send UDP multicast message to check if a cluster is already running and connects a cluster if there's already one.
If the nodes are in same network and your firewall allows UDP multicast message you don't need to do anything, they will discover each other and distribute the work & data automatically.
Leader election is done using Raft, voteElection is an internal method and when a node don't get any heartbeat from the leader for some time, it will be invoked so that a new leader can be elected. You may learn about Raft consensus algorithm from here: https://raft.github.io/
In fact, Kume is not ready for production and I don't know when it will be because I'm quite busy at the moment with other projects. :/ However, I think if you are looking for a distributed processing framework that implements decent distributed algorithms (Raft, CRDT etc.) in order to practice for distributed programming, it may help a lot.

Special Thanks, expect the follow blog post


Minor issue in documentation

Their is a minor issue in documentation.
According to documentation, to include files into a target we should do like this (http://www.rubydoc.info/github/jcampbell05/xcake/master/file/docs/Cakefile.md#Include_Files):
target.include_files = "DifferentAppFolder/*.*" target.include_files << "OtherFolder/*.*"
in fact it does not work at all, the << operator leads to empty target (no files included at all). After consulting with our Ruby developer, I found out that we should instead do like this:
target.include_files = ["Libs/**/*.*"] target.include_files << "Src/**/*.*"
that means that include_files is an array, so when we use = we have to provide an array of strings as initial value, and then later we can add items (strings) into array, one at a time, using << operator.

Great catch @maximkhatskevich, could you submit a PR to fix this ?


Get is not a method but has arguments with hugo version 0.112.5

Hello,
When I try to build my site I encounter this error wish seems to be related to https://github.com/gohugoio/hugo/issues/10862 and https://github.com/nanxiaobei/hugo-paper/issues/166
Start building sites …  hugo v0.112.5-48e33e10af2feb2a0e1c32d04880ed016619f2d8 windows/amd64 BuildDate=2023-05-29T07:27:36Z VendorInfo=gohugoio Built in 1270 ms Error: error building site: "C:\Users\dim\Desktop\tdm\content\_index.md:9:1": failed to render shortcode "map": failed to process shortcode: "C:\Users\dim\Desktop\tdm\layouts\shortcodes\map.html:4:18": execute of template failed: template: shortcodes/map.html:4:18: executing "shortcodes/map.html" at <site>: Get is not a method but has arguments

did you get any solution to it?

I‘m currently on leave, but can have a look once I’m back.On 8 Jul 2024, at 10:49, Eyoel Meles @.***> wrote:
did you get any solution to it?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

hey, I just came across the same issue, and see that a guy have forked your repo and fix it; https://github.com/bruvduroiu/hugo-maps/commit/d062f0d9d60f8de31cc21464032ccb675bacdae7


ck集群导入之后节点无法展示，但是普罗米修斯监控的指标却可以展示

ck集群导入之后节点无法展示，但是普罗米修斯监控的指标却可以展示

the same as #37

This issue has not been active for 1 month, so we decided to close it. If you have any questions, please reopen a new issue.


Feature request: fast way to verify no desync issues with replays

I would like to allow runs with minor mods such as Gender Unlock onto the leaderboards. Presently, the only way I have to verify a replay will play back correctly with no desyncs is to play it back, which can take a long time even at the highest speed.
As I understand it, the code that loads quicksaves essentially plays back a replay as fast as possible. I would like to be able to do this to arbitrary replays to quickly verify that they do not contain desyncs due to mods, bugs, or other issues.

https://github.com/RogueCollab/RogueEssence/pull/19
This PR will enable the option in dev mode.  If the replay completes without fail, it is considered legitimate.  Any dev tool usage will ruin the integrity of the replay and cause it to desync or error by default.


fix: border radius of google sheet where clause removed

Description
Fixed the alignment issue of google sheet where inputs and error header background.
Fixes #8409 #7003
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

checked the alignment of the fields manually

Checklist:

[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
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
// Code coverage diff between base branch:release and head branch: bug/8409-google-sheet-where-columns

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
app/client/src/components/formControls/DynamicInputTextControl.tsx
95.45 (0.1)
71.43 (0)
83.33 (0)
95.35 (0.11)

/ok-to-test sha=3b3d61f


Can't listen to events which are not available as on... properties (for example focusout)

Some events don't have their attribute counterparts, one such example is focusout. Maybe it would be better if VanJS just bound all events handlers (properties starting with on whose value is a function) using addEventListener instead of relying on the DOM properties.
This would also make event names case insensitive (I like to use camelCase for event names).
Jsfiddle: https://jsfiddle.net/uqbt36mz/4/

Does onblur event handler work for your use case?
It's really weird that focusout and focusin events don't have the corresponding properties for event handlers. Not sure why the HTML standard is designed this way. I will keep this improvement idea in mind.
btw: right now I don't recommend to use camelCase for on... event handlers, as it is currently reserved for a special purpose.

The support for custom event handers was added in 1.2.8: https://github.com/vanjs-org/van/discussions/246.

@all-contributors please add @MrVoltz for bug


added hover

Pull Request Checklist
Thank you for contributing to our project! Please ensure the following before submitting your pull request:
issue #26
Description of Changes
about file index.html
so i added zoom to buttons like get started, call executive and send . when we will bring cursor to it. it will zoom.
then i added light grey color when hover on concept , contact, about, sign in.
about file 1.html
if you bring the cursor to any div, it will zoom.
Type of Change

[ ] Documentation update

Checklist

[ ] I have tested my changes and ensured they work as expected.
[ ] I have added necessary documentation (if applicable).
[ ] I have reviewed my code for style and linting issues.
[ ] I have ensured that any dependent changes are merged before this PR.

Thank you so much sir for giving me an opportunity to work on your project.

Hey @Aarnachauhan, I see no changes in your PR, please make sure you have made the necessary changes or else I wont be able to merge this PR


Is there a way to ignore __typename when converting records using ppxAs?

I'm migrating some code from @bsRecord to @ppxAs and running into an issue where the record types used in @ppxAs have to define __typename. Given __typename is a GraphQL internal field to disambiguate types, is there a way not to require this field in records?
  This record expression is expected to have type
    ReactHooksTemplate.Type.subType

  The field __typename does not belong to type ReactHooksTemplate.Type.subtype

It seems like the __typename is still required even if I disable addTypename in the Apollo cache:
~cache=Cache.InMemoryCache.make(
    ~addTypename=false,
    ()
  )

Fix thanks to @jfrolich:
Set:
"graphql": {
    "apolloMode": false,
    ...
}

in bsconfig.json.


[Storage] [File Share] Fixed next pylint errors in file share

Description
Fixed all next pylint errors in queue storage except docstring-keyword-should-match-keyword-only. This is the fix for issue https://github.com/Azure/azure-sdk-for-python/issues/32634.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-file-share


Add tarball support (rebirth)

WIP for adding tarball support.
We might not want all that .subscribe() stuff :grin:

Merged for now, but this will only be a temporary solution. I'm currently working on a less hackier version.


Add type check for maxConcurrency to ensure it is a number

Fixes #243
I've added a type check to the variable maxConcurrency to see that it is a number.

Thanks for making a pull request. Is there a reason why this check is necessary?
The library already has TypeScript support if you want to be type-safe.

Hello, I believe this issue was mentioned in issue #243.
This also handles the case when maxConcurrency is undefined.

Thanks, totally forgot about that issue!
I'll have a look, add a test case and merge it into the next release!


Nhost up not applying seeds on first run

Bug description
Running nhost up for the first time does not apply seeds.
According to https://docs.nhost.io/database#seed-data they should be applied:

When you're running nhost up for the first time, seed data is added.

Adding the apply-seeds flag however does apply the seeds:
nhost up --apply-seeds true
How to reproduce

Remove .nhost folder
Run nhost up

CLI version
1.2.0

thanks for reporting this. I will release the fix tomorrow.


builder wont open

builder wont open does it need to open?

no u need to open the file named pysilon


Make the module callable from Python script

I would like to use this module from a Python script but I can't access to the main function.
I thought write quickly a script that uses bumpversion et follows the Conventional Commits convention to release my project but I'll have to do so using bash.
I didn't find anything like this on the Internet. I can't believe it... I have missed it... 🤔

@masonlouchart
https://github.com/Michael-F-Bryan/auto-changelog#usage

Got it.


Scale should be able to accept KeyVault link for servicePrincipalProfile's clientId and secret

Is this a request for help?: Yes

Is this an ISSUE or FEATURE REQUEST? (choose one): FEATURE REQUEST

What version of acs-engine?:

0.16.1

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)

Kubernetes v1.10.1

What happened:
When scaling out (adding new nodes), if the servicePrincipalProfile's clientId and secret in apimodel.json contain keyvault link, the value of aadClientId and aadClientSecret in /etc/kubernetes/azure.json will also contain keyvault link. This breaks anything that relies on these values, e.g: the automatic pull image based on cluster service principal.
What you expected to happen:

There should be a validation. It is addressed by this bug
It should also work when servicePrincipalProfile's clientId and secret are defined as key vault link.

How to reproduce it (as minimally and precisely as possible):

Have servicePrincipalProfile's clientId and secret pointing to key vault in apimodel.json, eg:

"servicePrincipalProfile": {
      "clientId": "/subscriptions/<my-subscription-id>/resourceGroups/<my-resource-group>/providers/Microsoft.KeyVault/vaults/<my-vault>/secrets/<my-secret-name>",
      "secret": "/subscriptions/<my-subscription-id>/resourceGroups/<my-resource-group>/providers/Microsoft.KeyVault/vaults/<my-vault>/secrets/<my-secret-name>"
    },

Run the following command:

acs-engine scale \
	--subscription-id $subscriptionId \
	--resource-group $resourceGroupName \
	--location $location \
	--deployment-dir "$armTemplateDirectory" \
	--new-node-count $agentPoolProfileCount \
	--node-pool $agentPoolProfileName \
	--master-FQDN "$dnsPrefix.$location.cloudapp.azure.com"

Anything else we need to know:

Similar to this issue #3105


Update JOBOWNERS to assign image build, publish, and scan jobs to agent-delivery team

The Agent Delivery team has taken ownership of the image build and release workflows, including internal deployments.

/merge


node-pre-gyp install --fallback-to-build error on node v6.9.0

3557 verbose stack Error<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
3557 verbose stack Exit status 126
3557 verbose stack     at EventEmitter.<anonymous> (/root/.nvm/versions/node/v6.9.0/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
3557 verbose stack     at emitTwo (events.js:106:13)
3557 verbose stack     at EventEmitter.emit (events.js:191:7)
3557 verbose stack     at ChildProcess.<anonymous> (/root/.nvm/versions/node/v6.9.0/lib/node_modules/npm/lib/utils/spawn.js:40:14)
3557 verbose stack     at emitTwo (events.js:106:13)
3557 verbose stack     at ChildProcess.emit (events.js:191:7)
3557 verbose stack     at maybeClose (internal/child_process.js:877:16)
3557 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

my os is centos

You may post on the wrong repo<EMAIL_ADDRESS>should be located on https://github.com/RisingStack/v8-profiler.git. Meanwhile, I tested both 5.6.5 and 5.7.0. They both can be built correctly on node 6.9.4. Maybe you need 'npm install -g nan' and give another try.


DataType error: DataType 6 is not recognized in Java (version 2.4.0)

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Android 9
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: custom
TensorFlow installed from (source or binary):org.tensorflow:tensorflow-lite:0.0.0-nightly
TensorFlow version (use command below):version 2.4.0
Python version:
Bazel version (if compiling from source):N/A
GCC/Compiler version (if compiling from source): Android SDK Java API 28
CUDA/cuDNN version: N/A - CPU
GPU model and memory: N/A

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
Loaded a TTS mel generator tflite model in java on the android target.
runForMultipleInputsOutputs function. The model takes 4 tensors as input with INT32 (1, 1), BOOL(1,1), INT32 and Float.
Trying to print and feed input tensors with type boolean and dynamic size, however, it is crashing in printing and also later in
It is printing first input tensor details, however crashes while printing the seconds tensor details
D/SnsTTS: input tensors count: 4
D/SnsTTS: tensor[0] Shape: [1, 1] data type: INT32
java.lang.IllegalArgumentException: DataType error: DataType 6 is not recognized in Java (version 2.4.0)
at org.tensorflow.lite.DataType.fromC(DataType.java:79)
at org.tensorflow.lite.Tensor.(Tensor.java:484)
at org.tensorflow.lite.Tensor.fromIndex(Tensor.java:44)
at org.tensorflow.lite.NativeInterpreterWrapper.getInputTensor(NativeInterpreterWrapper.java:303)
at org.tensorflow.lite.Interpreter.getInputTensor(Interpreter.java:423)
Describe the expected behavior
It should print the input tensor details, for boolean type and also accept it in the run function in java
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
private void printTensor(Tensor tensor, int index){
int[] shape = tensor.shape();
DataType dataType = tensor.dataType();
Log.d(Tag, "tensor[" + index + "] Shape: " + Arrays.toString(shape) + " data type: " + dataType.toString());
}
private void printInterpreterDetails(Interpreter interpreter){

    int inputTensorCount = interpreter.getInputTensorCount();
    Log.d(Tag, String.format("input tensors count: %d", inputTensorCount));
    for (int inputTensorIndex =0; inputTensorIndex<inputTensorCount; inputTensorIndex++) {
        printTensor(interpreter.getInputTensor(inputTensorIndex), inputTensorIndex);
    }

}
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Here is the link to python implementation
https://github.com/TensorSpeech/TensorflowTTS

Java API's DataType enum should be updated. Team will work on this.

Hi @ambujbansal Can you uploaded the model here so I can reproduce it quicker?

fastspeech_quant.zip
private Interpreter loadModel(String modelpath){
        try {
            FileInputStream inputStream = new FileInputStream(modelpath);
            FileChannel fileChannel = inputStream.getChannel();
            MappedByteBuffer tfliteModel = fileChannel.map(FileChannel.MapMode.READ_ONLY, 0, fileChannel.size());

            Interpreter.Options tfliteOptions = new Interpreter.Options();
            tfliteOptions.setNumThreads(1);
            Interpreter interpreter = new Interpreter(tfliteModel, tfliteOptions);
            return interpreter;
        } catch (Exception e) {
            Log.e(Tag, "Error loading model", e);
        }
        return null;
    }

It is supported at the master head.
Could you give it a try.

A fix is submitted at commit 11d919f0a51aeb835230dc3a0a36df10346eb493

i meet the same problem:
model output:
output = tf.cast(output, tf.bool)

produce the error in Android Studio
E/libc: Access denied finding property "ro.hardware.chipname"
E/AndroidRuntime: FATAL EXCEPTION: CameraBackground
    Process: android.example.com.tflitecamerademo_mobilenet2unet_KrzysztofV_9, PID: 6336
    java.lang.IllegalArgumentException: DataType error: DataType 6 is not recognized in Java (version 2.4.0)
        at org.tensorflow.lite.DataType.fromC(DataType.java:79)
        at org.tensorflow.lite.Tensor.<init>(Tensor.java:484)
        at org.tensorflow.lite.Tensor.fromIndex(Tensor.java:44)
        at org.tensorflow.lite.NativeInterpreterWrapper.getOutputTensor(NativeInterpreterWrapper.java:326)
        at org.tensorflow.lite.NativeInterpreterWrapper.run(NativeInterpreterWrapper.java:170)
        at org.tensorflow.lite.Interpreter.runForMultipleInputsOutputs(Interpreter.java:343)
        at org.tensorflow.lite.Interpreter.run(Interpreter.java:304)
        at com.example.android.mobilenet2unet_KrzysztofV_9.ImageSegmentorFloatMobileUnet.runInference(ImageSegmentorFloatMobileUnet.java:148)
        at com.example.android.mobilenet2unet_KrzysztofV_9.ImageSegmentor.segmentFrame(ImageSegmentor.java:134)
        at com.example.android.mobilenet2unet_KrzysztofV_9.Camera2BasicFragment.segmentFrame(Camera2BasicFragment.java:1060)
        at com.example.android.mobilenet2unet_KrzysztofV_9.Camera2BasicFragment.access$1100(Camera2BasicFragment.java:103)
        at com.example.android.mobilenet2unet_KrzysztofV_9.Camera2BasicFragment$11.run(Camera2BasicFragment.java:943)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:241)
        at android.os.HandlerThread.run(HandlerThread.java:67)

@AR-fan Can you specify the exact version of TFLite you are using?
If you are using nightly, what exact date is that nightly version? Otherwise, what is used in your gradle file?

@thaink I also have the sane problem with tensorflow.
Exception in thread "main" java.lang.IllegalArgumentException: DataType 20 is not recognized in Java (version 1.15.0)
at org.tensorflow.DataType.fromC(DataType.java:85)
at org.tensorflow.Tensor.fromHandle(Tensor.java:540)
at org.tensorflow.Session$Runner.runHelper(Session.java:343)
at org.tensorflow.Session$Runner.run(Session.java:276)
at tftest3.main(tftest3.java:46)
it has similar issue with tensflor-lite as well #1079

ReportProblem.zip
Here, I create the model by runing "runMe.py" in "CreateModelWithPythonTensorflow" and saved the model in "model".
The maven project is given. I get the same problem. I added all files that may help to solve this issue.
Here is the output if you run the Java project:
`test_images\test_00001.png
28-28
1
4
inputTensor is: FLOAT tensor with shape [1, 28, 28, 1]
FLOAT
1.15.0
2021-03-20 03:47:26.040919: I tensorflow/cc/saved_model/reader.cc:31] Reading SavedModel from: CreateModelWithPythonTensorflow/model
2021-03-20 03:47:26.042983: I tensorflow/cc/saved_model/reader.cc:54] Reading meta graph with tags { serve }
2021-03-20 03:47:26.046158: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2021-03-20 03:47:26.058207: I tensorflow/cc/saved_model/loader.cc:202] Restoring SavedModel bundle.
2021-03-20 03:47:26.091805: I tensorflow/cc/saved_model/loader.cc:151] Running initialization op on SavedModel bundle at path: CreateModelWithPythonTensorflow/model
2021-03-20 03:47:26.099182: I tensorflow/cc/saved_model/loader.cc:311] SavedModel load for tags { serve }; Status: success. Took 58246 microseconds.
predicting...
Exception in thread "main" java.lang.IllegalArgumentException: DataType 20 is not recognized in Java (version 1.15.0)
at org.tensorflow.DataType.fromC(DataType.java:85)
at org.tensorflow.Tensor.fromHandle(Tensor.java:540)
at org.tensorflow.Session$Runner.runHelper(Session.java:343)
at org.tensorflow.Session$Runner.run(Session.java:276)
at TfDataTypeIssue.main(TfDataTypeIssue.java:43)
`

@micosacak TF 1.15 version is too old to be supported. Could you try upgrading your code to the recent TF version?

I use tensorflow 2.2. in Python. In java, the latest version is 1.15.

@micosacak could you file a separate issue? The original case is for the TensorFlow Lite library while your case is about TensorFlow java API. They are different and it would be better to address them separately.

@ambujbansal It looks like you are using an older Version of Tensorflow . Many bugs have been fixed in the latest version. Could you please execute your code using Latest Version 2.4.1 or 2.5 and let us know if the issue still persists? Thanks!


merge from template-arlac77-github

package.json

chore(deps): add ^4.3.0 remove ^4.2.0 (devDependencies.ava)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update virtual-machines-share-images-across-tenants.md

Add recent "gotcha" from customer as a note.

@jpmicrosoft : Thanks for your contribution! The author(s) have been notified to review your proposed change.


backend_1   | { code: -32000, message: 'unknown block' }

Hey I am trying to find a resolution to this, also in the future can we have a FAQ/wiki for common problems or error code and fixes.
Thanks
last log
backend_1   |   "PERMANENT_CLEANUP_INTERVAL_MS": 10000, backend_1   |   "MAX_PER_PAGE": 1000, backend_1   |   "DEFAULT_ERC20_TOKEN_PRECISION": 18 backend_1   | } backend_1   | { code: -32000, message: 'unknown block' }

What are you using for a node? This is a common error that Infura returns if it's under heavy load or the request fails.

Setup a (new) account with infura.io, created a project, used that link to Rinkeby via https, but ...
same problem here. Can't post an order, or looks more like as if they can not be retrieved.
GET http://localhost:3000/v3/orders?makerAssetData=0xf47261b00000000000000000000000008080c7e4b81ecf23aa6f877cfbfd9b0c228c6ffa&page=1&takerAssetData=0xf47261b0000000000000000000000000c778417e063141139fce010982780140aa0cd5ab 404 (Not Found)

orderbook:1 GET http://localhost:3000/v3/orderbook?baseAssetData=0xf47261b00000000000000000000000008080c7e4b81ecf23aa6f877cfbfd9b0c228c6ffa&quoteAssetData=0xf47261b0000000000000000000000000c778417e063141139fce010982780140aa0cd5ab 404 (Not Found)
backend.js:6 0x-launch-kit-frontend::Store::Market::Actions getAllOrders: fetch orders from the relayer failed.


Install script is no longer working

Installation script from the Readme is no longer working:
curl --proto '=https' --tlsv1.2 -sSf https://just.systems/install.sh | bash -s -- --to ~/bin

It looks like https://github.com/casey/just/releases/latest returns nothing, so $tag is invalid.
I didn't find any github docs about it, but saw some places would use this url instead: https://api.github.com/repos/casey/just/releases/latest.. Can it be some sort of deprecation of old API in favor to a new one?
Error output:
root@9f4e1c04e525:/# curl --proto '=https' --tlsv1.2 -sSf https://just.systems/install.sh | bash -s -- --to ~/bin
install: Repository:  https://github.com/casey/just
install: Crate:       just
install: Tag:
install: Target:      x86_64-unknown-linux-musl
install: Destination: /root/bin
install: Archive:     https://github.com/casey/just/releases/download//just--x86_64-unknown-linux-musl.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Thanks for the detailed issue! I opened #1172 with a fix, using the API URL as you suggested.


fix Entrypoint to use Base image entrypoint

This PR is a fix for https://github.com/eclipse-che/che/issues/23281
This PR also removes the run of stow during the build.  Running stow during the image build creates /home/user/.config resulting in .config being owned by root.
.config being owned by root breaks podman v5+

The build fails because the latest version of gopls is incompatible with the latest available version of go available in the ubi-9-appstream-rpms repo, I've made this PR to fix the gopls version to fix the build: https://github.com/devfile/developer-images/pull/207

The build fails because the latest version of gopls (which was released yesterday) is incompatible with the latest available version of go available in the ubi-9-appstream-rpms repo, I've made this PR to fix the gopls version to fix the build: #207

I will close this PR and resubmit with the latest from main

Superseded by https://github.com/devfile/developer-images/pull/208


docs: update README

docs: add CLI usage
docs: add special thanks
test: remove example tests from cmd/jsondiff

Codecov Report

Merging #11 (ed6cec8) into main (3a89d8b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   68.84%   68.84%
=======================================
  Files           2        2
  Lines         199      199
=======================================
  Hits          137      137
  Misses         44       44
  Partials       18       18

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 3a89d8b...ed6cec8. Read the comment docs.


No request data with django

I recently decided to switch from Raven to sentry-sdk version 0.7.3.
When an event was reported using Raven I use to have many useful tags (the URLs originating the error, the user browser/device, OS information and much more). All this comes out of the box without the need to include any scripts in the frontend.
Despite sentry-sdk has simplified the configuration process I find myself with a weaker error tracking system (fewer information on each event).
I am working on a Django project and followed the docs
Am I missing something?

The tags you see are generated serverside and are inferred from HTTP headers and the current URL. All of this should be there when you turn on the Django integration. We're using this for Sentry itself and it generally is supposed to work.
From what you've told me it seems that you generally have no request data attached to your events. Could you paste the exact code you're using, and more importantly, where do you call init of the SDK?

@bluesurfer any update on this? This seems like a bug in the SDK, even if just a UX bug.

@untitaker oops, sorry for delay.. I just put the docs code (with init sentry) at the end of my settings file and I haven't defined any LOGGING configuration.

From what you've told me it seems that you generally have no request data attached to your events.

Yes, that's the issue. My previously working logging configuration with Raven was:
# Raven
# ------------------------------------------------------------------------------
INSTALLED_APPS += ['raven.contrib.django.raven_compat']  # noqa F405
MIDDLEWARE = ['raven.contrib.django.raven_compat.middleware.SentryResponseErrorIdMiddleware'] + MIDDLEWARE

# Sentry
# ------------------------------------------------------------------------------
SENTRY_DSN = env('DJANGO_SENTRY_DSN')
SENTRY_CLIENT = env('DJANGO_SENTRY_CLIENT', default='raven.contrib.django.raven_compat.DjangoClient')
LOGGING = {
    'version': 1,
    'disable_existing_loggers': True,
    'root': {
        'level': 'WARNING',
        'handlers': ['sentry'],
    },
    'formatters': {
        'verbose': {
            'format': '%(levelname)s %(asctime)s %(module)s '
                      '%(process)d %(thread)d %(message)s'
        },
    },
    'handlers': {
        'sentry': {
            'level': 'ERROR',
            'class': 'raven.contrib.django.raven_compat.handlers.SentryHandler',
        },
        'console': {
            'level': 'DEBUG',
            'class': 'logging.StreamHandler',
            'formatter': 'verbose'
        }
    },
    'loggers': {
        'django.db.backends': {
            'level': 'ERROR',
            'handlers': ['console'],
            'propagate': False,
        },
        'raven': {
            'level': 'DEBUG',
            'handlers': ['console'],
            'propagate': False,
        },
        'sentry.errors': {
            'level': 'DEBUG',
            'handlers': ['console'],
            'propagate': False,
        },
        'django.security.DisallowedHost': {
            'level': 'WARNING',
            'handlers': ['console', 'sentry'],
            'propagate': False,
        },
    },
}

SENTRY_CELERY_LOGLEVEL = env.int('DJANGO_SENTRY_LOG_LEVEL', logging.INFO)
RAVEN_CONFIG = {
    'dsn': SENTRY_DSN
}

Than using sentry-sdk I simply put:
import sentry_sdk
from sentry_sdk.integrations.django import DjangoIntegration

sentry_sdk.init(
    dsn=SENTRY_DSN,
    integrations=[DjangoIntegration()]
)

Which version of Django and Python are you using?

@untitaker Django 2.1.7 with python 3.6.7.

I am also experiencing the same thing. Very similar setup to the one described by @bluesurfer. The Raven Python setup included a 'Cookies' section as well as better 'User' information (these both seem to be Django request object information).

@bcollazo @untitaker I have some updates.
I am following cookiecutter-django repository to lay down my project. It seems that with recent updates (also from sentry-sdk) the following configuration to me is working:
# LOGGING
# ------------------------------------------------------------------------------
LOGGING = {
    "version": 1,
    "disable_existing_loggers": True,
    "formatters": {
        "verbose": {
            "format": "%(levelname)s %(asctime)s %(module)s "
                      "%(process)d %(thread)d %(message)s"
        }
    },
    "handlers": {
        "console": {
            "level": "DEBUG",
            "class": "logging.StreamHandler",
            "formatter": "verbose",
        }
    },
    "loggers": {
        "django.db.backends": {
            "level": "ERROR",
            "handlers": ["console"],
            "propagate": False,
        },
        # Errors logged by the SDK itself
        "sentry_sdk": {"level": "ERROR", "handlers": ["console"], "propagate": False},
        "django.security.DisallowedHost": {
            "level": "ERROR",
            "handlers": ["console"],
            "propagate": False,
        },
    },
}

# Sentry
# ------------------------------------------------------------------------------
SENTRY_DSN = env("SENTRY_DSN")
SENTRY_LOG_LEVEL = env.int("DJANGO_SENTRY_LOG_LEVEL", logging.INFO)

sentry_logging = LoggingIntegration(
    level=SENTRY_LOG_LEVEL,  # Capture info and above as breadcrumbs
    event_level=logging.ERROR,  # Send no events from log messages
)

sentry_sdk.init(
    dsn=SENTRY_DSN,
    integrations=[sentry_logging, DjangoIntegration(), CeleryIntegration()],
)

Therefore to me this issue could be closed.

Ah that's neat, I wasn't aware of https://github.com/pydanny/cookiecutter-django/pull/1820!
Tbh I think it's highly unlikely that @bluesurfer has the same actual problem as you, @bcollazo. Could you open a new issue with more information?

We are also facing the same issue
We are not getting the Django request data info in sentry console with updated sentry SDK
With old raven Django client, there is no issue about getting request data in sentry
We are getting request data in sentry console, only if there is some exception raised before our program did access the request.body
We are getting can't read requst data once its already read error at sentry_sdk.integrations.django.DjangoRequestExtractor#raw_data

@anush0247 could you link an event that exhibits this behavior?

@untitaker please find below link
https://sentry.io/organizations/backend-developers/issues/1054285117/?project=240166&query=is%3Aunresolved

@bcollazo @untitaker I have some updates.
I am following cookiecutter-django repository to lay down my project. It seems that with recent updates (also from sentry-sdk) the following configuration to me is working:
# LOGGING
# ------------------------------------------------------------------------------
LOGGING = {
    "version": 1,
    "disable_existing_loggers": True,
    "formatters": {
        "verbose": {
            "format": "%(levelname)s %(asctime)s %(module)s "
                      "%(process)d %(thread)d %(message)s"
        }
    },
    "handlers": {
        "console": {
            "level": "DEBUG",
            "class": "logging.StreamHandler",
            "formatter": "verbose",
        }
    },
    "loggers": {
        "django.db.backends": {
            "level": "ERROR",
            "handlers": ["console"],
            "propagate": False,
        },
        # Errors logged by the SDK itself
        "sentry_sdk": {"level": "ERROR", "handlers": ["console"], "propagate": False},
        "django.security.DisallowedHost": {
            "level": "ERROR",
            "handlers": ["console"],
            "propagate": False,
        },
    },
}

# Sentry
# ------------------------------------------------------------------------------
SENTRY_DSN = env("SENTRY_DSN")
SENTRY_LOG_LEVEL = env.int("DJANGO_SENTRY_LOG_LEVEL", logging.INFO)

sentry_logging = LoggingIntegration(
    level=SENTRY_LOG_LEVEL,  # Capture info and above as breadcrumbs
    event_level=logging.ERROR,  # Send no events from log messages
)

sentry_sdk.init(
    dsn=SENTRY_DSN,
    integrations=[sentry_logging, DjangoIntegration(), CeleryIntegration()],
)

Therefore to me this issue could be closed.

라고 쓰여있는게 있길래 이 사람은 cookiecutter-django 를 써서 뭔가 해결해서 자신에게는 closed 라고 하는걸로 알았어요

@untitaker any update ?

Still working on it, I think I know what the issue is. Thanks for the
information so far!
On Wed, Jun 19, 2019 at 5:59 AM Aneesh Kumar<EMAIL_ADDRESS>wrote:

@untitaker https://github.com/untitaker any update ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/getsentry/sentry-python/issues/267?email_source=notifications&email_token=AAGMPRJG6AOIRCY7X67MWO3P3GVKHA5CNFSM4GYLHTG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYATSHA#issuecomment-503396636,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGMPRPMLESYODSOIVP2YW3P3GVKHANCNFSM4GYLHTGQ
.

PR at #393... I am pretty sure the issue is with django-rest-framework and not Django.

0.9.1 is out with this fix :) I hope it fixes all cases, but certainly should fix a few of them

@untitaker I am getting circular settings import issue after upgrading to 0.9.1
please check below stack trace once
File ".venv/local/lib/python2.7/site-packages/sentry_sdk/hub.py", line 74, in init
    client = Client(*args, **kwargs)
  File ".venv/local/lib/python2.7/site-packages/sentry_sdk/client.py", line 88, in __init__
    options["integrations"], with_defaults=options["default_integrations"]
  File ".venv/local/lib/python2.7/site-packages/sentry_sdk/integrations/__init__.py", line 80, in setup_integrations
    type(integration).setup_once()
  File ".venv/local/lib/python2.7/site-packages/sentry_sdk/integrations/django/__init__.py", line 128, in setup_once
    from rest_framework.views import APIView  # type: ignore
  File ".venv/local/lib/python2.7/site-packages/rest_framework/views.py", line 18, in <module>
    from rest_framework import exceptions, status
  File ".venv/local/lib/python2.7/site-packages/rest_framework/exceptions.py", line 17, in <module>
    from rest_framework.utils.serializer_helpers import ReturnDict, ReturnList
  File ".venv/local/lib/python2.7/site-packages/rest_framework/utils/serializer_helpers.py", line 9, in <module>
    from rest_framework.compat import unicode_to_repr
  File ".venv/local/lib/python2.7/site-packages/rest_framework/compat.py", line 156, in <module>
    from django.contrib.postgres import fields as postgres_fields
  File ".venv/local/lib/python2.7/site-packages/django/contrib/postgres/fields/__init__.py", line 1, in <module>
    from .array import *  # NOQA
  File ".venv/local/lib/python2.7/site-packages/django/contrib/postgres/fields/array.py", line 3, in <module>
    from django.contrib.postgres import lookups
  File ".venv/local/lib/python2.7/site-packages/django/contrib/postgres/lookups.py", line 4, in <module>
    from .search import SearchVector, SearchVectorExact, SearchVectorField
  File ".venv/local/lib/python2.7/site-packages/django/contrib/postgres/search.py", line 47, in <module>
    class SearchVector(SearchVectorCombinable, Func):
  File ".venv/local/lib/python2.7/site-packages/django/contrib/postgres/search.py", line 50, in SearchVector
    _output_field = SearchVectorField()
  File ".venv/local/lib/python2.7/site-packages/django/db/models/fields/__init__.py", line 172, in __init__
    self.db_tablespace = db_tablespace or settings.DEFAULT_INDEX_TABLESPACE
  File ".venv/local/lib/python2.7/site-packages/django/conf/__init__.py", line 56, in __getattr__
    self._setup(name)
  File ".venv/local/lib/python2.7/site-packages/django/conf/__init__.py", line 41, in _setup
    self._wrapped = Settings(settings_module)
  File ".venv/local/lib/python2.7/site-packages/django/conf/__init__.py", line 129, in __init__
    raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.

@anush0247 the issue has been reported as #397 and is fixed in 0.9.2 :)

@untitaker thank you it's working now


STRIPE_API_KEY issues within Google Cloud Manager

Bug report

Extension name: firestore-stripe-payments
https://extensions.dev/extensions/stripe/firestore-stripe-payments

Describe the bug
I created separate Firebase Project for Dev/Prod and noticed that I was getting the errors in the firebase-debug.log that were stating that NO API KEY was being provided on my checkout session requests. A lot of digging later and I think that there may be an issue related to how the extension is handling the STRIPE_API_KEYS
Details:
After configuring the Stripe Extension via the Firebase Console I'm seeing 2x 'secret' keys being added to Google 'Secret Manager' for the STRIPE_API_KEY

firestore-stripe-payments-STRIPE_API_KEY
firestore-stripe-payments-STRIPE_API_KEY**-XXXX**

where XXXX appears to be lowercase letters/numbers
If I look at the auto-generated ./extensions/firestore-stripe-payments.env file it seems to reference the -XXXX version
STRIPE_API_KEY=projects/${param:PROJECT_NUMBER}/secrets/firestore-stripe-payments-STRIPE_API_KEY-XXXX/versions/latest
Expectations: It should only have one value in Secret Manager for EACH project for the API KEY within Google Cloud Manager
Issues Caused:

If you have separate Firebase projects for each environment (e.g. DEV / PROD) then each will have a different -XXXX appended to it. This means the automatically generated .env won't work when changing env without manual modification of the .env files
When reconfiguring the extension, the STRIPE_API_KEY's within Secret Manager can become inconsistent.
Example: I reconfigured in Firebase Console for my PROD Firebase Project to use the production key (originally it was using 'test' keys).
After which:
On my PROD env
firestore-stripe-payments-STRIPE_API_KEY-XXXX is my prod key (correct)
firestore-stripe-payments-STRIPE_API_KEY is my dev/test key (error)

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Configure or Reconfigure the Firebase Run Payments with Stripe extension.
Expected behavior

There only to be one reference to STRIPE_API_KEY within Google Cloud Manager after configuring or reconfiguring the extension.
Not to have the -XXXX appended in the filename so that changing between different env/Firebase projects was easier.
If there was a reason to have 2x STRIPE_API_KEY's within Secret Manager that they would remain consistent after reconfiguring the extension via Firebase console.

Additional expectation (more feature request) that the Stripe Extension would have allowed you to configure both a 'Test' and 'Prod' key for a single project. This supports the workflow for local testing on emulators to pushing to production online.
Screenshots
If applicable, add screenshots to help explain your problem.
System information

Windows running WSL2 (Ubuntu)

Additional context
Add any other context about the problem here.

@jsteele-stripe can you take a look at this? It's been dormant for quite a while, but is being raised as a critical issue in the Firebase Me Discord community


ACA-42 - Multiple Organisation Policies in Assign Access within Organisation

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/ACA-42
Change description
Multiple Organisation Policies in Assign Access within Organisation
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x] No

not required as other has these changes https://github.com/hmcts/aac-manage-case-assignment/pull/49


Ignore UIMs that contains INLINE_PAGE

@Sena22 change your target branch to the feature branch luiza-parser

@Sena22 change your target branch to the feature branch luiza-parser

Done @grahamharper, I did select the luiza-parser branch the first place, not sure how it got switched.


Update README.md

strcutre -> structure

Thanks! merged.

Opps, its merged into develop branch.  Is it correct?(develop is not active at this time)

It is the correct README.md.
About that, I do not know which version to use from the repository.
I am building a simple ray-tracer and want to use the vertices from an object file.
What is the best version to use? From master?

Since v1.0.0, master is the active and recommended branch. develop is now a bit older and not recommended for the use.


fix(chat): fix disable Delete when Code app deployed (Issue #2692)

Description:
Delete option should be displayed for Code app in deployed state
Issues:

Issue #2692

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


python make.py html failure

nils@linux-5fmr:~/git/pandas/doc> python make.py html
Traceback (most recent call last):
File "/home/nils/local/bin/sphinx-build", line 5, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2829, in
working_set.require(requires)
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 706, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 604, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: Sphinx==1.3b2dev-20141122
Building HTML failed.
nils@linux-5fmr:~/git/pandas/doc> sphinx-build --version
Sphinx (sphinx-build) 1.3b2

I am closing this as we have not enough information to help or reproduce. @nilswagner If you still have this problem, feel free to re-open and provide more info!


VIP-744: Add notify flag to optionally suppress dashboard emails

https://github.com/votinginfoproject/Metis/pull/561
https://github.com/votinginfoproject/vip_admin/pull/326

This change contains 3 parts:

vip_admin sends the notify? flag to data-processor on the queue
data-processor does its thing and then passes that flag through to its completion message
the completion message gets picked up by Metis and then we use the flag to suppress emails

I tested 1-2 on QA. #3 seems hard to test in QA, so for now I believe this change is safe enough to push to staging. If for some reason the flag doesn't make it to Metis, accessing a non-existent property from a js object will just return undefined, which shouldn't break anything


Bmi calculator

Related Issue
Improvement in BMI Calculator (GSSoC'21)
Closes: #511
Describe the changes you've made

Alignment of text to the center, change in size and font of the text.
Change in shape of button and Change in the background.
Changed logo image and addition of box shadow.
updated GIF in script.js.

Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Checklist:

[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.
[ ] I have made corresponding changes to the documentation.
[x] New and existing unit tests pass locally with my changes.

Screenshots
Earlier-

NOW-

@Vishal-raj-1 @urvashi-code1255 @991rajat @harshgupta20 Please Review my PR.

@urvashi-code1255 Yes ,I have already updated it.

@urvashi-code1255 Thank you : )

@yashikabhargava  That looks like my design.


Fix various UI and Playback issues on mobile browser

What this PR does
Fix various UI issues and make background playback on mobile possible.
Fixes

<body> sizing error: vh, vw works like lvh, lvw in Safari which makes part of <body> appears behind browser UI
scrolling bug cause by uneven elements size in <DynamicScroller>: for touch screen, where scrolling up cause the page to jump back to item (index) 1. fixed for Artist and NowPlaying view
dropdown arrow icon wrong sizing in safari
playback won’t automatically continue/start when loading next song (pause then unpause fix it): this issue caused by Autoplay Policy. see #229, #212
.profiledrop display behind .smdropdown element
now playing on Tablet didn't show playback slide

Known Issues (that I can't/didn't fix)

mediaSession in Safari will track the fading-out song and misunderstood that the playback has ended (and pause the mediaSession), manually set it as "playing" did nothing.
when seeking to the last 30 seconds of the song, Safari would misunderstood that the playback has stopped.

Testing
Tested on Android, IOS and Desktop devices I have, with the following browsers:

Google Chrome (Android)
Google Chrome (IOS)
Safari (IOS)
Arc Search (IOS)
Arc (Windows)
Microsoft Edge (Windows)

Hi @Type-Delta
Thank you very much for opening this PR. I really appreciate the fixes you have done.
I've pulled your branch and tested the playback on Chrome for Android and it's working fine even on a locked screen. Amazing. I wasn't using the web client on mobile that much so I hadn't experienced some of the other issues you have fixed.
Thanks again for the fixes. Merging ...
About the 30 seconds thing. Might it be an issue with the silence padding removal feature? See https://github.com/swingmx/swingmusic/issues/231. Can you please try disabling that feature as mentioned on the issue and see whether it fixes it?
Please let me know whether it works.

Hi, @cwilvx
After a bit more testing, turns out it has something to do with how Safari tracks Audio elements.
The issue occurred from the changed in value of audio.src which caused the playback state of said
Audio element to be "paused" and confused the mediaSession.
And No, this had nothing to do with silence padding removal feature.
From my understanding, Safari tracks audio.src changes along with user interaction,
if the changes came from or right around user interaction events it would track the
changed Audio, recognize it as "paused" (it haven't been played yet) and update mediaSession accordingly.
Since preloading function is set up to run when the playback position of the current track is more than
the last 30 seconds, the moment user seek to that portion, the preload function would immediately fired, changing audio.src
of the standbySource to a new URL, triggering Safari to do its thing.
For the fix: I've tried preventing preload function from firing immediately with setTimeout(), but to no avail. :(
I'll came back to this problem later if I got any new ideas to try, though.

@Type-Delta
Thank you very much for looking into that issue. Let me know if you get any fixes.
Regarding the silence padding removal related issue, it happened when the silence data returns too late and the player module didn't handle that problem. It happened when the track happened when the track has a silence padding of more than 30s at the end of the file or when the network is slow (mostly on remotely selfhosted instances)
I've fixed that with this commit on a feature branch I'm working on.
Thank you again. Your contributions are welcome and very much appreciated.

Hey @Type-Delta
I went ahead and overwrote your commit with this one.
As the viewport shrinks, the bottom bar area is moved to the now-playing page gradually. Hope that's alright.

@Simonh2o
I don't mind at all, plus it makes the UX a bit smoother for everyone.
I have nothing complaints but, thanks for making it better! 😄


[SS][MINOR] Make EventTimeWatermarkExec explicitly UnaryExecNode

What changes were proposed in this pull request?
Making EventTimeWatermarkExec explicitly UnaryExecNode
/cc @tdas @zsxwing
How was this patch tested?
Local build.

Test build #79081 has started for PR 18509 at commit 2cc9fdc.

Test build #79081 has finished for PR 18509 at commit 2cc9fdc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79081/
Test PASSed.

Thanks! Merging to master.


[channels,settings] add a setting to ignore invalid devices

Add a setting IgnoreInvalidDevices. This is an escape hatch to optionally revert the behaviour of df4c076 - in #8909 we see a case where a server sends an IRP for an non-existent device, despite all rdpdr forwarding options being disabled.
If IgnoreInvalidDevices is set to TRUE, rdpdr will send a dummy response instead of returning an error (and preventing the connection from succeeding).

@freerdp-bot test

I just stumbled this error also. Might worth making this a default?

@hedwigz no, definitely not.
if you have any issue please provide some details, that is a bug!

@akallabeth We might be able to provide some more information in this topic.
What I see is the following log output when running from the command line: xfreerdp3 /u:username /v:hostname:
[15:26:53:900] [2487:000009ca] [WARN][com.freerdp.channels.rdpdr.client] - [devman_get_device_by_id]: could not find device ID 0xffffffff
[15:26:53:900] [2487:000009ca] [ERROR][com.freerdp.channels.rdpdr.client] - [rdpdr_process_irp]: irp_new failed with 55!
[15:26:53:900] [2487:000009ca] [ERROR][com.freerdp.channels.rdpdr.client] - [rdpdr_process_receive]: rdpdr_process_irp failed with error 55
[15:26:53:900] [2487:000009ca] [ERROR][com.freerdp.channels.rdpdr.client] - [rdpdr_virtual_channel_client_thread]: rdpdr_process_receive failed with error 55!
[15:26:53:900] [2487:000009b8] [ERROR][com.freerdp.core] - [checkChannelErrorEvent]: rdpdr_virtual_channel_client_thread reported an error. Error was 55
[15:26:53:900] [2487:000009b8] [ERROR][com.freerdp.core] - [freerdp_check_event_handles]: checkChannelErrorEvent() failed - 0
[15:26:53:900] [2487:000009b8] [INFO][com.freerdp.client.common] - [client_auto_reconnect_ex]: Network disconnect!

We don't have resources forwarded - actually using xfreerdp from the command line to test without resource options set and non is activated by default as far as I see in the manual.
One very interesting finding a colleague made is that this error only starts to arise when the system we try connect to is joined to a AD domain. But on the other hand I have read through other topics like https://github.com/FreeRDP/FreeRDP/issues/10138 and none of those things (disabling kerberos, host name resolution fix in krb5.conf) made any difference in our case.
As well this only happens with the recent version 3.x but not with the 2.x versions of XFreeRDP.
Find a diff between logs before and after joining an AD domain here: https://www.diffchecker.com/lD26xB6L
Also see my post in another forum (https://forum.devolutions.net/topics/39314/rdp-is-not-able-to-connect--2023171) where the responder pointed me to this topic here.
Thanks in advance!

@Sebastian-Roth this looks like a different issue, could you please open a new issue for that?

What I can think of here is that in your environment smartcard redirection is enforced (to log in with one) and something is not handled correctly.
the devolutions topic is correct as far as kerberos is concerned, it has nothing to do with this.

I opened a new issue - I also have this problem (for about 1 year) ...
issue 10807


Provides the groupId in the API calls headers

Provides the groupId in the API calls headers

Closes #111


LaTeX doc-view pane interacts annoyingly with the feature that asks to reload modified files

Whenever I save my TeX files, the preview pane uploads, as needed, but then, I get asked:
Please answer y or n.  File <filename>.pdf changed on disk.  Reread from disk? (y or n)

which kind of defeats the purpose of the doc-view pane since it has already been re-read.

Are you still experiencing this issue on the latest commit of Doom?


Redirect loop in debug builds using StrictMode with React 18.0.0-rc.0

Describe the problem
I experience a redirect loop using withAuthenticationRequired with React v18 (rc) in debug builds with webpack-dev-server when StrictMode is enabled. Everything works fine in production builds (webpack-dev-server not involved) or when disabling StrictMode.
My implementation is very similar to https://auth0.com/blog/complete-guide-to-react-user-authentication/ with minimal adjustments for react-router v6.
I reckon this is related to StrictMode changes in v18 (was mentioned at React Conf 2021).
Environment
"@auth0/auth0-react": "^1.8.0"
"react": "^18.0.0-rc.0"
"react-router-dom": "^6.2.1"
"webpack-dev-server": "^4.7.0"

Hi @peterhirn - we don't currently support react 18, but thanks for the heads up
I updated the example app to react 18 and couldn't reproduce the issue you've described - but happy to debug a reproducible example if you can provide one.
There is an issue with Strict Effects and withAuthenticationRequired which is causing loginWithRedirect to be called twice (because when strict effects are enabled, React intentionally double-invokes effects) which we will have to address when v18 is released and we add support for it.

Hi. Thanks for trying to reproduce, might be some other issue in my app. I'll try to create a minimal example.

Thanks @peterhirn - if you create an example the reproduces the issue, let me know and I'll reopen this


MSB4148: The name of a property stored under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0" has zero length

Node Version: v8.12.0
Npm: 6.4.1
Platform: Windows 10
Compiler: Visual C++ compiler
Module: node-usb | restify

Verbose output (from npm or node-gyp):

C:\Users\Glaucia Lemos\Downloads\Downloads\Backup - Comp Glaucia\Palestras\Apresentação - Semana da Mulher - ChatBot\semana-meninas-mulheres-ciencia>npm install

><EMAIL_ADDRESS>install C:\Users\Glaucia Lemos\Downloads\Downloads\Backup - Comp Glaucia\Palestras\Apresentação - Semana da Mulher - ChatBot\semana-meninas-mulheres-ciencia\node_modules\dtrace-provider
> node-gyp rebuild || node suppress-error.js

C:\Users\Glaucia Lemos\Downloads\Downloads\Backup - Comp Glaucia\Palestras\Apresentação - Semana da Mulher - ChatBot\semana-meninas-mulheres-ciencia\node_modules\dtrace-provider>if not defined npm_config_node_gyp (node "C:\Users\Glaucia Lemos\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Users\Glaucia Lemos\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Compilando os projetos desta solução um de cada vez. Para habilitar o build paralelo, adicione a opção "/m".
 System Windows_NT 10.0.17134
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Glaucia Lemos\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Glaucia Lemos\Downloads\Downloads\Backup - Comp Glaucia\Palestras\Apresentação - Semana da Mulher - ChatBot\semana-meninas-mulheres-ciencia\node_modules\dtrace-provider
gyp ERR! node -v v8.12.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
added 176 packages from 339 contributors and audited 372 packages in 8.55s
found 0 vulnerabilities

Hi guys! So... I've been while trying to execute node-gyp on my Windows 10. but without success. I've tried everything. Even the suggestion of the @refack here #1144. But no success.
I even install the VS 2015 and VS 2017 as you already said here on the documentation, but failed.
This is the message that appears in my screen:
MSB4148: The name of a property stored under the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0" has zero length.

I would like ask your help about it. Once I have been trying to install some packages use node-gyp and I can't continue to develop my projects.
Anyone here already resolve this issue?

After a quick search I've found this: https://blogs.msdn.microsoft.com/visualstudio/2010/02/26/my-visual-studio-2008-is-broken-after-uninstalling-net-framework-4-0/, maybe give it a try?

@bzoz I will try to make a uninstall here my VS 2017 and then I will return here if works! ;)

Doesn't worked it! :(

AFAICT this looks like a bug in the MSVS install... So maybe also report this issue at https://github.com/Microsoft/msbuild
As a workaround you could try importing this regfile https://gist.github.com/refack/363ee65cb3a9a9c5f59f1977cdbf5fc8

@refack I uninstall everything on my machine here.  I have done all the documentation procedures of the node-gyp and the error persists.
I've removed: VS 2017 and all subfolders. Everything.

Now I don't know what can be... :(

Well my first guess would be that it has something to do with your locale. You could try to search you registry for this value MSBuildRuntimeVersion for example. It might be in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\VersõesDeFerramentas ;)

Another thing you can try is to run node-gyp in a Developer Command Prompt for VS 2017 (cmd after running VsDevCmd.bat)

I will try here again and then I will report you! Thanks a lot again! :)

@refack  I formatted my computer. I installed the node-gyp, but at the time of knowing the version of it appears this error:

Going to close this issue once I formatted my computer and this error disappear.

I still have this issue, and I'm not willing to format my computer...


Fix typing issue in inference_utils.py

Looks like TextRegions and list[TextRegion] weren't consistent here. This was causing the following error in build_layout_elements_from_ocr_regions
AttributeError: 'list' object has no attribute 'element_coords'

While I was trying to partition this PDF with the hi_res strategy.
Update so that grouped_regions is always a list[TextRegions] and convert each TextRegions to a list[TextRegion] before running merge_text_regions on each element.

What versions of unstructured and unstructured-inference libraries are you using?


Any examples with animations?

I'd like to be able to prevent loading the route before an animation is done, issue the route change, and then have a loading in animation.
So something like:
onRouteChange = e => {
    e.preventDefault()
    document.body.classList.remove('anim-in')
    document.body.classList.add('anim-out')
    document.body.addEventListener('animationend', () => {
        issueRouteChange()
        document.body.classList.add('anim-in')
    }
}

obviously psuedocode

I didn't try this yet but here is some information that might be helpful: https://github.com/zeit/next.js/issues/88

Hey @fridays,
in order to prevent the top-level component from unmounting, I'm thinking about using a single page pages/index.js which is responsible for choosing which component to render.
But I don't know how to use this method with next-routes because I need a way to tell the index.js page which component it should render via the routes definition, maybe something like explicit params.
// routes.js
routes.add('blog', '/blog', 'index', {component: "BlogList"})
routes.add('blog-post', '/blog/:slug', 'index', {component: "BlogPost"})

// pages/index.js
switch (props.url.query.component) {
  case 'BlogList':
    // render BlogList
  case 'BlogPost':
    // render BlogPost
}

So is there anyway I can specify explicit query params like {component: "BlogList"} in the example above, or would you suggest a better way for approaching this problem? Thanks.

Hi @AmrN you can do something like this:
// pages/index.js
import React from 'react'
import routes from '../routes'

const components = {
  blog: props =>
Blog
,
  blogPost: props =>
Blog Post

}

export default class extends React.Component {
  static async getInitialProps ({asPath}) {
    return routes.match(asPath)
  }

  render () {
    const {route, params, ...props} = this.props

    if (route) {
      const Component = components[route.name]
      Object.assign(props.url.query, params)
      return <Component {...props} />
    }

    return
Not found

  }
}

The downsides with this method are no automatic code splitting and you need some custom error handling.


Fix typos in pt-BR README

Type of changes

[ ] Bug fix
[ ] New feature
[x] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[ ] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review. :smile:

Description
Learned today that rich has README files in other languages (from a tweet about polish, I believe) and decided to read the pt-BR version. Spotted a few typos, so prepared this PR. Thanks!

Thanks