What does happen if Record versioning is not available?

Hello,
what does happen if Record versioning is not available (e. g. no E5 license assigned) but records will be edited and thus a new version gets created? Will be the previous version lost? Is editing just not possible without Record versioning?
Thank you for clarifying!
Best Regards,

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

ID: 6ae5f811-9551-ea95-b113-9175a6f08d7e
Version Independent ID: e1eb8d3d-d439-e814-4a05-aa5bbc11f33e
Content: Learn about records - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/records.md
Service: o365-seccomp
GitHub Login: @cabailey
Microsoft Alias: cabailey

@GiantCrocodile Thank you for drawing my attention to the fact that this article had a licensing statement in it - will be removed in line with the other documentation pages for retention and records management.  Instead, use the link at the top of the page for a single and authoritative source of information for the latest updates.
If you follow this licensing link at the top of the page, you will read how licensing isn't always enforced, but that doesn't mean it's not required.  And when you refer to the licensing spreadsheet (PDF or Excel), you'll see that records management and records versioning requires an E5 license or equivalent.  To edit content that's been declared a record, it must first be unlocked, which then uses record versioning.  If in doubt about what licenses you need, please check with your Microsoft Account Manager or equivalent support channels. We can't comment on what will happen if you use a feature that you're not licensed to use because this isn't a supported scenario.

Hi @cabailey! Thank you for fixing the license info.
I'm aware that bypassing a license requirement isn't legal nor supported. That's now what I'm asking. I'm asking what will happen in case of an user doing this by being unaware of the license requirements: Does he/she get a proper error message or will this end in a license violation which an admin can't prevent?

@GiantCrocodile  We can't answer questions on what will happen if a feature is used without correct licensing.  As with all unsupported scenarios, you're welcome to test but the results might change later down the line.  There have been requests for improvements in the product around licensing enforcement and information, and this is something that engineering is looking into so I encourage you to add your feedback to UserVoice, this category: https://office365.uservoice.com/forums/289138-office-365-security-compliance?category_id=379531

@cabailey I see. Thank you for your help and feel free to handle this issue as resolved.


Better error message for using outdated moduleResolution: node(10)

Suggestion
🔍 Search Terms
moduleResolution node node10 eol esm commonjs cannot find types
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
When a TSConfig is using "moduleResolution": "node" or "node10" and an import resolves to an npm package whose types declarations that doesn't support Node < 16, the error message in tsc is very general:
Cannot find module '...' or its corresponding type declarations.

Same in VS Code:

Could we please have a secondary message added suggesting that the project be switched to using a more modern "moduleResolution"?
This message needs bikeshedding, but a starting proposal:
Cannot find module '...' or its corresponding type declarations.
    Consider upgrading your "moduleResolution" compiler option. See aka.ms/tsconfig#moduleResolution for details.

📃 Motivating Example
This has been a point of confusion in at least https://github.com/typescript-eslint/typescript-eslint/issues/7284. We've gotten a few duplicate reports.
💻 Use Cases
Same as ☝, I think. I can't think of anything more specific.

People are going to come here and complain if we issue that message and it turns out that the module really isn't there under any setting, and I don't really see a way we could determinatively detect which (if any) other resolution settings would work.

Hmm. Maybe it can just link to aka.ms/tsconfig#moduleResolution then?

detect which (if any) other resolution settings would work

Also, I'm realizing now I meant to suggest in the OP that this message should only be there if any other resolution setting would work. 😬

Under different module resolution settings, we could even have entirely different source files under analysis, rendering the original import moot. It's not tractable in the general case IMO

Could we just have node10 do the same thing node16 does and specially handle the error where they would have diverged?

Or something more naive where we keep track of whether exports was specified anywhere where we checked.

@DanielRosenwasser is it possible to use ambiguous language in the presence of “exports”? For example, “This package may be resolvable using (…) because we found type module and exports declared in the package”?
I’ve only converted a few packages I maintain to be ESM so far, but every time I do I get a ton of issues like https://github.com/blakeembrey/change-case/issues/304. The current message isn’t adequate to show the issue is in user configuration and not the package.

We use "may" a lot of the time, so I'm okay with that.

Coming back to this - this is a pretty persistent pain-point for users of @typescript-eslint.
We've found that a lot of users don't know that:

moduleResolution: node actually means node10
node16 exists
node10 is different to node16
they're using a module resolution that doesn't match their runtime (our minimum supported node version is 16).

We've had to keep this pinned issue up and open to give people docs on how to fix the unclear error message, or else they file an issue with us saying our package is broken.
I'm sure there are a lot of packages out there who continue to include a types field in their package.json solely to stave-off the support burden of users who are still (usually erroneously) using node10 resolution.
We could do this also - but it does seem "smelly" that we would consider changing our config to avoid support burden from an unclear TS error message.
I 110% get that we can't make the error message say something so absolute like "you're using node10 but this package doesn't have a types field declared, but it has an exports field, you must use node16 instead" because, well, it's a different module resolution and that advice may not even be correct!
But as @blakeembrey suggested maybe there's a way we can help nudge the user in the right direction for this specific case? Or at least suggest something that might help them try something else and self-service fix their problem, rather than having to reach for stackoverflow / github issues / discord messages in order to even learn about the 2 character config change that could fix their problem.
For example, would this rough logic be acceptable?
"if TS finds a package that has no types field but has an exports field with a nested types field, then append This package may be resolvable using (…) because we found typed exports declared in the package. to the error message"

@andrewbranch does the above sound like something we can do?

Yes 👍


Property lookup is gone

There's an example of usage for postcss-property-lookup plugin but looking at the npm package.json I can't see it and of course the example is not working either. Is this replaced by something else or just an error in the README?

The same, property lookup doesn't work for me


Update RealWorld Application

@JanFuhrmann

Current problem is, that somehow java is not always completely installed. Does the container somehow exit the script early?

Maybe the java 11 installation needs the upate-alternatives stuff as in java 8 ?
https://github.com/OpenTOSCA/tosca-definitions-common/blob/main/artifacttemplates/http%253A%252F%252Fopentosca.org%252Fartifacttemplates/Java_11-Install-w1/files/install.sh
https://github.com/OpenTOSCA/tosca-definitions-common/blob/main/artifacttemplates/http%253A%252F%252Fopentosca.org%252Fartifacttemplates/Java_8-Install-w1/files/install.sh

@nyuuyn, do you want to try it?


Error when trying to export task dataset

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
We are trying to export a task dataset in the "CVAT for video 1.1" format. However, after 4 hours it times out and an error message is printed, see below:
File "/opt/venv/lib/python3.10/site-packages/rq/timeouts.py", line 63, in handle_death_penalty     raise self._exception('Task exceeded maximum timeout value ' rq.timeouts.JobTimeoutException: Task exceeded maximum timeout value (14400 seconds)
This is a screenshot of the error message in the UI:

We have also tried to export the annotations in the "CVAT for images 1.1 format" (for debug purposes) but this isn't working either.
The task consists of 790 frames with a segment size of 25 and an overlap size of 5, resulting in 32 jobs with 30 frames per job.
The task is annotated with tracks and each job has between 50 and 110 unique tracks resulting in between 1400 and 3000 boxes/polygons (mostly boxes) in total per job. The whole task has around 55 000 boxes/polygons. All these annotations have been imported.
We are able to export the annotations from one job at a time, but since we need the tracks to be consistent between the jobs this isn't a feasible option.
For debug purposes we have tried to remove all annotations from 60-70% of the jobs and then export the task in the "CVAT for video 1.1" format which works.
Is there a known limit regarding the number of tracks or objects that you are able to export? Do you have any suggestions on how we can solve this issue? Is it worth trying to extend the timeout limit beyond 4 hours?
Expected Behavior
We should be able to successfully export the task in the "CVAT for video 1.1" format.
Possible Solution
No response
Context
No response
Environment
Server version: 2.6.1
Core version: 11.0.3
Canvas version: 2.17.4
UI version: 1.55.4

Thanks for your response @bsekachev! We will try to increase the timeout as a first attempt, if that doesn't work we'll try to upgrade to the latest release. I will get back to you with an update of our progress.


Allow state file directory to be configured

The state file directory should be configurable via both a command line option and the configuration file.
On Linux systems, by default, /var/lib/timber-agent/ should be used, pursuant to the manual page hier(7).
On BSD systemsn, by default, /var/db/timber-agent/ should be used, pursuant to the relevant manual pages for the major distributions: FreeBSD - hier(7), NetBSD - hier(7), OpenBSD - hier(7).
It is important to note to users that state files are designed to be a durable across reboots. If a user intends to customize the state file directory, it should not be set to a directory that will be wiped on reboot or a directory on a temporary or memory-only filesystem.

Looping back to this based on the proposal in #137, I should mention here that any change will have to take previous statefile locations into account, even if the new statefiles are written somewhere else. Say that the target is /var/log/nginx/access.log, that means that even if the statefile is written to /var/lib/timber-agent/state.json, the agent still needs to check /var/log/nginx/access-state.json.
Additionally, I think that this change either needs to store the state in a single file or the file names need to be a hash of the path.
In a single file scenario, it would look like this:
{
  "version": "0.6.1",
  "fileStates": {
    "/var/log/nginx/access.log": {
      "checksum": "FEED…",
      "offset": 8513
    }
  }
}

alternatively,
{
  "version": "0.6.1",
  "fileStates": [
    {
      "path": "/var/log/nginx/access.log",
      "checksum": "FEED…",
      "offset": 8513
    }
  ]
}

In the multi-file scenario, the filename would be something like state-L3Zhci9sb2cvbmdpbngvYWNjZXNzLmxvZw.json; L3Zhci9sb2cvbmdpbngvYWNjZXNzLmxvZw is the unpadded Base64 encoding of /var/log/nginx/access.log. The existing file format would stay the same (though I do recommend adding a version key for posterity's sake).


Feature request: Flatmap

As per contribution guidelines, I'm opening an issue for discussion regarding the implementation of Flatmap.
Per Documentation:

The FlatMap operator transforms an Observable by applying a function that you specify to each item emitted by the source Observable, where that function returns an Observable that itself emits items. FlatMap then merges the emissions of these resulting Observables, emitting these merged results as its own sequence.

A naive implementation could look like
func (o Observable) FlatMap(apply fx.FlatMappableFunc) Observable {
	out := make(chan interface{})
	go func() {
		for item := range o {
                        go func(sub Observable) {
                                handler := observer.Observer{
                                        NextHandler: func(i interface{}) {
                                                out <- i
                                        },
                                        ErrHandler: func(err error) {
                                                out <- err
                                        },
                                }
                                s := sub.Subscribe(handler)
                                <-s
                        }(apply(item))
		}
		close(out)
	}()
	return Observable(out)
}

I see that the dev branch has a Merge function, however I'm not sure how to exploit the underlying reflect.SelecCase with a dynamic number of Observables. Creating a subscriber (and a go routine) for each element seems sub-optimal, but out of the top of my head I'm not aware of a different solution.
I'd be happy to submit a PR once agreement of the implementation is reached.

PS: While I'm at it, it would also be very nice to have concatMap as well. Dependent on the implementation of flatMap, concatMap could be pretty easy.

Also, as a more general question: I can't help but notice that the majority of ReactiveX functions are still missing. What is the plan to get them all in? I'd love to contribute a few, but I don't know if I should create a PR for each one. I don't want to flood this project with issues and PRs.
Also what is the purpose of the dev branch? What is the lifecycle of that branch, i.e. when is it getting merged into master?

I've a plan to make a pull request. Which branch should I use as the starting point - dev or master?

@venth are you implementing FlatMap?

Yes. I have a plan to make in on goroutines. I wondered, if I shall introduce TestSubscriber/Observer before

@jochasinga, I have doubts related to current operators implementation. Currently operators like:

First,
Last and
others

perform iteration through channel. I've compared it to other reactivex implementations. Others implementations like: Scala based, Java based are relaying on Observer pattern and functional programming. In current implementation instead of applying observer pattern I see iteration through values in a channel.
Did I understand it correctly or I didn't get something?

Links to relevant articles:

http://reactivex.io/documentation/observable.html
https://dzone.com/articles/understanding-reactor-pattern-thread-based-and-eve

@jochasinga, it took me a while and tries to grasp the idea of flatmap implementation. I prepared the version based observer and subscription without usage of channels (https://github.com/venth/gorx/blob/master/operator/flatmap_observable.go) and have an idea how to deliver flatmap implementation consistent to channel based approach.


Draw horizontal and vertical lines

I was just wondering if it would be possible to draw vertical and horizontal lines on images?

For what purpose? As a tool? You can take a look at how we render reference lines here: https://github.com/chafey/cornerstoneTools/blob/547f29123bfc59e54a7a7c4734a09e7aee9fe2cb/src/referenceLines/renderActiveReferenceLine.js#L52

Yes as a tool.
I can use the lines measurement tool but I need to estimate to see if the line is vertical or not.

@gokhandilek do you still have a need for this? @swederik is this a common radiologist tool? Or can we close this issue?

This is from almost a year ago, and not a common tool I've heard of or seen before. Moving to closed for now. If someone speaks up, we can open this and mark it up for grabs.

How to use it for the new version ?https://github.com/chafey/cornerstoneTools/blob/547f29123bfc59e54a7a7c4734a09e7aee9fe2cb/src/referenceLines/renderActiveReferenceLine.js#L52


[Feature Request] Low code init/modify a configuration in specific schema

Low Code Init/modify the KCL configuration
Feature
provide a common way for users to init and modify a KCL configuration without writing the KCL code(or only write a little code)

init:

[IDE] display a list of schema/template
[user] select the schema/template to use
[IDE] display the attributes to config hierarchically
[user] fill in all the values: input field for most of the literal value; a drop-down box for Enum value; with default value auto-filled; with a gray question mark hover on the optional attribute and a red exclamation mark hover on the required attribute, etc.
[user] save the configuration and specify the file path to save the code.
[IDE] output the auto-generated KCL code to the file

modify:

[IDE] display the variables in the configuration file and all the attributes to config hierarchically. with all the attributes filled in with the current value.
[user] modify the values in the low code manner described in the [init] section.
[user] finish modification and save the configuration.
[IDE] output the auto-generated KCL code to current file

view

[IDE] display the variables in the configuration file and all the attributes to config hierarchically.
[IDE] for attributes with a docstring, display the docstring in a description manner.

Design

Related Issue: https://github.com/kcl-lang/kcl/issues/613


Allow lifetime polymorphism in local bindings

The following example doesn't compile in current Rust:
fn main() {
    let id = |x: &i32| x;
    {
        let a: Box<i32> = Box::new(42);
        id(&a);
    }
    {
        let b: Box<i32> = Box::new(43);
        id(&b);
    }
}

This is because a and b have non-overlapping lifetimes, so id cannot be fixed to either of them.
The typical solution is to lift id into a fn, making the lifetime parameter polymorphic:
fn id<'a>(x: &'a i32) -> &'a i32 { x }
// ...

But then we lose the ability to close over the environment.
Ideally, I'd like the compiler to accept something like this:
let id = for<'a> |x: &'a i32| -> &'a i32 { x };

that is, a closure which is polymorphic over the lifetime rather than fixed to a particular one.

The following works on master:
fn main() {
    fn id_type<T: Fn(&i32) -> &i32>(t: T) -> T { t }
    let id = id_type(|x: &i32| x);
    {
        let a: Box<i32> = Box::new(42);
        id(&a);
    }
    {
        let b: Box<i32> = Box::new(43);
        id(&b);
    }
}

I see two issues: one, rustc is terrible at inferring lifetimes for closures (https://github.com/rust-lang/rust/issues/28092 https://github.com/rust-lang/rust/issues/26937 etc.).  Two, it would be nice to have more direct syntax for explicitly specifying the lifetimes you want.


Fix another crash

Found while typechecking rustc with better name resolution...
walk_mut doing a preorder walk can lead to an infinite recursion when substituting type parameters; postorder is actually what we want.

bors r+


BIP-X: Morning Auction

Problem
From season to season, the temperature changes a maximum of +/-3% based on the state of Beanstalk. In instances where short-term demand exceeds short-term supply, Beanstalk may be paying significantly more than what is needed to attract creditors. While Beanstalk would rather have too high of a temperature rather than too low and risk not attracting creditors at all, the temperature can better optimize during times of excess demand.
Proposed Solution
Introduce a dutch auction during the first X blocks after the sunrise() call, where the Temperature ramps from 1% to 100% of the max Temperature. This time period will be referred as the morning within a season, and the mechanism named "the Morning Auction". (WIP)
Additionally, the soil issued above peg will change as a function of the Morning Auction, such that the maximum potential pods issued within a season (peas, WIP), will be reached if all soil is sown.
Specification

Redefine all instances of $h_t$ as the maximum Temperature $h_t^{\text{max}}$.

Redefine $h$ to:

$$ h =
\begin{cases}
{1} & if \quad c = 0 \
{max(h_t^{\text{max}}*log_{ab+1}(ac+1),1)} & if \quad 0 < c  < 25 \
{h_t^{\text{max}}} & else
\end{cases} $$
where $a$ is the control variable, $b$ is the number of blocks needed to elapse to reach max Temperature, and $c$ is the number of blocks that has elapsed since the sunrise() call.
$$
\begin{aligned}
a =& \ 2 \
b =& \ 25 \ (i.e \ \text{25 blocks until Temperature reaches its max)} \
c =& \ \text{currentBlock} \ - \text{sunriseBlock}
\end{aligned}
$$

Adjust the time in which Beanstalk considers demand for Soil increasing in instances where all but at most one Soil is Sown from 5 minutes to 10 minutes (i.e., $\Delta{E_{t-1}^{u^{first}}} \leq 600$).

Storage
Add to the Season struct: uint32 sunriseBlock.
Add to the Season struct: bool AbovePeg.
Add to the Field struct: uint128 beanSown.
Modify soil in the Season struct from datatype uint256 to uint128 in favor of beanSown.
Depreciate startSoil from the Weather struct
Existing Functions in scope
SeasonFacet

stepSeason()

LibDibbler

sow(uint256 amount, address account)
BeansToPods(uint256 beans, uint256 weather)

FieldFacet

sow(uint256 amount, LibTransfer.From mode)
sowNoSoil(uint256 amount, address account)
sowWithMin(uint256 amount, uint256 minAmount, LibTransfer.From mode)
totalSoil()

weather

stepWeather(int256 deltaB):

New Functions/Getters:
LibDibbler

MorningAuction(uint256 maxWeather, uint256 _block) - outputs the new scaled weather as a function of the maximum weather and the blocks elapsed since sunrise.
AuctionMath(uint256 a) - Math Helper for Morning Auction.
beansToPodsAbovePeg(uint256 beans, uint256 maxPeas) - issue pods when bean is above peg.

FieldFacet

yield() -  outputs the instantaneous temperature in the season (max temp has a getter via yield()
peas() - outputs Peas, or the amount of pods beanstalk is willing to issue.

SeasonFacet

abovePeg() - getter for bool abovePeg
sunriseBlock() - getter for uint32 sunriseBlock

Technical Implementation:
With this change, the temperature is dynamic within the season.
When Bean is above peg, the soil issued within a season is dynamic, and the maximum pods (peas) issued within a season is fixed.
When Bean is below peg, the soil issued within a season is fixed, and the peas is dynamic.

Over the 25 blocks within a season, the temperature starts at 1% (absolute), and ramps up to 100% of the temperature. The formula can be seen here:  https://www.desmos.com/calculator/soynntzc7h
s.f.soil and totalSoil() now behaves differently based on the peg.

When above peg, beanstalk issues the effective soil needed if all  soil was sown immediately after sunrise (the pods harvested from previous season). when soil is sown, the amount sown is scaled up to reflect the effective soil consumed.
Execution
Estimated development time: 2-3 weeks (lol).

Push proof-of-concept PR.
Beanstalk Farms code review.
External audit.
BIP.

closed in favor of BIP-30 PR: https://github.com/BeanstalkFarms/Beanstalk/pull/127


typed_endpoint: Rename WebhookPayload to JsonBodyPayload.

This kind of payload that's loaded from json in the body of the request is not only used for webhooks, but also in the push bouncer, and may get used elsewhere too - so a general name is better.
Extracted from #26697.

I have seen this CI failure before, but am not sure what leads to that.

Yeah this is a known nondeterminstic failure I've been unable to reproduce locally; to fix it, we likely need to add a bunch of debugging print statements to that test to figure out what's happening. There's an "#automated testing" thread about it.


Initialize a bluetooth connection between the device and the android app

Part of #7

Is the code available somewhere?


Remove code that relies on v4 cookie redirects

Description (required)
Astro 5 removed introduced a breaking change where failed actions no longer redirect back to the page where a form was submitted.
This PR modifies an "actions" example that relied on the v4 behavior, making it work with Astro v5.
Related issues & labels (optional)

Closes N/A
Suggested label: code snippet update

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note

en/guides/actions.mdx
Source changed, localizations will be marked as outdated.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳.

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.


feat(appsync-modelgen-plugin): expose readonly labels to model ts output

Description of changes

This allows us to omit the readonly fields (only if the config.isTimestampFieldsAdded flag is enabled in the cli.json within a user's project) from being suggested by Intellisense. The associated tests were updated automatically via running jest --updateSnapshot.
Additionally, I've extended the typescript-declaration-block.ts file with a new method to dynamically generate type blocks which get output in the index.d.ts file in user projects. I'm updating the types.ts in JS Datastore to reflect this new second parameter passed in to the constructor/copyOf (as seen in the generated snapshots in the test file).
Issue #, if available

None
Description of how you validated changes
yarn test
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #185 (906fc8c) into master (f9c1b1a) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #185      +/-   ##
==========================================
+ Coverage   85.18%   85.20%   +0.01%
==========================================
  Files         139      139
  Lines        6188     6196       +8
  Branches     1343     1348       +5
==========================================
+ Hits         5271     5279       +8
  Misses        839      839
  Partials       78       78

Impacted Files
Coverage Δ

...-plugin/src/visitors/appsync-typescript-visitor.ts
73.03% <100.00%> (+2.66%)
:arrow_up:

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 f9c1b1a...906fc8c. Read the comment docs.

Hi @AaronZyLee and @frimfram, I've made a few adjustments to this PR based on Typescript requirements in the Datastore JS library. I've added a new method to extend the class that generates classes to now generate types. Could you please give it another look when you have a chance and let me know if you have any questions or concerns? Thanks!

Overall, I have concerns about the backward compatibility.
Suggestion is that instead of changing the behavior of the existing function, maybe create a new function that calls the old one with additional new behaviors.
For example, instead of changing "generate" function, leave the old generate function as is and create a new one "generateWithTypes" that calls the original generate and then create more objects to be returned along with the results from the original.

Hi @frimfram this is a good call. I'm just wondering if we take this approach, would we need to wrap the visitor.generate(); in plugin.ts (and other .generate() calls like the test files) with a conditional check for the feature flag to call the appropriate method?
i.e.
if (this.config.isTimestampFieldsAdded) {
  visitor.generateWithTypes();
} else {
  visitor.generate();
}

Thanks for clarifying.

Overall, I have concerns about the backward compatibility.
Suggestion is that instead of changing the behavior of the existing function, maybe create a new function that calls the old one with additional new behaviors.
For example, instead of changing "generate" function, leave the old generate function as is and create a new one "generateWithTypes" that calls the original generate and then create more objects to be returned along with the results from the original.

Hi @frimfram this is a good call. I'm just wondering if we take this approach, would we need to wrap the visitor.generate(); in plugin.ts (and other .generate() calls like the test files) with a conditional check for the feature flag to call the appropriate method?
i.e.
if (this.config.isTimestampFieldsAdded) {
  visitor.generateWithTypes();
} else {
  visitor.generate();
}

Thanks for clarifying.

@nickarocho I would suggest to limit the scope to the appsync-javascript/typescript-visitor.ts rather than plugin.ts since the latter one is used by more than javascript generators. An example is like put generateWithTypes within generate


Eclipse resource filters

Hi @oehme ! This is a draft pull request for the first phase of the eclipse resource filters, adding the EclipseProject DSL support for filters with a basic custom matcher.  I am still cleaning up the documentation, but I wanted to open this so you could start to take a look.
Any of the checked boxes below indicate that I took action:

[x] Reviewed the Contribution Guidelines.
[x] Signed the Gradle CLA.
[x] Ensured that basic checks pass: ./gradlew quickCheck

For all non-trivial changes that modify the behavior or public API:

[x] Before submitting a pull request, I started a discussion on the Gradle eclipse Buildship plugin bug tracker
[x] Design document: https://github.com/gradle/gradle/tree/master/design-docs/features/ide-integration/richer-eclipse-model/resource-filters
[x] The pull request contains an appropriate level of unit and integration
test coverage to verify the behavior. Before submitting the pull request
I ran a build on your local machine via the command
./gradlew quickCheck <impacted-subproject>:check.
[x] The pull request updates the Gradle documentation like user guide,
DSL reference and Javadocs where applicable.

Some notes:

Deviation from spec: I used random UUIDs for the resource filters instead of epoch time, as the filters were all created at about the same time and it looked like collisions were likely.
I tried a few methods of testing the generated filter XML.  In the end, as the XML can get pretty complex, it seemed like the easiest way was to just assert a block of XML directly in the EclipseProjectIntegrationTest.  Because the filter ids are autogenerated, they are stripped out before asserting if they were not passed in the expected XML.
Still need to implement reading filters from an existing .project file

Hi @oehme , I have addressed your comments with a new commit.  We can squash later before merging.  I will work on the reading of the existing .project filteredResources next and add as a new commit here.

Hi @oehme , I have now added the support for reading filteredResources from an existing .project file and documentation for the new features.  Would you please take another look?

Let me know if you want to do anything about the target/appliesTo (files/folders) naming.  I made them all consistent (“appliesTo”) for now, but we can change it if you wish.
I wasn’t sure how the gradle team manages @since tags.  For now I used the placeholder NEXT_VERSION.  Please let me know if I need to update these.
I added extra commits to make the changes easier to review, but we can squash and rebase before merging.

Ok, I have added test "existing project file with equivalent resource filters is unchanged" to test that an existing .project file with two resource filters is unchanged after the "eclipse" task is run on a gradle project that defines two equivalent filters.
One thing to note is that the ids of the filters will possibly change if Eclipse had generated the filters, as it will use a timestamp instead of sequential integers.  As we do not store the id in our model, we can't recreate it, so the id will just change to a sequential number.  But subsequent runs of the "eclipse" task will keep the same filter ordering and numbering.  Do you think this will be an issue?

Hi @oehme , I have completed the latest round of code review changes, would you please have another look?  Thanks!

One thing to note is that the ids of the filters will possibly change if Eclipse had generated the filters, as it will use a timestamp instead of sequential integers.

I think we can live with that, yes. Can you check that Eclipse doesn't change the id back when you import the project? Otherwise it could become an annoying back-and-forth.
Apart from that, this looks really great to me and I can merge it as soon as the question above is clarified.

Hi @oehme , I tested importing the generated .project file into Eclipse, and Eclipse does not change the identifiers.  It will only change the ids if the filters are modified in the UI, and in that case it rewrites all of them (sometimes the ids are actually not unique, they are the same exact timestamp...).  So I think this behavior is fine.
I have squashed the code review commits and rebased onto the latest master, you can merge when you are ready.

Thanks for the great work @kpage! I'll be out for a week, but will merge this when I'm back. It will be part of Gradle 3.4, so if you have some time to adjust the "NEXT_VERSION" tags that would help.

Hi @oehme , I changed the NEXT_VERSIONs to 3.4 and rebased onto latest master.

Hi @kpage. This change looks good but we do have an outstanding test failure on Windows EclipseProjectIntegrationTest.existing project file with equivalent resource filters is unchanged. Would you please look into fixing it?

Warning:  org.apache.xerces.parsers.SAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized.

Thanks @eriwen  and @oehme , I have fixed the test and rebased onto the latest master.
Does gradle org have a public CI for pull requests?  I ran the tests locally before on Linux but did not have a Windows machine available.

@kpage Yeah, I kicked off CI for your PR here: https://builds.gradle.org/viewQueued.html?itemId=2197344&tab=queuedBuildOverviewTab
I'm afraid this didn't make it into 3.4. Could you please update the @since annotations to 3.5 in the meantime?

Hi @eriwen , I have updated the new @since annotations to 3.5

@kpage The CI build passed and with @oehme's +1 I'm going to merge this. Thanks very much for your contributions!

@kpage Would you like to follow up with the Tooling API part next so we have a complete story for 3.5?

Hi @big-guy , as this branch has already merged, I have opened a new pull request to address changes from your comments: #1328
@oehme sure, after the new code review comments are finalized, I can look at the Tooling API.


model_with_buckets in seq2seq.py

Hi all,
The online version of https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/seq2seq.py#L873
def model_with_buckets(encoder_inputs, decoder_inputs, targets, weights,
                       buckets, seq2seq, softmax_loss_function=None,
                       per_example_loss=False, name=None):

is different with the one installed from tensorflow-0.6.0-cp27-none-linux_x86_64.whl
def model_with_buckets(encoder_inputs, decoder_inputs, targets, weights,
                       buckets, num_decoder_symbols, seq2seq,
                       softmax_loss_function=None, name=None):

(extra num_decoder_symbols parameter) which caused
TypeError: model_with_buckets() takes at least 7 arguments (7 given)

when running https://github.com/tensorflow/tensorflow/blob/master/tensorflow/models/rnn/translate/seq2seq_model.py#L133.
Which one should I use?
Thanks,

If you have installed 0.6.0 from pip, always check out the code repository at the same branch/tag -- they should be compatible.
If you want the latest changes from master, you'll have to build the pip package from sources.


Consolidate git AHEAD and BEHIND into DIVERGED

If a branch is both ahead and behind, we only need to show the diverged status

Standards checklist:

[ ] The PR title is descriptive.
[ ] The PR doesn't replicate another PR which is already open.
[ ] I have read the contribution guide and followed all the instructions.
[ ] The code follows the code style guide detailed in the wiki.
[ ] The code is mine or it's from somewhere with an MIT-compatible license.
[ ] The code is efficient, to the best of my ability, and does not waste computer resources.
[ ] The code is stable and I have tested it myself, to the best of my abilities.
[ ] If the code introduces new aliases, I provide a valid use case for all plugin users down below.

Changes:

[...]

Other comments:
...

This has been fixed a different way in the upstream repo


backgroundColor function is passed malformed ScriptableContext context argument on load

Expected behavior
I am using a function on the backgroundColor property to generate different gradients for each bar of my graph using the ScriptableContext context argument to get information about the height of the bar being currently rendered.
The backgroundColor function should receieve a context argument that contains element.height and element.base on load.

Current behavior
A malformed context argument is passed on load that doesn't contain a element.height property. This causes my backgroudnColor function to be unable to return a gradient, and so the graph renders black.

Reproducible sample
https://codepen.io/willgardnerpenny/pen/Poadpdr
Optional extra steps/info to reproduce
If you hover over the bars in the codepen, they will render the gradient background as expected.
Possible solution
It might be that I'm using undocumented and unsupported behaviour of the backgroundColor context argument to render my graphs, in which case this is no longer an issue, and I'll make a PR updating either the type/docs for the ScriptableContext to reflect the current shape of this argument.
Context
No response
chart.js version
v4.0.1
Browser name and version
Chrome: Version 107.0.5304.121
Firefox: 107.0b9
Safari: Version 15.6.1 (176<IP_ADDRESS>.16)
Link to your project
No response

Closing this issue with the solution. element.base is not officially supported/documented; if you want the base value, you can call: context.chart.scales[scale].getBasePixel()

Using public api:
function getGradientFixed(context) {
  const chart = context.chart;
  const scale = chart.scales.y;
  if (!scale.width) {
    // something is accessing this property before scales are fully updated
    return 'black'
  }
  const barPixel = scale.getPixelForValue(context.parsed.y);
  const barPercent = scale.getDecimalForPixel(barPixel);
  const gradient = chart.ctx.createLinearGradient(0, scale.top, 0, scale.bottom);
  const color = "133, 80, 216"; //purple
  gradient.addColorStop(1 - barPercent, `rgba(${color}, 1)`);
  gradient.addColorStop(1, `rgba(${color}, 0)`);
  return gradient;
}


Removed preinstall script introduced in #365

Description
Closes #376.

I have a doctor's appt this morning but I will make every effort to cut a patch release today. (cc @josephdsumner do you have permissions to do this?)

@MelSumner I'm not in a hurry, so please feel free to next week. 🙂


[stable/rabbitmq-ha]: Service should get a ClusterIP by default.

What this PR does / why we need it:
The Service resource is headless by default, unless the user provides their own IP address or a value of "". The default behaviour should be to assign a cluster-internal IP from the service-cluster-ip-range.
I'm not sure this value is even required in the service.yaml template, but rather than remove it, I made it conditional.
Alteratively, I could just change the default value from None to "", but I think this way is more explicit.
Note: The discovery service created by service-discovery.yaml is headless by design.
Notice for reviewers:
Bumped chart version but current version may change depending on order of merges for outstanding PRs.

/cc @etiennetremel

This was changed from "" to None in PR #6443. I agree with you that default should be "" as that PR broke my upgrade. But not sure we should be changing back now since clusterIP field is immutable and will break upgrades again. To workaround, just set service.clusterIP: "" in your custom values.yaml.


When can we expect 0.6 release?

I could really use TLS support, but I'd rather pin to a version, not commit.

@c2h5oh
I think we can pin after #325

I'll add a dockerfile tomorrow - let's include it too.

Preparatory work for Dockerfile is in this pull request https://github.com/siddontang/ledisdb/pull/326
Final pull request will follow in the next hour or so.

Final pull request - Dockefile to allow building new version - https://github.com/siddontang/ledisdb/pull/327

With all 3 merged let's tag it 0.6


Ensure we have the correct path in monit

if/when the appcontroller crash or is killed, the path in monit doesn't
consider /usr/local/bin, creating the possibility of some of the scripts
to be unreachable.

OCD run https://ocd.appscale.com:8080/job/Daily Build/2332/


Major design changes

I'd like to implement a few changes to make this little project a more mature tool and easier to use. Things that could be improved IMO:

[ ] Use Maven for dependency management
[ ] Make it usable as library
[ ] Proper logging system
[ ] Proper CLI argument parsing using library
[ ] Make use of Java name conventions
[ ] Change license to a more accepted public domain license (like Unlicense or CC0)
[ ] Make use of the GitHub release system for distributing the software

What do you think?

I've never used Maven.  As long as it still builds in a normal install of Eclipse, I don't care.
I'm keeping the WTFPL.  Corrodias posted MLG 1.2.0 and earlier online with no license, so I contacted him, and we agreed to use the WTFPL.  He retroactively licensed MLG 1.0.0, 1.1.0 and 1.2.0 under it, and I licensed the newer code with it.
I used to use the Github release system many many years ago, but didn't like it at the time.  Its probably better now, IDK.
As for the rest, that sounds awesome!  Make a fork, do what you want, submit a pull request, and we will go from there...


Create LINQPad 8.0.16 manifest

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

2023-11-27 15:33:27.135 [CLI ] Package hash verification failed. SHA256 in manifest
[8e4b1577b2afb9c794048fc0de5f353ff268c756dd06b61e5249835818aa36d2] does not match download
[4dd8f19d9f4e5b0b0c7fe7dac299606c8d87822dac3383ee1b3539834b388633]

/AzurePipelines run

Hi @tiksn,
This package has numerous dependencies:

Can you help me to enumerate all of them?

@stephengillie unfortunately I have all dependencies installed locally apparently, so I was not able to catch that.

Hi @roehl-ottri , thanks for your comment.
I fixed the second part of your comment. Overtime, while the PR is open, I must update it from time to time. Unfortunately, LinqPad is not providing versioned URLs to installers.
As for microsoft.netcore.app.ref and microsoft.windowsdesktop.app.ref, those are Shared Frameworks, that should be installed by Microsoft.DotNet.Runtime.8 and Microsoft.DotNet.DesktopRuntime.8.
Please correct me if I am wrong.

The .ref.app packages are not shared frameworks, that would be part of the Runtime. They are packages containing reference assemblies. According to the NuGet packages page they are:

Internal implementation package not meant for direct consumption.

microsoft.netcore.app.ref and microsoft.windowsdesktop.app.ref contain the .NET reference assemblies. These do not come with the standard .NET 8 desktop runtime - they come only when you install the full .NET SDK (as they are considered design-time assets).
LINQPad will prompt to download these (only) if you haven't installed the full .NET SDK. In the context of winget, it is probably easiest to consider these a LINQPad dependency and download them always.
LINQPad requires the .NET Reference assemblies for exactly the same reason that Visual Studio requires them. The only difference is that Visual Studio requires that you install the full .NET SDK for frameworks that you wish to target, whereas with LINQPad, your queries can target frameworks for which just the .NET Desktop Runtime + reference assemblies are present.
(LINQPad author)

Another solution would be to make the .NET 8 SDK a requirement (if that's possible).

Ah... that makes a lot of sense. Thanks,  @albahari !
I'm not familiar enough with winget manifests to know if it supports NuGet package dependencies, but the full SDK is available for sure.


[BEAM-12548] Implement EqualsFloat test helper

Adds the EqualsFloat function, which ensures that all elements of a PCollection are within a given threshold of all of the elements in another PCollection. Also adds unit tests.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @lostluck


POST /api/v1/media/configure/?video=1 - 403 Forbidden

Hi.
Im trying to publish a video and i got this VideoSourceDurationCheckException error.
Anyone can help me with this?
my code:
import { S3 } from 'aws-sdk';
import { IgApiClient } from 'instagram-private-api';
import fs from 'fs';

const s3 = new S3();
const ig = new IgApiClient();
const bucket = 'posts';
const { INSTA_USER, INSTA_PASS } = process.env;

ig.state.generateDevice(INSTA_USER);

export const main = async () => {
  try {
    await ig.account.login(INSTA_USER, INSTA_PASS);

    const { Contents } = await s3.listObjectsV2({ Bucket: bucket, MaxKeys: 2, Prefix: 'memes/geral' }).promise();

    const files = await Promise.all(Contents.map(async ({ Key }) => {
      const file = await s3.getObject({
        Bucket: bucket,
        Key,
      }).promise();

      return file.Body;
    }));

    const publishResult = await ig.publish.video({
      video: files[0],
      coverImage: await fs.readFileAsync("../../src/assets/cover.png")
    });

    console.dir({ publishResult }, { depth: null })
  } catch (error) {
    console.error(error);
    throw error;
  }
}

When I get a file from s3, it comes in the following format.
I'm taking the content of the body property and put it in the video property of the publish method.
Is it right?
I also tried to save the file with fs.writeFile and dps use readFileSync like in the example but it also gave the same error.
{
    AcceptRanges: 'bytes',
    LastModified: 2022-08-04T23:15:24.000Z,
    ContentLength: 3252472,
    ETag: '"c491cfe2fb5bc29777fc34391fc1d56a"',
    ContentType: 'application/octet-stream',
    Body: Buffer(3252472) [Uint8Array] [
        0,   0,   0,  32, 102, 116, 121, 112, 105, 115, 111, 109,
        0,   0,   2,   0, 105, 115, 111, 109, 105, 115, 111,  50,
       97, 118,  99,  49, 109, 112,  52,  49,   0,   0, 209,   0,
      109, 111, 111, 118,   0,   0,   0, 108, 109, 118, 104, 100,
        0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
        0,   0,   3, 232,   0,   0, 250,  17,   0,   1,   0,   0,
        1,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
        0,   1,   0,   0,   0,   0,   0,   0,   0,   0,   0,   0,
        0,   0,   0,   0,
      ... 3252372 more items
    ]
  }

error:
{
    "errorMessage": "POST /api/v1/media/upload_finish/?video=1 - 400 Bad Request; server processing error: VideoSourceDurationCheckException",
    "errorType": "IgUploadVideoError",
    "stackTrace": [
        "IgUploadVideoError: POST /api/v1/media/upload_finish/?video=1 - 400 Bad Request; server processing error: VideoSourceDurationCheckException",
        "    at C:\\Users\\User\\Desktop\\dev\\Insta\\.webpack\\service\\src\\functions\\webpack:\\instagram-private-api\\dist\\services\\publish.service.js:26:1",
        "    at tryCatcher (C:\\Users\\User\\Desktop\\dev\\Insta\\.webpack\\service\\src\\functions\\webpack:\\bluebird\\js\\release\\util.js:16:1)"
}

video: video.mp4

For those who have the same problem, this error happens because the video is longer than 60 seconds. Although instagram accepts videos of up to 3 minutes, it seems that the API only accepts videos of up to 60 seconds.
And there are still other specifications that we need to follow to be able to post a video, follow: video specifications
Does anyone know a way to convert any video to the format that instagram accepts?

Hello @rafaelgdn ,
I'm having a lot of checkpoint problems lately using this API. Maybe we can collaborate!
My gmail is<EMAIL_ADDRESS>Did you have this kind of problem and fix it? Can you email me so we can try to talk about our objectives?


[REQUEST] Better Nim Language name demangling and source mapping

There are two minor issues that still exist for the Nim language support:
1.) Name Demangling
Writing a custom name demangler should be pretty straight forward. I believe the D language demangler can be used as an example.
2.) Better asm to source mapping
For some reason I never figured out, Godbolt does not always correctly interpret the gdb linedir annotations that nim adds. It works, but often provides incorrect mappings.
I have a potential solution, but I do not know how to implement it.
Nim provides a --debuginfo flag that outputs a simple tab delimited file which provides the source name, mangled name, and source file location for all symbols.
The source to asm mapping is my big problem.
How do I provide custom source to asm mapping information to Godbolt?

hey it works when i tried it, add --lineDir:on --debugInfo to flags and i see asm


rollup: fix tpcds rollup query errors as field type mis-match

What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tiflash/issues/7830
Problem Summary:
What is changed and how it works?
mainly: two things;
1: when building up expand OP in planner mode, use the child.getSchema rather than child.getSampleBlock.
2: when building up expand before_actions, we should traverse all the level to detect nullability-changed grouping column ref rather than the first_proj_level
3: currently, we will add a projection under expand OP, while https://github.com/pingcap/tidb/issues/45576 occurs
desc:
// By now, tidb projection has only two situation:
//     1: agg/join + shuffler + projection
//     2: tidb_reader + shuffler + projection
// in the exchanger sender of the shuffler, we can always add the alias change via 'buildFinalProjection'.
// rootProjection services as substituting the user-level alias name.
// nonRootProjection services as adding prefix alias name for distinguishing between fragments.
//
// but Expand + Projection is an exception.
// let's say we have a projection with two col-ref: [col2, col1]. while the source columns are [col1, col2].
// the projection actions will be nil, since all the column can be found in current analyzer, while the column
// position is switched in the nonRootProjection of exchangeSender, accompanied by adding prefix alias name.
//
// while for case in {Expand + Projection} here, there is no shuffler between Expand OP and Projection here.
// which will causing the child schema columns that Expand can see is different from child's sample block it saw.
// so adding column positions switching and fetching logic here in expand-pre-actions.

Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
tpcds refined sql:
query: 5, 18, 27 and so on
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

rollup: fix tpcds rollup query errors

/check-issue-triage-complete

/run-all-tests

/run-all-tests

/hold
@AilinKid When you want to merge this pr, you can comment /unhold

/unhold


add quotes to field if numeric in safe_cast macro

resolves #891
Problem

The safe_cast macro currently uses the try_cast function in snowflake, which has the known limitation:

Only works for string expressions.

This means that this does not work: select try_cast(1 as NUMBER);

Even though all of these do:
select try_cast(10000000000000000000000000000000000000 as NUMBER);
select try_cast('1' as NUMBER);
select try_cast(to_numeric(1) as NUMBER) as my_col;
select cast(1 as NUMBER);

Other warehouses support safe_cast for all data types (select try_cast(1 as NUMBER); works in BigQuery and postgres). For safe_cast to be an effective cross-db macro, it should have consistent behavior regardless of the warehouse.
This PR extends safe_cast to allow for fields that are type numeric by wrapping the field in quotes if it is a number:
select try_cast(1 as NUMBER); -> select try_cast('1' as NUMBER);
Testing
I have tested this by adding this macro to my example unit testing project. With the updated macro this unit test:
unit_tests:
  - name: test_valid_email_address # this is the unique name of the test
    description: my favorite unit test
    model: dim_wizards # name of the model I'm unit testing
    given: # the mock data for your inputs
      - input: ref('stg_wizards')
        rows:
          - {WIZARD_ID: 1, EMAIL<EMAIL_ADDRESS>    EMAIL_TOP_LEVEL_DOMAIN: example.com}
          - {WIZARD_ID: 2, EMAIL<EMAIL_ADDRESS>    EMAIL_TOP_LEVEL_DOMAIN: unknown.com}
          - {WIZARD_ID: 3, EMAIL: badgmail.com,         EMAIL_TOP_LEVEL_DOMAIN: gmail.com}
          - {WIZARD_ID: 4, EMAIL: missingdot@gmailcom,  EMAIL_TOP_LEVEL_DOMAIN: gmail.com}
      - input: ref('top_level_email_domains')
        rows:
          - {TLD: example.com}
          - {TLD: gmail.com}
      - input: ref('stg_worlds')
        rows: []
    expect: # the expected output given the inputs above
      rows:
        - {WIZARD_ID: 1, IS_VALID_EMAIL_ADDRESS: true}
        - {WIZARD_ID: 2, IS_VALID_EMAIL_ADDRESS: false}
        - {WIZARD_ID: 3, IS_VALID_EMAIL_ADDRESS: false}
        - {WIZARD_ID: 4, IS_VALID_EMAIL_ADDRESS: false}

creates the expected SQL:
with dbt_internal_unit_test_actual AS (
  select
    WIZARD_ID,IS_VALID_EMAIL_ADDRESS, 'actual' as actual_or_expected
  from (
    with  __dbt__cte__stg_wizards as (

-- Fixture for stg_wizards
select

    try_cast('1' as NUMBER)
 AS WIZARD_ID, try_cast(null as VARCHAR) AS WIZARD_NAME,

<EMAIL_ADDRESS>as VARCHAR)
 AS EMAIL,

    try_cast('example.com' as VARCHAR)
 AS EMAIL_TOP_LEVEL_DOMAIN, try_cast(null as VARCHAR) AS PHONE_NUMBER, try_cast(null as NUMBER) AS WORLD_ID
union all
select

    try_cast('2' as NUMBER)
 AS WIZARD_ID, try_cast(null as VARCHAR) AS WIZARD_NAME,

<EMAIL_ADDRESS>as VARCHAR)
 AS EMAIL,

    try_cast('unknown.com' as VARCHAR)
 AS EMAIL_TOP_LEVEL_DOMAIN, try_cast(null as VARCHAR) AS PHONE_NUMBER, try_cast(null as NUMBER) AS WORLD_ID
union all
select

    try_cast('3' as NUMBER)
 AS WIZARD_ID, try_cast(null as VARCHAR) AS WIZARD_NAME,

    try_cast('badgmail.com' as VARCHAR)
 AS EMAIL,

    try_cast('gmail.com' as VARCHAR)
 AS EMAIL_TOP_LEVEL_DOMAIN, try_cast(null as VARCHAR) AS PHONE_NUMBER, try_cast(null as NUMBER) AS WORLD_ID
union all
select

    try_cast('4' as NUMBER)
 AS WIZARD_ID, try_cast(null as VARCHAR) AS WIZARD_NAME,

    try_cast('missingdot@gmailcom' as VARCHAR)
 AS EMAIL,

    try_cast('gmail.com' as VARCHAR)
 AS EMAIL_TOP_LEVEL_DOMAIN, try_cast(null as VARCHAR) AS PHONE_NUMBER, try_cast(null as NUMBER) AS WORLD_ID
),  __dbt__cte__stg_worlds as (

-- Fixture for stg_worlds
select try_cast(null as NUMBER) AS WORLD_ID, try_cast(null as VARCHAR) AS WORLD_NAME
    limit 0
),  __dbt__cte__top_level_email_domains as (

-- Fixture for top_level_email_domains
select

    try_cast('example.com' as VARCHAR)
 AS TLD
union all
select

    try_cast('gmail.com' as VARCHAR)
 AS TLD
), wizards as (

    select * from __dbt__cte__stg_wizards

),

worlds as (

    select * from __dbt__cte__stg_worlds

),

accepted_email_domains as (

    select * from __dbt__cte__top_level_email_domains

),

check_valid_emails as (

    select
        wizards.wizard_id,
        wizards.wizard_name,
        wizards.email,
        wizards.phone_number,
        wizards.world_id,

		coalesce (regexp_like(
            wizards.email, '^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$'
        )
        = true
        and accepted_email_domains.tld is not null,
        false) as is_valid_email_address

    from wizards
    left join accepted_email_domains
        on wizards.email_top_level_domain = lower(accepted_email_domains.tld)

)

select
    check_valid_emails.wizard_id,
    check_valid_emails.wizard_name,
    check_valid_emails.email,
    check_valid_emails.is_valid_email_address,
    check_valid_emails.phone_number,
    worlds.world_name
from check_valid_emails
left join worlds
    on check_valid_emails.world_id = worlds.world_id
  ) _dbt_internal_unit_test_actual
),
-- Build expected result
dbt_internal_unit_test_expected AS (
  select
    WIZARD_ID, IS_VALID_EMAIL_ADDRESS, 'expected' as actual_or_expected
  from (
    select

    try_cast('1' as NUMBER)
 AS WIZARD_ID,

    try_cast('True' as BOOLEAN)
 AS IS_VALID_EMAIL_ADDRESS
union all
select

    try_cast('2' as NUMBER)
 AS WIZARD_ID,

    try_cast('False' as BOOLEAN)
 AS IS_VALID_EMAIL_ADDRESS
union all
select

    try_cast('3' as NUMBER)
 AS WIZARD_ID,

    try_cast('False' as BOOLEAN)
 AS IS_VALID_EMAIL_ADDRESS
union all
select

    try_cast('4' as NUMBER)
 AS WIZARD_ID,

    try_cast('False' as BOOLEAN)
 AS IS_VALID_EMAIL_ADDRESS
  ) _dbt_internal_unit_test_expected
)
-- Union actual and expected results
select * from dbt_internal_unit_test_actual
union all
select * from dbt_internal_unit_test_expected

Note: Ideally, this should be resolved by snowflake accepting select try_cast(1 as NUMBER);, but this is a work-around in the meantime.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

Note: I would like to add an integration test for this change in functionality, but don't know the best place for that.

Potential inspiration for adding a test for this https://github.com/dbt-labs/dbt-snowflake/pull/839/files#diff-d430faaa1899044a611162c84d921ec87857e6febcd79d9792680df8b96dfd57

@MichelleArk should i close this in favor of your fix?

Yes! This change was pulled into https://github.com/dbt-labs/dbt-snowflake/pull/896 here.


Publish the extension on OpenVSX

OpenVSX is vendor-neutral extension repository for VSCode. The open source version like Code, and Codium cannot connect with the Microsoft's extension repository due to legal reasons.
In lieu of this issue, can you publish the extension to the OpenVSX repository?

@Atinux @antfu @farnabaz any update?


VC: teardown tenant related ns in super master

When teardowning vc, vc-manager just remove the rootNS. Syncer doesn't know whether vc has not been loaded or deleted. We had better remove the tenant related ns in vc-manager vc teardown process.
There is a annotation mark whether this ns belongs to. tenancy.x-k8s.io/cluster vc-manager should scan the ns, and do clean.

/assign @charleszheng44

fixed at #440


Added support for Microsoft Push Notification Service (Windows Phone)

Added support for Microsoft Push Notification Service (Windows Phone).
Currently only supports 'Toast' notifications. (No support for 'Raw' or 'Tile' notifications)
See updated readme for detailed info.

#53


Adapt to 2023.6

Adapted from patch done by kamaradclimber on rte ecowatt :

HA/core removes the async keyword on a method called "async" :face_palm:
This patch fixes it at the expense of not restoring "extra" attributes
(such as "generation time", "period start", "period end" and "level
code") which is very sad.

Thanks a lot!


removeItem performance

👋🏼 Hi,
First of all, thanks for this amazing work.
We are using the file-system IO components at Tuist, and I'd like to bring up something that we notice regarding the performance of the NIOFileSystem.FileSystem.removeItem function.
When we run it against a large directory with many nested directories and and files, we noticed the performance is much worse than using FileManager or just rm -rf in a Linux environment. We benchmarked the performance with hyperfine  and the results are below.
Looking at the implementation, it seems that we are not parallelising at all, so I was wondering if this is something intentional, or if it's ok to refactor that code to run as much as possible in parallel.
Bechmarks
With NIOFileSystem
Benchmark

Time (mean ± σ):     67.939 s ±  4.450 s    [User: 61.906 s, System: 3.205 s]
Range (min … max):   63.684 s … 77.757 s    10 runs

With Foundation's FileManager
Benchmark:

Time (mean ± σ):      5.857 s ±  0.251 s    [User: 1.430 s, System: 2.067 s]
Range (min … max):    5.419 s …  6.190 s    10 runs

With rm -rf
Benchmark:
Time (mean ± σ):      3.150 s ±  0.386 s    [User: 0.022 s, System: 1.666 s]
Range (min … max):    2.225 s …  3.585 s    10 runs

Thanks for filling this! This is definitely something that we would take a patch for and parallelise the removal similar to how we did for copying in https://github.com/apple/swift-nio/pull/2806.

@pepicrft I've raised a PR (#3008) to address the issue of handling removal of items sequentially. I seem to be unable to reproduce your results though. The existing logic in main appears to be performing ok, when compared to rm -rf (albeit slower).
If you still have your test setup, would you mind sharing that, so I can try and reproduce that?

@pepicrft I've raised a PR (#3008) to address the issue of handling removal of items sequentially. I seem to be unable to reproduce your results though. The existing logic in main appears to be performing ok, when compared to rm -rf (albeit slower).
If you still have your test setup, would you mind sharing that, so I can try and reproduce that?

Thanks a lot, @mimischi 🙏🏼. I unfortunately don't have the setup anymore, but I remember it was a directory containing all the dependencies of a project that had been resolved by the SPM. Perhaps you can try with a project that has many dependencies

I've never followed-up here. I've done a few more tests on my PR, but never increased the number of files/directories above five-digits. The benchmarks showed that the new swift-nio is faster than both rm -rf and the FileManager implementation.

I've never followed-up here. I've done a few more tests on my PR, but never increased the number of files/directories above five-digits. The benchmarks showed that the new swift-nio is faster than both rm -rf and the FileManager implementation.

This is fantastic news. Thanks a lot @mimischi 🙏🏼


feat: time command

yeah it's just a time command
you can set the timezone you are in so we can know what time is it where you live
it uses https://api.srizan.ml
code is hosted at https://github.com/SrIzan10/api

any updates?

okay done

gimme a sec


Implement PayPal subscription webhooks

Implement web hooks for subscriptions to add new members to the system.
See https://developer.paypal.com/docs/api-basics/notifications/webhooks/rest/#configure-a-webhook-listener

https://github.com/HackRVA/memberdashboard/commit/6346ac6976d77a96985b9dff3df5446bcd56cc79


When a Chinese appears in a .py file, an error is reported for unrecognized characters

Describe the bug
当.py文件出现中文字符时，py转pyd时会报错无法识别的字符（main.py:10:20: Unrecognized character）
Code to reproduce the behaviour:
# example code

Expected behaviour
No response
OS
win20
Python version
3.10
Cython version
No response
Additional context
No response

This should work on the Cython 3 pre-release (let us know if it doesn't). It won't work on the 0.29.x releases

Duplicate https://github.com/cython/cython/issues/2601

这应该适用于 Cython 3 预发布版（如果不支持，请告诉我们）。它不适用于 0.29.x 版本
Where to download the pre-release version of Cython 3

Where to download the pre-release version of Cython 3

pip install --pre "Cython>=3"


bug: A dataclass field with init=False should not be a parameter

Here are failing tests.
from griffe.tests import temporary_visited_module

code = """
from dataclasses import dataclass, field

@dataclass
class PointA:
    x: float
    y: float
    z: float = field(init=False)

@dataclass(init=False)
class PointB:
    x: float
    y: float

@dataclass(init=False)
class PointC:
    x: float
    y: float = field(init=True)  # init=True has no effect
"""

with temporary_visited_module(code) as module:
    paramsA = module["PointA"].parameters
    paramsB = module["PointB"].parameters
    paramsC = module["PointC"].parameters

    assert "z" not in paramsA
    assert "x" not in paramsB and "y" not in paramsB
    assert "x" not in paramsC and "y" not in paramsC

Then there are the perhaps more complicated cases to deal with statically where the field class is wrapped inside another function e.g.
def no_init(default: T) -> T:
    """
    Set default value of a dataclass field that will not be __init__ed
    """
    return field(init=False, default=default)

@dataclass
class Point:
    x: float
    y: float = no_init(0)  # y is not a parameter

Parameters for dataclasses are currently dynamically created when accessing the class' parameters property. Seeing that the logic can get quite complex, and based on the fact that this parameters property cannot be easily extended by users or extensions, I think we should change the logic and generate an __init__ method object when visiting class decorated with @dataclasses.dataclass. Extensions for third-party libs (Pydantic, attrs, whatever) could then do the same. without any special code in Griffe itself.

I haven't looked at the how the parameters are generated, but I have a temporary solution that inspects ExprCall parameters and I only do the check for dataclasses.
Obviously this does not handle the cases when `field(init=False) is hidden inside another function.

Yes, that's what we'll use in Griffe too (thanks for the link). Just not in the parameters property as it's not extensible :)


small bug in example section of README

fixed error handling in example section of README.md

Closing this PR


Cloud drives status doesn't always show

Describe the bug
My personal google drive and work OneDrive doesn't not show it status when there clients are open. but my person OneDrive does. even when clients are closed the last know status should show.
Expected behaviour
Status bar should always show on all cloud drives.
Screenshots

Desktop (please complete the following information):

OS Version: Windows 10 20H2 19042.844
App version: v1.3.0..0

Log file
debug.txt
debug_fulltrust.txt

The issues of google drive icons not changing has been fixed in 1.4.1, However my school OneDrive account still doesn't have the sync tab details like it should. I also think that google drive should also have the sync tab stuff.

Fixed in 1.5.67


Nested Layouts for routes

I love the boilerplate but am having issues having nested layouts for instances
export default (
  <Route path='/' component={BaseLayout}>
    <Route path='auth' component={Auth} />
    <Route component={AuthenticatedLayout}>
      <Route path="dashboard" component={Dashboard} />
      <Route path='Inbox' component={Inbox} />
    </Route>
  </Route>
)

In this instance, you can see that the authenticated routes have another layout applied to it. But this boilerplate defines a different way to construct your routes such as
export default function createRoutes (store) {
  return {
    path: 'posts',
    getComponents (location, cb) {
      require.ensure([
        './containers/PostList',
        './reducer'
      ], (require) => {
        let PostPage = require('./containers/PostList').default
        let postReducer = require('./reducer').default
        injectAsyncReducer(store, 'posts', postReducer)
        cb(null, PostPage)
      })
    }
  }
}

So I would love assistance on this topic!

Did you get anywhere with this? I've tried something similar myself and couldn't get it working. I don't think redial can do data fetching on nested routes.
I tried this:
routes/postList/index.js:
export default function createRoutes (store) {   return {     path: 'posts',     getComponents (location, cb) {       require.ensure([         './containers/PostList',         './reducer'       ], (require) => {         let PostPage = require('./containers/PostList').default         let postReducer = require('./reducer').default         injectAsyncReducer(store, 'posts', postReducer)         cb(null, PostPage)       })     },     getChildRoutes(partialNextState, cb) {       path: '23',       console.log('get child routes of parent path')       require.ensure([], (require) => {         cb(null, [           require('./routes/Test').default,         ])       })     },   } }
Then:
routes/postList/routes/index.js:
export default function createRoutes (store) {   return {     path: '/test',     getComponents (location, cb) {       console.log('get comp of nested route test')       require.ensure([         './containers/Test',         './reducer'       ], (require) => {         let testPage = require('./containers/Test').default         let testReducer = require('./reducer').default         injectAsyncReducer(store, 'tests', testReducer)         cb(null, testPage)       })     }   } }
In this case Test Component doesn't use redial. This routing still doesn't work.
It would be nice to get a few things cleared up regarding how this type of routing would work with Redial and code splitting.

Not redial cannot do nested fetching. [redux-taxi](https://github.com/nyt/redux-taxi) and does.

@jaredpalmer Even without redial hooks on nested components the above example does not work, is this expected if the parent component is using redial?

getChildRoutes(partialNextState, cb) {
      path: '23',
      console.log('get child routes of parent path')
      require.ensure([], (require) => {
        cb(null, [
          require('./routes/Test').default,
        ])
      })
    },

this isn't valid js btw.

your issue doesn't have to do with redial, but how your defining your routes.
getChildRoutes should require another route file(s). getComponents should require components / reducers for the current route.

See the React-router v3 mega app for another example

With this code the route gets hit:
postlist/index.js
export default function createRoutes (store) {
  return {
    path: 'posts',
    getComponents (location, cb) {
      require.ensure([
        './containers/PostList',
        './reducer'
      ], (require) => {
        let PostPage = require('./containers/PostList').default
        let postReducer = require('./reducer').default
        injectAsyncReducer(store, 'posts', postReducer)
        cb(null, PostPage)
      })
    },
    getChildRoutes(partialNextState, cb) {
      console.log('get child routes of parent path')
      console.log('store: ' + store)
      require.ensure([], (require) => {
        cb(null, [
          require('./routes/Test').default(store),
        ])
      })
    },
  }
}

postlist/routes/test/index.js
export default function createRoutes (store) {
  return {
    path: 'test',
    getComponents (location, cb) {
      console.log('get comp of nested route test')
      require.ensure([
        './containers/Test',
        './reducer'
      ], (require) => {
        let testPage = require('./containers/Test').default
        let testReducer = require('./reducer').default
        injectAsyncReducer(store, 'tests', testReducer)
        cb(null, testPage)
      })
    }
  }
}

The getChildRoute function gets hit but the ./routes/Test is not rendered. This page has no redial hooks on it but it still does not render on the client or the server, the parent page /posts is shown.

I just ended up giving up on the routing technique used in this boilerplate. I removed async reducers and just added them in normally then went back to the conventional way of react router.

I managed to get this working today, do you want me to post my findings ?

Yes please. Add to the knowledge base!

@lewis-elliott yes!


Theme Integration

Hello guys!
The integration aims to provide the usual stuff:

admin section covered (for superusers)
DJANGO.contrib.auth flow pages
Registration
pages for common users

Being a simple kit, all pages should be migrated.
Ty!  🚀🚀

Great work guys @MySecondLanguage, @mominur-helios
Validated. Closing.


Publish the container image to GHCR or Docker Hub

I wanted to run this VERY USEFUL tool (THANK YOU) but didn't want to build it. I saw that running a docker container is mentioned in the documentation, so I ran it, but it failed because no image with the name inotify-info is available on Docker Hub.
I see a few <USERNAME>/inotify-info images on Docker Hub but none from @mikesart account. I ended up running the image from mongey/inotify-info and it worked fine, but still, I want to propose to:

Publish the image to this repository using GHCR or Docker Hub.
Update the readme either way with the correct image name, since the current one doesn't work.

Thank you! Awesome tool!
P.S. If you decide to publish a container image to this repo, the command to run it will look like this: docker run --rm --privileged -v /proc:/proc ghcr.io/mikesart/inotify-info

Just in case, here's a link to documentation on how to publish images to GHCR.

This was previously discussed in #28.
I have updated the README and clarified the build steps in #43, should be clearer now.


Revert "[event_engine] Move combiner executor usage to event engine"

Reverts grpc/grpc#31713 since it breaks importing.

Closed this PR since the issue in the importing was fixed forward.

We'll push ahead with the revert since this change introduces an init ref leak in end2end:channelz_service_test, apparently only on Windows.


BUG The carousel shifts to the right if slides have at least 1px border.

Steps:

Go to Examples page: https://ssense.github.io/vue-carousel/examples/
Navigate to the last slide
Add border: 1px solid #000; to the .VueCarousel-slide {

Actual result: carousel has shifted to the right.
See screenshots:
https://i.imgur.com/tAsJCv4.png
https://imgur.com/a/hIplEys

I think this is to do with adding border through the inspector. As the carousel width is calculated on render, changing the border will add 2px to each slide, without recalculating the width of the carousel.
If you add the border in your CSS and properly re-render, it will likely work out fine!


How to test OAuth code?

Description
I looked at the discussions here: https://github.com/slackapi/bolt-js/issues/302
How do you test the OAuth workflow?
Assume that we just test it manually. We have to do the following steps:

We still have to create the app (we need client id and secret to init the app in code)
Make sure to uninstall your app from your workspace
Implement the Add to Slack button
Press the Add to Slack button, and it should direct the user to the app slack oauth page (The url looks like https://<YOUR_APP>.slack.com/oauth/xxxxx)

Is my understanding right?
Also, is there an easy way to write automated tests for this workflow?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Is my understanding right?

Yes, it is.

Also, is there an easy way to write automated tests for this workflow?

At the Spec conference last year, we had a workshop on Slack app testing with Puppeteer. A similar approach may work for you.
https://github.com/ESattler/Functional-Testing-Slack-Bots/blob/master/starterfiles/README.md

Let us close this issue due to inactivity. Please feel free to write in when you have any further comments/questions!


"Change or Move Organizations" in Profile Does not Work

Describe the bug
The "Change or Move Organizations" button in Profile is inoperable.
To Reproduce
Steps to reproduce the behavior:

Go to Profile. Click the button. Nothing happens.

I can't remember if we built this functionality or not. If we have, please activate the button. If not, please hide the button.
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.

We haven't implemented it yet. I'll remove the button for now


Fix ToJsonString

Right now, this will only encode strings up to the first escape character, and it won't encode anything at all if no escape characters are found.
That is to say, currently "foo".to_owned().to_json_string() returns "", and "foo\" bar".to_owned().to_json_string() returns "foo".

Merged. ty


[Bug] During persist_docs, col names in the schema yml file should always be uppercased if we don't have a quote config on the column

Is this a new bug in dbt-snowflake?

[X] I believe this is a new bug in dbt-snowflake
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
If users have columns.name key in a mixed case - dbt does not correctly match the uppercased column name that comes from a describe table ... with what is in the schema.yml file - therefor, column descriptions aren't added to the column.
Expected Behavior
During the "matching process" - we should always uppercase the columns.name key no matter the case if the user doesn't specify the quote config on the column (https://docs.getdbt.com/reference/resource-properties/quote).
Steps To Reproduce
Project setup:
# dbt_project.yml
name: my_dbt_project
profile: all
version: "1.0.0"

models:
   my_dbt_project:
      +materialized: table

# models/schema.yml
models:
  - name: foo
    columns:
      - name: mixed_Case
        description: Col description

-- models/foo.sql
{{ config(persist_docs={"columns": true}) }}
select 1 as mixed_Case

Run
$ dbt --debug run
22:05:24  1 of 1 START sql table model dbt_jyeo.foo ...................................... [RUN]
22:05:24  Re-using an available connection from the pool (formerly list_development_jyeo_dbt_jyeo, now model.my_dbt_project.foo)
22:05:24  Began compiling node model.my_dbt_project.foo
22:05:24  Writing injected SQL for node "model.my_dbt_project.foo"
22:05:24  Began executing node model.my_dbt_project.foo
22:05:24  Writing runtime sql for node "model.my_dbt_project.foo"
22:05:24  Using snowflake connection "model.my_dbt_project.foo"
22:05:24  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
create or replace transient table development_jyeo.dbt_jyeo.foo
         as
        (
select 1 as mixed_Case
        );
22:05:24  Opening a new connection, currently in state closed
22:05:26  SQL status: SUCCESS 1 in 2.0 seconds
22:05:26  Using snowflake connection "model.my_dbt_project.foo"
22:05:26  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
describe table development_jyeo.dbt_jyeo.foo
22:05:26  SQL status: SUCCESS 1 in 0.0 seconds
22:05:26  Using snowflake connection "model.my_dbt_project.foo"
22:05:26  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
alter table development_jyeo.dbt_jyeo.foo alter

        "MIXED_CASE" COMMENT $$$$;
22:05:26  SQL status: SUCCESS 1 in 0.0 seconds
22:05:26  On model.my_dbt_project.foo: Close
22:05:27  Sending event: {'category': 'dbt', 'action': 'run_model', 'label': '102c02e3-7b4f-48a1-91be-ac0bb00f1129', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x13f491f50>]}
22:05:27  1 of 1 OK created sql table model dbt_jyeo.foo ................................. [SUCCESS 1 in 2.83s]

^ What happens here....

We created the table column as select 1 as mixed_Case - and what happens is Snowflake has this column as a uppercased MIXED_CASE (this is the default behaviour of Snowflake).
We run a describe table and the describe has returned that a column MIXED_CASE exist.
This uppercase MIXED_CASE that comes from the describe, does not match what is in the schema.yml which has that as mixed_Case.
"MIXED_CASE" != "mixed_Case" so we don't find a matching column description.
Because there is no matching column description then the comment added is empty.

What can users do about this
(A) They can quote the column name in the model
-- models/foo.sql
{{ config(persist_docs={"columns": true}) }}
select 1 as "mixed_Case"

# models/schema.yml
models:
  - name: foo
    columns:
      - name: mixed_Case
        description: Col description

$ dbt --debug run

22:10:57  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
create or replace transient table development_jyeo.dbt_jyeo.foo
         as
        (
select 1 as "mixed_Case"
        );
22:10:57  Opening a new connection, currently in state closed
22:10:59  SQL status: SUCCESS 1 in 2.0 seconds
22:10:59  Using snowflake connection "model.my_dbt_project.foo"
22:10:59  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
describe table development_jyeo.dbt_jyeo.foo
22:10:59  SQL status: SUCCESS 1 in 0.0 seconds
22:10:59  Using snowflake connection "model.my_dbt_project.foo"
22:10:59  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
alter table development_jyeo.dbt_jyeo.foo alter

        "mixed_Case" COMMENT $$Col description$$;
22:10:59  SQL status: SUCCESS 1 in 0.0 seconds

Here Snowflake has created a literal mixed case column name mixed_Case - the describe returns this exactly and we get a match in the schema.yml file - "mixed_Case" = "mixed_Case" - therefor, we can apply the column description appropriately.
Cons
Their table will have a literal mixed case column name which they may not want.
(B) They can uppercase / lowercase the column name in the schema yaml
-- models/foo.sql
{{ config(persist_docs={"columns": true}) }}
select 1 as mixed_Case

# models/schema.yml
models:
  - name: foo
    columns:
      - name: mixed_case # This can also be 'MIXED_CASE' (all uppercase) - the net effect is the same.
        description: Col description

$ dbt --debug run
22:15:28  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
create or replace transient table development_jyeo.dbt_jyeo.foo
         as
        (
select 1 as mixed_Case
        );
22:15:28  Opening a new connection, currently in state closed
22:15:30  SQL status: SUCCESS 1 in 2.0 seconds
22:15:30  Using snowflake connection "model.my_dbt_project.foo"
22:15:30  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
describe table development_jyeo.dbt_jyeo.foo
22:15:30  SQL status: SUCCESS 1 in 0.0 seconds
22:15:30  Using snowflake connection "model.my_dbt_project.foo"
22:15:30  On model.my_dbt_project.foo: /* {"app": "dbt", "dbt_version": "1.8.4", "profile_name": "all", "target_name": "sf", "node_id": "model.my_dbt_project.foo"} */
alter table development_jyeo.dbt_jyeo.foo alter

        "MIXED_CASE" COMMENT $$Col description$$;
22:15:31  SQL status: SUCCESS 1 in 0.0 seconds

For some reason, if the columns.name key is either:

All UPPERCASED.
All lowercased.

dbt has some internal methods to match this correctly.
Cons
User have to have a different column casing style between their model code and their schema yml files.
Relevant log output
No response
Environment
- OS: macOS
- Python: 3.11
- dbt-core: 1.8.4
- dbt-snowflake: 1.8.3

Additional Context
If users don't specify the quote column config (https://docs.getdbt.com/reference/resource-properties/quote) - I propose we always uppercase the columns.name key like (B) above - even if the user is going to specify a mixed case column name in the schema yml file.

https://github.com/dbt-labs/dbt-snowflake/blob/7fb4549abc52d53dfdbf02da423ee58cc8696ccc/dbt/include/snowflake/macros/adapters.sql#L2-L7
^ Ah ok so here is why Case (B) works... we both upper and lower the column names and match it in the column dict... therefore always lowercased or UPPERCASED would match something for sure....


2.3/rc1: Standardize right click behavior in VPE

Is your feature request related to a problem? Please describe.
As a user, I would like to observe consistent behavior if I right-click in the canvas area:

right click on node
right click on comment [node]
right click on canvas

Describe the solution you'd like
Right click on node
Current behavior:

Desired behavior:

Updated text: "Open Node Properties"

Right click on comment node
Desired behavior:

Context menu with entry "Open  properties" (see related https://github.com/elyra-ai/elyra/issues/1746#issuecomment-859650865)

Right click on canvas
Current behavior:

Desired behavior:

"Open properties" -> "Open Pipeline Properties"
"New File Node" -> "New Node" # opens properties view > palette tab

Discussion topic: For component nodes the editor should not display context menu entries that can never be used.

For example, a user cannot convert a component node into a file node and therefore the disabled "Open File" menu entry can never be utilized unless (this is what I believe should be discussed) this action would open the YAML file (e.g. in read-only mode) that the component is based on. If it should be possible to open the YAML file, the context menu entry should be renamed for [component] nodes to "Open Definition".


pattern in html is build wrong to the production

Hi there
I have a template which contains:
<input autofocus="autofocus" class="form-control" placeholder="Email" type="email"
        id="email" [(ngModel)]="model.email" name="email" required
            pattern="^\w+([\.-]?\w+)*@\w+([\.-]?\w+)*(\.\w{2,3})+$"
        #email="ngModel"/>

in dev it works fine, but when doing
npm run build.prod
the pattern is changed to
^w+([.-]?w+)*@w+([.-]?w+)*(.w{2,3})+$
you see the missing \ in the string.  (i found this out with the firefox inspector)
so the production code is not working.
How can this be fixed, and where in the build.prod will this be produced?
Thanks,
Martin

Does your production build runs the ahead of time compiler (compile.ahead.prod gulp task)?

Seems to be fixed in the new rc6 from yesterday... Thanks.

it is now there again.  i merged today the angular2-seed tree to my project.
the build.prod creates the error, build.prod.ext failes with
[13:55:55] 'compile.ahead.prod' errored after 2.24 s
r.rb:38:in `call'                                                                    │[13:55:55] TypeError: Cannot read property 'push' of undefined
        from /home/martin/.gem/ruby/2.3.0/gems/spring-1.7.2/lib/spring/application.rb│    at /home/martin/Projects/lf/client/tools/tasks/seed/compile.ahead.prod.ts:26:17

what can I do?

Hi @grauschnabel,
have you thought about using a programmatic validator to enforce your email pattern?
Have a look here: http://blog.thoughtram.io/angular/2016/03/14/custom-validators-in-angular-2.html#building-a-custom-validator

Yes, but normally I go the easiest way- and in development it works well, I just want the same in production...

Known issue in gulp-inline-ng2-template

Currently build.prod.exp doesn't use gulp-inline-ng2-template because it uses AoT with @angular/compiler.
I'll take a look at this issue as soon as I can. If anyone has some spare time help will be greatly appreciated!

I am also experiencing this issue when trying to run a pattern check inside my template. It is striping out the .
For now I have moved my RegExp to the controller but would love to continue to leverage this functionality once we figure out where this issue is coming from!

@grauschnabel I can no longer reproduce the issue using npm run build.prod.exp. I did some fixes in the AoT compilation support so I think everything should work now.
Would you verify and close the issue?

Closing it due to inactivity. @grauschnabel let me know if the issue is not resolved yet.

I am still experiencing the issue. Now in scss files (I guess they are minified as well) "content: '\24'" is compiled to "content: '24'" (the backslash is gone).


Scroll does not working when SketchPicker is enabled ?

https://codesandbox.io/s/reverent-shadow-jfl6po?file=/src/App.js

@Parameshvadivel
Could you let me know if you find any solution? I have the same problem.

@Parameshvadivel @Abdulrahman-Sallam Same issue. Any news? Thanks!

Same issue here, any news guys ?!


Animated.FlatList prop contentContainerStyle doesn't handle animated values

Description
As I noted in the heading, the Animated.FlatList component does not accept animated values for the contentContainerStyle property. It only seems to work for style.
This is not the behaviour one would expect from an animated component and should be changed.
React Native version:
System:
    OS: macOS 11.5.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 196.01 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.6 - /usr/local/opt/node@14/bin/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 6.14.15 - /usr/local/opt/node@14/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.2 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
    Android SDK:
      API Levels: 28, 29, 30, 31
      Build Tools: 29.0.2, 30.0.2, 31.0.0
      System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Arctic Fox 2020.3.1 Arctic Fox 2020.3.1
    Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_292 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.65.1 => 0.65.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Add Animated.FlatList with some sample data to your app
Try to pass an animated value to contentContainerStyle

Expected Results
I would expect this to work with one of the animated components, but instead the screen freezes.
Snack, code example, screenshot, or link to a repository:
https://snack.expo.dev/@reichhartd/animated_flatlist-example

@stale Yes, please leave it open.

I am having the same issue.

i have the same issue


Fix: remove latest from 0.17 version from Readme.md

This was discovered in #78, there are 2 latest versions (0.18 and 0.17).
Just to make sure, I ran docker run ruimarinho/bitcoin-core --version and the text Bitcoin Core Daemon version v0.18.0 was printed.
So it's just a documentation issue on the readme file.

For some reason, 0.13 alpine version failed. I just changed a readme. hehe

ACK
I forgot to remove the latest tag from 0.17 in #76.
The alpine build is a bit unstable because of the key servers that are being DOSd. Most likely not your fault.

Thanks!


Completions E2E tests

Stylable completions appear before CSS completions. [Can't be tested in server, no CSS completions]
Completions suggest file names from local FS for '-st-from:'. [Can't be tested in server, client loads the files]

Blocked by #2

2nd not relevant, other extension does it


Need content for the About page

Hard requirements from the project spec:

description of the site, its purpose, its intended users
the group name
the group members
for each member:

name
photo
bio
major responsibilities
no. of commits
no. of issues
no. of unit tests

stats:

total no. of commits
total no. of issues
total no. of unit tests
a link to the Apiary API
a link to the GitHub Issue Tracker
a link to the GitHub Repo
a link to the GitHub Wiki

data:
l  * inks to the data sources

description of how each was scraped

tools:

tools used
describe their use
special focus on optional tools that were not required

Other than the hard requirements go wild

Almost done. need rest of teams pics and info

done


logging: Duplicate only strings from rw memory

If argument for log_strdup is from ro memory then there is
no point to duplicate it. This may happen if function logs
variables coming from outside, e.g. function argument.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

fyi, @rakons


[Requesting Null.jpg Error] bypass

Temp bypass error for the null.jpg error
https://github.com/rarcega/instagram-scraper/issues/400

if "null" in str(url): - this can be bad, since the ig_cache_key-parameter in the url also contains lowercase letters. I think you should use something like if "https://static.cdninstagram.com/rsrc.php/null.jpg" in str(url):.

Doesn't work with --retry-forever option.
2019-09-16 13:20:52,258 - instagram_scraper.app - WARNING - Retry after exception HTTPError('403 Client Error: Forbidden for url: https://static.cdninstagram.com/rsrc.php/null.jpg',) on https://static.cdninstagram.com/rsrc.php/null.jpg from https://www.instagram.com/p/B2XFiekH3UN


Add shortcut to Quick Add Time

Currently, we click on Quick Add Time button to add time, I would like to add it via a keyboard shortcut.
Great project btw

Hey @dantehemerson, that's a great idea, I think I'd actually use that as well. Feel free to contribute a change if you'd like to give it a shot 🙂


Create a Component for the podcast list item

What is this one for? You made a ticket from the kanban an issue?

Sanix said we should create ticket in each task we do. when is done we close the issue and move to the next one.
Though is stressing and i don't see the need

Sanix said we should create ticket in each task we do. when is done we close the issue and move to the next one. Though is stressing and i don't see the need

seriously 😆

See na no me oh.
Will create the component and open pull request  hahahahha

😄 waiting for to review

@godsakani This closed issue is not correct, from what I can see the task hasn't been performed. The task from the title was to generate a list component for the podcasts which wasn't done. Please check everything and let's discuss before the issue and PR is closed or merged respectively.

@godsakani This closed issue is not correct, from what I can see the task hasn't been performed. The task from the title was to generate a list component for the podcasts which wasn't done. Please check everything and let's discuss before the issue and PR is closed or merged respectively.

No please . it was
First to create a podcastlist component which i did
secondly was then add that static list which am currently doing it


upgrade to Baragon 0.1.4 + handle INVALID_REQUEST_NOOP

@wsorenson @ssalinas could you help verify this logic is accurate?

@tpetr added a condition for INVALID_REQUEST_NOOP to go to a FAILED deploy state in deploy checker, imitating the behavior of a FAILED load balancer request


select 没有通过API方式清空选中值的方式吗

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info
What are the similar cases of this feature
通过API方式清空选中值
What problem does this feature solve?
通过API方式清空选中值

没有，只能通过 value 控制。