feat: use accountID instead of email in AuthScreens logic

Details
A part of the 'Secure Logins' issue, point 6.
Use accountID instead of email in AuthScreen auth logic. Made a new method called isLoggingInAsNewUserWithAccountID, since the isLoggingInAsNewUser method is still being used in other place.
Fixed Issues
$ https://github.com/Expensify/App/issues/19007
https://github.com/Expensify/App/issues/19007#issuecomment-1560558505
Tests
Only possible in Web:

Login into NewDot and verify that the default behavior is the same

Go to Old Dot

Click on the FAB button on the bottom left corner

Copy paste the link generated and switch to localhost but maintaining the same URL params

Check that the default behavior does not change, the page will redirect to the NewDot running locally

Login as user 1 in new dot

Open old dot and login as user 2

Click on the FAB button on the bottom left corner

Copy paste the link generated and switch to localhost but maintaining the same URL params

Check that the default behavior does not change, the page will redirect to the NewDot running locally

User 1 should be logged out, and User 2 should be automatically logged in.

Not in web:

Login into NewDot and verify that the default behaviour is the same

[x] Verify that no errors appear in the JS console

Offline tests
Not applicable
QA Steps
Only possible in Web:

Login into NewDot and verify that the default behavior is the same

Go to Old Dot

Click on the FAB button on the bottom left corner

Check that the default behavior does not change

Login as user 1 in new dot

Open old dot and login as user 2

Click on the FAB button on the bottom left corner

Check that the default behavior does not change, the page will redirect to the NewDot

User 1 should be logged out, and User 2 should be automatically logged in.

Not in web:

Login into NewDot and verify that the default behaviour is the same

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/25725586/abe45ab7-e4aa-48ef-90a8-a20a9b09c5cf

Mobile Web - Chrome
https://github.com/Expensify/App/assets/25725586/af68dc74-365c-4e3b-a907-57ae3845c5f4

Mobile Web - Safari
https://github.com/Expensify/App/assets/25725586/02966d31-21d4-45cf-82ce-9eec10b27a7d

Desktop
https://github.com/Expensify/App/assets/25725586/7ee76eed-8e83-4424-b958-b3db87cc885f

iOS
https://github.com/Expensify/App/assets/25725586/9d7ac6df-1a55-41f5-89d3-4c57838cc9c0

Android
https://github.com/Expensify/App/assets/25725586/59f2189d-16a6-4e2f-bb8b-00fb46cadfe3

All you @fedirjh - please test when you get a chance 🙏

@fedirjh @Beamanator Updated! Also added the extra test to the PR description, thank you!

why it only affects native ?

Investigating this now 🔎 not sure if it might be related to development setup. I've tried navigating from the OldDot directly in the mobile browser, but it seems deep linking is not triggering. Does this issue also happen with the NewDot prod app?

Closing since this being done in another branch: https://github.com/Expensify/App/pull/20157#issuecomment-1582663707


WP3 DELIVERABLE Electrofishing database template

The database (exchange format needs to be ready by the next datacall for wgeel - springtime 2026)


Update sbt, scripted-plugin to 1.10.6

About this PR
📦 Updates

org.scala-sbt:sbt
org.scala-sbt:scripted-plugin

from 1.8.3 to 1.10.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #640.


TopicTemplate and "Sub-Topics"

Is your feature request related to a problem? Please describe.
We would like to route some DataSetWriterGroup to a different nested topic path.
Describe the solution you'd like
We'd like to be able to define or override attributes that can be used in TopicTemplate in the configuration for each WriterGroup.
Describe alternatives you've considered
Using the {DataSetWriterGroup} in the topic template and setting it to something like "mytopicA/mySubTopicB" and "myTopicC/mySubTopicD" (in our case actually mytopicA.mySubTopicB since we are using DAPR + NATS) . This works but we are wondering whether this is officially supported or might "break" in future publisher versions.
=> Are there any restrictions that might be applied for DataSetWriterGroup in future versions of the publisher?
Additional context

There should probably be a better way to do this.  Especially because part 14 permits mqtt topic path and query chars in names.

Hi @marcschier. I created a PR #2193  which address this issue. This PR will enable us to define different topics für each datasetwriter. Please let me know whether are you ok with the changes or if there some things missing. Thanks.

In 2.9.5 (main branch) it is possible to set the topic per group, writer (and even at node level., but this is experimental). That way you should be able to accomplish what you want here.  Please be aware that support on this feature is only via GitHub.


Add YUV support (packed and semiplanar), refactor RGB support, refactor and add tests

I've refactored RGB support, now its only one parser for entire RGBA (including RGBA, BGRA etc.). Future color formats implementations should follow same structure i. e. ARGB or XRGB.
There is now YUV support included. For now there are packed 4:2:2 formats (YUY2/YUYV, UYVY) and semi-planar 4:2:0 formats (NV12 and NV21). For now only 8-bit formats are allowed.
I've also refactored parser tests - now they are using mocks.
EDIT: Now you CAN'T open files providing any resolution - if there will be not enough data in file to build an image in chosen color format and resolution, exception will be thrown.
Closes #18, fixes #19.

EDIT: Now you CAN'T open files providing any resolution - if there will be not enough data in file to build an image in chosen color format and resolution, exception will be thrown.

Is there a reason for this? We'd like to be able to use this app with malformed frames too. And probably with dumps containing multiple frames too.
So ideally we'd like to be able to just provide the width and it should be enough to calculate the height for the data it receives - the data can be padded with zeroes if it ends in the middle of the last line.

EDIT: Now you CAN'T open files providing any resolution - if there will be not enough data in file to build an image in chosen color format and resolution, exception will be thrown.

Is there a reason for this? We'd like to be able to use this app with malformed frames too. And probably with dumps containing multiple frames too.
So ideally we'd like to be able to just provide the width and it should be enough to calculate the height for the data it receives - the data can be padded with zeroes if it ends in the middle of the last line.

This was available in previous versions, but I thought that garbage data is not useful here so I removed it. But if you need that functionality, I will restore that right away.

I've changed the way data is interpreted - now only width should be provided and height is calculated by parsing function.
For now I leave height argument in parse method so it is compliant with current version of CLI and GUI. This will be changed in the future.


Add Pournelle's law

Hello Stéphane,
This law is true in every large corporation, as it seems you have experienced in your career.
Best regards,
Antoine

Hi Antoine ! Many thanks for this PR ! :star_struck:
It's fascinating how this Law intersects with the Shirky principle.
It warrants a reference, I'll take care of that :+1:


Feature Request: Filter workflow states from the Kanban view

I'd like to be able to filter arbitrary workflow states from a kanban board.
For example, I'd like to be able to ignore things in the abandoned state or the ice-box state.
Let me know if such a feature sounds possible and interesting.

At the moment there is already the range parameter.
If you would put abandoned and ice-box to the end of the states, then you could select everything needed with :range ("Todo" . "Done") if you would have e.g. the header #+TODO: Todo Plan Develop Test | Done Iced Abandoned

Thanks @gizmomogwai, this was exactly what I wanted.


Refine native class examples

Use the constructor in the application route. Avoid outdated bubbling route-actions.

@kategengler this example gives me an InternalError: "too much recursion" which seems to result from the router service being the same as the router we're constructing. Changing the code to:
this.on('routeDidChange', () => {
  const page = this.router.currentURL;
  const title = this.router.currentRouteName || 'unknown';

  this.metrics.track(page, title);
});

Seems to work and fix that issue.

@jrjohnson I have the code from the example verbatim in an app, and working, on 3.13.

which seems to result from the router service being the same as the router we're constructing

I'm not sure I understand this? This snippet is in the constructor of the Application Route, so we're not constructing a router.

Ah, I see a difference. The Octane blueprint and Ember 3.14 use:
import EmberRouter from '@ember/routing/router';
and this code has:
import Route from '@ember/routing/route';
Aside from the name of the import one is from router and one is from route. I have no idea which is correct.

@jrjohnson I think you are in the wrong file. This should be in app/routes/application.js not in app/router.js

😊 damn! Sorry for the noise. I've always had these instructions in router.js and I didn't even notice the difference. Super obvious why the import is different now too.

Thank you @kategengler and @jrjohnson.


CM-1069: sessions and users

fixes bug in assigning quiz to session (not user)
more generally, adds assign_session function and use it in routes if and only if the route has jwt_token and session_uuid (though not sure if this is the optimal criterion?)

@cyplas Let me know if you are still working on this

I more like solutions which allow us to cover "any other request". I would prefer solutions # 2,3,4 from this answer (not decorator) . You are free to use any solution you like. The acceptance criteria is avoid calling assign_session function directly from any endpoint. Having this we could don't worry about this bug in the future. All requests will be covered.

@danmash Good idea. I opted for solution 2. Now let's see if I understood you right. :) And I'm not sure if placing the hook in climatemind.py is appropriate, but I'm not sure where would be better?

@cyplas thank you for the update.
Let me think about your question.
Meanwhile, I suggest you add the following unittests because I don't know how to test these changes in a different way.

Create session factory without user
Make a request without access token and make sure user is not populated
Then create a user + access token and run the same request with cookie added. Assert the session user field populated successfully.
parameterize the test with multiple different URLs to make sure before_request works fine for any request

I suggest you add the following unittests because I don't know how to test these changes in a different way.

Create session factory without user
Make a request without access token and make sure user the session's user field is not populated
Then create a user + access token and run the same request with cookie added. Assert the session user field populated successfully.
parameterize the test with multiple different URLs to make sure before_request works fine for any request

I've tried to do something along these lines now, but I haven't written these kinds of tests before, so I'm fumbling my way along and clearly not there yet. The final assert fails, even though doing an analogous real API call works, so I think it's my test that's the problem, not the function. @danmash Your help would be appreciated.

@cyplas Great progress! I think the problem is the wrong argument order, see my suggestions above.

Codecov Report

Merging #363 (d68e368) into develop (f6baf4e) will increase coverage by 1.85%.
The diff coverage is 68.00%.

@@             Coverage Diff             @@
##           develop     #363      +/-   ##
===========================================
+ Coverage    60.83%   62.69%   +1.85%
===========================================
  Files           80       80
  Lines         2579     2592      +13
  Branches       375      377       +2
===========================================
+ Hits          1569     1625      +56
+ Misses         999      952      -47
- Partials        11       15       +4

Impacted Files
Coverage Δ

app/scoring/process_scores.py
74.13% <0.00%> (ø)

app/scoring/routes.py
41.46% <0.00%> (+4.87%)
:arrow_up:

app/session/session_helpers.py
97.50% <92.85%> (-2.50%)
:arrow_down:

conftest.py
100.00% <100.00%> (ø)

app/conversations/routes.py
53.03% <0.00%> (+3.78%)
:arrow_up:

app/auth/routes.py
40.18% <0.00%> (+4.67%)
:arrow_up:

app/alignment/routes.py
49.18% <0.00%> (+4.91%)
:arrow_up:

app/myths/routes.py
75.00% <0.00%> (+16.66%)
:arrow_up:

... and 1 more

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

I think the problem is the wrong argument order, see my suggestions above.

The main problem turned out to be that the @before_request was only being added to the app in climatemind.py, which is separate from the conftest.py one.


Fix race between reading file info and bitcask merge delete

Between listing a directory and reading each file info's, merge
delete can interleave. Then read file info results in enoent error.
This commit treats it as zero size file.
Typical error message of this race is:
{{badmatch,{error,enoent}},
 [{cs_suites,'-check_data_files_are_small_enough/3-lc$^0/1-0-',1,
             [{file,"riak_test/src/cs_suites.erl"},{line,538}]},

This PR includes only change of riak_test code.

@borshop merge


Loss is 0 in step 200 and assertion error.

I'm really really sorry to ask you a trivial question.
train.py train_bert_base works well!

I have Korean data in conll 2012 form.
they are work in e2e-coref model.
I want to apply Korean data to your model.
So I did run minimize.py, and train.py
But Loss is 0 in step 200 and assertion error in eval time.
assertion error log
Traceback (most recent call last):
  File "train.py", line 64, in <module>
    eval_summary, eval_f1 = model.evaluate(session, tf_global_step)
  File "/data/BERT-coref/coref/independent.py", line 559, in evaluate
    coref_predictions[example["doc_key"]] = self.evaluate_coref(top_span_starts, top_span_ends, predicted_antecedents, example["clusters"], coref_evaluator)
  File "/data/BERT-coref/coref/independent.py", line 524, in evaluate_coref
    predicted_clusters, mention_to_predicted = self.get_predicted_clusters(top_span_starts, top_span_ends, predicted_antecedents)
  File "/data/BERT-coref/coref/independent.py", line 499, in get_predicted_clusters
    assert i > predicted_index, (i, predicted_index)
AssertionError: (0, 0)

It's my experiments.conf
train_kor = ${best}{
  num_docs = 2411
  bert_learning_rate = 1e-05
  task_learning_rate = 0.0002
  max_segment_len = 128
  ffnn_size = 800
  train_path = ${data_dir}/train.kor.128.jsonlines
  eval_path = ${data_dir}/dev.kor.128.jsonlines
  conll_eval_path = ${data_dir}/dev.kor.v4_gold_conll
  max_training_sentences = 8
  bert_config_file = ${best.log_root}/multi_cased_L-12_H-768_A-12/bert_config.json
  vocab_file = ${best.log_root}/multi_cased_L-12_H-768_A-12/vocab.txt
  tf_checkpoint = ${best.log_root}/multi_cased_L-12_H-768_A-12/bert_model.ckpt
  init_checkpoint = ${best.log_root}/multi_cased_L-12_H-768_A-12/bert_model.ckpt
}

I changed the BERT model to the multi_cased.
I editted num_docs to 2411.

(It's result of minimize.py. Is this correct?)
and default ffnn_size and max_training_sentences cause memory error.
so I editted ffnn_size and max_training_sentences.
Is there anything I miss?

Not a trivial question at all. Thanks for your interest! The evaluation error is likely a product of the optimizer going off the rails. At a high level, I would first check if the data are correct and then move on to the optimization. A few comments and questions so that I can get a better sense of what might be wrong.

Did you make sure that minimize.py uses the same vocab as your config? More generally, does train.kor.128.jsonlines seem reasonable? It should have 2411 lines and the tokenization should make sense. The values in the clusters key should also make sense.
I'm not familiar with the Korean data. It would be good to check the documentation if the number of documents in the dataset is indeed 2411.
One more debugging strategy would be to try the BERT multilingual model on the Ontonotes Chinese data. This is just a sanity check to verify that the multilingual model "works" with the current code. I vaguely remember that I got it to work at some point, so it should work now.
If you're convinced that the data are fine, then this might be an optimization issue. Large transformer models, especially with more involved task architectures,  are hard to optimize. Might be a good idea to try a bunch of learning rates.
How much GPU memory do you have? Might be a good idea to reduce max_training_sentences even further and bump up ffnn_size.

I'm using Titan Xp.
It is train.py train_kor's log
I0902 19:18:27.344511<PHONE_NUMBER>66208 train.py:58] [0] loss=50.37, steps/s=0.00
I0902 19:18:54.144479<PHONE_NUMBER>66208 train.py:58] [100] loss=9.06, steps/s=2.47
I0902 19:19:21.534149<PHONE_NUMBER>66208 train.py:58] [200] loss=0.00, steps/s=2.94
I0902 19:19:49.008810<PHONE_NUMBER>66208 train.py:58] [300] loss=0.00, steps/s=3.14
I0902 19:20:16.368205<PHONE_NUMBER>66208 train.py:58] [400] loss=0.00, steps/s=3.26
I0902 19:20:43.680098<PHONE_NUMBER>66208 train.py:58] [500] loss=0.00, steps/s=3.33
I0902 19:21:10.876853<PHONE_NUMBER>66208 train.py:58] [600] loss=0.00, steps/s=3.38
I0902 19:21:37.686788<PHONE_NUMBER>66208 train.py:58] [700] loss=0.00, steps/s=3.43
I0902 19:22:04.828290<PHONE_NUMBER>66208 train.py:58] [800] loss=0.00, steps/s=3.46
I0902 19:22:32.054537<PHONE_NUMBER>66208 train.py:58] [900] loss=0.00, steps/s=3.48
I0902 19:22:59.043721<PHONE_NUMBER>66208 train.py:58] [1000] loss=0.00, steps/s=3.50
Loaded 248 eval examples.
2019-09-02 19:23:07.617607: W tensorflow/core/kernels/queue_base.cc:277] _0_padding_fifo_queue: Skipping cancelled enqueue attempt with queue not closed
Traceback (most recent call last):
  File "train.py", line 64, in <module>
    eval_summary, eval_f1 = model.evaluate(session, tf_global_step)
  File "/data/BERT-coref/coref/independent.py", line 559, in evaluate
    coref_predictions[example["doc_key"]] = self.evaluate_coref(top_span_starts, top_span_ends, predicted_antecedents, example["clusters"], coref_evaluator)
  File "/data/BERT-coref/coref/independent.py", line 524, in evaluate_coref
    predicted_clusters, mention_to_predicted = self.get_predicted_clusters(top_span_starts, top_span_ends, predicted_antecedents)
  File "/data/BERT-coref/coref/independent.py", line 499, in get_predicted_clusters
    assert i > predicted_index, (i, predicted_index)
AssertionError: (0, 148)

sometimes loss is NaN in step 100.
I checked my train conll and jsonlines.
It have 2411 documents.
and "clusters": [[[1575, 1582], [252, 254], [1284, 1286], [1778, 1784], [1821, 1823], [1162, 1164], [1930, 1932], [1, 15], [1084, 1090], [1587, 1589], [847, 849]], ..., [[978, 985], [925, 936]]] also make sense!
I tried Chinese data and It works...
and I'm trying a bunch of learning rates..

Hmm this is quite odd. The doc_key is basically a genre embedding, and having a different set of  genres should be fine. There are two learning rates -- one for the BERT parameters and one for the task (coreference-specific) parameters. The task LR should be larger than the BERT LR since we don't want the BERT params to change a lot. But it might be a good idea to set both of them to 1e-5 just to debug.

I'm trying to your code every day..
sometimes, loss is fine. (I don't know this situation...)
but aseertion error occurs frequently.
like
I0904 23:36:20.775774<PHONE_NUMBER>20032 train.py:58] [0] loss=52.75, steps/s=0.00
I0904 23:36:48.853983<PHONE_NUMBER>20032 train.py:58] [100] loss=56.96, steps/s=2.49
I0904 23:37:16.643731<PHONE_NUMBER>20032 train.py:58] [200] loss=106.59, steps/s=2.94
I0904 23:37:44.761991<PHONE_NUMBER>20032 train.py:58] [300] loss=167.72, steps/s=3.12
I0904 23:38:13.796795<PHONE_NUMBER>20032 train.py:58] [400] loss=174.39, steps/s=3.20
I0904 23:38:42.192664<PHONE_NUMBER>20032 train.py:58] [500] loss=126.75, steps/s=3.26
I0904 23:39:10.581388<PHONE_NUMBER>20032 train.py:58] [600] loss=113.55, steps/s=3.30
I0904 23:39:38.504084<PHONE_NUMBER>20032 train.py:58] [700] loss=59.20, steps/s=3.34
I0904 23:40:07.391193<PHONE_NUMBER>20032 train.py:58] [800] loss=79.45, steps/s=3.3                                                                                5
I0904 23:40:35.656905<PHONE_NUMBER>20032 train.py:58] [900] loss=45.97, steps/s=3.37
I0904 23:41:03.529552<PHONE_NUMBER>20032 train.py:58] [1000] loss=42.10, steps/s=3.39
Loaded 248 eval examples.
Evaluated 1/248 examples.
2019-09-04 23:41:11.234775: W tensorflow/core/kernels/queue_base.cc:277] _0_padding_fifo_queue: Skipping                                                                                cancelled enqueue attempt with queue not closed
Traceback (most recent call last):
  File "train.py", line 66, in <module>
    eval_summary, eval_f1 = model.evaluate(session, tf_global_step)
  File "/data/BERT-coref/coref/independent.py", line 568, in evaluate
    coref_predictions[example["doc_key"]] = self.evaluate_coref(top_span_starts, top_span_ends, predicte                                                                                d_antecedents, example["clusters"], coref_evaluator)
  File "/data/BERT-coref/coref/independent.py", line 533, in evaluate_coref
    predicted_clusters, mention_to_predicted = self.get_predicted_clusters(top_span_starts, top_span_end                                                                                s, predicted_antecedents)
  File "/data/BERT-coref/coref/independent.py", line 508, in get_predicted_clusters
    assert i > predicted_index, (i, predicted_index)
AssertionError: (0, 606)

Can you explain this Assertion?
I think, This assertion prevents the latter entity from being considered a predecessor. right..?
Is it essential?

From a quick glance, I think so. I suspect getting rid of it will mess up the evaluation, but you can still try it out. The official coref evaluation is rather complicated in that it needs to call perl scripts. It might be a good idea to turn those off (eval_mode=False  in independent.py) and just use the unofficial eval in python.
The problem seems to be in andecedent_scores. I would check that variable to see why it's making those predictions. If I understand this right, subtoken 0 should not have any antecedents and should not be a mention since it's the CLS token. Perhaps all mention/antecedent scores are the same? Or your clusters have CLS in them as a mention. I would check all those variables/data to see what's going on.

Thank you so much for your effort..

Closing due to inactivity. Please feel free to reopen if something comes up. Thanks!

As you think, The problem seems to be in andecedent_scores.
So I checked andecedent_scores.
While I was checking the code, I found something I didn't understand.
I think here is a bug.
def coarse_to_fine_pruning(self, top_span_emb, top_span_mention_scores, c):
    k = util.shape(top_span_emb, 0)
    top_span_range = tf.range(k) # [k]
    #[0,1,...k-1]

    antecedent_offsets = tf.expand_dims(top_span_range, 1) - tf.expand_dims(top_span_range, 0) # [k, k]
    '''
    0 -1 -2 -3 ... -k+1   <<[cls]
    1 0 -1 -2 ...         << 1st real-text token
    2 1 0 ...
    ...
    k-1 k-2 k-3 ...  0
    '''

    antecedents_mask = antecedent_offsets >= 1 # [k, k]
    '''
    F F F F ...   F                << I think should be changed.
    ...
    T T T T ...    F
 ...
F T T T ... F
#antecedents_mask[0][*] = False

because, token[0] is [cls].
and.... I face loss is NaN and assert i > predicted_index everyday.... T.T

Did you try training with that change?
Adding @freesunshine0316 who might be interested.

There is not change in code.
I just use korean data that work well on e2e model.

I want to know which document loss == NaN occurs.
It's train.py
 while True:
      tf_loss, tf_global_step, _ = session.run([model.loss, model.global_step, model.train_op])
      accumulated_loss += tf_loss
      if math.isnan(tf_loss):
            print current doc_key.        << but.. I dont have an idea to work this line.

Can you give me some advice on this?

I'm AFK for the weekend. Off the top of my head, one way would be to add an integer document ID to input_props. You can then print or tf.Print that with the loss in both the dev and train loops. I can take a closer look when I get back.

@fairy-of-9
Hi I have a similar concern here. Can you check the code behavior when the offsets are feed into the "bucket_distance" function. I think the negative values will be a problem.

@mandarjoshi90
Thanks a lot!
@freesunshine0316
I will check the function on Monday!

Hi,
Thanks @mandarjoshi90 and everyone for sharing your efforts with us.
I have a short question regarding training this model on another language, and I don't want to create a separate issue for this. Is it required to change the vocab.txt file and fill it with the chosen language's words? (I think this one is quite trivial :D, but this is my first experience using BERT/SpanBERT)


import error

Information
VIM version

:version
VIM - Vi IMproved 8.1 (2018 May 18, compiled May 18 2018 18:36:07)
MS-Windows 32 位图形界面版本 带 OLE 支持

Operating System:
Win 7 professional x64

What went wrong

when use pipenv , ale say [pylint] Unable to import
Reproducing the bug

my vimrc：
" Plug-w0rp/ale "
let g:ale_echo_msg_error_str = 'E'
let g:ale_echo_msg_warning_str = 'W'
let g:ale_echo_msg_format = '[%linter%] %s [%severity%]'
let g:airline#extensions#ale#enabled = 1
let g:ale_sign_error = 'E'
let g:ale_sign_warning = 'W'
let g:ale_python_auto_pipenv=1
" Check Python files with flake8 and pylint.
let b:ale_linters = ['flake8', 'pylint']
" Fix Python files with autopep8 and yapf.
let b:ale_fixers = ['autopep8', 'yapf']
" Disable warnings about trailing whitespace for Python files.
let b:ale_warn_about_trailing_whitespace = 0
let g:ale_python_auto_pipenv = 1
let pipenv_venv_path = system('pipenv --venv')

I try set let g:ale_python_auto_pipenv = 1 and let pipenv_venv_path = system('pipenv --venv').
it also happend.
then i set set PYTHONPATH='mypath\Scripts\python.exe' in the dos
then i run vim pipenv run gvim
in the gvim , run echo $PYTHONPATH , the results is right.
but the ale also tell me [pylint] Unable to import
so i don't know how to solve it
:ALEInfo

This isn't something that can be fixed in ALE. If it's a matter of setting environment variables, they should be set appropriately.


Not Working

Output:
[2020-10-20 22:03:13.238] [recordLogger] [info] Created d3d11 device from 0
[2020-10-20 22:03:13.238] [recordLogger] [info] found 3 displays
[2020-10-20 22:03:13.238] [recordLogger] [error] desktopdiplication is unsupported on current desktop mode

I have 3 monitors, but I also tried it with one, and it still didn't work.

it looks like this error code DXGI_ERROR_UNSUPPORTED  from microsoft api.
https://docs.microsoft.com/en-us/windows/win32/api/dxgi1_2/nf-dxgi1_2-idxgioutput1-duplicateoutput
from their docs:
"DXGI_ERROR_UNSUPPORTED if the created IDXGIOutputDuplication interface does not support the current desktop mode or scenario. For example, 8bpp and non-DWM desktop modes are not supported. If DuplicateOutput fails with DXGI_ERROR_UNSUPPORTED, the application can wait for system notification of desktop switches and mode changes and then call DuplicateOutput again after such a notification occurs. For more information, refer to EVENT_SYSTEM_DESKTOPSWITCH and mode change notification (WM_DISPLAYCHANGE).
"

From https://docs.microsoft.com/en-us/windows/win32/api/dxgi1_2/nn-dxgi1_2-idxgioutputduplication
"
A collaboration application can use IDXGIOutputDuplication to access the desktop image. IDXGIOutputDuplication is supported in Desktop Window Manager (DWM) on non-8bpp DirectX full-screen modes and non-8bpp OpenGL full-screen modes. 16-bit or 32-bit GDI non-DWM desktop modes are not supported.
"

Try to determine these params for your system.
Also which OS version do you use?

Windows 10, and I don't know but OBS studio doesn't seem to work for me also. Is there any way I could solve this?

Check these display params to see if desktop duplication supported or not. Also, I think its possible to change them.
Idk how to check or change them. You will need to google it

I have the displays on extended mode, but I can set them to duplicate.

No, modes here means not extended/duplicated

They are talking about bits per pixel and DWM enabled/disabled

Read my first comment in this issue

Ok, I tested it on a different pc, it worked, so im not going to bother solving it anymore.


Use cssnano instead of clean-css => reduce minified CSS by 8.6% (4.9% gzipped)

Minified size
Minified gain
Minified + zip size
Minified + zip gain

clean-css
150,996b
-
20,648b
-

cssnano
137,984b
8.6%
19,628b
4.9%

@vanduynslagerp According to this benchmark clean-css is much faster and it's just as good at CSS minification.

I think the benchmark use Bootstrap 3.
I didn't measure the execution time, but I'm not sure it's relevant anyway, as you wouldn't minify when you dev, only to push a new version.
In terms of file size I did the measure myself with the actual code current on the branch v4-dev.

Ref #20324.

This needs rebasing because of the new build system

Closing given this is based on Grunt.


MH-13028: Clean up mockup

This will update the mockup in the following ways:

Reducing the event data to the most relevant (see 3474586a5c184ecd1f1f7b15432d1be2209b2c74)
Addition of two tiny binary files to correctly showcase video editor

Things which are WIP ought to have the onhold tag.  Makes life easier to sort out what's actually ready for review :)

In general, even better would be to prepare the patch first and only then create the pull requests. That way, they do not get mixed up with things ready to be reviewed. Feel free to keep this though. That's no hard requirement. Thanks for working on this at all :D

@lkiesow The patch is now ready for review. To best test this: Run grunt serve without this patch and play around a little. Then merge (while grunt serve is still running) this PR und hit the refresh page on your browser. Things should "feel" better now. In particular the video editor ;-)

@jaysuz, would you mind me quashing the commits when I do the merge?

@lkiesow not at all, please go ahead 👍

The mockup is still far from being perfect, but it is much better than it was before. Thanks for the patch → merged


small fixes in vit-kedqr app

We added new release for vit-kedqr (migrated from go to rust). As a side effect parameters syntax changed.

Thx for the update. Merged it.


[DRAFT][Workers] Document Brotli compatibility flag, Fetch API compression and passthrough support

This flag will have a default compatibility date once https://github.com/cloudflare/workerd/pull/708 has been merged. Adds documentation for the flag and describes the role of the Accept-Encoding header in the Fetch API, as well as how compressed data passthrough can be achieved.

@irvinebroque this is a rewritten version of https://github.com/cloudflare/cloudflare-docs/pull/9519.  There's one aspect I need to confirm internally before this is ready for review. Looking forward to discuss any questions/concerns you have once that's done!


fix: Fix delete token cache from disk

In function unlinkAsync in file /src/util.js, we are calling function fs.unlink( path, callback ), but options param was provided, then this error raised when clear token:
Callback must be a function. Received {}

So we need to remove options param to make it works.

Coverage: 86.341%. Remained the same when pulling 395017c3caafffc18d6703eee3821e6f2bdd97e8 on fix-token-clean-cache into e006ddcb78b9bf24574aee3c55e18fb431fc737e on main.


Naive implementation of fragment data structure for newcomers

Describe your problem
As titled, to delivery better getting started experiences for users who want to dig into the graph data structure in vineyard.
Additional context
Add any other context about the problem here.

Closing as not need anymore and we have already finished pages about how to add custom C++/Python data types in documentation.


Allow POSTing image

Sorry for my incompetence, but why is POSTing explicitly forbidden?
For me it'd be way easier to POST the image to be transformed.

imagor is designed for transforming images on public endpoints. Utilizing the POST method here raises significant security concerns, making it unsuitable for public requests.
However, it's worth noting that the POST method can be appropriate between private microservices.
This could be a feature considered for implementation, though it should be made opt-in through configuration. And the security implications must be effectively managed.

You mean that the URL of the image to be transformed is filtered according to the configuration,
and POSTing would allow any image to be transformed?
So, either opt-in in configuration as "unsafe-POST", or require the same HASH method for POST-ing:
allow POSTing to base-url/HASH only, and check that HASH is the same as the uploaded file's hash ?

POSTing means no image path, while security hash requires image path to be in place.
So opt-in for POSTing means unsafe only.
POSTing also means bypassing Storage & Result Storage.
All in all POSTing requires a pretty big change to the current architecture.

I still fail to understand the security implications of exposing pushing image via POST. How is pushing a byte array to an image processor via POST less secure than the image processor pulling the same image via public url via GET? If attacker wants to process an image, it will get in regardless.


fix(client, debug): query catch & debug types

Fixes https://github.com/prisma/engines-wrapper/issues/128
And https://prisma-company.slack.com/archives/C016KUHB1R6/p1628697119034200

Note: It would have been better I think to separate in multiple PR (for next time)
It seems this PR has changes:

fixing the catch finally execution on model queries
debug type
and something not mentioned in the description, changes about transaction

@millsp Can you detail the changes about transaction?

Is it worth including in this patch?
Is it fixing something?

Replaced by https://github.com/prisma/prisma/pull/8720


Tdr 1611 retrieve specific files metadata

Looks good. The selectedFiles aren't passed in from anywhere in the query yet, I guess that's coming later.


Popups instead of redirects due to the first response to API request is randomly returned as "200 text/html"

Hello,
There's an issue i've been struggling with in Inertia for almost a month now.
I've created a dockerized Laravel Inertia app with source code available at GitHub.
It runs on https://calendize.it/
I'm struggling with the API sporadically returning "code 200 text/html" responses, even when it's not supposed to.
This happens a lot on the login screen, where the login is basically broken.
I've created a topic at Laracasts with no feedback.
I've tried putting ray calls in the controllers - and they return correct responses (jsons or Inertia pages when requested).
I've tried disabling nginx caching.
But still - once in a while (right now, for example), the server suddenly starts responding with  "code 200 text/html" , which messes up the app - the email check won't work and the login won't neither (request content with a redirect is opened in a popup).

Update - the culprit was the gzip compression in my nginx config.
Nothing to do with Inertia!


change to conda-forge cpython instructions

ref https://github.com/scipy/scipy/issues/21479#issuecomment-2334947851
Based on the guidance at https://anaconda.org/conda-forge/python-freethreading.
I can't actually get this to work locally: _python_rc does not exist (perhaps a typo or a missing channel).

Adding the python_rc label works for me:
mamba create -n python-freethreading -c conda-forge/label/python_rc python-freethreading

thanks @lesteve ! updated to that

I'm also not able to run the conda create command locally. Not sure what broke since that text was added, but the conda-forge channel does seem to be working locally for me so let's go with that for now.


Lab 3 - Letter frequency implementation

Fixes #63
Changes proposed in this PR:

Write a function that returns a mapping of each letter to its frequency
Write a function that returns a sorted slice of strings with elements

Codecov Report

Merging #92 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #92   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          11     12    +1
  Lines         170    186   +16
=====================================
+ Hits          170    186   +16

Impacted Files
Coverage Δ

03_letters/madhavansu/main.go
100% <100%> (ø)

Continue to review full report at Codecov.

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


PHOENIX-6554 : Pherf CLI option long/short option names do not follow conventions

…w conventions}

Another PR created


Heapster connections to InfluxDB

I'm trying to spin up a heapster rc in our Kubernetes cluster. I have InfluxDB <IP_ADDRESS> running outside of Kubernetes. Each time I start the rc  I get the following error:
E0929 23:15:17.504255       1 driver.go:326] Database creation failed: Server returned (404): 404 page not found
. Retrying after 30 seconds
Any ideas?

I am using the following options in the rc file:
      command:
        - /heapster
        - --source=kubernetes:http://IP_Address?insecure=true&inClusterConfig=false
        - --sink=influxdb:http://IP_Address:8086

same issue here.

kubernetes/heapster:v0.18.1 as specified in https://github.com/kubernetes/heapster/blob/master/deploy/kube-config/influxdb/heapster-controller.yaml doesn't work with InfluxDB 0.9.4. I had to build heapster from master branch and create my own Docker image with it.

Sorry for the confusion. #634 should fix this issue.

fixed by #634


crash while uploading songs

my server is really old and slow. while uploading several songs at once, groovebasin crashed with this error:
/home/josh/dev/groovebasin/lib/player.js:507
    self.grooveEncoder.detach(function(err) {
                       ^
Error: detach: not attached
    at startEncoderDetach (/home/josh/dev/groovebasin/lib/player.js:507:24)
    at Player.detachEncoder (/home/josh/dev/groovebasin/lib/player.js:631:3)
    at timeout [as _onTimeout] (/home/josh/dev/groovebasin/lib/player.js:942:12)
    at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)

Is there anything in the log before that, such as "encoder attach failed"?

http://pastebin.com/0bAhqDfy

I don't have a lot of confidence that it is fixed, but I also don't see how this problem could happen. If it happens again, re-open and then I'll add a try/catch for the detach: not attached error.


row.save erroring out - [Error: options.uri is a required argument]

row.save is erroring out with the following error:
[Error: options.uri is a required argument]
The code is:
row.save(function (err) {

                         if (err != null) {
                             console.log(err);
                         }
                    }
                    );

more context? how was row created?
I think there is a known bug with creating new rows and then saving them.
Going to put some time in soon to fix some of the outstanding PRs

pasting the code below(cloned from another github code)

  function workingWithRows(step) {

        var tonecreds = require('./tone-credentials.json');

        var toneAnalyzer = watson.tone_analyzer(tonecreds);

        sheet.getRows({
            offset: 1,
            limit: 23
        }, function (err, rows) {
            rows.forEach(function (row) {
                // Concepts
                var parameters = {
                    //text: row.answer,
                    text: row.sometext,
					knowledgeGraph: 1
                };

                var concepts = '';

                alchemy_language.concepts(parameters, function (err, response) {

                    if (err) {
                        console.log('error:', err);
                    } else {

                        response.concepts.forEach(function (concept) {
                            concepts = concepts + concept.text + ' - ';
                        });

                        row.concepts = concepts;
						console.log("concepts: " + concepts);
                    }

                });

                toneAnalyzer.tone({
                    text: row.sometext,
                    sentences: false
                }, function (err, data) {
                    if (err) {
                        console.log(err);
                    }

                    var tones = data.document_tone.tone_categories[EMOTION].tones;

                    tones.forEach(function (tone) {

                        var score = Math.round(tone.score * 100);

                        switch (tone.tone_name) {

                        case 'Anger':
                            row.anger = score;
                            break;

                        case 'Disgust':
                            row.disgust = score;
                            break;

                        case 'Joy':
                            row.joy = score;
                            break;

                        case 'Sadness':
                            row.sadness = score;
                            break;

                        case 'Fear':
                            row.fear = score;
                            break;
                        }

                        console.log(tone.tone_name + ': ' + Math.round(tone.score * 100) + '%');
                    });

                     row.save(function (err) {

						if (err != null) {
                             console.log(err);
                         }
                    }
					);

                });
            })
        });
                }])

I think this may be due to a change in the Sheets API. On this line https://github.com/theoephraim/node-google-spreadsheet/blob/master/index.js#L501 self._links.edit is not there.
What do you think?

Any updates from this issue ?

Oh great! Will try on my end. Thanks!

Yep this worked for me. However any column in the row that is protected results in the row save returning a 400 with an error:
Error: HTTP error 400 (Bad Request) - You are trying to edit a protected cell or object. Please contact the spreadsheet owner to remove protection if you need to edit.

Hey guys, just catching up here.
So it seems that the issue is that permissions were not set correctly on the doc to be editable?
And another related issue if the rows are "protected".
So not an actual bug, but could probably have some better error messaging?
Is that right?

Yes in my case that was it. Wrong permissions, therefore the edit URL is not found. Better error messaging could alleviate that.
However having a single column being protected appears to throw an error stating I am editing a protected range. Is this API writing the entire object back without checking what has changed? If it tries to right each column back without checking if the value has changed it would produce the error found. However if it tracked changes to the internal object it uses to map to the row, and only wrote the changed values, it would work fine.
Thanks!

Yes it does include the entire row in the update. As far as I understood, this is how the "row based" API works for their API. I think it is designed this way to make sure there are not race conditions with concurrent updates. If some data is not correct, it throws an error.
To update the contents of an existing row, first retrieve the row to update, modify it as desired, and then send a PUT request, with the updated row in the message body, to the row's edit URL.
I also don't see anything in their docs about protected cells/ranges.
Things could have changed in v4 of the API which I haven't looked at just yet.

Ah ok. Removing protected rows is easy enough for my use. But looking forward to v4 when its ready.
Thanks!

I've just a published a new version of this module which is a complete rewrite using Google's V4 Sheets API (v3 is being deprecated on March 3, 2020).
Docs available here - https://theoephraim.github.io/node-google-spreadsheet
Please test it out and if you find that there is still a problem, reopen the issue.
Thanks! 😄


Compile localized translation when starting development environment

Types of changes
Please put an x in the box that applies

[ ] Bugfix
[ ] New feature
[ ] Refactoring
[ ] Breaking change (any change that would cause existing functionality to not work as expected)
[ ] Documentation Update
[x] Other:  development environment enhancement

Description
Compile localized translation when starting development environment
Steps to Test This Pull Request
Steps to reproduce the behavior:

Start the development environment with the enter_dev_env.sh script
Open localhost:8000/zh-hant/ with web browser

Expected behavior
Content of the webpage is displayed in Traditional Chinese.
Related Issue
See #761 for more context.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #823   +/-   ##
=======================================
  Coverage   76.14%   76.14%
=======================================
  Files          70       70
  Lines        2687     2687
=======================================
  Hits         2046     2046
  Misses        641      641

Continue to review full report at Codecov.

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


Promise it wont hurt

Completes all exercises in the "promise it won't hurt" tutorial, satisfying all specs listed under "Day 3 & 4"

PR was reviewed with Frankie and Ethan before merging.


python311Packages.bumps: 0.9.1 -> 0.9.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.bumps is: Data fitting with bayesian uncertainty analysis
meta.homepage for python311Packages.bumps is: https://bumps.readthedocs.io/
meta.changelog for python311Packages.bumps is: https://github.com/bumps/bumps/releases/tag/v0.9.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.2 with grep in /nix/store/r2yfwc7hbmmsfzgxccvin0v185f66zlk-python3.11-bumps-0.9.2
found 0.9.2 in filename of file in /nix/store/r2yfwc7hbmmsfzgxccvin0v185f66zlk-python3.11-bumps-0.9.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.bumps
python312Packages.bumps
sasview

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r2yfwc7hbmmsfzgxccvin0v185f66zlk-python3.11-bumps-0.9.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.bumps https://github.com/r-ryantm/nixpkgs/archive/0d5302887b6d963a5a88f54d7f057401f1f1a236.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0d5302887b6d963a5a88f54d7f057401f1f1a236#python311Packages.bumps

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r2yfwc7hbmmsfzgxccvin0v185f66zlk-python3.11-bumps-0.9.2
ls -la /nix/store/r2yfwc7hbmmsfzgxccvin0v185f66zlk-python3.11-bumps-0.9.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

6 packages built:

python311Packages.bumps
python311Packages.bumps.dist
python312Packages.bumps
python312Packages.bumps.dist
sasview
sasview.dist

Maintainer pings
cc @rprospero for testing.

Result of nixpkgs-review pr 293727 run on x86_64-linux 1

6 packages built:

python311Packages.bumps
python311Packages.bumps.dist
python312Packages.bumps
python312Packages.bumps.dist
sasview
sasview.dist


Build VKStatic.1 project faild on Visual Studio Ultimate 2013

Hi, i have some tricky compile error when building VKStatic.1 project, here's some information:
1>------ Build started: Project: VKstatic.1, Configuration: Debug Win32 ------
1>  trampoline.c
1>trampoline.c(112): error C2143: syntax error : missing ';' before 'const'
1>trampoline.c(113): error C2065: 'disp_table' : undeclared identifier
1>trampoline.c(113): warning C4047: '==' : 'int' differs in levels of indirection from 'void *'
1>trampoline.c(116): error C2065: 'disp_table' : undeclared identifier
1>trampoline.c(116): warning C4047: 'function' : 'const VkLayerDispatchTable *' differs in levels of indirection from 'int'
1>trampoline.c(116): warning C4024: 'loader_lookup_device_dispatch_table' : different types for formal and actual parameter 1
1>trampoline.c(120): error C2065: 'disp_table' : undeclared identifier
1>trampoline.c(120): error C2223: left of '->GetDeviceProcAddr' must point to struct/union
1>trampoline.c(122): error C2065: 'disp_table' : undeclared identifier
1>trampoline.c(122): error C2223: left of '->GetDeviceProcAddr' must point to struct/union
1>trampoline.c(122): warning C4033: 'vkGetDeviceProcAddr' must return a value
1>trampoline.c(127): error C2143: syntax error : missing '{' before '__stdcall'

The error was generate at file trampoline.c, line 108:
if (!strcmp(pName, "CreateDevice"))
 	return NULL;

 /* return the dispatch table entrypoint for the fastest case */
 const VkLayerDispatchTable *disp_table = *(VkLayerDispatchTable **)device;
 if (disp_table == NULL)
 		return NULL;

I change the code like this and it works:
if (!strcmp(pName, "CreateDevice"))
{
    return NULL;
}

or:
 if (!strcmp(pName, "CreateDevice"))
 	return NULL;;

I am not sure which reason cause this compile error, maybe there's a unknown bug of visual studio  Ultimate 2013(Version 12.0.21005.1 REL)? Hope you will help me to solve this problem, thx.

I just tried this with the latest VS 2013 (Version 12.0.31101.00 Update 4) and I don't see this issue.  I built both 32-bit and 64-bit.  Can you update your VS and verify with the latest update that all is well?

@MarkY-LunarG Thanks for your reply. I have already updated the Visual Studio to version 2013 update 5 and than the compile error fixed. I am sure now that this is a bug in old version of Visual Studio 2013(Stupid Microsoft). Thanks for your help.
by the way, Happy dragon boat festival...


Youtube API upload speed is extremely slow

Hi there!
We experience a 3-5x slowdown compared to uploading speed from browser. Disabling gzip does not help and I'm not sure how to fix this. Any ideas?

That's strange. I wonder what causes your big difference in upload speed. Today, I uploaded a 206,682,243 byte mp4 video via my Visual Basic 2013 (.NET 4.5) program using the YouTube API (Google.Apis.YouTube.v<IP_ADDRESS>.1560, Google.Apis.Core.1.10.0)  in 4 minutes 43 seconds. When I used the browser upload for the same file, it took 4 minutes 14 seconds. Close enough that I consider most of the difference to be the result of variances in Internet speed.

Try playing with the different values to chunk size, https://github.com/google/google-api-dotnet-client/blob/master/Src/Support/GoogleApis/Apis/[Media]/Upload/ResumableUpload.cs#L187. I'm not sure how the browser handles it, but the client library split the media to small pieces and upload them separately, then if there is an error with one of the pieces, we follow with a retry.

Read more about it, int our media upload documentation - https://developers.google.com/api-client-library/dotnet/guide/media_upload.

I've read that and my implementation is pretty close to that. I'll try different chunk size and let you know

Seems like playing with chunk size did its job. Thanks for your help

Do you want to share what you was the right ChunkSize for you?
Thanks!
Eyal

In youtube-upload (python) we were using a chunk size of 1M and people reported lots of 502 errors. With 4M apparently it's ok.
https://github.com/tokland/youtube-upload/issues/87


How to create new an agent?

I want to create new an agent from client. What should I do? Can you write example for me? Thank you very much.

Unfortunately this is impossible. Every agent should be created via web-console


Doesn't work with brew install'ed swift

Hello @jinmingjian
This is a great resource, the sde package for vscode! Sadly, I've run into an issue with the extension and it seems to be the location of sourcekite.
I configured the vscode extension setting as
    "swift.path.sourcekite": "swift build -Xswiftc -framework -Xswiftc sourcekitd -Xswiftc -F -Xswiftc /Library/Developer/Toolchains/swift-latest.xctoolchain/usr/lib -Xlinker -rpath -Xlinker /Library/Developer/Toolchains/swift-latest.xctoolchain/usr/lib"

But, there isn't actually any ~/Toolchains folder in my machine.
I used brew install swift to install the latest version which is ,
Apple Swift version 3.1 (swiftlang-802.0.53 clang-802.0.42)
Target: x86_64-apple-macosx10.9

Any suggestions on how to configure in this case.

I think that this thread might be useful in figuring out the problem
https://github.com/JohnSundell/Marathon/issues/65#issuecomment-301637374


Create RESTApi to search raster data

By geospatial bounds
By type of image (multispectral / hyperspectral)
By temporal bounds

we can provide / expose more options in the REST API - I would think that most of it could be key value pairs.

Girder 3 Geospatial Plugin
The Girder 3 geospatial plugin provides the following query fields:

latitude
longitude
radius
relation (one of Mongo's geospatial query operators https://docs.mongodb.com/manual/reference/operator/query-geospatial/)
bbox
geometry (geojson geometry for the query in wkt format)
geojson

where one of 4 possible searches is done: latitude/longitude/radius, bbox/relation, geometry/relation, geojson/relation.  Perhaps oddly, the bbox, geometry, and geojson parameters are treated identically (that is, each is the appropriate json representation for whatever Mongo expects for the relation operator).
The latitude/longitude/radius search is performed as {$geoWithin: {$centerSphere: [[longitude, latitude], radius/radius_of_earth]}}
As such, the REST search is a thin veneer over Mongo's queries.  There is no direct support for faceted search with key-value information.  There is no support for time-based queries.
ResonantGeoData Search
We want faceted search.  I think we want full facet control (e.g., the sensor is one of a list, the sensor altitude is between two values, etc.).  This could be one way to implement time-based searches.
We want to support the various available functions: ST_Equals, ST_Disjoint, ST_Intersects, ST_Touches, ST_Crosses, ST_Within, ST_Contains, ST_Overlaps, ST_Relate, plus ST_Distance with optional upper and lower bounds.  We want inputs to be either WKT, GeoJSON, or simple values like latitude/longitude/altitude.
If we want to support complex operations, we will need some way to construct such queries, which means either a custom query language or a more transparent way to expose SQL.  For instance, I could see ultimately wanting to know what regions have n or more datasets that cover them in some time.
For video datasets, I could see wanting to query if any frame intersects with some location or if all of the video so intersects.
I think we want to support a general search endpoint that can do complex searches and have simple search endpoints for specific use cases.  For instance:

GET geometa/search could take a JSON search parameter which could be a list of:
{'geometry': , 'function': , 'value': , 'operator': <defaults to '=', but would support <, <=, >, >=, !=, 'srid': }
or
{'key': , 'value': , 'operator': <this could also contain regex, etc.>}
But here we are creating our own query language, and it would be better to use an existing one that is feature rich enough to provide what we want.  If we allow nesting, then we can support and/or joining of the terms.  The main code is to convert this query to sql.

GET geometa/near_point would take latitude, longitude, altitude, radius, and optionally time, timespan.

Thoughts?

As a further thought, do we want to expose other functions?  For instance, would it every be useful to find data base on its area or perimeter?

In the Girder database assetstore plugin, we generically exposed non-mutating database functions.  The functionality of this borders on exposing SQL in general (which could be done as an optional where clause).  This has the virtue that a client can construct sophisticated queries, but the drawback that you need to ensure that whatever queries are used are non-mutating.  There are some database functions that mutate database state that could be allowed (calls to random, for instance, which change the state of the random number generator, but would permit an arbitrary sampling of data).

As a further thought, do we want to expose other functions? For instance, would it every be useful to find data base on its area or perimeter?

May be I think it will be hard to cover all of the use cases so our full faceted search API needs to be flexible so that additional parameters can be added in the future. I would n't add these in the first pass. thoughts @banesullivan @brianhelba

ST_Equals, ST_Disjoint, ST_Intersects, ST_Touches, ST_Crosses, ST_Within, ST_Contains, ST_Overlaps, ST_Relate, plus ST_Distance with optional upper and lower bounds.

This sounds about right.

We want inputs to be either WKT, GeoJSON, or simple values like latitude/longitude/altitude.

For the inputs WKT or GeoJSON would be a good start - I would just pick one for now and later support others but yeah this sounds like a good idea.

If we want to support complex operations, we will need some way to construct such queries, which means either a custom query language or a more transparent way to expose SQL. For instance, I could see ultimately wanting to know what regions have n or more datasets that cover them in some time.

My inclination is towards a transparent way to expose SQL - perhaps we can look into if something already exists along these lines. A custom query language seems does not seem best as it will be hard to maintain.

@manthey @banesullivan @brianhelba perhaps we can start with something small (a handful set of parameters and end points with options to expand) is probably be my wish list. @manthey if that sounds good, it would be great if we can list out those small set here on the github.

I think this can be marked done. As more endpoints are desired, we can open new issues for them like #152


How to add style for slider steps ?

Hi every body,
I am looking for a way to add custom style to slider steps (e.g: 3 steps)
for example a small circle in each step
Any solution for that ?
Regards

Check @sharcoux/slider 3.2.0, Tell me if it answer your needs.
I'm trying to make a cross platform project for RN and RNWeb.

This would be a great addition

@jimmi-joensson I agree!
I believe this feature should come in pair with #71.


I have router-id all set.


let rake create required directories and enable rake without arguments

Currently it is rather complicated to prepare the C track (see https://gist.github.com/7083c629a709b01f63fc). This patch prevents rather cryptic error messages like
ERROR: Config filepath [:project][:build_root]['build'] does not exist on disk.
rake aborted!

/vagrant/exercism/c/vendor/ceedling/lib/ceedling/configurator.rb:265:in `validate'
/vagrant/exercism/c/vendor/ceedling/lib/ceedling/setupinator.rb:30:in `do_setup'
/vagrant/exercism/c/vendor/ceedling/lib/ceedling/rakefile.rb:46:in `<top (required)>'
/vagrant/exercism/c/vendor/ceedling/lib/ceedling.rb:66:in `load'
/vagrant/exercism/c/vendor/ceedling/lib/ceedling.rb:66:in `load_project'
/vagrant/exercism/c/raindrops/rakefile.rb:7:in `<top (required)>'
(See full trace by running task with --trace)

and it enables the user to type rake instead of rake test:all.

Thanks!


Not parsing correctly directory path in Windows 10 using Git Bash

Output of restic version
restic 0.17.1 compiled with go1.23.1 on windows/amd64
What backend/service did you use to store the repository?
Local file system (Windows 10)
Problem description / Steps to reproduce
When trying to list a directory in git bash, the directory path is not correctly parsed.
I run the command:
$ restic ls latest /data/dir1

And get the error:
Fatal: All path filters must be absolute, starting with a forward slash '/'

These are the steps I followed to reproduce the error in Git Bash:
$ restic version
restic 0.17.1 compiled with go1.23.1 on windows/amd64

$ restic snapshots
repository 837309d1 opened (version 2, compression level auto)
ID        Time                 Host         Tags        Paths                                            Size
-------------------------------------------------------------------------------------------------------------
e8c98f4b  2024-09-19 17:21:06  Spectre-RFF              C:\Users\ricaf\OneDrive\Desktop\testRestic\data  0 B
9fee10a2  2024-09-19 17:31:42  Spectre-RFF              C:\Users\ricaf\OneDrive\Desktop\testRestic\data  16 B
440c30f6  2024-09-19 18:55:03  Spectre-RFF              C:\Users\ricaf\OneDrive\Desktop\testRestic\data  16 B
d94c664d  2024-09-19 18:59:43  Spectre-RFF              C:\Users\ricaf\OneDrive\Desktop\testRestic\data  16 B
-------------------------------------------------------------------------------------------------------------
4 snapshots

$ restic ls latest
repository 837309d1 opened (version 2, compression level auto)
[0:00] 100.00%  3 / 3 index files loaded
snapshot d94c664d of [C:\Users\ricaf\OneDrive\Desktop\testRestic\data] at 2024-09-19 18:59:43.0210503 -0600 CST by SPECTRE-RFF\ricaf@Spectre-RFF filtered by []:
/data
/data/dir1
/data/dir1/dummy5.md
/data/dummy1.md
/data/dummy4.md

$ restic ls latest /data
Fatal: All path filters must be absolute, starting with a forward slash '/'

$ restic ls latest //data
repository 837309d1 opened (version 2, compression level auto)
[0:00] 100.00%  3 / 3 index files loaded
snapshot d94c664d of [C:\Users\ricaf\OneDrive\Desktop\testRestic\data] at 2024-09-19 18:59:43.0210503 -0600 CST by SPECTRE-RFF\ricaf@Spectre-RFF filtered by [/data]:
/data
/data/dir1
/data/dummy1.md
/data/dummy4.md

$ restic ls latest //data/dir1
repository 837309d1 opened (version 2, compression level auto)
[0:00] 100.00%  3 / 3 index files loaded
snapshot d94c664d of [C:\Users\ricaf\OneDrive\Desktop\testRestic\data] at 2024-09-19 18:59:43.0210503 -0600 CST by SPECTRE-RFF\ricaf@Spectre-RFF filtered by [//data/dir1]:

$ restic ls latest //data//dir1
repository 837309d1 opened (version 2, compression level auto)
[0:00] 100.00%  3 / 3 index files loaded
snapshot d94c664d of [C:\Users\ricaf\OneDrive\Desktop\testRestic\data] at 2024-09-19 18:59:43.0210503 -0600 CST by SPECTRE-RFF\ricaf@Spectre-RFF filtered by [//data//dir1]:

Expected behavior
The correct result should be:
$ restic ls latest /data/dir1
repository 837309d1 opened (version 2, compression level auto)
[0:00] 100.00%  3 / 3 index files loaded
snapshot d94c664d of [C:\Users\ricaf\OneDrive\Desktop\testRestic\data] at 2024-09-19 18:59:43.0210503 -0600 CST by SPECTRE-RFF\ricaf@Spectre-RFF filtered by [/data/dir1]:
/data/dir1
/data/dir1/dummy5.md

Actual behavior
$ restic ls latest /data/dir1
Fatal: All path filters must be absolute, starting with a forward slash '/'

Do you have any idea what may have caused this?
It runs perfectly in WSL and in PowerShell, so the problem is when it runs on Git Bash.
Did restic help you today? Did it make you happy in any way?
Yes! I'm testing restic and definitely will start using it.

$ restic ls latest /data/dir1
Fatal: All path filters must be absolute, starting with a forward slash '/'

This is a conceptual problem of Git Bash, which blindly translates everything that might be a file path. That is /data is translated to something like C:\some\path\data before passing it to restic. You can set the environment variable DEBUG_LOG=restic.log to check the parameters that were actually passed to restic.
Judging from your experiments // seems to cause Git Bash to think that the string is not a file path and therefore not translate it. I don't think there's anything we can do about that in restic.

Closing as this is not a restic bug.


Make ContractDeployer public

It's required so I can use the contract defined in one file in tests in another file.

Fixed in f30e64620e5dd6987802bfef5a44a5829788c552


LiteLLM Improvements

Hi @joshpxyne,
Thanks for merging our PR for LiteLLM.
I'm one of the co-maintainers of the package. How can we make it better for you?

some code example would be super appreciated @krrishdholakia 😄

Anything we're missing?
https://docs.litellm.ai/docs/providers/openrouter
completion('meta-llama/llama-2-13b-chat', messages)

bump? @mrgoonie


Support for jakarta annotation

MariaDB4jService relies on javax.annotation.PostConstruct to start itself in a Spring environment.
With Spring 6 out and the migration to jakarta annotations, this is not working anymore

Salut, merci for this feedback; good to know. If this is important to you, please raise a Pull Request to contribute to this open source by fixing this problem. (I'm happy to help you learn how to do this, if required.)

Sure, i am happy to contribute! i will take a look in the coming days. Thank you

#669

@gaetannandelec-ibboost how is that PR coming along? 😸
FYI I've now fixed the (previously broken) build, so now is a great time to contrib a PR... 😄

Hello, sorry for the delay on this! i made the change on my personal github account but it overlapses #650 so i am not sure what is the best approach?
I am also getting a failed unit test : defaultExecutables(ch.vorburger.mariadb4j.tests.DBConfigurationBuilderTest)
I am trying to figure out

it overlapses #650 so i am not sure what is the best approach?

Small separate PRs are usually, if it's possible.
Or just wait for #650 to be resolved? I have a WIP Draft PR, something still NOK; I'll try to wrap that up perhaps next weekend.

I am also getting a failed unit test : defaultExecutables(ch.vorburger.mariadb4j.tests.DBConfigurationBuilderTest)

You could open a separate new issue about that, with more details?
Or if you suspect it's a local issue for you, it's not unheard of 🙂 to just go ahead and raise a (still Draft?) PR, for you to see if it would pass the CI on the project (I don't mind if you want to try that).

it's probably local, i need to look into it a bit more. Yes as part of the changes, i kind of went through #650 as well and made changes. I will isolate this to this ticket and make a small PR to start with. Thanks for your patience!

Added pull request for your review https://github.com/vorburger/MariaDB4j/pull/693 .
Unit tests are not working in windows but there is already a ticket for that. I was able to run them under linux so all good


'module' object has no attribute 'AlignmentFile'

Hello,
I'm doing a little testing with version 0.1.0 and I've run into an issue.
my command based on the svtyper usage statement:
svtyper -B<PHONE_NUMBER>63.bam -i<PHONE_NUMBER>63.bam_temp.vcf -o result.test.vcf

And the result:
Traceback (most recent call last):
  File "/uufs/chpc.utah.edu/common/home/ucgdstor/common/apps/ember.arches/svtyper/0.1.0/svtyper", line 1519, in <module>
    sys.exit(main())
  File "/uufs/chpc.utah.edu/common/home/ucgdstor/common/apps/ember.arches/svtyper/0.1.0/svtyper", line 1514, in main
    args.dump)
  File "/uufs/chpc.utah.edu/common/home/ucgdstor/common/apps/ember.arches/svtyper/0.1.0/svtyper", line 1152, in sv_genotype
    bam_list = [pysam.AlignmentFile(b, 'rb') for b in bam_string.split(',')]
AttributeError: 'module' object has no attribute 'AlignmentFile'

Which made me think that pysam was not installed but:
$ python
Python 2.7.3 (default, Mar 28 2013, 15:20:19)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pysam
>>>

And of course the usage statement works so it's finding pysam:
usage: svtyper [-h] -B BAM [-i VCF] [-o VCF] [-l JSON] [-m INT] [-n INT] [--split_weight FLOAT] [--disc_weight FLOAT] [--debug] [--dump STR]
svtyper: error: argument -B/--bam is required

Any ideas?
--Shawn

Hi Shawn,
Pysam updated their variable names, I believe in version 0.8.3 or so. Can you check what version of pysam you're on?
python
Python 2.7.11 |Continuum Analytics, Inc.| (default, Dec  6 2015, 18:08:32)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
Anaconda is brought to you by Continuum Analytics.
Please check out: http://continuum.io/thanks and https://anaconda.org
>>> import pysam
>>> pysam.__version__
'0.9.0'

>>> import pysam
>>> pysam.__version__
'0.7.5'
>>>

yeah 0.7.5 won't work with the newer SVTyper. Try upgrading pysam. this will also enable CRAM support

I'll update and close if it resolves.

Updated to 0.9 and the issue went away.  Thanks for your help.


Story: ElectricPowerQualitySummary Entity and Repository

This story also includes a ElectricPowerQualitySummaryService, ElectricPowerQualitySummaryRepositoryTest, and database table(s) to support the entity class.

See 4ef7e281386e3d4f1d1e4954a2ae2a2587df13e3


Recipes: not indicated which models are downloaded

When choosing/selecting a model for an AI App in the Recipes Catalog, the menu displaying the models does not indicate which models are already on disk/downloaded.  In my case below, two of the models haven already been downloaded but I need to go back to the Models menu to check which of them they are.
Displaying downloaded models in the AI App menu would help me pick the ones I want to try out.
AI App models menu

Models menu

Not sure to clearly understand: do you want a visual indicator that the model is downloaded or do you want to filter the list ?

Not sure to clearly understand: do you want a visual indicator that the model is downloaded or do you want to filter the list ?

Apologies for being vague.  I am looking for a visual indicator in the list, so I can see directly which model is on disk.

Looking at the screenshots in https://github.com/containers/podman-desktop-extension-ai-lab/pull/714, we could add the same green icon so we have a consistent experience?

Looking at the screenshots in #714, we could add the same green icon so we have a consistent experience?

Yes, but the size of the table is smaller, and we may want to move away at some point of having duplicates table ?

Yes, but the size of the table is smaller, and we may want to move away at some point of having duplicates table ?

The icon could be smaller in a smaller list.

My argument: starting a Recipe should have a similar UI than creating a Playground or Model Service, with a list of models to select from, with one by default

Ah, I see what you mean.  So it should be drop-down menu instead?

My argument: starting a Recipe should have a similar UI than creating a Playground or Model Service, with a list of models to select from, with one by default

Ah, I see what you mean. So it should be a drop-down menu instead?

Maybe, I am not sure about the UX design, but it feel weird to me that the playground and the model service have a didicated page for creation, where the recipe is a mixte of selecting a model in a tab, and then clicking on a play button.

I like the drop-down menu but it lacks potentially useful information.  The recipes list shows the repository and license but not the size.

I think this is indeed inconsistency: https://github.com/containers/podman-desktop-extension-ai-lab/issues/623#issuecomment-2022798730
In some cases, that would be fine (the dropdown), but otherwise, yeah that is something we should be careful.
cc @ekidneyrh


line number is barely visible

Can you please fix it? thanks

Hmm....yeah I'll update it soon. Btw do you use relative number?

Yes, i use number and relative number both, maybe that's why

Yeah, maybe but I tried setting both of them

You can see this

Any updates on this? I was trying to make the line number just like the screenshot on the readme, but I have no idea how theming works in vim.

The screenshot had neovim mate.

I am using neovim though, and the line number is barely visible still

Can you please show a screenshot?

Here, with set number relativenumber:

now only set number

and now only set relativenumber

Seems like it's a relativenumber thing, but only in the current line.
It seems to be the same problem that the person who created the issue had.
Sorry for the delay, kind of forgot to check github notifications...

Uhmm can you please update the plugin? The recent fixes might have fixed this one too


More parked cars?

CARLA version: master
Platform/OS: Linux
Problem you have experienced: More parked cars in a map
What you expected to happen: Configurable variable that let's me add more number of parked cars
Steps to reproduce:
Other information (documentation you consulted, workarounds you tried):
Is there a way to add more parked cars to a map in Carla? In the real world the distribution of parked cars is different from what is seen in the maps.

I guess you could just write a small script which spawns a car without an autopilot and give them coordinates where you want to have them spawned.
something like this:
try:         ego_vehicle = world.get_blueprint_library().filter('vehicle.audi.etron')[0]          EGOtransf = carla.Transform(carla.Location(x=TPosX, y=TPosY, z=TPosZ), carla.Rotation())         SpawnEgo = world.spawn_actor(ego_vehicle, EGOtransf)         print("\nSpawning Target at ", EGO_sp)         input("\nPress Enter to terminate the Target") finally:         lidar_sen.destroy()         client.apply_batch([carla.command.DestroyActor(x) for x in Props])

Hi @truncs,
Right now we don't have any script to do that. But we have it in mind for future releases.


Update base commit of code coverage

Thanks Yifan for pointing out the issue on the test coverage workflow
The code coverage is comparing a merge commit to the common commit of a PR and the target branch. This will involve changes between this common commit and the latest commit of the target branch. This update will switch the common commit of the PR to the latest commit on the target branch.
Update indent of the workflow.

TLDR: this is to avoid problems, for example, in #8267 where the report of coverage diff contained changes for FirebaseFunctions and FirebasePerformance, which is unexpected since the PR didn't contain any code change related to them.
The diff for FirebaseFunctions and FirebasePerformance in #8267 actually comes from #8194 and #8265 respectively. The test for PR #8267 ran on the commit d3b4bd (as shown in GitHub Actions log), which merged 48df806 into 3ab732b. If we compared d3b4bd with 3ab732b, the resulted diff would be reflecting precisely the code change contained in the PR. However, as in the report we compared against 76d0144, an ancestor of 3ab732b, the diff included code change between 76d0144 and 3ab732b (outside of #8267), as listed in commit history.
48df806: the last commit pushed by the author to the PR #8267
3ab732b: the last commit on merge target branch, in our case master, picked by GitHub Actions at the time of CI run
@paulb777 @ryanwilson
One more problem in #8267 is that, the diff report also contains some number for FirebaseDatabase, FirebaseDynamicLinks and FirebaseFirestore. I suspect that these diff actually comes from flaky test execution, meaning even though the same test passed for both runs, but the code path executed were different, which resulted in different coverage number calculated. Do you know how Gran and I can deal with it?

@yifanyang Thanks for investigating. Some of the flakes are due to networking in the tests that is not deterministic run to run. We would need to update the tests to mock the networking so they become consistent.


Update current release

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit ff506a3dca9d706afff5fb967d27e0be66aeb770
https://deploy-preview-3360--calico.netlify.com


Replace duplicate validator detection mechanism

I was confused about when exactly allow_reuse=True was required, so I looked into the implementation. As far as I can tell, the motivation behind the feature is outlined in https://github.com/pydantic/pydantic/issues/312#issuecomment-449875744.
I think the same goal can be accomplished more cleanly with the metaclass's __prepare__ method, without requiring the library user to set allow_reuse=True.
Change Summary
This PR replaces the "duplicate validator" detection mechanism.
Before, there was a set of qualified validator names, and if a validator was added with a qualified name that already existed in the set, this was detected as a duplicate.
The new mechanism is to directly detect when a validator is re-assigned within the class body, by using a custom dict subclass as the class namespace. This is more convenient because it works without the user needing to specify allow_reuse=True, while still detecting validators with duplicate names.
I think it would be best to merge/implement this for pydantic V2, and retire the allow_reuse parameter for V2. However, if you want this for V1, this PR essentially deprecates the allow_reuse parameter, which no longer has any effect. It can be merged into V1 with the appropriate documentation changes.
Related issue number
None

Checklist

[x] Unit tests for the changes exist - covered by the existing test_duplicates.
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable - not relevant unless you plan to merge this to V1. For V2 this would just be removing the documentation for allow_reuse.
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
If we're not merging to V1 then we can skip change file check.
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review

This will have to wait for V2 by which time I suspect most of this code will be completely replaced.
If therefore delay any further work on this.
I also think we should make this a warning not an error in V2.

No problem. Thanks @samuelcolvin !

I think the principle here could still be very useful, but this will need to be rebased on main for V2. It might be easier to restart it given how much has changed.

The plan is to take this logic and move it onto the new code in main.

assigned both @hramezani and @adriangb, whoever gets here first, please work on it.

@nzig we're taking your (excellent) idea and using it in https://github.com/pydantic/pydantic/pull/5398. Please feel free to take a look there and give any feedback you have. Thanks for the contribution and sorry it took so long to get to it!

@adriangb  Looks good. Thanks for getting this in 😄 🚀 !


Update Pages “WhatIsTheBestTermiteControlTreatmentBarrierPage”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
f4a107564cd4b5de797eab06b54ec29a61f9c962

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/655ab2559cd0f30008adc314


Error when trying to add Cortana channel

I'm getting this error when I try to add the Cortana channel to my bot. This error appears when I click on the Cortana icon in the 'channels' blade for my bot settings in the Azure portal:
Sorry, something went wrong :-(
Trace Id : a08b1165-4b5d-465f-8fd2-d4691cfda350

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

ID: 155fd9a4-a390-eb9e-5f1a-fae7a2ede084
Version Independent ID: 21c420dc-db37-f5d5-ac38-c843055e195a
Content: Connect a bot to Cortana - Bot Service
Content Source: articles/bot-service-channel-connect-cortana.md
Service: bot-service
Product: bot-framework
GitHub Login: @RobStand
Microsoft Alias: kamrani

I'm not able to repro this. If you still need help, reach out to support engineering team on Stackoverflow.


Added SpaceX Website Clone

Closes: #407

Title : SpaceX Clone
Name: : Amruta Jayanti
Idenitfy yourself: :  GSSOC

Describe the add-ons or changes you've made 📃
I added SpaceX-Website-Clone
How Has This Been Tested? ⚙

I tested it locally .
Screenshots 📷

Type of change ☑

What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney I made the changes . Please approve . Its showing conflicts must be resolved

@Avdhesh-Varshney I resolved the conflicts also . Please approve .


travis: Split out frontend/backend/static-analysis more clearly

We want to accomplish a few things that may be somewhat interrelated or raise interesting tradeoffs:

[x] Add tools/test-tools to travis.
[ ] Split out lint-all so it can do backend-only or frontend-only (and maybe overlap as needed for tools that blur the line and are fast...but we should probably just split those tools as well--check-templates comes to mind)
[x] [Decided to skip] Possibly make sure various travis scripts bootstrap themselves by running tools/test-tools and other lint-like things on the tools themselves, so that devs don't get confusing errors from broken tools.

I think it'd definitely be worth making the linter run separately against the backend vs. frontend code.  I think I might do it as lint --frontend runs against everything in package.json, static/, and templates/, and the other one runs against everything else in the repo.
We'd just use these options in Travis, to end the confusion we get sometimes with developers ignored "backend" failures in their "frontend only" changes, that are actually caused by lint errors in their frontend changes.
The third bullet I think isn't a priority, so I checked it and marked it as not going to happen.

Fixed via #6170.


checkpoint reshape_text - partial fix

@FedeClaudi, I think reshape_text is not very robust. I give up now since I spent too much time on this.

indexing into generic string with possible non-unit byte characters should be exerted with caution and using nextindex(...) and friends (see https://docs.julialang.org/en/v1/manual/strings/#Unicode-and-UTF-8) - it's always a mess working with those strings;
01_test_text_utils.jl passes now with some limitations, and added test cases;
all others test need manual fixes when comparing output strings ==> all tests green now.

The
    for i in 5:10
        width = 2^i
        for offset in -10:10
            txt = '.'^(2width + offset)
            rt = reshape_text(txt, width)
            len = length.(split(rt, '\n'))
            # @show length(txt) width rt len
            @test all(len[1:(end - 1)] .== width)
            @test len[end] == (offset > 0 ? offset : width + offset)
        end
    end

test covers fixing the issue mentioned at https://github.com/FedeClaudi/Term.jl/pull/102#issuecomment-1153611730.

Codecov Report

Merging #107 (3acd78a) into v4 (a2a4659) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##               v4     #107      +/-   ##
==========================================
- Coverage   88.74%   88.69%   -0.05%
==========================================
  Files          32       32
  Lines        1910     1902       -8
==========================================
- Hits         1695     1687       -8
  Misses        215      215

Impacted Files
Coverage Δ

src/Term.jl
66.66% <100.00%> (-4.77%)
:arrow_down:

src/_text_reshape.jl
100.00% <100.00%> (ø)

src/panels.jl
95.77% <100.00%> (-0.28%)
:arrow_down:

Continue to review full report at Codecov.

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

I give up now since I spent too much time on this.

Of course, I appreciate your help.

I think reshape_text is not very robust

Reshaping text has been a major headache.. I've changed the way it works multiple times but yeah it's still not great. It needs to:

work decently efficiently
insert new lines at spaces without breaking words (unless the word is too long)
ignore ANSI and markup style info
ensure that style is carried over across multiple lines without bleeding into other content (e.g. when horizontally stacking two pieces of text..)

and of course the way strings are handled in Julia is a pain...

...non-unit byte characters...

which includes e.g. Panel's borders, so this happens all the time. But I've found that using nextindex on strings that don't have such characters gives some unexpected results... I don't understand why Julia handles strings the way it does instead of allowing indexing to access individual characters.

all tests green now

You're a hero! I'm very impressed with all the changes you've been making!

Reshaping text has been a major headache..

Gave me some too :laughing: .

I don't understand why Julia handles strings the way it does instead of allowing indexing to access individual characters.

Very special yes :hot_face: .

But I've found that using nextindex on strings that don't have such characters gives some unexpected results

Let's reserve that for future improvements, this limitation causes strings such as ต้าอ่วยวาทกรรมอาว์เซี้ยว กระดี๊กระด๊า ช็อปซาดิสต์โมจิดีพาร์ตเมนต์ อินดอร์วิว สี่แยกมาร์กจ๊อกกี้ โซนี่บัตเตอร์ฮันนีมูน ยาวีแพลนหงวนสคริปต์ แจ็กพ็อตต่อรองโทรโข่งยากูซ่ารุมบ้า บอมบ์เบอร์รีวีเจดีพาร์ทเมนท์ บอยคอตต์เฟอร์รี่บึมมาราธอน  to not respect the width parameter when split using reshape_text.

that was working for me before

Was it ? The split lines in https://github.com/FedeClaudi/Term.jl/blob/a2a46591f79f87b6269bfc26aebc5098411aefd4/test/01_test_text_utils.jl#L159 have length = [38, 39, 41, ...], thus not respecting width = 33 given as arg.

mmm the tests were passing, we maybe the tests weren't doing what I wanted them to do 😄
either way I agree that's not a high priority for now

Okay, looks good. Happy to merge when you're ready!

Happy to merge when you're ready!

Just bumping the coverage across the repo, and we should be good to go in a few minutes ...

Good to merge when CI is green :tada: !


Support GWD

rotated_retinanet_hbb_gwd_r50_fpn_1x_dota.py
AP50: 0.6888047290917456
AP75: 0.39804467910688085
mAP: 0.4001945828110586

GWD should be marked as completed.

The performance of GWD should also be added in README.md.

This branch has conflicts that must be resolved
Conflicting files
python/jdet/models/losses/__init__.py


chore(RHTAPWATCH-101): add contributing guide

Add a file to guide developers with setting up their dev environments and explains procedures and code review guidelines.

Waiting with review until all pending comments are taken care of

LGTM


Configurable Metrics prefix

Hi! I saw issue 615 and figure'd it would be something pretty easy to do in a morning.
All the tests still pass, and I've written the update so that it wouldn't break anyone's metrics
that are relying on the hardcoded "pool" being added to the pool name as the base of the
metrics name.

Coverage decreased (-0.3%) to 75.125% when pulling 11055d1281a7fa8acc3bcd9b15ad9031d5d8291d on EdgeCaseBerg:Metrics-Prefix into 39aa95eef464fc3f16a7953dbc92f0f6b91e666c on brettwooldridge:dev.

Seems to look good.
With Metrics 4.x in the future HikariConfig would also need an API to provide metric tags because in Metrics 4.x (currently their master branch) their metrics name will be represented by an instance of MetricName (https://github.com/dropwizard/metrics/blob/master/metrics-core/src/main/java/io/dropwizard/metrics/MetricName.java) which is immutable. This class supports attaching custom tags to a metric so that metric names do not have to be relatively long just because tags are encoded directly in the metric name like I described in my issue.
So with Metrics 4.x you could do:
Map<String, String> tags = ....;
tags.put("customer", "example.com");
tags.put("host", "cluster-host-01");
tags.put("jvm-instance", "1");

// with "metricPrefix" just being, e.g. "connection-pool" or "hikaricp".
registry.register(new MetricName(metricPrefix + ".activeConnections", tags), someGauge);


after updating js-controller 3.x TypeError: adapter.getForeignStateAChangedsync is not a function

After i have upgraded the js-controller 3.x - moma is permanently restarting
js-controller: 3.0.14
moma: 1.2.5
LOG output:
`

moma.0
2020-04-22 11:32:17.088
error
(1382044) TypeError: adapter.getForeignStateAChangedsync is not a function at Interval2.logError (/opt/iobroker/node_modules/iobroker.moma/lib/Interval.js:66:17) at process._tickCallback (inte

moma.0
2020-04-22 11:32:17.087
error
(1382044) uncaught exception: adapter.getForeignStateAChangedsync is not a function

`

fixed in 1.2.6


是不是不支持https开头的视频？？

不支持 https开头的视频，E/IJKMEDIA: https://xxxxxx: Protocol not found

https在默认的ijkplayer中是关闭的，你要打开响应的配置，重新编译ijkplayer，才能播放

i am also not able to get https to work. any solution?

@harshamv ijkplayer  openssl, I never config it before,I have no useful suggestion for you.


How can I use space as the split character?

data-splitchars="[ ]" doesn't work.

Turns out data-splitchars="[\s]" works.


Remove default index from searchapiclient

Summary
We are removing the default index name from the Search API Client and requiring it to be passed explicitly. This is because we are moving away from a single index called 'g-cloud' and moving towards an index-per-framework where the index name is the framework slug. Given this, we can get the index name programmatically and don't need to statically define it anywhere.
Bump version to 9.0.0
Ticket
Required work under https://trello.com/c/Hlq5mzAy/619-save-a-search-and-create-a-project

Ugh, coveralls!