[PDapp] Insight Report: Toast

Description
Fill out the Toast insight report from your findings from the audit
The insight report will be part of our decision making framework and is intend to:

Document all findings from the component audit
Confirm as many component details as possible
Mitigate component inconsistencies across Figma, Mobile and Extension

Include your thoughts on component name, description, api and any comments or topic to discuss relating to the component or it's make up. We will review the audit and insight report in our Wednesday technical sync to finalize the details of the component for all platforms.
Technical Details
The insight report should include the following for the component

name
description
variants/props
requirements (optional)
discussion/questions (optional)

Acceptance Criteria

name, description variants/props is filled out and matches with other platforms where possible

References

FigJam
Read exercised #05 Identify Existing Paradigms in Design and Code and #06 IdentifyEmergingandInteresting Paradigms in Design and Code in the Design System in 90 Days workbook

Can use insight report diagram @brianacnguyen has done for PDapp


#128 moved internal impl to detail dir/namespace

To keep consistency of public fkYAML library APIs as much as possible, implementations for internal use only have been moved to include/fkYAML/detail directory.
Such implementations are subject to changes without notices, and thus have no gurantee of consistency even if the fkYAML library provides its backward compatibility.
Those moved implementations will still be listed in the fkYAML release package because they are still necessary for a project which uses the fkYAML library.
Furthermore, part of doxygen comments have been fixed to make it up to day.
See #128 for more details.

To fix failure in GA workflow, the command for clang-format has been moved from CMakeLists.txt to Makefile.
This would be reasonable since clang-format does not require build options for a header-only library.


Fixed bug where changed rule woudlnt load if it failed to load previo…

Fixes a bug where if a rule gets added, and its initialization throws an exception, it is in self.rule_hashes but not self.rules. So if it changes, it will be "reloaded" but then it doesn't exist in self.rules so it doesn't get added (It normally replaces the old version with the new).
This also adds a test for this case and fixes the mock rules which were incomplete but weren't causing errors until I hit the bugged code.

just dooo it


Release 0.10.0

Signed-off-by: Tim Smith<EMAIL_ADDRESS>

:+1:. Might be nice to have tags for "Merged pull requests", but I can't say I care enough to have it block anything.


Rust 2018 idioms

related with #3328 https://github.com/rust-lang/rust/issues/58099

Hmm, having <'_> all over the place feels a bit gross to me, but if this is preferred in Rust 2018, then I guess we should just get used to it...
In any case, thank you for the PR!


Logging setting

Is there a public method to turn on logging? I turned it on with Logging.enableDebug = true; in .\Library\Logging.js but it would be nice to see logging without touching something inside node_modules.

You can use appInsights.setInternalLogging(true, true) to enable logging. The first argument enables/disables debug logging, the second enables/disables warning

It depends which version of this SDK you're using. In 0.22 as well as all stable releases (1.0+) this method is setInternalLogging, in releases before that there are two methods: enableVerboseLogging and disableVerboseLogging

In case someone comes looking for this, here is what worked for me: appInsights.Configuration.setInternalLogging(true,true);


i train the model on dataset dukemtmc, how can i evaluate the model on dataset market1501 before  Adaptation

i cna't load the model trained on duckmtmc, dukemtmc, num_classes=632 , market1501 ,num_classes=676,when i load the model ,
RuntimeError: Error(s) in loading state_dict for ResNet:
size mismatch for classifier_x2.weight: copying a param with shape torch.Size([632, 2048]) from checkpoint, the shape in current model is torch.Size([676, 2048]).
size mismatch for classifier_x2.bias: copying a param with shape torch.Size([632]) from checkpoint, the shape in current model is torch.Size([676]).

For evaluation, you don't need to care about the last fc layer.


Style setter for attached property failed when it has been set in ControlTemplate.

Describe the bug
If the style selector has no condition like ':has-icon' or property selector, the attached properties can not be set when they have been set in ControlTemplate.
Expected behavior
The BindingPriority of 'StyleTrigger' should have higher priority than 'TempaltedParent'.
Code
    <ControlTheme x:Key="{x:Type priority:EButton}" TargetType="priority:EButton">
        <Setter Property="priority:EButton.Template">
            <ControlTemplate TargetType="priority:EButton">
                <Grid Background="Green"
                      RowDefinitions="*,*,*"
                      ShowGridLines="True">
                    <Border x:Name="PART_Border"
                            Grid.Row="1"
                            Background="red" />
                </Grid>
            </ControlTemplate>
        </Setter>

        <Style Selector="^ /template/ Border#PART_Border">
            <Setter Property="Grid.Row" Value="2" />
        </Style>

        <!-- This can set successfully. -->
        <!--<Style Selector="^:pointerover /template/ Border#PART_Border">
            <Setter Property="Grid.Row" Value="2" />
        </Style>-->
    </ControlTheme>

Screenshots

Desktop (please complete the following information):

OS: [Win11]
OS Version [22H2]
Avalonia Version [11.0.0-preview4], [11.0.0-preview6]

Additional context
Demo for it.
Avalonia.AttachedProperty.Priority.zip

It is by design. Template priority is higher than style priority, but lower than style trigger priority. https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.Base/Data/BindingPriority.cs#L20-L38 In your case Grid.Row="1" won't make much sense with your expectations, as it needs to be replaced with a style.

Thank you. I have misunderstand it.


add docker network options for management network

to create a user defined network that will use the existing linux bridge one can use a docker option like this:
docker network create --driver=bridge \
  -o "com.docker.network.bridge.name=br0" mgmt

we can expose an option bridge_name under the mgmt section to reflect this intent
(ref)

the options can wait, since we added the most wanted on - the backing bridge in https://github.com/srl-labs/containerlab/pull/469/commits/f99cc29bd92dc5a39f2aae348e4d36690a0c70a2


Refactor: Batch write graphML

In this PR:

Use a dictionary to store the graphs
Avoid redundant checks
Use a single loop for adding nodes and edges
Batch write GraphML files: Instead of saving each graph individually, you can collect the graphs in a dictionary and write them to separate GraphML files after the loop. This reduces the number of file write operations.

Thanks a lot! I'll test soon :))

Works like a charm and much better, thanks!


fix: make textfield a controlled component

Issue #, if available:
Moving TextField from uncontrolled to controlled allows resetStateValues to properly reset its field to its initial state. This is called both during Clear onClick as well as during a success Submit if clearOnSubmit is set to true. This also contributes to the overall task of moving all components to controlled.
Tested locally in app with Date and Time fields, as well as interacting with onSubmit and reset onClick calls.
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #830 (9fdc21a) into main (6898d10) will increase coverage by 0.06%.
The diff coverage is 95.23%.

@@            Coverage Diff             @@
##             main     #830      +/-   ##
==========================================
+ Coverage   91.63%   91.69%   +0.06%
==========================================
  Files         102      102
  Lines        4122     4128       +6
  Branches     1175     1174       -1
==========================================
+ Hits         3777     3785       +8
+ Misses        325      324       -1
+ Partials       20       19       -1

Impacted Files
Coverage Δ

packages/codegen-ui-react/lib/forms/form-state.ts
98.49% <ø> (ø)

.../codegen-ui-react/lib/forms/react-form-renderer.ts
84.07% <50.00%> (+1.25%)
:arrow_up:

...ges/codegen-ui-react/lib/forms/component-helper.ts
96.00% <100.00%> (-1.37%)
:arrow_down:

...codegen-ui-react/lib/forms/form-renderer-helper.ts
98.32% <100.00%> (ø)

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 6898d10...9fdc21a. Read the comment docs.


Add debug info support for inlined and specialized generic variables.

This patch adds SIL-level debug info support for variables whose
static type is rewritten by an optimizer transformation. When a
function is (generic-)specialized or inlined, the static types of
inlined variables my change as they are remapped into the generic
environment of the inlined call site. With this patch all inlined
SILDebugScopes that point to functions with a generic signature are
recursively rewritten to point to clones of the original function with
new unique mangled names. The new mangled names consist of the old
mangled names plus the new substituions, similar (or exactly,
respectively) to how generic specialization is handled.
On libSwiftCore.dylib (x86_64), this yields a 17% increase in unique
source vars and a ~24% increase in variables with a debug location.
rdar://problem/28859432
rdar://problem/34526036

@swift-ci test

This might also fix SR-5935, but I haven't verified this yet.

Build failed
Swift Test Linux Platform
Git Sha - 36514c8e6a96523c3b4ebd551b5ac0b2c43901e7

Build failed
Swift Test OS X Platform
Git Sha - 36514c8e6a96523c3b4ebd551b5ac0b2c43901e7

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 36514c8e6a96523c3b4ebd551b5ac0b2c43901e7

Build failed
Swift Test Linux Platform
Git Sha - 36514c8e6a96523c3b4ebd551b5ac0b2c43901e7

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 46931576c59c1014afe6035c6acae1be2579a3ec

Build failed
Swift Test Linux Platform
Git Sha - 46931576c59c1014afe6035c6acae1be2579a3ec

@swift-ci test source compatibility


May I ask if there are any publications/papers for this project?

We are currently working on publishing them.
There will be some publications, hopefully this year.
Thanks for your interest!


docs: add some examples and reorder some parts

It adds some more detailed examples of configuration and reorder some parts to follow the installation process.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-07-21T15:49:14.356+0000

Duration: 6 min 52 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
5

Skipped
0

Total
5

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@astorm good questions. Let me have a stab at trying to answer them.
I think we can at least assume that the user has some basic k8s knowledge, since they've already deployed their app to a k8s cluster and now want to start monitoring them. But the user should not have to be proficient with APM to get started using the webhook. But ofc the easier we can make it, the better.
Do you think we can lower the barrier by improving the docs or do you think there's something more fundamental to the design that makes it particularly complicated?
One idea that comes to mind after watching one of your demos/async updates is that we could record a short demo (~5m) that walks users through a basic scenario on how to get started. I think you did a fantastic job with that demo (also loved the subtle humor 🙂). Would you be interested in recording a public-facing demo? I don't think it has to be super polished something along the lines and production quality of what you already did would be more than sufficient IMO.

Do you or @AlexanderWert have any thoughts/feeling on which user persona we're building this for? Mainly asking because as we start moving this out of technical preview and start writing technical and enablement docs having that user persona locked in is going to be increasingly important.

 Those users that have one or two (a few) services on k8s are not the target to use the webhook does not worth on those cases.


docs: Add comprehensive documentation for Tidy 5e sheet flags and hooks

Document what flags and hooks Tidy 5e sheet has, what they mean, where they are used, and how they are used.
Some Ideas
Generate it externally
Generate this documentation from what is actually in the code in main.
Automated it with a github action on changes to main, if possible.
Big pro for this approach .... ? I don't know. It was the first idea that came to mind.
Derive it within Foundry
When flags/hooks are consolidated to a centralized provider, use the mighty power of svelte to generate a flags reference and a hooks reference directly in Foundry, either in a dialog summoned by button click on the module's config settings, or in a debug tab on Sheet Settings. Heck, might we even have a Developer Settings UI as its own thing? There are other things I could use in there, in addition to flags and hooks references.
Big pro for this approach: localization is easier and the documentation will always stay relevant to the current code.
This approach requires performing a much-needed refactor to tidy 5e sheet flags and hooks: bringing them into consolidated providers (FlagsProvider, HooksProvider) that can also include metadata and explanations of their use.

I did do that, actually :D


Failed to save "Diaper change"

Original issue: https://github.com/babybuddy/babybuddy/issues/651
My partner and I enjoy using your Android app in conjuction with the self-hosted Babybuddy software - thanks for offering this easy-to-use tool to record everything quickly while "in the midst of it". :sweat_smile:
After using the app for a couple of days, my partner was unable to save any diaper change on her Android phone (Huawai P30). We tried complete re-install and cache cleaning but the problem persists. (See attached screenshot) The other functionalities work for my partner.
On my Android phone the app works flawlessly and I can track everything.
Do you have any idea what might be the problem and/or a suggestion of what to try? :upside_down_face:
https://user-images.githubusercontent.com/10435455/242285339-3f095aa2-109d-4573-a150-86f2d912e200.jpg

Hi Paul,
This problem returned as well. No idea what caused this issue to resurface. 😓

Hi P9k,
That is unfortunate for you, but also kind of good for the app! - At least if you want to debug the issue still?
If you want to give the debug session a go, would you be so friendly and forward the Google account we want to do the debugging on one more time to my email address? I deleted your last email(s) to protect your privacy since we did not actually start the debugging session last time!


make elasticsearch support native query

rdbms and mongo support native query now, but elasticsearch not supported.
make  elasticsearch support native query. it's very useful.

Hi @dreamingo88
I am looking towards the opportunity to add support for Elasticsearch native queries in Kundera.
What kind of native queries do you want to perform using Kundera?
For example in MongoDB,  sample find query db.collection.find({ "AGE": { $gt: 12 } }) (which anybody can run on mongo shell) can be done using Kundera.
String test = "{ \"AGE\": { $gt: 12 } }";
List<PersonMongo> list = em.createNativeQuery(test, PersonMongo.class).getResultList();

It would be great if you share your usecase too.
-Dev

Hi, @devender-yadav
My mean is just like mongodb's NativeQuery.
String test = "{     "match" : {         "message" : "this is a test"     } }"
List list = em.createNativeQuery(test, PersonES.class).getResultList();
It's very important and helpful.
Thanks!

Hi @dreamingo88 ,
Thanks for the suggestion. We will look into it.
-Dev


Union and Interface-based error handling

I used Pothos on the TypeScript/Node.js side before and I really liked their error handling, which, for some query hello, basically created a schema that looks like this:
type Error {
  message: String!
}

type Query {
  hello(name: String!): QueryHelloResult
}

union QueryHelloResult = Error | QueryHelloSuccess

type QueryHelloSuccess {
  data: String!
}

and could be queried like this:
query {
  hello(name: "World") {
    __typename
    ... on Error {
      message
    }
    ... on QueryHelloSuccess {
      data
    }
  }
}

This basically forced the user to handle both the success case and the error case, or the query would fail. Is this something we could add for async-graphql too, particularly the part about having the user having to handle all cases in the query itself rather than detecting whether an errors field exists?
Another article about this method: https://blog.logrocket.com/handling-graphql-errors-like-a-champ-with-unions-and-interfaces/

Any thoughts on this style of error handling @sunli829? Personally I think it could be good to enforce error side type safety like this just like how Rust's Result type handles it, just on the client side. Pothos uses an error plugin that generates the necessary unions, perhaps we could use a macro to do this as well.

I really like this idea. Our current frontend is struggling with error handling because the errors aren't typed.
It would be nice if we have some way to enable unions within Results, basically a Result<Object, Error> could become an Union or a "flatten" Union = Object | Error

@gusinacio Indeed, currently I'm just generating all of the unions manually but it would be great to have an extension in async-graphql directly such as with a macro annotation.

I'm also struggling with this, since async_graphql only allows unit enums. Is there a reason behind this limitation? Right now enum-based results are not even possible due to this limitation:
enum QueryResult {
    InternalError,
    Success { value: String },
}

Is there a workaround to this?


[Identity] Swagger documentation

Summary****Summary
Swagger documentation should be provided for Identity API endpoints
Details
N/A
Acceptance criteria

[ ] Identity API module has its own Swagger documentation
[ ] Swagger version is updated to the latest one
[ ] Mandatory parameters are documented

Additional context

there are some swagger-related filed that can be used as a guideline (ex. account-service-rest-api.yaml)
swagger documentation should be configured using Java annotations

Clear description or/and business justification of what the task is about.
Details
If applicable, detailed information regarding things to be considered, requirements etc.
Acceptance criteria
Precise and detailed conditions under which the task is considered to be completed.
Additional context
Add any other context or screenshots about the task.

Done and merged to swagger branch


setters partial overriding

for example, we need to process a value after conversion. If we simply override setter, we would use this code:
def attrname=(x)
  super
  @x = process(@x)
end

It seems to be ugly for me, but idk how to improve it, maybe callback wich would redifine setter?
e.g.
after_convert(:attrname) do |x|
  process(x)
end

That seems like a bloat feature, we would also have to do before_convert, around_convert, etc.
Either override a getter or define a custom converter

both solutions are bad, i'll try to explain why

getters with caching (and i need it) are extremly bad. Obliviously, i don't want to split conversion logic, as a result i sould use a trivial setter without conversion. Another missed point is encapsulation of public interface in setter, which makes it easy to see. In my suggestion after_convert hook is placed in class header with other interface description
the idea of  converter defenition is not so bad as i thinked about it first time, but tainbox does not provide interface to simply do it (mostly inheritance, but also namespacing). Of course, placing class-specific converters into global namespace is a short way to hell, so i need to use something like :'class_name/field_name' and it is realy bad

I think you should go with a custom setter then


to pass the Web Server Debug Validation

This solves the Remote host is configured as 'localhost' despite server host is probably not local problem in the validator. See http://stackoverflow.com/a/36152477/721065
Forgive me if I didn't follow the editing procedure correctly 😬

Should this be set in default.config.yml maybe?

I think that makes sense, yes

Related https://github.com/geerlingguy/drupal-vm/issues/1171#issuecomment-287469544.
I remember <IP_ADDRESS> had a meaning in VM world but cant recall what right now. Does the hostname work just as well?

Not sure what the hostname would be but if it resolves to the 'host' michine or that ip it should work.

Ah, that makes sense that the vagrant_ip would work too. Not sure if one other is better.

Ah <IP_ADDRESS> points to the host machine (in some cases, this varies though). @cdmo but for you it works using the guest machine's hostname as well?

We use "php_xdebug_remote_host: <IP_ADDRESS>"

@oxyc yes, I have it pointing to vagrant_hostname and it works fine. In my case this happens to be ul.dev.  I added my documentation change just to PHPStorm. Not sure how this affects other IDEs. Hard-coding the private  IP address would work, but it should be the same as vagrant ip I would think.

Yeah, I usually use the hostname and it works okay on my Mac with Sublime Text. Of course IP would be slightly more consistent, but I like the hostname :)
I haven't tried with PHPStorm on my Mac yet (only Windows).

Should we just find the default gateway inside vagrant?  Something like one of these?
netstat -r |awk '$1=="default"{print $2}'
route -n | grep 'UG[ \t]' | awk '{print $2}'
ip route show default | awk '/default/ {print $3}

Derp sorry, mine is actually <IP_ADDRESS> as well! Here's some of the interesting ansible facts we can use as wlel.
drupalvm_project | SUCCESS => {
    "ansible_facts": {
        "ansible_all_ipv4_addresses": [
            "<IP_ADDRESS>",
            "<IP_ADDRESS>"
        ],
        "ansible_default_ipv4": {
            "address": "<IP_ADDRESS>",
            "alias": "enp0s3",
            "broadcast": "<IP_ADDRESS>",
            "gateway": "<IP_ADDRESS>",
            "interface": "enp0s3",
            "macaddress": "08:00:27:79:98:32",
            "mtu": 1500,
            "netmask": "<IP_ADDRESS>",
            "network": "<IP_ADDRESS>",
            "type": "ether"
        },
        "ansible_enp0s3": {
            "active": true,
            "device": "enp0s3",
            "features": {},
            "ipv4": {
                "address": "<IP_ADDRESS>",
                "broadcast": "<IP_ADDRESS>",
                "netmask": "<IP_ADDRESS>",
                "network": "<IP_ADDRESS>"
            },
            "ipv6": [
                {
                    "address": "fe80::a00:27ff:fe79:9832",
                    "prefix": "64",
                    "scope": "link"
                }
            ],
            "module": "e1000",
            "mtu": 1500,
            "pciid": "0000:00:03.0",
            "promisc": false,
            "speed": 1000,
            "type": "ether"
        },
        "ansible_enp0s8": {
            "active": true,
            "device": "enp0s8",
            "features": {},
            "ipv4": {
                "address": "<IP_ADDRESS>",
                "broadcast": "<IP_ADDRESS>",
                "netmask": "<IP_ADDRESS>",
                "network": "<IP_ADDRESS>"
            },
            "ipv6": [
                {
                    "address": "fe80::a00:27ff:fe3d:5c2b",
                    "prefix": "64",
                    "scope": "link"
                }
            ],
            "module": "e1000",
            "mtu": 1500,
            "pciid": "0000:00:08.0",
            "promisc": false,
            "speed": 1000,
            "type": "ether"
        },
        "ansible_interfaces": [
            "lo",
            "enp0s3",
            "enp0s8"
        ],
    },
    "changed": false
}

@oxyc I get  {{ ansible_default_ipv4.gateway }} == <IP_ADDRESS>  too.
This is going to save me heaps of time with xdebug CLI setup 😄

@thom8 @oxyc I just used this in my config.yml:
php_xdebug_remote_host: "{{ ansible_default_ipv4.gateway }}"
And, voila, it worked. Passed the "Web Server Debug Validation" thing too. So, it probably makes more sense to make this part of the default.config.yml file.

@cdmo - In that case, can you update the PR and I'll go ahead and merge it?

Heh... all that for one line changed code :)

This is how the sausage of open source is made. Ain't pretty I guess ;) Thanks.

This should be good to merge no? Beetbox did already.

Heh, yes. It just slipped under the radar. I love how the PR ended up having 30+ comments and a few rewrites... and in the end it's a one line change 😆


Dad Jokes Project

Project title
Dad Jokes Project
Project Description
Fetches jokes with api in js.
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript
[ ] ReactJS

/assign


Send DB request stats

Send a count metric for every DB request. This helps to figure out what data sets are completely unused, and should probably be deleted.

This only sends aggregate data every minute, so it's not a high load on sequins or DataDog
In contrast to expvar metrics:

These are typed as RATE, so they can be safely summed over time
These aren't lossy—even a single request to a DB will be caught

I feel like, if we haven't, we should check with #observability to see what they think about the count batching. If I understand correctly, datadog/veneur already sends metrics upstream on an interval instead of real time. And since the communication to the agent is local I wouldn't imagine it's a terribly large burden on Sequins. Otherwise, this LGTM.

This is the approach OBS recommended when I asked them on Friday :)


Included Pages XMP Markup causes "Update Preview" loop

When a component in a included page is updated within the including page using XPM, and its respective page (included page) is not published afterwards, The "Update Sesssion Preview" button remains active and XPM asks for the update.
I think this has to do with the Component Presentations of the included pages not living withing the Including page itself, hence XPM cannot render the them with the latest version of either the component or component template

This is indeed a known side effect of the include pages being editable inside the actual page. Which is also why we added the edit icon on the include pages, so that you can click that and open the include page itself (making it fully editable), after which you can uatomatically get it publishe by pressing the Finish Editing button. And then you can easily go back to your original page with the back icon on the inlude page.
Since this issue is related to XPM behavior, I'm labeling it currently as won't fix, but I will make sure we discuss it as part of XPM and see if we can put better support for these scenarios in the product.


404 logic change

It seems like https://github.com/azu/can-npm-publish/commit/7967d92 changed the way 404s are treated.
For node 12 and 1.3.4 the exist code is 1 and npm ERR! code E404 is printed to the terminal
For node 14 and 1.3.4 the exist code is 1 and npm ERR! code E404 is printed to the terminal
For node 16 and 1.3.4 the exist code is 1 and npm ERR! code E404 is printed to the terminal
For node 12 and 1.3.3 things are all good
For node 14 and 1.3.3 things are all good
For node 16 and 1.3.3 can-npm-publish/lib/can-npm-publish.js:68:37 throws an Unexpected end of JSON input/undefined error

Here is my output for node 16 and 1.3.4:
> nvm use 16
Now using node v16.4.0 (npm v7.18.1)
> npx<EMAIL_ADDRESS>--verbose
npm ERR! code E404
npm ERR! 404 Not Found - GET https://mycompany.com/api/npm/npm/@scoped%2fpkgname- not_found
npm ERR! 404
npm ERR! 404  '@scoped/pkgname@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
{
  "error": {
    "code": "E404",
    "summary": "Not Found - GET https://mycompany.com/api/npm/npm/@scoped%2fpkgname- not_found",
    "detail": "\n '@scoped/pkgname@latest' is not in the npm registry.\nYou should bug the author to publish it (or use the name yourself!)\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
  }
}

npm ERR!      /Users/me/.npm/_logs/2021-06-23T17_27_52_658Z-debug.log

> echo $status
1

https://github.com/azu/can-npm-publish/pull/18/files#r649639587
Maybe, this change relates

npm 7 has a bug…
npm 7
❯ npm -v
7.18.1

~/.ghq/github.com/azu/can-npm-publish master*
❯ npm view not_found_package_123 --json 2>stderr.log 1>stdout.log

~/.ghq/github.com/azu/can-npm-publish master*
❯ cat stdout.log

~/.ghq/github.com/azu/can-npm-publish master*
❯ cat stderr.log
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/not_found_package_123 - Not found
npm ERR! 404
npm ERR! 404  'not_found_package_123@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
{
  "error": {
    "code": "E404",
    "summary": "Not Found - GET https://registry.npmjs.org/not_found_package_123 - Not found",
    "detail": "\n 'not_found_package_123@latest' is not in the npm registry.\nYou should bug the author to publish it (or use the name yourself!)\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
  }
}

npm ERR!      /Users/azu/.npm/_logs/2021-06-23T23_35_58_106Z-debug.log

npm 6
~/.ghq/github.com/azu/can-npm-publish master*
❯ npm -v
6.14.13

~/.ghq/github.com/azu/can-npm-publish master*
❯ npm view not_found_package_123 --json 2>stderr.log 1>stdout.log

~/.ghq/github.com/azu/can-npm-publish master*
❯ cat stdout.log
{
  "error": {
    "code": "E404",
    "summary": "'not_found_package_123' is not in the npm registry.\nYou should bug the author to publish it\n(or use the name yourself!)\n\nNote that you can also install from a\ntarball, folder, http url, or git url.",
    "detail": "\n 'not_found_package_123@latest' is not in the npm registry.\nYou should bug the author to publish it (or use the name yourself!)\n\nNote that you can also install from a\ntarball, folder, http url, or git url."
  }
}

~/.ghq/github.com/azu/can-npm-publish master*
❯ cat stderr.log
npm ERR! code E404
npm ERR! 404 'not_found_package_123' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404 (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! 404
npm ERR! 404  'not_found_package_123@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR!      /Users/azu/.npm/_logs/2021-06-23T23_36_48_205Z-debug.log

Related issues:

[BUG] npm view --json sompackage dist-tags has invalid json · Issue #3075 · npm/cli
[BUG] npm view --json outputs illegal JSON for existing package but non-existent version · Issue #3184 · npm/cli
[BUG] NPM 7.x broke the "--json" CLI parameter · Issue #2740 · npm/cli

I've fixed this error in #20
Please try https://github.com/azu/can-npm-publish/releases/tag/v1.3.5


Consider goreleaser for release automation

This is superseded by #24 since it'll probably be easier to use GitHub actions for this.


Allow to customise the "Need Help?" link from an archive's metadata

See https://github.com/resin-io-modules/etcher-image-stream/pull/28

See https://github.com/resin-io-modules/etcher-image-stream/pull/28


ClaimTrieSync looks at relation which is not set correctly to determine if claim is spent

[x] When processing an input and setting the relation to the spent output this needs to be marked valid otherwise the ORM will not save the change. 5cd411acb603806156b1ea5904b406853dea38de

[x] We need an upgrade script to reset all the claims that are considered spent. bfe0b2736eca20c34922fe4307c66754e5bccabb

I was able to add a sync to the claimtriesync job that handles this without a script.


Add resourcequota config

This adds the support to generate resourcequota configuration reference. We also prefer the GroupName used over the 'groupName' comment which sometimes deviates from the implementation.
related: https://github.com/kubernetes/website/pull/26820

Holding this pending #176
/hold
/approve cancel

/approve

/lgtm


Broken links to demos

Hi,
The links to the demos, on README file, are broken (except the Quickstart Welcome).
Where this happens -> line 33

Thanks for this valuable comment! All links are fixed now!


fix: Fix panic in avg aggregate and disable stddev by default

Which issue does this PR close?

Closes https://github.com/apache/datafusion-comet/issues/817
Related to https://github.com/apache/datafusion-comet/issues/824
Rationale for this change

Bug fix
q39 is the worst performing TPC-DS query compared to Spark (25-30 seconds compared to 9 seconds with Spark) and much of that time is because our implementation of stddev is slower than Spark. Disabling this aggregate provides a 2x speedup for the query (14 seconds) and helps our overall TPC-DS number.

What changes are included in this PR?

How are these changes tested?

Thanks for the review @huaxingao


Fix queue worker incorrectly stopped when there are still more items in the queue

Without case <-t.C, the workers would stop incorrectly, the test won't pass. For the worst case, there might be only one running worker processing the queue items for long time because other workers are stopped. Thanks to oliverpool for looking into the problem and proposing a fix.
Actually, the real problem is not completely fixed, the root cause is not directly related to the ticker, but is related to the logic of doDispatchBatchToWorker. It isn't a serious problem at the moment, so keep it as-is. More comments are added.

@oliverpool  I see you said you feel "sad" about there is no "@" ping here.
But actually, when I worked with some people from your fork, they said "don't bother me". So, that's really difficult to work with the people from the fork:

Sometimes: "Oh, don't ping me"
Sometimes: "Oh, they don't ping me"

And as I said in the description, thank you for looking into the problem, but your fix is not a complete one (neither this PR is). The root problem is the data-race between doDispatchBatchToWorker and workerNum. Maybe you could try to think about a complete solution (no need to thank to me for sharing the idea, feel free to do what you like)


Add base for es2019 and add Intl.getCanonicalLocales method

This adds base for ES2019 and adds Intl.getCanonicalLocales method as defined here:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/getCanonicalLocales
https://tc39.github.io/ecma402/#sec-intl.getcanonicallocales

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

this should be esnext.intl untill es2019 is ratified. also please file an issue to track the change.


feat: add video samples to notebook

Added human fall video samples to the existing notebook.
Here is the link to access the notebook. link

View / edit / reply to this conversation on ReviewNB
ivelin commented on 2021-09-02T16:27:15Z
bhavikapanara This sequence also misses the frames with the person actually fallen on the floor. Can you check why that is the case and add them to the detection samples.

Actually, I am skipping few frames because it is complicated to show all frames

I think it's reasonable to take snapshots once a second (1fps). That is how
we implement it in production relying on the fact that falls take between
600-800ms. this should be sufficient to capture all before and after fall
scenes.
On Fri, Sep 3, 2021 at 11:46 PM bhavika panara @.***>
wrote:

View / edit / reply to this conversation
https://app.reviewnb.com/ambianic/fall-detection/pull/22/discussion/ on
ReviewNB
ivelin commented on 2021-09-02T16:27:15Z bhavikapanara
https://github.com/bhavikapanara This sequence also misses the frames
with the person actually fallen on the floor. Can you check why that is the
case and add them to the detection samples.
Actually, I am skipping few frames because it is complicated to show all
frames
[image: image]
https://user-images.githubusercontent.com/19815572/132082709-b2593118-2f06-49ef-95ed-40a33a829098.png
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ambianic/fall-detection/pull/22#issuecomment-912906764,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARBUFLOA6BMOE4ZF6OEG73UAGQD5ANCNFSM5DJAOSFQ
.

I think it's reasonable to take snapshots once a second (1fps). That is how we implement it in production relying on the fact that falls take between 600-800ms. this should be sufficient to capture all before and after fall scenes.
…
On Fri, Sep 3, 2021 at 11:46 PM bhavika panara @.***> wrote: View / edit / reply to this conversation https://app.reviewnb.com/ambianic/fall-detection/pull/22/discussion/ on ReviewNB ivelin commented on 2021-09-02T16:27:15Z bhavikapanara https://github.com/bhavikapanara This sequence also misses the frames with the person actually fallen on the floor. Can you check why that is the case and add them to the detection samples. Actually, I am skipping few frames because it is complicated to show all frames [image: image] https://user-images.githubusercontent.com/19815572/132082709-b2593118-2f06-49ef-95ed-40a33a829098.png — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARBUFLOA6BMOE4ZF6OEG73UAGQD5ANCNFSM5DJAOSFQ .

@ivelin  Please see the updated notebook

@bhavikapanara Thank you for adding all important frames in the videos with before and after poses. Can you please print the confidence scores for keypoints under each detection frame as you did for the individual photos in this notebook.
Thank you!
View entire conversation on ReviewNB

@ivelin Please review the updated notebook


change webhook url

I want to set webhook url depending on rcptTo address
I'm starting mailin from app.js:
mailin.start({
  webhook: 'http://mydomain.com/mailin/incoming,
  disableWebhook: false
});

Can I change webhook url smth like this?
mailin.on('startMessage', function (connection) {
   if (connection.envelope.rcptTo[0].address ==<EMAIL_ADDRESS>{
     url = "http://host/ur1.php";
   } else if (connection.envelope.rcptTo[0].address ==<EMAIL_ADDRESS>{
     url = "http://host/ur2.php";
   }
}

Thanks

No, this won't work if you receive multiple emails simultaneously. However, since you can listen to the message event and post the webhook yourself to the correct url. Have a look to the mailin:postWebhook method to see how you can do that.

Thank you. Exactly what is needed


Change: use X instead of Space for toggle prioritization

This pull request remaps the Toggle command in Select priorities tab to X instead of Space, to ensure consistency between the main to-do tab and the Select priorities tab

this is a good observation, but wouldn't it be more convenient to make this customizable in config.lua?

that would probably be better for sure, but I think they should be the same by default.

@atiladefreitas  How about now?


Error customization

Hi.
Consider the following example:
package main

import "github.com/integrii/flaggy"

func main() {
	// Declare variables and their defaults
	var stringFlag = "defaultValue"

	// Create the subcommand
	subcommand := flaggy.NewSubcommand("subcommandExample")

	// Add a flag to the subcommand
	subcommand.String(&stringFlag, "f", "flag", "A test string flag")

	// Add the subcommand to the parser at position 1
	flaggy.AttachSubcommand(subcommand, 1)

	// Parse the subcommand and all flags
	flaggy.Parse()

	// Use the flag
	println(stringFlag)
}

when calling this by % ./main -f a, it shows the following error:
mymain

  Usage:
    mymain [subcommandExample]

  Subcommands:
    subcommandExample

  Flags:
       --version   Displays the program version string.
    -h --help      Displays help with available flag, subcommand, and positional value parameters.

Unknown arguments supplied:  f a

so, is there any option to show the error as Unknown arguments supplied: -f a instead of Unknown arguments supplied:  f a? I.e, replacing the empty space before   f by the - symbol.
Edit: the same for Expected a following arg for flag f, but it did not exist, it would be nice an option to show Expected a following arg for flag -f, but it did not exist instead, and Expected a following arg for flag --flag, but it did not exist instead of Expected a following arg for flag flag, but it did not exist, and so on.
TIA

it should be called like this: ./main f <value>, if you want a flag, try
flaggy.String(&stringFlag, "f", "flong", "desc")


add unit test for RemoteTaskActionClientTest

@zhxiaogg thanks for the PR!
Overall it looks good aside from some basic bookkeeping stuff:

There needs to be a license at the top of the file
The code needs formatted in accordance with https://github.com/druid-io/druid/blob/master/CONTRIBUTING.md
We need a CLA from http://druid.io/community/cla.html

hi @drcrallen ,
License added.
I'm sure I used the eclipse_formatting.xml found in the root path. Do I have to use the intellij one?
And you are quick, thanks!

@zhxiaogg I try to set aside time every day to make sure community contributed PRs get addressed in a timely manner, you happened to catch me in the middle of that time :)
Looks like the eclipse formatting might be way out of date. We've been using the intellij one.

Sorry for the confusion. If you cannot use the Intellij one let me know and I can submit a PR to your branch with the formatting.

@drcrallen  wait a second and I'll use intellij to reformat the code.

cool, @zhxiaogg can you squash your commits and it should be good at that point
:+1: after squash and travis

@drcrallen and @gianm  forgive me for my mistaken. License updated and commits rebased.

:+1: after squash, travis. Thanks @zhxiaogg!


[e2e]: generic workflow_dispatch main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8353237062
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Mar 20 03:07:43 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8364990295
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.default.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Wed Mar 20 19:56:33 UTC 2024
Tests are passing now. Closing this issue.


add target model's database

resolves #
This is a:

[ ] documentation update
[x] bug fix with no breaking changes
[ ] new functionality
[ ] a breaking change

All pull requests from community contributors should target the main branch (default).
Description & motivation
This package has a bug in the sense that it assumes the database used for materializing the models is the database defined in the profile file. This is not the case for us as we override the macros generate_database_name and generate_schema_name.
Change to be done (might be additional changes to be done):

dbt-model-usage/macros/common/generate_create_logs_query.sql
Line 40:
{{ target_model.schema }}.INFORMATION_SCHEMA.TABLES
should be:
{{ target_model.database }}.{{ target_model.schema }}.INFORMATION_SCHEMA.TABLES

Checklist

[ ] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[x] BigQuery
[ ] Postgres
[ ] Redshift
[ ] Snowflake

[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)

thanks @nhnam1105 -- can you please follow CircleCI's instructions below (unfollow your forked project in CircleCI and follow the source project) so a CI pipeline can be triggered?
https://circleci.com/docs/oss/#build-pull-requests-from-forked-repositories

Hey @rjh336, thanks for your response, I was able to trigger the CI pipeline. Can you please guide me the next step? Do I need to fill in the .env.sample file my bigquery variables in order to get the integration tests done since the CI logs indicated that the env var not provided?

@nhnam1105 sorry that was a missing circleci configuration on my end which I added. Try rerunning your CI job


support future and past dates and datetimes

fix #229

Codecov Report

Merging #295 (149f524) into main (800114b) will decrease coverage by 0.07%.
The diff coverage is 91.58%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #295      +/-   ##
==========================================
- Coverage   97.52%   97.44%   -0.08%
==========================================
  Files          54       54
  Lines        6131     6214      +83
  Branches       44       44
==========================================
+ Hits         5979     6055      +76
- Misses        152      159       +7

Impacted Files
Coverage Δ

src/errors/kinds.rs
78.24% <ø> (ø)

src/validators/date.rs
95.00% <89.65%> (-1.35%)
:arrow_down:

src/validators/datetime.rs
94.11% <90.47%> (-3.89%)
:arrow_down:

pydantic_core/core_schema.py
100.00% <100.00%> (ø)

src/input/datetime.rs
97.90% <100.00%> (+0.05%)
:arrow_up:

src/input/input_python.rs
98.54% <100.00%> (+<0.01%)
: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 800114b...149f524. Read the comment docs.


make build_docs fails

with the following message:
(ipythondev)m300028@alexnotebook:pycmbs$ make build_docs
python setup.py build_sphinx
running build_sphinx
Running Sphinx v1.2b3
/home/m300028/virtualenvs/ipythondev/local/lib/python2.7/site-packages/matplotlib-1.4.x-py2.7-linux-x86_64.egg/matplotlib/cbook.py:126: MatplotlibDeprecationWarning:
The Sphinx extension ipython_console_highlighting has moved from
matplotlib to IPython, and its use in matplotlib is deprecated.
Change your import from 'matplotlib.sphinxext.ipython_directive' to
'IPython.sphinxext.ipython_directive.
warnings.warn(message, mplDeprecation, stacklevel=1)
Traceback (most recent call last):
File "setup.py", line 37, in
license="MIT license")
File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "/usr/local/lib/python2.7/dist-packages/sphinx/setup_command.py", line 143, in run
freshenv=self.fresh_env)
File "/usr/local/lib/python2.7/dist-packages/sphinx/application.py", line 119, in init
self.setup_extension(extension)
File "/usr/local/lib/python2.7/dist-packages/sphinx/application.py", line 283, in setup_extension
mod = import(extension, None, None, ['setup'])
File "/home/m300028/virtualenvs/ipythondev/local/lib/python2.7/site-packages/matplotlib-1.4.x-py2.7-linux-x86_64.egg/matplotlib/sphinxext/ipython_directive.py", line 534, in
class IpythonDirective(Directive):
File "/home/m300028/virtualenvs/ipythondev/local/lib/python2.7/site-packages/matplotlib-1.4.x-py2.7-linux-x86_64.egg/matplotlib/sphinxext/ipython_directive.py", line 546, in IpythonDirective
shell = EmbeddedSphinxShell()
File "/home/m300028/virtualenvs/ipythondev/local/lib/python2.7/site-packages/matplotlib-1.4.x-py2.7-linux-x86_64.egg/matplotlib/sphinxext/ipython_directive.py", line 208, in init
self.cout = io.StringIO()
AttributeError: 'module' object has no attribute 'StringIO'
make: *** [build_docs] Error 1

Has been fixed by removin dependency on matplotlib extensions.


Preprint with status in extra fails to export

Debug log ID
8PKJSPS3-apse/6.7.192-6
What happened?
"File" > "Export Library . . . " > Select Better BibLaTeX and "keep updated" > Press "OK" >  Choose file > "An error occurred while trying to export the selected file".
There is a bibtex file generated and kept updated by BBT in the same folder, which is kept updated.  But, I no longer be able to generate a biblatex file.
Before this happened, I had noticed that the biblatex file hadn't been updated. I went to the BBT preferences, selected the biblatex file and pressed the "Update Now" button but the file wasn't updated. I repeated this a few times but the file wasn't updated.  So, I deleted the file and pressed the "Update Now" but the file wasn't generated. I then restarted Zotero and did the same but the file wasn't generated.

Can you select the auto-export library/collection (whichever it ends up being), right-click it, and send a debug log from that? It will have an ID with -refs- in it.

Thank you as always for your prompt help, but

Can you select the auto-export library/collection (whichever it is in your case), right-click it, and send a debug log from that?

I'm sorry that I can't figure out exactly what I'm supposed to do.  Can you break it down to a step-by-step set of instructions?  I repeated the procedure I described in my initial report, but I didn't know where, when, or what to right-click.

Oh I see you only have library auto-exports set up. Just right-click your library in the top left, select Better BibTeX -> Send debug log.

HZ8H8PJX-refs-apse/<IP_ADDRESS>81.6262-6

Just right-click your library in the top left, select Better BibTeX -> Send debug log.

The above log ID is the result of that.  I hope it helps.
In the meanwhile, the test build <IP_ADDRESS>81.6262 seems to have solved my original problem. I can now generate biblatex files.

I, too, cannot export to Better BibTeX anymore: debug log ID: AAS9D6Q2-euc/6.7.192-6.
"File" > "Export Library . . . " > Select Better BibLaTeX > Press "OK" > Choose file > "An error occurred while trying to export the selected file".
File is created with size 0.

@Baumtomographie please right-click the problematic items and send a debug log from the popup menu. The ID will have -refs in it.

The errors I get are:
"[JavaScript Error: "TypeError: library.waitForDataLoad is not a function" {file: "chrome://zotero/content/contextPane.js" line: 883}]
[JavaScript Error: "out of memory"]
[JavaScript Error: "out of memory"]
[JavaScript Error: "XML Parsing Error: no root element found
Location: https://s3.eu-central-1.amazonaws.com/ping
Line Number 1, Column 1:" {file: "https://s3.eu-central-1.amazonaws.com/ping" line: 1}]
[JavaScript Error: "XML Parsing Error: no root element found
Location: https://s3.ap-southeast-1.amazonaws.com/ping
Line Number 1, Column 1:" {file: "https://s3.ap-southeast-1.amazonaws.com/ping" line: 1}]
[JavaScript Error: "out of memory"]
[JavaScript Error: "out of memory"]"
I'm sorry, but I don't know where to find these "problematic items". The bib-file is empty.

Just select your library, right-click it, and send a debug log from the popup menu. But you may be suffering #2315.

@ryofurue there's still a bug (pubstate has the wrong value), a new version will drop soon that addresses it. Can you do me a favor? Can you export the item titled

Comparing the linear and nonlinear buoyancy-driven circulation

to "BetterBibTeX JSON" and "Zotero RDF", zip them up, and attach the zip here?

The debug log is empty, so there is no send option available.

Can you show a screenshot from that? The debug log is never empty, because I always add my own information to the top.

But have you disabled the cache as described in #2315?

@ryofurue there's still a bug (pubstate has the wrong value), a new version will drop soon that addresses it. Can you do me a favor? Can you export the item titled

Comparing the linear and nonlinear buoyancy-driven circulation

to "BetterBibTeX JSON" and "Zotero RDF", zip them up, and attach the zip here?

Here it is.
comparing-linear-and-nonlinear.zip
But these files were generated on a different machine from the one I made my initial report on.  My Zotero databases are sync'ed across all my machines, though.

Ah no I need it from the system you sent the debug logs from. The bug is fixed, but the debig log had the attached files in a text encoding I didn't expect. I want to see whether that's something my debug log does, or whether it's something zotero does. But that is system bound.
Or maybe it occurs on both systems. Can you also send a debug log for that item on the system you exported these zipped files from?

It shouldn't be happening at all, and I've had an Intel Mac, now have an m2 Mac, and I've never been able to replicate it. What locale are your machines configured for?

Thanks. The exports are OK, so that means I'm mutilating the debug log myself. DQWXFMSK-refs-apse/6.7.192-6 has the same issue, and the files in the zipfile are OK. I'll look into this separately -- for now, the problem we started with is solved. I'll cut a new release, you'll be upgraded automatically.

@Baumtomographie I can't move forward on your case without more input.

What locale are your machines configured for?

I'm curious myself!  I migrated from Linux to Mac more than 10 years ago. When I was using Linux, I roughly knew how system locale was set (/etc/ . . . ) and how the user overrides it.
Internally, Macs should be the same, but I've never looked into it.  You just open the shiny white box of your new Mac machine, switch it on, and answer several questions.  Then, you are good to go.  During this setup, I just choose "English (US)".
For my command shell, I set
LC_ALL="en_US.UTF-8"
LC_COLLATE="C"
but I don't think these would affect Zotero because I launch Zotero by double-clicking on it from "Applications" on Finder.
If you (we) are suffering from some weird character coding, does it come from the Zotero browser plugin or from the webbrowser or from the publisher who provides the metadata?

I don't think it's a encoding problem anymore, your files showed that. I have a fix lined up but I'm going to be tied up for a few more hours - I'd hugely appreciate it if you could test it when I have it done.

Yeah, got it, I was mutilating the logs. That's fixed now -- thanks for the help

@Baumtomographie please open a new issue for the problem you are experiencing.

When I launched Zotero ten minutes ago, BBT was updated, and I restarted Zotero.  I then went to the BBT preferences and pressed the "Export now" button. The biblatex file was renewed.  So everything seems to be working normally.


HTTP Client – Subscribe doesn't work for production serve/build

Versions
   / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
  / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
 / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
/_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
               |___/

Angular CLI: 1.6.4
Node: 8.1.0
OS: darwin x64
Angular: 5.2.0
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

@angular/cli: 1.6.4
@angular-devkit/build-optimizer: 0.0.38
@angular-devkit/core: 0.0.25
@angular-devkit/schematics: 0.0.46
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.4
@schematics/angular: 0.1.13
@schematics/schematics: 0.0.13
typescript: 2.6.2
webpack: 3.10.0

Repro steps
Just write a method in any of your service and make an HTTP call in it and subscribe to the result
Observed behavior
HTTP calls are working fine when I build or serve normally
ng build
ng serve

But when I serve them for production, HTTP calls are not being made
ng serve --prod
ng build --prod

Desired behavior
HTTP calls should work fine for production build as they are working for the normal build
Update
I just tried with AOT disabled and it seems to be working without it
ng serve --prod --aot=false
ng build --prod --aot=false

Any idea why AOT is not working?

I upgraded the cli to version 1.7.0 and it seems to be working now


set up eslint and auto lint on save for vscode

Description
Added eslint for frontend and backend. Will autolint on save for vscode if the eslint extension is installed. I think for webstorm, you just need to change a settings and it will autofix as well.
Added following dependencies for eslint:
- typescript-eslint/eslint-plugin": ^5.50.0
- eslint: ^8.0.1
- eslint-config-standard-with-typescript: ^35.0.0
- eslint-plugin-import: ^2.25.2
- eslint-plugin-n: ^15.0.0
- eslint-plugin-promise: ^6.0.0
- eslint-plugin-react": ^7.32.2
- eslint-config-prettier: ^8.8.0
Type of Change
Setup Change

I think u have the .vscode file added which we don't wanna push to git. It's on the personal end. As far as I gathered at least


Add a smoke test runner to dev-tools

This was fun to write, but given how its significantly more complex than I'd wish I wouldn't be surprised if there were bugs (but it doesn't need to be perfect to be useful, it's stochastic by design).
I've been running this in 'infinite' mode on one of my cores for 24hrs+ (and found #5393 and #5399). The idea is that before restarting the server, admins should run node dev-tools/smoke 5 or whatever and wait maybe 5 minutes as insurance against obvious crashes that would force a restart again anyway.

Unfortunately, I don't think this will catch most bugs. Very few bugs are actually crashes; they're usually just incorrect mechanics.
Actual integration tests would probably also be nice. Maybe a ./pokemon-showdown --no-fs-writing mode, which also listens on a nonstandard port, so it can't screw with an actively-running server.

Unfortunately, I don't think this will catch most bugs. Very few bugs are actually crashes; they're usually just incorrect mechanics.

Correct, this will 'only' catch crashes and protocol issues, like the 2 its already caught. That's more than nothing.

Actual integration tests would probably also be nice. Maybe a ./pokemon-showdown --no-fs-writing mode, which also listens on a nonstandard port, so it can't screw with an actively-running server.

This is also on my TODO list, these smoke tests do not preclude more integration tests.

Oh, yeah, I wasn't saying otherwise. That was just a somewhat-related thought.

I don't think this will catch most bugs.

Incidentally, if this were landed and @Marty-D had run this before /hotpatch formats, the latest TypeError: move.getHitData is not a function crash would have been caught. (caught within 30s of running on my machine) :)

At some point I'd like documentation on what the difference is between the harness and this, because they seem to do the same thing (run battles randomly and report the errors that result).
But you sound antsy. Nothing's blocking this, if you want to merge and figure out the rest later.

At some point I'd like documentation on what the difference is between the harness and this, because they seem to do the same thing (run battles randomly and report the errors that result).

Well, the smoke test runner builds on top of the harness, as does my forthcoming benchmarking and profiling logic (which will probably be added to harness instead of its own file). I imagine I'll probably build more things on top of the harness as well in the future. Logically it's all the same shit, they could all be in one monolithic file, but I don't think thats as maintainable, and the Pool/TeamGenerator/CoordinatedPlayerAI logic was distinct enough from the stuff in harness.js that it seemed like it could be a separate thing. PS seems to like monolithic files.

But you sound antsy. Nothing's blocking this, if you want to merge and figure out the rest later.

I'm only antsy because I find it really useful (I've been running it against all my recent changes and its saved me several times when the npm run test suite passed and missed bugs) and I'd like others to be able to use it. :)

Well, the smoke test runner builds on top of the harness, as does my forthcoming benchmarking and profiling logic (which will probably be added to harness instead of its own file). I imagine I'll probably build more things on top of the harness as well in the future. Logically it's all the same shit, they could all be in one monolithic file, but I don't think thats as maintainable, and the Pool/TeamGenerator/CoordinatedPlayerAI logic was distinct enough from the stuff in harness.js that it seemed like it could be a separate thing. PS seems to like monolithic files.

I do prefer files being separate. It's just that I'd like the line separating them to be sensible, which is important because I want developers to be able to know what file the thing they want to change is in. PS has monolithic files because it often isn't clear to me what the best way to separate them is.
In this case, I don't understand what the line is between a "harness" and a "smoke test", especially since HARNESS.md says "run 100 random battles and report any errors that occurred" and "the number of battles run can be configured" – which seems identical to your documentation of the smoke test runner?

I'm only antsy because I find it really useful (I've been running it against all my recent changes and its saved me several times when the npm run test suite passed and missed bugs) and I'd like others to be able to use it. :)

I'm not opposed to you squash-merging this whenever you personally feel it's ready.

PS has monolithic files because I procrastinate figuring out the best way to separate them.

Perfect is the enemy of the good. Nothing is set in stone, you can always reorganize at a later time if the original separation wasn't correct.

In this case, I don't understand what the line is between a "harness" and a "smoke test"

harness.js is poorly named, the relevant classes are Runner, MultiRunner and SmokeRunner.
All are test harnesses. Runner runs a single battle. MultiRunner runs many. SmokeRunner also runs many but with coordination instead of purely randomly, but there still should be room to somehow better merge these two. I think the main problem though is the harness.js vs. smoke.js file names - running node harness.js 100 runs 100 random battles which could also smoke out crashes/be described as a smoke test, its just less thorough/exhaustive than smoke.js.
Improving the organization/naming/documentation here is a goal of mine, but I don't know the answer just yet, I figure these things out of time. I keep adding crap to these (like for testing #5270), so I'm going to be forced to rethink the design to make things more maintainable and intuitive in the long run.

Perfect is the enemy of the good. Nothing is set in stone, you can always reorganize at a later time if the original separation wasn't correct.

On the other hand, nothing is set in stone, you can always split the monolithic files into smaller files later.
In the meantime, I like filenames that make sense. ;)


add cob4-13 cardiff

preparing the bringup launch and yaml file structure
merge together with

https://github.com/ipa320/cob_supported_robots/pull/16
https://github.com/ipa320/cob_calibration_data/pull/147

there will be another set of PRs when HW is set into service

we'll merge for now and open another PR as soon as the arms are available


Add FAQ entry for Marionette.inspector

Mention how you use the Chrome Extension marionette.inspector in a Maji App.
Reported by @kjwierenga

Please review :)

Looks good to me, useful extension :-)


GMS and Conscrypt don't negotiate HTTP/2 on Android 10+ and 3.12.x

From https://github.com/square/okhttp/issues/5879
3.12.9 added Android10Platform which IIRC we did to avoid issues with graylisted (and eventually blacklisted in 11) APIs via Reflection. So we backported it from 4.x.
c2e9ee2#diff-55fc33d7feaf12483a0809e1db851f58

We can fix in one of two ways

Backport all of SocketAdapter from 4.4 kotlin to 3.12 Java
Bump the Android10 check to Android 11+, but will still fail on Android 11

I'm going to close in a week unless we decide to support.  It is working with security on older Android, just not with Android 10+.  I don't personally view this as a critical security fix.
Workaround for app developers is an app bundle with older features for < Android 5.
https://developer.android.com/google/play/publishing/multiple-apks

I think HTTP/1 is fine for Android 10+ on OkHttp 3.12.x.


Failure to detect Ruby app from the Buildpacks sample directory

What happened?

I tried to build a ruby app with the base (paketobuildpacks/builder:base) and full (paketobuildpacks/builder:full) builder but they couldn't detect the app, and thus nothing was built. I'm using the sample app in the buildpacks sample repo. However, when I switch to Heroku buildpacks or the CNB ones, it was able to detect and build the app.

What were you attempting to do?

Build a Ruby app

What did you expect to happen?

Detect the app and package it.

What was the actual behavior? Please provide log output, if possible.

===> DETECTING
ERROR: No buildpack groups passed detection.
ERROR: Please check that you are running against the correct path.
ERROR: failed to detect: no buildpacks participating

Build Configuration

What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
using? Please include a version.

Tekton

What buildpacks are you using? Please include versions.

What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?

paketobuildpacks/builder:base and paketobuildpacks/builder:full

Can you provide a sample app or relevant configuration (buildpack.yml,
nginx.conf, etc.)?

https://github.com/buildpacks/samples/tree/main/apps/ruby-bundler

@ryanmoran I'm happy to take a look at implementing some improved detect logic here, but I don't have enough context on the ruby ecosystem to form opinions on what special files the ruby buildpack might look for, and, perhaps more importantly, how we might validate the contents of those special files.
It is also not obvious to me where that logic would live, as there is no "ruby-start" buildpack similar to the node/python ecosystems. It doesn't seem like this logic should live in the rackup buildpack, either. We could create a ruby-start buildpack, but even if we did, I am not sure that buildpack should create a bundle exec ruby <some-special-file> command, as that seems quite coupled to the bundler order group.
@pmbanugo I see your 👍 on the comment above. Do you have thoughts on what a solution might look like, and what special files might the ruby buildpack look for? No worries if not - I'm just seeking any and all input possible!


Custom scoped functions

Description
Built-in functions can be scoped, e.g. dots.c, docts.l. According to the documentation it is currently not possible to define own scoped functions.
Use Case
Same use case as for built-in functions. In fact, it is currently not possible to provide an interface to custom functions that mimics the Typst interface.
For example, if one wants to introduce abbreviations for the space of continuous or smooth functions one cannot use functions.cont and functions.smooth.

dots isn't a function, but rather a symbol. You can define your own symbols with the symbol constructor.
Beyond that you can put definitions into a module (requires a separate file) or dictionary (no separate file, but cannot call functions directly without extra parentheses) to scope them.
The one thing that isn't possible for users is for functions itself to also be a function.


Attempt to make matrix build for root, since some versions of root ar…

…en't usable.

Checklist

[x ] Used a personal fork of the feedstock to propose changes
[x ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

This lets us move forward with the CDS environment by not moving forward with root.


Complex number representation in YAML

The standard defines the YAML complex number representation to be of the form 1+2i, without surrounding parentheses. The test file complex.yaml surrounds some complex numbers with parentheses. Which is correct?
I also see that the regex given in the standard does not allow for inf or nan.
The standard seems to allow the form -1+-2i, which is disallowed by the regex.
Can you clarify?

The situation with parentheses appears to be an artifact of the way that Python represents complex numbers as strings, and the way that JSON Schema treats regular expressions. Unfortunately, in order to provide backwards compatibility, it looks like I may actually have to modify the standard to explicitly allow the existence of parentheses surrounding complex numbers.
Also, I don't believe the form -1+-2i should be allowed, so the documentation will need to be modified.
Thanks for pointing out these issues.

After digging into this more, it's clear that the current regex is not quite correct, and as a result it is not at all useful for its intended purpose. The fact that no anchors are explicitly given means that a wide variety of garbage strings will be inadvertently validated. This will need to be fixed, but I'm afraid that the result will be a very ugly regex indeed.

If you define such a regex, please also make explicit which captured groups contain the real and the imaginary part.
Maybe it would be cleaner to define the syntax in terms of a grammar? That would be easier to understand, and thus to get correct. It should be possible to derive a regex (semi-)automatically from a grammar.

Yes, maybe a grammar would be more expressive and easier to understand. However, I'm not sure whether there's a standard way to do that since BNF describes context-free grammars. I suppose a regex can be described using BNF, though.
Automatic conversion would be pretty cool, but I'm not aware of any ways to do that. It might be a fun project though...


Update nuget

Hey, would it be possible to push the latest to nuget? My backup plan would be to fork and publish my own nuget - but would prefer to use this one directly if I could.

Would also appreciate this update

See #17. We are working on it, will be done soon

Is there anything new on this topic? #17 has been merged.

I too could really use an update on the NuGet.

I have good news. "Soon" is now. Sorry for the delay, there were some organizational tasks to be done that held this up until now


decoupling compute: distance

The distance submodule computes distances between attributes. For string-type attributes, it computes string distances using metrics like jaro-winkler similarity or levenshtein. For numeric-type, the absolute difference. And so on...
So to apply the bridge pattern, the abstraction would be an abstraction of this distance class. And it has an Engine abstraction. An engine can use any of postgresql, sqlite, pandas, spark for computations


Allow for Usage of Cert-Manager in helm chart for webhook certificate

Description
What problem are you trying to solve?
I'd like to be able to use cert-manager to manage: https://github.com/aws/karpenter/blob/main/charts/karpenter/templates/secret-webhook-cert.yaml rather than relying on a pre-sync hook or some other mechanism.
How important is this feature to you?
Reasonably important. Allows us to control the issuer, renewal timing, and other features of the certificate.

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

We're thinking of just getting rid of our webhook altogether in-favor of using CEL.  Curious on your thoughts: https://github.com/aws/karpenter-core/issues/103

@bwagner5 I think that'd be great. Would remove extra maintenance requirements from karpenter's side and just allow for native tooling to be used.
I'm curious if there's a k8s versioning restriction on CEL? Or is it all K8s versions? If there is, it might make sense to add an option to still disable the webhook cert for those of us not on 1.28, or have slower upgrade cycles?

CEL has been available as a Beta feature (enabled by default) since K8s 1.25. Karpenter supports down to K8s 1.23 right now. So we'd need to setup a flag for this or wait until early next year to roll out CEL support as the default.
You are able to disable the webhooks by setting the DISABLE_WEBHOOK=true environment variable when installing Karpenter.

@bwagner5 Because I haven't looked into the webhooks specifically for Karpenter, do I lose out on anything by disabling them? Are they validating webhooks? If so I might spend some time helping convert from this to CEL.

We'd love the help!!!
We have some validating and some mutating (defaulting) webhooks. Most of the validations are fairly simple, so we're hoping that CEL is able to model those well enough, but it would be great if you'd be willing to help with that.
If you disable the webhooks, you lose the validations found below and you'd also lose any defaulting of the Provisioner. For example, if you give a provisioner with no requirement, we default AMD64 and on-demand.
Here's the validations for the AWSNodeTemplate: https://github.com/aws/karpenter/blob/main/pkg/apis/v1alpha1/awsnodetemplate_validation.go
And here is the validations for the Provisioner:
https://github.com/aws/karpenter-core/blob/main/pkg/apis/v1alpha5/provisioner_validation.go

@bwagner5 I opened: https://github.com/aws/karpenter/pull/4586 I'm not sure if you want the PR here or in karpenter-core. Let me know and I can redirect it

We'll need PRs in both Karpenter and karpenter-core, depending whether or not the validation is AWS specific or not.

This should be closed as part of v0.33.0


Starter hides tabline

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
starter
Description
Opening when mini.starter is opened the tabline is hiddent. Is there a way to show tabline always?
Neovim version
0.8.3
Steps to reproduce
Configure starter and tabline

nvim
what do you see? Tabline is hidden!

Expected behavior
Tabline should be  visible after starter open.
Actual behavior
Tabline is hidden just after starter open.

Not showing tabline and showing statusline is by design. This (subjectively) looks better.
There is a MiniStarterOpened event which you can use to reshow tabline. Try adding this after require('mini.starter').setup() call:
vim.cmd('autocmd User MiniStarterOpened set showtabline=2')

Does this solve your issue?

It works! Thanks! This is what I need!


pict-rs_0_3: drop

Description of changes
This was broken by the Rust 1.80 upgrade, and is an old version that we’d have to patch to keep working.
We have already done the 0.4 → 0.5 update without keeping around the old version or adding in any additional stateVersion logic in https://github.com/NixOS/nixpkgs/pull/280221. As a result, migration for 0.3 users is going to be a little awkward. I’ve done my best to provide comprehensive instructions for anyone who hasn’t already bumped to 0.4.
It is probably a footgun to add stateVersion logic for any package that makes backwards‐incompatible schema changes and only supports migration from the immediately previous version. Users won’t get migrated by default and we have to either package and maintain an endlessly growing list of old versions or add complicated instructions like this. It’s not really practical for us to support a significantly better migration story than upstream does.
cc @happysalada
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Oh, that’s problematic if it only support update from 0.3 to 0.4 and there is no such 0.4 in nixpkgs. I’ll try to override the package to update my server.

Yes, it’s unfortunate, I’m sorry :( We had 0.4 before the release of 24.05, but the bump happened without being mentioned in the release notes AFAIK.
stateVersion was probably never the right thing here since the migration can be done automatically and we can’t really maintain and patch an endlessly‐growing set of versions just to keep rollback working when the upstream migration code doesn’t keep that compatibility. Any users still on 0.3 were in a bad spot already before this PR, but hopefully the migration instructions can help them get out of it.
Ideally upstream would restore the 0.3 migration code to 0.5, but I don’t know how complicated that would be. cc @asonix

My stance on bringing back the 0.3 migration code in 0.5 is that I'd rather not. It's unfortunate that nixpkgs ended up in this situation though.

I totally forgot I can just mix different version of Nixpkgs to pick a specific package from one. That’ll be quite usefull (as 0.4.7 fail to compile for the same reason than 0.3)

My stance on bringing back the 0.3 migration code in 0.5 is that I'd rather not. It's unfortunate that nixpkgs ended up in this situation though.

Alright. I can understand not wanting to keep that legacy code forever, but hopefully you can understand that we also don’t want to (really: can’t, given maintainer resources) do the work of maintaining packages for old versions indefinitely and patching the code ourselves if they break, just for migration purposes. I don’t think there’s any way out here other than to roll forward and make sure we mention the major version bumps in the changelog in future.

I totally forgot I can just mix different version of Nixpkgs to pick a specific package from one. That’ll be quite usefull (as 0.4.7 fail to compile for the same reason than 0.3)

Right, that’s probably the best thing you can do to get the migration done. Did you try following my instructions in the error message I added? I’d appreciate any suggestions on how they could be made clearer, or any issues you run into during the process.

Looks good to me

I’ll wait a day or so to hear back from @marius851000 about the migration and then merge. This can’t make 0.3 more broken than it already is, so it’s only a matter of how good our migration instructions are.

Okay, I’m back (after some issue pushing the build on the server). So, using
    owner = "NixOS";
    repo = "nixpkgs";
    rev = "9b19f5e77dd906cb52dade0b7bd280339d2a1f3d";
    sha256 = "sha256-rCIsyE80jgiOU78gCWN3A0wE0tR2GI5nH6MlS+HaaSQ=";
  }) {}).pict-rs;```
does work (if you don’t mind Import From Derivation. Otherwise, it could be replace with a ``fetchurl``).

What didn’t worked was, after the migration for 0.4 was ran and switching to ``services.pict-rs.package = pkgs.pict-rs;`` was port binding, as it seems ``pict-rs`` 0.5, as configured in NixPkgs, does not respect the ``services.pict-rs.port`` port property (and 8080 is already used for... (check config) a custom hacky BOINC account manager).

Configuration tells me that PICTRS__SERVER__ADDRESS should be used instead of PICTRS__SERVER__ADDR. I’ll test that locally (and if it does work, I’ll suggest fixing it in this PR, even if that’s slightly outside of the scope of this PR)

Thanks for trying it out! I’ll happily deal with that fix in this PR if you confirm it works. Do you think it would be a good idea for us to document an exact services.pict-rs.package setting that should work for the transition? Not knowing how to select a package from a pinned Nixpkgs was one of my big worries about these instructions. We should be able to use builtins.fetchTarball to avoid IFD.

So, you can use this:
services.pict-rs.package = (import (builtins.fetchTarball {
    url = "https://github.com/NixOS/nixpkgs/archive/9b19f5e77dd906cb52dade0b7bd280339d2a1f3d.tar.gz";
    sha256 = "sha256:0939vbhln9d33xkqw63nsk908k03fxihj85zaf70i3il9z42q8mc";
  }) {}).pict-rs;

And PICTRS__SERVER__ADDRESS should indeed be used. It does bind correctly with systemd.services.pict-rs.environment.PICTRS__SERVER__ADDRESS = "<IP_ADDRESS>:5934";

Hmm... I have some doubt this migration has not happened well. I find an image I uploaded about a years ago on lemmy, and it return 404. I actually remember it said 0 images were migrated after switch to 0.4.0, but the files files and sled folder were populated (and still are). I’ll go investigate that.

Perhaps it’s related to the environment variable changes listed in the 0.3 to 0.4 migration guide? I could include those in the error message along with the package.

Indeed, removing the newly created folder sled-repo, setting systemd.services.pict-rs.environment.PICTRS__OLD_DB__PATH = config.services.pict-rs.dataDir; and returning to 0.4, it seems to be migrating now. I’ll leave it running while I sleep.

I’ve updated the PR with the fix and more precise instructions; please let me know how the migration goes and what you think of the new diff :)
Something I am worried about is that now that we’re setting PICTRS__SERVER__ADDRESS, the 0.4 step won’t get PICTRS__SERVER__ADDR set. Should we include that variable in the configuration snippet too so that it’s possible to check that the migration worked before bumping the version again?
Unfortunately, I guess this also means that anyone who opted in to upgrading to 0.4 in the past didn’t actually get things upgraded. There’s probably nothing we can do about that; hopefully they at least noticed before the bump to 0.5…

I think 0.4 also use PICTRS__SERVER__ADDRESS. At least it doesn’t crash with systemd.services.pict-rs.environment.PICTRS__SERVER__ADDR = pkgs.lib.mkForce null;. It has migrated well (and is properly the image as expected). I have to go to work now, so won’t check more than that. I’ve now returned to 0.5.0, and it’s own migration seems to go well.


Enable single-select or multi select based on condition?

Is there a way to implement the function in case where something is "active" ->singleSelect(true) otherwise singleSelect(false)?
EX)
->dependsOn('is_active')
->singleSelect(function () if('is_active' == 1) return true; else return false))
If it is working as dependsOnOptions, it can't be better
Thanks in advance

Hi! I don't think it's good practice to add a feature like that due to the nature of data (multi-select saves an array while singleSelect will save a single value).
However, I did add dependsOnMax option where you can specify a max of 1 to limit the max amount of selected options to 1.


Teamcity integration

This Fixes #683 https://github.com/zulip/zulip/issues/683
I will write the documentation soon, just wanted to get this pull request out there for feedback.

Automated message from Dropbox CLA bot
@dwrpayne, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Hmm... why are there a couple other commits in this branch? I am fairly new to github workflow - not sure what I need to do in order to fix this.

I believe that results from your having done a git pull rather than git pull --rebase at some point while developing your branch.  You should be able to fix this via:
git pull --rebase # to rebase your local branch on top of master
git push origin +HEAD:teamcity-integration # to update the branch on GitHub that this PR is based on

Ack! That seems to have made things worse. Sorry :( I think I'll close this pull request and try to fix it - maybe I'll make a new branch and cherry-pick the one commit I want into it. :)

OK -- even if you need to remake your local branch, you actually should be able to reuse this pull request if after making your new branch, you force-push using git push origin +HEAD:teamcity-integration, rather than making a new one.
You may want to play with a graphical git viewer like gitk or SourceTree to help you see what's going on if you run into a similar problem in the future.


Minor grammar proofread

just beating @sjmackenzie to the punch :wink:

gah, can you merge this I want to work off this commit, can you merge pls :-)


Is there a way where we can avoid shrinking of the events occuring at the same time and ovelap it instead?

Something like this? https://github.com/hoangnm/react-native-week-view/issues/233

No, So actually I have blocked some cells in the calendar  as shown in the image by  passing isTimeSlot key in the event, Just as you mentioned in issue

,
So I want to enable overlapping of events in the greyed out portion something like this:

But actually when I move the event to that greyed out section both the events are getting aligned side by side instead of overlapping

I see
This should be solved by the upcoming block-like events. We are trying to release them soon!

Thanks!
Any ETA on this

There is already a first working version implemented.
But I'm not sure on an ETA for the actual release, since it needs a couple of ongoing refactors (#219 and #229). I'd say still a couple of weeks

Check this comment in a similar issue with a solution


Bump 0.3.0

Bump 0.3.0
RPM package for FC36 will be from this version which is supporting Podman V4.
Signed-off-by: Navid Yaghoobi<EMAIL_ADDRESS>

LGTM


Update how-to-use-the-classic-connector.md

Classic multi-cloud connector got deprecated. MDC Engineering (Bahjat) already removed all existing legacy connectors from the backend, so no Removal instructions needed. AFAIC, this whole page can be removed.

@dcurwin
Can you review the proposed changes? Note that the validation warnings must be resolved before merging.
Articles must also contain a body of content that's sufficient and complete to stand on its own as an article. Should this article be deleted and redirected instead?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@elSagie  I'm closing this PR and addressing it in my own separate PR because of the complicated nature of the request.
#please-close

[like]  Eli Sagie reacted to your message:

From: prmerger-automator[bot] @.>
Sent: Sunday, January 28, 2024 10:54:24 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Eli Sagie @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update how-to-use-the-classic-connector.md (PR #119160)
Closed #119160https://github.com/MicrosoftDocs/azure-docs/pull/119160.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/119160#event-11619625035, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMT4CCS4KBLWTKD6GICPFJDYQYU6BAVCNFSM6AAAAABCI6MC46VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGYYTSNRSGUYDGNI.
You are receiving this because you were mentioned.Message ID: @.***>


Key Generation Fails in UI Intermittently

Appears the key is created behind the scenes in DB, etc, but not returned to UI. Need to grab client side and server side logs when it happens next.

may be related to #12 and a race scenarios deleting the old key before new one is created.  When this error occurs the key is incorrectly captured as a BYPASS key.


Validation with sacrebleu tokenizes escaped UNK-tokens

🐛 Bug
I'm on a translation task and do validation with BLEU during training. If --eval-tokenized-bleu is not set, scoring is done using the sacrebleu.DEFAULT_TOKENIZER. See these lines:
https://github.com/pytorch/fairseq/blob/d7b0bf7e55b48466ee7e371a959668dfb8feaaf6/fairseq/tasks/translation.py#L348-L357
UNK-tokens in references are escaped with <<UNK>> before scoring (line 351). This may produce a reference like this This is a new <<UNK>>.. In hypos the UNK-tokens are not escaped, leaving a hypothesis like this This is a new <UNK>.
Bug: The default tokenizer of sacrebleu breaks the UNK-tokens (which is probably not wanted behaviour) and scores each token separately, altering the bleu scores.
To Reproduce
Follow any translation example.
Code sample
This is whats currently implemented:
>>> hypo = "This is a new <UNK>."
>>> ref = "This is a new <<UNK>>."
>>> from sacrebleu import TOKENIZERS, DEFAULT_TOKENIZER
>>> TOKENIZERS[DEFAULT_TOKENIZER](hypo)
'This is a new < UNK > .'
>>> TOKENIZERS[DEFAULT_TOKENIZER](ref)
'This is a new < < UNK > > .'
>>> sacrebleu.corpus_bleu([hypo], [[ref]], tokenize=DEFAULT_TOKENIZER).score
55.96526475152516

This is how I think these sequences should be scored:
>>> hypo = "This is a new ABC."
>>> ref = "This is a new UNK."
>>> TOKENIZERS[DEFAULT_TOKENIZER](ref)
'This is a new UNK .'
>>> TOKENIZERS[DEFAULT_TOKENIZER](hypo)
'This is a new ABC .'
>>> sacrebleu.corpus_bleu([hypo], [[ref]], tokenize=DEFAULT_TOKENIZER).score
53.7284965911771

Expected behavior
The bleu score should not be influenced by the unknown token.
Environment

fairseq Version (e.g., 1.0 or master): master
PyTorch Version (e.g., 1.0): 1.2
OS (e.g., Linux): linux
How you installed fairseq (pip, source): source

Fixed by b2ee110c853c5effdd8d21f50a8437485bafb285

I also see that after fairseq.preprocess, some tokens are not there in the dicts for both the languages. What might be the reason?


[Question] Groovy DSL: No EachLike validation

A raw array "eachLike":
withBody eachLike(1) {
    type regexp('.*', 'banana')
}

produces:
[
  {
    "type": "banana"
  }
]

A named array "eachLike":
withBody {
    fruits eachLike(1) {
        type regexp('.*', 'banana')
    }
}

produces:
{
  "fruits": [
    {
      "type": "banana"
    }
  ]
}

A wrong DSL like:
withBody {
    eachLike(1) {
        type regexp('.*', 'banana')
    }
}

produces:
{}

but there is not warning or error regarding incorrect DSL usage.
Is there a way to produce an error or a warning in case "eachLike" is put in a wrong place inside "withBody" DSL?
Code examples can be found here: https://github.com/artamonovkirill/pact-issues-examples/tree/master/src/test/groovy/com/github/artamonovkirill/pact/eachlikevalidaiton

That will be really hard to detect. The first example works because the eachLike method returns a matcher, which is then passed to the withBody as a parmeter, and that method knows what to do with it.
The second example works because the builder uses the missing method functionality in Groovy, so
fruits eachLike(1) means execute the eachLike as before, but then pass it to the fruits method. And the method missing callback kicks in so it can be handled.
The problem is that there is nothing to hook on too. The outer closure is executed, which contains just the eachLike call, and then the closure terminates. Because the returned value of the eachLike method is not assigned to anything, it is lost.
One thing I could try is checking the result of the closure, and if that is a matcher then maybe something is wrong.

The return value works, I can detect that example. I can also detect this one:
withBody {
    fruits eachLike(1) {
        regexp('.*', 'banana')
    }
}

However, if something else is returned from the closure, then there is nothing I can do. I.e.,
withBody {
    eachLike(1) {
        type regexp('.*', 'banana')
    }
    "fruits" // This will be the return value
}


[Feature Request] Support for group convolution

Grouped convolution is supported well in pytorch's convolution layers / ops. If possible, it would a great to add that ability to torchsparse.

Thanks for bringing this up! The reason that we do not support grouped convolution is that it does not offer much speedup for sparse workloads. This is mainly because sparse convolution is memory-bounded instead of computation-bounded. That said, I think supporting this is still meaningful, and we probably need to do more optimization for it.

I'm also interested in support for grouping operations~
For the design of lightweight networks such as MobileNet, the use of depthwise separable convolutions (that is, setting the number of groups to the number of input channels) can reduce the amount of parameters.
For a kernel size of KxK, C channels (assuming the same number of input and output channels)

parameters
2D
3D

convolution
KxKxCxC
KxKxKxCxC

depthwise separable convolution
KxKxC + 1x1xCxC
KxKxKxC + 1x1x1xCxC

The bottleneck of computing relative to IO may be broken by increasing the size of the convolution kernel. RepLKNet made an attempt,  arXiv: https://arxiv.org/abs/2203.06717.

Thanks for providing the model size perspective! We will take that into our consideration.

Is there any update on the group sparse convolution?

any updates on this?


[BUG] JSONDecodeError for TOTP 2FA (Google Authenticator)

I am getting a JSONDecodeError exception when I try to perform two factor authentication with Google Authenticator.
Am I doing something wrong or has Instagram changed the API?
Traceback:
Status 200: JSONDecodeError in private_request (user_id=10342827286, endpoint=/challenge/) >>> <!DOCTYPE html> (long html...)
future: <Task finished coro=<Dispatcher._process_polling_updates() done, defined at /app/.heroku/python/lib/python3.7/site-packages/aiogram/dispatcher/dispatcher.py:407> exception=ClientJSONDecodeError('JSONDecodeError [Errno Expecting value] <!DOCTYPE html>\n<html lang="en" class="no-js logged-in client-root touch">\n    <head>\n        <meta charset="utf-8">\n
(long html...)
</script>\n    </body>\n</html>
instagrapi.exceptions.ClientJSONDecodeError: JSONDecodeError [Errno Expecting value] <!DOCTYPE html> (long html...)
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: [Errno Expecting value] <!DOCTYPE html> (long html...)

@hittiks it looks like instagram has changed api, can you fix it?

@adw0rd No, I can't fix it

To recreate the behavior, you need to follow the link https://i.instagram.com/challenge/?next=/api/challenge/ (after 2FA)
So I tried to run that long HTML and got this page:
https://ibb.co/1GhWPyg

I have the same problem.

a quick fix:
pip install ensta
from ensta import Host

host = Host(username, password, totp_token=token)


Old running examples

Hi,
The running examples seem to use an old feature, e.g. --teams-roots instead of --teams-root (there could be others too).
Best,

It seems to be correct in the last version of the code.


Combine RPC http and ws server

Describe the feature
because we need to configure modules on a per transport basis, we currently use one Server for HTTP and WS, however this does not quite work since both now listen on the same address.
Instead we need to merge both of them and add a custom middleware that calls handles the request depending on the transport.
Additional context
No response

I can take this too since it covers rpc.

this is a bit tricky and I started working on this, but #1224 would be an easy pick off instead.

Alright.


Hooks

start using hooks

travis-ci is being real dumb.  Passes locally; gonna merge, and consider switching ci tools.