Add Phoenix + Ecto example

This PR add example for setting up OpenTelemetry in Phoenix application.
Since a lot of files is generated, I would suggest reviewing it by looking at each commits instead. It is committed in a way where each related changes is grouped together for easier code review.
Currently the example application contains two examples:

Phoenix HTML resources, which work perfectly fine with OpenTelemetry Phoenix
Phoenix LiveView resources, which only show traces of Ecto when navigating around.

We also included different configuration of exporter to export to different services. By default, the example is exporting to the OpenTelemetry collector (spinned up with docker compose).
Also, added some explanation on README to educate people on exporting to 3rd party services.
Additional thought I have is to also add screenshot or screencast for it, but for the time being, let's have this first and add those later down the road.

cc: @tsloughter @bryannaegele It's ready for review

I think we should merge this.
@bryannaegele @GregMefford any objection?
After that I'll open a PR to add the release configuration I'd like to see it have and we can discuss there if there is any objection to doing so -- I understand it could be seen as adding confusion rather than clarity.


Device Instance rename

Also makes import alias of device config package consistent throughout codebase as deviceConfig.

@tomponline  Looks good, please rebase

@stgraber rebased


fix package name typo

Codecov Report

Merging #44 (9783e13) into main (bf5203b) will increase coverage by 28.85%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main      #44       +/-   ##
=============================================
+ Coverage     10.05%   38.91%   +28.85%
  Complexity      123      123
=============================================
  Files           132       54       -78
  Lines          2565      663     -1902
  Branches        375       27      -348
=============================================
  Hits            258      258
+ Misses         2299      397     -1902
  Partials          8        8

Flag
Coverage Δ

unittests
38.91% <ø> (+28.85%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/main/kotlin/Main.kt

src/main/kotlin/constant/PixelConst.kt

src/main/kotlin/widget/config/ConfigBase.kt

src/main/kotlin/widget/config/ConfigRedis.kt

src/main/kotlin/widget/Drawer.kt

src/main/kotlin/module/TroubleZooKeeperEnum.kt

src/main/kotlin/module/TroubleKubernetesEnum.kt

src/main/kotlin/module/ConfigEnum.kt

src/main/kotlin/widget/config/ConfigCassandra.kt

src/main/kotlin/widget/minio/MinioInstance.kt

... and 68 more

Continue to review full report at Codecov.

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


Condition Mapping Logic Buildout

Buildout updates pushed to github here: https://github.com/CDCgov/prime-reportstream/pull/11122/files


Update tmdb extension

Description

Feature request #9502 : Add the ability to directly copy the TMDB ID to your clipboard

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Looks good to me, but do we really need to display the ID we are copying? Could the action simply be "Copy TMDB ID"? Just thinking if it's useful to show the ID here or better to keep it simple 🤔

LGTM
imo, It’s fine to display the user ID since the length of the string is small.

@andreaselia I was thinking of that, but the ID isn't shown anywhere, hence why I would add it in the Action menu. That way the user knows what it copied. It's only a few numbers, so it wouldn't mess up the Action panel.
If the ID was displayed in the Details, I would remove it from being displayed in the Action title I guess, does that make sense?
Let me know if I should remove it from the title :)

I agree, it doesn't provide additional value to the user seeing it rather than just copying it.
If we did want to display the ID somewhere, perhaps we could add it below "votes" here?


Implement Spec v2 Messages

Implement new messages from Spec v2, and see how hooking them up to devices/client API works out. This isn't a final implementation, but rather a way to figure out whether the messages translate well at the API level. Spec/schema refinement may happen during this work.

[ ] RawWriteCmd
[ ] RawReadCmd
[ ] RawSubscribeCmd
[ ] RawUnsubscribeCmd
[ ] RawReading
[ ] RSSILevelCmd
[ ] RSSILevelReading
[ ] BatteryLevelCmd
[ ] BatteryLevelReading

See also:

buttplugio/buttplug-rs#60
buttplugio/buttplug-csharp#653

buttplug-js will soon be part of buttplug-wasm in https://github.com/buttplugio/buttplug-rs-ffi, closing this bug as it relates to implementation that will be taken care of in buttplug-rs.


v2.0.0

2.0.0 (2024-02-05)
What's Changed

Rewrite into Typescript and Convert CommonJS to ES Module
Fix Linting, Thanks @dnicolson #216
Code Cleaup, Thanks @dnicolson #217
Housekeeping and update dependencies

Full Changelog: https://github.com/OpenWonderLabs/node-switchbot/compare/v1.10.0...v2.0.0

@dnicolson, do you have any thoughts on this?

Nothing comes to mind.
When including it in homebridge-switchbot I wouldn't release it as part of a patch release. I see you ultimately reverted part of the changes, the node-switchbot import is broken though, unfortunately.

Dang, well hopefully we can get this resolved. I will open another beta with a minor change version. To release node-SwitchBot with that.

@donavanbecker, I'm not sure how you want to solve this, but the problem with this release is an async issue in the constructor. The scanning code gets called before noble has been imported.
You can easily test before making a release, just by running something like test.mjs in the project directory after building:
import { SwitchBot } from './dist/index.js';

const switchbot = new SwitchBot();

(async () => {
  await switchbot.startScan({ id: 'XX:XX:XX:XX:XX:XX' });
  switchbot.onadvertisement = (ad) => {
    console.log(JSON.stringify(ad, null, '  '));
  };
})();

import { SwitchBot } from './dist/index.js';

const switchbot = new SwitchBot();

(async () => {
  await switchbot.startScan({ id: 'XX:XX:XX:XX:XX:XX' });
  switchbot.onadvertisement = (ad) => {
    console.log(JSON.stringify(ad, null, '  '));
  };
})();

would you want to add something like this to the repo that can be ran each time before publishing?

Maybe, the effectiveness would need to be evaluated though.


Add PR Title to metadata

Currently the metadata includes the top commit message. However, when numerous commits are merged in the same PR, the title is a much more useful piece of metadata. I would like to use ticket IDs from a PR title that could the be passed as metadata to other resources such as a jira-resourse that could then transition a ticket. I have submitted #172 to handle this.

Closed after merging #172 - please check out the dev image while I put together a release. Also, sorry for the long wait on this (and many other) issue.


build command results in 404 from server

I'm new to OmniSharp, so I don't know much yet about how to do a lot of troubleshooting.  After having failed to get a released version to work with DNX/project.json, I got the sources for the latest master (after the merge of the roslyn stuff) and tried that.  It kinda-sorta works, and I don't have all the red squigglies like before, but building doesn't work.  The following is produced in the OmniSharp output pane:

What did I do wrong?
Output of apm list:
C:\Users\Administrator\.atom\packages (7)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
see https://github.com/OmniSharp/omnisharp-atom/issues/100

Linking #451 to this issue.

The build command is not part of the server anymore.


Add aliyun log service support

https://github.com/AliyunContainerService/fluentd-pilot/commit/230d2c94241a5ac154811cbd99873d4bf2bef6d3


Notifications: Split templates per type

This change should give more freedom in the customisation of notification engines (and implementation of a new one). Some notifications could be more customised only for some specific engine (in other engines, default template (other.tpl) will be used).

@kiblik I think this part of defect dojo is require a localization support. Please add it

I agree with adding localization. I can add it. But it was missing until now. Can we merge this PR and I will add localization in the next iteration?

Of course! But you PR was planned for 2.19 version. You have a 1 month for adding new commits :)

@shipko, localization is ready. I would like to run ./manage.py makemessages ... but I'm waiting for https://github.com/DefectDojo/django-DefectDojo/pull/7352

@kiblik nice job! 👍👍👍

I suppose, we are ready for merge.


refactor: rewrite createRule and RuleTester

Currently, eslint-plugin-import-x patches @typescript-eslint/utils to add custom properties like the category and modify properties like the recommended.
The PR accomplishes the same thing, by doing some TypeScript exercises instead.

@JounQin @silverwind What do you think? Do you prefer creating our own utilities over patching ts-eslint?

@JounQin Would you like to cleat the cache of the GitHub Action? It seems that the CI failed to the corrupt cache.

@SukkaW
I raised https://github.com/typescript-eslint/typescript-eslint/issues/8897 to discuss about the optional parser property.
And I notice patches are also used in tseslint's repository https://github.com/typescript-eslint/typescript-eslint/blob/main/.yarn/patches, and considering there are some // @ts-expect-error - flow type comments in source codes, I'm also considering to add more patches for typings maybe, and the maintenance for such small patches should be easier than TypeScript exercises.
HDYT?

HDYT?

@JounQin Actually, I kinda hate the typescript-eslint project. Their maintainers have little knowledge of TypeScript, yet they ignore most of the communities' suggestions.
In fact, in my own eslint-plugin-sukka, I am writing my own createRule and RuleTester, without depending on either eslint or typescript-eslint.

I am closing the PR now since TypeScript ESLint 8 has addressed the custom property of createRule through generic parameters. The issue has already been resolved by me in another PR https://github.com/un-ts/eslint-plugin-import-x/pull/112.


[BUG 🐞] Navbar not working

Description
If we click to check carts, from there we cannot go to other components using Navbar options.
Steps to reproduce:
->Go to carts.
->Click on any navbar option.
Additional information
Make sure to read the CONTRIBUTING and SETUP docs before proceeding
Happy contributing. 💐
Star my other Repositories here

I will work on this issue.
Assign bro.

Screenshot not visible

PNG Not uploading I don't why.
but i have updated the description.
Also steps mention to reproduce.


Intersection Point in Y Shaped Linked Lists - POTD | 13-Nov-2024

Intersection Point in Y Shaped Linked Lists
Link
Difficulty: Medium
Given two singly linked lists, return the point where two linked lists intersect.
Note: If the linked lists do not merge at any point, return -1.
Examples:
Input: Linked list 1: 4->4->4->4->4, Linked list 2: 4->4->4

Output: 4
Explanation: From the above image, it is clearly seen that the common part is 4->4 whose starting point is 4.

Input: Linked list 1: 4->1->8->4->5, Linked List 2: 5->6->1->8->4->5

Output: 8
Explanation: From the above image, it is clearly seen that the common part is 8->4->5 whose starting point is 8.
Input: Linked list 1: 1->2->3, Linked list 2: 4->5->6
Output: -1
Explanation: There is no common part, so there is no interaction point.
Try to solve the problem without using any extra space.

Constraints:

2 ≤ size of first linkedist + size of second linkedlist ≤ 2*105
-1000 ≤ data of nodes ≤ 1000

Solved
class Intersect {
    // Function to find intersection point in Y shaped Linked Lists.
    int intersectPoint(Node head1, Node head2) {
        HashMap<Node,Integer> map = new HashMap<>();
        while(head1!=null){
            map.put(head1,head1.data);
            head1 = head1.next;
        }

        while(head2!=null){
            if(map.containsKey(head2)){
                return head2.data;
            }
            head2 = head2.next;
        }
        return -1;

    }
}


Lint some files and update languages/fr-FR.js

Description
Fixes #(issue)
(title of my pull request)
Type of change

Translation update
Other

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[] I have performed a self-review of my own code and tested it
[ ] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[x] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

I go to patch that sorry I don't understand why there is this problem

I had run npm run update-language-files I think this script add this lines

Yep, that the one

okay i understand now anyway i'm patching this

I think it's good now

I'm french too
And if you translate "monitor" in French "sonde" it's not the great word so for me "moniteur" and if you use a online dictionary or a translate tool you can see there is a great word

There are too many changes, I am afraid that I don't have time to check it.
I suggest this pr should just update fr-FR.js only and leave other files unchanged.

If you want, it's ur project ^^

There are too many changes, I am afraid that I don't have time to check it. I suggest this pr should just update fr-FR.js only and leave other files unchanged.

Close as this reason.


(JSON serialization) How to prepare for cirq_type deprecation?

Description of the issue
I use Cirq circuits and operations to represent my noisy simulations. I use to_json and read_json when serializing related data classes. I recently saw this deprecation warning:
Found 'cirq_type': 'MyCustomSerializedClass' in _json_dict_. Custom values of this field are not permitted, and will produce an error starting in Cirq v0.15.
Since my work is dependent on another code-base (which is tied to the current dev Cirq version), I expect that the implementations I reference above will soon stop working. Can I please have some guidance as to how serialization will be handled in the future? Is there some documentation I can reference? What should I do for json serialization when cirq_type is no longer supported?
Thank you!
Related issue: #3098
Cirq version
0.15.0.dev20220402003018

@mpharrigan @95-martin-orion who I think have the most context

Yup, this was me. The 'cirq_type' element of _json_dict_ is now auto-populated with the class name and (optional) namespace of the object in question. Ideally, classes which explicitly specify 'cirq_type' should just be able to remove it and everything should work out nicely, e.g.:
class MyCustomSerializedClass:
    # ...
    def _json_dict_(self):
        return {
            'cirq_type': 'MyCustomSerializedClass',  # remove this line
            # ...
        }

If your 'cirq_type' is not the name of the class, or you're specifying the _json_dict_ differently (e.g. with obj_to_dict_helper), it gets more complicated - please provide details here if that's the case.

I think your suggestion should work fine (I have been using self.__cls__.__name__ for all of my cirq types anyway). Thank you!

glad this worked out. Should we update the deprecation method?

I think we usually do a sweep and update all deprecated methods in one go, but yeah, we're now in v0.15(+dev) and explicit cirq_types should now produce an error.

Should we update the error message to clarify what a 3rd party dev should do instead?

Sounds good to me - something like "Do not explicitly specify 'cirq_type', it will be auto-generated based on the class name and (optional) namespace"?

yes :)


TypeError from trying to cache higher order functions

[x] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

If you try and cache a higher order numba'd function, you get a TypeError. I'm not sure if caching isn't meant to support higher order functions and this wasn't documented, or if this was a bug.
Minimal example:
import numba

@numba.njit()
def foo(x, y):
    return x + y

@numba.njit(cache=True)
def bar(func, x, y):
    l = list()
    for i in range(len(x)):
        l.append(func(x[i], y[i]))
    return l

bar(foo, [1,2,3], [4,5,6])

 Traceback
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
/usr/local/lib/python3.7/site-packages/numba/caching.py in save(self, key, data)
    481             # If key already exists, we will overwrite the file
--> 482             data_name = overloads[key]
    483         except KeyError:

KeyError: ((type(CPUDispatcher(<function foo at 0x120ae3400>)), reflected list(int64), reflected list(int64)), ('x86_64-apple-darwin18.7.0', 'haswell', '+64bit,-adx,+aes,+avx,+avx2,-avx512bitalg,-avx512bw,-avx512cd,-avx512dq,-avx512er,-avx512f,-avx512ifma,-avx512pf,-avx512vbmi,-avx512vbmi2,-avx512vl,-avx512vnni,-avx512vpopcntdq,+bmi,+bmi2,-cldemote,-clflushopt,-clwb,-clzero,+cmov,+cx16,+f16c,+fma,-fma4,+fsgsbase,-gfni,+invpcid,-lwp,+lzcnt,+mmx,+movbe,-movdir64b,-movdiri,-mwaitx,+pclmul,-pconfig,-pku,+popcnt,-prefetchwt1,-prfchw,-ptwrite,-rdpid,+rdrnd,-rdseed,-rtm,+sahf,-sgx,-sha,-shstk,+sse,+sse2,+sse3,+sse4.1,+sse4.2,-sse4a,+ssse3,-tbm,-vaes,-vpclmulqdq,-waitpkg,-wbnoinvd,-xop,+xsave,-xsavec,+xsaveopt,-xsaves'))

During handling of the above exception, another exception occurred:

TypeError                                 Traceback (most recent call last)
<ipython-input-4-8c5200b58787> in <module>
     12     return l
     13
---> 14 bar(foo, [1,2,3], [4,5,6])

/usr/local/lib/python3.7/site-packages/numba/dispatcher.py in _compile_for_args(self, *args, **kws)
    393                     e.patch_message(''.join(e.args) + help_msg)
    394             # ignore the FULL_TRACEBACKS config, this needs reporting!
--> 395             raise e
    396
    397     def inspect_llvm(self, signature=None):

/usr/local/lib/python3.7/site-packages/numba/dispatcher.py in _compile_for_args(self, *args, **kws)
    350                 argtypes.append(self.typeof_pyval(a))
    351         try:
--> 352             return self.compile(tuple(argtypes))
    353         except errors.TypingError as e:
    354             # Intercept typing error that may be due to an argument

/usr/local/lib/python3.7/site-packages/numba/compiler_lock.py in _acquire_compile_lock(*args, **kwargs)
     30         def _acquire_compile_lock(*args, **kwargs):
     31             with self:
---> 32                 return func(*args, **kwargs)
     33         return _acquire_compile_lock
     34

/usr/local/lib/python3.7/site-packages/numba/dispatcher.py in compile(self, sig)
    693             cres = self._compiler.compile(args, return_type)
    694             self.add_overload(cres)
--> 695             self._cache.save_overload(sig, cres)
    696             return cres.entry_point
    697

/usr/local/lib/python3.7/site-packages/numba/caching.py in save_overload(self, sig, data)
    663         """
    664         with self._guard_against_spurious_io_errors():
--> 665             self._save_overload(sig, data)
    666
    667     def _save_overload(self, sig, data):

/usr/local/lib/python3.7/site-packages/numba/caching.py in _save_overload(self, sig, data)
    673         key = self._index_key(sig, _get_codegen(data))
    674         data = self._impl.reduce(data)
--> 675         self._cache_file.save(key, data)
    676
    677     @contextlib.contextmanager

/usr/local/lib/python3.7/site-packages/numba/caching.py in save(self, key, data)
    489                     break
    490             overloads[key] = data_name
--> 491             self._save_index(overloads)
    492         self._save_data(data_name, data)
    493

/usr/local/lib/python3.7/site-packages/numba/caching.py in _save_index(self, overloads)
    535     def _save_index(self, overloads):
    536         data = self._source_stamp, overloads
--> 537         data = self._dump(data)
    538         with self._open_for_write(self._index_path) as f:
    539             pickle.dump(self._version, f, protocol=-1)

/usr/local/lib/python3.7/site-packages/numba/caching.py in _dump(self, obj)
    563
    564     def _dump(self, obj):
--> 565         return pickle.dumps(obj, protocol=-1)
    566
    567     @contextlib.contextmanager

TypeError: can't pickle weakref objects

@ivirshup thanks for raising this issue, reproduction was possible for me. Also, I can confirm that it does work fine without cache=True.

It's the same request as in https://github.com/numba/numba/pull/4467#issuecomment-529487799

It's the same request as in #4467 (comment)

@sklam, does it mean that this will work in 0.46 or that is the same request that will/might be addressed separately in the future?

@luk-f-a, no, it's just a note that the comment in the PR is making the same request as this issue.

As of mainline for 0.55, this does not reproduce. Closing, assumed fixed.


Change variable name hints

This patch has no functional impact.
Variable naming style is updated to hopefully prevent two points of confusion:

Variables named ..._facets have been changed to ..._facet.  There is no reason for a single uco-core:Facet node to be referred to with the plural of "facet".  A single uco-core:UcoObject graph node does have multiple Facets, but each Facet should be referenced in the singular.
The ObservableObject node's variable also had the suffix _facet. This hints at an incorrect ontological classification - ObservableObjects are a disjoint class from Facets (by way of the ObservableObject superclass UcoObject being disjoint from Facet).  The variable name has been changed.

Yes I see how that could be confusing thanks for the PR and the work on it


serverless-pseudo-parameters not installed.

1.0.1
https://app.circleci.com/pipelines/github/sterling000/deckmasterweb-serverless/9/workflows/beffe32c-c4bd-44b5-beac-dc37e0f71655
trying to figure out how to get passed this plugin install, it works locally, i can run serverless deploy and it functions properly, it's listed in the serverless.yml, i ran the serverless install plugin --name serverless-pseudo-parameters command locally and it ran fine. I've tried adding it to my config for the orb but i keep getting this error and not sure what to do next.
To Reproduce

Fork or Clone: https://github.com/sterling000/deckmasterweb-serverless
enable circleci for your repo
push a small change to trigger the pipeline.
observe in the deploy step, it fails to install the serverless-pseudo-parameters plugin after it installs the serverless-cli

Expected behavior

I started this project following the tutorial here: https://www.serverless.com/learn/tutorial/user-creation/
Then i attempted to add circleci CI/CD for it, so I followed the instructions here for this orb.
I just put the latest version numbers into the orb config because the example had errors with x.y etc.
I am still on step #17 User Creation of the tutorial. Everything functions fine locally, just trying to have it autodeploy for me when i submit to github. (I'll lock down the repo later once things are configured).

@sterling000 looking at where your Serverless config is ({project_root}/services/user-service/serverless.yml, I think you'd need to explicitly inform the serverless deploy command where this file is located.

typically, they assume it is {project_root}/serverless.yml.

So in this line of your CircleCI config, you'd probably want to do this:
- command: serverless deploy -v
- command: serverless deploy -v --config services/user-service/serverless.yml


Date format numeric time zone with : to necessary precision

MAN DATE(1)

  %z     +hhmm numeric time zone (e.g., -0400)
  %:z    +hh:mm numeric time zone (e.g., -04:00)
  %::z   +hh:mm:ss numeric time zone (e.g., -04:00:
  %:::z  numeric time zone with : to necessary precision (e.g., -04, +05:30)
  %Z     alphabetic time zone abbreviation (e.g., EDT)

Both %z and %Z work but none of variants with : does.

why there is no wiki ?


[wip] feat: add sso commands

Commands to manage Single Sign-On authentication on projects.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

43 of 75 (57.33%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 62.429%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/gen.go
1
3
33.33%

cmd/sso.go
42
72
58.33%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
3752

Relevant Lines:
6010

💛  - Coveralls

@kangmingtay can't reply to that comment not sure why, so here it is:

i dont think this defaults to saml - if it's excluded, i get the following error: Error: accepts 1 arg(s), received 0

This is intentional, the user has to enter saml or in the future oidc to explicitly specify the type.


fix: 🐛 fire onMount event before attempting to play video

Build version: 2.8.0-pr-32.141 :crossed_fingers: video-autoplay on Travis :tada:

Build version: 2.8.0-pr-32.143 :crossed_fingers: video-autoplay on Travis :tada:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Translation issue with paypal standard payment method on the checkout page

Bagisto Version: Master
Steps To reproduce--
1. Log in a customer.
2. Add any product to the cart.
3. Process for checkout of the order.
4. Try to select the Paypal standard payment method.
Expected result: There should not any translation issue with paypal standard payment method on the checkout page
Actual result: There is a Translation issue with PayPal standard payment method on the checkout page Please find the screenshot Here

@jitendra-webkul
I am closing this issue, because if the admin will add the payment and shipping method for the Arabic locale then it will be reflected on the front otherwise this will reflect with the default locale. Please find the screenshot Here


Stabilize the Riak cluster running in the K8s/Knative environment

This branch is primarily to stabilize the Riak cluster running in the K8s/Knative environment.  The main issue was that Erlang VM which a Riak node is running on doesn’t understand the resource limit set by K8s.  Therefore, Erlang thinks it has access to the full set of system resources on the host machine, but will unfortunately be killed by K8s once Erlang uses up its K8s-assigned resources.
Specifically, the main fixes include:

Match the number of Erlang schedulers in Riak container to the number of assigned CPUs.
Increase Riak container's memory limit to 8GB.
Change Riak's backend to more memory-friendly LevelDB, and limit LevelDB's memory usage to 4GB. (Also applied to Ansible scripts for VM and Bare-metal deployments)
Configure Riak container's liveness probe to enable it to restart after failing.
Add a number of Erlang VM optimization parameters. (Also applied to Ansible scripts for VM and Bare-metal deployments)
Fix a few errors in various scripts.

The timeout is for "riak ping".  It will finish fast in any case (succeeds
or fails).  If it would take more than 10 seconds to finish, then something
is wrong..
On Wed, Jun 24, 2020 at 8:28 AM Istemi Ekin Akkus<EMAIL_ADDRESS>wrote:

@iakkus commented on this pull request.
In deploy/helm/microfunctions/templates/riak.yaml
https://github.com/knix-microfunctions/knix/pull/53#discussion_r444672113
:

     readinessProbe:

       exec:
         command:
         - /usr/sbin/riak
         - ping
       initialDelaySeconds: 45

     timeoutSeconds: 30

     failureThreshold: 10

     periodSeconds: 10

     timeoutSeconds: 10

Why do we need this timeout to be so small? Is it because we want KNIX to
come up as fast as it can?
Having it so small can only lead to more problems: if the cluster is
loaded and riak takes time to start, then we'll create a retry storm.
I'd suggest to make it longer (e.g., 30 seconds). We can still keep the
failureThreshold to 3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knix-microfunctions/knix/pull/53#pullrequestreview-436358036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQSEDHN7B7H7FP7DGGGPPDRYGMKTANCNFSM4OGBDKIA
.

Changed "timeoutSeconds" to 30 seconds as I think it does no harm anyways.
On Wed, Jun 24, 2020 at 9:50 AM Ruichuan Chen<EMAIL_ADDRESS>wrote:

The timeout is for "riak ping".  It will finish fast in any case (succeeds
or fails).  If it would take more than 10 seconds to finish, then something
is wrong..
On Wed, Jun 24, 2020 at 8:28 AM Istemi Ekin Akkus <
<EMAIL_ADDRESS>wrote:

@iakkus commented on this pull request.
In deploy/helm/microfunctions/templates/riak.yaml
https://github.com/knix-microfunctions/knix/pull/53#discussion_r444672113
:

     readinessProbe:

       exec:
         command:
         - /usr/sbin/riak
         - ping
       initialDelaySeconds: 45

     timeoutSeconds: 30

     failureThreshold: 10

     periodSeconds: 10

     timeoutSeconds: 10

Why do we need this timeout to be so small? Is it because we want KNIX to
come up as fast as it can?
Having it so small can only lead to more problems: if the cluster is
loaded and riak takes time to start, then we'll create a retry storm.
I'd suggest to make it longer (e.g., 30 seconds). We can still keep the
failureThreshold to 3.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/knix-microfunctions/knix/pull/53#pullrequestreview-436358036,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQSEDHN7B7H7FP7DGGGPPDRYGMKTANCNFSM4OGBDKIA
.


 I make sure busybox was pulled in to the 2 nodes
More-info: https://github.com/docker/swarm/issues/619

Can I ask what happens when you run your example busybox but attach stdin?
$ DOCKER_HOST=localhost:2375 docker run -i busybox /bin/echo hello

We were seeing this problem in v0.0.1 where when you try to attach to a container - it would fail silently with no content.  The unix-socket branch here does not have this problem but you have to bind powerstrip to a unix socket.
The error you are seeing looks like it could be that problem.

@binocarlos
Same thing happens. Also I've tried to run, through a docker client previously installed into powerstrip, and worked. I have to confirm if it works with this specific example.

Yep, I can confirm that it works with a "normal" docker client inside powerstrip
[aanm@localhost ~]$ sudo docker exec -ti powerstrip bash
root@9ca988eb0c33:/app# apt-get update && apt-get install wget &&  wget -qO- https://get.docker.com/ | sh
# After being installed....
root@9ca988eb0c33:/app# docker run busybox /bin/echo hello
hello
root@9ca988eb0c33:/app# docker ps -a
CONTAINER ID        IMAGE                       COMMAND                CREATED             STATUS                              PORTS                                     NAMES
6e88aea46692        busybox:buildroot-2014.02   "/bin/echo hello"      13 seconds ago      Exited (0) Less than a second ago                                             swarm-02/elated_curie
7e5ca8eb1762        swarm:latest                "/swarm join --addr    About an hour ago   Up About an hour                    2375/tcp                                  swarm-02/swarm-agent
f26f57f321ae        swarm:latest                "/swarm join --addr    About an hour ago   Up About an hour                    2375/tcp                                  swarm-01/swarm-agent
fa0d2c0c5a29        swarm:latest                "/swarm join --addr    About an hour ago   Up About an hour                    2375/tcp                                  swarm-master/swarm-agent
f51ef437d200        swarm:latest                "/swarm manage --tls   About an hour ago   Up About an hour                    2375/tcp, <IP_ADDRESS>:3376->3376/tcp   swarm-master/swarm-agent-master

@binocarlos
argh... the problem is this:
For now, Powerstrip does not support TLS, but given that it should only be used for prototyping in local development environments, that's OK.

And docker-machine only runs with TLS.
Is there any ETA for TLS on powerstrip?

@aanm hey...
So - there are no plans to support TLS in Powerstrip in the near future - we have a bunch of other stuff to focus on.  That said - if a PR landed with this feature it would get serious consideration :-)
You could set DOCKER_TLS_VERIFY=0 or use a TLS terminator as a work-around.
I have a question - I notice you are using Powerstrip in front of the swarm master.  This is a novel way to do it - the normal pattern is to have powerstrip installed on each docker host.
Here is a (simplified) diagram from the recent blog post we did demonstrating powerstrip and swarm together:
          docker client

                |

           swarm deamon

           /          \

       node1          node2

         |              |

    powerstrip       powerstrip

        |               |

      docker          docker

and here is a diagram of what seems to be happening in your setup:
           docker client

                |

            powerstrip

                |

           swarm deamon

           /          \

       node1          node2

        |               |

      docker          docker

What are the powerstrip adapters you intend to use in this setup?
acknowledged that docker-machine uses TLS as it's default setup so there will some degree of manual setup in order to work-around the TLS issue.

Hmm I don't know why but I thought the nodes would be all equal but they could or couldn't be...
So... why not on both sides? ;-)
          docker client
                |
           powerstrip
                |

           swarm deamon

           /          \

       node1          node2

         |              |

    powerstrip       powerstrip

        |               |

      docker          docker

Hey - so interesting setup :-)
In theory that would work - however, what adapters would make sense in the upper-most powerstrip?

That's what I'm still trying to figure it out :-)

@aanm Were you able to make this setup work?
    docker client

                |

            powerstrip

                |

           swarm deamon

           /          \

       node1          node2

        |               |

      docker          docker

@Pensu I think so if the docker client isn't docker machine

@Pensu I think that setup would depend heavily on what Powerstrip adapters you were trying to use.
For example - if using powerstrip-weave - it would not work because the adapter would be running on a proxy node not the nodes that Docker itself is running on.
However - if you were wanting to change all containers to have extra environment variables - i.e. something that just changed the JSON body of the call to /containers/create and did not require software to be installed on the proxy machine - then it would work.
What are the adapters you are wanting to run in this setup?

@binocarlos ok, I was actually trying to add an authentication mechanism(or adapter?) to swarm, just to try it out. Btw I was able to make powerstrip work with this setup and as @aanm said, not with docker-machine but with the development setup.


Add support for something like testID /testKeyId for widgets

In react application you can specify a data-testId attribute to identify a component when performing unit/component tests.
Just like that:
"<MyComponent data-testId="myComponent" //>"
Then when I create a unit test in jest I can get the component directly from that data-testId and be happy.
Working with flutter when I want to find a element in a test the most used ways that I do is find it through the text (which is totally a bad practice because thats a thing that change a lot in the future) or the type of component, thats turn to be a mess in certain situations..
Why not create a key-id, a property linked to  the widget component that can be used by the test to identify a widget or multiples widget with same test-id. Just like that:
myComponent extends StatelessWidget {
myComponent() : super (testId:'myComponent')
}
In test you could find it with something like that:
find.byTestId('myComponent');

This is exactly what Key is for?
https://api.flutter.dev/flutter/foundation/Key-class.html
https://docs.flutter.dev/cookbook/testing/widget/finders#2-find-a-widget-with-a-specific-key

I always though that Key is internally used by flutter to check the state of a widget,  a testID should not have any purpose other than be used for locate a component in the render tree.

Hi @MisterLight
I have the same thought with @navaronbracke about this, you can use a Key to find a widget in unit tests.
If you still believe this issue is an appropriate feature request, please tell us the problem you are running into when using Key that led to you wanting a new feature. Thanks!


[Navi21][tests] Disable MLIR tests on gfx103x when libMLIR <= 1.0.0. [CI][Navi21][WORKAROUND] Enable MLIR tests on gfx103x with current docker image

This partially resolves issue #1913.

MLIR tests on gfx103x are disabled when libMLIR reports version <= 1.0.0

cmake ... -DMIOPEN_LIBMLIR_SUPPORTS_GFX103X=On can be used to override.

Added WORKAROUND_ISSUE_1913 to Jenkinsfile. It enables MLIR testing on GFX10 with current CI docker image.

@junliume https://github.com/ROCmSoftwarePlatform/MIOpen/labels/testing https://github.com/ROCmSoftwarePlatform/MIOpen/labels/urgency_normal
@jerryyin Can you please review this and take care about implement the remaining fixes (proposal):

Make changes in libMLIR so its version > 1.0.0
Bump libMLIR commit hash so the above change is included for MIOpen.
Update docker image for CI with new libMLIR.
Remove WORKAROUND_ISSUE_1913.

⚠ Jenkinsfile changes from forks are not used in CI (due to security reasons). Therefore we need to check if WORKAROUND_ISSUE_1913 really works (enables test_conv_igemm_mlir_fwd and test_conv_igemm_mlir_bwd_wrw on Navi21) after merging this PR. @junliume @jerryyin can you please take care about this?

@atamazov the CI fails with the following cmake error:
[2023-01-11T08:25:18.807Z] CMake Error at CMakeLists.txt:29 (if):

[2023-01-11T08:25:18.807Z]   if given arguments:

[2023-01-11T08:25:18.807Z]

[2023-01-11T08:25:18.807Z]     "OFF" "AND" "(" "GREATER" "100000000" ")"

[2023-01-11T08:25:18.807Z]

[2023-01-11T08:25:18.807Z]   Unknown arguments specified

[2023-01-11T08:25:18.807Z] Call Stack (most recent call first):

[2023-01-11T08:25:18.807Z]   test/CMakeLists.txt:126 (set_var_to_condition)

[2023-01-11T08:25:18.807Z]

[2023-01-11T08:25:18.807Z]

[2023-01-11T08:25:18.807Z] -- Configuring incomplete, errors occurred!

to reproduce"
CXX=/opt/rocm/llvm/bin/clang++ CXXFLAGS='-Werror'  cmake -DMIOPEN_TEST_FLAGS=' --disable-verification-cache ' -DCMAKE_BUILD_TYPE=release -DBUILD_DEV=On -DMIOPEN_USE_MLIR=OFF -DMIOPEN_LIBMLIR_SUPPORTS_GFX103X=ON -DMIOPEN_GPU_SYNC=Off -DBUILD_SHARED_LIBS=Off -DCMAKE_PREFIX_PATH=/opt/rocm    ..

@junliume @jerryyin PR is ready for next round of review & CI testing.


Migrate to JUnit 5

JUnit 5 is here for 1.5 year. Wouldn't be convenient to migrate from JUnit 4 up to the contemporary version of framework?
I've already did the migration in my fork of the project and the changes are relatively easy, mostly change of imports (e.g. N00StartKtTest.kt). I can prepare a pull request for this.

Thanks! Updated


NodePaths don't get adjusted when slices are injected

Currently, SliceManager is responsible for keeping track of slice indices.
When a slice gets applied, all other slice indices targeting the same node get moved in order to still point to the correct target.
However, I forgot to apply this same operation to all NodePaths that contain this node's index.

This should be fixed now, though not really tested.
If there are problems with this in the future we can open a new issue.


Scrcpy opens but crashes after few seconds

ERROR : Could not open audio device : WASAPI can't initialize audio client: Coinitialize has not been called

#3825
Do you use the latest scrcpy release (v2.1.1) with the SDL version containing a fix?

OK I updated it and now it got fixed. Thanks

I had the same problem with new version(v2.4)

SDL: 2.28.5 / 2.28.5
libavcodec: 60.31.102 / 60.31.102
libavformat: 60.16.100 / 60.16.100
libavutil: 58.29.100 / 58.29.100
libusb: - / 1.0.27

With that exact same error message (WASAPI can't initialize audio client: Coinitialize has not been called)? (try the latest version just in case, 2.6.1 currently)
If this still happens, it should be reported to libsdl: https://github.com/libsdl-org/SDL/issues/7478 (where the problem is expected to be fixed)

ERROR: Could not open audio device: WASAPI can't find requested audio endpoint: Element not found.

That's a slightly different message.
I just opened a new issue here: https://github.com/libsdl-org/SDL/issues/10506


When I specify --walet-url for cleos, execute "set set contract", indicating that the wallet is not unlocked, but only one keosd is running.

1、When I specify --walet-url for cleos, execute "set set contract", indicating that the wallet is not unlocked, but only one keosd is running.

2、keosd process:

@amActiveHello still not able to set contract after unlocking wallet ?

yes, it is.

Try ps aux | grep keosd.  Without the a flag, ps won't show you processes created in another terminal.  Until you get a clean start without an Address already in use complaint, there is definitely another process using port 8900, and it's probably another keosd.


[device controller] Add connect -code for connect using manual pairing code

Problem

At present, python controller has 'connect' command to provision over BLE/IP or using QR code. Need to add support to connect using manual pairing code to provision nodes using manual pairing code..
Fixes #9112

Change overview

Add connect -code support.
Updated logic in ConnectFromSetupPayload:

The code will test pairing over IP first, if failed, it will try BLE

The rendezvous infomation will be set to all if no rendezvous infomation provided.

Testing

Manually tested

@cjandhyala Please verify this.

@saurabhst ?


npm install race condition

Description
When using hap-nodejs via npm I discovered that it actually mattered in what order the packages hap-nodejs and<EMAIL_ADDRESS>are installed.
When I initially attempted to use this library, I looked at the BridgedCore.js example. Then I installed the needed packages and tried to refactor the code, so that it uses the npm dependencies.
I encountered a lot of problems related to localStorage being undefined. This is because of a hack, this library relies on. It trusts node-persist to be the same instance on the library & BridgedCore.js files. However, when you install hap-nodejs first, npm will install two instances of node-persist, which breaks the localStorage.
Case Distinction
a) install hap-nodejs first
This reliably fails on both of my systems, since npm will install two instances of node-persist.
Console Output
HAP-NodeJS starting...
/home/dodekeract/code/HAP-NodeJS/node_modules/hap-nodejs/node_modules/node-persist/node-persist.js:107
        return localStorage.getItem(key, callback);
                           ^

TypeError: Cannot read property 'getItem' of undefined
    at Object.nodePersist.getItem (/home/dodekeract/code/HAP-NodeJS/node_modules/hap-nodejs/node_modules/node-persist/node-persist.js:107:28)
    at Function.AccessoryInfo.load (/home/dodekeract/code/HAP-NodeJS/node_modules/hap-nodejs/lib/model/AccessoryInfo.js:103:23)
    at Bridge.Accessory.publish (/home/dodekeract/code/HAP-NodeJS/node_modules/hap-nodejs/lib/Accessory.js:417:39)
    at Object.<anonymous> (/home/dodekeract/code/HAP-NodeJS/BridgedCore.js:25:8)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:139:18)

npm list
<EMAIL_ADDRESS>/home/dodekeract/code/HAP-NodeJS
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>(git://github.com/KhaosT/node-curve25519.git#922eae612bb379fa84e8deb29f80c53d57c8be7b)
│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>(git://github.com/KhaosT/ed25519.git#6356bc9e6e4643d56020293c14920ac12bcaa1ac)
│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>(git://github.com/KhaosT/node-srp.git#7feff53254897a0b1b9f0667ad17a8beb78acbb9)
│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
Two separate instances of node-persist.
b) install<EMAIL_ADDRESS>first
This fixed the issue, since only one instance of node-persist will be installed. Took me about 4 hours to figure this one out though.
Console Output
HAP-NodeJS starting...

npm list
<EMAIL_ADDRESS>/home/dodekeract/code/HAP-NodeJS
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>(git://github.com/KhaosT/node-curve25519.git#922eae612bb379fa84e8deb29f80c53d57c8be7b)
│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>(git://github.com/KhaosT/ed25519.git#6356bc9e6e4643d56020293c14920ac12bcaa1ac)
│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├──<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>(git://github.com/KhaosT/node-srp.git#7feff53254897a0b1b9f0667ad17a8beb78acbb9)
│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
As you can see, there is only one instance of node-persist.
Code To Reproduce This
BridgedCore.js (modified)
var path = require('path');
var storage = require('node-persist');
var uuid = require('hap-nodejs').uuid;
var Bridge = require('hap-nodejs').Bridge;
var Accessory = require('hap-nodejs').Accessory;

console.log("HAP-NodeJS starting...");

// Initialize our storage system
storage.initSync();

// Start by creating our Bridge which will host all loaded Accessories
var bridge = new Bridge('Node Bridge', uuid.generate("Node Bridge"));

// Listen for bridge identification event
bridge.on('identify', function(paired, callback) {
  console.log("Node Bridge identify");
  callback(); // success
});

bridge.addBridgedAccessory(require('./Light_accessory.js').accessory);

// Publish the Bridge on the local network.
bridge.publish({
  username: "CC:22:3D:E3:CE:F6",
  port: 51826,
  pincode: "031-45-154",
  category: Accessory.Categories.BRIDGE
});

Light_accessory.js (modified)
var Accessory = require('hap-nodejs').Accessory;
var Service = require('hap-nodejs').Service;
var Characteristic = require('hap-nodejs').Characteristic;
var uuid = require('hap-nodejs').uuid;

// here's a fake hardware device that we'll expose to HomeKit
var FAKE_LIGHT = {
  powerOn: false,
  brightness: 100, // percentage

  setPowerOn: function(on) {
    console.log("Turning the light %s!", on ? "on" : "off");
    FAKE_LIGHT.powerOn = on;
  },
  setBrightness: function(brightness) {
    console.log("Setting light brightness to %s", brightness);
    FAKE_LIGHT.brightness = brightness;
  },
  identify: function() {
    console.log("Identify the light!");
  }
}

// Generate a consistent UUID for our light Accessory that will remain the same even when
// restarting our server. We use the `uuid.generate` helper function to create a deterministic
// UUID based on an arbitrary "namespace" and the word "light".
var lightUUID = uuid.generate('hap-nodejs:accessories:light');

// This is the Accessory that we'll return to HAP-NodeJS that represents our fake light.
var light = exports.accessory = new Accessory('Light', lightUUID);

// Add properties for publishing (in case we're using Core.js and not BridgedCore.js)
light.username = "1A:2B:3C:4D:5E:FF";
light.pincode = "031-45-154";

// set some basic properties (these values are arbitrary and setting them is optional)
light
  .getService(Service.AccessoryInformation)
  .setCharacteristic(Characteristic.Manufacturer, "Oltica")
  .setCharacteristic(Characteristic.Model, "Rev-1")
  .setCharacteristic(Characteristic.SerialNumber, "A1S2NASF88EW");

// listen for the "identify" event for this Accessory
light.on('identify', function(paired, callback) {
  FAKE_LIGHT.identify();
  callback(); // success
});

// Add the actual Lightbulb Service and listen for change events from iOS.
// We can see the complete list of Services and Characteristics in `lib/gen/HomeKitTypes.js`
light
  .addService(Service.Lightbulb, "Fake Light") // services exposed to the user should have "names" like "Fake Light" for us
  .getCharacteristic(Characteristic.On)
  .on('set', function(value, callback) {
    FAKE_LIGHT.setPowerOn(value);
    callback(); // Our fake Light is synchronous - this value has been successfully set
  });

// We want to intercept requests for our current power state so we can query the hardware itself instead of
// allowing HAP-NodeJS to return the cached Characteristic.value.
light
  .getService(Service.Lightbulb)
  .getCharacteristic(Characteristic.On)
  .on('get', function(callback) {

    // this event is emitted when you ask Siri directly whether your light is on or not. you might query
    // the light hardware itself to find this out, then call the callback. But if you take longer than a
    // few seconds to respond, Siri will give up.

    var err = null; // in case there were any problems

    if (FAKE_LIGHT.powerOn) {
      console.log("Are we on? Yes.");
      callback(err, true);
    }
    else {
      console.log("Are we on? No.");
      callback(err, false);
    }
  });

// also add an "optional" Characteristic for Brightness
light
  .getService(Service.Lightbulb)
  .addCharacteristic(Characteristic.Brightness)
  .on('get', function(callback) {
    callback(null, FAKE_LIGHT.brightness);
  })
  .on('set', function(value, callback) {
    FAKE_LIGHT.setBrightness(value);
    callback();
  })

Proposed Solution
Since relying on only having one instance of node-persist is apparently error-prone, I suggest to just allow users to pass in any storage solution they want to pass into this library. At least allow passing an instance of node-persist to have a reliable way to fix this issue.
Versions
npm: 2.15.1
node: 4.4.3
hap-nodejs: 0.3.2
node-persist: 0.0.8
OS: Ubuntu 16.04 & Raspbian Jessie

This is not a bug with the project, instead, it's how node.js lookup external modules. If you plan to use hap-nodejs in a separate project, please add hap-nodejs as a dependency of the project and use npm or other package manager to manage the modules.

Did you even read it? I AM using npm. What? This IS caused by this module not allowing to pass the node-persist instance.

@dodekeract I don't get it, if your dependency is managed by npm, how you can a) install hap-nodejs first or b) install<EMAIL_ADDRESS>first? npm doesn't give you the option to do this. homebridge has been using this package as a dependency for ages and it never encounter this problem.

@dodekeract and if you want, here is the sample test I created trying to reproduce this problem. After npm install it runs fine.

@KhaosT yes, npm does npm install a && npm install b.

@dodekeract but that's not what I mean by "manage dependency" ... ideally by using package.json, npm will recursively figure out what package is needed and install all things in the right place. If you manually install each package via npm, then due to the way how npm look up the existing packages, there might have a issue. However, I'm not sure in that case the issue belongs to this project or npm itself.

@KhaosT at least in my usual workflow (I added this to an existing project) I use npm install package --save. This will probably work on when somebody uses a fresh install of my project's repo, but it's REALLY confusing when you're trying to use a new package in a new project. From the installation order, it even makes sense to install hap first (if you're not aware of this bug).
It's like really confusing if everything breaks, just because you installed it in the wrong order when trying to include HAP in a project.

I'm having similar problems. Using hap-nodejs as a dependency, I've created my own module that does something similar to what BridgedCore.js does. Even though I'm not utilizing node-persist directly in my module, I have to include it and initialize the storage. I'm forced to call storage.initSync(); to support something internal to the way hap-nodejs works... which is strange, but even more frustrating now I'm dealing with this dependency install-order issue.
var storage = require('node-persist');
const HAP = require('hap-nodejs');
var uuid = HAP.uuid;
var Bridge = HAP.Bridge;
var Accessory = HAP.Accessory;
var Service = HAP.Service;
var Characteristic = HAP.Characteristic;

storage.initSync();

class HomekitBridge extends Bridge {

  constructor(name, relayController) {
    super(name, uuid.generate(name));
    this.relayController = relayController;
  }

  addValves(valves) {
    for (var key in valves) {
      this.addValve(key);
    }
  }

  addValve(name) {
    this.addBridgedAccessory(this._toAccessory(name));
  }

  _toAccessory(name) {
    var id = uuid.generate('underbluewaters:irrigation:'+name);
    let valve = new Accessory('Irrigation Valve', id);
    valve
      .getService(Service.AccessoryInformation)
      .setCharacteristic(Characteristic.Manufacturer, "Hunter")
      .setCharacteristic(Characteristic.Model, "606800")

    valve.on('identify', function(paired, callback) {
      callback(); // success
    });

    let self = this;

    valve
      .addService(Service.Outlet, name)
      .getCharacteristic(Characteristic.On)
      .on('set', function(value, callback) {
        self.relayController.set(name, value);
        callback();
      });

    valve
      .getService(Service.Outlet)
      .getCharacteristic(Characteristic.On)
      .on('get', function(callback) {
        var on = self.relayController.getState(name);
        callback(null, on);
      });

    valve
      .getService(Service.Outlet)
      .getCharacteristic(Characteristic.OutletInUse)
      .on('get', function(callback) {
        callback(null, true);
      });

    return valve;
  }

}

module.exports = HomekitBridge;

Okay, found a solution to the problem with node-persist initialization. For me at least. I was able to call the init method exposed by the main hap-nodejs module and that solved the issue. So in my code, it looks like this:
// no need for this
// const storage = require('node-persist');
// storage.initSync();
const HAP = require('hap-nodejs');
HAP.init();


for issue #12 (# 51) (rebased on current master)

working mailman parser
attach (default) date information so that feed can be parsed by importer
prepare the date hack
annotate items with dates

@chrisdone, can you point the Travis build to the organization repo?

Thanks @jwaldmann! I'll give it a review and hopefully we get the Travis build back pretty soon so we can give it a run :)

(bump) What is the status here? I don't quite see which of your requested changes do you think are blocking the merge. (I think: none.)

Thanks for taking the time on this @jwaldmann!


test: add tests for checking options are correctly passed to embed ui

Description
Adding a few test cases for ensuring the options are being correctly passed to the underlying embed ui frame. I have tested several types of values and also negative tests for error messages.
In order to initiate Embed with correct parameters I had to use a base64 encoded param in the url so that that original data type (e.g. null) is not tampered with.
We may decide later on to move/refactor these to a new home, but this should give us more confidence.
Fixes # https://gr4vy.atlassian.net/browse/TA-1643
Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own changes
[x] I have run yarn lint to make sure my changes pass all tests
[x] I have run yarn test to make sure my changes pass all linters
[x] I have pulled the latest changes from the upstream main branch
[x] I have tested both the react and the CDN versions on local and integration environments
[x] I have added the necessary labels to this PR in case a new release needs to be published after merging into main (e.g. release and patch)

Contribution guidelines
For contribution guidelines, styleguide, and other helpful information please
see the CONTRIBUTING.md file in the root of this project.

:rocket: PR was released in v2.11.7 :rocket:


trailing commas on multiline hashes needed to pass cookstyle

Not my favorite rule. :)

This has been fixed in #64


ARM support

EECS 281 is thinking about releasing this container image to students. One major roadblock is that it does not support ARM 64 version (MacOS). Reading the commit history I figured out that it was removed intentionally. Was there a particular reason?

This has been released to students at least in F22: https://eecs281staff.github.io/eecs281setup/guides/unified.
Build ARM native images on x86 machines by using qemu (or attempting some form of cross compilation, which was quite complex when I tried). Currently, building this image natively for x86 already takes hours, and building it in qemu simply takes too much time to be practical. However, it would be feasible now if we had an ARM build machine. Then, we could separately build the image for both platforms natively and publish an umbrella metadata that includes both images.
This, however, doesn’t mean that students can’t use this image on ARM. Docker automatically creates containers based on x86 images using qemu. Students need considerably fewer computational resources compared to compiling GCC and other tools during the build process, making it a more likely solution to compromise runtime speed, although it can be significant.

OK I see you are right.


Testing updated version of jackson-databind

Signed-off-by: Guian Gumpac<EMAIL_ADDRESS>Description
Testing that the updated jackson-databind version fixes the CVE
Issues Resolved
https://github.com/opensearch-project/sql/issues/897
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #943 (b3124b3) into 2.x (057fa44) will decrease coverage by 35.10%.
The diff coverage is n/a.

:exclamation: Current head b3124b3 differs from pull request most recent head 94ff931. Consider uploading reports for the commit 94ff931 to get more accurate results

@@              Coverage Diff              @@
##                2.x     #943       +/-   ##
=============================================
- Coverage     97.87%   62.76%   -35.11%
=============================================
  Files           284       10      -274
  Lines          7425      658     -6767
  Branches        475      119      -356
=============================================
- Hits           7267      413     -6854
- Misses          157      192       +35
- Partials          1       53       +52

Flag
Coverage Δ

query-workbench
62.76% <ø> (?)

sql-engine
?

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

Impacted Files
Coverage Δ

...ain/java/org/opensearch/sql/analysis/Analyzer.java

...rg/opensearch/sql/analysis/ExpressionAnalyzer.java

...org/opensearch/sql/analysis/HighlightAnalyzer.java

...opensearch/sql/expression/HighlightExpression.java

...h/sql/expression/function/OpenSearchFunctions.java

...ensearch/sql/planner/logical/LogicalHighlight.java

...opensearch/sql/planner/logical/LogicalPlanDSL.java

...l/opensearch/request/OpenSearchRequestBuilder.java

...search/sql/opensearch/storage/OpenSearchIndex.java

...ensearch/sql/ppl/utils/PPLQueryDataAnonymizer.java

... and 284 more

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


Issue loading the character sheet

Running foundry on the last V11 version of D&D 5E. Upon changing the vehicle sheet setting to Wildjammer the sheet closes and just doesn't open. The actor is still there, its just that nothing happens.

I get the same issue when ever I create a new token. But if I copy a token it works fine. When I export the sheet, it's lacking all the WJA info needed to populate the sheet.
DnD 4.1.2
Foundry 12 Build 331


Result-set fetch size font color

How can I change the font color of the result-set fetch size?

Unfortunately, it is not possible. Why do you need it?


refactor: Introduced freezed, fpdart and hooks to refactor LandingPage flow

Summary
Added freezed, hooks, fpdart dependencies and refactored the LandingPage to make use of them. Freezed will allow for easy state object generation and creation, hooks eliminates much boilerplate code and makes Stateful widgets Stateless, and fpdart allows for functional types for better null/error handing. This PR just refactors the LandingScreen to use all those packages.
This is mostly future-proofing, as the app and complexity grows, these packages become more indispensable.
Other Information
AuthenticationController was split up into 2 classes due to increasing complexity.
AuthenticationRepository was also changed to use TaskEither type from fpdart, eliminating the need for try/catch blocks in the controller classes.
Due to freezed/json_annotation package, now you have to call this command before running the project to generate the additional classes
flutter pub run build_runner build
or possibly
flutter pub run build_runner build --delete-conflicting-outputs
We should also update the Model objects to use freezed, but this should be a separate issue.

@linxydmhg thank you for such effort. My concern is that many people aren't familiar with freezed, fpdart, and hooks. Don't want people to stop contributing because they don't know Riverpod, Freezed, FPDart, and Hooks.
There was a discussion to introduce a base view but that was also stopped considering it would make things difficult for other contributors.
@jorre127 what do you think?

@dinurymomshad hmm yeah this is a hard one. If we would add all these I don't think the average person is going to be able contribute because we are so far distanced from "normal" flutter. Don't think most people even work with packages that change the state management like riverpods, and if you add functional programming on top of that most people are going to be lost and will probably only be able to contribute with small standalone widgets that don't handle logic. But on the other hand I do think this makes the code better and more stable. So it's probably something @KalleHallden  has to decide on.
Do we want better stable code that only a few people will be able to work on (more burden will fall on these people then to add new features to the project) or do we want to keep it more simple and allow more people to be able to contribute?

@dinurymomshad hmm yeah this is a hard one. If we would add all these I don't think the average person is going to be able contribute because we are so far distanced from "normal" flutter. Don't think most people even work with packages that change the state management like riverpods, and if you add functional programming on top of that most people are going to be lost and will probably only be able to contribute with small standalone widgets that don't handle logic. But on the other hand I do think this makes the code better and more stable. So it's probably something @KalleHallden has to decide on.
Do we want better stable code that only a few people will be able to work on (more burden will fall on these people then to add new features to the project) or do we want to keep it more simple and allow more people to be able to contribute?

I'd vote on keeping it simple until we are done organizing everything. We have tons of things left to do. Only the landing page is somewhat organized.

I honestly don't know which way to go. I haven't worked with these sort of things, my applications have usually been dead simple. So I am very lost when it comes to pretty much all of this stuff, I do think what you are suggesting is a good idea long term. Structure usually is. But short term we may need to keep it simple. But I feel very unqualified to even suggest something here.

Closing the pull request.


Delete node from orientdb when delete operation is performed within STIG

Currently the right click delete function within STIG does not delete the node form the database. This can be seen when querying the database after restarting the application or clearing the graph. Adding this feature would be helpful as the current workaround is downloading the json bundle, creating a new db, and then committing the objects in the updated json bundle to the new db.

Add in dropdown Graph select to --> delete selected from db


bar-card.js:5355:0 SyntaxError: export declarations may only appear at top level of a module

The bar-card component does not work anymore and I see these logs:
bar-card.js:5219:1 Uncaught SyntaxError: Unexpected token 'export'
bar-card.js:5355:0 SyntaxError: export declarations may only appear at top level of a module
I'm using hacs, the version of bar-card is  3.1.6 and Home Assistant 0.110.1

It appears that bar-card is now a module
    - url: /hacsfiles/bar-card/bar-card.js
      type: module

instead of
    - url: /hacsfiles/bar-card/bar-card.js
      type: js


Thanks

Just wanted to say thanks for these script examples - very useful!

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

ID: 2e56fc8a-59e1-84e4-d618-688fc6502cf1
Version Independent ID: 0edf6356-1e87-9117-09ec-6cb62a5549d2
Content: Scripting with Storage Spaces Direct performance history
Content Source: WindowsServerDocs/storage/storage-spaces/performance-history-scripting.md
Technology: storage-spaces
GitHub Login: @cosmosdarwin
Microsoft Alias: cosdar

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


skip pilot tests that fail under multicluster mode

Tests have gone from passing to failing in the pilot-multicluster job. These may have been caught early if this job was required. The goal of this PR is to get the job consistently passing, so we can mark it required and prevent any other regressions.
Things that have regressed:

calling Naked service always fails
traffic shifting flakes often

https://prow.istio.io/?repo=istio%2Fistio&pull=27954&job=integ-pilot-multicluster-tests_istio

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
cc49845c9bc40a99af96bba6450367eaaead7e67
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@nmittler tracking somewhat in: https://github.com/istio/istio/issues/24581
Not sure if they're real bugs or not yet.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6f9718aa465c24a63690df401b6ccd7ac5fe29f5
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
6f9718aa465c24a63690df401b6ccd7ac5fe29f5
link
/test integ-pilot-k8s-tests_istio

integ-security-k8s-tests_istio
6f9718aa465c24a63690df401b6ccd7ac5fe29f5
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
6f9718aa465c24a63690df401b6ccd7ac5fe29f5
link
/test integ-security-k8s-tests_istio

integ-pilot-k8s-tests_istio
6f9718aa465c24a63690df401b6ccd7ac5fe29f5
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
119ebfef5ce3786b9e9e3953fa3698395290078c
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
119ebfef5ce3786b9e9e3953fa3698395290078c
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Hoping to use https://github.com/istio/istio/pull/28035 to fix underlying issue rather than just skipping the tests.


⚠ ClamAV has degraded performance

In b6fe697, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 190 ms

Resolved: ClamAV performance has improved in c362cfe.


Internal Address

Hello. What is internal address in hd wallet of tron for? What is the diference between address 0 of account 0 of an mnemonic in deposit and internal mode?

Internal addresses are no different than external addresses (deposits) in technical point of view.
They just serve to different purpose.
Kindly check the explanation in BIP32 doc;
https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki


List out of index error

I am trying to create the certificate.
I am getting the following error

Traceback (most recent call last):
File "/root/docker_test/acme-tiny/acme_tiny.py", line 198, in
main(sys.argv[1:])
File "/root/docker_test/acme-tiny/acme_tiny.py", line 194, in main
signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER, CA=args.ca, disable_check=args.disable_check, directory_url=args.directory_url, contact=args.contact)
File "/root/docker_test/acme-tiny/acme_tiny.py", line 131, in get_crt
challenge = [c for c in authorization['challenges'] if c['type'] == "http-01"][0]
IndexError: list index out of range

order value is below

{u'status': u'ready', u'expires': u'2020-04-23T10:26:49Z', u'authorizations': [u'https://acme-v02.api.letsencrypt.org/acme/authz-v3/3952667423', u'https://acme-v02.api.letsencrypt.org/acme/authz-v3/3952667424'], u'finalize': u'https://acme-v02.api.letsencrypt.org/acme/finalize/83374546/3020394335', u'identifiers': [{u'type': u'dns', u'value': u'www.example.com'}, {u'type': u'dns', u'value': u'example.com'}]}

It looks like you either try to obtain a wildcard certificate (which requires DNS-01 challenges, which this script does not support), or you recently obtained a certificate for that domain with a DNS-01 challenge (the authz is still valid).
The authz (with domain name changed to example.com as in the issue itself):
$ curl https://acme-v02.api.letsencrypt.org/acme/authz-v3/3952667423
{
  "identifier": {
    "type": "dns",
    "value": "example.com"
  },
  "status": "valid",
  "expires": "2020-05-14T09:44:42Z",
  "challenges": [
    {
      "type": "dns-01",
      "status": "valid",
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/3952667423/xBagmA",
      "token": "HN3zDTTyhAn1J_Sxaf3O27Xjh_Cg7o8XR8FCOJ94TlE",
      "validationRecord": [
        {
          "hostname": "example.com"
        }
      ]
    }
  ],
  "wildcard": true
}

It says "wildcard": true, so you're apparently requesting a wildcard certificate.

OK. Will try for single domain

While closed, SAN/multiple domains are supported, wildcard domains are not.


Fuel compatibility (Galacticraft)

I am playing Bevo's tech pack (version 10-FULL) and I was shocked when I found out that you can't use Ender IO fuels with GalactiCraft. The GC wiki says that you CAN use other forge fuels as well, which makes me think that is a GC bug. Anyways, can you make your fuels compatible with GC (at least rocket fuel, since that would make a lot of sense) or is it impossible to make that without hacking micdoodle8's mod?

Galacticraft 3.0.10 now accepts EnderIO rocket Fuel Buckets as fuel.  Each will add 1000mB of fuel to a Fuel Loader.
http://wiki.micdoodle8.com/wiki/Whats_New
(Support for piped in Rocket Fuel will be added next build.)
I don't see that any of the other EnderIO Vat liquids are suitable for cross-mod support in Galacticraft as they do not have equivalents.
Question:  would it unbalance EnderIO if we allow buckets of Rocket Fuel to be filled in Galacticraft machines?

In what way? What would it cost? Rocket fuel is a very potent fuel, and
is usually quite difficult to make.
On Mar 23, 2015 9:17 AM, "Co-developer of Galacticraft" <
<EMAIL_ADDRESS>wrote:

Galacticraft 3.0.10 now accepts EnderIO rocket Fuel Buckets as fuel. Each
will add 1000mB of fuel to a Fuel Loader.
http://wiki.micdoodle8.com/wiki/Whats_New
(Support for piped in Rocket Fuel will be added next build.)
I don't see that any of the other EnderIO Vat liquids are suitable for
cross-mod support in Galacticraft as they do not have equivalents.
Question: would it unbalance EnderIO if we allow buckets of Rocket Fuel to
be filled in Galacticraft machines?
—
Reply to this email directly or view it on GitHub
https://github.com/SleepyTrousers/EnderIO/issues/985#issuecomment-84993620
.

That's what I mean.  Players who have advanced into late game can make Fuel in large quantities in Galacticraft.  Especially on Mars, if you have plenty of electricity there (which could come from solar), an infinite Fuel factory can be built without any resource cost once it starts working.  http://wiki.micdoodle8.com/wiki/Methane_Synthesizer
Currently we do not allow Fuel -> Rocket Fuel conversion, and sounds like it will be best if it stays that way.


feat(entoas): added field annotation for skip flag

Added Ignored field to Annotation struct to support ignored filed in spec (useful for deletedAt field or system fields don't need in spec).

cc @masseelch.
Also, please use Skip instead of Ignored to keep it consistent with the rest of the packages here (e.g. entgql).

@a8m I can rename field or need realize logic SkipMode?

@masseelch review pls

@badygin-yakov I am not sure what this PR does. For what I can see it adds an annotation but does not do anything with it. Can you explain?

Please fix the CI, then I will merge


Access the button not only from the readme

I almost never open Readme in a separate view, normally I just read it from the repo root page. So for me this button would be much more useful if it appeared there.
Also, as there is a plugin button in the Chrome toolbar, is it possible to access the TOC from there? When I'm in the middle of a big readme, it's not so convenient to croll all the way up to jump to some other section..

Hi @laughedelic, thanks so much for the input!
First, you should be seeing the button on the repo root page. Well, the button is missing its icon and it looks like an empty box, but I'm pushing a fix for that today. I usually view READMEs the same way. See #9.
Second, I like your idea to display the ToC from the button in the Chrome Menu. I thought about docking the navigation somehow for when you scroll a large README, but I think your selection is easier to implement. I'll create a new issue for this.
Thanks!

Great that you like the idea.
I see the empty square icon if I open a readme file, but I still don't see it on the root page:

Can it be that it interferes with the refined-github plugin?

Yep, that's why! I'll look into making it work with refined-github. I could also port this to refined-github and have it work with everything else they're doing. If you think this should be part of their extension, please comment on sindresorhus/refined-github#151. I'm not sure what's best for the project, and I'm happy to have it either way.


Restore scroll position

React Router restores scroll position between route changes, I don't have the time right now, but will hopefully have some time soon to try integrating the two libs and see if you can't get scroll positions for free, and routes along with it :)

That would be terrific! Thank you :)

Implemented in 0.4.0


Why are dependencies specified to patch level?

For instance, cortex-m-rt = "0.6.9" is set. But 0.6.10 is the latest release. So someone will have to create an issue, a pull request, a new RTFM release, etc.
If I am not mistaken, setting cortex-m-rt=0.6 in dependencies would do the right thing, and semver for pre-v1 releases should guarantee that nothing breaks.
Generally, I would expect dependencies to be specified as 0.x instead of 0.x.y, what am I missing?

Cargo already knows that 0.6.9 is compatible with 0.6.10 and will use the latter. The only way to prevent that is by using a stricter version requirement like "=0.6.9", but rtfm doesn't do that.

Ah OK, so it's asking for at least . 9. Thanks!


problem on generating fulltext rss

Hello, I have a problem on  generating fulltext rss from the existing rss source.
I want to get two type of information ( the link of "view in publisher" and the abstract ) from all link of the paper title. But I failed to extract these information. Can anyone give me some advice?

The setting of agent is attached as follow. The rss agent works and I have used "Re-emit" comand to test the website agent. The log of website agent shows "Values extracted: []". Thanks and sorry for my poor english:-)
Rss Agent
{
"expected_update_period_in_days": "50",
"clean": "false",
"url": "https://syndic8.scopus.com/getMessage?registrationId=BBIACDPABBIABBIBDBJHCBKJCFKGEEPGCKRFECJIBM"
}
Website Agent
{
"expected_update_period_in_days": "100",
"url": "{{url}}",
"type": "html",
"mode": "merge",
"extract": {
"paperlink": {
"css": ".divTextLink/a",
"value": "@href"
},
"abstract": {
"css": "#abstractSection/p",
"value": ".//text()"
}
}
}

Hi @oncev,
it looks like you have mixed css selector syntax with xpath. Try #abstractSection p and .divTextLink a. http://selectorgadget.com/ is a useful tool to get the right selectors without having to dig into the page source code.

Thanks, bro. I have tried http://selectorgadget.com/ for generating css selector for other websites and it works well. According ot the result of  http://selectorgadget.com/, I modifed the css of the two agents as "#outwardLinks .outwardTextLink" ( for "paperlink" ) and "#abstractSection p" ( for "#abstractSection/p"). But the website agent still shows "Values extracted: []". BTW, the http://fivefilters.org/ can generate full text rss for this rss source but only the last two rss information.

Sorry, I overlooked the notification email.
I think the problem is that the website is doing a series of redirects and also requires cookies to be set. If you open the URL of one of the RSS Feed results in a new incognito window it only shows a login page: https://www.scopus.com/record/display.uri?eid=2-s2.0-84929521433&origin=inward&txGid=1f29991cf2f4aa98011c003d2bb78506

Never mind. It seems that Huginn can not generate full text rss for this type of website:-(

If the website does not require JavaScript to work it should be possible, but working with cookies it not very straight forward. This issue has a few examples how it could work: https://github.com/huginn/huginn/issues/1497


Fix NullPointerException in CompositionRepository.mapWithout and Comp…

…ositionRepository.mapWithAlso

Let me check, I'll give you an update very soon. Thanks a lot!


Weird CPU support

not a bug but a question. i have a motherboard ROG strix x299-E, a i7-7740x cpu and rtx 3070 FE. My gpu and motherboard support resizable bar tho according to intel, it seems that my cpu isn't supported. However, when I enable resizable bar in my bios, nvidia control panel and GPU-z reports resizable bar as enabled. So is cpu support really is needed or not? and if cpu supported is needed, do i need to use the ReBarUEFI too to fix it?

Any CPU from ~2010 should be able to support rebar even if it's PCIe 2.0. I'm unsure about earlier stuff because no one has tried it.

So I dont need to use ReBarUEFI?

@GiulianoB-1 if you're motherboard has rebar option in BIOS no, because you can use that instead


Citations

Draft for devs to start getting familiarity with work and even reviewing model/database code.

METRIC
VALUE

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4041

@hyi @sblack-usu Reviewers, Jeff got a clarification with PIs and we are going to evaluate Citation eligibility by external reference aggregate, instead of .url file extension. This coincides with an earlier email thread you were on, so things are coming to closure. I'm wrapping up the new endpoint and logic and then need to test extensively and clean up. Should have something in the next couple days that we can do final polishing on and merge.


No way to disable dependabot on public repo

We have disabled dependabot alerts and security updates on our public repo. See the attached screenshot. As pointed out in bug https://github.com/dependabot/dependabot-core/issues/2097, those settings don't actually work.

We have also set open-pull-requests-limit to zero our dependabot.yml file, as documented here: https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#open-pull-requests-limit.
That does not stop dependabot.
We have also set ignore depenency-name to * in the yaml file, as documented at https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#ignore
That does not stop dependabot either.
So how do we keep dependabot out of our repo?

@diamondap you'll want to completely remove that config file, the open-pull-request-limit applies to periodic version updates only, it does not set a limit for security updates.
 Because it looks like its config file is configured to allow for 10 version updates.
Lmk if removing the config file resolves the issue though.

Well that may be the problem. I didn't know that other config file existed. I will delete the config file I pointed to and will adjust the settings in .github/dependabot.yml. Thanks for your help. I'll get back to you and let you know if that works.

Ah, yeah it needs to be in that exact location or dependabot cannot pick up the config file. It looks good now though so I think this should resolve it 🤞

OK, it looks like this worked. Thanks for the help.


Error loading en language

🧐 Have you read the FAQ and viewed similar issues?

[X] I have read the FAQ
[X] I have checked older issues, open and closed
[X] I did a clean install of SpotX as described in the FAQ

Сountry of your account
Canada
What is your Spotify Plan?
Free
Do you have Spicetify installed?
No
ℹ Computer information
- Spotify: <IP_ADDRESS>4.g42cf0a50
- Windows: Edition	Windows 11 Home
Version	22H2
Installed on	2023-04-11
OS build	22621.2283
Experience	Windows Feature Experience Pack 1000.22662.1000.0

- PowerShell: 5.1.22621.1778

📝 Description
(I closed my previous issue, thinking that issue #287's response would help me. However, it didn't so that's why I'm putting this issue back up again)

I downloaded the latest zip of spot x and extracted it using  7 zip and then if I open either bat file (install_new_theme.bat or install_old_theme.bat) it gives me this error. i did do a clean install of spotify too.
i did trying using a VPN because it was a solution for issue 287 but i don't know how to do "change DNS from ISP default"
i think mine is slightly different from issue 287 because i have this red text but it doesn't show for them

📸 Screenshots

also yes the vpn didnt help

Open the Powershell console and enter the following command:

$ExecutionContext.SessionState.LanguageMode

send response

ConstrainedLanguage

enter the commands into the console one by one and show their response:
[Net.ServicePointManager]::SecurityProtocol = 3072

[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor [System.Net.SecurityProtocolType]::Tls12

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

ok, then try this first
Set-ExecutionPolicy RemoteSigned -Force

then this again

I did and then still didn't do anything

try this
$ExecutionContext.SessionState.LanguageMode = "FullLanguage"

and this
[Net.ServicePointManager]::SecurityProtocol = 3072

Both didn't do anything

(Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Environment')

Its ok I have fixed this issue. For anyone in the future wondering how to do this, you search "View advanced system settings" in the search bar. Click environment variables on the bottom right. There should be user variables and system variables. There should be a variable called "__PSLockdownPolicy". You should change the value to 8.  If you don't see the __PSLockdownPolicy variable, you should make it yourself by clicking New (under system variables of course don't do it under user variables I don't know if it makes a difference. Name it __PSLockdownPolicy and set the value to 8 and click ok and then ok again to save changes. Basically what the error is it can't load the en language because the powershell is set to Constrained Language.  Changing the variable of PSLockdownPolicy will make it so your powershell is full language and it will fix your error. Hope this helps. More information here: https://cyberark.my.site.com/s/article/language-mode-error

Thanks for helping me


[Bug]: response from deployer is invalid.

What happened?
Attempting to use commands such as cargo shuttle deployment list, or cargo shuttle status leads to 502 Bad Gateway Error. And asks you to submit a ticket.
I did find a similar issue, specifically #328 but it appears to be from 2022.
Version
v0.17.0
Which operating systems are you seeing the problem on?
Linux
Which CPU architectures are you seeing the problem on?
x86_64
Relevant log output
Error: 502 Bad Gateway
message: response from deployer is invalid. Please create a ticket to report this

Duplicate declaration

[X] I have searched the issues and there are none like this.

Same here

From Discord:

chesedo: Our gateway is currently having issues. We are working on fixing it and will have an update soon

From discord:

chesedo: Our infra is fixed. There should be no more "502 Bad Gateway" errors


create playbook for pulsar-qld-gpu-dev

Does this need a separate playbook?

I didn't think so originally, but saw other dev playbooks and noted they included group_vars/dev.yml and don't call the slg.galaxy_stats role. So thought it might be needed. Which probably also means I should change the DNS domain of pulsar-qld-gpu-dev to be .gvl.org.au

As per @cat-bro's comment. This playbook is not required - can directly use the pulsar-qld-gpu playbook.


Creating gateway with portforward, result target port same as source port in container info

data={'hostname': 'b54e7f898708eeb7428a08', 'networks': [{'name': 'nat0', 'type': 'default', 'public': True, 'id': ''}, {'name': 'zerotier_nic', 'type': 'zerotier', 'id': '1d719394048f3525', 'ztClient': 'c3477dac9423a9cb64e8cb', 'public': False}], 'portforwards': [{'protocols': ['tcp'], 'srcport': 3568, 'srcnetwork': 'nat0', 'dstip': '<IP_ADDRESS>', 'dstport': 2801, 'name': 'myport'}, {'protocols': ['tcp'], 'srcport': 6000, 'srcnetwork': 'nat0', 'dstip': '<IP_ADDRESS>', 'dstport': 5000, 'name': 'portt'}], 'httpproxies': [], 'domain': '', 'certificates': [], 'routes': [], 'ztIdentity': ''}

steps:
1- create gateway with this data using (template: github.com/threefoldtech/0-templates/gateway/0.0.1)
2- get gateway's container info
Actual Result
The target port is same as source port in container info
port forward from public network to private one (did it twice on these ports 6000, 3568 to make sure)

Clearing a miss-understanding on the gateway port-forwards

with ZOS port forward you can NOT specify a destination address, it's always the VM or Container private address (default network)
Gateway does a trick by first forward the required ports to the gateway internal ports (same as source port), then internally it maintain it's own firewall rules to re forward those ports to the required destination ip:port

So from what I see, this looks correct. To validate, run nft list ruleset inside the container to check that those ports are reforwarded to the requested destination.
@grimpy  please confirm

Yes, I found the rule inside the container.

and this rule in the node

and I had a server running on<IP_ADDRESS>:2856
so I was expecting to reach the server through<IP_ADDRESS>:3176, but this didn't happen


Deploy Core, Management, Connectivity, Identity Resources to different TFC workspace (TF state files)

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
Is your feature request related to a problem?
Currently, if I switch the Management and Connectivity modules on, all resources will deploy to a single TFC workspace / TF state file.  If I add more custom landing zones, the single TF state file grows bigger and bigger. This makes the state file hard to maintain and easy for broken.
Describe the solution you'd like
Can we define TF remote backend per module? So that I have different TFC workspaces (TF state files) for the four modules and the landing zones.

Additional context

Thank you for this question @lintaonz.
The basic design principle of the module allows you to sub-divide your implementation in exactly the way you are asking, allowing deployment of the following groups of resources to be deployed across multiple TFC workspaces (TF state files):

Core resources (Management Groups with associated policies and IAM)
Connectivity resources
Management resources

These can even be sub-divided into multiple instances of the above, but as you might expect, this further increases complexity with diminishing benefit.
We actually do this partially within the test framework modules, so the basic code structure you need to achieve this is partially available there. There is also documentation in our Wiki explaining how to split your core resources across multiple module declarations using module nesting but we should probably add explicit guidance covering this scenario in full.
To get you started, if you look at the test framework modules you will notice that we abstracted all of the configuration settings into a dedicated settings module, and moved the custom lib folder up a level too. This allows the same inputs to be cross-referenced by each of the root modules used for resource deployments. This ensures each test module has consistent settings, and the same principle can be applied to your scenario.
The test 003 module is probably most similar to what you're looking for. If you look at the structure within main.tf, you will see we have multiple declarations of the module being called to deploy the following:

test_core to build the base Management Group hierarchy
test_nested_core to extend the Management Group hierarchy
test_management to add the Management resources
test_connectivity to add the Connectivity resources

As long as you do the following across each module declaration, you should be able to take each of these module declarations and move them into different root modules, allowing you to achieve your desired outcome:

Use consistent values for providers = {} across all
Use consistent values for configure_*****_resources input variables across all
Use consistent values for subscription_id_***** input variables across all
Toggle which resources are deployed using the deploy_***** input variables on each

If you look at how we did this using the settings module, you should be able to replicate this in a way which works across your multiple root modules.
TFC may make this a little trickier due to the way it works with initiating a root module. In my testing, TFC won't have access to folders which aren't directly under the root module path. You may get the following error (or similar):
╷
│ Error: Unreadable module directory
│
│ Unable to evaluate directory symlink: lstat ../alz_settings: no such file
│ or directory
╵

I don't have a specific solution to this, but I suspect there are multiple options using something like symlinks or git submodules to ensure the "external" folders are available within TFC, or you can simply store these values in TFC using Variable sets which can be mapped to each workspace. The approach you settle on will depend on what's supported by TFC, and what your requirements are around having configuration settings stored in Version Control, vs. TFC.
Hope this helps, but please let me know if you require further guidance on this.

Hi @krowlandson,
Thank you for your great answer. I think I can figure it out based on the test 003 module.
For the TFC error, I can use Terraform Working Directory to solve it.
Yes, it would be great if you can add an example in the wiki in the future.