Workflow integration

[ ] merging workflows (electron & muon)
[ ] When merging workflows, require exactly one ele or exactly one muon for the respective channels.
[ ] fill_none issue for selections
[ ] QCD workflow integration
[ ] boosted jet workflow integration

fill_none issue for W+c selections are discussed in #60


Find a way to persist squiggle results

We'll need it eventually; I've become convinced that there's no way around it, even if we delay it with long-running servers maintaining SqProject instances and keeping everything in memory.
Reasons why this is necessary:

users will run out of memory eventually on heavy projects
restarts will become painful
maintaining SqProject instances in the background is hard for environments such as VS Code extension
when we release Squiggle Hub with a distributed network of squiggle models, we'll want to cache the results, instead of forcing people to re-run the entire chain of dependencies

This is hard to do because of lambdas, but doable:

the results would have to include the entire source code or AST or intermediate representation in form of Reducer_T.expression; so lambdas could bring their squiggle source code with them in a persistent form
persistent results are a graph and not a tree, as @umuro noted previously
we'll have to take care to make this compatible across squiggle versions, or partially compatible, or force recalculations when versions don't match

One way to store these on disk is to create a foo.squiggle.out file for each foo.squiggle file when the it gets executed, and to choose a foo.squiggle.out file later on when it's more fresh than foo.squiggle.

CASE 1.
(Simple things should be easy)
"I don't care about projects, let me run some squiggle code"
return (
	<SquiggleChart code="x=5*2" />
);

CASE 2
(Custom long write-ups)
"I want to put several dependent snippets of Squiggle code on an HTML page"
return (
	<SquggleProject>
		First part
		<SquiggleChart code="y=5" />
		Second part
		<SquiggleEditor code="x=y*2" continues={[depId]} />
	</SquiggleProject>
);

CASE 3
(Observable)
"I can't wrap components that share a project in a top-level React component"
// cell 1
const project = SqProject.create;
// cell 2
return <SquiggleChart project={project} code="y=5" />;
// cell 3
return <SquiggleEditor project={project} code="x=y*2" continues={[depId]} />

CASE 4
(VS Code)
Caching is hard, each webview is a separate JS environment, so we can't share project instances between different previews.
Solution for now: don't share instances, re-run everything. This is the same as CASE 1:
return <SquigglePlayground code="y=5" />;

Solution for the later: persistent results, https://github.com/quantified-uncertainty/squiggle/issues/1198
Either cache the results on disk in foo.squiggle.out files, or run a background squiggle-server process and serve the results from it across multiple previews.

In case 3, I wonder if we could simplify things. The following notes are me thinking out loud, I haven't figured this out yet.
Instead of supporting passing the optional project prop in all Squiggle(Chart|Editor|Playground) components, we could ask users to always wrap their components in a SquiggleContainer HOC.
Here's how it would work, from the user's point of view:
<SquiggleContainer project={project /* can be omitted */}>
  <SquiggleEditor code="y=5" />
</SquiggeContainer>

In the implementation:

SquiggleContainer could create a project if it hasn't been passed in props and if there's no outer SquiggleContainer (this "if" condition is already implemented, I had this in mind when I implemented it initially)
useSquiggle would grab the project from the context with const { project } = useContext(SquiggleContext); when useSquiggle is called from any component that's nested inside SquiggleContainer, the project would always exist; otherwise it would use a global project from the context's defaults

We'd have to be careful with imlpementing this, though.
Consider:
const SquiggleEditor = ({ code }) => {
  const { result, bindings } = useSquiggle({ code });
  return <SquiggleContainer>
    <SquiggleViewer result={...} />
  </SquiggleContainer>;
);

If someone would try to render this version of <SquiggleEditor> without an explicit <SquiggleContainer> wrapper, it would create two projects: one in useSquiggle, and one in its <SquiggleContainer>.
There are two ways of fixing this that I see.
First:
const SquiggleEditor = ({ code }) => {
  const { result, bindings, project } = useSquiggle({ code });
  return <SquiggleContainer project={project}>
    <SquiggleViewer result={...} />
  </SquiggleContainer>;
);

Second:
const SquiggleEditor = ({ code }) => {
  const project = useSquiggleProject();
  const { result, bindings } = useSquiggle({ code, project });
  return <SquiggleContainer project={project}>
    <SquiggleViewer result={...} />
  </SquiggleContainer>;
);

Also, we could put in additional checks to avoid the bugs of this kind:

<SquiggleContainer> could throw an error if its project prop is set but doesn't match the context (i.e. it's context is { containerized: true, project: someOtherProject })
<SquiggleViewer> could throw an error if the result comes from the different project than its context (at least for now we can build this kind of check, it would be harder later on when results become serializable)

There's also a question of what should we do with the environment. We could remove the project prop from most components and leave it only on <SquiggleProject> level, but then I guess we have to uplift the environment prop to the <SquiggleProject> level too?
That makes sense to me if the environment is a project-level setting. But I can also see how in the future we could decide that the environment is actually a per-source setting. (see also: #1116)
In that case, it makes sense to allow it both on the project level (<SquiggleContainer project={project} environment={...}>) and on the source file level (<SquiggleEditor environment={...}>, which then passes it to useSquiggle, which passes it to project->setSource or to project->run).

I've already mentioned that idea to Slava earlier, but maybe we can store graphs as operation trees? That would also allow for easier sampling of region, alas requiring us to fix random seeds in some user-friendly way.

@berekuk, @OAGr , @Hazelfire
https://google.github.io/flatbuffers/
Binary File Format supporting C++, Java, C#, Go, Python, Rust, JavaScript, PHP, C, Dart, Lua, TypeScript
Implemented by Google


QoS 1 - Add interface for Subscription to register event callbacks

Depends on https://github.com/ros2/rclpy/pull/305
Adds just the new API for creating a subscription
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The interfaces will actually look pretty different based on learnings in implementing - will reopen when ready


Listener 2.0

Description
This PR introduces a new Orakl Network listener service. The new listener version ensures that no events are missed. It also offers to fetch old events retrospectively.
There are no changes related to settings of listener.
Architecture
flowchart LR
   launch-->latest
   latest-- repeatable job ---latest
   launch-->history
   latest-- success ---processEvent
   latest-- failure ---history
   history-->processEvent
   processEvent-- end of listener ---worker

Others

Updated localhost migration scripts
Removed localhost migration lock files
Added MIT license

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist before requesting a review

[x] I have performed a self-review of my code.

Deployment

[x] Should publish npm package
[x] Should publish Docker image

@kodyfanz This PR solves the issue https://github.com/Bisonai/orakl/issues/474 you raised. If you have time, it would be great if you can take a look at the code 🔥


chore: add document link on userDropdown

Description

用户下拉菜单增加文档链接
What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).

有一个想法。 添加一个侧边导航，把项目开发文档，外部文档通过 iframe 嵌入的方式加进来，或者外链的形式也可以，这样会让项目看起来更加丰富一些～

开了新issue，后面单独做


Minor Improvement (A New Variable) For the "window.title" Setting: ${rootParent}

Currently the window.title setting provides a whole bunch of variables for configuring your window title, which is awesome!  However, I've found that they fall short for a common use case I have: client and server folders.
Let's say I have two web projects, and each project has a client and server, so I organize them as:
~/projects/Foo/client
~/projects/Foo/server
~/projects/Bar/client
~/projects/Bar/server

I then open each one (as needed) in their own separate VS Code, so my "workspace folder" is either "client" or "server".
The problem is, if I use a window.title of ${folderName}, I see "client" or "server" (but I don't know the project name).  If I instead use a window.title of ${folderPath}, I get "~/projects/Foo/client", which would be great ... except that in my taskbar the window title gets truncated, so all I see is ~/projects/Foo: I don't see the folder name.
What I really want to see is Foo/client or Bar/server, but this is currently impossible.  Adding one simple variable of ${folderParent}, which resolves to the name of the parent of the workspace folder, would solve this.
With such a variable I could have a window.title of ${folderParent}/${folderName}, which would allow me to see Foo/client or Bar/server, and easily distinguish my different open editors.

@machineghost why not open all the folders into a multi root workspace into one window? Alternatively you could create a workspace file for each folder and give it a distinct name.

why not open all the folders into a multi root workspace into one window

I wasn't real knowledgeable about workspaces, but I read this and they sound great.
My concern is that when I used one editor before, all of my projects' files were in scope, so a CTRL + E foo would be slower. I often had a foo.js or fooBar.js in another project, and while this might seem trivial, over time going from:
CTRL + E foo ENTER
to:
CTRL + E foo look, think, maybe press DOWN once or twice, then ENTER
really adds up!  The hassle of having to start up multiple editors (on a machine I rarely restart) is worth it to avoid that.

Alternatively you could create a workspace file for each folder and give it a distinct name.

I hadn't thought of that , but just now I went and did "Save Workspace As..." for each editor to name them, then changed my window title to ${rootName}, and now I can see each one easily/separately in my system tray. Thanks!
I'll close the ticket, but for the record IF this bug is easy to solve, I'd vote for it to be re-opened, simply because a variable would solve this problem without require workspace files/knowledge.


more flexible dependencies

use more flexible dependencies. Move pytest to extra dependency, since it's only used at development time.

not sure how you generate your requirements.txt or poetry.lock, but those would need to be updated, too. If you give me the commands that you use (and the python version), I can run them and commit.

Hey @rb-synth ,
Thank you for your work! I've fixed the dependency versions in the toml file. Let me know if further adjustments are needed.


Add multi tenancy support

Add a way to have multiple tenants in Document Archiver with separate archiving folders.

Done in current SNAPSHOT build from today.


How to transfer ownership?

Hello, really well done project.
Today I launched rfm.sospedra.me
I'm looking for documentation to link maintainers that are looking to transfer their projects.
Do you cover this bit somewhere? I couldn't find it.
Thanks!

Thanks for the kind words! Not sure if we cover this or not but it's not an issue with this project so closing this for now. Thanks again!


Migration tool should consider supporting 'implicit-downcasts: false' users

Some packages (such as package:async) have in their analysis_options.yaml
analyzer:
  strong-mode:
    implicit-downcasts: false

It would seem like this is not relevant to the migration tool, because we will insert implicit downcasts for users. However, for two reasons this is not the case:

implicit downcasts from dynamic are allowed in nnbd, but not with the flag
with nullability, some relatives of dynamic may be migrated to subtypes

Ex:
dynamic d = 0;
Object o = d;

The migration for this introduces no changes. Which is a problem if you have implicit-downcasts: false, because
Object o = d;

is a downcast from dynamic in nnbd world. Which is accepted by default, but not accepted for projects with implicit-downcasts: false.
I think there are two solutions here:

detect this and insert casts as Object
(I suggest) removing the config from analysis_options

I suggest the latter because casts from dynamic were deliberately disabled because they are annoying and unlikely to be accidents. However, we may want to survey authors of these packages to check this :)
Its worth noting that there is a workaround: users can insert as Object into the code. It does not seem to get flagged as an unnecessary cast.

Note that @yjbanov brought this up in his meeting with the migration team on Aug 28.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


ISSUE #130 (solved) improved code and documentation for signup component

Changes Made:
Added Detailed Documentation:
Introduced a top-level description of the component to clarify its purpose.
Provided function-level comments for onSubmit and other critical sections.
Added inline comments to explain the behavior of input fields, buttons, and error messages.
Improved Error Handling:
Wrapped the onSubmit logic inside a try-catch-finally block to handle registration failures gracefully.
Updated feedback messages for a more user-friendly experience when errors occur during signup.
Code Formatting and Optimization:
Refactored the code for better readability with consistent indentation and spacing.
Used descriptive variable names and organized JSX elements to enhance clarity.
Impact:
Improved Maintainability: The added documentation will make it easier for future developers to understand and maintain the component.
Better User Experience: Enhanced error handling ensures meaningful feedback during failures.
Cleaner Code: Formatting improvements align with best practices for readability and structure.
This PR focuses on improving code quality without affecting the functionality of the Register component.

please mention issue no

I have mentioned in title #130

Well, these comments feels completely unnecessary, As all these functions are self explanatory.
Please consider some meaningful code contributions, as comments might not add any value as per our codebase and variable names.
Thanks for showing interest in this project <3


Remove redundant ASN1_INTEGER_set call

This trivial patch removes a duplicated call to ASN1_INTEGER_set.
Fixes Issue #6977
Signed-off-by: Eric Brown<EMAIL_ADDRESS>

Hi @levitte and @dot-asm , this PR has been approved 7 days ago, would you guys like me to merge this? :-)

Merged to 1.0.2, 1.1.0 and master.
Thanks.


Task checkboxes do nothing on click

First off, thank you for this extremely powerful plugin!
I don't know if this is supported, looking at tasks.ts I feel like it is (swapping rendered textbox and setting task checked in file).
However nothing happens, when clicking on the checkboxes. I also do not get any errors in the dev-console.
I am using dataviewjs to render the taskList like this:
dv.taskList(dv.pages('"" and !"templates" and !#someday').file.tasks.where(t => !t.completed), true);

Am I missing something or is it currently broken?

I had both, however today it works - really strange.
Since I also disabled all other plugins I think it was not a conflict with another plugin.
BUT it might be connected to the obsidian version (issue submitted on 0.11.3 - since yesterday on 0.12.3)
Does it work again for you @FekketCantenel ?

Note that several Obsidian versions broke this functionality (some internal API bugs), though it works on recent versions.

I'm on 0.12.3. I tried just now to check the box of a task embedded from my daily notes using dataviewjs. The checkbox worked visually but didn't send a signal to the file to check the box; when I reloaded, it was visually unchecked again.

@FekketCantenel if you are still seeing this issue on the most recent version, we will probably have to do a little extra debugging since I haven't been able to reproduce locally. Can you give what your query is, as well as a little snippet of the file the tasks come from?

In my Meta MOC:
```dataviewjs
dv.taskList(dv.pages("#meta").file.tasks
    .where(t => !t.completed))
```

In today's Daily Notes:
* [ ] test #meta

The dataviewjs pulls in the task fine. If I check the original task in Daily Notes and switch back to the MOC, after a few seconds the task is checked and disappears.
Same scenario, but I check the embedded task in the MOC dataviewjs. It visually checks, and then a few seconds later unchecks (as if updating with the true task's status). In the Developer Tools Console, the task's object pops up in the console the exact same as if I created it/unchecked it in the native file.
Is it possible that the every-few-seconds update poll is overriding the process that marks the checkbox in the original file?

Still seeing problems on latest version?

I've just upgraded to Dataview 0.3.12 and repeated the above steps. Checking boxes across files now works perfectly!
This codeblock pulls all tasks from a file if it has #meta anywhere. I expected it to only pull specifically tagged tasks — but I've learned over the past few weeks that Obsidian is much more page-based than block-based, so this behavior makes sense.


Prepare datasets and annotations

When I was doing Prepare datasets and annotations, there was an error using cp -r /path_to_crowdhuman_dataset/CrowdHuman_train crowdhuman/CrowdHuman_train.
Error: cp: cannot stat '/path_to_crowdhuman_dataset/CrowdHuman_train': No such file or directory

I created the crowdhuman_train and mot_train folders directly by hand, and put the training data sets in mot and crowdhuman. I don't know if it's right, because the accuracy dropped after I ran it.

@tran7777777
Hi
Are you using multiple GPUs or single GPU? I am currently unable to run the code successfully

@tran7777777
Can you tell me the cuda version, python version, torch version used? Thanks

11.3  3.8  1.12.1
single GPU

@tran7777777
thank you!I think we can communicate more. can you give me a contact.

I created the crowdhuman_train and mot_train folders directly by hand, and put the training data sets in mot and crowdhuman. I don't know if it's right, because the accuracy dropped after I ran it.
Hi, could you tell me the structure under the crowdhuman folder? After downloading the CH dataset, I find there are three folders called CrowdHuman_train01, CrowdHuman_train02 and CrowdHuman_train03. Should I put them in the crowdhuman folder or mix the images in the 3 folders into one folder named CrowdHuman_train?


Wirc full pipeline

Adds full functionality to reduce IR data (based on the WIRC pipeline). There are some issues to be sorted with the quaity of the photometric calibration (errorbars don't quite match those from wircpipe). Will be addressed in a separate PR.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

541 of 781 (69.27%)  changed or added relevant lines in 41 files are covered.
9 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.8%) to 82.75%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mirar/pipelines/winter/generator.py
13
14
92.86%

mirar/pipelines/winter/winter_pipeline.py
4
5
80.0%

mirar/processors/astrometry/autoastrometry/autoastrometry.py
7
8
87.5%

mirar/processors/bias.py
2
3
66.67%

mirar/processors/utils/image_loader.py
22
23
95.65%

mirar/catalog/gaia.py
18
21
85.71%

mirar/pipelines/wirc/load_wirc_image.py
35
38
92.11%

mirar/processors/sky.py
3
6
50.0%

mirar/processors/mask.py
103
107
96.26%

mirar/processors/astromatic/swarp/swarp.py
48
53
90.57%

Files with Coverage Reduction
New Missed Lines
%

mirar/processors/astromatic/sextractor/sourceextractor.py
1
75.73%

mirar/processors/utils/multi_ext_parser.py
1
41.1%

mirar/processors/astromatic/sextractor/settings.py
2
66.67%

mirar/processors/base_processor.py
2
97.93%

mirar/processors/astromatic/scamp/scamp.py
3
95.45%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
8107

Relevant Lines:
9797

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

552 of 792 (69.7%)  changed or added relevant lines in 47 files are covered.
13 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.8%) to 82.75%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mirar/pipelines/winter/generator.py
13
14
92.86%

mirar/pipelines/winter/winter_pipeline.py
4
5
80.0%

mirar/processors/astrometry/autoastrometry/autoastrometry.py
7
8
87.5%

mirar/processors/bias.py
2
3
66.67%

mirar/processors/utils/image_loader.py
22
23
95.65%

mirar/catalog/gaia.py
18
21
85.71%

mirar/pipelines/wirc/load_wirc_image.py
35
38
92.11%

mirar/processors/sky.py
3
6
50.0%

mirar/processors/mask.py
103
107
96.26%

mirar/processors/astromatic/swarp/swarp.py
48
53
90.57%

Files with Coverage Reduction
New Missed Lines
%

mirar/processors/astromatic/sextractor/sourceextractor.py
1
75.73%

mirar/processors/utils/multi_ext_parser.py
1
41.1%

mirar/processors/astromatic/sextractor/settings.py
2
66.67%

mirar/processors/base_processor.py
2
97.93%

mirar/processors/astromatic/scamp/scamp.py
3
95.45%

mirar/pipelines/winter/models/_proc.py
4
93.65%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
8107

Relevant Lines:
9797

💛  - Coveralls


Does the Handmark/handTracking model have training code and data sets?

Does the Handmark/handTracking model have training code and data sets?

Hi @LMR2018, Please refer this issue https://github.com/google/mediapipe/issues/2123#issuecomment-974152958 for your query . Thanks!


Moblenet V2: Importing graph with lower producer version into a graph with higher producer version

I developing a transfer learning application where I am retraining MobileNetV2 for my data stream.
I am retraining the model with retrain.py from tensorflow-hub and have made no modifications.
When I run the script from a terminal, I get this warning directly after the model is downloaded to a temporary directory in my user profile.
Importing a graph with a lower producer version 26 into an existing graph with producer
version 27. Shape inference will have run different parts of the graph with different
producer versions.

During my debugging efforts, I created a test.py script to find out where the warning is coming from:
import tensorflow as tf
import tensorflow_hub as hub

def create_module_graph(module_spec):
  """Creates a graph and loads Hub Module into it.

  Args:
    module_spec: the hub.ModuleSpec for the image module being used.

  Returns:
    graph: the tf.Graph that was created.
    bottleneck_tensor: the bottleneck values output by the module.
    resized_input_tensor: the input images, resized as expected by the module.
    wants_quantization: a boolean, whether the module has been instrumented
      with fake quantization ops.
  """
  FAKE_QUANT_OPS = ('FakeQuantWithMinMaxVars',
                     'FakeQuantWithMinMaxVarsPerChannel')
  height, width = hub.get_expected_image_size(module_spec)
  with tf.Graph().as_default() as graph:
    resized_input_tensor = tf.placeholder(tf.float32, [None, height, width, 3])
    m = hub.Module(module_spec)
    bottleneck_tensor = m(resized_input_tensor)
    wants_quantization = any(node.op in FAKE_QUANT_OPS
                             for node in graph.as_graph_def().node)
  return graph, bottleneck_tensor, resized_input_tensor, wants_quantization

def main():

   module_spec = hub.load_module_spec('https://tfhub.dev/google/imagenet/mobilenet_v2_100_96/classification/2')

   graph, bottleneck_tensor, resized_input_tensor, wants_quantization = create_module_graph(module_spec)

if __name__ =='__main__':
   main()

And found it originated from the create_module_graph function in retrain.py.  When I run the script from the terminal using python test.py, I get producer warning from above.  However, when I run main() from an ipython console I do not get the producer version warnings.
What do these warnings mean?
My tensorflow info:
# packages in environment at C:\Anaconda3\envs\dl_tools:
#
# Name                    Version                   Build  Channel
tensorflow-gpu            1.11.0                    <pip>
tensorflow-hub            0.1.1                     <pip>

i have the same question

Hi, danhamill and Builtor, thanks for reaching out.
TensorFlow Hub modules contain tf.GraphDefs at the core, and these have a format version number to help with correctly importing graphs into newer versions of TensorFlow. It so happened that this format version was bumped from 26 to 27 between the upload of TF-Hub modules for the public launch on 31 March 2018 and the current TensorFlow release.
However, we are currently not aware of any visible effect on module users from the reported change in shape inference, so our current recommendation is to ignore these warnings. They will go away with the
next refresh of modules.
Please speak up if you do experience an actual problem in using them. -- I'm keeping this bug open for that.
Thank you
arnoegw

Thanks for the information @arnoegw.  I haven't had any problems, but will report back if I do.

@danhamill  Any update on this ? If you haven't faced any issues(till date), please do let us know. We will close this issue. Thanks !

No Updates.  Considered this issue closed.

I am getting this same issue:
tensorflow/core/graph/graph_constructor.cc:1248] Importing a graph with a lower producer version 22 into an existing graph with producer version 26. Shape inference will have run different parts of the graph with different producer versions.


Move ExecCtx function implementations to .cc file

when they're accessing TLS variables.
I ran into a segmentation fault, when running a client application built
in Release mode linking to shared gRPC libraries (also built in Release
mode) on Windows. Running the same application with gRPC libraries built
in Debug mode was fine. After searching around I found the issue was
to do with the global grpc_init() specifically with
grpc_iomgr_init(). The crash was happening during the construction of
an ExecCtx instance. This class has a thread local member variable
which is getting modified during construction and desctruction.
Accessing the value of the TLS member variable in the header file was
always resulting in a segmentation fault. Moving these functions where
this variable is accessed to the source file fixed things for me. The
same applies also for the ApplicationCallbacExecCtx class.

Frankly, I don't have any real experience with thread-local variables. I can just say that this patch works for me on my system. Maybe someone who has more insight into how TLS variables work has a clue why I was getting this behaviour when the thread-local variables were accessed in the header file.
Just for reference:

System: Windows 10
Compiler: MinGW GCC 7.3
Build-System: CMake

@drfloob

@FMeinicke I think this is because you're using the old version of gRPC. With the latest one, you should be able to use pthread one by defining GPR_PTHREAD_TLS.

Closing this PR since this PR has a potential performance implication.


Added method for speaker playback on Android

related to https://github.com/zmxv/react-native-sound/issues/66
implemented the android version of this, using setSpeakerphoneOn's method of AudioManager: https://developer.android.com/reference/android/media/AudioManager.html#setSpeakerphoneOn(boolean)

We already have this working on ios?

#194

Already merged renanpupin's modified PR


Is there any way to get involved without using Discord?

Is there any way to get involved for people who don't use Discord? (I'm reading this page.)

You can join #wasm on Mozillas IRC server: https://wiki.mozilla.org/IRC and say hello as well :blush:

Thanks.


Add the ability to test stderr + improve integer overflow stuff

Do not merge before #174

(cc @linusg )


Invalid SteamID32/64 saved in database when saving trade offer url

As posted earlier on another issue on how to fix i will post it here again:
Few people seems to have issues when it comes to saving their steam trade offer url. This occurs due the steamid32/64 being saved incorrectly in the database.
How to fix in 2 edits:
First edit:
From here: https://github.com/ztizzlegaming/CSGOWinBig/blob/master/src/php/save-trade-token.php#L37
Line 37 till 43 replace them with the lines i posted below.
# Get steam id
$steamUserId = $steamprofile['steamid'];
# Convert steam 64 id to steam 32 id
//Get the steamid (really the community id)
$communityid = $steamUserId;
//Get the map name
//See if the second number in the steamid (the auth server) is 0 or 1. Odd is 1, even is 0
$authserver = bcsub($communityid, '76561197960265728') & 1;
//Get the third number of the steamid
$authid = (bcsub($communityid, '76561197960265728')-$authserver)/2;
//Concatenate the STEAM_ prefix and the first number, which is always 0, as well as colons with the other two numbers
$steam32Id = "STEAM_0:$authserver:$authid";

Second edit:
https://github.com/ztizzlegaming/CSGOWinBig/blob/master/src/php/deposit.php#L19 & https://github.com/ztizzlegaming/CSGOWinBig/blob/master/src/php/check-items.php#L19
Line 19 till 23 replace them with lines posted below.
# Convert Steam ID to Steam64 ID
$idParts = explode(':', $tradeOwnerSteamId32);
$authServer = $idParts[1];
$accountNumber = $idParts[2];

function steamid32ToSteamid64($steamid32) {
    $iServer = "0";
    $iAuthID = "0";

    $szTmp = strtok($steamid32, ":");

    while(($szTmp = strtok(":")) !== false)
    {
        $szTmp2 = strtok(":");
        if($szTmp2 !== false)
        {
            $iServer = $szTmp;
            $iAuthID = $szTmp2;
        }
    }
    if($iAuthID == "0")
        return "0";

    $steamId64 = bcmul($iAuthID, "2");
    $steamId64 = bcadd($steamId64, bcadd("76561197960265728", $iServer));
	$part = explode('.',$steamId64);
	return $part[0];
}

//$tradeOwnerSteamId64 = ($accountNumber * 2) + ($authServer +<PHONE_NUMBER>0265728);
$tradeOwnerSteamId64 = steamid32ToSteamid64($tradeOwnerSteamId32);

https://github.com/ztizzlegaming/CSGOWinBig-SteamBot/issues/12#issuecomment-142183030 still testing this so far it keeps working so its good right?

Hi, I appreciate the work you have put into this. If you want to use this instead of what I have done, by all means, go for it. However, for me at least, my code for calculating the steamID64 works, as I have shown out here: http://pastebin.com/MJcHAFw1. If your code doesn't work for calculating it and this does, by all means, use this method, but I am going to continue using what I have.

@ztizzlegaming  i know it works but for some reason it doesn't for other people.
So maybe it's nice to leave it as footnote ;).

Should<PHONE_NUMBER>0265728 be replaced with my bots 64ID?

@optiix no absolutely not. Its a number required for calculation. Do not mess with it.

@TheAnthonyNL
Okey. Thanks!

@TheAnthonyNL Is this fix still working?

Its implemented in latest version so yes.


[Java] parquet-arrow is broken due to different JDK version

Parquet was recently update to use Arrow 0.8.0 to resolve this JIRA: https://issues.apache.org/jira/browse/PARQUET-1128 but unfortunately the issue is actually not resolved because Arrow 0.8.0 uses JDK 7 and Parquet uses JDK 8.
I have filed a Jira against Arrow to upgrade to JDK 8: https://issues.apache.org/jira/browse/ARROW-2498
Once this is done, we will need to update parquet-arrow to use the new version of arrow.
Reporter: Andy Grove / @andygrove
Related issues:

[Java] Upgrade to Arrow 0.10.0 (duplicates)

Note: This issue was originally created as PARQUET-1278. Please see the migration documentation for further details.

Nándor Kollár / @nandorKollar:
@andygrove  I resolved this Jira since it looked like it is a duplicate of PARQUET-1390
Feel free to reopen if I was wrong.


L7 Visibility support in Antrea

L7 Network flow visibility enables visibility into the layer 7 protocols as we did for the l3/l4 earlier.
This feature enables the user to visualize L7 protocol information using 2 methods

Using L7 NP
Using Pod or namespace Annotations

Annotation key used is "l7visibility" and the value is the direction for which the flow visibility is required, which could be (ingress/egress/both).
Based of the annotation or the NP, the fields ("isL7", "httpVals") are populated and exported.
### - Design:
L7Visibility is to be designed in order to receive all the protected and unprotected flows of Layer7 type and to be visualized.
In order to complete this feature, we need the following flows.

L7visibility using the L7NPs:

A Layer7 NP when applied to the cluster will trigger the Suricata to start on the corresponding node. This is a current design flow used in Layer 7 engine.

Suricata is then leveraged to send this information to the exporter and exporter uses this information and connects it with the Layer 4 flow to create a complete Network flow .

The network flow is exported to the assigned exporters.
Fields used in the exporters are defined later.

L7 Visibility using the Annotations.

The flows that are not part of the L7 NP, can also be visualized using the pods and Namespace annotations.
The annotation key used here is "l7Visibility.antrea.io".
User can annotate pods or namespaces with the annotation key and a value for the traffic flow direction from the following (Ingress/Egress/both).
By default, there will not be any L7visibility information received by the exporter, i.e. none of the pods or namespaces are annotated by default.
Based off the annotation, the L7 watcher will recieve the pod or namespace event. L7watcher would use localPodInformers and namespace informers for this task.
Once the correct annotation key-value is received, the pod or pods in an annotated namespace would mirror their traffic to Suricata using Traffic control mark flows
Suricata will send the traffic flows information of these mirrored traffic. We currently only support HTTP traffic flows and thus these flows will be the only flows from Suricata to the exporter.
Exporter will then populate the necessary fields and export them to the exporters.

Deletion of the flows.

Similar to install of new Traffic control mark flows. The deletion of the mark flows will also be taken care of based of two scenarios.
User removes the annotations.
User deletes the pod or namespace. Only the ready pods or ready pods inside an annotated Namespace will have the corresponding traffic flows.
Once any of the two scenarios are met. The corresponding Traffic mark flow will be removed.

New Fields to be added in the exporter.

isL7: This field will help visualize only the l7 flows if required. It is used to also take care of future L7 protocols implementations which may require adding new fields and "isL7" to provide the differentiating field for L7 flows from L3/L4 flows.

HttpVals: This field is used and should contain all the http fields (in order) corresponding to a network flow. The fields are:
[Hostname, URL, UserAgent, ContentType, Method, Protocol, Status, ContentLength]

@tushartathgur you need a description of the change in the commit message and the PR description.
The referenced issue (fixes: #5398) does not look correct. There is already a separate, dedicated PR to address that issue.

I think there are some pretty large changes that are required:

the controller is not designed correctly at the moment (creation of individual watches, watching all the Pods in the cluster, no workqueue pattern)
I don't believe we should actually create a TrafficControl CR (instead we should reuse internal APIs for traffic control implementation). This would be a more streamlined implementation. And I don't think the Agent should have the RBAC permissions to create arbitrary TrafficControl CRs.

Typically, for a change like this, you want to first create a kind/design issue proposal, before implementing the feature. This way you can describe the design you have in mind (at a high-level), and get early feedback. Opening the issue may still be the right thing to do here.
As an aside, you are still referencing issue #5398 in your PR description, which is inaccurate. We have a dedicated PR to address that issue.

Thanks @antoninbas and @tnqn  for the above suggestions, I have added a new commit with the following changes

Redesigned l7Watcher(added workqueue, added informers)
Used TCmarkflows on place of TC CR
start Suricata only once

/test-all

/test-all

/test-all

Maintainers had came to an agreement that this can be moved to next release.

@tushartathgur  please help to resolve code conflicts.

@tushartathgur when addressing comments, please only reply them and leave it unresolved, this would be easier for reviewers to check their comments and close them after confirming, without expanding every comment again.

Please squash the commits and have a proper commit message.

Please squash the commits and have a proper commit message.

@tushartathgur we can't merge all 27 commits for this feature, while squashing via github will only generate a commit message simply based on all commit titles. Can you squash the commits and have a proper commit message?

@yuntanghsu could you take one more look at the new e2e test?

/test-all

The new e2e test failed

/test-all


Add gamesounds.xyz

Add another resource I found the today.

Hey @englercj , can you keep the list in alphabetical order, please?

Oops, sorry about that!
Updated to be first, since "Free" is before "Freesounds" when sorting alphabetically.

Thanks!


Generate model files as part of build process. Changes forked from PR #27

Generates model files using swagger code-gen during the build phase.
The PR is a fork of #27 created by @stepheno

Thanks for finishing this out, I had forgotten about this PR

Thank you, this is much needed! I will be testing this out and merging in the next few days.

Thank you @kishorenc


Move to "Whaka-project"

We got ourselves an organization account: https://github.com/Whaka-project
Transfer main repo in there.

https://github.com/Whaka-project/whakamatautau-util

Fix SCM configuration in the POM


chore(main): release 0.0.7

:robot: I have created a release beep boop
0.0.7 (2024-03-04)
Bug Fixes

Checksum errors with some MCP2-generated card images (#84) (73448ec)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/bodgit/psx/releases/tag/v0.0.7 :sunflower:


ERROR weewx.reportengine:         ****  No module named 'Cheetah', ... (and 'Images' and Rsync)

🐛 Bug Report
Running latest Raspberry Pi OS and Docker.  Utilized template docker-compose.yml with minor tweaks for my environment.  weewx runs fine pulling data from my IP based David Vantage Pro 2.  Submissions to Wunderground and other providers operating as expected.  Web Page generation fails due to missing Cheetah and Images modules.  Further, Rsync also appears to be missing from image.
My compose looks as follows:
version: "2.3"
services:
  weewx:
    container_name: weewx
    image: felddy/weewx
    network_mode: host
    environment:
      - TIMEZONE=US/Eastern
      - WEEWX_UID=weewx
      - WEEWX_GID=weewx
    volumes:
      - /srv/dev-disk-by-label-dune/Configs/weewx:/data
    restart: always

Variance from template compose file is due to using Portainer v2.0 on Rpi, which is limited to v2.x composer format.  I've been unable to utilize the "init: true" as it is unsupported and alternatives do not seem to work either.  Unsure if this prevents some internal process your created to install these services, but was unable to locate any references to installing the services post deployment.
Very appreciative for your efforts as one of the few (only?) armhf builds; other main images are 64bit.  Here's a broader snapshot of error log:
Sep 11 08:46:18 weewx[17] INFO weewx.manager: Added record 2020-09-11 08:46:00 EDT<PHONE_NUMBER>) to database 'weewx.sdb',
Sep 11 08:46:18 weewx[17] INFO weewx.manager: Added record 2020-09-11 08:46:00 EDT<PHONE_NUMBER>) to daily summary in 'weewx.sdb',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine: Unable to instantiate generator 'weewx.cheetahgenerator.CheetahGenerator',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  No module named 'Cheetah',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  Traceback (most recent call last):,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/reportengine.py", line 180, in run,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      obj = weeutil.weeutil.get_object(generator)(,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      mod = __import__(module),
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/cheetahgenerator.py", line 66, in <module>,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      import Cheetah.Filters,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  ModuleNotFoundError: No module named 'Cheetah',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  Generator ignored,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine: Unable to instantiate generator 'weewx.imagegenerator.ImageGenerator',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  No module named 'Image',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  Traceback (most recent call last):,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weeplot/genplot.py", line 15, in <module>,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      from PIL import Image, ImageDraw,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  ModuleNotFoundError: No module named 'PIL',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  ,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  During handling of the above exception, another exception occurred:,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  ,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  Traceback (most recent call last):,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/reportengine.py", line 180, in run,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      obj = weeutil.weeutil.get_object(generator)(,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      mod = __import__(module),
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weewx/imagegenerator.py", line 19, in <module>,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      import weeplot.genplot,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****    File "/home/weewx/bin/weeplot/genplot.py", line 17, in <module>,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****      import Image, ImageDraw,
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  ModuleNotFoundError: No module named 'Image',
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine:         ****  Generator ignored,
Sep 11 08:46:19 weewx[17] INFO weewx.reportengine: Copied 0 files to /data/www,
Sep 11 08:46:19 weewx[17] ERROR weeutil.rsyncupload: rsync does not appear to be installed on this system. (errno 2, 'No such file or directory'),
Sep 11 08:46:19 weewx[17] ERROR weewx.reportengine: rsyncgenerator: Caught exception '<class 'FileNotFoundError'>': [Errno 2] No such file or directory: 'rsync',
Sep 11 08:46:19 weewx[17] INFO weewx.restx: PWSWeather: Published record 2020-09-11 08:46:00 EDT<PHONE_NUMBER>),
Sep 11 08:46:20 weewx[17] INFO weewx.restx: Wunderground-RF: Published record 2020-09-11 08:46:20 EDT<PHONE_NUMBER>),
Sep 11 08:46:20 weewx[17] INFO weewx.restx: Wunderground-RF: Published record 2020-09-11 08:46:20 EDT<PHONE_NUMBER>),

I do have the same issue, running a normal Linux installation.

I needed to install Cheetah3 within the image manually to get it working. Maybe this is because you changed from python alpine to slim?

Hey @felddy and others,
did you ever solve this? I've just spent a few minutes on this but wasn't able to get it working with the multi-stage approach.

The following diff represents what I ended up with. It's not a satisfying solution but maybe it helps others while we figure out how to solve this is a better way :) Best!
diff --git a/Dockerfile b/Dockerfile
index b61a104..526132f 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -2,13 +2,14 @@ FROM python:3-alpine as stage-1

 ARG WEEWX_UID=421
 ENV WEEWX_HOME="/home/weewx"
-ENV WEEWX_VERSION="4.4.0"
+ENV WEEWX_VERSION="4.5.1"
 ENV ARCHIVE="weewx-${WEEWX_VERSION}.tar.gz"

 RUN addgroup --system --gid ${WEEWX_UID} weewx \
   && adduser --system --uid ${WEEWX_UID} --ingroup weewx weewx

 RUN apk --no-cache add tar
+#RUN apk --no-cache add py3-pillow zlib-dev jpeg-dev build-base

 WORKDIR /tmp
 COPY src/hashes requirements.txt ./
@@ -26,6 +27,7 @@ RUN chown -R weewx:weewx ${WEEWX_HOME}
 # Python setup
 RUN python -m venv /opt/venv
 ENV PATH="/opt/venv/bin:$PATH"
+RUN pip install --no-cache wheel
 RUN pip install --no-cache --requirement requirements.txt

 WORKDIR ${WEEWX_HOME}
@@ -34,12 +36,17 @@ RUN bin/wee_extension --install /tmp/weewx-mqtt.zip
 RUN bin/wee_extension --install /tmp/weewx-interceptor.zip
 COPY src/entrypoint.sh src/version.txt ./

-FROM python:3-slim as stage-2
+FROM python:3 as stage-2

 ARG TARGETPLATFORM
 ARG WEEWX_UID=421
 ENV WEEWX_HOME="/home/weewx"
-ENV WEEWX_VERSION="4.4.0"
+ENV WEEWX_VERSION="4.5.1"

 # For a list of pre-defined annotation keys and value types see:
 # https://github.com/opencontainers/image-spec/blob/master/annotations.md
@@ -55,9 +62,15 @@ RUN apt-get update && apt-get install -y libusb-1.0-0 gosu busybox-syslogd tzdat

 WORKDIR ${WEEWX_HOME}

-COPY --from=stage-1 /opt/venv /opt/venv
+#COPY --from=stage-1 /opt/venv /opt/venv
 COPY --from=stage-1 ${WEEWX_HOME} ${WEEWX_HOME}

+RUN pip install --no-cache wheel setuptools
+RUN pip install --no-cache configobj paho-mqtt pyserial pyusb
+RUN pip install --no-cache Cheetah3
+RUN pip install --no-cache Pillow
+
 RUN mkdir /data && \
     cp weewx.conf /data

diff --git a/src/hashes b/src/hashes
index 69e40eb..2945e6d 100644
--- a/src/hashes
+++ b/src/hashes
@@ -1,3 +1,3 @@
-4ad1f8ff990ce86d80b3bc5448d5545e67e8b42ac14fc6a041b7734740e846c5  weewx-4.4.0.tar.gz
+9650f9a4ce0f300a652d926820bc5b683a1826fd668c0e71413e88c772d7f056  weewx-4.5.1.tar.gz
 9580cc3e3d617d20ffc42138712634850f37716a1257e9da0516407970765813  weewx-mqtt.zip
 6229d493acd051730530ab50c235f57cc7f9c53dc1a8060c7b6e4817dd2bf66d  weewx-interceptor.zip

I have this issue  also.   Could  you please let me know how I can resolve it.   Many thanks

I have this issue too.  fedora 35.

A possible solution is using felddy/weewx as a base for your own image where the dependencies/libraries you need have been preinstalled. Here is an example that I'm using where I wanted mysql support, html report support, and the weewx-weatherlink-live driver. This formula has worked for me and may solve the issues that others have seen around missing python libraries.
FWIW I think it'd make sense to "upstream" some of this into the main felddy/weewx image - for example it probably wouldn't hurt to include the mysql support and common HTML rendering libraries "out of the box".
Quick explanation of what's going on in the below steps:

The first image is downloading a release of the weewx-weatherlink-live driver and then exiting. In theory this could be done in the main felddy/weewx image but I didn't think it made sense to install curl just for this one thing. This is only relevant for people who have a Davis WeatherLink Live and so it arguably isn't needed in the main felddy/weewx image.
The second image then does the bulk of the work installing various prerequisites:

Installs system dependencies for mysql support via apt-get:

libmariadb-dev-compat for weewx mysql support
gcc, for pip install mysqlclient to work (then uninstalled afterwards)

Installs pip/python libraries needed for mysql support, for the weewx-weatherlink-live driver that I'm using, and for HTML rendering to work (note: the preceding cd command into the venv is required or else the pip command for whatever reason doesn't actually install anything - this took hours to figure out):

MySQLdb for weewx mysql support
requests as required by weewx-weatherlink-live
Cheetah3 and Pillow as required for generating HTML reports (I'm just using Seasons right now)

Uninstalls gcc again as it's no longer needed after the pip install has completed (avoids wasting space in the final image)
Runs a python -c import statement as a sanity check that the libraries installed. If you add other libraries to the pip install command, it'd make sense to add them to this import statement to check that they actually work as part of the image build.
Runs wee_extension --install to install the downloaded weatherlink-live driver package that was copied over from the first image, then removes the redundant package file.

FROM docker.io/library/debian:bullseye-slim

# weewx image doesn't have curl/wget so just download from separate stage
ENV EXTENSION_VERSION=v1.0.11
RUN apt-get update \
  && apt-get install -y curl \
  && apt-get clean \
  && rm -rf /var/lib/apt/lists /var/cache/apt/archives \
  && curl \
  -Lo /tmp/weewx-weatherlink-live.tar.xz \
  https://github.com/michael-slx/weewx-weatherlink-live/releases/download/${EXTENSION_VERSION}/weewx-weatherlink-live-${EXTENSION_VERSION}.tar.xz

FROM docker.io/felddy/weewx:4.5.1

COPY --from=0 /tmp/weewx-weatherlink-live.tar.xz /tmp/weewx-weatherlink-live.tar.xz
# - install prerequisites for running pip install
# - install needed python packages to venv via pip (apt-get installs to host)
#   note that CD TO SITE-PACKAGES IS REQUIRED because pip just installs to cwd for some reason
# - uninstall gcc after completing pip install
# - install weatherlink-live extension
RUN apt-get update \
  && apt-get install -y gcc libmariadb-dev-compat \
  && apt-get clean \
  && rm -rf /var/lib/apt/lists /var/cache/apt/archives \
  && which pip \
  && cd /opt/venv/lib/python3.10/site-packages/ \
  && /opt/venv/bin/pip install --no-cache-dir mysqlclient requests Cheetah3 Pillow \
  && apt-get remove --purge -y gcc \
  && apt-get autoremove --purge -y \
  && /opt/venv/bin/python -c 'import MySQLdb, requests, Cheetah, PIL.Image' \
  && ${WEEWX_HOME}/bin/wee_extension --install /tmp/weewx-weatherlink-live.tar.xz \
  && rm -v /tmp/weewx-weatherlink-live.tar.xz

In any case, it should be possible to take the above steps as an example and update them to install what you need (while removing the stuff you don't need). In this case the resulting image ends up being around 90MB vs around 65MB for the original, so not too bad.
Also, if anyone happens to find this because they are running weewx-weatherlink-live in a Docker image, note that you need the container on the same subnet as the WeatherLink Live in order for UDP broadcasts to work and reports to be generated. This can be accomplished by running the container with --network=host/hostNetwork: true.

To confirm, to get my reports generating I had to run pip install Cheetah3 pillow in the container.

@felddy did you consider releasing a new image with these changes?

I'm sorry.  I've totally neglected this issue.  I'm catching up on this repo's PRs and issues now.  I'll chime in on this after I have a chance to digest it.

I'm sorry. I've totally neglected this issue. I'm catching up on this repo's PRs and issues now. I'll chime in on this after I have a chance to digest it.

@felddy sorry but if that modules are missing and the Docker Hub Image is not working, why you are still releasing it on docker hub?

@felddy was this ever resolved? I can see you made a lot of updates to the repo. But it seems its still not generating the html reports for me with the same error described in this issue.
I also opened this discussion before I realised it might be related to this: https://github.com/felddy/weewx-docker/discussions/210

Not only has this not been resolved, but #88 is so out of date, that the file that the patch was applied to no longer exists.
At this point, this project looks like abandonware.
Shame. It almost works. Someone with more time and than me could probably get it back up and running, or maybe get a working Docker working.

Hello @felddy,
are you still eager to maintain this project? If not, I want to propose to create a successor fork over at https://github.com/rejuvenate - We aim to provide a place for projects maintained by multiple active community members.
If everyone agrees I will create the fork over the next couple of days. @jonathankoren, @nickbp, all others and @felddy: Who would like to be added as maintainer to the project?

Hello @felddy, are you still eager to maintain this project? If not, I want to propose to create a successor fork over at https://github.com/rejuvenate - We aim to provide a place for projects maintained by multiple active community members.
If everyone agrees I will create the fork over the next couple of days. @jonathankoren, @nickbp, all others and @felddy: Who would like to be added as maintainer to the project?

This project is licensed CC0.  You have the freedom to do anything you'd like with the code.  I do not need to be a maintainer on any forks, but I appreciate the offer.
I apologize for not being more attentive to this feature.  I have a hard time telling people "No".  That said, I don't think it is a good fit for this repo.  There is a slippery slope to installing "all the things" and then having to test and support them forever.  As you have pointed out, it is easy enough to fork and extend the container.
In the future I'll port over the CONTAINER_PATCHES functionality that I implemented in my FoundryVTT container.  This has proven to be a useful way for users to add a-la-cart functionality and extensions to the container, and a good alternative to creating a new image for those without Docker skills.
At that time I'll remove default extensions like interceptor or mqtt and document how to configure them at container startup.
Thank you all for contributing.

Cross posted from #88
I was able to manually add pillow and cheetah to my running container as follows:
With weewx container running
docker exec -it -u 0 weewx bash
pip install Pillow==9.4.0
pip install CT3
restart weewx container
Ubuntu 22.04
The html files are now properly generated.
It would be nice to have them added to the image but I do not have the knowledge to do that.

Thanks @felddy for your explanation. It's great to see you active and I respect your opinion.
I will release a docker image that is based on the one here, but add the most obvious extensions, including interceptor, mqtt, or Pillowwith some useful additions. I already have it configured locally.


NO list of supported LINUX versions if NOT sudo

You have a list of supported OS versions if the account being used to do discovery is sudo'ing. However there is no indication of supported OSses if the account is not sudo.
If you provide a list for one thing you MUST provide a list for the alternate.

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

ID: 60d3e532-e3e5-219a-ce0c-502b48faaebb
Version Independent ID: 19765a75-4ee0-7ce7-5d34-1cac117cf80c
Content: Discover physical servers with Azure Migrate Discovery and assessment - Azure Migrate
Content Source: articles/migrate/tutorial-discover-physical.md
Service: azure-migrate
GitHub Login: @Vikram1988
Microsoft Alias: vibansa

@fearofweapons Thank you for your question. If I understand your query correctly, you are looking for a list of OS for LINUX versions if NOT sudo. In that case, you need to follow these steps:

The list of supported OS Linux version would remain the same.

No.
I am not looking for the list. Your documentation does not state if the list of servers supported by using a sudo account is the same as if using a non sudo account. The list of supported servers is in the sudo section and it is implied that this is the supported list for sudo accounts and there is a different list for non sudo accounts.
Regards,
Richard
From: SadiqhAhmed-MSFT @.>
Sent: 05 August 2021 15:18
To: MicrosoftDocs/azure-docs @.>
Cc: Richard Trusson @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] NO list of supported LINUX versions if NOT sudo (#79324)
@fearofweaponshttps://github.com/fearofweapons Thank you for your question. If I understand your query correctly, you are looking for a list of OS for LINUX versions if NOT sudo. In that case, you need to follow these steps:
[image]https://user-images.githubusercontent.com/44458118/128365550-f98e0127-c706-4d46-984a-4c50bb2c101c.png
The list of supported OS Linux version would remain the same.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/79324#issuecomment-893497436, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJER7C7RQTRHAYCYOI5O7TT3KMRHANCNFSM5BTQJEJA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

@fearofweapons This section makes it clear.

No – it does not.
It says if using a sudo account the following LINUX distributions are supported.
Then there is a new section talking about non sudo accounts, but no list of supported LINUX releases.
The list of supported LINUX distributions needs to be in a separate section titled – supported LINUX distributions.
Regards,
Richard
From: SadiqhAhmed-MSFT @.>
Sent: 05 August 2021 15:30
To: MicrosoftDocs/azure-docs @.>
Cc: Richard Trusson @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] NO list of supported LINUX versions if NOT sudo (#79324)
@fearofweaponshttps://github.com/fearofweapons This section makes it clear.
[image]https://user-images.githubusercontent.com/44458118/128367477-1ff6f2e0-524a-4636-be33-35403635fdb9.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/79324#issuecomment-893506239, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFJER7DR7KWVGXXC6HAPSZLT3KN6JANCNFSM5BTQJEJA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

@Vikram1988 Could you please review "fearofweapons" request and update the doc as required.

@fearofweapons i am working with Engg to confirm the list of Linux OS variants supported specifically with root and setcap permissions. The list os very specific to "sudo" access as we have only tested it on these variants so far.

As advised by my manager @jyothisuri, closing the issues that are older than a year.
#please-close


[BUG] npm ci always fails when pdk is installed

Describe the bug
Similar to #282, npm ci raises an error when used with pdk, but this time I have found no workaround as long as we use npm. Please see the reproduction step.
Because npm ci is a crucial command for npm users to install dependencies without modifying package-lock.json, this issue effectively makes pdk unusable for npm users.
I see PDK assumes to be used with pnpm, but is the above behavior expected? I feel it is unreasonable to shut out npm, which is a default package manager for Node.js.
Expected Behavior
npm ci successes.
Current Behavior
npm ci fails with an error.
Reproduction Steps
# run the below commands in an empty directory:
$ npm init -y
$ npm i aws-prototyping-sdk
$ npm i # run this to avoid the error reported on #282
$ npm ci # still get an error below

npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR!
npm ERR! Missing<EMAIL_ADDRESS>from lock file

Possible Solution
This bundledDependencies part may be working unexpectedly in npm, as in https://github.com/aws/aws-prototyping-sdk/issues/282#issuecomment-1489757347.
https://github.com/aws/aws-prototyping-sdk/blob/cf57586f2567a571c734606d6f003f6a5051bfca/private/projects/nx-monorepo-project.ts#L22-L27
Additional Information/Context
No response
PDK version used
0.17.4
What languages are you seeing this issue on?
No response
Environment details (OS name and version, etc.)
macOS 12.6.5

Hi @tmokmss, the PDK project (this github repo) itself requires PNPM, but the nx-monorepo project does not require PNPM and should default to projen default packageManager of YARN.
Can you try using the individual packages rather than bundled aws-prototyping-sdk package (eg: @aws-prototyping-sdk/nx-monorepo). The bundled package seems to be having issues and we plan to deprecate it in near future.

Hi @JeremyJonas, you saved my day, thanks! Yeah I also think the bundled package should be deprecated and clearly described in README to avoid confusion.

Closed as part of: https://github.com/aws/aws-prototyping-sdk/pull/384

npm ci is failing for me too.
pdk 0.22.12
node v18.17.1
cd `mktemp -d`
pdk new --package-manager=npm monorepo-ts
npm ci

results in
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR!
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm ERR! [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm ERR! [--strict-peer-deps] [--no-package-lock] [--foreground-scripts]
npm ERR! [--ignore-scripts] [--no-audit] [--no-bin-links] [--no-fund] [--dry-run]
npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info

What package manager do maintainers of this repo use with pdk? Is everyone using pnpm?

Fixed as part of: https://github.com/aws/aws-pdk/pull/602
Be sure to install the latest @aws/pdk cli and re-try.
npm install -g @aws/pdk

This still fails for me using 0.22.30 😢
$ npm --version
9.6.7
$ node --version
v18.17.1
$ npx @aws/pdk --version
0.22.30
$ npx @aws/pdk new monorepo-ts --package-manager=npm
...
👾 Installing dependencies...
👾 install | npm install --legacy-peer-deps

up to date, audited 981 packages in 1s

212 packages are looking for funding
  run `npm fund` for details

3 moderate severity vulnerabilities

...
 >  NX   Successfully ran target eslint for 0 projects

Initialized empty Git repository in /home/pelle/test/pdk/pdk-test/.git/
[main (root-commit) 600f7ad] chore: project created with projen
 19 files changed, 12847 insertions(+)
 create mode 100644 .eslintrc.json
...
 create mode 100644 tsconfig.json

$ npm ci
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR!
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm ERR! [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm ERR! [--strict-peer-deps] [--no-package-lock] [--foreground-scripts]
npm ERR! [--ignore-scripts] [--no-audit] [--no-bin-links] [--no-fund] [--dry-run]
npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info


feature request: interpolation for snipmate snippets

snipmate.vim has the following feature:
snippet date
 	`system("date +%Y-%m-%d")`

This means that when I type "date" the trigger will get the date from the system. Is it possible to have on nvim-cmp?
Here is the documentation for snipmate.vim:
https://github.com/msanders/snipmate.vim/blob/master/doc/snipMate.txt

This is already supported but depends on the snippet engine you are using. E.g. UltiSnips (with cmp-nvim-ultisnips) can handle Vim script code but LuaSnip does not currently. If you don't use UltiSnips, another possibility is to convert the snippets to vsnip format and use vsnip as your snippet engine. For that, have a look at my plugin snippet-converter.nvim😄

Yes. It's depending on to the your snippet engine. So nvim-cmp does nothing for this. Sorry.


Storing data during on-the-fly image processing

Is there a recommended approach to storing data generated during on-the-fly image processing.
Using metadata seems to be an option, but I am unsure if there is a better way - especially for numpy arrays and loading that data some time after the acquisition has been written to disk
def demo_image_processing_fn(self, image, metadata):
  # Some image processing occurs generating some data
  data = []

  # Save this data (into metadata?)
  metadata['data'] = data

  # Can we discard the image, but not the data?
  return None, metadata

depends what type of data you're generating
If the data is an image, you could have the function return multiple images, both the original and the processed version (though it would have to be unit8 or uint16 I think)
https://pycro-manager.readthedocs.io/en/latest/img_processors.html#returning-multiple-or-zero-images

# Can we discard the image, but not the data?
  return None, metadata

No, Im pretty sure this will cause some kind of error
If you're just trying to save some numpy arrays and don't need your original image data, I would just implement your own data saving with numpy.savez or something similar

Thanks for the advice - in this instance it would be additional non-image data. So I think some own implementation as you suggsted is most appropriate.


feat(output): update the HTML output

Issue #548
Updated:

HTML output to be consistent with CLI output
Warnings and --help descriptions

Added:

Support dynamic columns

Thanks @ekifel! 😄  Merging this into the v0.9 branch which we will use going forward for v0.9 features.


Add logo

Here are some of the logo assets. Ping me if you need something specific at a given resolution :)
I'm open to different ideas of using the Fractal logo. E.g. using it instead of "Home", or showing it on the Home landing page.

I added it both to the home page and instead of "Home". It also appears in the browser tab as favicon.

That's awesome! :)


bufio\bufio.go: Is Peek() in Reader incorrect?

What version of Go are you using (go version)?

$ go version

go version go1.14.2 windows/amd64
Does this issue reproduce with the latest release?
Unkown
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\Xiaoyi\AppData\Local\go-build
set GOENV=C:\Users\Xiaoyi\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=E:\go
set GOPRIVATE=
set GOPROXY=https://goproxy.cn,https://goproxy.io,direct
set GOROOT=E:\Program Files\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=E:\Program Files\go\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\Xiaoyi\AppData\Local\Temp\go-build969071118=/tmp/go-build -gno-record-gcc-switches

What did you do?
package main

import (
	"bufio"
	"fmt"
	"io/ioutil"
	"os"
)

func main() {
	f, err := os.Open("b.txt")
	if err != nil {
		panic(err)
	}

	fmt.Printf("%p\n", f)
	peek1, _ := bufio.NewReader(f).Peek(4)
	fmt.Println("1=>", string(peek1))

	fmt.Printf("%p\n", f)

	peek2, _ := bufio.NewReader(f).Peek(4)
	fmt.Println("2=>", string(peek2))

	r, err := ioutil.ReadAll(f)
	if err != nil {
		panic(err)
	}
	fmt.Println(string(r))
}

What did you expect to see?
0xc000006028
1=> 1111
0xc000006028
2=> 1111

What did you see instead?
0xc000006028
1=> 1111
0xc000006028
2=>

You're creating a new buffered reader for each Peek call, but re-using the file descriptor. The first Peek call advances the file offset, because it has to fill the buffer so that it can read. The second Peek call happens on a fresh bufio.Reader, which uses the same file descriptor to read data. That file descriptor is probably at EOF at that point.
If you change your program to re-use the buffered reader, you should see the results you expect: https://play.golang.org/p/ukUoAvmA3r2
For questions like these in the future, please use one of the community venues listed here: https://golang.org/help/#help


[Bug]: hotkey to toggle widget doesn't focus on chat's text box

Before Reporting

[X] I have checked FAQ, and there is no solution to my issue
[X] I have searched the existing issues, and there is no existing issue for my issue

What happened?
When using the hotkey to present the chat window, its text box doesn't get the focus: not desired. However, when I click that blue dot to present the chat window, its text box does get the focus (as expected).
How to reproduce the bug.

Go to Copilot's settings and set a hotkey to toggle the widget (e.g.: F1);
Go to Xcode and hit your hotkey (F1 in this case);
The chat window shows up;
The focus is still on Xcode's editor (not good), while the expected result is for the widget's text editor to receive the focus so that I can continue my chat.

The way it is now, the hotkey is completely useless since I have to also use the mouse to click on the chat's text box.
Relevant log output
NA

macOS version
14.1.1 (23B2082)
Xcode version
15.0.1
Copilot for Xcode version
Version 0.27.0 (280)
Node version

I think the same goes for Prompt to Code. I wonder if #396 fixes both issues?

Yes it does

Released in 0.27.1


⚠ Bofrost.at has degraded performance

In 266f50f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1428 ms

Resolved: Bofrost.at performance has improved in 8ea6379.


Embed Obsidian Note as Frame?

I have a heatmap calendar plugin that I use and I want to embed the file as a frame. At the moment I am just placing the note in my sidebar but it's not as clean as I would like. Is this possible? I've tried point the URL to the file but it's not rendering anything
Desired Functionality

Never mind. I figured it out with custom css. I added the property "cssclass" = .heatmap  to the YAML of my heatmap file. Then I used the following CSS snippet to clean it up a little (centring, removal of title & turn off scrolling)
/* targets the .heatmap css class, centres the content and turns off scrolling */
.heatmap {
    display: stretch;
    height: 100%;
    width: 100%;
    overflow-y: hidden;
    padding-top: 0px;
    margin-top: -20px;
}

/* removes the title. May not be necessary  */
.heatmap .view-header-title{
    display: none
  }

/* removes the title. 100% necessary */
.heatmap .inline-title{
    display: none;
  }

Still it would be nice to have this as a pane/frame with an icon instead of a note

Hi, this sort of feature is out of scope of the plugin in my opinion, sorry!


AngleSharp.Scripting, AngleSharp.Io. No support for dotNet Framework 4?

I tried to install "AngleSharp.Scripting" & "AngleSharp.Io" using Nuget. Both packages failed to install and get referenced.
"AngleSharp" has support for target framework net40 but not "AngleSharp.Scripting" & "AngleSharp.Io" ?

Yes, this is true. This may change once I find the time to continue development on the AngleSharp plugins, which would involve .NET core and finer grained dependencies. I think .NET 4 should be possible with a reference to the Bcl.Async. You may compile from source and reference it manually.
I keep the issue open to remind me on the enhancement.

Thanks a lot for the quick reply. I'm very much interested in the scripting functionality where we can inject JS, query variables, invoke functions, pass objects, run script/eval (like from a browser console) and get returns.
I will try compiling from the source. Thank you for the help.

I should have some time to continue working on this soon. In the meantime any help is appreciated.

Hello. I was unable to install this package from nuget, because it does not support .NET Core, looks like it's kind of similar issue. I compiled it from sources with VS2017 targeting netstandard1.6. I had to reference System.Net.NetworkInformation.dll and edit /src/AngleSharp.Scripting.JavaScript/SystemTypeConverter.cs a bit. If you want, i can share my diff via pull request so you will have less issues if you want to target .NET Core in future.

Sure, go ahead!

Nevermind, it crashes in runtime :( After some time trying to figure out how to overcome it, i switched to full .NET Framework. Also, the need to reference System.Net.NetworkInformation.dll just to compile it ruins the whole idea of using .NET Core.

Yup. In general it should run, but besides the one you mentioned the external dependency to Jint is the most crucial part. Here only the latest version is ready for .NET Standard / .NET Core. I am uncertain about the required changes in AS Scripting to make it work yet.

This is obsolete now. With AngleSharp now being .NET Standard 2.0 (or 1.3 incoming) there is no chance of having this in .NET 4.
Also Jint 3 (which will be used for AngleSharp.Js) is at least on .NET Standard 2.0.


MagusManga: Update image URL

Fixes pages not loading/opening in WebView to old cdn link

Checklist:

[ ] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[ ] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

Superceded by #4963 :pepesad:

Un-superceded by #4963


[bug] Aeotec Multisensor 6 now shows up Unknown/undefined Manufacturer/Product

Version
1.0.0-beta.0.6e2a0f7
Build/Run method

[ ] Docker
[ ] PKG
[x] Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: 1.0.0-beta.0.6e2a0f7
Describe the bug
Aeotec Multisensor6 is showing up in GUI Unknown manufacturer undefined and Unknown product undefined
There are no numbers saying what manufacturer/product was actually found.
Important Note: This was working in release 1.0.0-alpha.2.51f715c (~2 days ago)
Everything else appears correct as is in the GUI including the configuration parameters.
I checked the zwave-js device files (ZW100), and they appear to be there and correct.
My device's info: Mfg=0x0086 (134), Type=x0102(258), ID=x0064(100).

Could you show me a log output of zwavejs2mqtt? I'm currently working on a fix for this #240

Could you show me a log output of zwavejs2mqtt? I'm currently working on a fix for this #240

OK...

I started it up (with cached files) with the logs enabled and this time it worked (it found the correct manufacturing/Product)!
Repeated 1) again and it worked!
Cleared the cache files, restarted and the problem reoccurs :( .

Here is the zwavejs2mqtt log with 'silly' level (I snipped a few of the other nodes' log entries to shorten things up)
....
2021-01-15 12:15:41.082 INFO ZWAVE: Zwave driver is ready
2021-01-15 12:15:41.090 DEBUG MQTT: Publishing to z2mqtt/nodeID_1/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:41.083 INFO ZWAVE: Controller status: Driver ready
2021-01-15 12:15:41.092 INFO ZWAVE: Node added 1
2021-01-15 12:15:41.095 INFO ZWAVE: Node added 2
....
2021-01-15 12:15:41.113 INFO ZWAVE: Scanning network with homeid: blah blah
2021-01-15 12:15:41.094 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:41.097 DEBUG MQTT: Publishing to z2mqtt/nodeID_3/status: false with options { qos: 0, retain: false }
...
2021-01-15 12:15:41.557 INFO ZWAVE: Node 9 is awake
2021-01-15 12:15:41.560 DEBUG MQTT: Publishing to z2mqtt/nodeID_9/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:42.090 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:42.091 INFO ZWAVE: Node 2 is alive
2021-01-15 12:15:42.107 INFO ZWAVE: Node 2: metadata updated: 49-0-Humidity
2021-01-15 12:15:42.110 INFO ZWAVE: Node 2: value added: 49-0-Humidity => 40
2021-01-15 12:15:42.351 DEBUG MQTT: Publishing to z2mqtt/nodeID_3/status: false with options { qos: 0, retain: false }
...
2021-01-15 12:15:46.902 INFO ZWAVE: Node 2: metadata updated: 49-0-Ultraviolet
2021-01-15 12:15:46.904 INFO ZWAVE: Node 2: value added: 49-0-Ultraviolet => 0
2021-01-15 12:15:47.409 INFO ZWAVE: Node 3: value added: 134-0-libraryType => 3
....
2021-01-15 12:16:47.513 INFO ZWAVE: Node 9 is now asleep
2021-01-15 12:16:47.515 DEBUG MQTT: Publishing to z2mqtt/nodeID_9/status: false with options { qos: 0, retain: false }
2021-01-15 12:16:47.584 INFO ZWAVE: Node 2: value added: 128-0-level => 100
2021-01-15 12:16:47.585 INFO ZWAVE: Node 2: value added: 128-0-isLow => false
2021-01-15 12:16:47.891 INFO ZWAVE: Node 2: metadata updated: 49-0-Illuminance
2021-01-15 12:16:47.893 INFO ZWAVE: Node 2: value added: 49-0-Illuminance => 22
2021-01-15 12:16:48.020 INFO ZWAVE: Node 2: metadata updated: 49-0-Ultraviolet
2021-01-15 12:16:48.022 INFO ZWAVE: Node 2: value updated: 49-0-Ultraviolet 0 => 0
2021-01-15 12:16:55.868 INFO ZWAVE: Node 6: value updated: 50-0-value-66561 121.675 => 122.297
...
2021-01-15 12:17:08.339 DEBUG MQTT: Publishing to z2mqtt/nodeID_6/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:08.374 INFO ZWAVE: Node 2: value added: 132-0-wakeUpInterval => 3600
2021-01-15 12:17:08.379 INFO ZWAVE: Node 2: value added: 132-0-controllerNodeId => 1
2021-01-15 12:17:08.599 DEBUG MQTT: Publishing to z2mqtt/nodeID_11/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:08.600 INFO ZWAVE: Node 11 is alive
2021-01-15 12:17:18.810 DEBUG MQTT: Publishing to z2mqtt/nodeID_10/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:18.811 INFO ZWAVE: Node 10 is alive
2021-01-15 12:17:29.101 WARN ZWAVE: Node 2 doesn't support groups associations
2021-01-15 12:17:29.119 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: true with options { qos: 0, retain: false }
2021-01-15 12:17:29.109 INFO ZWAVE: Node 2: value added 2-49-0-Humidity => 40
2021-01-15 12:17:29.111 INFO ZWAVE: Node 2: value added 2-49-0-Ultraviolet => 0
2021-01-15 12:17:29.112 INFO ZWAVE: Node 2: value added 2-49-0-Illuminance => 22
2021-01-15 12:17:29.115 INFO ZWAVE: Node 2: value added 2-132-0-wakeUpInterval => 3600
2021-01-15 12:17:29.116 INFO ZWAVE: Node 2: value added 2-132-0-controllerNodeId => 1
2021-01-15 12:17:29.121 INFO ZWAVE: Node 2 ready: Unknown manufacturer undefined - Unknown product undefined (Unknown)
2021-01-15 12:17:29.124 INFO ZWAVE: Node 2: interview completed, all values are updated
2021-01-15 12:17:29.126 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: true with options { qos: 0, retain: false }
2021-01-15 12:17:29.242 INFO ZWAVE: Node 11: value added: 114-0-manufacturerId => 881
...
2021-01-15 12:17:39.538 DEBUG MQTT: Publishing to z2mqtt/nodeID_6/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:39.590 INFO ZWAVE: Node 2: metadata updated: 49-0-Air temperature
2021-01-15 12:17:39.600 INFO ZWAVE: Node 2: value added: 49-0-Air temperature => 72.8
2021-01-15 12:17:40.964 INFO ZWAVE: Node 2: metadata updated: 49-0-Humidity
2021-01-15 12:17:40.967 INFO ZWAVE: Node 2: value added: 49-0-Humidity => 40
...
2021-01-15 12:17:43.363 INFO ZWAVE: Node 10: value added: 134-0-firmwareVersions => 1.1
2021-01-15 12:17:43.885 INFO ZWAVE: Node 2: value added: 128-0-level => 100
2021-01-15 12:17:43.886 INFO ZWAVE: Node 2: value added: 128-0-isLow => false
2021-01-15 12:17:55.866 INFO ZWAVE: Node 6: value updated: 50-0-value-66561 122.297 => 122.68
....
2021-01-15 12:19:39.992 INFO ZWAVE: Node 7: interview completed, all values are updated
2021-01-15 12:19:39.995 DEBUG MQTT: Publishing to z2mqtt/nodeID_7/status: true with options { qos: 0, retain: false }
2021-01-15 12:19:45.563 INFO ZWAVE: Node 2: metadata updated: 49-0-Illuminance
2021-01-15 12:19:45.564 INFO ZWAVE: Node 2: value added: 49-0-Illuminance => 24
2021-01-15 12:19:48.273 INFO ZWAVE: Node 2: metadata updated: 49-0-Ultraviolet
2021-01-15 12:19:48.276 INFO ZWAVE: Node 2: value added: 49-0-Ultraviolet => 0
2021-01-15 12:19:55.866 INFO ZWAVE: Node 6: value updated: 50-0-value-66561 122.766 => 122.752
...
2021-01-15 12:20:32.145 INFO APP: Closing clients...
2021-01-15 12:20:32.146 INFO GATEWAY: Closing Gateway...
2021-01-15 12:20:32.154 INFO MQTT: MQTT client closed

OK...

I started it up (with cached files) with the logs enabled and this time it worked (it found the correct manufacturing/Product)!
Repeated 1) again and it worked!
Cleared the cache files, restarted and the problem reoccurs :( .

Here is the zwavejs2mqtt log with 'silly' level (I snipped a few of the other nodes' log entries to shorten things up)
....
2021-01-15 12:15:41.082 INFO ZWAVE: Zwave driver is ready
2021-01-15 12:15:41.090 DEBUG MQTT: Publishing to z2mqtt/nodeID_1/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:41.083 INFO ZWAVE: Controller status: Driver ready
2021-01-15 12:15:41.092 INFO ZWAVE: Node added 1
2021-01-15 12:15:41.095 INFO ZWAVE: Node added 2
....
2021-01-15 12:15:41.113 INFO ZWAVE: Scanning network with homeid: blah blah
2021-01-15 12:15:41.094 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:41.097 DEBUG MQTT: Publishing to z2mqtt/nodeID_3/status: false with options { qos: 0, retain: false }
...
2021-01-15 12:15:41.557 INFO ZWAVE: Node 9 is awake
2021-01-15 12:15:41.560 DEBUG MQTT: Publishing to z2mqtt/nodeID_9/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:42.090 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: false with options { qos: 0, retain: false }
2021-01-15 12:15:42.091 INFO ZWAVE: Node 2 is alive
2021-01-15 12:15:42.107 INFO ZWAVE: Node 2: metadata updated: 49-0-Humidity
2021-01-15 12:15:42.110 INFO ZWAVE: Node 2: value added: 49-0-Humidity => 40
2021-01-15 12:15:42.351 DEBUG MQTT: Publishing to z2mqtt/nodeID_3/status: false with options { qos: 0, retain: false }
...
2021-01-15 12:15:46.902 INFO ZWAVE: Node 2: metadata updated: 49-0-Ultraviolet
2021-01-15 12:15:46.904 INFO ZWAVE: Node 2: value added: 49-0-Ultraviolet => 0
2021-01-15 12:15:47.409 INFO ZWAVE: Node 3: value added: 134-0-libraryType => 3
....
2021-01-15 12:16:47.513 INFO ZWAVE: Node 9 is now asleep
2021-01-15 12:16:47.515 DEBUG MQTT: Publishing to z2mqtt/nodeID_9/status: false with options { qos: 0, retain: false }
2021-01-15 12:16:47.584 INFO ZWAVE: Node 2: value added: 128-0-level => 100
2021-01-15 12:16:47.585 INFO ZWAVE: Node 2: value added: 128-0-isLow => false
2021-01-15 12:16:47.891 INFO ZWAVE: Node 2: metadata updated: 49-0-Illuminance
2021-01-15 12:16:47.893 INFO ZWAVE: Node 2: value added: 49-0-Illuminance => 22
2021-01-15 12:16:48.020 INFO ZWAVE: Node 2: metadata updated: 49-0-Ultraviolet
2021-01-15 12:16:48.022 INFO ZWAVE: Node 2: value updated: 49-0-Ultraviolet 0 => 0
2021-01-15 12:16:55.868 INFO ZWAVE: Node 6: value updated: 50-0-value-66561 121.675 => 122.297
...
2021-01-15 12:17:08.339 DEBUG MQTT: Publishing to z2mqtt/nodeID_6/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:08.374 INFO ZWAVE: Node 2: value added: 132-0-wakeUpInterval => 3600
2021-01-15 12:17:08.379 INFO ZWAVE: Node 2: value added: 132-0-controllerNodeId => 1
2021-01-15 12:17:08.599 DEBUG MQTT: Publishing to z2mqtt/nodeID_11/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:08.600 INFO ZWAVE: Node 11 is alive
2021-01-15 12:17:18.810 DEBUG MQTT: Publishing to z2mqtt/nodeID_10/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:18.811 INFO ZWAVE: Node 10 is alive
2021-01-15 12:17:29.101 WARN ZWAVE: Node 2 doesn't support groups associations
2021-01-15 12:17:29.119 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: true with options { qos: 0, retain: false }
2021-01-15 12:17:29.109 INFO ZWAVE: Node 2: value added 2-49-0-Humidity => 40
2021-01-15 12:17:29.111 INFO ZWAVE: Node 2: value added 2-49-0-Ultraviolet => 0
2021-01-15 12:17:29.112 INFO ZWAVE: Node 2: value added 2-49-0-Illuminance => 22
2021-01-15 12:17:29.115 INFO ZWAVE: Node 2: value added 2-132-0-wakeUpInterval => 3600
2021-01-15 12:17:29.116 INFO ZWAVE: Node 2: value added 2-132-0-controllerNodeId => 1
2021-01-15 12:17:29.121 INFO ZWAVE: Node 2 ready: Unknown manufacturer undefined - Unknown product undefined (Unknown)
2021-01-15 12:17:29.124 INFO ZWAVE: Node 2: interview completed, all values are updated
2021-01-15 12:17:29.126 DEBUG MQTT: Publishing to z2mqtt/nodeID_2/status: true with options { qos: 0, retain: false }
2021-01-15 12:17:29.242 INFO ZWAVE: Node 11: value added: 114-0-manufacturerId => 881
...
2021-01-15 12:17:39.538 DEBUG MQTT: Publishing to z2mqtt/nodeID_6/status: false with options { qos: 0, retain: false }
2021-01-15 12:17:39.590 INFO ZWAVE: Node 2: metadata updated: 49-0-Air temperature
2021-01-15 12:17:39.600 INFO ZWAVE: Node 2: value added: 49-0-Air temperature => 72.8
2021-01-15 12:17:40.964 INFO ZWAVE: Node 2: metadata updated: 49-0-Humidity
2021-01-15 12:17:40.967 INFO ZWAVE: Node 2: value added: 49-0-Humidity => 40
...
2021-01-15 12:17:43.363 INFO ZWAVE: Node 10: value added: 134-0-firmwareVersions => 1.1
2021-01-15 12:17:43.885 INFO ZWAVE: Node 2: value added: 128-0-level => 100
2021-01-15 12:17:43.886 INFO ZWAVE: Node 2: value added: 128-0-isLow => false
2021-01-15 12:17:55.866 INFO ZWAVE: Node 6: value updated: 50-0-value-66561 122.297 => 122.68
....
2021-01-15 12:19:39.992 INFO ZWAVE: Node 7: interview completed, all values are updated
2021-01-15 12:19:39.995 DEBUG MQTT: Publishing to z2mqtt/nodeID_7/status: true with options { qos: 0, retain: false }
2021-01-15 12:19:45.563 INFO ZWAVE: Node 2: metadata updated: 49-0-Illuminance
2021-01-15 12:19:45.564 INFO ZWAVE: Node 2: value added: 49-0-Illuminance => 24
2021-01-15 12:19:48.273 INFO ZWAVE: Node 2: metadata updated: 49-0-Ultraviolet
2021-01-15 12:19:48.276 INFO ZWAVE: Node 2: value added: 49-0-Ultraviolet => 0
2021-01-15 12:19:55.866 INFO ZWAVE: Node 6: value updated: 50-0-value-66561 122.766 => 122.752
...
2021-01-15 12:20:32.145 INFO APP: Closing clients...
2021-01-15 12:20:32.146 INFO GATEWAY: Closing Gateway...
2021-01-15 12:20:32.154 INFO MQTT: MQTT client closed

@tommyjlong Does this comes from a ontainer built with #240 changes or not?
Does this only happen when the caceh file is not present or after a restart?

@tommyjlong Does this comes from a ontainer built with #240 changes or not?
Does this only happen when the caceh file is not present or after a restart?

@robertsLando .  I cloned from main last Wednesday, and changes from 240 are not present, so no I did not test with your fix.  Problem only occurs when starting with cache files not present.

@robertsLando .  I cloned from main last Wednesday, and changes from 240 are not present, so no I did not test with your fix.  Problem only occurs when starting with cache files not present.

I think we figured out the problem with #240 , seems that if the interview fails the ready event could be emitted anyway without the devive config informations. This will be fixed in next release

I think we figured out the problem with #240 , seems that if the interview fails the ready event could be emitted anyway without the devive config informations. This will be fixed in next release

Just tested with 1.0.0-rc.1.5846763.  This works now. I will go ahead and close.

Just tested with 1.0.0-rc.1.5846763.  This works now. I will go ahead and close.


DateTime

after i launch the nadekolauncher, there's always a "dotnet has stopped woking" box.
this is the error i get
system.formatexception string was not recognized as a valid datetime

#1094 This will be fixed soon-ish


Add default transform(sigmoid) for UnitContinuousDistribution

Fixes #214

Added _init_transform method for UnitContinuousDistribution
Added Sigmoid bijector in transforms.py

Fantastic @Sayam753! Thanks a lot for the quick fix! I'll merge this as it is, but the code coverage failure means that we are not testing pm.sample on a model that has a UnitContinuousDistribution (for example, a Uniform). In a later PR we can add a test in test_sampling.py that does that.


nmstate.gpg: Use new URL for GPG public key

The GPG public keys of maintainers are stored at
https://www.nmstate.io/nmstate.gpg
Updated README files to use this new URL.

This is a text only change, no need to rebase for testing.


Fixing update notification locale issue, update notification was shown in English for all locales

Removing pre-release specific code from release code, as it is causing update notification to be shown in English for all locales.
This will fix https://github.com/adobe/brackets/issues/14994

@niteskum

👍 LGTM


@typescript-eslint/block-spacing and @typescript-eslint/key-spacing are not turned off

Hi,
I noticed in the index.js file that you have turned off two rules: block-spacing and vue/block-spacing, but you didn't turn off @typescript-eslint/block-spacing. Similarly, key-spacing and vue/key-spacing have been turned off, but @typescript-eslint/key-spacing has not. Is there a reason for this ?

Hi!
Those two @typescript-eslint rules are quite new and nobody has added here yet. Would you like to make a PR?

Hi, I created a PR #243 for this issue.

Released in v8.7.0.

@ttionya
Thank you for creating the pull request. I forgot that I had also created this issue 😅.


Add another non-spec metadata - "name" to change factory name

Proposal details: https://github.com/stampit-org/stamp-specification/issues/121
TL;DR:
const HaveName = stampit({
  name: "Superman"
});

HaveName.name === "Superman"  // instead of the default "Stamp"

ping @FredyC

I don't know man, I never had this need for naming stamps really. It kinda feels that resulting name depends on the last named stamp composed in there. How can that be a good thing?

Well, properties, initializer, methods, etc behave the same way.

resulting [SOMETHING] depends on the last [HAS SOMETHING] stamp composed in there

Totally within the philosophy of stamps IMO.

Here is a blog post draft: https://medium.com/@koresar/fun-with-stamps-episode-23-new-name-feature-4be91c27edcb

Ok sure, since this far from a breaking change, then go ahead :)
Btw, I am still unsure why you are actually maintaining this package when there is the @stamp/it one which you even introduced in your blog as new way to do things. You should probably do the same change there if you want them to be the same although I don't see the point really. I thought that eventually, the stampit will just a be a redirect to @stamp/it to have a sane codebase. Your call.


Repository wnameless/oracle-xe-11g not found

Hi there,
I am getting this error since morning any idea why?
: repository wnameless/oracle-xe-11g not found: does not exist or no pull access
Also this link https://hub.docker.com/r/wnameless/oracle-xe-11g/ is giving 404

we are getting the same error, it's breaking some of our things

Any reason why its shutdown? If there are no plans for bringing it up, please let us know so that we will plan for alternates

At the moment we could only build the image on our own.
$ git clone https://github.com/wnameless/docker-oracle-xe-11g.git
$ cd docker-oracle-xe-11g
$ docker build -t wnameless/docker-oracle-xe-11g .

If anyone is interested I have pushed the image to our docker hub account thebookpeople/oracle-xe-11g

@wgriffiths can you please post a link to docker hub?

https://hub.docker.com/r/thebookpeople/oracle-xe-11g/

We are using this image across multiple CI pipelines/projects.
I'd rather not make the change to another image, unless we know for sure that this will not be re-uploaded. Can we please have a clarification if this deletion was intentional?

I have no idea that why my repository has been deleted. I am trying to bring it back ASAP.

The repository is back. I still need to figure out why my repository on docker hub has been deleted for no reason. I guess there is a problem between Github and Docker hub during the automated build process. I am now not able to build image from Github directly, instead I have to push my images from local machine.
If anyone knows what happened behind those issues, please let me know.

Interesting! The automated build is working now. What happened to Docker hub?
I think the only casualty I've got is that I lost all my stars on docker hub. So bad!


GELF processing failed - "invliad type: string expected f64" when sending log event from Tomcat 8.5

Hi,
We are getting the following error when sending Tomcat log event to Seq via GELF Input app in Seq:

Here is the log event output by Tomcat:

Settings in logging.properties:

Settings in GELF input:

Seq version: 5.1.3200
GELF Input version: 2.0.258-dev
logstash-gelf version: 1.13.0

Hi @macaustreet1 :wave:
Thanks for reaching out! I think the problem here is that the timestamp in the message is being sent as a string as per GELF 1.0, rather than as a number as per GELF 1.1. The Seq Input only supports the GELF 1.1 format. Do you know if your Logstash GELF plugin is configured for a particular version of the format?

Thanks for the quick response KodrAus!
Yes you re right. The issue is from the GelfLogHandler version.
The issue is gone after i added the following lines into the config:
biz.paluch.logging.gelf.jul.GelfLogHandler.version=1.1 biz.paluch.logging.gelf.jul.GelfLogHandler.timestampPattern=yyyy-MM-dd HH:mm:ss,SSS