/session/:sessionId/element/:id/element does not work?

The problem is the
$session->element('id', 'base_element')->element('xpath', '//div[@class="descr"]')
does not work as expected according to the
http://code.google.com/p/selenium/wiki/JsonWireProtocol#POST_/session/:sessionId/element/:id/element
The expected result is 'test is passed' instead of 'test is failed'
Code to reproduce
index.php
session('firefox');
        $session->open('http://xc53.crtdev.local/~aim/t.html');

        $txt = $session->element('id', 'base_element')->element('xpath', '//div[@class="descr"]')->text();
        print_r($txt);die;
?>
t.html for test1
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<title>Home :: Profile details :: Warning</title>

test is failed

test is passed

t.html for test2
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<title>Home :: Profile details :: Warning</title>

test is failed

test is passed

Output of the script is
[19:22][aim@rt:p4][~/www/selenium_tests]$ php index.php
test is failed
[19:22][aim@rt:p4][~/www/selenium_tests]$

The same issue with new
selenium-server-standalone-2.15.0.jar server

I think we should chalk this up as a protocol limitation.

this sounds like a legit problem, but you should raise it with the webdriver folks at http://code.google.com/p/selenium/ , i don't believe it's an issue with the client if i understand correctly.

ok
Thank you.

WA
https://github.com/facebook/php-webdriver/wiki/Workaround-for-element(..parent..)_element(..child..)_text()-problem

for this to be a client problem the actual REST request being sent on your 2nd element() would have to be malformed differently than the protocol defines.  can you paste in the REST request as the server prints it in the logs, if it's incorrect?

By definition, an xpath that starts with a '/' is an absolute path relative to the root node, not the context node.  What you want to use is:
$txt = $session->element('id', 'base_element')->element('xpath', 'div[@class="descr"]')->text();

Thank you, robocoder, jubishop.
You are right. It seems there was a problem with my code.
I have added a new wiki page
https://github.com/facebook/php-webdriver/wiki/Working-with-element-hierarchy


Fix issue with CodeCarbon lock

From CodeCarbon v2.7, a lock file is introduced (see here) to check whether another instance of codecarbon is running. If yes, an error is raised. One has to call my_energy_tracker.stop() to release the lock file.
This PR adds a stop method in the EnergyTracker class that should be called once the energy tracker is not needed anymore.
It also updates an import from huggingface_hub since v0.25 introduced a change (the new import is backward-compatible).
Fixes https://github.com/huggingface/optimum-benchmark/issues/260.

the failing tests are from the ongoing changes in #263

Acquiring the lock and releasing it between processes will probably not work (or cause issues) in multi-gpu/process setting (torchrun). I can see one process waiting for the other to release the lock to start measuring and causing async issues. We actually don't tests that (codecarbon+multi-gpu). I think a better thing to do here is to set allow_multiple_runs to True.
https://github.com/mlco2/codecarbon/blob/v2.7.0/codecarbon/emissions_tracker.py#L239-L255

Acquiring the lock and releasing it between processes will probably not work (or cause issues) in multi-gpu/process setting (torchrun). I can see one process waiting for the other to release the lock to start measuring and causing async issues. We actually don't test that (codecarbon+multi-gpu). I think a better thing to do here is to set allow_multiple_runs to True. https://github.com/mlco2/codecarbon/blob/v2.7.0/codecarbon/emissions_tracker.py#L239-L255

True for multi-process this is needed. I wouldn't set allow_multiple_runs to True for single-process benchmark though, we don't really know how several trackers can interfere with each other.

the failing tests are from the ongoing changes in #263

Let's wait for #263 to be merged then

we don't really know how several trackers can interfere with each other
Tbh it would be much better if we have one tracker in distributed settings


Autorest Regen Preview to 3.0.0-alpha.20230508.1 by Michael Nash from refs/pull/3328/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3328

API change check
API changes are not detected in this pull request.


readme says 0.2.0 not 0.3.0

hey @alexec, thank you for alerting me. I pushed a fix to the master

hey @alexec, thank you for alerting me. I pushed a fix to the master


Flow showing "incompatibe type" error on Promise-related functions

This is a very heavy simplification of my code
/* @flow */
function runA<X>(fn: () => (X | Promise<X>)): Promise<X>{
    return runB(fn);
}

function runB<X>(fn: () => (X | Promise<X>)): Promise<X>{
    return Promise.resolve().then(() => fn());
}

This shows the following (not very helpful) error:

Promise
This type is incompatible with some incompatible instantiation of X.

Rewriting to async doesn't help.
async function runA<X>(fn: () => (X | Promise<X>)): Promise<X> { // error on this line
    return runB(fn);
}

async function runB<X>(fn: () => (X | Promise<X>)): Promise<X>{
    return fn();
}

Reverting to older Flow fixes the error, so it's a regression.
Our library works a lot with Promises, so this is definitely annoying.

Oh. For some reason, switching the order in the function signature helps. Flow doesn't throw error here.
function runA<X>(fn: () => (Promise<X> | X)): Promise<X> {
    return runB(fn);
}

function runB<X>(fn: () => (Promise<X> | X)): Promise<X> {
    return Promise.resolve().then(() => fn());
}

I thought that A | B and B | A is equivalent.

@runn1ng In general, no, A | B is not equivalent to B | A when A and B may overlap (on the other hand, if they are "disjoint"...i.e., no type can be both A as well as B, then order shouldn't matter).
Basically we want ordering precisely to resolve cases of overlap. In your example, X is more general that Promise<X>, so having it appear before makes the second case never fire. I'm guessing what's happening is that you pass in a Promise<T>, it gets unified with the X case, so the return type becomes something like Promise<Promise<T>>...which is precisely what putting Promise<X> first in the order is designed to prevent. See the core Promise lib that consistently follows this ordering: https://github.com/facebook/flow/blob/master/lib/core.js#L500

....I was never listening enough during my Prolog classes, so I am bad at unification logic :)
I still don't get what is happening there.
So not sure if it's a bug, or not.

@runn1ng Sorry, I should have explained more clearly. Let me try again.
No, this is not a bug...union cases are supposed to tried in order, with the understanding that the first case wins. So the union type X | Promise<X> is essentially the same as X, because whatever you throw at the union, the chances of it matching the first case X is always greater than it matching the second case Promise<X>, so the second case is never reached.
So suppose you define a function whose input is () => (X | Promise<X>) and output type is Promise<X>. Let's consider some calls to that function.
Example (1): You pass something of type () => string. Then string matches X. Once that happens, the return type expands to Promise<string>.
Example (2): You pass something of type () => Promise<number>. Then Promise<number> also matches X (the second case is never reached)! Once that happens, the return type expands to Promise<Promise<number>>.
Something like example (2) is happening the code above. Changing the order of cases in the union fixes the problem, because Promise<number> matches Promise<X>, so X becomes number, and the return type correctly expands to Promise<number>.

Thanks! That makes sense.

From my understanding of TS, it chooses the more-specific case first. Am I wrong on this? If Flow is aiming to hit better TS compatibility some day, it would be nice (and less surprising) to hit this behavior.
TS example

(I'm surprised - positively - that you keep closing 5 year old issues. Thanks!)


In *.ini files, changed "software_version" to mdc2020.

This allows to locate files in POMS monitoring stage

Hi @oksuzian,
You have proposed changes to files in these packages:

CampaignConfig

which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for ea7b95d8671031d7fbcb793cf249838d169f6971: build  (Build queue has 1 jobs)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at ea7b95d8671031d7fbcb793cf249838d169f6971.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged ea7b95d8671031d7fbcb793cf249838d169f6971 at 2444e0c62042e275a61c394fe75e227f5550d927

build (prof)
:white_check_mark:
Log file. Build time: 11 min 19 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at ea7b95d8671031d7fbcb793cf249838d169f6971 after being merged into the base branch at 2444e0c62042e275a61c394fe75e227f5550d927.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.


When the API hasn't had a request in awhile, the first request "hangs" subsequent requests succeed

For reasons unknown, whenever the API hasn't received a request in awhile, the first request it receives "hangs". Cancelling the request, followed by resubmitting the request will work.

issue appears to have been due to ipfs config issues


Deserializing boxed trait without knowing what type it is

Hi, I have an application with a map of trait objects and was wondering how you'd use this crate to deserialize them.  Here is a simplified problem.
#[macro_use]
extern crate serde_derive;
#[macro_use]
extern crate erased_serde;
extern crate serde;
extern crate serde_json;
use std::fmt::Debug;

#[derive(Serialize, Deserialize, Debug)]
struct A;
impl Foo for A{}

#[derive(Serialize, Deserialize, Debug)]
struct B;
impl Foo for B{}

trait Foo: erased_serde::Serialize + Debug {}
serialize_trait_object!(Foo);

fn main() {

    let v: Vec<Box<dyn Foo>> = vec![Box::new(A), Box::new(B), Box::new(A)];
    let s = serde_json::to_string(&v).unwrap();

    let deser = &mut serde_json::de::Deserializer::from_str(&s);
    let mut json = erased_serde::Deserializer::erase(deser);
    let w: Vec<Box<dyn Foo>> =  erased_serde::deserialize(&mut json).unwrap();

    println!("v: {:?}", v);
    println!("w: {:?}", w);

}

If I replace w: Vec<Box<dyn Foo>> with w: Vec<Box<A>> it compiles and runs but is obviously wrong.  Trying to add serde::Deserialize to Foo leads to lifetimes hell and the inability to use trait objects because
error[E0038]: the trait

Foo cannot be made into an object
--> src/main.rs:20:1
|
20 | serialize_trait_object!(<'d>Foo<'d>);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait Foo cannot be made into an object
|
= note: the trait cannot require that Self : Sized
= note: this error originates in a macro outside of the current crate (in Nightly builds, run with > -Z external-macro-backtrace for more info)

How would you recommend I implement saving for a container of (among other things) boxed traits?

You would need to provide an implementation of Deserialize for your trait object:
use serde::{Deserialize, Deserializer};

trait Foo: erased_serde::Serialize + Debug {}
serialize_trait_object!(Foo);

impl<'de> Deserialize<'de> for Box<dyn Foo> {
    fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>
    where
        D: Deserializer<'de>,
    {
        /* your implementation here */
    }
}

The Deserialize impl can use whatever means makes sense to determine which concrete Foo implementation(s) to produce.

The serialized json string is [null,null,null] so the type information is already lost. Do you know how to get the type name into the serialized version? Will that require manually impl serialize?

@dtolnay I also would like to deserialize with an erased type. In my case, I already have an object in memory of the correct type, behind a trait object, and I would like to invoke deserialize_in_place on it, using some type erasure magic to make it work through the trait object. Is that possible? Any hint on how to implement it?

I think @CasperN's use case is addressed by https://github.com/dtolnay/typetag and @rasky's by https://github.com/dtolnay/erased-serde/issues/33.


Recipe changes not autobaked for multiple inputs

Describe the bug
Only the input in focus is autobaked on recipe change
To Reproduce
Add 2nd input tab by pressing '+' on the Input menu bar
Add a generate operation from 'Other' category
Expected behaviour
All output tabs contain generated data
Screenshots
N/A
Desktop (if relevant, please complete the following information):

OS: MacOS Monterey 12.3.1
Browser: Safari 15.4
CyberChef version: 9.37.3

Additional context

This is intended behaviour. Clicking 'Bake' will bake all the inputs. Auto-bake will only bake the active input.
The reasoning for this is that CyberChef can support hundreds of thousands of inputs. Baking all of those at once every time you type a single character in the input might not be desirable! In theory we could add some logic to check how many inputs there are and auto-bake if it's a low number, but I would rather we act consistently.


Fix message for Cardinality rule type

If Cardinality rule is used with min_cardinality, an exception is raised because the alert message only refers to max_cardinality.
With this check at get_match_str function from CardinalityRule class, message is customised depending on the term used

:+1:


Import/ Export forms

I like to be able to export a form that I have created and share the exported form with others. They then have the ability to import the form
BTW: Thank you for this great plugin!

The good news is that you can already export it. What is missing is the import part. What is your desired workflow? You want a button to import a form that opens a modal, or navigates to a different section? I'm also curious about who are you sharing it with, if you can tell me.

BTW: Thank you for this great plugin!

Thank you for the nice words.

The good news is that you can already export it. What is missing is the import part. What is your desired workflow? You want a button to import a form that opens a modal, or navigates to a different section? I'm also curious about who are you sharing it with, if you can tell me.

BTW: Thank you for this great plugin!

Thank you for the nice words.

hi! yes, a simple Import button would be sufficient.
in the first place I would be sharing it with myself, for use on my phone, next to my laptop.
thanks again for a useful plugin!


Load env variables from custom kernelspecs

Fixes #9171

Codecov Report

Merging #9172 (12f75fe) into main (7991354) will decrease coverage by 1%.
The diff coverage is 100%.

@@          Coverage Diff           @@
##            main   #9172    +/-   ##
======================================
- Coverage     71%     70%    -2%
======================================
  Files        382     382
  Lines      24845   24853     +8
  Branches    4031    4035     +4
======================================
- Hits       17751   17459   -292
- Misses      5481    5768   +287
- Partials    1613    1626    +13

Impacted Files
Coverage Δ

...atascience/jupyter/kernels/jupyterKernelService.ts
79% <100%> (+<1%)
:arrow_up:

.../client/datascience/errors/sessionDisposedError.ts
60% <0%> (-40%)
:arrow_down:

.../client/datascience/notebook/liveKernelSwitcher.ts
58% <0%> (-35%)
:arrow_down:

.../datascience/notebook/notebookControllerManager.ts
58% <0%> (-22%)
:arrow_down:

src/client/datascience/jupyter/jupyterUtils.ts
47% <0%> (-18%)
:arrow_down:

...ient/datascience/jupyter/kernels/kernelSelector.ts
56% <0%> (-18%)
:arrow_down:

...lient/datascience/jupyter/jupyterSessionManager.ts
45% <0%> (-17%)
:arrow_down:

src/client/common/configuration/service.ts
67% <0%> (-15%)
:arrow_down:

...datascience/interactive-common/notebookProvider.ts
57% <0%> (-15%)
:arrow_down:

src/client/common/application/encryptedStorage.ts
29% <0%> (-15%)
:arrow_down:

... and 31 more


Remove duplicate cherrypy logs in the central services

Fixes #8111 and #8644
The actual change to stop the duplicate log records was just with the log.screen=False line, which disables writing log records to stdout. This way we keep only the cherrypy access and error logs (with a format that ain't great, but I couldn't fix it yet). Notice that everything that is not an HTTP request (access) is logged with the error log manager, see documentation in:
https://tools.ietf.org/doc/python-cherrypy3/api/cherrypy._cplogging-module.html
Second change was to make ReqMgr2 slightly more verbose, recording original user parameters, priority and status transitions.
Seangchan, as we discussed, logging for priority change of requests not assigned yet are ugly, since the web UI posts to ReqMgr server the whole dictionary built for the client's browser.

Another issue that I don't think we can fix are those print statements before the logging is setup, given that we disable the screen log, I don't see them in my tests. :(

@ticoann I still want to do some pylint cleanup, but please review. And if you're concerned about the logging format or something else, we can discuss tomorrow. I think we can wait until Monday for the next testbed

@ticoann I just pushed another commit moving the log.screen thing down to the moment we run the server. That way we can get all the initial setup logging out (including a dump of the service config) and still get rid of duplicate logs.
If you think it makes more sense, I can squash those commits.

Thanks Alan, patch looks good to me.


SharePoint List selector Expansion

Description
Initial changes to support SharePoint Lists being chosen for Backup Operations.

Type of change

[x] :sunflower: Feature

Issue(s)

close #1785

Test Plan

[x] :zap: Unit test

Commit 51cbeaf changes error output.
Related Issue:

#1664

@ryanfkeepers not sure why this would be failing by adding selectors. Any insight would be helpful.
estBackupOpIntegrationSuite/TestBackup_Run_sharePoint (3.67s)
      integration_runners.go:68: TestBackupOpIntegrationSuite/TestBackup_Run_sharePoint run at 2022-12-13T18:56:40.407429755Z
  2022-12-13T18:56:41.988Z	DEBUG	sharepoint/data_collections.go:102	Creating SharePoint Library collections	{"site": partA, partB"}
      backup_test.go:512:
          	Error Trace:	/home/runner/work/corso/corso/src/internal/operations/backup_test.go:512
          	Error:      	Received unexpected error:
          	            	2 errors occurred:
          	            		* errors prevented the operation from processing
          	            		* retrieving data to backup: sharePoint list collections not supported

          	Test:       	TestBackupOpIntegrationSuite/TestBackup_Run_sharePoint

@dadams39 see https://github.com/alcionai/corso/blob/main/src/internal/connector/sharepoint/data_collections.go#L64

@dadams39 see https://github.com/alcionai/corso/blob/main/src/internal/connector/sharepoint/data_collections.go#L64
Test was temporarily adjusted to exclude SharePoint.List after the selectors were updated. Issue #1795 marks the test to be adjusted after SharePoint.List.Collections are enabled.

TestSharePointSelectorSuite/TestSharePointSelector_Include_Sites (0s)
sharepoint_test.go:212:
Error Trace:	/home/runner/work/corso/corso/src/pkg/selectors/sharepoint_test.go:21

Commit to fix the configuration failure below:
TestSharePointSelectorSuite/TestSharePointSelector_Include_Sites (0s)
      sharepoint_test.go:212:
          	Error Trace:	/home/runner/work/corso/corso/src/pkg/selectors/sharepoint_test.go:21

@ryanfkeepers could you specifically at this test?
Prefer to have a second set of eyes look at this prior to committing.

@ryanfkeepers could you specifically at this test? Prefer to have a second set of eyes look at this prior to committing.

That looks good for now.


Clarification Needed

Hi @bkuschel,
I think a clarification is needed that this repo is related to "Qlik Sense Enterprise on Kubernetes".

Thx @stefanwalther. I have updated the README.MD to indicate as such.


chore: add csi-node nvme-connect-fallback to helm values

Description
Add nvme-connect-fallback option to helm for allowing users to let initiator node connect over tcp in case the node is not rdma capable, even though volume target exposes rdma transport.
Motivation and Context

Regression

How Has This Been Tested?
By templating the helm values.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added unit tests to cover my changes.

bors merge


expansion of available settings?

since this is a decompilation project, i will take a wild guess that it's now possible to modify it, isn't it possible to expand available settings? (bigger polyphony, bit depth, bigger sample rate, etc.)

In theory yes, but what would be the point ?
And who would do it, because I don't have any interest in doing it ?

Now that's a good question, mostly to get better output quality, and i think that i even know someone who might do that, no guarantees tho


Adding shutdown service option

If you are interested I added the shutdown feature inside the service command.
Some people asked me about that one.
I have to add some tests, and improve the code but let me know if it makes sense to have this feature ?
Thanks

I was thinking to execute the shutdown command as a background process, and notify to use the jobs command to check the progress.
If you have 10 nodes for examples, it could be long to shutdown all of them and wait the CLI to finish the operation.
What do you think about that ?

With respect to running in a background process. I'm not sure what this would look like from a user experience, perhaps open a separate issue for this. I've always worked on the assumption that if the user wants it to be backgrounded they will do so at the command line (add &). If you think there should be alternatives I'm all for considering them, but lets not block this useful contribution on an additional feature.

@rgardler I did the changes. Let me know if it make senses now ?
Thanks for the review :)

This is great, thank you. On reflection this command should be "deallocate" rather than "shutdown". I'll merge this when I have the time to make this final change. If you want to update the PR that would be great but not necessary for me to eventually merge this.
Once merged (or before) we'll need a restart command too. Again I'll welcome a PR for this, but not necessary for me to merge this command.

You right, I thought to rename it to deallocate, it makes more senses.
I will work on the restart command on an other PR.
Thanks

Done I changed the name.

Now that I am testing this code I understand your comment about deallocation in separate threads. I didn't realize just how long it takes to iterate over each individual VM and deallocate them. I do think it makes sense to do the individual deallocates calls in parallel, but the CLI command should not return until all have completed. Again, I'm not going to block merging this on such an enhancement. Once my tests are complete I'll merge.

My tests are not working. It seems that once the VMs are started after a shutdown they do not converge again. This is likely because for a deallocate we lose data on the ephemeral disk.
I've merged your changes and add a start command as well as a basic test into the branch julienstroheker-feature-shutdown, you can see my changes at https://github.com/rgardler/acs-cli/compare/julienstroheker-feature-shutdown?expand=1
Any help in debugging the cause of the failed restart would be appreciated. In the meantime I'm going to close this PR so that we can move work into the shared feature branch.

Sound good I will check on my side.


PolicyReport output not working

I set key --set policyreport.enabled=true and its now working

How to reproduce it

Expected behaviour

Screenshots

Environment

Falco version:

System info:

Cloud provider or hardware configuration:
OS:

Kernel:

Installation method:

Additional context

Hi,
I suppose you're installing Falcosidekick with Helm, but as long the release with this feature (2.25.0) will not be changed for managing this output.

ok. I wait this

I'm closing this issue. If you need more, please open a new one in https://github.com/falcosecurity/charts


PR4: Search is not returning any result. No response

After selecting a valid date. Clicking on search is not showing any results.

Hi,
Can you please try again and please select locations which are in different cities for better results.
If that doesn't work, please let us know the search criteria which might be a bug.
Thanks,
Alakh

works fine


Reference Error: _ is not defined (StackTrace)

I added some code with a recent commit, and Globalize Compiler will no longer complete a production build.
Unfortunately, the error seems a bit cryptic for me to decipher. I tried searching this repo and it's predecessor (rxaviers/globalize-webpack-plugin) for ReferenceError or another sign of this problem, but it looks like that message may be coming from a dependency, or I was simpy unable to turn up results as I expected.
The error I'm getting tells me _ isn't defined, but doesn't go into detail about where this error actually originates from in the code.  I'm a bit stumped, and I've started removing the code from the commit (rolling back to the previous commit fixes it), but I've not had much success with this method, either.
Here's the error:
Populated the new fields of `messages/zh-Hant.json` using the default translation.
ReferenceError: _ is not defined
    at eval (eval at extractor (~/Sites/esports-ui/node_modules/react-globalize-compiler/lib/extract.js:65:10), <anonymous>:3:35)
    at ~/Sites/esports-ui/node_modules/globalize-compiler/lib/compile-extracts.js:59:23
    at Array.reduce (native)
    at Object.compileExtracts (~/Sites/esports-ui/node_modules/globalize-compiler/lib/compile-extracts.js:58:49)
    at GlobalizeCompilerHelper.compile (~/Sites/esports-ui/node_modules/globalize-webpack-plugin/GlobalizeCompilerHelper.js:63:33)
    at ~/Sites/esports-ui/node_modules/globalize-webpack-plugin/ProductionModePlugin.js:236:51
    at RegExp.[Symbol.replace] (native)
    at RegExp.[Symbol.replace] (native)
    at String.replace (native)
    at ~/Sites/esports-ui/node_modules/globalize-webpack-plugin/ProductionModePlugin.js:230:58
    at Array.forEach (native)
    at ~/Sites/esports-ui/node_modules/globalize-webpack-plugin/ProductionModePlugin.js:227:63
    at Array.forEach (native)
    at Compilation.<anonymous> (~/Sites/esports-ui/node_modules/globalize-webpack-plugin/ProductionModePlugin.js:225:10)
    at Compilation.applyPlugins (~/Sites/esports-ui/node_modules/tapable/lib/Tapable.js:26:37)
    at Compilation.<anonymous> (~/Sites/esports-ui/node_modules/webpack/lib/Compilation.js:558:8)
    at Compilation.next (~/Sites/esports-ui/node_modules/tapable/lib/Tapable.js:67:11)
    at ExtractTextPlugin.<anonymous> (~/Sites/esports-ui/node_modules/extract-text-webpack-plugin/index.js:285:5)
    at ~/Sites/esports-ui/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:52:16
    at Object.async.forEachOf.async.eachOf (~/Sites/esports-ui/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:236:30)
    at Object.async.forEach.async.each (~/Sites/esports-ui/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:209:22)
    at ExtractTextPlugin.<anonymous> (~/Sites/esports-ui/node_modules/extract-text-webpack-plugin/index.js:237:10)
    at Compilation.applyPluginsAsync (~/Sites/esports-ui/node_modules/tapable/lib/Tapable.js:71:13)
    at Compilation.seal (~/Sites/esports-ui/node_modules/webpack/lib/Compilation.js:525:7)
    at Compiler.<anonymous> (~/Sites/esports-ui/node_modules/webpack/lib/Compiler.js:397:15)
    at ~/Sites/esports-ui/node_modules/tapable/lib/Tapable.js:103:11
    at Compilation.<anonymous> (~/Sites/esports-ui/node_modules/webpack/lib/Compilation.js:445:10)
    at ~/Sites/esports-ui/node_modules/webpack/lib/Compilation.js:417:12
    at ~/Sites/esports-ui/node_modules/webpack/lib/Compilation.js:332:10
    at ~/Sites/esports-ui/node_modules/webpack/node_modules/async/lib/async.js:52:16

Any insight is much appreciated!

Looks like I had a typo in my search, at least on this repo. I found #17, which was filed by my coworker, but doesn't address this specific problem, unless I accidentally wrapped something dynamic in <FormatMessage>.  I'll post back if my removing sections of the code troubleshooting bears fruit.

Ok, I found it.  We had some code my aforementioned coworker had written that took options, and I tried to extract that to a Global Constant for use elsewhere in the codebase (I was trying to directly utilize Globalize to format a number that's being passed to another, 3rd party react component over which I do not have control).
So in the course of refactoring, I tried to change the input to <FormatNumber>, and he had even left a comment about how this cannot be dynamic, which I overlooked when I made this change 🤕
         <FormatNumber options={NUMBER_FORMAT_OPTIONS}>
             {number}
         </FormatNumber>

I see you made progress on your search. Please, do you still need any input? Did you find a bug? Thanks

I'm not sure where the stack trace originates from, but this error seems to be related to trying to use an object reference for <FormatNumber> versus a "hard coded" object in the props.  If I understand correctly, this may be related to globalize-webpack-plugin using eval to read the value of the options prop.
I have solved the problem in our code base by replacing the reference with an object literal containing the option values, so we can close this, but I would have two questions:

How is the stack trace being handled in this case? The error gave me no indication of what I had done wrong, and because I stopped one task and switched to another, I lost the context of what happened and had to troubleshoot by removing chunks of code until I found the culprit.
If my hypothesis (derived in part from #17 ) is right then we cannot pass references to props in react-globalize.  Is this the case? Will it always be the case? It makes it a little harder to work with.  For instance, I'm working on a bread crumb feature now, and I cannot simply take the displayName of the component and drop that into <FormatMessage>, either, because the body gets evaled, right?


Implementation of async package validation

Estimate is boxed to this sprint.

We have broken this implementation item up.


Bulk Fav

The fav function now accepts an "all" parameter for affecting many cards at once.
Added new shorthand commands:
->favs (->cards -fav)
->unfav (->fav remove)
Updated help text for favorites & fixed a reported typo.

Is it possible to run this command through confirmation process? Like in sell when people have to confirm it. There is a system in a bot written for that

Is it possible to run this command through confirmation process? Like in sell when people have to confirm it. There is a system in a bot written for that

I'll take a look probably later today.

Is it possible to run this command through confirmation process? Like in sell when people have to confirm it. There is a system in a bot written for that

The requested functionality has been added.


Remove split sentences in translations

Describe the bug …
There are several split sentences, which usually make translating the strings difficult
https://github.com/konstantintutsch/Lock/blob/main/src/cryptography.c#L16
More information: https://wiki.gnome.org/TranslationProject(2f)DevGuidelines(2f)Never(20)split(20)sentences.html
Relevant log output
#define HANDLE_ERROR(Return, Error, String, Context, FreeCode) if (Error) \
    { \
        g_warning(C_("Error message constructor for failed GPGME operations", "Failed to %s: %s"), String, gpgme_strerror(Error)); \
        \
        FreeCode \
        \
        gpgme_release(Context); \
        \
        return Return; \
    }

The new strings should now also be available in the Turkish translation.
Just checked and Weblate did not apply the changes from fe9101e91d6e32dd41569253dc95e1aaeb2b92dc to the Turkish translation for some reason. It's fixed.


Structure of isA in TypeConstraint

Currently, the isA property of a TypeConstraint has _name and _namespace properties, as shown below:
{
    "min": 0,
    "max": 1,
    "constraints": [
    {
        "type": "TypeConstraint",
        "isA": {
            "_namespace": "shr.lab",
            "_name": "TestMethod"
        },
        "onValue": false,
        "path": ""
    }
    ],
    "type": "IdentifiableValue",
    "label": "shr.observation:Method",
    "identifier": {
        "label": "Method",
        "type": "Identifier",
        "namespace": "shr.observation"
    }
}

These are intended to be private properties (hence the _ prefix).  Since isA is an Identifier in the models, I think this should be represented in the JSON the same way identifiers are represented elsewhere.  So, the example above probably should be:
{
    "min": 0,
    "max": 1,
    "constraints": [
    {
        "type": "TypeConstraint",
        "isA": {
            "type": "Identifier",
            "label": "TestMethod",
            "namespace": "shr.lab"
        },
        "onValue": false,
        "path": ""
    }
    ],
    "type": "IdentifiableValue",
    "label": "shr.observation:Method",
    "identifier": {
        "label": "Method",
        "type": "Identifier",
        "namespace": "shr.observation"
    }
}

@gregquinn2001, @Dtphelan1 : Any objections?

This makes sense to me!  I'm on board the with suggested change.

sounds good to me too. Should be simple to update SSVE as well.

I'll go ahead an update the SSVE then.

Latest PR adds support for the isA value change:
https://github.com/standardhealth/spec_json2html/pull/9

This is still an open issue in spec_json2html, but for the purposes of this project (shr-json-export), it is fixed.


Sparse matrix crash

Hello!
I'm using this code:
import scipy.sparse as sparse
import nmslib

test_features = sparse.csr_matrix(test_features) # test_features 5000 x 322
train_features = sparse.csr_matrix(train_features) # train_features 45000 x 322

hnsw = nmslib.init(method = 'hnsw', space = 'cosinesimil_sparse', data_type=nmslib.DataType.SPARSE_VECTOR)
hnsw.addDataPointBatch(train_features)
hnsw.createIndex()

hnsw.knnQuery(test_features, k=10)

Using this, I get this error:
IndexError: tuple index out of range

How can I fix it? If I use simply cosinesimil without creating sparse matrix, my jupyter notebook kernel dies. Once I got an error
Check failed: obj1->datalength() == obj2->datalength()
...
RuntimeError: Check failed: it's either a bug or inconsistent data!

A bit related to #479

Hi @adtsvetkov is it the latest version? Can you also share the data?

PS: I also double-checked how the data is created in our notebook. Make sure you do exactly the same thing. In any case, it's not possible to tell what's wrong without a reproducible example that has some data + complete code.

Hi @adtsvetkov is it the latest version? Can you also share the data?

It's the latest version, upgraded with conda.
@searchivarius
Of course, here is the code and data :
import pandas as pd
import numpy as np
import scipy.sparse as sparse
import nmslib

df = pd.read_csv("bigdata2.csv")
# female = 2
# male = 1
df.loc[df.Sex == "female", 'Sex'] = 2
df.loc[df.Sex == "male", 'Sex'] = 1

df.loc[df.Label == True, 'Label'] = 1
df.loc[df.Label == False, 'Label'] = 0

arr = np.array(df).astype(np.float32)
arr = arr.copy(order='C')

np.random.shuffle(arr)
train_size = int(0.9 * arr.shape[0])
train_features = arr[:train_size, :-1].astype('float32')
train_labels = arr[:train_size, -1].astype('float32')
test_features = arr[train_size:, :-1].astype('float32')
test_labels = arr[train_size:, -1].astype('float32')

test_features = sparse.csr_matrix(test_features)
train_features = sparse.csr_matrix(train_features)

nsw = nmslib.init(method = 'sw-graph', space = 'cosinesimil_sparse', data_type=nmslib.DataType.SPARSE_VECTOR)
nsw.addDataPointBatch(train_features)
nsw.createIndex()

nsw.knnQuery(test_features, k=10)

Hi @adtsvetkov  thank you for sharing. First, there's indeed some bug with knnQuery, I need to address it someday, but could you try use knnQueryBatch instead? I actually don't get things crashed but I get an error:
Unable to cast Python instance to C++ type (compile in debug mode for details)

This is actually not surprising, b/c knnQuery cannot deal with batches. Querying a single row is also problematic. So, there's clearly an issue to be addressed. But to get something working you better switch to batch querying.
Also, please, note that I do not maintain the conda version of NMSLIB, only the version that is installed by pip.

Hey @searchivarius, I just hit the same IndexError: tuple index out of range exception both with knnQuery and with the recommended workaround knnQueryBatch.
Do you have an idea how we can investigate this further?

@PLNech is there a reproducible example?

@searchivarius I'm afraid not, I didn't think about versioning that code... Will make sure to save it next time I hit any issue :sweat_smile:
Anyway, I think it's solved as once I followed your advice in #514 I now have a functional indexing and search.
Thanks for the fast support! Have a nice day & WE :hugs:


Move saving checkpoints from model to trainer

Closes #214, #89, #203. It involves a refactor where the trainer now saves checkpoints instead of the model.
This solves #203, which asks for saving optimizer and scheduler states for much improved restarting of training. The slightly changed interface allows PET checkpoints to work both for restarting and exporting (#214). Finally, we document what a checkpoint (e.g. model.ckpt) should be (#89).
Contributor (creator of pull-request) checklist

[ ] Tests updated (for new features and bugfixes)?
[x] Documentation updated (for new features)?
[x] Issue referenced (for PRs that solve an issue)?

📚 Documentation preview 📚: https://metatrain--262.org.readthedocs.build/en/262/

Does this work with the design to support lightning?

Yes, by inheriting from the lightning classes and making the necessary adaptations (as we were planning to do before)

So the idea is that we need to save checkpoint in the trainer to be able to also save the optimizer state, but we want to load checkpoints from the model for export/restart?

@Luthaf yes, that's the idea. The same checkpoint can be read by the trainer (reads everything, for restarting training) or the model (just loads the model, for exporting)


Use del instead of rimraf

Simplify deleting target and build

Nice, I've never seen del before.

SOLD!


DBFS root Blob storage IP address

If finding IP address method is something critical to run ADB in private vNET this section should be called out or highlighted clearly. I'm working with a large insurance company and we have been struggling with this for 2 days. We followed the article and created all UDR rules described except this part finding the DBFS IP address and adding it to UDR as it wasn't clear... After opening a support ticket with Microsoft we got this section clarified and hence solved the problem.
Hope others will not struggle with this just because it might not be clear to all people using ADB in private vNET.
Thanks.

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

ID: a44cbeaf-af2c-ef7e-b411-24556279d898
Version Independent ID: aaced3ee-7d7c-a9d6-a81b-b132674fa055
Content: User-defined route settings for Azure Databricks - Azure Databricks
Content Source: databricks/administration-guide/cloud-configurations/azure/udr.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

Thank you for the feedback. We have assigned the issue to the content author. They will evaluate and update the document as appropriate.

Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7025) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close

#please-close


Milestone/v6.25.0

Closes #343

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


grpc: per-silo shared completion queues for Google gRPC client library.

Previously, we had one thread per stream, which is terrible for
performance but simple. In this patch, a per-TLS thread completion
thread is setup by the AsyncClientManager and shared amongst all clients
(and streams). There is now somewhat complex cross-thread shared state
(including some narrow locked sections) to deal with stream shutdown
during inflight operations.
Risk Level: Low (only Google gRPC client impacted, not in prod use).
Testing: existing tests, with --runs_per_test=1000 for {grpc_client_integration_test,ads_integration_test,metrics_service_integration_Test}. Also added some new unit tests for Google gRPC client call creation in google_async_client_impl_test and client destruction in grpc_client_integration_test.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

@mattklein123 this is WiP, I need to sort out some teardown issues first (will consult @vjpai). Meanwhile, can you take a look at the locking that's now happening between handleOpCompletion() on the silo threads and completionThread and LMK how sad it makes you.
I would ideally like to have this lock-free, and we can probably do that with atomics (and probably memory barriers), but wanted to start with something that would allow us to reason about correctness easily.

@vjpai I've incorporated your feedback, PTAL for gRPC library sanity if you get a chance. Thanks.

@mattklein123 @vjpai this is now ready for final review.

@mattklein123 @zuercher FWIW, GUARDED_BY is still broken on OS X.

@dnoe can you take a pass on this?

Will take a look.

I think the reason GUARDED_BY didn't fail the TF builds is that they don't have -Werror set. So they got a lot of warnings.
I think if you had
LOCKABLE std::mutex completed_ops_lock_;

then GUARDED_BY should work. You'll also need to tag locks on the mutex with SCOPED_LOCKABLE, e.g.:
SCOPED_LOCKABLE std::unique_lock<LOCKABLE std::mutex> lock(stream.completed_ops_lock_);

These could be simplified with some typedefs. for the mutex and unique_lock.

Another option if we can't get it to work on OSX is to just have a private include for thread_guards.h which defines some things and then makes them nothing for OSX.

@zuercher @mattklein123 thanks for the ideas, let's handle the thread annotation issue separately in https://github.com/envoyproxy/envoy/issues/2571, since I don't want to conflate with this already large PR.

This is ready for another pass, I didn't remove locking of handleOpCompletion, since I wanted to ensure we atomically handle an entire post set of op completions before another one is possible, per the invariant.


fix rename with Postgres with repeatable read

When Postgres is configured to use repeatable read as isolation level, the select  in XX for update query return partial result.
This PR workaround this problem by use two ordered select queries.

Codecov Report

Merging #2109 (3ea6c11) into main (35918c3) will decrease coverage by 0.06%.
The diff coverage is 73.33%.

@@            Coverage Diff             @@
##             main    #2109      +/-   ##
==========================================
- Coverage   61.87%   61.80%   -0.07%
==========================================
  Files         138      138
  Lines       24839    24834       -5
==========================================
- Hits        15368    15349      -19
- Misses       7659     7674      +15
+ Partials     1812     1811       -1

Impacted Files
Coverage Δ

pkg/meta/sql.go
65.51% <73.33%> (-0.26%)
:arrow_down:

cmd/rmr.go
58.73% <0.00%> (-1.93%)
:arrow_down:

pkg/fs/fs.go
75.82% <0.00%> (-1.84%)
:arrow_down:

pkg/chunk/cached_store.go
75.82% <0.00%> (-0.37%)
:arrow_down:

pkg/fuse/fuse.go
78.10% <0.00%> (+0.50%)
:arrow_up:

pkg/vfs/reader.go
80.29% <0.00%> (+0.54%)
:arrow_up:

pkg/chunk/utils_unix.go
93.33% <0.00%> (+20.00%)
:arrow_up:

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 35918c3...3ea6c11. Read the comment docs.


y-axis flickers

Godot version
4.0 beta 1  Vulkan
System information
Windows 10 64bit, i7-7700k, RTX 3080
Issue description
y-axis flickers in standard settings when camera is moved

Steps to reproduce
start and move the camera in the viewport
all 4.0 alphas and beta
Minimal reproduction project
default settings

Already reported. IIRC it only flickers when viewport is odd sized

Duplicate of https://github.com/godotengine/godot/issues/37016


proxy: panic when adding new member

goreman start
add new member
proxy panic in 1min:

23:16:42 proxy | Starting proxy on port 5003
23:16:42 etcd1 | Starting etcd1 on port 5000
23:16:42 etcd2 | Starting etcd2 on port 5001
23:16:42 etcd3 | Starting etcd3 on port 5002
23:16:42 proxy | 2015/02/01 23:16:42 no proxy data-dir provided, using default proxy data-dir ./default.etcdproxy
23:16:42 proxy | 2015/02/01 23:16:42 proxy: using peer urls [http://localhost:7001 http://localhost:7002 http://localhost:7003]
23:16:42 proxy | 2015/02/01 23:16:42 etcdserver: could not get cluster response from http://localhost:7001: Get http://localhost:7001/members: dial tcp <IP_ADDRESS>:7001: connection refused
23:16:42 proxy | 2015/02/01 23:16:42 etcdserver: could not get cluster response from http://localhost:7002: Get http://localhost:7002/members: dial tcp <IP_ADDRESS>:7002: connection refused
23:16:42 proxy | 2015/02/01 23:16:42 etcdserver: could not get cluster response from http://localhost:7003: Get http://localhost:7003/members: dial tcp <IP_ADDRESS>:7003: connection refused
23:16:42 proxy | 2015/02/01 23:16:42 proxy: etcdserver: could not retrieve cluster information from the given urls
23:16:42 proxy | 2015/02/01 23:16:42 proxy: listening for client requests on <IP_ADDRESS>:8080
23:16:42 etcd1 | 2015/02/01 23:16:42 no data-dir provided, using default data-dir ./infra1.etcd
23:16:42 etcd1 | 2015/02/01 23:16:42 etcd: listening for peers on http://localhost:7001
23:16:42 etcd1 | 2015/02/01 23:16:42 etcd: listening for client requests on http://localhost:4001
23:16:42 etcd3 | 2015/02/01 23:16:42 no data-dir provided, using default data-dir ./infra3.etcd
23:16:42 etcd2 | 2015/02/01 23:16:42 no data-dir provided, using default data-dir ./infra2.etcd
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: name = infra1
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: data dir = infra1.etcd
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: heartbeat = 100ms
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: election = 1000ms
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: snapshot count = 10000
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: advertise client URLs = http://localhost:4001
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: initial advertise peer URLs = http://localhost:7001
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: initial cluster = infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003
23:16:42 etcd3 | 2015/02/01 23:16:42 etcd: listening for peers on http://localhost:7003
23:16:42 etcd3 | 2015/02/01 23:16:42 etcd: listening for client requests on http://localhost:4003
23:16:42 etcd2 | 2015/02/01 23:16:42 etcd: listening for peers on http://localhost:7002
23:16:42 etcd2 | 2015/02/01 23:16:42 etcd: listening for client requests on http://localhost:4002
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: start member a8266ecf031671f3 in cluster e9c7614f68f35fb2
23:16:42 etcd1 | 2015/02/01 23:16:42 raft: a8266ecf031671f3 became follower at term 0
23:16:42 etcd1 | 2015/02/01 23:16:42 raft: newRaft a8266ecf031671f3 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
23:16:42 etcd1 | 2015/02/01 23:16:42 raft: a8266ecf031671f3 became follower at term 1
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: name = infra2
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: data dir = infra2.etcd
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: heartbeat = 100ms
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: election = 1000ms
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: snapshot count = 10000
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: advertise client URLs = http://localhost:4002
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: initial advertise peer URLs = http://localhost:7002
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: initial cluster = infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: added member 6e3bd23ae5f1eae0 [http://localhost:7002] to cluster e9c7614f68f35fb2
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: added member 924e2e83e93f2560 [http://localhost:7003] to cluster e9c7614f68f35fb2
23:16:42 etcd1 | 2015/02/01 23:16:42 etcdserver: added local member a8266ecf031671f3 [http://localhost:7001] to cluster e9c7614f68f35fb2
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: name = infra3
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: data dir = infra3.etcd
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: heartbeat = 100ms
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: election = 1000ms
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: snapshot count = 10000
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: advertise client URLs = http://localhost:4003
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: initial advertise peer URLs = http://localhost:7003
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: initial cluster = infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: start member 924e2e83e93f2560 in cluster e9c7614f68f35fb2
23:16:42 etcd3 | 2015/02/01 23:16:42 raft: 924e2e83e93f2560 became follower at term 0
23:16:42 etcd3 | 2015/02/01 23:16:42 raft: newRaft 924e2e83e93f2560 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
23:16:42 etcd3 | 2015/02/01 23:16:42 raft: 924e2e83e93f2560 became follower at term 1
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: start member 6e3bd23ae5f1eae0 in cluster e9c7614f68f35fb2
23:16:42 etcd2 | 2015/02/01 23:16:42 raft: 6e3bd23ae5f1eae0 became follower at term 0
23:16:42 etcd2 | 2015/02/01 23:16:42 raft: newRaft 6e3bd23ae5f1eae0 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
23:16:42 etcd2 | 2015/02/01 23:16:42 raft: 6e3bd23ae5f1eae0 became follower at term 1
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: added local member 6e3bd23ae5f1eae0 [http://localhost:7002] to cluster e9c7614f68f35fb2
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: added member 924e2e83e93f2560 [http://localhost:7003] to cluster e9c7614f68f35fb2
23:16:42 etcd2 | 2015/02/01 23:16:42 etcdserver: added member a8266ecf031671f3 [http://localhost:7001] to cluster e9c7614f68f35fb2
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: added member 6e3bd23ae5f1eae0 [http://localhost:7002] to cluster e9c7614f68f35fb2
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: added local member 924e2e83e93f2560 [http://localhost:7003] to cluster e9c7614f68f35fb2
23:16:42 etcd3 | 2015/02/01 23:16:42 etcdserver: added member a8266ecf031671f3 [http://localhost:7001] to cluster e9c7614f68f35fb2
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 is starting a new election at term 1
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 became candidate at term 2
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 received vote from 924e2e83e93f2560 at term 2
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 [logterm: 1, index: 3] sent vote request to 6e3bd23ae5f1eae0 at term 2
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 [logterm: 1, index: 3] sent vote request to a8266ecf031671f3 at term 2
23:16:43 etcd1 | 2015/02/01 23:16:43 raft: a8266ecf031671f3 [term: 1] received a MsgVote message with higher term from 924e2e83e93f2560 [term: 2]
23:16:43 etcd1 | 2015/02/01 23:16:43 raft: a8266ecf031671f3 became follower at term 2
23:16:43 etcd1 | 2015/02/01 23:16:43 raft: a8266ecf031671f3 [logterm: 1, index: 3, vote: 0] voted for 924e2e83e93f2560 [logterm: 1, index: 3] at term 2
23:16:43 etcd2 | 2015/02/01 23:16:43 raft: 6e3bd23ae5f1eae0 [term: 1] received a MsgVote message with higher term from 924e2e83e93f2560 [term: 2]
23:16:43 etcd2 | 2015/02/01 23:16:43 raft: 6e3bd23ae5f1eae0 became follower at term 2
23:16:43 etcd2 | 2015/02/01 23:16:43 raft: 6e3bd23ae5f1eae0 [logterm: 1, index: 3, vote: 0] voted for 924e2e83e93f2560 [logterm: 1, index: 3] at term 2
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 received vote from a8266ecf031671f3 at term 2
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 [q:2] has received 2 votes and 0 vote rejections
23:16:43 etcd3 | 2015/02/01 23:16:43 raft: 924e2e83e93f2560 became leader at term 2
23:16:43 etcd3 | 2015/02/01 23:16:43 raft.node: 924e2e83e93f2560 elected leader 924e2e83e93f2560 at term 2
23:16:43 etcd2 | 2015/02/01 23:16:43 raft.node: 6e3bd23ae5f1eae0 elected leader 924e2e83e93f2560 at term 2
23:16:43 etcd1 | 2015/02/01 23:16:43 raft.node: a8266ecf031671f3 elected leader 924e2e83e93f2560 at term 2
23:16:43 etcd2 | 2015/02/01 23:16:43 rafthttp: starting client stream to 924e2e83e93f2560 at term 2
23:16:43 etcd1 | 2015/02/01 23:16:43 rafthttp: starting client stream to 924e2e83e93f2560 at term 2
23:16:44 etcd3 | 2015/02/01 23:16:44 etcdserver: published {Name:infra3 ClientURLs:[http://localhost:4003]} to cluster e9c7614f68f35fb2
23:16:44 etcd2 | 2015/02/01 23:16:44 etcdserver: published {Name:infra2 ClientURLs:[http://localhost:4002]} to cluster e9c7614f68f35fb2
23:16:44 etcd1 | 2015/02/01 23:16:44 etcdserver: published {Name:infra1 ClientURLs:[http://localhost:4001]} to cluster e9c7614f68f35fb2
23:16:50 etcd3 | 2015/02/01 23:16:50 etcdserver: added member 4dd8628e0da2f78b [http://<IP_ADDRESS>:7004] to cluster e9c7614f68f35fb2
23:16:50 etcd3 | 2015/02/01 23:16:50 sender: error posting to 4dd8628e0da2f78b: dial tcp <IP_ADDRESS>:7004: connection refused
23:16:50 etcd3 | 2015/02/01 23:16:50 sender: the connection with 4dd8628e0da2f78b becomes inactive
23:16:50 etcd3 | 2015/02/01 23:16:50 sender: failed to send message in 266.365us
23:16:50 etcd3 | 2015/02/01 23:16:50 sender: failed to send message in 786.008us
23:16:50 etcd2 | 2015/02/01 23:16:50 etcdserver: added member 4dd8628e0da2f78b [http://<IP_ADDRESS>:7004] to cluster e9c7614f68f35fb2
23:16:50 etcd1 | 2015/02/01 23:16:50 etcdserver: added member 4dd8628e0da2f78b [http://<IP_ADDRESS>:7004] to cluster e9c7614f68f35fb2
23:17:12 proxy | panic: runtime error: invalid memory address or nil pointer dereference
23:17:12 proxy | [signal 0xb code=
23:17:12 proxy | 0x1 addr=0x0 pc=0xa2b61]
23:17:12 proxy | goroutine 27 [running]:
23:17:12 proxy | runtime.panic(0x3e5260, 0x6772a4)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/runtime/panic.c:279 +0xf5
23:17:12 proxy | github.com/coreos/etcd/etcdserver.(*Cluster).PeerURLs(0x0, 0x0, 0x0, 0x0)
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/etcdserver/cluster.go:178 +0x371
23:17:12 proxy | github.com/coreos/etcd/etcdmain.func·007(0x0, 0x0
23:17:12 proxy | , 0x0)
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/etcdmain/etcd.go:253 +0x81
23:17:12 proxy | github.com/coreos/etcd/proxy.(*director).refresh(0x208737530)
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/proxy/director.go:56 +0x35
23:17:12 proxy | github.com/coreos/etcd/proxy.func·001()
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/proxy/director.go:42 +0x75
23:17:12 proxy | created by github.com/coreos/etcd/proxy.newDirector
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/proxy/director.go:45 +0x9a
23:17:12 proxy | goroutine 16 [chan receive (nil chan)]:
23:17:12 proxy | github.com/coreos/etcd/etcdmain.Main()
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/etcdmain/etcd.go:77 +0x56b
23:17:12 proxy | main.main()
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/main.go:48 +0x1ab
23:17:12 proxy | goroutine 19 [finalizer wait]:
23:17:12 proxy | runtime.park(0x14510,
23:17:12 proxy | 0x67a8d0, 0x679369)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/runtime/proc.c:1369 +0x89
23:17:12 proxy | runtime.parkunlock(0x67a8d0, 0x679369)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/runtime/proc.c:1385 +0x3b
23:17:12 proxy | runfinq()
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/runtime/mgc0.c:2644 +0xcf
23:17:12 proxy | runtime.goexit()
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/runtime/proc.c:1445
23:17:12 proxy | goroutine 28 [IO wait]:
23:17:12 proxy | net.runtime_pollWait(0x2208726d10, 0x72, 0x0)
23:17:12 proxy | 	/private/tmp/go-eKWUV2/go/src/pkg/runtime/netpoll.goc:146 +0x66
23:17:12 proxy | net.(*pollDesc).Wait(0x2087945a0, 0x72, 0x0, 0x0)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/net/fd_poll_runtime.go:84 +0x46
23:17:12 proxy | net.(*pollDesc).WaitRead(0x2087945a0, 0x0, 0x0)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/net/fd_poll_runtime.go:89 +0x42
23:17:12 proxy | net.(*netFD).accept(0x208794540, 0x507ac8, 0x0, 0x22087253c8, 0x23)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/net/fd_unix.go:419 +0x343
23:17:12 proxy | net.(*TCPListener).AcceptTCP(0x20874e0c8, 0x208750ea8, 0x0, 0x0)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/net/tcpsock_posix.go:234 +0x5d
23:17:12 proxy | net.(*TCPListener).Accept(0x20874e0c8, 0x0, 0x0, 0x0, 0x0)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/net/tcpsock_posix.go:244 +0x4b
23:17:12 proxy | net/http.(*Server).Serve(0x208718a20, 0x2208726eb0, 0x20874e0c8, 0x0, 0x0)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/net/http/server.go:1698 +0x91
23:17:12 proxy | net/http.Serve(0x2208726eb0, 0x20874e0c8, 0x2208726e88, 0x2087a4220, 0x0, 0x0)
23:17:12 proxy | 	/usr/local/opt/go/libexec/src/pkg/net/http/server.go:1576 +0x7c
23:17:12 proxy | github.com/coreos/etcd/etcdmain.func·008()
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/etcdmain/etcd.go:303 +0x14b
23:17:12 proxy | created by github.com/coreos/etcd/etcdmain.startProxy
23:17:12 proxy | 	/Users/unihorn/gopath/src/github.com/coreos/etcd/gopath/src/github.com/coreos/etcd/etcdmain/etcd.go:304 +0xc28
23:17:12 proxy | Terminating proxy

@yichengq I cannot reproduce this on master. Also I found there is a bug that might cause this, but it is not caused by adding a member.

More reliable way to reproduce:

apply patch

diff --git a/Procfile b/Procfile
index 7e6f4f7..b1e8458 100644
--- a/Procfile
+++ b/Procfile
@@ -1,5 +1,5 @@
 # Use goreman to run `go get github.com/mattn/goreman`
-etcd1: bin/etcd -name infra1 -listen-client-urls http://localhost:4001 -advertise-client-urls http://localhost:4001 -listen-peer-urls http://localhost:7001 -initial-advertise-peer-urls http://localhost:7001 -initial-cluster-token etcd-cluster-1 -initial-cluster 'infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003' -initial-cluster-state new
-etcd2: bin/etcd -name infra2 -listen-client-urls http://localhost:4002 -advertise-client-urls http://localhost:4002 -listen-peer-urls http://localhost:7002 -initial-advertise-peer-urls http://localhost:7002 -initial-cluster-token etcd-cluster-1 -initial-cluster 'infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003' -initial-cluster-state new
-etcd3: bin/etcd -name infra3 -listen-client-urls http://localhost:4003 -advertise-client-urls http://localhost:4003 -listen-peer-urls http://localhost:7003 -initial-advertise-peer-urls http://localhost:7003 -initial-cluster-token etcd-cluster-1 -initial-cluster 'infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003' -initial-cluster-state new
+etcd1: sleep 1 && bin/etcd -name infra1 -listen-client-urls http://localhost:4001 -advertise-client-urls http://localhost:4001 -listen-peer-urls http://localhost:7001 -initial-advertise-peer-urls http://localhost:7001 -initial-cluster-token etcd-cluster-1 -initial-cluster 'infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003' -initial-cluster-state new
+etcd2: sleep 1 && bin/etcd -name infra2 -listen-client-urls http://localhost:4002 -advertise-client-urls http://localhost:4002 -listen-peer-urls http://localhost:7002 -initial-advertise-peer-urls http://localhost:7002 -initial-cluster-token etcd-cluster-1 -initial-cluster 'infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003' -initial-cluster-state new
+etcd3: sleep 1 && bin/etcd -name infra3 -listen-client-urls http://localhost:4003 -advertise-client-urls http://localhost:4003 -listen-peer-urls http://localhost:7003 -initial-advertise-peer-urls http://localhost:7003 -initial-cluster-token etcd-cluster-1 -initial-cluster 'infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003' -initial-cluster-state new
 proxy: bin/etcd -proxy=on -bind-addr <IP_ADDRESS>:8080 -initial-cluster 'infra1=http://localhost:7001,infra2=http://localhost:7002,infra3=http://localhost:7003'

goreman start
wait 1 min


Protractor not working with Firefox using Selenium standalone server.  Works if using directConnect: true

Bug report

Node Version: v4.1.2
Protractor Version: 2.4.0
Browser(s): Firefox 44, 45
Operating System and Version Mac 10.11.4
Your protractor configuration file

`exports.config = {
seleniumAddress: 'http://localhost:4444/wd/hub',
specs: ['tests/*.js'],
baseUrl: 'http://localhost/',
framework: 'jasmine2',
//directConnect: true,
capabilities: {
browserName: 'firefox'
},
...
`

A relevant example test: Any simple test that opens browser and navigates to a web page.
Output from running the test: Firefox opens, but it doesn't load page.  Eventually, it will error out
Steps to reproduce the bug:

start selenium stand alone server
run test
browser will open, but doesn't navigate to page
eventually errors out.

The URL you are running your tests against (if relevant)

Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver
/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:108
var template = new Error(this.message);
^
UnknownError: Unable to connect to host <IP_ADDRESS> on port 7055 after 45000 ms. Firefox console output:
:1452825183000,"updateDate":1452825183000,"applyBackgroundUpdates":1,"skinnable":true,"size":8164,"sourceURI":null,"releaseNotesURI":null,"softDisabled":false,"foreignInstall":false,"hasBinaryComponents":false,"strictCompatibility":true,"locales":[],"targetApplications":[{"id":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","minVersion":"44.0","maxVersion":"44.0"}],"targetPlatforms":[]}
1461270371565   addons.xpi  DEBUG   getModTime: Recursive scan of {972ce4c6-7e08-4474-a285-3208198ce6fd}
1461270371565   addons.xpi  DEBUG   Updating XPIState for {"id":"web2pdfextension@web2pdf.adobedotcom","syncGUID":"pK2loL5dv2Vj","location":"app-system-local","version":"15","type":"extension","internalName":null,"updateURL":null,"updateKey":null,"optionsURL":null,"optionsType":null,"aboutURL":null,"icons":{},"iconURL":"chrome://web2pdfextension/skin/C_AdobeLogo_48x48.png","icon64URL":"chrome://web2pdfextension/skin/C_AdobeLogo_64x64.png","defaultLocale":{"name":"Adobe Acrobat DC - Create PDF","description":"Converts a web page to PDF","creator":"Adobe Systems Incorporated","homepageURL":"http://www.adobe.com/"},"visible":true,"active":false,"userDisabled":true,"appDisabled":false,"descriptor":"/Library/Application Support/Mozilla/Extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/web2pdfextension@web2pdf.adobedotcom","installDate":1449871153000,"updateDate":1449871153000,"applyBackgroundUpdates":1,"bootstrap":false,"size":167926,"sourceURI":null,"releaseNotesURI":null,"softDisabled":false,"foreignInstall":true,"hasBinaryComponents":false,"strictCompatibility":false,"locales":[],"targetApplications":[{"id":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","minVersion":"4.0","maxVersion":"46.0"}],"targetPlatforms":[],"multiprocessCompatible":false,"signedState":2}
1461270371566   DeferredSave.extensions.json    DEBUG   Save changes
1461270371566   addons.xpi  DEBUG   Updating database with changes to installed add-ons
1461270371566   addons.xpi-utils    DEBUG   Updating add-on states
1461270371566   addons.xpi-utils    DEBUG   Writing add-ons list
1461270371573   addons.manager  DEBUG   Registering shutdown blocker for XPIProvider
1461270371573   addons.manager  DEBUG   Provider finished startup: XPIProvider
1461270371573   addons.manager  DEBUG   Starting provider: LightweightThemeManager
1461270371573   addons.manager  DEBUG   Registering shutdown blocker for LightweightThemeManager
1461270371574   addons.manager  DEBUG   Provider finished startup: LightweightThemeManager
1461270371574   addons.manager  DEBUG   Starting provider: GMPProvider
1461270371577   addons.manager  DEBUG   Registering shutdown blocker for GMPProvider
1461270371577   addons.manager  DEBUG   Provider finished startup: GMPProvider
1461270371577   addons.manager  DEBUG   Starting provider: PluginProvider
1461270371578   addons.manager  DEBUG   Registering shutdown blocker for PluginProvider
1461270371578   addons.manager  DEBUG   Provider finished startup: PluginProvider
1461270371578   addons.manager  DEBUG   Completed startup sequence
1461270371764   addons.manager  DEBUG   Starting provider:
1461270371764   addons.manager  DEBUG   Registering shutdown blocker for
1461270371765   addons.manager  DEBUG   Provider finished startup:
1461270371902   DeferredSave.extensions.json    DEBUG   Write succeeded
1461270371902   addons.xpi-utils    DEBUG   XPI Database saved, setting schema version preference to 17
1461270371902   DeferredSave.extensions.json    DEBUG   Starting timer
1461270371904   addons.repository   DEBUG   No addons.json found.
1461270371904   DeferredSave.addons.json    DEBUG   Save changes
1461270371906   DeferredSave.addons.json    DEBUG   Starting timer
1461270371920   addons.manager  DEBUG   Starting provider: PreviousExperimentProvider
1461270371920   addons.manager  DEBUG   Registering shutdown blocker for PreviousExperimentProvider
1461270371920   addons.manager  DEBUG   Provider finished startup: PreviousExperimentProvider
1461270371939   DeferredSave.extensions.json    DEBUG   Starting write
1461270371965   DeferredSave.addons.json    DEBUG   Starting write
1461270371968   DeferredSave.extensions.json    DEBUG   Write succeeded
1461270371978   DeferredSave.addons.json    DEBUG   Write succeeded
at new bot.Error (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:108:18)
at Object.bot.response.checkResponse (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/response.js:109:9)
at /usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:160:24
at [object Object].promise.ControlFlow.runInFrame_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:1857:20)
at [object Object].goog.defineClass.notify (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:2448:25)
at [object Object].promise.Promise.notify_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:564:12)
at Array.forEach (native)
at [object Object].promise.Promise.notifyAll_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/../webdriver/promise.js:553:15)
at goog.async.run.processWorkQueue (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/async/run.js:130:15)
at process._tickCallback (node.js:357:9)

From: Task: WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:157:22)
at Function.webdriver.WebDriver.createSession (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:131:30)
at [object Object].Builder.build (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/builder.js:445:22)
at [object Object].DriverProvider.getNewDriver (/usr/local/lib/node_modules/protractor/lib/driverProviders/driverProvider.js:38:7)
at [object Object].Runner.createBrowser (/usr/local/lib/node_modules/protractor/lib/runner.js:180:37)
at /usr/local/lib/node_modules/protractor/lib/runner.js:256:21
at _fulfilled (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:797:54)
at self.promiseDispatch.done (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:826:30)
at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:759:13)
at /usr/local/lib/node_modules/protractor/node_modules/q/q.js:525:49
[launcher] Process exited with error code 1
Feature Request

Reasons for adopting new feature
Is this a breaking change? (How will this affect existing functionality)
cannot run using selenium server.

I can second this. Having exactly the same problem.

Cannot reproduce with FireFox 45.0.1 and the same OS.
What version of the selenium server are you running? Can you make sure it's up to date?

@spengilley @tommyz0123 are you both using Protractor 2.x? I haven't been able to reproduce this using 3.x

@NickTomlin Yes, I'm using 2.4.0.  I start the selenium server using "webdriver-manager start".  One thing I tried that works is to start it from my config by setting "seleniumServerJar".  But, I need to run grid, so this won't help.

@NickTomlin how do you update to 3.x?  I ran "webdriver-manager update" and it says i'm already up-to-date.

@tommyz0123 You can upgrade protractor by editing your project's package.json or globally via npm install -g protractor@latest

I'm going to go ahead and close this since there hasn't been any activity and a version upgrade should hopefully sort things.

yes. upgrading to 3.x fixed the problem for me.

Unfortunately upgrading to version 3 isn't an option for us. We are using Angular 1.2.29 to support IE8. Could this not be patched in version 2?

This is happening to me on protractor 3.10.9 even after running webdriver-manager update

I nave this problem on protractor 5

@karolmie1 @alexfromapex
Could you open separate issues? Thanks!

Protractor Version : 5.1.1
Firefox Version : 45.x
Not able to run protractor script on firefox version
What are the solution?

@makwanaparth94 , why use FireFox 45?
Secondly, as far as I know FireFox 45 isn't supported by Protractor 5.1.1 with Selenium 3. Can't you upgrade to 53?

Protractor 5.x requires Selenium 3 and Firefox 52 or greater. The changes made to Firefox's automation prevent us from easily support old and new Firefox in the same Protractor release.
If you need to test on Firefox 45, you're stuck with Protractor 4.x

@wswebcreation I updated it with latest version and now it's running


feat(RELEASE-996): add release-service-monitor to production

this commit adds the release-service-monitor to production cluster.
Signed-off-by: Leandro Mendes<EMAIL_ADDRESS>

Responded with a question about this on slack


build: create v0.18.1-beta release branch

Adds the following PR as the sole fix for v0.18.1-beta:

https://github.com/lightningnetwork/lnd/pull/8862

ah - the only thing is that this now contains the release notes for 0.18.2 ...

replaced by https://github.com/lightningnetwork/lnd/pull/8863


Resolve problem with isomorphic support

This small changes fix problem with isomorphic app.
(If u merge it, don't forgot to change README.md ;) )

Awesome, you've made a lot of people really happy :)
Merging and will update the readme and the a bit !
Thanks !

U are welcome))
ср, 31 авг. 2016 г. в 18:07, Rakan Nimer<EMAIL_ADDRESS>
Merged #65 https://github.com/RakanNimer/react-google-charts/pull/65.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RakanNimer/react-google-charts/pull/65#event-773729153,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqv_5Xc-Vqw0c7Y__rMG3NRmZZ_z1erks5qlY8pgaJpZM4Jxfi6
.


Add support for multi-frame requests

See conversation in Issue #2

Reviewed with @emarsman and @rwoberholzer


Use mermaid for "defmt ecosystem" diagram

What
This PR removes the previous (static) diagram of the defmt ecosystem from the README and replaces it with a mermaid code block.
Context
Mermaid is a JavaScript based diagramming and charting tool that renders Markdown-inspired text definitions to create and modify diagrams dynamically. It is widely used. By now both GitHub and crates.io do render mermaid diagrams, in GitHub you can even interact with them (zooming in and out mostly, but still).
Why
This change will make it easier to keep the diagram up to date, since we don't rely on other tooling (draw.io in our case) to modify the diagram.
Drawbacks
As a grain of salt I have to say that I actually do like the aesthetics of the previous diagram more (see below). But I still think that the advantages outweigh that. It is possible to style the mermaid diagram with CSS, but I did not want to go down that road.
Before

After

I will do a pre-release on crates.io to see if it renders there as well.

Unfortunately it fails to render. See https://crates.io/crates/defmt/0.3.6-beta.0
crates.io shows a warning popup with "Failed to render mermaid diagram." and in the console it prints "WARN: Could not find the language 'mermaid', did you forget to load/include a language module?".
It could be because I am not using the default renderer.

It could be because I am not using the default renderer.

Nope. Changing back to the default renderer does not change anything.

As a grain of salt I have to say that I actually do like the aesthetics of the previous diagram more (see below).

hm, I find the mermaid one (at least as rendered here) more pretty

We need to wait for https://github.com/rust-lang/crates.io/issues/6786 to be resolved

We need to wait for rust-lang/crates.io#6786 to be resolved

The bug is fixed and does render on crates.io now! 🎉


Crash with a combination of recent mods

I recently got a crash during gameplay using a combination of recent mods with Ryujinx 1.1.809. I was running around in the rain on the Great Plateau.

TotK 1.1.0
Ryujinx 1.1.809
Mods are from latest pull from this repo as of this issue's creation date/time

Main log:
Ryujinx_1.1.809_2023-05-20_10-17-07.log
Crash error log (from console):
ryujinx-1.1.809-crash-mods.log

FSR Sharpening is known to crash Ryuginx, it's why i ask to read the documentation, plus this mod alone is useless
Try to disable 1024x shadow too

Ahh I see, sorry for not reading it more closely. I was scanning the docs for notes and changes but I somehow missed that point. Thanks for pointing out 👍
I'm still using totk-friends v2 which has some FSR fixes baked in. That's been much smoother so far, and it includes 1080p / LOD fixes as well.

Ahh I see, sorry for not reading it more closely. I was scanning the docs for notes and changes but I somehow missed that point. Thanks for pointing out 👍
I'm still using totk-friends v2 which has some FSR fixes baked in. That's been much smoother so far, and it includes 1080p / LOD fixes as well.


Added users/self route.

Added the users/self route.
Fixes #37
This will return user object when user hits this endpoint.

@Rucha1499 I think you are working over swaraj's commits.
His PR is merged now, it'll be great if you can take a pull from Develop and only push your commits

LGTM


Await custom user state when provisioning Equinix Metal Devices

Rather than relying on Equinix Metal's reported device state, users may wish to take advantage of custom states, reported through POSTing to metadata to signify when Terraform should consider a node active.
https://metal.equinix.com/developers/docs/server-metadata/user-state/
For example:
resource "metal_device" "foo" {
  behaviors {
    wait_for_userstate = {state: succeeded, code: 1234}
  }
}

With a definition like this, rather than waiting for the "status: active" poll, Terraform would wait for an event to be received on for this device with the matching userstate.
Within the server, the user would trigger this event via userdata or SSH provisioning:
curl -s -X POST -d '{"state":"succeeded", code: 1234, message:{"testly":"test"}}' $(curl -s https://metadata.platformequinix.com/metadata | jq -r .user_state_url)

message can be any JSON blob, I believe.
It's not clear to me what format Terraform would accept to allow for user-state event matching. Is state enough? code? code + state? message? code + state + message? Do we limit Terraform to matching on text messages or should we match the whole message object or subentities within it?

If this feature is implemented, it should be noted as best practice whenever userdata is specified and network mode will be converted to Layer2 only.

wait_for_userstate = {state: succeeded, code: 1234}

@cprivitere points out that it would be necessary for CloudInit to report failure too. The wait_for parameter would need to be aware of failure conditions/states.
A failed CloudInit would result in a failed provision. Should Terraform leave the machine up? Do we want another behavior to define this?
Perhaps:
wait_for_userstate = { userstate: {state: succeeded, code: 1234}, <something to define failure behavior> }

A timeout based failure would be triggered if the userstate was not pushed in the create timeout window.

Is there an API endpoint for retrieving userstate for a device?  I don't see it in the docs.

@ctreatma it's part of the device events feed:
/metal/v1/devices/.../events?&per_page=25&page=1
The event will have a type that identifies it as a user-state event.

I don't know if userstate events also appear in that list, but there an wait_for_userstate and wait_for_provisioning_event would function similarly.


naming a warp point 'name' will crash the game

Error Message
Error while running event level::on_tick(ID 0)
...Data/Roaming/Factorio/temp/currently-playing/control.lua:14:attempt to concatenate local 'err'/a table value)
Known Causes
Know causes that will result in error:

typing /make-warp name

To Reproduce (please give for each cause outlined above)
Steps to reproduce the behavior:

Cause 1

Open a game that has the latest version of the script
type /make-warp name

Other information (please complete the following information):

Windows, +whatever ExplosingGaming is running on
Factorio Version: [0.16.45]

Additional context
It has crashed one explosiveGaming server (s2) today (2018-05-26) while Gizan was playing.

The problem of the crash was due to an error in the error handdle within the core files so that was a luckly find as any error would have crashed the server. See fix.
The warp problem was an easy fix just added some valadation to which names could be used, there may be other areas where this problem will arise. See fix.


Attachments from RapidPro

Significant amount of work related to RapidPro Bot is done in #130. Attachments from RapidPro however are tricky. There are mainly two issues with attachments right now:
1. Attachments aren't parsed 'out' from the message body
Attachments need to be parsed from the message's body and show up as preview-able content for (Image, Video and Audio files)
2. Attachments do not live on the IoGT Server
IoGT is intended to be free-to-use for all users. However, data charges are incurred for any external links/resources. To mitigate this, we have to come up with a strategy to download attachments on the IoGT server and replace external links with internal ones. Other ideas are welcome too.

cc: @dannyparsons @geoo89

Thanks, yes agree with the approach for 2.

I think we can close this ticket. There is another ticket which is related to the bugs from the RapidPro bot.
cc: @geoo89


Upload torcharrow build to conda

In this PR I have two changes:

Added uploading sections to pytorch-nightly conda channel to both linux and osx builds.
Switched the building trigger to nightly (previously it was triggered with every pull request).

Once this is done we should be able to install from conda pytorch-nightly channel: https://anaconda.org/pytorch-nightly/torcharrow . A little caveat though, is since we don't have a delocate-wheel/audit-wheel equivalent, import torcharrow will throw an error of dylib not found from its default path. This is something we are actively working with velox team and will hopefully resolve soon.

LGTM with one comment

where's the comment? 😄


building tweaks v0.12.1.x on mac (osx) and 'make check' fails

Is v0.12.1.x the active development branch? Should it pass the tests in 'make check'?
I was only able to build on mac using:
brew uninstall protobuf
brew install homebrew/versions/protobuf260 --c++11
export CXXFLAGS=-std=c++11
./configure
Which builds successfully. (Note: there are some warnings)
However, 'make check' fails.
/Applications/Xcode.app/Contents/Developer/usr/bin/make  check-TESTS check-local

FAIL: test/test_dash
PASS: qt/test/test_dash-qt
Testsuite summary for Dash Core 0.12.1
TOTAL: 2
PASS:  1
SKIP:  0
XFAIL: 0
FAIL:  1
XPASS: 0
ERROR: 0
See src/test-suite.log
Please report to https://github.com/dashpay/dash/issues
test-suite.log.txt
dash_build_output_from_9c5db04.txt
Note: Changed the log file to end with .txt for github.
I would like to work on the doc (https://github.com/dashpay/dash/blob/v0.12.1.x/doc/build-osx.md_ and cleaning up the warnings, but not until the 'make check' works successfully.

You shouldn't use C++11 to compile Dash Core, we don't fully support this yet. The reason why you may want to compile is probably because Qt5 5.7 (which is default for homebrew now iirc) requires C++11, so make sure to install Qt version < 5.6.2 (Qt5 5.6.2 has some other issues, 5.6.1-1 should work just fine): brew install https://raw.githubusercontent.com/Homebrew/homebrew-core/e6d954bab88e89c5582498157077756900865070/Formula/qt5.rb

Thanks.
I also had to run: (as protobuf v3.1 has issues)
brew uninstall protobuf
brew install homebrew/versions/protobuf260 --c++11
Also, the latest commit now passes the 'make check'.
Closing issue.


[doc:build_docs.py] can't build document on ubunt WSL for windows 10

previously I have not had any issues building the document on my Linux subsystem
but even after upgrading and updating
I am having this issue.
rasmus@JBMPTN2:~/opnetitan$ sudo ./util/build_docs.py --preview
INFO: Parsed hw/ip/aes/data/aes.hjson
INFO: Parsed hw/top_earlgrey/ip/alert_handler/data/autogen/alert_handler.hjson
INFO: Parsed hw/ip/entropy_src/data/entropy_src.hjson
INFO: Parsed hw/ip/csrng/data/csrng.hjson
INFO: Parsed hw/ip/edn/data/edn.hjson
INFO: Parsed hw/ip/flash_ctrl/data/flash_ctrl.hjson
INFO: Parsed hw/ip/gpio/data/gpio.hjson
INFO: Parsed hw/ip/hmac/data/hmac.hjson
INFO: Parsed hw/ip/i2c/data/i2c.hjson
INFO: Parsed hw/ip/keymgr/data/keymgr.hjson
INFO: Parsed hw/ip/lc_ctrl/data/lc_ctrl.hjson
WARNING: NMI_GEN contains extra key reset_request_list
INFO: Parsed hw/ip/nmi_gen/data/nmi_gen.hjson
INFO: Parsed hw/ip/otbn/data/otbn.hjson
INFO: Parsed hw/ip/otp_ctrl/data/otp_ctrl.hjson
INFO: Parsed hw/ip/padctrl/data/padctrl.hjson
INFO: Parsed hw/ip/pattgen/data/pattgen.hjson
INFO: Parsed hw/top_earlgrey/ip/pinmux/data/autogen/pinmux.hjson
WARNING: !!MIO_OUTSEL not found in register list.
WARNING: !!MIO_OUTSEL not found in register list.
WARNING: !!MIO_OUTSEL not found in register list.
WARNING: !!MIO_OUT_SLEEP_VAL not found in register list.
WARNING: !!MIO_OUTSEL not found in register list.
WARNING: !!MIO_OUTSEL not found in register list.
WARNING: !!MIO_OUTSEL not found in register list.
WARNING: !!MIO_OUT_SLEEP_VAL not found in register list.
WARNING: !!WKUP_DETECTOR not found in register list.
WARNING: !!WKUP_DETECTOR_CNT_TH not found in register list.
WARNING: !!WKUP_DETECTOR_PADSEL not found in register list.
WARNING: !!WKUP_DETECTOR_CNT_TH not found in register list.
WARNING: !!WKUP_DETECTOR_CNT_TH not found in register list.
WARNING: !!WKUP_DETECTOR_PADSEL not found in register list.
WARNING: !!WKUP_DETECTOR_PADSEL not found in register list.
WARNING: !!WKUP_DETECTOR not found in register list.
WARNING: !!WKUP_DETECTOR not found in register list.
WARNING: !!PERIPH_INSEL not found in register list.
INFO: Parsed hw/top_earlgrey/ip/pwrmgr/data/autogen/pwrmgr.hjson
WARNING: SW_RST_CTRL_N: hwext register readable by software cannot be hro. Changing it to hrw.
WARNING: SW_RST_CTRL_N: hwext register readable by software cannot be hro. Changing it to hrw.

INFO: Generated Software API Documentation (Doxygen)
WARNING: Doxygen Generated Warnings (saved in /home/rasmus/opnetitan/build/docs-generated/sw/doxygen_warnings.log)
INFO: Generated DIF Listing for sw/device/lib/dif/dif_alert_handler.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_gpio.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_hmac.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_i2c.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_otbn.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_otp_ctrl.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_plic.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_pwrmgr.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_rstmgr.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_rv_timer.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_spi_device.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_uart.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_usbdev.h
ERROR: No DIF functions found for sw/device/lib/dif/dif_warn_unused_result.h
INFO: Generated DIF Listing for sw/device/lib/dif/dif_warn_unused_result.h
INFO: Hugo binary path: /home/rasmus/opnetitan/build/docs-hugo/hugo
INFO: Checking for correct Hugo version: 0.71.0
Built in 547 ms
Error: Error building site: process: readAndProcessContent: walk: Readdir: decorate: lstat<EMAIL_ADDRESS>no such file or directory
Error building site

I see doxygen spits out a huge file of warnings but I didn't find anything in the file to indicate the actual problem.
but I am not sure how to continue my debugging

This line is odd:
Error: Error building site: process: readAndProcessContent: walk: Readdir: decorate: lstat<EMAIL_ADDRESS>no such file or directory
Where's the opnetitan typo coming from?

That is just my git path i accidentally made a typo wheb i created the folder
Hent Outlook til Androidhttps://aka.ms/ghei36

From: Philipp Wagner<EMAIL_ADDRESS>Sent: Monday, October 26, 2020 3:21:35 PM
To: lowRISC/opentitan<EMAIL_ADDRESS>Cc: Rasmus Madsen<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [lowRISC/opentitan] [doc:build_docs.py] can't build document on ubunt WSL for windows 10 (#3901)
This line is odd:
Error: Error building site: process: readAndProcessContent: walk: Readdir: decorate: lstat<EMAIL_ADDRESS>no such file or directory
Where's the opnetitan typo coming from?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/lowRISC/opentitan/issues/3901#issuecomment-716578668, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM3LL7ZTNWQUXT34O232RS3SMWAW7ANCNFSM4S7NRDVQ.

@imphil I was looking in the usbdev/data/usbdev.prj.hjson that it seem to complain about but I don't see any problems there.

This looks like https://github.com/gohugoio/hugo/issues/6526, which points at emacs backup files created in the opentitan directory, which then hang hugo (it's surprisingly picky about things in the opentitan tree it shouldn't care about). Can you try to read through the linked issue and see if any of the proposed workarounds do the trick for you?
I'd try to

Close emacs
delete backup files rm -f<EMAIL_ADDRESS>Optionally delete the hugo build directory rm -rf /home/philipp/src/opentitan/build/docs

closing emacs worked for some odd reason.. thank you


IPS-667 OTG Monitoring and alerting for event bridge

Proposed changes
What changed

Added dead letter queues for event bridge schedules (not stubs)
Added cloudwatch alarms for the dead letter queues if message count is greater than zero
Added map for retries and delays.

Why did it change
To enable monitoring and alerting on the HMRC OTG token refresh
Issue tracking

IPS-667

Checklists
Environment variables or secrets

[X] No environment variables or secrets were added or changed

Move to shorter named branch to prevent workflow failures: https://github.com/govuk-one-login/ipv-cri-otg-hmrc/pull/65


Use the new timeseries extractor made for CCNA

https://github.com/ccna-biomarkers/ccna_ts_extraction

This is over-engineering. Settled for a half way solution.


fix unit test breakage due to lint changes

Addresses #14756
Signed-off-by: Srini Brahmaroutu<EMAIL_ADDRESS>Change require for unit test failure from the pr#14875

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "btrfs_test_failure" git@github.com:brahmaroutu/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM


[SUPPORT] Flink write to COW Hudi table,hive aggregate query results has duplicate data but select * did not

Describe the problem you faced
I use Flink write Hudi COW table and sync to hive , but hive aggregate query (eg. count(*), row_number() over() )results has duplicate data but select * did not.
To Reproduce
Steps to reproduce the behavior:

Flink-SQL write  Hudi COW table.

upsert
        String hudiSinkDDL = "CREATE TABLE hudi_table(\n" +
                "id String,\n" +
                "name String,\n" +
                "age Int,\n" +
                "PRIMARY KEY (id) NOT ENFORCED \n" +
                ") WITH (\n" +
                // 基本配置
                "'write.operation' = 'upsert',\n" +
                "'write.precombine' = 'true',\n" +
                "'connector' = 'hudi',\n" +
                "'path'= '${basePath}',\n" +
                "'table.type' = 'COPY_ON_WRITE',\n" +
                "'write.tasks' = '2',\n" +
                "'write.bucket_assign.tasks' = '2',\n" +
                // 同步hive配置
                "'hive_sync.conf.dir'='/opt/apache-hive-3.1.3-bin/conf',\n" +
                "'hive_sync.enabled' = 'true',\n" + // 将数据集注册并同步到 hive metastore
                "'hive_sync.mode' = 'hms',\n" + // 采用 hive metastore 同步
                "'hive_sync.metastore.uris' = 'thrift://localhost:9083',\n" +
                "'hive_sync.db' = 'cdc_hudi',\n" +
                "'hive_sync.table' = '${tableName}',\n" +
                // 小文件&压缩配置
                "'clean.retain_commits' = '1',\n" +
                "'metadata.compaction.delta_commits' = '5',\n" +
                "'hoodie.parquet.compression.codec' = 'gzip',\n" +
                "'hoodie.parquet.max.file.size' = '268435456'\n" +
                ")";

insert data into MySQL and update it.

-- insert
insert into table_test_duplicate_1(id,name,age) values('dup_clean_1','Camellia',11);
-- update
update table_test_duplicate_1 set age = 20 where id ='dup_clean_1';

select * from cdc_hudi.table_test_duplicate_1 where id = 'dup_clean_1'; Normal results.

execute aggregate function; data duplication.

select count(1) from cdc_hudi.table_test_duplicate_1 where id = 'dup_clean_1';

select
*,
row_number() over (partition by id order by age desc) as rank
from cdc_hudi.table_test_duplicate_1 where id = 'dup_clean_1';

Expected behavior
Why do aggregated queries and regular queries have inconsistent results？Your help is appreciative.
Environment Description

Hudi version : 0.14.0

Spark version : no

Flink version : 1.17.0

Hive version : 3.1.3

Hadoop version : 3.3.6

Storage (HDFS/S3/GCS..) :HDFS

Running on Docker? (yes/no) :no

what's you hive execution engine? do you update the hudi-hadoop-mr-bundle jar in hive.tar.gz or tez.tar.gz on hdfs?

what's you hive execution engine? do you update the hudi-hadoop-mr-bundle jar in hive.tar.gz or tez.tar.gz on hdfs?

Sorry for the late reply. I am using Hive-on-MR, and hudi-hadoop-mr-bundle-0.14.0.jar has been added to ${HIVE_HOME}/auxlib.

Is the hive table synced automatically from the ingestion job?

Is the hive table synced automatically from the ingestion job?

yes, Hive synchronization haven been enabled.

can you show us the create table statement from Hive?

can you show us the create table statement from Hive?

Okay, the table in Hive is an external table automatically generated during synchronization. The statement is as follows:
CREATE EXTERNAL TABLE cdc_hudi.table_test_duplicate_1(
_hoodie_commit_time string COMMENT '',
_hoodie_commit_seqno string COMMENT '',
_hoodie_record_key string COMMENT '',
_hoodie_partition_path string COMMENT '',
_hoodie_file_name string COMMENT '',
id string COMMENT '',
name string COMMENT '',
age int COMMENT '')
ROW FORMAT SERDE
'org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe'
WITH SERDEPROPERTIES (
'hoodie.query.as.ro.table'='false',
'path'='hdfs://localhost:8020/user/hive/warehouse/cdc_hudi.db/table_test_duplicate_1')
STORED AS INPUTFORMAT
'org.apache.hudi.hadoop.HoodieParquetInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.parquet.MapredParquetOutputFormat'
LOCATION
'hdfs://localhost:8020/user/hive/warehouse/cdc_hudi.db/table_test_duplicate_1'
TBLPROPERTIES (
'last_commit_completion_time_sync'='20240112161204004',
'last_commit_time_sync'='20240112160716028',
'spark.sql.sources.provider'='hudi',
'spark.sql.sources.schema.numParts'='1',
'spark.sql.sources.schema.part.0'='{"type":"struct","fields":[{"name":"_hoodie_commit_time","type":"string","nullable":true,"metadata":{}},{"name":"_hoodie_commit_seqno","type":"string","nullable":true,"metadata":{}},{"name":"_hoodie_record_key","type":"string","nullable":true,"metadata":{}},{"name":"_hoodie_partition_path","type":"string","nullable":true,"metadata":{}},{"name":"_hoodie_file_name","type":"string","nullable":true,"metadata":{}},{"name":"id","type":"string","nullable":false,"metadata":{}},{"name":"name","type":"string","nullable":true,"metadata":{}},{"name":"age","type":"integer","nullable":true,"metadata":{}}]}',
'transient_lastDdlTime'='1704939293')

Looks good, @xicm can you help confirm this issue?

Seems a bug

Seems a bug

When I set hive.input.format=org.apache.hudi.hadoop.hive.HoodieCombineHiveInputFormat , result is right , is this necessary before querying?

Yeah, you should use HoodieHiveInputFormat or HoodieCombineHiveInputFormat. This is a Chinese doc that you can take a refeerence: https://www.yuque.com/yuzhao-my9fz/kb/kgv2rb