fix(rpc): always include withdrawals in RPC

this fixes the debug_getRawBlock hive test.
In RPC, withdrawals are always included, no withdrawals are empty list.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@f2cb8be). Click here to learn what that means.
The diff coverage is 78.57%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #1894   +/-   ##
=======================================
  Coverage        ?   73.07%
=======================================
  Files           ?      418
  Lines           ?    51179
  Branches        ?        0
=======================================
  Hits            ?    37401
  Misses          ?    13778
  Partials        ?        0

Flag
Coverage Δ

integration-tests
19.59% <7.14%> (?)

unit-tests
67.40% <71.42%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/rpc/rpc/src/debug.rs
26.47% <25.00%> (ø)

crates/primitives/src/block.rs
78.10% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Added prefix option for agents

This prevents users from having to repeat themselves in tests, by setting a common prefix for all routes.

I think this should be closed in favor of #453

These two PRs provide different features

@Thann  yes you are right.
Let me give this some thought as I want to make sure if we start extending capabilities with extra "options" we do so in a way to keep the object Prototype manageable. I think along the lines of what you have with the optional options object is the way to go.

Pull Request Test Coverage Report for Build 407

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.8%) to 99.111%

Totals

Change from base Build 404:
1.8%

Covered Lines:
141

Relevant Lines:
142

💛  - Coveralls

Pull Request Test Coverage Report for Build 407

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.8%) to 99.111%

Totals

Change from base Build 404:
1.8%

Covered Lines:
141

Relevant Lines:
142

💛  - Coveralls


Submission 6

Lastly we updated result with some changes in DNN. We somewhat expect this problem set is more suitable to boosted tree than DNN; however, for curiosity, we keep testing our ideas. :)
Please take a look at both ModeResult and Smooth one. Much appreciated!!
best,
Charles

Hello Charles... I'm afraid the contest has closed --- I cannot accept any more entries.
I'll score this for you, but I can't change your score.
Thank you for your participation, all the same. Kudos for pushing hard on deep learning!

Hey... this one got 0.521. As you say --- perhaps not the dataset for DNNs to shine. Soon I hope there will be a contest with a bigger dataset!

Dear Matt,
Can we have the hidden well facies label for testing? (If available
already) where can I get it?
I hope this email still finds you!
Best,
Charles
On Wednesday, February 1, 2017, Matt Hall<EMAIL_ADDRESS>wrote:

Hey... this one got 0.521. As you say --- perhaps not the dataset for
DNNs to shine. Soon I hope there will be a contest with a bigger dataset!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/seg/2016-ml-contest/pull/227#issuecomment-276553236,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYNxIC-Bfn4PthRbi9RIxFLKDTauAr3Cks5rX-hqgaJpZM4LzZjz
.


added background to starting-comment class

new issue comment background wasn't styled. this fixes that.

I appreciate the help! :)


feat: add fuzzy single select prompt

Superseeds #34.
There is sadly one problem that I can't resolve. I wanted to add the search term to the prompt so that users can see what they typed. But I can't find a way to delete the old prompt. My attempt is commented out inside the loop.
When I include the commented out code, I still get a new prompt each time I type a character.
Follow-up with a working GIF.

In the example I type ice. Since Ice matches exactly, it is shown first.

Applying this patch does display the search prompt. As far as I understood, there is no performance impact. Preserve prompt does also delete all lines but keeps the prompt intact. Manually calling clear does delete the prompt as well.
diff --git a/src/prompts/fuzzy.rs b/src/prompts/fuzzy.rs
index 1e6859c..024460a 100644
--- a/src/prompts/fuzzy.rs
+++ b/src/prompts/fuzzy.rs
@@ -158,15 +158,11 @@ impl<'a> FuzzySelect<'a> {
         let matcher = fuzzy_matcher::skim::SkimMatcherV2::default();

         loop {
-            // TODO: resolve
-            // if !search_term.is_empty() {
-            //     render.clear_preserve_prompt(&size_vec)?;
-            //     match &self.prompt {
-            //         Some(prompt) => render.select_prompt(&format!("{}: {}", prompt, search_term))?,
-            //         None => render.select_prompt(&format!("> {}", search_term))?,
-            //     };
-            // }
-            // ENDTODO
+            render.clear()?;
+            match &self.prompt {
+                Some(prompt) => render.input_prompt_selection(prompt, &search_term)?,
+                None => render.select_prompt(&format!("> {}", search_term))?,
+            };

             // Maps all items to a tuple of item and its match score.
             let mut filtered_list = self.items.iter()
@@ -258,7 +254,6 @@ impl<'a> FuzzySelect<'a> {
             if filtered_list.len() > 0 && (sel < page * capacity || sel >= (page + 1) * capacity) {
                 page = sel / capacity;
             }
-            render.clear_preserve_prompt(&size_vec)?;
         }
     }
 }
\ No newline at end of file

I'll open another issue for this, but working on the code base the first time I had a hard time understanding some logic. Some parts have a rather high cognitive complexity and without comments they are hard to grasp. This should be opened as a new issue though.
Maybe some internal documentation would be nice as well. For example the render methods could include a short example on what the output looks like exactly. Ideally, write_formatted_str would actually return the string and not delegate the call to self.term. That way, the examples could be even run using rustdoc tests.

Fixed the prompt in the latest commit. Here are two screenshots, one with and one without a prompt text. The commit message does explain my changes to Theme to accomplish this:

Hi, just a quick question about the return value of the interact() functions in this PR:
Is there a specific reason, why this here is returning a String?
The other select-type prompts in dialoguer return usize as the position of the selected item(s) in the input array (select) or an array of the positions (multi_select) respectively. I was just starting to include the current state of this PR in my code and was expecting a usize, which confused me a little bit 😅 .

@deg0nz I was confused as well. Returning the index would coherent.
@SirWindfield If there are more items than free lines in the terminal, the line with the prompt and the search string is not displayed anymore and thus hard to see what was typed.

The second issue is a general issue with dialoguer and need to be fixed in a more abstract way.

what 's the status of this issue ? could it be merged to the master?

what 's the status of this issue ? could it be merged to the master?

examples/fuzzyselect.rs has dos file format, it should be unix.
src/prompts/fuzzy_select.rs has dos file format, it should be unix.

I will not continue to work on this PR. If someone wants to take over, feel free to do so!

I would like to take over. I just don't know how to contribute to this particular PR. I've never taken over a PR before.
@SirWindfield can you assign it to me somehow? Or should I do something?

You can make a new PR.
On Wed, Apr 7, 2021, 15:09 Beh @.***> wrote:

I would like to take over. I just don't know how to contribute to this
particular PR. I've never taken over a PR before.
@SirWindfield https://github.com/SirWindfield can you assign it to me
somehow? Or should I do something?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mitsuhiko/dialoguer/pull/79#issuecomment-814946201,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABKU37RDXBMIVUZBYYF2NTTHRRS5ANCNFSM4QMBO6QQ
.

I think I could try to make a new PR. but currently my fork is just get this PR merged, I need to look into @pksunkara 's review message carefully and make some change to the code, and then make a new PR.

Hey, @pksunkara
I started to apply your suggestions in my fork and came pretty far. Could you please answer the questions I add to your comments above and explain some more stuff?


[ENH] in Lag, make column naming consistent between single-lag and multi-lag case

Problem:
Lag outputs column names prefixed with "lag_x__" when using multiple lags. If a single lag is specified then the output column name is the same as the original column name (if the input is a pd.DataFrame rather than a pd.Series) without "lag_x__" prefixed to the original column name. It would be desirable for the output column names to be consistent, irrespective if a single lag or multiple lags is specified.
Fix implemented:
Lag now outputs the same column name irrespective of whether a single lag or multiple lags is specified.

The context which drove me to want to make a change was related to creating a pipeline of transformers. I have a pipeline where I want to apply the Lag transformer to different columns with different lags, in some cases I want to apply a single lag to a given column like so:
feat_eng_pipe = ColumnTransformer(
                  transformers=[
                    ('', 'passthrough', ['x1']),
                    ('lag_x2', Lag(lags=[3]), ['x2']),
                    ('lag_x3', Lag(lags=[1,2,3]), ['x3']),
                    ],
                  remainder='drop',
                  preserve_dataframe=True
                  )

The resulting dataframe from applying this pipeline will give different column names to lag variables created from x2 compared to x3. This inconsistency is troublesome because I will now have a dataframe where the lag variables of x3 are prefixed with lag_{}__ but the lag variable of x2 will just be called x2 which could be mistaken for just passing through x2. Note, in this example because no two transformers act on the same column we do not get the transformer names being prefixed to the output columns.

Re code:
If you want to remove the case distinction, I think it would be possible more easily, by just removing the "if" branch of the "if/else", and running only the "else" part?

Yes you're right! I've made the change and also added a unit test. It would be good to get your feedback on the unit test also if you think it looks a bit verbose.

This inconsistency is troublesome

I see, I'm convinced now - the inconsistency is a frustrated user expectation bordering on being a bug, in this case.

I've made the change and also added a unit test. It would be good to get your feedback on the unit test also if you think it looks a bit verbose.

The new test looks good to me.
Planning to approve/merge once/if the CI suite passes.

PS: since 0.13.1, you should be able to do sth like this:
feat_eng_pipe = Lag()['x1'] + Lag(lags=[3])['x2'] + Lag(lags=[1,2,3])['x3']

where the square brackets apply the transformer only to those variables, and the addition means feature union.
Optional passthrough is not yet a dunder, but was thinking of the tilde.

PS: since 0.13.1, you should be able to do sth like this:
feat_eng_pipe = Lag()['x1'] + Lag(lags=[3])['x2'] + Lag(lags=[1,2,3])['x3']

where the square brackets apply the transformer only to those variables, and the addition means feature union.
Optional passthrough is not yet a dunder, but was thinking of the tilde.

Thanks! Very cool! Will be using this in the future. Tilde sounds very reasonable. An alternative would be to implement an identity transformer if you wanted a more explicit, but more verbose, syntax.

Thanks! Very cool! Will be using this in the future. Tilde sounds very reasonable. An alternative would be to implement an identity transformer if you wanted a more explicit, but more verbose, syntax.

Say, what do you think of the variable naming that happens in this case? I think you get a double prefix with Lag, once for the transformer, once for the lag. That looks a bit odd.

Thanks! Very cool! Will be using this in the future. Tilde sounds very reasonable. An alternative would be to implement an identity transformer if you wanted a more explicit, but more verbose, syntax.

Say, what do you think of the variable naming that happens in this case? I think you get a double prefix with Lag, once for the transformer, once for the lag. That looks a bit odd.

Hi @fkiraly.
It's a tricky one. You get the double prefix in these cases:

Two or more transformers applied to a single column

data = pd.DataFrame(data={'x1':[1,2,3], 'x2':[1,2,3], 'x3':[1,2,3]})

feat_eng_pipe = ColumnTransformer(
                  transformers=[
                    ('', 'passthrough', ['x1']),
                    ('lag_foo', Lag(lags=[1]), ['x2']),
                    ('lag_bar', Lag(lags=[2]), ['x3', 'x2']),
                    ],
                  remainder='drop',
                  preserve_dataframe=True
                  )

feat_eng_pipe.fit_transform(data)

Resulting column names: ['__x1', 'lag_foo__lag_1__x2', 'lag_bar__lag_2__x3',        'lag_bar__lag_2__x2']

Using the alternative method of constructing a FeatureUnion mentioned above irrespective of whether a column is used by more than one transformer

data = pd.DataFrame(data={'x1':[1,2,3], 'x2':[1,2,3], 'x3':[1,2,3]})

feat_eng_pipe = Lag()['x1'] + Lag(lags=[1])['x2'] + Lag(lags=[2])[['x3']]

feat_eng_pipe.fit_transform(data)

Resulting column names: ['TransformerPipeline_1__lag_0__x1', 'TransformerPipeline_2__lag_1__x2',        'TransformerPipeline_3__lag_2__x3']
I'm not sure how you can make Lag stand alone and also work with pipelines in a way that the column names are simple in both.


wasm-terminal: Android keyboard blur, jumps terminal history to top

On blur, we should call this.xterm.scrollToBottom(). 😄

I don't believe this is relevant now that we've rewritten the package as @wasmer/sdk.


Cannot build<EMAIL_ADDRESS>on osx

Hi guys, i'm trying to use https://github.com/chloi/sightline package, but I got an error on npm install due to node-sass errors during the build.
I'm on OSX Yosemite(v10.10.2) using iojs-v1.3.0, here's the output:
><EMAIL_ADDRESS>install /Users/vruno/Documents/Urucas/Node/sightline/node_modules/harp/node_modules/terraform/node_modules/node-sass
> node build.js

child_process: customFds option is deprecated, use stdio instead.
child_process: customFds option is deprecated, use stdio instead.
  CXX(target) Release/obj.target/binding/binding.o
In file included from ../binding.cpp:1:
../node_modules/nan/nan.h:409:19: error: no type named 'ExternalAsciiStringResource' in 'v8::String'; did you mean 'ExternalStringResource'?
      v8::String::ExternalAsciiStringResource *resource) {
      ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
                  ExternalStringResource
/Users/vruno/.node-gyp/1.6.2/deps/v8/include/v8.h:2017:19: note: 'ExternalStringResource' declared here
  class V8_EXPORT ExternalStringResource
                  ^
In file included from ../binding.cpp:1:
../node_modules/nan/nan.h:408:36: error: redefinition of 'NanNew'
  NAN_INLINE v8::Local<v8::String> NanNew(
                                   ^
../node_modules/nan/nan.h:403:36: note: previous definition is here
  NAN_INLINE v8::Local<v8::String> NanNew(
                                   ^
../node_modules/nan/nan.h:1728:12: error: no member named 'IsExternalAscii' in 'v8::String'; did you mean 'IsExternal'?
  if (str->IsExternalAscii()) {
           ^~~~~~~~~~~~~~~
           IsExternal
/Users/vruno/.node-gyp/1.6.2/deps/v8/include/v8.h:1981:8: note: 'IsExternal' declared here
  bool IsExternal() const;
       ^
In file included from ../binding.cpp:1:
../node_modules/nan/nan.h:1729:23: error: no type named 'ExternalAsciiStringResource' in 'v8::String'; did you mean 'ExternalStringResource'?
    const v8::String::ExternalAsciiStringResource* ext;
          ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
                      ExternalStringResource
/Users/vruno/.node-gyp/1.6.2/deps/v8/include/v8.h:2017:19: note: 'ExternalStringResource' declared here
  class V8_EXPORT ExternalStringResource
                  ^
In file included from ../binding.cpp:1:
../node_modules/nan/nan.h:1730:16: error: no member named 'GetExternalAsciiStringResource' in 'v8::String'; did you mean 'GetExternalOneByteStringResource'?
    ext = str->GetExternalAsciiStringResource();
               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
               GetExternalOneByteStringResource
/Users/vruno/.node-gyp/1.6.2/deps/v8/include/v8.h:2084:40: note: 'GetExternalOneByteStringResource' declared here
  const ExternalOneByteStringResource* GetExternalOneByteStringResource() const;
                                       ^
In file included from ../binding.cpp:1:
../node_modules/nan/nan.h:1730:9: error: assigning to 'const v8::String::ExternalStringResource *' from incompatible type 'const v8::String::ExternalOneByteStringResource *'
    ext = str->GetExternalAsciiStringResource();
        ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/nan/nan.h:1731:11: error: assigning to 'const char *' from incompatible type 'const uint16_t *' (aka 'const unsigned short *')
    *data = ext->data();
          ^ ~~~~~~~~~~~
7 errors generated.
make: *** [Release/obj.target/binding/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:169:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1044:12)
gyp ERR! System Darwin 14.1.0
gyp ERR! command "/usr/local/bin/iojs" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/vruno/Documents/Urucas/Node/sightline/node_modules/harp/node_modules/terraform/node_modules/node-sass
gyp ERR! node -v v1.6.2
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
Build failed
npm ERR! Darwin 14.1.0
npm ERR! argv "/usr/local/bin/iojs" "/usr/local/bin/npm" "install"
npm ERR! node v1.6.2
npm ERR! npm  v2.7.1
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node build.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/vruno/Documents/Urucas/Node/sightline/npm-debug.log

Any ideas?

HI @vrunoa, node-sass prior to 3.0.0-beta doesn't support iojs since it was released long before iojs existed.
The 0.9.3 release is very old, and no longer supported. I would suggest to https://github.com/chloi/sightline that they update to 3.0.0.

Thanks for the info @xzyfer


GEODE-7463: make docLinks public

Provide structure for doclinks for better Swagger experience

Authored-by: Joris Melchior<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@onichols-pivotal @jinmeiliao @dschneider-pivotal @demery-pivotal

👍
Are GET /management/ and GET /management equivalent?

Yes, they are treated the same

👍
Are GET /management/ and GET /management equivalent?

Yes, they are treated the same

Please add tests for both forms, and both with and without security enabled.
When I tried a quick curl tests, they do not appear equivalent to me:
$ curl -s http://localhost:7070/management/
{"latest":"http://localhost:7070/management/v1/api-docs","supported":["http://localhost:7070/management/v1/api-docs"]}
$ curl -s http://localhost:7070/management
(no output)

+1
Are GET /management/ and GET /management equivalent?

Yes, they are treated the same

Please add tests for both forms, and both with and without security enabled.
When I tried a quick curl tests, they do not appear equivalent to me:
$ curl -s http://localhost:7070/management/
{"latest":"http://localhost:7070/management/v1/api-docs","supported":["http://localhost:7070/management/v1/api-docs"]}
$ curl -s http://localhost:7070/management
(no output)

I tried in the browser and there they behave the same. I'll experiment and will add tests accordingly.


integer | float for value suggested

Currently the data type for the suggested amount is inconsistent. for XSD both would fit in decimal.

int is mandatory for lightning, but there is a float in the example
float is mentioned in general and seems to be in use

I guess the integer lost due to common practice?

Agreed.  Will fix.


Add filter support for the DropdownList component

Implemented. Now the component has a property to control the functionality called [searchOnList].


Request: Add set bonuses to all gifts that are part of a set

There are a few gifts like Sanguine Desire and Da Capo that provide bonuses if wearing the corresponding weapon/armor, but it feels like a missed opportunity to not have all of the set gifts synergize in some way.
This will also be a good opportunity to verify that existing set bonuses work as expected for any potential bug fix additions.

There is a fair number of EGO in the game.  Making tailored set bonuses would take a fair bit of time, so I would like to propose a time-saving measure.
The idea is that if there are no pre-existing bonus script associated with a gift, the related weapons and EGO get a minor boost dependent on the abnormality's danger.  Armor can receive a 0.1 increase in resistance, and weapons +1 damage.  This means a Zayin gift set has +0.1 and +1, while a Aleph is +0.5 and +5 respectively.


nyc ts-node --project does not work on windows.

Expected Behavior
On my windows system when i try this
$(npm bin)/nyc --report-dir coverage/server $(npm bin)/ts-node --project server/tsconfig.json node_modules/jasmine/bin/jasmine.js 'server/**/!(*index).ts'

It should run tests for the code and report on coverage.
Observed Behavior
It throws the following output
C:\Program Files\nodejs\node.exe: bad option: --project
ERROR: Coverage for lines (0%) does not meet global threshold (90%)
ERROR: Coverage for functions (0%) does not meet global threshold (90%)
ERROR: Coverage for statements (0%) does not meet global threshold (90%)

Additional
The below code however workings fine.
$(npm bin)/ts-node --project server/tsconfig.json node_modules/jasmine/bin/jasmine.js 'server/**/!(*index).ts'

The .nycrc file looks like this
{
    "check-coverage": true,
    "lines": 90,
    "statements": 90,
    "functions": 90,
    "branches": 90,
    "all": true,
    "include": [
        "server"
    ],
    "exclude": [
        "**/index.ts",
        "**/tests/*.ts",
        "**/*.model.ts",
        "**/*.module.ts",
        "server/server.spec.ts"
    ],
    "reporter": [
        "html",
        "json",
        "text-summary"
    ],
    "extension": [
        ".ts"
    ]
}

Forensic Information
Operating System: Windows 10 on MINGW64
Environment Information:
https://gist.github.com/rupamroy/fb66b53010b7657e83dcc0a3fa0d1039

@rupamroy are you able to provide a link to the project that is having this issue?

No sorry i can't do that , This is within a corporate network and not open sourced project.

Hi Any update on this issue ?

@rupamroy haven't had a chance to spin up a Windows VM, please feel free to join our community slack if you want to try to recruit some folks to dig into this bug:
http://devtoolscommunity.herokuapp.com/
It would be helpful if you could provide a minimal failing reproduction in a toy repo ... doesn't need to be the proprietary codebase you use at work.

Well i found a solution and noting it down just in case anyone needs it.
This issue occurs in Git bash on windows the solution is to use a redirection operator < between the nyc and ts-node command
$(npm bin)/nyc --report-dir coverage/server < $(npm bin)/ts-node --project server/tsconfig.json node_modules/jasmine/bin/jasmine.js 'server/**/!(*index).ts'

But now even though the command are working well nyc seems to not honoring the tsconfig path provided in the --project parameter and i have no clue why nyc should be related to tsconfig in any way. Becoz now i am getting the error as if i am not passing the --project parameter. Or due to redirection operator < may be the parameter is not getting passed into the ts-node command, Not sure what is going on.

I have created a demo project https://github.com/rupamroy/test-nyc to show the issue. The issue happens only in windows , the README describes the problem and the command used.


Initial Helm-based installation

Create Helm charts for the installation of kepler-exporter

https://github.com/sustainable-computing-io/kepler-helm-chart


Add TeslaFi to latest

RE-CHECK!

jsonConfig looks good...

RE-CHECK!

RE-CHECK!

"xs" should specify a value of "12" at admin/jsonConfig.json/items/_StandardTab/_donate  ->  has to be 6, otherwise button is too big
I'm no friend of automated translations - so I don't use i18n

RE-CHECK!

Your TOO fast :-)
Size check has been disabled for divider an staticImage in the meantime. Checks are adjustes to results in real life. :-)
I18n is a warning only which will not be considered blocking.

:)  -  so all this 5 times 12 for dividers could be removed?.... -> next release ;)
... so must be fixed label isn't relevant anymore? Or do I have to change something?

Sorry, but due to travel / absence I will not able to do the review before ioBroker Meeting Solingen next weekend.

@hombach
First of all - THANK YOU for the time and effort you spend to maintain this adapter.
I would like to give some feedback based on my personal oppinion. @Apollon77 might have additional suggestions or even a different oppinion to one or the other statement. Please feel free to contact him if you cannot follow my suggestions or want to discuss some special aspects.

[ ] TeslaFi related to tibber?
Is teslafi related to tibber or is this loga a copy/paste error?
'pull of homes from Tibber-Server'

[ ] unused onMessage handler
onMessage handler has no obvious functionality. Please remove from code an config.

[ ] invalid characters should be filtered from object ids
Some characters are not allowed to be used as part of an object id. If an object id is not hardcoded or even depending on user input you should ensure that such an object id does not contain an invalid character.  Iobroker provides the constant adapter.FORBIDDEN_CHARS, i.e. by using the following snippet:

function name2id(pName) {
    return (pName || '').replace(adapter.FORBIDDEN_CHARS, '_');
}

[ ] avoid usage of setObject
setObject(Async) creates a new object whenever it is called. You should avoid using setObject unless you really want to create new objects. Creating a new object deletes any userConfig, i.e. configures history logging which is most likely not desired. Most likely either setObjectNotExists oder (even better in most cases) extendObject should be used. Extend Object ensures that attributes like role, read/write flag etc. are set as specified and hence extendObjet should be preferred when called once during startup of the adapter.

[ ] reevaluate state roles
Only the values specified here (https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md) may be used as state roles. Do not invent new names as this might disturb the functionality of other adapters or vis.
In addition the roles MUST match the read/write functionality. As an example a role value.* requires that the state is a readable state. Input states (write only) should have roles like level.*. Please read the description carefully. States with role 'button' should (must) have attribute 'common.read=false' set. A button ( "Taster" in german only triggers when you press but else has no state), so it should also be not readable. This is also like HomeMatic does it. A switch has clear states true or false and so can be read.
Please avoid using general roles (state, value) whenever a dedicated role exists.
One example: role 'value' must not be writeable.

[ ] Is there any reason to not use i18n translation environment?
I suggest to evaluate to use i18n translation environment and the iobroker/adapter-dev environment (https://github.com/ioBroker/adapter-dev#iobroker-adapter-dev). You could easyly add new strings to the english json and run npm run translate afterward. When using i18n environment activating iobrokers weblate translation system (see https://github.com/ioBrokerTranslator/doc) is trivial.

[ ] Add timeout to axios calls
All axios calls should have a timeout set. The default value for axios timeout is 0 which results in no timeout. So an unresponsive remote system could lead to an hanging adapter. Either set an appropiate timeout per axios call or set a default timeout globally for the axios instance.

[ ] consider using adapter.setTimeout / this.setTimeout instead of (standard) setTimeout
The adapter package provides wrapper routines for native setTimeout, setInterval, clearTimeout and clearInterval. Using those routines ensures that timers are cancelled on on load. Additional checks on thomse limits might be performed, too. So consider replacing native setTimeout/clearTimeout by adapter.setTimeout/adapter.clearTimeout or this.setTimeout/this.clearTimeout. The same refers to setInterval/clearInterval.

[ ] check and limit configurable timeouts / intervals
Node setTimeout/setInterval routines have a maximum allowed value of 2,147,483,647 ms. Using delays larger than 2,147,483,647 ms (about 24.8 days) result in the timeout being executed immediately. So all (user configurable) values passed to setTimeout / setInterval should be checked in code and limited. Checking/limiting in code is required as config data could be changed directly or by some other adapter too, so limiting at ui level might not be sufficient.

[ ] check and limit intervals used to access cloud services
Limit all intervals used to access cloud services to a reasonable value. If users configure an inapprobiate access rate this could lead to suspending the service by the provider for all ioBroker users.

[ ] linter setup
Please use standard iobroker linter setup. This is located at @iobroker/eslint-config. See migration guide at https://github.com/ioBroker/ioBroker.eslint-config/blob/main/MIGRATION.md

Thanks for reading and evaluating this suggestions.
McM1957
Please add a comment when you have reviewed and fixed the suggestions or at least commented the suggestions and you think the adapter is ready for a re-review!

TeslaFi related to tibber?
Is teslafi related to tibber or is this loga a copy/paste error?
-> yes, copy/paste error -> FIXED
unused onMessage handler
onMessage handler has no obvious functionality. Please remove from code an config.
-> REMOVED
invalid characters should be filtered from object ids
-> NO USER DRIVEN object ids used
avoid usage of setObject
-> NOT USED
PART 1 - more to follow

@mcm1957 Hi Martin, may I ask for a review this weekend... I'd need my fork of iobroker.repositories for my other adapters to get some things released... ;)

Will check if I have time tomorrow. But cannot promise.
But what*s the problem? You can release differnet adapters independently. Simply use ba seperate branch per Adapter. If you use www.iobroker.dev or edit dierectly at www.github.com a new branch and the corresponding PR will be created automatically.

REVIEW - WORK IN PROGRESS

[ ] TeslaFi related to tibber?
Is teslafi related to tibber or is this loga a copy/paste error?
'pull of homes from Tibber-Server'

[ ] unused onMessage handler
onMessage handler has no obvious functionality. Please remove from code an config.

[ ] invalid characters should be filtered from object ids
Some characters are not allowed to be used as part of an object id. If an object id is not hardcoded or even depending on user input you should ensure that such an object id does not contain an invalid character.  Iobroker provides the constant adapter.FORBIDDEN_CHARS, i.e. by using the following snippet:

function name2id(pName) {
    return (pName || '').replace(adapter.FORBIDDEN_CHARS, '_');
}

[ ] avoid usage of setObject
setObject(Async) creates a new object whenever it is called. You should avoid using setObject unless you really want to create new objects. Creating a new object deletes any userConfig, i.e. configures history logging which is most likely not desired. Most likely either setObjectNotExists oder (even better in most cases) extendObject should be used. Extend Object ensures that attributes like role, read/write flag etc. are set as specified and hence extendObjet should be preferred when called once during startup of the adapter.

[ ] reevaluate state roles
Only the values specified here (https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md) may be used as state roles. Do not invent new names as this might disturb the functionality of other adapters or vis.
In addition the roles MUST match the read/write functionality. As an example a role value.* requires that the state is a readable state. Input states (write only) should have roles like level.*. Please read the description carefully. States with role 'button' should (must) have attribute 'common.read=false' set. A button ( "Taster" in german only triggers when you press but else has no state), so it should also be not readable. This is also like HomeMatic does it. A switch has clear states true or false and so can be read.
Please avoid using general roles (state, value) whenever a dedicated role exists.
One example: role 'value' must not be writeable.

[ ] Is there any reason to not use i18n translation environment?
I suggest to evaluate to use i18n translation environment and the iobroker/adapter-dev environment (https://github.com/ioBroker/adapter-dev#iobroker-adapter-dev). You could easyly add new strings to the english json and run npm run translate afterward. When using i18n environment activating iobrokers weblate translation system (see https://github.com/ioBrokerTranslator/doc) is trivial.

[ ] Add timeout to axios calls
All axios calls should have a timeout set. The default value for axios timeout is 0 which results in no timeout. So an unresponsive remote system could lead to an hanging adapter. Either set an appropiate timeout per axios call or set a default timeout globally for the axios instance.

[ ] consider using adapter.setTimeout / this.setTimeout instead of (standard) setTimeout
The adapter package provides wrapper routines for native setTimeout, setInterval, clearTimeout and clearInterval. Using those routines ensures that timers are cancelled on on load. Additional checks on thomse limits might be performed, too. So consider replacing native setTimeout/clearTimeout by adapter.setTimeout/adapter.clearTimeout or this.setTimeout/this.clearTimeout. The same refers to setInterval/clearInterval.

[ ] check and limit configurable timeouts / intervals
Node setTimeout/setInterval routines have a maximum allowed value of 2,147,483,647 ms. Using delays larger than 2,147,483,647 ms (about 24.8 days) result in the timeout being executed immediately. So all (user configurable) values passed to setTimeout / setInterval should be checked in code and limited. Checking/limiting in code is required as config data could be changed directly or by some other adapter too, so limiting at ui level might not be sufficient.

[ ] check and limit intervals used to access cloud services
Limit all intervals used to access cloud services to a reasonable value. If users configure an inapprobiate access rate this could lead to suspending the service by the provider for all ioBroker users.

[ ] linter setup
Please use standard iobroker linter setup. This is located at @iobroker/eslint-config. See migration guide at https://github.com/ioBroker/ioBroker.eslint-config/blob/main/MIGRATION.md

Thanks for fixing most issues, The following issues still need attention:

[ ] avoid usage of setObject

setObject(Async) creates a new object whenever it is called. You should avoid using setObject unless you really want to create new objects. Creating a new object deletes any userConfig, i.e. configures history logging which is most likely not desired. Most likely either setObjectNotExists oder (even better in most cases) extendObject should be used. Extend Object ensures that attributes like role, read/write flag etc. are set as specified and hence extendObjet should be preferred when called once during startup of the adapter.
You are using setObject i.e. here:
https://github.com/hombach/ioBroker.teslafi/blob/60b533418f207cdfa9fd88a7d8c46ce3b2e82aa8/src/lib/projectUtils.ts#L179
Wouldn't it be sufficient to use extendObject? setObject will delete the old object and hence delete all user defined attribute, i.e. setting for history adapter.

[ ] reevaluate state roles

Only the values specified here (https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md) may be used as state roles. Do not invent new names as this might disturb the functionality of other adapters or vis.
In addition the roles MUST match the read/write functionality. As an example a role value.* requires that the state is a readable state. Input states (write only) should have roles like level.*. Please read the description carefully. States with role 'button' should (must) have attribute 'common.read=false' set. A button ( "Taster" in german only triggers when you press but else has no state), so it should also be not readable. This is also like HomeMatic does it. A switch has clear states true or false and so can be read.
Please avoid using general roles (state, value) whenever a dedicated role exists.
role 'value' must not be writeable.
https://github.com/hombach/ioBroker.teslafi/blob/60b533418f207cdfa9fd88a7d8c46ce3b2e82aa8/src/lib/projectUtils.ts#L218
role 'indicator' must not be writeable.
https://github.com/hombach/ioBroker.teslafi/blob/60b533418f207cdfa9fd88a7d8c46ce3b2e82aa8/src/lib/projectUtils.ts#L269

[ ] consider using adapter.setTimeout / this.setTimeout instead of (standard) setTimeout

The adapter package provides wrapper routines for native setTimeout, setInterval, clearTimeout and clearInterval. Using those routines ensures that timers are cancelled on on load. Additional checks on thomse limits might be performed, too. So consider replacing native setTimeout/clearTimeout by adapter.setTimeout/adapter.clearTimeout or this.setTimeout/this.clearTimeout. The same refers to setInterval/clearInterval.
You're using setInterval here
https://github.com/hombach/ioBroker.teslafi/blob/60b533418f207cdfa9fd88a7d8c46ce3b2e82aa8/src/main.ts#L71
check and limit intervals used to access cloud services

[ ] Limit all intervals used to access cloud services to a reasonable value. If users configure an inapprobiate access rate this could lead to suspending the service by the provider for all ioBroker users.
Please add a suitable lower limit too:
https://github.com/hombach/ioBroker.teslafi/blob/60b533418f207cdfa9fd88a7d8c46ce3b2e82aa8/src/main.ts#L71

-> avoid usage of setObject
This is only used for adapter setup.... you have to read the total code - automatic scanning for key words dosn't work this time....
				if (!forceMode) { 					await this.adapter.setObjectNotExistsAsync(stateName, { 						type: "state", 						common: commonObj, 						native: {}, 					}); 				} else { 					await this.adapter.setObjectAsync(stateName, { 						type: "state", 						common: commonObj, 						native: {}, 					}); 				}
projectUtils.ts is a helper class I'm using in most adapters
-> reevaluate state roles
same, projectUtils.ts is a helper class I'm using in most adapters. The fact it's able to set up writable states doesn't tell it's used in the adapter. IUpo to now, all states are read only, as they are just states polled from the car. They have special background for the car but most of them no dedicated type in ioBroker. So I would prefer generall roles.
-> consider using adapter.setTimeout / this.setTimeout instead of (standard) setTimeout
WiP
-> Limit all intervals used to access cloud services
allready done .... jsonConfiig.json:
				"UpdateInterval": { 					"type": "number", 					"label": "LBL_UpdateInterval", 					"hidden": "!data.TeslaFiAPIToken", 					"min": 10, 					"max": 86400, 					"step": 1,

DONE

-> avoid usage of setObject
Well extendObject would be the better solution anyway in my oppinion. But finally it's your decision as using setObject is strongly discouraged but not forbidden. So its non blocking.
-> reevaluate state roles
The mentioned roles must not be used with writeable statesat any time. So there is no need to allow the code to set writeable to true. I do not see why code creating incorrect states should be present. Please remove writeable option or pass role as parameter setting it correctly. As you use this code at several apaters the fix shpould be applied everywhere to avoid incorrect states.

Hi Martin, adding the role as optional parameter in case of setting up writeable states is a good idea... implemented in 0.4.4.

added a few more precise state roles in 0.4.5

@hombach
This adapter has been released to latest repository and should be visible within 24h maximum.
Please create a thread at https://forum.iobroker.net/category/91/tester titled like "Test Adapter " to collect some user feedback and provide a link to this topic when requesting addition to stable repository later.
Note: If an other testing topic already exists, it' OK to continue using this topic too.

Hi Martin, kann gerne was posten - darf man aber ja in der Catagory nicht.

Als dev darfst du es.
Bitte ping HOMORAN via PN / Chat an dass er dich freischaltet


Issues running Colab

Hi! I wanted to try out the SLAHMR project on my own video and was trying to run the provided Colab notebook.
However, I've been running into an issue on the "run on demo video" block ("AttributeError: 'Namespace' object has no attribute 'vis'"). I've been trying workarounds including using more absolute paths and manipulating arguments but I haven't had luck in bypassing this just yet.
Does anyone know how to get around this? Thanks!

I tried it again and it seems to be working without issues for me.
Is it possible that you are using an older version of the code? At some point, a small change broke the preprocessing script (giving an error that was very similar to the one you are reporting). But this should be fixed now if you pull the latest version of the code.

You're right, it was an issue with some of the older code. Thank you!


Segfault on HEAD with endwise enabled.

nvim-treesitter-endwise is causing a segfault using Neovim @ HEAD. See: https://github.com/neovim/neovim/issues/18079 for the details.

Can nvim_get_mode() be used in this plugin instead of FFI?

API functions cannot be used, see https://github.com/RRethy/nvim-treesitter-endwise/blob/f653101e056cebcee71b47b8adb93d3a878cda36/lua/nvim-treesitter/endwise.lua#L196-L203. The FFI call was to fix https://github.com/RRethy/nvim-treesitter-endwise/issues/9.
I see that the signature of get_mode has changed which is unfortunate. I'll have to think about how to go about fixing this.


[uni-algo] Add new port

Fixes #29716

[x] Changes comply with the maintainer guide
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[x] Only one version is added to each modified port's versions file.

Tested on:
Windows MSVC 19.16 (triplets: x86-windows, x64-windows, x64-windows-release)
Windows MinGW GCC 12.1 (triplets: x64-mingw-static, x64-mingw-dynamic)
Linux GCC 12.2 (triplets: x64-linux, x64-linux-dynamic, x64-linux-release)
Tested in both classic and manifest modes of vcpkg.
Everything seems to be fine.

@microsoft-github-policy-service agree

/azp run

/azp run


Failed to find a default file in the app artifacts folder (.next) for Hybrid next.js deployment to Azure Static App from Azure Pipelines

Describe the bug
I am getting the following error when trying to deploy a SSR-supported next.js application to Azure Static App from Azure Pipelines

The structure of the project is very straight forward , the package.json file is on the root folder, the .next folder gets generated under the root folder as well , the folders inside the root look like the image below, please notice that the pages folder sits under /src/pages:

I added a buildAz task, so to create an empty node_modules under the generated .next folder after the build, following the approach detailed on this thread, but the issue seems unrelated:
This is how the azure pipelines looks like:

Expected behavior
Being able to deploy to Azure Static Web apps our existing next.js project without losing the SSR capabilities of next.js as it is now supported  https://aka.ms/swa-nextjs-ssr-blog

@camila-akqa Thanks for sharing the logs and package.json.
As you don't want the html export feature of the NextJS, can you please remove the && next export from the build command in your package.json and try again.
Please let me know if it helps. Thanks!

Hi @vivekjilla
Thanks again for looking into this. I am already doing that, so in Az Pipelines I've these field:
app_build_command: 'yarn **buildAz**'
is_static_export: false
api_location: ""
output_location: ""

and In the package.json I've defined a task that looks like next:
"buildAz": "cross-env IGNORE_TYPESCRIPT_ERRORS=true next build --no-lint",
Please notice that I tried deploying the same project as static, eg. including "&& next export" in the build command and with the following fields in Azure pipelines , and the site is deployed correctly:
is_static_export: true
api_location: ""
output_location: "out"

I've made some changes since the last time I posted last message (eg. reducing the size of the node_modules) , so I can reattach the logs if needed.
Really appreciate all help you can provide! thanks.
Camila

Oh @vivekjilla
I actually changed had this 2 tasks on my package.json
 "build": "yarn generate && cross-env IGNORE_TYPESCRIPT_ERRORS=true next build --no-lint && next export",
    "buildAz": "yarn generate && cross-env IGNORE_TYPESCRIPT_ERRORS=true next build --no-lint",

After your previous comment I anyway changed to be
"build": "cross-env IGNORE_TYPESCRIPT_ERRORS=true next build --no-lint",
    "buildStatic": "yarn generate && cross-env IGNORE_TYPESCRIPT_ERRORS=true next build --no-lint && next export",

And updated the pipeline to use yarn build instead of yarn buildAz, eg:
app_build_command: 'yarn build'
And it is now working!!!!!!!
Thanks a lot for your help!!


Local kolla container image builds

Sync all repositories to local Pulp

Don't forget to add the following to etc/kayobe/containers/pulp/settings.py:
ALLOWED_CONTENT_CHECKSUMS = ["sha1", "sha224", "sha256", "sha384", "sha512"]

@m-bull Do you consider this ready for review now?


Dragging floating windows is stuttery.

Hyprland Version
Hyprland, built from branch main at commit c34ad12183506cb5f52bfb65b44e3a274e996fc3 dirty (cursormgr: scale hotspot with buffer).
Date: Mon Mar 18 00:30:21 2024
Tag: v0.37.1-10-gc34ad121
flags: (if any)
System Information:
System name: Linux
Node name: asus
Release: 6.8.1-zen1-1-zen
Version: #1 ZEN SMP PREEMPT_DYNAMIC Sat, 16 Mar 2024 17:15:23 +0000
GPU information:
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller])
0000:01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) (prog-if 00 [VGA controller])
os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo
plugins:
Bug or Regression?
Bug
Description
core i9-11900h rtx 3050 laptop.
120hz screen.
Animations look smooth in 120hz than 60hz as expected but dragging a floating windows looks same in 60hz and 120hz.
Other DEs dont have this problem.
How to reproduce
Drag a floating windows in 120hz and 60hz using
monitor=eDP-1,1920x1200@60,0x0,1
monitor=eDP-1,1920x1200@120,0x0,1
Crash reports, logs, images, videos
No response

well I am on 240hz and can not reproduce this.

well I am on 240hz and can not reproduce this.

well I am on 240hz and can not reproduce this.

could you give me any idea how can i solve this? I'm a linux beginner since a few weeks.

I have no idea because you seem to be the only one with this issue.

I have no idea because you seem to be the only one with this issue.

I think #4553 is related to my issue.

I have no idea because you seem to be the only one with this issue.

I can confirm the video provided in #4669 is exactly the case with me , but seeming the bug is fixed,not in my case.

Update:
I installed hyprland 0.34.0 and now floating windows feel buttery smooth. I hope this bug get fixed as soon as possible.

I don't think that one does anything for monitors that aren't 60hz.

here we go again
what's your package manager for -git version?


Fixing Issue #68

Update DefaultToastLayoutRenderer
Adding some code to move the view just under the StatusBar.

Can we please get this merged and into a new nuget release?

@swansca79 - apologies on the delay. After testing this (quite a while ago), while it fixes AppCompat it breaks the standard implementation. Hence I need to merge this, then add more code to accommodate people who haven't upgraded to AppCompat.


Add libmlx* CDTs

Includes libmlx4 and libmlx5 CDTs.
Please see the repo readme for directions on how to make PRs on this repo.
Checklist:

[x] if you have added a CDT, it appears in the cdt_slugs.yaml file and
you have rerun the script python gen_cdt_recipes.py.
[ ] if you have changed the CDT generator code (rpm.py), you have bumped
the build number in conda_build_config.yaml and have remade all of the
recipes via running python gen_cdt_recipes.py --force
[ ] if you have added a custom CDT recipe, you have added the name of the CDT
with custom: true in the cdt_slugs.yaml file.
[ ] all CDT recipes have build number set by {{ cdt_build_number }} for
old-style/legacy CDTs or {{ cdt_build_number|int + 1000 }} for new-style CDTs
[ ] if you see a warning about a CDT not having a license, you have added the
license_file key in the cdt_slugs.yaml file with the path to the appropriate
license in licenses/

NOTE: If you make any changes to cd_slugs.yaml, you need to reun the generator code
via python gen_cdt_recipes.py. Add the --fast option to make this go more quickly.

This wound up touching and adding way more CDTs than I would have naively expected. Maybe I'm doing something wrong? 😬

Your machine is still not generating the CDTs properly. Can you send me the full output of the command you ran? Are there any errors?

Yeah I'm not sure I understand why though (or how to fix it). My best guess is requirements might be missing ( https://github.com/conda-forge/cdt-builds/issues/32 ), but I honestly don't know 🤷♂ Happy to make changes 🙂
Just running python gen_cdt_recipes.py. Am using condaforge/linux-anvil-comp7 with the directory passed through (as this doesn't run on macOS).
There's a ton of output. Have attached as a text file.

Installed the requirements noted here and reran. It seems to have done a bit better. Not sure if we are still missing things though. Please let me know 🙂

This will run on OS X. Install the requirements I sent.
I think I might have missed a key detail. Run the script over and over again until all of the warnings or errors go away. It very often hits a race condition.

Do you need these on cos7? As far as I can tell, there are no RPMs for them on cos7.


Create 0000-01-02-acebunny00.md

created a branch, created a file and made a commit, and opened a pull request

created a branch, created a file and made a commit, and opened a pull request


how to evaluate the result?

Hello,
I have trained the model, but I don't know how to visualize the testing results just like the 'readme' shows. I'm new to it, thanks for any help!

File "unet.py", line 43, in
FLAGS = tf.flags.FLAGS
AttributeError: module 'tensorflow' has no attribute 'flags'
i m getting this error. How you solved it? Thanks

@yongshuo-Z
Hi,  you can get the result in readme by tensorboard. I save the curves and some segmentation results during the training in tensorboard summary. But I haven't implemented the code to get all the evaluation images.

@manvirvirk
Maybe you are using a newer version of TF, like tf 2.0. The 'tf.flags' has been abandoned in tf2. You can use tf1 or search the alternatives in tf2.


Bump carbon identity framwork version to 5.20.368

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2146657687

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2146657687
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2147510468

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2147510468
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2148608963

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2148608963
Status: success


Compatibily of bundled file syntax  with web browsers

Hi !
I try to use a biojs module in a new component and I use webpack to bundle modules. When I use the bundled file in a html file , I obtain these error messages :
« SyntaxError: class is a reserved identifier »  in the bundle file with  mozilla firefox 44.0
« Uncaught SyntaxError: Unexpected token [ » in the bundle file with google chrome 48.0.2564.116
My understanding is that the syntax use in the bundled file is not supported by web browsers.
Is it  possible to modified the syntax use for write the bundled file ?
My system is Ubuntu 15.04.
Thank you in advance.

@maudema it sounds like you aren't preprocessing with Babel. Class is an ES2015 feature that needs to be transpiled to ES5. Are you using React?

I had not use React . It would seem that the problem took from one of my dependencies.
The issue is resolved now.
Thank you for your answer.


Missing Button loading state in Figma

Button has a built in loading state, but there is no sketches for it in Figma? :)

I have created and tested an animated spinner for the button's loading state in Figma.
What has been done:

[ ] Animated the spinner for the button's loading state.
[ ] Designed the animated spinner for all button sizes (small, medium, large) and states (default, hover, active, disabled).
[ ] Tested across all states (default, hover, active, disabled) and sizes to ensure consistent behavior and appearance.
[ ] Created examples in Designsystemet Core UI Kit

I'm not sure if having multiple lines in a button is considered a good UX practice. But I would like to know what you think about the placement of the spinner: should it be centered in the middle of the button, as shown in the image, or placed next to the first line of text when the button contains two lines? @mrosvik & @Febakke

In Storybook it looks like the icon and the loader is centered. I think we should keep it this way, since the padding above text is very small, and the loader will not be aligned with the first line of text.

I have implemented a spinner that supports all colors, utilizing the same 'sub-tokens' for consistency across different colors.
Background: color.<variable>.surface-default
Stroke: color.<variable>.border-default

Skal spinner være synlig på hover? Vi har satt opp prototypingsoppførsel på button komponenten og ser ut til å ikke fungere så bra med spinner. Det gir kanskje ikke mening at en knapp med loader får hover?
Alternativer:

Legg til spinner på alle states?
La være as is, vil se litt buggy ut i prototyper
Lagg spinner button som egen variant hvor den ikke er koblet til hover med prototyping

Vi går for alternativ 2: La være as is, vil se litt buggy ut i prototyper. Vi kan evt. utbedre dette senere ved behov.


[Feature request] Provide API to set custom ClassInstanceManager

[Feature request] Provide API to set custom ClassInstanceManager.
This is needed for proper integration with IoC frameworks (Spring, Guice, Dagger, PicoContainer, etc...)
Also described here #49

@mdolinin You can use ClassInstanceManager.setClassInitializer() for this. Here's an example usage.

@kashishm But i couldn't control Hooks instances.
Second when i run in parallel mode. This solution will create new Spring context for each thread.
But what if we want to use one context for all tests, and share some objects.

But i couldn't control Hooks instances.

I am not sure if I understand this. Can you please elaborate?

Second when i run in parallel mode. This solution will create new Spring context for each thread.
But what if we want to use one context for all tests, and share some objects.

In multi process parallel execution, creating new Spring context for each process is required and in multi thread parallel execution you can use singleton ClassInitializer instance and use it in ClassInstanceManager.setClassInitializer() for every thread.

Since issue #49 is closed, this issue should be closed as well

Duplicate of #49.


Use arro3 for dictionary encoding

Available PR templates

Default
Version Release
Alternatively delete and start empty

With https://github.com/kylebarron/arro3/pull/159 I should be able to update and merge this


Long running regression test suite

What type of enhancement is this?
Other
What does the enhancement do?
As GreptimeDB is releasing weekly builds, we may need some regression test suite that runs continuously 24x7 to check if any recent change breaks the major functionalities.
We shall first start with data integrity tests that insert random rows of data into GreptimeDB and checks whether:

row num counted matches rows inserted;
simple SQL queries return correct results, like min/max/point queries/group by queries;
deleting table rows reclaims disk space;
any degradation in performance happens;
...

The regression test suite may evolve to a chao test suite in the future.
Implementation challenges
No response

Longevity testing: https://github.com/scylladb/scylla-longevity-tests


Apply php-cs-fixer

Apply php-cs-fixer settings as for doctrine1 and symfony1 repositories

Can I take this?

Sure, go on! :+1:
pipelines are not successful, we should have a look at it too by removing the unsupported php versions

Closed by #4


Force is-ip v4.0.0

Motivation
See #4689
Description
Until we fix things upstream, force v4.0.0

I think this doesn't work :(


Remove generated files from source control

This PR https://github.com/cloudevents/sdk-javascript/pull/140 introduced 21,838 lines of mostly HTML/non-Cloud SDK code into master.
It introduces files not related to this repo:
https://github.com/cloudevents/sdk-javascript/tree/master/docs/fonts
For example, these files were not hand-written and aren't expected to be added to source control:

@lance can we use gh-pages instead for this or somehow not include these files in master? This is common for most projects and will keep PRs slim. Or let's just use md files rather than HTML files.

A docs/ folder is simply not very node-like.
Feel free to look at the way any of the top npm packages document their modules for comparison:
https://www.npmjs.com/browse/depended

This was fixed in https://github.com/cloudevents/sdk-javascript/pull/194.


DOM Exception in angular 8 Drag and Drop CDK

Bug, feature request, or proposal:
My Bug is  Unhandled Promise rejection: Failed to execute 'appendChild' on 'Node': The new child element contains the parent. ; Zone: <root> ; Task: Promise.then ; Value: DOMException: Failed to execute 'appendChild' on 'Node': The new child element contains the parent.
What is the expected behavior?
I need to drag a simple box and drop it another dropbox
What is the current behavior?
My current application is not working as expected. I can drag the box and drop it in dropzone. But I'm getting an error after dropping the box and my application stops working thereafter.
What are the steps to reproduce?
I have created stackblitz to reproduce my issue.
https://stackblitz.com/edit/angular-ebfpvj
Drag the blue box and drop it in the second box.
Open the console to check the issue after dropping the dragged box.
Versions of Angular, Material, OS, TypeScript, browsers are affected?
My package.json file
{   "name": "canvas-poc",   "version": "0.0.0",   "scripts": {     "ng": "ng",     "start": "ng serve",     "build": "ng build",     "test": "ng test",     "lint": "ng lint",     "e2e": "ng e2e"   },   "private": true,   "dependencies": {     "@angular/animations": "~8.1.0",     "@angular/cdk": "^8.2.3",     "@angular/common": "~8.1.0",     "@angular/compiler": "~8.1.0",     "@angular/core": "~8.1.0",     "@angular/forms": "~8.1.0",     "@angular/platform-browser": "~8.1.0",     "@angular/platform-browser-dynamic": "~8.1.0",     "@angular/router": "~8.1.0",     "rxjs": "~6.4.0",     "tslib": "^1.9.0",     "zone.js": "~0.9.1"   },   "devDependencies": {     "@angular-devkit/build-angular": "~0.801.0",     "@angular/cli": "~8.1.0",     "@angular/compiler-cli": "~8.1.0",     "@angular/language-service": "~8.1.0",     "@types/node": "~8.9.4",     "@types/jasmine": "~3.3.8",     "@types/jasminewd2": "~2.0.3",     "codelyzer": "^5.0.0",     "jasmine-core": "~3.4.0",     "jasmine-spec-reporter": "~4.2.1",     "karma": "~4.1.0",     "karma-chrome-launcher": "~2.2.0",     "karma-coverage-istanbul-reporter": "~2.0.1",     "karma-jasmine": "~2.0.1",     "karma-jasmine-html-reporter": "^1.4.0",     "protractor": "~5.4.0",     "ts-node": "~7.0.0",     "tslint": "~5.15.0",     "typescript": "~3.4.3"   } }

The error is most-likely because you have cdkDropList [cdkDropListConnectedTo]="[dropZone]" on the inner box. This means that you're trying to connect the drag item itself to the opposite drop zone. Is this what you intended or was the drop list supposed to be on the outer box?

Closing since there hasn't been any new information in a while.


Feedback regarding lesson: Sumtcita

Please provide your feedback here...
In lesson 11 of the lojban course, one thing wasn't very clear for me, but I ended up grasping it after consulting The Incomplete Lojban Language.
9.5. Modal places: FIhO, FEhU (https://lojban.pw/cll/uncll-1.2.7/xhtml_section_chunks/section-selbri-modals.html)
"mi viska do fi'o kanla [fe'u] le zunle
It is important to remember that even though le zunle is placed following fi'o kanla, semantically it belongs in the x1 place of kanla. [...] Modal sumti [...] may not be marked with FA cmavo."
In my opinion, It should be explained in the lesson that only selbri can go into fi'o...fe'u. There's one example that was probably wrong, and it made me believe sumti could be placed inside fi'o...fe'u. This is the example:
fi'o gasnu do {fe'u} mi vecnu lo skami
I pasted the sentence into a parser, and the parser couldn't tell me the structure of the sentence. When I placed fe'u after gasnu it gave me a positive result.
It should also say in the lesson that what comes after fi'o SELBRI fe'u is the x1 of SELBRI.
Example: fi'o[opening] mukti[selbri] {fe'u}[closing] ma[x1] (Or something like that.)
Not saying this, will make people think they should place fa before the sumti.
It actually says that what comes after fi'o SELBRI fe'u is the x1 of SELBRI, but it does that in other words: "This sumtcita then absorbs the next sumti." and "A sumtcita can only absorb one sumti, which is always the following one." which isn't very clear for me (I don't know about other learners).
One more thing.
When I click in the contact button at the bottom of the page, nothing happens.
You guys are doing a great job. I had actually given up on lojban a long time ago, but your website sparkled a fire in me and motivated me to come back. I'm still a beginner, but hopefully one day I'll be able to help. Thank you!
Context
For context, this feedback refers to the lesson "Sumtcita" in the course "Getting started with Lojban (alpha)".

(Accidentally closed.)

(Accidentally closed.)

Thank you very much for the detailed feedback, it is really appreciated!
That example was indeed incorrect, it should have been "fi'o gasnu {fe'u} do mi vecnu lo skami". I fixed this example, and also made some changes to make the lesson clearer (they will be live in 10min or so). The previous version was indeed quite confusing. Please let me know if you think they helped, and also if there is anything that could be further clarified.
Thanks again!

Thank you very much for the detailed feedback, it is really appreciated!
That example was indeed incorrect, it should have been "fi'o gasnu {fe'u} do mi vecnu lo skami". I fixed this example, and also made some changes to make the lesson clearer (they will be live in 10min or so). The previous version was indeed quite confusing. Please let me know if you think they helped, and also if there is anything that could be further clarified.
Thanks again!

I liked the new version. Thank you!

I liked the new version. Thank you!


Unable to create F# projects in VSCode

Hello,
I have the latest version of VScode and ionide. When I create a new F# project in an empty folder using the command palette using I get the "Project created" message but no project gets created.
I expect it to just create a project.
Environment

OS: Windows 10
Ionide version: 4.0.6
VSCode version: 1.38.0 (User setup)
dotnet SDK version: 2.2.401
.Net Framework version: .Net Framework 4.8

Here is the Forge log:
C:\Users\USERNAME\.vscode\extensions\ionide.ionide-fsharp-4.0.6\bin_forge\Forge.dll new project -n test -t classlib --folder ""  --no-prompt No executable found matching command "dotnet-C:\Users\USERNAME"

After the latest update to F# and .Net I'm getting this message:
Could not execute because the specified command or file was not found.
Possible reasons for this include:

You misspelled a built-in dotnet command.
You intended to execute a .NET Core program, but dotnet-C:\Users\Moe does not exist.
You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.

I have a similar problem on Mac OS, I go "View / Command Palette / F#: New Project (Project Scaffold)" and I get the error "Creating Project Failed - Directory is not empty" It occurs whether or not I have a folder open, and in the case that the folder is open, the directory is indeed empty.
I can create a .fsx file and write some F# code and, for example, use ALT-Enter to run it, however the tool-tips do not work either.
Ionide 4.2.0

Version: 1.39.2
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:33:00.827Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.6.0

FYI @MudiLoodi I think the general issue you're seeing is more of a docs problem than anything else, since we still suggested doing things in an older way (that was a lot more fragile!).
https://github.com/dotnet/docs/pull/15851 should probably make all of that go away


Remove/Insert row data complications.

go to: http://handsontable.github.io/handsontable-ruleJS/

Delete row no 5
Open contextMenu at 5 row and choose 'insert row above'

result: 2 rows added:

one empty
one with formulas in B6 and C6 copied from line 5 before removing it and changed for bigger range of cells.

this is caused by the issue I raised in #26, but no response yet to that


Kafka integration testing using Docker

[Current coverage][cc-pull] is 19.98% (diff: 100%)

Merging [#177][cc-pull] into [master][cc-base-branch] will decrease coverage by 27.55%

@@             master       #177   diff @@
==========================================
  Files            72         72
  Lines          4474       4474
  Methods           0          0
  Messages          0          0
  Branches        523        523
==========================================
- Hits           2127        894   -1233
- Misses         2266       3542   +1276
+ Partials         81         38     -43

Powered by Codecov. Last update [123f4ee...524be23][cc-compare]
[cc-base-branch]: https://codecov.io/gh/scrapinghub/frontera/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/scrapinghub/frontera/compare/123f4ee1cb026dea8221e6b0d9f5e0fa8c92f9a8...524be23a894d4adcb415a2b3d41b77f91651451f?src=pr
[cc-pull]: https://codecov.io/gh/scrapinghub/frontera/pull/177?src=pr

@Preetwinder any thoughts why it reports decrease of code coverage?

Isn't it showing 2.32% increase?

Now it shows increase... weird


Get packaging module from setuptools

Fixes #189.
packaging is apparently not a built-in and results in build failures if it's not installed in the user's environment. pkg_resources is also not built-in but it's vendored into setuptools so it's safe to use during build as well as RT.

/te-ci


preLaunchTask is never run when using vscode-edge-devtools.debug

Environment (please complete the following information):

OS (e.g., Windows 10): MacOS 11.6.2
Extension version (e.g., 1.2.3): 1.4.2

Describe the bug:

When using the vscode-edge-devtools.debug type in a configuration in launch.json, the preLaunchTask is never actually executed, and the Edge debugger opens right away without running anything first. This repros with npm and shell tasks (defined in tasks.json). The behavior is fixed by using pwa-msedge instead.
Repro steps:

Create a task in .vscode/tasks.json
Add a preLaunchTask property into a vscode-edge-devtools.debug launch configuration in .vscode/launch.json referencing the task label
Run the debug config

Expected behavior:

The specific preLaunchTask should run before the Edge debugger extension. It doesn't.
Additional context:

Related to #501

Thanks for flagging that up, we'll look into it.

same here

I can verify that I also have experienced this issue. You can use compound launch configurations to kind of get around it, but it's not something I'd rely on.

same here


Laravel 5.4 Support

When using on L5.4 I'm getting the following error on BootFormsServiceProvider@53:
Call to undefined method Illuminate\Session\Store::getToken()

As the L5.4 upgrade guide states, all calls to getToken() should be changed to token(). Other than that, everything looks fine.
@adamwathan do you think that something else should be necessary?

+1
Can we get django23's pull request merged?

Merged.


Creating a Navbar

Is your feature request related to a problem? Please describe.
Website navigation issues
Describe the solution you'd like
A side navbar should be introduced which has all the section titles and which navigates the user to the respective section.. this would be very much user friendly and also a hamburger type navbar should be made as a alternative for this in this mobile website
Describe alternatives you've considered
None
Additional context

I would like to take this issue. Kindly assign me .

@EshanTrivedi21 Request you yo assign it to me, I would like to work on this issue.

Thank you

what's the progress @Aishaa-26

Yes... working on it....will send within two hours.
On Wed, 19 Oct, 2022, 2:17 pm Eshan Kalp Trivedi, @.***>
wrote:

what's the progress @Aishaa-26 https://github.com/Aishaa-26
—
Reply to this email directly, view it on GitHub
https://github.com/EshanTrivedi21/Git-CheatSheet/issues/88#issuecomment-1283649937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW2QR3GYVXVXHTQLB3NQ5KLWD6YQ7ANCNFSM6AAAAAARHYTUVA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes... working on it....will send within two hours.
On Wed, 19 Oct, 2022, 2:17 pm Eshan Kalp Trivedi, @.***>
wrote:

what's the progress @Aishaa-26 https://github.com/Aishaa-26
—
Reply to this email directly, view it on GitHub
https://github.com/EshanTrivedi21/Git-CheatSheet/issues/88#issuecomment-1283649937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW2QR3GYVXVXHTQLB3NQ5KLWD6YQ7ANCNFSM6AAAAAARHYTUVA
.
You are receiving this because you were mentioned.Message ID:
@.***>

great

You can go on with that buddy, already assigned you the task! @Gopal2021025

Whats the progress @Aishaa-26 @Gopal2021025 ?


feat: 🎸 rename the discussion title to be clearer

reference: https://huggingface.slack.com/archives/C04L6P8KNQ5/p1696502639784009 (internal)

it wont cause issues to find back existing discussions? (to know where you're posting new comments on)

no, we find it by author, not by the title


Tests for current VMI tools

Unit tests for recording the current behavior of abel.tools.vmi, such that future corrections (see #312) can maintain backward compatibility or detect where and how it is broken.
The file abel/tests/test_tools.py, which contained a mix of very superficial tests of VMI and centering tools, is deleted: the imporoved VMI tests are moved to abel/tests/test_tools_vmi.py, and these centering tests, already covered by abel/tests/test_tools_center.py, are simply removed.

@DanHickstein and @stggh, something strange happens with GitHub (or on my side): I cannot add any reviewers (neither labels, although can assign myself). Could you please add yourself or each other as a reviewer to this PR? Just to check.

Huh, you have "Admin" access to the repository, so that should let you do anything you want on the webpage as far as I understand.

I know, and it all worked fine before... Perhaps, GitHub again broke something in “old” (~1 year old) browsers. :–/

You're going to have to upgrade from Netscape Navigator sometime... :)

If nobody objects, I'm going to merge this and move on to adding the new functions...

Yes, this seems fine to me. Even if not yet perfect, seems better than what was there before. Fine with me to merge.

My python 3.8.6 claims """ is depreciated?  (not related to this PR):
[Gibbo:.+el-MR-tools.vmi]$ pytest-3
============================= test session starts ==============================
platform linux -- Python 3.8.6, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
rootdir: /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi
plugins: cov-2.11.1
collected 90 items

abel/tests/test_basex.py .............                                   [ 14%]
abel/tests/test_benchmarks.py ..                                         [ 16%]
abel/tests/test_dasch_methods.py .....                                   [ 22%]
abel/tests/test_direct.py .....                                          [ 27%]
abel/tests/test_hansenlaw.py .......                                     [ 35%]
abel/tests/test_linbasex.py ..                                           [ 37%]
abel/tests/test_math.py .                                                [ 38%]
abel/tests/test_onion_bordas.py ......                                   [ 45%]
abel/tests/test_rbasex.py ...............                                [ 62%]
abel/tests/test_tools_center.py ......                                   [ 68%]
abel/tests/test_tools_circularize.py .                                   [ 70%]
abel/tests/test_tools_distributions.py ................                  [ 87%]
abel/tests/test_tools_polynomial.py .....                                [ 93%]
abel/tests/test_tools_symmetry.py .                                      [ 94%]
abel/tests/test_tools_vmi.py .....                                       [100%]

=============================== warnings summary ===============================
abel/__init__.py:23
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/__init__.py:23: DeprecationWarning: invalid escape sequence \.
    filterwarnings('default', '^abel\.', category=DeprecationWarning)

abel/tools/analytical.py:164
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/analytical.py:164: DeprecationWarning: invalid escape sequence \
    """

abel/tools/analytical.py:222
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/analytical.py:222: DeprecationWarning: invalid escape sequence \
    """

abel/tools/math.py:64
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/math.py:64: DeprecationWarning: invalid escape sequence \m
    """

abel/tools/polynomial.py:18
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/polynomial.py:18: DeprecationWarning: invalid escape sequence \
    """

abel/tools/polynomial.py:193
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/polynomial.py:193: DeprecationWarning: invalid escape sequence \
    """

abel/tools/transform_pairs.py:56
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:56: DeprecationWarning: invalid escape sequence \s
    """ coefficient

abel/tools/transform_pairs.py:66
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:66: DeprecationWarning: invalid escape sequence \e
    """**profile1**:

abel/tools/transform_pairs.py:149
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:149: DeprecationWarning: invalid escape sequence \e
    """**profile2**:

abel/tools/transform_pairs.py:198
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:198: DeprecationWarning: invalid escape sequence \e
    """**profile3**:

abel/tools/transform_pairs.py:268
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:268: DeprecationWarning: invalid escape sequence \
    """**profile4**:

abel/tools/transform_pairs.py:376
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:376: DeprecationWarning: invalid escape sequence \e
    """**profile5**:

abel/tools/transform_pairs.py:422
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:422: DeprecationWarning: invalid escape sequence \e
    """**profile6**:

abel/tools/transform_pairs.py:470
  /home/stg121/Software/Python/PyAbel/PyAbel-MR-tools.vmi/abel/tools/transform_pairs.py:470: DeprecationWarning: invalid escape sequence \e
    """**profile7**:

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=================== 90 passed, 14 warnings in 17.51 seconds ====================

@stggh, thanks for the toPES suggestion! I've changed the test accordingly.
As for the """ warnings, they are in fact about TeX and Sphinx escapes that are not Python-escaped (like '\sqrt' instead of '\\sqrt' or r'\sqrt'). It's strange that they don't show up in the CI test, neither I saw them locally. However, pycodestyle indeed detects them, so I'll include the corrections in the next PR.
@DanHickstein, yes, these test are very basic and, in principle, something deeper is needed. I think, however, that most other stuff, like non-default and non-integer origin, or the resolution, should be done in tests of polar.py, which we in fact don't have at all... I'd be glad if somebody else can work on this (and other missing tests). Maybe, we should broaden #290 to list all necessary test improvements and then, on occasion, start working on them?


FeatureRequest - support maintenance windows

Locksmith support utilization of maintenance windows;
https://coreos.com/os/docs/latest/update-strategies.html#auto-updates-with-a-maintenance-window .
Would be nice for update operator to support setting up maintenance window preferably via TPR setting.

Agreed, this is key for us. In addition, being able to easily suspend/resume reboots is important too.

Reboot windows are now supported in master (see #170). I'll update this issue and then close it out once a release is tagged that has this feature in it.

is there an eta, when a new release is made? we actually need this feature.

v0.7.0 is released, with support for reboot windows! See the release page for details - https://github.com/coreos/container-linux-update-operator/releases/tag/v0.7.0


Remove shards

This change removes all text related to shards, including code, tests, documentation, and configuration settings.
99% of the change is removed lines and all remaining tests pass. Only 3 tests are removed:

nodestore/DatabaseShard_test.cpp
rpc/NodeToShardRPC_test.cpp
rpc/ShardArchiveHandler_test.cpp

Only 2 tests are modified:

nodestore/Database_test.cpp: Remove tests of Database::ledgersPerShard().
rpc/RPCCall_test.cpp: Remove tests of download_shard and node_to_shard.

So what's the replacement method to reliably and trustlessly share a full history node database?

@MarkusTeufelberger tarball, rsync, all the most popular methods for copying data. The sharding feature was never completed. What is there to replace?

There's a comment mentioning shards in src/xrpld/nodestore/backend/NuDBFactory.cpp (lines 152-158), it probably needs to be updated

I also see mention of HTTPDownloader::do_session in src/xrpld/net/detail/HTTPDownloader.cpp (line 127)

Codecov Report
Attention: Patch coverage is 36.23188% with 44 lines in your changes missing coverage. Please review.

Project coverage is 74.8%. Comparing base (a39720e) to head (dd6b21a).
Report is 1 commits behind head on develop.

Additional details and impacted files

We have to ignore the "failing" check from codecov, the one that is showing "36% of diff hit (target 71%)". The alternative is to add more code in unit tests, which this PR should not do.

@ximinez asked...

Why not finish the feature?

In part because the code is particularly stale.  Mickey gave me a core dump on the state of shards in November of 2021.  No one has done any development (at all) on shards since then.  That's a good 2.5 years worth of stale.  Mickey was hoping that I would pick up development of shards.  But I didn't.  Ripple had other plans for what I needed to work on.
Also, Ripple ended up throwing it weight into clio, which was described as an alternative to shards as a solution for the full history problem.  If you believe that clio solves the full history problem, then shards are a lot less useful.
Another reason to not finish Shards is because Mickey was just discovering some additional difficult parts of shards.  The code is not bad code, but the feature is not actually done.  There's no one with a vision for how the feature should be completed.
I hope that history helps.

Based on my understanding of the old design, I have reservations.
I imagine that activity among ledger objects follows a power law distribution. Most objects are rarely touched, and a few objects represent most of the touches in any given block. If we pack new objects into a shard until it reaches a size limit, and then seal that shard and distribute it, then most objects in the shard are in the small set of frequently touched objects, but a few objects in the shard will be from the infrequently touched set.
How does this affect the performance of serving particular queries I might have?

If I want one particular object as it existed in one particular ledger, then I need a proof path from the header of that ledger to that object. If the shards are storing inner nodes, then the search might involve a path through multiple shards, held by different servers, and shards will fill up quickly because they are storing so much data from inner nodes. If the shards are not storing inner nodes, then they will store less data, but the search will involve even more shards, that are even more likely to be held by different servers, because we have to collect the leaves of the entire subtree to recompute the inner nodes.

If I want a complete copy of one ledger, then as time goes on, each object becomes more likely to be the only object of interest in its shard. The number of bytes I'm downloading explodes because most of it is for other ledgers.

I think what we really want is consistent hashing of ledger objects, not bundles of ledger objects that we call shards. But we need consistent hashing in the context of a trustless, decentralized peer-to-peer network with high turnover. There may be good solutions in this problem space. I haven't seen them, but I haven't done any research.
Then, there are my engineering sentiments. I don't like the proliferation of branches that shards introduced. I'd rather just see a clean replacement of the nodestore abstraction.


Manage fees when pytrader takes multiple positions in the same instrument in different directions

Its dumb to pay poloniex fees when two predictor_configs go against each other.  These two trades should cancel each other out insetad of actually going to the exchange.

https://github.com/owocki/pytrader/issues/5


Updating our protection from command injection

Our protection from command injection has been broke many times before, due to the fact we block commands that contain some characters that might be executed on the bash shell, and then other issues about arguments injection came and we had to drop requests if it's using arguments that limited the user input to not access valid stuff

I decided to allow those characters again, but using quotes to disallow the execution of them on the shell, That would allow the user to use much more stuff and would keep discord-recon secure again

This feature will be added on the next release of discord-recon

This issue has been fixed on the current release


Can Unminify button search all folders within Blob Storage Account ?

Is your feature request related to a problem? Please describe.
We are using the UnMinify feature of Application Insights for our Angular Frontend project. We have configured Azure Devops to Copy Source Maps to our Blob Storage account by following this article. https://docs.microsoft.com/en-us/azure/azure-monitor/app/source-map-support. To keep things organized, we are storing the SourceMaps with the version information (20200707.2) like this.
https://<STORAGEACCOUNT>.blob.core.windows.net/sourcemaps/20200707.2/1.f10f936dc57eed434bd0.js.map
The problem is that when we click Unminify button, Application Insights is searching only the ROOT of the folder to look for source maps.
Describe the solution you'd like
Is there some magic we can do to ensure that Application Insights searches either all the folders or a specific folder for the correct version to find the source maps?
Describe alternatives you've considered
We are currently copying source maps from all releases directly in to the root of the BLOB Container which is a bit tough to organize.
Additional context
none

The current behavior is for it to search for the mapfile based on the folder structure of the originating JS file. The exact behavior is described here: https://docs.microsoft.com/en-us/azure/azure-monitor/app/source-map-support#push-your-source-maps-to-your-blob-container
To self-debug, you can view the network tab of your browser's F12 menu and see where we are looking for mapfiles when you click unminify.
You do not need to host all of your mapfiles at the root of the storage container anymore.


Module 4: Lab 13: Azure Monitor

Module   4: Lab 13: Azure Monitor
Ex 1   Task 5 Step 4: The default is to show the Resource Type : Log Analytics.   Click the X to show all the resource types on the left, then scroll down, and   then select Virtual machine to show example queries for that resource type.

updated


BTS-1950: geo index query stuck

Scope & Purpose
BTS-1950: geo index query stuck
The geo index iterator got stuck when multiple coverings were requested
multiple time. The corresponding flag was not resetted resulting in an
endless loop.

[x] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.12.0: (Please link PR)
[ ] Backport for 3.11: (Please link PR)
[ ] Backport for 3.10: (Please link PR)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[x] GitHub issue / Jira ticket: BTS-1950
[ ] Design document:

The CircleCI failure is unrelated and also occurs in "devel".

I still need to write a test before merging.


added style Menubutton, and finished sync

a Menubutton added for selecting style,
connected style of text_area to style of preview_area via a self.css member field
added another flag reset of text_area.edit_modified so that on_input_change fires when it should.

Hi @hbregalad and thanks for this brilliant PR ! The project is only about 15/16 hours old so i honestly wasn't expecting any other contributors, thank you !
The PR is good, i'll accept and merge, thanks.


Fix for allow mutation and corresponding test case

This is actually my very first pull request to a github repo, I hope it is helpful. Any feedback is appreciated of course! I have run the testcases, they were green.

Thanks for the PR! :)

I've continued this on https://github.com/pydantic/bump-pydantic/pull/65. I couldn't commit here. :(

When you push a PR on a project, ideally you would create another branch, because the fork has the same configuration as the main branch, so your fork's main branch is protected, and I couldn't push here. 😅
(I've given co-author to you on the other PR)


the operate system say don't find the "data/train"

dear author,
my os is win11, The fellow is my mistake information. do you know how to solve it?
FileNotFoundError: [WinError 3] 系统找不到指定的路径。: 'data\train'
when i create the "data/train", there is another probelm.
self = reduction.pickle.load(from_parent)
_pickle.UnpicklingError: pickle data was truncated

Hi @sunwuzhou03,
Please ensure that you have correctly assigned the data directory path to the variable data_dir in the dataset.py file. If your data directory is located outside the repository directory, please provide an absolute file path. Additionally, I have updated preprocess.py to address some bugs related to parsing Windows file paths. If you continue to encounter this issue, please specify which file you were running and provide the complete error message. Thank you!


readme: remove startup script instances

As startup script was dropped, the readme is now updated to drop any references

Thanks for the update, docs are often the last thing to get updated lol

This is one of the indispensable piece of software in my workflow, cool idea combining with zoxide

I agree! Glad I was able to make this open source so others can use it ❤


[data_transformer.cpp:1036] Check failed: datum_channels > 0 (0 vs. 0)

When I ran the train.sh file I got error, I got the Check failed error. Has anyone found a fix for this ? I noticed there've been 2 different issues on this without any fix. The log is shown below:
I1129 02:30:17.158061 22823 layer_factory.hpp:77] Creating layer data
I1129 02:30:17.158288 22823 net.cpp:100] Creating Layer data
I1129 02:30:17.158316 22823 net.cpp:408] data -> data
I1129 02:30:17.158370 22823 net.cpp:408] data -> label
I1129 02:30:17.158926 22824 db_lmdb.cpp:35] Opened lmdb trainval_lmdb/
F1129 02:30:17.159502 22823 data_transformer.cpp:1036] Check failed: datum_channels > 0 (0 vs. 0)
*** Check failure stack trace: ***
@     0x7f265ef055cd  google::LogMessage::Fail()
@     0x7f265ef07433  google::LogMessage::SendToLog()
@     0x7f265ef0515b  google::LogMessage::Flush()
@     0x7f265ef07e1e  google::LogMessageFatal::~LogMessageFatal()
@     0x7f265f695552  caffe::DataTransformer<>::InferBlobShape()
@     0x7f265f5ca548  caffe::AnnotatedDataLayer<>::DataLayerSetUp()
@     0x7f265f52a3fa  caffe::BasePrefetchingDataLayer<>::LayerSetUp()
@     0x7f265f668f07  caffe::Net<>::Init()
@     0x7f265f66a761  caffe::Net<>::Net()
@     0x7f265f64539a  caffe::Solver<>::InitTrainNet()
@     0x7f265f6467a7  caffe::Solver<>::Init()
@     0x7f265f646b4a  caffe::Solver<>::Solver()
@     0x7f265f6925b9  caffe::Creator_RMSPropSolver<>()
@           0x40bd3a  train()
@           0x408638  main
@     0x7f265d89f830  __libc_start_main
@           0x408f09  _start
@              (nil)  (unknown)
Aborted (core dumped)

This error is due to the data type, the error was gone when I changed the data type from AnnotatedData to Data in MobileNetSSD_train.prototxt and MobileNetSSD_test.prototxt file.


Android 15

Thanks for this amazing module. Could you please make it compatible with a15 too? It works with los 21, but not with los 22. Module is not opening both with kernelsu or magisk. Setup is lsposed mod and zygisk next.

Not related to the module, your lsposed is broken. The only lsposed version that works on Android 15 is https://github.com/JingMatrix/LSPosed

@Juby210  So sorry for trouble. Returning back to zygisk next from rezygisk fixed the thing. Thanks for your all help again. Wish you best.


handlers: fix response encoding format

According to the official wire protocol documentation^1:

In simple Query mode, the format of retrieved values is always text, except when the given command is a FETCH from a cursor declared with the BINARY option.

However, for the binary protocol the situation is more complicated, as this is determined by the Bind^3 command^2:

Bind also specifies the format to use for any data returned by the query; the format can be specified overall, or per-column.

Given the above infromation, this aligns the implementation here with the sqllite and duckdb examples from the pgwire repository.
To see why the current state is an issue, try running SELECT 1::int4 from a Rust crate that uses rust-postgres. Using the example from this gist:
cargo run --example pg_client -- query "SELECT 1::int8"

Without the fixes I get:
error retrieving column 0: error deserializing column 0: failed to fill whole buffer
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

with the fixes:
┌──────────┐
│ Int64(1) │
├──────────┤
│        1 │
└──────────┘

Thank you for the patch and detailed explaination. Are you using this example in your own project?

Are you using this example in your own project?

Yes, but nothing production-ready! I've forked it and I'm now building a more complete frontend (codename postfusion). Currently it's just a vehicle to explore arrow and datafusion work behind a more familiar interface (also a lot of benchmarks have Postgres/psql-compatible implementations, which makes running them easier).
I'll see how far I can go with it—if it ends up being anything interesting I'll put it out with an Apache license.


Guidance on training custom model

[Hi there, do you have any further guidance on model training, beyond your help pages?
I have a large volume of parallel documents and TM files I can use to train  a custom model.
Is TM data better suited to sentence/phrase dictionary training and parallel docs for regular training?  Thanks in advance]

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

ID: 8ad6bc07-7e56-f28d-eb45-d5d0dd2ae49f
Version Independent ID: f4197865-63fa-6f7a-2e9a-0d2ea5b5a9bf
Content: Train model - Azure Cognitive Services
Content Source: articles/cognitive-services/Translator/custom-translator/how-to/train-custom-model.md
Service: cognitive-services
Sub-service: translator-text
GitHub Login: @laujan
Microsoft Alias: lajanuar

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

@tristanmaccana
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1
If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.