Create Profile for vuga willy

Name
vuga willy
Profile Image

Hello! my name is vuga William
A South Sudanese-born refugee for 28 years. As a refugee, I faced a couple of challenges that made me come up with basic yet fulfilling solutions to solving challenges that affect me and my community which included in-access to opportunities in the refugee camp because of the in- access to skills and information and hence I created a Community Based Organization, Youth Empowerment foundation that is empowering and changing the narrative by providing skills and knowledge to refugees and host communities in the refugee camps in Adjumani hence giving me the stand as a tech advocate and community transformer.
Country
Uganda
Region
West Nile
Organisation
The Youth Empowerment Foundation (YEF)
Languages
English, Juba Arabic and Mad'i
Skill 1
Video, photography  & Audio
Qualifications for Skill 1
Over the years i have worked with  Kapital Movie Industry, where i learned a lot about leadership, videography and storytelling  and I am proud to be able to use these tools and softwares DSC00587
Skill 2
Developing Open Technology Skills and imparting Community Information
Qualifications for Skill 2
#ASKnet
Access to skills and Knowledge Network, i received a Certificate of completion of the Training Program on developing open technology skills and imparting community information (TOT)

Skill 3
No response
Qualifications for Skill 3
No response
Skill 4
No response
Qualifications for Skill 4
No response
describe yourself
Vuga William is my name, am 35 years old. A South Sudanese Male, living in Pagriniya Refugee Settlement in Uganda (Adjuamani district ). This is my second time becoming a refugee in  Uganda, due to civil war that erupted back home in 2013 and 2016 in the country South Sudan. This has negatively affected my youthful lifetime.
As life keeps pressing harder Technology has changed everything! I started learning peer to peer with my friends through workshops, and working on the Defyhatenow (Hate speech Mitigation and counteract online and offline hate speech), That was paving way for me to organize lot of meetups and workshops for my community later on founding Youth Enpowerment Foundation (YEF), a community innovation Hub That helps thousand communities both refugee and host to address their local problems, YEF has become a pool for young people to have access to information and basic learning at the center.

E-Mail
<EMAIL_ADDRESS>Phone
+256784164470
WhatsApp
+256784164470
Website
No response
Telegram
Vuga William
GitHub
vuga william
LinkedIn
No response
Twitter
@vugawilliam
Facebook
vuga william
Instagram
vuga william
Mastodon
No response
WikiFab
No response
Other
<EMAIL_ADDRESS>

I think the qualifications via pictures is a nice Idea and we definitely all know Vuga so @vugawilliam skills can be testified by @maliarich @yyenki @romeoplat and @timmwille :dancing_men:

@MartinSchott Skill 1 would refer to "Media & Art" and Skill 2 to "Hardware & Repair" but we definitely might want to split into Skill 3 for "Community & Moderation" and also Skill 4 as "Organisational Development" as he is founder of YEF Hub :100:

@vugawilliam later you can also clarify here via comment or add additional skills/info via Issue templat "Skills Update"

I feel like for some of us we can also have the power of adding and editing our profiles later

I think the qualifications via pictures is a nice Idea and we definitely all know Vuga so @vugawilliam skills can be testified by @maliarich @yyenki @romeoplat and @timmwille 👯♂
Would this be another option fo #85 process of verification?

Absolutely!

I think organizational development and media & Art would work well.
On Thu, Jan 6, 2022, 3:35 PM Yine Nyika @.***> wrote:

I think the qualifications via pictures is a nice Idea and we definitely
all know Vuga so @vugawilliam https://github.com/vugawilliam skills can
be testified by @maliarich https://github.com/maliarich @yyenki
https://github.com/yyenki @romeoplat https://github.com/romeoplat and
@timmwille https://github.com/timmwille 👯♂
Would this be another option fo #85
https://github.com/ASKnetCommunity/LEAD/issues/85 process of
verification?
Absolutely!
—
Reply to this email directly, view it on GitHub
https://github.com/ASKnetCommunity/LEAD/issues/77#issuecomment-1006551489,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANSI4W5ULBQ27JGKZ3JG74LUUWEBLANCNFSM5JLLYIUA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

I included the skills 1 and 2 as @timmwille suggested, but didn't include Skill 3 for "Community & Moderation" and also Skill 4 as "Organisational Development", because I would need a qualification text for that. If you want that to be included as well, please provide a qualification text for each (similar as you have done for the first two skills) @vugawilliam . Thank you very much!
Btw, it's a great idea to include the photos!

@vugawilliam ok cool add your certificates in here is fine

And can we re work on the basic grammar describing @vugawilliam 'S AMAZING WORK

Just edited the |Description of @vugawilliam , @chardso @timmwille anyone can jump in and check up as well as we try to get this profile to the verified column

There is Vuga willy and Vuga William, and there is also Vuga William ,28years and Vuga William 35year,which one is the true age? Other wise the descriptions are all good ,detailed and some of us have seen practically in the field.verify age and which description and push.

Ooh sorry he has been a refugee for 28years not 28yrs old,pole papa.

So how is the status on this Profile?

I would say its done,but maybe detailed consultation be done in the meeting tomorrow.

made some edits on Williams profile basically correcting region and fixing gramma

so I can see this is now verified @ASKnetCommunity/coordinators and I will ping @MartinSchott to add this final edit :) thx a lot!

is uploaded in content branch, but needs to be pulled to main branch

ok we close this as it will join the main branch soon

final i have add more 2 years plus ...so am now 37 years old

Doesn't matter,viewers can mathematically calculate.


Build throws warnings originating in graphql-language-service-interface

I have React app which depends on graphiql which we render on certain route (graphiql is not deployed as standalone app).
When executing:
npm run build

Several warnings are returned. Since our CI/CD treats warnings as errors, this is preventing us from building on CI/CD (unless we turn this off)
./node_modules/graphql-language-service-interface/dist/getOutline.d.ts 2:7
Module parse failed: Unexpected token (2:7)
You may need an appropriate loader to handle this file type.
| import { Outline } from 'graphql-language-service-types';
> export declare function getOutline(queryText: string): Outline | null | undefined;
| //# sourceMappingURL=getOutline.d.ts.map

./node_modules/graphql-language-service-interface/dist/getDefinition.d.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type.
| import { FragmentSpreadNode, FragmentDefinitionNode, OperationDefinitionNode, NamedTypeNode } from 'graphql';
| import { DefinitionQueryResult, FragmentInfo, Uri, ObjectTypeInfo } from 'graphql-language-service-types';
> export declare const LANGUAGE = "GraphQL";
| export declare function getDefinitionQueryResultForNamedType(text: string, node: NamedTypeNode, dependencies: Array<ObjectTypeInfo>): Promise<DefinitionQueryResult>;
| export declare function getDefinitionQueryResultForFragmentSpread(text: string, fragment: FragmentSpreadNode, dependencies: Array<FragmentInfo>): Promise<DefinitionQueryResult>;

./node_modules/graphql-language-service-interface/dist/autocompleteUtils.d.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type.
| import { GraphQLField, GraphQLSchema, GraphQLType } from 'graphql';
| import { CompletionItem, ContextToken, State, AllTypeInfo } from 'graphql-language-service-types';
> export declare function getDefinitionState(tokenState: State): State | null | undefined;
| export declare function getFieldDef(schema: GraphQLSchema, type: GraphQLType, fieldName: string): GraphQLField<any, any> | null | undefined;
| export declare function forEachState(stack: State, fn: (state: State) => AllTypeInfo | null | void): void;

./node_modules/graphql-language-service-interface/dist/getAutocompleteSuggestions.d.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type.
| import { GraphQLSchema } from 'graphql';
| import { CompletionItem, ContextToken, State, AllTypeInfo, Position } from 'graphql-language-service-types';
> export declare function getAutocompleteSuggestions(schema: GraphQLSchema, queryText: string, cursor: Position, contextToken?: ContextToken): Array<CompletionItem>;
| export declare function getTokenAtPosition(queryText: string, cursor: Position): ContextToken;
| export declare function getTypeInfo(schema: GraphQLSchema, tokenState: State): AllTypeInfo;

./node_modules/graphql-language-service-interface/dist/GraphQLLanguageService.d.ts 4:7
Module parse failed: Unexpected token (4:7)
You may need an appropriate loader to handle this file type.
| import { CompletionItem, DefinitionQueryResult, Diagnostic, GraphQLCache, GraphQLConfig, GraphQLProjectConfig, Uri, Position } from 'graphql-language-service-types';
| import { Hover } from 'vscode-languageserver-types';
> export declare class GraphQLLanguageService {
|     _graphQLCache: GraphQLCache;
|     _graphQLConfig: GraphQLConfig;

./node_modules/graphql-language-service-interface/dist/getHoverInformation.d.ts 4:7
Module parse failed: Unexpected token (4:7)
You may need an appropriate loader to handle this file type.
| import { ContextToken, Position } from 'graphql-language-service-types';
| import { Hover } from 'vscode-languageserver-types';
> export declare function getHoverInformation(schema: GraphQLSchema, queryText: string, cursor: Position, contextToken?: ContextToken): Hover['contents'];
| //# sourceMappingURL=getHoverInformation.d.ts.map

./node_modules/graphql-language-service-interface/dist/getDiagnostics.d.ts 4:7
Module parse failed: Unexpected token (4:7)
You may need an appropriate loader to handle this file type.
| import { Diagnostic, CustomValidationRule } from 'graphql-language-service-types';
| import { Range } from 'graphql-language-service-utils';
> export declare const SEVERITY: {
|     ERROR: number;
|     WARNING: number;

Toolset versions:

node: v10.16.3
npm: 6.9.0
tcs: 3.7.2

I'm not sure whether this is the same issue as #882, I saw webpack being used by react build script, but errors are different.

Yes, webpack shouldn’t be a problem. Is there a reason you are importing
.d.ts files?
On Wed, Nov 13, 2019 at 6:02 AM Zdenek Havlin<EMAIL_ADDRESS>wrote:

I have React app which depends on graphiql which we render on certain
route (graphiql is not deployed as standalone app).
When executing:
npm run build
Several warnings are returned. Since our CI/CD treats warnings as errors,
this is preventing us from building on CI/CD (unless we turn this off)
./node_modules/graphql-language-service-interface/dist/getOutline.d.ts 2:7
Module parse failed: Unexpected token (2:7)
You may need an appropriate loader to handle this file type.
| import { Outline } from 'graphql-language-service-types';

export declare function getOutline(queryText: string): Outline | null | undefined;
| //# sourceMappingURL=getOutline.d.ts.map

./node_modules/graphql-language-service-interface/dist/getDefinition.d.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type.
| import { FragmentSpreadNode, FragmentDefinitionNode, OperationDefinitionNode, NamedTypeNode } from 'graphql';
| import { DefinitionQueryResult, FragmentInfo, Uri, ObjectTypeInfo } from 'graphql-language-service-types';

export declare const LANGUAGE = "GraphQL";
| export declare function getDefinitionQueryResultForNamedType(text: string, node: NamedTypeNode, dependencies: Array): Promise;
| export declare function getDefinitionQueryResultForFragmentSpread(text: string, fragment: FragmentSpreadNode, dependencies: Array): Promise;

./node_modules/graphql-language-service-interface/dist/autocompleteUtils.d.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type.
| import { GraphQLField, GraphQLSchema, GraphQLType } from 'graphql';
| import { CompletionItem, ContextToken, State, AllTypeInfo } from 'graphql-language-service-types';

export declare function getDefinitionState(tokenState: State): State | null | undefined;
| export declare function getFieldDef(schema: GraphQLSchema, type: GraphQLType, fieldName: string): GraphQLField<any, any> | null | undefined;
| export declare function forEachState(stack: State, fn: (state: State) => AllTypeInfo | null | void): void;

./node_modules/graphql-language-service-interface/dist/getAutocompleteSuggestions.d.ts 3:7
Module parse failed: Unexpected token (3:7)
You may need an appropriate loader to handle this file type.
| import { GraphQLSchema } from 'graphql';
| import { CompletionItem, ContextToken, State, AllTypeInfo, Position } from 'graphql-language-service-types';

export declare function getAutocompleteSuggestions(schema: GraphQLSchema, queryText: string, cursor: Position, contextToken?: ContextToken): Array;
| export declare function getTokenAtPosition(queryText: string, cursor: Position): ContextToken;
| export declare function getTypeInfo(schema: GraphQLSchema, tokenState: State): AllTypeInfo;

./node_modules/graphql-language-service-interface/dist/GraphQLLanguageService.d.ts 4:7
Module parse failed: Unexpected token (4:7)
You may need an appropriate loader to handle this file type.
| import { CompletionItem, DefinitionQueryResult, Diagnostic, GraphQLCache, GraphQLConfig, GraphQLProjectConfig, Uri, Position } from 'graphql-language-service-types';
| import { Hover } from 'vscode-languageserver-types';

export declare class GraphQLLanguageService {
|     _graphQLCache: GraphQLCache;
|     _graphQLConfig: GraphQLConfig;

./node_modules/graphql-language-service-interface/dist/getHoverInformation.d.ts 4:7
Module parse failed: Unexpected token (4:7)
You may need an appropriate loader to handle this file type.
| import { ContextToken, Position } from 'graphql-language-service-types';
| import { Hover } from 'vscode-languageserver-types';

export declare function getHoverInformation(schema: GraphQLSchema, queryText: string, cursor: Position, contextToken?: ContextToken): Hover['contents'];
| //# sourceMappingURL=getHoverInformation.d.ts.map

./node_modules/graphql-language-service-interface/dist/getDiagnostics.d.ts 4:7
Module parse failed: Unexpected token (4:7)
You may need an appropriate loader to handle this file type.
| import { Diagnostic, CustomValidationRule } from 'graphql-language-service-types';
| import { Range } from 'graphql-language-service-utils';

export declare const SEVERITY: {
|     ERROR: number;
|     WARNING: number;

Toolset versions:

node: v10.16.3
npm: 6.9.0
tcs: 3.7.2

I'm not sure whether this is the same issue as #882
https://github.com/graphql/graphiql/issues/882, I saw webpack being
used by react build script, but errors are different.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/graphql/graphiql/issues/996?email_source=notifications&email_token=AAKOFF63NKN2NXDI6SYI4WTQTPNFHA5CNFSM4JMZDJZ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HY7CKUA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKOFF7Y6BMNUI75HJVE7R3QTPNFHANCNFSM4JMZDJZQ
.

@acao I don't import anything myself, this seems to be done somewhere within react build scripts.
I did only:

npm install graphiql (this brought dependency on graphql-language-service-interface)
`import GraphiQL from 'graphiql'
import ...css
<GraphiQL .../>

nothing more.

We have a webpack example we will be merging in the next week, until we
make this fix it wont work with create react app without overriding the
webpack config. but it should work fine with CRA once we merge that dynamic
file resolution bugfix for webpack. Been talking with a webpack maintainer
about it, very tricky!
On Wed, Nov 13, 2019 at 1:07 PM Zdenek Havlin<EMAIL_ADDRESS>wrote:

@acao https://github.com/acao I don't import anything myself, this
seems to be done somewhere within react build scripts.
I did only:

npm install graphiql (this brought dependency on
graphql-language-service-interface)
`import GraphiQL from 'graphiql'
import ...css
<GraphiQL .../>

nothing more.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphql/graphiql/issues/996?email_source=notifications&email_token=AAKOFF5JUMMK5Y6IXS4SPLDQTQ65VA5CNFSM4JMZDJZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED7DE7Y#issuecomment-553529983,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKOFF4LRGLRF3HZRADOYWDQTQ65VANCNFSM4JMZDJZQ
.

I'm using GraphiQL in the exact same way as @wdolek and was experiencing the same warnings.
I've just updated to GraphiQL 0.17.0 and can confirm the warnings are gone!

Fixed!
+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS> <-- got updated
| | +--<EMAIL_ADDRESS> <-- got updated
| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS> <-- got updated
| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>


fix defaults for not rails environment

:+1:
Could you update the gem version and deploy to RubyGems?


[BUG] Unsupported Media Type Error using @AllArgsConstructor

Describe the bug
When using the @AllArgsConstructor annotation in the project, the error "415, Unsupported Media Type, Content type application/json; charset=UTF-8 not supported" is thrown when trying to access the REST service.
@PutMapping("/register")
	public ResponseEntity<User> register(@Valid @RequestBody(required = false) User user, @ApiIgnore Errors err) {
		User savedUser = userService.register(user);
		return new ResponseEntity<User>(savedUser , HttpStatus.CREATED);
}

@Entity
@Getter
@Setter
@Table(name = "USER", schema = "public")
@NoArgsConstructor
@AllArgsConstructor
public class User {

	private static final long serialVersionUID = 1L;

	@Id
	@Setter
	@Size(max = 36)
	@GeneratedValue(generator = "uuid2", strategy = GenerationType.AUTO)
	@GenericGenerator(name = "uuid2", strategy = "org.hibernate.id.UUIDGenerator")
	@Column(name = "id", updatable = false, nullable = false, unique = true)
	private String id;

	@NotBlank
	@Size(min = 4, max = 40)
	@Column(unique = true, updatable = false)
	@Email(regexp =<EMAIL_ADDRESS>	private String email;

	@Column(name = "name")
	private String name;

	@Enumerated
	@Column(name = "user_type")
	private UserType userType;

	@NotBlank
	@JsonProperty(access = Access.WRITE_ONLY)
	private String password;
}

Sending the json to follow in the service the error
"415, Unsupported Media Type, Content type application/json; charset=UTF-8 not supported"
was thrown.
{
"id": "5658c49d-32bf-4996-a204-fc159b41727a",
"name": "Testing User",
"email"<EMAIL_ADDRESS>"phone": "44999999999",
"password": "123changeme",
"userType": "DRIVER"
}

Lombok version 1.18.8
Platform "Spring Tool Suite 4", Java: OpenJDK 11

Can you please provide the minimal program to demonstrate the error?

I have found that the problem is in attribute of type java.util.List. The application does not know how to convert it to JSON.
I'll close the issue.


Select input should support option groups

React Select is designed to allow for options to be displayed in groups, however we are a bit strict about how we present options to our input and it appears we disallow this feature.
Shape for groupOptions in example on home page is here

Note: This is a feature that is currently used in the Sencha implementation of a client app that we are updated to the new toolkit. So this is a real world desire for this driving the ticket.

PR is here:
https://github.com/xh/hoist-react/pull/1529

👍


Add note about thread safety of ConfigProvider

Fixes KAFKA-9634.

Any chance of code reivew @rajinisivaram, @kkonstantine, @hachikuji?

ok to test

@kkonstantine are you able to merge this now or are you still waiting for 2.5.0?

2.5 is still in RC generation and testing phase and only blockers are considered for merging on that version branch. Best to wait for this non-urgent PR, which would be nice to backport.
I'll keep track of this and a few other PRs to merge once we go out of code freeze again soon. Thanks for the reminder.

One irrelevant test failure on jdk11. Will merge this documentation change, since it's zero risk.
Thanks for improving the docs with this useful note @tombentley !

Merged to trunk and backported to 2.5, 2.4, 2.3, 2.2, 2.1 and 2.0


[QUESTION] SDK C++ Producer Freezing

When running kvs_gstreamer_sample.cpp, it works for several hours but after a seemingly random number of hours (but less than 24 hours) the process seems to freeze with no errors I can see, and no CPU usage.
Do you have any recommendations on how to debug or fix this issue? Thank you!
top shows 0% CPU usage.:
    1 root      20   0   18384      4      4 S   0.0  0.0   0:00.01 kinesis.sh
   11 root      20   0 1235280  43632  12468 S   0.0  0.3   5:19.93 kvs_gstreamer_s
  105 root      20   0   18516   3380   3012 S   0.0  0.0   0:00.00 bash
  122 root      20   0   38748   3252   2748 R   0.0  0.0   0:00.00 top

The kinesis.sh is just
AWS_DEFAULT_REGION=$AWS_REGION ./kvs_gstreamer_sample $AWS_VIDEO_STREAM_NAME YOUR_RTSP_STREAM

As far as I can see, there are no errors reported, it is just frozen. I am running inside a docker container (as part of microk8s kubernetes deployment). Restarting the container restores the stream.
** Logging **
Below is an excerpt of last few hundred lines of the log:
[DEBUG] [09-02-2021 23:31:54:075.617 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [09-02-2021 23:31:54:075.625 GMT] Reporting fragment ack received. Ack timecode<PHONE_NUMBER>215
[DEBUG] [09-02-2021 23:31:54:075.637 GMT] postReadCallback(): Wrote 6033 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:54:075.681 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:31:54:180.258 GMT] Kinesis Video client and stream metrics
        >> Overall storage byte size: 134217728
        >> Available storage byte size: 134122975
        >> Allocated storage byte size: 94753
        >> Total view allocation byte size: 144080
        >> Total streams frame rate (fps): 29
        >> Total streams transfer rate (bps): 460480 (449 Kbps)
        >> Current view duration (ms): 100
        >> Overall view duration (ms): 1068
        >> Current view byte size: 26787
        >> Overall view byte size: 93169
        >> Current frame rate (fps): 29.9425
        >> Current transfer rate (bps): 460480 (449 Kbps)
[DEBUG] [09-02-2021 23:31:55:075.771 GMT] postReadCallback(): Wrote 65524 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:55:075.989 GMT] postReadCallback(): Wrote 1867 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:55:076.012 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:31:55:247.488 GMT] Kinesis Video client and stream metrics
        >> Overall storage byte size: 134217728
        >> Available storage byte size: 134050187
        >> Allocated storage byte size: 167541
        >> Total view allocation byte size: 144080
        >> Total streams frame rate (fps): 29
        >> Total streams transfer rate (bps): 462136 (451 Kbps)
        >> Current view duration (ms): 167
        >> Overall view duration (ms): 2136
        >> Current view byte size: 30648
        >> Overall view byte size: 164421
        >> Current frame rate (fps): 29.9788
        >> Current transfer rate (bps): 462136 (451 Kbps)
[DEBUG] [09-02-2021 23:31:55:252.917 GMT] postWriteCallback(): Curl post body write function for stream with handle: TokyoEbisu_BagStorage and upload handle: 17 returned: {"EventType":"RECEIVED","FragmentTimecode":1612913511282,"FragmentNumber":"91343852333181699951138633462681958899716587045"}

[DEBUG] [09-02-2021 23:31:55:253.023 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [09-02-2021 23:31:55:253.044 GMT] Reporting fragment ack received. Ack timecode<PHONE_NUMBER>282
[DEBUG] [09-02-2021 23:31:55:253.094 GMT] postReadCallback(): Wrote 30648 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:55:253.261 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:31:55:256.903 GMT] postWriteCallback(): Curl post body write function for stream with handle: TokyoEbisu_BagStorage and upload handle: 17 returned: {"EventType":"BUFFERING","FragmentTimecode":1612913512350,"FragmentNumber":"91343852333181699956090393619823480358147953908"}

[DEBUG] [09-02-2021 23:31:55:256.943 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [09-02-2021 23:31:55:256.957 GMT] Reporting fragment ack received. Ack timecode<PHONE_NUMBER>350
[DEBUG] [09-02-2021 23:31:55:364.821 GMT] postWriteCallback(): Curl post body write function for stream with handle: TokyoEbisu_BagStorage and upload handle: 17 returned: {"EventType":"PERSISTED","FragmentTimecode":1612913511282,"FragmentNumber":"91343852333181699951138633462681958899716587045"}

[DEBUG] [09-02-2021 23:31:55:364.882 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [09-02-2021 23:31:55:364.895 GMT] Reporting fragment ack received. Ack timecode<PHONE_NUMBER>282
[DEBUG] [09-02-2021 23:31:55:364.913 GMT] postReadCallback(): Wrote 5582 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:55:364.947 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:31:55:600.383 GMT] postWriteCallback(): Curl post body write function for stream with handle: TokyoEbisu_BagStorage and upload handle: 17 returned: {"EventType":"RECEIVED","FragmentTimecode":1612913512350,"FragmentNumber":"91343852333181699956090393619823480358147953908"}

[DEBUG] [09-02-2021 23:31:55:600.431 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [09-02-2021 23:31:55:600.449 GMT] Reporting fragment ack received. Ack timecode<PHONE_NUMBER>350
[DEBUG] [09-02-2021 23:31:55:600.471 GMT] postReadCallback(): Wrote 11681 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:55:600.553 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:31:55:604.957 GMT] postWriteCallback(): Curl post body write function for stream with handle: TokyoEbisu_BagStorage and upload handle: 17 returned: {"EventType":"BUFFERING","FragmentTimecode":1612913513418,"FragmentNumber":"91343852333181699961042153776965001551043981746"}

[DEBUG] [09-02-2021 23:31:55:604.985 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [09-02-2021 23:31:55:604.994 GMT] Reporting fragment ack received. Ack timecode<PHONE_NUMBER>418
[DEBUG] [09-02-2021 23:31:55:680.101 GMT] postWriteCallback(): Curl post body write function for stream with handle: TokyoEbisu_BagStorage and upload handle: 17 returned: {"EventType":"PERSISTED","FragmentTimecode":1612913512350,"FragmentNumber":"91343852333181699956090393619823480358147953908"}

[DEBUG] [09-02-2021 23:31:55:680.192 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [09-02-2021 23:31:55:680.213 GMT] Reporting fragment ack received. Ack timecode<PHONE_NUMBER>350
[DEBUG] [09-02-2021 23:31:55:680.237 GMT] postReadCallback(): Wrote 3356 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:55:680.322 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:31:56:681.080 GMT] postReadCallback(): Wrote 22074 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:31:56:681.244 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:32:17:702.257 GMT] postReadCallback(): Wrote 84 bytes to Kinesis Video. Upload stream handle: 17
[DEBUG] [09-02-2021 23:32:17:702.338 GMT] postReadCallback(): Pausing CURL read for upload handle: 17
[DEBUG] [09-02-2021 23:32:17:876.924 GMT] postWriteCallback(): Curl post body write function for stream with handle: TokyoEbisu_BagStorage and upload handle: 17 returned: {"EventType":"RECEIVED","FragmentTimecode":1612913513418,"FragmentNumber":"91343852333181699961042153776965001551043981746"}

Ah sorry I realise this issue was misreported, actually it is
Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
Error combine with for some reason microk8s not restarting the container. I will close this and re-open with more details if I cannot fix.


Enable countdown timer

I can't seem to make the countdown timer work... Are you just supposed to add the following to the config.py file:
game_start = '2016-06-02T09:00:00-0900'
game_end = '2016-06-02T16:00:00-0900'

Sorry I didn't get back to you sooner, but it would look something like:
GAME_TIME = ('2016-06-02T09:00:00-0900', '2016-06-02T16:00:00-0900')


Update Configure-intranet-forms-based-authentication-for-devices-that…

…-do-not-support-WIA.md
Adding additional parentesis. If not, entries will be registered as:
Mozilla/5.0 (Windows NT"
and
Mozilla/5.0 (Macintosh; Intel Mac OS X"

Otherwise, I approve of these changes, you are quite right.

@marcelodiiorio Please go in and review/accept the suggestions so we can do a final review pass and get the changes incorporated.

All clarified. Please proceed, if there are no more pendings.

Sorry, I lost the overview here. I cannot tell which of the two quotation uses is the correct one.

Let me clarify what is needed:
Set-AdfsProperties -WIASupportedUserAgents ((Get-ADFSProperties | Select -ExpandProperty WIASupportedUserAgents) + "Mozilla/5.0 (Windows NT)")
And
Set-AdfsProperties -WIASupportedUserAgents ((Get-ADFSProperties | Select -ExpandProperty WIASupportedUserAgents) + "Mozilla/5.0 (Macintosh; Intel Mac OS X)")
Instead of quotes, we need to add extra parenthesis. That was my mistake. Once we add this, the entries in the WiaSupportedUserAgents properties will be added as:
Mozilla/5.0 (Windows NT)
and
Mozilla/5.0 (Macintosh; Intel Mac OS X)

Thank you. It has been a somewhat stressful day for me at work today, so every positive feedback helps. I see now. I will have a check to see if it needs amending, then I'll comment again.

There it is. I just needed to get my bearings again. This is the format you use below in the same document page.

There it is. I just needed to get my bearings again. This is the format you use below in the same document page.

Thanks @illfated. Do you agree with my proposed changes then?

As soon as you go in and use the [Commit suggestion] button, I will approve.

Done.

Now, this is what confuses me:
    Set-AdfsProperties -WIASupportedUserAgents ((Get-ADFSProperties | Select -ExpandProperty WIASupportedUserAgents) + "Mozilla/5.0 (Windows NT"))

Here you have placed the quote (") before both the ending parentheses )) Compared to the other line:
    Set-AdfsProperties -WIASupportedUserAgents ((Get-ADFSProperties | Select -ExpandProperty WIASupportedUserAgents) + "Mozilla/5.0 (Macintosh; Intel Mac OS X)")

Here you have placed the quote (") between the closing parentheses. This goes against what I thought I had understood from what we discussed just before. I genuinely believed that these 2 lines were supposed to use the same format and that the Mac OS X line was the correct format.

The second one is correct. The same applies to both cases. Can you change it? If not I'll do it later. I put the correct entries in one of my previous comments.

Both entries must end with )"), like I've suggested.
That's the right format. User agent entries must not contain quotes. I ran it in different prod environments recently, achieving the expected results.

Very well, then it appears we agree on the change. Please commit the suggestion above, then we will be good to go.

Done. Thanks @illfated!

This does not appear to be done. 3 times you have marked the suggestion as a Resolved conversation (This conversation was marked as resolved by marcelodiiorio).
I will add the suggestion again. Please make sure that you are able to submit the change below (incoming).

Not sure if you are being blocked from using the [Commit suggestion] feature, but if you do, please try to edit and save that same change in your own file.

Not sure if you are being blocked from using the [Commit suggestion] feature, but if you do, please try to edit and save that same change in your own file.

It's done now. I don't know why, but It wasn't working from the mobile phone.

@illfated @marcelodiiorio  I'm going to go ahead and merge the updates. They should go live either this afternoon or tomorrow morning, depending on how long the merge takes to happen.


Remove docker-1.11 from blobs

It is hard to understand which  docker version is used from spot.

@alex-slynko thanks for PR, this change is now merged into master via the #79 PR.


Fix Codacy markdown warnings

Hopefully this fixes the Codacy markdown warnings. Need to open a PR for Codacy to run.

Looks like Codacy now reports the list indentation warnings as fixed.


[lit-next] Add tsconfig for dowleveling polyfill-support to ES5

Fixes https://github.com/Polymer/lit-html/issues/1564

lit's polyfill-support still results in some const's that I don't expect. The other ones don't. Need to investigate.

lit's polyfill-support still results in some const's that I don't expect. The other ones don't. Need to investigate.


x/mobile/cmd/gomobile: remove gomobile stripped NDK

gomobile stripped NDKs created by release.go are still smaller than the android full NDK.
But

it adds maintenance overhead.
go starts supporting more architectures so stripped NDK is no longer tiny.
some users want to choose android api level different from the default the stripped NDK contains.

I propose to remove the need of stripped NDK.
Now gomobile can reuse cached NDKs, so I don't expect the tool to require users to download it for every init command.
Unclear issue is
what to do about open-AL tar file gomobile init also downloads?
@crawshaw @eliasnaur @rakyll

Is it too naive to attempt to build the openal libraries during gomobile init?

that's what i am thinking as well but according to what's in cmd/gomobile/release.go,
building open-al requires 'cmake'. I don't know how easy to set it up.

Another case, I talked to someone at gophercon that customizes ndk to compliment their android fork. As @rakyll mentions on #14618 I agree this should be settable as an env var.


Notes on team meeting 28/02/2024

validation currently occurs across rawdata and derivatives. I think this is actually okay (because duplicate names should not occur between derivatives and rawdata) but it can lead to confusing validation errors
Name validation occur across the whole project. So if there is an invalid name in the project it will error even if the current name in the input is okay
When transerring entire project, there are two transfer logs (one for rawdata, one for derivatives) which is confusing

TODO: address these quickly or spin out into standalone issues

[ ] It is not clear in which order to 'setup SSH' and when to save. It would be much clearer to display a pop-up on 'saving' when SSH is chosen and then prompt to setup SSH. The 'Setup SSH' button can then appear, as well as a 'Go to project Screen' button. The 'Go To Project Screen' button can also appear for local filesystem. On the Configs screen from the project manager tab, we can have the button under some other name.
[ ] For SSH remove rather than grey-out the 'Select' button that appears next to the central path button
[ ] For the TUI (and, actually, the API) take only the parent folder and automatically create the project name folder provided. This parent folder must exist.  This avoids having to input duplicate information and makes it much clearer what neeeds to be done. Make it clear what you are selecting both in the tooltip as well as the 'Selct' tree screen.
[ ] Make 'Close' and 'Main Menu' consistent. They should just say 'Back' and be located in a consistent position (top left, or possibly right if this interferes with the DirectoryTree).
[ ] make the banner on 'Make new project' say 'Make new project' not 'Configure new project'.
[ ] Although spaces in project name are caught, check for all special characters. Consider online validation.
[ ] Hide all hidden folders in the directorytree select, at least the 'Select' ones. Maybe just hide all, cannot envision why these would ever be necessary to display.
[ ] Lookin into what CTRL+SHIFT+N is doing - on some screens allows writing commands into the terminal
[ ] Check the warning provided for invalid local / central path (datashuttle side). It is not clear as the second line is close to duplicating the first - merge these.
[ ] Make clear in docs it is necssary to click / hover for input box and directorytree shortcuts.
[ ] Add tooltips to as many widgets as possible / required.
[ ] Move the 'Overwrite old files' option as a toggle on the transfer tab. Keep it persistent. Rename it to 'Overwrite Existing Files'. Add a tooltip (+ existing documentation) to make it extremely clear what this does. Consider an additional argument to transfer optiosn that will overwrite the global setting.
[ ] Add a window explaining shortcut commands + datashuttle tabs. This could be in little ? boxes or something similar on the relevant pages.
[ ] Change global font in .tcss? might be terminal-emulator specific.
[ ] Have somewhere to include a list of files / folders to never transfer (similar to gitignore) e.g. people may have trained models or large data they want to exclude from transfer.
[ ] A way to rename folders through the DirectoryTree
[ ] Look into validation and make it clearer - should really only operate on the names not the whole project. For example, if an invalid folder name is in the folder it iwill show up as a validation error.
[ ] Having an invalid folder name and then trying to CTRL+A or double click on the input raises an actual, breaking error.
[ ] Add gitpyton as a dependency to get better git logging
[ ] Have most recent logs at the top of the filetree
[ ] For directorytree's have a little 'refresh' button in the corner rather than using CTRL+R.
[ ] The TCSS on the transfer status legend in light mode is still for dark mode
[ ] Just make the show transfer tree appear with local filesystem but not SSH, doc that somewhere. Remove it from 'Settings', then make light/dark mode toggable somewhere on the home screen. Then remove 'Settings tab.
[ ] Have set of template 'templates' for named templates (lol) that can be easily insterted rather than using regexp
[ ] Add docs on the concident transfer issue.
[ ] Sampel script for API users, don't focus fully on API when doing outreach.

TODO: add validation for renaming sub- or ses- folders


how to generate train and val pickle files

Firstly, thank you for great project. It would be nice if you can explain how to generate the  triain and val pickle files in https://github.com/weiyithu/SurroundOcc/blob/main/docs/data.md.  @weiyithu

Hi, you can try this: python tools/create_data.py nuscenes --root-path ./data/nuscenes --out-dir ./data/nuscenes --extra-tag nuscenes --version v1.0 --canbus ./data


MathJax not always rendering.

Have you checked that your issue isn't already filed?

[X] I read through FAQ and searched through the past issues, none of which addressed my issue.
[X] Yes, I have checked that this issue isn't already filed.

Bug description
MathJax does not render after refreshing the page once. There is a JS error.
How to reproduce the bug
I'm not sure what's unique about my distill page in particular, but if you visit https://alexzhang13.github.io/blog/2024/annotated-kan/ and refresh the page, the MathJax won't render anymore. When I render the default distill page, this isn't an issue.
Error messages and logs
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'replaceChild')
    at e.replace (tex-mml-chtml.min.js:5:6799)
    at e.updateDocument (tex-mml-chtml.min.js:5:192956)
    at t.updateDocument (tex-mml-chtml.min.js:5:41366)
    at e.updateDocument (tex-mml-chtml.min.js:5:185993)
    at e.updateDocument (tex-mml-chtml.min.js:5:699183)
    at Object.renderDoc (tex-mml-chtml.min.js:5:34972)
    at e.renderDoc (tex-mml-chtml.min.js:5:35195)
    at t.render (tex-mml-chtml.min.js:5:38146)
    at tex-mml-chtml.min.js:5:22264
    at e (tex-mml-chtml.min.js:5:727971)

What operating system are you using?
Mac
Where are you seeing the problem on?
Deployed site
More info
This issue also occurs on the local website as well -- it isn't a deployed site exclusive issue.

I've run into this as well. It happens non-deterministically.
On the occasion it has happened, I noticed the following console error message indicating mathjax checksum was not loaded successfully:

Failed to find a valid digest in the 'integrity' attribute for resource<EMAIL_ADDRESS>with computed SHA-256 integrity 'YyRhy+F3bG+zvvwsW1E/uy5s5pKXwmG/bOPlV+1pt6o='. The resource has been blocked

@orm011 Yeah this is also how I got around it temporarily. Actually, the original error above had to do with trying to use colors in MathJax, which for some reason it doesn't really like. I then ran into the issue you described.
I'm not really proficient in web-dev so I don't know the dangers of not including the integrity attribute, but for now it seems fine.

Can you guys test if https://github.com/alshedivat/al-folio/commit/d019fc0f18d51c7c378f34e4432b38529b506ead fixes this? I made a mistake when using mathjax dependencies.

I tried your fixes and they seem to work.


Issues building openvdb static libs on Windows

Hi there,
So I'm trying to build openvdb on Windows (static libs not DLLs).
I have the latest and greatest copy of the depot and ran:
vcpkg install tbb openexr blosc zlib boost --triplet x64-windows-static
then:
cmake -DCMAKE_TOOLCHAIN_FILE=C:\vcpkg\scripts\buildsystems\vcpkg.cmake -DVCPKG_TARGET_TRIPLET=x64-windows-static -A x64 -DUSE_STATIC_DEPENDENCIES=ON -DOPENVDB_CORE_SHARED=OFF -DUSE_WINDOWS_STATIC_RUNTIME=ON  ..
and got this:
# cmake -DCMAKE_TOOLCHAIN_FILE=C:\vcpkg\scripts\buildsystems\vcpkg.cmake -DVCPKG_TARGET_TRIPLET=x64-windows-static -A x64 -DUSE_STATIC_DEPENDENCIES=ON -DOPENVDB_CORE_SHARED=OFF -DUSE_WINDOWS_STATIC_RUNTIME=ON  ..
-- Selecting Windows SDK version 10.0.17763.0 to target Windows 10.0.18363.
-- CMake Build Type: Release
-- Suppressing some noisy MSVC CXX warnings, set OPENVDB_CXX_STRICT=ON to re-enable them.
-- Configuring for OpenVDB Version 7.1.0
-- Configuring for OpenVDB ABI Version 7
-- ----------------------------------------------------
-- ------------- Configuring OpenVDBCore --------------
-- ----------------------------------------------------
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Error at C:/Program Files/CMake/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164 (message):
  Could NOT find Blosc (missing: Blosc_LIBRARY) (found suitable version
  "1.17", minimum required is "1.5")
Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:445 (_FPHSA_FAILURE_MESSAGE)
  cmake/FindBlosc.cmake:190 (find_package_handle_standard_args)
  C:/usr/vcpkg/scripts/buildsystems/vcpkg.cmake:286 (_find_package)
  openvdb/CMakeLists.txt:87 (find_package)

Any ideas what I'm doing wrong here?
Regards,
Tom

I did try version 7.0.0 but ran into issues with tbb_debug.lib as mentioned in https://github.com/AcademySoftwareFoundation/openvdb/issues/668, hence why I've tried the latest code.

The static build on Windows is missing some CMake support which is not yet in the master branch. See this thread https://github.com/AcademySoftwareFoundation/openvdb/issues/627
and this PR:
https://github.com/AcademySoftwareFoundation/openvdb/pull/654
If you can, give it a shot with those changes

That helped a bit. I now get:
libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol LZ4_decompress_safe referenced in function lz4_wrap_decompress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol LZ4_compress_fast referenced in function lz4_wrap_compress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol LZ4_compress_HC referenced in function lz4hc_wrap_compress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol snappy_compress referenced in function snappy_wrap_compress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol snappy_uncompress referenced in function snappy_wrap_decompress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol snappy_max_compressed_length referenced in function blosc_c [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol ZSTD_compress referenced in function zstd_wrap_compress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol ZSTD_decompress referenced in function zstd_wrap_decompress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol ZSTD_isError referenced in function zstd_wrap_compress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] libblosc.lib(blosc.c.obj) : error LNK2019: unresolved external symbol ZSTD_maxCLevel referenced in function zstd_wrap_compress [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj] C:\vcpkg\openvdb\build\openvdb\cmd\Debug\vdb_print.exe : fatal error LNK1120: 10 unresolved externals [C:\vcpkg\openvdb\build\openvdb\cmd\vdb_print.vcxproj]
when running:
cmake --build . --parallel 4 --config Debug --target install
Any idea how I can fix that?

Ah that's for vdb_print which I don't think I need.

Can you try adding -DBLOSC_USE_EXTERNAL_SOURCES=ON to your CMake command (again, only part of the #654 PR)

Does openvdb support building with "Multi-threaded Debug DLL (/MDd)"?
I noticed in openvdb/CMakeLists.txt that you specify /MT.  Using the CMake generated projects, I swapped to /MDd in the Visual Studio Project Settings but when I built I got the following errors:
>C:\vcpkg\openvdb\openvdb\Grid.cc(19): error C2491: 'openvdb::v7_1::GridBase::META_GRID_CLASS': definition of dllimport static data member not allowed 1>C:\vcpkg\openvdb\openvdb\Grid.cc(20): warning C4273: 'META_GRID_CREATOR': inconsistent dll linkage 1>c:\vcpkg\openvdb\openvdb\Grid.h(351): note: see previous definition of 'public: static char const * const openvdb::v7_1::GridBase::META_GRID_CREATOR' 1>C:\vcpkg\openvdb\openvdb\Grid.cc(20): error C2491: 'openvdb::v7_1::GridBase::META_GRID_CREATOR': definition of dllimport static data member not allowed 1>C:\vcpkg\openvdb\openvdb\Grid.cc(21): warning C4273: 'META_GRID_NAME': inconsistent dll linkage 1>c:\vcpkg\openvdb\openvdb\Grid.h(352): note: see previous definition of 'public: static char const * const openvdb::v7_1::GridBase::META_GRID_NAME' 1>C:\vcpkg\openvdb\openvdb\Grid.cc(21): error C2491: 'openvdb::v7_1::GridBase::META_GRID_NAME': definition of dllimport static data member not allowed 1>C:\vcpkg\openvdb\openvdb\Grid.cc(22): warning C4273: 'META_SAVE_HALF_FLOAT': inconsistent dll linkage 1>c:\vcpkg\openvdb\openvdb\Grid.h(353): note: see previous definition of 'public: static char const * const openvdb::v7_1::GridBase::META_SAVE_HALF_FLOAT' 1>C:\vcpkg\openvdb\openvdb\Grid.cc(22): error C2491: 'openvdb::v7_1::GridBase::META_SAVE_HALF_FLOAT': definition of dllimport static data member not allowed
Regards,
Tom

Does openvdb support building with "Multi-threaded Debug DLL (/MDd)"? I wonder if you don't support this due to some dependant libraries not supporting MDd as well?

Hi @thomasmfields - as of CMake 3.15 you can use the CMAKE_MSVC_RUNTIME_LIBRARY to control the MSVC Runtime selection . I've just merged #708 which removes the manual specification of /MT as you pointed out and instead reads for this variable. Whilst OpenVDB should build with any value of CMAKE_MSVC_RUNTIME_LIBRARY  e.g. /MDd) there might be issues with how its finding dependencies compatible with Windows's Debug Runtime. I'm unsure how stable /MDd or /MTd are, but it would be worth trying with the latest changed.
More on this CMake variable here:
https://cmake.org/cmake/help/latest/variable/CMAKE_MSVC_RUNTIME_LIBRARY.html

Hi @Idclip - thanks for the update. I just tried this but unfortunately, it doesn't work. During the build I'm getting:
Half-2_3.lib(half.cpp.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MD_DynamicRelease' in Grid.obj [C:\usr\vcpkg2020_04\openvdb\build\openvdb\openvdb_shared.vcxproj]
tbb.lib(task.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MD_DynamicRelease' in Grid.obj [C:\usr\vcpkg2020_04\openvdb\build\openvdb\openvdb_shared.vcxproj]
etc, etc.
I used:
cmake -DCMAKE_TOOLCHAIN_FILE=C:/usr/vcpkg2020_04/scripts/buildsystems/vcpkg.cmake -DCMAKE_MSVC_RUNTIME_LIBRARY=MultiThreadedDLL -DVCPKG_TARGET_TRIPLET=x64-windows-static -A x64 -DUSE_STATIC_DEPENDENCIES=ON ..
then:
cmake --build . --parallel 4 --config Release --target install
Maybe you can test this locally?

Hi @thomasmfields - what you're reporting doesn't seem to be a problem with the OpenVDB build system. The message doesn't match value 'MD_DynamicRelease' in Grid.obj infers that VDB is correctly being built with /Md. However the OpenEXR and TBB dependencies that are being found have been built with /MT (Half-2_3.lib(half.cpp.obj) and tbb.lib(task.obj) - detected for 'RuntimeLibrary': value 'MT_StaticRelease'). These are incompatible with each other - all libraries need to be built against the same MSVC runtime.
With vcpkg specifically, it's my understanding that packages installed with the VCPKG_TARGET_TRIPLET=x64-windows triplet are built by default with /Md - however packages with the VCPKG_TARGET_TRIPLET=x64-windows-static triplet (the one you're using) are built with the /MT triplet. I'd recommend either trying to use -DCMAKE_MSVC_RUNTIME_LIBRARY=MultiThreaded or re-installed your dependencies through vcpkg with ``VCPKG_TARGET_TRIPLET=x64-windows`

Hi @Idclip - what I'm after is a build of openvdb and all its dependencies as .lib files that I can include and link in a project that is built using Runtime Library: Multi-threaded DLL (/MD). This is why I was using VCPKG_TARGET_TRIPLET=x64-windows-static.  What would be the build instructions for that?
At the moment I have openvdb .lib files but I have to put them in a /MT project which outputs a DLL and interface with the library like that. I'd like to just link the libs into my main project as normal.

I'm not sure if I've understood correctly, so I apologise if I'm being too verbose with this explanation:
It's important not to confuse /MD (MultiThreadedDLL) and /MT (MultiThreaded) with Static or Dynamic library variants. You can build a static and shared library with /MD or with /MT. This /M option is the simply the link time selection of the MSVC C++ Runtime library which must match across absolutely every single library you use. Typically, it doesn't make much sense to build a static library with /MD (and vice versa), so most build systems will default the runtime selection depending on the type of library you want to build. This is what vcpkg does. By selecting VCPKG_TARGET_TRIPLET=x64-windows-static you're asking vcpkg for static libraries (just a .lib, no .dll). This implicitly builds with /MT. When configuring OpenVDB, OpenVDB will configure both a static and shared variant. Both will build against the same MSVC C++ Runtime variant you select. You'll produce 3 artefacts. The static build will produce a libopenvdb.lib. The dynamic builds will produce both an openvdb.lib and an openvdb.dll (dynamic libraries on Windows need both a .lib which acts as an import and a runtime .dll). You can disable the static or dynamic library configuration with:
-OPENVDB_CORE_SHARED=ON/OFF # shared libs
-OPENVDB_CORE_STATIC=ON/OFF # static lib
By default, they're both on.
It sounds like you want to build with /MD but use static dependencies? This would be absolutely fine - except that vcpkg is building all static variants (with the  VCPKG_TARGET_TRIPLET=x64-windows-static) with /MT. The x64-windows triplet (without the -static suffix) builds dynamic libraries with /MD. I'm by no means an expert on vcpkg so I'm afraid I don't know if it's possible to further customize these options, you'll have to ask the vcpkg devs or take a look through those docs. If it's not and you want to build static libs with /MD, you may have to build all of the libraries you need from source yourself.

Closing due to inactivity - @thomasmfields please absolutely re-open if you have further questions or comments


dreambooth updates

Train dreambooth and inference. I created LatentDiffusionDreamBooth instead of using LatentDiffusionDB because LatentDiffusionDB rewrites many functions.

@SamitHuang @zhaoyuzhi @DongyaoZhu @zhanghuiyao Feel free to review. I forgot to add reviewers ahead.

is it possible to add scripts for finding rare token identifiers?

Look nice overall!
Please also complete the quantitative evaluation using metrics like CLIP-T (same as the implemented CLIP score), CLIP-I, and enrich the comparison results~

is it possible to add scripts for finding rare token identifiers? can wait until this pr is merged

Sure, finding rare token identifier automatically will be the option for the user in the future. Once this PR is merged, I will work on this.

Look nice overall! Please also complete the quantitative evaluation using metrics like CLIP-T (same as the implemented CLIP score), CLIP-I, and enrich the comparison results~

The current todo items include the qualitative comparison between naïve finetuning vs.. dreambooth.
As for the quantitative evaluation, the results make more sense when the dreambooth is trained with multiple subjects (e.g., 30 in the dreambooth paper) and we averaged the  CLIP-T and  CLIP-I scores. I'm wondering whether it's worth it, because diffuser  does not provide quantitative results nor qualitive results for dreambooth.


LSP type info on hover shows type of result instead of expression when using backpassing

What Git revision are you using?
1.0.26
What operating system are you using, and which version?

[x] Linux / Ubuntu
[x] Linux / Other
[x] macOS
[x] Windows

Describe what the problem is?
The lsp hover shows Bool instead of the actual type. This is due to it inferring the validator type.
What should be the expected behavior?
The actual type of the function or its arguments based on where my mouse hovers over

so this is definitely related to backpassing

Fixed in #999


ENH: stats.sem: add array-API support

Reference issue

towards #20544
What does this implement/fix?

makes sem array-API compatible.
Additional information

It also occured to me that the existing tests don't check axis at all. I guess it's OK to leave it that way... At some point we'll give array API support to _axis_nan_policy and its tests, and those will cover it.

Are you happy with this? Seems pretty straightforward, so I can merge when the last test finishes.

Are you happy with this? Seems pretty straightforward, so I can merge when the last test finishes.

Yes all good from my end


Add a timeout snapshot function

The best way I can find to investigate https://dev.azure.com/dnceng-public/public/_build/results?buildId=24183&view=results failure.
Devenv is showing some diag when resetting the settings. When the test timeout is reached, we don't anything about that.
So adding a separate thread to capture the screen every X minutes when waiting for devenv to exit.

Is there anyway to test this change locally? (I guess maybe build a NuGet package and consume it locally?)

I don't have write permission : ) @sharwell  can you merge this in?


tools: NeuVector: introducing NeuVector (REST) scan type

This commit adds the support of NeuVector
(https://github.com/neuvector/neuvector) tool for importing scan results. Scan results can be exported via REST API in JSON format (that is why the tool is named 'NeuVector (REST)'). There is no GUI for that at the moment.
Scan results are just a list of issues found in packages installed in a container or an image. Very similar to Twistlock.
NeuVector also provides compliance scan results. This is not supported by the introduced tool.

I could use this.  Thanks for adding


Add API for getting which visible paragraph index the caret is on

currentParagraph is used to get the caret's paragraph index in terms of the total paragraphs, but now that #501 has been merged, there's not a counterpart for determining the caret's paragraph index in terms of the visible paragraphs. It should be Optional<Integer> currentVisibleParagraph

This is also something that can be done via #600.


Replace lombok JSONified data classes with autovalue.

There's still a lot of lombok in the code that will need to get replaced in a future PR for Java 9+. Upgrading lombok broke a lot of data classes, seemingly all the ones that act as JSON data objects. I replaced many of those with AutoValue and removed any unnecessary lombok annotations in the classes.
I've also removed any tests that were solely checking whether the lombok @Data annotation worked. The test helper for that used a bunch of reflection that breaks in Java 9+, and doesn't seem to add value to the test suite. If those classes compile, they would pass the test (at least in Java 8).

Ah, that makes sense. I should go back through and update those tests then.


Random generated circuit cannot be cut

I randomly generated a 10-bit quantum circuit with a depth of 88 and a number of two-qubit gates of 49, However, the cutting method cannot be found using the mip cutting searcher，What is the reason for this？
Here is my qasm file and  code
random_qasm.txt
cuts = cut_circuit_wires(     circuit=circuit,     method="automatic",     max_subcircuit_width=9,     max_cuts=100,     num_subcircuits=[i for i in range(2, 10)], )
The error message is：

This is the figure of circuit

Cutqc is deprecated and no longer supported.  Please use the new cut finder introduced with the 0.7 release series.

Closing all CutQC issues now that it has been removed.


Remove CollectorFieldsVisitor

Summary of the changes / Why this improves CrateDB
The addField functionality wasn't used and what was left was basically
equivalent to what the SourceLookup already does.
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed

retest this please


Updated the AdColony calls to Android 2.2.1 and iOS 2.5.0

As part of this, I have managed to debug a couple of launch issues I was having with iOS... where AdColony was complaining it was being initialized in a background thread. Whilst it is not ideal to foreground thread this, apparently it is necessary. Tested on Android and iOS devices (physical and emualted)

You need to add the AudioToolbox.framework AND the WebKit.framework to the resulting xcode project (previously only the AudioToolbox was required)

I've had issues initializing on iOS as well so glad to know this might be a fix.  I'll update the framework dependencies in plugin.xml and bump the version so people hopefully notice they should reinstall the plugin.


add action to release docs

Hi @kshtsk, Guna mentioned that the use of GHCR is for testing purposes only. Given that's the case, is it correct to assume removal of the existing drone.yml happens at a later time?

Hi @kshtsk, Guna mentioned that the use of GHCR is for testing purposes only. Given that's the case, is it correct to assume removal of the existing drone.yml happens at a later time?

Hi @btat
I don't know about what are the plans, what I understand it is going to move this part of infra to a new cluster, and one of the option of improving the process is to migrate building of containers closer to the respecting repos, in particular, use the actions as much as possible, which could follow to discontinue drone usage, so as soon as 'actions' work the .drone.yml can be dropped. Since building containers is going to happen in actions, then it is reasonable to push images to GHCR. Later on we can switch infra to use GHCR instead dockerhub or other, however it is not decided it yet, as I understood from Paul's words. Now, since actions do not interfere the drone jobs, there is no acute need to drop its config now.


Refused to load script

Getting this error when ever loading the extension:
"Refused to load the script 'chrome-extension://a5359a9d-e2f9-46a3-a0e5-0911e6083ec5/assets/index.tsx-B39MazF-.js' because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' http://localhost:* http://<IP_ADDRESS>:*". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback."

Hi @huzaifa-bilal-01, thanks for opening the issue.
Could you please provide more information on your system and what steps you have already taken to fix the problem?
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Steps/attempts taken to fix
Add the steps you have attempted to fix your problem here.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows, Linux, MacOS] including version
Browser [e.g. chrome, firefox] including version

I had the same issue yesterday. After upgrading Chrome, the problem was resolved.
My current Chrome version is: Version 130.0.6723.70 (Official Build) (arm64).

I had the same issue yesterday. After upgrading Chrome, the problem was resolved. My current Chrome version is: Version 130.0.6723.70 (Official Build) (arm64).

Chrome is up to date
Version 130.0.6723.70 (Official Build) (64-bit)
My chrome is up to date but still getting the same error.

Hi @huzaifa-bilal-01, thanks for opening the issue.
Could you please provide more information on your system and what steps you have already taken to fix the problem?
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior A clear and concise description of what you expected to happen.
Steps/attempts taken to fix Add the steps you have attempted to fix your problem here.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Windows, Linux, MacOS] including version
Browser [e.g. chrome, firefox] including version

Thanks for your response! Below is the information related to the issue I encountered:
BUG:
When loading extension, I receive the following error message in the console:

It seems like the extension is blocked from loading its own script due to the CSP settings.
TO REPRODUCE:
Steps to reproduce the issue:

Install the extension locally.
Load the extension in Chrome.
Open the browser console.
Reload the page where the extension is active.
See the CSP error in the console.

EXPECTED BEHAVIOUR:
I expect the extension to load its own script (content script) without being blocked by the CSP, allowing it to function correctly.
DESKTOP:
OS: Windows 10, Windows 11
Browser: Chrome (Version 130.0.6723.70), Edge (Version 130.0.2849.46), Brave (Version <IP_ADDRESS>)
NOTE: It is working fine on the opera or opera gx browser.

@huzaifa-bilal-01 Thanks for bringing this to my attention.
Looks like Chrome updated their CSP with a recent browser update.
Should be fixed within the most resent version of this template repository.
If you want to fix it in your project without creating a new project from this template, you will need to update the package @crxjs/vite-plugin from the current version to<EMAIL_ADDRESS>Let me know if this works for you.

@huzaifa-bilal-01 Thanks for bringing this to my attention.
Looks like Chrome updated their CSP with a recent browser update.
Should be fixed within the most recent version of this template repository.
If you want to fix it in your project without creating a new project from this template, you will need to update the package @crxjs/vite-plugin from the current version to<EMAIL_ADDRESS>Let me know if this works for you.

Yeps this worked. Thanks 👍

Awesome!
Closing.


Update dependency pulumi_cli to v3.49.0

This PR contains the following updates:

Package
Type
Update
Change

pulumi_cli
http_archive
minor
v3.48.0 -> v3.49.0

Release Notes

pulumi/pulumi
v3.49.0
Compare Source
3.49.0 (2022-12-08)
Features

[sdk] Add methods to cast pointer types to corresponding Pulumi Ptr types
#11539

[yaml] Updates Pulumi YAML to v1.0.4 unblocking Docker Image resource support in a future Docker provider release.
#11583

[backend/service] Allows the service to opt into a bandwidth-optimized DIFF protocol for storing checkpoints. Previously this required setting the PULUMI_OPTIMIZED_CHECKPOINT_PATCH env variable on the client. This env variable is now deprecated.
#11421

[cli/about] Add fully qualified stack name to current stack.
#11387

[sdk/{dotnet,nodejs}] Add InvokeSingle variants to dotnet and nodejs SDKs
#11564

Bug Fixes

[docs] Exclude id output property for component resources
#11469

[engine] Fix an assert for resources being replaced but also pending deletion.
#11475

[pkg] Fixes codegen/python generation of non-string secrets in provider properties
#11494

[pkg/testing] Optionally caches python venvs for testing
#11532

[programgen] Improve error message for invalid enum values on pulumi convert.
#11019

[programgen] Interpret schema.Asset as pcl.AssetOrArchive.
#11593

[programgen/go] Convert the result of immediate invokes to ouputs when necessary.
#11480

[programgen/nodejs] Add . between ? and [.
#11477

[programgen/nodejs] Fix capitalization when generating fs.readdirSync.
#11478

[sdk/nodejs] Fix regression when passing a provider to a MLC
#11509

[sdk/python] Allows for duplicate output values in python
#11559

[sdkgen/go] Fixes superfluous newline being added between documentation comment and package statement in doc.go
#11492

[sdkgen/nodejs] Generate JS doc comments for output-versioned invokes and use explicit any type.
#11511

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: undefined
Command failed: CARGO_BAZEL_REPIN=1 yarn bazel sync --only=cargo
error Command "bazel" not found.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


230 add public or private option to dataset

I am opening this as a draft pull request. My plan is to limit the scope of this particular issue to being able to make datasets public (visible to everyone) or private (visible to user only),  giving users the ability to change status and having the public ones show and the private ones hidden. Giving users other than the creator the ability to do anything but view a public dataset will be saved for later.
Right now I need to replace the text input for status with a dropdown. Will look for feedback,.

@tcnichol @lmarini Is this ready for review? I see it's in draft state

I need to merge in main and make a few small fixes, then this should be ready.

I'm marking this one ready for review.
You can now select between status of PUBLIC or PRIVATE with a SHARED option currently commented out. I wanted to make sure this was a dropdown and not a text input. Current behavior is that if a dataset is PUBLIC anyone can see it, and PRIVATE only the creator can share it. Other options would need to wait for roles to be enabled to work.
Visually it's not that great, so hoping to get some feedback to make it look better and more consistent with the rest of the front end design.

Luigi, I was unable to replicate that error.
Will also be putting a check in place where (for now) only the owner can change something from private to public or back again. This will probably need to be changed once permissions are implemented, but would make sense for now.

@tcnichol not sure why, but I am also not able to replicate that exact error. Sorry for the confusion, I must have not had the latest version.
I think I am seeing something related. If I switch one dataset and that dataset is set to public, I think that's the default if I go to switch another dataset, instead of the current state of that dataset.

Do you still want to add the check so that only owner can switch state to this PR?

Luigi,
Right now only the owner being able to change status is enforced on the backend. I think it would be ideal if the option doesn't even appear on t


{"code": -32000, "message": "JSON Parse error: Unexpected token: H"}

at dapp demo. [feat/dapp-universal-provider]
web3Provider.getBalance(currentAccount).then((balance) => {
  let etherString = ethers.utils.formatEther(balance);
  console.log("Balance-: " + balance);
  console.log("Balance: " + etherString);
}).catch(err=>{
  console.log("err");
  console.log(err);
});

both etherjs and web3js. this issue occurs -> {"code": -32000, "message": "JSON Parse error: Unexpected token: H"}
seems like there s something wrong in @walletconnect/universal-provider.

Thanks @KayCm, was able to reproduce and will look into it.

Same problem for me

We are having the same issue over here, do you have any updates on this/could you guide us on how to fix it ourselves?

Same here. tried with both ethers and web3. Almost every method leads to this error.
Can someone pinpoint the initial emitter of the error? that would help start debugging
const web3Provider = new ethers.providers.Web3Provider(provider.current)
const signer = web3Provider.getSigner()
const from = await signer.getAddress()
const contract = new ethers.Contract(contractAddress, contractABI(token.type), signer)
const txt = await contract.functions.transferFrom(from, to, tokenId)

Hi @StevenBarnett1 @sebastian-sanchez-variv @pinki-palacios
We are currently debugging it, apparently it's not an issue with react-native because we could reproduce it also in react. We'll keep you all updated, as it's an important issue.

Thanks @ignaciosantise!
Not sure if this is useful. But we found out that this call
https://github.com/WalletConnect/walletconnect-monorepo/blob/v2.0/providers/universal-provider/src/UniversalProvider.ts#L72
It's throwing a more readable error. Maybe it rings a bell
[Error: invalid BigNumber value (argument="value", value=undefined, code=INVALID_ARGUMENT, version=bignumber/5.7.0)]

Hey @pinki-palacios, fix will be merged in #25
For now, go to the UniversalProvider config an uncomment and change to an empty brace
universalProviderSession = await universalProvider.connect({
      namespaces: {
        eip155: {
          methods: [
            'eth_sendTransaction',
            'eth_signTransaction',
            'eth_sign',
            'personal_sign',
            'eth_signTypedData',
          ],
          chains: ['eip155:1'],
          events: ['chainChanged', 'accountsChanged'],
          rpcMap: {},
        },
      },
    });


Fixed debug mode for UnicodeDecodeError

Why silence the error in debug mode?

A Trac ticket is needed to explain the issue. A regression test is also required. Pull requests should be sent to master, not against a stable branch. Thanks!


Event handler

Is your feature request related to a problem? Please describe.
There is no building feature to raise events
Describe the solution you'd like
Event handler
Describe alternatives you've considered
👍
Additional context
👋

Some different event types would be usefull,
I suggest:

Timer Events
Action Events
Collision Events
Input Events


[Question] How can I get H_{v} (projected image feature) ?

Question
I'm trying to leverage feature vector from LLaVA for my research. How can I get projected image feature H_{v}?

I found it on llava_arch.py.


MedeBoss submission

any othe description please.time is under endurement.[ca]make+made
(You can replace all of this text with your description.)
Before creating your pull request, please check your content against these quality criteria:

Did you consider search engine optimization (SEO) when you chose the title in the metadata section and the H1 heading (i.e. the displayed title that starts with a single #)?
For new articles, did you add it to the table of contents?
Did you update the "ms.date" metadata for new or significantly updated articles?
Are technical terms and concepts introduced and explained, and are acronyms spelled out on first mention?
Should this page be linked to from other pages or Microsoft web sites?

For more information about creating content for docs.microsoft.com, see the contributor guide at https://docs.microsoft.com/contribute/.

admission


any performance benchmark?

curious on use cases where it is faster to be used

You mean in which cases being NUMA aware would be an improvement to Go code in general?

FYI I'm archiving this project fork, but of course, you can move the discussion upstream to https://github.com/lrita/numa


Mocha test case Couldn't able to coverage on customFilterListRender and customSort (MUIDataTable). Anyone please quide me. Give an example for mocha test cases for customFilterListRender  and CustomSort

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

1.customFilterListRender: value =>XXX
2. .customSort: (data, colIndex, order ) => {
3.
4.
Your Environment

Tech
Version

Material-UI

MUI-datatables

React

browser

etc

I'm not able to understand what problem you're experiencing. Is there a way you can rephrase it?

So, if you're looking to test your own custom code, I think you might be better served by asking in a testing, mocha-focused forum. The issues raised here are primarily for those that are specific to this library, in that there's a bug, or a feature request, or a question about how to use a feature. Testing your code, be it code that is used with this library or not, sounds like it's out of scope.
In addition, you wouldn't really want to test that another library functions properly as part of your own test suite. That's very difficult to do because you don't have access to the internals of the particular library you're using, and you would need to rely on that library to do its own testing. For example, if you're using lodash.merge, you wouldn't test that lodash.merge works directly. You'd only test one of your own project features that may or may not be using such a utility function. If you test all the implementation details, including those of other libraries, then you're tied to specific implementations and libraries, and you can't change them later. For example, you might want to switch table libraries, or lodash for underscore, or something like that.
If the customSort and/or customFilterListRender features of this library aren't tested enough for your liking, I'd be more than happy to review a PR that adds testing to this library. Otherwise, I'll probably need to close this issue as being out of scope.


MacOS versíon fails to launch properly - 'Damaged - eject disk image'

The disk image opens OK, but if I try to launch directly from the disk image, I get this error...
Is it the case that this app MUST be in the applications folder?

The app isn't signed because I can't afford to sign it, so general convenience features in macOS might just not work.


demo.ipynb: several audio (output) clips are silent?

Christian, this is wonderful.  I look forward to learning how we can train differentiable audio effects using your system.
For now I'm just going through the demo notebook, and after the text that reads

"We will apply our processing on the guitar signal from before in the exact same way, except this time we will call the process() method of the channel. Before we apply the processing with the default settings, let's change the equaliser and compressor (by default they will do no processing)."

...there are two code blocks, followed by two audio samples.  The second audio clip is silent for me.  Is that to be expected?   I'm also noticing silence for the second clips in the pairs of audio clips accompanying the Panner, the Delay, and the Reverb.
Perhaps I should mention, I see the following warning somewhat regularly; not sure what its consequences are:
> /home/shawley/env_pymix/lib/python3.8/site-packages/pymixconsole/processors/convreverb.py:88: WavFileWarning: Chunk (non-data) not understood, skipping it.
  sr, h = wavfile.read(filename)   # load the audio file for correct impulse response

AH! I see, I should be trying out your compressor example in auraloss anyway!  I'll switch over to that for a while...

Hey Scott. This works for me when loading the notebook into Google colab. I have noticed inconsistent behavior with how the audio gets rendered in the notebook when using colab vs. local. I am not sure of the exact cause. I would try loading this notebook in colab though to see if you get the same results.
The warning message that you see does show for me as well, but that should not impact the results. Thanks for checking out the repo.


Some options appear to not have any effect

Raising issue as part of JOSS review https://github.com/openjournals/joss-reviews/issues/5428
Some of the options documented at https://acerbilab.github.io/pyvbmc/api/options/vbmc_options.html do not appear to have any corresponding active code paths which use them. From some limited scanning, those that I've come across which this appears to apply to are:

retry_max_fun_evals
optim_toolbox
repeated_acq_discount - this appears to have been used at one point but the relevant code block is now commented out https://github.com/acerbilab/pyvbmc/blob/b7c6e381be75dd508ac9663825fd77ed8885816d/pyvbmc/vbmc/active_sample.py#L465

Hi @matt-graham, thanks for pointing these out. As you've probably guessed, these options are from the MATLAB implementation but are unused in this implementation, at least for the time being. To avoid confusion we removed them just now in pull #140.


Dockerlab assignment: port number conflict

two applications are running on port 8080

Not an issue anymore as Jenkins is the only application running on port 8080 now.


Border class repr error

Hi,
I can't print the border objects
Example:
from energyquantified.metadata import Area
areas = Area.by_tag('GB')
borders = areas.borders
print(borders)

Error:
energyquantified\metadata\area.py in __repr__(self)
     277             self.sink.tag,
     278             # self.allocations,
 --> 279             sorted(self.allocations),
     280         )
     281
TypeError: '<' not supported between instances of 'Allocation' and 'Allocation'

Looks like the Allocation class doesnt have the dunder methods for less than (__lt__) and greater than (__gt__) and therefore cannot run the sorting.
Running on version 0.6
Python 3.8.10

I've published a fix in v0.6.1
Thanks for the bug report, @stanton119. I didn't notice that you posted an issue until today – can't remember getting a notification. Sorry about the delay.


why I don't get the same output with the same input and same model?

I use this code to get output file which is a road with detected path according to detected lines:
from os.path import splitext, basename
import numpy as np
import cv2
from moviepy.editor import VideoFileClip
from keras.models import load_model
model = load_model('full_CNN_model.h5')
class Lanes():
def init(self):
self.recent_fit = []
self.avg_fit = []
lanes = Lanes()
vid_in = "line_1.mp4"
vid_output = 'line_1_out.mp4'
video_capture = cv2.VideoCapture()
fourcc = cv2.VideoWriter_fourcc(*'XVID')
name, extension = splitext(basename(vid_in))
output = name + '.avi'
if video_capture.open(vid_in):
property_id = int(cv2.CAP_PROP_FRAME_COUNT)
total_frames = int(cv2.VideoCapture.get(video_capture, property_id))
frame_no = 1
width, height = int(video_capture.get(cv2.CAP_PROP_FRAME_WIDTH)),
int(video_capture.get(cv2.CAP_PROP_FRAME_HEIGHT))
fps = video_capture.get(cv2.CAP_PROP_FPS)
video_writer = cv2.VideoWriter(output, fourcc, fps, (width, height))
while video_capture.isOpened():
    ret, frame = video_capture.read()
    if not ret:
        break

    small_img = np.array(np.resize(frame, (80, 160, 3)))
    small_img = small_img[None,:,:,:]

    prediction = model.predict(small_img)[0] * 255

    lanes.recent_fit.append(prediction)
    if len(lanes.recent_fit) > 5:
        lanes.recent_fit = lanes.recent_fit[1:]

    lanes.avg_fit = np.mean(np.array([i for i in lanes.recent_fit]), axis = 0)

    blanks = np.zeros_like(lanes.avg_fit).astype(np.uint8)
    lane_drawn = np.dstack((blanks, lanes.avg_fit, blanks))
    lane_image = np.resize(lane_drawn, (720, 1280, 3))

    result = cv2.addWeighted(lane_image, 1, lane_image, 1, 0)

    if frame_no % 20 == 0:
        print('# {}/{} frames processed!'.format(frame_no, total_frames))

    frame_no += 1
    video_writer.write(frame)
video_capture.release()
video_writer.release()

I also used the code in the original repository, but I did not get the same output in repository, Although I use the same steps.
Do I have to train another model now?

My apologies for not getting back to you earlier on this.
It might be a little easier to debug with the output video, but it could be a difference in how scipy's imresize function I used originally and the np.resize function you used do their re-sizing. Most likely, the input images once re-sized are no longer the same.
The second possibility is that there may be a difference in image color channels. OpenCV uses BGR, and since you are using it as the video capture, that may differ from how I trained on RGB images (and loaded with moviepy's VideoFileClip). That actually seems like the more likely issue, if that's actually occurring.

That's True.
Solved!


Added New features - user access mgmt, service connectors to confluent .net sdk

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Confluent

Created issue for spell check issue : https://github.com/Azure/autorest.csharp/issues/4291#issue-2158464258
@jsquire


hotkey not working with select

hotkey not working after  key 'enter'  select element value

my solution
hotkeys('enter', (event, handler) => {
event.preventDefault();
});
and  use up, down change value

@rataphan-t I don't know if I can solve your problem. https://codesandbox.io/s/hotkeys-128-8ivqv


ConvolutionalEncoder: contradictory description of parameter conv_layer_activation

https://github.com/dmlc/gluon-nlp/blob/ca071a6dfd7ad729a50127d1e43afe417b3230b6/gluonnlp/model/convolutional_encoder.py#L63-L66
The docstring says that if nothing is specified for conv_layer_activation, no activation will be applied; however, the default is tanh, so tanh will be applied if nothing was specified. I don't think Kim et. al paper applies any activation, so the default value of this parameter should be linear in order to be consistent with the rest of the documentation.
Maybe I misinterpreted the docstring, but it's at least confusing.

Sorry, Kim et al do use tanh.

https://github.com/yoonkim/lstm-char-cnn/blob/master/model/TDNN.lua#L27

Yes, they use tanh, but then shouldn't the description of the default behavior be changed?

Thanks for pointing out the docstring issue and no worries regarding tanh.  I agree we should change the docstring. Do you want to open a PR to change it?
If so, you may also wish to add
 seq.add(nn.Activation(conv_layer_activation))

to
if conv_layer_activation is not None:
    seq.add(nn.Activation(conv_layer_activation))

or similar in
https://github.com/dmlc/gluon-nlp/blob/ca071a6dfd7ad729a50127d1e43afe417b3230b6/gluonnlp/model/convolutional_encoder.py#L117

OK, I will open a PR.


[FLINK-6988] Add additional tests coverage for Kafka 0.11 connector

This PR only adds additional tests coverage for Kafka 0.11 connector. Please check individual commit messages for change log.

Merged alongside #4239


Failed to extract the values using '%resource.referenceSeq.referenceSeqId' against 'Hl7.Fhir.ElementModel.PocoElementNode'

Describe the bug
Failed to extract the values using '%resource.referenceSeq.chromosome' against 'Hl7.Fhir.ElementModel.PocoElementNode'.
Failed to extract the values using '%resource.referenceSeq.referenceSeqId' against 'Hl7.Fhir.ElementModel.PocoElementNode'
FHIR Version?
R4
Data provider?
CosmosDB/SQL Server
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
Expected behavior
A clear and concise description of what you expected to happen.
Actual behavior
A clear and concise description of what actually happened.

AB#79273

@brendankowitz can you add details to reproduce?


Migrate account presets to camelCase

Fixes https://github.com/OpenZeppelin/cairo-contracts/issues/382

Let's put this and nile's PR on hold until we merge 0.10.

@martriay The more I think about this the less I think it is a good idea. I started to align in the Argent repo then realized it posed a lot of questions: should I use camelCase for external function parameters as well? Output parameters? The answer is probably yes if you want to be consistent (weird to have both camel case and snake case in the same function definition), but then you are passing camel case variables to your snake case internal methods... and you are back to the same mixing mess. Not even mentioning the fact that __execute__ and __validate__ still have snake case arguments.
While I can understand the logic of using camel case for ERC standard, the IAccount interface is purely a StarkNet standard so the argument does not apply there. On the other hand, I feel that you are gradually diverging from the convention of all the other projects in the ecosystem which will either force everybody to align for consistency (in that case it should probably be discussed), or make all the other projects inconsistent by forcing them to mix between different conventions (e.g. when they interact with an account).

Hello @juniset thanks once again for giving this a thorough thought.

should I use camelCase for external function parameters as well? Output parameters?

Yes. All external methods and its parameters would be camelCased as per the extensibility pattern. We've received many questions/complaints around us not following it and the confusion this generates. We agreed with them.

While I can understand the logic of using camel case for ERC standard, the IAccount interface is purely a StarkNet standard so the argument does not apply there.

The extensibility pattern tries to provide easy to follow guidelines to design libraries and contracts. It does not reference EIPs or other networks, it's purely StarkNet.
Although it recognizes the existence of EIP-based interfaces, it's not the goal to specify how to deal with them but to simplify the thought process so developers don't have to think whether they're interacting/interfacing with an ERC standard to name their functions, so it simply uses camelCase for contracts (similar to Vyper's decision).
Part of the reason for this is that there's a lot of non-EIP but defacto standards such as access control interfaces, or you could even be implementing an interface that ends up being an EIP in the future. EIP-ness of an interface is not future proof.
The goal therefore is to have a super simple mental model: if it's an external/public function of a contract, it needs to be camelCase. You don't need to worry about deciding/guessing whether it corresponds to an existing (or future!) EIP or not.

then you are passing camel case variables to your snake case internal methods... and you are back to the same mixing mess. Not even mentioning the fact that __execute__ and __validate__ still have snake case arguments.

I recognize there's 2 exceptions here: system-defined account entrypoints (__execute__, __validate_declare__, and __validate__) as well as system-defined parameters (N_len for any N named array). I see accepting these exceptions as super specific the lesser evil. Otherwise we'll see a huge mix casing when calling contract functions (and I personal believe that (1) default entrypoints won't be much called from contracts, and (2) that N_len parameters will be absorbed by the language in the future, as any other high level language).
There's one super important point to highlight here: ecosystem-wide consistency was not possible since the moment starkware decided to use snake_case for their stdlib (unlike Vyper), and users wanting to follow ERC interfaces. Unless one of them gets dropped, we can't have consistency.
Once we accept inconsistency, the question is what rule/pattern are we going to use to decide when to use each casing. Here's is where we lean towards the simpler model: all external interfaces have to be camelCase (an easier superset of camelCasing ERC contracts only). Distinguishing between non/ERC contracts is a much harder thought process with no clear gain, since we'll have inconsistencies anyway. This decision only minimizes those inconsistencies.

On the other hand, I feel that you are gradually diverging from the convention of all the other projects in the ecosystem which will either force everybody to align for consistency (in that case it should probably be discussed), or make all the other projects inconsistent by forcing them to mix between different conventions (e.g. when they interact with an account).

Considering the points presented above, I believe the ecosystem is already diverging by itself. Some projects use cameCase for their externals, some projects use ERC contracts, etc. If we were to not implement camelCase on the Account, we would not be following the Extensibility pattern thus collaborating to the growing chaos.
Casing mixing already exists and this change is our own take on how to minimize it, using some form of occams' razor: if in doubt, choose the simpler model.
Re: discussion, there were discussions for this (here and here) and if anything they just showed lack of ecosystem-wide agreement, for which we need to reply with an opinionated decision otherwise we'll stall.
Finally, considering that:

at this point we're looking into releasing Cairo 0.10 support as soon as possible and we're in the final lap
with the 0.10 migration and eventual regenesis coming soon, we aim to bundle as many breaking changes together in a single release as possible.

Is that we sadly cannot afford to reopen this discussion so close to releasing.

This PR is superceded by #449 btw.

There is ecosystem wide agreement on naming now - it's snake_case. Look at Aave, Jedi swap, Starknet ID, Dope Wars, Empiric Oracle just to name a few. From my point of view, it's OZ that's diverging from the consensus. Besides ERC methods, there really not much support for camelCase anywhere.

at this point we're looking into releasing Cairo 0.10 support as soon as possible and we're in the final lap

This change didn't really have to be in the 0.10 support release, you decided so.
I'm curious, did you consult any of the leading wallet providers (Argent, Braavos, Ledger, MetaMask, apologies if I'm missing any) about this breaking change?
Finally, won't changing this break the StarkNet CLI?

This change didn't really have to be in the 0.10 support release, you decided so.

And yes I decide what's on the roadmap because that's my job. But we've been super public about our roadmap, more than any other project in the space. And the rationale behind my decision is above: to bundle as many breaking changes together as possible, to minimize migration hurdles.

You are right. Even though I follow this repo quite closely, I don't remember seeing the project management UI and I missed that the IAccountchange was assigned to be in this upcoming release 2 weeks ago. I missed that, my bad and I apologize.
Also note it's nothing personal, I'm simply trying to stand up for what I believe is right.

I understand you feel very strongly about your opinion, but it's not enough to legitimize it.

Yes, I do have a strong opinion as do you. So that applies both ways☝🏼

when there's no ecosystem wide agreement

That's simply not true. Cairo stdlib is snake case, so there's precedence. Furthermore, I've presented a handful of well known projects above, all using snake case in their API.
From my point of view, this change doesn't bring any benefit to the ecosystem.

Thanks @martriay for the detailed response. And I'm sorry to have reopened the discussion, just realised some implications of it while working on its implementation :-)
@milancermak I want to emphasise that Martin has been very transparent and communicative about this change, and we started the discussion a while ago. While I don't necessarily agree with it, I do recognise that it makes sense for the consistency of the OZ repo since their starting point is to write ERC compliant contract standards on StarkNet. And I did agree to it for the sake of consistency.
But we need to communicate that change to the wider ecosystem because is_valid_signature is used by dapps. So we'll need to update the libraries to use the camel case version (starknet.js, starknet.py, etc) as well as tell dapps to update their contracts. Changing the account interface is a breaking change.
I might keep both versions (is_valid_signature and isValidSignature) to give dapp contract the time to adapt.

Also note it's nothing personal, I'm simply trying to stand up for what I believe is right.

I know and I appreciate you being on top of our development process, you made notable contributions in the past so I'm glad to know we can keep it civil.

Yes, I do have a strong opinion as do you. So that applies both ways☝🏼

Sure that's what I mean by lack of ecosystemic agreement but as I said before decisions have to be made and I'm in a position that forces me to do so. I know I'll bear the weight of bad decisions and this time I think this is the right way.

Thanks @martriay for the detailed response. And I'm sorry to have reopened the discussion, just realised some implications of it while working on its implementation :-)

Yes, very understandable.

But we need to communicate that change to the wider ecosystem because is_valid_signature is used by dapps.

I think this is one of Milan's most accurate points. I started to reach out to projects so they update accordingly. I also sent an updated comment on the standard account interface discussion, and I'll open an issue on the shamans forum.
Closing this now since it's been superceded by #449. Thanks again for your comments.