Is PatternFly-ng2 a good name for this project?

Ekk!  Love that it's a question, I vote it is not a good name. Principally, Angular peeps say stop putting numbers on things (its not angular 2 or 4 moving forward, its simply Angular vs AngularJS - 1.x.  Secondly, yeah, gotta reiterate my personal comfortableness with the versioning of the ng here.
Suggestions:

patternfly-angular - would be the most appropriate, but its kinda already been taken :frowning_face:
patternfly-ng - :vulcan_salute:  avoids version lockin also :vulcan_salute: you could also inverse this... :thinking:
angular-patternfly - kinda confusing given the first suggestion but inline with other repos

Good question @dgutride
I agree, we should not attach it to a version. I'd rather prefix the name with "patternfly-" than with "angular-"

@AllenBW  - other options we discussed would be patternfly-ngx.  I do think it might be nice to differentiate this from angular-patternfly somehow.

@dgutride oh that works, x for allllllllllll versions :world_map:

Should we just create a branch of angular-patternfly?  That is what I see a
lot of other projects doing.
Cheers,
Walden
On Thu, Mar 9, 2017 at 9:44 AM, Dana Gutride<EMAIL_ADDRESS>wrote:

@AllenBW https://github.com/AllenBW - other options we discussed would
be patternfly-ngx. I do think it might be nice to differentiate this from
angular-patternfly somehow.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/patternfly/patternfly-ng2/issues/2#issuecomment-285370318,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD7PtXiiKY8sM1LY84_Xe-cXEpda3_kpks5rkBBZgaJpZM4MYFrM
.

Looking at the Angular world it seems that the most "standard" name would be ng-patternfly.

I agree with @lorthirk ng-patternfly is a good name

The patternfly standard has been to use patternfly- as the prefix.  Would everybody be ok with patternfly-ng (based on what I'm seeing as the recommendations)?
@carlosthe19916 @lorthirk, @allenbw, @andresgalante

+1 for patternfly-ng.  Having the patternfly- prefix first highlights this as a patternfly project, rather than as an angular project, ie. it's not just some angular extension, but rather fits with the family of patternfly-* framework integrations.

+1 re: patternfly as a prefix!

+1 - patternfly as prefix makes it consistent and easier to find when looking amongst the patternfly repos

I would recommend patternfly-ng or -ngx. I'm seeing both in use. A lot of libraries that had -ng2 have gone to -ngx. But newer ones are going either way. At this point -ngx is the way the community knows that it isn't Angular 1. For me, I like the cleaner look of -ng.

I agree with @bleathem point about keeping patternfly first because this is a patternfly project.

-ngx reminds me of nginx

that is one of the downsides to that version, yet another reason to go with -ng

IMO patternfly-angular is better, explicit, not too long, prefixed by patternfly

Repo renamed to patternfly-ng - thanks all for the great input.  Closing issue...


Ram usage

Hi.
verged takes 1.6 gb on linux.. It's too much and should be improved IMO.
PS : I'm using the 4.0.2a version

It will be improved in upcoming codebase v.0.17 which is due to release
anytime soon.
On Fri, Nov 2, 2018, 17:56 piratoskratos<EMAIL_ADDRESS>wrote:

Hi.
verged takes 1.6 gb on linux.. It's too much and should be improved IMO.
PS : I'm using the 4.0.2a version
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vergecurrency/VERGE/issues/820, or mute the thread
https://github.com/notifications/unsubscribe-auth/AjzlvIfPS-aIPx3CBNl30RJ-aRRKtkMqks5urDnugaJpZM4YLkEP
.

@piratoskratos Included in next release @karanpatel863 pointed out.


Added docs and script for integration tests

Added docs for running functional integration tests locally
Added a simple shell script to run the functional integration tests locally

@billonahill Fixed.

👍


Updated the links

Summary

Ticket Link

Hello @Sayanta66,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


need sdk version constraints in pub

Here's the problem: if we (or anyone else) push a new version of a package to Pub, and this version is built against bleeding_edge, it will break trunk users. If we don't push this new zip file, we break bleeding_edge users. It's a no win situation.
One possible answer is to queue up the package and upload it just as the trunk push goes out, but that's no good either.
Here's a strawman proposal:
  depedencies:
    # Note: you can only use >= constraints!
    sdk: ">= 0.2.0+14118"
Say we have these html5lib versions:
  0.0.16 -> sdk: ">= 0.2.0+14118"
  0.0.15 -> sdk: ">= 0.2.0+13942"
If pub is looking for html5lib, and I have SDK 14000, pub will get 0.0.15. It will not get 0.0.16, yet. Once my trunk Editor upgrades itself, I'll get 0.0.16
People using html5lib/web_components are already having pain with our bleeding_edge pub packages. This seems like the only sensible fix for the next few milestones while breakage is happening frequently. But I'm open to other ideas.
BTW -- you can only use >= constraints, because SDK can never be upgraded or downgraded by Pub. That keeps the rule a bit more sane.

This issue has been moved to dart-lang/pub#249.


Api clean up

Coverage increased (+1.0%) to 100.0% when pulling 68647da24ca344ff2359a265c4735e9f7e57961b on api-clean-up into c2edfc4af1089b625da7bec7c56e40ab37f7cd7b on master.


Defs: squish keyword defs by resetting newlines to 1

Closes #13

Deciding against this strategy for now, as it needs lookahead ala module directives to know when it's appropriate to squish and when it's not.
Speaking of module directives, we could speed this Style up substantially - and have greater context allowing us to implement this newline behaviour - by copying the implementation of ModuleDirectives (run on :defmodule and style its body children, rather than traversing an entire code swath)


Remove Sonar Dead Store Issues.

This is a proposed fix to resolve all dead store issues in Sonar. This is a draft request, the unclear points are annotated.
https://analysis.apache.org/component_issues/index?id=org.apache.archiva%3Aarchiva#resolved=false|rules=findbugs%3ADLS_DEAD_LOCAL_STORE

@ecki  Thanks!


publish for 2.12, please?

@adamw
do you guys want to adapt this small thing as a companion of odelay?

I can publish it under our groupId, but no promises around maintenance :)

@adamw any progress here? Can I help somehow? I guess I can send a PR to your fork with packages rename

@softprops I guess easiest would be moving ownership like before - could you do it?

@softprops to the softwaremill org please :)

@adamw I'm seeing this when I do that

I think its because its an org I'm not a member of. Could I just transfer to you and you can transfer it to that org?

Ah, sure, go ahead

transfer request sent

Here you go: https://repo1.maven.org/maven2/com/softwaremill/undelay/

Thanks for stepping up on that @adamw!

thank you guys!


Memory / RAM Problem in Live Demo

Hey there, looks like a really cool project. However, when I open the live demo I see massive memory usage. The application consumes around 10 GB in 30 seconds or so, before either the browser or I kill it. Problem tested and observed on the following:

Windows + Chrome 78
Windows + Firefox 74
Arch Linux + Firefox 76

Don't know if this is a sign of problems with the library or if it is specific to the demo though. Let me know if you'd like any more info from me.

Interesting. Sounds like garbage collection isn't working properly in it.

Looking into it.    I'm not seeing the same issue with my local code on a quick check.

@Thanson16  @justinclift    Fixed. Demo was old go version.
I have updated the demo to go 1.14 and the latest wasm_exec.js as well.
Whilst I had updated the library for 1.13 previously, the demo was still on old 1.11 which definitely has leaks.    Also,  1.14 has additional cleanup for js_value in the GC now, which is nice.
I'm letting it run overnight to confirm, but seems OK in a short test.
Please check if this fixed it for you.

Quick test on Firefox + Linux and all looks great! Thank you!

@Thanson16  Welcome.  Let me know if there is anything you'd like to see added.   I may have some time to do more work on this shortly.


Allow use of main instead of android_main

Inspired by #504.
Instead of requiring the user to do PLATFORM_ANDROID #ifdefery,
have the android_main entry point exported by raylib and call
the user-defined main. This way many games could (in theory)
run unmodified on Android.
This is untested!

Just waiting to get some time to test this change properly when merging... I'm closing academic term this week and I'm a bit busy for long implementation/testing sessions...

Merged. Need to test it properly.

Amazing! It works like a charm! :D


Handle exceptions in truss watch

Connection Errors, TrussHandle construction errors

@joostinyi can you update on what we need here for the 0.6.0 release?


Add error message when newer version of MB config is opened on old Model Builder

As we continue to update Model Builder and the .mbconfig files, some versions of Model Builder won't be able to support some .mbconfig files.
For example, if Jake crates an mbconfig files on version 16.6.8, and it creates a mbconfig file with version 1.2,  Becca won't be able to open that version on Model Builder 16.0 because it has no idea what to do with mbconfig version 1.2.
We should add in the current Model Builder a message that tells people the mbconfig file is newer than the current version supported.

To test, manually open an mbconfig file and change a version to be newer (e.g. make something version 3). You don't need to change anything about the actual object. Error message should show saying "version 3 of type x".

Yes, got the the error message on ML.Net Model Builder: <IP_ADDRESS>6701 (Main)


Fails to startup

After I fixed issue #36, the below error is logged when I run the container:
info: 1/9/16 16:19:52,904	[tribeca:config]	MongoDbUrl = mongodb://tribeca-mongo:27017/tribeca
info: 1/9/16 16:19:52,916	[tribeca:main]	Listening to admins on *:3000
info: 1/9/16 16:19:52,958	[tribeca:config]	TRIBECA_MODE = dev
error: Terminating! uncaughtException [TypeError: undefined is not a function] TypeError: undefined is not a function
at new Publisher (/tribeca/tribeca/common/messaging.js:41:34)
at getPublisher (/tribeca/tribeca/service/main.js:130:33)
at /tribeca/tribeca/service/main.js:190:9
at /tribeca/node_modules/q/q.js:1229:26
at _fulfilled (/tribeca/node_modules/q/q.js:834:54)
at self.promiseDispatch.done (/tribeca/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch (/tribeca/node_modules/q/q.js:796:13)
at /tribeca/node_modules/q/q.js:556:49
at runSingle (/tribeca/node_modules/q/q.js:137:13)
at flush (/tribeca/node_modules/q/q.js:125:13)

Debugging through the code, I see a very weird behavior.
When I use node console:
var test = require('./messaging.js');
it will import the variables in Topics, including Topics.ProductAdvertisement thats needed at line 190 in main.js (line 270 in main.ts)
but when I put breakpoint in main.js at line 190 then use repl:
Messaging Object's Topics only contains functions and when I try to reimport it, Topics still only contains a function

same issue :/

@WaleedAshraf, I got this fixed yesterday. Please update your local code.


Auth Routes from an API

Hello support team,
I read https://nuxtjs.org/examples/auth-routes and make my project works well. But I want to use API Auth from URL: http://localhost:8000/rest-auth/login/ instead of using username: demo and password: demo.
How can I fix file api/index.js
/ Add POST - /api/login
router.post('/login', (req, res) => {
  if (req.body.username === 'demo' && req.body.password === 'demo') {
    req.session.authUser = { username: 'demo' }
    return res.json({ username: 'demo' })
  }
  res.status(401).json({ message: 'Bad credentials' })
})

// Add POST - /api/logout
router.post('/logout', (req, res) => {
  delete req.session.authUser
  res.json({ ok: true })
})

Thank you!

.

I'm closing this issue because it's not really related to nuxt source code, I recommend you to post on our gitter to get help from the community.


Select environment variable in stack app template doesn't propagate.

Bug description
When deploying custom stack's app template with environment variables of "select" type, those variables are not propagated to stack's environment. Only those of another types ("preset" and "text") are.
Expected behavior
All environment variables defined in stack's app template propagating to deployed stack. The same not happens with containers templates.
Portainer Logs
Unnecessary.
Steps to reproduce the issue:

Go to 'App Templates'.
Click on '+ Add template'.
Click on 'Swarm stack' to select it as template type.
Scroll down to 'Environment'.
Click on '+ add variable'
Click on 'Select (Choose value from list)' to select it as variable type.
Fill all required fields.
Click on 'Create the template'.
Click on just created template.
Fill required fields.
Click on 'Deploy the stack'.
Click on just created stack.
Click on 'Editor' tab.
Scroll down to 'Environment'.
See that "select" variables aren't there.

Technical details:

Portainer version: 1.24.0
Docker version (managed by Portainer): 19.03.8
Platform (windows/linux): Linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker stack deploy ...
Browser: Google Chrome 83.0.4103.61

Additional context
Not applicable.

Note that we are redeveloping Portainer App Templates and there will be a completely new UX for them in 2.0
This issue wont be addressed separately, but rather as part of the rewrite.

Future 1.24.* releases will only receive security fixes and custom templates were changed in the upcoming 2.0 release via #3861 where there is not currently environment variables available via custom template creation. So I will actually close this as it won't need to be addressed


Generate mutationKeys for useMutation hooks

What is the problem this feature would solve?
I want to have mutationKeys to arrange invalidations of queries after mutation occurs. But right now no mutationKey was generated for mutation hooks. Can this feature be implemented/?
External documents/projects?
No response
What is the feature you are proposing to solve the problem?
No response
What alternatives have you considered?
No response

@wuyuanyi135 Can you provide details about the relevant kubb plugins this change would involve? You mean swr? Or react-query? Or whatever?

@helt Hi, I meant the react-query plugin, I wrote a template as workaround. However, since I am not familiar with this project this template may look awkward :P. The goal is to put mutationKey onto each mutation requests
import transformers, {camelCase} from '@kubb/core/transformers'
import {Function,} from '@kubb/react'
import {Mutation} from '@kubb/swagger-tanstack-query/components'
import {} from '@kubb/plugin-oas'
import {ReactNode} from "react";

export const templates = {
    ...Mutation.templates,
    react: function Template(
        {
            name,
            params,
            mutateParams,
            JSDoc,
            client,
            hook,
            dataReturnType,
        }: React.ComponentProps<typeof Mutation.templates.react>): ReactNode {

        const isFormData = client.contentType === 'multipart/form-data'
        const headers = [
            client.contentType !== 'application/json' ? `'Content-Type': '${client.contentType}'` : undefined,
            client.withHeaders ? '...headers' : undefined,
        ]
            .filter(Boolean)
            .join(', ')

        const clientOptions = [
            `method: "${client.method}"`,
            `url: ${client.path.template}`,
            client.withQueryParams ? 'params' : undefined,
            client.withData && !isFormData ? 'data' : undefined,
            client.withData && isFormData ? 'data: formData' : undefined,
            headers.length ? `headers: { ${headers}, ...clientOptions.headers }` : undefined,
            '...clientOptions',
        ].filter(Boolean)

        const resolvedClientOptions = `${transformers.createIndent(4)}${clientOptions.join(`,\n${transformers.createIndent(4)}`)}`

        const formData = isFormData
            ? `
   const formData = new FormData()
   if(data) {
    Object.keys(data).forEach((key) => {
      const value = data[key];
      if (typeof key === "string" && (typeof value === "string" || value instanceof Blob)) {
        formData.append(key, value);
      }
    })
   }
  `
            : undefined

        const keyFunctionName = `${camelCase(name, {prefix: 'get', suffix: 'MutationKey'})}`

        return (
            <>
                <Function export name={keyFunctionName}>
                    {`
         return ['${client.path.path}'];
                    `}
                </Function>

                <Function export name={name} params={params} JSDoc={JSDoc}>
                    {`
         const { mutation: mutationOptions, client: clientOptions = {} } = options ?? {}

         return ${hook.name}({
           mutationFn: async(${mutateParams}) => {
             ${hook.children || ''}
             ${formData || ''}
             const res = await client<${client.generics}>({
              ${resolvedClientOptions}
             })

             return ${dataReturnType === 'data' ? 'res.data' : 'res'}
           },
           mutationKey: ['${client.path.path}'],
           ...mutationOptions
         })`}
                </Function>
            </>
        )

    }
} as const

Actually, exposing mutation keys is also interesting for swr.

@helt @wuyuanyi135 What will be expected as mutationKey?
Example of what I was thinking about, an object with the url but no params(because those are defined in the mutate function.
import client from "axios";
import type { UseMutationOptions, UseMutationResult, MutationKey } from "@tanstack/react-query";
import type { RequestConfig } from "axios";
import { useMutation } from "@tanstack/react-query";

 export const updatePetWithFormMutationKey = () => [{ "url": "/pet/{petId}" }] as const;

 export type UpdatePetWithFormMutationKey = ReturnType<typeof updatePetWithFormMutationKey>;

 /**
 * @summary Updates a pet in the store with form data
 * @link /pet/:petId
 */
async function updatePetWithForm(petId: UpdatePetWithFormPathParams["petId"], data?: UpdatePetWithFormMutationRequest, params?: UpdatePetWithFormQueryParams, config: Partial<RequestConfig<UpdatePetWithFormMutationRequest>> = {}) {
    const res = await client<UpdatePetWithFormMutationResponse, UpdatePetWithForm405, UpdatePetWithFormMutationRequest>({ method: "POST", url: `/pet/${petId}`, params, data, ...config });
    return updatePetWithFormMutationResponse.parse(res.data);
}

 /**
 * @summary Updates a pet in the store with form data
 * @link /pet/:petId
 */
export function useUpdatePetWithForm(options: {
    mutation?: UseMutationOptions<UpdatePetWithFormMutationResponse, UpdatePetWithForm405, {
        petId: UpdatePetWithFormPathParams["petId"];
        data?: UpdatePetWithFormMutationRequest;
        params?: UpdatePetWithFormQueryParams;
    }>;
    client?: Partial<RequestConfig<UpdatePetWithFormMutationRequest>>;
} = {}) {
    const { mutation: mutationOptions, client: config = {} } = options ?? {};
    const mutationKey = mutationOptions?.mutationKey ?? updatePetWithFormMutationKey();
    const mutation = useMutation({
        mutationFn: async ({ petId, data, params }: {
            petId: UpdatePetWithFormPathParams["petId"];
            data?: UpdatePetWithFormMutationRequest;
            params?: UpdatePetWithFormQueryParams;
        }) => {
            return updatePetWithForm(petId, data, params, config);
        },
        ...mutationOptions
    }) as UseMutationResult<UpdatePetWithFormMutationResponse, UpdatePetWithForm405> & {
        mutationKey: MutationKey;
    };
    mutation.mutationKey = mutationKey as MutationKey;
    return mutation;
}

@stijnvanhulle Using url of mutation path looks good. After all, mutation is not cached. I don't think including parameters in the keys is necessary.


Add back ref_type field to payloads

Thanks!
On Thu, Jan 14, 2016, 12:43 AM Bernat Borrás Paronella <
<EMAIL_ADDRESS>wrote:

Merged #46 https://github.com/gitskarios/GithubAndroidSdk/pull/46.
—
Reply to this email directly or view it on GitHub
https://github.com/gitskarios/GithubAndroidSdk/pull/46#event-514706689.


how to handle django login page from vuejs ?

hi,
I followed your project structure. I would like to know how we can use allauth templates from vuejs components ?

if you want use the django auth, you can try the DRF, because the vuejs usually use the json  to transport data
Content-Type:application/json

@gagansuntle Now you can use the DRF auth view.


enable PT-PT translation in crowdin

following on @SooluThomas ' instructions here
Did you find a doc bug or broken link that needs to be fixed?

What is the file name(s) where you found the bug?

What is the current text that needs to be fixed or removed? (You can copy and paste)

What should the documentation say instead?

Are there other related issues or pull requests about this bug?

Does existing documentation need to be updated with new content?

Which files need to be updated?
https://crowdin.com/project/qiskit-docs?
What content needs to be updated or replaced? (You can copy and paste)
currently there is only option to contribute to JA.
What new content needs to be added?
support for translation to PT-PT

Thank you @derivation and @SooluThomas .


[FLINK-21027][state] Introduce KeyedStateBackend#isSafeToReuseState for opmitization hint

What is the purpose of the change
Introduce KeyedStateBackend#isSafeToReuseState for opmitization hint.
Brief change log
Introduce new KeyedStateBackend#isSafeToReuseState API.
Verifying this change
This change added tests and can be verified as follows:

Added unit test of StateBackendTestBase#testIsSafeToReuseState
Remove StateConfigUtilTest.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure


Fix generating unique component id

Date.now().toString(36) - this fail to generate unique component id when asynchronously calling component install. I added additional randomness to id generation which fix the issue.

Hi @alaminopu. Thank you, yes ... this is good fix!


Unable to change SSH settings : Virtual Arrow Keys & Read Buffer Size

Describe the bug
The press on these rows doesn't do anything 😤

Now fixed : https://testflight.apple.com/join/QSrBK59z

With build above I see this: but nothing happens when I tap on "Pad" or "Fast"

Hello @mbierman 👋
Latest release should work :

Which release version are you using?

Yes, works now!


Receiving this error too frequently while running tests - This socket has been ended by the other party

Current behavior
When I run my tests from feature files and there are some 5 different features.
All of them do run in sequentially, this error which I mentioned below stops my execution and everything is skipped!
Receiving this below error:
This socket has been ended by the other party
Error: This socket has been ended by the other party
at TLSSocket.writeAfterFIN [as write] (node:net:541:14)
at IncomingMessage.ondata (node:internal/streams/readable:766:22)
at IncomingMessage.emit (node:events:513:28)
at addChunk (node:internal/streams/readable:324:12)
at readableAddChunk (node:internal/streams/readable:297:9)
at Readable.push (node:internal/streams/readable:234:10)
at HTTPParser.parserOnBody (node:_http_common:131:24)
at TLSSocket.socketOnData (node:_http_client:542:22)
at TLSSocket.emit (node:events:513:28)
at addChunk (node:internal/streams/readable:324:12)
at readableAddChunk (node:internal/streams/readable:297:9)
at Readable.push (node:internal/streams/readable:234:10)
at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)
Desired behavior
While running tests the execution should not be blocked because of this issue, this issue is very random and common
Test code to reproduce

Versions

Cypress version: 13.6.2
Preprocessor version: 18.0.4
Node version: 18+

Checklist

[ ] I've read the FAQ.
[ ] I've read instructions for logging issues.
[ ] I'm not using<EMAIL_ADDRESS>(package name has changed and it is no longer the most recent version, see #689).

Omitting to fill out the template properly is completely inappropriate. You need to provide reproducible examples to your issues.

Hi @badeball , can we talk or chat, as this is troubling me a lot, Need your guidance on this!

No, I'm afraid I don't provide any support beyond this issue tracker.


Update typeref_decoding_asan.swift

Update 'typeref_decoding_asan.swift' as a result of SR-10341 on ppc64le.

@compnerd @dcci Please review and approve.

I think that you should do a bit more investigation into why this is failing.  This is trying to construct a string from a NUL value which is incorrect.  The question is what is that string and why is it being constructed in an invalid way.

Hi @compnerd
I have built swift toolchain in release mode as debug build runs out of space (needs more than 80GB space and 6 hrs of build time).
However I did manage to debug to a certain extent using print statements in file ReflectionContext.h and this is what I found:-

The code flow crashes while accessing 'StrTab' variable at the following statement while constructing std::string in file 'ReflectionContext.h:455' inside "function bool readELFSections(RemoteAddress ImageStart)":-
auto SecName = std::string(StrTab + Offset);

Following is the error thrown:-
terminate called after throwing an instance of 'std::logic_error'
what():  basic_string::_M_construct null not valid

I tried printing the value of StrTab, however as expected, it crashes at that step too.

"StrTabBuf.get()" which is used to construct variable 'StrTab' prints 0

Can anyone explain what this piece of code is trying to do? I tried going through the code in the stack trace, however I am not well versed with the finer details of the code and will require help from swift community. Anyone you could point me to who can guide me on this and help fix this issue?

It is just reading the image.  The string table should be present in the binary.  I would try to figure out why that is missing.

It is just reading the image. The string table should be present in the binary. I would try to figure out why that is missing.

Thanks @compnerd , please do let me know.

I meant that you should try to figure out why StrTab is 0.  This unfortunately requires the build output to diagnose.

Can one of the admins verify this patch?

I'm going to close this out due to age and inactivity. The PR's contents appear to have changed significantly as well.


fix: highlight words per occurrence

Currently the word highlighter highlights all occurrences of the word in the wordNumbers lines.
E.g /word/1,3  highlights word in lines 1 and 3
The correct behaviour is to highlight the first and 3rd occurrence of 'word', regardless of line.

fix options.wordCounter to increase per occurrence of word instead of per line

also changed to a map to work easier with the multiple words feature

mark as visited but don't wrap word occurrences that aren't in the wordNumbers range

we still need to do the processing in the while loop to get the right node indexes, so just avoid splitting or wrapping the node when it should be ignored

I guess this is a breaking change, even if the current behaviour is incorrect according to the docs.
Edit: thought I had rebased but apparently not... I think I've understood what the multi word feature should do, and looks to be working with these changes.

closes #57

Great thanks!


make design for scheduler written in Python + C and worker written in Python

The purpose of this task is to evaluate feasibility of Python as a language
for scheduler logic and worker logic

The task

design scheduler logic
design C and Python interfaces between C part of the scheduler and Python
part of the scheduler
design worker logic
design communication interface between scheduler and worker
design persistent state machines for scheduler
design FDMI record persistence & deduplication on scheduler
get all designs reviewed

Definition of done

designs from the list above are available for review
designs from the list above are reviewed

Work in progress: https://github.com/Seagate/cortx-multisite/blob/main/doc/replication.rst and https://github.com/Seagate/cortx-multisite/blob/main/doc/replication-dld.rst.

Donald R Bloyer commented in Jira Server:

[~532357] [~744292] [~720600]
This appears to be looking at some decisions about replication design.  Is this inherently resolved with RGW?  I assume this functionality already exists there?  or we still have to add this worker/scheduler capability?

Ujjwal Lanjewar commented in Jira Server:

In the current form, this ticket is invalid as it depends on legacy S3 design. This may need to redesigned with RGW differently.

Ujjwal Lanjewar commented in Jira Server:

{quote}why would we need to evaluate the best language if it already exists in RGW?
{quote}
Yes, this is the reason, I mentioned that this ticket is invalid and needs to be relooked/redesign. RGW does not have python and like this may already be there in C++. RGW has threads unlike legacy S3 server with multiple processes.

Donald R Bloyer commented in Jira Server:

[~720600] [~533453]
Does this already exist in RGW (this scheduler function this appears to be referring to)?  If so, we should close this as no work or something as it already exists in RGW

Chetan Deshmukh commented in Jira Server:

we should close it, for reasons given by Ujjwal already, doesnt apply in RGW

Donald R Bloyer commented in Jira Server:

[~533453]  I think what you are saying is that the language decision is already de facto as we are using RGW (ie C++)
[~535110] this ticket is unassigned from Board Genius.  I do not know what protocol we used to assign this for someone to close?  Would this be closed by Ruth or someone?  I assigned to you in the interim.

Chetan Deshmukh commented in Jira Server:

{quote} I think what you are saying is that the language decision is already de facto as we are using RGW (ie C++)
{quote}
yes [~211146]

Closing as an obsolete


Default selected GPU is not faster presented in system.

Getting an error in caffe ( https://github.com/BVLC/caffe/pull/2195#issuecomment-148927253 ) I have added some debug output to xgemm.cc and also got info about used device
Name:				Devastator
Vendor:				Advanced Micro Devices, Inc.
Available:			Yes
Compute Units:			4
Clock Frequency:		760 mHz
Global Memory:			570 mb
Max Allocateable Memory:	142 mb
Local Memory:			32768 kb
But according to my clinfo https://gist.github.com/inferrna/f183896a683ba773e3b4 I have more powerful device Pitcairn which was not selected.
As I found in src/library/blas/AutoGemm/AutoGemmTools/ProfileAutoGemm.cpp
    device = NULL;
    for (i = 0; i < nrDevices; i++) {
        err = clGetDeviceInfo(list[i], CL_DEVICE_NAME,
            sizeof(deviceName), deviceName, NULL);
        CL_CHECK(err);
        assert(err == CL_SUCCESS);
        if ((err == CL_SUCCESS) ) {
            device = list[i];
            break;
        }
    }

it just selects first available device. May be it would be better to select most powerful device, for example by comparing value of compute_units*clock_frequency.

Actually it is more complicated than simply looking at the peak performance of a card. For example the current implementation runs most efficient on Hawaii architecture with OpenCL 2.0 run time.
Anyway you can use the environment variable GPU_DEVICE_ORDINAL to mask you OpenCL device. If you set GPU_DEVICE_ORDINAL=1, device 0 will be masked out.

Actually it is more complicated than simply looking at the peak performance of a card.
Simply looking at the peak performance of a card is little more complicated than just selecting first GPU in list.
Using system variables may be an solution but I can't find GPU_DEVICE_ORDINAL in source code. Is it clBLAS variable or it usable only with AMD driver?


Preview Does Not Change After Generating Template Preview

Steps to Reproduce

Select File -> Open Template
Select Plain Cover Letter
Open the PDF Preview window if it's not open and check that the PDF preview for the template has been generated.
Select File -> Open File
Open a .tex file.  Notice that the PDF preview does not change.
Close Open Latex Studio
Start Open Latex Studio
Notice that the PDF Preview for welcome.tex is not generated.

Actual Result
After generating a PDF preview for a template, the preview does not update after opening a new file or restarting Open Latex Studio.
Expected Result
PDF previews should be generated normally after opening a template.
**NOTE: To generate PDF previews normally again, I deleted the .OpenLaTeXStudio folder in my Users folder and restarted Open LaTeX Studio.

Happens on more than just templates.  Switching files isn't updating the PDF preview most of the time on my system. Will have to investigate once I can get the code built.

I've looked into this issue a little more, and here's what I've found:

After opening a document or template that uses the LaTeX Letter class, the preview will not change unless a document that also uses the Letter class is opened.  Basically, once a Letter document is opened, only Letter previews will be generated.

The preview also locks up when the Multi-Purpose Title Page template is opened.

I'm able to force the previews to work normally again by deleting the preview.aux file.  So, a possible solution to this issue would be to delete the preview.aux file when a new file is opened.  Does anyone have any more insight into this?


add tip about nodenv permissions

Why:

What's being changed:

Check off the following:

[ ] All of the tests are passing.
[ ] I have reviewed my changes in staging.
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

Make "Spell Check" is consistent.


Can't create issue report via desktop app

I'm using macOS desktop app v2.8. Wanted to report an issue (tried couple of time, also restarted app couple of time), but all the time getting "Could not submit" message.

It could be related with github timeouts.

Here are logs of app state when I was not able to send logs via report log feature in desktop app (macOS, v2.10.1).
renderer.log
main.log

Uploading mysterium-node.log…
Uploading myst_supervisor.log…


Question on ./model/dgaf.py

Good job! Thank you for your excellent work!
I have a question about the Kernel Generation, i.e., what the meaning of the following code in the FuseBlock module.

    fuse_kernel = torch.tanh(fuse_kernel) / (self.aff_scale_const + 1e-8)

   abs_kernel = torch.abs(fuse_kernel)

   abs_kernel_sum = torch.sum(abs_kernel, dim=1, keepdim=True) + 1e-4

    abs_kernel_sum[abs_kernel_sum < 1.0] = 1.0

    fuse_kernel = fuse_kernel / abs_kernel_sum

Could you please provide more information about this? Thank you for your kind consideration of this request.

Hello, thank you for attention,
Its function is to let the sum of the learned kernel weights to one, i.e.,  \sum_{i=1}^{k^2} w_1 = 1

Thanks for your answer.
I have one more question, i.e.,  why use this form for kernel normalization rather than softmax functions? What is the physical meaning of this form?

Hello,
The kernel normalization is a common way for the guided filter, and you can use any kind of function (e.g., softmax) you like to achieve this goal.  I suggest that you read some papers about guided filters to find more reasonable explanations.
Best regards,
Zhiwei Zhong

If you have any questions you can send me an email<EMAIL_ADDRESS>or add my WeChat for more convenient communication.
Thanks.


Create docs for using wikitude plugin in the dev app

Work being currently done here: https://github.com/phonegap/phonegap-docs/tree/wikitude

Published now and lives here: http://docs.phonegap.com/tutorials/develop/wikitude/


luci-app-package-manager: support new APK repositories.d configs

Support new APK repositories.d configs following OPKG was to better split distfeeds and customfeeds.
Support for ""legacy"" repositories is kept to support migration period and to support custom scenario where user use this file instead.

Seems to work.
I built a test build with this included, and editing both files works ok.

Think this should be merged ASAP if everyone is ok with the format for the additional 2 files...
I didn't want to complicate this too much with introducing logic to list files in directory (as that would also list files in the keys directory and is a security risk)

Yeah, like I said yesterday, looks good.
Just merge it.


Tidy up submit_windowed_post()

Summary of changes
Changes introduced in this pull request:

Fixed outdated comments see this PR
Adjusted code to match Lotus more cleanly (there is no functional change just reads cleaner)

Reference issue to close (if applicable)

Closes n/a
Other information and links

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

Note: cargo clippy fails from files outside of what I touched I believe due to a new version of clippy adding extra conditions.
I'm happy to fix it in this commit but don't want to overlap if it's being fixed in another commit.

@kirk-baird That's right, new clippy, new warnings 😵
It was fixed in a recent commit https://github.com/ChainSafe/forest/pull/1098/commits/b4215f7c32971a37dabead4ef2beb1491d07ee6c
Just pull main into here and the Earth should start rotating again 😄

It was fixed in a recent commit b4215f7
Just pull main into here and the Earth should start rotating again

Looks like that commit hasn't been merged into main yet :( and I'm not sure which fork it is on.


Subnet Delegation without name property Results in InvalidRequestFormat Error

Bicep version
Bicep CLI version 0.31.92 (b06509316a)
Describe the bug
When deploying subnets in a loop using an array, I want to enable subnet delegation for a specific subnet based on a condition. However, the deployment fails with an error indicating a null value for item.name which is definitely not true, because when I comment out the delegation part with the condition, the subnet creates without any issues.
I expect only one subnet with a name containing db should have delegation enabled.
All other subnets should be deployed without delegation.
To Reproduce
Steps to reproduce the behavior:

Define an array of subnet configurations like this: [{"name":"xxx","prefix":"<IP_ADDRESS>/28"},{...},...]
Add a condition to enable delegation for subnets whose name contains 'db':

resource subnet 'Microsoft.Network/virtualNetworks/subnets@2024-03-01' = [
  for item in subnets: {
    parent: vnet
    name: '${item.name}-subnet'
    properties: {
      addressPrefixes: [
        item.prefix
      ]
      networkSecurityGroup: {
        id: resourceId('Microsoft.Network/networkSecurityGroups', '${item.name}-nsg')
      }
      delegations: (contains(item.name, 'db')
        ? [
            {
              properties: {
                serviceName: 'Microsoft.DBforMySQL/flexibleServers'
              }
            }
          ]
        : [])
      privateEndpointNetworkPolicies: 'Enabled'
      privateLinkServiceNetworkPolicies: 'Enabled'
    }
  }
]

Deploy the template using the condition above.

The deployment fails with the error:
{"code":"InvalidRequestFormat","message":"System.ArgumentException: item.Name is null"}

The Azure Portal also displays the error:
{"code":"InvalidRequestFormat","message":"Cannot parse the request."}

Whether a property is required or optional is determined by the resource provider's service model. Transferring this issue to the bicep-types-az repo so we can ask the service team to update this upstream of Bicep.


bug fix: fissile build error when commit_hash is a scientific format string

This PR is to fix issue : https://github.com/SUSE/fissile/issues/383

We were thinking of updating the yaml library for this, but it turns out this works fine too

Isn't this better than the updated yaml library? Because this should also work for purely numeric hashes, which would still get the wrong type even with the updated yaml library.

@mook-as updated the PR.


Individual Ingress rules per service/helm chart

This PR splits the single ingress rule that exposes the catalogservice and the healthservice that currently exist only in the catalogservice helm chart into individual ingress rules per service, packaged together with the service in individual helm charts. See discussion in PR #351 for more details.

One example from a recent sample implementation:

Each API has its own helm chart with its own ingress(.yaml) definition.

They all use the same ingress controller / fqdn and all of them share the same certificate:

The current schema here is /catalogservice/api/* and /healthservice/api/* wouldn't it be easier if we'd switch to /api/healthservice/* and /api/catalogservice/*.

The current schema here is /catalogservice/api/* and /healthservice/api/* wouldn't it be easier if we'd switch to /api/healthservice/* and /api/catalogservice/*.

@sebader do we want to consolidate all APIs under /api as part of this PR? Currently all APIs are hosted on AKS and this would reduce the need to modify the FD config when APIs are changed, removed or added. Like in the diagram shared above:

Removing /api from the default route is an easy thing and it will make things more logical (which I realized last week too, trying to figure out what the correct route is without looking :D). So I support that.

Removing /api from the default route is easy and it will make things more logical (which I realized last week too, trying to figure out what the correct route is without looking :D). So I support that.

hm, I just started to do that in the code when I realized: It actually is not that easy. Because then we are back in reverse procxy rewrite hell :(

Seems to work.. https://dev.azure.com/Mission-Critical/Online/_build/results?buildId=1547&view=results

lets just once more deploy it on a fresh branch so that we get a brand new cert

before we do that let me parameterize a few more things


Add method to get access to error text

Original author: tfmorris (January 26, 2012 21:30:45)
In cases where the EvalError.message contains useful information (e.g. the error returned from a URL fetch), there's currently no way to get access to it.
I propose adding a new pseudofield to Cell which, if the Cell contains an EvalError, will return EvalError.message instead of the EvalError itself (which can not be evaluated in the normal manner).
The proposed name is "error" which would make the GREL syntax:
cell.error
The value field (i.e. cell.value) would continue to return the error object.
Original issue: http://code.google.com/p/google-refine/issues/detail?id=525

@thadguidry & @wetneb: here, what we are returning is more an errorMessage than an error (which would be the object that we already have, and that some day, we might also want).
I believe it's still time to correct that…
What do you think?
Regards,
Antoine

@antoine2711 Hi, sorry I've been away for about a week or so.
Hmm, the main use case we have always heard was that of being able to easily surface HTTP errors, even to the point of actually parsing our the HTTP error codes themselves.  I've heard this numerous times as a wishlist from lots of data journalists in newsrooms and librarians that use OpenRefine against APIs in-house and through subscription services they use.  So that's the primary driving use case, really around Fetch URLs (HTTP) error reporting, so that they can re-run the Fetch for those that were missed etc. for only those with certain error codes, message text contains, etc.
It's not the only case for surfacing error messages however.  But I cannot off the top of my head think of other OpenRefine operations other than HTTP inclusive of Recon.
Then there's the case of OpenRefine extensions later on, also being able to produce error types in cells and this issue should still allow GREL to easily extract those, the idea being able to extract fields from an "error" object stored in a cell.  That's the high-level ask that I have heard time and again.
HTTP operations certainly need improvement as well to support the underlying ease of error surfacing.  Such as our issue to improve our HTTP handling by moving to OKHttp client, etc.
How to make error object field extract easy for our users is the challenge.  Thinking more about that...
What fields in Java custom "error" object do we setup to store?  error code, error message, error type, what else? Or instead should an "error" object simply be stored instead as pure JSON and then ANYTHING is possible even for extensions that want to utilize the "error" JSON object and populate it as needed into cells?
But my personal preference for various reasons, not the least of which is flexibility long-term, and just flip our existing "error" object handling into JSON.  And when you ask GREL for cell.error it returns a complete JSON object that can then be parsed further with existing GREL JSON functions, or we might later decide to be really nice and provide at least the 3 basic fields of "error type", "error code", "error message" and bake that into Fetch URLs and Recon for starters.
...that's all up to you guys.

Hi @thadguidry, what you wrote is interesting, but this issue here is about returning the text of the error() function.
All that you mentioned in you comment, is worthy I think, at least of a good discussion. But it's out of the scoop of this issue and my comment.
Right now, if we go on with error() that returns a string, it will be breaking in the futur if we want to implement error() that returns an object.
Today, I would just change the name of this « field » to errorMessage(). It leaves the door opened to all that you talked about while still gaining this current functionality.
Regards,
Antoine

@antoine2711 So you feel there should be 2 kinds of accessible errors that can be stored in a cell.  EvalError and...?
What I am proposing is that ALL accessible errors can be stored as 1 kind... JSON.  We introduced cell.error recently with that merge, yes, I understand...but I would have designed that differently, to treat all errors to be stored as JSON as there are multiple benefits around that for users and extension authors.

@antoine2711 So you feel there should be 2 kinds of accessible errors that can be stored in a cell. EvalError and...?

Not at all. What I'm saying here is EvalError.message should be returned by errorMessage(), not error().

What I am proposing is that ALL accessible errors can be stored as 1 kind... JSON. We introduced cell.error recently with that merge, yes, I understand...but I would have designed that differently, to treat all errors to be stored as JSON as there are multiple benefits around that for users and extension authors.

I think all this discussion should be a new issue by itself. Something broad like « Give a rich and complete access to errors in OpenRefine ». For the particular question of returning an object or a json object, I would not « object » to neither (there's a pun just for you! ;-) ), I would return an object error with error.toJson() that would give you your JSON object. In my dreams, you could also write columns.Col1.toJson(), which would return the whole column in JSON, with errors also expressed in JSON.
Regards, Antoine

Yes cell.errorMessage() would be a better name for this.

@zengchu2: do you want to make the change? I can do it if you prefer.
Regards, A.

@zengchu2: do you want to make the change? I can do it if you prefer.
Regards, A.

I am occupied with some other stuff these days, it will be great if you can help me with this !

It's a variable, not a function (ie cell.error, not cell.error()).
I don't want to get into too much bikeshedding, but verbose camel case (cell.errorMessage) doesn't really fit with the current variable naming stylistically.  errmsg? message?
Whatever it gets called, it needs to be documented in the help.

Whoever takes it up, please link it to this issue so that it gets closed when the fix is merged this time.

It's a variable, not a function (ie cell.error, not cell.error()).

Thank you for this clarification. I corrected myself in this issue.

I don't want to get into too much bikeshedding, but verbose camel case (cell.errorMessage) doesn't really fit with the current variable naming stylistically.  errmsg? message?
Whatever it gets called, it needs to be documented in the help.

Of course, all of this will be documented in our new documentation system.
For the « camel case », I see a lot of columnNames, typeMatch, nameMatch, nameLevenshtein, nameWordDistance, toRowIndex and fromRowIndex.
What would be our alternative?
Regards,
Antoine

I am occupied with some other stuff these days, it will be great if you can help me with this !

@zengchu2: sure mate! Thanks for the fast answer.
Regards, A.


MRU OP Files

you need to modify this method so that it is backward compatible by checking for MRUOPFileList
== null and if null, initializing MRUOPFileList:
public List<String> getMRUOPFileList() {
        return MRUOPFileList;
    }

ditto for
public String getMRUOPFileFolderPath()


Need to include namespace, BlankPage, IBlankPage, IBlankPageProtected etc possible self-referencing projection types when replacing .g.h for clean build

Namespace can be grabbed by regex. Make it support only 1 namespace per file is a good default.

Encounter an issue in test data which in essence is the same problem as #71: creating dummy types of these types would produce redefinition if the header include other implementation type. Those implementation type headers are still referencing .g.h, which includes all those existing types.
In theory, since during bootstrap midl content would be replaced with a dummy namespace, in a clean build this issues shouldn't exist. But a long term solution is to duplicate cppwinrt's work and generate a single header which include all these types...It seems forking cppwinrt to add a generation mode without class body is easier?

Tested in sample app, generating fake projected types is indeed OK. But also encountered another systematic issues where authored enum etc don't have their projected types generated yet.
A complete solution likely involve:

For all in-project component types, generate fake-projected types in .idlgen.h during bootstrap
For library types, keep using CppWinRTMake(Static|Ref)Projection (just skip component projection)
Since idlgen cannot easily modify included headers' .g.h, replacing actual content of all existing .g.h during bootstrap
After IdlgenCppGenerateIDL, replace .g.h to the original content

Conceptually, this is just extending what idlgen currently does to a single file in memory, to all files in a pre-pass in .idlgen.h.

Should just create $(IntDir)idlgen/Generated Files and put everything there and pass this dir to idlgen when generating IDL instead of renaming back and forth.
Just like cppwinrt works by (a) midl -> mdmerge, we work by generating (Class|Enum|other).g.h for both projected and impl types -> merge in $RootNamespace.h for projected types

Even better, we could generate fake projection by generating initial idl, and rely on cppwinrt to generate the projection. The problem of modifying the projection thus becomes a problem of modifying idl. This also eliminates the problem of mixing real projection and fake projection - there is simply no fake projection anymore. We only have bootstrapping idl.
We still have --gen-fake-projection option, but it

would be renamed to --gen-bootstrap-idl
supersede IdlgenCppClearMidl
generates midl entites with empty body (e.g. runtime class definition without any properties/methods/events)

Encountered the following limitation:

IProtected and IStatics cannot be generated, and any attempt to generate them would reproduce definition removal issue
Enum etc cannot be referenced directly in header. It's kind of fine as they cannot be inlined anyways (from a projection, this is indeed a limitation if devs can access the implementation type).
Xaml generated header *.xaml.g.h isn't generated

Good news is defining multiple class in the same header indeed just works™ (provided that you included all the boilerplate of factory impl, include .g.cpp, etc).
So if I found the build task for generating xaml.g.h and add that as dependency before IdlgenCppGenerateIDL, we should be all set. I wonder if vanilla XAML project works here?

So the target to generate .xaml.g.h etc is actually MarkupCompilePass1, adding that target and generate xaml.g.h and clean build is fixed :tada:
...But then I encountered the same "building from cli doesn't work" issue 🤦 Already using VS 2022 dev shell. Investigating...


Chrome thinks your file is sus.

Title.

(No Issue template is provided don't get mad at me.)

This program is being built automatically using actions, however if you don't trust it you can always upload it to virustotal or build it yourself.

This program is being built automatically using actions, however if you don't trust it you can always build it yourself.


Implement custom validator annotation for the date in HistoryRequestDTO

Summary

@FitBuddyDate default validation error message use the message fitbuddy.validation.message.invaliddate in application.properties
FitBuddyDateValidator class is using injected fitbuddy.validation.pattern.date message as date pattern for the validation (by default yyyy-MM-dd). Made the injection via constructor, I think it's a good way (for testing the validator class in the future perhaps)
Uncommented HistoryControllerTest tests are still passing.

Close issue(s)
Closes #131

@mepox You're right about creation the DateTimeFormatter object everytime, big mistake from my side.
Fixed two issues, could you review?

@dmitriydb Thanks for applying the changes. All looks good to me. This will be merged soon 🎉


Added support for localized questions, responses, demographics.

Added getLocaleResource method to helperMethods.js to extract localized
string or array from a JSON object. For backwards compatibility the
method recognizes if the object property hasn't been localized, i.e.
it's a string or an array.
Modified code to call getLocaleResource when reading json file objects
from the profile folder including demographic questions, survey
questions, section descriptions and home page text.
Added section to README.md for Localization.
Created unit tests for getLocaleResource method.

Will resubmit based on current master branch code line


#137: Upgrading container to v0.26.0 of BookStack

Hey @tylwright,
could you rebase against master. I had finally time to do all the missing old stuff. I would really appreciate if you rebase against.
Your current pr is looking good for me. I'll also update the others.

Will do.  One second.


Fix issues around tlsRedirect (#29895)

Fix issues around tlsRedirect

Fixes https://github.com/istio/istio/issues/27315

Fixes https://github.com/istio/istio/issues/27157

This partially reverts https://github.com/istio/istio/pull/24958. This
PR did two things - allow using httpsRedirect without VirtualServices
(good) and remove all routes when using httpsRedirect (bad). The latter
breaks in two cases: when a user has an HTTPS server and they put
httpsRedirect, it previously was silently ignored - after the PR, all
the routes were dropped. With this change, these routes are added, and
users will get a warning at validation time since the config is not
useful.
The other case is that a user can have an HTTP server but still "bypass"
the httpsRedirect with X-Forward-Proto and num_trusted_hops, so removing
the routes breaks this.
Both of these cases have unit and integration tests.
Additionally, the original PR indirectly caused httpsRedirect=true to
take precedence during Gateway conflicts. Previously, the last gateway
won, which caused weird behavior. I kept the behavior of the original PR
here; during conflict we will keep the httpsRedirect. This isn't ideal,
since it interferes with cert-manager ACME requests. Longer term we will
want to make httpsRedirect per-route most likely. See
https://github.com/istio/istio/issues/27643#issuecomment-755755760 for
more info.

note

Fixes

fix lint

fix echo

(cherry picked from commit 56d740a174df19204dea4962295c2e6ea44d77e3)
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test lint_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test lint_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test lint_istio_release-1.8

gencheck_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test gencheck_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test lint_istio_release-1.8

gencheck_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test gencheck_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test lint_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
f496053248e830b90b7e51d1e93283510e3fc094
link
/test integ-telemetry-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.8
de7200a09e2ba36241ba62ff4d9e6a58d412d65b
link
/test lint_istio_release-1.8

integ-telemetry-k8s-tests_istio_release-1.8
f496053248e830b90b7e51d1e93283510e3fc094
link
/test integ-telemetry-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio_release-1.8
f496053248e830b90b7e51d1e93283510e3fc094
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-security-multicluster-tests_istio_release-1.8
f496053248e830b90b7e51d1e93283510e3fc094
link
/test integ-security-multicluster-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio_release-1.8
f496053248e830b90b7e51d1e93283510e3fc094
link
/test integ-telemetry-k8s-tests_istio_release-1.8

integ-security-multicluster-tests_istio_release-1.8
f496053248e830b90b7e51d1e93283510e3fc094
link
/test integ-security-multicluster-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest


Session management

In GitLab by @jakebeal on Jul 15, 2019, 10:22
Per the discussion in #65, #66, #67, we need to have a way to track whether a session is in progress or not and to garbage collect terminated sessions.  The most likely way to implement this is going to be with a heart-beat, based on @nwalczak's observations so far.

In GitLab by @nwalczak on Jul 17, 2019, 10:42
created branch 74-session-management

In GitLab by @nwalczak on Jul 17, 2019, 10:42
mentioned in merge request !26

In GitLab by @nwalczak on Jul 23, 2019, 11:29
closed via merge request !26

In GitLab by @nwalczak on Jul 23, 2019, 11:29
closed via commit b4f3d0ac210094f3ab3aaa3e2af147ca0267796c


[TypeScript] Remove template literal to compat with minimum required version

closes #33558
Typescript version <4.1.5 throws an error in 2 places that use template literal types but the minimum Typescript MUI requires is 3.5.
Changes

Grid2
Replace the template literal types with GridPropsOffsetOverrides in the system grid. For custom breakpoints, developers need to augment the offset props like this:
// System
declare module "@mui/system/Unstable_Grid" {
  interface GridPropsOffsetOverrides {
    mobileOffset: true; // adds the `mobile` breakpoint
    tabletOffset: true;
    laptopOffset: true;
    desktopOffset: true;
  }
}

// Material UI
declare module "@mui/material/Unstable_Grid2" {
  interface GridPropsOffsetOverrides {
    mobileOffset: true; // adds the `mobile` breakpoint
    tabletOffset: true;
    laptopOffset: true;
    desktopOffset: true;
  }
}

// Joy UI
declare module "@mui/joy/Grid" {
  interface GridPropsOffsetOverrides {
    mobileOffset: true; // adds the `mobile` breakpoint
    tabletOffset: true;
    laptopOffset: true;
    desktopOffset: true;
  }
}

experimental_extendTheme: Move the template literal to themeCssVarsAugmentation file, so that it does not break the app if it does not use CSS theme variables feature.

This is still an open question, is it okay for the experimental feature to require a higher TypeScript version? cc @mui/core
Test
I have tested with the CodeSandbox packages and it does not break the build anymore.

[x] I have followed (at least) the PR section of the contributing guide.

experimental_extendTheme: Move the template literal to themeCssVarsAugmentation file, so that it does not break the app if it does not use CSS theme variables feature.

This is still an open question, is it okay for the experimental feature to require a higher TypeScript version? cc https://github.com/orgs/mui/teams/core

Could we support this via module augmentation import?


[Splittermond] Fixing importer bug

Changes / Comments

I fixed a bug where after a JSON character import the character had a full damage modifier.

Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[X] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

something's fishy here


Inventory notification

Your tool/software has been inventoried on Rawsec's CyberSecurity Inventory.
https://inventory.rawsec.ml/tools.html#fireELF
What is Rawsec's CyberSecurity Inventory?
An inventory of tools and resources about CyberSecurity. This inventory aims to help people to find everything related to CyberSecurity.

Open source: Every information is available and up to date. If an information is missing or deprecated, you are invited to (help us).
Practical: Content is categorized and table formatted, allowing to search, browse, sort and filter.
Fast: Using static and client side technologies resulting in fast browsing.
Rich tables: search, sort, browse, filter, clear
Fancy informational popups
Badges / Shields
Static API
Twitter bot

More details about features here.
Note: the inventory is a FLOSS (Free, Libre and Open-Source Software) project.
Why?

Specialized websites: Some websites are referencing tools but additional information is not available or browsable. Make additional searches take time.
Curated lists: Curated lists are not very exhaustive, up to date or browsable and are very topic related.
Search engines: Search engines sometimes does find nothing, some tools or resources are too unknown or non-referenced. These is where crowdsourcing is better than robots.

Why should you care about being inventoried?
Mainly because this is giving visibility to your tool, more and more people are using the Rawsec's CyberSecurity Inventory, this helps them find what they need.
Badges
The badge shows to your community that your are inventoried. This also shows you care about your project and want it growing, that your tool is not an abandonware.
Feel free to claim your badge here: http://inventory.rawsec.ml/features.html#badges, it looks like that , but there are several styles available.
Want to thank us?
If you want to thank us, you can help make the project better known by tweeting about it! For example:
So what?
That's all, this message is just to notify you if you care.

ok

Rawsec's CyberSecurity Inventory.

This is now a scam site lmao

The domain was stolen, @SandroMartens the official domain now is https://inventory.raw.pm/


Developer setup inst. main/master?

Seeing that the project has switched to "main" as default now, the current developer setup steps start out as:

git remote add upstream https://github.com/pypa/warehouse.git
git checkout master
git fetch upstream
git merge upstream/master

Should master be changed to main here?

Yes! Thanks for raising the issue.

I have completed most of the changes to the documents with exception of the historical section. Some of the links in the historical section do not appear to be valid links anymore.
I am trying to work through one issue with a change that gives a warning, treated as an error when I run make docs.

I ref #9095, somehow posted the pull request  to #9095 instead of here.


[SPARK-4819] Remove Guava's "Optional" from public API - WIP

Just an example to use Scala Option to replace Guava Optional. I'm actually not sure whether this is the best option since it breaks source compatibility beyond "import".

cc @srowen  -- if we use Scala's Option, I think we can just recommend users to use get and isDefined.

Test build #48426 has started for PR 10512 at commit 49ca121.

Yes that's viable too. I was just prepping something very similar but with an inlined clone of Java 8 Optional, on the theory that's next-most-Java-like. https://github.com/apache/spark/pull/10513

Test build #48426 has finished for PR 10512 at commit 49ca121.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48426/
Test FAILed.

Going to close this one since I was only posting it for demo.


[MM-27827] Cypress test for MM-T1190 - Terms of service appears after verifying email

Summary

Adds a cypress test to ensure the custom terms of service appears after verifying the email

Ticket Link

https://mattermost.atlassian.net/browse/MM-27827
Test link: https://mattermost.atlassian.net/projects/MM?selectedItem=com.atlassian.plugins.atlassian-connect-plugin%3Acom.kanoah.test-manager__main-project-page#!/testCase/MM-T1190

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.


MDX variable headings display badly in TOC

What version of starlight are you using?
0.7.3
What version of astro are you using?
2.10.5
What package manager are you using?
npm
What operating system are you using?
Mac
What browser are you using?
Safari
Describe the Bug
If I put a javascript variable as a heading in MDX, it looks fine on the page, but bad in the sidebar:
export const variableName = "Javascript heading";

## {variableName}

Results in Javascript heading written on the page, but variableName in the sidebar.

With a function that returns a string, it writes something like functionName in the sidebar - but again works well on the main page.
Link to Minimal Reproducible Example
https://stackblitz.com/edit/github-i3eo86?file=src%2Fcontent%2Fdocs%2Findex.mdx
Participation

[ ] I am willing to submit a pull request for this issue.

Thanks for the issue @VojtaStruhar! We rely on Astro's conversion of your content to a list of headings so will have to check with the team whether this is something they can fix upstream.
Will move this issue to the Astro repo for now as that is where we'd need to fix it.


Allow to wait for host to be ready

In many cases, more so when in a proxy, we need to wait and block until the proxy (using the WAF) is ready to accept requests.
The way we solved this in coraza-proxy-wasm is that we have a dedicated instruction running a curl and waiting for the host to be available. This is handy but not ideal as we have another piece of complexity for such a simple problem. Also in corporate envs, pulling an image isn't trivial and that is a friction.
I wish go-ftw allows to pass in a URL and it would wait until that URL returns 200.

Any input on this @fzipi ?

I don't think this makes sense. You mean the first time, in general, or what? This can be solved outside the tool, right?

Let me see if I get this clear:

there is a composer (or similar mechanism) that starts the waf and something else.
that something else takes (some) time to be up and ready.
the waf will answer some code, while that other container is not ready, that is NOT 200 OK.
what is expected if there is an error and the upstream never is ready?

If the upstream never gets ready it is pointless to run ftw so we just fail.
On Thu, 30 Mar 2023, 12:28 Felipe Zipitría, @.***>
wrote:

Let me see if I get this clear:

there is a composer (or similar mechanism) that starts the waf and
something else.
that something else takes (some) time to be up and ready.
the waf will answer some code, while that other container is not
ready, that is NOT 200 OK.
what is expected if there is an error and the upstream never is
ready?

—
Reply to this email directly, view it on GitHub
https://github.com/coreruleset/go-ftw/issues/142#issuecomment-1490064834,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAVX3LZ22R2K7JBNB2TW6VN43ANCNFSM6AAAAAAWANGUM4
.
You are receiving this because you authored the thread.Message ID:
@.***>


can not set the file name

https://github.com/PhilippKrone/react-native-fileupload/blob/master/android%2Fsrc%2Fmain%2Fjava%2Fcom%2Fyoloci%2Ffileupload%2FFileUploadModule.java#L116

@kazaff What exactly do you mean?


NullPointerException at DeviceInfo.java:66

SDK version: 7.2.1
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.net.NetworkCapabilities.hasTransport(int)' on a null object reference
       at com.inmobi.commons.core.utilities.b.b.b(DeviceInfo.java:66)
       at com.inmobi.commons.core.utilities.b.b.a(DeviceInfo.java:113)
       at com.inmobi.commons.core.b.d.a(EventProcessor.java:129)
       at com.inmobi.commons.core.b.d.a(EventProcessor.java:1084)
       at com.inmobi.b.a.a(TRCComponent.java:9142)
       at com.inmobi.b.a$1.run(TRCComponent.java:110)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:784)

Let me know if you need any more details.

Hey @mjurkus, thanks for reporting the issue.
Above issue is fixed in SDK version 7.2.2, you can go ahead and update your app with latest sdk version.


使用vqvae之后loss下降的非常缓慢，请问有参考的loss曲线吗？

OK, 那我等等

We also find this and report here. As a result, we choose a VAE from stability-ai to train our current models.


PPL - Less pin positions available than expected when using define_pin_shape_pattern

Describe the bug
This is a follow up to #4061, I know that it should have been fixed by #4071 but it doesn't seems to work even after pulling down the lastest commits and re-building OpenROAD.
I have a design whose core area is a bit more than 320um x 320um, my minimum pitch is 0.32 for the x/y axis so I expect to have 1000*1000 = 1 000 000 pin position available but OpenROAD tells me that it only has 13 568 pins positions available.
Just as info : I use OpenROAD-flow-script. To update OpenROAD I have gone in the OpenROAD-flow-scripts/tools/OpenROAD, used git checkout master then git pull, followed then by cd build and make. I even tried git submodule update --remote and git submodule update --remote --recursive, to see if it came from the use of submodule.
Building OpenROAD after pulling down the latest commits didn't seemed to fix the issue, I hope it isn't just a mishandling on my part...
Expected Behavior
Pin placement allowed due to sufficient pin locations.
Environment
Git commit:<PHONE_NUMBER>02e0f3f1561320096912cf84d688b4
kernel: Linux <IP_ADDRESS>-microsoft-standard-WSL2
os: Ubuntu 22.04.2 LTS (Jammy Jellyfish)

(Note that I just did another commit, but the build should be from the last commit from October 5th)

To Reproduce
TestCase.zip
Here should be every needed file to reproduce the issue. Create a TestCase directory in OpenROAD-flow-script/tools/OpenROAD/test/ and extract every file there. Open the gui with openroad -gui and enter source "ldpc4x4_asap7_bottom.tcl" in the TCL command box.
Relevant log output
No response
Screenshots
No response
Additional Context
I also noticed that the RAM usage could go as high as 15GB with the following test case (with 16GB allowed at maximum for the Linux VM), I don't know if it is normal or not.

@lustefan97 I'm having this error when running your attached test case during placement:
[ERROR GPL-0302] Use a higher -density or re-floorplan with a larger core area.
Given target density: 0.60
Suggested target density: 0.61

Could you add the log file where the number of available positions is reported? Do you see it in an error message or just in an INFO message?

@eder-matheus I don't think I even got to global placement, I was stuck in the (random) IO pin placement just before that.
I feel like it is an error on my part, where I failed to update OpenROAD... Just to be sure, in order to properly update OpenROAD, I just have to go into OpenROAD-flow-scripts/tools/OpenROAD/, use git checkout master then git pulland finally build OpenROAD again by going into OpenROAD/build/ and using make to compile everything back again.
I know that my files are up-to-date with the master branch, but it seems that I failed to build OpenROAD with the recent changes....

Yes indeed, it was a bad manipulation on my part, I do have the same error as you do for the global placement now... Sorry for the inconvenience

@lustefan97 No problem, you've raised an essential missing in the PPL tool. It wasn't reporting the number of positions from the top layer grid; my PR is covering it now.
Also, when using the OpenROAD-flow-scripts, you can use the build_openroad.sh script to get the latest updates in the submodules. So, if you want to build ORFS with the latest commits from the OpenROAD repository, you can run ./build_openroad.sh --latest. This will update all submodules to the latest commit. Also, you can use the flag --local to build everything in your machine instead of docker.


Icons Added

Icon Added: src/icons/0162_phoneArrowRight_i.svg
Icon Added: src/icons/0163_phoneArrowLeft_i.svg
Icon Added: src/icons/0164_phoneDownCurvedArrow_i.svg

+1


Document that imports/ directory in Meteor 1.3 makes something an "import"

Right now, this section: https://github.com/fourseven/meteor-scss/#file-types doesn't cover that putting a file in imports/ also makes it not load eagerly. Probably worth updating now that 1.3 is out.

Closing per https://github.com/fourseven/meteor-scss/commit/7189df6c37f9779a1795de68c2b8868216b52802


initial render is messy in server/static render

I made this gif that explains what is going on: https://gyazo.com/c43c410aa9cb93bfdfaf4c2da8559019
Basically when you go to a page for the first time, the tool-tip popup contents display then go away once javascript executes.
In my case, the tooltip is configured to only popup on click. And as a fix, I plan on simply making that component only display tool tip once componentDidMount, but it's kind of a hack and that info won't be on page source / seo-friendly.
I guess I imagined that the contents of the popup would at least be hidden on the initial rendered, not just splattered on the screen in some place as to cause a flicker for server-side / static rendered apps.
Am I missing some config or could this be improved in the code?

Dealing with this issue as well.

Same...

If a custom wrapper component is used, checking if window is defined or process.browser for next.js before rendering would be another workaround, but still, it won't solve SEO issue. I am not sure how it can be solved SEO-friendly though.

Same issue here


Add Withdrawals struct

Changes Proposed

Added a Withdrawals structure in the primitives module to encapsulate a vector of Withdrawal.
Noticed that an equivalent type, Withdrawal, is also present in the alloy library but resides in the rpc crate. This often leads to confusion between the Withdrawal type of reth primitives and the Withdrawal type of alloy.
To achieve complete integration and unify the types, suggesting the following steps:

Move Withdrawal and Withdrawals up a level in the alloy crate to place them at the root instead of within the rpc module.
Completely remove the definitions of Withdrawal and Withdrawals from the reth primitives.

Next Steps
If this pull request is accepted, I propose to merge it first.
Following that, further work could be carried out on the alloy library to complete the refactoring.
The aim is to rely solely on Withdrawal and Withdrawals from the alloy library, eliminating the need for these types in the reth primitives.

@mattsse wdt about this one? If this is fine I can work on rlp decoding stuff for Block in order to pass the CI

@Rjected anything to unlock here?


Class "Flasher\Prime\Flasher" not found

I got the error "Class "Flasher\Prime\Flasher" not found" in Laravel 9 with the Windows 11 operating system, I think this error is because the Windows operating system cannot have a file with the same name as in the php-flasher package, namely the Flasher file. php and flasher.php, if on linux I don't think there is a problem.

Hello @a3m-nix, thanks for using PHPFlasher and for reporting the issue,
Can you please share a project where this error is happening, or give more details about it?
What are : PHP version, PHPFlasher version?

PHP 8.1.6 (cli) (built: May 11 2022 08:55:59) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.1.6, Copyright (c) Zend Technologies
PHP Flasher  latest version from this https://php-flasher.io/docs/installation/

Thank you @a3m-nix, I will rename the helper files to helpers.php, I will let you know when it's done,
I don't have Windows to test this, thanks in advance

Can you upgrade to v1.10.1 and check if the fix works for or not:
composer update "php-flasher/*"

it's working fine now, thanks a lot for the help and good response.

You're welcome, Thanks for the confirmation 🎉


i can't migrate to androidX

I tried with several methods to migrate my application to AndroidX and I can't do it.
My application stops after trying it.
I try Android Studio and Vscode, following the documentation, and I can't solve this.

Hi @CristhianFonseca please show your error

Hi @CristhianFonseca
can you please provide your flutter doctor -v?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

@luffynas no error comes out, only the application stops

Hi @CristhianFonseca please show your error

no error comes out, only the application stops

I give up this error. I will create a new project from the console

Hi @CristhianFonseca
can you please provide your flutter doctor -v?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

https://github.com/CristhianFonseca/errorAndroidXFlutter

add several line in your gradle.properties
android.enableJetifier=true
android.useAndroidX=true

Hi again @CristhianFonseca
does the proposed solution fix the issue?
(thank you @luffynas )
Please refrain
from posting pictures if not necessary.
Thank you

Hi @iapicca
no, I had to create a new project from console with tag --androidx

@CristhianFonseca I tried your app https://github.com/CristhianFonseca/errorAndroidXFlutter, after adding
android.enableJetifier=true
android.useAndroidX=true

it works just fine. What the issue did you have or have now?

@CristhianFonseca I tried your app https://github.com/CristhianFonseca/errorAndroidXFlutter, after adding
android.enableJetifier=true
android.useAndroidX=true

it works just fine. What the issue did you have or have now?

I also know this, but it didn't help me


ISPN-11650 Session externalization tests are hanging with ATTRIBUTE granularity + EAP7.3+hotrod-session-management

https://issues.redhat.com/browse/ISPN-11650

integrated! thanks @wburns !


A0-2240: Refactor aleph node RPC

Description
Aleph Node Rpc does not need to be dependent on B: Block. This replaces and is heavily based on #1102, which got sufficiently obsoleted by other changes that it was simpler to write it from scratch.
Type of change
Refactor

Nice. I'd consider using opaque::Header instead of <Block as BlockT>::Header> (or, even better, import Header from primitives), but the decision is yours.


Get an open source certificate for code signing

Certum provides those for cheap

Certum does not provide non-physical key certificates anymore

Looks like Certum has created a new product just for that - need to revisit

Yes, Chrome is strongly in the opinion the installer is fishy/malware, and Windows isn't exactly encouraging installing it either. If fixing this requires a bit of dough, I'm sure thankful users would chip in for the cost - I would.

Does Chrome actually warn of installer as malware? Never seen it, do you have a screenshot?
I plan to get a hardware key soon:tm: then will be able to look into getting builds signed


South west england

#110243076
I have also disabled the generate DOS questions script as it clobbers the questions files since hints and validations have been added.

Wow - we have the same list of locations in 19 files.
Changes look good :+1:


clear route cache when adding routes

if the app uses cached routes, we should rebuild the route cache otherwise dev. must do it manually after creating the route and adding the sidebar item.

Hi Pedro - I see our system has already thanked you for submitting your first PR, but I wanted to thank you too 🙏
So glad to see "your first contribution". Let me know if you intend to submit any more PRs 😉😂

I cannot let you know that, if I do, after I might have to kill you. I am working in some undercover project (shhhhhhhh 🤫).
😸


AttributeError: 'NoneType' object has no attribute 'startswith' error after update to 1.0.4

Hi there,
setting svprioritize: cancer/civic results in the following error:

Traceback (most recent call last):
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 50, in _setup_logging
yield config
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 480, in organize_samples
return ipython.zip_args(apply(run_info.organize, *args))
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/run_info.py", line 70, in organize
item = add_reference_resources(item, remote_retriever)
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/run_info.py", line 183, in add_reference_resources
data = _fill_prioritization_targets(data)
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/run_info.py", line 267, in _fill_prioritization_targets
os.path.dirname(os.path.realpath(utils.which("simple_sv_annotation.py"))),
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/posixpath.py", line 375, in realpath
path, ok = _joinrealpath('', filename, {})
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/posixpath.py", line 381, in _joinrealpath
if isabs(rest):
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/posixpath.py", line 54, in isabs
return s.startswith('/')
AttributeError: 'NoneType' object has no attribute 'startswith'

Solution for me: Remove svprioritize option.
The same error is occuring when running bwa:

[2017-07-24T08:49Z] compute-6-28: Aligning lane 1T with bwa aligner
[2017-07-24T08:49Z] compute-6-15: Unexpected error
Traceback (most recent call last):
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 50, in _setup_logging
yield config
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipythontasks.py", line 205, in process_alignment
return ipython.zip_args(apply(sample.process_alignment, *args))
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/sample.py", line 116, in process_alignment
data = align_to_sort_bam(fastq1, fastq2, aligner, data)
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/alignment.py", line 65, in align_to_sort_bam
names, align_dir, data)
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/alignment.py", line 119, in _align_from_fastq
out = align_fn(fastq1, fastq2, align_ref, names, align_dir, data)
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/ngsalign/bwa.py", line 163, in align_pipe
names, rg_info, data)
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/ngsalign/bwa.py", line 172, in _align_mem
"%s | %s" % (_get_bwa_mem_cmd(data, out_file, ref_file, fastq_file, pair_file), tobam_cl))
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/site-packages/bcbio/ngsalign/bwa.py", line 67, in _get_bwa_mem_cmd
bwakit_dir = os.path.dirname(os.path.realpath(utils.which("run-bwamem")))
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/posixpath.py", line 375, in realpath
path, ok = _joinrealpath('', filename, {})
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/posixpath.py", line 381, in _joinrealpath
if isabs(rest):
File "/bcbio/local/share/bcbio/anaconda/lib/python2.7/posixpath.py", line 54, in isabs
return s.startswith('/')
AttributeError: 'NoneType' object has no attribute 'startswith'

An update on this: It seems that the newest bcbio version deletes files that are within /work/log/ipython/startup/ at some point during runs? That seems to cause the trouble for me, since I've a cluster specific config file there...

Sorry about the problem, the error message looks like you're missing tools in your path. If all of the bcbio tools are up to date, you need to ensure the --tooldir directory where they're located is present at the start of your PATH. Hope this resolves the issues for you.

Sorry, meant to also ask about the ipython setup. We don't purposely delete any directories as far as I remember, although I'm not sure about the behavior of ipython itself. If this is where you're setting the PATH I'm not totally sure what to suggest as I haven't tweaked ipython at this level myself. I'm happy to adjust anything inside bcbio to avoid this if we can identify where it's coming from.

Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "offwhite.py", line 55, in run
self.re = self.s.post(url, data=self.data, proxies=self.proxy)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/sessions.py", line 555, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/sessions.py", line 508, in request
resp = self.send(prep, **send_kwargs)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/sessions.py", line 618, in send
r = adapter.send(request, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/requests/adapters.py", line 440, in send
timeout=timeout
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/urllib3/connectionpool.py", line 595, in urlopen
self._prepare_proxy(conn)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/urllib3/connectionpool.py", line 816, in _prepare_proxy
conn.connect()
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/urllib3/connection.py", line 284, in connect
conn = self._new_conn()
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/urllib3/connection.py", line 141, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/urllib3/util/connection.py", line 51, in create_connection
if host.startswith('['):
AttributeError: 'NoneType' object has no attribute 'startswith'

can someone help me?

Hi Andrea-- it looks like you are running on OSX, which we don't support unfortunately. A lot of the third party tools don't work on OSX, see http://bcbio-nextgen.readthedocs.io/en/latest/contents/installation.html#installation for more information.


Can not query storage catalog when Fault Tolerant Execution is activated

Currently this connector causing issues, if FTE is enabled on the trino cluster. Queries directing to this catalog fail.

What's the error you're getting?

Do you think, this can be fixed/implemented for this connector? It would be great if queries could still read from this catalog, while FTE is enabled.

Fixed in 37630ef8bfbad5e2978957dcd5407d63e99ca3b0, will release a new version once Trino 465 is out.


Performance Issues: when connected to TOR

https://user-images.githubusercontent.com/62699947/230619955-ec2e5daf-3304-42ee-a06a-b51732db5ac6.mp4

When connect to Tor, the app get stuck. Clicking on anything does not react at all.I will have to kill the app and restart then only it starts working.

Issue seems outdated, please reopen if still relevant


Do not fail when dependency SHA cannot be read from file

Right now, we fail and return if any one dependency SHA cant be found. We need to continue looking at other deps.

you can find this code specifically for the java provider here:
https://github.com/konveyor/analyzer-lsp/blob/main/provider/internal/java/dependency.go#L202

@punithnayak thank you! please take it away

Hey @pranavgaikwad

Facing this issue

Hey @pranavgaikwad can you please tell  me how resolve this issue

I think that you need to add docker.io as a registry

Fixed via #272


[QA Testing - New Router] Address Autocomplete Not Populating in Preview

Description
Following the QA Testing Steps in the Excel, the Preview does not auto-complete address fields.
Steps to reproduce
"1.  Select “Add form element”
2.  Scroll to the Address input block and select it
3. Select a input field under the Address block
4. Navigate to the input block menu and select “More”
5. Scroll to “Select an autocomplete attribute”
6. Select “Full address” in the drop down menu
7. Save your selection"
8. Go to Preview.
9. Type in any of the newly added fields, they're treated as regular textboxes.
Details

Browser: Chrome
Operating system: Mac OSX
Environment: Staging
Language: English

Expected behaviour
The autocomplete autocompletes any of the fields.

Clarification required: don't believe there is a "Full address" autocomplete option in the dropdown?

... and from my testing, looks like the appropriate autcomplete property is being added to the inputs
From here, the behaviour of the inputs is browser-dependent.

I may of mistaken the functionality!~ I assumed it was a functional autofill ala : Type in Ont and get Ontario.

In this case it's just the browser auto-complete.
https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete
Going to close.
Note see: https://github.com/cds-snc/platform-forms-client/pull/3139 work that was done on a typeahead component


Update Eslint/Babel Packages

Updated Eslint and Babel Dependencies occasioned by upgrades in babel-preset-metalab and eslint-config-metalab.
Removed Node v.0.12 from Travis test, babel-preset-metalab no longer supports this version of node.

Same comment as on https://github.com/metalabdesign/webpack-udev-server/pull/32 RE .babelrc https://github.com/metalabdesign/webpack-udev-server/pull/32#issuecomment-286550205


pydantic.errors

Thank you for your great work!
before  i run demo in win, requirements.txt was installed.
when i run 'python scripts/sampleui.py' ,the error occured:
AttributeError: pydantic_core_schema
During handling of the above exception, another exception occurred:
raise PydanticSchemaGenerationError(
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <class 'starlette.requests.Request'>. Set arbitrary_types_allowed=True in the model_config to ig
nore this error or implement __get_pydantic_core_schema__ on your type to fully support it.
If you got this error by calling handler() within __get_pydantic_core_schema__ then you likely need to call handler.generate_schema(<some type>) since we do not call __get_p ydantic_core_schema__ on <some type> otherwise to avoid infinite recursion.

maybe use gradio 4.43.0 in windows


Initial upgrade for .NET Core 3.0 and CORS

This PR includes minimum upgrade path explained by Migrate from ASP.NET Core 2.2 to 3.0.
It also includes nuget package upgrades to the latest previews.

Nice, this is cool 👍😊 I look forward to .NET Core 3.0.
Thanks!

I updated Fluent Assertions in this PR but seems like tests needs to be updated :/

Yes, I know, I have older version of FluentValidation in UnitTests because I will need to rewrite probable a lot of tests, so upgrading of this library will be later. :)

I will continue here: #390.
Thanks for initial version!


NPM failing to publish

The publish job succeeded (release - pulumi/pulumi-junipermist@f8dfe70), but it doesn't look like the package made it on to npm.

Tursn out the package was just hidden because it was marked private. I've made it public now


fix:  less promises for scanning and await with allSettled

alternative to https://github.com/vitejs/vite/pull/11243
doesn't add cancel() function to as that may have performance implications and the way the function has to be passed around isn't nice.
Description

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the Commit Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

/ecosystem-ci run

/ecosystem-ci run sveltekit