Add postgres to deployment configuration

Now that tracker has been published with postgres support, we'll want to add some example deployment configuration.

Add a docker/postgres folder and include a simple docker-compose.yaml file for running the postgres integration
Add a step to scripts/generate.sh to generate a postgres.yaml file similar to that of mysql.

You can probably use either of bitnami/postgres or bitnami/postgres-ha since we already have the bitnami repo tapped for mysql.

Update readme to call out to availability of postgres resources

@MadhuvanthG mind taking a look at this now that postgres support has been published?

Sure, this should be quick. I've already got an example, will push it to /deploy repo.Shall look into the scripts as well

An example added in the PR that's open. Now working on adding a step to generate.sh.
@mjpitz, I'm new to Helm (have worked with K8s though). My understanding of what generate.sh does is that

Uses the chart templates for different services (tracker, indexer etc..) under /charts
Packages the chart into a versioned archive under gh-pages branch
Creates a mysql.yaml so someone could easily set-up a mysql DB in K8s (this is what I'll have to replicate for Postgres)

I'm unable to see how all these fit together, if you could help fill gaps in my knowledge/understanding, I could make changes with more confidence.

@MadhuvanthG Helm is a nice little package manager for Kubernetes deployments. There are a lot of cases where you want to have more than one copy of something so having a template package is really useful.
Your understanding of the script is spot on. Having all of the blobs pre-generated makes it super easy for folks to get started.
One place that will help you understand how a lot of this fits in is the deployment documentation section of the site: https://deps.cloud/docs/deployment/k8s/ This space provides a useful landing zone to help folks get started. On the k8s side of the world, I can see us updating Step 3 to say "Deploy Database" instead of explicitly MySQL.
I'm still contemplating if we want a more in depth database section in the docs or not. I added a section on the data models and I figured that would be a good starting point.


Mount failure on Snapshot View.

@ijc recently found that runc couldn't mount volumes inside snapshot view, if the destination path does not exist in the image. That's why we always create new snapshot for application container now https://github.com/kubernetes-incubator/cri-containerd/pull/221.
However, one thing I don't understand is that we are always using snapshot view for our sandbox container, which is using a pause image (built from scratch, only contains a pause binary). And it actually works will until we upgrade containerd to v1.0.0-beta.0.
process_linux.go:348: container init caused \"rootfs_linux.go:57: mounting \\\"proc\\\" to rootfs \\\"/run/containerd/io.containerd.runtime.v1.linux/k8s.io/b2bdb4818eb4717f457f31f2082f3480bbfb2a5567c27c0c0236f8429fb8c312/rootfs\\\" at \\\"/proc\\\" caused \\\"mkdir /run/containerd/io.containerd.runtime.v1.linux/k8s.io/b2bdb4818eb4717f457f31f2082f3480bbfb2a5567c27c0c0236f8429fb8c312/rootfs/proc: read-only file system\\\"\"": unknown

https://travis-ci.org/kubernetes-incubator/cri-containerd/jobs/273504171
https://travis-ci.org/kubernetes-incubator/cri-containerd/jobs/273504679

I could change sandbox to create new snapshot, or remove the default mounts for sandbox container. However, I'd really like to understand why this happens since v1.0.0-beta.0? Is this a regression? What change causes this?

https://github.com/containerd/containerd/pull/1373 caused this, but it is not a regression. Prior to this PR, views were not read-only. Even worse, writing to a view caused corruption of the  parent committed snapshot.
So creating a writable snapshot and let runc remount it as RO via config.json seems the right approach.

@AkihiroSuda Cool! Thanks a lot, that's the answer I need.
I'll fix cri-containerd correspondingly. And will close this issue after the fix is verified. :)

OK. Even I get rid of all mounts, I still get this error:
rpc error: code = 2 desc = failed to create task for sandbox "f958202408b956a05ccc899d4735f8b102ccc845532c975748c6e29028292266": OCI runtime create failed: container_linux.go:265: starting container process caused "process_linux.go:348: container init caused \"rootfs_linux.go:69: creating device nodes caused \\\"mkdir /run/containerd/io.containerd.runtime.v1.linux/k8s.io/f958202408b956a05ccc899d4735f8b102ccc845532c975748c6e29028292266/rootfs/dev: read-only file system\\\"\"": unknown
It seems that runc will try to create /dev no matter what https://github.com/opencontainers/runc/blob/1c81e2a794c6e26a4c650142ae8893c47f619764/libcontainer/rootfs_linux.go#L31.
Given so, I'll use WithNewSnapshot for sandbox container for now.


TypeScript 5.2 "move to file" results in duplicate imports

Bug Report

🔎 Search Terms

refactoring
duplicate imports
move to file

🕗 Version & Regression Information

I was unable to test this on prior versions because it's a new feature in 5.2

⏯ Playground Link
N/A
💻 Code
common.ts:
export const x = 1;

a.ts:
import { x } from './common';

export const bar = x;

b.ts:
import { x } from './common';

export const foo = x;

Use the "Move to file" refactoring to moveexport const bar = x; in a.ts to b.ts:
https://github.com/microsoft/TypeScript/assets/921609/507f0a7f-eab8-4bab-967a-4af92919f201
🙁 Actual behavior
Duplicate imports.
🙂 Expected behavior
No duplicate imports.
Note the same issue occurs with namespace imports.

I got the same general problem, however for me the imports were duplicated even if they didn't exist in the destination file before.
i.e. moving from:
import { baz } from './baz';

export const bar = baz;

into:
import { qux } from './qux';

export const foo = qux;

would result in:
import { qux } from './qux';
import { baz } from './baz';
import { baz } from './baz';
import { baz } from './baz';

export const foo = qux;
export const bar = baz;

Duplicated exactly 3 times, for some reason.


POOL_LBUF_DEPTH for Xilinx Device

Hi, I am trying to build PipeCNN on Xilinx Device. However, the parameter POOL_LBUF_DEPTH required by conv_pipe_xilinx.cl has not defined in hw_param.cl. Any suggestion value for this parameter?

I have replaced the POOL_LBUF_DEPTH with POOL_MAX_SIZE and generated the conv.xclbin successfully. While I meet the following error when executing ./run.exe conv.xclbin ,
ERROR: Invalid scalar argument size, expected 4 got 1
ERROR: clSetKernelArg() for kernel "maxPool", argument index 0.
ERROR: CL_INVALID_ARG_SIZE
Location: host/main.cpp:898
Failed to set argument 0 of kernel pool
I am using the Xilinx Alevo U200 and SDAccel 2018.2
Any suggestion on this error?

I have replaced the POOL_LBUF_DEPTH with POOL_MAX_SIZE and generated the conv.xclbin successfully. While I meet the following error when executing ./run.exe conv.xclbin ,
ERROR: Invalid scalar argument size, expected 4 got 1
ERROR: clSetKernelArg() for kernel "maxPool", argument index 0.
ERROR: CL_INVALID_ARG_SIZE
Location: host/main.cpp:898
Failed to set argument 0 of kernel pool
I am using the Xilinx Alevo U200 and SDAccel 2018.2
Any suggestion on this error?

I want to know how you build it successfully?Because I build it failed,and the error is Unknown extension 'cl_intel_channels' - ignoring [-Wignored -pragmas];Unknown type name 'channel' .Then xilinx workers tells me that isn't a xilinx program,so the error occurs!Can you tell me how did you do?

@WenyeLiu and @cococener I was wondering if you could build it successfully for Xilinx device. I have been trying for quite some time to build it for U200 and no success yet.


Force flag not working

Using Puppet to create a Virtual Machine using the Vagrant infrastructure
Puppet-CPAN version 1.5.0
Workstation Host: Ubuntu/Mint; puppet 3.4.3; Perl 5.18.2
VM: Centos 7; puppet version 3.7.4; Perl version 5.16.3
*Puppet file:
class foo {
  include cpan
  # This is "chaining" - the sequence has to follow the arrows,
  # and if one fails, it all stops there...
  cpan { 'IRI' :
      ensure  => present,
      require => Class['oricpanmodules'],
    }->cpan { 'RDF::Trine' :
     ensure  => present,
      require => Package['raptor2']
    }->cpan {'RDF::Trine::Model' :
      ensure => present,
    }->cpan {'RDF::Trine::Parser' :
      ensure => present,
    }->cpan {'RDF::Trine::NamespaceMap' :
      ensure => present,
    }->cpan {'RDF::Trine::Serializer::Turtle' :
      ensure => present,
    }->cpan {'RDF::Trine::Serializer::RDFJSON' :
      ensure => present,
    }->cpan {'RDF::Trine::Serializer::RDFXML' :
      ensure => present,
    }->cpan { 'RDF::Lazy' :
      # Note: RDF::Lazy 0.081 fails tests under Perl 5.16 & later
      # Requires the --force flag
      ensure  => present,
      require => Class['::cpan'],
      force => true,
    }
}

The RDF::Lazy module is known to fail it's tests under Perl 5.16, however the code itself is fine.
If I ssh onto the Vagrant box, and install the module directly, it goes:
[vagrant@ori-devel ~]$ sudo cpan RDF::Lazy
CPAN: Storable loaded ok (v2.45)
.......
Failed 1/11 test programs. 6/100 subtests failed.
.......
Running make install
   make test had returned bad status, won't install without force

verses
[vagrant@ori-devel ~]$ sudo cpan -f RDF::Lazy
CPAN: Storable loaded ok (v2.45)
.........
 VOJ/RDF-Lazy-0.081.tar.gz
  /usr/bin/make install  -- OK

So this makes me think there's an issue with the cpan module and the force flag

closing this since it's a duplicate of #8


Failing tests

@joemoorhouse as part of #36 I'd like first to make sure I can run tests locally. I am encountering two issues:

I can't run the tests by following the CONTRIBUTING.md guide. More precisely, I do get past the pipenv environment creation, but nothing happens when I run the tox commands which the documentation points to, to run the tests. At any tox command I get this message

ROOT: No tox.ini or setup.cfg or pyproject.toml found, assuming empty tox.ini at /Users/emiletenezakis/devseed/os-climate-hazard

I can circumvent this and run pytest directly. More precisely, from the root of the repo pytest src/test. However many tests fail (see the summary of the log below. I can share more details if useful).

Do these tests run successfully on your side ? If so, can you share your set up if it is at all different from mine (or the one described in the docs).
=========================== short test summary info ============================
FAILED src/test/test_drought_indicators.py::test_spei_indicator - KeyError: 'OSC_S3_ACCESS_KEY_DEV'
FAILED src/test/test_drought_indicators.py::test_check_result - KeyError: 'OSC_S3_ACCESS_KEY_DEV'
FAILED src/test/test_drought_indicators.py::test_doc_store - ValueError: environment variable OSC_S3_ACCESS_KEY_DEV not present
FAILED src/test/test_tile_creation.py::test_xarray_writing - FileNotFoundError: No such file or directory: '<zarr.storage.DirectoryStore...
FAILED src/test/test_tile_creation.py::test_map_tiles_from_model - KeyError: 'inundation/wri/v2/inunriver_historical_000000000WATCH_1980'
FAILED src/test/test_tile_creation.py::test_convert_tiles - KeyError: 'OSC_S3_BUCKET'
FAILED src/test/test_wind_onboarding.py::test_wind_onboarding - rasterio.errors.RasterioIOError: /Users/emiletenezakis/devseed/os-climate-h...
============ 7 failed, 11 passed, 14 skipped, 40 warnings in 4.04s =============

Thanks !

Hi @emileten,
Certainly some of those are expected to fail without credentials set up: there are some tests which need S3 access; others are mocked. But as I mentioned, the hazard repo needs to be brought into line with the other repos and Linux Foundation best-practice (we don't want 'hazard' to have a double meaning :)) and think it's best to do that right now - since you will also need the CI/CD pipeline. I just discussed this with @ModeSevenIndustrialSolutions. I'll make the most pressing changes tomorrow/Friday this week:

Migrate from pipenv to pdm
Bring structure in line with LF standards, e.g. migrate test to 'tests'
Ensure tox passes and set up GitHub Action to run tox for PRs
I migrated another repo recently so will not take me long. I think Matt may then have some time next week to work on other aspects, but I think we'll already be in a reasonable state CI/CD-wise.

Does all that sound OK for you?
Thanks,
Joe

Thanks @joemoorhouse yes that makes sense!
In the meanwhile, is there any way for me to run these tests locally ? From the logs it looks like setting up my AWS credentials in a standard way with no particular permissions isn't going to work (the code seems to be looking for some specific environment vars for example).
No worries if not, but if that's easy I might as well do it

@joemoorhouse I think I am able to run the tests locally now. Question though, do any of these tests now actually download any data from the OS-C S3 buckets ? I see a lot of those that actually do I/O with S3 are skipped.

Hi @emileten,
No, currently the tests are all mocked - any which actually move data around are skipped for CI purposes. My assumption up until now has been that we don't want our CI tests to be reading and writing data to S3. But certainly one to revisit. There are some tests very hard to do without actually reading/writing something. @ModeSevenIndustrialSolutions, @MichaelTiemann, @redmikhail might be interested in that discussion.
Thanks,
Joe


Homework work

OK, so I found the source of my confusion - I was committing files in the wrong directory. I think I have it sorted now - at any rate, you should see session04 has 5 files so far, including kata_14_trigrams.

I need to include which lab I'm working on in my commit comments :-)

hmm -- lots if file changes -- I"ll try to see what's going on.

Wow -- this has kinda gone to heck. You have:
IntroPython2016/Session04
rather than it being in your own directory in students.
and a dir called:
students/UWPCE pvosper
and also:
students/pvosper
The goal here is to have everything of yours in:
students/pvosper
you can arrange it inside there however you want, but using teh sessions dirs makes sense.
You should be able to move things around with:
git mv Session04/some_file pvosper/Session04/some_file
Note that git doesn't track directories -- only files. if there is an empty dir, git will ignore it.


 Could probably "forget" them, but that seems to just be a work around.

What we ended up doing is leaving them active and not making them go unknown, but we made it so active errors can be closed.


Replace secrets with secret map for application

The application currently uses individual secrets. Replace with project secret map.

This is completed in code engine deployment.


heyheyhey

this repo is from a year ago and my life is a lot better now

@judytuna could you please review

wat

output:
cause the players gonna play, play, play, play, play
and the haters gonna hate, hate, hate, hate, hate
baby, I'm just gonna shake, shake, shake, shake, shake
shake it off, shake it off
heartbreakers gonna break, break, break, break, break
and the fakers gonna fake, fake, fake, fake, fake
baby I'm just gonna shake, shake, shake, shake, shake
shake it off, shake it off


Shorter random hex color

This is my favourite one-liner for random hex color, that is shorter than the previous one.
(I recorded a video about it, too)

Thanks @robinpokorny 👍


[FEAT]: Migrate Navigator to Functional Component & Migrate to RTK Query

Notes for Reviewers
This PR fixes #9985 #11493

[x] Migration of Class to Function Components
[x] Migration of dataFetch to RTK query
GET: /api/provider/capabilities,
GET: /api/system/version
[x] E2E test for navigator

Signed commits

[x] Yes, I signed my commits.

@senthil-athiban let's discuss this PR and Updates during the Meshery dev meeting call, if you would. Please add it as an agenda item to the meeting minutes.

@senthil-athiban, let's discuss the updates in this PR during the Meshery dev meeting call, if you would. Please add it as an agenda item to the meeting minutes.


Rearchitecture of Dashboard features

Summary of changes, manly found in the lib/rearchitecture folder:

created a new entry point of the app: main_dev.dart that skips the splash screen; to use this entry point, you can import the run configuration from run_configurations/dev.run.xml
implemented a feature based architecture, using Bloc as state management solution; all the new, or refactored code, will be found in the lib/rearchitecture folder; in a feature based architecture, we create a folder and add all related code to it inside that folder
refactored code and created features to be used in the "Dashboard" tab - with the exception of "Plasma" and "Latest Transactions" widgets that I considered to be part of another mother tab
used HydratedCubits, instead of the inhouse blocs; cubits are lightweight blocs that handle one single job; HydratedCubits cache their last state and restores it
I've added the https://pub.dev/packages/very_good_analysis package for linter rules; it's far more stricter than the previous solution; I haven't solved all the warnings and hints in the app, because that would make my PR too wide in terms of scope
I've created a new version of CardScaffold, one that does not listens to a stream anymore; this new widget also uses the new app themes that are more closer to the default Material Design used by Flutter, especially when it comes to the text styles: I preferred to used the original ones, instead of overwriting them
fixed the switch from the back of the new cards - when active, the thumb was disappearing
fixed the feature of hiding, unhiding the front widget of card (the password field was not being dismissed properly, and the switch was showing that the discreet mode was not active, but front widget was still hidden)
started using localized strings, so it will be easier to translate the app later
added unit tests for the cubits used

The high amount of changes in the folders outside lib/rearchitecture are due to running dart fix --apply, that fixed warnings from the new linter rules. One new rule that I wanted to use specifically, and that generated a lot of changes, is the one that requests strict types when declaring a local variable. I've added comments for this choice in the analysis_options.yaml file

Not sure why exactly, but the default app icon is only used in the task bar.

Not sure why exactly, but the default app icon is only used in the task bar. The app icon and system tray are restored.

I build the app using flutter build windows --release and all the three icons are the Syrius icon.
I also fixed the build on macOS and Linux. There was a problem with building some paths for some dll or .so files.

Icon has been reset to default flutter icon. See screenshot.
Header font size of new scaffold card is bigger causing a discrepancy between old and new cards. See screenshot.
The Pillar Rewards values in the vertical column do not fit. See screenshot.
Metadata information is not being build. See comments.
App Links support has been removed.

I know about the misalignment of the two cards. Its intended because I haven't refactored the Plasma card from the Dashboard tab, I want to do it when I refactor the whole plasma tab; after I finish the Plasma tab, everything will be even on Dashboard as well. But I can make it sooner if it's a deal breaker.
I changed how the Y values are generated on charts. And added more space for the Y values.
I restored the generation of metadata.
Enabled full app_links support: the Windows app can now be opened by an URL using the scheme syrius://. I can go to the bridge and open the app from it in order to test it in combination with the WC feature.

I know about the misalignment of the two cards. Its intended because I haven't refactored the Plasma card from the Dashboard tab, I want to do it when I refactor the whole plasma tab; after I finish the Plasma tab, everything will be even on Dashboard as well. But I can make it sooner if it's a deal breaker.

You're right, this will be solved once all widgets have been refactored. Let's leave this as it is for now.

Not sure why exactly, but the default app icon is only used in the task bar. The app icon and system tray are restored.

I build the app using flutter build windows --release and all the three icons are the Syrius icon.
I also fixed the build on macOS and Linux. There was a problem with building some paths for some dll or .so files.

Turns out to be a caching issue on my side. It's working now.

I want to leave a comment that explains the part of code that finds the path for some .dll and .so files and outputs a copy of those in the application folder. This process happens for each desktop build: Windows, Linux and macOS. The app needs some libraries to function, like the libpow library. The app looks for those files in multiple locations, such as the root folder of the application. But they are original found only in the SDK, as is the case of the libpow library.
So, for each desktop build, there is a some code that looks up the path of the znn_sdk_dart library in the local cache of the machine. And sincer we already know where the libpow dll is located inside the znn_sdk_dart, we can append the two paths and install the dll inside the application folder.
The issue is that originally, the znn_sdk_dart was searched for inside the dart_tool/package_config.json file. It looks up the path by going through the file one line at a time. The catch is that the package_config.json in the Dashboard-PR is generated now as one long line. I don't know what caused the change from generating a multi-line file to a single line file.
So I decided to look for the paths inside the dart_tool/package_config_subset that seemed to be generated in a consistent way.

Found an issue with the rendering of the AZ project/phase list. A part of the project and phase list is blanked out and blocks further scrolling. Seems like the widgets crash. See screenshots.

Found an issue with the rendering of the AZ project/phase list. A part of the project and phase list is blanked out and blocks further scrolling. Seems like the widgets crash. See screenshots.

Done.


Use Sparkle Swift package

Sparkle provides a Swift package. Is there a reason to check in the complete framework to the repository instead of using the package? If yes feel free to close the PR as this is just something I noticed :).
Note that I am not entirely sure this branch works correctly (as I don't know how to test it). However I follow all the steps from the Sparkle 2.* documentation.

Thanks for submitting, I was reluctant to migrate because I would need to find a way to test this properly to make sure the autoupdate keeps working. I'll give it a shot later.

Thank you, merged in https://github.com/p0deje/Maccy/commit/a0ee02e00db1fb4939d8ed88a8a8a2fada8b7269


decoupling model configs from classify.py

New Feature Summary
#25 made first implementation of a MMIF wrapper of the model we trained. One of the implementational choice (given time constraint at the time) was hard-coding model configuration into classify.py. I request a new feature that basically decouple the model configuration to another generic file (could be .py, .json. or .yaml) thats' imported into classify.py and in turn into app.py if necessary.
Moreover, if we can generate such a file from a result report file (such as this, note that the file contents is somewhat outdated now, and the latest train.py requires (and records) more configuration k-v)
Related
No response
Alternatives
No response
Additional context
No response

I think we can close this once the last updates to saving out and loading configuration files are done.


Update Wikidata SPARQL converter

Update the converter to match the new ThingTalk syntax we added in the past year.
The old code was also problematic. Most of the issues are fixed. Or operator is still broken, we will fix it later.

Pull Request Test Coverage Report for Build 1065

33 of 38 (86.84%)  changed or added relevant lines in 1 file are covered.
37 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.4%) to 80.086%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/wikidata_sparql.js
33
38
86.84%

Files with Coverage Reduction
New Missed Lines
%

lib/ast/function_def.js
1
79.49%

lib/compiler/ast-to-ops.js
1
79.32%

lib/typecheck.js
1
87.04%

lib/runtime/formatter.js
14
67.74%

lib/wikidata_sparql.js
20
79.49%

Totals

Change from base Build 1061:
-0.4%

Covered Lines:
8807

Relevant Lines:
10584

💛  - Coveralls

I think this looks good.
I'm not sure about the part where you say "We don't know if a value is represented as a string or an array". Wouldn't we know that from the type?

do you mean this one: "we don't know if a value is represented as a string or an entity in Wikidata"
Lots of things we considered String is also an entity in wikidata (like given name, last name), so we cannot decide based on thingtalk type.

Yes I meant string or entity (brain fart, probably).
Time to add a new annotation with the wikidata type? We did that for schema.org (even though we didn't really use it)

Mostly I ask because it looks like you're generating some really inefficient SPARQL and I worry things will timeout more often than not.

Mostly I ask because it looks like you're generating some really inefficient SPARQL and I worry things will timeout more often than not.

I tested that, in fact there is no significant difference in terms of time. but yeah, we should probably include type information - it's going to be tricky though because the same property can be used for different types of values (even for the same domain). Anyway, it's going to be part of the project to dump the entire wikdiata.


⚠ Bofrost.at has degraded performance

In b269fa7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1292 ms

Resolved: Bofrost.at performance has improved in cca81c0 after 6 minutes.


Add DownloadContentsWithMeta to receive RepositoryContent

Added an additional method and tests for callers to receive a
RepositoryContent when downloading a large file from a GitHub
repository. This simplifies future operations (e.g. UpdateFile)
involving the requested file.
Fixes: #1809.

@wesleimp Thanks for the approval. Unfortunately, I just accidentally hit Re-request review. My bad. 🙈

Thank you, @wesleimp !
Merging.


PyDict should expose a wrapper over PyDict_GetItemWithError

Currently PyDict::get_item wraps PyDict_GetItem and returns an Option::None when the key is missing or an exception occurs. It makes code incapable to differentiate between the two scenarios and code like this likely incorrect:
dict.get_item("key").ok_or_else(|| KeyError::py_err("key"))?;

Marking for part of possible collections improvements in 0.15


Add ESRI streets and imagery to demo app layer list

@mraross commented on Thu Nov 02 2017
Sandbox demo available at:
https://gogs.data.gov.bc.ca/leolou/playground/src/master/esri-map-demo.html
Add ESRI streets immediately following MapBox Streets and ESRI imagery immediately following MapBox Satellite

Up in delivery now: https://cmhodgson.github.io/ols-devkit/ols-demo/index.html


fix(jsx/dom): fix dom rendering bugs for fragment.

The code “Fragment is continuous across components” was not updating the DOM correctly, so it was fixed.
For example, the following
https://github.com/honojs/hono/compare/main...usualoma:hono:fix-consecutive-fragment?expand=1#diff-8f050239e20450fd8425feb7efbda60df851ebbc32bec8139d6d9ad1b53a7bc0R1123-R1145
The author should do the following, if applicable

[x] Add tests
[x] Run tests
[x] bun run format:fix && bun run lint:fix to format the code

@usualoma
Thanks!


Adjust Thai "L" format

Adjust Thai localized short date format to read day/month/year (moment/moment#3692).
@sirn, 👍 or 👎?

The test failures appear to be unrelated and were previously reported in #3691.

:+1: Looks good to me.

:+1: Looks good to me.

Yeah, we need to figure out what's up with the build server. That aside, @ichernev this looks good.

Closing to re-open and start the build again. #hack

@maggiepint I'm not sure if its just me, but you can go in travis and click a button to reset the build if it looks fishy. But opening and closing is the poor-mans-way that works too :)

Merged in 9b738aa4aa26dd6b359c68da7686b6352db972af


Tries to set breakpoint at main, although setting stopAtEntry is False

Hi,
I use the c_cpp extension in VScode with a large c++ project.
One issue is, that starting the debugger session takes more than one minute.
I activated the logging to see what is happening. It came out, that there is a log entry saying:
1: (7051) <-1009-break-insert -f main
Then the log prints all methods within my project with the name main.
Finally the log contains the time it took to search all those methods:
--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (47494) 1009: elapsed time 40443\n"},"seq":112}
The thing about this: I disabled the stopAtEntry in the launch settings of my project
{
"name": "(GDB) mybinary (logging)",
"type": "cppdbg",
"program": "/path/to/mybinary.exe",
"request": "launch",
"cwd": "/path/to",
"stopAtEntry": false,
"linux": {},
"MIMode": "gdb",
"miDebuggerPath": "/u1/debugger/gdb-13.2.0/bin/gdb",
"logging": {
  "engineLogging": true,
  "moduleLoad": true,
  "trace": true,
  "traceResponse": true,
}

I think that this is an error not using the setting.
Looking at the source code, there might be a something wrong in:
MIEngine\src\MIDebugEngine\Engine.Impl\DebuggedProcess.cs:821
Best regards,
Frank

Is there anyone who can acknowledge this issue?


docs: change pypi badges url from pypi.com to pypi.org

https://Pypi.org is the official web for python packages, pypi.com dont work

Thanks!


Create demo video

First non-narrated attempt can be found here: trace-explorer-demo1.mov
https://github.com/lnsp/trace-explorer/assets/3391295/eae0c25c-ed27-486f-85d4-851912c9a6ee
I'll redo it as soon as the #2 is implemented for the comparison panel.

@durner
https://github.com/lnsp/trace-explorer/assets/3391295/d61e9cdc-6e99-4a4d-ad9f-3c6d37564e61


Is IIS required for .net core application, why not just use kestrel? Can someone state pros vs cons of both please?

[Enter feedback here]

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

ID: 888b22d0-7261-c6fd-e4b3-07a4c1f66d06
Version Independent ID: ddfcec03-a396-8851-49cd-629b9c7edc8a
Content: What OS to target with .NET containers
Content Source: docs/architecture/microservices/net-core-net-framework-containers/net-container-os-targets.md
Product: dotnet-architecture
Technology: microservices
GitHub Login: @nishanil
Microsoft Alias: nanil

Hi @CSG-richard, thank you for reaching out.
No, you need to use the kestrel Web Server to host .NET Core/.NET 5 applications. To know more about the kestrel, you can refer Web server implementations in ASP.NET Core
Hope this helps !

Just to clarify the above statement further, it's not mandatory to use IIS to host the ASP.NET Core apps. You can use the Kestral web server as well.  For more details, please refer Host and deploy ASP.NET Core

Considering the original question has been answered, I am closing this issue as of now. Please feel free to reopen, if needed. Thank you.


it seems 'adding -1' is more accurate for flipping

Thank you for the contribution. Did you notice any difference by using -1 for flipping?

Thank you for the contribution. Did you notice any difference by using -1 for flipping?

when p_x=0, then the flipped position should be (w-0-1)=w-1, instead of w(it is out of the range).

when p_x=0, then the flipped position should be (w-0-1)=w-1, instead of w(it is out of the range).


Add IWebHostBuilder.UseKestrel(options) overload to configure Kestrel

Copied from #713:
var host = new WebHostBuilder()
    .UseKestrel(options =>
     {
         options.NoDelay = true;
         options.ThreadCount = 4;
         options.UseHttps(...);
     })
    .UseStartup<StartupHelloWorld>()
    .Build();

host.Run();

We should also remove these as a result of this:
https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNetCore.Server.Kestrel.Https/HttpsApplicationBuilderExtensions.cs
It clears up the fact that these aren't actually pieces of middleware but server configuration.

YES PLS RIGHT NOW LOVE IT :shipit:

I did a test implementation and there are some problems around extension methods that require resolved services to configure. UseConnectionLogging() requires an ILoggerFactoryand UseHttps() and requires the base path to the x509cert.

Kestrel

Add KestrelServerOptions and remove KestrelServerInformation
Remove KestrelServerInformation from server features
Add IServiceProvider to KestrelServerOptions
Change UseKestrel() to add the IServerFactory to the container directly
Add UseKestrel(Action<KestrelServerOptions>) which adds
Change connection filter extension methods to extension methods on KestrelServerOptions


Cilium pods with well-known identities get stuck in "restoring" state if etcd is down

Saw Cilium restore logic get stuck while restoring a pod with a well-known identity:
github.com/cilium/cilium/pkg/ipcache.(*IPIdentityWatcher).waitForInitialSync(...)
        /go/src/github.com/cilium/cilium/pkg/ipcache/kvstore.go:388
github.com/cilium/cilium/pkg/ipcache.WaitForKVStoreSync(...)
        /go/src/github.com/cilium/cilium/pkg/ipcache/kvstore.go:412
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).restoreIdentity(0xc00044d500, 0xc0004deca0, 0x4432ca)
        /go/src/github.com/cilium/cilium/pkg/endpoint/restore.go:333 +0x9cf
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).RegenerateAfterRestore(0xc00044d500, 0x0, 0x0)
        /go/src/github.com/cilium/cilium/pkg/endpoint/restore.go:230 +0x45
github.com/cilium/cilium/daemon/cmd.(*Daemon).regenerateRestoredEndpoints.func1(0xc00044d500, 0xc000af8f50)
        /go/src/github.com/cilium/cilium/daemon/cmd/state.go:292 +0x2b
created by github.com/cilium/cilium/daemon/cmd.(*Daemon).regenerateRestoredEndpoints
        /go/src/github.com/cilium/cilium/daemon/cmd/state.go:291 +0x6d4

Restoring such a pod should not wait on etcd to resolve the identity, because the identity is well-known.

Won't fix.


Throw some error when use deploy contract

Describe the bug

cargo install ckb-capsule
capsule new my-demo
Change entry.rs

10 - 14 lines
use ckb_std::{
    debug,
    high_level::{load_script},
    ckb_types::{bytes::Bytes, prelude::*},
};

30-32 lines

    // let tx_hash = load_tx_hash()?;
    // debug!("tx hash is {:?}", tx_hash);

capsule build --release
deploy

const demo = fs.readFileSync('./my-demo/build/release/my-demo')

function bytesToHex(bytes) {
  let res = "0x";
  for (let i = 0; i < bytes.length; i++) {
    res += bytes[i].toString(16).padStart(2, "0");
  }
  return res;
}

const data = bytesToHex(demo)
const contractScript = {
      "capacity": '2630200000000',
      "lock":{
          "args":"0xe5f98b05a4aefc6984acea200402ea74b2a389a2",
          "codeHash":"0x9bd7e06f3ecf4be0f2fcd2188b23f1b9fcc88e5d4b65a8637b17723bbda3cce8",
          "hashType":"type"
      },
      "data": data
  }

https://pudge.explorer.nervos.org/transaction/0x7ffd3902e758228373c15c37a8bc8fea6745c3e10fc9d24eadc1a13f28924f39
Ouput[0] is the deployed contract.
6. use contract
This is signed tx, I use the deployed contract on Ouput[1].type
https://wetransfer.com/downloads/5c40df6b6b659fa1e836b06b9c27706420220830093317/7e52431b24fe0927e0ce18278cce7aea20220830093331/00a6e0?utm_campaign=WT_email_tracking&utm_content=general&utm_medium=download_button&utm_source=notify_recipient_email
Screenshots
If applicable, add screenshots to help explain your problem. (The command and the output)
Error screenshot

Additional context
Please post the following informations:

Output of capsule --version: 0.8.0
Output of ckb-cli --version: I deploy tx by Neuron.
Rerun your command with  RUST_BACKTRACE=1 RUST_LOG=capsule=trace environment, then post the output as a file.

I should use type or data1 in the type script when calling the contract. Becasue we should use VM version 1


NPL(node Port Local) doesn't works for Multi-Port Services objects

Describe the bug
For the service object with multiple ports, the NPL pod annotations are created for one of the port. Not for the all the ports
To Reproduce
step1 : created SVC object with Multiple Ports
apiVersion: v1
kind: Service
metadata:
  annotations:
    nodeportlocal.antrea.io/enabled: "true"
  labels:
    app: nginx
  name: svc-nginx
spec:
  ports:
  - name: web
    port: 80
    protocol: TCP
    targetPort: 8080
  - name: web-sec
    port: 443
    protocol: TCP
    targetPort: 8081
  selector:
    app: nginx

root@tvk-k8s119-ant-master-1:~# kubectl get svc -o wide
NAME         TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE    SELECTOR
svc-nginx    ClusterIP   <IP_ADDRESS>   <none>        80/TCP,443/TCP   101m   app=nginx

step2 : observed that NPL annotations are created  only for the targetPort 8080 and it doesn't got created for the targetPorts/PodPorts 8081. As per the Expectation the NPL annotations should be added all the targetPorts/PodPorts.
root@tvk-k8s119-ant-master-1:~# kubectl get pods -o=jsonpath="{range .items[*]}{'\n'}{.metadata.name}{':\t'}{.metadata.annotations}{end}"

nginx-deployment-b68c6d696-frrfj:	{"nodeportlocal.antrea.io":"[{\"podPort\":8080,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":50001}]"}
nginx-deployment-b68c6d696-qb2j4:	{"nodeportlocal.antrea.io":"[{\"podPort\":8080,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":50000}]"}
nginx-deployment-b68c6d696-qtzm7:	{"nodeportlocal.antrea.io":"[{\"podPort\":8080,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":50002}]"}
nginx-deployment-b68c6d696-xtg5t:	{"nodeportlocal.antrea.io":"[{\"podPort\":8080,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":50000}]"}root@tvk-k8s119-ant-master-1:~#

Expected
As per the Expectation the NPL annotations should be added for the all the targetPorts/Pod Ports.
Versions:
Please provide the following information:

Antrea version (v0.13.0).
Kubernetes version (1.19)

Do the Pods selected by your Service have 2 container ports (8080 and 8081)? Could you share the yaml for your Deployment?
I am not able to reproduce with the following yaml:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-nginx
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 3
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: my-nginx
        image: nginx
        ports:
        - containerPort: 8080
        - containerPort: 8081
---
apiVersion: v1
kind: Service
metadata:
  annotations:
    nodeportlocal.antrea.io/enabled: "true"
  labels:
    app: nginx
  name: svc-nginx
spec:
  ports:
  - name: web
    port: 80
    protocol: TCP
    targetPort: 8080
  - name: web-sec
    port: 443
    protocol: TCP
    targetPort: 8081
  selector:
    app: nginx

$ kubectl get pods -o=jsonpath="{range .items[*]}{'\n'}{.metadata.name}{':\t'}{.metadata.annotations}{end}"

my-nginx-9494bb7df-m4txm:	{"nodeportlocal.antrea.io":"[{\"podPort\":8080,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":40004},{\"podPort\":8081,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":40005}]"}
my-nginx-9494bb7df-pxftm:	{"nodeportlocal.antrea.io":"[{\"podPort\":8080,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":40000},{\"podPort\":8081,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":40001}]"}
my-nginx-9494bb7df-xscwc:	{"nodeportlocal.antrea.io":"[{\"podPort\":8080,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":40002},{\"podPort\":8081,\"nodeIP\":\"<IP_ADDRESS>\",\"nodePort\":40003}]"}

Actually My container spec has only port 8080 exposed, once i added the port 8081, the NPL annotations are added as expected
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 4
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: <IP_ADDRESS>:5001/service-chain-apps
        ports:
        - containerPort: 8080

Just one doubt here, even though the container  port 8081  is not mentioned in the POD container spec, Nothing stops us from creating SVC object with the targetPort 8081, By default containers ports are exposed and it works fine. Can we create the NPL annotations for the POD based on the svc object Target Ports

@tamilhce I tend to agree with you. I am not sure why the current implementation is using the (optional) containerPorts from the Pod spec, as opposed to the targetPorts from the Service spec. It may be because of the initial NPL implementation in Antrea: NPL had to be enabled for each Pod using an annotation, as opposed to via an annotation on the Service selecting the Pods.
I would be open to making this change, but I think we need to hear from the folks who designed & implemented the NPL feature: @sudswasavi @monotosh-avi @hemantavi @chauhanshubham

@antoninbas @tamilhce
We had explored few options while designing NPL (https://docs.google.com/document/d/1SoAKBvbbt2QMnGmt53E8ja0ZxCv_T4r1zLVnMzpykTg), one option was creating a new CRD - NPLEndpointSlice which would follow the default Endpoint slice implementation and use target port for service. The other option - which we implemented, was annotating Pod with Container Ports of the Pod. In case of Endpoint or EndpointSlice, the objects are created per Service, so the target port fits perfectly. But the Pod annotation is tied to a Pod, if a Pod is selected by multiple Services, it can get complicated.
If we stick with current implementation, the user have to use ContainerPorts in the Pod Spec, which should be possible as the app developer should know about the Ports used by the application.
With the target port based approach, one option is to ignore Container Ports and select a union of all target ports from all Services selecting a Pod, and then adding that in Pod Annotation. But NPLEndpointSlice is probably more suited for target port based rule provisioning.

With the target port based approach, one option is to ignore Container Ports and select a union of all target ports from all Services selecting a Pod, and then adding that in Pod Annotation. But NPLEndpointSlice is probably more suited for target port based rule provisioning.

This seems like the most sensible solution to me. I'm not sure why you think this solution is more complicated. In the current implementation, whenever we process a Pod, we already iterate through all Services:
https://github.com/vmware-tanzu/antrea/blob/347de8266882f92dea4654be980b27dedda63881/pkg/agent/nodeportlocal/k8s/npl_controller.go#L263-L281
It would be easy to have this function return the list of NPL-enabled Services selecting the Pod, which can then be used to compute the union of all target ports, as you suggested. Why do you think things would be more complicated with this solution? Would it be more complicated for users trying to use NPL, from an implementation perspective, or for external LBs trying to consume the mapping information?
I think the Service target port approach is better from a usability perspective. The discussion on Pod annotation vs NPLEndpointSlice is not as much about usability, and more about integrating with LBs. If necessary, we could include more information in the NPL Pod annotation, e.g. for each mapped port we could include the list of Services consuming the port.

@antoninbas I was concerned about the implementation in case we need to keep track of a target port being used by multiple services, but looks like it won't involve extensive changes. In any case, we should be able to implement this.
About the usability improvement, I think we don't need the service name in the Pod annotation, because in that case the annotation can get big, if a Pod is being referred by a large number of services. Because of this issue and as Annotation is unstructured, I thought NPLEndpointSlice becomes useful, where we could define our own spec.
For now, we can include the target Port in Pod annotation without the service name, the external LB should be able to derive the mapping by looking at the Service and Pod Annotation.


[PRFC] - add support for refreshKeys

Hey, I just made a Pull Request!
This is a potential implementation of the https://github.com/backstage/backstage/issues/12155 Nothing set in stone, would like some feedback on it!
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Not sure if I should comment on the RFC or the PRFC might be good to combine them next time 😅
Yeah I agree, I'll definietly combine them next time, it is a littlebit awkward this way. :/

@jhaals With this my intention was to understand the problem space and try to explore the way it can be done, if you think in a general sense it looks okey, I'd move forward with adding tests, and making sure it passes the ci and move it to a regular PR.

@Rugvip Addressed the comments, opted to add the emit to the resolvers as the easiest solution right now. I can see some tests failed, but they pass locally, can it be that it is flaky?

Shall we :shipit: as is and leave the triggering of refreshes as a followup?

I'd say so let's merge this one and I'll create a follow-up issue where we can discuss the different approaches for triggering the refreshes. I can explore both and create some PRs with the different approaches to discuss which fits better.

🎉


allowing get_env() to run without the DEFAULT argument

Related to https://github.com/gruntwork-io/terragrunt/issues/391
This PR allows the get_env() helper to work with a single argument such as in get_env("ENV_VAR_NAME")

existing test cases pass
2 new test cases are provided to test the new expectations
updated README.md

...
I tested the new implementation in the following UC:
    extra_arguments "password" {
      commands = ["${get_terraform_commands_that_need_vars()}"]
      arguments = ["-var", "'password=${get_env("DB_PWD")}'"]
    }

And it works like a charm
But beware not to forget the single quotes surrounding the var definition as in -var 'foo=bar' or in "'password=${get_env("DB_PWD")}'".
for some reason terraform plan [..] -var some_var= will assign an empty string to some_var instead of not setting some_var, when terraform plan [..] -var 'some_var=' works OK

and here are test results
test_results.txt

Is this still in progress, or stuck? Would love to see this feature land.

@lorengordon : i'll try summing up the above discussion and resume the work on it soon.
What behavior would you expect from an end-user perspective?

I'd say something like this:
export FOO=foo

get_env("FOO", "bar")
# returns "foo"

get_env("FOO")
# returns "foo"

unset FOO

get_env("FOO", "bar")
# returns "bar"

get_env("FOO")
# raises exception and exits non-zero

PR not updated for over a year, closing


Implicit type conversion in arithmetic

See: #353

Ok so the problem here is:

There was a really dumb bug in the type bindings.
Fixing it causes basically all compilation to fail, because:

In the AbstractionPass, arithmetic operators are transformed into typeclass method calls, e.g. a*b becomes trappingMul(a,b).
Arithmetic operations are supposed to have relaxed rules when constants are involved. That is: something like i + 1 should work regardless of what kind of integer type i is (signedness considerations aside).
But the relaxed rules don't apply (obviously) to method calls: if you have i: Int8 and trappingAdd(i, 10), the compiler sees:

The method trappingAdd(a: T, b: T): T
The variable i: Int8
The constant 10: Int32
[After fixing the bug in the type bindings] it sees you're trying to bind T => Int8 and T => Int32, and dies.

The solution:

Fix AbstractionPass to not transform arithmetic operators to method calls.
Implement the relaxed type checking rules in the typing pass (where we know types), then transform arithmetic operators to method calls, and then typecheck those.
Fix any subsequent issues that pop up.


Cannot build on OpenBSD.

Hi,
Cannot build micro on OpenBSD 7.0 ending with errors:
# github.com/zyedidia/pty
../../.go/pkg/mod/github.com/zyedidia/pty@v1.1.15/pty_openbsd_amd64.go:27:10: undefined: ptmget
../../.go/pkg/mod/github.com/zyedidia/pty@v1.1.15/pty_openbsd_amd64.go:28:34: undefined: ioctl_PTMGET
*** Error 2 in /home/tracnac/Project/micro (Makefile:19 'build-quick')

Don't go deeper but there's something wrong with your fork of github.com/creack/pty
Thanks Yvan
Specifications
OpenBSD 7.0 amd64
Commit hash: N/A
OS: OpenBSD 7.0
Terminal: st
Ouput of the failed compilation:
{12:23} tracnac@ttyp3 [Project] $ git clone https://github.com/zyedidia/micro.git
Cloning into 'micro'...
remote: Enumerating objects: 17758, done.
remote: Counting objects: 100% (586/586), done.
remote: Compressing objects: 100% (258/258), done.
remote: Total 17758 (delta 364), reused 477 (delta 320), pack-reused 17172
Receiving objects: 100% (17758/17758), 12.35 MiB | 4.27 MiB/s, done.
Resolving deltas: 100% (12016/12016), done.
{12:24} tracnac@ttyp3 [Project] $ cd micro/
{12:24} tracnac@ttyp3 [micro] $ ls
LICENSE               Makefile              assets/               data/                 go.sum                pkg/                  snapcraft.yaml
LICENSE-THIRD-PARTY   README.md             cmd/                  go.mod                internal/             runtime/              tools/
{12:24} tracnac@ttyp3 [micro] $ make
GOOS= GOARCH= go generate ./runtime
go: downloading gopkg.in/yaml.v2 v2.2.8
go build -trimpath -ldflags "-s -w -X github.com/zyedidia/micro/v2/internal/util.Version= -X github.com/zyedidia/micro/v2/internal/util.CommitHash= -X 'github.com/zyedidia/micro/v2/internal/util.CompileDate=' " ./cmd/micro
go: downloading github.com/go-errors/errors v1.0.1
go: downloading github.com/mattn/go-isatty v0.0.11
go: downloading github.com/yuin/gopher-lua v0.0.0-20191220021717-ab39c6098bdb
go: downloading github.com/zyedidia/tcell/v2 v2.0.8
go: downloading github.com/layeh/gopher-luar v1.0.7
go: downloading github.com/zyedidia/go-shellquote v0.0.0-20200613203517-eccd813c0655
go: downloading github.com/zyedidia/json5 v0.0.0-20200102012142-2da050b1a98d
go: downloading github.com/zyedidia/terminal v0.0.0-20180726154117-533c623e2415
go: downloading github.com/sergi/go-diff v1.1.0
go: downloading golang.org/x/text v0.3.2
go: downloading github.com/zyedidia/clipboard v1.0.3
go: downloading github.com/blang/semver v3.5.1+incompatible
go: downloading github.com/mitchellh/go-homedir v1.1.0
go: downloading github.com/zyedidia/glob v0.0.0-20170209203856-dd4023a66dc3
go: downloading github.com/zyedidia/go-runewidth v0.0.12
go: downloading github.com/dustin/go-humanize v1.0.0
go: downloading github.com/gdamore/encoding v1.0.0
go: downloading github.com/lucasb-eyer/go-colorful v1.0.3
go: downloading github.com/zyedidia/pty v1.1.15
go: downloading github.com/rivo/uniseg v0.1.0
go: downloading github.com/xo/terminfo v0.0.0-20200218205459-454e5b68f9e8
# github.com/zyedidia/pty
../../.go/pkg/mod/github.com/zyedidia/pty@v1.1.15/pty_openbsd_amd64.go:27:10: undefined: ptmget
../../.go/pkg/mod/github.com/zyedidia/pty@v1.1.15/pty_openbsd_amd64.go:28:34: undefined: ioctl_PTMGET
*** Error 2 in /home/tracnac/Project/micro (Makefile:19 'build-quick')
{12:25} tracnac@ttyp3 [micro] $

I can reproduce the problem outside micro...
{12:55} tracnac@ttyp3 [debug] $ cat go.mod
module main

go 1.17

require github.com/creack/pty v1.1.17

replace github.com/creack/pty => github.com/zyedidia/pty v1.1.15

{12:54} tracnac@ttyp3 [debug] $ cat debug.go
package main

import (
	"io"
	"os"
	"os/exec"

	"github.com/creack/pty"
)

func main() {
	c := exec.Command("grep", "bar")
	f, err := pty.Start(c)
	if err != nil {
		panic(err)
	}

	go func() {
		f.Write([]byte("foo\n"))
		f.Write([]byte("bar\n"))
		f.Write([]byte("baz\n"))
		f.Write([]byte{4}) // EOT
	}()
	io.Copy(os.Stdout, f)
}
{12:54} tracnac@ttyp3 [debug] $ go run debug.go
# github.com/creack/pty
../../.go/pkg/mod/github.com/zyedidia/pty@v1.1.15/pty_openbsd_amd64.go:27:10: undefined: ptmget
../../.go/pkg/mod/github.com/zyedidia/pty@v1.1.15/pty_openbsd_amd64.go:28:34: undefined: ioctl_PTMGET
{12:54} tracnac@ttyp3 [debug] $

Working fine with the original mod...
{12:57} tracnac@ttyp3 [debug] $ go mod tidy
{12:57} tracnac@ttyp3 [debug] $ go run debug.go
foo
bar
baz
bar
{12:57} tracnac@ttyp3 [debug] $ cat go.mod
module main

go 1.17

require github.com/creack/pty v1.1.17
{12:58} tracnac@ttyp3 [debug] $

Humm ok easy fix...
Just clone the original repo: https://github.com/creack/pty
And reapply the change from run.go (Basically copy the run.go file  from github.com/zyedidia/pty to the original repo)
Point the repo to the original, build ok.
replace github.com/zyedidia/pty => ../ptycreack

@zyedidia Maybe you need to reclone the original repo or merge latest change from it.
Thanks Yvan

Thanks for reporting this.


Prevent candid space bombs

The Candid spec has been updated (https://togithub.com/dfinity/candid/issues/434) and now the test suite now longer passes (https://github.com/dfinity/motoko/pull/4013). Someone needs to update Motoko.
This needs a new counter during decoding. We don't actually need a predicate for “zero size type”, it should suffice (and be simpler) to notice when the buffer pointer did not get moved.
This needs to happen also in the skipping code in the rust rts, I believe. I ought to double check if the spec is clear about that and whether the test suite covers both variants (space bomb in ignored and not-ignored parts of the message.)
Candid spec compliance is presumably kinda important, if only because it looks odd if not; so maybe worth putting on the internal JIRA?

The test suite covers both the skipped case and non-skipped case. The spec says to check the length on the wire, not on the expected type.

Sorry, I never noticed this issue. Will take a look soonish.


login with 1.6.0 wrong redirection

In the laravel project im working we update with composer from "apereo/phpcas": "1.5.0" to 1.6.0
them when try to access to cas login the url it redirects stay on http//example.com/mylaraveldir/cas/login and show a blank page
but when I turn it back to 1.5.0 it show me the right url somehing like:
https://example.com/cas/login?service=http//example.com/mylaraveldir/cas/login
and the usual cas login form, is there any change that I have to do in the configuration with the new version or is something wrong ?

If you turn on PHP error log you should be able to see more information. However, there is a breaking change meant to address a security issue in 1.6.0: https://github.com/apereo/phpCAS/blob/master/docs/Upgrading

Please feel free to reopen if you have further information.


Unable to download files using Cordova

When trying to download files under a compiled Meteor Cordova app, I'm using a "fetch" for further processing.  I'm getting a "TypeError: Failed to fetch".  Any ideas?

Hello @SeraVault ,
Post the code you're using.
And update thread following our issue template.

Closed due to silence at issue owner end.
Feel free to reopen it in case if the issue still persists on your end.


Succeeding pythonPackages opencv & netcdf4 not in binary cache

Issue description
The two packages pythonPackages.opencv and pythonPackages.netcdf4 build fine on my NixOS virtual machine. But hydra does not provide any binaries for these packages.
For netcdf4 I can find a page which states: "it was removed from the jobset": http://hydra.nixos.org/job/nixpkgs/trunk/python27Packages.netcdf4.x86_64-linux
And for opencv I cannot even find the pythonPackages one: http://hydra.nixos.org/search?query=opencv
As I rely on the binary cache on my machine this is a bit of a bummer for me. (Our admin did only provide me with a /nix symlink on my main machine instead of a mount and thus all local builds fail due to this impurity.)
What is the reason that those packages don't show up on hydra? How do jobs get on the http://hydra.nixos.org/jobset/nixpkgs/trunk jobset?
Steps to reproduce
All the following commands start a successful build instead of fetching from cache.
nix-shell -p python27Packages.opencv
nix-shell -p python35Packages.opencv
nix-shell -p python27Packages.opencv3
nix-shell -p python35Packages.opencv3
nix-shell -p python27Packages.netcdf4
nix-shell -p python35Packages.netcdf4

Technical details

System: openSUSE 13.2
Nix version: nix-env (Nix) 1.11.4
Nixpkgs version: "17.03pre96125.a6f392a"

Hydra jobs are based on the release*.nix files in https://github.com/NixOS/nixpkgs/tree/master/pkgs/top-level and
https://github.com/NixOS/nixpkgs/tree/master/nixos
For example, nixpkgs/trunk uses pkgs/top-level/release.nix as can be seen at http://hydra.nixos.org/jobset/nixpkgs/trunk#tabs-configuration.
The larger package sets, like the Python package set, and Haskell package set, are by default not build. Only packages that are depended on will be build.

(Also, how are you going to work with the packages then? nix-shell will work because it won't write to the store, but you cannot use python.withPackages unless you have the env built already on the other machine.)

Ok. Currently I'm quite happy with only the nix-shell variant as most of the important compiled packages worked out of the box (numpy, pandas, ...). However it's unfortunate that the python bindings for the compiled packages opencv, netcdf, gdal, etc. are not on hydra.

Ok. So as I understand they are not built by default, because of hardware limitations: https://github.com/NixOS/nixpkgs/commit/ccd1029f58a3bb9eca32d81bf3f33cb4be25cc66
While this is unfortunate, it does however answer my question, so I will close this.


[BUG] Theme selection does not work with Firefox

In the add reference form, it is not possible to interact with the themes field.

After different tests on different browsers, I have the impression that the bug does not occur with a Chromium ported browser. I noticed the problem with Firefox, but I didn't have the opportunity to test on Safari.

For now I cannot log in anymore when I'm on Firefox. I think it's due to your updates on the CORS parameters. Let's talk about it and see what we can do!

@gaeVG I have done some research and must say I am a bit confused on the reason why this is not working.
So I have asked directly the library contributors for help: https://github.com/JedWatson/react-select/discussions/5294
Let's wait and see waht they say. Hopefully it's not a silly mistake and I don't ridicule myself, haha

Ok so the probleme was that for some reason on Frefox, the Select component was going inside the fieldset above. It wasn't clickable anymore.
The solution (maybe temporary) I found was to add some style specifically for firefox so that the theme selection is clickable again. It's not too annoying in terms of overall style.


Restructured Project Codebase to Be More Compact

Linked with Issue #16. After noticing that the CodeEngine, IKS, and common files in our codebase were getting all mixed together, we needed to separate the files in a way that they would be more readable to us as developers as well as anyone trying to use/work with our repository. This PR introduces that separation; the CodeEngine files have their own subdirectory, as do the IKS files; in addition, there are subdirectories for files shared between the two application types, as well as a subdirectory for the root module of our Terraform implementation.

Heads-up; the Travis tests failed because of the restructuring. When I restructured, I changed the positions of a ton of different files, and that broke some of the import statements in the testing. Should be normal behavior.


A new Section or Page with links to this resource should be added that documents the process to fully decommission SfB Server on prem

A new Section or Page with links to this resource should be added that documents the process to fully decommission SfB Server on prem.
For example, Removing SfB Server from an on prem environment by using Topology Builder to remove your deployment will cause users Skype related attributes to be set to $NULL and propagated to the cloud.  This has been reported in the MVP community.  In one instance the TelURI attribute was set to $NULL.
I don't believe this should happen so the PG should weigh in as to how SfB Server should be removed from the Topology and uninstalled in a manner that does not cause an outage for the customer.

@dinocaputo Hi we will evaluate adding this to the future documentation updates. Thanks!


Fix: activity bug

the upper-left side of the user page should only show current epoch keys-related spent
the upper-right side of the user page should only show current epoch keys-related receiving
the list of activities should check if it is a spent from user comparing to all epoch keys instead of current epoch keys
user.allEpks are sorted somewhere, causing the user.currentEpochKeys be wrong. Make the user.allEpks be protected.

user.allEpks are sorted somewhere, causing the user.currentEpochKeys be wrong. Make the user.allEpks be protected.

This confuses me, shouldn't that cause a compile error then?

don't know ˊˋ just find it be resorted somewhere causing the currentEpochKeys are wrong


Land use class and methods

Create a class to integrate land use data, following a compatible format to the ones used in population and food data

Adressed by 873969632bc4cd8c5900f31f08867a506e008642


 Doesn't seem to me like it has a good default value. Is there any practical reason to have it?

Every field of TxIn has a default value. Presumably the default TxIn would be the one that's populated by the default values of every one of its fields.
And the reason is so you can initialize a TxIn piece by piece.

I'm unsure if this is a good idea. I have an intuitive feeling that Default should be to generate meaningful, useful, default values. Just because parts have default, doesn't necessarily mean the the sum of default parts should be a default whole.
Initializing piece by piece can be achieved by something like fn new_empty() -> Self or even simply new. In contrast, the Default trait has a meaning - it comes into play when people write higher-level abstractions generic over having a meaningful, neutral and useful default value. Typically when skipping initializing a certain data is totally fine and useful. So my worry is that giving a meaningless default value to a any type is exposing user to a risk of not noticing, that they should probably have to handle that explicitly.

I specifically need an empty TxIn to give to miniscript::Descriptor::satisfy so that I can extract the witness from it.

@dpc I think you're over thinking it.
A default value is a nice thing as long as it's possible(i.e. with Box and references it's not).
step by step initialization, might not be the most idiomatic thing in rust (i.e in rust people generally prefer to initialize the fields and then construct a struct from all the fields) but sometimes it's still very useful.
Anyway, there are some RFCs to allow safe step by step initialization, until then I think using Default is what most of the ecosystem does.

Just to make sure it was noticed: fn new_empty() -> Self can return a new struct with empty fields, so impl Default is not necessary for "step by step initialization". Default is purely for generalizing over stuff that has a meaningful, neutral default value.
I agree that this is not a big deal one way or another, and I might be overthinking it here, though. :)

Anyway, there are some RFCs to allow safe step by step initialization, until then I think using Default is what most of the ecosystem does.

I am confused. I don't really see a point here. In this case, there's nothing preventing step by step initialization, be that let mut txin = Default::default() or let mut txin =  TxIn::new_empty(). And normally builders like https://docs.rs/crate/derive_builder  are doing a great job at providing flexible and convenient step by step initialization, and it is trivial for the compiler to get rid of any overhead.


browser.wait waits indefinitely after performing browser.restart

Referencing https://github.com/angular/protractor/issues/3881
Hi there!
I am facing a similar issue, when using browser.restart. In my case, a subsequent browser.wait call waits almost indefinitely, and times out after an obscene amount of time, although the page is loaded and visible the whole time.
I perform the restart operation in the Before hook of Cucumber:
Before(function(scenario) {         let currFeatureName=scenario.sourceLocation.uri;         console.log('feature : ',currFeatureName);         if(featureName===null)             featureName=currFeatureName;         else if(currFeatureName!==featureName)             return browser.restart();     });
Followed by a Given, where I perform a browser.get, followed by a browser.wait, before interacting with my element:
Given(/^user is logged in SNAPP$/,function(){         console.log('started : ');         browser.ignoreSynchronization = true;         browser.driver.get(browser.params.logon.url);         browser.wait(until.visibilityOf(element(by.id('logonDialogLbl'))),1000,'waiting to load url');         logonpage.logon();         browser.sleep(2000);
It is seemingly getting stuck in the browser.wait call, and times out, after waiting for an enormous amount of time.

Similar issue, which seems to happen to me since Chrome 64

Same here.  It was working since the Chrome 64 update.  Now when I perform a browser.get('someUrl') and do a subsequent browser.wait it stalls.  I now have to logout and log back in prior to each of my tests.  This is cumbersome.

same issue as @philsnyder

Same issue here. Calling a subsequent browser.wait after a browser.get() stalls.  Chrome 64.

same error like @gologox since Chrome 64.

Seems to be fixed with Chrome 65.

I'm on chrome 65 but the issue is still there.


rbd: Allow user to disable key rotation

This patch allows user to disable automatic
key rotation by annotating StorageCluster
with keyrotation.csiaddons.openshift.io/enable=false

/assign @iamniting

@black-dragon74 Have you tested it? If not pls add a hold on the PR and test it before it gets merged.

I tested an older version of this PR. The core implementation did not change. I am putting a hold, will cancel it once I test it out.
/hold

@black-dragon74 Have you tested it? If not pls add a hold on the PR and test it before it gets merged.

I tested an older version of this PR. The core implementation did not change. I am putting a hold, will cancel it once I test it out.
/hold

Thanks

Tested with the latest set of changes. Everything is working as expected.
/hold cancel


fix: update deployment.yaml of traps not to use projected volume

:tada: This PR is included in version 1.1.0-beta.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Try build operator using apollo-ci

This shouldn't be merged as-is, it's just a test that follows up on this discussion https://github.com/stackrox/stackrox/pull/3126#discussion_r974928788

/test all

Operator says
/usr/local/bin/stackrox-operator: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory

Looks like once again, we get tripped up by CGO_CFLAGS and CGO_LDFLAGS being set unconditionally in the build container. We should really remove this from the apollo-ci container. For now, I guess ENV CGO_LDFLAGS="" in the operator Dockerfile should suffice?

/retest

/test all

/test all

/test all


Intermittent test failure in stats_server_test

Intermittently, I get errors when running the test suite:
  1) test #measure when a job fails does not increment :total_running_time (Kitto.StatsServerTest)
     test/stats_server_test.exs:73
     Assertion with == failed
     code: Kitto.StatsServer.stats().dummy_job().total_running_time()== running_time
     lhs:  2.0e-6
     rhs:  1.0e-6
     stacktrace:
       test/stats_server_test.exs:82: (test)

The lhs and rhs change, but they are always off by a tiny amount.

As an additional note, the test seed doesn't seem to effect it. I can run with the same seed 5 times and the tests will generally fail 1 of those times.

This test has to be refactored, it sometimes breaks in travis too :-/


timer

simple timer displayed in seconds

The new feature code has been merged down to main at this point.


Manage ssh host keys and certs

I'd like to add the ability to manage ssh host keys (e.g., ssh_host_rsa_key and ssh_host_rsa_key.pub) and especially host key certificates (e.g., ssh_host_rsa_key-cert.pub), but I can't find the place in the web console to do so, nor have I found the documentation on how to do so.
The ssh.config middleware call returns these keys and certs, but I don't know the best way to update them. By RTFSing, I've found a number of datastore calls that can probably do the trick, but since I can't find documentation for this, I suspect this is not the recommended way of doing it.

I think you have to updated them in /data/freenas-v1.db.services_ssh.
If you look at the date in /usr/local/etc/ssh/ssh_host* you will likely see the current boot-time. Which service/call writes them out i never bothered to check tho.

Yes, that's the file that gets updated by the datastore calls that update ssh keys. But I'm looking for the recommended way of updating these keys.
Actually, I'm more interested in updating the certs, but can't find any documentation or guidance on how to do this.

@crpb Can I ask use case of changing host keys?

In my case, I'd like to sign the host key with my site CA. In practice, this means generating a key on a secure machine, then installing it on the TrueNAS box. So this could apply to any site where the admins have a key distribution system and want to install their own keys.


I'm having trouble downloading from funimation

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2<IP_ADDRESS>. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2<IP_ADDRESS>

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.funimation.com/shows/cowboy-bebop/asteroid-blues/']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 3.4.4 - Windows-10-10.0.15063
[debug] exe versions: none
[debug] Proxy map: {}
...
<end of log>

Description of your issue, suggested solution and other information
I'm trying to download from funimation. When I entered this (youtube-dl.exe -v https://www.funimation.com/shows/cowboy-bebop/asteroid-blues/) into command prompt, here's what I got:
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.funimation.com/shows/cowboy-bebop/asteroid-blues/']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 3.4.4 - Windows-10-10.0.15063
[debug] exe versions: none
[debug] Proxy map: {}
[Funimation] asteroid-blues: Downloading webpage
[Funimation] 116802: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 404: NOT FOUND (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp_2hklmx2\build\youtube_dl\extractor\common.py", line 503, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp_2hklmx2\build\youtube_dl\YoutubeDL.py", line 2168, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default

Yeaaaah, they changed a bunch of stuff.  I'm trying to work out what they changed the flow to, looks like a complete rewiring though.


refactor(emit): Reverse behaviour of the composed flag.

It was originally inverse to the default behaviour to preserve backward compatibility when the spec
churned. Now that we can make breaking changes towards 5.0, we can make this behave as it should by default, for encapsulation purposes.
BREAKING CHANGE: fixes #768

Is it really worth writing a test to assertion built-in behaviour? Maybe to see that we're adhering to the default behaviour.

yup exactly

So I've refactored the tests to see that we're passing the correct options, custom options and custom detail. I've removed the old tests as they were testing built-in behaviour. All we're doing is passing along information. Pls review.

Closing to retarget to the 5.0 branch.

Oh, you can retarget now. Win!


Azure DevOps notifications not appearing

Information

Onefuzz version: 3.1.0
OS: any

Provide detailed reproduction steps (if any)
Create a job that will find a crash, with an ADO notification
Expected result
When a crash is found, an ADO issue is opened.
Actual result
A crash is found, but no issue is opened.

Exception from service logs:
Exception while executing function: Functions.queue_file_changes Result: FailureException: AttributeError: 'ADO' object has no attribute 'client'
Stack:   File "/azure-functions-host/workers/python/3.7/LINUX/X64/azure_functions_worker/dispatcher.py", line 405, in _handle__invocation_request
    invocation_id, fi_context, fi.func, args)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/azure-functions-host/workers/python/3.7/LINUX/X64/azure_functions_worker/dispatcher.py", line 607, in _run_sync_func
    func)(params)
  File "/azure-functions-host/workers/python/3.7/LINUX/X64/azure_functions_worker/extension.py", line 215, in _raw_invocation_wrapper
    result = function(**args)
  File "/home/site/wwwroot/queue_file_changes/__init__.py", line 38, in main
    file_added(event, last_try)
  File "/home/site/wwwroot/queue_file_changes/__init__.py", line 25, in file_added
    new_files(container, path, fail_task_on_transient_error)
  File "/home/site/wwwroot/onefuzzlib/notifications/main.py", line 155, in new_files
    fail_task_on_transient_error,
  File "/home/site/wwwroot/onefuzzlib/notifications/ado.py", line 264, in notify_ado
    ado.process()
  File "/home/site/wwwroot/onefuzzlib/notifications/ado.py", line 215, in process
    for work_item in self.existing_work_items():
  File "/home/site/wwwroot/onefuzzlib/notifications/ado.py", line 90, in existing_work_items
    self.client, project=filters.get("system.teamproject")


restructure docs under main topics

As discussed with @Hofer-Julian, this follows the lead of the iMOD documentation, to use the top navigation for the main topics, and uses the sidebar for organizing the main topics.
These are the main topics proposed in this PR:

Naming suggestions welcome. We could remove the Julia and Python part and just use "Core" and "Tooling".
The main diff here is that I moved the usage docs from the main page to a separate page under the "Julia core" topic. More work is still needed on the docs as for instance the equations page is getting quite outdated.
Each topic has an index pages that you land on when you click the topic. I wrote some text for those, aiming for a brief overview text with (introduced) links to the other pages in the topics.

Naming suggestions welcome. We could remove the Julia and Python part and just use "Core" and "Tooling".

IMO it’s fine as is


Development: Add student code of conduct and apso as a static assets

Checklist
General

[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context
The student code of conduct linked in the template of plagiarism case post and linked in the post created by continuous plagiarism control was no longer available.
Original thread on Slack: https://ls1tum.slack.com/archives/G6TCVL6HL/p1696873741965929.
Description
The student code of conduct is now a static asset of Artemis.
Steps for Testing
Prerequisites:

Log in to Artemis.
Go to TEST_SERVER_URL/content/documents/student-code-of-conduct.pdf and check if the PDF loads.

Review Progress
Code Review

[ ] Code Review 1
[ ] Code Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Ping @b-fein @dfuchss you should probably replace these files in your local instance / fork.

I can look at it next week

This PR is stacked and should be merged after #7302 is merged


1028|Recover a Tree From Preorder Traversal |C++

Recover a Tree From Preorder Traversal -
Add C++ code
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[] Improving Code
[] Improving Documentation
[] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[] Python
[x] C++
[] Java
[] SQL

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Pls assign this issue to me.

please assign this to me

This issue is now open for assignment.


Status Bar Won't Hide - iOS7

Hi there - Great component!  Having a bit of a showstopper issue for my app though.
After implementing the SWRevealController my status bar no longer hides.   I have tried the following:

Hiding via IB
Hiding in my base view controller using

(BOOL) prefersStatusBarHidden

Hiding using this code in viewdidload.

[self prefersStatusBarHidden];
[self performSelector:@selector(setNeedsStatusBarAppearanceUpdate)];

Prior to SWRevealController I was just using 2 above and everything work perfectly.  Any ideas?

@perryao Yes, did you get it working in the end?

I have the problem of the navigation bar being resized. Any update? Thanks.

Has anyone found a solution regarding the navigation bar being resized?

https://github.com/wicharek/UINavigationBar-FixedHeightWhenStatusBarHidden

@iDevelopper Thanks for the link, I will try this out.
@wicharek Is there a Cocoa pod for this library?

@jrejaud nope, didn't had chance to add it. It is a very simple category though, just a single header and .m-file. Feel free to use it. However, note that although it should be working in general, in some cases it can cause a "jumpy" effect when showing/hiding status bar with animation.
P.S. Will add a podspec if you need it :)

No worries, I'll just copy and pasted it.
Cheers, Jordan Rejaud, EIT M.S. Carnegie Mellon University<EMAIL_ADDRESS>jordanrejaud.com
On Fri, Mar 4, 2016 at 4:54 AM, Vitaliy Ivanov <<EMAIL_ADDRESS>> wrote:
@jrejaud nope, didn't had chance to add it. It is a very simple category though, just a
single header and .m-file. Feel free to use it. However, note that although it
should be working in general, in some cases it can cause a "jumpy" effect when
showing/hiding status bar with animation.
P.S. Will add a podspec if you need it :)
—
Reply to this email directly or view it on GitHub .


bal-input add mask for phone numbers with and without the prefix (+41)

[ ] Swiss mask
[ ] Germany mask
[ ] France mask
[ ] Italian Mask
[ ] Belgium
[ ] Luxembourg
[ ] General phone mask = number and spaces

First gather the mask from the sbu's
implement the mask in the bar-input

This is a prerequisite of the bal-phone-input component
Requested by @stefanbukovski

prefix could be 0049 or +49

moved to https://github.com/baloise/design-system/issues/714


operator pmem-csi-os (v1.0.2)

We have updated the below files:

Updated PMEM-CSI driver container image version sha key (https://connect.redhat.com/projects/6112818bee4963304e288f24/images)

Updated annotation yaml file with openshift version 4.10

We have renamed the pr-title

Invalid pr-title


Ensure compatibility of parser with earlier python versions

open_ncml only runs on Python 3.10.

See #14


dns-sortlist not recognized in network-config

Hi Stéphane,
I entered this ticket for cloud-init on launchpad.  I'm pretty sure the issue is in their code, but I thought you might be interested as well.
I'm using LXD with Ubuntu images, and cloud-init to do initial setup of container.  I'm not sure, but I believe the issue is in cloud-init, but would appreciate a pointer to the right location if not.  Currently using network-config meta data, cloud-init takes the following config and converts correctly:
version: 1
config:

type: physical
name: eth0
type: nameserver
address: ['xx.xx.xx.xx']
search: ['example.local', 'example.org']

However including the following line is not recognized:
sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx']
Please add support for this standard nameserver option.

Yeah, LXD"s involvement here is limited to passing a big blob from the user (user.network-config) to cloud-init through a file on the filesystem.
What's valid data is entirely up to cloud-init and related specifications (network stuff may involve nplan too nowadays).
So this should indeed be tracked entirely on Launchpad against cloud-init. If/When this is supported in cloud-init, things will just work without any change being needed on the LXD side.

@stgraber @brauner Good morning Stephane and Christian.  I've added this over at launchpad under cloud-init and cloud-init(ubuntu).  They've been up for months.  I can't imagine it's more than a five minute task, and half a dozen lines of code, but it's not even been looked at.  TBH, both groups seem pretty dead.  Any ideas on where else this could be posted that is actually active?

@smoser FYI ^

@jfgibbins can you point at a bug you opened ? sorry if we've missed it.
I'm not quite sure theres a lot we can do with 'sortlist' as we're kind of a middle man to the network configuration tool ( ifupdown/resolvconf in 16.04, 16.10 and netplan in 17.10+).

#1704402
#1711967
@smoser Hey Scott, now it's been a while since I looked at this, but isn't cloud-init handling the writing of the resolv.conf for nameserver and domain search already?  This one just be adding one more line to the file.  At one point I could have sworn I found where the code was doing that part, but it's been a few months.  If not, please tell me which code is actually handling that, and I can get a bug report posted there.

@smoser Well, I'm not following the same path I did before, but if I'm following the code right, cloudinit/distros/debian.py is calling the renderer, in this case cloudinit/net/eni.py which is actually writing the /etc/network/interfaces/50-cloud-init.cfg file.  If that's correct, it should just be adding dns-sortlist under def _iface_add_subnet(iface, subnet):  in eni.py?  As it stands now, the entry never makes it into the cfg for ifup/resolv to even know about.  According to the man resolvconf, dns-sortlist is a valid option to be passed to resolvconf from ifup, which I know works, cause if I manually add the parameter as such it shows up in resolv.conf.
iface lo inet loopback
dns-nameservers x.x.x.x
dns-search greywolfe.local greywolfe.org
dns-sortlist x.x.x.x x.x.x.x
Honestly, I'd attempt a push/pull, whatever it's called on launchpad, but I still screw up my own git, and frankly, not a programmer, and would hate to butcher your code.

P.S. and don't worry, not even going to touch the subject of modifying gai.conf for the networking through cloud-init.  Well, unless you get really bored, let me know. ;)


Wallet Connect integration

I've builded a first integration of the WalletConnect Provider. There are now 2 buttons for each supported provider(Metamas and WalletConnect). I think it would make sense to use some kind of popup (like for example Uniswap) to show the users the different ways they can select to choose a wallet.
We also need a infura.io id for our project. Does anyone know if there are developer dao mail accounts which we can use ....? @goldzulu @rasmuscnielsen
From a technical standpoint, I created a class called WalletProvider which encapsulated the logic of using different wallet providers. More providers could be easily added by extending this class.

@AlexNi245 This is awesome, thanks so much for working on this. Will try and find time to review it soon.
Looking at the diff, I feel there are some changes that were reverted from my latest commit. Ie some comments, and tokens = ref([]) was changed to ref(null).
Any chance perhaps you started the work before you had pulled down latest update?
If so, perhaps you could try and create a new branch from the latest feat/wallet, and cherry-pick the commits containing your work on the wallet connect feature, and see if that solves it? :-) In this case you might just have to create a new pr afterwards though from the updated branch.

Yes, you're right. I forgot to merge the upstream branch before I started working. However, I merged the upstream later on and I seemingly reverted a few of your changes during the merge.
I made a commit to bring your changes in useWalletState.js back. If there are any other files affected, please let me know :)

@AlexNi245 Sorry for the delay! Just tested this locally and works perfectly 👏 Well done!
I'll merge and do a bit of refactoring + design work on #44 branch :-)
As for the Infura.io I have absolutely zero idea. I hope someone will reply to you on the discord. As for committing the key to GIT, I guess it's a public-facing key given that will be bundled with the frontend anyway - so no security issues there right?


Drop thunder.compile

...at the cost of removing things that still rely on it (in particular transforms changing the signature that have not been ported over).
It seems unmaintained in Q1+Q2, no plans to revive.

triage review: yes, please.

Closed by #1114 built on #837.


Fix: add ericsson mibs

Adding mibs:

ERICSSON-ALARM-MIB
ERICSSON-ALARM-PC-MIB
ERICSSON-ALARM-TC-MIB
ERICSSON-TC-MIB
ERICSSON-TOP-MIB

:tada: This PR is included in version 1.15.7-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Props scale not working

Props scale not working in latest version 1.1.4, may be  it is not published yet?

已收到您的邮件，会尽快进行处理

@hrynko Can you help me with the scale prop. I cant figure out how to work with it. I tried setting it to :scale="20" for example. This is supose to zome in/out, right?

已收到您的邮件，会尽快进行处理

This is supose to zome in/out, right?

Not really, it represents the ratio of canvas size to document size. So it is more about optimization, you can adjust it based on your canvas size if you need to optimize the memory usage (the larger scale value, the better image quality, the more memory usage).
This prop has an automatic value, so you don't have to use this prop unnecessarily. And to implement scaling, I would suggest considering the width prop and constraining the component in a scrollable parent block.

This is supose to zome in/out, right?

Not really, it represents the ratio of canvas size to document size. So it is more about optimization, you can adjust it based on your canvas size if you need to optimize the memory usage (the larger scale value, the better image quality, the more memory usage).
This prop has an automatic value, so you don't have to use this prop unnecessarily. And to implement scaling, I would suggest considering the width prop and constraining the component in a scrollable parent block.

So what you mean is to change the width of the parent element of the canvas to implement the scaling function, for example using transform:translateZ(0) scale(10)

已收到您的邮件，会尽快进行处理

em~~~~~ scale not working

same here

已收到您的邮件，会尽快进行处理

It's been a while, but scale prop is now included in 1.1.5. Sorry for delay.

已收到您的邮件，会尽快进行处理


can not reproduce the AP on coco dataset

When I downloaded the pre-trained model on the coco dataset you provided for inference, I found that the instance segmentation accuracy of the coco data set always differs by 0.2AP. The following is the experimental result.

METHOD
BACKBONE
PQ
PQTH
PQST
AP
MIOU
#PARAMS
CONFIG
CHECKPOINT

OneFormer
Swin-L†
57.9
64.4
48.0
49.0
67.4
219M
config
model

57.9
64.4
48.0
48.8
67.4

OneFormer
DiNAT-L†
58.0
64.3
48.4
49.2
68.1
223M
[config]
[model]

58.0
64.3
48.3
49.0
68.1

The following is my experimental environment.
Environment info:
-------------------------------  ------------------------------------------------------------------------------------------------
sys.platform                     linux
Python                           3.8.16 (default, Jun 12 2023, 18:09:05) [GCC 11.2.0]
numpy                            1.24.3
detectron2                       0.6 @/home/bingxing2/gpuuser206/OneFormer/detectron2/detectron2
Compiler                         GCC 6.3
CUDA compiler                    CUDA 11.3
detectron2 arch flags            7.0
DETECTRON2_ENV_MODULE            <not set>
PyTorch                          1.10.1 @/home/bingxing2/gpuuser206/.conda/envs/oneformer/lib/python3.8/site-packages/torch
PyTorch debug build              False
torch._C._GLIBCXX_USE_CXX11_ABI  False
GPU available                    Yes
GPU 0,1,2,3,4,5,6,7              NVIDIA A100-PCIE-40GB (arch=8.0)
Driver version                   510.47.03
CUDA_HOME                        /usr/local/cuda
Pillow                           9.5.0
torchvision                      0.11.2 @/home/bingxing2/gpuuser206/.conda/envs/oneformer/lib/python3.8/site-packages/torchvision
torchvision arch flags           3.5, 5.0, 6.0, 7.0, 7.5, 8.0, 8.6
fvcore                           0.1.5.post20221221
iopath                           0.1.9
cv2                              4.7.0
-------------------------------  ------------------------------------------------------------------------------------------------
PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) oneAPI Math Kernel Library Version 2021.4-Product Build 20210904 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v2.2.3 (Git Hash 7336ca9f055cf1bfa13efb658fe15dc9b41f0740)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - LAPACK is enabled (usually provided by MKL)
  - NNPACK is enabled
  - CPU capability usage: AVX512
  - CUDA Runtime 11.3
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_37,code=compute_37
  - CuDNN 8.2
  - Magma 2.5.2
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.3, CUDNN_VERSION=8.2.0, CXX_COMPILER=/opt/rh/devtoolset-7/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.10.1, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

Hi @HuYanchen-hub, thanks for your interest.
Do you set the task=instance when running the evaluation script? The numbers you shared seem to correspond to task=panopticin the evaluation script. We mention the same in the instructions here.
I ran the evaluation on an A100 myself now and obtained the following results for the DiNAT-L backbone:
#### DiNAT-L Oneformer
[07/05 05:47:28 d2.evaluation.testing]: copypaste: Task: segm
[07/05 05:47:28 d2.evaluation.testing]: copypaste: AP,AP50,AP75,APs,APm,APl
[07/05 05:47:28 d2.evaluation.testing]: copypaste: 49.2071,73.8117,53.6113,29.4197,53.7316,70.9744

You might experience a variance of 0.1-0.2 units when running evaluations on different machines (I remember noticing something like that while experimenting).

Thanks for your reply, when I set task=instance, I got the correct result. But when I use swin-L backbone to test instance semantic tasks with task=semantic, I get mIoU which is lower than task=panoptic. I would like to ask if the mIoU results you reported are the higher of them? Or is it due to variance caused by different experimental equipment?
copypaste: Task: sem_seg
[07/05 21:06:35 d2.evaluation.testing]: copypaste: mIoU,fwIoU,mACC,pACC
[07/05 21:06:35 d2.evaluation.testing]: copypaste: 67.2288,72.4984,78.5884,82.9312

And when I use DiNAT-L Backbone to test with task = panoptic, the experimental result of PQ_{st}is also 0.1 different from your result.
Task: panoptic_seg
[07/05 21:14:12 d2.evaluation.testing]: copypaste: PQ,SQ,RQ,PQ_th,SQ_th,RQ_th,PQ_st,SQ_st,RQ_st
[07/05 21:14:12 d2.evaluation.testing]: copypaste: 57.9436,83.7602,68.4097,64.3089,84.9244,75.2713,48.3356,82.0030,58.0525

OneFormer is a very good work, and we want to support this algorithm in the open source object detection toolbox mmdetection, so we need to master more experimental details. Thank you for your help.

Hi @HuYanchen-hub, thanks for working on adding the support of OneFormer to detection!
We report the metric scores corresponding to the metric-focused task for each task. So, we report mIoU with task=semantic. I believe the difference you notice is within the variance range both for mIoU and PQ_st.

Thanks for you reply!

Hi @HuYanchen-hub, thanks for working on adding the support of OneFormer to detection!
We report the metric scores corresponding to the metric-focused task for each task. So, we report mIoU with task=semantic. I believe the difference you notice is within the variance range both for mIoU and PQ_st.

Thank you very much, get it!


Please drop the requirement marking it as "isDesktopOnly"

Is your feature request related to a problem? Please describe.
Doesn't work on Android.
Describe the solution you'd like
Please change that.
Additional context
Admittedly it does not make much sense on a phone but a tablet or a ChromeOS device would profit from this.

duplicate (#34)


Getting this template released

@emilianozublena hey, wanted to check with you what are your plans for this template. If you still want to maintain it, as I was thinking, basing on the fact that it got contribution and there are starts, that we should finally release it as official asyncapi template.
But of course it makes sense only if it is going to be maintained

Sorry for the late response @derberg, trying to get back into a more active state around this template. I'd publish it ofc, i'll make sure to answer any potential issues/PR's back and also work around a few things that we can improve.

@emilianozublena in Poland we say "better late than never" 😆
good to see you back and that you want to be more active here. I was recently approached by one guy from Poland concerned about the state of the template. I think he was willing to contribute 😄
@Ferror good news, Emiliano is back 💪🏼 we probably brought him with our thoughts 😄 I suggest you open the issue and describe your ideas for improvements there.
And please folks, forget about yesterday's game. We let you @emilianozublena win because Lewandowski felt sorry for Messi not scoring the penalty. Normally Poland plays better football, at least I hope so 🤣

Awesome to hear someone's willing to contribute, that'll make things easier for sure. Open to any PR's or even issues like this to discuss of things we need to change/improve and/or add :)
@derberg i saw messi and lewandoski arguing, i think that prbly he told messi that now they're even lol

Should we close this issue and let @Ferror open a new one to start chatting about it? @derberg

I definitely recommend running a separate issue about possible contributions. But please leave this one open.  In the coming days I will contribute PR that will enable automated releases in this template.
Would be great if you could rename this repo from asyncapi-php-template to php-template as it is already under asyncapi and npm name will be @asyncapi/php-template


Migrate docs from reST to MyST

Let's use the MyST Parser Sphinx extension? https://myst-parser.readthedocs.io/en/latest/

Agreed!


Criado usando o Colaboratory

Blog post do Leão

Exercício 1
https://github.com/thiagoverdan/photo-colorization/blob/b303042a82e4030b4f05f6a1391d3dcb3e92422f/_notebooks/2021-09-04-Blog-post-do-Leao-thiagoverdan.ipynb