Introduce broadcast API for event sharing

What this PR does / why we need it?
This PR implements a broadcast API, which enables the sharing of a broader range of general events beyond the current document and presence events in Yorkie's Publish-Subscribe model.
Any background context you want to provide?
1. Broadcast Events:
Users can now broadcast custom events with a specified topic and payload.
The payload can be of any type, as long as it is serializable.
// Broadcast an event with a topic and payload
const payload = 'hello';
client.broadcast(doc, 'TOPIC_NAME', payload);

2. Subscribe to Broadcast Events:
Users can subscribe to specific topics and handle the events via a callback function.
The callback is triggered whenever an event with the corresponding topic is broadcast.
// Subscribe to a specific topic for broadcast events
doc.subscribeBroadcastEvent('TOPIC_NAME', (topic, payload) => {
    // Handle the broadcast event for the specified topic
});

What are the relevant tickets?

Related to https://github.com/yorkie-team/yorkie/issues/628
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Introduced a broadcast method in the Client class to send messages to specified topics.
Added a new event type Broadcast to enable clients to subscribe to broadcast messages.
Implemented a utility function to validate the serializability of payloads for broadcasting.
Added a subscribeBroadcastEvent method to allow clients to register handlers for broadcast events.

Bug Fixes

Enhanced error handling for broadcasting unserializable payloads within the Client class.

Tests

Added test cases to verify both successful broadcasting of serializable payloads and error handling for invalid payloads.

@sejongk
There are a few things I'd like to share:
1. How Handlers for Each Topic Are Managed:
Inside the Document class, I've added a broadcastEventHandlers which is a map to manage the handlers for each topic.
// document.ts
export class Document<T, P extends Indexable = Indexable> {
  // skipped

  private broadcastEventHandlers: Map<
    string,
    (topic: string, payload: any) => void
  >;
}

When a user subscribes to a specific topic for broadcast events:
// User subscribes to a broadcast event with the topic "TOPIC_NAME"
doc.subscribeBroadcastEvent('TOPIC_NAME', (topic, payload) => {
    // Handle the broadcast event for the specified topic
});

The handler is registered in the broadcastEventHandlers map:
export class Document<T, P extends Indexable = Indexable> {

  public subscribeBroadcastEvent(
    topic: string,
    handler: (topic: string, payload: any) => void,
    error?: ErrorFn,
  ): Unsubscribe {

    // Register the handler in broadcastEventHandlers
    this.broadcastEventHandlers.set(topic, handler);

2. How PbDocEventType is Converted to DocEventType:
Within the applyWatchStream method of the Document class, which applies the given watch stream response to the document, the conversion from PbDocEventType to DocEventType occurs as follows:
  public applyWatchStream(resp: WatchDocumentResponse) {
      // skipped
      } else if (type === PbDocEventType.DOCUMENT_BROADCAST) {
        if (resp.body.value.body) {
          const { topic, payload } = resp.body.value.body;
          const decoder = new TextDecoder();

          event.push({
            type: DocEventType.Broadcast,
            value: { topic, payload: JSON.parse(decoder.decode(payload)) },
          });
        }
      }

      if (event.length > 0) {
        this.publish(event);
      }
    }
  }

3. Test Case for Sending Unserializable Payloads:
As discussed earlier, I've added a test case in client_test.ts to handle unserializable payloads. If there are any additional test cases needed, please let me know.
Lastly, I've verified that the broadcast API works as expected in several examples, but I believe further testing is necessary to ensure complete coverage.

@gwbaik9717
CI failed due to incorrect pnpm version in CI configuration. It is currently fixed in the main branch.

@sejongk
Here is an update.
1. Unified Broadcast Event Subscription
Users can now use the existing subscribe method to subscribe to broadcast events. Since subscribing to a broadcast event requires both a type and a topic, I've introduced a new SubscribePair type, which is structured as follows:
type SubscribePair = {
  type: string;
};

Building on this, the BroadcastSubscribePair extends SubscribePair:
type BroadcastSubscribePair = {
  type: 'broadcast';
  topic: string;
} & SubscribePair;

Here’s an example of how to subscribe to a broadcast event:
   const unsubscribe = d2.subscribe(
        { type: 'broadcast', topic: "TOPIC_NAME" },
        (topic, payload) => {},
   );

2. Call broadcast from Document not Client
Broadcasting is now handled directly by the Document not Client, aligning with the subscription mechanism.
To support this, I’ve added a client attribute within the Document class. This client attribute is an instance of the Client and is set when the client attaches to the document, and unset when it detaches.
export class Document<T, P extends Indexable = Indexable> {
  // skipped
  private client?: Client;

    /**
   * `setClient` sets the client of this document.
   *
   * @internal
   */
  public setClient(client?: Client): void {
    this.client = client;
  }

}

Here’s an example of how to broadcast a topic with payload.
// must be serializable
const payload = {a:1, b:"2"}
await doc.broadcast("TOPIC_NAME", payload);

@sejongk
Sorry for the late review. I'll check it today.
CC) @chacha912, @gwbaik9717

@hackerwins, I've reviewed, but could you please check it once more in case I missed anything? (Please check the comments I've left with cc regarding the subscribe interface and client property)

@hackerwins @chacha912 @sejongk
Here's an update.
In order to resolve the circular reference issue, we’ve removed the client reference from the Document class.  Instead, we've decided to have Client subscribe to Document's broadcast events and handle them by calling Client's broadcast method.
However, this solution presents two challenges:
1. Unsubscribing Handlers
We had to ensure that handlers registered in subscribe are properly unsubscribed when document is detached from client.
To address this, we’ve decided to manage unsubscribeBroadcastEvent within the Attachment class, since the lifecycle of the client’s attachment and the sub/unsub process are the same.
export class Attachment<T, P extends Indexable> {
  // skipped
  unsubscribeBroadcastEvent: Unsubscribe;
}

With this approach, when attaching a document to a client using the attach method of Client, we subscribe to the document’s event stream, and we unsubscribe when detaching:
  public attach<T, P extends Indexable>(
    doc: Document<T, P>,
    options: {
      initialPresence?: P;
      syncMode?: SyncMode;
    } = {},
  ): Promise<Document<T, P>> {
    // skipped
    const unsubscribeBroacastEvent = doc.subscribe(
      'broadcast',
      (topic, payload, onBroadcastError) => {
        try {
          this.broadcast(doc.getKey(), topic, payload);
        } catch (e: unknown) {
          if (e instanceof Error) {
            onBroadcastError?.(e);
          }
        }
      },
    );

    this.attachmentMap.set(
          doc.getKey(),
          new Attachment(
            this.reconnectStreamDelay,
            doc,
            res.documentId,
            syncMode,
            unsubscribeBroacastEvent,
         ),
    );

  private detachInternal(docKey: DocumentKey) {
    // skipped
    attachment.unsubscribeBroadcastEvent();

2. Error Handling for Broadcast Events
The second challenge involves handling errors during broadcast events, such as when broadcasting an unserializable payload. Initially, we could simply use a try-catch block to handle errors when directly accessing the client's broadcast method:
try {
   doc.broadcast(broadcastTopic, payload)
}catch(e){
 // do something
}

However, since we’re now dealing with an event stream, a different approach to error handling is required. To accommodate this, I've introduced a new interface for broadcasting events. This interface includes an error handling function that triggers when a broadcast event fails.
// Usage
const errorFn = () => {
    // Do something
}
doc.broadcast("topic", payload, errorFn)

Here's an update.
As mentioned earlier, we've decided to have the Client subscribe to the Document's broadcast events and handle them by invoking the Client's broadcast method. The challenge I encountered was distinguishing between local and remote broadcast events. Since the client is now subscribed to the document's broadcast events, both local and remote events are received, which creates the following issue:

Without differentiation, this setup can lead to an unexpected infinite loop. This happens because the client, upon receiving its own broadcast event, will rebroadcast it, creating a never-ending cycle.

This scenario can be reproduced with the following test code. The test simulates a situation where the publisher is broadcasting an event and, at the same time, subscribing to the broadcast event. Currently, since Yorkie does not support self-broadcast filtering, the subscribe handler gets called, leading to numerous recursive broadcasts, as evidenced by the test results:
 it('Should not trigger the handler for a broadcast event sent by the publisher to itself', async ({
    task,
  }) => {
    await withTwoClientsAndDocuments<{ t: Text }>(
      async (c1, d1, c2, d2) => {
        const eventCollector1 = new EventCollector<[string, any]>();
        const eventCollector2 = new EventCollector<[string, any]>();
        const broadcastTopic = 'test';
        const payload = { a: 1, b: '2' };

        // Publisher subscribes to the broadcast event
        const unsubscribe1 = d1.subscribe('broadcast', (topic, payload) => {
          if (topic === broadcastTopic) {
            eventCollector1.add([topic, payload]);
          }
        });

        const unsubscribe2 = d2.subscribe('broadcast', (topic, payload) => {
          if (topic === broadcastTopic) {
            eventCollector2.add([topic, payload]);
          }
        });

        d1.broadcast(broadcastTopic, payload);

        // Assuming that subscribers can receive the broadcast event within 1000ms.
        await new Promise((res) => setTimeout(res, 1000));

        unsubscribe1();
        unsubscribe2();

        assert.equal(eventCollector1.getLength(), 0);
        assert.equal(eventCollector2.getLength(), 1);
      },
      task.name,
      SyncMode.Realtime,
    );
  });

To resolve this issue, I've introduced a LocalBroadcast event type in addition to the existing Broadcast event. The LocalBroadcast event is only triggered when the local document attempts to broadcast. This addition allows us to clearly distinguish between local and remote broadcast events, preventing the infinite loop scenario by ensuring that a client does not handle its own broadcast events.

export enum DocEventType {
  /**
   * `Broadcast` means that the broadcast event is received from the remote client.
   */
  Broadcast = 'broadcast',

  /**
   * `LocalBroadcast` means that the broadcast event is sent from the local client.
   */
  LocalBroadcast = 'local-broadcast',
}

 /**
   * `broadcast` the payload to the given topic.
   */
  public broadcast(topic: string, payload: any, error?: ErrorFn) {
    const broadcastEvent: LocalBroadcastEvent = {
      type: DocEventType.LocalBroadcast,
      value: { topic, payload },
      error,
    };

    this.publish([broadcastEvent]);
  }


chore: gracefully handle tree view sort error to avoid crashing the tree view

chore: gracefully handle tree view sort error to avoid crashing the tree view
This PR:

Preemptively filters out note ids that will cause the sort logic to fatally crash the tree view rendering (note ids not in sync with noteDict)

tree view will omit the out-of-sync note ids from rendering.

Properly log when this happens so we can troubleshoot the root cause with the surrounding context available.

NOTE: the links don't work. you'll need to go into the wiki and use lookup to find the note until we fix some issues in the markdown export

Code
Basics

[x] code should follow Code Conventions
[x] circular dependency check: make sure your code is not introducing new circular dependencies in plugin-core.  See Avoiding Circular Dependencies.
[x] sticking to existing conventions instead of creating new ones

eg: if configuration for utilities are already in one module or package, add future utilities there as well

Extended

General

[x] check whether code be simplified
[x] check if similar function already exist in the codebase. if so, can it be re-used?
[x] check if this change adversely impact performance

Operations

[x] when shipping this change, will it just work or will it introduce additional operational overhead due to complicated interface or known bugs?

Architecture

[x] check if code is introducing changes on a foundational class or interface. if so, call for design review if needed

eg: making changes to DNode

Instrumentation
Basics

[~] if you are adding analytics related changes, make sure the Telemetry docs are updated

Extended

[~] can we track the performance of this change to know if it is successful?

eg: see usage for export pod

Tests
Basics

[~] Write Tests
[ ] Confirm existing tests pass
[ ] Confirm manual testing
[ ] Common cases tested
[ ] 1-2 Edge cases tested
[ ] If your tests changes an existing snapshot, snapshots have been updated

Extended

[~] If you are adding a new language feature (graphically visible in VS Code/preview/publishing), an example is included in the test workspace
CSS

[~] display is correct for following dimensions

[~] sm: screen ≥ 576px, eg. iphonex, (375x812)
[~] lg: screen ≥ 992px
[~] xxl: screen ≥ 1600px eg. mac (1600x900)

[~] display is correct for following browsers (across the various dimensions)

[~] safari
[~] firefox
[~] chrome

Docs

[~] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR
[~] does this change introduce a new or better way of doing things that others need to be aware of? if so, an async should be created and a process added in Development or Packages

Close the Loop
Extended

[~]  is this a developer BREAKING change? if another person cloning from this branch will need to adjust their dependencies or mental model of the architecture, then it is. if this is the case, make sure this is communicated according to Close Loop

eg: breaking dev change due to new dependency

related: https://github.com/dendronhq/dendron/issues/2786, https://github.com/dendronhq/dendron/issues/2451

Does the tree view render reliably after this change? (reliably here meaning not-empty 😄 )
We can give it some runs in nightly

Let me try to force this to test it out 😄 pretty hard to manually test.

Since this sorta silences the issue, I added an explicit call to action to reload vscode when it happens.
So far we have identified that this only happens during workspace sync, but there may be more cases where this could happen.
The call to action will be sending up events that could help us determine the surface area of this issue.


Negative numbers are not supported by the parser

Discord username
No response
What type of issue is this?
Permanent – Ocurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
During the demo we spotted that input -2 is considered a unary application of the - operator, not the negative number, as it should be.
-2 produces:
Ast: Ast { wrapped: WithID { wrapped: WithLength { wrapped: Module(Module { lines: [BlockLine { elem: Some(Ast { wrapped: WithID { wrapped: WithLength { wrapped: SectionRight(SectionRight { opr: Ast { wrapped: WithID { wrapped: WithLength { wrapped: Opr(Opr { name: "-", right_assoc: false }), length: 1 }, id: Some(4169b315-60db-42f9-9a35-1078b3b0776d) } }, off: 0, arg: Ast { wrapped: WithID { wrapped: WithLength { wrapped: Number(Number { base: None, int: "2" }), length: 1 }, id: Some(6e2f3c62-b71f-4f7b-baf0-0af31214237e) } } }), length: 2 }, id: Some(854895b7-8836-4268-91eb-40e701b04b8b) } }), off: 0 }] }), length: 2 }, id: None } }

- 2 produces similar AST:
Ast: Ast { wrapped: WithID { wrapped: WithLength { wrapped: Module(Module { lines: [BlockLine { elem: Some(Ast { wrapped: WithID { wrapped: WithLength { wrapped: SectionRight(SectionRight { opr: Ast { wrapped: WithID { wrapped: WithLength { wrapped: Opr(Opr { name: "-", right_assoc: false }), length: 1 }, id: Some(a2144ab8-d4f7-46ba-8c46-a42753800527) } }, off: 1, arg: Ast { wrapped: WithID { wrapped: WithLength { wrapped: Number(Number { base: None, int: "2" }), length: 1 }, id: Some(547c287d-f1cf-436d-9daa-ea8af4f6c664) } } }), length: 3 }, id: Some(e1fe25f3-5887-47e7-a9f2-091456c5cc68) } }), off: 0 }] }), length: 3 }, id: None } }

Expected behaviour
-2 is a negative number, not a function.
How we can reproduce it?
#[test]
fn negative_number() {
    let parser = Parser::new();
    let input = "-2";
    let ast = parser.parse(input, default());
    eprintln!("Ast: {ast:?}");
    panic!()
}

Screenshots or screencasts
No response
Enso Version
current develop (2d29456)
Browser or standalone distribution
Other (provide the browser name in the next field, please)
Browser Version or standalone distribution
none
Operating System
MacOS
Operating System Version
No response
Hardware you are using
No response

Oh, I see what's happening. The parser itself is per spec (and covered by tests), this is a bug in lowering to the frontend Ast representation.


Upload chunks now supports content string. Fixed bug with celluloid require.

Contact us if you have any questions!

Made your requested changes with ChunkHelper module. Also fixed a bug that I found with checking if string is path.

Is this ready for a merge?

I think it should be ready. We are currently using it in production.


Update getting-started-with-group-managed-service-accounts.md

Updated examples to using samaccountname versus simply the ADObject name string. Inputing a string in this field if not located in the default AD containers will fail without using the samaccountname, DN, or ObjectGUID.

These lines are PowerShell cmdlets, right? Would you mind improving the document by adding the syntax name PowerShell to the preceding line of back ticks for each cmdlet line you have edited?
For cosmetic purposes, it would also be nice if you could remove the surplus blank lines below many of the cmdlets.
(if you prefer, I can add the suggestions directly in this PR content, but I thought it would be better if you are able to make all the changes in 1 extra commit by yourself, instead of getting 1 commit for each change if I add suggestions for all the changes.)

@illfated Good call. Updated.

This topic is not my field of expertise, so I don't have any working experience with it. Even so, the http notation (http/ITFarm1.contoso.com/contoso.com, http/ITFarm1.contoso.com/contoso, http/ITFarm1/contoso.com, http/ITFarm1/contoso) looks a bit odd to me, but I presume there would have been complaints about incorrect command parameters from other users way before this, had they been incorrect in this format and usage.


Bump minimist to ~1.2.3

Bump minimist to ~1.2.3 for prototype pollution. npm audit will provide more details.

Actually it would be better to bump it to 0.2.1 (it's also fixed) to have better backward compatibility

I don't think there's any chance this thing will be fixed, this package has pull requests that have been sitting here for 5 years.

Please merge it !!!


I got many errors when install. What should i do?

Hi everyone,
I'm running CentOS 7 and install node.js with the latest stable version as following.
I'm using root account too.
[root@ip-10-0-7-69 ~]# npm -v
3.7.3
[root@ip-10-0-7-69 ~]# node -v
v5.9.0
Then, i install hubot but got so many errors.
[root@ip-10-0-7-69 ~]# npm install -g hubot coffee-script yo generator-hubot
npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-select'
npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-what'
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
/root/.nvm/versions/node/v5.9.0/bin/coffee -> /root/.nvm/versions/node/v5.9.0/lib/node_modules/coffee-script/bin/coffee
/root/.nvm/versions/node/v5.9.0/bin/cake -> /root/.nvm/versions/node/v5.9.0/lib/node_modules/coffee-script/bin/cake
/root/.nvm/versions/node/v5.9.0/bin/hubot -> /root/.nvm/versions/node/v5.9.0/lib/node_modules/hubot/bin/hubot
/root/.nvm/versions/node/v5.9.0/bin/yo -> /root/.nvm/versions/node/v5.9.0/lib/node_modules/yo/lib/cli.js

<EMAIL_ADDRESS>postinstall /root/.nvm/versions/node/v5.9.0/lib/node_modules/yo
yodoctor

sh: yodoctor: command not found
/root/.nvm/versions/node/v5.9.0/lib
tqq<EMAIL_ADDRESS>tqq<EMAIL_ADDRESS>tqq<EMAIL_ADDRESS>mqq UNMET PEER DEPENDENCY<EMAIL_ADDRESS>npm ERR! Linux 3.10.0-327.10.1.el7.x86_64
npm ERR! argv "/root/.nvm/versions/node/v5.9.0/bin/node" "/root/.nvm/versions/node/v5.9.0/bin/npm" "install" "-g" "hubot" "coffee-script" "yo" "generator-hubot"
npm ERR! node v5.9.0
npm ERR! npm  v3.7.3
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>postinstall: yodoctor
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'yodoctor'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the yo package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     yodoctor
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs yo
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls yo
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /root/npm-debug.log
Could someone help me please?

more or less the same here:
npm install -g coffee-script yo generator-hubot

npm WARN deprecated<EMAIL_ADDRESS>Use @slack/client instead, this package is no longer maintained
`--<EMAIL_ADDRESS>npm ERR! fetch failed https://registry.npmjs.org/inquirer/-/inquirer-0.7.3.tgz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 400
npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-select'
npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-what'
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm

Fixed in https://github.com/slackhq/hubot-slack/pull/309


OPT Changed links to HTTPS.

Codecov Report

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

@@          Coverage Diff          @@
##           master    #13   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      1    -1
  Lines          79     77    -2
=====================================
- Hits           79     77    -2

Impacted Files
Coverage Δ

pkgsettings/__init__.py

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 f02905f...f20c7cb. Read the comment docs.


Column Names vs Graph API

Hello,
in the table on this page the columns are named "String ID" and "GUID".
However when fetching licenses via Graph "get-mgsubscribedSku" the properties are called "SkuPartNumber" and "SkuId".
Could this be adapted, so the same terms are used everywhere?

@joergrenn
It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!

Hello @AjayBathini-MSFT
the question is what is the "correct" Name for these properties?
On that it depends if the documentation needs to be updated or the graph api response.
You can get the licenses via Powershell using the example listed on this MS Learn Page.

@joergrenn
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.


CB-19019 sync added to terminate flows to not miss changes of instances

See detailed description in the commit message.

TODO: ignore sync failure, if deletion fails, next delete will execute sync anyway

retest this please


Add new Animated API to animation docs.

We should wait to merge this until the new API is available.
Let me know if you have any feedback, either on the docs themselves or the actual API :)

This is amazing - :clap: :clap: for @sahrens

Awesome work @sahrens. This commit removes LayoutAnimation docs - is it now deprecated?

@paramaggarwal - still there, just re-arranged slightly: https://facebook.github.io/react-native/docs/animations.html#layoutanimation

@brentvatne Ya, I noticed later and edited my comment. Thanks!


clap is incompatible with vim-signature

Environment (please complete the following information):

OS: Windows 10 64 bit
(Neo)Vim version:

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Mar 24 2022 23:02:44)
MS-Windows 64-bit GUI version with OLE support
Included patches: 1-4621

vim-clap version: SHA-1: 6fd4fecaf8b1da31c625e5f02822778d4a2a08b5
Have you reproduced with a minimal vimrc: no
Have you updated to the latest plugin version: yes

Describe the bug
vim-signature's key map will be triggered at clap's input popup, and the content of key map codes will be insert.
To Reproduce
Steps to reproduce the behavior:
1,start clap source panel
2,enter history panel and press the key m as quickly as possible
3,the content of key map code will be input automatically
Expected behavior
nothing be input automatically
Screenshots
.

Could you please also provide a minimal vimrc to help reproduce it?

"Start (neo)vim with command: `vim -u min.vim`

set pyx=3
set langmenu=none
let $LANG = 'en'
syntax on
set nocompatible              " be iMproved, required
filetype off                  " required

let $VIM_DIR = 'D:/programs/vim'
call plug#begin('$VIM_DIR/vimfiles/plugged')
filetype plugin indent on
" =================================================================
Plug 'kshenoy/vim-signature'
let g:SignatureMap={}
let g:SignatureMap['GotoNextLineAlpha']=''
let g:SignatureMap['GotoPrevLineAlpha']=''
let g:SignatureMap['GotoNextSpotAlpha']=''
let g:SignatureMap['GotoPrevSpotAlpha']=''

Plug 'liuchengxu/vim-clap', {'on': ['Clap!','Clap']}
let g:clap_disable_run_rooter = v:true
nmap <C-p>   :Clap!<CR>
nnoremap <A-p> :<C-U><C-R>=printf('Clap grep +no-cache ' . '++query='
            \ . expand('<cword>'))<CR>
vnoremap <A-p> :<C-U><C-R>=printf('Clap grep +no-cache ' . '++query='
            \  . escape(misc#get_visual_selection(),'\| '))<CR>

augroup my_clap_augroup
    autocmd!
    autocmd FileType clap_input let b:asyncomplete_enable=0
augroup END

let g:clap_theme = 'material_design_dark'
let g:clap_layout = {'relative': 'editor','width': '90%','height':'40%','row':'20%', 'col': '5%' }
let g:clap_preview_direction = 'UD'
let g:clap_selected_sign = {'text': ' +', 'texthl': 'ClapSelectedSign', 'linehl': 'ClapSelected' }
let g:clap_current_selection_sign = { 'text': '>>', 'texthl': 'ClapCurrentSelectionSign', 'linehl': 'ClapCurrentSelection' }
"=================================================
call plug#end()
filetype plugin indent on    " required

Thank you, it's solved.


Error Deploying to AWS EKS

Hello,
I'm trying to deploy to AWS EKS. I've configured kubectl for my cluster in amazon. I'm getting the following error when running serverless deploy -v
Unable to find required information for authenticating against the cluster
Unable to find required information for authenticating against the cluster
/Users/jamesingold/Repos/juxly/perfcol-serverless/node_modules/serverless-kubeless/lib/config.js:58
return JSON.parse(this.configMag.data[key]);
^
TypeError: Cannot read property 'runtime-images' of undefined
at Config.get (/Users/jamesingold/Repos/juxly/perfcol-serverless/node_modules/serverless-kubeless/lib/config.js:58:44)
at Object.getRuntimeDepfile (/Users/jamesingold/Repos/juxly/perfcol-serverless/node_modules/serverless-kubeless/lib/helpers.js:183:34)
at ReadStream.s.on (/Users/jamesingold/Repos/juxly/perfcol-serverless/node_modules/serverless-kubeless/deploy/kubelessDeploy.js:103:39)
at ReadStream.emit (events.js:187:15)
It looks like there is an authentication issue, even though I'm logged in through kubectl
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "configmaps "kubeless-config" is forbidden: User "system:anonymous" cannot get configmaps in the namespace "kubeless"",
"reason": "Forbidden",
"details": {
"name": "kubeless-config",
"kind": "configmaps"
},
"code": 403
}

What was the resolution?

That's no solution.
The problem is likely that the way Kubeless talks to the Kubernetes Master API fails to take into account the custom authentication method required by EKS in ~/.kube/config:
- name: arn:aws:eks:eu-west-1:XXXXX:cluster/CLUSTERNAME
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      args:
      - token
      - -i
      - CLUSTERNAME
      command: aws-iam-authenticator

Please reopen.

Yes @japsu, that was a workaround more than a solution.
At that time the library we are using to work with Kubernetes in this plugin didn't support that new way of authenticating but it seems that it's available now (since this October): https://github.com/godaddy/kubernetes-client/issues/306
I am reopening this issue but we will need help updating the library!

Has anyone been able to look at this? Unsure if the iam-authenticator method needs to be used any longer. In May AWS made the authentication easier by putting it in the Amazon EKS CLI. Not sure if that streamlines the work needed or not.

I am also having this issue. Setting the two required envar's and.
Then I am able to run kubectl commands:
kubectl get pods --namespace kubeless
NAME                                          READY   STATUS    RESTARTS   AGE
kubeless-controller-manager-646876977-qb46g   3/3     Running   0          19h

Howerver, running:
serverless deploy -v
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Unable to find required information for authenticating against the cluster
Unable to find required information for authenticating against the cluster

  Type Error ---------------------------------------------

  TypeError: Cannot read property 'runtime-images' of undefined

@bradleybluebean @andresmgot I still have the same issue even on the last release of serverless (including the merged PR) :
$ sls version
Plugin: 3.6.1
SDK: 2.3.0
Components: 2.22.3
$ npm list serverless-kubeless
<EMAIL_ADDRESS>/.../serverless-kubeless/examples/get-python
└──<EMAIL_ADDRESS>$ k get configmaps kubeless-config -n kubeless
NAME              DATA   AGE
kubeless-config   10     2m7s

$ serverless deploy
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Unable to find required information for authenticating against the cluster
Unable to find required information for authenticating against the cluster

  Error --------------------------------------------------

  Error: Request returned: 403 - configmaps "kubeless-config" is forbidden: User "system:anonymous" cannot get resource "configmaps" in API group "" in the namespace "kubeless"
    Response: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"configmaps \"kubeless-config\" is forbidden: User \"system:anonymous\" cannot get resource \"configmaps\" in API group \"\" in the namespace \"kubeless\"","reason":"Forbidden","details":{"name":"kubeless-config","kind":"configmaps"},"code":403}
  false

hmm I just found out that the change is not included in the version that is installed when you don't specify any version. I don't why but the version that is installed is 0.7.3 ... I installed 0.9.2 and got it working. Should I create an issue about that ?

that depends on the content of the package.json. Probably it's not updated in the example you tried to deploy. You can update the version there and send a PR so the next person that tries it doesn't find the issue :)

what do you mean ? I'm saying npm install serverless-kubeless should install the last version when it installed 0.7.3. So I wonder if it's just that some versions were not deployed to the repo for some reasons

I mean, when doing npm install serverless-kubeless it installs the latest version:
▶ npm install serverless-kubeless
+<EMAIL_ADDRESS>added 108 packages from 164 contributors and audited 192 packages in 7.488s

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

found 0 vulnerabilities

The problem is when you do npm install in a project that has an old version. I assume that this example<EMAIL_ADDRESS>/.../serverless-kubeless/examples/get-python) has an old version of serverless-kubeless in its package.json. That's why you are seeing that version.

@andresmgot thanks for the answer, it makes sense !


[NT-1355] Lights On header bugfix

📲 What
Fixes a bug causing the project cards to be scrolled behind the Lights On header in the editorial projects collection.
Note: Contains unrelated formatting updates from bin/format.sh . not being run in #1223 😅
🤔 Why
This is a regression introduced where DiscoveryPageViewController's backgroundColor is changed after it's added as a child of EditorialProjectsViewController. We need this to remain clear for the behaviour in the editorial projects list.
🛠 How
When this DiscoveryPageViewController's viewWillAppear is called we pass in a boolean to indicate whether its parent is EditorialProjectsViewController and we don't emit the backgroundColor or contentInset changes in that case as these are configured by the parent VC.
Note: Initially I thought I would just pass the VC's class into the VM for this logic but that would require the VM to be aware of VC classes.
👀 See

Before 🐛
After 🦋

✅ Acceptance criteria

[ ] When viewing the Lights On editorial collection the projects scroll behind the header.

Note this has since been updated to instead provide the background color for discovery from a shared function which is used for the cells and the background of DiscoveryPageViewController.

@jgsamudio good question - we did this for the header originally when we used it for Go Rewardless (#971), but perhaps it doesn't work for this particular image, what do you think, @colleenmacd?

I think the animation doesn't work as well for this image because the image
has a lot of grain/texture on it, which contributes to it looking slightly
pixelated when scaled up. The Go Rewardless image was a PNG graphic
floating on top of a solid background so it worked better. If it's simple
to disable that, I'd vote for that, but if its a larger effort, let me
know— not a big deal to keep it
On Mon, Jun 15, 2020 at 11:49 AM Justin Swart<EMAIL_ADDRESS>wrote:

@jgsamudio https://github.com/jgsamudio good question - we did this for
the header originally when we used it for Go Rewardless (#971
https://github.com/kickstarter/ios-oss/pull/971), but perhaps it
doesn't work for this particular image, what do you think, @colleenmacd
https://github.com/colleenmacd?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kickstarter/ios-oss/pull/1224#issuecomment-644216204,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMOMN4AYIMG527VWHKPXB5LRWY7GXANCNFSM4N34FVGQ
.

--
Colleen MacDonald She/Her
Senior Product Designer, Native Apps
Kickstarter is a Public Benefit Corporation
https://www.kickstarter.com/charter


Mass edit of device site and rack

Environment

Python version: 3.6.8
Nautobot version: v1.1.1

Proposed Functionality
Allow changing site and rack when mass editing devices.

Use Case
We quite often move more devices (example: 20 at once) between sites/racks and doing these changes one-by-one is tedious. Having the ability to just select them all and do this change in UI at once would be very helpful since people doing these migrations are not really capable of using API at all.

Database Changes
None

External Dependencies
None

Can assign to myself and Josh S

what's your timing on this?  If it is in the next 2-3 weeks, it'll make 1.2, otherwise, 1.3.  Can you let us know? :)

@jedelman8 today. I have the PR in. I may just need to do a small working session on the tests.


Add linting infrastructure/fixes

The changes look good, but I wonder if eslint and prettier are essentially performing the same function (i.e. linting) and that would yield contrasting results.
What is linted according to prettier might not be acceptable to eslint and viceversa

The changes look good, but I wonder if eslint and prettier are essentially performing the same function (i.e. linting) and that would yield contrasting results.
What is linted according to prettier might not be acceptable to eslint and viceversa

We would need to watch for trouble there, but the reason I put in both is that the React build process runs the linter at build time (which I actually find kind of silly) but it's catching things prettier doesn't, like unused imports. Since prettier is a formatter, it does make sense that it focuses on that and doesn't catch other issues such as unused imports. So for now at least, I think running both is fine.


🎨 Improve wording

The initial wording just looked weird.

@falexwolf do you prefer For instance. Example or is the comma version fine?

Great that you're fixing these! I think they broke because of bulk string replacements at some point.
I'll make detailed comments.


Feature/updatecore

You did it @dinakarmeda!
Thank you for signing the Anthem Opensource Software CLA.


feat: Add organizer detail

Add organizer detail activity, fragment, presenter

Fixes #454

@mejariamol Please review last commit

@mejariamol That can lead to overlap in some cases

@mejariamol They are the only ones available. Perhaps you can point me to the solid ones which are not present


[PE-D][Tester B] App allows users to add in emails without a period symbol in the domain

Description: The AddressBook app allows users to add emails that do not have the period symbol, potentially recording erroneous emails.
Steps to Reproduce:

Open the AddressBook app.

Enter a command to add a new contact with an email without a '.' in the domain.
Example command:
add r/volunteer n/John Doe p/98765432 e/johnd@examplecom a/311, Clementi Ave 2, #02-25 t/friends t/owesMoney h/30

Expected Result:
The app rejects the contact information with an error message.
Actual Result:
The app accepts the contact information.

Labels: type.FeatureFlaw severity.Medium
original: Runus01/ped#6

Add as feature enhancement to do email format checking with external library.

I'm gonna close this. I have a counterexample.
It is possible to have email addresses without periods, in the special case when the NGO has an intranet. This is known as a Single Label Domain (SLD) https://support.microsoft.com/en-us/topic/b5e60cf3-9099-8560-f872-3889e84da646. While SLDs are generally not recommended, it is possible.
Since the application is a single user application, this scenario is possible.
@voldiemort @seah-minlong @Justin-Yeo @zzzlou Close this issue if you guys are agreeable.


functions: Cannot start emulator.

Hi, I'm unable to emulate my functions. It shows following error:
Cannot start emulator. Error: Cannot find module '/usr/local/lib/node_modules/firebase-tools/node_modules/grpc/src/node/extension_binary/grpc_node.node'
Is it a bug or is there any fault in my firebase-tool setup?

Hey @nhathiwala,
I never came accross this in my setup. Maybe try de-installing and re-installing firebase-tools just in case :)

same sh*t here... I uninstalled and reinstalled firebase-tools but nothing happened...
I tried it on Windows 10 built in linux bash.

@tzs007 It seems like there's an issue with gRPC, which is a separate (also Google driven) library. Can you try running
npm install -g grpc

And see if that completes successfully? There may have been an issue installing this module that was lost in other noise when you installed firebase-tools. If there are errors when installing grpc, can you file an issue at https://github.com/grpc/grpc and reference this one?

Closing, please let us know/reopen if you are still having the issue after trying @inlined command.

Hi there,
I try many ways still getting same error
It's show
functions: Cannot start emulator. Error: Cannot find module '/usr/local/lib/node_modules/firebase-tools/node_modules/grpc/src/node/extension_binary/grpc_node.node'
When I try to install it again it was success
but it show installed via remove like this
[grpc] Success: "/usr/local/lib/node_modules/grpc/src/node/extension_binary/node-v48-darwin-x64/grpc_node.node" is installed via remote
When I look in directory
/usr/local/lib/node_modules/firebase-tools/node_modules/grpc/src/node/extension_binary
there is nothing inside as well and and still could not run Functions in local.
My System is: macOS Sierra 10.12.6
Please give me some advice, thank you in advance.


[Enhancement Styling] : New Ui of login and signup page

@itsmohit097 ,
Description
Please provide a brief description of the issue or feature request.
reDesign the login page
user fell like a good and fun type

like this:

@Varsani2520 , I can improve the UI of login page .
can you assign this issue to me.

@Varsani2520 i need a better ui of login and signup page
do u want to work on this issue?

Yes @itsmohit097
If you assigned me i want to work on that

@Varsani2520 please wait a moment. A contributor is currently working on the API integration. Once that is finished, I will assign you.

Ok

@Varsani2520 u can start working on this.
As you can see it is a health related website. The images you use suits the theme.Also add smooth transitions.

Hey @itsmohit097 ,so assigned me

also add the gssoc and level 1 ,2,or 3 labeled


mixed mode assemblies

As far as I know ILMerge does not accept mixed mode assemblies, those containing unmanaged code. I have some assemblies created using C+/CLI and would like to merge them. I am wondering if  extending ILMerge to handle assemblies like this is possible, even if there is only a single mixed mode assembly. I am happy to do the work for this if possible but would require some guidance, at present I am reading ECMA 335 and have downloaded and built ILMerge and am going to step through the existing code. However I don't want to spend too much time if this is simply not doable or would not be merged. If it is possible any pointers to things to read first would be gladly recieved.

Yes, it doesn't know what to do with the C++ generated part of the assembly. I actually don't know if it is possible to add this functionality, but it would be great if you can figure it out. The main thing would be to understand how to modify references that are in the C++ part to metadata that is in the C# part and/or in other input assemblies. I don't know of any pointers to provide, but I'm happy to discuss it with you as you move forward.


Lametric component sound problem and cycles feature request

Home Assistant release (hass --version):
0.57.3
Python release (python3 --version):
Python 3.5.2
Component/platform:
https://home-assistant.io/components/notify.lametric/
Description of problem:
Notification sound does not work.
Additional info:
Added
sound: notification
to /home/homeassistant/.homeassistant/notify.yaml
- name: lametric1
  platform: lametric
  display_time: 20
  icon: a7956
  sound: notification

and component stops working.
In the code (lametric.py), the sound is added to the list of frames. And the list of frames is added to the model.
I think the sound has to be added to the model.
See:
https://github.com/keans/lmnotify/blob/master/lmnotify/models.py
and
http://lametric-documentation.readthedocs.io/en/latest/reference-docs/device-notifications.html
notify/lametric.py
        frames = [text_frame]

        if sound is not None:
            frames.append(sound)

        _LOGGER.debug(frames)

        model = Model(frames=frames)

If sound is added to the list of frames, component stops working.
It would be nice, if cycles were also implemented. At the moment, the notification is displayed once, also if display_time is set to 20 seconds. If cycle are configurable, the notification could be shown maybe 3 times or 0 for static.

Does the display_time option work? If display time is set to 20 seconds, the notification is shown for 20 seconds?

No. The notification is only displayed once.

So nothing changes if you change the display_time option? Should we remove that option then?

Let me try in milliseconds.

It makes 20000000 in the log, the recalculate works. :D  No, if it is set to 20 seconds in the config, the notification is showed once. It is about 6 seconds.
From lametric site for lifetime:
The time notification lives in queue to be displayed in milliseconds. Default lifetime is 2 minutes. If notification stayed in queue for longer than lifetime milliseconds – it will not be displayed.
It is not the time to display. It defaults to 2 minutes. I think it is useless.

Thanks for this info. I think we should keep it to not make a breaking change, but we should document it properly with the info above.
I'll try to add cycles. Should it be a configuration option or service data option?

For my opinion it should be a configuration option. It lets the user choose the repeats to show a message.

@MartinHjelmare The service call from the dev console works, but if I add the sound to the automation, it does not work.
`2017-11-14 20:25:36 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_call_id=140511511142072-84, domain=notify, service=lametric1, service_data=sound=bicycle, message=Lennart ist unterwegs.>
2017-11-14 20:25:36 DEBUG (MainThread) [homeassistant.components.websocket_api] WS<PHONE_NUMBER>29264: Sending {'id': 2, 'type': 'event', 'event': {'time_fired': datetime.datetime(2017, 11, 14, 19, 25, 36, 424787, tzinfo=), 'event_type': 'state_changed', 'origin': 'LOCAL', 'data': {'new_state': <state device_tracker.lennart_iphone=not_home; longitude=XXXXX, friendly_name=Lennart, battery=100, tid=LE, entity_picture=/local/images/lennart_neu.png, latitude=XXXXX, source_type=gps, gps_accuracy=65 @ 2017-11-14T20:25:36.424747+01:00>, 'entity_id': 'device_tracker.lennart_iphone', 'old_state': <state device_tracker.lennart_iphone=home; longitude=XXXXX, friendly_name=Lennart, battery=100, tid=LE, entity_picture=/local/images/lennart_neu.png, latitude=XXXXX, source_type=gps, gps_accuracy=65 @ 2017-11-14T20:23:05.278210+01:00>}}}
2017-11-14 20:25:36 ERROR (MainThread) [homeassistant.core] Invalid service data for notify.lametric1: extra keys not allowed @ data['sound']. Got 'bicycle'

@MartinHjelmare Automation rule is the right place, isn't it?
I think, the best way would be, to make the definition of the sound in the config (notify.yaml or configuration.yaml)). One sound for all messages to lametric. Otherwise you have to add the sound to every notification and in my opinion there is no need to make different sounds for notifications on lametric from HA.

I think we should keep the sound in the service call. That is the most flexible.
Can you post your automation? I think you're missing the data key in the service data. It's easier to test service calls in the developer tools service tab in the frontend. There you write json instead of yaml though.

This is my automation rule:

alias: 'Sende Nachricht beim Verlassen des Zuhauses von Lennart'
trigger:
platform: state
entity_id: device_tracker.lennart_iphone
from: 'home'
to: 'not_home'
action:
service: notify.lametric1
data:
message: 'Lennart ist unterwegs.'
sound: 'bicycle'

Try this:
- alias: 'Sende Nachricht beim Verlassen des Zuhauses von Lennart'
  trigger:
    platform: state
    entity_id: device_tracker.lennart_iphone
    from: 'home'
    to: 'not_home'
  action:
    service: notify.lametric1
    data:
      message: 'Lennart ist unterwegs.'
      data:
        sound: 'bicycle'

Failed config on config test.

My fault. With data...data...it works.

No the data key under service data for notify component is made for non standard extra keys, eg sound in this case.
This is documented here:
https://home-assistant.io/components/notify/#service

Ok, then it has to be documented in the lametric component (Extended functionality).

Do we rock on with the cycles change?

Yeah, I'll try do something on the cycles. I'll ping you when I have something.

@MartinHjelmare Made it and created a pull request.
#10656


OSX pip installation error

pip installation in conda 3.7 environment on OSX 10.14 throws...

clang: warning: libstdc++ is deprecated; move to libc++ with a minimum deployment target of OS X 10.9 [-Wdeprecated]
ld: library not found for -lstdc++
clang: error: linker command failed with exit code 1 (use -v to see invocation)
error: command 'g++' failed with exit status 1

@ktavabi
Thanks for reporting!

It should be resolved with<EMAIL_ADDRESS>- https://github.com/frictionlessdata/tabulator-py#v138


Search Comments and Resources does not show full path

Currently when searching on class, method, field, and code Jadx shows the full node path within the Text Search window.  When searching on Resource and Comments Jadx only shows the class / file without the path.  This makes it a bit harder to identify which entry I am looking for and it feels a bit odd that its not the same functionality for all search options.

That is true.  Perhaps another good issue / suggestion would be to make a custom key bindings page so i can see the current bindings and change them if desired.
Obviously, this is a very minor issue that really only helps with polishing Jadx.


compilation error

Following the https://coraza.io/docs/integrations/haproxy/ to build coraza waf with haproxy, but with the latest code and go, the installation error:
# go install github.com/jptosso/coraza-server/cmd/coraza-server@master
# github.com/jptosso/coraza-waf/utils/libinjection
../pkg/mod/github.com/jptosso/coraza-waf@v1.2.0/utils/libinjection/libinjection_cgo.go:21:10: fatal error: libinjection.h: No such file or directory
   21 | #include "libinjection.h"
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
# github.com/jptosso/coraza-waf/utils/regex
../pkg/mod/github.com/jptosso/coraza-waf@v1.2.0/utils/regex/regex_pcre.go:60:10: fatal error: pcre.h: No such file or directory
   60 | #include <pcre.h>
      |          ^~~~~~~~
compilation terminated.

# go version
go version go1.17.5 linux/amd64

Hey @leibaogit, coraza-server is experimental, I will update the codes today  and remove C dependencies.
About your issue with libinjection and PCRE, for PCRE you can install libpcre++-dev and for libinjection see this discussion: https://github.com/jptosso/coraza-waf/discussions/107
Still, I would wait for the update today, I will reply to this ticket once the update is pushed.

With the guidance, I can successfully install the coraza
apt install libpcre++-dev -y

git clone https://github.com/libinjection/libinjection
gcc -std=c99 -Wall -Werror -fpic -c libinjection/src/libinjection_sqli.c -o libinjection/libinjection_sqli.o
gcc -std=c99 -Wall -Werror -fpic -c libinjection/src/libinjection_xss.c -o libinjection/libinjection_xss.o
gcc -std=c99 -Wall -Werror -fpic -c libinjection/src/libinjection_html5.c -o libinjection/libinjection_html5.o
gcc -dynamiclib -shared -o libinjection/libinjection.so libinjection/libinjection_sqli.o libinjection/libinjection_xss.o libinjection/libinjection_html5.o
cp libinjection/*.so /usr/local/lib
cp libinjection/*.o /usr/local/lib
cp libinjection/src/*.h /usr/local/include/
chmod 444 /usr/local/include/libinjection*
ldconfig

# go install github.com/jptosso/coraza-server/cmd/coraza-server@master
#

Good to know ! I will close this issue after CGO mandatory dependencies are removed from coraza-server.

coraza-server updated to Coraza v2, if you need libpcre or libinjection support add the plugins to the main file:
import (
	"flag"
	"sync"

	"github.com/jptosso/coraza-server/config"
	"github.com/jptosso/coraza-server/protocols"
	"github.com/jptosso/coraza-waf/v2"
	"github.com/jptosso/coraza-waf/v2/seclang"
	"github.com/sirupsen/logrus"
      _"github.com/jptosso/coraza-pcre"
      _"github.com/jptosso/coraza-libinjection"
)


Getting error using browserify

I am using vue cli browserify setup. I am getting error.
import errorDisplay from '../components/errorDisplay.vue'; ^ ParseError: 'import' and 'export' may appear only with 'sourceType: module'
My package.json looks like
{   "name": "xxx",   "version": "0.1.0",   "description": "xxx",   "author": "xxx",   "private": true,   "scripts": {     "watchify": "watchify -vd -p browserify-hmr -e src/main.js -o dist/build.js",     "serve": "http-server -o -c 1 -a localhost",     "dev": "npm-run-all --parallel watchify serve",     "build": "cross-env NODE_ENV=production browserify -g envify -p [ vueify/plugins/extract-css -o dist/build.css ] -e src/main.js | uglifyjs -c warnings=false -m > dist/build.js"   },   "browserify": {     "transform": [       [         "babelify",         {           "presets": [             "es2015",             "stage-2"           ]         }       ],       "vueify"     ]   },   "browser": {     "vue": "vue/dist/vue.common.js"   },   "dependencies": {     "lodash": "^4.17.4",     "q": "^1.5.0",     "vue": "^2.0.1",     "vue-formly": "^2.5.0",     "vue-formly-bootstrap": "^2.2.7",     "vue-input-tag": "0.0.16",     "vue-resource": "^1.3.4",     "vue-router": "^2.7.0",     "vue-strap": "github:wffranco/vue-strap",     "vue2-filters": "^0.2.2"   },   "devDependencies": {     "babel-core": "^6.0.0",     "babel-plugin-transform-runtime": "^6.0.0",     "babel-preset-es2015": "^6.0.0",     "babel-preset-stage-2": "^6.0.0",     "babel-runtime": "^6.0.0",     "babelify": "^7.2.0",     "browserify": "^13.1.0",     "browserify-hmr": "^0.3.1",     "cross-env": "^2.0.0",     "envify": "^3.4.1",     "http-server": "^0.9.0",     "npm-run-all": "^2.3.0",     "proxyquireify": "^3.0.1",     "uglify-js": "^2.5.0",     "vueify": "^9.0.0",     "watchify": "^3.4.0"   } }
Not sure why its failing to bundle.

@jaideepdas I'll take a look at the error and get back to you k. Thanks for using Vue Formly!

Sure, thanks for replying.
On 23 Oct 2017 11:45 pm, "matt-sanders"<EMAIL_ADDRESS>wrote:

@jaideepdas https://github.com/jaideepdas I'll take a look at the error
and get back to you k. Thanks for using Vue Formly!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/formly-js/vue-formly-bootstrap/issues/7#issuecomment-338749319,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQtuP6pssQ4md5roYgzfoxYyRE3L-r8ks5svNe3gaJpZM4QCflq
.

@jaideepdas I just tried out the default browserify tempate and it all worked fine. then I switched the package.json file for the one you provided and again it worked fine. Have you tried doing a clean npm install to see if that fixes it? Also how are you running Vue Formly? Are you using:
import VueFormly from 'vue-formly';
import VueFormlyBootstrap from 'vue-formly-bootstrap';
Vue.use(VueFormly);
Vue.use(VueFormlyBootstrap);

or
const VueFormly = require('vue-formly');
const VueFormlyBootstrap = require('vue-formly-bootstrap');
Vue.use(VueFormly);
Vue.use(VueFormlyBootstrap);

I tried both of those and it worked.

I am initiating it like
import VueFormly from 'vue-formly'; import VueFormlyBootstrap from 'vue-formly-bootstrap'; Vue.use(VueFormly); Vue.use(VueFormlyBootstrap);
without the semi colons. Nothing special. How are you running your dev bundler. I am using vuejs cli's
npm run dev

hmm yea, very odd.
Can you try with a clean install and let me know if the issue is still happening?

Still save error
`D:\workspace\formly_test_app\node_modules\vue-formly-bootstrap\src\fields\baseField.js:1
import errorDisplay from '../components/errorDisplay.vue';
^
ParseError: 'import' and 'export' may appear only with 'sourceType: module'
D:\workspace\formly_test_app\node_modules\vue-formly-bootstrap\src\fields\baseField.js:1
import errorDisplay from '../components/errorDisplay.vue';
^
ParseError: 'import' and 'export' may appear only with 'sourceType: module`
I am attaching the source code you can set it up and try
formly_test_app.zip

thanks @jaideepdas that helped heaps. So what I found is that the error when you're trying to import baseField.js from vue-formly-bootstrap in your components/DateField.vue file. I'm not entirely sure why this isn't working but I'll look into it. For the meantime, just copy those files locally and import them that way. I'll notify you here when I've found a fix.


Logging: Design all up logging approach

We're not 100% happy with where we have landed - so we want to revisit this in 2.0. Next step is for @ajcvickers to prepare something for a design meeting.

Logging Proposal for 2.0
Scoping and sugar
Principle: logging is something that is setup and configured for the application, not per context instance.
To achieve this we introduce some new configuration APIs that are associated with the service provider. This is effectively application-level, or EF-global level configuration, although bound to the service provider so as not to be truly global.
We run the code to set configuration for this only once when we first use a new service provider.
This existing configuration would move:

WarningsConfiguration
MaxPoolSize
IsSensitiveDataLoggingEnabled
LoggerFactory
MemoryCache
ReplaceService

This means that ILogger no longer needs to be a scoped service, which solves the problem of logging forcing other services to be scoped.
Consequence/limitation: we cannot log for only one context instance and not another. This is something that we support with EF6, but does not work well with the logger abstractions we have. It would likely be ugly to implement and need something like:

A LoggerProvider that keeps track of the context instances for which logging is enabled, removing instances when contexts are disposed.
Passing the context instance to each Log call in a well-known way to allow for filtering

It's probably not worth doing all of this, especially given that most code just logs everything to one log anyway. For things that need correlation, we can do it in a way that is more natural to the logging abstractions, such as the work that was already done for connections.
API
We could introduce a new "On..." method for this API, but this is probably not necessary. Instead we could hang it off of "OnConfiguring". The logging sugar API (Issue #1199) would also go here, since it is application/global configuration. Maybe something like this:
optionsBuilder
    .UseSqlServer(@"Server=(localdb)\mssqllocaldb;Database=Demo;")
    .GlobalConfiguration(b => b
        .EnableSensitiveDataLogging()
        .Log(message => Console.WriteLine(message)));

As stated above, this new builder would only be run once the first time a new service provider is used. This could be confusing in a similar way to OnModelCreating, but then creating a new "On..." method could also be confusing in the same way.
Logger names and event IDs
From the Logging docs:

"Name your loggers with a distinct prefix so they can easily be filtered or disabled."
"A logging event may specify an integer event id. Event ids should uniquely identify a logging publication call site within a logging category (i.e. the name passed to ILoggerFactory.CreateLogger when creating the logger instance)."

Proposal for names/categories
Create a hierarchy of categories that we think best matches the semantics of what people will want to filter on. For example:

Everything EF logs starts with "Microsoft.EntityFrameworkCore"
Within this, everything related to the store/database starts with "Microsoft.EntityFrameworkCore.Database"
Within this, all SQL starts with "Microsoft.EntityFrameworkCore.Database.Sql"

Query would use: Microsoft.EntityFrameworkCore.Database.Sql.Query
Migrations would use: Microsoft.EntityFrameworkCore.Database.Sql.Migrations
Update pipeline would use: Microsoft.EntityFrameworkCore.Database.Sql.Update

Within this, connection logs start with "Microsoft.EntityFrameworkCore.Database.Connection"
And  so on...

Now filtering can be done with a simple "StartsWith" call in a LoggerProvider. We can also add nice sugar for this when using our Log API.
Proposal for event IDs

Based on definition above, event IDs are for identifying a call site; each call site should have a different ID.
When database providers log to one of the categories above, they should do so using an event ID that does not collide with one we are using
However, given that an application (service provider) can only be used with one database provider at a time, maybe it is okay to have the following distinctions:

A range of values to use for core EF code (10000-19999)
A range to use for relational code (20000-29999)
A range to use for providers (30000-39999)

The range from 0-9999 is not used so that code (most likely provider code) that does not follow this convention will still likely not cause collisions.

@ajcvickers Would you explain "not per context instance."? Thanks.

@MaherJendoubi I mean you can't register logging for a single instance of a DbContext but rather must register logging for all instances of DbContext that are associated with a given IServiceProvider.

Notes from design meeting discussion:

For the "global configuration" we will try separating this out into a new builder/method combination:

OnStartup on the context (for the OnConfiguring style of code)
AddEntityFrameworkOptions on the service collection (for the AddDbContext style of code)

We could consider allowing global configuration of all the other options as well, but will defer this for now
Providers will generally use the same categories as core/relational code uses, often by using the logger we supply
For event IDs, we will extend the range used by providers (to make @AndriySvyryd happy) and add a constant somewhere in our code for the provider start value
We will not attempt to have providers coordinate separate ranges--benefit not worth the cost
We will have globally unique IDs in EF core and relational code, even though they only really need to be unique within the category.

Proposal for logging categories
Notes:

Just a proposal: for discussion in the design meeting.
The principle here is to provide categories that allow for easy filtering by application code.

Preferably with StartsWith or EndsWith or a combination of the two

There are obviously other dimensions that could be used--for example, should SQL be included in Query category?

Categories:

Microsoft.EntityFrameworkCore.Database.Sql

ExecutedCommand

Microsoft.EntityFrameworkCore.Database.Connection

OpeningConnection
ClosingConnection

Microsoft.EntityFrameworkCore.Database.Transaction

TransactionIgnoredWarning
AmbientTransactionWarning
BeginningTransaction
CommittingTransaction
RollingbackTransaction

Microsoft.EntityFrameworkCore.Update

SavedChanges

Microsoft.EntityFrameworkCore.Model.Validation

All model validation messages

Microsoft.EntityFrameworkCore.Query

IncludeIgnoredWarning
CompilingQueryModel
PossibleUnintendedUseOfEqualsWarning
QueryClientEvaluationWarning
IncludingNavigation
CompilingQueryModel
OptimizedQueryModel
QueryPlan

Microsoft.EntityFrameworkCore.Infrastructure

ManyServiceProvidersCreated
ServiceProviderCreated

Microsoft.EntityFrameworkCore.Scaffolding.Design

SequenceMustBeNamedWarning, ColumnMustBeNamedWarning, etc.

Microsoft.EntityFrameworkCore.Migrations

RevertingMigration
ApplyingMigration
MigrateUsingConnection
MigrateUsingConnection
GeneratingMigrationDownScript
GeneratingMigrationUpScript

Microsoft.EntityFrameworkCore.Migrations.Design

ForeignMigrations
DestructiveOperation
ForceRemoveMigration
NoMigrationFile
NoSnapshotFile
RemovingMigration
RemovingSnapshot
RevertingSnapshot
ReusingSnapshotName
NoMigrationMetadataFile
ManuallyDeleted
WritingMigration
WritingSnapshot
ReusingNamespace
ReusingDirectory

Updated categories above based on design meeting discussion. Only change was to remove the .Design subcategory since it was deemed necessary.


WIP: Getting 500 errors for GET Collection

Reviewers
Functional: @MDunitz
Readability: @mckinsel

Changes

add test to return a collection with the minimum number of field allowed
add tests to verify the fix.
remove required fields from dataset schema in openAPI
This is part of the dropbox integration work

When reading a dataset already in the database, not all fields expected according to the openAPI spec were present. Since the only way to add a dataset to a collection is through the upload of an H5AD file, which does its own validation, we can relax the fields required in the openAPI spec. The spec has been modified to allow more field in the dataset to be null. This presently only affect responses we return since users cannot population these field through the API.
This PR currently breaks the My Collections page. I'll need to work with Frontend to resolve this before merging.

@MDunitz it's a super handy feature of unittests that let's you add a cleanup handler to a specific test. Since these tests create a resources that are only relevant to that single test we want to clean up that test data afterward so they don't pollute the test environment for the rest of the tests.


How do I dismiss a notification in hyprland?

Hyprland is working in Athena on your setup?

Thank you. I will test it

Fixed


Xlm money missing forgot to enter memo ID , i sent it to my own wallet

Money was sent to my own wallet on stellar but is missing because I forgot to enter memo ID

Did you ever figure this out


Swellrt.org pad does not load with Firefox

I have issues accessing the pad at swellrt.org with firefox, while I do not have those issues neither accessing pear2pear app pad nor accessing the pad at swellrt.org with chromium.
I do not have the issue neither accessing with chromium.
Here I copy the browser log:

message
code line

Session started
/swellrt/ (línea 381)

Atmosphere Connection Close 501
atmosphere.js (línea 2898)

Network disconnected null
/swellrt/ (línea 367)

Atmosphere callback 501
atmosphere.js (línea 2898)

Websocket failed. Downgrading to Comet and resending
atmosphere.js (línea 2898)

Atmosphere Connection Transport Failure Websocket failed. Downgrading to Comet and resending

Please provide Firefox version. Thanks
2015-08-06 11:47 GMT+02:00 atfornes<EMAIL_ADDRESS>
I have issues accessing the pad at swellrt.org with firefox, while I do
not have those issues neither accessing pear2pear app
http://p.p2pvalue.eu pad nor accessing the pad at swellrt.org with
chromium.
I do not have the issue neither accessing with chromium.
Here I copy the browser log:
message code line Session started /swellrt/ (línea 381) Atmosphere
Connection Close 501 atmosphere.js (línea 2898) Network disconnected null /swellrt/
(línea 367) Atmosphere callback 501 atmosphere.js (línea 2898) Websocket
failed. Downgrading to Comet and resending atmosphere.js (línea 2898) Atmosphere
Connection Transport Failure Websocket failed. Downgrading to Comet and
resending
—
Reply to this email directly or view it on GitHub
https://github.com/P2Pvalue/swellrt/issues/49.

Sure, Firefox version is 39.0

@atfornes Do you see the same requests as in #52 ?

yes, I have a screenshot of the Headings and answers of the request, but dont know how to add it here ...

See #54


cluster id is not synced to the local_status.compliance

Refers: https://issues.redhat.com/browse/ACM-5467
The cluster_id in status.managed_clusters table may be changed over time. So we need to update the cluster_id in local_status.compliance
https://github.com/stolostron/multicluster-global-hub/blob/4c86a47c93193c58c9053ba8b5fd2a05ef676fd0/manager/pkg/statussyncer/transport2db/syncer/dbsyncer/managed_clusters_db_syncer.go#L88-L94

/hold

Does it really resolve the missed cluster_id issue?

/hold

CREATE OR REPLACE FUNCTION public.set_cluster_id_to_local_compliance() RETURNS trigger
    LANGUAGE plpgsql
    AS $$
BEGIN
  UPDATE local_status.compliance set cluster_id=(SELECT cluster_id FROM status.managed_clusters
  WHERE payload -> 'metadata' ->> 'name' = NEW.cluster_name AND leaf_hub_name = NEW.leaf_hub_name)
  WHERE cluster_name = NEW.cluster_name AND leaf_hub_name = NEW.leaf_hub_name;
  RETURN NEW;
END;
$$;
DROP TRIGGER IF EXISTS update_compliance_table ON local_status.compliance;
CREATE TRIGGER update_compliance_table AFTER INSERT OR UPDATE ON local_status.compliance FOR EACH ROW WHEN (pg_trigger_depth() < 1) EXECUTE FUNCTION public.set_cluster_id_to_local_compliance();

This trigger will not update all the cluster_id in the compliance table.


⚠ Bofrost.de has degraded performance

In 551fa2e, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1058 ms

Resolved: Bofrost.de performance has improved in f2a2d0e after 20 minutes.


samples: wifi: Enable sample on disco_l475_iot1

The disco_l475_iot1 has the Inventek eS-WiFi, so lets enable the sample
on the board.  (This also gets us something that will build test the
eS-Wifi driver as part of sanitycheck).
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@92fba52). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #11567   +/-   ##
=========================================
  Coverage          ?   48.33%
=========================================
  Files             ?      270
  Lines             ?    42113
  Branches          ?    10138
=========================================
  Hits              ?    20355
  Misses            ?    17673
  Partials          ?     4085

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 92fba52...9832cb5. Read the comment docs.


feat: Add pre-trained models section

New section of the site, dedicated to hosting a curated set of
pre-trained ML models.
The focus is going to be in providing models that are:

not feasible for children to train themselves, because of the
amount of training data they'd need to be able to do it
fun or interesting uses of ML

I've only got a couple of ML models to start with, but the plan
is to add additional ones soon.
I will also start adding some worksheets that demonstrate how
to use the new blocks.
The new section isn't linked into the rest of the site. This is
mostly because I haven't worked out how/where to do that yet,
but it will also let me soft-launch the feature by sharing the
URL with some potential testers.
Signed-off-by: Dale Lane<EMAIL_ADDRESS>

quick test sb3 file for the face detection model : https://drive.google.com/open?id=1pIj8nQsG8cVWFZtvD_8XXXSxvyBsOJe2


Can't reset x-range with zoom enabled on dynamic data

I'm using $http.get() to obtain timeseries data for a candlestick chart, and then using $scope.api.updateWithData() to populate the chart.
If I leave zoom disabled, all works well.  However if I turn it on, I get two problems:

firstly - no zoom or pan actions actually work.  The chart stubbornly stays at its normal zoom level, and instead the page (in Chrome) just tries to scroll

secondly - if I start off with no $scope.data at all then I get an exception from line 571: cannot read property 'call' of undefined and still can't move the graph, although the correct X range is used.   If I start instead with an empty array (whether [] or [{values: []}] then the graph goes to the start of the unix epoch (1970/01/01) and then won't pan.

I'm using 1.0.5, with code as follows:
    $scope.config = {
        refreshDataOnly: false
    };

    $scope.data = [{values: []}];

    $scope.options = { chart: {
        type: 'candlestickBarChart',
        x: function(d) { return d.date; },
        y: function(d) { return d.close; },
        xScale: d3.time.scale(),
        height: 600,
        xAxis: { axisLabel: 'Date and Time', showMaxMin: false,
            tickFormat: function(x) { return dateFormat(new Date(x * 1000))
        },
        yAxis: { axisLabel: 'QPS', showMaxMin: false,
            tickFormat: d3.format('.3r') },
        zoom: { enabled: true, horizontalOff: false, verticalOff: true },
        useInteractiveGuideline: false
    }};

    $http.get('....').then(function(res) {
        // mangle data into the required structure
        ...
        $scope.api.updateWithData(data);
    });

Please advise...

p.s. if zoom.enabled === false then I get neither the exception nor the incorrect X range

I seem to have resolved this by placing a call to $scope.api.refresh() immediately before the call to .updateWithData().  Putting it after (which seemed to be the intuitive thing to do) didn't work - it left me with a blank "No data" graph.

Is simple $scope.$apply() not working instead using api?
$http.get('....').then(function(res) {
    // mangle data into the required structure
    ...
    $scope.data = data;
    $scope.apply(); //new data will be applied; directive automatically will be refreshed with new data
});

No, that throws an error $digest already in progress.

No, it throws an $digest already in progress error

ohh, sure..
if so, just the line $scope.data = data; should update the chart.. without $apply()..

The docs do say that should update the chart, but doesn't appear to fix up the zoom information.
AFAICS the call in nvd3Utils.zoom() via d3.behavior.zoom() that sets up the xScale, yScale etc only happens when a call to api.refresh() is made.

aha, I got it..
update is not working correctly with zoom enabled. it's a bug.. thanks!

Any update on a fix for this?


tensorflow issue on python3.5 running at raspbian 9 stretch

tensorflow library was downloaded from python wheels to raspberry pi 3 running raspbian 9. Thonny shell log reports a runtime warning while executing "import tensorflow" instruction: compile version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

I am also having the same warnings:
(keras_tf) pi@raspberrypi:~ $ python -c "import tensorflow as tf; print(tf.__version__)"
/home/pi/.virtualenvs/keras_tf/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5
  return f(*args, **kwds)
/home/pi/.virtualenvs/keras_tf/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
  return f(*args, **kwds)
1.11.0
(keras_tf) pi@raspberrypi:~ $

Thanks for your update... Regarding the issue, can it be fixed?
Looking forward your comments.
Thanks and regards
El mié., 3 de oct. de 2018 17:19, agrutter87<EMAIL_ADDRESS>escribió:

I am also having the same warnings:
(keras_tf) pi@raspberrypi:~ $ python -c "import tensorflow as tf; print(tf.version)"
/home/pi/.virtualenvs/keras_tf/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5
return f(*args, **kwds)
/home/pi/.virtualenvs/keras_tf/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
return f(*args, **kwds)
1.11.0
(keras_tf) pi@raspberrypi:~ $
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/22422#issuecomment-426820782,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApakeIfNwITdMV8lalYRG-bFCjHhiQC3ks5uhTgNgaJpZM4WyuI-
.

Nagging Assignee @petewarden: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

hello
after installing tensflow version 1.1.0. this is the error i get when try to import tensorflow as tf
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow.py", line 41, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "/usr/lib/python3/dist-packages/thonny/backend.py", line 305, in _custom_import
module = self._original_import(*args, **kw)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "/usr/lib/python3.5/imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "/usr/lib/python3.5/imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: /usr/local/lib/python3.5/dist-packages/tensorflow/python/_pywrap_tensorflow_internal.so: wrong ELF class: ELFCLASS64
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/pi/Desktop/opencv_test.py", line 4, in
from tensorflow import tf
File "/usr/lib/python3/dist-packages/thonny/backend.py", line 305, in _custom_import
module = self._original_import(*args, **kw)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/init.py", line 24, in
from tensorflow.python import *
File "/usr/lib/python3/dist-packages/thonny/backend.py", line 305, in _custom_import
module = self._original_import(*args, **kw)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/init.py", line 51, in
from tensorflow.python import pywrap_tensorflow
File "/usr/lib/python3/dist-packages/thonny/backend.py", line 305, in _custom_import
module = self._original_import(*args, **kw)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow.py", line 52, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow.py", line 41, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "/usr/lib/python3/dist-packages/thonny/backend.py", line 305, in _custom_import
module = self._original_import(*args, **kw)
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "/usr/lib/python3.5/imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "/usr/lib/python3.5/imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: /usr/local/lib/python3.5/dist-packages/tensorflow/python/_pywrap_tensorflow_internal.so: wrong ELF class: ELFCLASS64
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/install_sources#common_installation_problems
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

kindly help.

Question: did you find a solution or is it working right now? As shown in the ticket https://github.com/tensorflow/tensorflow/issues/26459 some other people has the very same problem without any solution. sharing your solution would be fine.


Over the Edge sheet typo fix and Shadows Over Sol sheet update

Fixed typo in the Important Person attribute of the Over the Edge 2e sheet. Also updated the Shadows Over Sol character sheet for compatibility with the Siren's Call supplement.

These are some pretty extensive changes to the Shadows over Sol sheet. Will this upgrade affect users currently using the sheets? I'm mostly concerned about data being lost due to attribute names being changed.
If any attribute names have been changed, you can use sheet workers to update the old sheet to the new version.

No attributes were changed on the Shadows Over Sol sheet. Most of the big changes you see are to the structure of  tags to make the sheet flow better when it is resized. The way the sheet previous used CSS floats made it look weird when you resized the sheet to make it more narrow.


It work good the app but still say that have an error!

Analyzer Feedback from IntelliJ
Version information

IDEA AI-191.8<IP_ADDRESS>77832
2.7.0-edge.fa4379946109467c8a48f20f19d83d7c72968a3e
AI-191.8<IP_ADDRESS>77832, JRE 1.8.0_202-release-1483-b03x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1366x768

Exception
Dart analysis server, SDK version 2.7.0-edge.fa4379946109467c8a48f20f19d83d7c72968a3e, server version 1.27.4, FATAL error: Failed to handle request: {id: 3, method: analysis.setAnalysisRoots, params: {included: [C:\Users\Rafael\AndroidStudioProjects\flutter_app], excluded: [C:\Users\Rafael\AndroidStudioProjects\flutter_app\.idea, C:\Users\Rafael\AndroidStudioProjects\flutter_app\.dart_tool, C:\Users\Rafael\AndroidStudioProjects\flutter_app\.idea, C:\Users\Rafael\AndroidStudioProjects\flutter_app\.pub, C:\Users\Rafael\AndroidStudioProjects\flutter_app\build]}, clientRequestTime:<PHONE_NUMBER>463}
FileSystemException: Directory watcher closed unexpectedly, path = 'C:\Users\Rafael\AndroidStudioProjects\flutter_app'
#0      _FileSystemWatcher._listenOnSocket.<anonymous closure> (dart:io-patch/file_patch.dart:309:11)
#1      _ExpandStream._handleData (dart:async/stream_pipe.dart:248:23)
#2      _ForwardingStreamSubscription._handleData (dart:async/stream_pipe.dart:164:13)
#3      _rootRunUnary (dart:async/zone.dart:1136:13)
#4      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#5      _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#6      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#7      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#8      _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
#9      _StreamController._add (dart:async/stream_controller.dart:640:7)
#10     _StreamController.add (dart:async/stream_controller.dart:586:5)
#11     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1384:35)
#12     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:890:18)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#15     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#16     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

For additional log information, please append the contents of
file://C:\Users\Rafael\AppData\Local\Temp\report.txt.

Thanks for reporting this issue! This was previously reported at https://github.com/dart-lang/sdk/issues/38853; please follow along there.

Duplicate of https://github.com/dart-lang/sdk/issues/38853


Add reminder for Fractal potions

Add an optional reminder for Fractal potions. Need to think about handling stacks (remind if <5) and limiting to Fractals (get map via Mumblelink?).

Added as default custom reminder in https://github.com/Zerthox/arcdps-food-reminder/commit/85aadedcf22cda9fb7c719f33066a5597b74b60b. Filtering via map id from Mumblelink.


UX: docker network inspect should show stopped containers

Currently, stopped containers no longer appear when inspecting a network, but re-appear when they are started again (paused containers on the other hand, are still visible).
From a UX perspective, I expected containers to appear in the network, regardless of their state (but with an empty IP-address if stopped)

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

:heavy_plus_sign: 1

This is because a stopped container is not part of any network.

@cpuguy83 except that the container does try to reconnect on restart --- and fails if the network is gone.

/cc @mavenugo @mrjana @tiborvass. just jotting these down so that it can be discussed

ping @thaJeztah @mavenugo @mrjana @aboch @sanimej


Stripchat No Video Formats Found

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Most parts of the world
Provide a description that is worded well enough to be understood
When downloading, it would say that there are no video formats found. Stopped working since today, site usable/playable via browser.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://stripchat.com/sexgreat']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.10.04 [4e0511f] (win32_exe)
[debug] Python 3.8.10 (CPython 64bit) - Windows-10-10.0.20348-SP0
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg N-108625-g28ac2279ad-20221012 (setts), ffprobe N-108625-g28ac2279ad-20221012
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2022.09.24, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1690 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.10.04, Current version: 2022.10.04
yt-dlp is up to date (2022.10.04)
[debug] [Stripchat] Extracting URL: https://stripchat.com/sexgreat
[Stripchat] sexgreat: Downloading webpage
[Stripchat] sexgreat: Downloading m3u8 information
WARNING: [Stripchat] Failed to download m3u8 information: <urlopen error [Errno 11001] getaddrinfo failed>
ERROR: [Stripchat] sexgreat: No video formats found!; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1477, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1574, in __extract_info
  File "yt_dlp\YoutubeDL.py", line 1632, in process_ie_result
  File "yt_dlp\YoutubeDL.py", line 2569, in process_video_result
  File "yt_dlp\YoutubeDL.py", line 1027, in raise_no_formats
yt_dlp.utils.ExtractorError: [Stripchat] sexgreat: No video formats found!; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

Having the same issue.

Configuration changed. https://github.com/yt-dlp/yt-dlp/pull/5445 fixes this issue.


feat(amazonaurora): adding customization Aurora Vector Store

Fixes #599

Added VPC customization option to Aurora Vector Store
Made some attributes accessible such as:

vpc to understand where the cluster has been deployed
auroraSecurityGroup for adding custom Ingress Rules

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

Thanks @aws-rafams ! Did you deploy the construct to verify it works with your changes ?

Yes, I have tested it and it works, the only thing to be careful is that the VPC must have Private and Public subnets, otherwise deployment will fail. I have updated the docs accordingly.

Still failing, looking at the build

Fixed the build, @aws-rafams could you please have a look/test those changes make sure it's all good on your end ? Then we can merge

Fixed the build, @aws-rafams could you please have a look/test those changes make sure it's all good on your end ? Then we can merge

will pull changes and test them. Also a question, do you think we should generate a name for the cluster identifier? Using the construct two times results in a deployment error as there will be two clusters with the same identifier (it is now internally hardcoded).

Fixed the build, @aws-rafams could you please have a look/test those changes make sure it's all good on your end ? Then we can merge

will pull changes and test them. Also a question, do you think we should generate a name for the cluster identifier? Using the construct two times results in a deployment error as there will be two clusters with the same identifier (it is now internally hardcoded).

Sure, good catch ! We can do it in a separate PR just to avoid too many changes here if that works for you !

Was testing the changes, and it seems due to a change recently introduced regarding VPC endpoints (#614), the CustomResource Lambda which gets credentials from SecretsManager and connects to the Aurora Database, is now on a SubnetType.PRIVATE_ISOLATED subnet rather than on a SubnetType.PRIVATE_WITH_EGRESS. The deployment fails as the Lambda can't reach SM. Will now test manually creating the SM endpoint, but in my opinion this should be transparent to the user and a new endpoint should be created if not present.

Was testing the changes, and it seems due to a change recently introduced regarding VPC endpoints (#614), the CustomResource Lambda which gets credentials from SecretsManager and connects to the Aurora Database, is now on a SubnetType.PRIVATE_ISOLATED subnet rather than on a SubnetType.PRIVATE_WITH_EGRESS. The deployment fails as the Lambda can't reach SM as in the provided custom VPC there is no existing endpoint. Will now test manually creating the SM endpoint, but in my opinion this should be transparent to the user and a new endpoint should be created if not present.

Thanks @aws-rafams , I was able to reproduce. I found out a similar issue when testing another sample which uses the custom resource. I reverted the changes introduced to the VPC. We can merge your original changes which were working, and I'll have a look to re-apply later the changes from the previous PR

@aws-rafams Could you please pull the latest on this branch and do a last run to make sure it works on your end ? If it is all good, we can merge. Thank you !

Was testing the changes, and it seems due to a change recently introduced regarding VPC endpoints (#614), the CustomResource Lambda which gets credentials from SecretsManager and connects to the Aurora Database, is now on a SubnetType.PRIVATE_ISOLATED subnet rather than on a SubnetType.PRIVATE_WITH_EGRESS. The deployment fails as the Lambda can't reach SM as in the provided custom VPC there is no existing endpoint. Will now test manually creating the SM endpoint, but in my opinion this should be transparent to the user and a new endpoint should be created if not present.

Thanks @aws-rafams , I was able to reproduce. I found out a similar issue when testing another sample which uses the custom resource. I reverted the changes introduced to the VPC. We can merge your original changes which were working, and I'll have a look to re-apply later the changes from the previous PR

I have tested the latest commits and on my end everything works as expected.


GEN-9: Review&Revise the Project Planning

What's up?

In our Week #2 Meeting #2, we decided to revise the project planning and come up with possible improvements in our next meeting on 16/10/2022 @18.00. Since each step of the planning is dependent on other steps as well, we decided to make the necessary updates on planning in our meeting altogether.
Within this task, all team members are expected to review the project planning and provide possible improvements on our Discord text channel 🖥-project-planning  within the Milestone subchannel. @sinemKocoglu already provided the raw version of the project plan so that we can change it easily using Project Libre (unfortunately).
You can find the project planning we prepared for CmpE451 at the first Milestone deliverable here. Please notice that the project planning presented in Milestone II is for Practice App.

To Do

[x] Review the project plan individually, take notes for possible updates/improvements.
[x] Revise the project plan together in the meeting.

Deadline
20.10.2022 @18:00
Additional Information
No response
Reviewers
@KarahanS (will close the issue when all actions are taken)

In our general Meeting-3, we discussed about our project plan and prepared a draft. Regarding actions will be taken by @kostanya and @sinemKocoglu. Closing this issue.


Move away from setup.py test

🐞 Problem
We all want setup.py to go away, so let's better use Makefiles or plain pytest commands.

💡 Possible solutions

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

Related: https://github.com/poliastro/poliastro/issues/252


[SPARK-47390][SQL][FOLLOWUP] Fix TIME_WITH_TIMEZONE mapping in PostgresDialect

What changes were proposed in this pull request?

This PR fixes a bug in SPARK-47390, we shall separate TIME from TIMESTAMP case-match branch
Why are the changes needed?

bugfix
Does this PR introduce any user-facing change?

no
How was this patch tested?

local test with #45519 merged together
Was this patch authored or co-authored using generative AI tooling?
no

Docker test passed.
Merged to master.


upgrade go version to 1.9.1

Release note:

mixer is now built with go 1.9.1

This change is

/assign @douglas-reid

/lgtm


No export links available for google form and google map

Summary
I am trying to export the google workspace documents. For this, I use export link from files resource to get the available download link for the document type. I can get for documents such as google doc, slide, spreadsheet etc. However, for google form, google map, I don't get the export links. Thus, cannot export the documents.
https://developers.google.com/drive/api/guides/manage-downloads#export-content-browser

Sample Name
(i.e. Java Samples)
Expected Behavior
Get export links for google form, google map to export the document
Actual Behavior
No export links available from files resource
Specifications

Java version (java -version) - 17
OS (Mac/Linux/Windows) - Mac

Thoe files are not exportable. See https://developers.google.com/drive/api/guides/ref-export-formats for supported conversions.
For forms, use the Forms & sheets APIs to export to whatever format needed.

If you'd like to file a feature request for the API to support additional conversions, file it at https://b.corp.google.com/issues/new?component=191650&template=824106&pli=1


[event-hubs] Bundle size is large

Package Name: @azure/event-hubs
Package Version:  5.8.0
Operating system: Windows
[x] nodejs

version: 16.14.2

[x] typescript

version: 4.4.3

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Description and screenshots
The event hubs bundle size is quite large.

I only have this import: import { EventDataBatch, EventHubProducerClient } from '@azure/event-hubs';
To Reproduce
Steps to reproduce the behavior:

I analyzed bundle using @next/bundle-analyzer

Expected behavior
Smaller bundle size
A couple questions:

Are you using tree shaking?
Would it be possible to have a lite package? For example, https://github.com/mobxjs/mobx-react-lite

Additional context

Azure app insight used to have the similar problem.
Please see the reference here:

https://github.com/microsoft/ApplicationInsights-JS/issues/1076

/cc @jeremymeng

cc @qiaozha Want to know the progress of how you handling this issue. Thanks