Update icon and title audio classification

Can you verify the classification happening in the app? It's picking up a lot of random things that aren't happening, and not picking up things like "speech" or "whistling" when that is happening. Thanks.

Can you verify the classification happening in the app? It's picking up a lot of random things that aren't happening, and not picking up things like "speech" or "whistling" when that is happening. Thanks.

I will check it now

I updated the branch to change TensorFlowLiteTaskAudio to TensorFlowLiteSwift.
Please help me check again.
Thanks you.

I am still seeing wrong results consistently with this. Just whistling into the phone and not getting 'whistling'.

Hi @PaulTR
I checked the model label file and the speech_commands label doesn't have whistling and speech. Please help me check.
labels:
background
down
go
left
off
on
right
stop
up

It shouldn't be the speech one with whistling - it's the other one that
isn't registering it.
On Mon, Oct 28, 2024, 8:25 PM Tuan Mai A. @.***> wrote:

Hi @PaulTR https://github.com/PaulTR
I checked the model label file and the speech_commands label doesn't have
whistling and speech. Please help me check.
labels:
background
down
go
left
off
on
right
stop
up
—
Reply to this email directly, view it on GitHub
https://github.com/google-ai-edge/litert-samples/pull/38#issuecomment-2443034810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR2C37VZLKMMS7DO4GCTYTZ53W2JAVCNFSM6AAAAABPRGAHCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBTGAZTIOBRGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

You can see the MediaPipe sample to see what it should look like. They use
the same models.
On Mon, Oct 28, 2024, 8:26 PM Paul Trebilcox-Ruiz @.***> wrote:

It shouldn't be the speech one with whistling - it's the other one that
isn't registering it.
On Mon, Oct 28, 2024, 8:25 PM Tuan Mai A. @.***>
wrote:

Hi @PaulTR https://github.com/PaulTR
I checked the model label file and the speech_commands label doesn't have
whistling and speech. Please help me check.
labels:
background
down
go
left
off
on
right
stop
up
—
Reply to this email directly, view it on GitHub
https://github.com/google-ai-edge/litert-samples/pull/38#issuecomment-2443034810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR2C37VZLKMMS7DO4GCTYTZ53W2JAVCNFSM6AAAAABPRGAHCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBTGAZTIOBRGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I am using label.txt file extracted from tflite file using python code, I think label is added wrongly to metadata.
vocal = zipfile.ZipFile('./demo/speech_commands.tflite').extractall('label')

Not comparing the speech commands model - can you verify this all with the standard audio classification model (the one with 'music', 'whispering', 'whistling', etc.)? Thanks.

I checked several sources and it seems the models used are different so the labels are different too.
https://github.com/tensorflow/examples/blob/master/lite/examples/sound_classification/ios/SoundClassification/Model/labels.txt
https://www.tensorflow.org/datasets/catalog/speech_commands

You can compare the iOS sample to the Android sample. They're using this model: https://storage.googleapis.com/ai-edge/interpreter-samples/audio_classification/android/yamnet.tflite (I copied the same one into the ios folder) and returning the correct results.

Hi Paul,
iOS using this yamnet model:
https://storage.googleapis.com/ai-edge/interpreter-samples/audio_classification/ios/yamnet.tflite

Right, and they should be the same model.
On Tue, Nov 5, 2024, 7:28 PM Tuan Mai A. @.***> wrote:

Hi Paul,
iOS using this yamnet model:
https://storage.googleapis.com/ai-edge/interpreter-samples/audio_classification/ios/yamnet.tflite
—
Reply to this email directly, view it on GitHub
https://github.com/google-ai-edge/litert-samples/pull/38#issuecomment-2458604789,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR2C36QCC2E372XTHZJL3DZ7F5ELAVCNFSM6AAAAABPRGAHCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYGYYDINZYHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@PaulTR I removed the speech commands model, I think we can use only yamnet model now.


Add steps to check system version before Memory Pit

This pull request resolves #118 and should supersede it.
Steps to note down one's system version as well as a beautiful screenshot as to where it is was added to make sure people actually get the correct Memory Pit download instead of doing a system update.

I have also amended the Memory Pit download links to use the system version region lettering, since now that we are actually telling people to take note of the system version what people will need will be easier to identify this way.

I have also amended the Memory Pit download links to use the system version region lettering, since now that we are actually telling people to take note of the system version what people will need will be easier to identify this way.


Join field breaks when put on collection with versions

Describe the Bug
Join field breaks when put on a collection with versions. For example, Pages have a relation to Posts. Posts join to Pages. Both collections have versions. This error shows up [ Server ] Error: column pages_rels._posts_v_id does not exist
It could be that versions on both are required for the bug to present itself. Join works if the collection being joined TO (Pages in this example) has versions and Posts doesn't.
Link to the code that reproduces this issue
https://github.com/alexanderbnelson/payload-example
Reproduction Steps

Log into admin
Click on the posts collection

View the code for the posts collection config.
https://github.com/alexanderbnelson/payload-example/blob/main/src/collections/Posts/index.ts
Which area(s) are affected? (Select all that apply)
area: core
Environment Info
Binaries:
  Node: 20.11.0
  npm: 10.9.0
  Yarn: 1.22.19
  pnpm: 9.13.2
Relevant Packages:
  payload: 3.0.1
  next: 15.0.3
  @payloadcms/db-postgres: 3.0.1
  @payloadcms/email-nodemailer: 3.0.1
  @payloadcms/graphql: 3.0.1
  @payloadcms/live-preview: 3.0.1
  @payloadcms/live-preview-react: 3.0.1
  @payloadcms/next/utilities: 3.0.1
  @payloadcms/payload-cloud: 3.0.1
  @payloadcms/plugin-form-builder: 3.0.1
  @payloadcms/plugin-nested-docs: 3.0.1
  @payloadcms/plugin-redirects: 3.0.1
  @payloadcms/plugin-search: 3.0.1
  @payloadcms/plugin-seo: 3.0.1
  @payloadcms/richtext-lexical: 3.0.1
  @payloadcms/translations: 3.0.1
  @payloadcms/ui/shared: 3.0.1
  react: 19.0.0-rc-65a56d0e-20241020
  react-dom: 19.0.0-rc-65a56d0e-20241020
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:37:36 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12

Just a heads up, I'm still getting the same error after upgrading to 3.1.0. Using the same reproduction.

Hey Alexander, can you please ensure you are on the latest version? Delete node_modulels / lockfile / .next and reinstall. Because I can't reproduce it, with versions + drafts on both sides + hasMany relationship.
I'm sure I had this specific error in my tests and it was gone after.

I used this config:
import type { CollectionConfig } from 'payload'

export const versionsSlug = 'versions'

export const Versions: CollectionConfig = {
  slug: versionsSlug,
  fields: [
    {
      name: 'category',
      relationTo: 'categories',
      type: 'relationship',
    },
    {
      name: 'categoryVersion',
      relationTo: 'categories-versions',
      type: 'relationship',
    },
    {
      name: 'categoryVersions',
      relationTo: 'categories-versions',
      type: 'relationship',
      hasMany: true,
    },
  ],
  versions: {
    drafts: true,
  },
}

import type { CollectionConfig } from 'payload'

import { versionsSlug } from './Versions.js'

export const categoriesVersionsSlug = 'categories-versions'

export const CategoriesVersions: CollectionConfig = {
  slug: categoriesVersionsSlug,
  fields: [
    {
      name: 'relatedVersions',
      type: 'join',
      collection: versionsSlug,
      on: 'categoryVersion',
    },
    {
      name: 'relatedVersionsMany',
      type: 'join',
      collection: versionsSlug,
      on: 'categoryVersions',
    },
  ],
  versions: {
    drafts: true,
  },
}


activesupport: Update the type of Array.wrap

At present, Array.wrap will be return an empty tuple for untyped value because it matches to the first method_type: (nil) -> [].
In the type world, the behavior of an empty tuple is different from an empty array.  For example, calling a enumerable method will cause type an error:
app/app.rb:18:28: [error] Type `bot` does not have method `to_s`
│ Diagnostic ID: Ruby::NoMethod
│
└ Array.wrap(foo).map { |e| e.to_s }
                              ~~~~

This changes the return type of Array.wrap for nil value to Array[untyped].
refs: https://github.com/ruby/gem_rbs_collection/pull/683

@nickjer What do you think about this change?

/merge

Thank you for reviewing! @ksss @nickjer


error in SCGLUEModel.fit() got an unexpected keyword argument 'edge_weight'

Hi, Zhijie:
When I used the example from this part (https://github.com/gao-lab/GLUE/blob/master/experiments/TripleOmics/s02_glue.py), I encountered an error. Upon examining the code that encodes this part, I discovered that we do not have these parameters. I am unsure if this is a problem with the version I am using or if there is another issue.
I would greatly appreciate your response. Thank you and I look forward to hearing back from you.
Dan

Thanks for the report! The case studies were conducted with v0.2.0, but the argument has since been removed in newer versions. We now require the name of edge attributes to be fixed (i.e., "weight" for edge weight, "sign" for edge sign). You may safely remove the arguments edge_weight="weight" and edge_sign="sign" and the model should work fine.


Fix misleading indent lint error message

Why
The error message was hardcoded to 4 so read incorrectly when a custom indent size was used.

:man_facepalming: Thank you, Jeremy!


Imitate java.net.*

See contribution example: https://github.com/memory-agape/php-java/pull/35

Moved.


[BEAM-9827] Ensure minimum watermark hold is computed across all keys

For computing the current output watermark we need to compute the minimum
watermark hold across all watermark holds. We maintain an in-memory view of all
watermark holds because iterating over all keys is an expensive operation which
we only want to do when restoring from a checkpoint, not on every watermark.
The watermark view may not be in sync with its backing managed state. This
change corrects this by maintaining a priority queue with all watermark holds
and adding additional tests.

Run Flink ValidatesRunner

Run Java Flink PortableValidatesRunner Streaming

Run Nexmark Flink

This fixes the flaky test in BEAM-9827.

👍 This change makes sense. I'm little bit unsure about memory requirements here, but hopefully storing an offset per key / window should be ok.

Run Flink ValidatesRunner

Run Java Flink PortableValidatesRunner Streaming

Run Nexmark Flink

Run Portable_Python PreCommit

Thanks for the review @dmvk!

CC @tweise


Support for Web Components

First of - thanks for the great work on this!
It would be amazing to also support Web Components (Lit, Stencil) to connect.

I work on a web component design system.
The way it's built, consumers initialize the entire library before bootstrapping their client side app, so all published custom elements are available everywhere (consumers don't explicitly import/initialize individual components/custom elements).
The output of the React API is very close to what I need. The biggest issue, right now is that I'd need to be able to customize and/or remove the import line above the markup snippet.  Additionally, some of our Figma components are implemented via semantic HTML using published CSS classes (no custom elements or components, just CSS).

Hey, thanks for your interest in Code Connect!
We’re planning to add support for more frameworks in the near future. We can’t say yet exactly which frameworks or when, but it’s helpful for us to hear from the community to help us decide where to focus, so please feel free to add a 👍 to this issue if you are also interested in support for web components. I will leave this issue open to track interest.
Code Connect is also designed to be extensible, and the community will be able to create their own plugins to support frameworks and languages which we don’t natively support. More details about how to build these plugins will be coming soon!
It's interesting what you say about the React support being very close to what you would need @CITguy. It sounds like if we had the ability to support plain HTML (i.e. not specify a React component in the figma.connect call) and the ability to manually specify import statements, this might work for you?

+1 one that feature request! Also working on a design system built on web components using Stencil.js! Would be a highly appreciated addition!

+1

Hey @tomduncalf-figma!
Thanks for the response on this issue.  Like others here, I'm very excited to use Code Connect with our Design System being built with Lit Web Components.

It sounds like if we had the ability to support plain HTML (i.e. not specify a React component in the figma.connect call) and the ability to manually specify import statements, this might work for you?

I would say that yeah, this is true! Being able to specify the import statement and then supporting HTML would cover most cases, I believe. Here's an example of a button component in Lit:
import<EMAIL_ADDRESS>
// And then usage:

<my-button variant="secondary" disabled>Button</my-button>

A more complex example may be Shoelace's Tree components:
import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
<sl-tree>
  <sl-tree-item>
    Deciduous
    <sl-tree-item>Birch</sl-tree-item>
    <sl-tree-item>
      Maple
      <sl-tree-item>Field maple</sl-tree-item>
      <sl-tree-item>Red maple</sl-tree-item>
      <sl-tree-item>Sugar maple</sl-tree-item>
    </sl-tree-item>
    <sl-tree-item>Oak</sl-tree-item>
  </sl-tree-item>

  <sl-tree-item>
    Coniferous
    <sl-tree-item>Cedar</sl-tree-item>
    <sl-tree-item>Pine</sl-tree-item>
    <sl-tree-item>Spruce</sl-tree-item>
  </sl-tree-item>

  <sl-tree-item>
    Non-trees
    <sl-tree-item>Bamboo</sl-tree-item>
    <sl-tree-item>Cactus</sl-tree-item>
    <sl-tree-item>Fern</sl-tree-item>
  </sl-tree-item>
</sl-tree>

There are some concepts that are Lit-specific like property expressions but for most Design Systems, I think supporting string and boolean attributes (HTML!) would be a great start.

+1 to this
I use StencilJS alongside a Storybook instance. The Storybook instance is set up to use Web Components which uses lit. Either using the StencilJS files or the Storybook stories would be great. Thank you!

+1 from the Carbon Design System team, we are currently exploring this in React, but also support Web Components.

+1 From the Microsoft Fluent Design System

It's interesting what you say about the React support being very close to what you would need @CITguy. It sounds like if we had the ability to support plain HTML (i.e. not specify a React component in the figma.connect call) and the ability to manually specify import statements, this might work for you?

basically... yes 😄

+1 from Meteomatics team 👋
Also for Storybook & Stencil setup.
Thank you, folks!

+1 from the Maersk Design System team too

+1 from Mastercard's Design System team!

Any news on that? @tomduncalf-figma
+1 from ABB Process Automation

Sounds like this should have been first, total no-brainer.

1 for the British Airways Design System 🛫

+1 from the Breuninger's Design System team

+1 from Migros Multibrand Design System Team

Mui Would be amazing :)

+1 from the Grit Design System's team from Progressive Leasing. We exclusively use StencilJS.

+1 from Zywave's Booster Design System. We exclusively use Lit!

We are happy to announce that we’ve released Code Connect v1.1.1, which includes a preview of support for HTML-based frameworks (including Web Components, Angular and Vue).
We’d love to get your feedback on this, so please take a look at the docs and try it out, and please reach out to us with any questions or feedback.
Please note that while HTML support is in preview, we reserve the right to make changes to the API, although we hope to not have to make any major changes.

+1 Also working on a design system built on web components using Stencil.js! Would be a highly appreciated addition!


Could not find module

Hi, this is my first time making an issue, so go easy on me!
So I installed the project through npm and got this error. Then I also tried to install it with bower and still got the same error. I'm on ember cli 1.13.1.
Error: Could not find module 'ember-new-computed' imported from 'ember-anchor/mixins/controller-support'

I'll fix this in the blueprint. For now, just run
ember install ember-new-computed

and you should be good to go


amazing-graceful-fs + fixups for 0.8

meant to be used in combination with #45 adding 0.8 support
0.8 uses streams1 so it does not have an open method. I simply copied and pasted the constructor contents.
https://github.com/joyent/node/blob/v0.8.22/lib/fs.js#L1221-L1283
the lines changed in the constructors are legacy-streams.js: 59 and 110 -- to use the fs.open from gfs.

This seems like it might work.  I'll try to take a look later today or this weekend.
Another approach I'd thought of was to hijack the emit method and handle EMFILE.  But this should probably work, as well.  0.8 is frozen, so it's unlikely that relying on internals is going to be too dangerous.

no no the emit method hack is a horrible idea!
I had an even worse one... toString the constructor, replace the fs.open with open
then, eval it back into a function :)
I was afraid of the criticism, haha
I didn't really think about it when I pushed this.
but, do you want me to rebase this branch against master ?

Nah, I can just cherry-pick the relevant bit.

awesome!


fail to run the inference demo

run the demo script, and get the following error. @yaolug  @Efficient-Large-Language-Model could you please help me?,
python  llava/eval/run_vila.py     --model-path Efficient-Large-Model/Llama-3-VILA1.5-8b     --conv-mode llama_3     --query "<image>\n Please describe the traffic condition."     --image-file "demo_images/av.png"
Setting pad_token_idtoeos_token_id:128001 for open-end generation. Traceback (most recent call last):   File "/media/md1/users/york/workspace/VILA/llava/eval/run_vila.py", line 162, in <module>     eval_model(args)   File "/media/md1/users/york/workspace/VILA/llava/eval/run_vila.py", line 124, in eval_model     output_ids = model.generate(   File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context     return func(*args, **kwargs)   File "/media/md1/users/york/workspace/VILA/llava/model/language_model/llava_llama.py", line 171, in generate     outputs = self.llm.generate(   File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context     return func(*args, **kwargs)   File "/opt/conda/lib/python3.10/site-packages/transformers/generation/utils.py", line 1764, in generate     return self.sample(   File "/opt/conda/lib/python3.10/site-packages/transformers/generation/utils.py", line 2924, in sample     if stopping_criteria(input_ids, scores):   File "/opt/conda/lib/python3.10/site-packages/transformers/generation/stopping_criteria.py", line 132, in __call__     return any(criteria(input_ids, scores) for criteria in self)   File "/opt/conda/lib/python3.10/site-packages/transformers/generation/stopping_criteria.py", line 132, in <genexpr>     return any(criteria(input_ids, scores) for criteria in self)   File "/media/md1/users/york/workspace/VILA/llava/mm_utils.py", line 298, in __call__     outputs.append(self.call_for_batch(output_ids[i].unsqueeze(0), scores))   File "/media/md1/users/york/workspace/VILA/llava/mm_utils.py", line 279, in call_for_batch     raise ValueError( ValueError: Keyword tensor should have 2 or 3 dimensions, got 1

I got the same error

Sorry, there is an issue when moving the repo. I just fixed it. Could you try again?
Make sure you pass
--conv-mode=hermes-2 for 40b
--conv-mode=v1 for 13b
--conv-mode=llama_3 for 8b
--conv-mode=v1 for 3b

Yes! it is working now! Thank you!

git pull the code, and solved the problem. thanks!

git pull the code, and solved the problem. thanks!

Hi there,
Our team has moved our VILA to a new location: NVLabs/VILA. We kindly request that you update your references to the old repository location with the new one (e.g, git clone / pipeline integration). This will ensure that you have access to the latest updates, improvements, and bug fixes for VILA project. Current repo will be archieved in one week (Jul 10th) and made private after one month (Aug 4th).
Thank you for your understanding and continued support. If your issue still exists, feel free to open a new one in the new place. We appreciate your patience and cooperation during this transition.
Best regards,
VILA Team


Add Sphinx templates for data description etc. to cookiecutter template

Add a template page for data description, project description (this could be on main page), workflow etc.

Done


feat(RELEASE-537): add option to skip pyxis repo publishing

If pyxis.skipRepoPublishing is set to true in the data file, the publishing of the repo in Pyxis will be skipped.

/test release-pipelines-e2e-suite


New PR to test SignCLA at 2019-08-08 12:33:08.324231959 -0700 PDT m=+3.669873892

Body of PR

indiv-pass-fork-staging: test succeeded


HHH-13872 - Make the Java Stream close the underlying ScrollableResultsIterator upon calling a terminal operation

https://hibernate.atlassian.net/browse/HHH-13872

@NathanQingyangXu @dreab8 @sebersole Would you mind taking a look at this PR?
This PR adds two benefits:

It allows us to pass the closeHandler when creating a derived Stream, IntStream, LongStream, DoubleStream as a result of a mapToInt, mapToLong, etc method on the original Stream
We can close the underlying ResultSet after calling a terminal operation since the Stream is not reusable afterward. If we don't do that, we the ResultSet will be open until the Session gets closed or the or the currently running transaction is committed or rolled back.

Do we have the concern that this feature will break some existing client code which assumes it is their responsibility to close the stream whenever they want? Seems not.
It might be a good idea to put some thing in our wonderful user guide to explain this cool feature to avoid unnecessary bug reporting or suchlike.

@NathanQingyangXu I added a test case for the close method and it works just fine. I think that in case this feature gets merged, it's a good idea to update the User Guide to explain how the JPA 2.2 Stream results work in Hibernate, and why it's a good idea to call a terminal operation sooner than later.

@NathanQingyangXu @sebersole I pushed the new commit based on our discussion.
I'm now thinking of adding a new test case that will run on Java 9+ only so that I can verify the outcome of the takeWhile and dropWhile methods. I want to make sure the Stream is closed for those methods as well when executing the terminal operation.

There are some check-style failures.  Other than that, +1

I run the check phase to fix those issues as well.

I also added test cases for takeWhile and doWhile.

I updated the User Guide as well. I'll rebase and merge it tomorrow.

@NathanQingyangXu I rebased the branch from master and squashed all previous commits. If you can merge it, I'd really appreciate it. Thanks.

@NathanQingyangXu I rebased the branch from master and squashed all previous commits. If you can merge it, I'd really appreciate it. Thanks.

I have no such rights for I am a community contributor only. But I guess Steve will do that soon.

I updated the User Guide as well. I'll rebase and merge it tomorrow.

Thanks for the User Guide update. I used to finish a big PR to improve on it: https://github.com/hibernate/hibernate-orm/pull/3174.
One thing I really love it is the testing code and easy verification. That is brilliant.
Seems lots of work needs to be done after v6 is released.


Generated the Api Management SDK

Should probably wait for this issue [https://github.com/Azure/azure-rest-api-specs/issues/893](Api Management Plans: Json Unmarshalling Bug) to be solved

Hi @devcfgc, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


squid:S1066 - Collapsible "if" statements should be merged

This pull request is focused on resolving occurrences of Sonar rule
squid:S1066 - Collapsible "if" statements should be merged
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S1066
Please let me know if you have any questions.
George Kankava

Automated message from Dropbox CLA bot
@georgekankava, it looks like you've already signed the Dropbox CLA. Thanks!

lgtm


Fix broken pdf redirects

Previously if a pdf url returned a redirect the pdf would not be proxied correctly. This PR fixes a couple issue that were causing this:

The pdf url that was being passed from the python app was incomplete (it was missing query params).
The Content-Type header request was not following redirects so if the first redirect did not respond with a pdf Content-Type the request would be routed to legacy via.
The nginx redirect url replacement was incorrectly replacing the url with the previous /_id/ endpoint instead of the new /proxy/static/ endpoint.
The CORS header was being appended to rather than overwritten inside nginx when proxying the third-party pdf which lead to an invalid value in the CORS header when the third-party pdf server also returned a CORS header.

I believe this coverage failure is just due to the xfail tests and it can be ignored.

Part of why coverage is failing is that the second assert in the xfail test is never being hit because the first assert fails. Coverage is kind of right that this is a problem--the xfail test is not currently testing that the second assert in fact fails. It can be fixed using parametrize:
diff --git a/tests/unit/py_proxy/views_test.py b/tests/unit/py_proxy/views_test.py
index 3039193..67a5388 100644
--- a/tests/unit/py_proxy/views_test.py
+++ b/tests/unit/py_proxy/views_test.py
@@ -131,8 +131,13 @@ class TestPdfRoute:
         assert result["pdf_url"] == f"{nginx_server}/proxy/static/{pdf_url}"

     @pytest.mark.xfail
+    @pytest.mark.parametrize(
+        "query_param", ["via.request_config_from_frame", "via.open_sidebar"]
+    )
     @httpretty.activate
-    def test_does_not_include_via_query_params_in_pdf_url(self, pyramid_config):
+    def test_does_not_include_via_query_params_in_pdf_url(
+        self, pyramid_config, query_param
+    ):
         url = (
             "http://thirdparty.url/foo.pdf?param1=abc&param2=123"
             "via.request_config_from_frame=lms.hypothes.is&via.open_sidebar=1"
@@ -143,8 +148,7 @@ class TestPdfRoute:

         result = views.pdf(request)

-        assert "via.request_config_from_frame" not in result["pdf_url"]
-        assert "via.open_sidebar" not in result["pdf_url"]
+        assert query_param not in result["pdf_url"]

     def test_pdf_passes_client_embed_url_to_renderer(self, pyramid_config):
         request = Request.blank("/pdf/https://thirdparty.url/foo.pdf")

Now all the lines in the xfail test are being hit.

The second piece of missing coverage is due to a similar reason: again an xfail test has lines that aren't being reached because an assert that comes before those test lines fail. I think again coverage is kind of right here: since the assert isn't the last thing in the test, part of the test isn't being run, so we don't actually know that the test would pass if the code was correct and the xfail was removed.
In this case, as well as adding another parametrize, we need to remove the callback and move the assert to the end of the test, which also nicely simplifies the test code:
diff --git a/tests/unit/py_proxy/views_test.py b/tests/unit/py_proxy/views_test.py
index 3039193..a82326f 100644
--- a/tests/unit/py_proxy/views_test.py
+++ b/tests/unit/py_proxy/views_test.py
@@ -252,37 +252,33 @@ class TestContentTypeRoute:
         assert result.location == redirect_url

     @pytest.mark.xfail
+    @pytest.mark.parametrize(
+        "query_param", ["via.request_config_from_frame", "via.open_sidebar"]
+    )
     @httpretty.activate
-    def test_does_not_pass_via_query_params_to_thirdparty_server(self, pyramid_config):
-        def request_callback(request, uri, response_headers):
-            assert "via.request_config_from_frame" not in uri
-            assert "via.open_sidebar" not in uri
-            return [200, response_headers, "{}"]
-
+    def test_does_not_pass_via_query_params_to_thirdparty_server(
+        self, pyramid_config, query_param
+    ):
         request = self._create_request(
             request_url="/https://thirdparty.url?"
             "via.request_config_from_frame=lms.hypothes.is&via.open_sidebar=1",
             thirdparty_url="https://thirdparty.url",
             content_type="application/pdf",
             pyramid_config=pyramid_config,
-            request_callback=request_callback,
         )

         views.content_type(request)

+        assert query_param not in httpretty.last_request().path
+
     # pylint: disable-msg=too-many-arguments
     def _create_request(
-        self,
-        request_url,
-        thirdparty_url,
-        content_type,
-        pyramid_config,
-        request_callback=None,
+        self, request_url, thirdparty_url, content_type, pyramid_config,
     ):
         httpretty.register_uri(
             httpretty.GET,
             thirdparty_url,
-            body=request_callback or "{}",
+            body="{}",
             adding_headers={"Content-Type": content_type},
         )
         request = Request.blank(request_url)

You need to add xfail_strict = True so that the tests will actually fail if an xfail test passes:
diff --git a/tox.ini b/tox.ini
index b547c0b..4d9a924 100644
--- a/tox.ini
+++ b/tox.ini
@@ -3,6 +3,7 @@ filterwarnings =
     error
     ; Suppress warnings about an import of `imp` by Pyramid
     ignore:the imp module is deprecated in favour of importlib
+xfail_strict=true

 [tox]
 envlist = tests

You need to add raises=AssertionError to the xfails to make sure that they're failing because the assertion fails and not because something else is going wrong. I think one of your xfail tests is actually failing for a different reason other than the assertion.
diff --git a/tests/unit/py_proxy/views_test.py b/tests/unit/py_proxy/views_test.py
index 3039193..ed01f6d 100644
--- a/tests/unit/py_proxy/views_test.py
+++ b/tests/unit/py_proxy/views_test.py
@@ -130,7 +130,7 @@ class TestPdfRoute:

         assert result["pdf_url"] == f"{nginx_server}/proxy/static/{pdf_url}"

-    @pytest.mark.xfail
+    @pytest.mark.xfail(raises=AssertionError)
     @httpretty.activate
     def test_does_not_include_via_query_params_in_pdf_url(self, pyramid_config):
         url = (
@@ -251,7 +251,7 @@ class TestContentTypeRoute:

         assert result.location == redirect_url

-    @pytest.mark.xfail
+    @pytest.mark.xfail(raises=AssertionError)
     @httpretty.activate
     def test_does_not_pass_via_query_params_to_thirdparty_server(self, pyramid_config):
         def request_callback(request, uri, response_headers):

Can you remove all the @httpretty.activate's? They don't do anything, the global httpretty_ fixture already ensures that it's activated for all tests:
diff --git a/tests/unit/py_proxy/views_test.py b/tests/unit/py_proxy/views_test.py
index 3039193..ebbe374 100644
--- a/tests/unit/py_proxy/views_test.py
+++ b/tests/unit/py_proxy/views_test.py
@@ -131,7 +131,6 @@ class TestPdfRoute:
         assert result["pdf_url"] == f"{nginx_server}/proxy/static/{pdf_url}"

     @pytest.mark.xfail
-    @httpretty.activate
     def test_does_not_include_via_query_params_in_pdf_url(self, pyramid_config):
         url = (
             "http://thirdparty.url/foo.pdf?param1=abc&param2=123"
@@ -214,7 +213,6 @@ class TestContentTypeRoute:
             ),
         ],
     )
-    @httpretty.activate
     def test_redirect_location(self, pyramid_config, requested_path, expected_location):

         request = self._create_request(
@@ -236,7 +234,6 @@ class TestContentTypeRoute:
             ("text/html", "http://via.hypothes.is/https://thirdparty.url"),
         ],
     )
-    @httpretty.activate
     def test_redirects_based_on_content_type_header(
         self, pyramid_config, content_type, redirect_url
     ):
@@ -252,7 +249,6 @@ class TestContentTypeRoute:
         assert result.location == redirect_url

     @pytest.mark.xfail
-    @httpretty.activate
     def test_does_not_pass_via_query_params_to_thirdparty_server(self, pyramid_config):
         def request_callback(request, uri, response_headers):
             assert "via.request_config_from_frame" not in uri

I think there's a problem with the httpretty_ fixture copied from LMS, which suggests that the LMS one has the same problem as well. The httpretty_ fixture registers responses, and these sometimes seem to override the responses registered by the individual tests. It can be fixed like this:
diff --git a/tests/unit/py_proxy/conftest.py b/tests/unit/py_proxy/conftest.py
index ae20b8f..307de26 100644
--- a/tests/unit/py_proxy/conftest.py
+++ b/tests/unit/py_proxy/conftest.py
@@ -50,24 +50,7 @@ def httpretty_():
     all with mock responses. This handles requests sent using the standard
     urllib2 library and the third-party httplib2 and requests libraries.
     """
-    httpretty.enable()
-
-    # Tell httpretty which HTTP requests we want it to mock (all of them).
-    for method in (
-        httpretty.GET,
-        httpretty.PUT,
-        httpretty.POST,
-        httpretty.DELETE,
-        httpretty.HEAD,
-        httpretty.PATCH,
-        httpretty.OPTIONS,
-        httpretty.CONNECT,
-    ):
-        httpretty.register_uri(
-            method=method,
-            uri=re.compile(r"http(s?)://.*"),  # Matches all http:// and https:// URLs.
-            body="",
-        )
+    httpretty.enable(allow_net_connect=False)

     yield

I think the content_type() view is forgetting to add the via.* query params to the Via URL when it redirects to Via to proxy an HTML file.

I don't see an issue with this so I'm not sure why it's not auto-logging in.

Re-tested and it seems to work now. I think there might have been a problem with my local client

Let's get this deployed, then I think we may be ready to switch LMS over to it


Correct usage with extract-text-webpack-plugin?

I'm investigating using this in combination with extract-text-webpack-plugin to turn a large number of EJS files directly into HTML files without producing JavaScript bundles along the way. I've got a solution working, but it doesn't feel ideal — I'd love your input on a better approach. Here's the relevant pieces of my webpack config:
const glob = require('glob');
const ExtractTextPlugin = require('extract-text-webpack-plugin');

const ejsExtract = new ExtractTextPlugin(2, '[name]');

const entries = {};

glob.sync('./ejs/*.ejs').forEach((path) => {
  const fileName = path.match(/(\w+).ejs/)[1];
  entries[fileName + '.html'] = path;
});

const webpackConfig = {
  entry: entries,

  output: {
    path: __dirname + '/dist',
    filename: '[name]' // will be initialized as a JS file, but overwritten by ExtractTextPlugin afterwards
  },

  module: {
    loaders: [
      {
        test: /\.ejs$/,
        loader: ejsExtract.extract(['raw', 'ejs-html'])
      }
    ]
  },

  plugins: [
    ejsExtract
  ],

  resolve: {
    extensions: ['', '.js', '.scss', '.ejs']
  },

  ejsHtml: {
    some_data: 'goes here'
  }
};

(yes, this is a bit crazy, feel free to close if you don't want to go down this rabbit hole)

The more research I'm doing into extract-text-webpack-plugin, the more I'm thinking this is the closest I'm going to get to a "decent" solution. Sorry for the noise!

Sorry for failing to reply earlier. I know this is closed, but I might take a look at it later and see if I can be of any help. I'm just a bit preoccupied right now.

I think your intuition is right that you are unlikely to find a very elegant solution to your problem. Webpack,  at its core, is intended to combine all your static assets into one or a few JavaScript bundles. You can, of course, deviate from that core function using plugins and loaders. But the more you deviate, the more convoluted your solution is likely to become. Since you want to produce a lot of files without any JavaScript bundles, you can expect an inelegant and somewhat hacky configuration file.
That said, if you can handle just one JavaScript bundle – and it would be unusual not to have one if using Webpack – you might do better to forgo the extract-text-plugin, raw-loader, and glob module, and to use the file-loader along with a require.context instead. Your Webpack configuration file will include something like this:
entry: 'src/entry.js',
output: {
  path: `${__dirname}/dist`,
  filename: '[name].bundle.js'
},
module: {
  loaders: [
    {
      test: /\.ejs$/,
      loader: 'file?name=[name].html!ejs-html'
    }
  ]
},
ejsHtml: {
  // ...
}

The above configuration will produce a .html in your output directory for every .ejs file you require(). However, if you have a large number of such files, you don't want to require() all of them; instead, in entry.js, you can use a require.context, like so:
var req = require.context('.', true, /\.ejs$/);
req.keys().map(req);

This will effectively require() all .ejs files in the src directory and any subdirectories. You will, of course, be left with an entry.bundle.js file. If you are hoping to avoid that, then some inelegant hack will still be needed. But if you don't want even one JavaScript bundle in your output, then you might want to reconsider whether Webpack is the right tool to begin with.


Run a script on behalf of a user with a JWT token

Is your feature request related to a problem? Please describe.
we are creating a service that requires updating several resources in the users azure subscription. in order to do so, we have setup an azure ad application that has the proper permissions (https://management.azure.com/user_impersonation). when we request a token on behalf of the user for managing resources we are able to use the rest api with the obtained token. However, currently there is no supported way to run the cli with a valid external JWT token although the cli itself operates with them (stored in the accessTokens.json file).
Describe the solution you'd like
an additional login option that allows you to specify a JWT token. in order for this to work, refresh tokens shouldn't be required and shouldn't be preemptively refreshed on calls. An alternative would be to disable refreshing tokens with a config setting.
Describe alternatives you've considered
we are currently using service principals to run the commands, however this means that however invokes the script has the same permissions as the service principal. We would like to run the commands under the logged in user.
we have tried injecting the jwt and a refresh token into the accessTokens file run the script but it fails on refreshing the token
Additional context
this is what the debug log looks like:
az_command_data_logger : command args: resource list --debug
metadata file logging enabled - writing logs to 'C:\Users\***\.azure\commands'.
Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument.<locals>.add_subscription_parameter at 0x044342B8>]
Event: CommandInvoker.OnPostArgumentLoad []
Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument.<locals>.add_ids_arguments at 0x04434270>, <function register_cache_arguments.<locals>.add_cache_arguments at 0x04434930>]
Event: CommandInvoker.OnCommandTableLoaded []
Event: CommandInvoker.OnPreParseArgs [<function _documentdb_deprecate at 0x04C2EAE0>]
Event: CommandInvoker.OnPostParseArgs [<function OutputProducer.handle_output_argument at 0x03B6A9C0>, <function CLIQuery.handle_query_parameter at 0x03B87C00>, <function register_ids_argument.<locals>.parse_ids_arguments at 0x044348E8>, <function handler at 0x04A9C198>]
Getting management service client client_type=ResourceManagementClient
msrest.universal_http.requests : Configuring retry: max_retries=4, backoff_factor=0.8, max_backoff=90
msrest.async_paging : Paging async iterator protocol is not available for GenericResourceExpandedPaged
attempting to read file C:\Users\DidierCaron\.azure\accessTokens.json as utf-8-sig
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - Authority:Performing instance discovery: ...
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - Authority:Performing static instance discovery
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - Authority:Authority validated via static instance discovery
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - TokenRequest:Getting token from cache with refresh if necessary.
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - CacheDriver:finding with query keys: {'_clientId': '...', 'userId': '...'}
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - CacheDriver:Looking for potential cache entries: {'_clientId': '...', 'userId': '...'}
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - CacheDriver:Found 1 potential entries.
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - CacheDriver:No resource specific cache entries found.
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - CacheDriver:Found an MRRT token.
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - CacheDriver:Returning token from cache lookup, AccessTokenId: b'***', RefreshTokenId: b'***'
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - CacheDriver:Acquiring new access token from MRRT token.
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - TokenRequest:called to refresh a token from the cache
adal-python : 183cb04f-7ab5-43df-b296-9ec973978f76 - TokenRequest:Getting a new token from a refresh token
urllib3.connectionpool : Starting new HTTPS connection (1): login.microsoftonline.com:443
urllib3.connectionpool : https://login.microsoftonline.com:443 "POST /***/oauth2/token HTTP/1.1" 400 419
cli.azure.cli.core.util : AADSTS26000: The provided access grant requires interaction.
...

add to S173


[BUILD]capture io exception in server start

What changes were proposed in this pull request?
noticed that the CI is kind of flaky when starting master http server, turns out I didn't capture IOException
Why are the changes needed?
stable CI
Does this PR introduce any user-facing change?
no
How was this patch tested?
CI

@CodingCat, this has already been fixed in #2424. @turboFei, PTAL.

@CodingCat, this has already been fixed in #2424. @turboFei, PTAL.

yes. similar fix, thanks


Download attachments

https://trello.com/c/xpS0zlU4/803-download-an-attachment-file-through-content-publisher
This is the initial attempt at doing 'intelligent preview' for an asset, so that we redirect to Asset Manager only when we know a file is available, and potentially try to upload it if it's not in Asset Manager at all e.g. if it was uploaded as part of the edit form for a document. Further work:

Use the auth bypass token in the asset URL
Use the new preview path elsewhere in the app
Consider if we want special behaviour for infected files

I've done a bit of refactoring on the PreviewService, which had similar code for managing assets, to keep the tests manageable. The commit explains a bit more about the pros/cons of doing that - it seems to be a compromise between duplication and stubbing our own code.

@kevindew I've rebased this against the now-merged rendering PR and added a new commit to use the new in-app preview path. Slight downside is we now have to pass document everywhere, but the only alternative seems to be attachment_revision.revisions.first.document :-|.

@benthorner that seems reasonable, I can't imagine we'd likely be in a a situation where we aren't already in a document context before looking up the attachment. Even if we did have a nice association based method it'd likely generate an extra query.


2019-12-01 tc015 M3SD FLGACCEPTTMAX is missing from generated parameter results

FLGACCEPTTMAX should be generated if requested by MCT$PARAMETERLIST even if FLAGS$FLGEMESIS doesn't exist. With commit 6e99fab it isn't generated for tc015 M3SD. Will need to check other test cases if this is the case.
Also missing from tc016 M3SS, tc017 M4SD

I am noticing that the test cases for M3SD, M3SS and M4SD dont have FLGEMESIS in the MCT. Please make sure that FLGEMESIS is in the MCT (Just how FLEXKEL, FLGEXAUC, FLGEXSDE are present). Given that as a pre-req, I am able to generate FLGACCEPTTMAX.

FLGEMESIS is not a defined MCT keyword/element. It's a "possible" dataset value but not required. Review of the Computation Engine Specifications document appears to support that. FLGEMESIS is a time based flag that is intended only to be present in the input concentration dataset itself.

Just want to clarify based on the comment above, would the data represented by FLGEMESIS ever have a different name other than "FLGEMESIS". The only reason I am bring this up is because usually the computation engine checks the MCT keyword/element pair as a reference before looking at the dataset for the column name, and I want to account for a case where it is named differently in the dataset (if that is even a possibility). Based on your comment, I will make the appropriate changes in the next commit.

We can assume that there CAN be a definition in the MCT of FLGEMESIS and it will define the name of the column in the dataset. The default will be that mct$FLGEMESIS=="FLGEMESIS".

If I add FLGEMESIS to mct with value of "FLGEMESIS" now tc008 M1SD fails to run with the following error message:
> mct$FLGEMESIS
[1] "FLGEMESIS"
> results_list <- run_computation(data=d, map=mct, flag=flags, parameterset=parameterset)
Error in `[.data.frame`(tmp_df, , map_data$FLGEMESIS) :
  undefined columns selected
In addition: Warning messages:
1: In run_M1_SD_computation(data = merged_data, map = map_data, method = method,  :
  Flag 'FLGACCEPTTAU' cannot be computed if 'TAUi' is not provided
2: In run_M1_SD_computation(data = merged_data, map = map_data, method = method,  :

 Show Traceback

 Rerun with Debug
 Error in `[.data.frame`(tmp_df, , map_data$FLGEMESIS) :
  undefined columns selected

Please let me know when you've adjusted the code to not require a value of FLGEMESIS in the dataset. It should be optional in both MCT and dataset. If it is defined in MCT, the code should attempt to find a column with the name of the value of MCT$FLGEMESIS ("FLGEMESIS" by default in the MCT definitions) but not require that a value must appear in the dataset. I've updated all of the local (to my machine) definitions of the mcts to include FLGEMESIS now with value "FLGEMESIS" but I suspect each and every test case will now fail.

This issue was addressed in bb8e82d, please let me know if it still occurs.

Retested with commit bb8e82d and tc015. FLGACCEPTTMAX is now generated for the output parameter results and presence of FLGEMESIS in MCT no longer causes crash.
This issue will be closed but FLGEMESIS in MCT will be tested with other test cases.


fix: add exec as reserved keyword for Python

Description
This PR adds the missing reserved keyword exec for python that failed black-box tests.

/rtm


fix rotation of callout anchor

fixes #1503
and at the same time cleans up the code a bit

use an MPoint for the symbol offset, so that we can use its rotate method
add an conversion method Offset.ToPoint
add a variant of MPoint.Rotate that otates around the origin

Thanks for the review, @inforithmics!


Split Substrate messages into multiple substreams

Next two items of #1692
Fix #1517
See the comment here for a description: https://github.com/paritytech/substrate/issues/1517#issuecomment-461460022
This PR still uses the old behaviour by default. Once the network has upgraded to a version of Substrate/Polkadot that contains this PR, I'll try if everything works correctly (if we can still sync), then switch to the new behaviour by default, then eventually remove the old behaviour in the future.
While this PR adds a lot of code, removing the old behaviour would remove almost all of the custom_protos module, as we would switch to helpers that are inside libp2p.
I marked as "onice" because we need to publish a new version of the yamux crate that fixes some issues, but other than that the PR is ready.

@tomaka who is capable of reviewing this?

@twittner, I suppose.


use git log to determine when a file was last updated

resolve #117

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

31 of 38 (81.58%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.4%) to 31.298%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

broker.go
0
1
0.0%

entry.go
31
37
83.78%

Totals

Change from base Build<PHONE_NUMBER>:
2.4%

Covered Lines:
246

Relevant Lines:
786

💛  - Coveralls


release 0.4.0

Once #1264 is merged to fix high priority issue #1265, we should do a 0.4.0 release.

I'm waiting for #1082 to get merged as well and then I'll release later tonight.

I've updated the ticket title and description, since we decided that #1082 implies a bump to 0.4.0.

Ah good call.

Blessing 525866f as our golden commit.

tagged 0.4.0 and pushed to release

Changelog and VERSION have been updated on master.

Homebrew PR opened: https://github.com/Homebrew/homebrew-core/pull/5266

@stefantalpalaru release underway

0.4.0 for Windows is now available in bintray

0.4.0 for Linux Debian and RPM packages are now available in bintray

Waiting on homebrew now...

Gentoo ebuild updated.

thanks @stefantalpalaru!

for what appears to be reasons unrelated to any of the content in the PR, the homebrew PR https://github.com/Homebrew/homebrew-core/pull/5266 failed their CI and hasn't been restarted yet. So, we are waiting on that. The first couple times I did this, homebrew was painless and made it through their CI and was merged in a couple hours.
Last time it took about 26-28 hours.
We are currently at 13 hours.
I think I might update the release docs to say you can announce the release once, the Deb, RPM and Windows packages are available with a link to the homebrew PR and a note that OSX and Gentoo builds should be ready soon (assuming Stefan hasn't already updated Gentoo by that point).

I sent the release notice email to pony+user and also dropped a note in IRC. I'm leaving this open til the Homebrew PR is merged.

They kicked their jenkins CI again and after a couple hours it finally got to run so we are just wanted on someone to merge the Homebrew PR at this point.

Homebrew PR merged. 0.4.0 released!


Theme switcher bugs

The black theme has this app title bug.

https://github.com/user-attachments/assets/40ccd47d-ede2-41c8-a536-2fdc4d5ad4fb

In the light theme, the colour of the main body of the app is the same colour of the dark theme.

Fixed


I can't see my ESP8266 worker at pool.vkbit.com or public-pool.io

Good afternoon.
I'm a technologies teacher and I want to introduce my students in Bitcoin mining.
In LeafMiner you suggest pool.vkbit.com, but when configured, I can't see my ESP8266 worker at it!
I tried also with public-pool.io, but I have the same problem.
I only can view my device at pool.nerdminers.org, but I prefer the last one.
Do you know where can be the problem? What can I do?
Thanks a lot.

Related issues:

Change default pool to public-pool.io
ESP8266 - not visible at pool (no valid shares submitted?)

@prosselloe Happy to hear about introducing students to Bitcoin mining, the docs needs for sure a revamp as I recall the vbkit.com is not anymore supporting low difficulty.
For public-pool.io it should work if nothing outstanding has changed, at the end do suppose it uses the same version of pool.nerdminers.org.
Do you have by any chance any log out of public-pool.io?
I have no esp(s) next to me in this moment so it's a bit tricky to test it

Here you have an examlple:
[D] Network: <<< len: 0
[I] Network: Connecting to sagemcomFE20...
[I] Network: Connecte[D] Current: Hashrate: 21.01 kH/s
[D] Miner: [0] > Hash 0.000852483860 > 0.000100000000
[I] Miner: [0] > [1734bbe] > 0x06b4b227 - diff 0.000852483860
[I] Network: >>> {"id":241,"method":"mining.submit","params":["3NH6hkTmy7WcAL37LaUCbyZX1cDM4jXVzq.ESP-AE7DB6","1734bbe","85415904","66bf41c3","06b4b227"]}
[D] Network: <<< len: 0
[I] Network: Connecting to sagemcomFE20...
[I] Network: Connected to WiFi
[I] Network: IP address: (IP unset)
[I] Network: MAC address: 84:CC:A8:AE:7D:B6
[D] Network: Connecting to host public-pool.io...
[D] Network: Connecting to host public-pool.io...
[D] Miner: [0] > Hash 0.000118492436 > 0.000100000000
[I] Miner: [0] > [1734bbe] > 0x06b5ac4c - diff 0.000118492436
[I] Network: >>> {"id":242,"method":"mining.submit","params":["3NH6hkTmy7WcAL37LaUCbyZX1cDM4jXVzq.ESP-AE7DB6","1734bbe","85415904","66bf41c3","06b5ac4c"]}
[D] Network: <<< len: 0
[I] Network: Connecting to sagemcomFE20...
[I] Network: Connected to WiFi
[I] Network: IP address: <IP_ADDRESS>
[I] Network: MAC address: 84:CC:A8:AE:7D:B6
[D] Network: Connecting to host public-pool.io...
[D] Current: Hashrate: 5.06 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 20.99 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 20.99 kH/s
[D] Current: Hashrate: 21.01 kH/s
[D] Miner: [0] > Hash 0.000113918082 > 0.000100000000
[I] Miner: [0] > [1734bbe] > 0x06baee1d - diff 0.000113918082
[I] Network: >>> {"id":243,"method":"mining.submit","params":["3NH6hkTmy7WcAL37LaUCbyZX1cDM4jXVzq.ESP-AE7DB6","1734bbe","85415904","66bf41c3","06baee1d"]}
[D] Network: <<< len: 0
[I] Network: Connecting to sagemcomFE20...
[I] Network: Connected to WiFi
[I] Network: IP address: <IP_ADDRESS>
[I] Network: MAC address: 84:CC:A8:AE:7D:B6
[D] Network: Connecting to host public-pool.io...
[D] Current: Hashrate: 3.44 kH/s
[D] Miner: [0] > Hash 0.000291851949 > 0.000100000000
[I] Miner: [0] > [1734bbe] > 0x06bd3759 - diff 0.000291851949
[I] Network: >>> {"id":244,"method":"mining.submit","params":["3NH6hkTmy7WcAL37LaUCbyZX1cDM4jXVzq.ESP-AE7DB6","1734bbe","85415904","66bf41c3","06bd3759"]}
[D] Network: <<< len: 0
[I] Network: Connecting to sagemcomFE20...
[I] Network: Connected to WiFi
[I] Network: IP address: <IP_ADDRESS>
[I] Network: MAC address: 84:CC:A8:AE:7D:B6
[D] Network: Connecting to host public-pool.io...
[D] Current: Hashrate: 12.73 kH/s
[D] Current: Hashrate: 21.01 kH/s
[D] Miner: [0] > Hash 0.000146904586 > 0.000100000000
[I] Miner: [0] > [1734bbe] > 0x06c2de57 - diff 0.000146904586
[I] Network: >>> {"id":245,"method":"mining.submit","params":["3NH6hkTmy7WcAL37LaUCbyZX1cDM4jXVzq.ESP-AE7DB6","1734bbe","85415904","66bf41c3","06c2de57"]}
Best regatds.

It's a bit strange it continues to reconnect after submit, a this point something is happening in the response.
Need to check as soon I have a device around, but not later than next week

Hi, i have the same issue. Tried it with 0.16 and 0.17 - here are the results with an esp8266 12-F and 0.17:
Stack smashing detected.
Exception (5):
epc1=0x401003fa epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

stack>>>

ctx: sys
sp: 3fffff90 end: 3fffffb0 offset: 0000
3fffff90:  3fffdad0 00000000 3fffdab0 401003fa
3fffffa0:  feefeffe 00000000 3fffdab0 40229f2c
<<<stack<<<

I just merged the v/0.0.17 branch - https://github.com/matteocrippa/leafminer/pull/50
Let me know if it works anyhow better

Thanks for the merge, i tested it again and sadly it did crash again.
Here are the results:
[I] Current: Job: 1857787 ready to be mined
[D] Network: <<< len: 0
--------------- CUT HERE FOR EXCEPTION DECODER ---------------
Stack smashing detected.
Exception (5):
epc1=0x401003fa epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

stack>>>

ctx: sys
sp: 3fffff90 end: 3fffffb0 offset: 0000
3fffff90:  3fffdad0 00000000 3fffdab0 401003fa
3fffffa0:  feefeffe 00000000 3fffdab0 40229f2c
<<<stack<<<
--------------- CUT HERE FOR EXCEPTION DECODER ---------------
ets Jan  8 2013,rst cause:2, boot mode:(3,7)
load 0x4010f000, len 3424, room 16
tail 0
chksum 0x2e
load 0x3fff20b8, len 40, room 8
tail 0
chksum 0x2b
csum 0x2b
v0009fe10
~ld
����o��r��o|�$��l "���{�$�N��o�$`��r�p��l��[I] Main: LeafMiner - v.0.0.17 - (C: 1)
[I] Main: Compiled: Oct  6 2024 19:28:56
[I] Main: Free memory: 36136

But does it happen as soon as the first job arrives or after a few time / jobs?

It's everytime as soon as the second job is about to begin. First job is being transmitted ok.
This time the esp just hangs without a crash, so no exception code.
Seems a bit random if it crashes or hangs.
`[I] Main: LeafMiner - v.0.0.17 - (C: 1)
[I] Main: Compiled: Oct  6 2024 19:28:56
[I] Main: Free memory: 36136
[I] Main: ESP8266 - Disable WDT
[I] Storage: Setup: OK
[I] Configuration: wifi_ssid: XXX
[I] Configuration: wifi_password: XXX
[I] Configuration: wallet_address: XXX.esp1
[I] Configuration: pool_password:
[I] Configuration: pool_url: public-pool.io
[I] Configuration: pool_port:<PHONE_NUMBER>
[I] Configuration: blink_enabled: off
[I] Configuration: blink_brightness: 256
[I] Configuration: lcd_on_start: on
[I] Configuration: miner_type:
[I] Configuration: auto_update: off
[I] Blink: Blinking 5 times
[I] Network: Connecting to XXX...
[I] Network: Connected to WiFi
[I] Network: IP address: X.X.X.X
[I] Network: MAC address: X:X:X:X:X:X
[D] Network: Connecting to host public-pool.io...
[I] Network: >>> {"id":1,"method":"mining.subscribe","params":["LeafMiner/0.0.17", null]}
[I] Network: >>> {"id":2,"method":"mining.authorize","params":["XXX.esp1",""]}
[I] Network: >>> {"id":3,"method":"mining.suggest_difficulty","params":[0.000100]}
[D] Network: <<< len: 76
[I] Network: <<< [subscribe] {"id":1,"error":null,"result":[[["mining.notify","a770bbf1"]],"a770bbf1",4]}
[I] Current: New session id: a770bbf1
[D] Network: <<< len: 35
[I] Network: <<< [authorized] {"id":2,"error":null,"result":true}
[I] Network: Authorized
[D] Network: <<< len: 62
[I] Network: <<< [mining.set_difficulty] {"id":null,"method":"mining.set_difficulty","params":[0.0001]}
[I] Current: New difficulty: 0.000100000000
[D] Network: Difficulty set to: 0.0001000000
[D] Network: <<< len: 1329
[I] Network: <<< [mining.notify] {"id":null,"method":"mining.notify","params":["1914621","6499fa46d4e51a1ca3417f4ffbeeaaa943c6a1560002193b0000000000000000","02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff170338310d5075626c69632d506f6f6c","ffffffff0282e8f71200000000160014d5e652ee5cdcca88658c1bd8a0ad903d751e7b5b0000000000000000266a24aa21a9ed8b213665f0bf0236ae5a0517ce7360db9e33646d2bb80d1a48782c211facc00900000000",["dcb1bcf87e5b39ce2cc759ba75d94686220f16622a0001b747843578ae8f5f6a","dd556341cd62c9bd7cf957bc9a2a4e18215541b03190ef0aa742d82a35a1b09e","38e3cc1223e97532a94d4d8c212a346c5cdd4dfe916fb29aaaa39b089245b077","23b8770b0b061b23a5f864fd6d59934785a08856fc5a1a921071bdd072b594f7","6dbef30120c0c5943f8008749e1c67fce1224d6b4dea3103410a97b90221fcc4","cc0245ddaa5550ca13f31e863dea81531c00549610a161f0d04757d2e44255bf","0f179b7ca152f8f9b30270c7e8d681a3346632ee3b11ecdaeaa0aeb18442c2b7","f64b902bac1af21a112603fb36ef0663136789dc918e0e42d986db177d6a9a5c","54eebf804532dfc0d8224b605d6df7033478bfde7dc6beaa07435271f16ac696","8b4f8f1ad37fcfd1330f5f74ea987feca735be8c22bdcd9d1a0a02b288c0be89","19f3db3d4171462f38c426f8e33169f23f5e0146ea936b1b1c1031f01916106e","855e88e79d03a54b92e5624b4f9521f7e88cdd3bb506a7f923beb960e893e01f","8f8bae989a20afa05b21cd61e87675a22b8624cad0bf520cc62ef9c2d56aafbf"],"20000000","17032f14","670397c1",true]}
[I] Job: Random value:<PHONE_NUMBER>
[I] Job: Hex value: 6147D0B5
[D] Job: Coinbase hash: 7c0d374ad943bbe7abba38ff2bf3526bda30599f5f9d7fd2251933e1cb0742c8
[D] Job: Merkle root: c41ef48ac52cf42a65253dc9d3fabace58703fe8aeb056a36834b55e475c72c3
[I] Current: Job: 1914621 ready to be mined
[D] Network: <<< len: 1263
[I] Network: <<< [mining.notify] {"id":null,"method":"mining.notify","params":["191463a","6499fa46d4e51a1ca3417f4ffbeeaaa943c6a1560002193b0000000000000000","02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff170338310d5075626c69632d506f6f6c","ffffffff024c83fc1200000000160014d5e652ee5cdcca88658c1bd8a0ad903d751e7b5b0000000000000000266a24aa21a9eda11a9cb31ee3398e3f3985a33a05affc17be5cf736134caddf7bc1d161fe43c400000000",["725c6924b05a746345a535c6196fa1a07d0601303180511fa9058d8cb24d6364","6fe3c83730d81edd6f1f3307d0009f295aba86e03e36fa1b0b3c1f24bc2b7e4e","c08e331eb507c0d25f1ec52ff26956beec8f67eafba636bbfa88403594729fa3","fe12dd2f200eccf05fef92812bf585f40de300a36283f2e5c1540199b834e6f1","6ce34550578e0c29629d9fed6418c355b4ff0ad3a1447d92854288e90515193f","d7c1ce04b29f675efd4b560ddcb18aaa383963258a6017dbd4800a358e82663f","c8e8483921df67012883f123e16021f23b8e7258c6c4b79f7692dad3c81edadd","03985469846a70d62ed209a406e07fc6cf4bf2f28066c580f7a4cd4d63165c3b","a36443592b299fe15a378e133144edb2cbf3cf3a54ecd3b5f2175de33cb5420d","5dad64397a105fdd5b3aa6564a069933298e6a2816d382fd6c973ee284570749","63099f9e49e99dd8fe6ae2760f214b1d5b9cb3cbdb03050171e68b3a0a9783a6","635ebca914e4f0c9d631f9f98d43f4273a5d06c2ee89ba34849d2285a9eaef0d"],"20000000","17032f14","670397fd",false]}
[I] Job: Random value:<PHONE_NUMBER>
[I] Job: Hex value: 6147D0B5
[D] Job: Coinbase hash: 8676648ab038f8194c148f879bcc9c31cdb93adaa9e8379a3b38722a197b0290
[D] Job: Merkle root: 3fb4441c4792907045057f5584e83ddb592de42bba8d2720bbe8885b85783a92
[I] Current: Job: 191463a ready to be mined
[D] Network: <<< len: 0
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 20.99 kH/s
[D] Current: Hashrate: 20.99 kH/s
[D] Miner: [0] > Hash 0.000727760514 > 0.000100000000
[I] Miner: [0] > [191463a] > 0x000dd7c7 - diff 0.000727760514
[I] Network: >>> {"id":6,"method":"mining.submit","params":["XXX.esp1","191463a","6147D0B5","670397fd","000dd7c7"]}
[D] Network: <<< len: 35
[I] Network: <<< [mining.submit] {"id":6,"error":null,"result":true}
[I] Network: Share accepted
[I] Current: Hash accepted: 1
[D] Network: <<< len: 0
[I] Current: New highest hashed difficulty: 0.000727760514
[D] Current: Hashrate: 7.50 kH/s
[D] Current: Hashrate: 20.98 kH/s
[D] Current: Hashrate: 20.99 kH/s
[D] Current: Hashrate: 20.99 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 20.99 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 20.98 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Current: Hashrate: 21.00 kH/s
[D] Miner: [0] > Hash 0.000102266647 > 0.000100000000
[I] Miner: [0] > [191463a] > 0x002094ff - diff 0.000102266647
[I] Network: >>> {"id":7,"method":"mining.submit","params":["XXX.esp1","191463a","6147D0B5","670397fd","002094ff"]}
[D] Network: <<< len: 1263
[I] Network: <<< [mining.notify] {"id":null,"method":"mining.notify","params":["1915492","6499fa46d4e51a1ca3417f4ffbeeaaa943c6a1560002193b0000000000000000","02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff170338310d5075626c69632d506f6f6c","ffffffff024702041300000000160014d5e652ee5cdcca88658c1bd8a0ad903d751e7b5b0000000000000000266a24aa21a9edadb4bdd2ee3a7c1f5c2ba5fdab7f3e9a0ebff4724d9da33af9b9b6cbf95e68bc00000000",["7db6b407c7420698a7299529943ee4013bbd44b536f228d2eca51abdd8e40877","bf6f63905ddd6529e2d7935a98417b8e79d50f20e3052145234d4f99bf778584","5fa96e28ba67bdcaff4cbec9e13af6b41edf2199d9c3f459e7b9d035b0f406d9","cd859a256efaed2ffd760ddc60787e455fe1d694858a4fa0839081d430fcb4fd","abb824ce408c3f9bf2668b5b6d7b78ad7fd9f858cda6bc5a79ca847a17be98a1","8c56a22231ea1124dd2d813c0358892fb597bd39fc33b7893a28fc2d2b64a18e","54113e6c9f71e3439b87af89adf3d8e7ca83e13eaf2a0cbe2399f3d8dded585b","85fb2dc6345578e60240f25715fd6ca20bdb3d6bb50b2c0348c5a3714ed2e58b","9ae8acaee74f9b0e9e77664b83b0dbecceb86a2c5548e3b9fa79a00fe676d10a","cd5bf862f5e2b1f7a51352d7e7aaa8bb094600b49c9d450d5f8819d7f263fc22","e8e54713c6378685780c424b557620cdfb92d1e1120875edae354c970542a6dc","aaaac5438e85f1b426d17f2dfe2b6eae0a762011ccdad23d98286cb2bf773c96"],"20000000","17032f14","67039839",false]}
[I] Job: Random value:<PHONE_NUMBER>
[I] Job: Hex value: 6147D0B5
[D] Job: Coinbase hash: 25630e824cd41451deab90d25d9c824af4437ff52acd6ec74bc0f23737665ff5
[D] Job: Merkle root:`
Thanks again for your work, i really appreciate it!

Can be an overflow, esp8266 it's not the greatest in memory, btw when it crashes it later restarts no?
I need to check if it's not a force crash I had to trigger to make it work

Can be an overflow, esp8266 it's not the greatest in memory, btw when it crashes it later restarts no? I need to check if it's not a force crash I had to trigger to make it work

Nope it does not recover and needs a hard reset

Is there any update for this issue, I am having the same problem

i having the same issue :(


Fix translation system

This PR will at some point close #244, it:

Simplifies how lib/translate.ts works.
Removes the need for specifying the locale in translations.ts files.
Makes sure a translation key is returned if a translation is missing, so we can easily identify what needs work.
Fixes hydration issues.

I'm drafting a PR so I can test on the Vercel deployment.

Wow! I'll make sure @vinayaksh42 also sees this as he and I spoke some about this.

Cool! It'd be great if @vinayaksh42 can focus on removing the need for the /en if the user locale is set to english, so #189. I will be handling other translation issues, updated my PR description to reflect this.


[CSRanking] Adjust ranking of makeIterator overloads in for-in context

Prefer an overload of makeIterator that satisfies
Sequence#makeIterator requirement  when .makeIterator()
is implicitly injected after sequence expression in for-in
loop context.
This helps to avoid issues related to conditional conformances
to Sequence that add makeIterator preferred by overloading
rules that could change behavior i.e.:
extension Array where Element == Double {
  func makeIterator() -> Array<Int>.Iterator {
    return [1, 2, 3].makeIterator()
  }
}

for i in [4.0, 5.0, 6.0] {
  print(i)
}

makeIterator declared in the Array extension is not a witness to Sequence#makeIterator and shouldn't be used because that would change runtime behavior.
Resolves: https://github.com/apple/swift/issues/60514
Resolves: https://github.com/apple/swift/issues/60958

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please test

@swift-ci please test source compatibility

@AnthonyLatsis Sure, let's let the source compat run and I'm going to rename before merging.


Allows for RecordNotFound errors to be defined in the settings

Currently ActiveRecord is a dependency for this Gem. This PR allows to set the RecordNotFound error class from the config.

Thank you for contributing @robguilfoyle!
I'm currently working on the next version of Knock and this dependency will go away, so I will not merge this right now.
Cheers!


attiny2313 targe uses the wrong ISA

Not sure if by design or mistake, but the attiny2313 spec sets --mmcu=at90s2313:
$ grep tiny2313 -A 2 avr-specs/sync-from-upstream.py
    "attiny2313": {
        "cpu": "at90s2313",
    },

According to the avr-gcc manual, while code for the at90s2313 can probably run in the attiny2313, they actually have a slightly different ISA:
GCC supports the following AVR devices and ISAs:

avr2

    “Classic” devices with up to 8 KiB of program memory.
    mcu = (...) at90s2313, (...) .

avr25

    “Classic” devices with up to 8 KiB of program memory and with the MOVW instruction.
    mcu = (...) attiny2313, (...).

@urlordjames, as your PR #294 added this, maybe you have any more info on this?

@urlordjames, as your PR #294 added this, maybe you have any more info on this?

I must have skimmed the manual and missed it.  Good catch!  Thus far I haven't run into any issues in my use case, apologies if this caused a headache on your end.

On Fri, Sep 30, 2022 at 05:55:18AM -0700, urlordjames wrote:

@urlordjames, as your PR #294 added this,
maybe you have any more info on this?

I must have skimmed the manual and missed it.  Good catch!  Thus far
I haven't run into any issues in my use case, apologies if this caused
a headache on your end.

Ideas for getting beyond the headache are welcome

Of course I will submit a PR that resolves this when I find the opportunity.  I don't entirely recall why I used "at90s2313" instead of "attiny2313", maybe it didn't initially work on my system or something.  I will test this on one of the ATtiny2313's I have to verify the suggested change actually works.

@urlordjames, perfect, this is very nice of you.  I don't have any of these MCUs on hand so if you can test on real hardware, this will be best.  That said, as avr2 (what is currently used) is a subset of avr25 (what the proposed change would use), we're on the safe side right now.  Thus I don't think this issue has high priority at the moment.  So no need to stress over it!

Upon trying to change at90s2313 to attiny2313 I stumbled upon what must have made me decide to use it in the first place.  It appears that the Nixpkgs version of avr-gcc fails to find crtattiny2313.o and crashes when -mmcu=attiny2313 is supplied as an argument.  The first time around I must have assumed that attiny2313 was incorrect somehow, so I used at90s2313 instead.  I don't think this is intended behavior and I suspect it may be a bug in Nixpkgs, so I will be opening an issue there.  Regardless, after forcibly coercing avr-gcc to find the correct files (by adding -B/nix/store/fd99zs5zrfbk9pyyj3mqgmwq01ibfgcc-avr-libc-avr-2.0.0/avr/lib/avr25/tiny-stack to pre-link args) I was able to confirm this works on a real ATtiny2313.  I apologize if this ended up causing incorrect behavior for anyone.


issue #10 add test.

Codecov Report

Merging #11 (bef4b4c) into main (8841aeb) will increase coverage by 3.12%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main       #11      +/-   ##
===========================================
+ Coverage   96.87%   100.00%   +3.12%
===========================================
  Files           1         1
  Lines          32        37       +5
===========================================
+ Hits           31        37       +6
+ Misses          1         0       -1

Flag
Coverage Δ

unittests
100.00% <100.00%> (+3.12%)
:arrow_up:

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

Impacted Files
Coverage Δ

source/karasux/nullable.d
100.00% <100.00%> (+3.12%)
:arrow_up:

Continue to review full report at Codecov.

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


Rename applicability levels to Safe, Unsafe, and Display

After working with the previous change in https://github.com/astral-sh/ruff/pull/7821 I found the names a bit unclear and their relationship with the user-facing API muddied. Since the applicability is exposed to the user directly in our JSON output, I think it's important that these names align with our configuration options. I've replaced Manual or Never with Display which captures our intent for these fixes (only for display). Here, we create room for future levels, such as HasPlaceholders, which wouldn't fit into the Always/Sometimes/Never levels.
Unlike https://github.com/astral-sh/ruff/pull/7819, this retains the flat enum structure which is easier to work with.

Sorry for the churn I know this touches a lot of files.


Add disc age #569

resolves issue #569
Concisely describe what has been changed/addressed in the pull request.
add output of discard_at_age for forecast years
What tests have been done?
visual exam of report.sso shows that discard_at-age now appears for forecast years

@e-perl-NOAA   help please.

Probably has to deal with the merge conflicts with the recent push of the makefile updates. Will rebase tomorrow morning.

@Rick-Methot-NOAA this should be good to merge now


How about adding --upgrade flag (like deno version upgrade)

After deno 1.0 release, many feature and api is changed. and denon also version updated fastly.
denon --upgrade
excute it
deno install -Af --unstable https://deno.land/x/denon/denon.ts

The feature is planned for v2.0.0 release, see #44 for updates


Multi Account basic template self mutating pipeline

Describe your changes
Issue ticket number and link
Checklist before requesting a review

[ ] I updated CHANGELOG.MD with a description of my changes
[ ] If the change was to a module, I ran the code validation script (scripts/validate.sh)
[ ] If the change was to a module, I have added thorough tests
[ ] If the change was to a module, I have added/updated the module's README.md
[ ] If a module was added, I added a reference to the module to the repository's README.md
[ ] I verified that my code deploys successfully using seedfarmer apply

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 99d50a077d6aa31f50eb326fdfe4e79413b70ab4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: a58593b3c3c7587e55d012ad9675dc476192fa6b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 0a484d6faa863382a040b93ff445ca9b448837e9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 65b9dcda85dde10fba379a5b61804d51f2660377
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: a2e30c314590b9d435fd7613555e402727a62d75
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 517e54d0927f43eed93cbc3d3327dcb43b00b8a0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 8bb696cd391c64dcd6e84cd639e1b695875023ea
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 7097041f40fa9af63aaf43b65ec38391cc7a1fee
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Please update changelog.md and run the code formatter as well.

Please update changelog.md and run the code formatter as well.

CHANGELOG updated, thanks!

Please update changelog.md and run the code formatter as well.

Please update changelog.md and run the code formatter as well.

CHANGELOG updated, thanks!

Additionally code formatter fixes applied.

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 5e7025e1c3aa8182e6f75494fdd344d509f05bdd
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: cc266fa6d13d6cb3ca8fb85dd935f3cad1611df3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: fd2afd78fe9375ebcd2019bbb3eeb6d34f612389
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: b54bbf24099172a032cd87f4b0bd78d9294a456c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 1335b92a9205388d8b2970f740e0d764929c5524
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: ff4cca3dc5cf3893920cf3fe71be91b0182ae15a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 967361f2c8063f1dbf033aa71ee9580056e80d30
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 68420339d77b4b7422b880ac10b5d655c6b42404
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: aa7f6b01e23aac47bcf2fa167aa3799f7badf9ae
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: eb59a0da0a21f60709af2ab91a9ae153c5be7c47
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 235228412bb79aa2702b7dbae7d12911788a7ccd
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 90e1fc8d814ee609cd6b067566ddb62e654847d7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 44f604bd7489bba2dc5393c1a3ed081d9986e7f9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 56af5b16cdab88b243bb40df445031535c32157e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: c6581c98deda4bc5e2fb8f520be14d89da3e8e0e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

FYI quick verification in a single account was successfull. @acbhatt12 you have tested multi-account deployment as well, correct?

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: b952a4c5d86db8b63bd89147938eecd58337a98c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 03027f6933eca231e6074597a1cb8f1519423f3b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 5bc69e837666f33623c369088ab0fe6b025f6cf1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: ff162c0c2e97f6e1f198195964bd00046101b3a7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Publications

👷 Deploy Preview for crpp-ai-oncology-zurich processing.

Name
Link

🔨 Latest commit
c2cc74b8f82bc6afd6b42db0712bb770400f2001

🔍 Latest deploy log
https://app.netlify.com/sites/crpp-ai-oncology-zurich/deploys/656e0d9feae4d7000829eb30


[Improvement]: Add Footer

Create a Footer component that holds contact info (twitter and github)

Also add a link to the about ratings page /about/ratings


PR for everything I've done so far on my fork

Hi Soichi. I looked over this changes. We should discuss. I am not convinced that this is the repository we want to change.

Franco,
Do you mean the changes I made to  scripts/life_demo.m? Or the fact that there are now new files specific to SCA? On the fork that I am working with Brent, we've put all the SCA related stuff under /sca directory so that those *.sh scripts will be hidden.
If I can't put SCA scripts here, I will need to host those SCA script elsewhere and pull this repo as a dependency - and somehow needs to maintain compatibility with specific version of life code.. I hope we can keep it together.
In any case, you can reject this pull request - since we are making other changes on our fork - we can discuss weather or not to merge it upstream.

Hi Sochi.
I guess I am still considering options for merging the SCA changes into the general repository.
We might need to discuss a plan to these changes. But the would be good to do in person.
Franco Pestilli
<EMAIL_ADDRESS><EMAIL_ADDRESS>I have a new Google Phone:
(347) 829-4185

On Aug 25, 2016, at 2:06 PM, Soichi Hayashi<EMAIL_ADDRESS>wrote:
Franco,
Do you mean the changes I made to scripts/life_demo.m? Or the fact that there are now new files specific to SCA? On the fork that I am working with Brent, we've put all the SCA related stuff under /sca directory so that those *.sh scripts will be hidden.
If I can't put SCA scripts here, I will need to host those SCA script elsewhere and pull this repo as a dependency - and somehow needs to maintain compatibility with specific version of life code.. I hope we can keep it together.
In any case, you can reject this pull request - since we are making other changes on our fork - we can discuss weather or not to merge it upstream.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/francopestilli/life/pull/53#issuecomment-242485893, or mute the thread https://github.com/notifications/unsubscribe-auth/ACBYc6n2KIoBBPTIofOEBFZRbP1SZQYZks5qjdm3gaJpZM4JR1tv.


'cmsplugins' needs to work for djangocms_text_ckeditor.fields.HTMLField

Currently djangocms-text-ckeditor's HTMLField doesn't have the ability to link to other CMS pages.
DjangoCMS has cmsplugins, a plugin for CKeditor for that.
However as explained in djangocms-text-ckeditor's README (see Usage as a model field), this is not supported for HTML fields. This Model Field is heavily relied upon for the creation of custom content elements in DjangoCMS. Not being able to link to CMS pages from them is quite a brutal shortcoming of DjangoCMS in comparison to other CMS systems and frameworks.
Can we have some insights into why this core piece of functionality is not implemented in djangocms-text-ckeditor?

This functionality depends on the whole django CMS placeholder stack, which is not available unless you are using a placeholder (a PlaceholderField in the case of non CMS models)
You can easily add a PlaceholderField in you custom models as detailed in http://django-cms.readthedocs.io/en/latest/how_to/placeholders.html and then using plugins all the way down.
You can provide your users a default text plugin when the model is created first to make their work easier as detailed in the default_plugins section of the CMS_PLACEHOLDER_CONF documentation (http://django-cms.readthedocs.io/en/latest/reference/configuration.html#cms-placeholder-conf)

Quick note: Workaround for something like 'Title and Text" plugin which contains a text input and a html field: Create a plugin that contains an input field and let editors know that they should insert a TextPlugin into it (allow_children = True)

Update: the django CMS Association's ckeditor 5 workgroup is working on making the link functionality independent from the in-text plugin functionality. This means that the problem described in this issue would be solved for the linking functionality, i.e. it would be possible to link dynamically to CMS pages even inside djangocms_text_ckeditor.fields.HTMLField.
Please read more and/or participate here: https://django-cmsworkspace.slack.com/archives/C01CJN3DSNS

With regards to placeholder functionality, django cms v4 allows other models to reuse the placeholder model, there could be a way to make djangocms-text-ckeditor work using a placeholder of it's own. This is how djangocms-alias works. This would be for django-cms 4+ only though sadly.


⚠ Bofrost.be has degraded performance

In 2f64d39, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1275 ms

Resolved: Bofrost.be performance has improved in e71696b after 6 minutes.


“Updating Windows Update Agent Header Files” download link broken

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Link to article:
Tell us where exactly a problem occurs.
Updating Windows Update Agent Header Files
https://docs.microsoft.com/en-us/windows/desktop/Wua_Sdk/updating-windows-update-agent-header-files
Problem:
What's wrong with the article?
The download link broken
http://go.microsoft.com/fwlink/p/?linkid=185614

@GrantMeStrength can you please take a look at this issue?

Links have been corrected, thank you.


Docs

We should have awesome docs on running PgVillage

Chainsmith & SSL
Etcd
Stolon
Wal-g / restore
PgRoute66, HAProxy, AVChecker
Quickfix
PgQuartz
Connection paths
New cluster, new user


Tidy up Nginx cache-related directives

Have one set of proxy_cache_valid settings
Express 'expires' with more easily-read "days" format
Remove redundant proxy_cache_valid directives. There was some variation, but not enough for it to be perpetuated.

My original reason for modifying the proxy Nginx configuration was to make caching more effective for thumbp, but I decided it needed some cleanup.

Sorry for issuing another pull request that wasn't really ready and required more commits. Commit 4e61422 in particular adds some significant changes.
This is all to improve caching in anticipation of going HTTPS and possibly incurring a hit in overall page speed, especially with the thumbnail images.
These changes should be tested in a test / staging environment before being finalized.

This branch needs some more work. I'll reopen this PR when it's ready.


Cache NPM node_modules in CI

Cache NPM node_modules to speed up installation.  Saves roughly 25 seconds in total
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 2.X
┆Issue Number: DOCK-781
┆Epic: Speed up Builds

Might be of use https://docs.cypress.io/guides/guides/continuous-integration.html#Example-circle-yml-v2-config-file

Circle CI is restoring and saving the cache when necessary.


[MPLUGIN-384] restore compatibility with Maven 3 ecosystem

https://issues.apache.org/jira/browse/MPLUGIN-384

I think that Maven class loading won't load the class from the plugin: it is taken from Maven core classloader (that contains compat), see https://maven.apache.org/guides/mini/guide-maven-classloading.html
but you're right that it deserves testing in real life to check that I'm not wrong (IIRC, I already saw such a class copy in another case, but I don't remember where)...

I checked with real environment, metadata to oss was deployed correctly.

thank you Slawomir


Blur Image after Cropping

Hello again
I have already sent you my code in my previous Issue
I select file from gallery or camera and then i crop the image and i m getting the blur image
Please help

can you upload example image

the one i m using to upload as my profile image?

it's not only about a specific image, I need to understand what are you doing and what is the result compared to the expected result.

ahhhh i got the issue.... i wasn using small size of result image.... i m saving result in different sizes and i m using the wrong size in view
thanks for your time


Describing something has happened in future

It was announced on December 8th, 2023: Seriously? Here is the URL
Looks like correct information: Tuesday, 8, December 2020
Screenshot

Thanks for your report @SKJoy.


iSpindel calibration not working missing numpy package

Update installation package.

Tested with latest version of numpy but that seams to give the wrong result. Force installation of numpy==1.18.4 (this seams to work, or at least give a reasonable value).


Waffle should be able to auto-create flags/switches/samples

Manually having to create these is kind of tedious and unneeded.
Automatically creating them if they don't exist (configurable with a setting of course) would be better :)

will this ever happen? as @WoLpH said 3 years ago, this is unneeded and tedious.

Honestly, it's never been high on my list.
The biggest issue is that, in my day to day of using waffle for the past however many years, it's never been enough of a pain point to deal with the fallout of trying to do it.

Creating them out of request/response cycles requires a level of code analysis that's just not worth including. Looking at Python and multiple types of templates, evaluating expressions that get used as flag names, etc. Or it requires a huge change of listing all the names somewhere.
Creating them during request/response cycles is the winner, but it doesn't necessarily get you the full set, and requires handling a bunch of race/concurrency issues that don't come up if we don't do it.

And like I said, it's never bothered me nearly enough for me to say "OK, I'm going to fix this now."

Not being passive aggressive here, but this is annoying enough for me to look at other solutions such as  Gutter. feature flipping libs should be as simple as it can get, sync'ing keys manually is clearly not human friendly and it is prone to error.

Is it annoying enough to help contribute a solution? I'm open to it, but, like I said, it's never tripped my personal "too annoying gotta fix" breaker.
Otherwise, yep, there definitely are other solutions out there that might fit your needs better.

Well, to be fair. I already created a pull request 3 years ago to fix this. So there was already a contributed solution ;)
I still think some high-performance solution needs to be there. The get_or_create method suggested in some related discussion is exactly what you are trying to avoid with a package such as waffle.

I'd be interested in contributing a patch for this if it would be accepted. My plan would be to create a settings value (WAFFLE_CREATE_MISSING_FLAGS, WAFFLE_CREATE_MISSING_SWITCHES, etc. although I'm open to feedback on naming). To avoid changing historic behavior the setting could be off by default, but perhaps allow those that are interested to enable it so that when a flag/switch is encountered it could be automatically created and respect the WAFFLE_FLAG_DEFAULT, WAFFLE_SWITCH_DEFAULT, WAFFLE_SAMPLE_DEFAULT values on creation).

@WoLpH , can this be closed, since we now have those WAFFLE_CREATE_MISSING_X options now?

Yes, I believe so :)
Honestly, I'm currently not using Waffle so I cannot easily check anymore. But I might use it again for a project soon.


vocab.json for WikiText-103

Hello.
The downloaded WikiText-103 only has the following three files:
wiki.test.raw  wiki.train.raw  wiki.valid.raw
It seems that the run_experiment.py requires the dictionary file vocab.json. Is there a script for generating vocab.json?

Hi! Thanks for asking; my apologies—I should have uploaded the conversion scripts already.
The dataset can be found here.
For reference, I've also uploaded the script we used to convert the original dataset here.
(If it's of any interest, we have just recently released an early version of a more reusable library of unit scaling components for PyTorch.)

Thank you! It's very helpful!