Get image as an object instead of url

Issue Description
onTapImage(event) {
const uri = event.nativeEvent.selected;
        if (this.state.images[uri]) {
              delete this.state.images[uri];
        } else {
              this.state.images[uri] = true;
        }
        this.setState({ images: {...this.state.images }})

}
[ENTER DESCRIPTION HERE]
The above code is from cameraKit example project. when i tap an image i am getting the image url,
however i want to get image as a file. ie as an object with filename, extension, url etc.
So that i can send the file to S3 for storage.
How is this going to be possible.
Steps to Reproduce / Code Snippets / Screenshots
[FILL THIS OUT - It will be extremely helpful]

Environment
"react-native-navigation": "^2.0.2641"
"react-native": "0.57.4",
"react-native-camera-kit": "^7.3.3",
both ios and android

To upload externally, please use another library like react-native-fs or expo-filesystem and use the generated uri.
Closing due to inactivity


Custom options moved to yaml config file to override them

A yaml config file has been created.
Options declared in config.yaml is merged with options from config.yaml.dist.

@arkadiych Thank you for the improvements!


How to Stake and Farm in Ubeswap

Create tutorial on how to stake and farm using Ubeswap.

Ubeswap docs: https://docs.ubeswap.org/
Ubeswap Yield Farming on Celo: https://www.youtube.com/watch?v=7iHDF-DifSY&t=13s
Ubeswap Homepage: https://ubeswap.org/

Meeting with Felipe tomorrow to discuss


The values of the properties 'Soft Delete' and 'Retention Days' show 'Error loading property' for one Premium account

Storage Explorer Version: 1.16.0
Build: 20201112.8
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Previous release(1.16.0)
Steps to reproduce:

Create one Premium StorageV2(general purposev2) account in portal.
Expand the account in Storage Explorer -> Select 'Blob Containers' node.
Check the 'Soft Delete' and 'Retention Days' in Properties panel.

Expect Experience:
The values of the properties 'Soft Delete' and 'Retention Days' show well.

Actual Experience:
The values of the properties 'Soft Delete' and 'Retention Days' show 'Error loading property'.

More Info:
This issue also reproduces for one Premium Storage(general purpose v1) account.

Verified on build 20201116.2. This issue still reproduces. The details of the premium account show below:
Direct Link of the account: storageexplorer://v=1&accountid=%2Fsubscriptions%2F5d17327f-ed05-4b65-bfd1-f498ac160d55%2FresourceGroups%2Fcti-kristine%2Fproviders%2FMicrosoft.Storage%2FstorageAccounts%2Fabcpremiumv2&subscriptionid=5d17327f-ed05-4b65-bfd1-f498ac160d55

Found a relevant issue either in the SDK or on the service side. Will wait for their response to see if we can fix it/workaround it.

Move to 1.19.0 since we are blocked and no customer is reporting it.

Did some investigation and opened the a bug in the SDK for the root cause.
https://github.com/Azure/azure-sdk-for-js/issues/14411

Try to get an ETA from the service team.

Update the behavior for this issue:
On the build 202100818.3, The Soft Delete value displays 'Disabled'.

Display a failed activity log when clicking 'Configure Soft Delete Policy...'.

Error details:
  "name": "RestError",   "message": "Error \"SyntaxError: Unexpected token  in JSON at position 0\" occurred while parsing the response body - <?xml version=\"1.0\" encoding=\"utf-8\"?>\n<StorageServiceProperties><Cors/><DeleteRetentionPolicy><Enabled>false</Enabled><AllowPermanentDelete>false</AllowPermanentDelete></DeleteRetentionPolicy></StorageServiceProperties>."


Keep guava in step with Scio

Currently we are on 0.21 while Scio is on 0.20. Should investigate downgrade and potential issues. Concerned this may cause unexpected errors when running.

Seems to be the case. Fixing now

Closing, please try 0.3.1 and re-open if there are issues

@idreeskhan Still reproducible with the 0.3.1.jar
[ForkJoinPool-1-worker-5] ERROR org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler - 2018-04-13T15:11:52.057Z: java.lang.NoSuchMethodError: com.google.common.base.Preconditions.checkNotNull(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/Object;
	at org.apache.beam.sdk.io.gcp.bigquery.BigQueryAvroUtils.convertRequiredField(BigQueryAvroUtils.java:169)
	at org.apache.beam.sdk.io.gcp.bigquery.BigQueryAvroUtils.getTypedCellValue(BigQueryAvroUtils.java:131)
	at org.apache.beam.sdk.io.gcp.bigquery.BigQueryAvroUtils.convertGenericRecordToTableRow(BigQueryAvroUtils.java:115)
	at org.apache.beam.sdk.io.gcp.bigquery.BigQueryAvroUtils.convertGenericRecordToTableRow(BigQueryAvroUtils.java:104)
	at org.apache.beam.sdk.io.gcp.bigquery.BigQueryIO$TableRowParser.apply(BigQueryIO.java:381)
	at org.apache.beam.sdk.io.gcp.bigquery.BigQueryIO$TableRowParser.apply(BigQueryIO.java:374)
	at org.apache.beam.sdk.io.gcp.bigquery.BigQuerySourceBase$1.apply(BigQuerySourceBase.java:204)
	at org.apache.beam.sdk.io.gcp.bigquery.BigQuerySourceBase$1.apply(BigQuerySourceBase.java:198)
	at org.apache.beam.sdk.io.AvroSource$AvroBlock.readNextRecord(AvroSource.java:581)
	at org.apache.beam.sdk.io.BlockBasedSource$BlockBasedReader.readNextRecord(BlockBasedSource.java:223)
	at org.apache.beam.sdk.io.FileBasedSource$FileBasedReader.advanceImpl(FileBasedSource.java:470)
	at org.apache.beam.sdk.io.FileBasedSource$FileBasedReader.startImpl(FileBasedSource.java:465)
	at org.apache.beam.sdk.io.OffsetBasedSource$OffsetBasedReader.start(OffsetBasedSource.java:261)
	at com.google.cloud.dataflow.worker.WorkerCustomSources$BoundedReaderIterator.start(WorkerCustomSources.java:594)
	at com.google.cloud.dataflow.worker.util.common.worker.ReadOperation$SynchronizedReaderIterator.start(ReadOperation.java:347)
	at com.google.cloud.dataflow.worker.util.common.worker.ReadOperation.runReadLoop(ReadOperation.java:183)
	at com.google.cloud.dataflow.worker.util.common.worker.ReadOperation.start(ReadOperation.java:148)
	at com.google.cloud.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:68)
	at com.google.cloud.dataflow.worker.DataflowWorker.executeWork(DataflowWorker.java:330)
	at com.google.cloud.dataflow.worker.DataflowWorker.doWork(DataflowWorker.java:302)
	at com.google.cloud.dataflow.worker.DataflowWorker.getAndPerformWork(DataflowWorker.java:251)
	at com.google.cloud.dataflow.worker.DataflowBatchWorkerHarness$WorkerThread.doWork(DataflowBatchWorkerHarness.java:135)
	at com.google.cloud.dataflow.worker.DataflowBatchWorkerHarness$WorkerThread.call(DataflowBatchWorkerHarness.java:115)
	at com.google.cloud.dataflow.worker.DataflowBatchWorkerHarness$WorkerThread.call(DataflowBatchWorkerHarness.java:102)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Still reproducible on ratatool-0.3.2-SNAPSHOT. :(
@idreeskhan

Hmm worked for me locally @tkhduracell

Have you tried the public jar?

Local Build:
shasum -a 256 ratatool-0.3.2-SNAPSHOT.jar
364f48303d9298458c8409ebda8d9253736a52fcf086fea7d292ddd650a8971c  ratatool-0.3.2-SNAPSHOT.jar

Uploaded Jar:
shasum -a 256 ~/Downloads/ratatool-0.3.2-SNAPSHOT.jar
364f48303d9298458c8409ebda8d9253736a52fcf086fea7d292ddd650a8971c  /Users/idrees/Downloads/ratatool-0.3.2-SNAPSHOT.jar

Ah, heh, I see the problem actually.

I've uploaded a gzipped pack folder which works for me end-to-end for BigDiffy and BigSampler with BQ, also will PR changes to public Homebrew formula to fix it as well. For now it can be run by executing bin/big-diffy, will need to update docs before releasing a full version.
SHA256 is 7684a016e3619e1860cfbb08ae0a3932b5c42d2c8d698927fc9d6fe59be083fb

Closing this issue for now, re-open if the packed folder does not address your issues.


[FEATURE REQUEST]: Simplify tsconfig.json to make room for incremental changes when necessary

Feature details?
The current state of the tsconfig.json is too "strict" & it should be "toned down" to make room for future increments. On top of it, simplifying the config file will also get rid of errors caused by experimental features like #73.
That said, Next.js already provides a standard default config file with the following contents:
{
  "compilerOptions": {
    "target": "es5",
    "module": "esnext",
    "jsx": "preserve",
    "strict": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "noEmit": true,
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true
  },
  "exclude": ["node_modules"],
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx"]
}

The standard configurations should be a good starting point right now. Additionally, do take a look at the following config values which I think might benefit contributors with a better dev experience;

baseUrl
paths
noUnusedLocals
noUnusedParameters

Add more of such config values I might've missed out & please have a productive discussion below before suggesting any additional config values.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Also, add path aliases. whoever is working on it.

For those who're wondering how to add path aliases:
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": ["src/*"]
    }
  }
}

How about also adding some strict type checking options?
{
  "compilerOptions": {
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "alwaysStrict": true
  }
}

Also, add path aliases. whoever is working on it.

Can you explain more on how the project structure is gonna be? Right now, I guess we can add one path alias for static media files and 1 path alias for a generic component folder. I don't know what else can we add?
{
  "compilerOptions": {
      "paths": {
      "@static/*": ["public/*"],
      "@components/*": ["src/components/*"]
      },
   }
}

As, we are still discussing on whether to add the experimental options or not, I commented it out for now. Does this look good?
{
  "compilerOptions": {

    // Basic Options
    "target": "es2017",
    "lib": [
      "dom",
      "dom.iterable",
      "es6",
      "esnext",
      "es2017"
    ],
    "allowJs": true,
    "jsx": "react",
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,

    // Strict Type-Checking Options
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "alwaysStrict": true,

    // Module Resolution Options
    "moduleResolution": "node",
    "baseUrl": ".",
    "paths": {
      "@static/*": ["public/*"],
      "@components/*": ["src/components/*"]
    },

    // Experimental Options
    // "experimentalDecorators": true,
    // "emitDecoratorMetadata": true,
  },
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx"
  ],
  "exclude": [
    "node_modules"
  ]
}

@vigneshwar221B cool looks good, would you like to work on a PR with the changes? But could you hold up for just a bit? I would like discuss something about support for experimental features & path aliases. Also do take a look at #80 which will refactor the current tsconfig.json to tone down on the strictness.

Sure, get back to me when you finalise your decision on experimental features and path aliases. I'll make a PR.

@vigneshwar221B you can go ahead & share the PR with the changes you want to make on the current tsconfig.json file. Do note, some of the configurations have already been added in #80.
As for experimental support, let's hold on to them for now & we can add them when absolutely necessary later on.


Errorhandling if funding is not sufficient

Use a wallet (track visible on test slaapyhoofd wallet) with 700sats
Write two cards with a funding amount of each 600 sats
"Error that BRRing wallets not possible"
Two wallets are created and visible in the write section
Every generated wallet where one link is missing should be treated as unsuccessful (count) and should not be funded.
Every generated wallet where the links were all generated but the funding wasnt possible should be treated as unsuccessful (count) and nothing should be shown from them at all. Not for writing nor for printing.
If the funding is missing the wallets resp. payment cannot be rollbacked so a count is needed to know how much cards are missing.
+Errortext that x wallets couldnt be funded/not all links generated and can be written after this job.

See commit
Instead of complex error handling during the batch, a balance check is performed before batches with filling up enabled.

How about not generated links a step before ?

How about not generated links a step before ?

It is checked before the entire batch starts, so nothing is created.

🚀 Moon


Allow usage of "className"

Hi, I use tachyons [0] to style react for web, so I'd like to use the className property in react-native as well.
It allows me to use "mini"-css classes and write code like this, instead of using the styles property, which I find way better (after having tried both approaches).
   <View className="w1 wv">

   </View>

[0] http://tachyons.io/docs/

Hi!
Do you want to use real CSS in React Native? It's not possible yet and probably won't be. You have to have tachyons implementation for RN.
For more info check this article http://facebook.github.io/react-native/docs/style.html#content

Check https://speakerdeck.com/vjeux/react-css-in-js

@kohver No, I don't want real css, I just want classnames I can assign to React's CSS-subset and then use.
@satya164 I know that presentation. I used this (styles={styles.main}) in production multiple times, but I prefer the way tachyons and http://www.basscss.com do it. In my eyes it's superior.

@fab1an There is no reason you shouldn't be able to have a className prop. Does RN give you warning if you use className?

No, but the classnames don't seem to be applied to react-native?

@fab1an What do you mean by they are not applied? You've to handle the prop in your component if you want to. React Native doesn't support CSS.

I'm not talking about supporting CSS. I'm taking about being able to create a React.StyleSheet with properties like so:
var styles = StyleSheet.create({
  w100: {
    width: 100
  },
  h100: {
    height: 100
  },
  bg-black: {
    backgroundColor: '#000000',
  },
  bg-white: {
    backgroundColor: '#FFFFFF',
  },
});

and then use it like so:
<View className="h100 w100 bg-black">
   <Text className="w100 bg-white"/>
</View>

This way I have my styles at the place where the are being applied, which makes development faster AND I don't need to find a name for every css component, which is good since they rarely have a proper semantic meaning.
I can implement this myself with a babel-transformation, but I wanted to if something like this is possible out of the box.

@fab1an No. React Native doesn't support this pattern. To support this at runtime, you'll have to implement a className prop in every component that wants to support this and you also need a reference to the styles object to extract the styles out from it. Also conditionally applying style is much messier with this approach.
Why not just use this? It doesn't look that different to me.
<View style=[ s.h100, s.w100, dark ? s.bgBlack : null ]>
   <Text style=[ s.w100, s.bgWhite ]/>
</View>

For conditional styles I tend to use the classnames library.
I didn't know you could pass an array to style. Maybe I'll write the babel-transform, but this should work for me in the meantime, thank you.

You can write that as a 3rd party plugin and it will just work.
What to do:

Call MyCustomStyleSheet.create() that just calls StyleSheet.create() but also stores keys in a global object so you can refer to them
Wrap every component you want to style that way by a HOC Stylable (or whatever) that, given a className string, will cal MyCostomStyleSheet.resolve(strings) and return an object with styles where strings is a separated by spaces list of keys to apply

What do you mean by "HOC"?
That sounds good, but i think it's too much clutter to wrap every JSX tag in an extra parent.

@fab1an Higher order components - https://medium.com/@franleplant/react-higher-order-components-in-depth-cf9032ee6c3e

More or less this -> https://gist.github.com/grabbou/cec8608d7dbb54ec8cb4080134a997e5
Note - it probably does not work, but shows the concepts :)

Great! Thanks.

I build this into a library: https://github.com/fab1an/react-native-tachyons

Maybe you could use https://github.com/alibaba/rax/blob/master/packages/babel-plugin-transform-jsx-stylesheet/README.md.


[WIP] split the client from the cli (take 2)

Addreses #43

Coverage increased (+0.2%) to 85.014% when pulling a45a96d98f26a5f7820608beb9bb1a16fa46a6ea on Fak3:f43_2 into 8ed63ee19ea5e9316e06a2cfa5e372241ac58cc6 on frictionlessdata:master.

Coverage decreased (-0.6%) to 84.238% when pulling ab5a579b94945efcc02a1ef7981e39cf99392b19 on Fak3:f43_2 into 8ed63ee19ea5e9316e06a2cfa5e372241ac58cc6 on frictionlessdata:master.

Coverage decreased (-0.5%) to 84.278% when pulling 41fd902e19b4a95354f17486b9e7e26d979e2a4d on Fak3:f43_2 into 8ed63ee19ea5e9316e06a2cfa5e372241ac58cc6 on frictionlessdata:master.


Field is getting cleaned, but doesn't show as invalid

A field in an object is type: [PhotosSchema], but if I validate the object and check the invalid keys, keys from the parent schema are being expected. Specifically:
The parent schema:
var GroveSchema = new SimpleSchema({
  name: {
    type: String
  },
  belongsTo: {
    type: [String],
  },
  createdAt: {
    type: Date
  },
  towers: {
    type: [TowerSchema],
  },
  photos: {
    type: [PhotosSchema]
  },
  variables: {
    type: Object,
    blackbox: true
  }
});

PhotosSchema:
PhotosSchema = new SimpleSchema({
  // the S3 url
  url: {
    type: String
  },
  takenById: {
    type: String,
    regEx: SimpleSchema.RegEx.Id
  },
  dateTaken: {
    type: Date
  },
  groveId: {
    type: String,
    regEx: SimpleSchema.RegEx.Id
  }
});

If I make an object with all the fields in PhotoSchema, add that to the photos array in a object that matches GroveSchema, then call the following code, I get the following output:
var photoContext = PhotosSchema.namedContext("photo1");
console.log(photoContext.validate(photo)); // prints 'true'
console.log(photoContext.invalidKeys()); // prints '[]'

var groveContext = GroveSchema.namedContext("grove1");
console.log(groveContext.validate(self)); // prints 'true'
console.log(groveContext.invalidKeys()); // prints '[]'
GroveSchema.clean(self);
console.log(self);
// output of this line is (edited for space):
    {
      photos: [ {} ]
    }
console.log(photo);
// output of this line is:
    {}

The towers field is designed similarly, but I haven't noticed any similar issues.

Turns out it was a file load order issue.


[remote_config] values are empty on andorid

I am using remote config in my project but the values are empty.

I have tested with the old version of my project withfirebase_remote_config: ^0.0.6 and it's working fine.
I have also tried with a new project without installing extra packages,  and still the same issue although I am getting Firestore data just fine.
Tested on both android emulators, phon with debugging and with build version.

   final RemoteConfig remoteConfig = RemoteConfig.instance;
    await remoteConfig.setConfigSettings(RemoteConfigSettings(
      fetchTimeout: const Duration(seconds: 10),
      minimumFetchInterval: const Duration(hours: 1),
    ));

   print(remoteConfig.getString('MYKEY');

Flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 2.5.0-6.0.pre.49, on Microsoft Windows [Version 10.0.19042.1110], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[√] Chrome - develop for the web
[√] Android Studio (version 3.5)
[√] VS Code (version 1.46.1)
[√] Connected device (3 available)

• No issues found!

Flutter dependencies

environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter

 firebase_core: ^1.4.0
  firebase_remote_config: ^0.10.0+3

Hi @naumanahmed19
Please call await remoteConfig.fetchAndActivate();. Take a look at the example to see how to use the latest version of the plugin.
https://github.com/FirebaseExtended/flutterfire/blob/master/packages/firebase_remote_config/firebase_remote_config/example/lib/main.dart
Thank you


Create rule DDF00006: Timing windows must be fully defined

Create rule defined for  #8

Logic: if any of timingWindow, timingWindowLower or timingWindowUpper is populated in an instance of the Timing entity, then all three must be populated

This rule has been updated and retested for 2.6. timingWindow, timingWindowLower and timingWindowUpper were renamed to window, windowLower and windowUpper respectively.

@ASL-rmarshall
It works okay and looks okay so I am moving it to done.
There are couple questions related more to my understanding. In column P, "relativeToFrom.decode" it is "Start to Start" and then in column U "type.decode" says After except for row 11. Row 11 says Before and the "relativeToScheduledInstanceId in column V is ScheduledActivityInstance_7 whereas column W is "ScheduledActivityInstance_6". I am looking at the "success' example. Will you explain these two columns?
The letters in the description, are those arbitrarily assigned?

This rule to only report where rel_type = "definition". Associated test data have been updated and unit tests have been rerun successfully.

Saving POC definition before overwriting for DDF4:
Authorities:
  - Organization: CDISC
    Standards:
      - Name: USDM
        References:
          - Citations:
              - Cited Guidance: 'USDM'
                Document: 'USDM v3.0'
            Origin: USDM Conformance Rules
            Rule Identifier:
              Id: 'DDF00006'
              Version: '1'
            Validator Rule Message: 'If any part of a timing window is specified then all
              parts should be specified'
            Version: '1.0'
        Version: '3.0'
Check:
  all:
    - name: rel_type
      operator: equal_to
      value: 'definition'
    - any:
        - name: window
          operator: non_empty
        - name: windowLower
          operator: non_empty
        - name: windowUpper
          operator: non_empty
    - not:
        all:
          - name: window
            operator: non_empty
          - name: windowLower
            operator: non_empty
          - name: windowUpper
            operator: non_empty
Core:
  Id: 'CORE-000402'
  Status: Draft
  Version: '1'
Description: 'Timing windows must be fully defined.'
Executability: Fully Executable
Outcome:
  Message: 'Incomplete timing window definition (missing window, windowLower or
    windowUpper)'
  Output Variables:
    - parent_entity
    - parent_id
    - parent_rel
    - id
    - window
    - windowLower
    - windowUpper
Rule Type: Record Data
Scope:
  Entities:
    Include:
      - Timing
Sensitivity: Record


Migrate PipelineResourceResult

Changes
This commit rename PipelineResourceResult and also move it to v1.
It was first introduced just to write digest as results for image resources but over the time,
generalized to take in more results. But it really is just an abstraction of TaskrunResult, ResourceResult and InternalTektonResult. And since now the pipelineResources is going to be removed, we would need to move it to result_types and rename it.
There will be a followup PR removing the resourceResult field for taskrun.
Fixes: https://github.com/tektoncd/pipeline/issues/6197

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[ ] Follows the commit message standard
[ ] Meets the Tekton contributor standards (including
functionality, content, code)
[ ] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

TODO: rename the pipelineResourceResult

/kind misc

/retest

/retest

/cc @chitrangpatel
since you've done a lot of work with results

Been wondering where to move the const of types since it is not migrated to v1 and would we also need to migrate it to not to reference to v1beta1.InternalTektonResultType when we decide to deprecate v1beta1?
Also wondering since the resourceResult is also not in v1, shall we create an issue to refactor this PipelineResourceResult TaskRunResultType to be using the actual TaskRunResult struct?

Thanks for the reviews and comments.
Instead of migrating the PipelineResourceResult struct and renaming it in the same PR. This PR now intends to break things down by removing PipelineResourceResultType only so as to be the least confusing as possible. PTAL 🙏

I do appreciate the time on this @lbernick 😃
And to put the above pointers in a summary, on the next step:

Refactor filterResults func
Migrate git-init image off PipelineResourceResult to TaskRunResult
^^ above 2 could happen in parallel
Tombstone ResourcesResult

I do appreciate the time PLUS guidance on this @lbernick 😃
And to put the above pointers in a summary, on the next step:

Refactor filterResults func
Migrate git-init image off PipelineResourceResult to TaskRunResult
^^ above 2 could happen in parallel
Tombstone ResourcesResult

yeah that sgtm, I'd focus on the changes needed for removing pipelineresources-- I started poking around with a readability refactor to status.go

/lgtm

/test pull-tekton-pipeline-alpha-integration-tests


fix: Fix error when calling "starknet_state_root" and "starknet_last_proven_block"

Bug Report
Currently, when calling "starknet_state_root" and "starknet_last_proven_block" on the "start" thread:
https://github.com/danilowhk/beerus/blob/57a47dd37091ba97263248955318681de0393fdb/beerus_core/src/lightclient/beerus.rs#L118
and
https://github.com/danilowhk/beerus/blob/57a47dd37091ba97263248955318681de0393fdb/beerus_core/src/lightclient/beerus.rs#L124
Currently we can confirm that the helios_client is working well within the thread/loop
https://github.com/danilowhk/beerus/blob/57a47dd37091ba97263248955318681de0393fdb/beerus_core/src/lightclient/beerus.rs#L132
And when calling "starknet_state_root" and "starknet_last_proven_block" with the wrong contract address, it returns 0.
So I believe the issue is within the functions itself(it could be because the function was moved from "beerus" to "beerus.ethereum_client."
Beerus version:
0.1.0
Current behavior:

Expected behavior:

Steps to reproduce:

Related code:

insert short code snippets here

Other information:

Can we lazy static the DEFAULT_STARKNET_CORE_CONTRACT_ADDRESS?

Can I try solving this issue?


added callback param to write function

Hi @biggora,
I tried your CLI with Node.js v10.14.1 and I got a TypeError at runtime.
As you can see here in history section I have fixed it.
Please merge it and if you will I sync my branch with your latest updates (now it's up to date).
I reference the related issue.

@biggora are you planning to work on this project?

Yes if you are interested


[opentelemetry] Enhance monitoring dashboard and add alerts for OpenTelemetry logs

Priority
None
Is your feature request related to a problem?
Enhance monitoring dashboard.
https://github.com/monitoringartist/opentelemetry-collector-monitoring could be a starting point for dashboard and alerts for the OTEL collector monitoring.
Adding alerts to OpenTelemetry logs
Additional context.
No response
Reference Issues
No response

Previous implementation: #339

follow-up on #435


Staging

Not sure why it bumped to 0.7.0

Coverage remained the same at 96.175% when pulling 6f0f6863f7ccc88d5476f73e0c28bb9748c74f8f on staging into b834c4ee25894e559fde4b2d5fcb71b13077bd4d on master.

Coverage remained the same at 96.175% when pulling 0eda699f026621b95c0448f46608e10cef1bf0f3 on staging into b834c4ee25894e559fde4b2d5fcb71b13077bd4d on master.


Build SciF Docker image as a Singularity container

Task to do
Convert the Docker image to Singularity
Reason
The Docker image needs to be converted to Singularity before it can be run on the HPC
Result
There's a singularity container containing the docker image

This is no longer needed


Creating mysql cdc source tables failed during wide table test

Describe the bug
https://buildkite.com/risingwave-test/wide-table/builds/107#0191e434-7017-47a6-863a-098f2ece810a
[WARN] Using S3 as the storage backend! MinIO deployment is forcefully disabled!
--
  | [INFO] [workspace/k8s] [namespace: wide-table-op9kn] Happy benchmarking!
  | Generating realtime_waybill_detail data
  | Generating realtime_waybill_cost_fee data
  | Creating realtime_waybill_detail table
  | mysql: [Warning] Using a password on the command line interface can be insecure.
  | Creating realtime_waybill_cost_fee table
  | mysql: [Warning] Using a password on the command line interface can be insecure.
  | Creating RW source and tables
  | CREATE_SOURCE
  | ERROR:  Failed to run the query
  |
  | Caused by these errors (recent errors listed first):
  | 1: Expr error
  | 2: Unsupported function: cast(timestamp with time zone) -> timestamp without time zone
  |
  | ERROR:  Failed to run the query
  |
  | Caused by these errors (recent errors listed first):
  | 1: Expr error
  | 2: Unsupported function: cast(timestamp with time zone) -> timestamp without time zone

Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
v2.0.0-rt.4
Additional context
No response

it worked before? sounds like a breaking change

cc @xiangjinwu to take a look. btw @cyliu0 can provide the table schema to you which is a customer scenario.

Note the following naming differences between MySQL and PostgreSQL (RisingWave):

MySQL datetime is PostgreSQL timestamp (without time zone).
MySQL timestamp is PostgreSQL timestamptz, which is number of s/ms/us passed since 1970-01-01 00:00:00 in UTC.

Unsupported function: cast(timestamp with time zone) -> timestamp without time zone

This looks like we are trying to insert a timestamptz (MySQL timestamp) into RisingWave timestamp

@xiangjinwu But we have run this case for the past months. It never failed because of this. You can check the build history on the buildkite.
And we never use MySQL timestamp in the upstream tables according to the upstream table schemas https://github.com/risingwavelabs/kube-bench/blob/main/manifests/wide-table/wide-table-sql.template.yaml#L7-L1246.
And there is no timestamptz as well. You can check the source tables in the same file above.

Thanks for sharing the schema, which is mapping from MySQL datetime to RisingWave timestamp (without time zone) correctly. There should be no timestamp with time zone at all during this test. @StrikeW Is there any related change in MySQL CDC logic in the past 2 months?

becaue 2.0.0-rc.1 passed the test, I suppose the buggy commit is in the following range:
https://github.com/risingwavelabs/risingwave/compare/v2.0.0-rc.1...release-2.0

In the following range between v2.0.0-rt.3 and v2.0.0-rc.1
https://github.com/risingwavelabs/risingwave/compare/dc8faba297a3e4a5da3ceaf8d8ca6456a00...v2.0.0-rc.1

After https://github.com/risingwavelabs/risingwave/pull/18322, we can't define column in CDC tables like this update_time timestamp  DEFAULT CURRENT_TIMESTAMP,. The correct definition should be update_time timestamp  DEFAULT CURRENT_TIMESTAMP AT TIME ZONE 'Asia/Singapore', -- or UTC. We may support the former one in the future like MySQL and PG. But for now, we fixed our test cases to adapt to this in https://github.com/risingwavelabs/kube-bench/pull/457

#18513


[0.4] Remove $addUpdateTags

This PR is the first of many
Accidential tag inheritance
Updates can be tagged but they can also potentially be batched. Batching can be lead the unexpected behavior / race conditions.
For example, I bootstrap the editor and run a second update to add an emoji. The first is a history-merge update while the second the default update. Should the second be batched with the first? Probably not since this will introduce different behavior for undo-redo.

Fix
We can flush sync incompatible updates immediately. If the second update has different tags than the first we can immediately reconcile the first and generate the final EditorState from it.
Concerns

$addUpdateTags: This method can be called literally anywhere in the update cycle, even in transforms. Transforms are unpredictable and we can't find out until they're executed, whereas we have full control of the tags passed in updates.
Not so much of a concern but nested updates have to be taken into consideration. They'd follow the same rules, first run the parent, if the nested update has incompatible/different tags flush sync the parent and then follow up with the nested.

Follow-up

Why are updates limited to a single tag? They can potentially carry many. This can become particularly useful if you're passing tags to fulfill the requirements of some built-in plugin while you still want to introduce your personal ones.
This introduces the opportunity to batch the reconciliation while still delivering users the corresponding EditorStates. It's a nice BE work but also requires further conversation on whether we want to this because we break the promise that updateListener matches the reconciled/rendered EditorState._

I'm not sure we want to remove this, as it provides a purpose that can't be achieved else-wise. Let's take this offline, as I feel there's maybe a better way of dealing with this without removing the desired behavior here.

Back to the drawing board


Add unit test to verify producer can produce block with r1 signing key

For testing #2275

PR is updated. It now checks only until the new set of producers finishes its first round


Upgrade opentracing & jaeger lib

upgrade opentracing to 0.32.0
upgrade jaeger to 1.1.1
fix the infinite loop bug when closing tracing context due to the NoopScopeManager always return non-null instance

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

tchannel seems to be using google maven central, java monorepo is not publishing to that artifactory, going to figure this out.

Codecov Report

Merging #199 into master will decrease coverage by 0.06%.
The diff coverage is 66.67%.

@@             Coverage Diff              @@
##             master     #199      +/-   ##
============================================
- Coverage     71.95%   71.89%   -0.06%
  Complexity       10       10
============================================
  Files            87       87
  Lines          2660     2661       +1
  Branches        320      319       -1
============================================
- Hits           1914     1913       -1
- Misses          525      526       +1
- Partials        221      222       +1

Impacted Files
Coverage Δ
Complexity Δ

.../com/uber/tchannel/tracing/OpenTracingContext.java
78.95% <66.67%> (-9.94%)
0 <0> (ø)

Continue to review full report at Codecov.

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

Codecov Report

Merging #199 into master will increase coverage by 0.01%.
The diff coverage is 88.89%.

@@             Coverage Diff              @@
##             master     #199      +/-   ##
============================================
+ Coverage     71.95%   71.97%   +0.01%
  Complexity       10       10
============================================
  Files            87       87
  Lines          2660     2661       +1
  Branches        320      319       -1
============================================
+ Hits           1914     1915       +1
  Misses          525      525
  Partials        221      221

Impacted Files
Coverage Δ
Complexity Δ

.../com/uber/tchannel/tracing/OpenTracingContext.java
89.47% <88.89%> (+0.58%)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


List all hololive live streams

Implement a command !hololive to list all live streams of all hololive member.
(holostars, holo china and indonesia are excluded)

#4 Merged


Fixes #142 Removes unwanted components and libraries needed from npm

@aneeshd16 Please check the wall with this update, this hopefully shouldn't break the changes, I couldn't extensively test it.

Tested.

@prasht63 Can this branch be deleted after the merge? Please do if it is no longer needed.


Support call to LogonUser and LogonUserEx

Thanks @Connicpu for your feedback. First time that I use Winpr, first time that I participate to a opensource project, didn't know about the CONTRIBUTING.md... Thanks and sorry for all mistakes.

Hey it's no problem! :smile: We all have to learn somehow, right?

Absolutely, but not everybody accepts dumb mistake ;)  So Thanks to be patient !!

What should be rearranged ?

Github.... threw away my comments in the review? Wow, good job Github.

But the constant will be included in the extern "system" block, is it what we want ?  Where constant should be declared ? Why should I move them there ? Thx


Plantuml output for stream handling not rendered in documentation

The documentation at
https://daimler.github.io/sechub/latest/sechub-architecture.html#how-pds-provides-output-and-error-stream-content-of-running-jobs-in-clustered-environments
is not rendered correctly - maybe used plantuml on release build to old, or format has changed.
must be fixed

When adding

legend
<size:8> Rendered with Plantuml Version %version() </size>
end legend

and using an installed asciidoctor instance by eclipse plugin
I got:

So it is valid with Plantuml Version 1.2021.2

When executing
./gradlew documentation

I got the same problem on my local machine


Add support for latest OpenSuSE images

I would like to use the latest OpenSuSE images to test different Puppet modules using Travis CI.
At least Docker and Vagrant should work without any problemt, but I am not sure if additional docker_image_commands are necessary.

Can one of the admins verify this patch?

Could you rebase this?


No model.rda file in https://water.usgs.gov/GIS/dsdl/gwmodels/SIR2016-5080/model.zip

I'm trying to load R objects from model.rda. However, there doesn't appear to be a model.rda file in https://water.usgs.gov/GIS/dsdl/gwmodels/SIR2016-5080/model.zip after downloading file, unzipping, and copying contents to archive folder in working directory.

Should have included this file in the model archive, even though its not necessary for running the calibrated model. One suggestion is to grab it from here. Also, keep in mind that processing instructions exist for a wrv-training  course I gave a few years back.


Image Manifest config must allow any mediaType?

Following investigations in #1025 I noticed that a registry behaving like Quay.io can comply with the 1.1 spec but only allow an Image Manifest artifact with an artifactType of application/vnd.oci.image.config.v1+json.
Should this be a MUST or a SHOULD, or is the existing text already appropriate?
Signed-off-by: Bracken Dawson<EMAIL_ADDRESS>

I think if any change is needed to the config.mediaType description it probably belongs in #1043 now.


GPU resource manager cgroup support

This is an RFC only, don't merge. We could propagate the resource info like this via the allocation response annotations.
The first commit "gpu_plugin: fractional resource management" has it's own PR, so don't waste your time reviewing it here

Codecov Report

Merging #639 (de0e81d) into main (a207bfe) will decrease coverage by 5.21%.
The diff coverage is 3.93%.

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

@@            Coverage Diff             @@
##             main     #639      +/-   ##
==========================================
- Coverage   57.75%   52.54%   -5.22%
==========================================
  Files          31       32       +1
  Lines        2192     2421     +229
==========================================
+ Hits         1266     1272       +6
- Misses        853     1074     +221
- Partials       73       75       +2

Impacted Files
Coverage Δ

pkg/deviceplugin/api.go
25.00% <0.00%> (-2.78%)
:arrow_down:

cmd/gpu_plugin/gpu_plugin_resource_manager.go
0.94% <0.94%> (ø)

cmd/gpu_plugin/gpu_plugin.go
76.66% <10.00%> (-8.34%)
:arrow_down:

pkg/deviceplugin/server.go
84.82% <100.00%> (-1.51%)
:arrow_down:

Continue to review full report at Codecov.

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

Closing. To be revisited later.


Can't show * on the card

Hello,
I like your credit card library that's very amazing. However, I've tried any ways and still can't show "**** **** **** 1234" on the card. Would you mind if you can demo how to show "*" on the card?
Thank you.

Please refer to #53


The size of parentElement can be specified as the size when maximized by control

If matchParent:true is specified,
the size of parentElement (clientWidth, clientHeight) specified at initialization
is set to the size of maximized.
The default behavior matches the innerWidth and innerHeight of the window

If matchParent is specified
When maximizing, use the size of parentElement specified at initialization.
ParentlElement is often used only for adjusting the display order,
Therefore, only if matchParent:true is specified, match the size of parentElement


Version and package distribution fix

Coverage increased (+0.04%) to 68.15% when pulling 333817bbfcd3864153f61a9b9bf8fee67120fb72 on fix/version into 210e4255e60908ceb0cc5a6b3b71d234b985638c on master.


Add ClearSessions command to clear all user sessions

I don't see why this should be part of the framework. It seems too niche from my understanding of the code.
How likely one would want to disconnect all of their users?
I think this could belong to a project's code or as a 3rd-party package.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!


Add Client auth plugin and tls support for function to connect with broker

Motivation
If broker has authentication and tls enabled then function doesn't have support to pass auth data to broker.
Modifications
Add auth-plugin and TLS support at function to connect with broker.
Result
Function can connect to broker over tls and with custom auth-plugin

retest this please


Fails to build latest serde because of out-of-date nightly

I am hitting an issue with serde-derive building on docs.rs: https://docs.rs/crate/rtps/0.2.0/builds/31750
error: the `#[rustc_macro_derive]` attribute is only usable with crates of the `rustc-macro` crate type
 --> .cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.8.11/src/lib.rs:9:3
  |
9 | #[rustc_macro_derive(Serialize)]
  |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The relevant issue in the serde repository: https://github.com/serde-rs/serde/issues/567 .
It looks like the nightly in my build is from September -- perhaps updating it would help?
$ rustc --version
rustc 1.14.0-nightly (289f3a4ca 2016-09-29)

Yes updating would help, the rustdoc bug is fixed in rustc 1.14.0-nightly (9c31d76e9 2016-10-03).

I updated nightly but still getting same error: https://docs.rs/crate/rtps/0.2.1/builds/31776

I cloned rtps 0.2.1 locally and ran cargo doc with rustc 1.14.0-nightly (3210fd5c2 2016-10-05) and it worked. I can try to debug tonight.

@dtolnay can you give me rustc command used to compile serde_derive-0.8.11/src/lib.rs from cargo doc --verbose output?

rustc /home/david/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.8.11/src/lib.rs --crate-name serde_derive --crate-type rustc-macro -C prefer-dynamic -g -C metadata=a27bc5a26505dfc7 -C extra-filename=-a27bc5a26505dfc7 --out-dir /media/david/coding/github/rtps/target/debug/deps --emit=dep-info,link -L dependency=/media/david/coding/github/rtps/target/debug/deps --extern serde_codegen=/media/david/coding/github/rtps/target/debug/deps/libserde_codegen-d813637bf949d9ed.rlib --cap-lints allow

The difference is --crate-type lib vs --crate-type rustc-macro.
You are going to need a new cargo in order to pick up https://github.com/rust-lang/cargo/pull/3064. I am using cargo 0.13.0-nightly (a713da1 2016-10-05).

Yes need to start using a newest version of cargo in cratesfyi.

@onur is there anything I can do to help?

I've updated cargo and [serde_derive](https://docs.rs/serde_derive) is building fine now.
But for some reason rtps is still failing to build.
I also tried to build rtps on my local machine (rustc 1.14.0-nightly (6dc035ed9 2016-10-15)) and it says:
error: loading custom derive macro crates is experimentally supported (see issue #35900)
  --> src/lib.rs:16:14
   |
16 | #[macro_use] extern crate serde_derive;
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: add #![feature(proc_macro)] to the crate attributes to enable

error: loading custom derive macro crates is experimentally supported (see issue #35900)
  --> src/lib.rs:16:14
   |
16 | #[macro_use] extern crate serde_derive;
   |              ^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: add #![feature(proc_macro)] to the crate attributes to enable

error: aborting due to 2 previous errors

error: Could not compile `rtps`.

I believe this issue is fixed in docs.rs and rtmp may need an update for #![feature(proc_macro)] definition.

This ticket should be reopened as the problem persists. The rustc version is fine but I think the issue may be an older cargo. Here is a recent travis build of rtps which compiles fine: https://travis-ci.org/xdds/rtps/builds/168725503 (this is the version 0.2.3 I published one day ago).
What version of cargo is the service using?

@xrl I updated cargo again and looks like everything is working fine now.
BTW clippy is only working on very latest nightly and docs.rs isn't periodically updating nightly ATM. It's better idea to use clippy as a optional dependency. See #54, #62.

@onur thanks, this is great news! I will take your advice on clippy, it is my highest maintenance dependency.


Kernel dies when using weighted C-SVC

I am trying to train an SVM model from python with the following parameters -s 0 -t 0 -c 1 -b 1 -u 0 -w1 10 -w-1 1 and my Jupyter kernel dies. If I train with -s 0 -t 0 -c 1 -b 1 -u 0 it trains fine. I am importing the functions from svm.py and running them inside a jupyter notebook on a Python 3.5.2 conda environment on a Ubuntu Linux VM.

Thanks for your feedback. I found the bug on command line parser and I have already fixed it. You can update code and try again.

Yep, looks good. Unbelievably fast response


{Network} Add an example in command az network application-gateway waf-policy policy-setting update

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Network


Update OWNERS_ALIASES

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign vinaykumar01
You can assign the PR to them by writing /assign @vinaykumar01 in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: so-abahadur
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [so-abahadur]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: so-abahadur
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [so-abahadur]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: so-abahadur
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [so-abahadur]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: so-abahadur
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [so-abahadur]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Pass in dynamic prop to "react" based on "to" email

This isn't really an issue but discussions aren't enable, so here I am. I am in a situation where I want to send emails to a group of people, lets say 10-20 email addresses. However, I would like to customize it with "Dear John Doe" or "Dear Jane Doe", you get the point. However, I don't know of a way other than to create an await resend.emails.send({}) for each email address. Is there a way that I could possibly avoid that or what's the best practice around that?

If you're using the react key, you can pass the email component like this
"react": MyEmail({ name: "James" })

If you're using the react key, you can pass the email component like this
"react": MyEmail({ name: "James" })

But that name will be different between the let’s say 10-20 emails I’m sending the email to.

Can you share the code you're currently using? I'm assuming that you have a loop in a contacts array

So this is what my /app/api/send/route.ts looks like
import { NextResponse } from 'next/server'
import { Resend } from 'resend'

import EmailTemplate from '@/emails/emailTemplate'

const resend = new Resend(process.env.RESEND_API_KEY)

export async function POST(request: Request) {
  const { name, email, message, subject } = await request.json()

  try {
    const data = await resend.emails.send({
      from: `Email From <${process.env.EMAIL_FROM_ADDRESS}>`,
      to: [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>      ],
      reply_to: email,
      subject: subject,
      react: EmailTemplate({ name, email, subject, message }),
    })

    return NextResponse.json(data)
  } catch (error) {
    return NextResponse.json({ error })
  }
}

Which is the basic example provided in the README.

@bukinoshita any ideas here?

@JamesSingleton It wouldn't make sense that you could send a single email to multiple people, with that email having different content for each recipient.
The appropriate way to handle this would be to map your contacts into an array of emails, then use the batch function to send one those out.
Cheers!

Ah! I didn’t know about the batch functionality! Thanks for pointing that out!


Minor edit - fixed broken links

I have made the minor edits to add log capture and prometheus in the list of docs. Can your review them?


ARTEMIS-2941 Improve JDBC HA connection resiliency

https://issues.apache.org/jira/browse/ARTEMIS-2941

I've run the CI tests on this and it's not causing regressions :+1:

I've removed a byteman test that was relying on something that was already broken before this PR ie the number of tryLocks on FileLockNodeManager.


checkov: 2.4.41 -> 2.4.42

Diff: https://github.com/bridgecrewio/checkov/compare/refs/tags/2.4.41...2.4.42
Changelog: https://github.com/bridgecrewio/checkov/releases/tag/2.4.42
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 256184 run on x86_64-linux 1

2 packages built:

checkov
checkov.dist


fix: 🐛 ignore github ID for typos check

Related issue (if exists)

Summary

🤖 Generated by Copilot at b05da09
Fix .typos.toml configuration and add custom spelling for JSerFeng. This change improves the accuracy and consistency of the typos tool for checking spelling errors in the codebase.

Walkthrough

🤖 Generated by Copilot at b05da09

Add a new section default.extend-identifiers to the .typos.toml file to customize the spelling of certain identifiers that are not recognized by the typos tool (link)
Remove the duplicate entry for **/CHANGELOG.md from the default.exclude array in the .typos.toml file, as it is already specified in the previous line (link)

Oh, we should just ignore GOVERNANCE.md


WIP: Reorganize docs

Codecov Report

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

@@          Coverage Diff          @@
##           master   #115   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           5      5
  Lines         190    190
=====================================
  Hits          190    190

Continue to review full report at Codecov.

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

Closing this out for now. Will take another stab at organizing the docs later


Feat: Adding Blogger Scraper

Describe the feature
The scraper will allow users to retrieve articles from Google Blogger based on a specified topic. The feature will include a Blogger class with a method that scrapes article titles and links from the Google Blogger search results page for the given topic.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

Hey @MavSneha, I just checked that the Blogger module is not working, so it doesn't make any sense to write test case for a module that is not working.
Fix it if you can (raise a separate issue for that) then we can continue with this issue.
Closing it for now!

@nikhil25803 Sir should I contact project mentors to get this resolved?
Sugam Arora
Yashwanth R


Make t-dapicker above all other dives

Hi.
I'm planning to use your beautiful plugin as picker only.
I've added the html code to my Bootstrap modal content.
The problem is the the height of my modal is small, and when I click on my picker div, the calendar is shown but it is not above the modal, it creates scroll.
I can't understand how to make calendar appear above all other html blocks on my page.
Thank you in advance!
In attachments there are what I have now, and what I really need.

Hi @luntik4344
I have checked css-style t-datepicker with bootstrap modal. You can see demo.


Increase test coverage for unbounded and bounded cases

Which issue does this PR close?

Closes #.
Rationale for this change
In the PR we parametrize tests to increase test coverage. This PR extends this PR so that tests consider unbounded, and bounded sources when prefer_existing_sort flag is false and true.
All of the changes are in tests. This PR effectively increases test coverage.

What changes are included in this PR?

Are these changes tested?
Yes

Are there any user-facing changes?

Since this doesn't change any code excepts tests I will go ahead and merge it to let code flow. In case of any future issues related to this PR, we will quickly address with follow-ons.


feat: add log viewer options

Whenever I view the logs of a pod, I always set the same options pretty much. ^-^'
This just creates some global settings which sets the default log viewer options.
For now, it only covers follow, timestamp and wrap.
I'm considering doing others later, but figured for now this would be nice.
It looks to me (though I didn't check manually) that the reset() method wasn't resetting the wrap checkbox anyway, so this also fixes that.

While we're at it, I'm just wondering about this. 🤔
// eslint-disable-next-line @typescript-eslint/prefer-for-of
for (let i = 0; i < newContent.length; i += 1) {
    if (newContent[i].length > 0) {
        content[counter] = newContent[i];
        fpcCounter++;
        fullPageContent[fpcCounter] = newContent[i];
        counter++;
    }
}

Is there a reason you're not using a for-each? I normally would change this without asking, but given in the repo the warning it explicitly disabled too, I wanted to ask about it.

While we're at it, I'm just wondering about this. thinking
// eslint-disable-next-line @typescript-eslint/prefer-for-of
for (let i = 0; i < newContent.length; i += 1) {
    if (newContent[i].length > 0) {
        content[counter] = newContent[i];
        fpcCounter++;
        fullPageContent[fpcCounter] = newContent[i];
        counter++;
    }
}

Is there a reason you're not using a for-each? I normally would change this without asking prior, but given in the repo the warning is explicitly disabled too, I wanted to ask about it.

The log viewer has a long and troubled history as it changed quite a bit lately. I guess this was made during some performance enhancement PRs. First we showed all logs in a single push but it was slow when highlighting all words based on a list of regexes and the logs were > 10MB. So we tried to optimize every thing we could. Using objects instead of arrays, pagination, reduce the number of regexes. I guess I also switched to the old style for which could make me earn some ms of execution. Maybe after pagination and all other changes this is not necessary anymore but i didn't look at it anymore honestly.

Moved the config to the centralized config.ts.
Changed some wording for consistency. (Trying to use the term "Settings" everywhere rather than switch between "Options" or "Settings".
Add a "Save Settings" button in the webview which saves the 3 settings.

Note, for now this is only allowing follow, timestamp, and wrap to be configured and saved. However, I'll happily do the other settings too, plus the "Run" by default.
Maybe I can do those in a separate PR, though?
I'd like if we can just establish if we're happy with the structure of this first, then I can just follow-through for the rest.

Ignore the other default values like 0 or seconds. (That's for a separate PR I was working on. Just subjective usability improvement and refactors, but that's out of scope for this PR.)

@SethFalco could you please rebase it? Thanks!!

Rebased and conflicts resolved. 👍🏾

Hmm, the failed test seems odd. 🤔
Could we maybe do a retry to see if that was a random timeout first?

It cure looks like a random timeout - I've re-started the actions.

Ahh, sorry about that.
Just a few minutes ago I was looking at this and wanted to tweak setSettings a bit, so I force-pushed there anyway. ^-^'
Thought for future, it'd be better if it took an options object rather than a bunch of parameters.
That way in future to set particular settings we could just do:
setSettings({
  sinceSelect: 1
});

Instead of something like:
setSettings(null, null, null, 1);


Customize Peer Interface

Request New Feature.
We can change the key public key with the network traffic . If you can be select the fields to display. that's great

It's a great project.
Thanks so much.

Customizing the UI is currently not supported. But you can change the HTML template and re-compile the project yourself...


Update external docs

@jschuler how did you get variables updated on those. I have logged #94 for it

@wtrocki I think these variables get replaced further up the pipeline? Within the guides repo they are not resolved, but in prod they are. Not exactly sure where they get injected, @pmuir will know

Ok. So this is more or less localhost problem that we can ignore or fix later

@jschuler -- looks good from my end. Thanks!

@jciroli-rh a11y update will be handled in this issue https://github.com/cloudmosaic/quickstarts/issues/44

@jschuler Looking again, the icon update looks good 👍
But now the order has changed. The original order, and the order in the document is what I would expect. Is that something you're able to control?


Include a .gitignore in the rpm directory

Makes it easier for people to update and build the rpms

Added to rollup. Thanks!


[auto-bump] dependency by tbantle22

:coffee: An Automated Dependency Version Bump PR :crown:
Initial Changes
The initial changes contained in this PR were produced by `go get`ing the dependency.
```
$ cd ./go
$ go get github.com/dolthub//go@
$ go mod tidy
```
Before Merging
This PR must have passing CI and a review before merging.
After Merging
An automatic PR will be opened against the LD repo that bumps the bounties version there.

This PR has been superseded by https://github.com/dolthub/bounties/pull/2446

This PR has been superseded by https://github.com/dolthub/bounties/pull/2447


Fix inconsistent indentation in label doc for custom text classification

Was a bit confusing while trying to catch validation errors with my document.

@microsoft-github-policy-service agree

@jboback
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@sign-off

#sign-off


Allow firing undeclared signals

Because I love the brand new Signal system, may I request this?
To make more "fire and forget" Signal system, calling Fire() regardless whether the signal is declared is better I thought. Imagine this situation:
You have VideoPlayer class that fires VideoPlayer.OnPauseSignal (nested in VideoPlayer class). VideoPlayer is used in both SceneA and SceneB. In SceneA, OnPauseSignal is used to invoke some action but not in SceneB. In this case, you want to declare OnPauseSignal only in the SceneContext of SceneA, don't you?
With C# delegate(or event), you can check if the delegate is null or not. With UnityAction, nothing happens if the action have no listeners. So we need some workaround for Signals.

Makes sense.  Thanks


Basic OpenVDB read support

Description
Add OpenVDB reader to OIIO
Tests
Not yet, no
Checklist:

[x] I have read the contribution guidelines.
[x] If this is more extensive than a small change to existing code, I
have previously submitted a Contributor License Agreement
(individual, and if there is any way my
employers might think my programming belongs to them, then also
corporate).
[x] I have updated the documentation, if applicable.
[x] I have ensured that the change is tested somewhere in the testsuite
(adding new test cases if necessary).
[x] My code follows the prevailing code style of this project.

As I remember TBB was required as somewhere deep in VDB headers it was being pulled in.
But I'll investigate and make sure it wasn't from inclusion of something not included here.

TBB indeed needs to be visible for compile & link.
Split out TBB to be a separate CMake object.
Added cached variables OPENVDB_LOCATION for TBB_LOCATION.
Might still need to be an update to travis & appveyor to run the test.

CI seems to show not having VDB doesn't break the build, is it worth trying to get it supported there?

LGTM, except that I tried to check on my laptop and it failed to find TBB. Offline, Roman and I discussed and he's going to substitute a different FindTBB.cmake, the one from USD, which seems to work better.

Correct, not having VDB should not break the build.
I'll go back later and adjust the travis files to make sure openvdb is installed (at least on Mac, where it's easy thanks to Homebrew) so that this feature is exercised. You can try that, too, if you want, but no big deal if you want to move on and I'll take care of it separately.

Seems good here, probably worth trying to make sure it works as expected on OS X.
Next travis build should give it a try..

On OSX (both on my laptop and Travis), its finding TBB but not finding OpenVDB. Not sure why.

Could NO_DEFAULT_PATH in FindOpenVDB.cmake:66 be the culprit? Seems I stripped that from the header portion but not the library.

Updated test to not use blosc, are you going to push something on top with the working CMake or is that something to be done here?

I'm happy to do it (since I already made the changes on my end to test it).
Should I merge what you have and then send a separate PR for that? Or should I push back to your branch to make it all one merge (you need to have checked the box that lets me push to your branch, for that to work)?

I'll push the button..

Builds on OSX and passes the unit test!
I'm going to add some touch-ups and then push back so you can see and approve.

Great thanks...Out of curiosity the VDB library was 4 or 3?

5

OK, I pushed some minor fixes on top of yours. A lot was just minor cleanup I would have done at some later time as I touched up the docs or prepared for a release.

The original FindOpenVDB.cmake was unreliable. Replaced with one found  elsewhere on the net (from Blender, bearing a BSD license).

Makefile wrapper: directly use OPENVDB_ROOT_DIR

Update INSTALL.md and oiiointro.tex to document the new optional      dependencies and how we incorporated those two new Find*.cmake files      from other projects (with appropriate licenses).

Simplification of the TBB and OpenVDB sections of externalpackages.cmake,      they didn't need to be quite so verbose, didn't need to -UUSE_BLAH if not      found, did not need to set BLAH_FOUND (done by the FindBlah itself),      and I added minimum versions of both packages based on this year's      VFX Platform guidelines (as a forward-looking new feature in master,      I don't feel the need to verify support of older versions).

Update oiio docs chapter on supported formats to include OpenVDB.

Some extremely minor formatting and whitespace fixes in      openvdbinput.cpp to conform to prevailing project style.

Simplification of the SPI-specific Makefile-bits.

Minor touch of field3d to add "worldtolocal" metadata to conform to the      new convention we're using with vdb.

Everything seems to work as was, so I'd say good to go.
Left two little comments above, but totally fine if you want to show them to the waste-bin.


publish_to fir. android release failed

Successfully packaged build/1.0.0+1/abc-1.0.0+1-android.apk
RELEASE FAILED in 47s
Exception: Missing ANDROID_HOME environment variable.
#0      AppPackageParserApk.parse (package:parse_app_package/src/parsers/apk/app_package_parser_apk.dart:14:7)
#1      parseAppPackage (package:parse_app_package/src/parse_app_package.dart:15:17)
#2      AppPackagePublisherFir.publish (package:flutter_app_publisher/src/publishers/fir/app_package_publisher_fir.dart:68:37)
#3      FlutterAppPublisher.publish (package:flutter_app_publisher/src/flutter_app_publisher.dart:30:28)
#4      FlutterDistributor.publish (package:flutter_distributor/src/flutter_distributor.dart:251:56)
#5      FlutterDistributor.release (package:flutter_distributor/src/flutter_distributor.dart:345:19)

#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)

name: dev-android
package:
platform: android
target: apk
skip_clean: true
build_args:
target-platform: android-arm64
publish_to: fir

ios is right

publish_to pgyer is right

variables:
FIR_API_TOKEN: "sdasnjsadhsakdashjkdgaskhjgd"
output: build/
releases:

name: dev
jobs:

name: dev-android
package:
platform: android
target: apk
skip_clean: true
build_args:
target-platform: android-arm64
publish_to: fir
name: dev-ios
package:
platform: ios
target: ipa
skip_clean: true
build_args:
export-method: development
publish_to: fir

需要在环境变量里配置你的 ANDROID_HOME


ArchiveFiles: empty files created

Question, Bug, or Feature?
Type: Bug
Task Name: ArchiveFiles: empty files created
Environment
Using Azure Pipelines

Account name: mscodehub
Team name: MicrosoftManagementPlatform-Core

Using the Hosted agent in the Hosted Ubuntu 1604 agent pool
Issue Description
Pointing the ArchiveFiles task on a directory with files only creates an archive with a "b" folder inside. Just for debugging purposes, i executed a bash script with "tree ." as the command with the same workingFolder as the ArchiveFiles sourceFolder and all the files are clearly present, but the ArchiveFiles task doesn't pick them up.
Attached logs
logs_97217.zip

Hey @AhmedBM ,
Could you provide the following information:

The yaml you are using

From what I see, your pipeline contains the following:

Copy Artifacts to Build.ArtifactStagingDirectory
Archive Files via a zip file from Build.BinariesDirectory to Build.ArtifactStagingDirectory
Archive Files via a tar.gz file from Builds.BinariesDirectory to Build.ArtifactsStagingDirectory.
Publish the tar.gz file generated
Publish the zip file generated.

I don't see where you set up files to be in the Build.BinariesDirectory, where do files get populated into that folder?

Closing since we didn't get a response on this. If this is still an issue feel free to comment with the info requested and we can reopen.


I believe there is no other callback missing for filter_with/2 to work properly. WDYT?
Related to #289


Unable to start Atom: "dyld: Symbol not found: _CIDetectorTypeText"

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Atom 1.28.0 fails to start on OSX 10.10.1
Steps to Reproduce

Start Atom as usual from the Applications folder, Spotlight, or the command line

Expected behavior: [What you expect to happen]
App to launch as usual
Actual behavior: [What actually happens]

When started from Finder/Spotlight, a popup window appears which states Atom cannot be opened because of a problem.

When started from the command line with /Applications/Atom.app/Contents/MacOS/Atom, the error text is:

dyld: Symbol not found: _CIDetectorTypeText
  Referenced from: /Applications/Atom.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework
  Expected in: /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
 in /Applications/Atom.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework
Trace/BPT trap: 5

When started with atom --safe, the error text is

LSOpenURLsWithRole() failed for the application /Applications/Atom.app with error -10810.

Reproduces how often: [What percentage of the time does it reproduce?]
100% of the time; unable to start Atom normally
Versions
The Atom version commands are not working. They cause the "Atom cannot be opened because of a problem" popup to appear.
I downloaded the latest version of Atom (1.28.0) and replaced my previous installation with it, but the result was the same.
OSX Yosemite 10.10.1
Additional Information

I have tried re-downloading Atom and reinstalling it, which made no difference to the error

I have tried removing ~/.atom, which made no difference

I have tried restarting my system several times

The issue seems to have started after two instances of the program opened following a system restart, but both hung and had to be force quit. Googling the specific dyld error message I receive in the console yields no relevant results.

P
On Fri, Jun 22, 2018, 9:00 PM textchimp<EMAIL_ADDRESS>wrote:

Prerequisites

Put an X between the brackets on this line if you have done all of
the following:

Reproduced the problem in Safe Mode:
https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide:
https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions:
https://discuss.atom.io/c/faq
Checked that your issue isn't already filed:
https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides
the described functionality: https://atom.io/packages

Description
Atom 1.28.0 fails to start on OSX 10.10.1
Steps to Reproduce

Start Atom as usual from the Applications folder, Spotlight, or the
command line

Expected behavior: [What you expect to happen]
App to launch as usual
Actual behavior: [What actually happens]

When started from Finder/Spotlight, a popup window appears which
states Atom cannot be opened because of a problem.
When started from the command line with
/Applications/Atom.app/Contents/MacOS/Atom, the error text is:
dyld: Symbol not found: _CIDetectorTypeText
Referenced from: /Applications/Atom.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework
Expected in: /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
in /Applications/Atom.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework
Trace/BPT trap: 5

When started with atom --safe, the error text is

LSOpenURLsWithRole() failed for the application /Applications/Atom.app with error -10810.
Reproduces how often: [What percentage of the time does it reproduce?]
100% of the time; unable to start Atom normally
Versions
The Atom version commands are not working. They cause the "Atom cannot be
opened because of a problem" popup to appear.
I downloaded the latest version of Atom (1.28.0) and replaced my previous
installation with it, but the result was the same.
OSX Yosemite 10.10.1
Additional Information

I have tried re-downloading Atom and reinstalling it, which made no
difference to the error
I have tried removing ~/.atom, which made no difference
I have tried restarting my system several times
The issue seems to have started after two instances of the program
opened following a system restart, but both hung and had to be force quit.
Googling the specific dyld error message I receive in the console
yields no relevant results.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/17565, or mute the thread
https://github.com/notifications/unsubscribe-auth/AJxdGwuhMVYlmOk0-GTYwyMKeLygg5Lzks5t_b1KgaJpZM4U0oaA
.

Same here on MacOSX 10.9.5 and atom 1.28.0 (obtained via apm --version, since atom --version does not work). The error occurred from evening to morning: yesterday everything was fine, today atom does not start. Possibly a regression due to an automatic update to version 1.28.0?
Moreover, before getting this error I had the following error
user$ /Applications/Atom.app/Contents/MacOS/Atom
  dyld: Library not loaded:
    /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
  Referenced from: /Applications/Atom.app/Contents/Frameworks/Electron
  Framework.framework/Versions/A/Electron Framework
  Reason: image not found
  Trace/BPT trap: 5

but I solved it using
user$ sudo ln -s /System/Library/Frameworks/IOBluetooth.framework/Frameworks/CoreBluetooth.framework /System/Library/Frameworks/CoreBluetooth.framework

I also can't start Atom 1.2.8 suddenly not anymore on OSX 10.10.5. It still worked yesterday.
Process:               Atom [708]
Path:                  /Applications/Atom.app/Contents/MacOS/Atom
Identifier:            com.github.atom
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Atom [708]
User ID:               501
Date/Time:             2018-06-23 18:09:50.574 +0100
OS Version:            Mac OS X 10.10.5 (14F2511)
Report Version:        11
Anonymous UUID:        F597F35C-D5C4-9689-B920-882F606AE052
Time Awake Since Boot: 2900 seconds
Crashed Thread:        0
Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Symbol not found: _CIDetectorTypeText
Referenced from: /Applications/Atom.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework
Expected in: /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
in /Applications/Atom.app/Contents/MacOS/../Frameworks/Electron Framework.framework/Electron Framework

Same here on OSX 10.10.5, except I don't see a popup - Atom 1.28.0 just silently fails to open.
Downgrading to Atom 1.27.2 solved it for me.

How did you downgrade? Could you describe the process?

https://github.com/atom/atom/releases

Ok, I was expecting that answer... I mean, if I delete my current version of Atom 1.28.0 and reinstall Atom 1.27.2, then do I loose all the package I installed and all the configurations I set?

Reverting to 1.27.2 working for me so far (the sudo ln -s move came up empty for me). Thanks, jamols and lebenspuls!

@sir-ion: no config / package issues here, just drop 'Atom.app' from the 1.27.2 .dmg into /Applications (and disable auto-updates if necessary)

I can also confirm that reverting to 1.27.2 is working for me (with my original .atom folder). Thanks for this suggestion.

Worked for me as well, but there is a gotcha: if you have autoupdates enabled it'll only start once. So essentially what you have to do is to
1/ download Atom 1.27.2
2/ unzip it
3/ launch it
4/ disable auto updating
5/ delete the previously extracted Atom executable
6/ unzip it again and move it to /Applications

same problem, had to fully remove, and then download 1.27.2, and followed oditorium's to do list.  and it works.  note: to disable auto updating, once atom is open, go to the menu option "ATOM", then "About Atom", and you'll see the checkbox there to install updates.  uncheck that.  notes: number 5 and 6 seem strange, on oditorium's suggestion, but it is how it will work.

I'm unable to reproduce with macOS 10.12.6 but  it looks like everyone hitting this that mentioned their macOS version was on macOS 10.10.x or earlier.
About this error:

dyld: Symbol not found: _CIDetectorTypeText

I found this Electron issue that looks related?  x-ref: https://github.com/electron/electron/issues/13404.

Same for me, macOS 10.10.5

i’ve the same problem!
https://discuss.atom.io/t/atom-crashes/56261
1.28 worked, now it doesn't.
and
1.29 doesn't work
Downgrading worked, thanks for help
1.27 WORKS
what happened with other versions?

Same for me, now I downgraded I got this annoying popin, telling me the linter package is not compiled with the same node version. Too bad.
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 54. Please try re-compiling or re-installing

Hey folks, thanks a lot for all the issue reports!  We need a bit of help determining which version of Atom/Electron this issue started happening in.  Could someone who sees this crash try both of these releases and let me know if the problem still exists on either one:

Atom 1.28.0-beta0 / Electron 2.0.0: https://github.com/atom/atom/releases/tag/v1.28.0-beta0
Atom 1.28.0-beta1 / Electron 2.0.1: https://github.com/atom/atom/releases/tag/v1.28.0-beta1

This will help us determine the version of Electron where this issue started to occur.
Thanks a lot for your help!

Both version runs smoothly on my MacOSX 10.9.5 (but I still get the error using atom 1.28.0).
I run beta versions both with "double-click" from the finder and using terminal (no output at all, all clean).

Thanks @sir-ion, that was helpful!

Running on MacOSX 10.10.5:
Atom 1.28.0-beta0 works
Atom 1.28.0-beta1 works
Atom 1.28.0-beta2 works
Atom 1.28.0-beta3 works
Atom 1.28.0 crashes

1.28.0 same issue OS X Yosemite

Same issue: Atom cannot be opened because of a problem.
ATOM v1.28.0
OS X Yosemite v10.10.5

Here with same problem and return/revert to v1.27.2 worked (albeit I had to reinstall twice to thwart auto-updates).
Commenting merely to get thread notifications. Thanks!

Phew! Excuse me while I change my underpants...

We need a bit of help determining which version of Atom/Electron this issue started happening in

I think this is not a problem with Electron itself, but with how it was built, or rather on what version of the OS it was built.
There is a simple general rule of thumb for complex software where you cannot easily control the SDK against which the build has to be made (= the oldest supported OS version): build on a system running the oldest OS version.

We need a bit of help determining which version of Atom/Electron this issue started happening in

I think this is not a problem with Electron itself, but with how it was built, or rather on what version of the OS it was built.
There is a simple general rule of thumb for complex software where you cannot easily control the SDK against which the build has to be made (= the oldest supported OS version): build on a system running the oldest OS version.

Same exact issue as OP down to the error messages, downloading v1.27.2 worked. Mac OS X 10.9.

Same issue. I have a Macbook Air 2014. Had to download Atom 1.27.2 remove auto-update and deleted my prefs. argh.

According to https://github.com/electron/electron/issues/13459#issuecomment-400878134, Electron v2.0.3, which Atom v1.28.0 is built on, uses a version of Chromium that will not run on versions of macOS prior to version 10.10. I realize that some of you are running versions of macOS 10.10.x, but at least it is a partial explanation.

This issue is resolved in https://github.com/atom/atom/pull/17620, and we're actively working on publishing this fix as part of Atom 1.28.1 and Atom 1.29.0-beta1.
Once those releases are published, Atom should once again run on OS X 10.10.x. 💦

Atom 1.28.1 and Atom 1.29.0-beta1 are now available and should resolve this issue for anyone using Atom on OS X 10.10 Yosemite. Additionally, if you're seeing this issue on OS X 10.11 El Capitan or macOS 10.12 Sierra, please give this update a try and let us know if you continue to experience the problem.

I can confirm this is working for me on OS X 10.9.5 👏

Thanks for getting this fixed 👍


Reading LibSVM datasets

Discussed in #72, LibSVM have some really awesome and large datasets that might be good for benchmarking and also might be crucial for people wanting to try out golearn. Probably need a new FixedDataGrid which stores things in the LibSVM memory format, as well as the parsing functions.

good


installation trouble

I am having trouble installing. Do you have any ideas?
$ rake install --trace

rake aborted!
LoadError: cannot load such file -- bundler/gem_tasks
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require' /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'
/home/jose/ruby/dozedois/Rakefile:1:in <top (required)>' /usr/lib/ruby/vendor_ruby/rake/rake_module.rb:28:in load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:28:in load_rakefile' /usr/lib/ruby/vendor_ruby/rake/application.rb:689:in raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:94:in block in load_rakefile' /usr/lib/ruby/vendor_ruby/rake/application.rb:176:in standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:93:in load_rakefile' /usr/lib/ruby/vendor_ruby/rake/application.rb:77:in block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:176:in standard_exception_handling' /usr/lib/ruby/vendor_ruby/rake/application.rb:75:in run'
/usr/bin/rake:27:in `'

$ ruby --version

ruby 2.3.0p0 (2015-12-25) [x86_64-linux-gnu]

$ rake --version

rake, version 10.5.0

looking

@jsta what version of bundler do you have

able to reproduce with that ruby version, i was on 2.2.3,
fixing some stuff

I solved it on my end. First I (re?)installed bundler and a ruby development environment:

$ sudo gem install bundler
$ sudo apt-get install ruby-dev

$ rake install was still giving me and error so I tried:

$ gem install /home/jose/ruby/dozedois/pkg/dozedois-0.0.9.gem
ERROR:  While executing gem ... (Gem::FilePermissionError)     You don't have write permissions for the /var/lib/gems/2.3.0 directory.

which was solved by:

$ sudo rake install

great, glad you sorted it out. I had to do the same, had to reinstall bundler after switching to ruby v2.3.1
I'll add to readme that sudo may be required
note to self: https://github.com/bundler/bundler/issues/4602


Minor spelling typos

Describe the bug
A typographical error on one of the pages
To Reproduce
Steps to reproduce the behavior:

Go to 'https://react-hook-form.com/advanced-usage/#TransformandParse'
Go to line 2
11th word

V7

JS Template
TS Template

V6

JS Template
TS Template

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

ty, would you like to send us a PR?

Sure, I'd like to do that.


Fixed #31314 -- Raised CommandError when locale is not specified in makemessages.

makemessages needs either the --locale, --exclude, or the  --all flag to work properly. Failure to pass one of those three flags should result in CommandError, but that is currently broken because of a small bug.
This PR fixes this issue, which has been reported as ticket #31314 in the issue tracker.
https://code.djangoproject.com/ticket/31314

@cmackenziek Thanks :+1: I pushed minor edits to tests.
Welcome aboard :boat:

I just scratched my head for an hour trying to figure out why I was getting CommandError: Type 'manage.py help makemessages' for usage information. when using plain old makemessages (as I've always done). I finally found I needed to pass in --all or a locale although I never used to. It would be great if the message was a little more helpful and specified that the locale is required but missing?


[FEATURE] Added a Navbar

Added a Floating Navbar
Smooth Scrolling To Components - Collections, Products, Footer
Below are the screenshots

@pooranjoyb Hey! Please review the PR.

Sorry accidently closed it

Hii can you use the Glassmorphism UI, rather than a solid color? @Vedant5751

Which one do you prefer?
White/Transparent

Lighter Green

More Opaque Green

@Vedant5751 I suggest that you don't fix the navbar at the top, because its covering all section's heading.

@Mahitej28 so u just want a simple broad wrapper at the top? Do u want me to include this to ur existing navbar (with pop shop.com and cart icon) or make a navbar above that part?

@Mahitej28 so u just want a simple broad wrapper at the top? Do u want me to include this to ur existing navbar (with pop shop.com and cart icon) or make a navbar above that part? or just remove the sticky attribute from my navbar?

Just remove the sticky attribute because its overlapping with the heading of different sections while scrolling.

@Mahitej28 so u just want a simple broad wrapper at the top? Do u want me to include this to ur existing navbar (with pop shop.com and cart icon) or make a navbar above that part? or just remove the sticky attribute from my navbar?

Just remove the sticky attribute because its overlapping with the heading of different sections while scrolling.

its done , check the new pull request i made


ja: Make docs/reference/glossary/configmap.md follow v1.18 of the original text

This is a Feature Request

What would you like to be added
Update docs/reference/glossary/configmap.md to follow v1.18 of the original (English) text.
Why is this needed
content/ja/docs/reference/glossary/configmap.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/blob/dev-1.18-ja.1/content/ja/docs/reference/glossary/configmap.md
Original
https://github.com/kubernetes/website/blob/fb6364d/content/en/docs/reference/glossary/configmap.md
diff between translated and v1.18
https://gist.github.com/fd3ad5bfc035f20d1e75321d36cd215d
Note
Currently, we use dev-1.18-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/assign

@kakts 対応済みのように見られます。

@yu-kasuya
ご確認ありがとうございます。　こちら確認したところ確かに対応済みでした。
https://github.com/kubernetes/website/blob/dev-1.18-ja.1/content/ja/docs/reference/glossary/configmap.md
こちらcloseいたします


Move policy package over to asynchronous IPCache API

Meta: https://github.com/cilium/cilium/issues/21142
Depends on:

[x] https://github.com/cilium/cilium/pull/19765
[x] https://github.com/cilium/cilium/pull/21413
[x] https://github.com/cilium/cilium/pull/21414

Convert the daemon over to using the new IPCache interface which handles
merging of metadata from multiple sources. As a side effect, we can
clean up some of the identity refcounting/management handling code from
the daemon in favour of the core code in pkg/ipcache.
This patch may subtly change the ordering of operations for policies
that have {to,from}CIDR{,Set} rules in them. Previously:

Figure out the prefixes
Synchronously allocate identities for the prefixes
Regenerate policy for all relevant endpoints
Trigger IPCache updates asynchronously, including
4a. Trigger SelectorCache / policy updates via IPCache
4b. Update datapath IPCache

Step (2) may now occur after 3 but will continue to occur before (4).
This means that step (3) will only prepare the SelectorCache and policy
constructs associated with the endpoints, but not associate the new
identities for the CIDRs to those policy constructs. That latter step is
deferred to the incremental "identity update" logic in (4a).

/test

/test

runtime job hit known flake https://github.com/cilium/cilium/issues/24342. Re-running.

/test

/test

Cilium L4LB XDP job hit https://github.com/cilium/cilium/issues/24728
runtime job hit https://github.com/cilium/cilium/issues/22373

/test-runtime

/ci-l4lb

I really don't understand how deletion of stale prefixes is supposed to happen here; I'm particularly confused about the interplay between the PrefixLengthCounter, the local Allocator, and the metadata cache. We seem to have two refcounts, but then we immediately delete from the metadata cache without checking any of these?
This is made more difficult to understand because it is InjectLabels, a.k.a. the "final" stage in updating, that manages identity (de)allocation. How do we prevent races here?
If there is some sort guarantee here that I'm missing, it would be good to explicitly call out.

I really don't understand how deletion of stale prefixes is supposed to happen here; I'm particularly confused about the interplay between the PrefixLengthCounter, the local Allocator, and the metadata cache.

Yes indeed, PrefixLengthCounter is adding unnecessary complications here. That code is actually doing nothing at this point, we should just remove it (cf. https://github.com/cilium/cilium/issues/22116).

We seem to have two refcounts, but then we immediately delete from the metadata cache without checking any of these?

I think I alluded to this in the prior work in https://github.com/cilium/cilium/issues/21142 and https://github.com/cilium/cilium/pull/19765, but I recognize that it's not super explicit and much of it is also before your time. I think that my response in the thread above should hopefully provide enough background that this makes sense.

This is made more difficult to understand because it is InjectLabels, a.k.a. the "final" stage in updating, that manages identity (de)allocation. How do we prevent races here?

More and more we're moving that identity logic into InjectLabels() for all local identity use cases - for the special kube-apiserver logic (the original motivation), for node manager (https://github.com/cilium/cilium/pull/23208), for policy (here), etc.
Until we achieve that, we mostly assume that each subsystem either allocates and deallocates references in a balanced way, or explicitly avoids performing any of that identity allocation. The previous code (now removed in this PR) did CIDR identity allocation upon policy add and deallocation during the delete. For the most part, that was for a discrete set of IP addresses vs. the addresses that InjectLabels() handles, since up until now InjectLabels() only handled this for the kube-apiserver IP address.
The new model for the IPCache now attempts to decouple some of this "desired" vs "realized" state logic such that the identity allocation and corresponding ipcache updates are handled asynchronously by a dedicated goroutine that is also responsible for triggering updates to other subsystems (including eventual bpf policymap updates). As such, this code which is handling an event can no longer make assumptions about when the identities are ready, but it just lines up the policy repository and the ipcache updates + triggers endpoint policy updates such that eventually the correct policy will be applied.

If there is some sort guarantee here that I'm missing, it would be good to explicitly call out.

Yeah I'm with you there. I've tried to call out as many of these in the new comments in reactToRuleUpdates() which discuss the asynchronous nature of the new ipcache model, but admittedly this logic is not the simplest to dive into, and I have a fair bit of background to the history of this code. Hopefully some of my responses above can help to shed some light into this area, and if you think that there are specific points I could better document somewhere then I'm open to that.

Thanks for the reviews, I'll apply the diffs & rebase.

:crying_cat_face: https://www.githubstatus.com

(Just a side-note from reading the comments here, I've been thinking this for the past few months, but I'm no longer liking the name InjectLabels() because it's not just labels anymore :slightly_smiling_face:. Eventually, we should proabbyl rename to InjectMetadata or AssocaiateMetadata(). The initial implementation (kube-apiserver policy selection logic) actually used the "injection" semantic to "inject" the appropriate labels for certain IPs (reserved:kube-apiserver), but we are well past that point now.)


Added task_id in the content type

This helps us to co-relate which taskid this payload belongs to.
We have been working with ingress team to provide us a way to upload
metadata along with the file, that feature is still in discussion so
in the meantime the work around they suggested is to  store the task_id in a portion of the content
type
The content type is currently
"application/vnd.redhat.topological-inventory.filename+tgz"
The filename portion is the category
We are changing this to
"application/vnd.redhat.topological-inventory.b761ca40-e53e-4a5f-97cf-7453bdbdca93+tgz"
In the JSON message from the Ingress Service this shows up as Category
b'{"account":"6089719","category":"b761ca40-e53e-4a5f-97cf-7453bdbdca93","metadata":{"reporter":"","stale_timestamp":"0001-01-01T00:00:00Z"},

@bzwei Changes applied