Integration in CI/CD pipeline when there are also non-migration changes

Hi, this looks like the tool I need, but I'm having some trouble integrating it into our CI/CD pipeline, perhaps you can help.
Current situation
Currently we have to do our migrations (state mv, import etc) manually, outside of the CI/CD pipeline. But aside from the migrations it works like this:

Changes in terraform code are made on a separate branch.
A merge/pull request is created for the branch.
CI/CD pipeline does a terraform plan.
Reviewer checks the terraform code and the output of the plan.
Branch is merged into the main branch.
CI/CD pipeline does another terraform plan (to ensure no changes were done on the main branch in the mean time).
Reviewer checks the plan again.
Reviewer starts manual job in the CI/CD pipeline that runs terraform apply with the previously created plan.

Desired situation
I would love to use tfmigrate in history mode to do all our migrations for us at the same time as the terraform code for the migrations is actually merged and applied by the CI/CD pipeline. So I came up with this:

Changes in terraform code are made on a separate branch.
A merge/pull request is created for the branch.
CI/CD pipeline does a tfmigrate plan.
Reviewer checks the terraform code and the output of the plan.
Branch is merged into the main branch.
CI/CD pipeline does tfmigrate apply to apply the migrations that were merged (together with the terraform code causing the migrations)
CI/CD pipeline does another terraform plan (to ensure no changes were done on the main branch in the mean time).
Reviewer checks the plan again.
Reviewer starts manual job in the CI/CD pipeline that runs terraform apply with the previously created plan.

Difficulties

Our merge/pull requests will contain more than just migration code. For example there may be a mv/rename of a resource, but in the same merge request that resource' attributes are also changed. So tfmigrate plan results in a non-empty plan causing the CI/CD pipeline to fail.
And even if we would make separate merge/pull requests for migrations and 'normal' terraform changes, how would we combine both tfmigrate and 'normal' terraform plan/apply into the same pipeline without the tfmigrate part failing?
I tried using a wrapper script around the terraform command with TFMIGRATE_EXEC_PATH that always exits with a 0 exit code for the terraform plan command, but then tfmigrate doesn't seem to output the plan results to the console.

A potential solution might be to always have tfmigrate plan output the plan results and have an option for it to not fail when there are diffs. But perhaps I misunderstood and that is the wrong way of using the tool. Would you have any suggestions on how to properly integrate tfmigrate into our development pipeline while allowing 'normal' terraform changes besides the migrations?

Hi @WVan, Thank you for sharing your use-case!
It looks like a problem similar to #36. It had been implemented in #37, but it was recently deprecated in #63 due to a change in Terraform 1.1. At time of this writing with the latest tfmigrate v0.3.0 + Terraform v1.1.0, there is no perfect single solution due to some technical constraints.
Knowing that not all use cases can be covered, but the following might be help:

For renaming a resource address in a single tfstate, use a new moved block introduced in Terraform 1.1. See https://www.hashicorp.com/blog/terraform-1-1-improves-refactoring-and-the-cloud-cli-experience
For moving a resource accross two tfstates, use a multi_state migration in tfmigrate and not to include other normal configuration changes in a single pull request.
For importing or removing a resource in a single tfstate, use a state migration in tfmigrate with setting a force attribute to true, which allows you to apply migration even if it contains some plan changes, finally run a normal terraform apply to converge changes.

A native plannable import feature has been proposed in the upstream, but not implemented yet. https://github.com/hashicorp/terraform/issues/26364

After thinking about how to implement a pipeline, you may simplify them into the 3rd case because your pipeline already has a step for an approval before terraform apply, which allows you to review changes ignored by tfmigrate apply with the force attribute.

I'm going to close this because there has been no activity on this recently. Please feel free to reopen this if you have any questions or suggestions. Thanks!


Enable specifying classpath to include other submodules for Type Resolution

Expected Behavior

I want to be able to specify that other modules in my gradle build should be included as part of classpath but not  for analysis, only to assist in type resolution.
It seems the extension only allows me to set source packages
Current Behavior

If i resolve a type in a class in my module that detekt is applied to:
bindingContext[BindingContext.TYPE, typeReference]

and the type is from other included module X then the type class descriptor will be deserialized class MyOtherModuleClass
Context

I want to be able to access PsiElements of types from other modules in my project for further analysis.
Perhaps this is possible now, feel free to move this to a question if so.

For more context - Im running from an Android project and ive been calling detektDebug to run.
looking at the plugin code (as of writing from latest release of 1.23.7 - the code has been refactored on main since https://github.com/detekt/detekt/pull/7016) - it doesnt seem there is actually a way to set extraInputSource for an android task via the detekt extension source param.
Reading the doc it seems I might need to write my own task based on https://github.com/detekt/detekt/issues/2259

ok best I could come up with was to follow https://github.com/detekt/detekt/issues/2259#issuecomment-669888008
In case this helps someone else:
we have detekt applied per module of a multi module project.  If type resolution is required to resolve the sibling module types then you can add the additional source required like so:
fun findKotlinSourceFiles(projectName: String): List<File> {
  val projectDir = project(":$projectName").projectDir
  val sourceDir = projectDir.resolve("src/main/java")
  return if (sourceDir.exists()) {
    sourceDir.walkTopDown().filter { it.isFile && it.extension == "kt" }.toList()
  } else {
    emptyList()
  }
}

tasks.withType<Detekt>().configureEach {
  var additionalSourceSet = emptyList<File>()
  additionalSourceSet += findKotlinSourceFiles(projects.yourModuleName.name)
  additionalSourceSet += findKotlinSourceFiles(projects.yourOtherModuleName.name)

  doFirst {
    source(additionalSourceSet)
  }
}

however this does have the setback that if you have baselined issues for those other modules - now you will also need to baseline for this module.
Ideally there would be a way to include these other modules on the classpath with their source resolved so that they are not included as part of analysis.

I want to be able to specify that other modules in my gradle build should be included as part of classpath but not for analysis, only to assist in type resolution.

As you found out, this is not easily possible.
The caveat of using the SourceTask is a good workaround, and you're probably fine with that. Also why is it a problem if the extra sources are also used for analysis. Is it for performance reasons?

I'm probably missing something here. Detekt should add to the classpath all the modules that are used to compile your module. If those other modules are used they should be added to the classpath too. Also, if two modules are siblings then they don't depend between each other. So it should be fine if they are not added to the classpath. What am I missing?


Expose compiler object responsible for compiling the preact application

As mentioned by #70, I started creating a reusable compiler instance responsible for building or watching a preact application. The commands are now using this compiler to generate their output. The compiler is exposed as main entry so one can use it in their own project like this;
const createCompiler = require('preact-cli');

let compiler = createCompiler(/* any options can be passed here */);

// Compile the application and optionally serve it through the dev server by passing a bool.
await compiler.compile(true);

// Return a prerendered string for the given params
compiler.prerender(/* any params passed to prerender */)

I guess this can be seen as a first step in exposing an api to built upon; like exposing the prerender functionality to render compiled preact strings in a node.js app, replacing the dev server with dev middleware so you can mount the preact-cli on your own server, etc.

@developit did you manage to find some time to look at this PR? It would be great to have some sort of extendability built into this project

Not yet, no. Hopefully someone else can review before me!

given that there has been no activity I'm gonna close this
we're working towards modularising the cli which will also export the config

Why was this closed?
I still cannot find a good answer to the question:
How to take a preact-cli app and make it server-side rendering?
I was hoping this PR was the answer...

@Download You can require the build/ssr-build/ssr-bundle.js file directly and pass in whatever URLs you want to as props.url.
It's the same approach the CLI is using internally to produce the "prerendered" outputs -- except that you can do it at runtime.
I have a full example with this approach & am using it on a couple sites: https://github.com/lukeed/preact-cli-ssr


Add fetchGistsUpdatedSince: method to OCTClient class

This method supports 'since' parameter of API to list gists.

Almost two years late, but this looks good :smile:


KAFKA-14920: Address timeouts and out of order sequences

When creating a verification state entry, we also store sequence and epoch. On subsequent requests, we will take the latest epoch seen and the earliest sequence seen. That way, if we try to append a sequence after the earliest seen sequence, we can block that and retry.  This addresses potential OutOfOrderSequence loops caused by errors during verification (coordinator loading, timeouts, etc).
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Test failures look unrelated. 👍


Changing health bar icons during a song

Describe your problem here.
Does anyone know the correct command to change the icons of the characters during a match? I've been trying with setProperty('iconP1', 'images/icons/icon-agoti') and setProperty('iconP1', 'icons/icon-void') and similar commands. However, the game crashes. I don't know how to do it correctly; does anyone know the code?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

runHaxeCode([[game.icon(P1/P2).changeIcon('nameoficon')]])


Fix comment json format

With elm front-end, if there is a comment, there is an error while loading an article.
According to realworld api
https://github.com/gothinkster/realworld/tree/master/api#single-comment,
this is the right example.
{'comments': [{'updatedAt': '2016-02-18T03:22:56.637Z', 'body': 'It takes a Jacobian', 'createdAt': '2016-02-18T03:22:56.637Z', 'id': 1, 'author': {'image': 'https://i.stack.imgur.com/xHWG8.jpg', 'bio': 'I work at statefarm', 'following': False, 'username': 'jake'}}]}

but in flask-realworld,
we got this.
{'comments': [{'createdAt': '2017-08-30T05:22:41.529511+00:00', 'updatedAt': '2017-08-30T05:22:41.529540+00:00', 'body': '123', 'id': 1, 'author': {'profile': {'image': None, 'bio': None, 'email'<EMAIL_ADDRESS>'username': 'u2', 'following': False}}}]}

The only difference between these is 'author' section.
We need to remove profile key and put profile's item to 'author' section.
because I don't know how schema? works here, I just removed profile key like below...
data['author'] = data['author']['profile']

I think this is just a fast easy solution for this since I don't know how schema class works.
author = fields.Nested(ProfileSchema)

I knew this part has a problem. I don't know how to fix it lol.

Hello,
Sorry for the delay, I didn't notice the github Email just for the new change, there is really no proper way to do this, your solution is fine.
Maybe you should add a test so that this won't happen again and I will merge it.

hmm...
I tried to add a comment view test, but I can't see or access marshmallow results during the test.

Merged thanks.

Nice! I'm learning from you a lot. Thank you!


def make_tome_block

Hi, thank you for your great work! I'd like to ask about the make_tome_block function in the case where the diffuser pipeline is not used. Is it fully functional in the current version, or is it necessary for me to complete it myself?

Hi,
make_tome_block does work now. It is inherited from the original ToMe codebase. As we conduct experiments with diffusers, we have not added support for other diffusion implementations.
Due to my schedule, I may not be able to fix it soon. However, you can follow make_diffusers_tome_block to complete it:

Copy your transformer forward code to make_tome_block.ToMeBlock.forward
Add compute_merge and unmerge operations before and after self-attention.

Thank you so much for the prompt reply and for providing guidance on the implementation! I will definitely proceed with completing the implementation on my own.


 Did a release, but totally forgot to change the version number and date before I did it. https://help.github.com/articles/editing-and-deleting-releases/ - I could not delete the release, it only seemed to wipe all the descriptions and left me with no edit anymore.  And if I download the release (zip), sure enough it has the old date etc.
So now what?

I just edited the description - https://github.com/ghacksuserjs/ghacks-user.js/releases/tag/61.0
Kinda pisses me off, any attempt to recreate a v61 goes back to that point in time

@earthlng ^^ or I could delete it again (not sure if it really is deleted or it remains with no description - its weird) and create a 61.0.1? Either way it's a shitty outcome

https://help.github.com/articles/about-releases/

Tags mark a specific point in the history of your project

So I guess that's that then. If I want a nice release with the fixed date + version, I would have to use a different tag

it's just a date - who cares?! if you want to do a 61.0.1 that's fine too, I don't really care

:jeans: , I played around with those features (tags/releases) a couple of weeks ago for the first time, and deleting seemed kind of weird at first for me, too (maybe that has something to do with the fact that I didn't RTFM). I remember having seen something similar to what you describe, but I could successfully delete the whole tag from GitHub without using Git after a few tries. Moreover, I just tried the same again and I could do it without any problems.
After deleting the tag, you should indeed be able to re-create it pointing to another time in history (like that specific commit when you changed the date & version lines. Don't give up on me, :jeans:!! I would love to push the fixed tags myself, if I could, but I think Github doesn't have that functionality, and to push them from Git I'd need write access to this repo (and if I had write access I wouldn't need Git anyway) :disappointed:
Just go crazy on that tag 'til it gives up or something. (?) I mean, I would give you instructions on how to do it, but there really isn't much more to it than what the GitHub help page says. Once it's done, when you're going to re-create the tag you just change the Target to the hash of your desired commit (c4d131a ?), and presto.

On a good note, the release is authored by earthlng (cuz he played with it), and the note on the release implies that he fucked up, and not me :+1:

I forked this repo in bare form, preserving all tags (using Git), and then I deleted that release + the 61.0 tag and re-created them pointing to b3b3ae4 (which is where you changed the date + version).
https://github.com/claustromaniac/ghacks-user.js/releases/tag/61.0
It's not too late. But I don't really care, I just wanted to let you know that it still is doable. You just have to delete the release first and then the tag. Is there any reason to not do it? Honest question, I really don't know.

I'll give it a shot ...

Done!  ;)
I tried adding a commit in my fork to see if that fixed the "x commits to master" thing, but it apparently didn't. Maybe adding another tag will fix it? Lets try that...

Just FYI, the missing "x commits to master" thing was reported a few months ago. It seems to be either a bug or something they only partially removed from the platform.
https://github.community/t5/How-to-use-Git-and-GitHub/x-commits-to-master-since-this-release-is-missing/m-p/3705


EHN: explicit test for Freesurfer & MNE environment variables?

I regularly encounter people who run into highly non explicit subprocess.call() errors due to inexistent environment variable and source (FREESURFER_HOME, 'MNE_ROOT`) or missing Freesurfer licence.
Today, the error was due to the fact that Spyder didn't have the same env variable as the terminal.
In any case, I think it'd be very helpful if we had a little function that checks i) whether the necessary env variables are present and ii) whether they point to a real path, and throw an error otherwise.

can you give a function that does not check this early enough?

We already have something like this for subjects_dir I think, so we can generalize that function for this purpose. Although in the case of MNE and FreeSurfer, we could verify paths a bit better e.g. by looking for files we know should be close to the root of the install, so maybe separate functions would be best.

The case I encountered today was make_watershed_bem IIRC. (Not my computer though, so you won't have much more details.)
In sort of the same topic, I personally check that the subject has been correctly segmented with from the log of freesurfer recon-all. But this may be too stringent depending on how users ran their segmentations.
def check_freesurfer(subjects_dir, subject):
    # Check freesurfer finished without any errors
    fname = op.join(subjects_dir, subject, 'scripts', 'recon-all.log')
    if op.isfile(fname):
        with open(fname, 'rb') as fh:
            fh.seek(-1024, 2)
            last = fh.readlines()[-1].decode()
        print last
        print('{}: ok'.format(subject))
        return True
    else:
        print('{}: missing'.format(subject))
        return False

what you report weird:
https://github.com/mne-tools/mne-python/blob/master/mne/bem.py#L956
no?

Unfortunately, I can't tell you much more. The error was in Spyder which I don't have. Also, adding env vars in Spyder via mne.utils.set_config() didn't work, but os.env[''] did. I'm not sure how spyder deals with env variables.
Two additional errors followed:

missing licence file despite export FREESURFER=path/to/freesurfer/
no writing permission in path/to/freesurfer/subjects after freesurfer fresh install on a mac.

Both errors crashed non-explicitely after subprocess.call()

Also, adding env vars in Spyder via mne.utils.set_config() didn't work

Just to be clear, mne.utils.set_config(...) does not set environment variables, it sets variables in the mne-python config file. So setting those will only have an effect when mne-python goes to query variables, not when external programs do.
I guess we could have mne-python query these vars and pass them, if available, in the run_subprocess call if that would make things easier.

I'm not sure how spyder deals with env variables.

Spyder deals with env variables the same way that any program does, which depends on the OS and how it is launched. If you launch it from a terminal, it should inherit the env of the terminal. If you launch it from the OS's GUI, then it will probably only have the global vars (i.e., not those from any particular user's .bashrc or .cshrc file).

missing licence file despite export FREESURFER=path/to/freesurfer/
no writing permission in path/to/freesurfer/subjects after freesurfer fresh install on a mac.

I suspect these are both issues with the FREESURFER install rather than MNE. Can the user use FreeSurfer properly outside of the mne-python context?

I suspect these are both issues with the FREESURFER install rather than MNE. Can the user use FreeSurfer properly outside of the mne-python context?

Absolutely, these are Freesurfer issues; but it was difficult to track down for the user, because the thrown error was cryptic.

FYI @kingjr it's "ENH" not "EHN", looks like a few of your issues have this issue :)

yep, definitely a systematic error, my bad

I remember it took me a while to figure out what ENH stood for ;)

can you give a function that does not check this early enough?

mri_watershed called by mne.bem.make_watershed_bem (identified in https://github.com/mne-tools/mne-python/issues/3274)

the _prepare_env in bem.py is meant to check early. it's not good enough?
if not PR welcome

the _prepare_env in bem.py is meant to check early. it's not good enough?

Apparently not.
I started a PR to try to automatically detect freesurfer directory in case the user hasn't given the right env variables (or whatever other reason, such as conflict between profile sources).
I'm nearly there:
https://gist.github.com/kingjr/97d19a1d5d2af7b2f7e5b9b7badfe4d2
But didn't manage to capture the failure to launch SetUpFreeSurfer.sh, and I'm spending way too much time on this, so I'll just leave it there until we find the motivation to finish it.


Reconsider sending fingerprint to Rollbar

This library sets the fingerprint field when sending log messages to Rollbar (https://github.com/stvp/roll/blob/master/client.go#L142). This is probably often a good idea since there is more context lower down about where the error is coming from. However, for some cases this results in improper groupings that cannot be overwritten. The hierarchy for fingerprints is as follows (in descending priority): client provided, custom groupings from the UI, Rollbar calculated grouping.
For example, we have an unmarshal error that includes the bytes from the message that was getting unmarshaled. When the fingerprint is calculated (https://github.com/stvp/roll/blob/master/stack.go#L64) with the title string - in this case the error message - this results in separate fingerprints for errors coming from the same source. We want these errors to be grouped in Rollbar, and could use a custom grouping to do this, but cannot because we are unable to overwrite the client provided fingerprint.
Would you consider a PR to do one of the following:
1 - No longer use the title in the hash (probably the easiest, just remove https://github.com/stvp/roll/blob/master/stack.go#L66)
2 - Remove setting the fingerprint in the client
3 - Provide an option to log without a custom fingerprint
4 - Something else that you suggest?
Based on the function description, Option 1 seems to be the best. This way we guarantee that the hash is always the same for the same filename, method name, and line number.

I opened a PR for option number 1 that I proposed above. Please let me know your thoughts.

Fixed with #8 and ca202b60b2601abe3e2e6a948a12b1b856badf6c. Thanks!


LnumDiff is wrong with FilterModeDiffContext

Something wrong with #450

https://github.com/reviewdog/reviewdog/pull/513/files#r407182204

It looks like diff line number changed due to annotation comments in Files changed tab.
It works fine in Converstation tab.

it seems it's GitHub bug.


Remove @ tag from all comments

Summary
and format the multiple line comments
Impact
format change only
Testing
ci

Remove @ tag from all comments

why?

Remove @ tag from all comments

why?

Because all NuttX native comments don't use @, which are copied from other code base to identify the special element.

Remove @ tag from all comments

why?

Because all NuttX native comments don't use @, which are copied from other code base to identify the special element.

well, what's the benefit we can gain by removing them?
i feel doxygen style comments are popular enough.

Remove @ tag from all comments

why?

Because all NuttX native comments don't use @, which are copied from other code base to identify the special element.

well, what's the benefit we can gain by removing them?

Improve the consistency.

i feel doxygen style comments are popular enough.

It isn't popular in NuttX code base.


Unable to edit yaml for rke2 custom and node driver clusters

Setup
Rancher version: 2.6-head 160abae
Browser type & version: Chrome
Describe the bug
While creating a custom/node driver clusters, not able to edit anything on the yaml file when we select edit as yaml option.
To Reproduce

Create a custom rke2 cluster
Click on edit as yaml option at the bottom right of the cluster form.
Try to edit any text on the yaml.

Result
Unable to edit anything on the yaml.
Expected Result
Editing is allowed

Verified editing yaml working on the commit efa312e 2.6-head


Installation script attempts to install Python 3.9 on Windows 7

The installation script downloads and tries to install Python 3.9.0 even if the VM is a Windows 7 installation, where the installation will always fail, as the Python 3.9.0 installer is set to refuse installation on anything below Windows 8.1
Manually installing Python 3.8.6 into C:\Python39 and issuing cinsts --force libraries.python3.fireeye will succesfully install the libraries and tools that depend on python3, but it'd be great if the installation script took care of such things automagically.

@shinmai, We just upgrade FLARE-VM to v<IP_ADDRESS> that should limit python version to 3.7.x to work on Windows 7.

This is still an issue for me
You have python3 v3.7.2 installed. Version 3.9.1 is available based on your source(s).
python3 not upgraded. An error occurred during installation:
 Updating 'python3 3.7.2' to 'python3 3.9.1' failed. Unable to find versions of 'libraries.python2.fireeye, libraries.py
thon3.fireeye' that are compatible with 'python3 3.9.1'.
python3 package files upgrade completed. Performing other installation steps.
The upgrade of python3 was NOT successful.
python3 not upgraded. An error occurred during installation:
 Updating 'python3 3.7.2' to 'python3 3.9.1' failed. Unable to find versions of 'libraries.python2.fireeye, libraries.py
thon3.fireeye' that are compatible with 'python3 3.9.1'.

Hi @zaqes, Sorry I missed this issue.
Currently, on Windows 7, we have to limit python version to 3.7.x. Starting at 3.8, python no longer supports windows 7. There are two options here:

Do not update and work with an older version of python. Based on your error message, it says 3.7.2.
Use FLARE-VM on Windows 10. We are testing a few more edge cases while attempting to support Windows 10. However, the current install script should mosty work on Windows 10 x64. You should still have most of the packages.

Hi @Dobatymo,
Thank you for using FLARE-VM. Recently, I am no longer a member of FireEye/Mandiant and the FLARE-VM development team. Therefore, I am unable to support this issue. However, if Python installation is still an issue, I'd recommend opening a new ticket for the current FLARE-VM development Team.
Nhan


[FloatingActionButton] set touch flag in handleTouchEnd

Fixes #5076

@jkettmann Right, that sounds safe to double check at the touchEnd event.
I'm gonna merge it as soon as 0.16.0 is released. Thanks.


400 Client Error from when downloading behind our firewall

Hi,
I wanted to report an issue I encountered when running totalsegmentator from behind our corporate firewall/proxy (400 Client Error). I was a bit confused because I am able to access those Zenodo zip files from behind our proxy, but I was able to resolve the issue by removing the following lines of code:
https://github.com/wasserth/TotalSegmentator/blob/4f4196ac6e7d7b3b33bbb7ed6afe7cdd81aa9438/totalsegmentator/libs.py#L57-L60
Based on the stack overflow thread linked in that comment, this is a workaround that can break things in certain circumstances (like mine I suppose). Perhaps this should be removed, or consider making the use of HTTP/1.0 configurable from the totalsegmentator API?
A quick and easy fix would be to use an environment variable (e.g. TOTALSEG_ENABLE_HTTP1.0) which can be set to toggle this behavior. If this is of interest I'd be happy to put a Pull Request in.
Thanks.

Thanks for pointing this out. Using a optional environment variable is a nice idea. The default should be the current behaviour. So when TOTALSEG_DISABLE_HTTP1.0 is not set, then it is using the current code. When TOTALSEG_DISABLE_HTTP1.0 is set, then the lines of code which you showed should be disabled. A pull request would be great.


[Shared Component] LineContainerComponent

For this move there were 2 different implementations in GUI and the Inspector. I ended up choosing the GUI implementation since it did not rely on global state.

@deltakosh I tested in local dev and there seemed to be no difference but if you want to double check this is fine. :)

@deltakosh I tested in local dev and there seemed to be no difference but if you want to double check this is fine. :)


Clarified that QuerySet.filter() and Q() can both be empty.

@adamchainz Thanks for this patch :+1:, however I agree with Tim, I don't think it clarifies much about dynamic creation of combined (possibly empty) Q conditions.

@adamchainz Thanks for this patch :+1:, however I agree with Tim, I don't think it clarifies much about dynamic creation of combined (possibly empty) Q conditions.

Yeah fair enough. Rather than modifying the referenece it might be better having a worked example of building a Q dynamically.

Yeah fair enough. Rather than modifying the referenece it might be better having a worked example of building a Q dynamically.


Update  icon  to support older versions of Unity

"d_ol_plus_act" is not available in older versions of Unity
Unable to load the icon: 'd_ol_plus_act'.
Note that either full project path should be used (with extension) or just the icon name if the icon is located in the following location: 'Assets/Editor Default Resources/Icons/' (without extension, since png is assumed)
UnityEditor.EditorGUIUtility:IconContent(String)
RecentSceneToolbar.RecentSceneToolbarGUI:OnToolbarGUI() (at E:/Github/Unity-Recent-Scene-Toolbar/Editor/RecentSceneToolbarGUI.cs:45)
UnityToolbarExtender.ToolbarExtender:OnGUI() (at E:/Github/Unity-Recent-Scene-Toolbar/unity-toolbar-extender-1.4.3/Editor/ToolbarExtender.cs:143)
UnityToolbarExtender.ToolbarCallback:OnGUI() (at E:/Github/Unity-Recent-Scene-Toolbar/unity-toolbar-extender-1.4.3/Editor/ToolbarCallback.cs:108)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) (at C:/buildslave/unity/build/Modules/IMGUI/GUIUtility.cs:179)

I replaced it with "Toolbar Plus" from Unity-2018.1.6

Thanks for the PR!
I would like to add the symbol condition UNITY_2019_1_OR_NEWER so that the icon does not change in Unity 2019 and the above.


Generate routes dynamically based on locale

Is there a good solution to add routes dynamically, per request, based off of req.locale?
For example, a desired solution would be some middleware like so:
// routes.ts
const routes = require('next-routes')
module.exports = routes(); // export routes object as normal

// middleware.ts
export const setRoutes: express.Handler = (req, res, next) => {
  const routes = require('./routes');

  // require a configuration file containing all routes in various languages
  const routeDefinitions = require('./route-definitions');
  const { category } = routeDefinitions[req.locale];

  // define the route based off the locale
  routes.add(`/${category}`, 'category');
}

// server.ts
const app = next({ dev })
const routes = require('./routes');
const handler = routes.getRequestHandler(app);

Although this doesn't seem to work, like it will only accept routes being added when next-routes is initially required.
I've looked at next-routes-with-locale but the main downside with this is you need to pass the locale on all Links and the locale is prefixed as part of the URL.

Managed to get around this issue just by allowing the route to accept multiple strings, e.g.
routes.add(`/(${categoryEN}|${categoryNB})`, 'category')

Then checking in the page's getInitialProps if the path matches the expected path for that locale, if it doesn't match send a 404 e.g.
import { localeRoutes } from './locale';
import { error } from './actions';

static async getInitialProps({ query, store }) {
  const path = query['0'];
  const { locale } = store.getState().intl;
  if (path !== localeRoutes[locale]) {
    store.dispatch(error(404))
  }
  return {};
}

This seems to solve the issue in a relatively straight forward way. If anyone comes across a similar problem with a different solution, please feel free to share it here.


EN: Content "Left-hand nav"

Summary: Documentation of component guidance in EN for the Left-hand navigation component on the Design System website.
Including use cases, how to use guidance, accessibility guidelines and more.
Acceptance Criteria:

[x] Component Kickoff
[x] Component review
[x] Sync with Dev and Design
[x] Research and consulting other design libraries
[x] Component ID (name, definition, example image
[x] Use case (when to use guidance & related components)
[x] How to use guidance
[x] Accessibility guidelines
[x] Inclusive language
[x] Descriptive text for images
[ ] Translation & Localization
[ ] Bilingual review – content design
[x] Ensure consistency: ordering, terminology, high level voice/tone/style
[ ] Final review

[ ] -  Assemble best practice research writing error messages
[ ] -  Meet with developer to review planned functionality
[ ] -  Prototype pages (use case, design, code)
[ ] -  Draft content for use case
[ ] -  Draft content for design
[ ] -  Draft content for code
[ ] -  Review and validate content with designer(s) and developer(s)
[ ] -  Bring to content critique

@nchoquet Side navigation's ready.

@SmartMouthWords, translation is ready here:
https://docs.google.com/document/d/1rpl65Se7vOnkZ0nXdhoLt0IpoBFgrqo4yc7JCBUsuKo/edit?usp=sharing

✅ Final bilingual content review complete

Missing "Also called" section
Missing Visuals for French Anatomy
Should be released in tandem with Top navigation

🚀 Ready for dev

@ethanWallace @melaniebmn @ClementineHahn

EN: https://docs.google.com/document/d/11QfydplaM-fDoxjJkNd7u778o1cS5JMFQf0jApzeGks/edit
FR: https://docs.google.com/document/d/1rpl65Se7vOnkZ0nXdhoLt0IpoBFgrqo4yc7JCBUsuKo/edit


Split contributing guide into smaller guides

There are various ways to contribute, let's split the CONTRIBUTING.md guide into these three separate guides:

Suggestions
Raising issues by using BBC A11y against your content
Contributing code changes

Fixed in master


WIP: Switch to pathlib

Switching code from using os.path to using Pathlib (per request in https://github.com/hjacobs/pykube/pull/55)

@hjacobs Marked this as WIP as I clean up the tests, I just wanted to make sure this is what you were looking for?
Basically I found once I started replacing some references it made sense to carry all the way through, that is to only interact with Paths and not strings for as long as I can.

Apologies for the delay here, this is now finished:
luke@Lukes-MacBook-Air pykube % grep -r 'os\.path' pykube tests
luke@Lukes-MacBook-Air pykube %


How to get the index of 3d landmark in BFM model?

I find the index of 3d landmark is so accurate. How can you get it?
I want to use BFM 2019 model for face reconstrustion. Can you tell me how to get the index of 3d landmark.
Thank you!

Hi, Can you slove this problem? I also want to know how to get 3D landmark index. Can you tell me? Thank you.


Add assert_asset_exists, assert_href_exists

Related issues and pull requests

Closes #84

Description
Gives us more insight into why the existence check failed.
Checklist

[x] Add tests
[x] Add docs
[x] Update CHANGELOG

Codecov Report
Patch coverage: 69.56% and project coverage change: +0.56% :tada:

Comparison is base (61be760) 78.69% compared to head (28dc693) 79.25%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #85      +/-   ##
==========================================
+ Coverage   78.69%   79.25%   +0.56%
==========================================
  Files          15       15
  Lines         859      863       +4
==========================================
+ Hits          676      684       +8
+ Misses        183      179       -4

Files Changed
Coverage Δ

src/stac_asset/__init__.py
100.00% <ø> (ø)

src/stac_asset/http_client.py
55.81% <33.33%> (+3.64%)
:arrow_up:

src/stac_asset/planetary_computer_client.py
42.10% <50.00%> (ø)

src/stac_asset/s3_client.py
52.30% <50.00%> (+3.03%)
:arrow_up:

src/stac_asset/client.py
79.34% <60.00%> (-1.77%)
:arrow_down:

src/stac_asset/filesystem_client.py
92.00% <66.66%> (-3.46%)
:arrow_down:

src/stac_asset/_functions.py
90.30% <100.00%> (+0.26%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update docs

There is tpm2-tss on several places and the RELEASE.md duplicates the doc/RELEASE.md this project already has. I'd prefer to keep the current one as it has be carefully tailored.

Oh I didn't see the doc/RELEASE.md, sorry. I will correct that.

There is tpm2-tss on several places and the RELEASE.md duplicates the doc/RELEASE.md this project already has. I'd prefer to keep the current one as it has be carefully tailored.

Oh I didn't see the doc/RELEASE.md, sorry. I will correct that.

updated, sorry for the delay I forgot about this.

Thanks.


Fix Docker builds

Hi guys! :D
Docker was failing to build, I fixed it.
Also I think either it's not pushed to quay.io, or it's private. Could someone check, please?

Hey Kieran,
how is it going mate?
:P

Not so bad thanks 😄


Fixing issue with Pandas data frame trait

There was a bug in PandasDataFrame trait where we were assuming that the index is not named. This PR fixes that issue. Because of this, we were getting the issue in MarketMap when we click on the cell.
There is another reason why this issue surfaced only now. Previously in ipywidgets, only attributes whose value changed were sent across to the python side on call of .touch function. But now, in the first and second calls, many more attributes are sent across. @jasongrout is looking at the issue on the ipywidgets side.

@SylvainCorlay From what I can see, in the first call to touch after the model is initialized, the attribute _buffered_state_diff of the WidgetModel has all the attributes of the Model and hence all the attributes are sent across to the python side.
After the first two calls (investigating why the second call is affected), _buffered_state_diff seems to be working fine. Do you have any idea why this could be the case?

Are you using ipywidgets 5.x or master?
On Aug 15, 2016 11:28 PM, "ssunkara1"<EMAIL_ADDRESS>wrote:

@SylvainCorlay https://github.com/SylvainCorlay From what I can see, in
the first call to touch after the model is initialized, the attribute
_buffered_state_diff of the WidgetModel has all the attributes of the
Model and hence all the attributes are sent across to the python side.
After the first two calls (investigating why the second call is affected),
_buffered_state_diff seems to be working fine. Do you have any idea why
this could be the case?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bloomberg/bqplot/pull/272#issuecomment-239934713, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACSXFkbDKpQSNNbMutMdJLlB8YdlTEbNks5qgNn3gaJpZM4Jkwpm
.

I was using ipywidgets master.

ok, master changes the way we define default values that may cause something like this. When we switch to ipywidgets 6, there model.defaults will have to be changed to a function...

model.defaults doesn't have to change to a function. But anything that refers to the defaults from the base widget should use _.result (http://underscorejs.org/#result) or the equivalent, just like backbone does (http://backbonejs.org/docs/backbone.html#section-54). This is backwards compatible and covers the case where defaults is a function or an attribute.
So, for example, https://github.com/bloomberg/bqplot/blob/2d597baf9b3c581905f8d75f7b5c44ed09b7b4db/js/src/HandDrawModel.js#L22 would be (I think, without testing...)
defaults: _.extend({}, _.result(widgets.WidgetModel.prototype, 'defaults'), {

Yeah but to be more homogeneous across the board, I would prefer it to always be a function.

sure, but in the interim, downstream libraries need to have a backwards compatible solution. So even if they move to having a function, they should still use something like _.result to get the upstream values.


Bottom navigation stuck at the top

What kind of Issue is this?
Question / Problem
This might be a little premature, but I'm going through the walkthrough of rendering a bottom tab navigator, and it's stuck at the top of the screen? I didn't see any styling on the code given as an example. So I feel like it's simple that I'm missing. Or is there actually a problem?
Screenshot for reference, code below:

Here's my code:
Navigation.js
import React from 'react';
import BottomNavigation, { FullTab } from 'react-native-material-bottom-navigation';
import { View, Text } from 'react-native';

const tabs = [
  {
    key: 'games',
    icon: 'gamepad-variant',
    label: 'Games',
    barColor: '#388E3C',
    pressColor: 'rgba(255, 255, 255, 0.16)'
  },
  {
    key: 'movies-tv',
    icon: 'movie',
    label: 'Movies & TV',
    barColor: '#B71C1C',
    pressColor: 'rgba(255, 255, 255, 0.16)'
  },
  {
    key: 'music',
    icon: 'music-note',
    label: 'Music',
    barColor: '#E64A19',
    pressColor: 'rgba(255, 255, 255, 0.16)'
  }
];

const renderIcon = ({ isActive }) => (
  <View>
    <Text>Hello</Text>
  </View>
);

const renderTab = ({ tab, isActive }) => (
  <FullTab
    key={tab.key}
    isActive={isActive}
    label={tab.label}
    renderIcon={renderIcon}
  />
);

export const Navigation = () => (
  <View>
    <BottomNavigation
      renderTab={renderTab}
      tabs={tabs}
    />
  </View>
);

App.js
import React, { Component } from 'react';
import { Navigation } from './Navigation';

class App extends Component {
  render() {
    return (
      <Navigation />
    );
  }
}

export default App;

As a follow up, I copied and pasted your code right into my editor and got the same result.

The example in the readme should reproduce the bottom navigation at the bottom.
    <View style={{ flex: 1 }}>
        <View style={{ flex: 1 }}>
          {/* Your screen contents depending on current tab. */}
        </View>
        <BottomNavigation
          onTabPress={newTab => this.setState({ activeTab: newTab.key })}
          renderTab={this.renderTab}
          tabs={this.tabs}
        />
      </View>

The outer view with flex: 1 will cause the view to fill the entire screen. The inner view with flex: 1 will cause the view to fill everything except the height of the bottom navigation, leaving it at the bottom.
Alternatively you can position it absolute at the bottom.

Ok great. I didn't see that on the root readme. I was looking at this one here that might need to be updated then. It wasn't very clear that flex needed to be applied there, although it does make sense (noob user here). I guess I have to play around with it still. The playground example either doesn't like me or it's not working, in that when you run it, it says that the sdk is out of date or something like that. I can't remember because I ran it the other night, but I thought it would be worth mentioning if other people have tried it unsuccessfully and haven't said anything.

Positioning the Bottom Navigation should work similar to positioning of other React Native Views. It doesn't position itself by default on the bottom, to make it more flexible and configurable.
Since this is not an issue with the Library, I'm going to close this.


[ruff 0.8] Remove deprecated rule UP027

Summary
Remove UP027 in Ruff 0.8. UP027 has been deprecated since https://github.com/astral-sh/ruff/pull/12843, which landed as part of Ruff 0.6 (released on August 15th).
Test Plan

cargo test -p ruff_linter passes
git grep UP027, git grep UnpackedListComprehension and git grep unpacked_list_comprehension all show no references to the rule remain outside of the changelog
Wait for the ecosystem report to see how much impact this has

Wait for the ecosystem report to see how much impact this has

Seems like it's not possible to get an ecosystem report here, because of the fact that this PR targets the ruff-0.8 branch, and will be the first commit on the ruff-0.8 branch that deviates from main. Once this is merged into the ruff-0.8 branch, I'll open a PR to merge that branch into main and take a look at the ecosystem report on that PR.


docs: fix link in README

This PR fixes a broken (wrong formatted) link in the README and introduces a styled block quote instead of the ATTENTION section.

Nice catch, thank you!


  However, one spot that's lacking is the ability to use the output of one query as the input for another without re-uploading the query results using s3.to_parquet.
I would like an option for athena.read_sql_query in CTAS mode to keep the temporary table created from the query results, embed the temporary table name in query_metadata, and provide a destructor method that deletes the temporary table and S3 data.
If this were available I could run a query in one Jupyter cell, view the results (potentially in batches), and then query against those results in Athena or join in additional data, while finally cleaning up the temporary state in a later cell.

Hi @ddrinka, would the create_ctas_table achieve what you have in mind? It creates a CTAS table, returns the query metadata and keeps the S3 objects. Setting the wait argument to True ensures that the query completes. In fact, read_sql_query is using this same method under the hood.
Also note the keep_files argument in read_sql_query which preserves the S3 objects from the CTAS

@jaidisido In my use case I'd still like the results delivered locally, but with the table as well as the S3 files left behind.  The benefit to me is the notebook user gets a preview of the intermediate query results (optionally just the first batch of results), but the data also exists as a temporary table that future Athena queries can use.
If you think of a Spark workflow where you might combine a series of operations or SQL queries, while being able to view any of the intermediate results, but with the power of Athena backing each workflow step, that's what I'm trying to emulate using wrangler.

I feel this is too opinionated and specific of a use case. The library aims to provide decoupled methods to help develop your own workflow like the one you are describing but we want to avoid catering for narrow ones if they are not generic enough


More Videos Button on front page goes to wrong place

Describe the bug
The More Videos button on the home page point to Leroy Merlin's YT channel.
Expected behavior
Should go to here: https://www.youtube.com/channel/UCoSPSd6Or4F_vpjo4SmyoEA
Additional context
Couldn't see how/where to edit the link from the more-videos-button

whoops :) fixed. it was here: https://github.com/InnerSourceCommons/innersourcecommons.net/blob/master/layouts/shortcodes/more-videos-button.html


TLS Fake

hi
The proxy link that is with Fake Tls ( hash and base64 ) Some of the Iranian internet is not working and cannot be connected
At the beginning and after the server config
And the server is not filtered
Where's the problem?

You have probably made a mistake somewhere. I can confirm this proxy works in Iran with no issues.
Dont forget that telegram client SHOULD be upgraded to the latest version, otherwise TLS proxy wont work.

You have probably made a mistake somewhere. I can confirm this proxy works in Iran with no issues.
Dont forget that telegram client SHOULD be upgraded to the latest version, otherwise TLS proxy wont work.

Thanks, the problem was resolved and the telegram was not updated
How can I connect to any user
Secret code different with this method Base64 Fake TLS
But there is a basic code secret in Configuration

How can I connect to any user
Secret code different with this method Base64 Fake TLS
But there is a basic code secret in Configuration
for example
500 > Links with different Fake tls secret ,

Sorry, I don't understand your question

How can I connect to any user
Secret code different with this method Base64 Fake TLS
But there is a basic code secret in Configuration
for example
500 > Links with different Fake tls secret ,

Sorry, I don't understand your question

I need 500 proxy links with different secret ( Base64 Fake tls )

Theoretically I guess you can define 500 handlers with 500 different secrets, But I am not sure if it is a good idea practically.
Probably @seriyps can shed some light on this matter.

Theoretically I guess you can define 500 handlers with 500 different secrets, But I am not sure if it is a good idea practically.
Probably @seriyps can shed some light on this matter.

Thank you
Waiting for @seriyps comment

@ZarinNegah it's described here: https://github.com/seriyps/mtproto_proxy#personal-proxy--multi-secret-proxy
So, you enable policy to only allow connections with certain TLS domains and generate unique domain & unique link.

@ZarinNegah it's described here: https://github.com/seriyps/mtproto_proxy#personal-proxy--multi-secret-proxy
So, you enable policy to only allow connections with certain TLS domains and generate unique domain & unique link.

thank you
I didn't understand how to apply these codes
Because I don't have much knowledge of this language
You have tips for using and user the following section
https://github.com/seriyps/mtproto_proxy#personal-proxy--multi-secret-proxy


Add template block for admin title name.

This change adds a template block around the "Wagtail" string in the skeleton title, allowing implementors to override the title instead of having to override the entire skeleton.html template.
Unsure if this was omitted intentionally or not (for branding?), but figured I'd open a PR to gauge interest.

Hey @nicksergeant,
thank you for your pull request.
This is a duplicate of #5344 (also very recently opened). I cannot comment from the maintainer's point of view, but it does look like there is interest for this, so imho it can't hurt

@zerolab ah great! That one has documentation also. Closing in favor of #5344.


Configure CI for iOS build and deploy

CircleCI have granted us access to MacOS executors, so we can do this now


Java installation handling

The Elasticsearch module handles the java installation, the Logstash module does not. Is that a decision which has been made for purpose or just a missing feature?

@jarpy @electrical do you have any information on this?

Not handling Java installation is by design (even though it still exists in the Elasticsearch module).
For me, one of the largest sources of pain in the Puppet community is modules that cause duplicate resource declarations by over-extending their scope. It's true that Java is a requirement for Logstash, but that doesn't mean the Logstash module should directly install it. All the logic we should ever need is nicely encapsulated in puppetlabs/java. Embedding a (less complete) implementation of the same logic in the Logstash module is a waste of effort and a source of resource conflicts.
This is the best description of the issue I've seen: https://www.youtube.com/watch?v=v9LB-NX4_KQ&feature=youtu.be&t=44m30s
In fact, as a Puppet developer, that whole video kinda changed my life. :)

Ok, so I would suggest to add a snippet to the Readme about that. I will do a PR


Update app-editor.component.html DOM text reinterpreted as HTML

By using innerText, it will avoid the risk of HTML injection, as these properties automatically escape any HTML special characters in the provided text. This helps prevent cross-site scripting (XSS) vulnerabilities by treating the input as plain text rather than interpreted HTML.

Hi @evil-shrike Could You Please Review This PR
Thanks

see https://github.com/google/triggerator/pull/17


Default Spack install fails

Describe the bug
Fixing #299 with this commit seems to have caused a side effect when installing with Spack.
To Reproduce
The default version of Mercury in the Spack package is 1.0.1. So if installing everything fresh with Spack, spack install mercury, you get<EMAIL_ADDRESS>and<EMAIL_ADDRESS>which then reproduces the issue in #299:
[prompt]$ spack install mercury
==> Installing mercury
⋮
==> Executing phase: 'cmake'
⋮
  >> 30    CMake Error at src/util/CMakeLists.txt:38 (CHECK_SYMBOL_EXISTS):
     31      Unknown CMake command "CHECK_SYMBOL_EXISTS".
     32
     33
     34    -- Configuring incomplete, errors occurred!

After troubleshooting and finding the issue, was able to use workarounds of either using the master branch:
spack install mercury@master

or an older version of cmake
spack install mercury<EMAIL_ADDRESS>
Expected behavior
One of two things,

spack install mercury will default to a working combination (newer version, master branch, or older cmake)
spack install<EMAIL_ADDRESS><EMAIL_ADDRESS>will provide a proper error

Platform (please complete the following information):

System description
Compiler version: [gcc 4.9.3]
Plugin and protocol used [ofi, sm]
Dependency version [spack defaults: libfabric 1.8.0, bmi, boost 1.70.0]

Potential solutions
Add a conflicts or depends_on to the Mercury Spack package so users know what is wrong if trying to install with the latest cmake and default version.

Add a conflicts:

conflicts('^cmake@3.15.0:', when='@:1.0.1')

results in:
[prompt]$ spack spec<EMAIL_ADDRESS><EMAIL_ADDRESS>Input spec
--------------------------------
mercury

Concretized
--------------------------------
==> Error: Conflicts in concretized spec
⋮
1. "^cmake@3.15.0:" conflicts with "mercury@:1.0.1"

or

Add a depends_on:

depends_on(cmake@:3.14.999', when='@:1.0.1', type='build')

results in:
[prompt]$ spack spec<EMAIL_ADDRESS><EMAIL_ADDRESS>Input spec
--------------------------------
mercury

Concretized
--------------------------------
==> Error: An unsatisfiable version constraint has been detected for spec:
⋮
mercury requires cmake version <IP_ADDRESS>:3.14.999, but spec asked for 3.15.1

Other combinations (i.e., spack install mercury@master) succeed.

Right I don't think the fix for #299 causes any side effects. It's just that the Spack package needs to be updated so that cmake >= 3.15 does not get used with mercury 1.0.1. I'll fix the spack package to reflect that.

True. Probably not the best choice of wording on my part.
Thank you for the response and for looking into it.

With https://github.com/spack/spack/pull/12504 merged in upstream spack this should be fixed now.


Test issue

Test issue

Ahoy! Thank you for opening your first issue here!\nIf this request is regarding troubleshooting your application, please reach out to the support team via https://support.twilio.com.


enable relative paths for directory param in rake export

Currently the evm:export commands require a fully qualified path for the "directory" parameter.  This simple change enables the script to handle relative paths too.

Hi @mikebutak .  Thanks for the contribution!  Can you fix the style issues caught by the bot?

@Fryguy should be ready after the build.

It looks like it passed all tests.

@Fryguy saw the style issues you were talking about and corrected them.

Would it make sense to squash commits to just 1 for this one-line change?

yes @chessbyte I'll submit a clean PR.


back to top

hey
I didnt wanna make some pr that would impose on style of your design, so I'd like to request back to top idea here, if possible.

You're totally welcome to suggest changes!


Mesh com 1.5

last updates on MS 1.5 to develop

@martin-tii, should this be merged and pushed for another approver or canceled?

new changes will be done on this code, so this PR is not necessary


Sound Classifier: show progress during preprocessing

Currently ~80% of training time is spent doing feature preprocessing. Once #1216 is fixed we should be spending a lot less time doing feature preprocessing, but it will still be a significant amount of the total train time. We should show some progress information during feature preprocessing.

It would also be good to add progress printing for VGGish feature extraction too.
The current breakdown of training time (with #1216 and coremltools not supporting batching):

~80% preprocessing
~15% VGGish feature extraction
~5% Train custom model


ubuntu.sh: is that possible run source ~/.profile instead of suggest user reboot/relogin

Describe problem solved by the proposed feature
Simplify toolchain installation progress.
Current tip: Reboot or logout, login computer before attempting to build NuttX targets

I think we do this because usermod changes don't happen until after reboot/login. So in fact this may only affect the case where you also want to upload the new binary at the same time as build. That said, I suspect that will be a lot of cases.
Did you try building or building/uploading? If it works, perhaps we could be more specific note ie "before attemptiong to upload NuttX targets". Not sure it is worth it though.

@hamishwillee The script can run source ~/.profile at final to apply the PATH change to avoid reboot/login.
If do not do this, system can not find arm-gcc that just downloaded.
https://github.com/PX4/Firmware/blob/master/Tools/setup/ubuntu.sh#L158-L164

@bys1123 Can it find it anyway - as per your post https://github.com/PX4/Firmware/issues/14916 ? :-)
My point above though is that we can do this and they will be able to build. But they will still require a reboot if we want them to be able to do uploads because reloading th profile does not fix the usermod problem. So happy to make this change to load the profile, but we still require the reboot.
Make sense.?

@bys1123

The script can run source ~/.profile at final to apply the PATH change to avoid reboot/login.

Correct but as @hamishwillee wrote the usermod changes require logout/login. Alternatively, you could use newgrp but like source ~/.profile you have to do it in every console and that's hard to explain to a user. In my opinion it's much easier to just tell users to logout and log back in.

@julianoes Understand, thanks for explain.


fix: inlay hints maybe emit too early

closes #395

Based on the comments in #395, it looks like this doesn't really fix that problem.

Based on the comments in #395, it looks like this doesn't really fix that problem.

no, if no this, regardingless project size, it would be high possibility failed,
seems gopls really was a bit delay (not really ready) to response,
besides this is a refine to inlay hints code anyway,
so this PR is required.
--
shane.xb.qian

thanks to that patch on channel, i reduced the value of delay a bit, should be a balanced value now, wish so.

or let it be, since that channel patch perhaps was better or good enough.


Fix ko setup

Like knative-sandbox/eventing-rabbitmq#178 to avoid any problems during the release process
Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>

/assign @matzew

/assign @matzew

/test pull-knative-sandbox-eventing-kafka-integration-test-channel-consolidated-sasl

/test pull-knative-sandbox-eventing-kafka-integration-test-channel-consolidated-sasl


osx plugin: add partial support for iTerm2

It looks that iTerm2 can be controlled using the same osascript commands.

it may be duplicate with https://github.com/robbyrussell/oh-my-zsh/pull/4907

You are right, closing then.


Spinouts not working

the spinouts are just sitting in thornstalks not moving at all or damaging the player

This issue has been fixed in newer versions.

Spinouts in 12.2 are still not working.  It is not clear if this is because later versions broke them again or if other mods are interfering with their behavior (Special AI in particular is suspect)


Add skipping light updates option

New feature:

Option to skip light updates.

It solve request https://github.com/Foddy/node-red-contrib-huemagic/issues/107
Regards,
Mx

Sorry... Unfortunately, this was not the right place that causes API limit errors, which is why I had to revoke it. The requests to the bridge take place in the "recheck" method under "hue-bridge-config.js".
But I added a small delay between requests to the Hue Bridge (in v2.0.5). Maybe this solves your problem? :S

When enabled, this feature just disable the bridge.events.on(...) function like the "universal mode". The idea behind is that we don't want to recieve auto or delayed updates from the light but only on demand from an input flow like inject.
I don't get the API limit errors except if we spam the manual update.

Hm I understand. Please give me some time so I can implement the whole thing a little more "elegantly". It would be optimal if this setting also means that the requests on the bridge no longer take place and that the setting can also be used for groups and other nodes.
I will come back to this soon!

Should be available in v2.1 :)!

Hi @Foddy,
Thanks for you update, I tested in 2.2.2 but unfortunately it does not have the expected behaviour.
We don't receive any update from an input flow when "Skip events from node" is set to true.
My fault, I think that we did not work on the same feature.
On my side "Skip events from node" means doing nothing when light change but it may work only on demand.
Here an example of flow who require this feature:

In this flow, the blink alert will loop infinitly and this is why the "Skip events from node" is required for.
I hope my explanation is better this time.


Use correct service mapping based on RMW_IMPLEMENTATION and ROS distro

Cyclone DDS uses a different topic mapping for services. Cyclone is the standard middleware in galactic.
Fixes https://github.com/dora-rs/dora/issues/449

I did some tests using RMW_IMPLEMENTATION=rmw_cyclonedds_cpp. The requests are received correctly by the service server, but the responses never reach the client for some reason.

Apparently the Cyclone mapping of the the ros2-client crate was only tested against ROS2 galactic, so it might not be compatible with humble.


index.md can't build automatically

If I add a new post, the Jekyll will generate a new .html file in _site, but it can't update index.html automatically. Here is my index.md. Everything is ok of I use Jekyll without Docker.
---
title: Home
layout: page
---

{% for post in site.posts %}
  {% capture y %}{{post.date | date:"%Y"}}{% endcapture %}
  {% if year != y %}
    {% assign year = y %}

{{ y }}

  {% endif %}

    <time datetime="{{ post.date | date:"%Y-%m-%d" }}">{{ post.date | date:"%Y-%m-%d" }}</time>
    {{ post.title }}

{% endfor %}

This is a problem with Docker and is a known issue, if you are not on Linux use Docker Native for your operating system, if you are on Windows inside of Ubuntu SubSystem, use Polling, if you wish to continue to use what I assume is Docker Machine, please also force polling which will resolve this issue.


Avoid using cached request

Fixes #158

There's a common issue when hitting the cart.js endpoint from Shopify,
it's cached by default so it's causing an issue when loading items from
the cart, sometimes the cart shows up as empty when hitting the back
button.

This commit adds a timestamp to the API call to get a non-cached
response. This approach is done by Shopify itself to avoid loading cached assets

Note: I am maintaining a Shopify theme and we have a custom slide cart component created from scratch (no libraries used), we faced the same issue and before creating a fix for this I found this library and I would like to contribute to it with that simple fix.

@gavinballard whenever you have a chance could you please take a look at it?

@8geonirt Released in 1.0.2.

@8geonirt Released in 1.0.2.

Awesome! Thanks for taking a look at it 👍

It seems this isn't working anymore and the cart.js endpoint is being cached regardless.

Another workaround:
    $.ajax({         type: 'GET',         url: '/cart.js',         cache: false,         dataType: 'json',         success: function(cart) {             CartJS.init(cart, {                 "moneyFormat": "{{ shop.money_format }}",                 "moneyWithCurrencyFormat": "{{ shop.money_with_currency_format }}",                 "requestBodyClass": "cart-loading"             });         }     });

Thanks @capatina. I have an underlying change to pass cache: false in the Ajax request, should be released shortly.


feat: ros2 tf graph

Hi,
here is another contribution for this project. I have created (with help of F1rrel) ROS2Tf OmniGraph, which uses omni.isaac.ros2_bridge.ROS2PublishTransformTree to publish transform tree on ROS2 topic. Name of the topic is by default /quadrotor/tf. Type of topic is tf2_msgs/msg/TFMessage.

Graph instance is created under vehicle with default name /tf_pub.
The vehicle uses body instead of standardized base_link, so base_link is created and body is connected to it. Then transforms for rotors and sensors are attached to body.
This OmniGraph creates transform for every sensor, which has attribute prim_path (e.g. Lidar - can be found in another pull request).

The transformations can be viewed in Rviz2 using:
rviz2 --ros-args -r __ns:=/quadrotor -r /tf:=tf -r /tf_static:=tf_static. Fixed Frame needs to be set on base_link and TF visualization needs to be added.
In .zip file below you can find following examples using ROS2Tf OmniGraph:

9_ros2_graph_tf.py contains only ROS2Tf OmniGraph.
9_ros2_graph_tf_lidar.py contains ROS2Tf and ROS2Lidar OmniGraphs (to work properly, ROS2Lidar pull request needs to be merged into main).

9_ros2_graph_tf_examples.zip

Hi,
I had to force-push some changes due to TF creation of some sensors, such stereo-camera, where additional parent link need to be created to connect left and right camera to it.

This looks nice!
I won't have time to merge it this weekend, but probably at the end of next week, I will test this and check the best way to handle TFs for those who don't want to install the built-in package. What I have now in Python doesn't seem to be the preferred solution for most.


Discussion: mandatory non-interactive defaults

Discussion
Non-interactive default rules are currently framed as optional.
However, parts of the current implementation assume that non-interactive defaults are mandatory (e.g. inclusion/paths.go). If desired, we can modify the current implementation to support optional non-interactive defaults. Before we do so, I'm wondering why non-interactive defaults are optional rather than mandatory (i.e. a block validity rule)?

The original reasoning behind allowing for non-deterministic square layouts was to allow for tighter packing of the square via allowing some form of interaction between the block producer and the users submitting blobs. With recent changes specified in ADR009, and the potential to reduce padding even further with other mechanisms #1161, this might not be needed any more.
This would mean that if we wanted to increase the packing efficiency, then it is up to us, and the community, to build such tooling. It also has the benefit of forcing all validators to use an efficient packing algorithm, instead of only the sophisticated ones.
Deterministic block layout would allow us to simplify the implementation by not having to wrap PFB transactions with the index when we gossip them. As pointed out by @cmwaters, doing so would significantly simplify the compact blocks implementation, because we would be able to reference the transactions gossiped via its hash. Not only that, but it would also stop block producers from setting an arbitrarily setting the max square size.
Notably, deterministic block layouts might limit other features that we have discussed, such as adding priority metadata to specific blobs within the same namespace, or allowing for custom ordering of blobs in the same namespace.

I would be in favour of mandatory non-interactive default rules, but I do not know the consequences and possible limitations.
Custom ordering within the same namespace could still be possible if the deterministic block layout has an ordered set of transactions as an input. The order can be specified in the input. The only downside is that it would follow the non-interactive default rules if that is one.

I would like to elaborate on some of these points:

When we're talking about deterministic construction, we're talking about the square and not the block (these are two distinct abstractions to me). A block producer still has all the sovereignty to dictate what transactions go in and in what order. This means that there is still a market for MEV infrastructure and block producers can think of ways of maximising their return.
I think the square should be an internal abstraction that both block producers and users are unaware about. How all this works is rather complex. It's far simpler for users to have the conventional mental model of "I post blob, I get blob". Non-interactive submission is simpler to use. Similarly, the block producers shouldn't be subject to a system of constraints where they need to think of novel methods of packing.
I think it's important that celestia's core function (i.e. publishing blobs) works seamlessly out of the box. Other areas we may want to leave the design space open for third party infra and services but I think relying on it here may impact a users experience of Celestia. What this means is that if we want interactive PFB submission, we should properly support a form of that flow and not rely on others. That way we're directly responsible for users positive experience.
Padding is a computational cost, not a storage cost or a bandwidth cost. Computational costs are generally the cheapest (and the quickest). While there are undoubtedly gains to be made for more efficient packing of the square. These are negligible and I don't think they should be our top priority.
As mentioned, it leads to a far simpler implementation of compact blocks.
We are still able to improve the efficiency of the constructing algorithm over time.
We should still be wary of the consequences of human error. If we implement a non-deterministic deterministic construction algorithm this can be consequential to the liveness of the chain.

If we have mandatory non-interactive default rules, then we will get a nice side effect that the square can be recomputed given an ordered list of transactions. This could enable more compact storage requirements for full nodes, in particular archival nodes. Because computation is less expensive than storage.

Per recent sync discussion, we are moving forward with this! and it will be incorporated before mainnet.


Fix installation of truffleruby+graalvm on macOS

See #1459.
This way avoids moving and removing files.

@ssnickolay checked and it works.


Carthage categories

I'm currently looking into this library and am trying to find a solution to use the categories with Carthage. The 'copy the files into the checkout folder'-option doesn't work for me, because I use a automate build system, which updates all the dependencies.
I agree, that linking all the categories would be a bad idea.
My proposal to solve this problem is, having separate schemes/targets for each category.
These targets would depend on the PromiseKit and include the code of their category.
Pros of this solution are:

The user can simply add the build binaries of the categories that he requires.
There is no linking of unnecessary (system) libraries
Dependency management with carthage would work, even on automated build servers.

Cons:

A lot of schemes and targets would be required (platforms * categories = something like 60 targets and schemes)
All schemes of a platform would be build by carthage with every carthage update --platform ***

The best solution would be the support of "sub-projects" by carthage, but until then I think this is a possible solution.
I could create thees targets if this is something other user a interested in.
Would appreciate any feedback.
PS. I've already added the iOS Foundation category on the carthage branch of my fork.

I agree that this sounds like an issue that needs resolved. I'd like to not have anyone prevented from using PromiseKit just because their configuration is different. And automated build systems are fairly common. However, I'm hesitant to introduce that level of complexity into the project just for Carthage. Forgive me, I haven't used an automated build system myself and am not super familiar with Carthage; can you elaborate a little more on the specifics of the issue?

The thing is that I usually don't want to include the code of a external framework in my internal codebase, because this makes updating way more complicated.
So in my case I want to use only the Foundation category in my iOS App. Obviously it would be inefficient to include all categories and with that link all necessary system frameworks.

Sorry, my questions was why specifically is copying the relevant category files into the Carthage checkout folder not sufficient under your automated build system? Again, I'm asking because I'm not familiar with your situation, so I'm trying to understand.

Oh, right.
The Carthage checkout folder isn't in our git (or in our case svn). On our build server we run carthage update which downloads all the dependencies and builds them. This is all done automatically with each commit.
For now I include the needed category classes in my project, but I don't really like this solution.

When copying the files into the project you are unable to automatically update them
Its third-party code in your project (which I personally don't like).
A small thing is that you don't have the usual access control. Because the classes are in your project you can access internal (swift) function/variables instead of only public

+1 For me the problem is similar:
We import PromiseKit via another dependency. And then we cannot import the categories because of that.

You could add a copy files phase to your app's project?

Thinking about it, that's even more than necessary, just drop the files into your app's project from the Carthage checkout. On fresh clones the files will show up red until Carthage is run.

We could add another xcodeproj with schemes for each category. But it in: Categories. Then we won't pollute the main xcodeproj with all the other schemes which is really our concern since managing the project is already tedious.

just tried to do the import from carthage checkouts. It seems to be a good idea but fails here:
#if !COCOAPODS
import PromiseKit
#endif

Removing the #if checks solves the problem.

Im still waiting for the day that SPM will be the default :)

The issue is tricky in this project. We have cocoapods + carthage . Carthage is used to import 1 library. this one lib imports Promisekit.

Ugh. Yeah.  Maybe I can figure out a solution by building two Frameworks in CocoaPods…

I honestly don't think we can manage this, it is quite a lofty maintenance burden on top of that which we already have regarding all the categories (podspec + tests).
I maintain the solution is to drop the files from the Carthage checkout into your xcodeproj. Carthage checkouts the files into your source tree, so it seems an acceptable compromise.
When and if Xcode allows one scheme for multiple platforms we will add schemes for the categories, modify our tests to use the schemes and then also be able to easily test tvOS and watchOS which currently we do not for the same reasons outlined above.
Sorry.

@mxcl I see you are putting all the categories in separate repo. That solution is way better and cleaner!!!

Since my discovery of Single-scheme, multiplatform targets I have implemented this as requested.
Each category is now a separate repository at https://github.com/PromiseKit
So you can request them separately in your Cartfile.
For CocoaPods we import the sources for the categories using git submodules, so nothing has changed for CocoaPods users.


[AutoPR cdn/resource-manager] [test, pls ignore]

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4604

Closing PRs that are older than 1 month.


train using Pytorch1.8.0

I am a freshman.
I use Pytorch1.8.0 but got this error, but do not know how to fix...
Traceback (most recent call last):   File "main.py", line 201, in <module>     train()   File "main.py", line 101, in train     loss, scalar_outputs, image_outputs = train_sample(sample, compute_metrics=do_summary)   File "main.py", line 159, in train_sample     image_outputs["errormap"] = [disp_error_image_func()(disp_est, disp_gt) for disp_est in disp_ests]   File "main.py", line 159, in <listcomp>     image_outputs["errormap"] = [disp_error_image_func()(disp_est, disp_gt) for disp_est in disp_ests]   File "/home/rc/anaconda3/envs/DL/lib/python3.7/site-packages/torch/autograd/function.py", line 262, in __call__     "Legacy autograd function with non-static forward method is deprecated. " RuntimeError: Legacy autograd function with non-static forward method is deprecated. Please use new-style autograd function with static forward method. (Example: https://pytorch.org/docs/stable/autograd.html#torch.autograd.Function)

我也是这个问题，请问你解决没？

我也是这个问题，请问有解决的吗

你好 这个问题最后得到解决了吗

I solve this problem, and the code works in pytorch 1.13.0. Here is my solution.

go to utils/visualization.py. In class disp_error_image_func, add @staticmethod before forward and backward function
go to main.py. change [disp_error_image_func()(disp_est, disp_gt) for disp_est in disp_ests] to [disp_error_image_func().apply(disp_est, disp_gt) for disp_est in disp_ests] in test_sample and train_sample function

But I don't know if this modification will affect the final result.


Attempting to use uninitialized value lstm/LSTMCell/W_0 on Distributed TensorFlow

On a cluster of Tensorflow, which has one ps server, and one worker:
def inference(self, inds, early_stops):

            ...

            with tf.variable_scope('lstm_encoder') as scope:
                initializer = tf.random_uniform_initializer(-0.08, 0.08)
                lstm_cell = tf.nn.rnn_cell.LSTMCell(self.hidden_units, initializer = initializer, state_is_tuple = True)
                if self.is_training and self.keep_prob < 1:
                    lstm_cell = tf.nn.rnn_cell.DropoutWrapper(lstm_cell, output_keep_prob = self.keep_prob)

       ...

 with tf.device(tf.train.replica_device_setter(worker_device =
                                                          '/job:worker/task:%d' % int(os.environ['task_index']), cluster = cluster)):
                train_op, loss = inference()

it turns out that:
tensorflow.python.framework.errors.FailedPreconditionError: Attempting to use uninitialized value sentiment/lstm_encoder/RNN/LSTMCell/W_0
     [[Node: sentiment/lstm_encoder/RNN/LSTMCell/W_0_S8 = _Send[T=DT_FLOAT, client_terminated=false, recv_device="/job:worker/replica:0/task:0/gpu:0", send_device="/job:ps/replica:0/task:0/gpu:0", send_device_incarnation=-5768356229269645157, tensor_name="edge_226_sentiment/lstm_encoder/RNN/LSTMCell/W_0", _device="/job:ps/replica:0/task:0/gpu:0"](sentiment/lstm_encoder/RNN/LSTMCell/W_0)]]
     [[Node: sentiment/lstm_encoder/RNN/LSTMCell/B/Assign_S4 = _Recv[client_terminated=false, recv_device="/job:worker/replica:0/task:0/gpu:0", send_device="/job:ps/replica:0/task:0/gpu:0", send_device_incarnation=-5768356229269645157, tensor_name="edge_214_sentiment/lstm_encoder/RNN/LSTMCell/B/Assign", tensor_type=DT_FLOAT, _device="/job:worker/replica:0/task:0/gpu:0"]()]]

I try to place variables on cpu or gpu, both of them did not work.

Can you share the code that you use to initialize the variables?

I push it to github, you can reference this

Thanks for sending over that code. There's nothing obvious in that file that would lead to variables being uninitialized, but I haven't read all of the files.
Could you try adding an explicit call to sess.run(init_op) in your session, to see if the initialization is being missed for some reason?
If that doesn't fix things, the next step would be to package up your code as a single file with no external code or data dependencies, and we can take a look at why the initialization isn't working as expected.

@mrry Thank you for your help. I have tried sess.run(init_op), it doesn't work. Before that, I wrote it on singal machine, putting all variables  and ops on gpu, it was fine. Then I modify it on distributed version, it does not work any more.
In fact, I write a cluster base on mesos,  I run this example on it. I am not sure if the cluster has bugs, although a mnist example can run on it
so I will update this issue

not yet, I rewritted my distributed code, and want to use sync_trainer instead async_trainer, but the gpu is busy,
so you will close this issue?

I'll close it for now, but please feel free to re-open if you can reproduce it with a smaller example!

Think I am running into something related to this issue on v1.0. Will see if I find time to get a small reproducible example going, but I encountered it doing the following:
Took cifar10 tutorial and instead of a convnet, built an RNN (using the contrib RNN cells, tested with both basic rnn / gru cells, and also with both dynamic rnn and the static rnn).
AFAIK there is no easy way to get the RNN variables on the CPU, so I wrapped the entire graph in the following hack:
from tensorflow.python.framework.graph_util_impl import must_run_on_cpu

def all_gpu_but_pin_vars_to_cpu(node):
  if must_run_on_cpu(node, FLAGS.pin_vars_to_cpu):
    return "/cpu:0"
  return "/gpu:0"

with tf.device(all_gpu_but_pin_vars_to_cpu):
   // build graph

(as an aside, I have two suggestions:

it would be nice if tf.get_variable got a new device parameter, so we could use arg_scope to accomplish the above in a clean way (see tf.slim which supports this, and also variable from contrib/framework/python/ops/variables.py)
alternatively, or additionally, it would be nice if the function passed to tf.device were allowed to return None, which would result in the default placement)

Then, if we initialize a session with allow_soft_placement, the error is thrown during the init op:
sess.run(tf.global_variables_initializer())

I was able to work around this with another hack that forces a 2-step initialization:
try:
  sess.run(tf.global_variables_initializer())
except:
  sess.run(tf.global_variables_initializer())

This catches the error, variables initialize correctly, and training proceeds ok.


fix(dao) cassandra boolean serialization

Summary
Correctly serialize boolean values in Cassandra.
Issues resolved
Queries filtering on boolean values would result in an error. At the admin API level, this can be reproduced by issuing a request that filters on a boolean field - e.g., GET /apis?preserve_host=false, which will result in a 500 response.

I think an integration test in the DAO or Admin API suite would be appropriate?

Manually merged, thank you!


All error variants for ApplicationStateError should be unique.

I've also improved naming—it should be more meaningful for methods (e.g. JwksNew instead of New if the constructor is Jkws::New).

/ok-to-test sha=5544990


Ugly quickfix for broken tracebacks

Issue: https://github.com/modal-labs/pytest-markdown-docs/issues/XX or N/A

@prbot approve


Added youtube channel

I have added a youtube channel
Description
Addition to youtube channel i.e. Aditya Verma
Fixes #1540
Checklist

[x] My change follows the Contributing Guidelines
[x] I have added only one new link to the list.
[x] I have checked that the link that I added does NOT exist in the project already.
[x] I have sorted the link alphabetically under the related section.

@sdmg15 please review this.
Thankyou

Hello, thanks for your contribution. Youtube channel are hard to check in terms of provided content. No more channels will be added thanks.


missing node in script part of package.json

Hi,
I had to add node in the script part, otherwise after deploying, it App Engine will always say
/bin/sh: 1: exec: app.js: not found
So the final working package.json looked like below.
{
  "name": "argon",
  "version": "0.0.1",
  "description": "DCM Reporting to BigQuery connector",
  "main": "app.js",
  "engines": {
    "node": ">=10"
  },
  "scripts": {
    "start": "node app.js",
    "start-dev": "nodemon app.js",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "Google Inc.",
  "license": "Apache-2.0",
  "dependencies": {
    "@google-cloud/bigquery": "^2.0.6",
    "google-auth-library": "^3.0.1",
    "hapi": "^18.0.0",
    "luxon": "^1.10.0"
  },
  "devDependencies": {
    "eslint": "^5.12.1",
    "eslint-config-google": "^0.11.0",
    "nodemon": "^1.18.9"
  }
}

Thanks for reporting this! Fixed in https://github.com/google/argon/commit/5dab53fbf9646e7ebd6bf8dd0201161c69883f5c.


account for case of no domain passed with username in NTLMAuthenticator

Fixes issue 794

Thank you @shadiakiki1986.


Misleading click feedback in complex md-nav-list

Bug, feature request, or proposal:
UX related bug
What is the expected behavior?
When the user clicks a link in a md-list-item inside a complex md-nav-list, the link should be activated
What is the current behavior?
When the user clicks the link close to the edge, she obtains the feedback (the ripple effect is fired) but the link does not get the click event
What are the steps to reproduce?
Use the template provided at https://material.angular.io/components/component/list#navigation-lists (For more complex navigation lists...) or visit http://plnkr.co/edit/oqGfqlDTYRLF4bOSHQGv?p=preview
Click at the edges of the elements of the list.
What is the use-case or motivation for changing an existing behavior?
An UX issue; users get the feedback when they click but the app does not fire the action
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Tested with Chromium 58.0.3029.81 and Firefox 45.9.0
Is there anything else we should know?
The following gif shows how the mat-list-text element (container of the <a> element ) is smaller than the mat-list-item element. Therefore, it doesn't get the click event

Agreed, this behaviour is confusing

I also got this problem, very confusing, here is my plunker with a md-nav-list containing an icon, link and button:
https://plnkr.co/edit/9HDykcCwiNugXLh5OQVi?p=preview

The problem is that the cursor is changed to the pointing hand and on click the ripple effect triggers, but not the action.
I tried also setting <md-list-item (click)="..."> or <md-list-item [routerLink]="...">, but then then the button event is not triggering anymore.

Workaround fix using event.stopPropagation() until this issue is fixed:
https://plnkr.co/edit/9HDykcCwiNugXLh5OQVi?p=preview
<md-nav-list>
  <md-list-item *ngFor="let folder of folders" (click)="clickListItem(folder)">
    <md-icon md-list-icon>folder</md-icon>
    <a md-line>{{folder.name}}</a>
    <button md-icon-button (click)="clickListItemButton(folder, $event)">
      <md-icon>info</md-icon>
    </button>
  </md-list-item>
</md-nav-list>

  clickListItem(folder: any): void {
    alert('List Item "' + folder.name + '" was clicked');
  }

  clickListItemButton(folder: any, event?: Event): void {
    if (event) {
      event.stopPropagation();
    }

    alert('Button "' + folder.name + '" was clicked');
  }

@BaimosTechnologies, I've fixed your plunker https://plnkr.co/edit/ex2D9u8lx5DNgRY21KE6?p=preview
In adition, when user clicks on md-icon-button it applies ripple effect to whole list-item, however handler for list-item is not fiered.
So as a user I would expect ripple effect to not appear for the list-item.
What do you think?


bootstrap colorselector

Is it possible to setup a drop down with custom options I would like to do something like this
  <option value="106" data-color="#A0522D">sienna</option>

Basically setting up a  bootstrap colorselector or something like this - https://atmospherejs.com/natestrauser/bootstrap-colorpicker

You can do it by making a custom input type.


DotNetSource logo link to GitHub should be https

The DotNetSource logo in this repo and on stickermule has a link to the dotnet GitHub repos, but unfortunately it is http. Would be great to update this to https to keep everyone safe :lock: :lipstick:

/cc @martinwoodward
I agree. This does appear to be a rookie mistake.

Thanks. @kuhlenh, if you get chance to spin up AI feel free to fix this one - otherwise I'll take a look in the morning.

Actually, I'm on this now but I'll need @kuhlenh or someone else to update the EPS version if that's ok


Isolate hop project from application

Hello.
Sorry for the English, I used google translator.
I would like to suggest a change to the xml.py file.
According to the documentation, it would be necessary to leave the hop artifacts in the home_home/project folder for the plugin to work correctly.
Analyzing the code I thought and tested the following solution.
the commented line is the original of the project and the line below is the change suggestion
#self.project_folder = f'{hop_home}/{project["projectHome"]}'
if hop_home == self.project_home:
self.project_folder = self.project_home
else:
self.project_folder = f'{hop_home}/{self.project_home}'
This way I can leave the hop project isolated from the hop application, gaining mobility.
for the documentation you could leave it like this:
If your project is in a custom location, in the apache airflow connection configuration, home_home must be the same as the folder where your project is, so the plugin works correctly.
Attention: it is necessary that the hop artifacts are in the Airflow container, in the same path.

Error:

Hello...
because the flow runs normally, but the airflow returns an error.
*** Reading local file: /opt/airflow/logs/dag_id=dag-w-teste/run_id=manual__2022-11-28T10:53:11.964359+00:00/task_id=tsk-w-teste/attempt=1.log
[2022-11-28, 10:53:12 UTC] {taskinstance.py:1165} INFO - Dependencies all met for <TaskInstance: dag-w-teste.tsk-w-teste manual__2022-11-28T10:53:11.964359+00:00 [queued]>
[2022-11-28, 10:53:12 UTC] {taskinstance.py:1165} INFO - Dependencies all met for <TaskInstance: dag-w-teste.tsk-w-teste manual__2022-11-28T10:53:11.964359+00:00 [queued]>
[2022-11-28, 10:53:12 UTC] {taskinstance.py:1362} INFO -
[2022-11-28, 10:53:12 UTC] {taskinstance.py:1363} INFO - Starting attempt 1 of 1
[2022-11-28, 10:53:12 UTC] {taskinstance.py:1364} INFO -
[2022-11-28, 10:53:12 UTC] {taskinstance.py:1383} INFO - Executing <Task(HopWorkflowOperator): tsk-w-teste> on 2022-11-28 10:53:11.964359+00:00
[2022-11-28, 10:53:12 UTC] {standard_task_runner.py:54} INFO - Started process 6627 to run task
[2022-11-28, 10:53:12 UTC] {standard_task_runner.py:82} INFO - Running: ['', 'tasks', 'run', 'dag-w-teste', 'tsk-w-teste', 'manual__2022-11-28T10:53:11.964359+00:00', '--job-id', '3', '--raw', '--subdir', 'DAGS_FOLDER/dag-w-teste.py', '--cfg-path', '/tmp/tmp7xghbt2k']
[2022-11-28, 10:53:12 UTC] {standard_task_runner.py:83} INFO - Job 3: Subtask tsk-w-teste
[2022-11-28, 10:53:12 UTC] {dagbag.py:525} INFO - Filling up the DagBag from /opt/_dags/dag-w-teste.py
[2022-11-28, 10:53:13 UTC] {task_command.py:384} INFO - Running <TaskInstance: dag-w-teste.tsk-w-teste manual__2022-11-28T10:53:11.964359+00:00 [running]> on host 58ad4d15dc5e
[2022-11-28, 10:53:13 UTC] {taskinstance.py:1590} INFO - Exporting the following env vars:
<EMAIL_ADDRESS>AIRFLOW_CTX_DAG_OWNER=Agroterenas
AIRFLOW_CTX_DAG_ID=dag-w-teste
AIRFLOW_CTX_TASK_ID=tsk-w-teste
AIRFLOW_CTX_EXECUTION_DATE=2022-11-28T10:53:11.964359+00:00
AIRFLOW_CTX_TRY_NUMBER=1
AIRFLOW_CTX_DAG_RUN_ID=manual__2022-11-28T10:53:11.964359+00:00
[2022-11-28, 10:53:13 UTC] {base.py:71} INFO - Using connection ID 'hop_default' for task execution.
[2022-11-28, 10:53:13 UTC] {operators.py:83} INFO - TESTES/W_TESTE.hwf: Workflow 'W_TESTE' was added to the list with id eeb56df5-06a9-45d9-bd09-d4a1afbc4be3
[2022-11-28, 10:53:13 UTC] {operators.py:87} INFO - TESTES/W_TESTE.hwf: Started OK
[2022-11-28, 10:53:13 UTC] {taskinstance.py:1851} ERROR - Task failed with exception
Traceback (most recent call last):
File "/opt/airflow_dags/airflow_hop/operators.py", line 92, in execute
work_status_rs = conn.workflow_status(self.workflow, work_id)
File "/opt/airflow_dags/airflow_hop/hooks.py", line 190, in workflow_status
raise AirflowException('{}: {}'.format('HTTP', error))
airflow.exceptions.AirflowException: HTTP: Error 500 java.lang.NullPointerException
[2022-11-28, 10:53:13 UTC] {taskinstance.py:1401} INFO - Marking task as FAILED. dag_id=dag-w-teste, task_id=tsk-w-teste, execution_date=20221128T105311, start_date=20221128T105312, end_date=20221128T105313
[2022-11-28, 10:53:13 UTC] {standard_task_runner.py:102} ERROR - Failed to execute job 3 for task tsk-w-teste (HTTP: Error 500 java.lang.NullPointerException; 6627)
[2022-11-28, 10:53:13 UTC] {local_task_job.py:164} INFO - Task exited with return code 1
[2022-11-28, 10:53:13 UTC] {local_task_job.py:273} INFO - 0 downstream tasks scheduled from follow-on schedule check

Add PR #27


Exceeds OS Max Path Limit (OSOE-557)

Hey there, I was trying to get the Lombiq Training Demo for Orchard Core set up. But in the rebuilding process I got this error.
The project 'Lombiq.NodeJs.Extensions.SolutionMarkdownAnalysis' ran into a problem during the last operation: Cannot expand metadata in expression
"$([MSBuild]::ValueOrDefault('%(FullPath)', '').StartsWith($([MSBuild]::EnsureTrailingSlash($(MSBuildProjectDirectory)))))".
The item metadata "%(FullPath)" cannot be applied to the path "node_modules\nodejs-extensions\node_modules\%40textlint-rule\textlint-rule-no-invalid-control-character\lib\CONTROL_CHARACTERS.js".
 Path<EMAIL_ADDRESS>exceeds the OS max path limit.
The fully qualified file name must be less than 260 characters.
 C:\Program Files\dotnet\sdk\7.0.102\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets
You may need to reload the solution after fixing the problem.

From what i understand, I could get around this by moving project directly to my C:\ drive, but that didn't seem right to me especially considering that the project isn't nested that deep in my filesystem currently. So, do I need to move the project up a couple folders or is there a setting I am missing?
Thanks
Jira issue

That fixed it, thanks for the quick response.


Complete Day 4 in NodeJS

[x] Part 1
[x] Part 2

Done! However Day 4 Part 2 code doesn't work correctly as of it's current state, I had it working at one point but I messed up with adding it to the version control


Refactor init scripts

Fix: #126
Use one python file instead of bash file and bunch of python scripts.
It makes bootstrap considerably faster and makes it easier to support
the code.

repushed to satisfy linter. not changes to the code itself only style.

@smacker I've tried and it works for me! Thanks!


[CI] GHCR and docker image updates

Publish docker container image to GHCR

With published version (tag) and latest too on release

Update README

Signed-off-by: Azeem Sajid<EMAIL_ADDRESS>

@liquidaty: A test container image has been published with the commit SHA as its tag.
Please see https://github.com/liquidaty?tab=packages. You might want to remove that.
CI has been configured to publish it on release only to save the storage. Thanks!


Add phosphor-icons-tailwindcss to README - Community Projects

This PR adds to README a link to phosphor-icons-tailwindcss, a TailwindCSS plugin for Phosphor as atomic CSS. I extracted this from an ongoing project thinking this might be helpful for others.
Happy to support transferring this to live under phosphor-icons org if you think that's something helpful for the eco.
Thanks for the good work :100:, Phosphor has been a joy to use.

@rektdeckard thanks. An unplugin is nice indeed, but I think we'd need to re-implement quite a few things, namely:

parsing source code to look up for matching class names (quite a few edge cases I believe, for example in Svelte class:something={condition} will apply .something class if condition is true)
injecting atomic CSS into the dist bundle

Having option is nice, but I believe if people are interested in atomic CSS nowadays it's highly probable they'd reach for UnoCSS & TailwindCSS, which do both (1) & (2) very well.