ADUGroup not visible to deployment group setup on ThinkedEdge SE30 with 0.9.2-early-access

Summary
Trying the latest updates of device-update agent and deliveryoptimization agents.
My physical device seems poperly configured, but the device class does not appear in the device update deployment group list.
Configuration
Physical machine: ThinkEdge SE30 (same as the one used by joproulx on https://github.com/Azure/iot-hub-device-update/issues/185)
OS: 20.04.5 LTS (Focal Fossa)
IotEdge: 1.4.1
Device update agent: deviceupdate-agent_0.9.2_20.04_amd64.deb
Delivery optimization agent : deliveryoptimization-agent_0.7.0_amd64.deb and libdeliveryoptimization_0.7.0_amd64.deb from https://github.com/microsoft/do-client/releases/download/v0.9.0/ubuntu2004_x64-packages.tar
du-config.json:
{   "schemaVersion": "1.1",   "aduShellTrustedUsers": [     "adu",     "do"   ],   "iotHubProtocol": "mqtt",   "manufacturer": "Lenovo",   "model": "ThinkEdge SE30",   "agents": [     {       "name": "Device update agent",       "runas": "adu",       "connectionSource": {         "connectionType": "AIS",         "connectionData": ""       },       "manufacturer": "Lenovo",       "model": "ThinkEdge SE30"     }   ] }
Azure portal of Device Update has the public preview enabled.
Device history
Provisioned through the DPS with TPM attestation before migrating the portal.
Original device update version: deviceupdate-agent_0.8.2_public_preview_amd64.deb
Basic troubleshooting
The devices and the seem to run fine:

du-agent.20221017-040207.log
iotedge-check.txt
systemctl-status.txt

Message routing (untouched) seems fine:

Here is the current state of the IoTHubDeviceUpdate module twin: ModuleIdentityTwin.json.txt
The reported properties seem to tell that the communication between the agent and Device update is fine. (good aduVer and doVer uploaded by the agent, recent communication date).
Here is the section that defines the tags for the deployment groups:
    "tags": {         "ADUGroup": "se30_canary"     },
Following the advice of the Device Update troubleshooting guide, I set the ADUGroup tag to another tag, or tried to set it null and recreate it a while after; nothing changed.
Symptom
I'm trying to create a deployment group for this device but the tag "se30_canary" is not available:

The two tags on the screenshot are coming from other tests. What is expected here is to have a tag "se30_canary"
Moreover, the device is not even visible in the default group (by device class):

More context
I am doing the same think for AzureVms on deviceupdate-agent_0.8.2_public_preview_amd64.deb with no delivery optimisation agent installed. Groups can be created just fine, and updates can be deployed:

potentially related issues
https://github.com/Azure/iot-hub-device-update/issues/156
https://github.com/Azure/iot-hub-device-update/issues/185
https://github.com/Azure/iot-hub-device-update/issues/216

Hi @jzaegel, you are using the early access agent for the upcoming release and the current portal which is why your groups may not be appearing correctly. Please can you check if your group are appearing here -  early access Azure Portal?

Hi esha0611
You are right. I can see my group just fine on the new portal.

I mistakenly thought that the upper banner was a sign that I was on the early access portal:

Thanks a lot


YATCO changes the background color of the chat in the main window is preserve background is enabled

Only shows up when you don't mute the chat in the main window and have preserve background enabled. I think I'm editing the background before doing the copy, and so it's effecting the main window as well.

new issue in EMCO: https://github.com/demonnic/EMCO/issues/1


exporting IDB into BinNavi built from first checkin

Just noticed your new check in, will reattempt with a new build.
I was getting error exporting: executing query failed: ERROR: could not create unique index "ex_3_base_types_pkey" DETAIL: Key(id)=(822) is duplicated.
Is this known/resolved thanks.

I can confirm this issue.

I can unfortunately not reproduce the issue. I tested the checked in plugins. Can you provide some more details such that I am able to reproduce the error. Thanks.

@0xFFFFFFFE I can already provide you with the following details:

OS: Windows 7 SP1 64bit
PG: Postgres 9.4.4 64bit
IDA: IDA Pro 6.8 32bit
Target: Savant Web Server 3.1

I can provide you the actual IDB file later today if you would need it.

I have to correct myself (should not do so much late night hacking). The currently checked in exporter for windows is broken by a bug I introduced. This is already fixed in an upstream version, which I will check in soon. Ill close the bug as soon as this is done.

Still not working. Pulled latest. Built under Linux. Run under Windows 8.1. Tried to import 32 bit kernel32.dll. Same Issue again.

I can confirm the issue is not fixed with the latest commit.

Alright, it should be fixed now. Didn't properly sync to the latest internal version. Tested both Windows and Linux.
Ah well, we (zynamics) are still figuring out how to properly do OSS :)

Sorry. Got same issue:
Error exporting: executing query failed: ERROR: could not create unique index "ex1_base_types_pkey" DETAIL: Key (id)=(2112) is duplicated.
I did a fresh git clone.
Do you need a logfile? Or idb?
Thanks,
Matthias

IDB would be optimal. And optionally the SHA1 hash of your zynamics_binexport_8 plugin in your IDA directory. Which date does the plugin report in IDA's output window?
Do you also have BinDiff installed? If so, please overwrite its zynamics_binexport_8 plugin with the one from this repository.

Got it finally working. Removed BinDiff. Deleted zynamics_binexport_8 files. Installed it again. Works!
Thanks for your support!

Cool thanks for checking that it now works.
Matthias Kaiser<EMAIL_ADDRESS>schrieb am Di., 25. Aug. 2015 um
22:51 Uhr:

Got it finally working. Removed BinDiff. Deleted zynamics_binexport_8
files. Installed it again. Works!
Thanks for your support!
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/3#issuecomment-134737067.

We'll also update BinDiff in a few days to contain the right plugin. Having both BinNavi and BinDiff is relatively common, after all.


Failure to write a file to user:// should be a serious error with a visible error message

Godot version:
3.2.2 stable
OS/device including version:
Windows 10
Issue description:
Tried to write a file with ":" in the filename by accident. Fails silently, no error message on console with -d, only visible in the debugger. Should be a more serious error.
Steps to reproduce:
Tried to write a file with ":" in the filename to user:// on Windows 10.

Note: : is only disallowed in filenames on Windows, not on other platforms.


Add OpenTelemetry attributes to the metrics backend

Before submitting pull request:

[x] Check if the project compiles by running sbt compile
[x] Verify docs compilation by running sbt compileDocs
[x] Check if tests pass by running sbt test
[x] Format code by running sbt scalafmt

Closes #2292
/claim #2292

@adamw Have a review on it at your free time

Thanks - the PR looks good! I've left a couple of minor comments before we merge

@adamw Done! Added review comments

@adamw Can it be merged now?

@varshith257 Yes, all done, thanks :)

@adamw Any communication channel to connect with you? I have some doubts regarding implementation of other issue works

@varshith257 I think it would be best to keep the discussions on the appropriate GH issue, otherwise there's softwaremill.community Discourse and Scala Space's Discord


Rubocop-daemon stalls on macOS when Homebrew netcat is installed

The rubocop-daemon script is currently setting $NETCAT_CMD to nc on macOS. When netcat from Homebrew is installed, and the $PATH is set up such that /usr/local/bin comes before /usr/bin, rubocop-daemon hangs while trying to run /usr/local/bin/nc.
If we hard-coded $NETCAT_CMD to /usr/bin/nc on macOS, this would probably be fixed.

thanks for the fix, I've submitted a PR!


Add docstrings for nox sessions

Description
Adds descriptive docstrings for nox sessions, which can be listed with the nox --list or nox -l commands, closes #3048
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[x] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[x] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all
[x] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

The docstrings are kept as single-line only because the first line will be printed when listing sessions. There is an open feature request to print the full docstring of a session (https://github.com/wntrblm/nox/issues/694)

I also disabled colour output in the CI by default since we would not need it in non-interactive shells usually, and I refactored the session arguments (a bit) with nox.options


cometbft: init at 0.38.6

Description of changes
Opening PR on behalf of @jakzale who first packaged.
Since this is essentially the successor to tendermint, should that derivation be deprecated and/or have a warning?

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

0.38.7 came out right after this was put up. Updating PR


[gitlab_agent_deploy] Move image to datadog-agent-buildimages

What does this PR do?


⚠ Bofrost.com has degraded performance

In afffddd, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 845 ms

Resolved: Bofrost.com performance has improved in 5bf5e91.


Automated Collection Testing

Once the user defines(and saves) the collection, user can just click a button to test all the requests within that collection at once.
Further discussion needed whether protoman will just check the status code or the actual return(users can decide if they want to)

sidenote: postman collection exists so that user can define the sequence for the request calls


^@ inserted where there should presumably be a newline

Description
^@ is inserted for completions where there should seemingly be a newline and indentation.
This occurs when the completion is the only possible candidate, as shown in the example below, and also when there are multiple completions to select from.
Neovim version
NVIM v0.7.2
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
dcb7ebb36f0d2aafcc640f520bb1fc8a9cc1f7c8
Operating system and version
Kubuntu 22.04 LTS
Affected language servers
pyright
Steps to reproduce

nvim -nu minimal_init.lua
(pyright is already configured)
Load a new empty Python file (e.g., :e file.py)
Enter the following:

class C:
    def __st

While still in insert mode, press <c-x><c-o> for auto completion

Actual behavior
The following shows the full file with the completed text. There is a ^@ string inserted where there should presumably be a newline.
class C:
    def __str__(self) -> str:^@    pass

Expected behavior
I expected a newline and proper indentation instead of a<EMAIL_ADDRESS>class C:
    def __str__(self) -> str:
        pass

Minimal config
minimal_init.lua without modifications
LSP log
N/A

"Isn't this more of a core issue? nvim-lspconfig is just configuration."

I just opened https://github.com/neovim/neovim/issues/20250.

It's a multiline snippet completion, which isn't supported in core yet -- you need a completion and snippet plugin for those.


Fix subfields check in Update operation

WHY
BEFORE - What was wrong? What was happening before this PR?
Fix for https://github.com/Laravel-Backpack/CRUD/issues/5002
Checking for the existence of subfields in the Update operation is not strict enough.
AFTER - What is happening after this PR?
This PR uses isset() to check the array key existence and hence solves the bug.
HOW
Is it a breaking change?
No
How can we test the before & after?
By adding a field within a CRUD with the following configuration:
$this->crud->addField([
    'label' => 'Category',
    'type' => 'select',
    'name' => 'category_id',
    'entity' => 'category',
    'attribute' => 'category_name',
    'model' => 'App\Models\Category'
]);

A new inspection was created.

The inspection completed: 1 new issues


Images

@leanne-fan, can you share a folder of images with me? Stuff from past events, etc.
cc @szweibel

Sorry for the delay, Patrick!
Is this what you were looking for? https://drive.google.com/drive/folders/11GpsLCMP5WYnOR89Pr8sdRLDXYQEa5Zm?usp=sharing

Hi @leanne-fan , I was thinking something along the lines of people in a workshop context, i.e. people at one of the Institutes or similar. I may have access to some old photos from my GCDI days, but something newer if photos have more recently been taken would be a help. @szweibel , have anything from your participation, or seen anything alone these lines?

Google Drive of pre-covid DHRI Workshops: https://drive.google.com/drive/folders/1D4-yzfQChAoI0hA-kM-hLrSO_SDGq74R?usp=share_link

Thank you! :)

Perfect, thanks! :smile:


MQTT Broken

MQTT appears to be broken on the latest firmware release (v4.8.6).
Just received the hardware so this is from the pov of a "clean" install.
Upon entering the MQTT settings (i.e. hostname, username, password & interval) and hitting save, the fields get cleared again and no topics are published to the broker.
I did also notice that the POST requests made upon hitting save end up timing out.
Installing the previous release (v4.8.5) works fine.
Unrelated to this issue:
I also noticed the device being a lot less responsive on v4.8.6.
Loading the actual pages are fine but it takes a lot more time to for the data to be retrieved on the dashboard compared to v4.8.5.

Thanks for mentioning this issue.
Due to a bug in the 4.8.6 version the dongle reboots when one of the mqtt settings where changed. That is why the response is slow.
This is solved in the 4.8.6b version. Please try this one with /remote-update?version=4.8.6b


Displaying a real error unrelated to the plugin

What/Why/How?
If program has any error and redocly.yaml which has plugin - error replaced by text. Real info about error is hiding.
For example add mistake in syntax package.json and rund redocly with any plugin.
After this fix, error should be showed throth console.warn().
Check yourself

[x] Code changed? - Tested with redoc/reference-docs/workflows (internal)
[x] All new/updated code is covered with tests
[x] New package installed? - Tested in different environments (browser/node)

Security

[x] Security impact of change has been considered
[x] Code follows company security practices and guidelines

Thanks for the PR. I'll take a look at it a bit later.

I'm closing this in in favour of https://github.com/Redocly/redocly-cli/pull/1674 as it better handles the error message.

Thank you for #1674


How to handle live stream not started error?

I am integrating the player into html-js static site, below is my code:
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>Static Template</title>
    <script src="https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>    <link
      rel="stylesheet"
      href="https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>    />
  </head>
  <body>
    <video
      id="my-player"
      class="video-js vjs-16-9"
      controls
      preload="none"
      width="100%"
    >
      <source
        src="8fCGUaEp3DcVM3BlizlfOBQeev02TgzFE016RcdedReBo"
        type="video/mux"
      />
    </video>

    <script>
      videojs("my-player", {
        plugins: {
          httpSourceSelector: {},
          mux: {
            debug: true,
            automaticErrorTracking: false,
            data: {
              video_title: "Example Title"
            }
          }
        }
      });
    </script>
  </body>
</html>

The streaming is not started yet, It shows the "A network error caused the media download to fail part-way." error in the player, is there any way to handle this error and show a preview image or wait for the host message or something?

Codesandbox link:
https://codesandbox.io/s/mux-videojs-player-error-tsdm72

Hi @turivishal thanks for opening this issue.
For live streams, you'll have to wait until the stream is "active". Before "active" the playback ID will not be able to used in a player.
You can monitor the live stream status via webhooks or with GET /video/v1/live-streams/{LIVE_STREAM_ID}
Let me know if this helps

Thank you for your reply, It makes sense.


localSourcePath option doesn't seem to work

I am currently trying to use the new "localSourcePath" option to try to speed up our parallel builds (multiple parallel codebuild builds which all use the same source), among other possible improvements once I get this working.  However, I consistently get a message like this:
[AWS CodeBuild Plugin] Local file to be uploaded to S3: /ebsvol/jenkins/workspace/my-workspace-name/src.zip
[AWS CodeBuild Plugin] /ebsvol/jenkins/workspace/my-workspace-name/src.zip (No such file or directory)
I create the zip file at the beginning with:
sh 'mkdir -p git'
dir('git') {
checkout scm
}
sh 'rm -f src.zip'
zip dir: 'git', glob: '', zipFile: 'src.zip'
And then subsequently pass it into the awsCodeBuild plugin:
awsCodeBuild(
projectName: codeBuildProjectName,
buildSpecFile: buildSpecOverride,
region: region,
credentialsId: credentialId,
credentialsType: 'jenkins',
sourceControlType: 'jenkins',
localSourcePath: 'src.zip',
sseAlgorithm: 'AES256')
Am I doing something wrong here?  Or am I hitting some weird corner-case?

Can you run sh 'pwd; ls' after creating the zip file to ensure the zip is in my-workspace-name/?

Yes, I tried that too.  It shows both the path it says is missing, and that the zip file is there (and the git repo subdirectory).

Can you send me information about your Jenkins setup so I can try to reproduce this?

Is it possible that the CodeBuild steps and zip steps are being run on different nodes?

Okay I think I was able to reproduce the issue. With an older Jenkins installation, the zip command failed and I had to install the pipeline-utility-steps plugin to get it to work. On a newer installation, the zip command silently failed, but once again worked after installing the pipeline-utility-steps plugin. Can you try installing that plugin and see if that fixes your build?

Sorry for the delay--I've been working on about three different projects in the last day or so.  I did check, and we do have pipeline-utility-steps version 2.2.0, which looks to be the latest.  And we are running Jenkins 2.150.2 via the official Docker image.
Here is a simplified version of what I am doing in our Jenkinsfile:

def makeCodeBuildProject(
    Map params = [:],
    String codeBuildProjectName) {
    def buildSpecOverride = params["buildSpecOverride"] ?: ""
    def region = params["region"] ?: "us-east-2"
    def srcPath = params["sourcePath"] ?: ""

    def result = awsCodeBuild(
        projectName: codeBuildProjectName,
        buildSpecFile: buildSpecOverride,
        region: region,
        credentialsId: 'my-credentials',
        credentialsType: 'jenkins',
        sourceControlType: 'jenkins',
        localSourcePath: srcPath,
        sseAlgorithm: 'AES256')

    def artifactPath = result.getArtifactsLocation().split(':::')[1]
    return artifactPath
}

timestamps {
    def artifactPathSpecs = []
    node('master || ecs') {
        stage('Preparation') { // for display purposes
            sh 'mkdir -p git'
            dir('git') {
                // Get hub-core source
                checkout scm // get source from current branch/PR
            }

            sh 'rm -f src.zip'
            zip dir: 'git', glob: '', zipFile: 'src.zip'
        }
        stage('Build') {
            parallel "GCC": {
                sh 'pwd && ls'
                def artifactPath = makeCodeBuildProject(
                    region: "us-east-1",
                    sourcePath: "./src.zip",
                    'my-project-x64-use1-codebuild') //codeBuildProjectName
                artifactPathSpecs.push([s3path: artifactPath, localFolder: 'ubuntu-x64', region: 'us-east-1', friendlyName: 'GCC'])
            }, "Clang": {
                // Uses the same CodeBuild project (and ECR image) as ubuntu-x64 above
                def artifactPath = makeCodeBuildProject(
                    region: "us-east-1",
                    sourcePath: "./src.zip",
                    'my-project-x64-use1-codebuild', //codeBuildProjectName
                    buildSpecOverride: 'tools/docker_builds/ubuntu-x64/buildSpec-clang.yml')
                artifactPathSpecs.push([s3path: artifactPath, localFolder: 'ubuntu-x64-clang', region: 'us-east-1', friendlyName: 'Clang'])
            } //… other targets omitted ...

            failFast: false
        }
    }
}

In the "GCC" path, I was doing the pwd && ls -la as a sanity check, and it is outputting:
+ pwd
/ebsvol/jenkins/workspace/my-workspace-name
+ ls
git
git@tmp
src.zip

And this is the error output from the codebuild step:
[AWS CodeBuild Plugin] Using credentials provided by the DefaultAWSCredentialsProviderChain for authorization (provided from Jenkins credentials ****)
[AWS CodeBuild Plugin] Local file to be uploaded to S3: /ebsvol/jenkins/workspace/my-workspace-name/src.zip
[AWS CodeBuild Plugin] /ebsvol/jenkins/workspace/my-workspace-name/src.zip (No such file or directory)

It seems like the two things are happening on the same node, and the zip file appears to be there.

I wasn't able to reproduce the issue running a build on Jenkins 2.150.2 in a Docker image, although I was only using one master node. Can you tell me a bit more about your node setup?

Ahh, okay.  This did occur to me last night too.  Yes, we have a more complicated setup.  We have a master instance in ECS which does almost no work, and these codebuild jobs are setup to occur on separate EC2 slave instances.  (Ignore the node name in my Jenkinsfile script--the ones designated to run the codebuild jobs are labeled "master", for... reasons... Our master instance is labeled "Jenkins".)
So I wonder if it is trying to read the zip file locally, instead of off of the agent's workspace?  That would explain why it shows up in the ls, but triggers a file not found.

I think I was able to reproduce the issue after setting up a node. We did some work a while back to properly handle remote workspaces, but it doesn't look like the new logic for local source is implemented improperly. I'll debug a bit and keep you updated.

Should be fixed by 29f2fa137e5b8c415e07c4d638dd56b7c9ccca54. I implemented something similar to your change from a while back. This will be released today in version 0.36, so let us know once you've verified it works for your use case.


GroupBy field should be guided by enum choices and be part of flow configuration instead of Header configuration

To track flows using source MAC addr and source IP addr, here's how currently it's done:
packet = [
    FlowHeader(choice='ethernet', ethernet=FlowEthernet(), group_by=[FlowGroupBy(field='src', label='Source MAC Addr')]),
    FlowHeader(choice='ipv4', ipv4=FlowIpv4(), group_by=[FlowGroupBy(field='src', label='Source IP Addr')),
]

Problems are:

There's no implicit validation on what could be accepted as field names to be tracked with
To distinguish between two field names, we end up providing separate label
It's a bit tedious to specify group_by in each header - subjective
Usage of track_by vs group_by - subjective

We could essentially configure it as part of Flow instead of Header, so that all the fields can be provided in one place. (It also goes along well with how we return group_by stats - i.e. they're directly contained within flow stats itself)
In fact, we could define a list of ENUMs which will be descriptive enough and not require label input.
FlowFlow(
    packet=[
        FlowHeader(choice='ethernet', ethernet=FlowEthernet()),
        FlowHeader(choice='ipv4', ipv4=FlowIpv4()),
    ],
    # fields is a list of enums
    tracking=Tracking(fields=['src_mac_addr', 'src_ip_addr'])
)

Lastly,  TrackBy or GroupBy should be extensible to include stats with custom offsets (e.g. group by values belonging to offset 16-18) and basic latency configuration (this is not a hard requirement in first phase as I understand).
e.g.
Tracking(
    fields=['src_mac_addr', 'src_ip_addr', 'custom'],
    # configure two latency bins
    latency=Latency(
        method='cut_through',
        bins=[
            LatencyBin(min=10, max=100),
            LatencyBin(min=1000, max=10000)
        ]
    ),
   custom=SomeContainer(...)
)

Every packet header field takes a pattern - that pattern offers an option to specify a ingress_tracking_name. The existence of the unique name indicates the field is to be tracked and the name is also what is seen in the flow_results.
Latency bins should be opened as a separate issue and marked as an enhancement.
The Flow.Pattern includes the following:
ingress_result_name:
          description: >-
            A unique name is used to indicate to the system that the field may
            extend the result row key and create an aggregate result row for
            every unique ingress value.
            To have ingress columns appear in flow result rows the flow result
            request allows for the ingress_result_name value to be specified
            as part of the request.
          type: string


TypeScript and Angular 5 support

Do you plan to introduce TypeScript and Angular 5 support anytime in near future?

We'll discuss about your question.

That would be great. This calendar rocks.

Thanks @MRisto for your attention.
There are several request for supporting frameworks like vue, typescript.
I agree with you.
We don't have any plan, but we want it also.
Some typescript expert's help would be great for this calendar.

I'm on it.

Oh, I found something wrong in the minified tui-calendar.min.css file.
Please use not minified css file tui-calendar.css instead until i fix it.
The next version might be released before 17th May.
Thank you!

@dongsik-yoo  Cool, I have updated it as directed. Now I don't see day numbers. The same link please check.

@amanvishnani Good, the only what you have to do is set height of container.
And in that link, there is no real #cal element before new Calendar().

@dongsik-yoo Thanks for the help.

@amanvishnani You're welcome. Are you working on making typescript wrapper?

@dongsik-yoo My primary goal is to make it work on Angular with Typescript by creating a component wrapper around it, which could be reused by installing as npm dependency and, importing module and components from it.

@amanvishnani Great! It will be awesome! I'm look forward to your good package.

hello all, working on something similar, available at https://github.com/brnrds/ngx-tui-dev/tree/master/projects/ngx-tui-calendar/src/lib or via $ npm install ngx-tui-calendar
currently broken, getting
ERROR Error: StaticInjectorError(AppModule)[NgxTuiCalendarComponent -> ElementRef]:
StaticInjectorError(Platform: core)[NgxTuiCalendarComponent -> ElementRef]:
NullInjectorError: No provider for ElementRef!
in Angular 5/6 @amanvishnani maybe we can merge these efforts?

@brnrds Sure we can work collaboratively on this project, I was hoping if we could host repository somewhere on this organization itself. This will keep all related repositories at one place.
@dongsik-yoo What do you think?

@brnrds @amanvishnani Amazing.
We have an internal process of managing github repository. I hope we offer a proper repository, but I can't promise you. We'll discuss this tomorrow. I'll let you know the result or maybe guide.

@amanvishnani @dongsik-yoo so far my progress has been to emulate the approach in https://github.com/mattlewis92/angular-gauge/blob/master/src/gauge.component.ts to make a wrapper for tui.calendar.
@amanvishnani feel free to submit pull requests, or move the code in the repo above to a new one.

@brnrds @amanvishnani Good news!
We can offer a new repository for your working!
So what do you want the repository name to be?

https://github.com/xieziyu/ngx-echarts/tree/master/projects/ngx-echarts/src/lib
Code inside this lib will help you a lot. It is Angular wrapper of Echarts, which provides directive and service to use echart. It shows how to handle window resize, option changes, and other events.
It would be also useful to wrap tui.chart with this approach.

And using directive would be better than wrapper component, because getting viewport from DOM does not work well inside component.
https://github.com/nhnent/tui.calendar/blob/b908747419cb01caf23b5b8e838e00284650da2a/src/js/view/view.js#L182-L193
So these lines should not work as expected... you might have to manually pass height and width. Or you need a bunch of glue code for setting component's host style.
@dongsik-yoo ngx-<lib name> is generally used after Angular 4.x, so ngx-tui.calendar would be ok. But I prefer tui.calendar.ng or tui.calendar.ngx.

I am in favor of either one of tui.calendar.ngx or ngx-tui-calendar as a repository name and  @nhnet/<final-repo-name> as the final package name.
@dongsik-yoo @icepeng @brnrds what do you guys think?

It might be @tui/calendar with scoped package. NHN Entertainment has other projects like Haste Framework, and tui means TOAST UI.
And we can create @tui/angular then implement tui components as much as possible. I think we don't need to create each repo like ngx-tui-calendar, ngx-tui-chart, ngx-tui-editor, etc... Just include Angular parts together in one module, and install scripts separately.
If you write angular project with tui.calendar and tui.chart:
package.json
"dependencies": {
  ~~~
  "@tui/angular": "1.0.0",
  "@tui/calendar": "1.0.0",
  "@tui/chart": "1.0.0"
}

angular.json
~~~
"styles": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>],
"scripts": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>]

app.module.ts
  imports: [
    ~~~
    TuiModule.forRoot()
  ]

app.component.html
<tui-calendar [options]="calendarOptions"></tui-calendar>
<tui-chart [options]="chartOptions"></tui-chart>
<!-- <tui-editor></tui-editor> (Error!) -->

Thanks for the pull request, @amanvishnani ! Also for the reference @icepeng :-) Busy with a few tasks but I'll push an update as soon as I figure out how to actually show the calendar.
As for the repository name, while all suggestions seem viable, I particularly like<EMAIL_ADDRESS>because it would make things organized as more Toast UI projects have their Angular wrappers. My suggestion is to for now to keep working on the repository @amanvishnani is already contributing to, and once it's actually working create to "official" repository under your organization, and I'll delete this temporary one.
Also, input on best practices is most welcome, since I'm a relative newcomer to Angular (and client-side in general) and would like to contribute to a good implementation that can be used for other TUI Angular wrappers.

Completely agree with @icepeng suggestions.
@brnrds Sure let's work on your repo and once we a complete working prototype lets move it to the repo in this Org.

@icepeng As you point, tui-calendar's container must have height.
@amanvishnani @brnrds We have a discussion to determine the repository name and package name convention. I'll let you know when I have a decision.

Hello all, things just got rather busy around here and I'll only have time/availability to work on this from the 2018/05/21 onward. If @amanvishnani or other contributors send pull requests I'll gladly merge them,  or I can transfer ownership, whichever there is consensus about.

Good news, had a chance to pick this up yesterday, and António, a colleague, also helped out. This is now working: https://github.com/brnrds/ngx-tui-dev , pending adding type/interface definitions for the library's classes and installation instructions. https://github.com/brnrds/ngx-tui-dev

I introduce your works at the top of this repo's README.
Thanks for your cooperation @brnrds and António.

@amanvishnani any news on your end? About ready to hand this over, any feature requests? Right now it exposes the library's events and methods to Angular.

@brnrds Sorry I was busy for past few days so, didn't checked. If you feel like bare minimal version is ready then sure go ahead.

Updated readme with installation and usage instructions: https://github.com/brnrds/ngx-tui-dev
Could someone please try and see if these instructions are clear enough to get it to work?

@brnrds @amanvishnani  @icepeng  thanks for putting this wrapper. I tried the instructions ... Calendar UI came well ...  but the popups are not working... So I added tui-calendar.js into scripts section ( not in instructions) ... now I get below error ( still pop ups are not working) ...
Uncaught TypeError: Cannot read property 'browser' of undefined
at Object. (tui-calendar.js:3632)
at webpack_require (tui-calendar.js:36)
at Object. (tui-calendar.js:2978)
at webpack_require (tui-calendar.js:36)
at Object. (tui-calendar.js:2681)
at webpack_require (tui-calendar.js:36)
at Object. (tui-calendar.js:111)
at webpack_require (tui-calendar.js:36)
at Object. (tui-calendar.js:73)
at webpack_require (tui-calendar.js:36)

@brnrds  thanks for the reply. I will check the mentioned ngx-tui-calendar.component.ts  for details

@srinek TOAST UI Calendar has a mandatory dependency tui-code-snippet. Please refer to the link https://github.com/nhnent/tui.calendar#-dependency.

Hey all lets at least move the repo over here please, ngx-tui-calendar is a great name and goes well with other ngx packages, I too will contribute as I want to use this in a commercial project.
@dongsik-yoo can you at least make the repo here please, @brnrds and everyone else lets start PR'ing!

@dongsik-yoo Would it be very difficult to remake this in typescript?
If we don't have a typescript version, it means having to keep all the DTO's up to date manually, which will be maintenance hell in the future, and will make development slow.
If we do have a typescript version, it means writing a very small wrapper around it, which will take care of most of the code.
This is a very promising project!

@Worthy7
About typescript version
I understand advantage and disadvantage what you said. TOAST UI family aren't written in typescript, only in javascript. So I guess it's too difficult to rewrite this calendar. But We will discuss about making typescript interface for TOAST UI.
Offering new repository of NHN Entertainment
We've been discuss about offering our official named repository. Two subjects.

What benefits give to offering a repository named under the company to community and users? Some wrappers of tui-editor are already maintained by community.
There are many TOAST UI application and components. Do we need to offer all wrapper package repositories?

We'll decide it ASAP, maybe next week.

@dongsik-yoo Thanks for the reply.

I suppose the repository doesn't really matter. The main thing is just the npm package name - which is good at the moment.

I think that primarily, just work with demand. At the moment this package is getting popular, so starting here with Typescript interfaces would be great. Of course if the whole thing was in Typescript, that would be better but it is too much to ask.

Thanks!

NHN Entertainment offers a new repository for angular wrapper. https://github.com/nhnent/tui.ngx-calendar. Thank you @kartikbb @MRisto @amanvishnani @brnrds @Worthy7 @icepeng @srinek .
And another TOAST UI Family, Grid v3.0 has been released. New awesome theme and Tree+Grid feature. Please take a look. This grid has beed adopted by many company at their back office.

Good news.
If we create other Angular wrapper for TOAST UI, then we have to create each repositories like tui.ngx-grid, tui.ngx-chart... right?
I prefer to have only one package tui.angular and import module, like Angular Material does.

Hmm nah. Angular Material is going to rely on a lot of common base components, TUI doesn't.
We can change things in the future but I think we should at least try to continue like this for now until something difficult comes along.
For example:
https://github.com/angular/material2/blob/master/src/lib/tabs/tabs-module.ts
If one uses Angular Material then it's expected that you would use most of the modules. It's not like that with TUI.

I thought too many repos would be created in nhnent organization in future, but it might be ok for now.

@brnrds Do you have write access to the new repo? Can you deal with my PR's please?

@Worthy7 I merged your PR.

Can you also NPM Release? This kinda needs to be a regular thing if possible
On Mon, 9 Jul 2018 at 17:01, 유동식<EMAIL_ADDRESS>wrote:

@Worthy7 https://github.com/Worthy7 I merged your PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nhnent/tui.calendar/issues/82#issuecomment-403393888,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEirH5SCvz42MjsYOhPSdearAjj1QKkCks5uEw3PgaJpZM4Tqtx0
.

@Worthy7 Did you get the npm access permission from @brnrds ?
There is possibility that I make a mistake because I don't know about this wrapper.
I think it's better that you and @brnrds release the npm package.
What do you think?

I have no idea how to release packages but I can learn. Thanks
On Mon, 9 Jul 2018 at 17:43, 유동식<EMAIL_ADDRESS>wrote:

@Worthy7 https://github.com/Worthy7 Did you get the npm access
permission from @brnrds https://github.com/brnrds ?
There is possibility that I make a mistake because I don't know about this
wrapper.
I think it's better that you and @brnrds https://github.com/brnrds
release the npm package.
What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nhnent/tui.calendar/issues/82#issuecomment-403405016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEirHx9twC7BhoCwbgA-VDbfqmSF7ydTks5uExeegaJpZM4Tqtx0
.

Anyone knows why I am getting the errors above?

@vindiezel23

Please open these issues in the ngx repo
The latest npm is broken @dongsik-yoo

@vindiezel23 The wrappers of tui-calendar are maintained by community and users. So ngx-tui-calendar's users will be grateful for you if you send us PR.
@Worthy7 I'm sorry but I can't maintain the ngx repo because NHNEnt offers the ngx repo by request of users.

@dongsik-yoo Well, someone needs to be in charge of pushing and fixing NPM packages.

@brnrds Could please write about release process of  npm package?
@Worthy7 I agree. I ask @brnrds to provide the release process.

@brnrds poke

@dongsik-yoo Can you please give me NPM permission for now and I'll see what I can do

@dongsik-yoo  https://www.npmjs.com/~worthy7

Done. @Worthy7 has been added as a maintainer.

@dongsik-yoo How do you want this to work exactly?
There are two ways:
I make and add features and fix issues via pull requests, then you approve them and pull them into master, and then publish to NPM.
Or, I become a contributer on the repo, and I manage it all.
It makes no sense for me to have NPM permission but not GitHub permission. Let me know which one works for you - I don't mind either way, and I can tell you how to use NPM publish properly since I figured it out today.

@Worthy7 Actually, I have to choose first option that you suggest. Because NHN Entertainment has the company's management policy of their repositories.
I also agree with you about different permission between NPM and Github. But it can't be done with this NHN repository.
How about using another independent repository again?

So who in NHN is going to check Pull requests and publish to NPM?
If there is nobody then it's entirely pointless.
I can teach you about how to do the NPM publishes. I wrote it here:
https://github.com/Worthy7/tui.ngx-calendar/wiki/How-to-NPM-Publish-(for-devs)
Remove my permission from NPM then. I would rather keep this simple for myself. At some point I think that NHN should be contributing to this angular version anyway, so keeping the repo with you guys seems logical.

@dongsik-yoo Please merge in my pull request for ReadOnly, then the NPM changes one,  and try to publish to NPM yourself then :-)

@dongsik-yoo @Worthy7 , is there any update on the Angular 5/6/7 wrapper for this component?

@nicholasgcoles It's completely dead and it looks like it will stay that way.


HADOOP-18416. fix ITestS3AIOStatisticsContext test failure

Follow on to HADOOP-17461.
Description of PR
backport from trunk for test fix, also contains a commented out portion (to be added once prefetch jira is in branch-3.3)
How was this patch tested?
mvn clean verify -Dparallel-tests -DtestsThreadCount=4 -Dscale
[WARNING] Tests run: 417, Failures: 0, Errors: 0, Skipped: 4
[WARNING] Tests run: 1147, Failures: 0, Errors: 0, Skipped: 146
[ERROR] Tests run: 124, Failures: 0, Errors: 1, Skipped: 10 (timeout error, unrelated)
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

CC: @steveloughran @mukund-thakur. Backport to the trunk test fix, but also contains a commented-out portion as discussed (to be added once prefetch jira is in branch-3.3).

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  0s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
39m  8s

branch-3.3 passed

+1 :green_heart:
compile
0m 44s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 41s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 51s

branch-3.3 passed

+1 :green_heart:
javadoc
0m 46s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 27s

branch-3.3 passed

+1 :green_heart:
shadedclient
26m 45s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 42s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 23s

the patch passed

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
javadoc
0m 26s

the patch passed

+1 :green_heart:
spotbugs
1m 11s

the patch passed

+1 :green_heart:
shadedclient
25m 41s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 17s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

104m 38s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4931/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4931

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux cedd50bbc5a4 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / efd684bcd03f16b4e2c0e3874a6a0bacd9b550a2

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4931/1/testReport/

Max. process+thread count
526 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4931/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

LGTM.
Mehakmeet, you don't need to get a +1 on a simple backport, seeing that yetus is happy is enough. if it's complicate it is still good to get some review, but only looking for risk of regressions, rather than any major change

@steveloughran Noted. Wanted to double-check since this has a commented-out bit from the trunk changes. Wanted to see if this was within the coding standard(having a TODO comment in production code). Thanks for letting me know.

Cherrypicked this one in branch-3.3.5 @mehakmeet  thank me later :P

@mukund-thakur Thanks! 😄


Need a way to update list of gdk-pixbuf loaders

Other packages can provide "loader" plugins that gdk-pixbuf can load dynamically, allowing it to process new image format files. But in order for gdk-pixbuf to know about these loaders, a special cache file must be updated when these packages are installed or uninstalled.
I believe that this means that packages that provide gdk-pixbuf loaders — like the newly-added librsvg — need post-link and post-unlink scripts to deal with updating the gdk-pixbuf loader cache.
In order to update the loader cache, one needs to execute a non-trivial bit of shell code. Below is what I have been using in my personal packages:
# Make sure that loaders.cache is fully up-to-date. I don't want to assume
# that pkg-config is available, so we hack a bit to avoid running it when we
# get the cache location. Or we could just glob or hardcode the binary version
# ...

set -e
eval $(grep -v : $PREFIX/lib/pkgconfig/gdk-pixbuf-2.0.pc)
if [ -z "$gdk_pixbuf_cache_file" ] ; then
    bindir="$(echo $PREFIX/lib/gdk-pixbuf-2.0/*)"
    if [ ! -d $bindir ] ; then
       echo >&2 "error: no such gdk-pixbuf binary directory $PREFIX/lib/gdk-pixbuf-2.0/*"
       exit 1
    fi
    gdk_pixbuf_cache_file=$bindir/loaders.cache
fi
$PREFIX/bin/gdk-pixbuf-query-loaders >$gdk_pixbuf_cache_file

I think that gdk-pixbuf should provide this bit of shell script so that not every dependent package needs to embed the same logic — that way, if the script needs changing, all that needs to happen is to update the gdk-pixbuf package itself.
By the same logic, I think that the above script should just be provided as gdk-pixbuf's own post-link and post-unlink scripts. Other packages can then just pass off responsibility on to it:
exec $PREFIX/bin/.gdk-pixbuf-post-link.sh

I can prepare a PR if this sounds like a good plan.

That would have helped this n00b today

Wait a minute, I fixed this! This functionality is now available.


[REVIEW] Would love some feedback

Resume link
https://drive.google.com/file/d/1h0grq7rQEv4ltwCId3a7NjAXyUMQNq5Z/view

Some suggestions from my point of view -

Bold the skills, you have used in your projects or in your open-source contributions
In the education section, mention only pass out batch year (according to your resume, it would be 2023 I guess, instead of 2020-present)
your wheatherz deployed link is taking too much time to load.
improve the UI of your wheatherz application.
there are too many white spaces in your resume. Try to reduce it.

One thing I must say, I am impressed to see the Project section as the first section. people generally choose education as the first section.

Thank you so much for the feedback 👍🏽

@theritikchoure will you please review my resume?
here is the link: https://drive.google.com/file/d/12oiADJEPhcr4hpfmbDgwqZmRtzAuxHn9/view

@asifurrahaman754

try to write every bullet point in a complete sentence.

for example, your current bullet point

Implemented search in user panel.

you can write like this 👇

implemented search in the user section which searches by username, email, and name or user location

there are too many white spaces in your resume. Try to reduce it.
try to include 3-4 bullet points for your project's description.
do not include the duration of the project
increase the font size (it is not 12px)

I really like your portfolio. Good job 👍

@theritikchoure thank u so much, will do that


improvements to saving and loading callback state

What does this PR do?
Draft with initial commit for an improved state saving and loading for Callbacks.

This is a bugfix, since pickling with the keys type(callback) would pickle the callback class source, and this prevents loading the checkpoint outside of PL.

Feature: With a state identifier, we will be able to produce a (more) unique key for the callbacks. It allows us to save more than one of the same type of callback since we can now disambiguate.

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Hello @awaelchli! Thanks for opening this PR.

In the file pytorch_lightning/trainer/callback_hook.py:

Line 275:21: W503 line break before binary operator

Do see the Hitchhiker's guide to code style


add topics

I suggest adding topics such as turbulence, cfd in the About section at https://github.com/astr-code/astr

thanks for the head up.


thank you for this amazing resource

this is my first open source contriputing

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @serkan1221, @aggdotred, @DenisRebenok, @anhskohbo, @onurvarol, @featheredperson, @hschen2k

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
rmkrjy, @ahlinc, @athanasiaorange, @ahoskins, @rahulkp220, @arlandi, @peachypeace, @crudbug, @ZielinskiLukasz, @sachaarbonel, @nchamaa, @christianboyle, @kohlerm, @MrinalJain17, @RonanTalboom, @fpilee, @lootstrum, @Semmu, @ykari, @lricoy

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
mtfash, @wuhaow, @Yang-zhiyuan, @ztxcyk, @prabuddh1, @dxnn, @Nicacioneto, @anarkrypto, @DENGCPU, @om2c0de, @nerdfiles, @KingjZhang, @OXOYO, @liulinhui, @gawd-coder, @tsalvatore, @dfinkler, @matavic, @askender, @vpodolyan

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!soliditydev, @southppp22, @mimiweary, @pauluhn, @Krustev3233, @ShaanWocker, @hjxhjxhjx1997, @fijimunkii, @forrestchang, @jasan-s, @livc, @koshieguchi, @codyx, @0xBaconPancakes, @JTGMAGIC, @mateuszwestrych, @Zer0ne001, @emmeair, @mauluong, @sinornis

Hey there,
We've got some thrilling news for you! GitHub is currently looking for skilled Developers to join our team. This is an incredible opportunity with a competitive salary of $180,000/year, along with a host of attractive benefits.
Interested in taking your career to the next level? Don't miss out! Click here to apply and secure your spot.
Looking forward to potentially welcoming you aboard!
Best regards,
GitHub Recruitment Team
0xxs, @didaunesp, @annata, @eighteyes, @Sweetheart11, @prite36, @mebizx, @prxgr4mm3r, @garyhtou, @Huaida, @SolbiatiAlessandro, @Baoufa, @aliel, @veejar, @hankmor, @kincsescsaba, @andrusenn, @arekgotfryd, @Neo42, @npjd


add TROUBLESHOOTING.md

Fixes #2928.

We should change the main readme to point to this doc instead of the shared troubleshooting doc on gcloud-common.

Also, add [skip ci] in the commit description.

pls don't close #2928 yet. I'll add another PR w/ more information after this file is committed.

@garrettjonesgoogle @saturnism Done.

Sorry I think I wasn't clear - the [skip ci] has to be in the title, not the extended description.

do we need to update README.md as well? There is a Troubleshooting section that points to a shared troubleshooting doc that only has links.

@saturnism I already recommended that and @pongad already took care of it.

@garrettjonesgoogle Done, but [skip ci] seems to not stop Circle...

Looks like [skip ci] doesn't apply to fork builds: https://circleci.com/docs/1.0/skip-a-build/
When you squash & merge, could you put the [skip ci] on the end instead of the beginning of the commit title?


Backdrop is not compiling after upgrading to Flutter 3.10

Describe the bug
After upgrading Flutter to version 3.10.0 I can no longer compile app that is using backdrop package.
This is due to breaking changes in AppBar widget:
https://docs.flutter.dev/release/breaking-changes/3-7-deprecations#appbar-sliverappbar-and-appbartheme-updates
brightness and textTheme properties have been removed.
To Reproduce
Steps to reproduce the behavior:

Upgrade Flutter to version 3.10.0
Try to compile the code.
See error:
app_bar.dart:199:7: Error: No named parameter with the name 'brightness'

@tobolski thank you. will have a look asap

@tobolski This has been fixed and released to pub.dev with v0.9.0.
Thanks for reporting, do check yourself in project's README!


feat: rename CowSwap -> CoW Swap

Current dependencies on/for this PR:

main

PR #1111   👈

This comment was auto-generated by Graphite.


Requirements: upgrade to mypy 0.590 & add assertion in timeout.py.

Latest upgrade to mypy, with minor assertion fix.
I'm getting another provision issue, though I have followed the requirements upgrade process, and run-mypy is running fine with mypy 0.590 and this small fix. The error I have is as follows; happy to retest on my droplet if there is advice on resolving this:
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=6.11.5".

With mypy 0.590, we can now add a py.typed file, to indicate that Zulip is typed in the packaging, though PEP 561 is still WIP as I understand it. We can also do so for the API repo, for which 0.590 otherwise doesn't make much of a change (from 0.560).

@priyankp10 I think that yarn error suggests we should upgrade ts-loader; can you take care of that?
I think adding a py.typed is irrelevant for the main Zulip repo (realistically, nobody is going to build a package using it as a library), but it could be nice for the API repo.

ts-loader is already updated in the webpack upgrade PR, and that upgrade is why we are seeing this error. It looks like the node version is not v8.x.x which it should be, @neiljp did what is the output of node -v  should be v8.11.1.

Oh, interesting; provision should definitely upgrade us to 8.x...
For this PR itself, merged, thanks @neiljp!


[connectivity_plus] eliminate indirect FFI dependency (#65)

Same as

package_info_plus_windows: https://github.com/fluttercommunity/plus_plugins/commit/cf13721d4daf7b838fff6b7442f41a8a67b9fd34
path_provider_windows: https://github.com/flutter/plugins/commit/25957033132ac17094e82bec58e429fac073a483
...

Moves the real implementation of connectivity_plus_linux behind a conditional export, instead of exporting a stub on platforms that don't support dart:ffi. This avoids build breakage in web projects that have transitive dependencies on connectivity_plus (and thus connectivity_plus_linux due to manual endorsement).
This will no longer be necessary once https://github.com/flutter/flutter/issues/52267 is fixed since only Linux builds will ever need to have a code-level dependency on connectivity_plus_linux.

Thank you! Is it necessary to release a new version for connectivity_plus and connectivity_plus_linux?

I think both. connectivity_plus_linux is going to be released for the first time.


refactor some css, add css to column rename

[ ] Documentation

Codecov Report

Merging #290 into remove-styled-components will not change coverage by %.
The diff coverage is 100.00%.

@@                    Coverage Diff                     @@
##           remove-styled-components      #290   +/-   ##
==========================================================
  Coverage                    100.00%   100.00%
==========================================================
  Files                            15        13    -2
  Lines                           182       170   -12
==========================================================
- Hits                            182       170   -12

Flag
Coverage Δ

#cypressspecs
?

#jestspecs
100.00% <100.00%> (ø)

Impacted Files
Coverage Δ

.../components/CardAdder/components/CardForm/index.js
100.00% <ø> (ø)

...ents/Board/components/DefaultColumnHeader/index.js
100.00% <100.00%> (ø)

assets/services/getUrlParams.js

Continue to review full report at Codecov.

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

Codecov Report

Merging #290 into remove-styled-components will not change coverage.
The diff coverage is 100.00%.

@@                    Coverage Diff                     @@
##           remove-styled-components      #290   +/-   ##
==========================================================
  Coverage                    100.00%   100.00%
==========================================================
  Files                            15        13    -2
  Lines                           182       170   -12
==========================================================
- Hits                            182       170   -12

Flag
Coverage Δ

#cypressspecs
?

#jestspecs
100.00% <100.00%> (ø)

Impacted Files
Coverage Δ

.../components/CardAdder/components/CardForm/index.js
100.00% <ø> (ø)

...ents/Board/components/DefaultColumnHeader/index.js
100.00% <100.00%> (ø)

assets/services/getUrlParams.js

Continue to review full report at Codecov.

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


Bug: no message for email confirmation sent

Bug report
Describe the bug
When signing up using Supabase Auth widget, there is no message stating that an email has been sent for confirmation.

This looks like a duplicate of https://github.com/supabase/ui/issues/73?

Yep @jonthomp, duplicate indeed.
Closing in preference for #73


Container fails to start

Hi there, my container is failing to start.
  shinkro:
    image: ghcr.io/varoop/shinkro:latest
    container_name: shinkro
    volumes:
      - /home/containers/shinkro:/config
    ports:
      - 7011:7011
    environment:
      - SHINKRO_USERNAME=NAME
      - SHINKRO_PASSWORD=PASSWORD
      - PLEX_USERNAME=NAME
      - ANIME_LIBRARIES=Anime
      - PUID=1000
      - PGID=1000
    restart: unless-stopped
    security_opt: [no-new-privileges:true]

Tailing the logs:
2024-12-02T05:23:32.974601819Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:32.989767848Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:34.163037660Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:35.110729494Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:36.187768973Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:37.632501938Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:39.870198922Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:43.721982458Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:23:50.748574207Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:24:04.161727082Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:24:30.423082962Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:25:22.244553236Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:26:22.872838575Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:27:23.534696047Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:28:24.242303871Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:29:24.934789267Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:30:25.607970766Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:31:26.292649026Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:32:26.887851120Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:33:27.502777480Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:34:28.163419798Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:35:28.830427737Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:36:29.461802405Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:37:30.179140131Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:38:30.796475724Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:38:39.385612811Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:38:40.327674594Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:38:41.219078667Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:38:42.280011060Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-02T05:38:43.706462544Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")

Hi, I tried to replicate this error but wasn't able to. Could you tell me about the environment you are using?
Additionally try running gosu "$USER_NAME" /usr/local/bin/shinkro --config /config from the container's terminal and let me know the output.

Hi, I tried to replicate this error but wasn't able to. Could you tell me about the environment you are using?

Sure! I'm on a RPi 4B (Debian bookworm) using docker compose with the above config. For what it's worth, the config.toml file was created but is empty.

Additionally try running gosu "$USER_NAME" /usr/local/bin/shinkro --config /config from the container's terminal and let me know the output.

Unfortunately I cannot because the container seemingly crashes immediately on start-up. Even with docker compose run shinkro gosu "$USER_NAME" /usr/local/bin/shinkro --config /config, I get:
/usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")

Hmm, config.toml shouldn't be empty but that's not the issue here. You can keep the container running and try executing other commands in it by accessing the container's shell like this:
docker exec -it shinkro /bin/sh
Then run the command I mentioned earlier.  Just try executing docker compose down and then docker compose up -d before it.

docker exec -it shinkro /bin/sh

Yea, unfortunately that doesn't work unless the container is running. When shinkro crashes the container goes down. I had tried that earlier:
jono 🌐 Pi in ~
λ dc-up shinkro
[+] Running 1/1
 ✔ Container shinkro  Started

jono 🌐 Pi in ~
λ docker exec -it shinkro /bin/sh
Error response from daemon: Container 8ad48f3640006bc06258d4ff8396f571eb27cf9f78df36693bbf6e543c8bbeb9 is restarting, wait until the container is running

*spamming the above command results in the same thing until the container is up, then immediately crashes resulting in...*

jono 🌐 Pi in ~
λ docker exec -it shinkro /bin/sh
OCI runtime exec failed: exec failed: cannot exec in a stopped container: unknown

Hmm, this is quite strange I am not able to replicate this issue on arm so it's not a platform specific issue. Could you try creating the container without setting the PUID and PGID?

Hmm, this is quite strange I am not able to replicate this issue on arm so it's not a platform specific issue. Could you try creating the container without setting the PUID and PGID?

Ahh that's probably it. Starting without the PUID/PGID vars:
2024-12-03T06:41:40.562920147Z chown: unknown group
2024-12-03T06:41:40.589912497Z 2024-12-03 06:41:40 FTL shinkro.Username not set in /config/config.toml
2024-12-03T06:41:41.517930770Z chown: unknown group
2024-12-03T06:41:41.532850896Z 2024-12-03 06:41:41 FTL shinkro.Username not set in /config/config.toml
2024-12-03T06:41:42.393234831Z chown: unknown group
2024-12-03T06:41:42.407347815Z 2024-12-03 06:41:42 FTL shinkro.Username not set in /config/config.toml
2024-12-03T06:41:43.433200546Z chown: unknown group
2024-12-03T06:41:43.446997682Z 2024-12-03 06:41:43 FTL shinkro.Username not set in /config/config.toml
2024-12-03T06:41:44.871682061Z chown: unknown group
2024-12-03T06:41:44.887000201Z 2024-12-03 06:41:44 FTL shinkro.Username not set in /config/config.toml

Then took down the container, added the vars back in, and started again:
2024-12-03T06:42:10.834471493Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-03T06:42:11.808708283Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")
2024-12-03T06:42:12.802458436Z /usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")

Is there any way to not have this container run as root?

 Specifically, this one : gosu "$USER_NAME" /usr/local/bin/shinkro --config /config

Similar issue to before unfortunately; the container crashes immediately with this error:
2024-12-03T06:41:44.871682061Z chown: unknown group
2024-12-03T06:41:44.887000201Z 2024-12-03 06:41:44 FTL shinkro.Username not set in /config/config.toml

And I can't run the command because the container has shut down.

hmm try deleting config.toml from your local folder, and then let the container create it again from scratch using the env variables. It is only crashing now because config.toml is empty which is expected behavior

Sweet, that did the trick!
jono 🌐 Pi in ~
λ dc-up shinkro
[+] Running 1/1
 ✔ Container shinkro  Started                                                                                0.6s

jono 🌐 Pi in ~
λ docker exec -it shinkro /bin/sh
/app # gosu "$USER_NAME" /usr/local/bin/shinkro --config /config
/usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")

Could you also try running just gosu version ? Let me know the output of that

Could you also try running just gosu version ? Let me know the output of that

/app # gosu version
/usr/local/bin/gosu: line 0: syntax error: unexpected end of file (expecting ")")

Okay, looks like gosu isn't working correctly, try using this image, I have added fixes to the way gosu is installed:
docker pull ghcr.io/varoop/shinkro:pr-57
Let me know if that works for you with all env variables including PUID and PGID set normally

Success!

Now that's working, thank you! Is there a way to run this container without root privileges though?

The shinkro process will always run on user set by PGID & PUID. Outside of that you can choose to run the container by another user using docker compose like this:
  shinkro:
    image: ghcr.io/varoop/shinkro:latest
    container_name: shinkro
    **user: 1000:1000**
    volumes:
      - /home/containers/shinkro:/config
    ports:
      - 7011:7011
    environment:
      - SHINKRO_USERNAME=NAME
      - SHINKRO_PASSWORD=PASSWORD
      - PLEX_USERNAME=NAME
      - ANIME_LIBRARIES=Anime
      - PUID=1000
      - PGID=1000
    restart: unless-stopped
    security_opt: [no-new-privileges:true]
    ```


docs(ia) Improve information architecture of the Capabilities section and metadata content

Made several improvements to the Capabilities section:

Divided and chunked the content into new sections for Data Management, Search and Retrieval, and Generation and Observability
Refined the previous Metadata Filters section by chunking into separate child topics, improving navigation and usability
Miscellaneous improvements throughout these new sections

@pwoznic I love this new organization! Thanks for doing this. One suggestion: can we split "Generation and Observability" into "Generation" and "Observability and Evaluation"? I think the latter stands alone, as it's a major area in which we're investing.
The hierarchy would then be:

Generation

Mockingbird LLM
Summarizers
Generative prompts

Observability and Evaluation

Query Observability
Hallucination Evaluation

Also, on a separate note, "summarizers" no longer exist in API v2 as a concept. They're now replaced by "generation presets". Per the Query API docs:


Netrw shows a empty window when jumping back

Steps to reproduce

Create a folder 1 with a subfolder 2 inside it
Run gvim.exe 1, gVim shows the contents of folder 1
Select 2/ and press Enter, gVim opens folder 2
Press Ctrl-o. An empty window is shown.

Expected behaviour
The contents of folder 1 should be shown.
Version of Vim
9.1.466
Environment
OS: Windows 10 Home
Terminal: GUI
Logs and stack traces
No response

FWIW, I tired it with Vim 9.1.505 on Arch Linux, and it exits to shell at step 4.

I had a quick look, but too much messes with the jumplist. Even on a empty profile, I already have one jump when loading netrw. When switching to another directory, I had created several invalid jump positions, so I had to use <Ctrl-O> several times until I got back to the previous buffer. Note, even searching to the 2 directory creates a jump list entry.
I don't think there is an easy solution to it. Jumps are just created to easily (and depend on your viminfo file). I have long given up with the jumplist, I find it too confusing.

FWIW, I tired it with Vim 9.1.505 on Arch Linux, and it exits to shell at step 4.

I have no idea, how Ctrl-o can return to the shell. That sounds wrong.

I have no idea, how Ctrl-o can return to the shell. That sounds wrong.

Sorry for the false alarm, turns out what thought to be "exiting to shell" had to do with Midnight's Commander Ctrl-o shortcut (I ran Vim from Midnight Commander's command line).


Unable to extract and upload PackageInfo.xml

When attempting to perform Attestation signing, I am now getting an error about missing PackageInfo.xml when uploading the file to the partner center.  However, this document does not explain that file, or its contents - nor does it list it as a requirement for attestation signing.

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

ID: ed287852-04b7-1569-fd51-2640cfa24f57
Version Independent ID: a8ce732f-5b41-f1ce-e37d-a7c2794546a4
Content: Attestation signing a kernel driver for public release - Windows drivers
Content Source: windows-driver-docs-pr/dashboard/attestation-signing-a-kernel-driver-for-public-release.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @EliotSeattle
Microsoft Alias: eliotgra

Thanks for the feedback, @toonetown, and apologies for the delay.
I see in https://social.msdn.microsoft.com/Forums/ie/en-US/2e4e98bd-49ce-4d44-bee1-68cc79d23c14/unable-to-extract-and-upload-packageinfoxml?forum=whck that this was due to a temporary server error and has since been resolved.
Sorry you had trouble, and glad it's fixed!


Training on Submitted Images

IDK if this is already taking place but maybe you could use images submitted to help train the Neural Network?
Also maybe there could also be a people category.

Hey hey!  So the first things first.  If you have some categories that you're identifying as mistakes, you can contribute to the scraper.
https://github.com/alexkimxyz/nsfw_data_scraper
There might be a torrent file of the training data soon.  From that torrent, there is room to clean the data and augment and organize it.

Ask me or https://twitter.com/KarthikRevanuru for the key
https://mega.nz/#!Q5RnDQYa
Let me know if you make a modified training set that we could use!


No MQTT re-subscription if connection lost for Cloud script

When using the cloud script, if for some reason, the MQTT server connection is lost (server restart, network outage, etc...), the service never tries to subscribe back to the command topic.
You have to restart the service to make the commands work again.
It could be a great enhancement to check if subscription is still active.

Hello @smillier, I've pushed a commit to address this (https://github.com/SebLz/ha-addons/commit/3fd9c45ecc6bdf7c5f01b07cb78882ee7c2c158e), is this better on the new version ?

It seems to be working fine now. Thanks for the improvement.


Bottom Navigation Bar instead of Tab Bar

Hi there! I came across this repository and spotted an issue that caught my attention. I'm relatively new to coding and have been working with Dart for only about 8-9 months So please let me know if there is issue with code i have written, I'm eager to learn and contribute to Hacktoberfest. Looking forward to collaborating with you all!

@ManishModak Can you share a screen recording with the changes?

@ManishModak Nice work on your part. But there was already one existing PR before yours.
Closing this as of now. If you have noticed any other improvement scopes/bugs, please feel free to open a PR.

ok no problem i will see if i can contribute in something else.


New package: Mill v1.7.0

Registering package: Mill
Repository: https://github.com/pevnak/Mill.jl
Created by: @Sheemon7
Version: v1.7.0
Commit: 4bc05bb0854d4492cd3071a84c93dd9a9b0618fd
Git reference: master

Assuming #4328 is what you want.


push image without namespace failed

Login as admin and try to push a image failed, got "insufficient scope" from registry/distribution. Here is the command that I use to push
docker push <IP_ADDRESS>/ubuntu:v0.4
the project/namespace where I am trying to push to is the library project under admin account, I supposed to have the write permission. When I dig into the harbor code I find
https://github.com/vmware/harbor/blob/master/service/utils/authutils.go#L66
Obviously, harbor intentionally omit this kind to scenario , I want know is this a bug or not?
thanks

It's not a bug, the design is you need to explicitly set the namespace in push command, in your case:
docker push <IP_ADDRESS>/library/ubuntu:v0.4
the library was added by docker client when trying to pull images from docker hub.
So you  even can update the code to check against project "library" when the namespace is not set, but I think the pull will fail, as it will trigger API on registry and registry will not add this "default" namespace

@reasonerjt  make sense to me, thanks for the response

@cmingxu Thanks, I'm closing the issue along with the PR.


VMR Stage 2 Builds Failing in Arcade with Obsolete Reference

The latest run of the VMR is failing stage 2 builds with the following error:
/vmr/src/arcade/src/Microsoft.DotNet.SignTool/src/VerifySignatures.cs(104,42): error SYSLIB0057: 'X509Certificate.CreateFromSignedFile(string)' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057) [/vmr/src/arcade/src/Microsoft.DotNet.SignTool/Microsoft.DotNet.SignTool.csproj::TargetFramework=net9.0]
##[error]/vmr/src/arcade/src/Microsoft.DotNet.SignTool/src/VerifySignatures.cs(104,42): error SYSLIB0057: (NETCORE_ENGINEERING_TELEMETRY=Build) 'X509Certificate.CreateFromSignedFile(string)' is obsolete: 'Loading certificate data through the constructor or Import is obsolete. Use X509CertificateLoader instead to load certificates.' (https://aka.ms/dotnet-warnings/SYSLIB0057)

This error is the result of these changes being brought in by https://github.com/dotnet/sdk/pull/41988.
We need to update the code in arcade/src/Microsoft.DotNet.SignTool/src/VerifySignatures.cs to remove the obsolete reference.

From https://github.com/dotnet/docs/issues/41662:

If you are loading X.509 content, X509CertificateLoader.LoadCertificate and X509CertificateLoader.LoadCertificateFromFile can be used.

Oh nice, the next breaking change. @ellahathaway will you take care of it or should I?

Oh nice, the next breaking change. @ellahathaway will you take care of it or should I?

@ViktorHofer Ikr. I've got this one, but thanks for offering to help :)


Development - Deletion process after sending email

use TransactionalEventListener to update the reported state and create new service class to check the reported item and detele them

update the status as reported -> delete process is triggered


archisteamfarm: Add shim

It is a CLI app, so make sense to have a shim for it.

Closes #XXXX

Relates to #XXXX

[x] I have read the Contributing Guide.

Thanks!


Does not change any Value after Upload

Hi Guys,
i have an issue when Uploading my csv to Jamf Pro.
I got following errors :
2022-08-19 11:42:30 [INFO  ]: Beginning CSV Parse - Attributes update.
2022-08-19 11:42:30 [INFO  ]: Attempting to GET the Jamf Pro Version from the API.
2022-08-19 11:42:30 [INFO  ]: Successful GET completed. 200.
2022-08-19 11:42:30 [INFO  ]: Jamf Pro Version: 10.40.1-t1659581750
2022-08-19 11:42:30 [INFO  ]: Submitting a PUT to https://xxxxx.jamfcloud.com/JSSResource/mobiledevices/serialnumber/F9FZP0W2MF3Q
2022-08-19 11:42:30 [ERROR ]: Failed PUT. 403.
2022-08-19 11:42:30 [ERROR ]:

Status page

Forbidden
The server understood the request, but is refusing to fulfill it
You can get technical details here.
Please continue your visit at our home page.

2022-08-19 11:42:30 [INFO  ]: Submitting a PUT to https://xxxxxx.jamfcloud.com/JSSResource/mobiledevices/serialnumber/xxxxxxxx
2022-08-19 11:42:30 [ERROR ]: Failed PUT. 403.
2022-08-19 11:42:30 [ERROR ]:

Could you guys please help me to solve the issue.
It would really help us in our Daily Business.
Kind Regards

Hey @kkug10290! if you've already moved past this just let us know, but to explain the problem:
A 403 error means the account used to access the resource doesn't have the correct permissions. See: https://developer.jamf.com/jamf-pro/docs/getting-started-2
According to: https://developer.jamf.com/jamf-pro/docs/classic-api-minimum-required-privileges-and-endpoint-mapping
the account needs these permissions:

Update - Mobile Devices
Update - Users

So the first step is to make sure the account you're logging into the mut with has those permissions.
If that still fails does switching to the most up to date version of the mut change the error?


Detect amount of words that are written in all capital letters

Already in: https://github.com/SuffolkLITLab/FormFyxer/blob/88595275b5d3cfdcea4be501be547fae67900fd6/formfyxer/lit_explorer.py#L723


Deprecate PyramidInputPresenter >> #strings in favor of #inputModel

We can use string as the model for each input. In most of the case it will only be strings but we could imagine injecting other thing in the input using the strings and applyStrings methods.

done in #202


Feature request: Support mdx component rendering

Runme's current implementation will ignore the mdx-superset and treat it as vanilla markdown.
It'd be great to make transparent mdx component rendering available.

Should we transfer this issue to https://github.com/stateful/runme ?

I don't know the architecture well enough but if that's what makes sense go for it /cc @adambabik 👍

Let’s keep it here please at least until it’s being worked on. This is the
repo that’s linked to the extension so users will pay attention to it
irrespective of implementation details.
On Wed, Oct 26, 2022 at 4:22 PM Adam Christian @.***>
wrote:

I don't know the architecture well enough but if that's what makes sense
go for it /cc @adambabik https://github.com/adambabik 👍
—
Reply to this email directly, view it on GitHub
https://github.com/stateful/vscode-runme/issues/33#issuecomment-1292610713,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB5FH2Y75RTIDJSATWDTGTWFGHITANCNFSM6AAAAAARNKWCC4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Validate workflow document updates

Validate workflow document to track clinical process.
Shared and validated to make sure it's updated in the right way.

Maybe included with #211 ?


climate slider may have 0 size

If previous column is very large climate slider can have 0 size which allows to set only minimum size.

@tomaszduda23 any workarround on this yet?


Support precompiling NIfs

It would be awesome if it was possible to precompile (and possibly cross-compile for different architectures) the Nifs for published libraries. This would make the installation by the user of the library a lot and removes the requirement to install Zig.
This has already been done by other Nif providers like rustler:
https://github.com/philss/rustler_precompiled
It usually works by building the nifs and adding the object files to a GitHub release.
When a user installs the library from Hex, the library looks if the files exist locally and downloads them from the release if not.

yep.  This is on the todo list in VERSIONS.md  I will try to do it for 0.14 (thought I had an issue up for it but i don't see it anymore)


Organizations of event managers

Being a member of an organization allows you to create and edit any event owned by that organization.
Each organization should have a page with a list of events and any organization information. Possibly related to #227, or could just have a website link and text field.

I think the organization should also have other information. Highest priority: the organization's favored payment configuration and the organization's locale info. This would give us a mechanism to allow limited event creation by non-superusers and could help streamline event creation overall for organization members.

:+1:

Resolved by a4a975453f9143d16096f374da3df5c5f59ecbbd


Make function to plot abundances

Codecov Report

Merging #14 (cab8776) into main (f070191) will decrease coverage by 4.49%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
- Coverage   46.42%   41.93%   -4.50%
==========================================
  Files           3        3
  Lines          56       62       +6
==========================================
  Hits           26       26
- Misses         30       36       +6

Impacted Files
Coverage Δ

src/wrappers.jl
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Bump v6.0.0

Artifact can be viewed here: :
https://3952-62313804-gh.circle-artifacts.com/0/sandbox/mdbook/book/index.html

Artifact can be viewed here: :
https://3951-62313804-gh.circle-artifacts.com/0/packages/style/storybook-static/index.html

Artifact can be viewed here: :
https://3951-62313804-gh.circle-artifacts.com/0/sandbox/sapper/__sapper__/export/index.html

Artifact can be viewed here: :
https://3951-62313804-gh.circle-artifacts.com/0/sandbox/vuepress/docs/.vuepress/dist/index.html


Page navigation on main site

Codecov Report

Merging #34 (639970d) into master (f5e57b3) will decrease coverage by 0.45%.
The diff coverage is 100.00%.

:exclamation: Current head 639970d differs from pull request most recent head 3be4a34. Consider uploading reports for the commit 3be4a34 to get more accurate results

@@            Coverage Diff             @@
##           master      #34      +/-   ##
==========================================
- Coverage   83.57%   83.11%   -0.46%
==========================================
  Files          85       85
  Lines        1406     1404       -2
  Branches      116      117       +1
==========================================
- Hits         1175     1167       -8
  Misses        231      231
- Partials        0        6       +6

Impacted Files
Coverage Δ

LinkDotNet.Blog.Web/Pages/Index.razor
100.00% <100.00%> (ø)

LinkDotNet.Blog.Web/Pages/BlogPostPage.razor
86.66% <0.00%> (-6.67%)
:arrow_down:

...Web/Shared/Admin/Dashboard/VisitCountPerPage.razor
88.00% <0.00%> (-4.00%)
:arrow_down:

...egistrationExtensions/SqlRegistrationExtensions.cs
71.42% <0.00%> (-3.58%)
:arrow_down:

LinkDotNet.Blog.Web/Shared/Skills/SkillTable.razor
71.11% <0.00%> (-2.23%)
:arrow_down:

LinkDotNet.Blog.Web/Shared/Profile.razor
94.91% <0.00%> (-1.70%)
:arrow_down:

Continue to review full report at Codecov.

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


Improve ROS2 code generator to support Services, Actions and parameters

The current template supports only topics.
https://github.com/ipa320/ros-model/blob/master/plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/Ros2CodeGenerator.xtend

Done for services.
The full ROS2 support will be re-plan and probably the ROS2 src code generator completely re-written , then this issue can be closed . For the new implementation the meta-issue #109 holds already the topic

Done for services.
The full ROS2 support will be re-plan and probably the ROS2 src code generator completely re-written , then this issue can be closed . For the new implementation the meta-issue #109 holds already the topic


Add hyva back to sponsors

Hyvä has sponsored twice the amount Sansec has sponsored (and continues to sponsor till date), so it seems fair to still be mentioned as Gold Sponsor.

For reference: https://opencollective.com/warden
@navarr

@wigman  According to Open Collective, we only have "Backers" and "Supporters", and only "Supporters" have the benefit of being listed on the Warden site. They're also listing Hyvä as a "Backer" level, not "Supporter". That's the only reason I am marking this as rejected, but @navarr can chime in and override it if he feels.

@bap14 I've spoken directly to Willem about this. I'd like to leave this open while I think of ways of honoring previous sponsors. Hyvå was incredibly lovely and helpful as was Swiftotter and they deserve some amount of continuing recognition (that doesn't detract the current sponsors)

@navarr I figured there was a history there I wasn't aware of.

Just an idea - what if add to sponsors not only current sponsors, but also those who donated let's say >$500 over last year?


Add README

Can we add something related to middleware in a separate PR?

Sure, not a blocker for me. I would be happy to add it even.


Revisit demo MediaFlux code, post-retreat

After the RDSS retreat day (March 13, 2023), revisit this code, this code, this code, and this code, and either remove or refactor it to pass CI/work with our agreed-upon programmatic approach sustainably.
Acceptance criteria:

[ ] Add pagination to classes https://github.com/pulibrary/tiger-data-app/tree/main/app/models/mediaflux
[ ] Add additional classes to https://github.com/pulibrary/tiger-data-app/tree/main/app/models/mediaflux
[ ] Edit the code and update to utilize helper classes in https://github.com/pulibrary/tiger-data-app/tree/main/app/models/mediaflux

Hey team! Please add your planning poker estimate with Zenhub @bess @jrgriffiniii


add initial_value for base vars

Followup of #2670 which implemented initial_value for computed vars.
import reflex as rx

from pydantic import Field

class State(rx.State):
    basevar: str = Field(default="basevar", initial_value="initial")

    @rx.var(initial_value="initial")
    def test(self) -> str:
        return "Hello, world!"

#  cv = State.test
#  cv_initial = cv._initial_value
#  print(f"{cv=}, {cv_initial=}")

#  state = State()
#  state_d = state.dict(initial=True)
#  initial_d_state = state_d["state.state"]
#  initial_test = initial_d_state["test"]
#  print(f"Initial state: {initial_test=}")

def index() -> rx.Component:
    return rx.center(
        rx.vstack(
            rx.heading(State.test),
            rx.heading(State.basevar),
            rx.button(
                "Check out our docs!",
                size="4",
            ),
            align="center",
            spacing="7",
            font_size="2em",
        ),
        height="100vh",
    )

app = rx.App()
app.add_page(index)

@benedikt-bartscher can you elaborate on the use case for this feature? I'm trying to understand where the "initial_value" would show up? Seems like a pre-hydration placeholder maybe?

@masenf  you are right, it allows setting a different value in the initial state dict (pre-hydration). This can f.e. be used to prevent default_factorys to be executed at compile time.

This can f.e. be used to prevent default_factorys to be executed at compile time.

At compile time, the State class is still instantiated, so i believe that would call all of the default_factory functions regardless. There would need to be some mechanism to delay the execution of these functions in the Base itself i think.

Marking this as draft until re-synced with main (can be closed if it's no longer needed)


Various cleanups, use random seed, optimization

@hhbyyh Please verify that the changes make sense, especially removing the kron() call.  Thanks!
For private vars needed for testing, I made them private and added accessors.  Java doesn’t understand package-private tags, so this minimizes the issues Java users might encounter.
Change miniBatchFraction default to 0.05 to match maxIterations.
Added a little doc.
Changed end of main online LDA update code to avoid the kron() call.  Please confirm if you agree that should be more efficient (not explicitly instantiating a big matrix).
Changed Gamma() to use random seed.
Scala style updates

@jkbradley Thanks for the great effort. I'm running some test to verify the replacement of kron. Other changes looks good to me.

Merged